SCM210-CoreInterface with SCM.pdf

(1)

SCM210

Core Interface SAP SCM

mySAP Supply Chain Management

Date Training Center Instructors Education Website

Participant Handbook

Course Version: 2004 Q3

Course Duration: 2 Day(s) Material Number: 50069930

(2)

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.

Trademarks

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

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. • ORACLE® is a registered trademark of ORACLE Corporation.

• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

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

• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING

WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,

INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

(3)

About This Handbook

This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following typographic conventions are also used.

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.

Also used for cross-references to other documentation both internal (in this

documentation) and external (in other locations, such as SAPNet).

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.

(4)

Type Style Description

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text _{Exact user entry. These are words and 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.

Icons in Body Text

The following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor’s presentation.

(5)

Course Overview

This course is designed to instuctor consultants and super users on the inner workings of the Core Interface. You will be instructed on the necessary steps to connect the landscape as well as the congfiguration necessary to transfer master data initially and any changes from SAP R/3 to SAP SCM. In addition you will be introduced to the steps required to transfer transactional data from SAP R/3 to SAP SCM and back.

Target Audience

This course is intended for the following audiences:

• Customers, Implementation Partners and SAP Consultants

Course Prerequisites

Required Knowledge

• Basic knowledge of SAP R/3 Master Data Recommended Knowledge

• Basic knowledge of Material Masters, Bills of Materials, Routings, Work Centers and Location data.

• Basic understanding of supply chain planning concepts.

Course Goals

This course will prepare you to:

• Understand the steps and tools to integrate an SAP SCM system with a SAP R/3 system to enable intensive supply chain modeling and planning

Course Objectives

After completing this course, you will be able to:

• Identify the necessary steps to setup integration between and SAP R/3 system and an SAP SCM (APO) system

(8)

• Identify the tools necessary to initiate and monitor the continuous transfer for master data and transactional data between and SAP R/3 and an SAP SCM system.

• Transfer master data from SAP R/3 to SAP SCM and familiarize yourself with the results.

• Review the master data modeling structure in SAP SCM

• Review the steps of transactional data integration and transfer planning results from SAP SCM to SAP R/3.

SAP Software Component Information

The information in this course pertains to the following SAP Software Components and releases:

(9)

Unit 1

Integration in SAP SCM

Unit Overview

In this unit you will be instructed on the details of setting up integration between SAP R/3 and SAP SCM. This will include linking the two systems and demonstrating intial integration configuration. Users will setup integration models to initally transfer master data, and review the steps necessary to initiate a change or “delta” tansfer. Lastly, users will be instructed on various tools that can be used to monitor and correct any data transfer issues.

Unit Objectives

After completing this unit, you will be able to:

• Explain the basic concept of integrating SAP SCM to a OLTP (On-line Transaction Processing System) system.

• Give a basic explanation as to how SAP R/3 and SAP SCM systems integrate.

• Explain the basic steps to integrate an SAP R/3 and an SAP SCM System • Demonstrate the need or use of RFC connections between SAP R/3 and

SAP SCM systems

• Explain the use of Inbound and Outbound queues when integrating SAP R/3 and SAP SCM.

• Explain the purpose of Business system groups in integration SAP SCM with one or more OLTP systems.

•

• Create integration models for transfer of transactional data using SAP recommended selection methods.

• Activate integration models for transfer of transactional data. • Describe the data transfer process, and how errors are recorded • Demonstrate the qRFC Monitor and explain its purpose in handling

(10)

• Demonstrate the Application Log and explain its purpose n handling transfer errors

• Demonstrate the SCM Queue Manager and explain its purpose in handling transfer errors

• Demonstrate the qRFC Alert and explain its purpose in handling transfer errors

• Explain the differences between the Post Processing and the previously mentioned tools.

• Demonstrate the Compare/Reconcile functionality and explain its purpose in handling transfer errors

• Explain how new SAP SCM relevant data is transfer automatically from SAP R/3 via existing integration models

• Explain how changes in SAP R/3 to existing integrated data, will be transfer to SAP SCM via the CIF.

• Organize integration models according to SAP recommendations.

Unit Contents

Lesson: Overview of Integrating SAP R/3 and SAP SCM... 3

Lesson: Technical integration of SAP R/3 and SAP SCM ... 8

Procedure: Defining Flexible RFC Destinations... 15

Procedure: Business System Groups ... 23

Exercise 1: Architecture of Integration... 25

Lesson: Generating and Activating Integration Models... 30

Exercise 2: Transfer of Master Data ... 37

Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM... 46

Procedure: Monitoring transfer errors with the qRFC monitor... 52

Procedure: Application Log for Error Processing ... 55

Procedure: Monitoring transfer errors with the SCM Queue Manager ... 57

Procedure: Managing transfer errors with the qRFC Alert ... 59

Procedure: Compare/Reconcile Report ... 67

Lesson: Incremental Transfers for Master Data Changes... 69

Procedure: Setting Background jobs for Master Data Transfer ... 72

(11)

SCM210 Lesson: Overview of Integrating SAP R/3 and SAP SCM

Lesson: Overview of Integrating SAP R/3 and SAP SCM

Lesson Overview

This unit discusses the integration methods between and SAP SCM system and one or more Online Transaction Processing Systems (OLTP)

Lesson Objectives

After completing this lesson, you will be able to:

Business Example

Your organization currently uses SAP R/3 for planning and has acquired SAP SCM for more intensive supply chain modeling and planning. You need to have a general understand for how these two separate systems will integrate to allow your company to leverage its SAP SCM investment for supply chain modeling/planning.

Integrating SAP SCM to a On-line Transaction Processing

System (OLTP)

As you should already be aware SAP has divided supply chain planning and execution into two discinct functions and has created two distinct software packages, one to handle execution (SAP R/3) and another to handle advanced planning (SAP SCM). These two systems have been developed separately, therefore they have two separated data bases for both transactional data and master data. However, in order for any business to function properly, these two systems need to act as one. In order to ensure that businesses can function in a real time environment, SAP has developed software that will allow the two systems to interact seamlessly in real time. The software that integrates SAP R/3 with SAP SCM is called the Core Interface (CIF)

(12)

Figure 1: Core Interface

The Core Interface (CIF) is responsible for the data exchange between SAP R/3 and SAP SCM Systems. The CIF is a real-time interface that links SAP SCM with one or several SAP R/3 Systems. Only the data objects needed in the data structures in SAP SCM for the different planning and optimization processes are transferred from the complex data set of the SAP R/3 system into SAP SCM. The Core Interface guarantees both the initial data transfer (initial transfer) and also the transfer of data changes within SAP SCM. The integration of SAP R/3 with the CIF interface is possible as of release 3.1I. Earlier releases or an R/2 System can be connected with BAPIs as "Non-SAP R/3 Systems". (BAPI = Business Application Programming Interface).

Integrating SAP R/3 to SAP SCM

Once a customer has purchased one of SAP’s “mySAP” products (SAP SCM, SAP BW, SAP CRM, etc....), a software component called the SAP R/3 Plug-in must be installed if your SAP R/3 system is to integrate with any of the SAP Extension products. The Plug-in software will enable businesses to integrate a mySAP component (for example, SAP SCM or SAP BW) with one or several SAP R/3 Systems. With the SAP R/3 Plug-in, several mySAP components can be inserted at the same time. Most Plug-ins concern add-ons (SAP R/3 standard software enhancements with additional functions). Different mySAP components can be supplied with transaction and master data from the SAP R/3 Plug-in. In this way, the CIF interface not only provides the SAP SCM system with initial data records (initial supply), it also guarantees a step-by-step supply with all the relevant data changes. In the case that

(13)

the BW within SAP SCM needs to be integrated with your SAP R/3 system,

Extractors are provided by the plug-in to support data transfer of master

data and transactional data.

Figure 2: SAP R/3 Plug-In Technology

The integration between SAP R/3 and SAP SCM is possible as of release 3.1I. For earlier releases, R/2 or non-SAP products standard BAPIs exist, and can be found by executing transaction BAPI in SAP SCM. However, the necessary code will have to be written to link the transaction in the execution system to the SAP SCM transaction.

One area of the CIF that users will become very familiar with is the integration model. Integration models will be the mechanism that users will choose specifically which master data and transactional data needs to pass between the two systems. Planners will be responsible for determining when new master data is created, whether it is SAP SCM relevant data, and therefore, should be included in an integration model.

(14)

Figure 3: Integration Models and the CIF

Users will typically set up multiple integration models depending how they have arranged for the data to be transferred in large quantities. Integration models are created in SAP R/3 with a specific SAP SCM system as it’s

destination or target. SAP has provided some rough guidelines that will assist companies in creating and monitoring the data transfer. Integration models will be used to perform both the initial data loads and delta updates.

Initial Load

The first time specific master data or transactional data is set to the recieving SAP SCM system.

Delta Updates

As more SAP SCM relevant data is created, periodic background jobs will be run, to re-create the existing integration models allowing for new master data to be sent to SAP SCM or terminating integration for obsolete master data.

For easy integration from SAP R/3 to SAP SCM, it is necessary to install the Plug-in relevant to the SAP R/3 release that your company is using. As of 2003, Plug-ins are released once a year pertaining to new functionality. Also note that support packages are delivered periodically for the plug-ins. For more information regarding how the plug-in might affect your implementation go to:

(15)

Lesson Summary

You should now be able to:

(16)

Lesson: Technical integration of SAP R/3 and SAP SCM

Lesson Overview

This lesson will describe the initial steps to setting up your SAP R/3 system to integrate with your SAP SCM system.

Lesson Objectives

SAP SCM systems

•

Business Example

Your organization currently uses SAP R/3 for planning and has acquired SAP SCM for more intensive supply chain modeling and planning. You need to understand some of necessary technical settings for connecting these two separate systems to enable your company to leverage its SAP SCM investment for supply chain modeling/planning.

Overview of Setting up integration

The first steps in integrating SAP R/3 and SAP SCM will typically be done by our Basis implementation team. Several of these settings are relevant for more than just integrating with SAP SCM. They are part of the fundamental implementation and upgrade methodology that is outlined by SAP. The majority of these settings are also typically performed only once, and may only need to but updated based on the newest release of SAP SCM that you are using.

(17)

SCM210 Lesson: Technical integration of SAP R/3 and SAP SCM

Figure 4: Structure of an RFC Link: Overview

Defining Logical Systems

The first step in integrating two distributed data bases is to identify the unique sending and receiving systems in your SAP landscape. Every client in an SAP system must be uniquely identified in case data will be shared between a particular client in another landscape or another OLTP system (non-SAP). The unique identifier is called the Logical System Name. You must create these logical system names in both SAP R/3 and SAP SCM. SAP recommends that you name the logical system as follows: [System name]CLNT[Client name], for example, OMOCLNT800 for client 800 in system OMO, and give a good description so it is easy to identify the purpose of the logical system (e.g. R/3, CRM, SCM).

(18)

Figure 5: Defining Logical Systems

Once both logical system names have been created in both the SAP R/3 and SAP SCM systems, you must assign these logical system names to the physical clients that exist in both systems, so that the systems can be uniquely addressed in a complex system landscape. Even though you created two logical system names you will assign in the SAP R/3 system the SAP R/3 logical system name to the SAP R/3 client and in the SAP SCM system the SCM logical system name to the SCM client. Do not assign both names in both systems!

Caution: There are additional settings in this table that relate to a

standard currency and how/if changes to configuration settings are allowed and managed. Consult you basis team or project manager to determine what settings should be set.

RFC Link Destinations in SAP SCM integration

Once all clients that will be integrating for your SCM solution has been identified in SAP terms, we must identify where the physical server/client sits on the network infrastructure. In order to communicate between you SAP R/3 and SAP SCM systems you will establish an RFC (Remote Function Call) destination.

(19)

Remote Function Call

An SAP interface protocol based on CPI-C (Common Programming Interface-Communication) used to simplify the programming of communication processes between systems. RFC’s enable you to call and execute predefined functions in a remote system - or in the same system. They manage the communication process, parameter transfer and error handling.

Figure 6: Defining RFC Destinations

RFC destinations create and reverse the link between theSAP R/3 and the SAP SCM Systems. You define the RFC destinations that are “R/3 connections ”(for both SAP R/3 and for SAP SCM) in the administration of the particular systems, transaction Define Target Systems for RFC Calls (transaction code

sm59). In the SAP R/3 system, RFC destination in SAP R/3 under the logical

SCM System name that you have defined and assigned an SCM client to (in our example APOCLNT800). As a target machine, you enter the server address of the SCM server and the system number, so that the SCM System can be addressed in the network.

(20)

Figure 7: RFC Destination Configuration Figure 7: RFC Destination Configuration

Finally, you enter a user that will create the link to the SAP SCM System. This user must exist in the SAP SCM System and have full authorization. This is necessary for the transfer of master and transaction data into SAP SCM . Do the same in SAP SCM : You create an RFC destination under the logical SAP R/3 System name that you have defined and assigned an SAP R/3 client to (in our example, R3CLNT800). You enter the target machine and system number of the SAP R/3 System. Finally, you enter a user that exists in the SAP R/3 System and has the necessary authorization. You can set the RFC destinations between the SAP R/3 and SAP SCM System, so that if an error in the transfer occurs, a new attempt at transferring automatically starts.

Flexible RFC Destinations

As of SCM 4.0, companies will have the opportunity to use multiple or flexible RFC destinations. This change came about due the need of two types of data transfer between SAP R/3 and SAP SCM, pure background data transfer, and calling up user transactions like a Global ATP check. In the case of users calling transactions from either SAP SCM or SAP R/3 , we need to assure that they in fact have authorization to perform the transaction. In earlier releases the RFC

(21)

destination had only one user to log in under, and they had to have access to all necessary integration transactions. As of SCM 4.0 and Plug-in PI2003.1, users can now setup different RFC destinations for the following scenarios:

• In SAP R/3

– Debugging in SAP SCM

– Calling up the QRFC monitor in SAP SCM – Displaying the Application log in SAP SCM – Carrying out availability checks in SAP SCM • In SAP SCM

– Debugging in SAP R/3

– Calling up the QRFC monitor in SAP R/3 – Displaying the Application log in SAP R/3

Figure 8: Flexible RFC Destination Configuration Figure 8: Flexible RFC Destination Configuration

(22)

In order to use Flexible RFC Destinations you will have to follow three steps: 1. Create a separate user for each RFC context. Ensure that the user type

is set to Dialog so that users can perform the transactions interactively. Create and assign a user profile that covers the required tasks.

2. Create a separate RFC destination for each context with its own user for branching into the application log of the corresponding SCM system.

Hint: You go to transaction code SM59 in SAP R/3 and setup an

RFC destination called APOCLNTALOG which is to be used for branching into the application log only of the SCM system APOCLNT800.

3. Assign the RFC Destination to the corresponding logical system and “CIF Application” using transaction CFC7 (or SM30, view, V_CIFRFCDS).

(23)

Defining Flexible RFC Destinations

1. Transaction code: SPRO

2. Follow menu path: Integration with other my SAP.com Components→ Advanced Planning and Optimization→Basic Settings for Setting Up the System Landscape→Assign RFC Destinations to Different Application Cases. 3. Review settings for the different applications.

Data Channels and Queues in SAP R/3 integration

Once the RFC destinations have been established, we must define what the release is of the receiving SCM system. In your SAP R/3 system, you will have to identify the logical system name that represents your SAP SCM system, and identify at what release level it is operating.

Figure 9: Determine Target System and Maintain APO Release

As the system performs the integration in various ways for different SAP APO/SCM releases, you must also enter the release of the APO target system. (Transaction APO Releases in the CIF settings). As SCM continues to evolve this has an impact on how data is technically transferred to SAP SCM.

(24)

Once you have established the release level of your receiving system, we must identify the logical systems are available for the users to send the data from SAP R/3 to the correct SAP SCM system. With this configuration activity you will add all the logical system names with which your SAP R/3 system will be integrating. The CIF uses a data transfer process called QRFC (queued remote function call). This means that the data is stored temporarily in queues Additionally qRFCs may be grouped in LUWs.

LUW

Logical unit of work (LUW) in which multiple queued remote function calls (qRFC) are collected for a data transfer using the Core Interface (CIF). The sequence of qRFCs within an LUW is determined in the source system and retained during posting to the target system. Changes to data that are made using the qRFCs in an LUW are only posted if all qRFCs in the LUW can be processed successfully.

The queue type (inbout or outbound) determines whether the queues processing is controlled by the sending system or recieving system. In addition to this step you will identify the transfer mode type. In actuality the transfer mode type is set by internal parameters.

Figure 10: Outbound and Inbound Queues

During integration of SAP SCM and SAP R/3, mass transactions such as planning data in SAP SCM, where a large amount of data to be transferred is created, can cause considerable system loads in the receiving system. This

(25)

is caused by the missing workload distribution of the qRFC processing in the target system. If inbound queues are used, the system load on the target system is taken into account. If you are expecting high amounts of integration data and insufficient work process resources in the target system, it may be useful to switch to inbound queues. The conversion from outbound (standard) to inbound queues takes place in the SAP R/3 when determining the APO target systems (transaction code CFC1) and in SAP SCM when assigning the logical systems to a business system group (APO Customizing).

Figure 11: Data Transfer Queues Figure 11: Data Transfer Queues

When you enter a logical target system in transaction CFC1, the system automatically suggests the type Outbound Queue. This setting means that the queue processing is controlled by the sending system (SAP R/3). This may lead to problems if the receiving system (SAP SCM) does not currently have enough free work processes to process the queue.

Hint: If you are processing large amounts of integration data and it is

believed you have insufficient work process resources, it may be useful to change this setting to Inbound Queues. This means that the queue processing is controlled by the receiving system (SAP SCM). IF there are not enough work processes available here the data is saved when entering SAP SCM and then processed at a later point in time.

(26)

Business System Groups

Figure 12: Business System Group (1)

An SAP SCM System can be integrated with several SAP R/3 Systems (logical systems). It may, therefore, be the case that the number assignment for certain master data objects, for example, material masters, is not the same in all these logical systems. In the example above, material number A in logical systems 1 and 2 signifies the same hammer, whereas the same material number in logical system 3 (perhaps a subsequently purchased plant) is a screw. If logical systems 1, 2 and 3 are planned with the same SAP SCM System, the problem arises that the system cannot simply transfer the SAP R/3 material numbers into SAP SCM, as they may be ambiguous. The fact that the same material may have different material numbers in different logical systems, is not discussed on this or the following pages. If this does occur, you can use a customer exit in SAP SCM inbound processing where you map the relevant material numbers from the different logical systems onto the unique material number in SAP SCM.

(27)

To guarantee that the naming of master data in distributed system landscapes is unique, business system groups are defined in SAP SCM as areas of the same naming convention. A Business System Group (BSG) groups different physical systems to form a higher-level logical unit. If, for example, two logical systems (LS1 and LS3) exist in a system landscape in which SAP SCM is integrated, and contain different materials with the same name (Material A is a hammer in LS1, but a screw in LS2), this conflict must be resolved for integration in SAP SCM. First of all, both logical systems are to be assigned to different business system groups (BSG1 and BSG2). The logical systems were each assigned to one business system group. The SAP SCM System, as an independent logical system, must also be assigned to a business system group. Each source system (SAP R/3 ) is assigned to a BSG. One BSG can consist of one or several source systems but must contain at least one SAP R/3 source system.

(28)

If the situation arises that two different logical systems with identical number ranges are operating when a distributed system landscape is constructed with SAP SCM, the identical names must be changed with a customer exit. The following enhancements are available as customer exits (transactions SMOD and CMOD) for the inbound processing in the SAP SCM System (the list is not complete):

APOCF001 EXIT_/SAPAPO/SAPLCIF_LOC_001: Location

APOCF002 EXIT_/SAPAPO/SAPLCIF_ATP_001: Maintain ATP check control APOCF003 EXIT_/SAPAPO/SAPLCIF_IRQ_001: Reduction of planned indep. req.

APOCF004 EXIT_/SAPAPO/SAPLCIF_ORD_001: Production and planned orders

APOCF005 EXIT_/SAPAPO/SAPLCIF_PROD_001: Products

APOCF006 EXIT_/SAPAPO/SAPLCIF_PU_001: Purchase order documents EXIT_SAPL_1004_001: Resource

(29)

APOCF011 EXIT_/SAPAPO/SAPLCIF_STOCK_001: Stock For further customer exits: see the online help.

Hint: As of SCM 4.0 all customer exits are located in the IMG.

Menu Path: Integration with other my SAP.com Components→

Advanced Planning and Optimization→Application-Specific Settings and Enhancements→...

If the situation arises that two different logical systems with identical number ranges are operating when a distributed system landscape is being constructed, a unique mapping structure must be constructed. Firstly, you must define the business system groups in APO Customizing step Maintain Business System Group (under Basis Settings in APO). In the next step (Customizing step Assign Logical System and Queue Type) you assign the diverse logical systems of your system landscape to a BSG. You should be aware that within a system group, the same naming convention must apply, i.e. the different master data objects must have unique names within the group. The last step mainly consists of the master data objects from the different BSGs being copied with unique names into SAP SCM using a customer exit. These customer exits exist for all master data. You must maintain a BSG, even when only one SAP R/3 is linked with one SAP SCM System, or when several SAP R/3 Systems are connected without the risk of

(30)

ambiguities. You will only need more than one BSG when there is no unique naming convention. The SAP SCM System should preferably be assigned to the BSG, where its data must not be renamed.

(31)

Business System Groups

1. Transaction code SPRO

2. Advanced Planning and Optimization→Basis Settings→Integration→ Business system group→Maintain business system group

3. Review current business groups

4. Advanced Planning and Optimization→Basis Settings→Integration→ Business system group→Assign Logical System and Queue Type

(32)

(33)

Exercise 1: Architecture of Integration

Exercise Objectives

After completing this exercise, you will be able to:

• Review the technical settings of the RFC connection between the SAP R/3 System and an SAP SCM System.

Business Example

As your company implements SAP SCM , the integration needs to be set up between the two systems. This integration uses an RFC connection and these settings must be maintained to set up the integration.

Task:

The link between an SAP R/3 System and the SAP SCM System is based on an RFC connection that connects two logical systems.

1. Which SAP R/3 client are you working in?

2. Which logical system name is assigned to your SAP R/3 client? Look in your SAP R/3 system

3. Which SAP SCM client are you working in?

(34)

4. Which logical system is assigned to your SAP SCM client?

5. In the SAP R/3 System, display the RFC connection to the SAP SCM System. Which user name is used for logon to the SAP SCM System?

6. In the SAP SCM System, display the RFC connection to the SAP R/3 System. Which user name is used for logon to the SAP R/3 System?

(35)

Solution 1: Architecture of Integration

Task:

The link between an SAP R/3 System and the SAP SCM System is based on an RFC connection that connects two logical systems.

1. Which SAP R/3 client are you working in?

Answer: Varies, for example, 8##

2. Which logical system name is assigned to your SAP R/3 client? Look in your SAP R/3 system

Answer: Varies, but should use the format T90CLNT090. Use the

following menu paths to check the system name assigned: Tools→ Customizing→IMG→Edit Project , Choose SAP Reference IMG, then Integration with Other mySAP.com Components→Advanced Planning and Optimization→Basic Settings for Setting up the System Landscape→Assign Logical System to a Client.

3. Which SAP SCM client are you working in?

Answer: Varies, should be the same as the SAP R/3 client, for example,

8##.

4. Which logical system is assigned to your SAP SCM client?

Answer: Varies, but should use the format APOCLNT8##. Use the

following menu paths to check the system name assigned: Tools→ Customizing→IMG→Edit Project , choose SAP Reference IMG, and then SAP Web Application Server→Application Link Enabling (ALE)→Sending and Receiving Systems→Logical Systems→Assign Client to Logical System. 5. In the SAP R/3 System, display the RFC connection to the SAP SCM

System. Which user name is used for logon to the SAP SCM System?

Answer: USERADMIN.

Use the following menu paths to check the user name: Tools→

Administration→Administration→Network→RFC Destinations (SAP R/3 Connections), and then Locate the logical system name of the SAP R/3 System and double click to display the details..

(36)

6. In the SAP SCM System, display the RFC connection to the SAP R/3 System. Which user name is used for logon to the SAP R/3 System?

Answer: USERADMIN.

Use the following menu paths to check the user name:Tools→Customizing →IMG→Edit Project , Choose SAP Reference IMG, then Integration with Other mySAP.com Components→Advanced Planning and Optimization→ Basic Settings for Setting up the System Landscape→Set Up RFC Destination, and then Locate the logical system name of the SAP R/3 System and double click to display the details..

(37)

Lesson Summary

SAP SCM systems

(38)

Lesson: Generating and Activating Integration Models

Lesson Overview

After the RFC connection is set up between the SAP R/3 System and the SAP SCM System, an integration model controls the data objects that integrate.

Lesson Objectives

• Activate integration models for transfer of transactional data.

Business Example

Planning elements must be transferred from the SAP R/3 system to the SAP SCM system to derive a proper production plan. Upon completing a production plan, the results must be transferred back to the SAP R/3 system to perform additional planning via MRP, or actual manufacturing or procurement activities. Now that you have reviewed the necessary configuration to start the integration of transactional data between and SAP SCM system and an SAP R/3 system, you need to trigger the actual transfer of that data. In order to accomplish the bi-directional flow of transactional data you will setup and activate an integration model for the necessary objects.

Integration Models: Creating and Activating

The data transfer between the SAP R/3 and SAP SCM systems is defined and controlled using the Core Interface (CIF). The CIF is the central interface for connecting SAP SCM to the existing SAP R/3 system environment. An RFC connection with the SAP R/3 System is a technical requirement for successful data transfer to SAP SCM using the Core Interface. The CIF interface is an add-on to the SAP R/3 System that you install using the relevant plug-in. The exact installation process is dependent, amongst other things, on the SAP R/3 release you are working with. You can find current detailed information on plug-ins in SAPNet, under the alias /R3-plug-in. The selection of master data that the system transfers to SAP SCM is determined in an integration model that you define in the SAP R/3 System.

(39)

SCM210 Lesson: Generating and Activating Integration Models

Figure 16: Master Data Interface: Core Interface (CIF)

The Core Interface is a real-time interface. Only the data objects needed in the data structures reconciled in planning in SAP SCM for the particular planning and optimization processes are transferred from the complex data set in SAP R/3 to SAP SCM. Both the initial data transfer (initial transfer) and the transfer of data changes to SAP SCM are made through the Core Interface. The master data objects in SAP SCM are not identical to those in SAP R/3. During master data transfer, the relevant SAP R/3 master data is usually mapped onto corresponding SAP SCM planning master data. The SAP R/3 system is always the dominant system for master data. Only specific SAP SCM master data that does not exist in SAP R/3 is maintained directly in SAP SCM .

(40)

Figure 17: Master Data Objects of the CIF

You define the integration model that controls the transfer of master and transaction data in the SAP R/3 System. You can find the menu option Core Interface Advanced Planner and Optimizer (the CIF menu) under Logistics→ Central Functions→Supply Chain Planning Interface. The integration model distinguishes between each data object. SAP recommends that you organize your integration models according to the list published in the CIF: Tips and Tricks document. In the integration model, you select the data set that you want to transfer. You specify the following in the integration model. The SAP SCM target system for the data transfer - The data objects you want to transfer. You can delete integration models that you no longer need. Note that you must first deactivate these integration models.

(41)

Figure 18: Initial Data Transfer of Master Data: Overview

The master data that the system will transfer for the first time (initial

transfer), from the SAP R/3 System into the SAP SCM System, is defined in an integration model. This integration model is generated in the SAP R/3 System using transaction CFM1. An integration model is uniquely defined by its name and application. It is useful to create several integration models with the same name but as different applications. This will help ensure that the data pools of your integration models are generally not too big. This enables you to handle errors more easily. The target system that you specify in the integration model determines the SAP SCM System that the master data is transferred into. The target system is a logical ( SAP SCM) system that must have an RFC connection. Finally, you use a particular integration model to specify which master data you want the system to transfer. To do so, you first specify the master data types that flow into the integration model. In the second step, you specify the selection criteria to be used for the selection of the individual master data documents in the SAP R/3 System. You complete the generation of the integration model by "executing" the model (this means that the data objects of the model are compiled) and then you save it.

(42)

Figure 19: Generate Integration Model for Initial Data Transfer Figure 19: Generate Integration Model for Initial Data Transfer

To transfer data into SAP SCM, you must activate an integration model that has previously been generated. You activate an integration model with the Activate Integration Model transaction (transaction code CFM2) in the CIF. It is useful to have several integration models active at a time. Choose the Start function to trigger the initial data transfer into SAP SCM: The master data, or the equivalent of the SAP SCM master data in SAP SCM, exists in the SAP SCM System. Basically, only the master data that was not available in any other active integration model is transferred (delta comparison). To be able to carry out the delta matching that was executed during activation of an integration model quickly, the system refers to the runtime version of the integration models. The runtime version is formed in the background from all active integration models, each with one object type and target system, formatted optimally and saved to the database. It is automatically updated during the activation of new models. You can access the runtime version manually from report RCIFIMAX. The initial data transfer usually runs in a particular order: the objects are selected successively, transferred to SAP SCM and processed there in this sequence. For improved system performance, it is also possible to execute a parallel initial data transfer: several integration models can be activated at the same time. You can set during parallel

(43)

processing whether to run the selection in SAP R/3, processing in SAP SCM or both at the same time. Parallel processing takes place within an object type, whereas the different object types are still transferred in sequence.

Figure 20: Selection Criteria for MRP Type X0

Planning is not necessarily executed for all materials in SAP SCM. Planning for critical materials can take place in SAP SCM, while less critical materials (such as consumption-controlled purchasing materials) are planned exclusively in SAP R/3. Materials planned in SAP SCM should not be planned again in SAP R/3 - the planning result from SAP SCM is transferred directly in the form of planned or production orders to SAP R/3. However, for materials with a BOM, You should assign these materials a special MRP type with the MRP procedure "X" ("without MRP, with BOM explosion"). This will ensure that dependent requirements will be created in the SAP R/3 system for non-SAP SCM-relevant components. (This MRP procedure is available as of 4.0; if you work with earlier releases, use MRP type "P4" with a planning time fence of 999 days). It is also possible to use the MRP type X0 to select materials relevant for SAP SCM in the integration model. If you give materials that are to be planned in SAP SCM a special plant-specific material status, you can use the material status to limit the selection further. In general, you should be careful about separating SAP SCM-relevant materials from those that are not SAP SCM-relevant: For effective planning in SAP SCM, you must be sure that all materials important for the planning process are actually planned

(44)

in SAP SCM. (Take capacity planning as an example: If the capacities are to be planned for the different resources in SAP SCM, all materials that are produced on these resources must be planned in SAP SCM.)

(45)

Exercise 2: Transfer of Master Data

Exercise Objectives

After completing this exercise, you will be able to:

• Prepare SAP R/3 material masters for planning in SAP SCM

• Create an integration model for the initial data transfer and execute the transfer

Business Example

Precision Petrol Pump company constitutes a number of independent business units located in different parts of the world. Each unit is headed by a business unit head and operates as an independent entity under the parent company. As part of a move to centralize planning functions in SAP SCM, you must transfers data from you SAP R/3 system to the SAP SCM system.

to initiate this transfer you will create an integration model that will select the relevant master data for integration to SAP SCM and activate this model.

(46)

Task 1: Review the Configuration of MRP Type X0

To expedite the transfer of master data you wish to select the SAP SCM relevant master data by filtering off of several field settings in the various master data objects. When transferring the Material Master your planners will use the MRP type X0 to select SAP R/3 materials masters that need to be transferred to SAP SCM.

1. Which MRP procedure is defined in the MRP type X0?

2. What effect does this MRP procedure have?

3. Which planning method is entered in this MRP Type?

Task 2: Manage SAP SCM relevant Master Data

In order to transfer your master data to SAP SCM as easily as possible we will set the material master up so that many different materials could possibly select at one time during the generation of the integration model

1. Change the material master T-F1## in plant 1000, so that the MRP Type is set to X0, and the MRP controller is set to 0##.

(47)

Task 3: Create an Integration Model to Transfer Materials

to SAP SCM

Create an integration model to transfer Material Master records from SAP R/3 to SAP SCM.

1. Create and generate an integration model for master data using plant 1000, MRP Ctrlr 0##, and MRP Type X0. Use the data in the following table to identify your integrations model. After generating the model do not leave the transaction!

Field Data

Model Name PUMP##

Logical system APOCLNT8XX

APO Application MAT T-F1##

2. Save your settings as the variant Mat. ## with the description T-F1##.

Task 4: Transfer Material to SAP SCM

Activate your integration model to begin the initial data transfer and setup the incremental data transfer.

1. Activate your integration model PUMP##.

(48)

Task 5: Review Transfer Results

Check the results of the master data transfer in the SAP SCM System.

1. What is the description of the product T-F1##?

2. Which user created this product master record?

(49)

Solution 2: Transfer of Master Data

Task 1: Review the Configuration of MRP Type X0

To expedite the transfer of master data you wish to select the SAP SCM relevant master data by filtering off of several field settings in the various master data objects. When transferring the Material Master your planners will use the MRP type X0 to select SAP R/3 materials masters that need to be transferred to SAP SCM.

1. Which MRP procedure is defined in the MRP type X0?

Answer: MRP Type X0 has MRP procedure X, Without MRP, with BOM

explosion assigned to it.

Display the configuration of the MRP type X0 by first going to the IMG of the SAP R/3 System using the menu path Tools→Customizing→IMG →Edit Project. Once in the IMG click the button on the tool bar to access the SAP Reference IMG. In the SAP Reference IMG use the menu path Production→Material Requirements Planning→ Master Data→Check MRP Types.

Select the MRP Type X0 and click the button on the tool bar or simply double click on MRP Type X0.

2. What effect does this MRP procedure have?

Answer: This MRP procedure means that the corresponding materials

will not be planned in the SAP R/3 System during any MRP/MPS planning runs. Note this setting is only relevant if you have items on the BOM that are still planned in SAP R/3. If a BOM change takes place to an SAP R/3 relevant item on the BOM, existing planned orders must be adjust to reflect the BOM changes. During the next SAP R/3 planning run all existing planned orders will have the BOM re-exploded so that the SAP R/3 relevant changes can be consider and planned. No header information on the planned order will change since this will be controlled by the orders in SAP SCM. If all items on the BOM are SAP SCM relevant, consider using MRP type ND (No Planning).

3. Which planning method is entered in this MRP Type?

Answer: The Planning method assigned to MRP Type X0 is 1, Planned

by external system. Check the Additional selection parameters section to find this information.

(50)

Task 2: Manage SAP SCM relevant Master Data

In order to transfer your master data to SAP SCM as easily as possible we will set the material master up so that many different materials could possibly select at one time during the generation of the integration model

1. Change the material master T-F1## in plant 1000, so that the MRP Type is set to X0, and the MRP controller is set to 0##.

a) Menu path in the SAP R/3 Enterprise: Logistics→Production

→Master Data →Material Master→Material→Change → Immediately. (MM02)

b) Enter Material number T-F1##, and pressENTER. c) Select MRP 1 view, and press ENTER.

d) Enter Plant 1000, and press ENTER.

e) Change the MRP type toX0, and the MRP Controller to 0## f) Select SAVE

Task 3: Create an Integration Model to Transfer Materials

to SAP SCM

Create an integration model to transfer Material Master records from SAP R/3 to SAP SCM.

1. Create and generate an integration model for master data using plant 1000, MRP Ctrlr 0##, and MRP Type X0. Use the data in the following table to identify your integrations model. After generating the model do not leave the transaction!

(51)

Field Data

Model Name PUMP##

Logical system APOCLNT8XX

APO Application MAT T-F1##

a) From the SAP R/3 main menu choose Logistics→Central Functions →Supply Chain Planning Interface→Core Interface Advanced Planning and Optimizer→Integration Model→Generate→Create

b) Enter the data in the above table in the header fields. c) Select the Materials indicator on the left side of the screen.

d) Enter the selection criteria in the table below, on the right side in the general selections for materials section. Leave all other fields blank.

Field Data

Plnt 1000

MRP Ctrlr 0##

MRP Type X0

e) Execute .

f) On the next screen click the button. You can check which materials were selected by double clicking on the Materials line.

Note: Only when the message “Integration model PUMP##

generated for target system APOCLNT8XX and application

MAT T-F1## ” appears have you successfully generated

and integration model:

g) Select Continue h) Select Back once.

2. Save your settings as the variant Mat. ## with the description T-F1##.

a) Select Save.

b) Enter the variant name Mat.## with the description T-F1## c) Select Save.

(52)

Task 4: Transfer Material to SAP SCM

Activate your integration model to begin the initial data transfer and setup the incremental data transfer.

1. Activate your integration model PUMP##.

a) From the SAP R/3 menu, Logistics→Central Functions→Supply Chain Planning Interface→Core Interface Advanced Planning and Optimizer→Integration Model→Activate

Your integration model information should default into the fields since that was the last one you used. If it doesn’t make sure that the fields are correct with the information from the previous step and execute.

Double click on the date/time line or click it and click the button on the tool bar. A green check should appear in front of it. To begin the initial data transfer, click the

button on the tool bar.

Task 5: Review Transfer Results

Check the results of the master data transfer in the SAP SCM System. 1. What is the description of the product T-F1##?

Answer: Pump PRECISION 100. Using SAP Menu→Advance Planning and Optimization→Master Data→Product enter your product T-F1##, plant 3100, select the location radio button, and click the

button.

2. Which user created this product master record?

Answer: USERADMIN as found on the Administration tab.

3. Where does this user come from?

Answer: The user USERADMIN is used by SAP R/3 to log on to the SAP

SCM system during the CIF transfer of data. This user can be found in the RFC destination and indicates this product master record was transferred from SAP R/3 via the CIF.

(53)

Lesson Summary

(54)

Lesson: Monitoring and Error handling tools for integrating

SAP R/3 and SAP SCM.

Lesson Overview

Upon implementing SAP SCM, your organization has committed to transfer large amounts of data between the SAP R/3 and SAP SCM data bases. Due to the large volume of data that will pass between the systems, often times errors or inconsistencies will occur. In order to correct these errors or inconsistencies, you will become familiar with the SCM queue manager, and various delta reports that can identify and correct inconsistencies in the data.

Lesson Objectives

• Describe the data transfer process, and how errors are recorded • Demonstrate the qRFC Monitor and explain its purpose in handling

transfer errors

• Demonstrate the Application Log and explain its purpose n handling transfer errors

• Demonstrate the SCM Queue Manager and explain its purpose in handling transfer errors

• Demonstrate the qRFC Alert and explain its purpose in handling transfer errors

• Explain the differences between the Post Processing and the previously mentioned tools.

• Demonstrate the Compare/Reconcile functionality and explain its purpose in handling transfer errors

Business Example

Assume your company is using SAP R/3 and SAP SCM, the integration through the CIF needs monitoring to ensure the two systems stay in sync. You need to use the available tools to resolve any possible problems and ensure data consistency and accuracy across systems.

(55)

SCM210 Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM.

Monitoring and Error Handling

As data is transfer between the two systems, it is grouped into qRFC-LUWs (Logical Units of Work). The data within each LUW is only processed in the receiving system if all data within that LUW can be sent successfully. If one or more LUW entries cannot be transferred, a queue entry with the status SYSFAIL is created for the entire LUW. This can quickly lead to what is referred to as the “serialization :”affect. Serialization may take one of the following forms

• One queue error might block a large number of subsequent queues • Random blocks of unrelated business data

• A single error might cause immense inconsistencies between the systems. Example: An error on a sales order might cause PP data not to be recorded in a timely fashion.

In this situation, the first LUW that fails, causes any other LUWs for the same data channel to queue up and have a status WAITING.

(56)

The Core Interface offers several basic monitoring functions to monitor the data transfer from SAP R/3 to SAP SCM as well as from SAP SCM to SAP R/3: the qRFC monitor to display incorrect queue entries and the application log.

Note: As of SCM 4.0 companies can initiate a new “CIF error

handling”process. It does not work in all applications, but the details will be explained later.

In addition, the qRFC alert monitor is used to monitor the queues in SAP SCM and SAP R/3 that are relevant to SCM-R/3 integration. If queue blocks are detected, an automatic message can be sent to a predefined destination. Instead of evaluating the analyses in both systems (SAP R/3 and SAP SCM ) separately when errors occur, the user can use the central SCM Queue Manager available in SAP SCM to monitor the queues and application logs in both systems. Whereas the transactions qRFC monitor and qRFC alert are to be carried out separately for outbound and inbound queues, both queue types can be monitored at the same time in the SCM Queue Manager.

The communication between SAP R/3 and SAP SCM is based on the

asynchronous transfer technology of the queued Remote Function Call (qRFC). A Remote Function Call (RFC) is calling a function module in a different system. This technology is used in the integration between SAP SCM and SAP R/3 both for the initial data supply and transfer of data changes (from SAP R/3 to SAP SCM) as well as for the publication of planning results (from SAP SCM to SAP R/3). The data is first buffered by the sending system and then transferred to the target system (outbound queues, inbound queues are also possible). The big advantage of this is that the application that triggered the data transfer does not have to wait until the update has been completed in the target system. However, this means that return parameters cannot be passed on and potential error messages cannot be directly returned to the application. Two types of errors are distinguished for the processing of qRFC calls:

1. Communication errors: This includes network problems, a non-existing

RFC destination, and so on. Since the data transfer is repeated after certain periods, most of these communication errors should disappear once the network connection is available again.

2. Application error: This includes program errors, non-posting of data

in the target system, missing master data at a transaction date, etc. Application errors cannot be solved by the system independently and must be processed by the system administrator.

(57)

The central instance for monitoring application errors is the SCM Queue Manager, a central tool containing information about the SAP R/3 and SAP SCM qRFC monitors. The qRFC monitors are available in SAP R/3 and SAP SCM for outbound or inbound queues. All transfer fields (queues) are displayed for the target system, they can be activated or deleted.

qRFC Monitor for Error Processing

Figure 23: Using the qRFC Monitor

In the initial data transfer, transfer fields are recognized and displayed at the time of the integration model activation. Repeat and Ignore functions are available in the dialog box. If you choose Repeat, the system attempts to start initial data transfer again (for example, if there was only a temporary problem in system communication). The Ignore button can be used if the activation has failed due to an existing transaction data queue. As failed transaction data transfers do not necessarily affect a master data transfer, the initial transfer can ignore this entry. This function cannot be used for previous failed initial data transfers. In this case, the problem must be analyzed with the qRFC monitor. During online transfer (for example, stock postings in SAP R/3 ), transfer fields are not displayed online for the runtime (asynchronous transfer technology). This means that you do not have to check in the qRFC monitor during non-transfers of data between SAP SCM and SAP R/3 whether entries marked in red are displayed. This check can be carried out automatically

(58)

by qRFC alert. There is a qRFC monitor in both SAP R/3 and SAP SCM. In the qRFC monitor, by double-clicking on the affected lines, all function calls for the selected transfer queue are displayed. The top function module blocks all following entries in the case of an error. You can display the current status text from the error short text. A detailed error message is stored in the application log of the target system. In the example above, the user from the RFC destination is either locked in SAP SCM or does not exist.

Figure 24: Queue Channels for Data Transfer: Examples

In the example above, the PPM could not be transferred for material C because the material itself was not transferred. The queue for the next initial transfers of master data is therefore blocked. However, online transfers for transaction data can still be carried out, provided that an active integration model exists for the master or transaction data in question. There are various queue channels available in the interface:

CF_ADC_LOAD - Initial data transfer CFSTK* - Stocks,

CFPO* - Purchase Orders and Purchase Requisitions CFPLO* - Planned Orders/Production Orders

CFSLS* - Sales Orders

(59)

CFCNF - Confirmations

CFPIR* - Planned Independent Requirements

CFMAT* - Planned Independent Requirements Reduction CFPCM* - Production Campaigns

CFCLA* - Master Data for Classes

CFCHR* - Master Data for Characteristics CFSHP* - Shipments

CFCUVT* - Planning Tables

(* stands for the number of the purchase order, sales order etc.)

Note: The status of these queues can be view via transaction CFP2

If only temporary communication errors occur in the network connection, the failed transfers (entry in the qRFC monitor) can be started again (by choosing Activate queue in the qRFC monitor). If you only want to re-start an object type (for example, locations) within a queue, you can choose the Execute LUW function to repeat the transfer of locations. If there are communication errors and you want to execute the new activation of the queue automatically, you can make a setting in the RFC destination (transaction SM59) so that the system attempts in defined time intervals to transfer the data (in the RFC destination under TRFC Options; default setting - 30 attempts every 15 minutes).

(60)

Monitoring transfer errors with the qRFC monitor

1. SAP R/3 Menu Path: Logistics →Central Functions→Supply Chain Planning Interface→Core Interface Advanced Planner and Optimizer→ Monitoring→qRFC Monitor

2. There you will see the Queues that are blocked

3. Select the queue that is related to your material (T-F2##) and select Display Selections

4. Here you will see the LUW that has been formed with the transactions that have failed. Note the status SYSFAIL

5. Select the LUW and select Choose

Application Log for Error Processing

You can use the application log to trace when (time), and what (data objects and integration model) was transferred by whom (user). In addition, the application log provides a detailed error message if an application error occurred. As a prerequisite, logging must have been switched on. The setting of the logging mode takes place in SAP R/3 or SAP SCM (transaction CFC2 in SAP R/3 and /SAPAPO/C4 in SAP SCM). The following settings are possible: • Standard (only the headers of the data records are logged) •

• Detailed (header and contents of the transferred data records are logged). •

The detailed logging can quickly lead to large data quantities and therefore performance problems in the production operation. For this reason, we recommend using detailed logging only when the detailed data is actually needed, for example, in the implementation phase. The system does not delete the logs automatically. To prevent extreme database load, we recommend deleting the logs periodically (also possible in background processing). If you do not make an entry in the date and time fields, all logs older than two weeks are deleted.

(61)

Figure 25: Using the Application Log

In the example above, an initial data supply was carried out in SAP R/3 to transfer several different master data, including, for example, purchasing info records. One of the purchasing info records transferred was for a vendor that does not exist in SAP SCM. This purchasing info record could therefore not be transferred. You can select different subobjects for the CIF object in the SAP R/3 and SAP SCM application log. These include, for example, EP External procurement, IP In-house production, or INITIAL Initial supply and LOCATION Location: customer, plant, vendor (the entries for an initial supply and an transfer of data changes are grouped under the subobject INITIAL). The transaction ID of the sending application serves as the key of an error message (TID field in the qRFC line of the qRFC monitor of the sending system). When you enter this number, you can display all messages for this qRFC call in the target system. In the application log, you enter the number of the transaction ID in the External ID. field and execute the selection. The system displays all messages for the call in question. With SAP R/3 transaction CFC6, you can set the interface parameters that are to be executed in the application log.

In the example above, a planned order for a finished product and purchase requisitions for the components of the finished product have been created in SAP SCM. However, these were not included in any active integration model at the time of order creation. Therefore, the orders were not transferred to

(62)

SAP R/3 but kept in the queue. In the outbound log, you always recognize the log of successful transfers. In the logging of the target system, error messages are displayed if errors occurred during transfers.