59
SAP SCM 4.1 June 2005 English Building Block B05 Replication SAP AG Neurottstr. 16 69190 Walldorf Building Block Configuration Guide

CIF Replication BB

Embed Size (px)

DESCRIPTION

CIF Replication BB

Citation preview

Page 1: CIF Replication BB

SAP SCM 4.1

June 2005

English

Building BlockB05 Replication

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

Page 2: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

Copyright

© Copyright 2005 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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C 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.

MaxDB is a trademark of MySQL AB, Sweden. 

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 informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 45

Page 3: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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.

© SAP AG Page 3 of 45

Page 4: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

Content

1 Preparation........................................................................................................................ 5

1.1 Prerequisites............................................................................................................5

2 Preliminary Steps...............................................................................................................5

2.1 SAP R/3: Preliminary Steps.....................................................................................5

2.2 SAP SCM: Preliminary Steps................................................................................12

3 Data Replication..............................................................................................................21

3.1 Activating the Application Indicator........................................................................21

3.2 Creating Integration Models (SAP R/3)..................................................................22

3.3 Checking Results and Creating Variants (SAP R/3)..............................................24

3.4 Activating Integration Models (SAP R/3)................................................................26

3.5 Changing Integration Models (SAP R/3)................................................................27

3.6 Maintaining Distribution Definition (SAP SCM)......................................................29

4 Additional Customizing for Replication............................................................................30

4.1 Deactivating the Customizing Import from SAP R/3 (SAP SCM)...........................30

5 Master Data Delta Transfer..............................................................................................31

5.1 Activating ALE Change Pointers............................................................................31

5.2 Delta Transfer of Material Masters, Customers and Suppliers..............................31

5.3 Delta Transfer of Production Data Structures........................................................33

5.4 Delta Transfer of Production Orders......................................................................34

6 Monitoring........................................................................................................................ 36

6.1 Setting up the qRFC Alert (Optional).....................................................................36

6.2 Monitoring in SAP R/3...........................................................................................37

6.3 Monitoring in SAP SCM.........................................................................................40

7 Troubleshooting...............................................................................................................45

© SAP AG Page 4 of 45

Page 5: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

1 PreparationMake 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 Prerequisites

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

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 SCM system.

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

SAP R/3 IMG menu SAP Customizing Implementation Guide Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for the Data Transfer Set User Parameters

Transaction code CFC2

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 entry 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.

© SAP AG Page 5 of 45

Page 6: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

To avoid performance problems, we recommend that you 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 have finished.

2.1.2 Changing the MRP Type (SAP R/3)

UseIn this important step, you define which of your materials are to be planned in the SAP SCM system and not in SAP R/3, which means they are excluded from planning in the SAP R/3 system. To achieve this, you need to change the MRP type of the materials you want to plan in SAP SCM. 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.

Consider carefully which materials to select.

If you want to implement this step using mass maintenance, refer to the next section.

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

SAP R/3 menu Logistics Materials Management Material Master Material Change Immediately

Transaction code MM02

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 SCM system.

© SAP AG Page 6 of 45

Page 7: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

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

Be careful when using the mass maintenance transaction. You may inadvertently change more materials than intended by specifying an incorrect range.

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

SAP R/3 menu Logistics Materials Management Material Master Material Mass Maintenance

Transaction code MM17

2. Confirm the information prompt.

3. On the Mass Maintenance: Materials (Industry) screen, on the Tables tab page, select the following line:

Short Description Table Name

Plant Data for Material MARC

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

Description Fld Name

MRP Type MARC-DISMM

5. Choose Execute.

6. Confirm the warning message.

7. 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

8. Choose Execute.

9. 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.

10. In the New Values screen area, select the MRP type X0 - W/O MRP, with BOM Explosion for the materials you have selected.

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

© SAP AG Page 7 of 45

Page 8: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

You can undo changes by selecting Undo Changes.

12. Choose Save and confirm the warning message.

13. Check the message text in the Mass Main. Status tab page.

14. Choose Back four times.

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

UseSAP R/3 does not differentiate between production plants and distribution centers. In SAP SCM, however, these locations are distinguished by the location type. Moreover, different settings apply to them, for example, production is not possible in a distribution center. For successful data transfer, you need to 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 IMG menu SAP Customizing Implementation Guide Production Distribution Resource Planning (DRP) Basic Settings Maintain assignment of node type - plant

Transaction code SPRO

2. Choose the activity 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. If the Choose Activity dialog box is displayed, choose Cancel and go back.

© SAP AG Page 8 of 45

Page 9: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

Use

The procurement type defines how a material is procured, for example, by external procurement or by in-house production. This activity ensures that the correct procurement type is maintained for locations of the type Distribution Center. In a distribution center, the material is procured externally, for example, from a production plant. All location products that can be found in a distribution center should have the procurement type “F” for external procurement.

If the SAP Best Practices for SCM scenario you are installing does not include distribution centers, skip this activity.

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

SAP R/3 menu Logistics Materials Management Material Master Material Change Immediately

Transaction code MM02

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

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

4. In the Organizational Levels dialog box, enter the name of the distribution center and choose Enter.

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

6. Save and go back.

7. Repeat the procedure for all materials to be planned in the SAP SCM system.

You can also perform these changes using mass maintenance. To do this, open transaction MM17, choose Plant Data for Material (table MARC) from the Tables tab and the following field from the Fields tab: MARC-BESKZ. For a detailed description on working with the mass maintenance transaction, refer to the section Changing MRP Type using Mass Maintenance in this document.Be careful when working with the mass maintenance transaction.

© SAP AG Page 9 of 45

Page 10: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

UseThe purchasing group is a buyer or a group of buyers, who are responsible for certain purchasing activities. In order to create purchase requisitions in SAP SCM for externally procured materials and to transfer them to SAP R/3, make sure that a purchasing group has been assigned in your material master.

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

SAP R/3 menu Logistics Materials Management Material Master Material Change Immediately

Transaction code MM02

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

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 screen area, assign an existing Purchasing Group.

6. Save and go back.

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

You can also perform these changes using mass maintenance. To do this, open transaction MM17, choose table MARC from the Tables tab and following field from the Fields tab: MARC-EKGRP. For a detailed description on working with the mass maintenance transaction, refer to the section Changing MRP Type using Mass Maintenance in this document.Be careful when working with the mass maintenance transaction.

© SAP AG Page 10 of 45

Page 11: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 SCM.

The purpose of this activity is to determine which resource types are assigned to the resources created in SAP SCM during the initial transfer of capacities from SAP R/3. By default, capacities are mapped to single-activity resources or multi-activity resources in SAP SCM and can be used only in Production Planning and Detailed Scheduling (PP/DS). In order to use resources for PP/DS and SNP, the resource type single-mixed and multi-mixed resources must be applied.

Note that you cannot change the resource type in SAP SCM.

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

SAP R/3 IMG menu SAP Customizing Implementation Guide 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

Transaction code SPRO

2. On the 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 Multimixed resource

3. Choose Save.

4. Choose or create a customizing request.

5. Go back.

© SAP AG Page 11 of 45

Page 12: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

2.2 SAP SCM: Preliminary Steps

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

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

The customizing import from SAP R/3 to SAP SCM 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 transfer customizing data only once. Otherwise, existing settings could be overwritten.

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

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

Transaction code SPRO

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

Field Value Comments

TQA (Temporary quantity assignment) X Select

Import Customizing Allowed Select from Possible Entries

3. Choose Save. If a system prompt appears, choose or create a customizing request.

4. Go back.

© SAP AG Page 12 of 45

Page 13: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

2.2.2 Maintaining Units of Measurement (SAP SCM)

UseCarry out this activity only if the SAP R/3 data, which has to be transferred to SAP SCM, requires additional units of measure that are not included in the SAP standard. If you have defined additional units of measure in your SAP R/3 system, you need to define these in SAP SCM, as well.

We recommend that you check whether the unit “PC” is maintained in your SAP SCM system.

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

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

Transaction code CUNI

2. On the Units of Measurement: Initial Screen, choose Units of measurement. The Change Unit of Measurement of Dimension screen appears. Check whether the table lists all units of measurement that you need by comparing this table with the corresponding table in your SAP R/3 system.

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

3. To add a new unit of measurement, choose Create from the application toolbar. Maintain all fields in accordance with the corresponding Customizing settings in your SAP R/3 system.

4. Save your entries.

5. Enter a customizing request and go back.

6. Repeat this step for all additional units of measurement required.

© SAP AG Page 13 of 45

Page 14: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

2.2.3 Checking / Maintaining Forms of Address (SAP SCM)

UseYou have to check if some standard address data (the so-called “forms of address”) which are available in the SAP R/3 system, are also maintained in SAP SCM. If not, you need to create all relevant forms of address in SAP SCM customizing before you start the data replication.

You can check the forms of address in the SAP R/3 system using the following R/3 IMG path: SAP Customizing Implementation Guide SAP Netweaver SAP Web Application Server Basis Services Address Management Forms of Address and Name Components Maintain Forms of Address.

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

SAP SCM IMG menu mySAP SCM - Implementation Guide SAP Web Application Server Basis Services Address Management Forms of Address and Name Components Maintain Forms of Address

Transaction code SPRO

2. In the Change View "Titles (Business Address Services)": Overview screen, choose New entries and make the necessary entries.

3. Save your entries and go back.

2.2.4 Maintaining Planners (MRP Controllers) (SAP SCM)

UseThe MRP controller in R/3 corresponds to the planner in SAP SCM. As the customizing data of MRP controllers/planners is not automatically transferred via the APO Core Interface from SAP R/3 to SAP SCM, you need to create all relevant planners in SAP SCM customizing manually before you can start the data replication.

To do this, you create planners in SAP SCM using their planner key from SAP R/3 and assign planning privileges to them. You need to select one or more SCM applications for which each planner is to be responsible.

However, you do not need to reassign the materials to the planners for which they are responsible because existing assignments of MRP controllers to a material are transferred to SAP SCM during the data replication with the material master.

You can check the MRP controllers in the SAP R/3 system by using the following R/3 IMG path: SAP Customizing Implementation Guide Production Material Requirements Planning Master Data Define MRP Controllers.

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

© SAP AG Page 14 of 45

Page 15: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

SAP SCM IMG menu mySAP SCM – Implementation Guide Advanced Planning and Optimization Supply Chain PlanningSpecify the Person (Planner) Responsible

Transaction code SPRO

2. In the Change View “Person responsible for a material ….)”: Details screen, choose New entries and specify the key of the relevant MRP controller from SAP R/3 and assign the required planning areas to the planner, as in the following example:

Planner Prod.plnnr SNP plnnr DemandPlnr TransPlnnr Name

001 X X X Planner 001

3. If necessary, repeat the previous step to create more planners.

4. Save your entries and go back.

2.2.5 Defining the Transportation Group (SAP SCM)

UseThe transportation group is an identifier that groups important transportation-specific attributes of a product. Each product is assigned to a transportation group.

An example for product attributes could be “refrigerated transportation required” or “dangerous goods”.

The assignment of a transportation group to a material is transferred to SAP SCM via CIF with the material master. The customizing for defining the transportation groups, however, is not transferred. Therefore, you need to create all relevant transportation groups in SAP SCM 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.

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

SAP SCM IMG menu mySAP SCM – Implementation Guide Advanced Planning and Optimization Transportation Planning and Vehicle Scheduling Basic Settings Maintain Transportation Group

Transaction code SPRO

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.

© SAP AG Page 15 of 45

Page 16: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

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

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

3. In the Select View(s) dialog box, select Sales: General/PlantData 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 area, select the transportation group (Trans. Grp) and make changes if necessary.

6. Save your entries.

2.2.6 User Settings and Activating the CIF Application Log (SAP SCM)

UseWith this step, you maintain some global parameters for the SAP SCM 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.

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

SAP SCM menuAdvanced Planning and Optimization APO Administration Integration Settings User Settings

Transaction code /N/SAPAPO/C4

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

* 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.

© SAP AG Page 16 of 45

Page 17: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

2.2.7 Defining Class System (SAP SCM)

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

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

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

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

Variant Configuration can be used in Make-To-Order scenarios for mass production, for example in the automobile industry. It is also applicable when working with configurable products. This setting allows you to perform the characteristics-based planning on the basis of the R/3 characteristic and class system. You do not need to maintain the object dependencies in SAP SCM once again. 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 SCM system.

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

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

SAP SCM IMG menu mySAP SCM Implementation Guide Advanced Planning and Optimization (APO) Basis Settings Define Configuration Relevance (CDP or Variant Configuration)

Transaction code SPRO

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

Field Value

Settings CDP or Variant Configuration

3. Save your entries and go back.

© SAP AG Page 17 of 45

Page 18: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

2.2.8 Installing General User Exit (SAP SCM)

UseCustomers, suppliers, production plants, distribution centers, etc. from SAP R/3 are all defined as locations, that is, as one category in the SAP SCM system. As a consequence, you have to rename locations in the SAP SCM system to prevent a customer and a production plant number from having the same location number in SAP SCM. 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 SCM.

The following three situations deal with three different source codes for the user exit (this section uses SAP 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 especially occurs with vendor and customer numbers.

2. There are identical location identifiers in different external systems. In this case, you need to verify whether the locations in the different systems are identical or not. The proposed source code only deals 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.

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.

Procedure

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

SAP SCM menu Tools ABAP Workbench Utilities Enhancements Project Management

Transaction code CMOD

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

© SAP AG Page 18 of 45

Page 19: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 choose a name for your project 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 the Enhancement assignments radio button and choose Change.

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

Enhancement APOCF001

10. Choose Save and go back.

11. Select the Components radio button and choose Display. In the Display U02B0501 screen, verify that the name of the project is correct.

12. Double-click the function exit: EXIT_/SAPAPO/SAPLCIF_LOC_001. The Function Builder screen appears.

13. On the Source code tab page, scroll down to the bottom of the screen and double-click the line Include ZXCIFUSERU06.If a warning message appears, choose Enter to continue.

14. The Create object dialog box appears. 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 described in the Use section above.

cifloc2.txt: for situation 2described in the Use section above.

cifloc3.txt for situation 3 described in the Use section above.

© SAP AG Page 19 of 45

Page 20: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

Make sure that all lines containing comments, which starts with an asterisk “*” are colored blue 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 PL1000/SS8CLNT224 in SAP APO, where “SS8” is the system name and “224” the client name. Note that the character “@” is not used when renaming the plant because SAP SCM-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.

© SAP AG Page 20 of 45

Page 21: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

3 Data ReplicationDuring data replication, the master data from the SAP R/3 system is transferred to the SAP SCM system and a reciprocal system connection is activated.

The data replication is carried out by means of different integration models that define the data types and data volume for the replication. The following section describes how you create and activate integration models. Integration models are not only used for transferring master data from SAP R/3 to SAP SCM, but also enable the transfer of transaction data between both systems.

Note that you run the risk of overwriting changes to master data and Customizing settings that were made in SAP APO

if you create and activate a new integration model that contains the same objects (e.g. product master data; or ATP settings) as other integration models that were activated before

If you activate an existing integration model again.

Therefore, always compare a new integration model with an existing integration model that may contain similar data and make sure that the changes made in APO after the activation of the first integration model are not overwritten.

3.1 Activating the Application Indicator

Use Before you start the data replication, you need to make sure that the business transaction events are active in SAP R/3. Only if these events are active for the SAP SCM integration, will changes to the transaction data be transferred from SAP R/3 to SAP SCM. This setting should have already been made by your system administrator, but we recommend that you check these settings in order to avoid possible problems later on.

Procedure1. To access the activity, use the following navigation option:

SAP R/3 transaction code BF11

2. Confirm the message The table is cross client.

3. On the Change View: Application Indicator”: Overview screen, check whether the applications ND-APO and NDI are active, i.e. selected. If they are inactive, select the indicators to activate them.

4. Choose Save and go back.

© SAP AG Page 21 of 45

Page 22: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

3.2 Creating Integration Models (SAP R/3)

UseIn this activity, you define the range of master and transaction data to be transferred. We recommend that you create different integration models for master and transaction data (refer to the scenario installation guide for the recommended number of models for a specific scenario). This does not only improve the performance, but also helps to identify any errors that may occur during data transfer.

For each integration model, carry out all steps of the following two activities before you create the next integration model:

Creating Integration Models

Saving Results and Creating Variants

As each scenario needs different integration models, the following section provides a generic description of how to create integration models, but no specific information for individual integration models. You can find specific integration model data for the scenario you are installing in the section Data Replication in the corresponding scenario installation guide. Go through the following activities using both this configuration guide and the scenario installation guide.

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. Refer to the scenario installation guide to find out how many integration models your scenario requires.

3.2.1 Defining the Integration Model

Only the data you define in your integration models will be transferred. Incomplete data may cause errors during data transfer or the run of a process in the SAP SCM system.

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

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

Transaction code CFM1

2. The Create Integration Model screen appears. It contains three major sections:

Material Dependent Objects

General Selection Options for Materials

Material Independent Objects.

3. Refer to the section Building Block Replication in the scenario installation guide to find the specific integration model data. Specify the following values for the integration model according to the information in the scenario installation guide:

© SAP AG Page 22 of 45

Page 23: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

Field name User action and values Default values

Model Name Specify a unique 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 SCM application

e.g. MASTERDATA or TRANS_DATA

4. Select all Material Dependent Objects as specified for the model in the scenario installation guide. If there are no material-dependent objects for an integration model, proceed with step 8 (material-independent objects).

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

Field name User action and values Comments

Material To define the range of materials (for which the material dependent objects should be transferred ) 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 without production planning processes (for example: VMI or Order Fulfillment) continue with step 8.

6. Select the PDS R/3 indicator and choose the yellow arrow button next to it. Another screen area with additional data entry fields appear. Make the following entries:

Field name User action and values

PDS Type PP/DS (select)

Production Version Enter a production version of the product

Rep.mfg The default value Detailed Planning to Rate-based Plng should only be changed if it corresponds to your requirements

7. If you have phantom products in your BOM, you can also transfer them with the PDS object. Select the BOM indicator and choose the yellow arrow button next to it. Another screen area with additional data entry fields appear. Make the following entries:

Field name User action and values

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

Alternative Enter the alternative ID of the BOM

© SAP AG Page 23 of 45

Page 24: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

8. 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.

9. Refer to the scenario installation guide and select the Material Independent Objects according to the integration model.

10. 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 material independent objects you have already selected.

Note: By definition, the section General Selection Option for Materials does not apply to the material independent object.

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.

11. Do not save your entries for this integration model but go to the next activity to check the consistency of the model and to create a variant.

ResultYou have defined an integration model. Continue with the next activity in this document (Checking results and creating variants) before you create the next integration model.

3.3 Checking Results and Creating Variants (SAP R/3)1. After you have defined all objects that you want to include in the integration model,

choose Execute in the Create Integration Model screen 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 clicking on it and 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 and go back.

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

As a result of the consistency check of the integration models for transaction you may receive warning messages such as “material is not included in the integration model”. You can ignore these messages if the material master data has already been included in a previous model.

5. Save your selection.

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

© SAP AG Page 24 of 45

Page 25: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 –Variant Attributes screen, enter a name and a description for your variant and choose Save.

10. Go back to the previous activity (Create Integration Model) to create another integration model, if necessary. If you have created, saved and checked all integration models for your scenario, proceed with the next activity.

ResultYou have saved and checked the consistency of the integration model you have created.

If you have completed all integration models of your scenario, you can activate them according to the next procedure.

© SAP AG Page 25 of 45

Page 26: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

3.4 Activating Integration Models (SAP R/3)

UseWhen you have created the integration models containing the data you want to transfer to SAP SCM, you need to activate them to trigger the initial data transfer from SAP R/3 to SAP SCM.

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

ProcedureNote that you need to activate the integration models in the same sequence they were created in.

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

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

Transaction code CFM2

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 select 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 of their creation date and time. They may also be assigned to different logical systems (target systems) and SAP SCM applications.

3. Choose Execute.

You can carry out a consistency check between this one, and other, already activated integration models. 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. To activate an integration model, double-click the creation date of the model you want to activate. As an alternative, you can click the date and choose Set to active/inactive from the application toolbar.A green checkmark before the creation date of the model indicates that the integration model is active.

To deactivate an active model, double-click the date of the model or choose Set to active/inactive from the application toolbar.A red cross before the model indicates that the model is inactive.

5. To trigger the data replication to the target system (SAP SCM), choose Start.

© SAP AG Page 26 of 45

Page 27: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

6. If the CIF_Load prompt appears, asking you “Should the interval be created”, choose Yes.

7. If the following Application Log prompt appears, choose

a. No, if you do not want to branch to the application log.

b. Yes, to display the CIF Application log including a list of the objects that were transferred appears. Go back.

8. Confirm the information message “Activation or deactivation of the selected models is complete”.

3.5 Changing Integration Models (SAP R/3)

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

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/3 menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Create

Transaction code CFM1

2. On the Create Integration Model screen, choose Goto Variants Get Variant from the menu bar.

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.

6. Choose Save and go back.

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 AG Page 27 of 45

Page 28: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

Transaction code CFM2

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 at the same time.

6. Go back.

Result The changes included in the changed integration model have now been transferred to SAP SCM.

© SAP AG Page 28 of 45

Page 29: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

3.6 Maintaining Distribution Definition (SAP SCM)

UseThe following procedure describes how to distribute the planning results from SAP SCM 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.

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

SAP SCM IMG menu mySAP SCM – Implementation Guide Integration with SAP Components Integration of SAP SCM and SAP R/3 Basic Settings for Data Transfer Publication Maintain Distribution Definition

Transaction code /N/SAPAPO/CP1

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, choose New entries and make the entries in the table as required for your scenario. Refer to the scenario installation guide for specific values:

Publication Type Location No. Logical System

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

4. Choose Enter. The SAP Rel. column is filled automatically.

5. Save your entries and go back.

© SAP AG Page 29 of 45

Page 30: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

4 Additional Customizing for Replication

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

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

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

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

SAP SCM 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

Transaction code SPRO

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

2. To deactivate the import of customizing make the following settings:

Field Value Comments

TQA (Temporary quantity assignment)

XSelect

IC (Import Customizing) Not Allowed Select using Possible Entries (F4)

3. Choose Save and go back.

ResultYou have completed all activities related to the initial data transfer from the SAP R/3 system to SAP SCM. Go back to the Scenario Installation Guide and proceed with the installation of the next building block.

© SAP AG Page 30 of 45

Page 31: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

5 Master Data Delta Transfer

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

The activities for transferring changed or additional master data are usually not relevant for the initial data transfer and can therefore be omitted at this stage.

PrerequisitesThe initial data transfer has already been performed. This means, that the objects to be transferred, for example, material master or PDS 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.

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

SAP R/3 IMG menu

SAP Customizing Implementation Guide 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

Transaction code SPRO

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

3. Choose Save and go back.

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 SCM automatically. This section describes which settings are required for enabling a delta data transfer for material masters, customers and suppliers.

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

© SAP AG Page 31 of 45

Page 32: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

5.2.1 Configuring Change Transfer Before Changing the Master Data

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

SAP R/3 IMG menu SAP Customizing Implementation Guide Integration with other mySAP.com Components Advanced Planning and Optimization Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data -> Configure Change Transfer for Master Data

Transaction code CFC9

2. In the Change Transfer for Master Data screen area, select 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.

Field name User action and values

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 this, go to the Initial Data Transfer and Change Transfer for Resource screen area.

3. Choose Save and exit the transaction.

5.2.2 Transferring the Master Data Changes1. To access the activity, 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 SCM system is correct.

© SAP AG Page 32 of 45

Page 33: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 SCM.

4. Choose Execute.

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 Production Data Structures

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

PrerequisitesAn active integration model with production data structures (PDS) is available.

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

SAP R/3 menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner & Optimizer Integration Model Change Transfer Production Data Structure (PDS) Transfer Production Data Structure (PDS)

Transaction code CURTO_Create

2. On the Transfer of Production Data Structures to SAP APO screen, make the following entries:

Field name User action and values

Logical system Enter an APO logical system number

PL Version in APO Enter the version “000”

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

Plant Enter a production plant

Production Version Enter a production version number

Rate-Based Planning Select this radio button you use rate-based planning

Change Transfer By setting this indicator, you specify that only those production data structures are transferred to SAP SCM for which a master data change has been made since the last transfer.

3. Choose Execute.

Result The production data structures in APO are updated using the current information.

© SAP AG Page 33 of 45

Page 34: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

5.4 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 SCM.

PrerequisitesAn active integration model for production orders is available.

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

Delete operation

Include component

Changes to the duration of an operation will not be transferred to SAP SCM, because SAP SCM 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.

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

SAP R/3 IMG menu

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

Transaction code OPU3

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

5. Choose Save and go back.

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 SCM. This is required if this operation does not exist in SAP SCM.

© SAP AG Page 34 of 45

Page 35: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

SAP SCM IMG menu mySAP SCM – Implementation Guide Integration with SAP Components Integration of SAP SCM and SAP R/3 Basic Settings for Data Transfer Publication Maintain Object-Specific Settings

Transaction code /N/SAPAPO/CP3

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 In-house production

Retransfer Only retransfer after online transfer

4. Choose Save and go back.

© SAP AG Page 35 of 45

Page 36: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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) are to be informed in what way about errors occurring during the data transfer. This way, no time is wasted and the user can quickly respond to any unusual situations.

The activities for setting up the qRFC Alert are optional and not essential for the installation of your business scenario and the initial data transfer. You can therefore omit this section if you do not want to use the monitoring functions described hereafter.

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

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

SAP SCM menu Advanced Planning and Optimization APO Administration Integration Monitor qRFC Alert (Outbound Queues)

Transaction code /N/SAPAPO/CW

If you are working with inbound queues, you must open transaction /N/SAPAPO/CQINW.

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

Field name User action and values

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 SCM.

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 SCM system, e.g. AS7CLNT001

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

© SAP AG Page 36 of 45

Page 37: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

6.2 Monitoring in SAP R/3

6.2.1 Displaying the qRFC Monitor (SAP R/3)

UseCommunication between SAP R/3 and SAP SCM is based on the asynchronous transfer technique of queued Remote Function Calls (qRFC). This technique is used for the integration of SAP SCM to the SAP R/3 system, concerning both the initial data supply and transfer of data changes (SAP R/3 SAP SCM), as well as the publication of planning results (SAP SCM 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 SCM.

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 menuLogistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring qRFC Monitor

Transaction code CFQ1

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.

© SAP AG Page 37 of 45

Page 38: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 SCM 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 menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log Display Entries

Transaction code CFG1

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

Use Possible Entries <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 sub object. 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:

© SAP AG Page 38 of 45

Page 39: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

octagonal 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 icon 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.

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

SAP R/3 menu Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log Delete Entries

Transaction code CFGD

2. On the Delete Application Log Entries screen, select the sub objects 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.

© SAP AG Page 39 of 45

Page 40: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

6.3 Monitoring in SAP SCM

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

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.

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

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 SCM menu Advanced Planning and Optimization APO Administration Integration Monitor QRFC Monitor (Output Queue).

Transaction code SMQ1

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 options from the application toolbar.

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

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.

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

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 AG Page 40 of 45

Page 41: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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

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

Transaction code SMQ2

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 options from the application toolbar.

6.3.3 Displaying the CIF Application Log (SAP SCM)

UseThis activity is used to view the application log. You can analyze the logs and their messages, and obtain 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 SCM and SAP R/3.

Prerequisites Logging is activated

At least one integration model is generated and activated.

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

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

Transaction code /N/SAPAPO/C3

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

You can use Possible Entries <4> next to Subobject or, alternatively, use the wild card ( ) to see the all 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.

© SAP AG Page 41 of 45

Page 42: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 sub object. This enables you to see what data objects were sent between the systems. This function is particularly useful for determining errors.

For further information about a message, select the log row and choose 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 icon 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 option again shows all messages of this type.

6.3.4 Deleting Entries in the Application Log (SAP SCM)

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.

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

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

Transaction code /N/SAPAPO/C6

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

© SAP AG Page 42 of 45

Page 43: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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.3.5 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 SCM system.

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

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

SAP SCM menu Advanced Planning and Optimization APO Administration Integration CIF Compare/Reconcile Function Execute Compare/Reconcile

Transaction code /N/SAPAPO/CCR

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

Field name User action and values

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 SCM and one for the objects missing in SAP R/3.

© SAP AG Page 43 of 45

Page 44: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

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 SCM online help.

© SAP AG Page 44 of 45

Page 45: CIF Replication BB

SAP Best Practices Building Block B05 Replication: Configuration Guide

7 Troubleshooting

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

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.

7.1.1.1.2 ProcedureTo correct the error, proceed as follows:

1. Run the report /sapapo/check_customizing in SAP SCM. 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 SCM 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 SCM.

5. Activate the integration model again.

© SAP AG Page 45 of 45