SAP SCM 4.

0 March 2004 English

Building Block SCM Collaboration Settings
Building Block Configuration Guide

SAP AG Neurottstr. 16 69190 Walldorf Germany

SAP Best Practices

Building Block SCM Collaboration Settings: Configuration Guide

Copyright
© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

© SAP AG

Page 2 of 42

SAP Best Practices

Building Block SCM Collaboration Settings: Configuration Guide

Icons
Icon Meaning Caution Example Note Recommendation Syntax

Typographic Conventions
Type Style Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. 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.

Example text

EXAMPLE TEXT Example text <Example text>

© SAP AG

Page 3 of 42

SAP Best Practices

Building Block SCM Collaboration Settings: Configuration Guide

Content
1 2 Purpose................................................................................................................................. 5 Collaborative Planning.......................................................................................................... 6 2.1 2.2 2.3 2.4 2.5 3 Prerequisites .................................................................................................................. 6 Uploading the Configuration Role .................................................................................. 6 General Settings ............................................................................................................ 7 Collaborative Demand and Supply Planning ............................................................... 12 Collaborative Transportation Planning......................................................................... 22

EDI Settings for Vendor-Managed Inventory...................................................................... 25 3.1 3.2 3.3 3.4 Prerequisites ................................................................................................................ 25 Uploading the Configuration Role ................................................................................ 25 EDI Settings APO......................................................................................................... 25 EDI Settings R/3........................................................................................................... 30

4

EDI Settings for Collaborative Management of Delivery Schedules .................................. 37 4.1 4.2 4.3 4.4 Uploading the Configuration Role ................................................................................ 37 Defining EDI Port (APO) .............................................................................................. 37 Creating Partner Profiles.............................................................................................. 38 Creating IDOC Templates............................................................................................ 39

© SAP AG

Page 4 of 42

© SAP AG Page 5 of 42 . refer to the Installation Guide of this building block. The building block Configuration Guide describes how to manually configure a building block without using automated configuration tools.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 1 Purpose The purpose of this document is to describe general configuration steps required to manually configure the system landscape that has already been installed using the corresponding installation or configuration guides for installation. If you want to use BC sets and CATT procedures for an automated installation process.

1.1 SAP Notes for Building Block SCM Collaboration Settings The following SAP notes are required to install and use this building block: SAP Note # 577845 Component Description SCM-APO-CA-COP CLP 40: Install ITS services for APO collaborative 2. If you want to install and run the section Collaborative Demand Planning. that is. you must first install the building block Demand Planning. you need to upload the configuration role and assign it to your user. for SAP APO or SAP R/3. SAP Best Practices provides a configuration role for each component involved in this configuration. The configuration role is a special user menu that enables you to comfortably access all necessary transactions for the configuration from the relevant system. The following roles are available: Technical name S32_02C Description Configuration role for SCM collaboration settings (SAP APO) Procedure For details on how to upload configuration roles to the system and how to work with them.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2 2.0 or a higher version is required by the external partner. you must have already installed the Internet Transaction Server (ITS). © SAP AG Page 6 of 42 .2 Use Uploading the Configuration Role Before you start with the configuration according to the manual procedures described in this configuration guide. 2. Microsoft Internet Explorer 5.1 Collaborative Planning Prerequisites In order to be able to install and perform Collaborative Planning. refer to the document Essential Information.

you have to create an RFC destination and a node in SAPconnect.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. Gateway Host Gateway service 6.wdf.sap.3. for example.1 Defining an RFC Destination Use Before you can send e-mails from your SAP APO system. Outgoing messages are transferred from SAPconnect via RFC to the external communication system. Choose Test connection to test each connection. Procedure 1.sap. “mailsig. First.corp” IP address Entry SEND_MAIL T (TCP/IP) RFC destination for outgoing Internet messages If the SAP Gateway is not running on the current application server. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Defining an RFC Destination SM59 Tools Administration Destinations Administration Network RFC 2. 7.3 General Settings 2. Choose Destination → Gateway options. you have to create an RFC destination. specify the SAP Gateway you want to use to establish the connection to the Internet Mail Gateway server. Make the following entries according to the RFC destination: Field RFC destination Connection Type Description 4. Activity type Program Target Host Save As Start on Explicit host For example.wdf. Choose Create (F8) 3. for example.corp” <R/3 gateway service>. “/mail/sap/OUT/mlunxsnd” For example. Choose Enter. Save your RFC destination. “mailgwo. 5. “sapgw88” © SAP AG Page 7 of 42 . <R/3 gateway host>.

Access the activity using one of the following navigation options: SAP APO Menu Transaction Code SAP Menu Maintaining Settings in SAPconnect SCOT Tools → Business Communication → Communication → SAPconnect 2. Choose Continue. if necessary. choose Continue. The Create nodes dialog box appears. Select RFC Node. If the RFC Node radio button is active. Enter a node and a description: Field name Node Description 4. Select the following option: Field name Address type 9. To create a node for sending Internet messages.2 Maintaining Settings in SAPconnect Use SAPconnect provides a standard interface for external communication. an e-mail system. 3. A node represents a logical view of an external communication system in SAP R/3. Make the following entry: Field name Address area User action and values * User action and values Internet User action and values SEND_MAIL User action and values MAIL Outgoing Internet messages © SAP AG Page 8 of 42 . Every external communication system is represented by a node. 10.3. Procedure 1. choose Create on the SAPconnect Administration screen. Make the following entry: Field name RFC Destination 7. 8. Choose Continue. 6. Choose Continue. It comprises information necessary to send messages from the SAP R/3 system via an external communication system. 5.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. The RFC destination and the Internet must be assigned as means of communication. for example.

Make the following entries: Field name Hours Minutes 19. Choose Continue. 16. status. User action and values Select Deselect User action and values Deselect Deselect User action and values 0 0 User action and values N User action and values Deselect User action and values PDF HTM HTM TXT © SAP AG Page 9 of 42 .SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 11. 12. 20. Choose Continue. Choose Continue to save the node. Choose Continue. Choose Continue. Deselect the following fields: Field name Node can resolve path references Node is to be monitored by the alert monitor 21. Choose Continue. 18. Make the following entry: Field name Set further address types? 17. Make the following entry: Field name Restrict send time 15. 22. Select the following fields: Field name Node is ready for use Node supports: Connection test. 14. Confirm the following output formats: Field name SAPscript/Smart Forms ABAP List Business Object/Link RAW Text 13. Choose Continue. trace 23.

Access the activity using one of the following navigation options: SAP APO Menu Transaction Code SAP Menu 2. 4. for example. 5 minutes: Month(s) Week(s) Day(s) Hour(s) Minute(s) 0 0 0 0 5 9. Choose Period values (F5). the send process determines the appropriate nodes and transfers messages to external communication systems. Choose Start condition (F5) to specify a period and start conditions: Start time Periodic job Immediate start Select RSCONN01 INT Value SEND_MAIL B (Medium priority) Scheduling the Background Job SM36 Tools CCMS Jobs Definition 7. Choose Return. 8. Choose Save to save the start condition. 11. Procedure 1. messages are sent externally only if regular send processes have been scheduled. Therefore. 10. Choose Other period to specify an individual period. Choose Save to save the job definition and release the job. Moreover. choose ABAP program and make the following entries: Name Variant 5. On the Create Step 1 screen. Choose Save. © SAP AG Page 10 of 42 .SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. Choose Save to save the period values. 6.3 Scheduling the Background Job Use The send process reads messages to be sent from the Business Communication Interface queue.3. Make the following entries: Field Job name Job class 3.

PGAT7F.4 Assigning the Logical Web Server Use Assign a logical Web server to the logical system. Ignore the message “Table is cross –client” 4.g.SAP-AG. AT7CLNT001) Name of the ITS web server with the accompanying port (e. make the following entries: Field LogSystem Web server Web Protocol 5.DE:1080) The protocol to be used (HTTP or HTTPS) © SAP AG Page 11 of 42 . so that collaborative planning services can be run via the SAP easy access menu. In the Change view Logical Web Servers for Logical Systems screen.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. Access the activity using one of the following navigation options: SAP APO Menu Transaction Code SAP Menu Assigning the Logical Web Server SM30 System → Services → Table maintenance → Extended table maintenance 2. 3. Comment Name of the logical system you are working with (e. Procedure 1.g. enter TWPURLSVR in the Table/View field and choose Maintain. In the Maintain Table Views: Initial screen.3. Save and go back.WDF.

user. 4.sapag. The Internet browser is opened and the APO Collaborative Planning screen is displayed.1 Creating and Uploading the Mail Template Use During the collaborative planning process.com). This procedure describes how to create and upload an e-mail template. 2.wdf.txt". 5. 2. You can use it.4 Collaborative Demand and Supply Planning 2. Procedure 1.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. you need to assign your e-mail address to your user.txt) on your computer. Create a text for an e-mail in Microsoft Word and save it as a txt.g. You can access this URL via the path Demand Advanced Planning and Optimization Demand Planning → Planning → Collaborative Demand Planning (transaction /SAPAPO/CLPISDP). A default template for e-mails is provided: "Template_Mail. Copy the URL and include it into your txt.5 Maintaining the Internet Mail Address Use If you want to send e-mails from SAP APO.name@company. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Maintaining the Internet Mail Address SU01 Tools → Administration → User Maintenance → Users 2. Save and go back. 3. An example of a hyperlink: http://pgas7w1.de:1080/scripts/wgate/clpsdp/!?~language=en&~client=001) © SAP AG Page 12 of 42 . On the User Maintenance screen. but you have to delete the URL first and enter the correct URL as described below. the collaboration partner is notified via e-mail that a draft demand plan is available. file.3. 3. Copy the URL of the Collaborative Planning Book into your document.4. Procedure 1.file (text only *. enter your Internet e-mail address (e.

9.file (for example C:\Template_mail. 13.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 6. In the Business Document Navigator dialog box. 11. 10. Choose Execute. On the Create tab page. expand the folder Select a document type or application. Double-click Text. 12. To upload the file to the APO system. On the Business Document Navigator screen. Go back. In the Business Document Navigator: File Selection dialog box.txt) and choose Open. make the following entries: Field Class name Class type Object key 8. proceed in the following way: SAP APO Menu Transaction Code SAP Menu Creating and Uploading the Mail Template OAER Tools → Business Documents → Miscellaneous → Business documents 7. enter a description and choose Continue. select the txt. Value DP_SNP OT DP_SNP Troubleshooting If the error message “Knowledge Provider error: Object does not exist” is displayed. access the transaction SBDSV1 and create the following entry: Field Class name Class type DocuClass DocuClass DocuClass Object name Value DP_SNP Other objects BDS_LOC2 BDS_POC2 BDS_REC2 BDS_CONN05 © SAP AG Page 13 of 42 .

type screen area. Select the Document contents tab. you create a user for your collaboration partner (e. 12. enter DLI.. On the Distr. In the Title screen area. 9.g. enter DL CLP. On the Attributes tab page. enter the folder name CLP. 5.. © SAP AG Page 14 of 42 . Access the activity using one of the following navigation options: SAP APO Menu Transaction Code SAP Menu 2.4. enter the recipient's e-mail address and choose Internet address.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2.4.3 Creating User for Collaboration Partner Use In this step. 11. 8. 13. Choose Folder → Create from the menu bar. 4. Procedure 1. 10. Select Shared folders. the description DL CLP.2 Creating the Distribution List Use This step allows you to create a distribution list containing your collaboration partner’s e-mail address. Creating the Distribution List SO04 Office → Folders → Shared Folders 2. Choose Create more. partner or customer) in APO. list content tab page. Select CLP. Save and go back. The CLP subfolder is displayed. In the Create folder dialog box. enter DL CLP. On the Attributes tab page. 3. and choose Transfer. 7. in the Recip. 6. Choose the right part of the Create document button.

4. Choose Create or Copy. which enables you to enter notes in the Internet planning book. which enables you to show a graphical representation of your data in the Internet planning book. enter the parameter /sapapo/clp_webgraph. 3. On the Profile tab page.4. 7. value X (with a capital X). value XLS (with a capital XLS). 4.4.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Procedure 1. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu 2. 9. assign a profile. enter: Parameter /sapapo/clp_webdown. you create a macro allowing you to send e-mails directly from your planning book using a pushbutton. 3. On the Parameters tab page. 8. 5. 6. On the Logon data tab page. Choose Edit. Save and go back. On the Parameters tab page. © SAP AG Page 15 of 42 .1 Creating Macros in the Planning Book Use In this step.4 Collaborative Demand Planning 2. enter the parameter /sapapo/clp_webnote.4. which enables you to export data and process it in Microsoft Excel. On the Parameters tab page. value X (with a capital X). Access the activity using one of the following navigation options: SAP APO Menu Transaction Code SAP Menu Creating Macro in Planning Book /SAPAPO/SDP8B Advanced Planning and Optimization Demand Planning → Environment → Current settings → Define Planning Book 2. Enter a user name. Select Data view. Creating User for Collaboration Partner SU01 Tools → Administration → User Maintenance → Users 2. enter the initial password. Procedure 1. Enter the planning book DP_001 and the data view DP_STANDARD.

Make your first entry without a transaction code as shown in the table below: Name e. Enter a descriptive text (e. WEBUSER e. 7.g. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Assigning a User to a Planning Book /SAPAPO/SDPPLBK Advanced Planning and Optimization → Demand Planning → Environment → Current Settings → Assign User to Planning Book 2. Right-click the new macro and choose Add mail. Send mail to partner) and assign a pushbutton. 2. PLANNING DATA HAS BEEN CHANGED). Choose Check. Choose MacroBuilder → Data view. the document text (see Chapter Mail Template) and the recipient (see Chapter Distribution List).g. Save and go back.g. Choose Save and Save All.4. In the dialog box. 13.g. Go back. Right-click on the macro node below the planning table and choose Add macro.2 Assigning User to Planning Book Use This procedure enables you to assign a user to the planning book and data view. Select the new macro. Enter a Descriptive Text (e.4. The view APO Macro Builder is displayed.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 5. Choose Generate to generate the macro. Right-click the new macro and choose Add macro step. 11. Choose Continue. Go back. Code Plng book DP_001 DP_001 Data view DP_CLP DP_CLP Specific book Fixed View Do not select Do not select Select Select 3. 6. Procedure 1. The Planning Book: Demand Planning – Standard dialog box is displayed. 9. You can restrict the user’s access to one book and one view. 8. 15. add a title (e. choose User defined (Iterations 1) and choose Continue. 12.g. Choose MacroBuilder. 10. which should appear in the planning book. WEBUSER /SAPAPO/SDP94 Trans. 14. Mail). © SAP AG Page 16 of 42 .

4.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. © SAP AG Page 17 of 42 . In the Object selection dialog box. Choose Selection window. The system displays them in a table. Restrict the selection to products that are assigned to the user by selecting APO Product or Sold-to party and entering the corresponding products or customers (multiple selection). choose APO Product. Log on with the new user you have created in the activity "Creating User for Customer / Partner". to which the user will have access). 7. Procedure 1. Enter the name of the user as the selection text and choose Save.3 Maintaining Selection Profiles for User Use You have to build a working profile for each collaboration partner to restrict his or her access to authorized data.4. Enter the planning version 000 in the field to the right of the APO Planning Version field 6. 11. SAP APO Role Menu Transaction Code SAP Menu Maintaining Selection Profiles for User /SAPAPO/SDP94 Advanced Planning and Optimization → Demand Planning → Planning → Interactive Demand Planning 2. 9. You can access the objects by double-clicking the selection. in the Show screen area. 4. Choose Save selection. Store saved selections by choosing Maintain selection profile and using drag & drop to transfer the saved selection from the right to the left area. Choose Save and Copy. 8. Go back.e. 10. After creating a selection of products. 5. Create a selection of products that are assigned to the user (i. Proceed in the following way: 3. assign it to a user selection profile in order to make it visible to the collaboration partner in collaborative demand planning.

4. Select the line item that contains the material for which the scheduling agreement was set up and choose Additional Data. If it is not. Enter the number of the Scheduling Agreement. Procedure 1. In the Administration screen area. This data needs to be transferred to SAP APO through the Integration Model.2 Maintaining Purchase Scheduling Agreement in APO Use The purpose of this activity is to maintain the control profile for the purchase scheduling agreement in APO. 4.4. Prerequisites You have set up the vendor master data.g.1 Checking Master Data for Procurement Scheduling Agreement in SAP R/3 Use The purpose of this activity is to check that the procurement scheduling agreement is set up correctly in R/3 so it can be used for Collaborative Management of Delivery Schedules. material master and relevant purchase scheduling agreement in the SAP R/3 system. Procedure 1. change it to this value. 5. 5500000002. 3.5 Collaborative Supply Planning 2. Save your entries.4.5. Access the activity using one of the following navigation options: SAP APO Role Menu Procurement Relationships © SAP AG Page 18 of 42 . check whether the content of the Ext Planning field is 1.5. Access the activity using the following navigation options: SAP R/3 Role Menu Transaction Code SAP Menu Change Scheduling Agreement ME32L Logistics → Material Management →Purchasing →Outline Agreement → Scheduling Agreement → Change 2. and choose Overview.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 2. e. 2.

make the following entries: Field name Destination Location Product Number Scheduling Agreement Description User action and values e. Procedure 1. 2.g. 5. tab page. agmt. if necessary. select the document line that matches your product. On the right side of the screen. HT61PR-1100 e. Choose Execute to enter the Display External Procurement Relationships screen. make the following entries: © SAP AG Page 19 of 42 .4.g. Choose Save to save your entries and exit. On the External Procurement Relationships screen. Transportation lanes represent the buying or selling relationship between partners. 4. In the left screen area.g. under APO sch. then choose Display<->Change to access the change mode.g.g. On the Transportation Lane: Access screen. Select Notes 3. PLBP01/KD6416 e.5. make the following entries: Field name Update LiveCache Process Description User action and values e. 10 e.3 Maintaining Means of Transport for Transportation Lane Use The purpose of this activity is to check whether a valid means of transport exists for the transportation lane and to define one. location combination. 04 Notes 6. Agmt. transportation lane between the supplier and plant has been created automatically. Access the activity using the following navigation options: SAP APO Role Menu Transaction Code IMG Menu /SAPAPO/SCC_TL1 Advanced Planning and Optimization → Master Data → Transportation Lane→ Transportation Lane Transportation Lane 2.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Transaction Code IMG Menu /SAPAPO/PWBSRC1 Advanced Planning and Optimization → Master Data → Procurement Master Data → Procurement Relationships 2. When you create the purchase scheduling agreement in SAP R/3 and transfer it to SAP APO. choose Sch. It is necessary to maintain a valid means of transport for this lane.

2. check whether there is a valid means of transport for all product or a valid Means of Transport for your specific product.4. 000 e. PLBP01/KD6416 Notes 3. Choose Save and exit. Code Plng book 9ASAS Data view SAS (1) Specific book Do not Fixed View Select © SAP AG Page 20 of 42 .g. 01012004 e. SUH6100/KD6416 e.g. You can restrict the user’s access to one planning book and one view.5. create three new records as in following table: Make your first entry without a transaction code as shown in the table below: Name e.g. 31122005 Notes 6. Trans. Choose Copy and Close icon to save your entries. 5. you can exit to finish this process.g. Procedure 1.4 Assigning User to Planning Book Use This procedure enables you to assign a user to the planning book and data view. 4. 0001 e. and make the following entries: Field name Means of Trans Start Date End Date Description User action and values e. Choose Change icon to go on to the next screen.g.g.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field name Model Name Start Location Dest. Choose Creation of New Entry. otherwise continue following steps to create one. If there is. 7. Location Description User action and values e.g. On the Data view Last Selected sheet. On the Change Transportation Lane:… screen. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Assigning a User to a Planning Book /SAPAPO/SDPPLBK Advanced Planning and Optimization → Demand Planning → Environment → Current Settings → Assign User to Planning Book 2.

Store saved selections by choosing Maintain selection profile and using drag & drop to transfer the saved selection from the right to the left area. Choose Save selection.5 Maintaining Selection Profiles for User Use You have to build a working profile for each collaboration partner to restrict his or her access to authorized data. Agrmnt.4. 3. Restrict the selection to products which are assigned to the user by selecting APO Product and entering the corresponding products number.g. 2. 8. Enter the name of the user as the selection text and choose Save. WEBUSER Trans.5.g. After creating a selection of products.e. Further restrict the selection to those document numbers that are assigned to the user by selecting APO document number and entering the corresponding number of the scheduling agreement. Procedure 1. WEBUSER e. Enter the planning version 000 in the field to the right of the APO Planning Version field. Sched. Log on with the new user you have created in the activity Creating User for Customer / Partner. Save and go back. 7. 5. 6. Choose Selection window to create a selection of products that are assigned to the user (i. © SAP AG Page 21 of 42 . Code Plng book Data view Specific book select Do not select Do not select Fixed View Select Select /SAPAPO/SNPSA 9ASAS SAS (1) SAS (1) /SAPAPO/CLPISAP 9ASAS 3. 4. assign it to a user selection profile in order to make it visible to the collaboration partner in collaborative demand planning. to which the user will have access). 9. choose APO Locatn. In the Object selection dialog box. Prod.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Name WEBUSER e. in the Show screen area. SAP APO Role Menu Transaction Code SAP Menu Maintaining Selection Profiles for User /SAPAPO/SNPSA Advanced Planning and Optimization → Supply Network Planning → Planning → Scheduling Agreements (Procurement) → Interactive Scheduling Agreements 2.

2.g. The system displays them in a table. Access the activity by choosing one of the following navigation options: APO Menu Transaction code SAP Menu → Tools → Administration → User Maintenance → Users SU01 The Maintain User screen is displayed. Procedure 1. © SAP AG Page 22 of 42 . 3. you have to create a user in SAP APO for your collaboration partner. S8100).1 Creating User for Collaboration Partner Use If you want to use collaborative planning.6 Sending User and Password to Collaboration Partner Use Inform the collaboration partner about the user and password you have created. Go back.4. To access the objects double-click the selection. Repeat steps 3 to 6 for each user. Choose Save and Copy. 2. 2. enter an initial password. 5. 2. Choose Create (F8). Save and go back.5.5 Collaborative Transportation Planning 2. 6.5. On the Logon data tab page. 11. in the Password screen area.2 Maintaining Collaboration Partners Use The purpose of this activity is to make the necessary settings for collaborative transportation planning. Enter a user name (e.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 10. 4.

Choose Save and go back.5. if necessary. 7. SAP internal user S8100 as internal mail address in SAP system). 11. Enter an e-mail subject and text for Announcement of planning steps and for Undo planning steps (e. A transport request for workbench is displayed. S8100). 10.g.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Prerequisites You have created one or more users in the APO system for the collaboration partners to enable them to access the system. 12. Choose Continue. 2. Select an existing request or create a new one. 4. Please check. Choose Possible entries <F4>. choose Collaboration Partners and New Entries. Save your entries. Shipments created/deleted. select New Internet address and enter the e-mail address of the business partner (e.g. Procedure 1.g. choose New Entries and select the collaborative scenario Transportation planning. 9. Enter a business partner and a partner description (e. 6. 8. Procedure 1. Double-click Communication settings.3 Assigning Partner to Transportation Service Provider Use The purpose of this activity is to assign the collaboration partner defined in the previous steps to a transportation service provider (TSP). Best regards). Select Sending of e-mails activated. Access the activity by choosing one of the following navigation options: APO Menu SAP Menu Advanced Planning and Optimization Transportation Planning/Vehicle Scheduling Environment Current Settings Collaborative Transportation Planning Make Settings for Collaborative Planning /SAPAPO/CLP_SETTINGS Transaction code 2. Double-click User Assignment and choose New Entries. Assign the user of the transportation planner to the collaboration partner and select Transportation RFQs. Access the activity by choosing one of the following navigation options: APO Menu SAP menu Location Advanced Planning and Optimization Location Master Data © SAP AG Page 23 of 42 . In the Change View “Collaboration Partners”: Overview screen. 3. 5.

choose Transportation service provider and select the TSP that is used for collaboration. S8100).SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Transaction /SAPAPO/LOC3 2. 4. enter the collaboration partner (e. Choose Change.g. 5. 3. On the Location Master Data: Initial Screen. © SAP AG Page 24 of 42 . In the Change Location screen area. Choose Save and go back twice.

SAP Best Practices provides a configuration role for each component involved in this configuration. Its objective is to electronically interchange structured business data such as purchase orders. 3. The following roles are available: Technical name S32_02C S32_01C Description Configuration role for SCM collaboration settings (SAP APO) Configuration role for SCM collaboration settings (SAP R/3) Procedure For details on how to upload configuration roles to the system and how to work with them. The configuration role is a special user menu that enables you to comfortably access all the necessary transactions for the configuration from the relevant system. you need to upload the configuration role and assign it to your user.3.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3 3.3 EDI Settings APO EDI is a concept that integrates business application systems.2 Use Uploading the Configuration Role Before you start with the configuration according to the manual procedures described in this configuration guide. invoices and payment orders. and to automatically process this data in the recipient’s application system. © SAP AG Page 25 of 42 . refer to the document Essential Information. The IDocs are read as sequential files. that is.1 Defining EDI Port (APO) Use The EDI port specifies how the IDocs are transferred to the EDI subsystem. 3. 3.1 EDI Settings for Vendor-Managed Inventory Prerequisites Your system landscape must be set up to enable the exchange of messages via Electronic Data Interchange (EDI). for SAP APO or SAP R/3. The IDoc (intermediate document) is used as the interchange format.

Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Defining EDI Port (APO) WE21 Tools → Business Communication → IDoc Basis → Administration → Port Definition 2. Outbound Trigger. or a logical system. C6220 KU © SAP AG Page 26 of 42 . Inbound File. enter a physical directory (e. 5. for example. Inbound File. make the following entries: Field Partn. Do not forget the last slash. partners must be defined with inbound or outbound parameters. enter the EDI_PATH_CREATE_USERNAME function module. as the file name is simply appended as a directory! AT7 is the name of the APO system in the example. 4.g. D:\usr\sap\AT7\SYS\global\ ). Value e.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Procedure 1. Status File tab pages. select File and choose Create. Enter a port. VMI Port. Procedure 1. 3. customer. On the Partner Profiles screen. Save and go back. On the Partner Profiles screen.3. such as VMI and a description. 3. On the Ports in IDoc processing screen. choose Create from the application toolbar.g. On the Outbound File.2 Creating Partner Profiles (SAP APO) Use To enable IDoc communication. in the Ports screen area. The partner type determines the partner master data read by IDoc interface. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Creating Partner Profiles (APO) WE20 Tools → Business Communication → IDoc Basis → Administration → Partner Profile 2. 6. On the Outbound File. 3. type Description Number that uniquely identifies a vendor. number Partn. Status File tab pages.

you create an IDoc template in the SAP APO system. In the Inbound parameters screen area.g. SAPAS7 User action and values PROACT Comment Default message type Note The receiving system is always an SAP system. 5. choose Create inbound parameter. 9. Go to the Post processing: permitted agent tab page and make the following entries: Field Type Agent 5. you may receive an error message. On the Partner Profiles: Inbound parameters screen. Choose Create. SAPAT7) Choose the logical system that is assigned to your client Partner number Partner type e. 7. which you can ignore. Select the IDoc segments’ line EDIDC. 6. 8.3 Creating IDOC Template PROACT Use In this step.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 4. As the template contains only sample data. enter the message type PROACT. Procedure 1. Description Classifies the recipient of error notifications Permitted users Value US (User) Your username 3. This IDoc can be used as a template for further inbound processing of planning data. Access the activity choosing one of the following navigation options: SAP APO menu Transaction code Tools → Business Communication → IDoc Basis→ Test → Test Tools WE19 2.g. 4. Make the following entries: Field name Port User action and values e. make the following entries: Field name Via Message Type 3. Choose Save. AS7CLNT001 LS © SAP AG Page 27 of 42 . Go to the Inbound options tab page and enter the process code PRAC_APO.g. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID> (e. Save and go back. On the Test Tool for IDOC Process screen.3.

Choose Continue. CUC6220/ES7031 Comment Vendor Description Partner qualifier User action and values WE e. APO-FERT-03 Comment Material number of vendor Description User action and values 300 e. 11. 10.g. Choose Continue. CUC6220/ES7031 Comment Ship-to party 19. Choose Continue. 17. 12. Double-click the E1ADRM1 line and make the following entries: Field name PARTNER_Q PARTNER_ID 9. Double-click the E1EDP19 line and make the following entries: Field name Identification Material Description User action and values e. and make the following entries: Field name QUALF Description User action and values 003 Comment Sales © SAP AG Page 28 of 42 . 14. Expand the structure of E1ADRM1.g.g. 7. Double-click the E1ADRM1 line you have just created and make the following entries: Field name PARTNER_Q PARTNER_ID 13. 002 e.g. CUC6220 KU Choose the partner profile 8. Expand the structure of E1EDP31. Choose Continue. Double-click the E1EDP32 line. Double-click the E1ADRE1 line and make the following entries: Field name EXTEND_Q EXTEND_D 16. Choose Insert and select at the same level.g. 15. Change the sender data: Field name Port Partner number Partner type Description User action and values VMI Note e. 18. Select the E1ADRM1 line and choose Copy.g.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 6. CUC6220/ES7031 Comment Own account number for recipient Description Partner qualifier User action and values LF e.

22. Choose Standard Inbound to enter the record. Date_to = ‘20031130’ and Time_to = ‘235959’ to specify the quantity for November 2003 TIME DATE_TO TIME_TO 20. Result One IDoc template (message type PROACT) is created in the system.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field name QUANTITY UNIT DATE Description User action and values e. 23. The IDoc number…transferred to application message is displayed. Choose Continue.g. 235959 21.g.g. Time = ‘000000’. PCE e. e. 20031101 Comment For example. 5000 e. enter the values Date =’20031101’. 000000 e. In the Test inbound IDoc using partner profile dialog box.g.g. 20031130 e. choose Continue. © SAP AG Page 29 of 42 .g.

On the Ports in IDoc processing screen. in the Ports screen area. On the Outbound File. 3. Outbound Trigger.4. Do not forget the last slash. On the Outbound File. and a description.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3. 4. 6. Procedure 1. enter the function module EDI_PATH_CREATE_USERNAME. Inbound File. Access the activity using one of the following navigation options: SAP R/3 Role Menu Transaction Code R/3 Menu Path Defining EDI Port (R/3) WE21 Tools → Business Communication → IDoc Basis → Administration → Port Definition 2. Enter a port. e. File Port VMI.1 Defining EDI Port (R/3) Use To enable IDoc communication.g.g. 5. partners must be defined with inbound or outbound parameters. e.g. Inbound File. enter a physical directory (e. © SAP AG Page 30 of 42 . Save and go back. select File and choose Create. Status File tab pages. as the file name is simply appended as a directory! DS7 is the name of the R/3 system in the example. D:\usr\DS7\SYS\global\). VMI. Status File tabs.4 EDI Settings R/3 3.

4. Procedure 1. or a logical system. Access the activity using one of the following navigation options: SAP R/3 Role Menu Transaction Code SAP Menu Creating Partner Profiles (R/3) WE20 Tools → Business Communication → IDoc Basis → Administration→ Partner Profile 2. On the Partner Profiles screen. On the Partner Profiles: Outbound parameters screen. Go to the Post processing: permitted agent tab page and enter the following values: Field Type Agent 5. 3. choose Create from the application toolbar. 2.2 Creating Partner Profiles (SAP R/3) Use Partner profiles are necessary for IDoc inbound/outbound processing. Choose Test. In the Partner Profiles screen area. Description Classifies the recipient of error notifications. Choose Save. Value e. The partner type determines the partner master data the IDoc interface reads. type Description Number that uniquely identifies a vendor. customer. C6100 KU 4. enter the following values: Field Partn. Permitted users Value US (User) Your username Outbound Parameters 1. make the following entries: Field Partn fnct Message type Message code 3.g. choose Create Outbound parameter. number Partn. make the following entries: Description Value SP ORDRSP VMI © SAP AG Page 31 of 42 .4.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3. On the Outbound options tab page. In the Outbound parameters screen area.

choose Create Outbound parameter. 2.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field Receiver port Description Specifies how the IDocs are transferred to the EDI subsystem. On the Inbound options tab page. Value E (EDIFACT) Description Value V1 BAV0 SD10 Message type Version 7. ORDERS 001 Inbound Parameters 1. funct. Value ORDM For further messages’ separation. you can specify the partner SP function containing the sender and the recipient ORDCHG VMI X © SAP AG Page 32 of 42 . make the following entries: Field EDI standard Description Defines the general interpretation scheme which is used as a basis for translating an IDoc type into an EDI data structure. make the following entries: Field Partn. The port must be created in the port description first. On the EDI Standard tab page. On the Message control tab page. Value e. make the following entries: Field Process code Description A process code identifies the type of data processing for inbound processing. choose Insert row and make the following entries: Field Application Message type Process code 6. In the Inbound parameters screen area.g. Description Value Using this optional parameter. Message type Message code Test 3. On the Partner profiles: Inbound parameters screen. Save and go back. SAPES7 Transfer IDoc Immed Basic type Syntax check X ORDERS01 X 5.

make the following entry : Field name Sales Organization Sales document type 5. On the Change condition records (Order Confirmation VMI): Fast Change screen. Choose Execute. Select application V1 and choose Condition records. 6. order acknowledgments are generated for sales orders as messages of the type BAV0. In the standard system. 4. VMI) and choose Condition records.4.g. Description Value X X 3. Procedure 1. On the Change Order confirm.g. 8.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field Syntax check Trigger immediately 4. make the following entries: Field name Sales document type Partner Function Partner Medium 7. Save and go back. 3. Save and go back. C6100 6 Notes Description User action and values e. BP01 Notes © SAP AG Page 33 of 42 . Description User action and values TAV SP e. Select BAV0 (Order confirm. You must create the required condition records for this. (BAV0): Selection screen.3 Creating Condition Records Use The sales order is transferred to the customer by EDI in the form of an order acknowledgment (message type ORDRSP with the message variant VMI). Repeat this procedure for all VMI Customers. Access the activity using one of the following navigation options: SAP R/3 Role Menu Transaction Code Creating Condition Records NACE 2.

an IDoc template is created in the R/3 system. On the Test Tool for IDOC Processing screen. ES7CLNT031 LS Choose the logical system. Enter the message code: Description User action and values VMI Note e. you may receive an error message.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3. As the template contains only sample data. Procedure 1.g. Change the sender data: Field name Port Partner number Partner type 8. which is assigned to your client 7. This IDoc can be used as a template for further inbound processing of sales order data.4 Creating IDOC Template ORDCHG Use An IDoc of the message category ORDCHG is used for transferring the purchase order number to the vendors’ SAP R/3 system after the purchase order has been generated in the customers system. 5. Access the transaction choosing one of the following navigation options: SAP R/3 menu Transaction code Tools → Business Communication → IDoc Basis→ Test → Test Tool WE19 2. C6220 KU Choose the partner profile © SAP AG Page 34 of 42 . SAPES7 User action and values ORDCHG Comment Default message type. 6. Note The receiving system is always an SAP system.g. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID>) Partner number Partner type e. Select the ORDERS05 IDoc type and choose Continue. Change the recipient data: Field name Port User action and values e. which you can ignore.4. Choose Create. make the following entries: Field name Via Message Type 3. In this step. Select the EDIDC line.g. 4.

Choose Insert and select at the same level. Choose Continue. © SAP AG Page 35 of 42 . 0000000116 Comment Vendor order Sales order number Result One IDoc template (message type ORDCHG) is created in the system. Description User action and values VMI Note 10.g. Choose Continue. 15. Description User action and values 000 e. 12.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field name Message code 9. EUR Comment 13. Double-click on the E1EDK02 line you have just created and make the following entries: Field name Qualifier Document 17. choose Continue. 14. Description User action and values 002 e.g.g. which will replace the fictitious purchase order number in the sales order. Double-click the E1EDK02 line and make the following entries: Field name Qualifier Document Description User action and values 001 e. 4711 Comment Customer purchase order Purchase order number of the customer’s system. Choose Continue. In the Test inbound IDoc using partner profile screen area. Double-click the E1EDK01line and make the following entries: Field name ACTION CURCY 11. 18. Choose Standard Inbound to enter the record. Choose Continue. Select the E1EDK02 line and choose Copy. The message IDoc number…transferred to application is displayed. 19. 16.

4. Select the line with function module IDOC_INPUT_ORDCHG_VMI. Access the activity choosing one of the following navigation options: SAP R/3 menu Transaction code 2. Choose Save and go back. 5. © SAP AG Page 36 of 42 .5 Checking Assignment Function Module and IDoc Type Use In this step check whether IDoc type ORDERS05 have been assigned to function module IDOC_INPUT_ORDCHG_VMI and the application object type BUS2032. Tools → Business Communication → IDoc Basis→ Inbound Processing Settings t → Message/application object WE57 Choose Change and confirm the messages. Change Basic Type to ORDERS05 if necessary. 4. Procedure 1. 3.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3.

2 Use Defining EDI Port (APO) The EDI port specifies how the IDocs are transferred to the EDI subsystem. select Transactional RFC and choose Create.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 4 EDI Settings for Collaborative Management of Delivery Schedules 4. for SAP APO or SAP R/3. © SAP AG Page 37 of 42 .1 Use Uploading the Configuration Role Before you start with the configuration according to the manual procedures described in this Configuration Guide. SAP Best Practices provides a configuration role for each component involved in this configuration. in the Ports screen area. you need to upload the configuration role and assign it to your user. refer to the document Essential Information. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Defining EDI Port (APO) WE21 Tools → Business Communication → IDoc Basis → Administration → PoDocrt Definition 2. The IDocs are read as sequential files. Procedure 1. The configuration role is a special user menu that enables you to comfortably access all necessary transactions for the configuration from the relevant system. that is. The following roles are available: Technical name S32_02C S32_01C Description Configuration role for SCM collaboration settings (SAP APO) Configuration role for SCM collaboration Settings (SAP R/3) Procedure For details on how to upload configuration roles to the system and how to work with them. On the Ports in IDoc processing screen. 4.

MY SAP APO Port. On the Partner Profiles: Inbound parameters screen. AS7CLNT001. e.3 Use Creating Partner Profiles To enable IDoc communication. 9.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 3. A000000036 and a description. 5. 3. In the Version screen area. enter the message type DELINS. choose Create from the application toolbar. Permitted users Value e.0x 6. AS7CLNT001 a customer. choose Create from the application toolbar. or a logical system. Enter a port e. your user ID © SAP AG Page 38 of 42 . Confirm the dialog box that is displayed.g. e. In the Inbound parameters screen area. number Partn.g. On the Partner Profiles screen. Procedure 1. The partner type determines the partner master data read by the IDoc interface. Choose Save. choose Create inbound parameter. US (User) e. 8. 10. In the Partner Profiles screen area.g. Go to the Post processing: permitted agent tab and make the following entries: Field Type Agent 5. 4. LS 4. select IDOC Record Types SAP Release 4. Go to the Inbound options tab page and enter the process code /SAPAPO/DELI. 4. On the Partner Profiles screen.g. e. partners must be defined with inbound or outbound parameters. 7. type Description Value Number which uniquely identifies a vendor.g.g. make the following entries: Field Partn. 7. Description Classifies the recipient of error notifications. Save and go back. Enter an RFC destination e.g. Access the activity using one of the following navigation options: SAP APO Role Menu Transaction Code SAP Menu Creating Partner Profiles (APO) WE20 Tools → Business Communication → IDoc Basis → Administration → Partner Profile 2. 6. Choose Save.

pack size. e. 14. AS000000036. 5. The partner type determines the partner master data read by the IDoc interface. an IDoc template is created in the APO system. In the Partner Profiles screen area. for Output mode. Choose Create. your user ID 4.g. e. US (User) e. 4. make the following entries: Field name Via Message Type 3.g. This IDoc can be used as a template for further inbound processing of delivery schedules. Go to the Post processing: permitted agent tab and enter the following values: Field Type Agent 13. e. there may be an error message which you can ignore. Procedure 1. enter the message type DELCONF. Save and go back.g. 15. 19.g. On the Partner Profiles: Inbound parameters screen. e. 1. Change the recipient data: User action and values DELINS Comment Default message type © SAP AG Page 39 of 42 . number Partn. AD 12. Description Classifies the recipient of error notifications Permitted users Value e. make the following entries: Field Partn.g.g. choose Create Outbound parameter. On the Test Tool for IDOC Process screen.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 11. type Description Value Number which uniquely identifies a vendor. Choose Save. or a logical system. In the Outbound parameters screen area. Select the EDIDC line. Keep the content of Basic type field as DELFOR01. 16. 18. Select Transfer IDOC immed. As the template contains only sample data. enter a receiver port. 0 a customer. Access the transaction choosing one of the following navigation options: SAP APO menu Transaction code Tools → Business Communication → IDoc Basis→ Test → Test Tools WE19 2.4 Use Creating IDOC Templates In this step. 17. On Outbound Options tab page.

which is assigned to your client 6.g. EXT-AS82-3000 Comment Partner’s (customer) vendor number Description User action and values e. AS7CLNT001 LS Choose the partner profile Dlv. 10 e.g. Double-click the E1EDP10 line and make the following entries: Field name IDNKD Description Partner’s (customer) material number User action and values e. AS7CLNT001 LS Choose the logical system. LF e.g.g. 10 User action and values e.g.schedule Dlv.g.g.g.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field name Port User action and values e. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID> (e. Expand the structure of E1EDK09. 1 day before current date 9.g. A000000036 Note e.g.date e. Function Partner 12. SAPAT7) Partner number Partner type e. 55000000 e.g. Change the sender data: Field name Port Partner number Partner type 7. SAPAS7 Note The receiving system is always an SAP system. Choose Continue 8.g. current date e. Double-click the E1EDKA1line and make the following entries: Field name Part. 13. L8001 © SAP AG Page 40 of 42 . 10. Choose Continue. 11.g.sched.schedule Partner’s contract line number Partner’s delivery schedule line number Date of previous delivery schedule Description Partner’s (customer) contract number User action and values e. Double-click the E1EDK09 line and make the following entries: Field name Contract number PO date Dlv. Choose Continue.

5000 e. 1st day of the week three weeks from now for forecast Comment EDATUV Format YYYYMMDD EZEIT Time at which the delivery schedule was created The date to which the schedule line is valid e. weekly.g.g. 1000 e. 5000 for JIT e. 1200 EDATUB e. D for JIT e.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide Field name ARKTX VRKME LFIMG VEMNG ABHOR Description Partner’s (customer) material description ISO unit The latest quantity delivered to the customer The latest quantity received by the customer Date up to which the just-intime delivery schedule is valid User action and values e. Choose Continue. 03 for forecast 14.g. current date + 2 weeks Comment JIT Horizon Format YYYYMMDD AKUEM SCREL The cumulated quantity received by the customer Specify the release type e. ABS system e. 1st day of the week 4 weeks from now for forecast WMENG The quantity of items in the schedule line The cumulated quantity of the schedule line e. 15.g.g. 50000 for forecast FZABR 17. Choose Continue. monthly The date from which the schedule line is valid User action and values e.g. 1000 e.g. 1st day of next week for JIT e. Double-click the E1EDP16 line and make the following entries: Field name PRGRS Description Date type such as daily.g.g. © SAP AG Page 41 of 42 .g. 1st day of next week for JIT e. 1000 for JIT e. Expand the structure of E1EDP10.g.g. W for forecast e.g.g.g.g.g. 16. 10000 for forecast e.g. PCE e.g. 02 for JIT e.

The message IDoc number…transferred to application is displayed.SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide 18. 20. © SAP AG Page 42 of 42 . Result One operative delivery schedule and one forecast delivery schedule has been created in the system. Choose Standard Inbound to enter the record. 21. choose Continue. In the Test inbound IDoc using partner profile dialog box. 19. Repeat steps 5 to 17 to generate a forecast delivery schedules.