SAP Best Practices EWM Configuration Guide Y31_BB_EN
December 28, 2016 | Author: damokrane | Category: N/A
Short Description
Download SAP Best Practices EWM Configuration Guide Y31_BB_EN...
Description
SAP EWM 7.01 November 2011 English
ERP-EWM Integration (Y31) Building Block Configuration Guide
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Copyright © 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. 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 64
SAP Best Practices
ERP-EWM Integration (Y31): 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 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.
Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG
Page 3 of 64
F2)
or the
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Content 1 Purpose................................................................................................................................. 6 2 Configuration Content for SAP EWM.....................................................................................6 3 Information for System Administrators...................................................................................6 4 System Connections.............................................................................................................. 7 4.1 Configuration Settings for the ERP System...................................................................7 4.2 Activating Business Functions in Switch Framework.....................................................9 4.3 Creating an RFC User in ERP.....................................................................................10 4.4 Naming the Logical System for the Connection to SAP EWM.....................................11 4.5 Assigning a Logical System to a Client.......................................................................11 4.6 Specifying the SAP APO Release...............................................................................12 4.7 RFC Destinations........................................................................................................ 12 4.7.1 Defining RFC Destinations in ERP.........................................................................13 4.7.2 Determining RFC Destinations for Method Calls in ERP.......................................13 4.8 Setting the Target System and Queue Type...............................................................14 4.9 qRFC Monitor Settings................................................................................................ 14 4.9.1 Maintaining qRFC Monitor (QIN Scheduler) Settings in ERP.................................15 4.9.2 Maintaining qRFC Monitor (QOUT Scheduler) Settings in ERP.............................15 4.9.3 Registering Display Programs for Application Log in ERP.....................................15 4.10 Setting User Parameters for Data Transfer...............................................................16 4.11 Checking Basic Table Entries....................................................................................16 4.12 Additional Material Master Attributes.........................................................................17 4.12.1 Activating Additional Material Master Screens.....................................................17 4.12.2 Maintaining Additional Screen Sequences...........................................................18 4.13 Extended Inbound Delivery.......................................................................................18 4.13.1 Assigning the Profile for Extended Inbound Delivery Processing (VL60) Users...18 4.14 Assigning Warehouse Number to Plant and Storage Location..................................19 4.15 Assigning Shipping Points to Plants..........................................................................19 4.16 Maintaining Shipping Point Determination.................................................................20 4.17 Assigning Goods Receiving Points for Inbound Delivery...........................................20 4.18 Organizational Structures in the ERP System...........................................................21 4.18.1 Maintaining Extended Warehouse Management-Specific Parameters................21 4.18.2 Defining the Queue for Extended Warehouse Management................................22 4.18.3 Logging Sent and Received Messages................................................................23 4.18.4 Registering the Navigation from the Queue.........................................................23 4.18.5 Generating the Distribution Model for ERP to EWM............................................23 4.19 Defining Delivery Split by Warehouse Number..........................................................24 5 Configuration Settings for SAP SCM...................................................................................24 5.1 Creating an RFC User in SCM....................................................................................26 5.2 Naming the Logical System for the Connection to SAP ERP......................................27 5.3 Assigning a Logical System to a Client.......................................................................27 5.4 Defining RFC Destinations in SCM.............................................................................28 5.5 Maintaining Business System Groups.........................................................................29 5.6 Assigning Logical System and Queue Types..............................................................29 5.7 Determining RFC Destinations for Method Calls in EWM...........................................30 5.8 Maintenance of the qRFC Monitor Settings.................................................................30 5.8.1 Maintaining qRFC Monitor (QIN Scheduler) Settings in EWM...............................30
© SAP AG
Page 4 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
5.8.2 Maintaining qRFC Monitor (QOUT Scheduler) Settings in EWM...........................31 5.9 Defining a Separate Business System........................................................................31 5.10 Defining the Business System...................................................................................32 5.11 Defining Outbound Communication...........................................................................32 5.12 Setting Control Parameters for the ERP Version Control..........................................33 5.13 Delivery Processing................................................................................................... 34 5.13.1 Defining Number Range Intervals........................................................................34 5.13.2 Defining Number Ranges for ERP Documents....................................................36 5.13.3 Defining the Delivery Priority................................................................................36 5.13.4 Defining Shipping Conditions...............................................................................37 5.13.5 Defining Incoterms............................................................................................... 37 5.14 Defining Warehouse Numbers..................................................................................37 5.15 Mapping Warehouse Numbers..................................................................................38 5.16 Activating Business Add-Ins (BAdIs).........................................................................38 5.16.1 Activating BAdI: Inbound Processing for Location...............................................38 5.16.2 Activating BAdI: Inbound Processing for Product.................................................40 5.16.3 Copying BAdI Method Source Code....................................................................40 5.16.4 Activating BAdI: Inbound Processing for Partner.................................................41 5.17 Define the Transportation Group...............................................................................42 5.18 Specifying Output Format of Product Number...........................................................43 5.19 Checking the SAP APO Model and Planning Version...............................................43 6 Data Transfer to SAP SCM Using the Core Interface (CIF).................................................44 6.1 Assign Warehouse No. to Warehouse No. of Decentralized SCM System................45 6.2 Activating Business Transaction Events (BTEs)..........................................................46 6.3 Configuring Change Transfers for Master Data...........................................................46 6.4 Activating ALE Change Pointers for Message Types..................................................47 6.5 Creating the Maximum Model......................................................................................48 6.6 Creating an Integration Model in the ERP System......................................................48 6.7 Activating the Integration Model in the ERP System...................................................49 7 Configuration Settings for SAP SCM after Data Transfer....................................................51 7.1 Checking Data Transfer via the Core Interface (CIF)..................................................52 7.2 Creating a Supply Chain Unit for a Warehouse...........................................................52 7.3 Creating a Supply Chain Unit Hierarchy......................................................................53 7.4 Enhancing Business Partners for Plants.....................................................................53 7.5 Assigning Warehouse Numbers..................................................................................55 7.6 Registering Display Programs for Application Log in EWM.........................................55 7.7 Activating Business Configuration Sets (BC Sets)......................................................56 7.8 Mapping Storage Locations from the ERP System to EWM........................................57 8 Additional Data Transfer to SAP SCM Using the Core Interface (CIF)................................58 8.1 Modifying the Integration Model for Additional Data Transfer......................................59 8.2 Creating a Variant for Deleting Inactive Integration Models.........................................60 8.3 Creating a Variant for Activating Integration Models for Background Processing........60 8.4 Scheduling Background Jobs and Specifying Start Conditions...................................61 9 Final Configuration Settings for SAP SCM...........................................................................63 9.1 Scheduling Background Jobs for Data Transfer per Report........................................63
© SAP AG
Page 5 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
ERP-EWM Integration 1
Purpose
This configuration guide provides you with the necessary information for configuring the integration of SAP ERP and SAP Extended Warehouse Management (EWM). In this integration scenario, SAP EWM is a component of SAP Supply Chain Management (SCM). In this document, SAP Advanced Planning and Optimization (APO) refers to the Core Interface (CIF) and not to the APO component. The CIF is used for transferring master data between the ERP system and SAP EWM. In this document, you find references to functions, which were developed for Service Parts Management (SPM). SAP EWM, for example, makes use of the processing of inbound deliveries function, which was developed for SPM.
2
Configuration Content for SAP EWM
This guide describes the complete configuration for integrating SAP ERP and SAP EWM, while SAP EWM is a component of SAP SCM. It does not describe the complete configuration for integrating SAP ERP and SAP EWM, while SAP EWM is an add-on application. You must ensure that you follow the configuration steps in exactly the order in which they are presented in this document. If you do not carry out the steps in this order, the system configuration may fail.
3
Information for System Administrators
System administrators have to make specific settings for the integration of SAP ERP and SAP EWM before any customizing activity is carried out. System administrators need to pay particular attention to the following activities: •
All cross-client activities, such as: o In the ERP system:
o
•
Activating Business Functions in Switch Framework
•
Assigning a Logical System to a Client
•
Naming the Logical System for the Connection to SAP EWM
•
Specifying the SAP APO Release
•
Activating Business Transaction Events (BTEs)
In SAP SCM: •
© SAP AG
Assigning a Logical System to a Client
Page 6 of 64
SAP Best Practices
•
4
ERP-EWM Integration (Y31): Configuration Guide
•
Naming the Logical System for the Connection to SAP ERP
•
Checking the SAP APO Model and Planning Version
All activities that relate to user exists or Business Add-Ins (BAdIs)
System Connections
You can use this process to connect the component SAP Extended Warehouse Management (EWM) to an enterprise resource planning (ERP) system. SAP EWM is a component of the SAP Supply Chain Management (SCM) application. This documentation describes the necessary settings to be made, based on the assumption that an SAP ERP system is used as the back-end system. If you use a different system, you have to make similar connections and settings.
Procedure Ensure that you follow the steps in the order outlined. If you do not carry out the steps in this order, the system configuration may fail. 1. Set up the ERP for connection to the SAP SCM system, see step Configuration Settings for the ERP System. 2. Set up SAP SCM for connection to the ERP system, see step Configuration Settings for SAP SCM. 3. Transfer data from the ERP system to SAP SCM, see step Data Transfer to SAP SCM Using the Core Interface (CIF). 4. Use the transferred data to make settings in SAP SCM, see step Configuration Settings for SAP SCM After Data Transfer. 5. Transfer additional data from the ERP system to SAP SCM, see step Additional Data Transfer to SAP SCM Using the Core Interface (CIF). 6. Make the final configuration settings for SAP SCM, see step Final Configuration Settings for SAP SCM.
Result By following through this process, you ensure the integration of the SAP EWM component with the ERP system.
4.1 Configuration Settings for the ERP System You can use this process to make configuration settings in the ERP system that are needed for the integration with SAP SCM. By connecting the two applications you can transfer data from the ERP system that is relevant for processes in SAP EWM.
Prerequisites You have installed and correctly configured the following systems on SAP Enhancement Package 2 for SAP NetWeaver 7.0:
© SAP AG
Page 7 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
•
SAP ECC 6.0 including SAP Enhancement Package EhP5
•
SAP SCM 7.0 including SAP Enhancement Package 1 for SAP SCM 7.0
In the ERP system, you have created the following objects: • •
Plants, for example 1000 Storage location(s), for example YAFS and YROD See Customizing for SAP ERP under Enterprise Structure → Definition → Materials Management → Maintain storage location.
• •
Warehouse numbers, for example EWM Shipping points, for example 1000 See Customizing for SAP ERP under Enterprise Structure → Definition → Logistics Execution → Define, copy, delete, check shipping point. Choose Define shipping point.
• •
Customers for example 491000 Customer assigned to plant 1000 See Customizing for SAP ERP under Materials Management → Purchasing → Purchase Order → Set up Stock Transport Order → Define Shipping Data for Plants. Alternatively, display table T001W. Check that a customer for example 491000 is assigned.
• •
Vendors for example 491000 Check that vendor is assigned to plant 1000, for example 491000 On the SAP Easy Access screen, choose Logistics → Materials Management → Purchasing → Master Data → Vendor → Purchasing → Display (Current) . Alternatively, choose transaction MK03. On the Purchasing Data screen, select → Purchasing Data. Alternatively, display table T001W. Check that a vendor for example 491000 is assigned.
•
Materials
In the ERP system you have defined an object structure as shown below, for example. SAP ERP Warehouse EWM
Plant 1000
Storage Location YAFS
Storage Location YROD
Shipping Point 1000 (Shipping Point)
Shipping Point 1000 (Goods Receiving Point)
Customer EWMCUST001
Vendor EWMVEND001
Procedure Ensure that you follow the steps in this order:
© SAP AG
Page 8 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
1. Activating Business Functions in Switch Framework 2. Creating an RFC User in ERP 3. Naming the Logical System for the Connection to SAP EWM 4. Assigning a Logical System to a Client 5. Specify the SAP APO Release 6. RFC Destinations 7. Setting the Target System and Queue Type 8. qRFC Monitor Settings 9. Setting User Parameters for Data Transfer 10. Checking Basic Table Entries 11. Extended Inbound Delivery 12. Assigning Warehouse Number to Plant and Storage Location 13. Assigning Shipping Points to Plants 14. Maintaining Shipping Point Assignment to Plant 15. Assigning Goods Receiving Points for Inbound Delivery 16. Organizational Structures in the ERP System 17. Defining Delivery Split by Warehouse Number 18. Activate Business Configuration Sets (BC Sets)
Result Your ERP system has now been configured to connect to SAP SCM.
4.2 Activating Business Functions in Switch Framework You can use this procedure to activate the following business function: •
LE, Extended Warehouse Management Integration (LOG_LE_INTEGRATION) which is prerequisite for the SAP EXTENDED WAREHOUSE MANAGEMENT RAPIDDEPLOYMENT SOLUTION.
For more information, see the business function documentation. This procedure is optional.
Procedure © SAP AG
Page 9 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
SAP NetWeaver → Application Server → System Administration → Switch Framework
Transaction Code
SFW5
2. If a dialog box Security Information is displayed choose Continue. 3. On the Switch Framework: Change Business Function Status screen, choose ENTERPRISE_BUSINESS_FUNCTIONS → LOG_LE_INTEGRATION. 4. Check the 'Planned Status' checkbox then choose Activate Changes.
4.3 Creating an RFC User in ERP You can use this procedure to create a user for the remote function call (RFC) connection of your systems. Contact the system administrator to create the RFC User or to get the relevant information.
Procedure 1. Access the transaction using one of the following navigation options: SAP ERP Menu
Tools → Administration → User Maintenance → Users
Transaction Code
SU01
2. On the User Maintenance: Initial Screen screen, enter RFCDIAUSER in the User field then choose Create. 3. On the Maintain User screen, make the following entries: Field Name
Description
User Action and Values
Comment
Address tab page
Last Name
RFCDIAUSER
Logon Data tab page
User Type
Dialog
Password
for example initial
Profile tab page
Password
For the integration with SAP SCM the relevant profile should be provides by system administrator. See SAP Notes 150315 and 784891. Do not assign too many rights to this technical user. If, for example, technical users for RFC connections have too many authorizations, RFC administrators from the calling system can easily log on to the called system and abuse the technical user’s authorizations. 70% of all attacks on systems
© SAP AG
Page 10 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide come from within the attacked company. Use the profile generator (transaction PFCG) to define an appropriate profile. See also SAP Note 727839.
Default tab page
Logon Language
EN
Decimal Notation
1.234.567,89
Date Format
DD.MM.YYYY
4. Choose Save.
4.4 Naming the Logical System for the Connection to SAP EWM You can use this procedure to name the logical system that is used in the remote function call (RFC) connection to SAP EWM.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components →Extended Warehouse Management →Basic Settings for Setting Up the System Landscape →Name Logical System
Transaction Code
SPRO
2. In the Caution: The table is cross-client dialog box, choose Continue (Enter). 3. On the Change View "Logical Systems": Overview screen, choose New Entries. 4. On the New Entries: Overview of Added Entries screen, make the following entries: Log.System
Name
CLNT e.g ERPCLNT001
ECC Backend for example
CLNT e.g SCMCLNT001
SCM system for example
5. Choose Save. For more information, see the customizing activity documentation.
4.5 Assigning a Logical System to a Client You can use this procedure to assign a logical system to the client in the ERP system for the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components →Extended Warehouse Management →Basic Settings for Setting Up the System Landscape → Assign Logical System to a Client
Transaction Code
SPRO
© SAP AG
Page 11 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. In the Caution: The table is cross-client dialog box, choose Continue (Enter). 3. On the Change View "Clients": Overview screen, select the client number for your ERP client then choose Details. 4. On the Change View "Clients": Details screen, in the Logical System field, enter the logical system for the ERP (created in the previous step), for example ERPCLNT001. For more information, see the customizing activity documentation.
4.6 Specifying the SAP APO Release You can use this procedure to specify the system type and release number of the target system you are connecting to. In this document, SAP Advanced Planning and Optimization (APO) refers to the core interface (CIF) functionality and not to the APO component.
Prerequisites You have named the Logical System for the target system. For more information about the Logical System of the target system, see Naming the Logical System for the Connection to SAP EWM.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components →Extended Warehouse Management →Basic Settings for Setting Up the System Landscape → Specify SAP APO Release
Transaction Code
SPRO
2. In the Caution: The table is cross-client dialog box, choose Continue (Enter) . 3. On the Change View "Systems and Their Types and Releases": Overview screen, choose New Entries. 4. On the New Entries: Overview of Added Entries screen, make the following entries: Field Name
Description
User Action and Values
Comment
Log.System
Logical System of the SCM system
Syst.Type
SAP_APO
Release
701
5. Choose Save. For more information, see the customizing activity documentation.
4.7 RFC Destinations To set up the RFC connection between the ERP system and SAP EWM, carry out the following steps in the order they are given. 1. Defining RFC Destinations in ERP 2. Determining RFC Destinations for Method Calls in ERP
© SAP AG
Page 12 of 64
SAP Best Practices
4.7.1
ERP-EWM Integration (Y31): Configuration Guide
Defining RFC Destinations in ERP
You can use this procedure to define remote function call (RFC) destinations in the ERP system that are used for the connection to the target system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components →Extended Warehouse Management →Basic Settings for Setting Up the System Landscape → Set Up RFC Destination
Transaction Code
SM59
2. On the Configuration of RFC Connections screen, select ABAP Connections then choose Create. 3. On the RFC Destination screen, make the following entries: Field Name
Description
User Action and Values
Comment
RFC Destination
Logical System of the SCM system
Connection Type
3
ABAP Connection
Description
for example SCM system
Technical Settings tab page
Load Balancing
Yes or No
Use preselected value
Target Host
for example iwdf00.wdf.sap.corp
System Number
for example 10
Logon & Security tab page
Trusted System
Yes or No
Use preselected value
SNC
Active or Inactive (use preselected value)
Use preselected value
Language
EN
Optional
Client
For example: 001
User
RFCDIAUSER
Password Unencrypted Password
The password you created in Creating an RFC User in ERP. Not selected
4. Choose Save.
4.7.2 Determining RFC Destinations for Method Calls in ERP You can use this procedure to determine remote function call (RFC) destinations in the ERP system used for method calls.
© SAP AG
Page 13 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
SAP NetWeaver → Application Server → IDoc Interface/Application Link Enabling (ALE) → Communication → Determine RFC Destinations for Method Calls
Transaction Code
BD97
2. On the Assign RFC Destinations for Synchronous Method Calls screen, select the relevant SCM logical system, for example SCMCLNT001. 3. Choose Standard BAPI Destination. 4. In the dialog box, enter the RFC destination created previously (see Defining RFC Destinations in ERP) in the RFC destination for BAPI calls field. 5. Choose Continue (Enter). 6. Choose Save. For more information, see the customizing activity documentation.
4.8 Setting the Target System and Queue Type You can use this procedure to set the target system and queue type for the transfer of data.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components → Extended Warehouse Management → Basic Settings for Setting Up the System Landscape → Set Target System and Queue Type
Transaction Code
SPRO
2. On the Change View “Target Systems, Operation Mode and Queue Type“: Overview screen, check that the data for the relevant logical system exist or enter the data as shown in the following table: Field Name
Description
User Action and Values
Comment
Log.System
Logical System
for example SCMCLNT001
Q-Type
Queue type
I (Inbound queue)
3. Save your entries.
4.9
qRFC Monitor Settings
The ERP system and SAP EWM communicate by means of remote function calls (RFCs). To maintain the settings for the inbound and outbound queues, carry out the following steps in the order they are given. 1. Maintaining qRFC Monitor (QIN Scheduler) Settings in ERP 2. Maintaining qRFC Monitor (QOUT Scheduler) Settings in ERP 3. Registering Display Programs for Application Log in ERP
© SAP AG
Page 14 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
4.9.1 Maintaining qRFC Monitor (QIN Scheduler) Settings in ERP You can use this procedure to make settings for inbound queues in the qRFC monitor (QIN Scheduler) of the ERP system.
Procedure 1. In the ERP system, on the SAP Easy Access screen, call transaction SMQR. 2. On the qRFC Monitor (QIN Scheduler) screen, choose Register without activation. 3. Enter the data as shown in the following table: Field Name
Description
User Action and Values
Comment
Queue Name
We recommend that you use *
Mode
D
Max. Runtime
60
Destination
- leave blank -
Attempts
30
Pause
300
4.9.2 Maintaining qRFC Monitor (QOUT Scheduler) Settings in ERP You can use this procedure to make settings for outbound queues in the qRFC monitor (QOUT Scheduler) of the ERP system.
Procedure 1. In the ERP system, on the SAP Easy Access screen, call transaction SMQS. 2. On the qRFC Monitor (QOUT Scheduler) screen, choose Register without activation. 3. Enter the data as shown in the following table: Field Name
Description
User Action and Values
Comment
Destination
for example SCMCLNT001
Max.Conn.
10
Max. Runtime
60
W/o tRFC
- leave blank -
4.9.3 Registering Display Programs for Application Log in ERP You can use this procedure to register display programs for application log in the ERP system.
Procedure 1. In the ERP system, on the SAP Easy Access screen, call transaction SMQE.
© SAP AG
Page 15 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. From the drop down menu on the top of the screen, choose Edit →Register Display Program. 3. Enter the queue and program names as shown in the following table. Queue Name
Program Name
CF*
CIFQEV02
DLV*
/SPE/QUEUE_DISPLAY_TOOLS
DLW*
/SPE/QUEUE_DISPLAY_TOOLS
EWM*
/SPE/QUEUE_DISPLAY_TOOLS
QI*
/SPE/QUEUE_DISPLAY_TOOLS
QM*
/SPE/QUEUE_DISPLAY_TOOLS
X*
RSXMB_SHOW_ENTRY
4.10 Setting User Parameters for Data Transfer You can use this procedure to set user parameters that are needed for data transfer using the APO core interface (CIF).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components → Extended Warehouse Management → Basic Settings for Data Transfer → Set User Parameters
Transaction Code
CFC2
2. On the Change View “Maintenance View for CIFGPARAMS”: Overview screen, check the entries. If necessary, create an entry with the following data: Field Name
Description
User Action and Values
User Name
RFCDIAUSER
RFC Mode
Q
Logging
D
Debug
- leave blank -
Comment
3. Save your entries. For more information, see the customizing activity documentation.
4.11 Checking Basic Table Entries You can use this procedure to check ISO codes. ISO codes need to be checked periodically as they may have changed and may need to be deleted. Check that the entries you use in the warehouse processes are identical in all systems, which are part of your system landscape.
Procedure 1. On the SAP Easy Access screen, execute transaction code SCMP.
© SAP AG
Page 16 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. Compare the information in the following tables in all of the systems, for example SAP ERP and SAP SCM: Table
Field
Description
T006
ISOCODE
Unit of measure
T002
LAISO
Language keys
TCURC
ISOCD
Currency codes
T005
INTCA
Countries
3. If necessary, using transaction SM30 to adjust the tables in all systems and provide the same data in all systems.
4.12 Additional Material Master Attributes Additional data can be saved with material master records. To save this data, additional material master screens have to be activated and maintained. For this purpose, carry out the following steps in the order they are given. 1. Activating Additional Material Master Screens 2. Maintaining Additional Screen Sequences If you have specified an output format for product numbers in the ERP system, you have to specify the same output format for product numbers in SAP EWM.
4.12.1
Activating Additional Material Master Screens
You can use this procedure to activate additional material master screens in the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu
Tools → Customizing → Business Configuration Sets → Activation of BC Sets
Transaction Code
SCPR20
2. On Business Configuration Sets: Activation screen, in the BC set field enter /SPE/MATERIAL_SCREENS.
This BC set delivers additional entries for screen sequence 21 of the material master maintenance. 3. Choose Activate BC Set (F7). 4. In the Prompt for Customizing request dialog box, enter a customizing request number. 5. In the Activation Options dialog box, select the following radio buttons: o
Overwrite All Data
o
Default Mode (Recommended)
6. Choose Continue Activation (Enter).
© SAP AG
Page 17 of 64
SAP Best Practices
4.12.2
ERP-EWM Integration (Y31): Configuration Guide
Maintaining Additional Screen Sequences
You can use this procedure to maintain the screen sequence for the additional material master screens in the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics - General → Material Master → Configuring the Material Master → Maintain Order of Main and Additional Screens.
Transaction Code
OMT3R
2. On Change View “Screen Order”: Overview screen, select sequence 21 and choose Details (Ctrl + Shift + F2). 3. For screen number 56, enter 300. 4. For screen number 57, enter 310. 5. Choose Save.
4.13 Extended Inbound Delivery 4.13.1 Assigning the Profile for Extended Inbound Delivery Processing (VL60) Users When creating inbound deliveries in ERP with transaction VL60, your user must be assigned to a UI profile for extended inbound delivery processing. When creating inbound deliveries in EWM, you navigate automatically to transaction VL60 in the ERP system with the RFC user. The RFC user must also be assigned to a UI profile for extended inbound delivery processing. You can use this procedure to assign normal users and the RFC user to a user group and the user group to an existing UI profile for extended inbound delivery processing.
Prerequisites You created an RFC user in the ERP system. For more information, see Creating an RFC User in ERP.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution→ Service Parts Management (SPM) → Extended Inbound Delivery Processing (SPM) → UI Profiles→ Maintain Profile Assign Users
Transaction Code
VL60P2
2. On Change View “User Groups in GR Dialog Automotive”: Overview screen, choose New Entries. 3. Create a user group, for example VL60ALL, and choose Enter. 4. Select the user group you created. 5. In the dialog structure, double-click Assignment User - User Groups. 6. Choose New Entries.
© SAP AG
Page 18 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
7. Enter all users working directly with transaction VL60 in ERP. Additionally enter the RFC user, for example RFCDIAUSER. 8. For each user, select the Default Group checkbox. 9. In the dialog structure, double-click Assignment Profiles - User Groups. 10. Choose New Entries. 11. Assign profile VL60ALL and select the Default Profile checkbox. 12. Choose Save.
4.14 Assigning Warehouse Number to Plant and Storage Location You can use this procedure to assign a warehouse number to the plant and storage location.
Prerequisite In the ERP system, you have created the following objects: • •
A plant Storage location(s)
•
A warehouse number
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Enterprise Structure → Assignment → Logistics Execution → Assign warehouse number to plant/storage location
Transaction Code
SPRO
2. On Change View “MM-IM Storage Location LE-WM Warehouse Number”: Overview screen, make the following assignments: Plant
SLoc
WhN
1000
YAFS
EWM
1000
YROD
EWM
If Storage Location YAFS and YROD do not exist for plant 1000, create them in the ERP IMG under Enterprise Structure → Definition → Material Management → Maintain storage location. The description for the storage locations are: o YAFS: Avail. For Sale o
YROD: Recv. on Dock
3. Choose Save.
4.15 Assigning Shipping Points to Plants You can use this procedure to assign shipping points to plants. One shipping point can belong to several plants.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP
© SAP AG
Enterprise Structure → Assignment →Logistics Execution →Assign
Page 19 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
system)
shipping point to plant
Transaction Code
SPRO
2. On the Shipping Points → Plants: Overview screen, assign all possible combinations to the plant, for example to plant 1000 as shown below. Plant
Shipping Point
1000
1000
1000
100R
3. Choose Save.
4.16 Maintaining Shipping Point Determination You can use this procedure to allocate the shipping points to the desired combinations of shipping condition and loading group for each plant.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution →Shipping →Basic Shipping Functions →Shipping Point and Goods Receiving Point Determination →Assign Shipping Points
Transaction Code
SPRO
2. On Change View “Shipping Point Determination”: Overview screen, assign the shipping points to the plant, for example to plant 1000, with all possible combinations of for example plant 1000, proposed shipping point for example 1000, the relevant loading group and the relevant Shipping Condition. For the SAP Extended Warehouse Management rapid-deployment solution, it is necessary to have at least the following combinations: SC
LGrp
Plant
PrShP
0001
1000
1000
1000
1000
3. Choose Save. For more information, see the customizing activity documentation.
4.17 Assigning Goods Receiving Points for Inbound Delivery You can use this procedure to assign one or several goods receiving points to the combination of plant and storage location. If you do not carry out this step, transaction VL60 displays an error message.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution →Shipping →Basic Shipping Functions →Shipping Point and Goods Receiving Point Determination →Assign Goods Receiving Points for Inbound Deliveries
Transaction Code
SPRO
© SAP AG
Page 20 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. On Change View “Assign Shipping Point as Goods Receiving Point to Plant/S screen, make the following entries: Plant
Stor. Loc.
Shipping Point
Sequence Number
1000
YAFS
1000
1
1000
YROD
1000
1
3. Choose Save.
4.18 Organizational Structures in the ERP System Organizational structures in the ERP system reflect the legal and organizational structure of your company. To customize organizational structures in the ERP system, carry out the following steps in the order they are given. 1. Maintaining Extended Warehouse Management-Specific Parameters 2. Defining the Queue for Extended Warehouse Management 3. Logging Sent and Received Messages (optional) 4. Registering the Navigation from the Queue 5. Generating the Distribution Model for ERP to EWM
4.18.1 Maintaining Extended Warehouse ManagementSpecific Parameters You can use this procedure to maintain EWM-specific parameters.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of EWM Connectivity→ Maintain Extended WM-Specific Parameters
Transaction Code
SPRO
2. On Change View “Extended Warehouse Management system”: Overview screen, choose New Entries. 3. On the New Entries: overview of Added Entries screen, make the following entry: Field Name
User Action and Values
Comment
WhN
EWM
Warehouse to be mapped to EWM
Ext. WM
ERP with Extended Warehouse Management
Comm. WM
Queued and Serialized Asynchronous RFC
© SAP AG
Description
Page 21 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
UD Distribution Immediately at Document Creation
Dist. Mode
Select this checkbox if to allow serial numbers in a decentralized WM
SN Dec. WM BatchDetEW GR fr. EWM Only
In the SAP Extended Warehouse Management rapid-deployment solution, neither unchecked deliveries nor serial numbers are used. 4. Choose Save. For more information, see the customizing activity documentation.
4.18.2 Defining the Queue for Extended Warehouse Management This procedure enables you to define the queue for Extended Warehouse Management (EWM).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of EWM Connectivity → Define Queue for Transfer to Extended WM
Transaction Code
SPRO
2. On the Change View “Configuration of EWM communication via Queue”: Overview screen, choose New Entries. 3. On the New Entries: overview of Added Entries screen, make the following entries: Field Name
User Action and Values
Comment
Receiver
,
The SCM logical system, for example SCMCLNT001
Queue Type
Inbound queue
Agg SQueue
No aggregation
MQueue Act
Mass Queue disabled (=> Single Queues)
MQueue Par 4. Choose Save.
© SAP AG
Description
1
Page 22 of 64
SAP Best Practices
4.18.3
ERP-EWM Integration (Y31): Configuration Guide
Logging Sent and Received Messages
This procedure allows you to log sent and received messages. This procedure is optional.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of EWM Connectivity →Log Sent and Received Messages
Transaction Code
SPRO
2. On Change View “Log messages between ERP and EWM”: Details screen, choose New Entries. 3. For Log received and Log send, select log success + error messages from the pulldown list. 4. Choose Save. For more information, see the customizing activity documentation.
4.18.4
Registering the Navigation from the Queue
This procedure allows you to register the navigation from a queue to the application log.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of EWM Connectivity → Register Navigation from Queue
Transaction Code
SPRO
2. On the Register Queue Navigation screen, if the Register radio button is not selected, choose Register and Execute. If it is already selected, no action is necessary. For more information, see the customizing activity documentation.
4.18.5 EWM
Generating the Distribution Model for ERP to
You can use this procedure to generate the distribution model for the ERP system to Extended Warehouse Management (EWM).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution → Extended Warehouse Management Integration → Basic Setup of EWM Connectivity → Generate Distribution Model ERP =>EWM
Transaction Code
/n/SPE/OL19
2. On the Customizing distribution model ERP to EWM screen, make the following entries: Field Name
© SAP AG
Description
User Action and Values
Comment
Page 23 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Warehouse Number
EWM
EWM's Logical System
Distribution Model view
EWM
Objects
Both
The SCM logical system, for example SCMCLNT001
Create entries
Action 3. Choose Execute.
A protocol for all selected warehouses is created.
4.19 Defining Delivery Split by Warehouse Number You can use this procedure to define settings so that deliveries in one warehouse are created automatically for specific warehouse numbers and delivery types, and if necessary, a delivery split is completed.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Logistics Execution →Shipping →Deliveries →Define Split Criteria for Deliveries →Delivery Split by Warehouse Number
Transaction Code
SPRO
A Choose Activity selection screen appears. 2. On Choose Activity screen, choose Define delivery split per delivery type. 3. On the Change View "Display Split for Warehouse Number per Delivery Type" Overview screen, select the Delivery Split -WhNo checkbox for the delivery type EL LF and LO. 4. Save your settings. 5. Choose Back to return to the previous screen. 6. Choose Determine the delivery split per warehouse number. 7. Select the Deliv.split by whse number checkbox for warehouses you use in SAP EWM. 8. Save your settings.
5
Configuration Settings for SAP SCM
You can use this process to make configuration settings in SAP SCM that are needed for the integration with the ERP system. By connecting the two applications, you can transfer data from the SAP EWM component, which is relevant for processes in the ERP system, to the ERP system.
Prerequisites
© SAP AG
Page 24 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
You have installed and correctly configured the following systems on SAP enhancement package 2 for SAP NetWeaver 7.0: • •
SAP ERP 6.0 including enhancement package 5 SAP SCM 7.0 including SAP enhancement package 1 for SAP SCM 7.0
You have configured the ERP system for connection to SAP SCM, see Configuration Settings for the ERP System.
Procedure Ensure that you follow the steps in this order: 1. Creating an RFC User in SCM 2. Naming the Logical System for the Connection to SAP ERP 3. Assigning a Logical System to a Client 4. Define RFC Destinations 5. Maintaining Business System Groups 6. Assigning Logical System and Queue Types 7. Determining RFC Destinations for Method Calls in EWM 8. Maintenance of qRFC Monitor Settings 9. Defining a Separate Business System 10. Defining the Business System 11. Defining Outbound Communication 12. Setting Control Parameters for the ERP Version Control 13. Delivery Processing 14. Defining Warehouse Numbers 15. Mapping Warehouse Numbers 16. Activating Business Add-Ins (BAdIs) (optional) 17. Defining the Transportation Group (optional) 18. Specifying Output Format of Product Number 19. Checking the SAP APO Model and Planning Version
Result You have configured SAP SCM to connect with the ERP system.
© SAP AG
Page 25 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
5.1 Creating an RFC User in SCM You can use this procedure to create an RFC user in SAP SCM for the integration with SAP ERP.
Procedure 1. Access the transaction using one of the following navigation options: SAP SCM Menu
Tools →Administration →User Maintenance →Users
Transaction Code
SU01
2. In the User field, enter for example RFCDIAUSER. 3. Choose Create. 4. On the Maintain User screen, make the following entries: Field Name
Description
User Action and Values
Comment
Address tab page
Last Name
RFCDIAUSER
Logon Data tab page
User Type
Dialog
Password
for example initial
If you are connecting SAP EWM to an ERP system, ask your system administrator for further details regarding the User Type
Profile tab page
Profile
For the integration with SAP ERP the relevant profile should be provides by system administrator. See SAP Notes 150315 and 784891. Do not assign too many rights to this technical user. If, for example, technical users for RFC connections have too many authorizations, RFC administrators from the calling system can easily log on to the called system and abuse the technical user’s authorizations. 70% of all attacks on systems come from within the attacked company. Use the profile generator (transaction PFCG) to define an appropriate profile. See also SAP Note 727839.
Roles tab page
© SAP AG
Page 26 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Role
Enter role which is provided by system administrator.
Default tab page
Logon Language
EN
Decimal Notation
1.234.567,89
Date Format
DD.MM.YYYY
5. Choose Save. Do not change the password of this user because it is used in RFC connections.
5.2 Naming the Logical System for the Connection to SAP ERP You can use this procedure to name the logical system that is used in the remote function call (RFC) connection to SAP ERP.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SCM Basis → Integration → Basic Settings for Creating the System Landscape → Name Logical Systems
Transaction Code
SPRO
2. In the Caution: The table is cross-client dialog box, choose Continue (Enter) . 3. On the Change View "Logical Systems": Overview screen, choose New Entries. 4. On the New Entries: Overview of Added Entries screen, make the following entries: Log.System
Name
CLNT e.g ERPCLNT001
ECC Backend for example
CLNT e.g SCMCLNT001
SCM system for example
5. Choose Save. For more information, see the customizing activity documentation.
5.3 Assigning a Logical System to a Client You can use this procedure to assign a logical system to the client in SAP SCM for SAP SCM.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SCM Basis → Integration → Basic Settings for Creating the System Landscape → Assign Logical Systems to a Client
Transaction Code
SPRO
© SAP AG
Page 27 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. In the Caution: The table is cross-client dialog box, choose Continue (Enter). This is a cross-client activity. 3. On Change View “Clients”: Overview screen, check whether the logical system for the SCM client exists, for example SCMCLNT001.
If it does not exist, define the logical system for the ERP client first. For more information about how to define a logical system, see Naming the Logical System for the Connection to SAP ERP. 4. On the Change View "Clients": Overview screen, choose the client number of your SCM system then choose Details. 5. On the Change View "Clients": Details screen, make the assignment in the Logical System field. For more information, see the customizing activity documentation.
5.4 Defining RFC Destinations in SCM You can use this procedure to define remote function call (RFC) destinations that are used for the connection to the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SCM Basis →Integration →Basic Settings for Creating the System Landscape →Set Up RFC Destination
Transaction Code
SM59
2. On the Configuration of RFC Connections screen, select ABAP Connections. 3. Choose Create. 4. On the RFC Destination screen, make the following entries: Field Name
Description
User Action and Values
Comment
RFC Destination
Logical System of the ECC system
Connection Type
3
ABAP Connection
Description
for example ECC system
Technical Settings tab page
Load Balancing
Yes or No
Use preselected value
Target Host
for example iwdf00.wdf.sap.corp
System Number
for example 10
Logon & Security tab page
Trusted System
Yes or No
Use preselected value
SNC
Active or Inactive (use
Use preselected value
© SAP AG
Page 28 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide preselected value)
Language
EN
Optional
Client
For example: 001
User
RFCDIAUSER
Password Current User
The password you created in Creating an RFC User in ERP. Not selected
5. Choose Save.
5.5 Maintaining Business System Groups You can use this procedure to maintain business system groups (BSGs).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SCM Basis → Integration → Basic Settings for Creating the System Landscape → Maintain Business System Group
Transaction Code
SPRO
2. On Change View “Business System Group”: Overview screen, enter the name of the business system group for the ERP system, for example ERP001.
We recommend that you enter a name that relates to the system and the client you are integrating. 3. Choose Save. For more information, see the customizing activity documentation.
5.6 Assigning Logical System and Queue Types You can use this procedure to assign the logical system and queue types to a business system group (BSG).
Prerequisites You have assigned all systems that are part of your system landscape to the same BSG since only one ERP System is used for the SAP Extended Warehouse Management rapiddeployment solution.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SCM Basis → Integration → Basic Settings for Creating the System Landscape → Assign Logical System and Queue Type
Transaction Code
SPRO
2. On the Change View “Assignment of Logical System to Business System Group”: Overview screen, choose New Entries.
© SAP AG
Page 29 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
3. On the New Entries: Overview of Added Entries screen, make the following entries: Business System Group
Logical System
SAP System
Release
Queue Type
ERP001
SCMCLNT001
X
Inbound Queues
ERP001
ERPCLNT001
X
Inbound Queues
4. Choose Save.
5.7 Determining RFC Destinations for Method Calls in EWM You can use this procedure to determine remote function call (RFC) destinations used for method calls.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
SAP NetWeaver → Application Server → IDoc Interface/Application Link Enabling (ALE) → Communication → Determine RFC Destination for Method Calls
Transaction Code
BD97
2. On the Assign RFC Destinations for Synchronous Method Calls screen, select the relevant ECC logical system, for example ERPCLNT001. 3. Choose Standard BAPI destination. 4. In the dialog box, enter the RFC destination created previously (see Defining RFC Destinations in SCM) in the RFC destination for BAPI calls field. 5. Choose Continue (Enter). 6. Choose Save. For more information, see the customizing activity documentation.
5.8 Maintenance of the qRFC Monitor Settings To maintain the settings for the qRFC Monitor for both inbound and outbound queues, carry out the following steps in the order they are given. 1. Maintaining qRFC Monitor (QIN Scheduler) Settings in EWM 2. Maintaining qRFC Monitor (QOUT Scheduler) Settings in EWM
5.8.1 Maintaining qRFC Monitor (QIN Scheduler) Settings in EWM You can use this procedure to make settings for inbound queues in the qRFC monitor (QIN Scheduler).
Procedure 1. In SAP SCM, on the SAP Easy Access screen, call transaction SMQR.
© SAP AG
Page 30 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. On the qRFC Monitor (QIN Scheduler) screen, choose Register without activation. 3. Enter the data as shown in the following table: Field Name
Description
User Action and Values
Comment
Queue Name
We recommend that you use *
Mode
D
Max. Runtime
60
Destination
- leave blank -
Attempts
30
Pause
300
5.8.2 Maintaining qRFC Monitor (QOUT Scheduler) Settings in EWM You can use this procedure to make settings for outbound queues in the qRFC monitor (QOUT Scheduler).
Procedure 1. In SAP SCM, on the SAP Easy Access screen, call transaction SMQS. 2. On the qRFC Monitor (QOUT Scheduler)screen, choose Register without activation. 3. Enter the data as shown in the following table: Field Name
Description
User Action and Values
Comment
Destination
for example ERPCLNT001
Max.Conn.
10
Max. Runtime
60
W/o tRFC
- leave blank -
5.9 Defining a Separate Business System You can use this procedure to name the business system of the system you have installed SAP EWM on.
Procedure In this integration scenario, SAP EWM is a component of SAP SCM. Therefore, you name the business system of SAP SCM. 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
Extended Warehouse Management → Interfaces → ERP Integration → General Settings→ Define Own Business System
Transaction Code
SPRO
2. On Change View “Name of Own Business System”: Overview screen, choose New Entries.
© SAP AG
Page 31 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
3. On the New Entries: Overview of Added Entries screen, enter the name of your own business system, for example SCM_001. For more information, see the customizing activity documentation.
5.10 Defining the Business System You can use this procedure to name the business system and all systems that are part of the system landscape.
Prerequisites You have defined the logical systems.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Define Business System
Transaction Code
SPRO
2. On the Change View “Buffer for SLD Data of Business Systems”: Overview screen, create a new entry for each system that is part of your system landscape. For example, enter the following values: Business System
Logical System
Manual Maint.
for example ERP_001
for example ERPCLNT001
Flag set. Event has occurred.
for example SCM_001
for example SCMCLNT001
Flag set. Event has occurred.
3. Choose Save. For more information, see the customizing activity documentation.
Result All named business systems are added to table /SCMB/TBUSSYS. If you use a System Landscape Directory (SLD), you need to ensure that the key name of the business system (BSKEY) used in SLD is the same as the one used in table /SCMB/TBUSSYS when the Manual Maint. field is set to Flag is Not Set.
5.11 Defining Outbound Communication You can use this procedure to define outbound communication.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
© SAP AG
Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Control for RFC Queue
Page 32 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Transaction Code
SPRO
2. On the Change View “qRFC Configuration for Communication ERP EWM”: Overview screen, choose New Entries. 3. On the New Entries: Details of Added Entries screen, make the following entries: Field Name
Description
User Action and Values
Business System
for example ERP_001
Queue Type
Inbound Queues
Aggr. Single Queues
No Aggregation
Mass Queue Act.
Comment
Mass Queue Deactivated (=> Individual Queue)
Parallel Mass Queues 4. Choose Save. For further information, see the IMG Documentation.
5.12 Setting Control Parameters for the ERP Version Control You can use this procedure to set control parameters for the ERP version control.
Prerequisites You have defined a business system, see Defining the Business System.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM system)
Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control
Transaction Code
SPRO
2. On the Change View “Recipient-Dependent Control of Processes”: Details screen, choose New Entries. 3. On the New Entries: Details of Added Entries screen, make the following entries: Field Name
Description
Business System SAP Release
User Action and Values
Comment
for example ERP_001 603
SAP ECC, Release 6.0 EHP3 and higher
Qulity Inspection section Quality Confirmation for
© SAP AG
Do Not Communicate Inspection Results to
Page 33 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Returns 4. Choose Save.
ERP
For more information, see the customizing activity documentation.
5.13 Delivery Processing To ensure that the delivery process can take place, number range intervals and table entries need to be consistent in both SAP EWM and the ERP system. To ensure consistency, check that the settings made in the following topics correspond in both systems. If they do not correspond, define them accordingly. Carry out the following steps in the given order. 1. Defining Number Range Intervals 2. Defining Number Ranges for ERP Documents 3. Defining the Delivery Priority 4. Defining Shipping Conditions 5. Defining Incoterms
5.13.1
Defining Number Range Intervals
You can use this procedure to define number range intervals.
Prerequisites You have defined number ranges in the ERP system, see Number Ranges for Deliveries. In the customizing for SAP SCM, define the intervals for the following items: • •
Define Number Ranges Interval for Technical Keys Define Number Ranges Interval for Outbound Deliveries
•
Define Number Ranges Interval for Inbound Deliveries and Outbound Del. Orders
•
Define Number Range Intervals for Expected Goods Receipt (Only if EGR is used)
Procedure Define Number Ranges Interval for Technical Keys 1. Access the transaction using one of the following navigation options: IMG Menu (SCM Extended Warehouse Management → Cross-Process Settings → System) Delivery Processing → Number Ranges → Define Number Range Intervals for Technical Key Transaction Code
SPRO
2. On the Number range for technical key screen, choose Change Intervals. 3. On the Maintain Number Range Intervals screen, choose Insert Interval (Shift + F1) and make the following entries:
© SAP AG
Page 34 of 64
SAP Best Practices NR Object
ERP-EWM Integration (Y31): Configuration Guide No.
Technical key 01 4. Choose Insert (Enter).
From number
To number
00000000000000000001
09999999999999999999
Ext
Define Number Ranges Interval for Outbound Delivery 1. Access the transaction using one of the following navigation options: IMG Menu (SCM Extended Warehouse Management → Cross-Process Settings → System) Delivery Processing → Number Ranges → Define Number Range Intervals for Outbound Deliveries Transaction Code
SPRO
2. On the Outbound Delivery screen, choose Change Intervals. 3. On the Maintain Number Range Intervals screen, choose Insert Intervel (Shift + F1) and make the following entries: NR Object
No.
From number
To number
Outbound Delivery
01
00000000000000000001
00000000009999999999
00000000010000000000
00000000019999999999
Outbound Delivery 02 4. Choose Insert (Enter).
Ext X
Define Number Ranges Interval for Inbound Deliveries and Outbound Del. Orders 1. Access the transaction using one of the following navigation options: IMG Menu (SCM Extended Warehouse Management → Cross-Process Settings → System) Delivery Processing → Number Ranges → Define No. Range Intervals for Inbound Deliveries and Outbound Del. Orders Transaction Code
SPRO
2. On the Inb.Del.,outb.Del. Order, Posting Change, Stock Transfer screen, choose Change Intervals. 3. On the Maintain Number Range Intervals screen, choose Insert Intervel (Shift + F1) and make the following entries: NR Object
No.
From number
To number
Processing Document
01
00000000000000000001
00000000009999999999
00000000010000000000
00000000019999999999
Processing 02 Document 4. Choose Insert (Enter).
Ext
X
Define Number Range Intervals for Expected Goods Receipt 1. Access the transaction using one of the following navigation options: IMG Menu (SCM Extended Warehouse Management → Cross-Process Settings → System) Delivery Processing → Number Ranges → Define Number Range Intervals for Expected Goods Receipt Transaction Code
SPRO
2. On the Expected Goods Receipt screen, choose Change Intervals.
© SAP AG
Page 35 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
3. On the Maintain Number Range Intervals screen, choose Insert Intervel (Shift + F1) and make the following entries: NR Object
No.
Expected GR 01 4. Choose Insert (Enter).
From number
To number
0000000001
9999999999
Ext
You only define Number Range Intervals for Expected Goods Receipt if EGR is used for your business processes.
5.13.2
Defining Number Ranges for ERP Documents
You use this procedure to define number ranges for delivery documents created in Extended Warehouse Management (EWM) and that are transferred to the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Interfaces → ERP Integration → Delivery Processing → Define Number Ranges for ERP Documents
Transaction Code
SPRO
2. On the Document Number for ERP System screen, choose Change intervals. 3. On the Maintain Number Range Intervals screen, choose Insert Intervel (Shift + F1) and make the following entries: NR Object
No.
ERP Document 01 Number 4. Choose Insert (Enter).
From number
To number
1000000000
1999999999
Ext
Ensure that you assign number ranges and number range intervals that differ from those of the ERP system. If they do not differ, problems arise while transferring the data. The number ranges for deliveries in the ERP system can be found under the following customizing path in the ERP system: Logistics Execution → Shipping → Deliveries → Define Number Ranges for Deliveries. Consider the number range numbers, for example 17 (outbound deliveries) and for example 41 (inbound deliveries), when checking the number range intervals in the ERP system and EWM.
5.13.3
Defining the Delivery Priority
You can use this procedure to define the delivery priority.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Cross-Process Settings → Delivery Processing → General Settings → Define Delivery Priority
Transaction Code
SPRO
© SAP AG
Page 36 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
2. On Change View “Delivery Priority”: Overview screen, check that the entries (contained in the table /SCDL/TDLVPRIO_V) of SAP SCM are consistent with the entries (contained in the table V_TPRIO) of the ERP system. You can use Transaction Code SM30 to check the customizing entries in both systems and adjust if there are inconsistencies.
5.13.4
Defining Shipping Conditions
You can use this procedure to define the shipping conditions.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Cross-Process Settings → Delivery Processing → General Settings → Define Shipping Conditions
Transaction Code
SPRO
2. On Change View “Shipping Condition”: Overview screen, check that the entries (contained in the table /SCDL/T SRVLVL) of SAP SCM are consistent with the entries (contained in the table V_TVSB) of the ERP system. You can use Transaction Code SM30 to check the customizing entries in both systems and adjust if there are inconsistencies.
5.13.5
Defining Incoterms
You can use this procedure to define international commercial terms (incoterms).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Cross Process Settings → Delivery Processing → General Settings → Define Incoterms
Transaction Code
SPRO
2. On the Change View “Incoterms”: Overview screen, check that the entries (contained in the table /SCMB/TSINC) of SAP SCM are consistent with the entries (contained in the table V_TINC)of the ERP system. You can use Transaction Code SM30 to check the customizing entries in both systems and adjust if there are inconsistencies.
5.14 Defining Warehouse Numbers You can use this procedure to define warehouse numbers.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Master Data → Define Warehouse Numbers
Transaction Code
SPRO
2. On the Change View “Define Warehouse Number”: Overview screen, enter the Warehouse Number, for example YEWM, and an appropriate Description for the warehouse.
© SAP AG
Page 37 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
3. Choose Save. For more information, see the customizing activity documentation.
5.15 Mapping Warehouse Numbers You can use this procedure to map warehouse numbers. These assignments are necessary to select a warehouse number in the core interface (CIF) integration model.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Interfaces → ERP Integration → General Settings → Map Warehouse Numbers from ERP system to EWM System
Transaction Code
SPRO
2. On the Change View “Mapping for Warehouse Number”: Overview screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, make the following entries: Field Name
Description
User Action and Values
Business System
for example ERP_001
WNoERP
EWM
Warehouse Number
YEWM
Comment
The warehouse number you have defined in previous step.
4. Choose Save.
5.16 Activating Business Add-Ins (BAdIs) By activating the Business Add-Ins (BAdIs) for locations or products, the system adds a suffix or a prefix, to the locations and products of the ERP system before storing them in SAP EWM. In this way, you can distinguish the following data: • •
Data coming from different ERP systems Data coming from one ERP system that has the same name but represents different objects, such as shipping points and plants
To activate the BAdIs, see the following procedures.
5.16.1 Activating BAdI: Inbound Processing for Location You can use this procedure to activate the Business Add-In (BAdI) for the inbound processing for locations. You must activate the following BAdIs if: •
you want to connect more than one ERP system to SAP EWM or;
© SAP AG
Page 38 of 64
SAP Best Practices •
ERP-EWM Integration (Y31): Configuration Guide
you use the same names for different objects, such as shipping points and plants.
If you do not activate this BAdI, locations with the same name, such as plants or shipping points, are not transferred using the core interface (CIF). This results in relevant data missing for the integration scenario. For the SAP Extended Warehouse Management rapid-deployment solution, it is mandatory to activate the BadI adding location prefixes to the locations to distinguish between for example shipping points and plants (SP1000, PL1000). The following table shows the prefixes for the location types used by the BAdI: Location Type
Name
Prefix Added
1001
Plant
PL
1002
Distribution Center
DC
1003
Shipping Point
SP
1005
Transportation Zone
- no prefix -
1007
MRP Area
MR
1010
Customer
CU
1011
Supplier
SU
1020
Carrier
CA
1040
Store
ST
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
SCM Basis → Integration → BAdIs for Specific Applications → Location and Business Partner → BAdI: Inbound Processing for Location
Transaction Code
SPRO
2. In the Business Add-ins: All Implementations for Definition SMOD_APOCF001 dialog box, select the APOCF001_TYPEDIF implementation. 3. Choose Create. 4. In the Business Add-In Builder: Create Implementation dialog box, in the Implementation Name field, enter a name for your implementation, for example Z_APOCF001_TYPEDIF. 5. Choose Continue (Enter). 6. On the Business Add-In Builder: Change Implementation Z_APOCF001_TYPEDIF screen, In the Implementation Short Text field, enter a description for your implementation, for example Locations of different type with similar names. 7. In the menu, choose Implementation → Activate. 8. The Create Object Directory Entry window opens. You can either
© SAP AG
o
Enter your package and choose Save, or
o
Save the object as a local object by choosing Local Object.
Page 39 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
9. You can copy the source code of the BAdI method delivered in the standard system to your BAdI implementation. For more information about copying the method source code, see Copying the BAdI Method Source Code.
5.16.2
Activating BAdI: Inbound Processing for Product
You can use this procedure to activate the Business Add-In (BAdI) for inbound processing for products to distinguish products from different ERP clients. Activating this BAdI is only necessary if you manage products from different ERP Clients in EWM and therefore NOT necessary for the SAP Extended Warehouse Management rapid-deployment solution.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
SCM Basis →Integration →BAdIs for Specific Applications →Product →BAdI: Inbound Processing for Product
Transaction Code
SPRO
2. In the Business Add-ins: All Implementations for Definition SMOD_APOCF005 dialog box, select the APOCF005_SYSDIF implementation. 3. Choose Create. 4. In the Business Add-In Builder: Create Implementation dialog box, in the Implementation Name field, enter a name for your implementation, for example Z_APOCF005_SYSDIF. 5. Choose Continue (Enter). 6. On the Business Add-In Builder: Change Implementation Z_APOCF005_SYSDIF screen, in the Implementation Short Text field, enter a description for your implementation, for example Identical product numbers from different systems. 7. In the menu, choose Implementation → Activate. 8. The Create Object Directory Entry window appears. You can either, o
Enter your package and choose Save.
o
Save the object as a local object by choosing Local Object.
9. You can copy the source code of the BAdI method delivered in the standard system to your BAdI implementation. For more information about copying the method source code, see step Copying the BAdI Method Source Code.
5.16.3
Copying BAdI Method Source Code
You can use this procedure as an example to copy the source code of the Business Add-In (BAdI) method to the BAdI implementations that you created for the inbound processing for locations. For more information, see Activating BAdI: Inbound Processing for Location.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM
© SAP AG
SCM Basis → Integration → BAdIs for Specific Applications →
Page 40 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
System)
Location and Business Partner → BAdI: Inbound Processing for Location
Transaction Code
SPRO
2. In the Business Add-ins: All Implementations for Definition SMOD_APOCF001 dialog box, select the APOCF001_TYPEDIF implementation. o APOCF001_TYPEDIF (for BAdI inbound processing forlocation) 3. Choose Display. 4. On the Business Add-In Builder: Display Implementation Z_APOCF001_TYPEDIF screen, select the Interface tab, then double-click the BAdI method. 5. Select the source code and copy it. 6. Access the corresponding BAdI implementation you created in the Activating BAdI: Inbound Processing for Location step. On the Interface tab page, double-click the BAdI method and paste the copied source code into it. 7. Save and activate the BAdI implementation.
5.16.4
Activating BAdI: Inbound Processing for Partner
If you use the same number range for customers and vendors and have overlapping numbers within one ERP system or across the ERP systems connected to EWM, you must implement a Business Add-In (BAdI) to allocate different partner numbers in EWM. Note that unlike products and locations, business partner numbers in EWM have the same number of digits (10) as in ERP. For this reason, adding a suffix is not always possible. You have the following options: • • •
If the Business Partners in ERP have a number length shorter than 10 digits, use an external number range, and add a prefix or a suffix (for example, V for vendors, C for customers) to the BP numbers Use an internal number range for business partners in EWM Use an external number range for business partners in EWM but use a BAdI to change either the customer numbers or the vendor numbers (for example, by replacing the first digit of the vendor number by a letter, for example, A for 1, B for 2, and so on)
For the SAP Extended Warehouse Management rapid-deployment solution, this BAdI is NOT implemented. The following settings are only shown as examples.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Number Ranges
Transaction Code
SPRO
Alternatively, you can maintain the number range by: o
© SAP AG
Call transaction SNUM.
Page 41 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
o
On the Number Range Object Maintenance screen, enter BU_PARTNER in the Object field then choose Display.
o
On the Number Range Object: Display screen Choose Goto → Number Ranges.
2. On the Central Business Partner screen, choose Change Intervals. 3. On the Maintain Number Range Intervals screen, choose Insert Intervals (Shift + F1). 4. In the Insert Interval dialog box, and make the following entries. NR Object
No.
From number
To number
Ext
Business partner
01
0000000001
0000489999
Business partner
02
0000490000
0000499999
X
Business partner
AB
A
ZZZZZZZZZZ
X
Business partner
MD
9000000000
9999999999
X
5. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings → Define Groupings and Assign Number Ranges
Transaction Code
SPRO
6. On Change View “BP groupings”: Overview screen, assign the number range to a business partner grouping and set the grouping as standard grouping for internal or external number assignment. Grouping
Short name
Description
Number range
0001
Int.no.assgn mnt
Internal number assignment
01
0002
Ext.No.Assg nmnt
External Number Assignment
02
X
AB
X
MDM0
External
Int.Std. Grping
Ext.Std. Grping
X
X
7. Access the transaction using one of the following navigation options (Optional): IMG Menu (SCM System)
SCM Basis →Integration →BAdIs for Specific Applications →Location and Business Partner →BAdI: Inbound Processing for Business Partner
Transaction Code
SPRO
8. In Business Add-in Builder: Create Implementation dialog box, create an implementation for classic BAdI SMOD_APOCF038 and activate it. SAP does not provide an example implementation as several options are possible. For more information, see the BAdI documentation. The ERP business partner numbers are contained in the table IT_CIF_BP (field PARTNER_ID for business partner number, field TYPE=CRM004 for vendors, field TYPE=CRM002 for customers). The changed number must be filled in table ET_BPMAP. Field EF_MAP_USE must be set to X for the changes to be taken into account.
5.17 Define the Transportation Group You can use this procedure to define the transportation group.
© SAP AG
Page 42 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Procedure This procedure is optional for this integration scenario. If you do define the transportation group, you have to ensure that the settings in both systems are the same. 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
SCM Basis → Master Data → Product → Maintain Transportation Group
Transaction Code
SPRO
2. On Change View “Transportation Group”: Overview screen, choose New Entries. 3. On the New Entries: Overview of Added Entries screen, make the following entries:
Transportation Group
Description
0001
On pallets
0002 4. Choose Save.
In liquid form
5.18 Specifying Output Format of Product Number You can use this procedure to specify the output format of product numbers in EWM. If EWM is connected to one ERP system, you can define the same output format as in ERP. To check the ERP Output Format of Product Numbers, you may access the transaction using one of the following navigation options: Logistics-General → Master Master → Basic Settings → Define Output Format of Material Numbers.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM SCM Basis → Master Data → Product → Specify Output Format of System) Product Number Transaction Code
SPRO
2. On the Change View "Data for Product Number Conversion": Details screen, check the Product No. Length field.
The default setting in SCM system is 40, which means the maximum input and output length of the product number can be up to 40 places. You can also define a template for displaying the product number. If SCM is planning for several ERP systems, it may be necessary to make the identical numbers from different ERP systems unique in SCM. It is usual to use a prefix or suffix to do this.
5.19 Checking the SAP APO Model and Planning Version You can use this procedure to check that an SAP APO model and planning version exist.
© SAP AG
Page 43 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Procedure 1. Access the transaction using one of the following navigation options: SAP Easy Access Tools → ABAP Workbench → Development → ABAP Editor Menu (SCM System) Transaction Code
SE38
2. On the ABAP Editor: Initial Screen screen, In the Program field, enter /SAPAPO/VERSION_CREATE_NO_APO. 3. Choose Execute.
A dialog box appears with the message APO is installed.If you are using APO, create version via transaction /SAPAPO/MVM.Is APO used? Since in the SAP Extended Warehouse Management rapid-deployment solution, APO is not used, choose No to have the program create Planning Model and Planning Version. Otherwise, choose Cancel and check if the planning model 000 and planning version 000 exist by calling transaction /n/SAPAPO/MVM and create accordingly. If you have authorization issues when creating the planning model and planning version, you can use transaction SU03 to check if the authorization objects C_APO_MOD and C_APO_VERS under Authorization Object Class APO are properly assigned to your user profile.
6
Data Transfer to SAP SCM Using the Core Interface (CIF)
You can use this process to transfer specific data from the ERP system to SAP SCM. To transfer the data, you must configure the core interface (CIF).
Prerequisites You have configured the ERP system for connection to SAP SCM. See the Configuration Settings for the ERP System. You have configured SAP SCM for connection to the ERP system. See the Configuration Settings for SAP SCM.
Procedure Ensure that you follow the steps in the given order: 1. Refer to the following information:
© SAP AG
•
Transferring Material Master Data
•
Activating Business Transaction Events (BTEs)
•
Configuring Change Transfers for Master Data
•
Activating ALE Change Pointers for Message Types
Page 44 of 64
SAP Best Practices •
ERP-EWM Integration (Y31): Configuration Guide
Creating the Maximum Model
2. Transfer specific data to SAP EWM: •
You transfer the data for plant, the shipping points, and the data for a business partner (vendor or customer) that you will use for the plant. To transfer the data, carry out the following steps in the order in which they are given: o o
•
Creating an Integration Model in the ERP System Activating the Integration Model in the ERP System
You transfer the data for the materials, customers, and vendors. Transfer of materials, customers and vendors takes place at a later stage of the configuration process (Y33 Central Master Data).
Before carrying out this process step, you have to make further configuration settings in SAP EWM.
Result You have transferred the data for a plant, the shipping points, and a business partner for the plant.
6.1 Assign Warehouse No. to Warehouse No. of Decentralized SCM System You can use this procedure to reduce the amount of material master data being transferred between the ERP system and SAP EWM. By carrying out this procedure, you can select specific warehouse numbers.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Integration with Other mySAP.com Components → Extended Warehouse Management → Assign Warehouse Number to Warehouse Number of Decentralized SCM System
Transaction Code
SPRO
2. On the Change View “Assign Warehouse No. to Warehouse No. of Decent. SCM System”: Overview screen, make the following entries: Field Name
WhN
Description
User Action and Values
Comment
EWM
Warehouse number in the ERP system.
YEWM
The warehouse number you have defined in the SCM system.
WHNDecSCM
3. Choose Save. For more information, see the customizing activity documentation.
© SAP AG
Page 45 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Result The Warehouse Number field appears on the screen for setting up the integration model. You can use this field to specify the relevant warehouse numbers when creating the integration model in the ERP system. For more information about creating the integration model, see Creating an Integration Model in the ERP System.
6.2 Activating Business Transaction Events (BTEs) You can use this procedure to activate business transaction events (BTEs) in the ERP system. By activating BTEs, the system replicates changes to the master data in the ERP system to the target system.
Procedure 1. In the ERP system, on the SAP Easy Access screen, call transaction FIBF. 2. On the SAP Business Framework: Business Transaction Events screen, in the menu, choose Settings → Identification → SAP Applications. 3. Confirm the 'Caution: The table is cross-client' information message. 4. On the Change View "BTE Application Indicator": Overview screen, make the following entries:
Appl. ND-APO NDI
Active
Text
X
New Dimension Plug-In APO
X
New Dimension Integration
5. Choose Save.
6.3 Configuring Change Transfers for Master Data You can use this procedure to ensure that the system landscape reflects all changes to the master data in the ERP system.
Prerequisites You have activated the business transaction events in the ERP system. For more information, see Activating Business Transaction Events (BTEs).
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Transaction Code
Integration with Other mySAP.com Components → Extended Warehouse Management → Basic Settings for Data Transfer → Change Transfer for Master Data → Configure Change Transfer for Master Data. SPRO
1. On the Change Target-System-Independent Settings in CIF screen, make the following entries:
© SAP AG
Page 46 of 64
SAP Best Practices Field Name
ERP-EWM Integration (Y31): Configuration Guide Description
User Action and Values
Material Master Change Transfer
2
Change Transfer for Customers
2
Change Transfer for Vendors
2
Immediate Transfer
X
Re-Read Stock
X
Filter Obj. Req. Reduc. 2. Choose Save.
Comment
X
For more information, see the customizing activity documentation.
Result The system landscape reflects the changes done to the master data in the ERP system.
6.4 Activating ALE Change Pointers for Message Types You can use this procedure to activate ALE change pointers for specific message types so that changes to master data are tracked.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (ERP system)
Transaction Code
Integration with Other mySAP.com Components → Extended Warehouse Management → Basic Settings for Data Transfer → Change Transfer for Master Data → Activate ALE Change Pointers for Message Types SPRO
1. On the Change View “Activate Change Pointers for Message Types”: Overview screen, make the following entries:
Message Type
Active
CIFCUS
X
CIFMAT
X
CIFMTMRPA
X
CIFVEN 2. Choose Save.
X
For more information, see the customizing activity documentation.
© SAP AG
Page 47 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
6.5 Creating the Maximum Model You can use this procedure to set the maximum runtime of the active integration model. We recommend that you make this setting before creating an integration model.
Procedure 1. Access the transaction using one of the following navigation options: SAP Easy Access Tools → ABAP Workbench → Development → ABAP Editor Menu (ERP System) Transaction Code
SE38
2. On the ABAP Editor: Initial Screen screen, in the Program field, enter RCIFIMAX. 3. Choose Execute. 4. On the Generate and reconcile the runtime version of active models screen, make the following entries: Field Name
Description
User Action and Values
Action to Execute
Generation
Object Types
*
Logical Target Systems 5. Choose Execute.
Comment
The SCM logical system, for example SCMCLNT001
6.6 Creating an Integration Model in the ERP System This procedure allows you to create an integration model in the ERP system for transferring a plant, shipping points, and a business partner for the plant. Business partner for plant: If you have assigned a customer and a vendor to your plant, you have the following options: • •
Transfer both to EWM, thus creating two business partners in EWM (for example, 491000 for the plant as vendor with ID type CRM004 and 491000 for the plant as customer with ID type CRM002) Transfer both to EWM, but only create BP for the vendor, thus creating only one business partner (for example, 491000) in EWM and add the ID types CRM002 and CRM011 in EWM as described in the Enhancing Business Partners for Plants step. For the SAP Extended Warehouse Management rapid-deployment solution, only the second option is possible with the configuration in the system.
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu
Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Create
Transaction Code
CFM1
2. On Create Integration Model screen, make the following entries: Field Name
© SAP AG
Description
User Action and Values
Comment
Page 48 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Model Name Logical System
APO Application
for example IMEWM1 The SCM logical system name, for example SCMCLNT001
EWM
Material Dependent Objects Section Plants
X
General Selection Options for Materials Section Plant
1000
Material Independent Objects Section Customers
X
Vendors
X
Shipping Points
X
Customer Section (enter by choosing Special Restrictions for the Customers checkbox) Customer
491000
Create Loc./BP
For SAP EXTENDED WAREHOUSE MANAGEMENT RAPIDDEPLOYMENT SOLUTION, only location is created for customer 491000
Vendor Section (enter by choosing Special Restrictions for the Vendors checkbox) Vendor
491000
Create Loc./BP 2
Both BP and location are created for vendor 491000 for the plant 1000
Shipping Point Section (enter by choosing Special Restrictions for the Shipping Points checkbox) Shipping Point
1000
See a detailed description how to transfer materials using the Core Interface (CIF) in the Central Master Data Configuration Guide (Y33). You can save your integration model as a variant for future reuse, for example VIMEWM1, by choosing Save and maintaining relevant attributes. 3. Choose Execute. 4. Choose Generate IM.
6.7 Activating the Integration Model in the ERP System You can use this procedure to activate the integration model in the ERP system.
© SAP AG
Page 49 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu
Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model → Activate
Transaction Code
CFM2
2. On the Change View “Activate or Deactivate Integration Model”: Overview screen, make the following entries: Field Name
Model Name Logical System
APO Application Do Not Issue Warning in Case of Parallel CIF Load 3. Choose Execute.
Description
User Action and Values
Comment
for example IMEWM1
The SCM logical system name, for example SCMCLNT001
EWM X
4. On the Activate or Deactivate Integration Model screen, in the frame on the left, choose the APO Application, for example EWM. Your integration model appears on the right. 5. Select the Integration Model line and choose Active/Inactive. The status of your integration model is displayed in the New Status field and it is should be Active now (green). 6. Select the line again and choose Start. When you do this for the first time, a CIF_LOAD dialog box appears asking ' Should the Interval be Created'. In this case, choose Yes. 7. In the dialog box Application log, choose Yes to view the log message or choose No to finish the activity. 8. Choose Continue to confirm the Activation or deactivation of the selected models is complete information dialog box. After the activation of the Integration Model, the ERP data is transferred to EWM as shown exemplary below. In the following chapters, necessary settings are described, for example, creating supply chain units or assigning external IDs to Business Partners.
© SAP AG
Page 50 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
SAP ERP Warehouse EWM
Plant 1000
Storage Location YAFS
Storage Location YROD
Shipping Point 1000 (Shipping Point)
Shipping Point 1000 (Goods Receiving Point)
Supply Chain Unit SP1000
Supply Chain Unit SP1000
Business Attribute SO
Business Attribute RO
Customer EWMCUST001
Vendor EWMVEND001
Supply Chain Unit PL1000
Business Partner EWMCUST001
Business Partner EWMVEND001
Business Attribute INV
Ext.ID CRM002
Ext.ID CRM004
SAP EWM
7
Configuration Settings for SAP SCM after Data Transfer
You can use this process to make necessary configuration settings in SAP SCM after the data has been transferred from the ERP system.
Prerequisites You have made the necessary configuration settings to transfer data from the ERP system to SAP EWM, see Data Transfer to SAP SCM using the Core Interface (CIF). You have transferred the data for a plant, shipping points and the business partner you want to use for the plant.
Procedure Ensure that you follow the steps in the given order: • •
Checking Data Transfer via the Core Interface (CIF) Creating a Supply Chain Unit for a Warehouse
•
Creating a Supply Chain Unit Hierarchy
•
Enhancing Business Partners for Plants
•
Assigning Warehouse Numbers
•
Mapping Storage Locations from the ERP System to EWM
•
Registering Display Programs for Application Log in EWM
© SAP AG
Page 51 of 64
SAP Best Practices •
ERP-EWM Integration (Y31): Configuration Guide
Activating Business Configuration Sets (BC Sets)
Result You have made settings to SAP EWM after the data transfer using the core interface (CIF).
7.1 Checking Data Transfer via the Core Interface (CIF) At this point of the configuration process, it is important that you check that the data for the plant, the business partner, and the shipping points has been transferred to SAP EWM. In SAP EWM, the transferred data is stored as follows:
Data in the SAP ECC
Data in SAP EWM
Plant
Locations; Supply Chain Units
Shipping Points
Locations; Supply Chain Units, for example the goods receipt office or the goods issue office
Customer or Vendor
Location; Business Partner
The transferred data is used for the warehouse settings in SAP EWM and it is relevant for the following configurations: • •
Creating Supply Chain Units for a Warehouse Creating a Supply Chain Unit Hierarchy
•
Creating Business Partners for Warehouses
•
Assigning Warehouse Numbers
•
Mapping Storage Locations from the ERP System to EWM
•
Registering Display Programs for Application Log in EWM
•
Activating Business Configuration Sets (BC Sets)
The data appears in the transactions mentioned above. Either a prefix or a suffix, or both are added to the data if you activated the Business Add-Ins (BAdIs) or user exits for the inbound processing for locations or products. For more information, see Activating Business Add-Ins (BAdIs).
7.2 Creating a Supply Chain Unit for a Warehouse You can use this procedure to create a supply chain unit (SCU) for a warehouse in SAP EWM. For more information, see SAP Note 1100049.
Procedure 1. Access the transaction using one of the following navigation options:
© SAP AG
Page 52 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
SAP SCM Menu
Extended Warehouse Management → Master Data → Maintain Supply Chain Unit
Transaction Code
/SCMB/SCUMAIN
2. On the Supply Chain Unit: Initial Screen screen, make the following entries: Field Name
Description
Supply Chain Unit
Type 3. Choose Change.
User Action and Values
Comment
for example PL1000
the SCU of the plant that transferred previously using the CIF
1001
Type: Production Plant
4. On the Supply Chain Unit: Maintenance screen, on the Alternative tab page, choose Add Role then add the business attribute INV (Warehouse). 5. Choose Save.
7.3 Creating a Supply Chain Unit Hierarchy You can use this procedure to create a supply chain unit (SCU) hierarchy.
Procedure 1. In the SAP SCM system, on the SAP Easy Access screen, call transaction /n/SCMB/SCUHIERMAIN. 2. On the Supply Chain Unit Hierarchy: Initial Screen screen, in the Higher-Level SCU frame, make the following entries: Field Name
Description
Supply Chain Unit
User Action and Values
Comment
for example PL1000
the SCU of the plant that transferred previously using the CIF
3. Choose Change. 4. On the Supply Chain Unit Hierarchy: Maintenance screen, choose Create and make the following entries.
Supply Chain Unit
Business Attribute
Supply Chain Unit
Business Attribute
PL1000
INV
SP1000
RO
INV
SP1000
SO
PL1000 5. Choose Save.
7.4 Enhancing Business Partners for Plants You can use this procedure to create a business partner for each plant maintained in SAP EWM.
Prerequisites
© SAP AG
Page 53 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
The data for the plant and the business partner for the plant have been transferred from the ERP system using the core interface (CIF).
Procedure 1. Access the transaction using one of the following navigation options: SAP SCM Menu
Extended Warehouse Management → Master Data → Maintain Business Partner
Transaction Code
BP
2. On the Change View “Maintain Business Partner”: screen, on the Find tab page, make the following entries and choose Start. Field Name
Description
User Action and Values
Find
Business Partner
By
Number
Comment
BP Number
The business partner of the plant that you transferred using CIF 3. Double-click the Business Partner of the search result; the detailed information of the BP is displayed on the right side of the screen. 491000
4. Choose Switch Between Display and Change (F6) to switch to the change mode. 5. In change mode, add roles BBP000, BBP003, CRM000, and CRM002 by selecting them in the Change in BP role field. After selecting each role, save your settings. 6. On the Identification tab, in the Identification Numbers frame, check if the data for the business partner has been transferred from the ERP system.
If you transferred a customer, the value CRM002 is automatically created. If you transferred a vendor, the value CRM004 is automatically created.
If you want to add the IDType CRM004 to your customer, it can only be maintained if you do not select the Display Only checkbox in the Customizing activity Define Identification Categories. For more information, see Customizing under → Cross-Application Components →SAP Business Partner →Business Partner →Basic Settings →Identification Numbers →Define Identification Categories. 7. You must define an additional entry for the business partner plant (CRM011). Field Name
IDType Identification Number Responsible
© SAP AG
Description
User Action and Values
Comment
CRM011 1000
The ERP Plant number
The Logical System of your ERP system
Page 54 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Institution 8. Choose Save.
7.5 Assigning Warehouse Numbers You can use this procedure to assign warehouse numbers.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Master Data → Assign Warehouse Numbers
Transaction Code
SPRO
2.
In the Determine Work Area: Entry dialog box, enter YEWM in the Warehouse Number field and choose Enter.
3. On the Change View "Assignments: Warehouse Number/Business Partner": Details screen, choose New Entries. 4. On the New Entries: Details of Added Entries screen, make the following entries: Field Name
Description
User Action and Values
Comment
Description
YEWM RDS Warehouse
Supply Chain Unit
PL1000
The SCU for the plant
Custodian
491000
The BP for the plant
Dflt Pty Entld
491000
The BP for the plant
Default Ship-To 5. Choose Save. For more information, see the customizing activity documentation.
7.6 Registering Display Programs for Application Log in EWM You can use this procedure to register display programs for application log in Extended Warehouse Management (EWM).
Procedure 1. In SAP SCM, on the SAP Easy Access screen, call transaction SMQE. 2. Choose Edit →Register Display Program. 3. Enter the queue and program names as shown in the following table.
Queue Name
Program Name
CF*
/SAPAPO/CIF_QUEUE_EVENT2
DLV*
/SCWM/QRFC_APPL_LOG_DISPLAY
© SAP AG
Page 55 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
DLW*
/SCWM/QRFC_APPL_LOG_DISPLAY
EWM*
/SCWM/QRFC_APPL_LOG_DISPLAY
QI*
QIE_RFC_DISPLAY_QUEUE_LOG
QM*
QIE_RFC_DISPLAY_QUEUE_LOG
WMDP*
/SCWM/QRFC_APPL_LOG_DISPLAY
WMT*
/SCWM/QRFC_APPL_LOG_DISPLAY
X*
RSXMB_SHOW_ENTRY
7.7 Activating Business Configuration Sets (BC Sets) For the SAP Extended Warehouse Management rapid-deployment solution, the following BC Sets are used for configuration: BC Sets
Description
/SMBAS/SCWM_V_T3000_B036_J01
Define Warehouse Number Control
/SMBAS/SCWM_V_T343G_B04L_J01
Define Storage Bin Identifiers for Storage Bin Structures
/SMBAS/SCWM_V_TACTTY_B03W_J01
Define Activities
/SMBAS/SCWM_T333_B004_J01
Define Warehouse Process Type
/SMBAS/SCWM_TAVLGROU_B04O_J01
Configure Availability Group for Putaway
/SMBAS/SCWM_TCATLOCN_B04P_J01
Configure Availability Group for Putaway
/SMBAS/SCWM_V_TCAT_B053_J01
Define Stock Types
/SMBAS/SCWM_V_T340DA_B04W_J01
Define Number Ranges for Whse Management
/SMBAS/NRIV_B04Y_J01
Define Number Ranges for Consolidation Group
/SMBAS/SCWM_TDSTGRP_B04Q_J01
Define Consolidation Group
/SMBAS/SCWM_TDSTGRPN_B04R_J01
Assign Number Range Intervals to Consolidation Groups
/SMBAS/SCWM_TEXCEP_B03T_J0J
Define Exception Codes - Create Exception Code
/SMBAS/SCWM_V_TEXEH_B03T_J0F
Define Exception Codes - Define Exception Code
/SMBAS/SCWM_V_TEXEIP_B03T_J0G
Define Exception Codes - Maintain Process Parameters
/SMBAS/SCWM_V_TEXEAD_B03T_J0E
Def. Exception Codes - Deliv. Adjustment in Case of Differen
/SMBAS/SCWM_V_TEXEWF_B03T_J0I
Def. Exception Codes - Maint. Follow-On Action (Workflow)
/SMBAS/SCWM_T334RRD_B04N_J0B
Spec. Stock Removal Rule - Defin. of
© SAP AG
Page 56 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide Stock Removal Rules
/SMBAS/SCWM_V_T334RR_B04N_J0D
Specify Stock Removal Rule - Stock Removal Rule
/SMBAS/SCWM_V_ACC_LG_B04U_J0C
Def. Accnt. Ass. Cat. and Allow in Warehouse No. - Warehouse
/SMBAS/SCWM_V_T3000_B036_J01
Update Warehouse Number Control
This BC should only be activated using the BAiO Solution Builder with variant files instead of using transaction SCPR20.
7.8 Mapping Storage Locations from the ERP System to EWM You can use this procedure to map storage locations from the ERP system.
Procedure 1. Access the transaction using one of the following navigation options: IMG Menu (SCM System)
Extended Warehouse Management → Interfaces → ERP Integration → Goods Movements → Map Storage Locations from ERP System to EWM
Transaction Code
SPRO
2. On the Change View “Customizing Mapping Table for ERP Plant Storage Location”: screen, create entries for mapping the storage locations. For examples of entries, see the following table:
Pla nt 100 0 100 0
Sloc YRO D YAFS
Log. system
Warehouse Number
Agr
YEWM
001
YEWM
002
3. Choose Save. After all settings are done, the Integration between ERP and EWM is completed. The picture below gives an exemplary overview on all configurations that are necessary for the SAP Extended Warehouse Management rapid-deployment solution.
© SAP AG
Page 57 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
SAP ERP Warehouse EWM
Plant 1000
Storage Location YAFS Storage Location YROD
Shipping Point 1000 (Shipping Point)
Shipping Point 1000 (Goods Receiving Point)
Vendor EWMVEND001
Warehouse YEWM
Supply Chain Unit PL1000
Business Partner EWMCUST001
Business Partner EWMVEND001
Custodian 491000
Business Attribute INV
Ext.ID CRM002
Ext.ID CRM004
Default Entitled 491000
Ext.ID CRM011
SCU Hierarchy
Supply Chain Unit SP1000
Supply Chain Unit SP1000
Business Attribute SO
Business Attribute RO
Availability Group 001
Stock Types F1, Q3, B5, R7
Availability Group 002
Stock Types F2, Q4, B6, R8
SAP EWM
8
Customer EWMCUST001
Additional Data Transfer to SAP SCM Using the Core Interface (CIF)
You can use this process to transfer additional data from the ERP system using the core interface (CIF). To transfer additional data, you modify the previously created integration model. For more information, see Creating an Integration Model in the ERP System.
Prerequisites You have made the necessary configuration settings to transfer data from the ERP system to SAP SCM, see Data Transfer to SAP SCM Using the Core Interface (CIF). You have made the configuration settings in SAP SCM after transferring the data from the ERP system; see Configuration Settings for SAP SCM after Data Transfer.
Procedure Ensure that you follow the steps in the given order: 1. You modify the previously created integration model to transfer the data for the materials, customers, vendors, and batches. For more information, see step Modifying the Integration Model for Additional Data Transfer. 2. You activate the enhanced integration model by doing one of the following: o
Activating the model manually, see Activating the Integration Model in the ERP System
o
Activating the model automatically as part of a background job. To activate it in the background, you have to carry out the following steps in the order they are given: •
© SAP AG
Creating a Variant for Deleting Inactive Integration Models
Page 58 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
•
Create a Variant for Activating Integration Models for Background Processing
•
Scheduling a Background Job and Specifying Start Conditions
Result You have transferred additional data from the ERP system to SAP EWM.
8.1 Modifying the Integration Model for Additional Data Transfer You can use this procedure to transfer the data for materials, customer, vendors, and batches from the ERP system.
Prerequisites You have created an integration model and saved it as a variant. For more information, see Creating an Integration Model in the ERP System. See a detailed description of how to transfer materials, customers and vendors using the core interface (CIF) in the Central Master Data Configuration Guide (Y33). For the SAP Extended Warehouse Management rapid-deployment solution, the objects are mentioned in the document.
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC 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, in the menu, choose Go To → Variants → Get Variant. 3. Enter or select the name of the variant that you created previously, for example VIMEWM1. 4. Choose Execute. 5. Select the following objects: o
Materials
o
Customers
o
Vendors
6. Save the changed integration model as a variant, for example VIMEWM1. 7. Choose Execute. 8. Choose Generate IM.
© SAP AG
Page 59 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
8.2 Creating a Variant for Deleting Inactive Integration Models You can use this procedure to create a variant that you use to delete inactive integration models. Integration models should be deleted for performance reasons.
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu
Logistics →Central Functions →Supply Chain Planning Interface →Core Interface Advanced Planner and Optimizer Integration Model → Delete
Transaction Code
CFM7
2. On the Delete Integration Models screen, make the following entries: Field Name
Description
User Action and Values
Comment
Model
for example IMEWM1
Logical System
APO Application
EWM
APO Application
Select Inactive IMs X Only 3. Choose Goto → Variants → Save as a variant to save as a variant. 4. On the Variant Attributes screen, make the following entries: Field Name
Description
Variant Name Description Only for Background Processing 5. Choose Save.
User Action and Values
Comment
for example VIMEWM1DEL
for example Delete Inactive IMs
X
8.3 Creating a Variant for Activating Integration Models for Background Processing You can use this procedure to create and activate integration models for periodic (hourly) background processing.
Procedure 1. In the ERP system, on the SAP Easy Access screen, call transaction CFM3. 2. On the Activate or Deactivate Integration Model (Possible in Background), make the following entries: Field Name
Model
© SAP AG
Description
User Action and Values
Comment
for example IMEWM1
Page 60 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
Logical System
APO Application
EWM
Ignore Faulty Queue Entries
X
APO Application
Do Not Issue Warning in Case of X Parallel CIF Load 3. Choose Goto → Variants → Save as a variant to save as a variant. 4. On the Variant Attributes screen, make the following entries: Field Name
Description
Variant Name Description Only for Background Processing 5.
User Action and Values
Comment
for example VIMEWM1BACK
for example Activate IMs in BJ
X
Choose Save.
Result A variant of the Integration Model has been created for the system to automatically retrieve and execute in a background job.
8.4 Scheduling Background Jobs and Specifying Start Conditions You can use this procedure to schedule background jobs for transferring master data from the ERP system and to specify their start conditions.
Prerequisites You have defined variants for: o o
Deleting inactive integration models Enhancing the integration model for additional data transfer
o
Activating integration models for background processing
Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu Tools → CCMS → Background Processing → Define Job Transaction Code
SM36
2. On the Define Background Job screen, make the following entries then choose Step:
© SAP AG
Page 61 of 64
SAP Best Practices Field Name
ERP-EWM Integration (Y31): Configuration Guide Description
Job Name Job Class
User Action and Values
Comment
for example EWMTRANSFER
for example B Middle Priority 3. In the Create Step 1 dialog box, in the ABAP program frame, make the following entries: Field Name
Description
User Action and Values
Name
RIMODDEL
Variant
VIMEWM1DEL
Language 4. Choose Save.
Comment
EN
5. On the Step List Overview screen, create step 2 by choosing Create. 6. In the Create Step 2 dialog box, in the ABAP program frame, make the following entries: Field Name
Description
User Action and Values
Name
RIMODGEN
Variant
VIMEWM1
Language 7. Choose Save.
Comment
EN
8. On the Step List Overview screen, create step 3 by choosing Create. 9. In the Create Step 3 dialog box, in the ABAP program frame, make the following entries: Field Name
Description
User Action and Values
Name
RIMODAC2
Variant
VIMEWM1BACK
Language 10. Choose Save.
Comment
EN
11. On the Step List Overview screen, choose Back. 12. On the Define Background Job screen, choose Start Condition. 13. In the Start Time dialog box, choose Date/Time. 14. In the Date/Time frame, make the following entries: Field Name
Scheduled start
© SAP AG
Description
User Action and Values
Comment
Planned Start Date
Planned Start Time
Page 62 of 64
SAP Best Practices No Start After Periodic Job
ERP-EWM Integration (Y31): Configuration Guide
Latest Execution Date
Latest Execution Time
X
The time frame between Planned Start Date and the Latest Execution Date has to be within one year. 15. Choose Period values. 16. In the Period Values dialog box, choose Hourly and then choose Save. 17. In the Start Time dialog box, choose Save.
Result The background jobs start at the specified times and time intervals.
9
Final Configuration Settings for SAP SCM
You can use this process to make the final configuration settings in SAP SCM once you have transferred the additional data from the ERP system.
Prerequisites You have made the necessary configuration settings to transfer additional data from the ERP system to EWM, see Additional Data Transfer to SAP SCM Using the Core Interface (CIF).
Procedure Follow the steps in Scheduling Background Jobs for Data Transfer per Report.
Result You have completed the integration of SAP ERP with EWM as a component of SAP SCM.
9.1 Scheduling Background Jobs for Data Transfer per Report For some special processes in EWM, it is necessary to transfer additional data via reports.
Procedure 1. Access the transaction using one of the following navigation option, or schedule regular jobs for the corresponding reports: SAP SCM Menu
Extended Warehouse Management → Interfaces → ERP Integration → Determine and Set Prices from ERP
Transaction Code
/SCWM/VALUTAION_SET
© SAP AG
Page 63 of 64
SAP Best Practices
ERP-EWM Integration (Y31): Configuration Guide
For processes such as Physical Inventory, Split Valuation Without Batches, Quality Management in EWM, run the report /SCWM/R_VALUATION_SET or schedule a background job to execute periodically.
© SAP AG
Page 64 of 64
View more...
Comments
