source: Best Practice: Data Consistency Between SAP R/3 and SAP APO 3.0/3.1
Report CIF_DELTAREPORT3 can be used to check the external consistency of the majority of transaction data used in APO (such as production orders, planned orders, sales orders, stocks, and so on).
It makes the following data checks:
• It only checks transaction data.
• It only checks that the data exists. It then compares important quantities and times. The level of detail varies between the different transaction data compared.
• The quantity is also checked for stocks.
Goal and Prerequisites
Report /SAPAPO/CIF_DELTAREPORT3 ensures that the data transferred using the Core Interface (CIF) is or remains consistent between SAP R/3 and SAP APO. If inconsistencies between the systems are detected, you can also use this tool to repair them. This report corrects problems quickly and easily. In the majority of cases, CIF can be used to resend the missing data. However, you need to completely understand the CIF model and integration between SAP APO and SAP R/3. This includes knowledge about master and transaction data in the relevant SAP R/3 and SAP APO systems. If inconsistencies occur between the systems, it is always advisable to analyze the causes of the error, to be able to rule out software errors, for instance. Knowledge of ABAP is also useful to be able to perform on-site error analyses.
Depending on the system settings in SAP APO, changes to transaction data are only listed and are not transferred synchronously to SAP R/3. This results in these changes being identified as inconsistencies, although they are not. Therefore, it is necessary to set a change pointer when the data is transferred from SAP APO to SAP R/3 before running /SAPAPO/CIF_DELTAREPORT3. You use transaction /SAPAPO/C5 to do this.
Technical System Prerequisites
• SAP APO Support Package 19
• PI.2001.1 with the associated note prerequisites. See SAP Note 458164.
Use
To start the report in SAP APO 3.0, you use transaction SE38, program name /SAPAPO/CIF_DELTAREPORT3. As of APO 3.1, you can use transaction /SAPAPO/CCR.
Online processing: The only field of the entry screen in which you have to make an entry is the Partner System field. You can choose any individual object types that you want to be checked.
Important Notes
• Making fewer restrictions when selecting data and choosing a large variety of object types will cause the runtime of the transaction to be longer. If the quantity of data you have chosen is too large, there is the possibility that a short dump (‘TIME_OUT’) will occur. In this instance, you have to run the report in background processing or reduce the quantity of data.
• You should start the compare/reconcile report only if there is a small data load in the Core Interface. For instance, you could do this during the night, when no planning runs that would generate CIF-relevant documents are taking place. Otherwise, the report could display ‘false’
inconsistencies due to runtime problems. You can use SAP Note 496779 or SAP APO 3.0A to prevent this from happening.
• You should not start the compare/reconcile report during initial data transfer or a delta compare/reconcile.
Background Processing
Before you can start a background processing run, you have to create suitable variants for program /SAPAPO/CIF_DELTAREPORT3. Note the following when doing this:
• Compare/reconcile reports can be run in parallel. Create multiple variants for report /SAPAPO/CIF_DELTAREPORT3 (see above). When defining the variants, note that the selected object types cannot overlap. To ensure this, you can assign a dedicated variant to each object type (sales order, production order, purchase requisition, and so on).
• You should start the compare/reconcile report only if there is a small data load in the Core Interface. For instance, you could do this during the night, when no planning runs that would generate CIF-relevant documents are taking place. Otherwise, the report could display ‘false’ inconsistencies due to runtime problems. See SAP Note 496779 from SAP APO 3.0A Support Package 21.
• You should not start the compare/reconcile report during initial data transfer or a delta compare/reconcile.
Verification/Subsequent Processing
Online Processing
Once the compare/reconcile is complete, an output screen appears, displaying an overview of the results. This is done separately according to documents (orders) and stocks. A line is displayed for every object type selected on the screen for testing, showing the following information:
• Total: The number of SAP R/3 objects that have been selected for comparison
• Error: The total number of errors found
• All other columns: Distribution of errors to individual error areas
A tab page displaying detailed lists of the individual faulty orders or stocks is displayed for every object type that is shown to have errors in the results overview.
In the case of orders, there is an additional tab page on every tab page for an incorrect object type listing the orders that were found in SAP R/3 but that are missing from SAP APO.
If required, execute a reconcile.
• Choose a tab page showing a detailed list of incorrect objects and select the lines you wish to reconcile (to make multiple selections, hold down the CTRL button at the same time).
• Choose the Send to APO button to start the reconcile.
• In the dialog box that appears, confirm that you have initiated the Send.
The current state of the data is read from the database. Then, the data is transferred asynchronously using the standard CIF interface of the object type.
A selection icon appears beside the selected lines in the Sent/Action column indicating that the Send has been initiated for the relevant objects. An object that has a selection icon cannot be resent, even if it is reselected for this purpose.
Background Processing
The spool list is the result of the compare function in background mode. To view the spool list for a job that ended without errors, choose your job in the job overview (transaction SM37), choose Spool, choose your spool list from the spool list overview, and choose Display (F6). As of APO Support Package 7, you also have access to all detailed lists of the faulty objects. To view these, see the spool list beside the summary results overview of the comparison for documents and stocks.
Compare/Reconcile Report Performance
In general, the consistency compare/reconcile of /SAPAPO/CIF_DELTAREPORT3 has four stages.
Stage 1: It evaluates the integration models to be checked. The runtime of this stage is linearly related to the size of the integration model.
Stage 2: It selects the data. We cannot provide a blanket statement about performance for this stage. The runtime is determined by the relationship between filter objects and the data objects to be checked. We cannot provide a general recommendation. For more detailed information, see SAP Note 439438.
Stage 3: It checks that the data exists in APO. After the integration models are evaluated and the corresponding data is read from SAP R/3, SAP APO is checked to see that the corresponding data exists here. The runtime is linearly related to the size of the integration model.
Stage 4: It checks whether the APO data does NOT exist in the SAP R/3 system. If you have a large integration model, this step will have a shorter runtime.
Important notes:
• For more information, see SAP Notes 439438 and 451446.
• To optimize the runtime, change the block size of the filter object. We cannot provide a general recommendation for the block size of the filter object since the ideal setting is always based on the relationship between the filter objects and the data objects to be checked.
Tuesday, May 19, 2009
Sunday, May 10, 2009
Safety Stock Planning
The standard methods of safety stock planning are used to build stock on hand
according to the safety stock values that you define in the location product master,
depending on previous experience. In contrast to model-based safety stock planning, forecast errors are not considered when you use the standard methods. You can maintain the safety
stock value as a static or time-dependent value. You can change the safety stock
values manually in interactive Supply Network Planning.
The advanced methods of safety stock planning are used to calculate the
time-dependent safety stock for finished products and components. In this type
of planning, the system takes into account the demand forecasts and forecast
errors within your supply chain.
Supply Network Planning (SNP) allows you to consider the actual supply
when planning safety stock. This means that, not only can the system take
forecast demand and actual demand into account, but it can also consider the
deviations between the planned Replenishment Lead Time (RLT) and the actual
Replenishment Lead Time.
The calculated safety stock is displayed in an SNP key figure in interactive
planning and can be changed manually or copied into another planning version, if
required. The calculated safety stock can also be used in both Production Planning
and Detailed Scheduling (PP/DS) and in Capable-to-Match.
If you keep safety stock both in the plant and in Distribution Centers (DCs), the
system uses the model-based calculation to take this into account. The system
always calculates the replenishment lead time starting from the last safety stock
leading location.
Calculating Safety Stock
Safety Stock Calculation Methods
• Available safety stock methods:
– SB Safety stock from location product master
– SZ Safety days' supply from location product master
– SM Maximum of SStk and SZ from location product master
– MZ Safety days' supply (maintained on a time-dependent basis)
– MB Safety stock (maintained on a time-dependent basis)
– MM Maximum of MB and MZ (maintained on a time-dependent basis)
– ATα service level and reorder cycle method
– ASα service level and reorder point method
– BTβ service level and reorder cycle method
– BSβ service level and reorder point method
If you want to use the standard methods (methods 1-3), go to the lot size tab page
of the location product master and enter the relevant data in the following fields:
• Safety stock
• SB method (safety stock method)
• Safety days' supply
To manually create safety stock on a time-dependent basis (methods 4-6), use a
macro to enter the safety stock or safety days' supply - on a time-dependent basis -
in the interactive planning table of SNP, and save the SB method on the lot size tab
page of the location product master. Mass maintenance of time series was put in
place for Release SCM 4.1 (transaction /SAPAPO/TSKEYFMAIN). Time-dependent safety stocks are stored in time series of the key figure
9ASAFETY. If you also want to plan these stocks in PP/DS, you must
assign this key figure in PP/DS Customizing.
The advanced methods of safety stock planning take the accuracy of Demand
Planning forecasts into account. To calculate the safety stock, you need to enter the demand planning key figures of your planning area that contain both past forecasts and realized demand.
The forecast errors are determined from the past data. Safety stock planning uses
relative forecast errors and the relationship from forecast errors and forecasts,
which can differ from one time bucket to the next. For the realized demand, select a key figure that contains the actual demand realized. These values can be updated from sales orders or invoiced sales quantities, etc., from the OLTP systems. For the planned demand, select a key figure that contains the forecast figures generated in the past.
As an alternative, errors for forecasts and replenishment lead times can be predefined in the location product master record (on the Lot Size tab page).
according to the safety stock values that you define in the location product master,
depending on previous experience. In contrast to model-based safety stock planning, forecast errors are not considered when you use the standard methods. You can maintain the safety
stock value as a static or time-dependent value. You can change the safety stock
values manually in interactive Supply Network Planning.
The advanced methods of safety stock planning are used to calculate the
time-dependent safety stock for finished products and components. In this type
of planning, the system takes into account the demand forecasts and forecast
errors within your supply chain.
Supply Network Planning (SNP) allows you to consider the actual supply
when planning safety stock. This means that, not only can the system take
forecast demand and actual demand into account, but it can also consider the
deviations between the planned Replenishment Lead Time (RLT) and the actual
Replenishment Lead Time.
The calculated safety stock is displayed in an SNP key figure in interactive
planning and can be changed manually or copied into another planning version, if
required. The calculated safety stock can also be used in both Production Planning
and Detailed Scheduling (PP/DS) and in Capable-to-Match.
If you keep safety stock both in the plant and in Distribution Centers (DCs), the
system uses the model-based calculation to take this into account. The system
always calculates the replenishment lead time starting from the last safety stock
leading location.
Calculating Safety Stock
Safety Stock Calculation Methods
• Available safety stock methods:
– SB Safety stock from location product master
– SZ Safety days' supply from location product master
– SM Maximum of SStk and SZ from location product master
– MZ Safety days' supply (maintained on a time-dependent basis)
– MB Safety stock (maintained on a time-dependent basis)
– MM Maximum of MB and MZ (maintained on a time-dependent basis)
– ATα service level and reorder cycle method
– ASα service level and reorder point method
– BTβ service level and reorder cycle method
– BSβ service level and reorder point method
If you want to use the standard methods (methods 1-3), go to the lot size tab page
of the location product master and enter the relevant data in the following fields:
• Safety stock
• SB method (safety stock method)
• Safety days' supply
To manually create safety stock on a time-dependent basis (methods 4-6), use a
macro to enter the safety stock or safety days' supply - on a time-dependent basis -
in the interactive planning table of SNP, and save the SB method on the lot size tab
page of the location product master. Mass maintenance of time series was put in
place for Release SCM 4.1 (transaction /SAPAPO/TSKEYFMAIN). Time-dependent safety stocks are stored in time series of the key figure
9ASAFETY. If you also want to plan these stocks in PP/DS, you must
assign this key figure in PP/DS Customizing.
The advanced methods of safety stock planning take the accuracy of Demand
Planning forecasts into account. To calculate the safety stock, you need to enter the demand planning key figures of your planning area that contain both past forecasts and realized demand.
The forecast errors are determined from the past data. Safety stock planning uses
relative forecast errors and the relationship from forecast errors and forecasts,
which can differ from one time bucket to the next. For the realized demand, select a key figure that contains the actual demand realized. These values can be updated from sales orders or invoiced sales quantities, etc., from the OLTP systems. For the planned demand, select a key figure that contains the forecast figures generated in the past.
As an alternative, errors for forecasts and replenishment lead times can be predefined in the location product master record (on the Lot Size tab page).
Friday, May 8, 2009
Note 428147 - Extraction of data from an SNP planning area
Note 428147 - Extraction of data from an SNP planning area
Summary
Symptom
When extracting data from an SNP planning area, you must take account of some special features. These are explained in this note.
- 1. Data can be extracted only for existing SNP aggregates.
Existing SNP aggregates are:
- 9AAC (9AACTNAME - APO Activity)
- 9AACPR (9AACTNAME, 9APPMNAME - APO PPM/PDS Name)
- 9ALA (9ATRNAME - APO Transportn Lane)
- 9ALO (9ALOCNO - APO Location)
- 9ALORE (9ALOCNO, 9ARNAME - APO Resource)
- 9AMA (9AMATNR)
- 9AMALA (9AMATNR, 9ATRNAME)
- 9AMALARE (9AMATNR, 9ARNAME, 9ATRNAME)
- 9AMALO (9ALOCNO, 9AMATNR)
- 9AMALORE (9ALOCNO, 9AMATNR, 9ARNAME)
- 9AMAPR (9AMATNR, 9APPMNAME)
- 9AMARE (9AMATNR, 9ARNAME)
- 9APR (9APPMNAME)
- 9ARE (9ARNAME)
- 9AREPR (9APPMNAME, 9ARNAME)
Only the characteristic/characteristic combinations contained in these aggregates may be used in the InfoSource, transfer structure and transfer rules.The simplest way of doing this is by always generating Export-DataSources for SNP planning areas to one of the aggregates and not to the Basis planning object structure '9ASNPBAS'.A typical result of using the Basis planning object structure '9ASNPBAS' without correcting the transfer structure is that, while data is transferred to a RemoteCube, it cannot be extracted in a BasisCube.
As of APO 3.0 Support Package 17 (or note 443613), only export DataSources for aggregates can be generated in SNP planning areas, they are no longer generated for the Basis planning object structure.
Furthermore, note that the navigation attributes 9ATTYPE, 9ALOCTO, and 9ALOCFROM up to APO 3.0 Support Package 17 (or note 441653) must be deleted from the transfer structure for the SNP aggregates '9AMALA' (9AMATNR/9ATRNAME) and '9AMALARE' (9AMATNR/9ATRNAME/9ARNAME). These navigation attributes can be used from the specified correction.
Due to technical restrictions the characteristics '9ATRNAME' and '9ATTYPE' can only be restricted with single values in the selection for the data extraction.The use of intervals and formatting characters (+/*) is not allowed for these characteristics.
- 2. For an SNP aggregate, only the key figures assigned to it can be extracted. You can see which key figures are assigned to an aggregate in transaction /SAPAPO/MSDP_ADMIN on the Key figure assignment tab of the relevant planning area. As of APO 3.0 Support Package 17 (or note 439366), only the key figures assigned to this aggregate are taken into account when an export DataSource is being generated for aggregates.
- 3. During the definition of queries, the following restrictions apply:
In the case of queries for the aggregate '9AMALA', certain key figures can only ever be extracted with another key figure.The key figure combinations that can only be extracted together are:
- (9AFSHIP, 9ADMDDF, 9ADMDDFVMI)
- (9AFSHIPLP, 9ADMDDFLP)
- (9AFSHIPVMI, 9ADMDDFVMI)
- (9APSHIP, 9ADMDDI, 9ADMDDIVMI)
- (9APSHIPLP, 9ADMDDILP)
- (9APSHIPVMI, 9ADMDDIVMI)
- (9ATSHIP, 9ADMDDT, 9ADMDDTVMI)
- (9ATSHIPVMI, 9ADMDDTVMI)
Header Data
| Release Status: | Released for Customer |
| Released on: | 02.01.2003 09:56:17 |
| Master Language: | German |
| Priority: | Correction with medium priority |
| Category: | Consulting |
| Primary Component: | SCM-APO-FCS-EXT Extraction |
| Secondary Components: | SCM-APO-SNP Supply Network Planning (SNP) |
Affected Releases
|
Related Notes
SNP Planning Area Aggregates
Aggregates is nothing but storing the data at that particular aggregate level,say for example 9ALORE is aggregate at your location and resource level.
If some of keyfigures assigned to this aggregate then you can store the data at this combination.(example 1) your capacity value of resource at plant level).
If you add new keyfigure in planning area that keyfiure by default assigned to 9ABAS level ,then you need to assign this keyfigure to your particular aggregate level by using table /sapapo/tspaplob.
IF you add any time series Key figure, in SNP planning Area then it will automatically assigned to all the Aggregates.
---------
Purpose of Aggregates:
Data can be saved in aggregates as well as on the lowest level of detail. An aggregate contains a subset of the characteristics in the master planning object structure.
the purpose of aggregates in APO is : to speed up data access and therefore increase performance.
Below aggregate are provided by sap with standard SNP functionality as soon as you make your MPOS SNP possible it add below aggregate in your PA.
9ALA
9ALORE
9AMALA
9AMALARE
9AMALO
9AMALORE
9AMAPR
9AMARE
9ARE
9AREPR
you can also create your own aggregate in a master planning object structure of APO by clicking with the right mouse button on the master planning object structure in S&DP Administration and choosing Create aggregate.
Source:https://www.sdn.sap.com/irj/scn/message?messageID=6027404
Another purpose for SNP aggregates is for data backup purpose:
If some of keyfigures assigned to this aggregate then you can store the data at this combination.(example 1) your capacity value of resource at plant level).
If you add new keyfigure in planning area that keyfiure by default assigned to 9ABAS level ,then you need to assign this keyfigure to your particular aggregate level by using table /sapapo/tspaplob.
IF you add any time series Key figure, in SNP planning Area then it will automatically assigned to all the Aggregates.
---------
Purpose of Aggregates:
Data can be saved in aggregates as well as on the lowest level of detail. An aggregate contains a subset of the characteristics in the master planning object structure.
the purpose of aggregates in APO is : to speed up data access and therefore increase performance.
Below aggregate are provided by sap with standard SNP functionality as soon as you make your MPOS SNP possible it add below aggregate in your PA.
9ALA
9ALORE
9AMALA
9AMALARE
9AMALO
9AMALORE
9AMAPR
9AMARE
9ARE
9AREPR
you can also create your own aggregate in a master planning object structure of APO by clicking with the right mouse button on the master planning object structure in S&DP Administration and choosing Create aggregate.
Source:https://www.sdn.sap.com/irj/scn/message?messageID=6027404
Another purpose for SNP aggregates is for data backup purpose:
- Data can be extracted only for existing SNP aggregates. Existing SNP aggregates are:
- 9AAC (9AACTNAME - APO Activity)
- 9AACPR (9AACTNAME, 9APPMNAME - APO PPM/PDS Name)
- 9ALA (9ATRNAME - APO Transportn Lane)
- 9ALO (9ALOCNO - APO Location)
- 9ALORE (9ALOCNO, 9ARNAME - APO Resource)
- 9AMA (9AMATNR)
- 9AMALA (9AMATNR, 9ATRNAME)
- 9AMALARE (9AMATNR, 9ARNAME, 9ATRNAME)
- 9AMALO (9ALOCNO, 9AMATNR)
- 9AMALORE (9ALOCNO, 9AMATNR, 9ARNAME)
- 9AMAPR (9AMATNR, 9APPMNAME)
- 9AMARE (9AMATNR, 9ARNAME)
- 9APR (9APPMNAME)
- 9ARE (9ARNAME)
- 9AREPR (9APPMNAME, 9ARNAME)
Subscribe to:
Posts (Atom)