1. Kindl of Audit to be Conducted (Technical or Functional)
2. Number of questions for the Audit
3. Structure of list of Questions (Question drill down level)
4. Valuation type of Questions
5. Question Priorites
6. What kind of Audit Controls to be implemented
7. Audit purpose
8. Audit Type
9. Kind of rating for the questions

Figure 12.0

• System Overview
• Security & Access Protection
• Workbench Organizer
• Transport System
• Accessing and Logging DB Tables
• Job Request Procedure
• Documentations
• System Logs
• Batch Input Interface
• Master Data Changes
• Reconciling Posting Data Closing
• Invoice Checking and Posting Run
• Business Process Auditing
• BASIS Audit

You need to collaborate with your supply chain partners. But you don’t need a separate interface for each and every one. Especially when those interfaces push up costs and drag down innovation. Time to discover SAP Information Interchange OnDemand. One universal interface that connects you to everyone in your value chain. Get the full story in a new e-book: http://www.sapebook.com/interchange

The document shows how to create the characteristics and classes to help you maintain waste packaging data if you do not have the module available in your system, I hope you find it useful, and i'm sure many of you will be able to improve on this method.

Waste packaging is generally required for six specific material types as listed below, I have also included two further fields; one field records the ‘other material’ type, such as Rubber and one records the value.

1.     Paper/Card

2.     Glass

3.     Aluminium

4.     Steel

5.     Plastic

6.     Wood

7.     Other

8.     Other Material Type

All of the above values are maintained for three categories, primary, secondary and tertiary packaging, Create the characteristic for each commodity type for primary, secondary and tertiary packaging. I have used the naming convention as below

·         Primary packaging        (Packaging discarded by the consumer) P1 – P8

o    P1_Paper

o    P2_Glass

o    P3_Aluminium

o    P4_Steel

o    P5_Plastic

o    P6_Wood

o    P7_Other

o    P8_Other_Material_Type

·         Secondary packaging    (Packaging discarded by the distributor/retailer)  S1 – S8

·         Tertiary packaging         (Packaging used for the transportation of goods) T1 – T8

Enter t-code CT04

Enter characteristic name

Press 'Enter'

Click ‘Yes

Select Data Type ‘NUM – Numeric Format’ and Value assignment ‘Single-value’

Enter Number of Characters, Decimal Places and Unit of Measure

The Template and Exponent Display values are automatically populated

Select the Values tab

Check the ‘Additional Values’ box and leave the ‘Char.Value’ field blank, this way you can enter any value when maintaining the data as the weight of the material can vary.

Save changes

Repeat as required for other commodities, Glass, Aluminium, Steel, Plastic, Wood, Other, for Primary, Secondary and Tertiary.

Next you want to create the last characteristic to describe ‘Other Material’

Follow the steps as above this time using the Data Type ‘Character Format’, it should look like the screenshot below.

Select the Values tab

Check the ‘Additional Values’ box and leave the other fields blank, this will enable you to enter any value, such as Rubber, Copper Brass, etc when maintaining data.

Save changes

Repeat for steps for secondary (S8_Other_Material) and tertiary (T8_Other_Material

Now you have the basic characteristics in place the next step is to assign them to a class.

We don’t want to see multiple characteristics for each requirement so we will assign these to a User Defined Class <Class Type 031> for Primary, Secondary and Tertiary packaging.

Creating a User Defined Class

Enter t-code CL01, then enter the class name and class type, and description.

Select the Characteristics tab, assign the characteristics P1 through to P8 as below and save changes.

Repeat the process to create user defined classes for secondary and tertiary packaging.

Next step is to create user defined characteristics

Enter t-code CT04

Enter the name and description as below; select the characteristic ‘Primary’ as the ‘Data Type’

Save changes, and repeat for secondary and tertiary.

The final step is to create a class for materials <Class Type 001> to bring the user defined classes together.

Enter t-code CL01

Enter the class name and class type, and description as below.

Select the characteristics tab, assign the characteristics as below and save changes .

Maintain data when creating new materials in MM01 by selecting Classifications view, and assigning the classification’ waste packaging’ to the object.  You can also use LSMW to populate existing objects.

To view data assigned to objects

Enter the transaction code MM03, enter the material number, then select Classification.

If prompted, on the next screen select Material Class (Type 001) and press 'Enter'

Classifications that are assigned to objects (materials) are listed under assignments, if you have a lot of classes assigned to a material use the scroll bar to view all classes assigned to an object, select the appropriate class and double click to move to the top.

If characteristic values are not visible, select the line

double click, to view the data.

Viewing the data in the material master record is fine if you only need to see the data assigned to one material, as the purposes of this exercise is to enable you to report for multiple objects/materials you can use this method.

Enter the transaction code CL30N, to call the Find Objects in Classes function

You can also call this function from MM03, then press F4, click on the drop down menu and select Materials for Class

Specify the class name and type

Press 'Enter'

In this screen you can either specify the values you want to view, or leave the fields blank and press F8 to view all values

Use the 'Export' icon to export data to Excel.

Be sure to read this interesting and informative White Paper from SAP's Frank Ruland and Siddharth Taparia featuring customer Artoni:

I figured out some items valuation method was not correct after performed receiving.

that item naver sold until now and valuation method is Standard.

is there any way to change valuation method of that item?

if that possible, let me know that SQL Query.

Please help me.

Direct procurement process:

The process of procuring materials that are directly used for production purposes is known as the direct material procurement process.

Using the direct procurement procedure, you can order BOM components for a planned order directly instead of via the warehouse.

Business scenario:  Consider the scenario of an enterprise that produces washing machines. The parts or components of a washing machine, such as electromechanical buzzers, suppressors, and electronic timers, are procured from external sources. As these parts are directly used in the manufacturing of washing machines, they are purchased, stored in the inventory, and issued to the production department, depending upon the department's need.

There are two ways of doing this procedure

1. Using special procurement key

2. Using item category 'non stock item'

SAP recommends the process to use with special procurement key

Required Settings in SPRO:

Step1: Define Direct procurement in MRP

IMG-> Production-> MRP-> Plant parameters-> Carry out overall maintenance of plant parameters

Indicator 1 or 3 are identical and used if direct procurement is to be triggered during MRP run

Indicator blank or 2 are identical and used if direct procurement is to be triggered only after the creation production order

Step2: Define Special procurement key:

IMG-> Production-> MRP-> Master data-> Define special procurement type

Master data setting: Assign the special procurement key in MRP2 view for the BOM component material master

Process:

To understand the process easily, I just created one simple example where the finished product BOM contains one component.

FERT# 2001682

ROH# 3003340

When you create the production order for the finished product, the MRP creates the  purchase requisition for the components with ‘direct procurement’ as the MRP element in MD04 screen as shown below,

Important points:

1. Purchase requisition created for direct procurement is firmed (marked as * in MRP element) which means you cannot change the quantities and dates for this requisition. The deletion button will be grayed out and deletion of firmed requisition is not possible.

2. You can even set the direct procurement in the BOM component when you want to use it for a particular BOM only. You enter this data in MRP data area of BOM component and this entry overwrites the entry in the material master.

3. You can also use the direct procurement process in networks using item category ‘non stock item’. You can determine whether a purchase requisition is created for each material or whether one collective requisition for all externally procured materials and services is created per network in SPRO under below link

IMG-> Project systems-> Structures-> operating structures-> Networks-> Settings for networks-> Specify parameters for network type.

Client Administration – Test

1. Define client

A client is an independent business unit within an R/3 system,it is the organizational and legal entity in the SAP system. In a physical SAP system there can be multiple clients in each of the system of SAP system landscape.A client has its own set user data.

1. How to create a client & how many clients we can create in sap R/3 system.

1 Transaction code SCC4, click on the “New Entry” button is pressed.

2 In the Client creation screen all the required items must be filled.

3 The client number, name & Cityare entered first.

4 Then Logical system is defined and currency, Role of a client, Changes and transports for client-specific objects.

5 Client-independent object changes category and the next is Protection: Client copier and comparison tool.

6 Once a Client is saved an entry is made in the table T000.

1. Name the different types profiles we can use for clients copy.

The different types of profiles are as follows

1 SAP_ALL - All client specific data without change document.

2 SAP_APPL - customizing and application data.

3 SAP_CUST - copy customizing data.

4 SAP_CUSV - customizing and report variants.

5 SAP_UAPP - user master records, report variants and Applica data.

6 SAP_UCUS - user master records and customizing.

7 SAP_USER - user master record and authorization profiles.

8 SAP_UCSV –customizing variants and master records.

1. How we can restrict the client to do changes and what are the options.

1 If you want to use this client as a sandbox client and you do not want to record or create a change request every time a change happens to the client then “Changes W/O automatic recording” is the right option.

2 If all the changes to the client should be recorded in a change request then “Automatic recording of changes” is the right option. You must choose this option for your master configuration client.

3 If “No changes allowed” is chosen, then no changes will be allowed to this client. You must choose his option for clients in the production environment to protect your system.

4 “No transport” option is used when you do not want any user to create a transport from this client.

1. What are the Pre - existing clients in SAP system & explain them briefly.

SAP comes with some pre-configured clients.

With a standard installation, SAP delivers 000, 001 and 066 clients which should not be changed/deleted from the system.

1 Client 000 is considered to be a SAP reference client and contains the client-independent data of R/3. Special admin tasks are performed here as user SAP* or DDIC.

2 Client 001 is a copy of client 000 with the difference being that the data is client-dependent.    Do not change any settings here. It should remain standard.

3 Client 066 is there for SAP Early Watch service. This client enables SAP to remotely access the customer system. SAP provides this service to the customer to improve the system performance. Client 066 should not be changed or deleted from the system. 

1. What is the difference between Client dependent & Client Independent?

Client-independent data such as ABAP Programs, R/3 repository objects through the entire system. Other data is client-dependent. Meaning, it can be viewed from one client. Client-dependent data includes customizing application and user data.

1. How do you identify the table which is client dependent or Client Independent?

To know whether a table is client dependent or independent you can search for a field MANDT. The client dependent tables always include the client field ‘MANDT’ as a part of the primary key.

1. Explain the client scenario for the three system landscape?

1 Client 200: Customizing/Development (CUST)

    All application customizing & system development are performed in this client.

2 Client 210: Sandbox (SAND)

   This is a general test client, initially created as a copy of the 001 or 000.

3 Client 220: Customizing/Development Testing (TEST)

   Copies of customizing changes are moved to this client (TEST) for unit testing.

4 Client 300: Quality Assurance Testing (QTST)

   Copies of customizing changes are moved here for system testing. The testing here is usually     performed by a different team.

5 Client 310: End-user Training (TRNG)

                  End-users are trained on the R/3 functionality in this client.

6 Client 400: Production (PROD)

   This client is used for the productive operation of the configured R/3 System.

7 Client 410: Pre-Production (PPRD)

                  Used by the project team to perform final testing of the customizing changes before

                  They are transferred to the production client (PROD).

1. Explain the different types of client copy and brief description about each client copy?

The Client Copy can be done in 3 ways

1. Local Client Copy: Here the data is copied into new Client from a client within the same system.
2. Remote Client Copy:In Remote copy the data is copied into the new client from a Remote system.
3. Client Transport:Data can also be filled into the newly created client, from another system by way of Transport Request.

1. Explain how to delete a client?

Delete a Client from SAP system

First log on to the client to be deleted with the proper authorization to delete a client.

1. Choose path Tools à Administration à Client admin à Special functions à Delete client or transaction SCC5

1. T-code to check the client copy logs.

SCC3

1. What are the pre necessary steps we need to take before doing the client copy?

1 For the stability of the system, always schedule the client copy in the nighttime when the users are not working in the system.

2 For the stability of the system, always schedule the client copy in the nighttime when the users are not working in the system.

3 For the best performance, always schedule the client copy in the background.

4 The value of maximum online runtime parameter “max_wp_run_time” in the instance profile might need to be increased for a large client copy.

5 Proper authorizations are required to run the client copy. As a basis system administrator you should have SAP_ALL profile to complete a client copy successfully. So SAP* is recommended as it has all the authorizations needed by the client copy.

6 Always check the Table space usage % in database portion before & after executing a client copy and also at the time of Client Copy process.

7 The main memory plays a significant role in the client copy. Make sure that you have enough memory to finish the client copy without any problem.

8 If the client copy is locked by another client copy run, then check the log before deleting the lock entry in SM12 to remove the lock.

1. Name the table where we can find the client related information?

T000

1. Which client setting you prefer for the sandbox and customizing client?

Automatic recording of changes & No changes to cross-client customizing objects

1. Which client setting you prefer for the Quality and Production client?

No changes to Repository and cross-client customizing objects & No changes allowed

Hi ,

This below info explains in detail about, How do you handle vendor installment payment terms in SAP R/3.

It would be very helpful for both MM/FICO Consultants.

Installment payment terms

1        VENDOR PAYMENTS IN INSTALLMENTS

2        INSTALLMENT PAYMENTS

2.1          CREATE ‘MAIN TERM’

2.2          CREATE ‘INSTALLMENT TERMS’

2.3          DEFINE INSTALLMENTS

2.4          ENTER THE NEW PAYMENT TERM IN THE VENDOR MASTER

2.5          TEST HOW THE PAYMENT TERM WORKS

3        AMOUNT SPLIT

3.1          TEST THE AMOUNT SPLIT

1    Vendor payments in installments

You want to make vendor payments in installments. How do you handle this in SAP R/3?

You have two alternatives:

1.  Use installment payment terms

2.  Activate document split

Of course you can also use partial payments or residual items, but these have nothing to do with payment terms.

2    Installment payments

Instead of entering several line items, you only enter the data for one item. The breakdown is carried out by the system automatically by means of the payment terms.

Configuration

You need to create four payment terms. First you create the ‘main term’ for the Installment. Here R001. This payment term is set to vendor master.

The Installments need also payments terms. Here you set the day limits for payments.

In IMG activity Define Terms of Payment for Installment payments you define the percentages and assign the Installment payment to the ‘main term’.

2.1    Create ‘main term’

Press New entries

  Choose   Save.

  Choose Back.

2.2    Create ‘Installment terms’

Press ‘New entries’

  Choose   Save. 

ChooseBack

2.3    Define Installments

2.4    Enter the new payment term in the vendor master.

Ensure that the key is entered in the vendor master record which represents the specified terms of Payment.

2.5 Test How the Payment term Works

CreatevendorinvoicewithtransactionFB60.Foroffsettingpostinguseaccount476000Officesuppliesandcostcenter 1000.UsetaxcodeV0.

Simulate and Post

  2.5    Testhowthepaymenttermworks

CreatevendorinvoicewithtransactionFB60.

Foroffsettingpostinguseaccount476000Officesuppliesandcostcenter 1000.UsetaxcodeV0.

Addthenetduedatetothelayout(    )orfrommenuSettings/Layout/ Current.You canseethattheinvoiceisdividedinthreeInstallmentswiththeirownduedates.Savethedocument.

3    Amount split

Ifyouhave fixedInstallments,youcanusetheInstallmentpaymentterms. However,ifyouneedto changetheamounts,thisisnotagoodsolution.Anychange inInstallmentpaymenttermsorinvoiceplansrequiresadditionalcustomizing.Thereisa waytouseflexibleamountsintheInstallments. EnableAmountSplitin the company codecustomizing.

Amountsplitenablesthesplitofaninvoiceorcreditmemo finalamount.AnewtabAmountsplit will appearonthescreensoftheEnjoytransactions(FB60, MIRO).ThismethoddoesnotworkfortheoldstyletransactionssuchasFB01.)

3.1    Testtheamountsplit

Createanewinvoice forvendor200(paymenttermsR001invendormaster).Opentab Amountsplit.

Youcansplittheamountaccordingtopaymentmethodortermsofpayment.Ifyouhaveenteredapayment method,thisentryhaspriorityoverthepaymentmethodinthetermsofpayment.

Ifnosplitismade–Installmentsaccordingtopaymentterm.

Makefollowingsplit:15000ispaidimmediately(paymentterm0001)and therestwithpayment termZR02.

Simulatethedocument and Post

Thanks,

With Best Regards,

Prabhakar Rao

Senior Consultant SAP MM

HITACHI CONSULTING

My client is facing huge increase on table TST03 due to frequent use of spool data, and this is starting to affect performance of the production system.

Although currently it is fine with deleting spool data after 10 days by house keeping job,

I believe once user increase (when other entities get into production later), start using the system and output spool,

it will result in worse performance for the system.

If anyone experienced a system using a huge number of spool data,

can you advise me what kind of action you took for this?

Here are some details.

System: SAP ERP 7.2

Quantity of Spool Data: Around 7,000 per day (80% of these are immediate output from smartforms)

The current size of table TST03: 90GB (DB total is 300GB)

Applies to:

All Enterprise Resource Planning implementation initiatives.

Summary

This paper signifies the need of undertaking a due diligence activity by any organization before considering an ERP implementation. This will allow them to leverage the outcome of this activity in making a more considerate and beneficial decision on an ERP implementation.

Author(s):    Sachin Rao

Company:    Barclays Bank Plc

Created on:  August 25, 20112011

Author Bio

Sachin a Mechanical Engineer by education has been in the field of SAP consulting for over 8 years, having core expertise in the modules of SRM, MM and WM. He has worked on several projects in SAP comprising implementation, roll-outs and support engagements. He has a good understanding of the business and its drivers especially in Automobile, Chemicals and Petroleum and Banking Domain. He has is also the author of the whitepaper ‘Need of Post Implementation Audits for ERP Implementation’.

Introduction

The success of any Enterprise Resource Planning (ERP) implementation in-terms of the operational and strategic value it brings to the organization, the benefits it realizes and the return on investment (ROI) is largely determined before the implementation starts.

This is an astonishing statement but true, the companies who have plans of implementing an ERP package should give a thought on the core benefits and reasons they want to get at the other end of implementation. This should begin well ahead of the implementation cycle, even before the ERP package and the implementation partner is identified.

Most of the failure in an ERP implementation has been more or less due the following reasons

§ Lack of specific goals and metrics

§ Users resistant to the new system

§ Users under-trained

§ Limited resources dedicated to implementation

Due Diligence

The dictionary meaning - ‘An investigation or audit of a potential investment’.

Generally, due diligence refers to the care a reasonable person should take before entering into an agreement or a transaction with another party.

Any company thinking in terms of a new ERP implementation has to be clear as to what it is expecting from having this task undertaken and the value for money spent on such implementation. Choosing to implement an ERP system can be a complex and time-consuming process; organizations should take a detailed look at their position, needs, and interests before going forward with planning an ERP implementation. In order to take into account the real need, benefits and core impact of implementation, one needs to undertake the activity of due diligence.

There are a number of indicators that signal when a company should consider implementing an ERP system:

§ Uncontrolled and rapid growth

§ Poor inventory control mechanism

§ Lack of process co-ordination

§ Failure to meet customer needs or expectations

§ Inconsistent delivery schedules

§ Inaccuracy in forecasting

§ Difficulties assessing financial health

§ Inaccurate or unknown Employee costs

But many of the times it is seen that a company gets into implementation for one of the following reasons which should not be the only determining factor to decide for an ERP implementation and hence the need for due diligence.

-              Our current system is not good enough to meet the current business needs and will require a lot of customization to keep it going

-              We are running out of support for the existing ERP package / the cost of keeping the existing package is more than implementing a new one

-              We have substantial budget this fiscal and want to spend it on a new implementation of ERP

As we know that each and every business is completely unique, and identifying which specific business conditions and processes need to be integrated or improved will ultimately determine if a system is necessary. The ERP package which may be built on any technology should fit the existing business process model, but not the other way around.

Due Diligence key Areas

The company that is undertaking this activity should at the end have answers for most if not all of the questions from the list. The in-depth insight that each answers gives will vary based on the interest and the type of business the company is interested in. Moreover the domain in which the business is operating will determine which questions need to be answered and to what extent. The questions which need to be dodged is the complete prerogative of the business under consideration.

Below is the list of probable questions which will have to be answered by any company to  get a clearer understanding on the real need, benefits and core impact of an ERP  implementation.

o    Why do we need this implementation?

This may seem to be an open ended question, forcing the company to think in various directions, which is a good start. This will give them an opportunity to list out all the points they would want to bring to the table and justify the need of going for the implementation.  A clear understanding on the priority of the points listed and which they wish to accomplish can be listed. This will give clarity on the factors that can be accomplished with the implementation. Some of the probing questions which can be listed are as below,

·        Enhance productivity, flexibility and customer responsiveness

·        Enable new business and growth strategies

·        Eliminate costs and inefficiencies

·        Extend business using the Internet

o    Which are the pain points that will be addressed with the implementation?

During the listing and prioritizing the factors which are compelling and directing for taking up the new initiative of implementation there will be some of the points which will qualify to be in the list by the virtue of being a pain point. These pain points need to be seen in the light of any business impact it makes or reduces the efficiency of a business process which can be eliminated or more efficiently managed with the development of a new process or deploying an ERP package.

o    What benefits / returns are expected from and after this implementation?

·        Improve alignment of Corporate strategies and business operations

·        Improve overall productivity

·        Reduce costs through increased flexibility

·        Improve financial management and corporate governance

·        Reduce risk across business

·        Gain higher ROI faster

·        Bring transparency in the business process

·        Support dynamically changing industry requirements

o    Who are the stake holders who will be affected from this change?

An organization which intends to implement ERP will need to identify and understand the stakeholders involved and how they contribute to the success or failure of the project. Broadly, the stakeholders can be categorized as below. The need to assign ownership with clear roles and responsibilities for each is a must

·        Executives and upper management

·        Departmental personnel such as middle management, procurement, and sales team

·        The IT department

·        Any other functions in the organization who are affected by the process changes

Due Diligence Activity Deliverables

Once the key areas are taken into account and all the outstanding questions and clarifications are complete, then all the activities carried out have to be consolidated as an approach document. Some of the points that needs to be highlighted are as below

·        Business Overview

·        Pain Areas

·        Business Process Improvements

·        Measurable Specifics of improvement

·        Cost Benefits

·        Long term benefits to the organization.

·        Road Map to accommodate future growth

·        Prerequisites for ERP package implementation

o    Process to identify the ERP package

o    Evaluation process for selection of Implementation Partner

Conclusion

The Due Diligence activities should be conducted by a service provider who should be a purely consulting firm and who should preferably not have any presence in the ERP implementation services. The only justification for this statement is that it may lead to a biased approach which will defeat the basic purpose of Due Diligence as one needs to have an open view during and at the end of this activity.

It would be better to seek the expertise of an independent consultant in the Supply Chain Management [SCM] area or a service provider having rich consulting experience pool. Consultants with specialized certifications in Supply Chain or with minimum of 10 years of experience in SCM would be best fit for conducting such due diligence. They will not only have a sound knowledge in the area but call also suggest core changes / inputs to the business process which will augment the overall efficiency and effectiveness of the business through ERP implementations.

Key feature of any ERP implementations

After the due diligence activity if the outcome justifies for going ahead with the ERP implementation the following should to be kept in mind

• ERP initiatives are always very challenging and demanding
• Business process re-engineering should happen before, not after, you implement your ERP software
• ERP is about your business, not only technology
• Selecting the right software is the first step in a successful ERP implementation
• SaaS (Software as a Service) ERP won’t eliminate all of your risks, either
• Your project will fail without adequate organizational change management
• Executive buy-in and support is critical to ERP success
• There is no “one size fits all” ERP strategy
• If your operations and ERP system are misaligned, it’s probably not the software’s fault
• Expectations are high, but most ERP implementations may not always properly define the “finish line.”
• Most organizations strive for “no customization,” initially,  but fail to do so eventually
• You don’t have to implement ERP all at once
• If you don’t measure it, you won’t achieve it

* The contents of this paper are my personal views and opinions, gained in the course of my experience.

Purpose

In this Document we will capture GL Planning/ Budgeting Process, Scenarios and requirement of an Organization.

This component is used to handle GL accounting transactions that you can Prepare Future forecast, Allocation in a Particular Department.

You can use the planning function in General Ledger accounting to enter and distribute plan data to create budgets, forecasts, and other reports.

You can quickly and easily enter large amounts of plan data. You have the following options for plan data entry:

1. You can enter amounts as plan totals that are (automatically or manually) distributed to the planning periods.
2. You can enter amounts as period amounts that are automatically totaled.
3. You can enter a combination of both totals and period amounts.

Features

Planning in General Ledger Accounting comprises the following functions:

1. You can perform planning locally. When setting up planning, you provide a framework for the individual planners and assign authorizations. You can also adapt the entry screen layout.
2. For balance sheet accounts, you can choose between planning balance sheet change values or balance sheet values.
3. For each fiscal year, you can post plan data to multiple versions.
4. You can compare actual and plan data
5. You can display totals records of your plan data.
6. You can display individual plan documents.
7. You can use allocations to allocate/distribute plan data

Planning

Planning is generally part of controlling. However, we can plan for the general ledger accounts in finance module of sap. This can be done to prepare the variance analysis within financial accounting.

Cost Center Planning

The planning application "cost center planning" enables the planning of the necessary budget of cost centers in the organizational structure of your company. You identify and value the relevant cost drivers, define manually entered prices (also called "political prices") for the internal activity allocation and enter primary and secondary costs.

Cost center planning involves entering plan figures for costs, activities, prices or statistical key figures for a particular cost center and a particular planning period. You can then determine the variances from these figures when you come to compare these plan values with the costs actually incurred. These variances (see: Variance Calculation) serve as a signal to make the necessary changes to your business processes.

Cost center planning forms part of the overall business planning process, and is a prerequisite for standard costing. The main characteristic of standard costing is that values and quantities are planned for specified time frames, independently of the actual values from previous periods.

Prerequisites

You have to activate the delivered planning application. For more information

Process Flow

The general process flow of cost center planning covers the following steps:

• Preparation: Planning cost drivers for externally related activities and the manually entered prices for internal activity allocation
• Planning of primary costs
• Planning of secondary costs
• Analysis of results in the SAP Business Information Warehouse
• Optional: Returning the plan data into the operational Cost Center Accounting of the R/3 System

Profit center Planning

Profit center planning forms is a part of corporate planning. For this reason, planning integration and reconciliation are particularly important.

Planning is a combination of top-down/bottom-up planning on several aggregation levels. The different roles of the persons involved in the planning process are reproduced with the help of various Planning Profiles, which enable a role-specific view of the existing planning objects.

Process Flow

Process Flow

The persons responsible for planning for their respective company call up their planning folder and plan revenue cost of sales, working capital, investments, and depreciation corresponding to the sequence suggested in the planning folder.

Master Data

The following profit center master data is maintained in the central master data maintenance system and distributed from there to the local systems:

1. Profit centers
2. Profit center groups
3. Account groups

Planning Program Update

Cost Center Planning

Define versions

Maintain fiscal Year -Select Version “0” and double Click on Settings for Each Fiscal Year .

Define Defined Planner Profiles

You use planner profiles to control the way planning is carried out. In a planner profile, you specify per planning area which planning layout is to be used with which default values. Per planning area, you can create as many planning layouts as you require. The profile item determines the order of the planning layouts within a planning area and can be used to assign the same planning layout to a planner profile in multiple areas, but with a different default setting each time.

Define Plan Versions

In this activity you can maintain plan versions for each ledger. For each fiscal year, you can post plan data to an unlimited number of versions.

Assign Fiscal Year to Version

In this activity, you can specify fiscal-year-dependent parameters for the plan versions of your ledgers. In so doing, you assign the desired fiscal year and posting period to your plan versions and activate them. You can also lock a plan version.

Define Plan Period

In this activity you can determine the posting periods allowed for entering planning data. You can create permitted posting periods in the form of variants, which can then be assigned to company codes.

Define Number Ranges for Plan Documents

In this IMG activity, you define the number range for your planning documents in General Ledger Accounting. You specify the following number range details for each company code:

• A number interval from which the document numbers are to be chosen
• The type of number assignment (internal or external)

Activate Line Items for Planning

In this activity you determine in the planning if summaries as well as plan line items are to be written.

And execute to update

User-Defined Planning Layouts

To be able to plan for cost elements, you first need to define the planning layout. In the planning layout, you specify the format of the planning screens.

Planning data

Display Plan Data F.01

Here Plan Version “0” used for display Plan data

1. Kindl of Audit to be Conducted (Technical or Functional)
2. Number of questions for the Audit
3. Structure of list of Questions (Question drill down level)
4. Valuation type of Questions
5. Question Priorites
6. What kind of Audit Controls to be implemented
7. Audit purpose
8. Audit Type
9. Kind of rating for the questions

Figure 12.0

• System Overview
• Security & Access Protection
• Workbench Organizer
• Transport System
• Accessing and Logging DB Tables
• Job Request Procedure
• Documentations
• System Logs
• Batch Input Interface
• Master Data Changes
• Reconciling Posting Data Closing
• Invoice Checking and Posting Run
• Business Process Auditing
• BASIS Audit

SAP Post Implemenation Audit - part 1

Author: Ranjit Simon John

Introduction to Audit in SAP

We all will be familiar with various types of Audit, Financial, Administrative, IS etc.

In the modern corporate world IS auditing is gaining more weight age due to the dependence of Business on IS. Auditing a traditional IT environment was more easy compared to auditing business process where highly complex ERP systems are implemented.

For a company with ERP system, it will be easy to certify the success of ERP implementation based on the KPIs defined. But few years down the line it will be highly difficult to check and analyze whether the system complies with the corporate governance rules.

The objectives of corporate governance are threefold:

. Transparency of information

. Internal control of processes

. Effectiveness of internal controls

The SAP process provides a consistent flow of data and information that enables the information to be controlled more quickly and accurately.

You can also configure additional controls for mySAP ERP Financials.

For example, you can arrange that every posting that exceeds a certain amount is marked and identified accordingly. You can monitor reported financial data and other key figures at any time.

Whenever a critical threshold is reached, you can investigate the cause of the problem.

SAP NetWeaver and SAP ERP offer built-in controls, including:

• Internal system controls
• Configurable controls
• Security controls
• Report control

Criteria  for preparing Audit Questionnaire

The audit questions should be framed based on a drill down approach on the business process.

Example: The impact of Financial Accounting on Sales & Distribution business process.

Control Objectives and Risks  in the Sales & Distribution Process mentioned above has to be developed;

Define every business process in each business units for identification of Control Objectives and Risks.

In the Sales & Distribution example mentioned the Control Attributes to be checked for Process Step PS2 is shown below;

The Risk associated with each business process control is identified.

Screen Shot of SAP MIC Implemented Tool.

To do basic auditing for the business process in SAP use TBI_REPORTS tool.

Execute ST13 -> Tool Name TBI_REPORTS

All the major business process checks can be checked and analyzed through the tool

Example: TBI report executed for Procurement -> Purchase Orders

For conducting audit through PLMD_AUDIT, check the blog;

SAP Post Implemenation Audit - Part 2

SNOTE is used for implementing the SAP notes in the system. SAP notes are small corrections delivered by SAP before releasing the support package. All the SAP notes will be included in the next support package release. The SAP notes which contain the correction instructions can be implemented in the system using the SNOTE and there can FAQ notes also which do not contain the correction instructions but are informative notes. The notes can be edited by SAP after releasing to the customers and when the SAP note is edited by SAP, new version of the SAP note will be released.

Few notes will be released to specific customers and they are called pilot release notes and they will be accessible and can be implemented by only those customers.

Note Implementation :

Before implementing the note in the system, please read the note completing and understand if it is valid for your system. Few notes contain the manual steps to be performed in the system before implementing the note. Please check the note and implement the pre-implementation steps manually in the system before implementing the note in the system and post implementation steps manually after the implementation of the note.

Please refer the steps specified below for implementing the note in the system using SNOTE.

Goto Transaction SNOTE : Download SAP note enter note number

After downloading the note, please goto SAP NOTE browser ctrl+F9 and enter the note number to check the implementation status of the note. The note can be implemented in the system if the "can be implemented" status is available. Please click on Implement SAP Note ctrl+F1 for implementing the note.

Different Implementation status available in SNOTE for particular SAP note downloaded in the system.

Can be Implemented - Note is valid for your system release and support package level and can be implemented in the system.

Cannot be implemented - Note is not valid for your system

Completely Implemented - The note is already implemented in the system

Incompletely Implemented - The note is partially implemented in the system and still some correction instructions of the note need to be implemented in the system.

Obsolete - The note is already delivered with the support package implemented in the system.

Obsolete Version Implemented - Either newer version of the note is released by the SNOTE or the system is upgraded to the higher version of the support package level.

The note log can be useful to check the implementation of the note and information about the version and date and time of the note implementation in the system

Following are the two important notes which need to be implemented in all the system depending on the basis releases. These notes contain the corrections for many known issues with the SNOTE.

875986    -  Note Assistant: Important notes for SAP_BASIS up to 702

1668882  -  Note Assistant: Important notes for SAP_BASIS 730,731,740.

Find the SAP SCRIPT form name from the spool output.

Click on spool

Form name

Search for IN01: gives the form name

Search for IN02 gives the windows

View form and windows with SE71

Article: Integration Approach of B2B partners for Large Business Transformation Projects

Summary: Article describes the key points to consider while finalizing the EDI partner (B2B Partners) integration strategy in a Global ERP transformation program .It emphasizes key challenges in an ERP implementation across multiple partner systems to maintain Business Process Continuity across the ERP system and the legacy Broker system in Horticulture industry

Author: Naveena Advani

Created on: 17th June, 2013

Author Bio: Naveen is Lead Consultant at Infosys and has over 9 years of professional work experience in SAP sales and Distribution. He has vast experience on various implementations and Rollouts for chemical, auto ancillary industry. His expertise is in processes in the Market to Sales, Order to Cash, Procure to Pay and Integrated Planning. Naveen is engineering graduate and post graduate in Management. He is alumni of Indian Institute of Technology – Roorkee. Naveen would like to thank his team members Sunny Suren, Vijay Vittal for their contribution towards this article

Business Scenario:

The company is the one of Major Breeder of horticulture Products like Young Plants and un-rooted cuttings. The end Customers are connected to breeder via Brokers/Agents (EDI partners).  The Brokers/Agents (EDI Partners) are connected to Breeder via B2B (Business to Business) for the Order fulfillment, Availability, Invoice related information exchange.  It is very important to have a smooth transition from a legacy based system to new platforms based on ECC.  Business operations should continue without requiring brokers to do any upgrade in technology or change in ways of working it becomes imperative to have the Smooth Business continuity strategy which should address the issues in the Operational Framework.

Operational Frame work,

Operational Framework

Operational Framework primarily focus on managing the below Key challenges

Technical Integration between Breeder and Brokers

Idoc based solution used to connect the Brokers for Order entry and Invoice Processing. Agro Chemical industry relies on availability information in planning the activities at nurseries or green houses. It is very critical to provide the Availability (ATP) information electronically. This can be achieved by using proxy based integration. Proxy based technology provides greater flexibility in defining the message structure. PI/XI middleware is great integration for SAP Proxy based communication.

Program Management:

EDI partner integration for a Transformation should be established as a distinct track as it would involve engaging additional stakeholders who would be continuing on legacy system based processes.  It is very important to identify the potential impacts by involving the key stake holders of EDI partners during the Blueprint workshops, Business Impact workshops. Transformations projects can run for several years it is imperative to involve the Brokers continuously during complete the course of implementation.

Performance of the interface.

Interfaces are the most critical piece in EDI partner Integration and below mentioned activities are very necessary in ensuring the stability and sustainability of the interface.

• Evaluate the Volume of Transaction load/Idoc on the interface. Including the Middleware load
• Adequate Work processes need to be allocated to manage the additional interface load. In case of Proxies, provide the dedicated queue.
• The interface should be designed to manage the peak load (month end/yearend) even though the frequency is less but business criticality is extremely high.
• Volume Or Stress testing of the interface should be done during test phases like IST and UAT.
• Continuous monitoring of the interface after go-live to ensure adequate response time that could affect ability of customer service to confirm orders

Data Integration

• Master Data maintenance

When a transformation Projects are implemented the data design undergoes a Harmonization, this harmonization of data integrating with EDI partner data requires complete and accurate data mapping of materials, customers and other data. Master data maintenance process need to be adapted to include data maintenance across company and EDI partners.

• Data Validation

The interfaces are heavily dependent on the integrity of data and would result in severe operational disruptions and productivity loss if master data is not maintained correctly. An automated Data validation tool to maintain and validate data is most desired approach. It is very important to ensure the correct data integrity during the Cutover from a Legacy system.

The data across the systems should be sync and updated. This can be achieved by Strong MDM (Master Data Management) governance, single source of Data reference and a focused data approach right from Data request to completion of Data Creation workflow

Subsystem/Vendor Integration

In the industry the vendors who supply the Products including the Product labels require most updated information. As lead times to Pack, ship products is usually a day, hence the process on Cutoff process, Substitution process places a very important role.  All the ship to address, packing label information, Export related information and Planning information must be communicated immediately incase of any changes to Subsystem/Vendors, responsible for Executing the Logistics.

Design Principles for new SAP System.

While engaging business users, Users of EDI partner, Partner IT support staff it has to be clearly communicated to them that the continuity solution in some cases a temporary/Interim solutions.  The interim solutions and requirements should be kept as simple as possible and only highly complex and high volume processes should be integrated across all EDI partners. Process improvements are strictly to be kept out of scope if the design destabilizes the solution. On a continuous improvement basis the legacy approaches would be de commissioned to keep the design simple on Data, System and Processes.

Aggateway provides industry standard templates for information exchange. Standard Chemical industry template can also be used in these integrations.

Reporting Consolidation

Top management reports and operational reports need to be consolidated. Reporting tool (ex, EDWH) are of powerful tools in consolidating the reporting needs. As Proxy based interfaces are used it require a good Operational report to be developed to monitor the interfaces. New reports would be needed to ensure smooth information flow.

Transformation Management

Transformation Impacts must be addressed with the EDI partners as well. In many projects the change Management is handled only within the Organization with users/employees of the company, but the Projects which integrate the EDI partners it is very important to address the Transformational issues throughout the course of implementation both from Inside and Outside perspective. It is very important to strategize the stabilization phase in conjunction with EDI partners.

Related Content

Monsanto Business Transformation Study

http://www.sdn.sap.com/irj/bpx/go/portal/prtroot/docs/library/uuid/f02f7c5f-e723-2b10-78a7-c274f5397ef2

The Critical Role of Organizational Change Teams in Transformation Projects

http://www.sdn.sap.com/irj/bpx/ocm?rid=/library/uuid/508b1863-897a-2c10-e688-eb2470fde6d3

Error-Free, Consistent Master Data Starts at the Source

http://www.sdn.sap.com/irj/bpx/mdm?rid=/library/uuid/50cdf4f7-ef28-2d10-1bba-d332f7082032

SAP Landscape Transformation Solution Brief

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/908a2c27-44b3-3010-e68f-bc984246894e?QuickLink=index&overridelayout=true&58475979772473

Aggateway of EDI and XML integration

http://www.aggateway.org/Home.aspx

For more information, visit the Enterprise Resource Planning homepage.

Glossary

Young Plant: Young plants is a starter plant, created from a cutting which creates a clone of Parent Plant.

Un Rooted Cutting: This is tip cutting of a plant and this is perishable in 3-4 days. Few genetics perish for weeks provided in a special temperature conditions.

Broker/Agent: Is a Agency based model customer who fulfills the Order fulfillment of Grower/Green houses. He is key in connecting the Breeders/Growers.

Therearetwopossibilitiestoachieveexclusion

Exclusionindicator KZNEP

1. Isset in theconditionrecordor in thecondition type (customizing)
2. Restrictions: itis not possiblethat a condition will excludeitselfandif a conditionisenteredmanuallyexclusion will not takeplace
3. Exclusionwith KZNEP isachievedbyusingrequirements (e.g. standardrequirement‚2‘). Review note 92090, 41490

Exclusiongroups

1.    Havetobesetup in customizing, IMG: Sales and Distribution -> Basic Functions -> Pricing -> Condition Exclusion

2.    Flexible: canbesetupforgroupsofconditionsor individual conditiontypesorrecords

3.    Rules areusedtojudgewhichconditionsareexcluded, e.g. bestprice

Restrictions: itis not possibletouse different rules in parallel, zerovaluesofconditionsare not usedforexclusion in standard (note 39641)

1 Warning

This documentation was written to link D35 CLNT 200 (ABAP stack) to DJ1 (JAVA STACK hosted in sapdj1.fr.rm.corp.local System number 01).

2 Creation of user ADS_AGENT in ABAP stack

type : service

Roles :

SAP_BC_FPADS_ICF

SAP_BC_FP_ICF

Transaction SU01 :

3 Creation of user ADSUSER in JAVA stack

In visual admin tool:

In visual Admin Tool:

Or in NWA:

The ADSUSER must be a technical user:

4 Creation of RFC destination in ABAP stack

Transaction SM59 :

N° service is 5<SN>00 where <SN> is the system number of JAVA STACK.

5 Activation of web services in ABAP STACK :

Transaction SICF :

Service name FP (sap/bc/fp) and FPADS (sap/bc/fpads).

6 Creation of http DESTINATION in JAVA STACK

Warning: the name MUST BE FP_ICF_DATA_<SID>!!! Where <SID> is the SID of the ABAP STACK.

Or in NWA:

7 Check FP_TEST_00 in ABAP stack

SE38 : ABAP FP_TEST_00 :

Click on print preview and if it is ok, you have :

Else you have an error message.

8 Check RFC connection from ABAP stack to JAVA stack

Se38 ABAP FP_PDF_TEST_00:

If it is ok, you have:

Else you have an error message and it means that you have some trouble in RFC connection in ABAP stack (check point 3).

9 Check the destination service in ABAP stack

Se38 : ABAP FP_CHECK_DESTINATION_SERVICE (available as of NW2004s SPS

08)

First time, you launch it without the selecting option “With destination Service”:

It calls the java stack to generate the form but didn’t send back the form, it just gives the size of the form:

Second time, you launch it with the selecting option “With destination Service”:

If it is ok, you have quite the same message (the size can be different)

Else you have an error message and you have to check task 4 and 5.

10 Annexes

Configuration guide on sap help

OSS note 944221 Trouble shooting

1. Context

1.1. Scenario

During ECC6 upgrade project, a sub-project to migrate platform,fromSolaris toAIX,should be performed.

Databaseis not changedand will remain Oracle database.

Unicode migration is not yet formally decided but will have little impact on this procedure.

To be able to minimize downtime, this migration is performed with Distribution Monitor tool.

By this way, resources from multiple servers are usable.

1.2. Big Pictures

1.3. Remarks

All optimization and configuration values in this document are closely dependant of used infrastructures.

For Next export runs, these optimization and optimization should be adjusted to match the new infrastructure configuration.

• Source database server         SAPTEP08
• Target database server         FRRMTEUSAPB01

2. Prerequisites

2.1. Operation System level

Several prerequisites should be check on each used server:

• Java virtual machine 1.6 should be installed in /usr/jre1.6.0_43
• Oracle client 11 should be installed in /oracle/client/11x_64
• OS groups sapsys and dba  should have same GID on all source/target AS and CI/DB servers (normally 200 and 201)
• OS users <sid_src>adm and <sid_tgt>adm
  • should have same UID on all source/target AS and CI/DB servers
  • should belong to groups sapsys and dba
  • should use ksh shell
  • should have home directory in nfs share /export/SAP/users/<sid>adm
• Theses home directories should contains a exe sub-directory for sap kernel and a tnsping program
  • Non Unicode for source system
  • Unicode for target system (in case of Unicode migration)

• .profile

• .profile

• Home directories should contain a copy of CIDB network directory (/oracle/SID/112_64/network)

• File /export/SAP/oracle/tnsnames.ora should contain tnsname entries to be able to connect both source and target database

2.2. Oracle

2.2.1. VBOX Indexes

VBOX indexes have to be rebuilded and compressed ; This operation is being implemented on P3B.

Status of this operation has to be check for each P3B database copy usage and for P3B database itself with production system will be migrated. 

2.2.2. PL/SQL Splitter

Oracle specific PL/SQL Splitter is used for transparent tables splitting. This package needs to be installed first.

1. Create necessary privileges for the schema user which is the owner of the tables to be split such as sapr3 by connecting to the database as SYSDBA:

2. Select the Output Directory and create it in Oracle:
   1. Save attached file presplitter.txt from OSS note 1043380 to PRESPLITTER.sql
   2. Launch SQL script

3. Install PL/SQL Package
   1. Save attached file splitter_hint.txt from OSS note 1043380 to SPLITTER.sql
   2. Launch SQL script

2.3. DISTMON tool

DISTMON tool and its User’s Guide are available as attachment in OSS note n°855772

Current DISTMON version available, and used, is 1.9.2

File DISTMON.SAR should be uncared in directory /export/DISTMON

2.1. SAP tools

SAP tools is available under directories /export/SAP/R3xx_nonunicode

Versions used for each run are:

• R3load             720_EXT_REL Patch Level 413
• R3ldctl             720_EXT_REL Patch Level 413
• R3szchk           720_EXT_REL Patch Level 413
• R3ta                 720_EXT_REL Patch Level 413

3. DISTMON Configuration

Main configuration directory, used during POC, is /export/DISTMON of target CIDB server; ie frrmteusapb01.

Main configuration file is distribution_monitor_cmd.properties

It use and refer to several others files, on same directory, which are described first.

3.1. File package_splitter_cmd.properties

This file allows specifying how packages and tables are splitted.

• Parameter top is commented; list of tables is managed by tableFile parameter
• Parameter tableLimit is commented; list of tables is managed by tableFile parameter
• Parameter packageLimit is set to 2000
• Parameter tableFile specify tables be excluded from packages

3.2. File package_splitter_tables.txt

This file is filled with table names that should be put in separate packages.

It contains 100 biggest tables identified in B6B.

These tables will be processed in next parts of this document depending on their categories

• Transparent tables
• Cluster tables
• VBOX table (partitionned table)

3.3. File unsorted_export.txt

This file is filled with table names that should be exported in unsorted mode.

This file is considerer with parameter unsortedExport=file 

Rem : For first POC the file was filled with the100 biggest tables

Starting with second POC, all tables are exported by unsorted mode with parameter unsortedExport=all 

In case of Unicode migration, cluster tables should be exported in sorted mode

R3load is able to identify automatically cluster tables and to export them in sorted mode without any other action.

By consequence, the file unsorted_export.txt is no more useful.

3.4. File parallel_index.txt / parallelIndexImport.txt

Rem: This file name is dependent of DISTMON version

This file is filled with table that all their indexes have to be created in parallel mode.

This file is considerer with parameter parallel_index_import=file 

It contains same entries that package_splitter_tables.txt file.

3.5. TABLES SPLITTING

3.5.1. File table_splitter_tables.txt

This file is filled with table that should be splitted

R3ta splits are based on file R3_hints.txt which should be in same directory as distmon tool.

It contains same entries that package_splitter_tables.txt file except for VBOX table which is performed manually.

R3ta splitting is perform by DISTMON tool itself (if parameter skipR3ta is not set).

Template of R3ta sentence :

• /export/SAP/R3xx_nonunicode/SOL/R3ta -f /export/SAP/commDir/PkgSplit/VAKPA.STR -table VAKPA%2 -o /export/SAP/commDir/R3ta/VAKPA.WHR -check_utf8 -l tableSplitter.VAKPA.log &

3.5.2. Table VBOX

Splits for VBOX table are generated manually.

Split rule is base on partition to have 1 WHR clause by partition:

• 25 partitions of 25 Go (280 Go of data)
• 1 partition of 500 Go (250 Go of data – 100Go of data on P3B)

Partitions timeframes are collected from file  APPL1.SQL (generated by report SMIGR_CREATE_DDL) and then processed  by Excel macro.

• File VBOX .WHR  is filled manually with formatted sentences:

• The file need to be splitted so that each WHR file contains only one WHR condition
  • From server     FRRMTEUSAPB01
  • In directory       /export/SAP/commDir/R3ta_VBOX
  • File VBOX.WHR is rename VBOX.WHR.old
  • Generated files are named VBOX-nnn.WHR

3.5.3. Tables cluster & pool

Splits for the 6 biggest tables cluster are generated online with R3ta tool

Splitting  can be performed before SAP upgrade.

3.5.3.1. R3ta

R3ta splits are based on file R3_hints.txt which should be in same working. Check that it contain right key field that should be used for splitting.

• Table cluster R3ta splitting is performed
  • From server       FRRMTEUSAPB01
  • In directory

• Files need to be splitted so that each WHR file contains only one WHR condition
  • From server     FRRMTEUSAPB01
  • In directory
  • Files <table>.WHR are rename <table>.WHR.old
  • Generated files are named <table>-nnn.WHR

3.5.4. Tables transparent

All others biggest tables are splitted by PL/SQL Splitter (Cf. OSS note n° 1043380 - Efficient Table Splitting for Oracle Databases)

• Tables transparent splitting is performed
  • From server
  • In directory
  • Split command sqlplus sapr3/<pwd> @plsql_splitter_TRANSP.sql

• Target directory for PL/SQL splitter is /tmp/ms_split (should be change during next package installation)
• <table>.WHR files contain several where clauses but should not be splitted again like VBOX / cluster tables.

• Splitting for all biggest transparent tables : 13 mns

3.5.5. Consolidation

All tables splitting should be consolidated into the single directory /export/SAP/commDir/R3ta

3.6. File OrderBy.txt

This fileis used to specifythe tables thatneed to be addressed first. Largest tableslargerand/or those ones havinglongest processing timesarerelevant.

For splitted tables, you must specify all of their packages(note:the programR3tatends to addan additional packageto the numberrequested).

Presence of thefile in DISTMONdirectory is enough totake into account its.

3.7. File distribution.txt

This file is used to distribute specifics tables on dedicated servers. Tables having longest processing times (largest, cluster, …) are relevant.

For splitted tables, you must specify only table name, not all of their packages.

Presence of thefile in DISTMONdirectory is enough totake into account its.

3.8. Report SMIGR_CREATE_DDL

This report should be executed before DISTMON preparation. It generates DDL statements for “special” tables like partionned tables (VBOX).

• Target directory is /export/SAP/commDir/MigrDdl
• If Unicode migration is confirmed,  check the box  

• Due to tablespace architecture adjustment, a special check has to be validated : correct TABART should be assigned to DDL statements (highlight in yellow)

3.9. File distribution_monitor_cmd.properties

This file is the central configuration file used by DISTMON.

• hostNames                  Pool of servers used by DISTMON
• hostNames.dataDirs     Data dump directory for each server
• commDir                      Central DISTMON directory
• r3ldctlExe                    Path to R3ldctl  
• r3szchkExe                  Path to R3szchk   
• r3szchkArgs                 Refer to § 6.2.5 od DISTMON User’s Guide
• r3taExe                        Path to R3ta
• parallelR3ta                  Number of R3ta process in paralell mode
• dataCodepage             Should be specified if export is in non-Unicode mode
• dbCodepage                Should be specified if export is in non-Unicode mode
• r3load.import.loadArgs Should be specified to use Direct Path
• migrationKey                Should be generated on SAP Marketplace for each migration

• timeDir

                                               should be the set when all others optimization tips have been activated

Remark:

• Parameters <host>.exportJobNum  and <host>.importJobNum  are used to distribute packages on pool of servers
• They should be adjusted regarding servers caracteristics : CPU (number/frequency) and memory

4. DISTMON preparation

4.1. Prerequisite

A best practice to avoid any former log/status files is to clean them before launching DISTMON preparation phase

4.2. Files DDLORA.TPL and DDL_LRG.TPL

After each R3ldctl execution, these files should be checked and adjusted by modifying  « schema id».

Substitution is not done correctly and should be executed manually before launching DISTMON preparation

• String @SCHEMAID@ should be replace by target schema ID: SR3 in our case

• For table and index storage parameters

4.3. File APPL1.SQL

Like this file is move in another directory during DISTMON preparation execution, it could be useful to check (again) the existing of file APPL1.SQL before launching again DISTMON preparation.

In same time, a additonnal check regarding right data class could be done ;-)   (cf. § 3.8« Report SMIGR_CREATE_DDL »)

• Target directory is /export/SAP/commDir/MigrDdl

• Vérifier le contenu (DATA CLASSE à

4.4.    Tables compressions : exclusion

Just for information, list of table that should not be compressed in target database are specified in files DDLORA_TPL and DDLORA_LRG.TPL in part « negcpr».

4.5.    Préparation

Command to launch DISTMON preparation execution

• Source directory is /export/DISTMON

4.6.    Unix permissions

1. Due to ours  N@!@N#   UID/GID issues, change permissions on all contents of /export/SAP directory

4.7.    Additionnal Checks

Controlthe distribution ofpackagesondifferent serversis usefulto move towardsan endoftreatmentpackagesat the same timeoneach of these servers.

• Source directory is /export/DISTMON

4.8. Distribution of file distribution_monitor_*

Program and last version of configuration file distribution_monitor_cmd.properties should be copied on all pool of servers

• Source directory is /export/SAP

5. DISTMON export / import

5.1. Oracle - Indexes

Some Oracle adjustments are required, mainly on larges cluster and pool tables to optimize data export.

Be careful, all indexes creation should not be perform during real production activity: They might have impact on end users activity.

I advise to create them after R3ldctl program has run. By this way these additional indexes will not be created on target database.

5.1. Prerequisite

A best practice to avoid any former dump/log/status files is to clean them before launching DISTMON export phase.

A good solution is to used dedicated script:

• Source directory is /export/SAP/scripts/nettoyage.ksh