B05_BB_ConfigGuide_EN_DE

SAP SCM 4.0

March 2004

English

Building BlockReplication

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Building Block Replication: Configuration Guide

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

© SAP AG Page 2 of 46


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Content1 Prerequisites 5

1.1 SAP Notes Building Block Replication SCM 5

1.2 Uploading the Configuration Role 5

2 Preliminary Steps 6

2.1 SAP R/3: Preliminary Steps 6

2.2 SAP APO: Preliminary Steps 6

3 Data Replication 6

3.1 Creating Integration Models (SAP R/3) 6

3.2 Saving Results and Creating Variants (SAP R/3) 6

3.3 Activating Integration Models (SAP R/3) 6

3.4 Changing Integration Models (SAP R/3) 6

3.5 Maintaining Distribution Definition (SAP APO) 6

4 Additional Customizing for Replication 6

4.1 Deactivating the Customizing Import from SAP R/3 (SAP APO) 6

5 Master Data Delta Transfer 6

5.1 Activating ALE Change Pointers 6

5.2 Delta Transfer of Material Masters, Customers and Suppliers 6

5.3 Delta Transfer of PPMs 6

5.4 Delta Transfer of Runtime Objects 6

5.5 Delta Transfer of Production Orders 6

6 Monitoring 6

6.1 Setting up the qRFC Alert (Optional) 6

6.2 Monitoring in R/3 6

6.3 Monitoring in APO 6

6.4 Compare / Reconcile Function 6

7 Troubleshooting 6



1 PrerequisitesMake sure that the connectivity between the SAP R/3 system and the SAP SCM system has been successfully set up. This step should have already been completed as part of the scenario installation.

1.1 SAP Notes Building Block Replication SCMCurrently no SAP Note is required for this building block.

1.2 Uploading the Configuration Role

UseBefore you start with the configuration according to the manual procedures described in this configuration guide, upload the configuration role and assign it to your user.

SAP Best Practices provides a configuration role for each component involved in this configuration, that is, for SAP APO or SAP R/3. The configuration role is a special user menu that enables you to comfortably access all necessary transactions for the configuration from the relevant system. The following roles are available:

Technical name Description

B05_01CConfiguration role for Replication SCM (SAP R/3)

B05_02CConfiguration role for Replication SCM (SAP APO)

ProcedureFor details on how to upload configuration roles to the system and how to work with them, refer to the document Essential Information.



2 Preliminary Steps

2.1 SAP R/3: Preliminary Steps

2.1.1 Activating the CIF Application Log (SAP R/3)

UseBy activating the CIF application log, you can analyze errors that occur during data transfer. The log will provide you with information such as who and when transferred what data from R/3 to the APO system.

Procedure1. Access the activity using one of the following navigation options:

SAP R/3 Role Menu Activating the CIF Application Log (SAP R/3)

Transaction Code CFC2

SAP Menu Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for the Data Transfer Set User Parameters

The Change View “Maintenance View for CIFGPARAMS”: Overview screen is displayed.

2. Choose New entries from the application toolbar.

3. In the Maintenance View for CIFGPARAMS table, make the following entries or select the given option from the list:

User RFC Mode Logging Debugging

* Q (Queued RFC) X (Normal) No entry (Debugging off)

4. Choose Save.

5. Enter a customizing request.

6. Go back.

To avoid any performance problems, it is recommended to set the user parameters for logging to "normal". To display a detailed error log, change the logging setting from "normal" to "detailed" for your user. Do not forget to change the settings back to "normal", after you finish.



2.1.2 Changing Material (MRP Type) (SAP R/3)

UseThis step is simple but very important. Here you define which of your materials are to be planned in the SAP APO system, i.e. they are excluded from planning in the SAP R/3 system. You achieve that by changing the MRP type of the materials you want to plan in SAP APO. The MRP type “X0” excludes materials from the MRP run in SAP R/3. It is also used as a selection criterion for the integration model and the data transfer.

Please consider carefully which materials to select.

If you want to use mass maintenance, implement the transaction MM17. Be careful when working with the mass maintenance transaction.


SAP R/3 Role Menu Changing Material (MRP Type) (SAP R/3)

Transaction Code MM02

SAP Menu Logistics Materials Management Material Master Material Change Immediately

2. On the initial screen, enter a material number and choose Enter.

3. On the Select View(s) dialog box, select the views: MRP 1 and choose Enter.

4. In the Organizational Levels dialog box, enter your plant or storage location and choose Enter.

5. On the MRP 1 tab page, in the MRP Procedure screen area, set MRP type X0.

6. Save and go back.

7. Repeat the procedure for all materials that are to be planned in the SAP APO system.



2.1.3 Changing Material (MRP Type) using Mass Maintenance (SAP R/3)

UseThis section describes how to change material master data using mass maintenance transaction.

Be careful when using the mass maintenance transaction. You might inadvertently change more materials than you intend to do if you specify an incorrect range.


SAP R/3 Role Menu Changing Material (MRP Type) using Mass Maintenance (SAP R/3)


SAP Menu Logistics Materials Management Material Master Material Mass Maintenance

2. On the Mass Maintenance: Materials (industry) screen, define relevant tables for mass maintenance. Select the following line:

Short Description Table Name

Plant Data for Material MARC

3. On the Fields tab page, select the following line :

Description Fld Name

MRP Type MARC-DISMM

4. Choose Execute.

5. On the Data Records to Be Changed tab page, specify the materials you want to maintain:

Field name User action and values Example

Material To define the range of materials you want to change, specify a high and a low value (material number)

e.g. APO-FERT-01 to APO-FERT-04

Plant To define the range of plants, specify a high and a low value (plant key)

e.g. BP01 to BP0X

6. Choose Execute.

7. On the Plant Data for Material tab page, select the materials you want to maintain.

The last column of the table contains the MRP type that needs to be maintained.

8. On the New Values screen area, select X0 - W/O MRP, with BOM Explosion.

9. To assign this value to all products, choose Carry Out a Mass Change.



You can undo changes by selecting Undo Changes.

10. Choose Save and choose Back four times.

2.1.4 Assigning the Node Type: Plant (SAP R/3)

UseThe R/3 system does not differentiate between production plants and distribution centers. In the SAP APO system, however, these locations are distinguished by a location type. Moreover, different settings apply to them, for example, no production is possible in a distribution center. In order for the data to be transferred correctly, it is required to specifically define which plants in SAP R/3 correspond to production plants and which to distribution centers.

Procedure1. Access the transaction using one of the following navigation options:

SAP R/3 Role Menu Maintaining assignment of node type - plant

Transaction Code SPRO

SAP IMG Menu Production Distribution Resource Planning (DRP) Basic Settings Maintain assignment of node type - plant

2. Select Allocation of node type.

3. Assign the node type “PL” to your production plants and “DC” to your distribution centers.

4. Choose Save.

5. Choose or create a customizing request.

6. Go back.

2.1.5 Checking Material (Procurement Type) (SAP R/3)

UseThe procurement type defines how a material is procured. In a distribution center, the material should be procured externally, for example, from a production plant. All location products where the location is a distribution center are to have the procurement type “F” for external procurement.

If you want to use mass maintenance, implement the transaction MM17 (see chapter Changing Material (MRP Type) using Mass Maintenance (SAP R/3)). In this case choose Table = Plant Data for Material (MARC) and Field = Procurement (MARC-BESKZ).

Be careful when working with the mass maintenance transaction.







2. On the initial screen, enter the material number and choose Enter.

3. On the Select View(s) dialog box, select the views: MRP 2 and choose Enter.

4. On the Organizational Levels dialog box, enter your plant (distribution center) and choose Enter.

5. On the MRP 2 tab page, in the Procurement screen area, select F as procurement type.



2.1.6 Checking Material (Purchasing Group) (SAP R/3)

UseThe purchasing group is a buyer or a group of buyers, who is/are responsible for certain purchasing activities. In order to create purchase requisitions in SAP APO and to transfer them to SAP R/3, assign a purchasing group in your material master.

If you want to use mass maintenance, implement the transaction MM17 (see chapter Changing Material (MRP Type) using Mass Maintenance (SAP R/3)). In this case choose Table = Plant Data for Material (MARC) and Field = Purch. Group (MARC-EKGRP).

Be careful when working with the mass maintenance transaction.






3. In the Select View(s) dialog box, select the MRP 1 views and choose Enter.

4. In the Organizational Levels dialog box, enter your plant and choose Enter.

5. On the MRP 1 tab page, in the General Data dialog box, assign an existing Purchasing Group.





2.1.7 Selecting Resource Type (SAP R/3)

UseThis step is mandatory only if you plan to work with Supply Network Planning (SNP) in SAP APO.

The purpose of this activity is to specify which resource type is to be assigned to resources created in SAP APO. Per default, capacities are mapped to single-activity resources or multi-activity resources in SAP APO and can be used only in Production Planning and Detailed Scheduling (PP/DS). You cannot change the resource type in SAP APO.

In order to use resources for Production Planning and Detailed Scheduling (PP/DS) and Supply Network Planning (SNP), you have to use mixed resources.

Prior to the first transfer of capacities from SAP R/3 to SAP APO, you have to specify which resource type is to be assigned to the resources created in SAP APO.


SAP R/3 Role Menu Selecting Resource Type


IMG Menu Integration with Other mySAP.com Components Advanced Planning and Optimization Application-Specific Settings and Enhancements Settings for Resources Set the Transfer of Resources to SAP APO

2. On the Change View “Change Target-System-Independent Settings in CIF screen, make the following entries:

Field name Description User action and values Notes

Type Single Resource

04 Single mixed resource

Type Multiresource

05 Multi-mixed resource

3. Choose Save.

4. Choose or create a customizing request.

5. Go back.



2.2 SAP APO: Preliminary Steps

2.2.1 Activating the Customizing Import from SAP R/3 (SAP APO)

UseThe purpose of this activity is to activate the settings in SAP APO that allow customizing to be imported from SAP R/3 to SAP APO.

The customizing import from SAP R/3 to SAP APO is selected in the integration model in the section Material Independent Objects. You can import customizing for Available-to-Promise (ATP) and for product allocation.

We recommend that you copy customizing data only once. Otherwise, existing settings could be overwritten.


SAP APO Role Menu Activating the Customizing Import from SAP R/3 (SAP APO)


IMG Menu mySAP SCM - Implementation Guide Advanced Planning and Optimization Global Available-to-Promise (Global ATP) General settings Maintain Global Settings for Availability Check

2. On the Change View “Global Settings: Overview“ screen, make the following settings:

Field Value Comments

TQA (Temporary quantity assignment) X Select

IC (Import Customizing) Do not select (check the Possible Entries list (F4))

3. Choose Save and go back.

2.2.2 Maintaining Units of Measure (SAP APO)

UseCarry out this activity only if your SAP R/3 data, which has to be transferred to SAP APO, requires additional units of measure that are not included in the SAP standard.



Procedure1. Run the activity Activate Units of Measure or access the transaction as following:

SAP APO Role Menu Maintaining Units of Measure (SAP APO)

Transaction Code CUNI

IMG Menu mySAP SCM - Implementation Guide General settings Check Units of Measurement

2. On the Units of Measurement: Initial Screen, specify a dimension for the unit of measurement you want to create in SAP APO. To do this, choose Possible Entries (F4), next to Units of Measurement, and select the required dimension.

3. Choose Units of measurement.

4. On the Change Unit of Measurement of Dimension screen, choose Create from the application toolbar to add a new unit of measurement.

5. Maintain all fields in accordance with the corresponding Customizing settings in your SAP R/3 system.

Use the transaction CUNI to access and check the settings in SAP R/3.

6. Save your entries.

7. Enter a customizing request and go back.

8. Repeat this step for all the additional units of measurement required.

2.2.3 Defining the Transportation Group (SAP APO)

UseThe assignment of a transportation group to a material is transferred to SAP APO via CIF with the material master. The customizing for defining the transportation groups, however, is not transferred. Therefore, you must create manually all relevant transportation groups in SAP APO customizing before starting data replication.

You can check and define the transportation groups in the SAP R/3 system by using the following R/3 IMG path: Sales and Distribution Basic Functions Routes Route Determination Define Transportation Groups.


SAP APO Role Menu Defining the Transportation Group (SAP APO)


IMG Menu mySAP SCM - Implementation Guide Advanced Planning and Optimization Transportation Planning/Vehicle Scheduling



Basic Settings Maintain Transportation Group

2. In the Change View "Transportation Group": Overview screen, choose New entries.

3. Make the necessary entries:

Transportation Group Description

Enter the transportation group used in your material master (e.g. 0002)

Enter transportation group description

(e.g. Transportation Grp. 01)

4. Save your entries and go back.

You can check the transportation group assigned to your materials in the R/3 system as following:

1. Open the transaction MM02 or use the path SAP Menu -> Logistics Materials Management Material Master Material Change Immediately


3. In the Select View(s) dialog box, select Sales: General/Plant and choose Enter.

4. In the Organizational Levels dialog box, enter your plant, sales organization and distribution channel and choose Enter.

5. On the Sales: General/Plant tab page, in the Shipping data (times in days) screen are, select the transportation group (Trans. Grp) and make changes if necessary.

6. Save your entries.

2.2.4 User Settings and Activating the CIF Application Log (SAP APO)

UseWith this step, you maintain some global parameters for the SAP APO users. In addition, you activate the CIF application log for these users. This enables you to analyze errors occurring during data transfer, because error messages are stored in the destination system’s application log. You have already activated the CIF application log in the R/3 system in the previous step.


SAP APO Role Menu User Settings and Activating the CIF Application Log (SAP APO)

Transaction Code /SAPAPO/C4

SAP Menu Advanced Planning and Optimization APO Administration Integration Settings User Settings

2. On the Change View Maintenance View for Global Parameters …” screen, choose New entries from the application toolbar and make the following entries:



User Logging Debugging Recording

<User name> Standard (only the number of transferred data records)

Debugging Off Default

3. Save your entries and go back to the installation role.

To avoid any performance problems, it is recommended to set the user parameters for logging to "Standard". To display a detailed error log, change the logging setting from "Standard" to "Detailed" for your user. Do not forget to change the settings back to "Standard" after you have finished.

2.2.5 Defining Class System (SAP APO)

UseIn this step, you define the characteristics and class systems required for planning configurable materials in the SAP APO system.

This activity is optional and is applicable only if you want to work with classes and characteristics within APO.

If you use classification in SAP APO, you have to decide which class system you want to use. You can choose between two characteristics: CDP and Classical.

CDP (C: Characteristic-dependent planning) can be used in Make-To-Order and Make-To-Stock scenarios. It enables you to use functions like characteristics propagation, block scheduling, and the consideration of characteristics during pegging.

Classical System (I: IBase and R/3 characteristics) can be used in Make-To-Order scenarios for mass production, for example in the automobile industry. Product configuration is shown in the iPPE (integrated product and process engineering).

You must define the class system before creating classified master data and characteristics-dependent transaction data in the SAP APO system.

Subsequent changes to this setting during productive operation may lead to loss of data!


SAP APO Role Menu Defining Class System (SAP APO)


IMG Menu mySAP SCM Implementation Guide Advanced Planning and



Optimization (APO) Basis Settings Define Class System (CDP or Classical Characteristic)

2. On the Change View “Definition of Characteristic and Class System”: Details screen, in the Definition of Characteristic and Class System screen area, select the required value, depending on your scenario:Field Value

Settings C (CDP) or I (IBase and R/3 characteristics)


2.2.6 Installing General User Exit (SAP APO)

UseCustomers, suppliers, production plants, distribution centers, etc. from SAP R/3 are all defined as locations, that is, as one category in the SAP APO system. As a consequence, you have to rename locations in the SAP APO system to prevent a customer and a production plant number from having the same location number in SAP APO. To do this, you need a user exit. The user exit adds the prefix “CU” for customers, the prefix “SU” for suppliers, and so on, and the logical system name is appended as a postfix to all location numbers. This way, you can be sure that even if two locations have the same number in SAP R/3, each of them has a unique number in SAP APO.

The following three situations deal with three different source codes for the user exit (this section uses note 458914 as a reference)

1. Different location types with the same name or number in the external system. For example, a customer and a supplier both have the number 1000. This problem increasingly occurs with vendor and customer numbers.

2. The same locations from different external systems. Here you must explicitly decide whether it is the same location in the different systems or not. The proposed source code deals only with the case where locations have the same external name, but are in fact different objects.

Example: Location (plant) 0001 in system A does not correspond to Location (plant) 0001 in System B.

However, if such a case occurs, you must deal with it explicitly in the user exit.

3. A combination of the first and the second problem.

The SAP R/3 enhancement concept allows you to add your own functions to SAP standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functions. Instead, the customer exits act as hooks. You can hang your own add-on functions onto these hooks.




SAP APO Role Menu Installing User Exits (SAP APO)

Transaction Code CMOD

SAP Menu Tools ABAP/4 Workbench Utilities Enhancements Project Management

2. In the Project Management of SAP Enhancements screen, enter a name for the project.

Project Name e.g. U02B0501„U“ for user exit“02” for a defined area/function“B05” for a relevant building block“01” as a counter

Generally, you give your project a name that indicates the type of functions contained and that shows which transactions are affected. It may be useful to agree upon a company-wide naming convention for enhancement projects.

3. Choose Create.

4. In the Attributes of Enhancement for Project… screen, enter a short text describing the function of the user exit - in this case” Renaming Locations”.

5. Choose Save.

6. The system prompts you to assign a change request. Enter a development class or choose Local object to save it locally. If you enter a development class, you will be able to transport the project and its components into a productive system if you wish to do so.

7. Go back.

8. Select Enhancement assignments and choose Change.

9. Go to the first line and specify the SAP enhancement packages you want to include:

Enhancement APOCF001

10. Choose Save.

11. Return to the main screen of the Project Management transaction, select Components from the sub-objects and choose Display. Make sure that the name of the project is correct.

12. In the Display U02B0501 screen, double-click the function exit: EXIT_/SAPAPO/SAPLCIF_LOC_001

13. In the next screen, under the Source code tab page, scroll down to the bottom of the screen and double-click the Include ZXCIFUSERU06 field.

14. The Create object dialog box is displayed. Confirm the message: Do you want to create the object?

15. Confirm the information message.

16. In the Create Object Directory Entry dialog box, choose a development class or save as local object.

The View ABAP Editor: Change Include ZXCIFUSERU06 screen is displayed.



17. Choose Utilities More utilities Upload/Download Upload.

18. Select one of the following files, depending on your particular requirements:

cifloc1.txt: for situation (1) mentioned in the Use section

cifloc2.txt: for situation (2) mentioned in the Use section

cifloc3.txt for situation (3) mentioned in the Use section

Make sure that all lines containing comments, which starts with an asterisk “*” are blue in color and have no indent, i.e. are aligned to the left. Only then does the system recognize these lines as comment lines. Otherwise a syntax error will be displayed.

In the coding provided, the locations are renamed by appending the logical system, e.g. plant number 1000 in SAP R/3, plant number in PL1000/SS8CLNT224 SAP APO where “SS8” is the system name and “224” the client name. Please note that the character “@” is not used when renaming the plant because SAP APO-BW does not recognize the symbol “@”. Therefore, the plant number is separated from the postfix with the character “/”.

19. Choose Save and Choose Activate.

20. Choose Back three times to return to the Project Management screen.

21. Choose Activate project from the application toolbar.

22. Go back.

2.2.7 Installing User Exit for SNP (SAP APO)

UseWith this step you will install a user exit which is required to run Supply Network Planning in the APO system. The user exit maintains the variable bucket consumption of mixed resources.

Procedure1. Run the activity Enhancements or access the transaction as follows:

SAP APO Menu Path SAP Menu Tools ABAP/4 Workbench Utilities Enhancements Project Management

Transaction Code CMOD

2. On the Project Management of SAP Enhancements screen, enter a name for the project:

Project e.g. U02SNP02„U“ for user exit



Name “02” for a defined area/function“SNP” for the building block“01” as a counter

Generally, you give your project a name that indicates the type of functions it contains and shows, which transactions are affected. It may be useful to agree upon a company-wide naming convention for enhancement projects.

3. Choose Create.

4. On the Attributes of Enhancement for Project…screen, enter a short text describing the function of the user exit - in this case “PPM Bucket Capacities”.

5. Choose Save

6. The system prompts you to assign a change request. Enter a development class or choose Local object to save it locally. If you enter a development class, you will be able to transport the project and its components into a productive system if you wish to do so.

7. Go back.

8. Select Enhancement assignments and choose Change.

9. Go to the first line and specify which SAP enhancement packages you want to include:

Enhancement APOCF012

Inbound Processing: Production Process Model

10. Choose Save.

11. Return to the main screen of the Project Management transaction, select Components from the sub-objects and choose Display. Make sure that the name of the project is correct.

13. On the Display U02S1102 screen, double-click the function exit EXIT_/SAPAPO/SAPLCIF_PPM_001

14. In the next screen under the Source code tab page, scroll down to the bottom of the screen and double-click the row: Include ZXCIFUSERU16.

The Create object dialog box is displayed.

15. Confirm the message Do you want to create the object?

16. Confirm information message.

17. In the Create Object Directory Entry dialog box, choose a development class or save as local object.

The View ABAP Editor: Change Include ZXCIFUSERU16 dialog box is displayed.

18. From menu choose Utilities More utilities Upload/Download Upload

19. Select the file ppm_bucket_consumption_user_exit_01.

It is delivered with SAP Best Practices CD.

20. Choose Save

21. Double-click the line perform bcons_prop_mix_res.

The Create Object dialog box is displayed.

22. Confirm the message Do you want to create the object?

23. In the following dialog box, change ZXCIFUSERU01 to ZXCIFUSERU16 and choose OK.



24. Confirm the warning message.

25. On the following screen, delete all codings except the first three lines. The screen should look as follows:

*----------------------------------------------------------------------*

***INCLUDE ZXCIFUSERU16 .

*----------------------------------------------------------------------*

26. Choose Utilities More utilities Upload/Download Upload.

27. Select the file ppm_bucket_consumption_user_exit_02 and choose Save.

28. Choose Activate.

29. Select all entries.

30. If a dialog box concerning syntax errors is displayed, ignore the error.

31. Choose Back three times to return to the Project Management screen.

32. Choose Activate project and go back

In some cases an error occurs during the implementation of the user exit: the INCLUDE ZXCIFUSERU16 is created twice. The result is that variable bucket consumptions are not transferred correctly. To solve this problem proceed as follows:

1. The Project Management of SAP Enhancements screen area is displayed. Enter the project you have just created, e.g. U02S1102

2. Select Components and choose Display.

3. Double-click EXIT_/SAPAPO/SAPLCIF_PPM_001.

4. Go to the bottom of the source code.

5. Double-click ZXCIFUSERU16.

6. Double-click the line perform bcons_prop_mix_res

7. Double-click ZXCIFUSERU16.

Under Found locations screen area INCLUDE ZXCIFUSERU16 is displayed

twice.

8. Double-click one of the lines.

9. Delete one of the identical lines ZXCIFUSERZZZ.

10. Save and activate ZXCIFUSERZZZ.



3 Data Replication

The following section describes how to create and activate integration models. Integration models are used to transfer master data from the SAP R/3 system to the SAP APO system and transaction data between both systems.

Before you start with the data replication, please make sure that the business transaction events are active in the SAP R/3 system. Only if these events are active for the SAP APO integration, will changes to the transaction data be transferred from the SAP R/3 system to the SAP APO system. This setting should have already been performed by your system administrator, so this note is just a reminder in order to avoid possible problems later on. Use the following procedure:

1. In your SAP R/3 system, open the transaction BF11.

2. Confirm the message The table is cross client.

3. On the Change View: Application Indicator”: Overview screen, check that the applications ND-APO and NDI are active, i.e. selected. If they are inactive, set them to active by selecting the box.


3.1 Creating Integration Models (SAP R/3)

UseIntegration models are used to transfer both master and transaction data from SAP R/3 to SAP APO.

This section describes how to create integration models in general. It does not contain specific information about the type of data you are going to transfer. You can find detailed instructions on the integration models of the scenario you are installing in the Data Replication section of the corresponding scenario installation guide. To continue with the installation of your scenario, open the Data Replication section of this scenario installation guide and go through this step using both documents.

PrerequisitesYou have decided how many integration models you need to create. The number of required integration models depends on the total amount of data you have to transfer.

ProcedureIt is recommended to create different integration models for master and transaction data. This does not only improve the performance, but also helps to identify any errors that may occur during data transfer.



Please note that only the data you specifically define within your integration models will be transferred. If the data is incomplete, errors may occur during data transfer or the run of a process in the SAP APO system.

1. Access the activity using one of the following navigation options:

SAP R/3 Role Menu Creating Integration Models (SAP R/3)

Transaction Code CFM1

SAP Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Generate Create

2. Make the following entries:

Field name User action and values Default values

Model Name Specify a name for the integration model

<Name> _ <Data type>

e.g. VMI_MD

Logical System Specify target logical system <System ID>CLNT<client number>e.g. CS7CLNT001

APO Application

Specify the name of the SAP APO application

e.g. MASTERDATA or TRANS_DATA

The Create Integration Model screen is divided into three major sections:

Material Dependent Objects

General Selection Options for Materials

Material Independent Objects.

3. Refer to the scenario installation guide and select the Material Dependent Objects specified there.

4. In the General Selection Options for Materials screen area, specify or define ranges for the material dependent objects by using the criteria applicable to all objects. The following table shows an example:

Field name User action and values Comments

Material To define the range of materials you want to plan in SAP APO, specify a high and a low value (material number)

Choose the yellow selection arrow to specify the details and to define the range for each data type.

Use the online help (press F1) for detailed information on specific settings

Plant To define the range of plants, specify a high and a low value (plant key)

MRP Type X0

…. ….



If you are installing a scenario where no production takes place (example: VMI or Order Fulfilment) continue with step 9.

If you use production process models (PPMs) for your business processes, perform steps 5 and 8.

If you use run time objects, perform steps 6 to 8.

5. Choose the yellow arrow button to the right of the PPM field. A dialog box is displayed. Make the following entries:

Field name User action and values

PPM Selection Date Enter 1: Resolution according to time of transfer

Rep.mfg Change the default value Detailed Planning to Rate-based Plng only if it corresponds to your requirements

6. Choose the yellow arrow button to the right of the PP/DS runtime object field. A dialog box appears. Make the following entries:


Production Version Enter a production version of the product

Rep.mfg Change the default value Detailed Planning to Rate-based Plng only if it corresponds to your requirements

7. If you have phantom products in your BOM, you can also transfer them with the runtime object. Choose the yellow arrow button to the right of the BOM field. A dialog box is displayed. Make the following entries:


Usage Enter the usage type of the BOM you want to transfer

Alternative Enter the alternative ID of the BOM

8. You can apply additional criteria to the PPM selection, for example, by further restricting the materials or the plants.

9. You can further restrict the selected material dependent objects by choosing the yellow arrow button next to the object. The selection criteria will be applied in addition to those defined in General Selection Option for Materials.

10. Refer to the scenario installation guide and select Material Independent Objects

11. Specify or define ranges for the material independent objects by choosing the yellow arrow button next to the objects. A dialog box is displayed. You can define value ranges and selection criteria for the objects you have already selected.

Please note: If you make no restrictions to the material independent objects selected for the integration model, the system automatically selects all objects for this object type, for example, all customers in the system. This can lead to significant performance problems during data transfer.



3.2 Saving Results and Creating Variants (SAP R/3)

Procedure1. After selecting the objects to be included in the integration model, choose Execute to display

the results list.

On the Create Integration Model screen, the selected filter objects are displayed, that is, the type and the (total) quantity of the selected data.

2. Navigate to the detailed view for each filter object by choosing Details.

A list and information of the data objects you have selected with the name of your model and the target system is displayed.

3. Verify that only the required objects are included in the integration model.

4. Choose Consistency Check to conduct a consistency check of the integration model.

If, as a result of the consistency check of the integration models for transaction you have warning messages such as “material is not included in the integration model”, you can ignore them, since the material master data have already been included in a previous model.

5. Choose Save or press Ctrl+S.

6. Confirm the information message "Integration model <name of your model> generated for target system <logical system name> and application <name of application>.

7. Choose Back twice.

8. In the Should your selection options be saved as a variant? dialog box, choose Yes.

It is recommended that you create variants, because the system does not save the selection options you have made when creating an integration model. By working with variants you are able to reuse the settings or change the original integration model at a later point in time. For more information see also the respective chapter “Changing Integration Models”.

9. On the ABAP – Save as Variant screen, enter a name and a description for your variant and choose Save.

10. Go back.



3.3 Activating Integration Models (SAP R/3)

UseAfter creating the integration models, containing the data you want to transfer to the SAP APO system, you need to activate them. The activation of an integration model leads to the initial data transfer from SAP R/3 to SAP APO.

PrerequisitesYou have created the required integration models as described in the previous step.


SAP R/3 Role Menu Activating Integration Models (SAP R/3)


SAP Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Activate

2. On the Activate or Deactivate Integration Model screen, make the following entries:

Model Logical/target system APO application

Enter the name of the integration model or press F4 to choose from the available models

e.g. AS7CLNT001 e.g. MASTERDATA, TRANS_DATA

If several integration models exist with the same name, they will be displayed in chronological order according to date and time. They may also be assigned to different logical systems (target systems) and SAP APO applications.

3. Choose Execute.

You can carry out a consistency check of the integration model before activating it. To do that, choose the creation data of the integration model and choose Check. This way, you can identify possible errors before the actual data transfer begins.

4. Select a model by double-clicking the creation date of the model or selecting Set to active/inactive from the application toolbar.

5. A green checkmark is placed before the creation date of the model.

6. If a model is already activated (green checkmark), deactivate the model by double-clicking the date or selecting Set to active/inactive from the application toolbar.A red cross is placed before the model, which is deactivated now.

7. Choose Start.



The message Integration Model has been successfully activated or deactivated is displayed.

If during the model activation the system displays error message NR 751 ‘For object CIF_LOAD , number range interval 1 does not exist, go to transaction code SNUM, enter the object CIF_LOAD and choose Number Range and Intervals to add the number range 1 (0001 – 9999).

You can choose Check to carry out a consistency check of the integration model.

3.4 Changing Integration Models (SAP R/3)

UseThis activity describes how to change existing activated integration models. Changes to integration models may be necessary, if you intend to plan additional products or locations in SAP APO.

PrerequisitesThe integration model you want to change has already been created and the settings have been saved as a variant.

Generating a New Integration Model1. Access the activity using one of the following navigation options:

SAP R/3Role Menu

Changing Integration Models


SAP R/3 Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Generate Create

2. On the Create Integration Model screen, go to Goto -> Variants -> Get Variant.

3. Select the variant, which corresponds to the integration model you want to change.

The settings for the integration model are displayed.

4. Proceed with making the required changes or enhancements to the integration model.

5. Choose Execute.

A new integration model is generated.


7. On the ABAP: Save as Variant screen, decide if you want to overwrite the existing variant or create a new one.

8. Go back.



Activating the Changed Integration Model1. Access the activity using the following navigation options:

SAP R/3Role Menu

Changing Integration Models


SAP R/3 Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Activate

2. Enter a model name, a logical system and an APO application and choose Execute.

3. On the Activate or Deactivate Integration Model screen, a green check symbol indicates the currently active integration model.

The changed integration model with the time and date of the change is displayed in the first row and is not active.

4. Double click the changed integration model. A green check symbol appears on its left. At the same time, a red cross appears to the left of the old integration model.

5. Choose Start.

The changed integration model is activated and the old version of this integration model is deactivated.

6. Go back.

Result You can now perform changes to active and deactivate integration models.



3.5 Maintaining Distribution Definition (SAP APO)

UseThis step describes how to distribute the planning results from SAP APO to the relevant logical backend systems.

Information on the particular planning results to be distributed can be found in the replication section of the respective SCM scenario.


SAP APO Role Menu Maintaining Distribution Definition (SAP APO)

Transaction Code /SAPAPO/CP1

IMG Menu mySAP SCM – Installation Guide Advanced Planning and Optimization Basis Settings Integration Publication Maintain Distribution Definition

2. On the Change View "Maintenance View for Distribution Definitions" screen, choose New Entries from the application toolbar.

3. On the New Entries: Overview of Added Entries screen, make the following entries as required for your scenario:

Publication Type Location No. Logical System SAP Rel.

e.g. In-house Production

e.g. Planned independent requirements

Enter your location no. e.g. 1000

Name of the R/3 logical system e.g.

DS7CLNT330

e.g. 4.6C




4 Additional Customizing for Replication

4.1 Deactivating the Customizing Import from SAP R/3 (SAP APO)

UseThe purpose of this activity is to deactivate settings in the SAP APO systems that allow customizing imports from SAP R/3 into SAP APO. Thus, you stop further customizing data being imported into SAP APO.

This activity is optional. We recommend that you copy the customizing data only once. Otherwise, existing settings could be overwritten. This activity prevents any additional customizing data from being imported into SAP APO.


SAP APO Role Menu Deactivating the Customizing Import from SAP R/3 (SAP APO)


IMG Menu mySAP SCM – Implementation Guide Advanced Planning and Optimization (APO) Global Available-to-Promise (Global ATP) General settings Maintain Global Settings for Availability Check

The Change View “Global Settings for Availability Check“ screen is displayed.

2. In order to deactivate the import of customizing make the following settings:

Field Value Comments

TQA (Temporary quantity assignment) X Select

IC (Import Customizing) X Select (check the Possible Entries list (F4))




5 Master Data Delta Transfer

UseThe following section describes how to transfer changes concerning the master data in R/3 to the APO system. This section does not describe how to perform the initial data transfer.

PrerequisitesThe initial data transfer has already been performed. This means, that the objects to be transferred, for example, material master or PPM have been already included in an active integration model.

5.1 Activating ALE Change Pointers

UseThis activity allows you to activate the setting that enables the transfer of master data changes using change pointers.


Transaction Code spro

R/3 IMG Menu SAP Web Appication Server Integration with other mySAP.com components Advanced Planning and Optimization Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Activate ALE Change Pointer Generally

2. On the Activate Change Pointers Generally screen, select Change pointers activated – Generally.




5.2 Delta Transfer of Material Masters, Customers and Suppliers

UseIn contrast to transaction data such as orders, purchase requisitions, etc., changes to master data in the SAP R/3 are usually not transferred to SAP APO automatically. This section describes which settings are required for a delta data transfer for material masters, customers and suppliers.

Please note that the first part of the procedure must be performed before the changes to the master data are made.

PrerequisitesAn active integration model for the objects to be transferred already exists.

Configure Change Transfer Before Changing the Master Data1. Access the activity using the one of following navigation options:

Transaction Code CFC9

IMG Menu SAP Customizing Implementation Guide Integration with other mySAP.com Components Advanced Planning and Optimization Basic Settings for the Data Transfer Change Transfer Configure Change Transfer for Master Data

2. In the Change Transfer for Master Data screen area, specify the periodic delta transfer of material masters, customers and vendors. It is not recommended to set the master data delta transfer to “immediately”, since this can easily lead to data inconsistencies between the two systems.


Material Master Change Transfer 1: ALE change transfer, periodic

Change Transfer for Customers 1: ALE change transfer, periodic

Change Transfer for Vendors 1: ALE change transfer, periodic

This setting defines that a change pointer is issued every time you change the material master, a customer or a vendor. As a result, you can periodically select these pointers and initiate the delta data transfer.



The delta transfer for resources is set to ALE Change Transfer, Periodic by default. To change that, go to the Initial Data Transfer and Change Transfer for Resource screen area.

3. Choose Save and exit the transaction.

Transferring the Master Data Changes1. To collect the change pointers and initiate the delta transfer, use one of the following

navigation options:

SAP R/3 Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Change Transfer Master Data

Transaction Code CFP1

2. In the Send Parameters screen area, make sure that the logical name of the target SAP APO system is correct.

3. In the Object Types screen area, select the objects that have been changed in SAP R/3 and have to be re-transferred to SAP APO.

If the selected objects have not been changed since the last data transfer, the message No master data changes – Transfer has not taken place is displayed.

5.3 Delta Transfer of PPMs

UseAny changes to bills of materials, routings, receipts and production versions taking place in SAP R/3 are recorded automatically. In this procedure, you can update the PPMs in SAP APO that are affected by the changes made in SAP R/3. However, there are not functions available allowing you to have different PPM versions in the SAP APO system at the same time.

PrerequisitesAn active integration model with the PPM is available.

ProcedureAll changes to BOM, routing, etc. made after the last PPM transfer have been automatically

recorded by the system.

1. Access the activity using one of the following navigation options:



Transaction Code CFP3

SAP Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner & Optimizer Integration Model Change Transfer PPM Send Changes

2. On the Sending Changes to Production Process Models screen, make the following entries:


Material Enter a materials for which you changed the BOM or routing

Plant Enter a production plant

Production Version Enter a production version number

3. Choose Execute.

ResultThe PPM in SAP APO is updated using the current information. If changes were not transferred, refer to the troubleshooting section.

5.4 Delta Transfer of Runtime Objects

UseAny changes to bills of materials, routings, receipts and production versions taking place in SAP R/3 are automatically recorded. If APO runtime objects are affected by these changes, you can use this procedure to update the runtime objects in SAP APO.

PrerequisitesAn active integration model with runtime object is available.


Transaction Code CURTO_Create

IMG Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner & Optimizer Integration Model Change Transfer PP/DS run time object Transfer PP/DS Runtime Object

2. On the Transfer of PP/DS Runtime objects to APO screen, make the following entries:




Logical system Enter an APO logical system number

Version Enter the version “000”

Material Enter the materials for which you have changed the BOM or routing

Plant Enter an production plant

Production Version Enter a production version number

Rate Routing Select if you use rate routing

Change Transfer By setting this indicator, you specify that only those R/3 runtime objects are transferred to SAP APO for which a master data change has been made since the last transfer.

3. Choose Execute.

Result The runtime objects in APO are updated using the current information. If changes were not transferred, please refer to the troubleshooting section.

5.5 Delta Transfer of Production Orders

UseThe purpose of this activity is to give some general recommendations about the changes of production orders in SAP R/3 that are transferred to SAP APO.

PrerequisitesAn active integration model for production orders is available.

ProcedureThe following changes to production orders will automatically be transferred to SAP APO:

Delete operation

Include component

Changes to the duration of an operation will not be transferred to SAP APO, because SAP APO is the leading system as far as the scheduling is concerned and the APO values will overwrite the R/3 values. However, the user still has the option to include a new operation in SAP R/3 or change the work centers, for example. In this case, the operation data has to be complete. In addition, the following settings must be made. For details, please refer to note 314816.



Settings in SAP R/31. Access the activity using one the following navigation options:

Transaction Code OPU3

IMG Menu Production Capacity Requirements Planning Operations Scheduling Define Scheduling Parameters for Production Orders

2. On the Change View: Scheduling Parameters Overview screen, select your plant and the order type you are using. For example:

Field name Values

Plant e.g. BP01

Order Type e.g. PP01

3. Choose Details.

4. Regardless of the production method you are using, select all the settings mentioned below:

Field name Values

Scheduling Select

Generate Capacity Requirements

Select

Automatic Scheduling Select


These settings ensure that when, for example, an operation is added to a production order in SAP R/3, and the capacity requirements are generated and transferred to SAP APO. This is required if this operation does not exist in SAP APO.

Settings in SAP APO1. Access the activity using one of the following navigation options:

Transaction Code /N/SAPAPO/CP3

IMG Menu mySAP SCM – Implementation Guide Advanced Planning and Optimization Basis Settings Integration Publication Maintain Object-Specific Settings

2. On the Change View: Object Specific Settings for Publication – Overview screen, choose New Entries.

3. Make the following entries:

Field name Values

Publ. Type Inhouse production

Retransfer Only retransfer after online transfer






6 Monitoring

6.1 Setting up the qRFC Alert (Optional)

UseThe qRFC Alert supports the user during the initial and the subsequent delta transfer of master and transaction data. In this step, you define the systems you want to monitor and identify which person(s) and in what way are to be informed about errors occurring during the data transfer. This way, no time is wasted and the user can quickly respond to any unusual situations.

PrerequisitesIf you want to receive e-mails via the Internet, you must enter an Internet address in your user settings.


SAP APORole Menu

Setting up the qRFC Alert

Transaction Code /SAPAPO/CW

APO Menu Advanced Planning and Optimization APO Administration Integration Monitor qRFC Alert (Outbound Queues)

If you are working with inbound queues, you must open transaction /sapapo/cqinw.

5. In the qRFC Monitoring (Outbound Queues) screen, make the following entries:


Local Outbound Queue

Target System Enter the logical name of the target R/3 system or leave the wild card “*” if more than one R/3 system is connected to SAP APO.

Notification Select “Initiator” (user who caused the queue block) or “Administrator” if there is one person responsible for the queue monitoring.

Remote Outbound Queue

Remote Systems Enter the logical name of the target R/3 system or enter a wild card “*”

Target System Enter the logical name of the SAP APO system, e.g. AS7CLNT001

Notification Select “Administrator” and enter the name of the user



After creating a profile, you must schedule a job to periodically activate the qRFC Alert.

6.2 Monitoring in R/3

6.2.1 Displaying the qRFC Monitor (SAP R/3)

UseCommunication between SAP R/3 and SAP APO is based on the asynchronous transfer technique of queued Remote Function Calls (qRFC). This technique is used for the integration of SAP APO to the SAP R/3 system, concerning both the initial data supply and transfer of data changes (SAP R/3 SAP APO), as well as the publication of planning results (SAP APO SAP R/3). The data is:

buffered by the sending system and transferred to the target system in a second step (outbound queue), or

transferred by the sending system and buffered in the target system (inbound queue).

The qRFC Monitor is used to monitor application errors in outbound and inbound queues. It is available in both SAP R/3 and SAP APO.

It is used for:

displaying the current status of a queue, e.g. status or number of entries in a queue,

locking or unlocking specified queues.

Procedure1. Access the activity using one of the following navigation options:SAP R/3 Role Menu Displaying the qRFC MonitorTransaction Code CFQ1SAP Menu Logistics Central Functions Supply Chain Planning

Interface Core Interface Advanced Planner and Optimizer Monitoring qRFC Monitor

In the qRFC Monitor (outbound queue) screen, the total number of entries and queues displayed.

2. To see the details of any particular entry/queue, select or highlight it and choose Display Selection from the application toolbar.

3. To refresh or delete the entries or queues, choose the respective buttons from the application toolbar.



6.2.2 Displaying the CIF Application Log (SAP R/3)

UseThis transaction is used to view the CIF application log. The application log allows you to track the following information concerning the data transfer:

time/ date

which integration model and data objects were transferred

name of the user who last made changes

The application log provides a detailed error message for queues with errors. It can be accessed from both SAP APO and SAP R/3.

Prerequisites logging is activated

at least one integration model has been generated and activated

Procedure1. Access the activity using one of the following navigation option:

SAP R/3 Role Menu Displaying the CIF Application Log

Transaction Code CFG1

SAP Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log Display Entries

2. On the Evaluate Application Log screen, select the subobjects for the object CIF you want to display.

Use the possible entries option (F4) next to Subobject or, alternatively, use the wild card (x) to see the complete logs.

In the Time restriction screen area, define the date and time (from/to) in order to see more specific logs distinguished by user, transaction code, program, etc. in the Log triggered by screen area.

3. Choose Execute from the application toolbar.

On the Display Logs screen, you can navigate to the messages for each transfer log by double-clicking a subobject. This enables you to see what data objects were sent between the systems. This function is particularly useful for determining errors.

You can get further information about a message by selecting the log row and then choosing Detailed information or Technical information from the application toolbar.

The navigation tree contains information for navigating within the message set. It can have any number of levels. You can select a subset of messages in the tree by double-clicking it. The selected messages are displayed in a list below the application logs list in the same screen.



Colored icons in the application toolbar area distinguish the message types and the number of messages for each type. These icons or pushbuttons are represented with different shapes: octagon stop: for cancel, red rectangle: for error, yellow triangle: for warning, green circle: for information.

In the message list, you can see whether there is a long text (yellow question mark button next to the message text) or further detailed information available. Choose the question mark icon next to the message text to display detailed information in a new dialog box.

You can reduce the number of messages by choosing the respective message type pushbutton or icon from the application toolbar. For example, to hide all messages of the type Information, choose Information – Hide (green circle push button). Choosing this pushbutton again shows all messages of this type.

6.2.3 Deleting Entries in the Application Log (SAP R/3)

UseThe records in the application log are not automatically deleted by the system. To prevent the database from overflowing, it is recommended that you delete the records at regular intervals.

If required, you can also schedule a background processing job to carry out this task.


SAP R/3 Role Menu Deleting Entries in the Application Log

Transaction Code CFGD

SAP Menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log Delete Entries

2. On the Delete Application Log Entries screen, select the subobjects for the CIF object you want to delete and choose Delete from the application toolbar.

If you do not make any entries in the date and time fields, all records that are older than one week are automatically deleted.

3. On the Delete Application Log Entries screen, the following information is displayed:

number of deleted logs

number of undeleted logs

4. Go back.



6.3 Monitoring in APO

6.3.1 Checking the qRFC Monitor - Outbound Queue (SAP APO)

UseThe qRFC Monitor is a central monitoring tool in the SAP system for asynchronous data transfer when using the queued Remote Function Call (qRFC) between two SAP systems or between an SAP system and external systems.


It is used for:

displaying the current status of a queue (e.g. status or number of entries in a queue)

locking or unlocking specified queues


SAP APO Role Menu

Checking the qRFC Monitor - Outbound Queue (SAP APO)

Transaction Code SMQ1

SAP Menu Advanced Planning and Optimization APO Administration Integration Monitor QRFC Monitor (Output Queue).

2. In the qRFC Monitor (Outbound queue) screen, choose Execute.

The total number of entries and queues is displayed.

2. To see the details of any particular entry/queue, select it and choose Display Selection from the application toolbar.

3. To refresh and delete entries or queues, choose the respective buttons from the application toolbar.

6.3.2 Checking the qRFC Monitor – Inbound Queue (SAP APO)

UseThe qRFC Monitor is a central monitoring tool in the SAP system for asynchronous data transfer when using the queued Remote Function Call (qRFC) between two SAP systems or between an SAP system and external systems.




It is used for:

displaying the current status of a queue (e.g. status or number of entries in a queue)

locking or unlocking specified queues.


SAP APO Role Menu

Checking the qRFC Monitor – Inbound Queue (SAP APO)

Transaction Code SMQ2

SAP Menu Advanced Planning and Optimization APO Administration Integration Monitor QRFC Monitor (Input Queue).

2. In the qRFC Monitor (Inbound queue) screen, choose Execute.

The total number of entries and queues is displayed.

3. To see the details of any particular entry/queue, select it and choose Display Selection from the application toolbar.

4. To refresh and delete entries or queues, choose the respective buttons from the application toolbar.

6.3.3 Displaying the CIF Application Log (SAP APO)

UseThis activity is used to view the application log. You can analyze the logs and their messages, and get more information about them in the Display logs dialog box. The application log allows you to track the following information about data transfer:

time/ date

which integration model and data objects were transferred

name of the user who last made changes

The application log provides a detailed error message for queues with errors. It can be accessed from both SAP APO and SAP R/3.

Prerequisites logging is activated

at least one integration model is generated and activated.




SAP APO Role Menu Displaying the CIF Application Log (SAP APO)


SAP Menu Advanced Planning and Optimization APO Administration Integration Monitor Application Log Display Entries

2. On the Evaluate Application Log screen, select the subobjects for the CIF object you want to display.

You can use possible entries options (F4) next to Subobject or, alternatively, use the wild card (x) to see the complete logs.

In the Time restriction screen area, define the date and time (from/to) in order to see more specific logs distinguished by user, transaction code, program, etc. in the Log triggered by screen area.

3. Choose Execute from the application toolbar.

On the Display Logs screen, you can navigate to the messages for each transfer log by double-clicking a subobject. This enables you to see what data objects were sent between the systems. This function is particularly useful for determining errors.

You can get further information about a message by selecting the log row and then choosing Detailed information or Technical information from the application toolbar.

The navigation tree contains information for navigating in the message set. It can have any number of levels. You can select a subset of messages in the tree by double-clicking it. The selected messages are displayed in a list below the application logs list in the same screen.

Colored icons in the application toolbar area distinguish the message types and the number of messages for each type. These icons or pushbuttons are represented by different shapes: octagon stop: for cancel, red rectangle: for error, yellow triangle: for warning, green circle: for information.

In the message list, you can see whether there is a long text (yellow question mark button next to the message text) or further detailed information available. Choose the question mark icon next to the message text to display detailed information in a new dialog box.

You can reduce the number of messages by choosing the respective message type pushbutton or icon from the application toolbar. For example, to hide all messages of the type Information, choose Information – Hide (green circle push button). Choosing this pushbutton again shows all messages of this type.



6.3.4 Deleting Entries in the Application Log (SAP APO)

UseThe records in the application log are not automatically deleted by the system. To prevent the database from overflowing, it is recommended to delete the records at regular intervals.

If required, you can also schedule a background processing job to carry out this task.


SAP APO Role Menu Deleting Entries in the Application Log (SAP APO)


SAP Menu Advanced Planning and Optimization APO Administration Integration Monitor Application Log Delete Entries

2. On the Delete Application Log Entries screen, select the subobjects for the CIF object you want to delete and choose Delete from the application toolbar.

If you do not make any entries in the date and time fields, all records that are older than one week are automatically deleted.

On the Delete Application Log Entries screen, the following information is displayed:

number of deleted logs

number of undeleted logs.

6.4 Compare / Reconcile Function

UseThe following section describes how the compare/reconcile function supports the user in correcting data inconsistencies that might exist between SAP R/3 and the SAP APO system.

PrerequisitesActive integration models for the objects, which show inconsistencies, are already active.




SAP APORole Menu

Compare / Reconcile Function

Transaction Code /SAPAPO/CCR

APO Menu Advanced Planning and Optimization APO Administration Integration CIF Compare/Reconcile Function Execute Compare/Reconcile

2. On the CIF Compare/Reconcile Function screen, make the following entries:


Partner System Enter a logical name of the target R/3 system

Material (Product Name) Enter the materials, for which inconsistencies exist

Plant (Location Name) Enter the respective plants

Model Name Enter the name of the active integration model, where the inconsistent objects are included

3. In the Objects to be Checked screen area, select the inconsistent objects, for example planned orders, production orders, etc.

4. Choose Execute.

The results screen consists of at least one tab page summarizing the check results. If they indicate inconsistencies, for example in the planned orders, a separate Planned Orders tab page will be displayed.

5. Go to the tab page with the detailed error message. There is a list indicating exactly which planned orders are inconsistent. It is divided in two sections: one for the objects missing in SAP APO and one for the objects missing in SAP R/3.

6. For details on the reason that caused the inconsistency, choose the error code number.

If you are aware of the reason that caused the inconsistency, and want only to update the system, select all inconsistent items and choose Transfer to APO or Transfer to R/3.

7. The message Refresh was triggered for the selected objects is displayed.

8. Choose Iteration.

The results table is updated. Check whether the inconsistent objects have disappeared.

For additional information on the CIF compare reconcile function, go the respective chapter in the SAP APO online help.



7 Troubleshooting

UseThe following section provides some useful tips on frequently encountered issues.

PPM TransferYou want to initially transfer the PPMs or you want to perform a delta transfer. The transfer is not successful. For more information on the PPM transfer, including Tips & Tricks, read SAP note 448085.

Error During Transfer of LocationsDuring the transfer of locations (customers, vendors, etc.) from SAP R/3 to APO you may get the error message “location does not exist” or a similar message.

ProcedureTo correct the error, proceed as follows:

1. Run the report /sapapo/check_customizing in SAP APO. In the result screen, you can probably see some entries with red light, showing data inconsistencies.

2. Access the following transaction in both the SAP R/3 and the SAP APO system:

SPRO WebAS Basis Services Address Management Maintain Texts for Form of Address

3. Compare the entries of a table.

4. Add the missing entries in SAP APO.

5. Activate the integration model again.


B05_BB_ConfigGuide_EN_DE

Documents

wide naming

yellow arrow

building block

supply network

background

utilities

temporary

question mark