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.
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##.
SCM210 Lesson: Generating and Activating Integration Models
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##.
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?
SCM210 Lesson: Generating and Activating Integration Models
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.
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!
SCM210 Lesson: Generating and Activating Integration Models
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.
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.
SCM210 Lesson: Generating and Activating Integration Models
Lesson Summary
You should now be able to:
• Create integration models for transfer of transactional data using SAP recommended selection methods.
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
After completing this lesson, you will be able to:
• 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.
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.
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.
SCM210 Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM.
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
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
SCM210 Lesson: Monitoring and Error handling tools for integrating SAP R/3 and SAP SCM.
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).
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