Building Block SNC Colloboration

SAP SCM 4.0

March 2004

English

Building Block SCM Collaboration Settings

SAP AG Neurottstr. 16 69190 Walldorf Germany

Building Block Configuration Guide

SAP Best Practices Building Block SCM Collaboration Settings: Configuration Guide

© SAP AG Page 2 of 42

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.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Content

1 Purpose................................................................................................................................. 5

2 Collaborative Planning.......................................................................................................... 6

2.1 Prerequisites .................................................................................................................. 6

2.2 Uploading the Configuration Role .................................................................................. 6

2.3 General Settings ............................................................................................................ 7

2.4 Collaborative Demand and Supply Planning ............................................................... 12

2.5 Collaborative Transportation Planning......................................................................... 22

3 EDI Settings for Vendor-Managed Inventory...................................................................... 25

3.1 Prerequisites ................................................................................................................ 25

3.2 Uploading the Configuration Role ................................................................................ 25

3.3 EDI Settings APO......................................................................................................... 25

3.4 EDI Settings R/3........................................................................................................... 30

4 EDI Settings for Collaborative Management of Delivery Schedules .................................. 37

4.1 Uploading the Configuration Role ................................................................................ 37

4.2 Defining EDI Port (APO) .............................................................................................. 37

4.3 Creating Partner Profiles.............................................................................................. 38

4.4 Creating IDOC Templates............................................................................................ 39



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.

The building block Configuration Guide describes how to manually configure a building block without using automated configuration tools. If you want to use BC sets and CATT procedures for an automated installation process, refer to the Installation Guide of this building block.



2 Collaborative Planning

2.1 Prerequisites

In order to be able to install and perform Collaborative Planning, you must have already installed the Internet Transaction Server (ITS).

If you want to install and run the section Collaborative Demand Planning, you must first install the building block Demand Planning.

Microsoft Internet Explorer 5.0 or a higher version is required by the external partner.

2.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 # Component Description

577845 SCM-APO-CA-COP CLP 40: Install ITS services for APO collaborative

2.2 Uploading the Configuration Role

Use

Before you start with the configuration according to the manual procedures described in this configuration guide, you need to upload the configuration role and assign it to your user.

SAP Best Practices provides a configuration role for each component involved in this configuration, that is, for SAP APO or SAP R/3. 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 Description

S32_02C 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, refer to the document Essential Information.



2.3 General Settings

2.3.1 Defining an RFC Destination

Use

Before you can send e-mails from your SAP APO system, you have to create an RFC destination and a node in SAPconnect. Outgoing messages are transferred from SAPconnect via RFC to the external communication system. First, you have to create an RFC destination.

Procedure

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

SAP APO Role Menu Defining an RFC Destination

Transaction Code SM59

SAP Menu Tools � Administration � Administration � Network � RFC Destinations

2. Choose Create (F8)

3. Make the following entries according to the RFC destination:

Field Entry

RFC destination SEND_MAIL

Connection Type T (TCP/IP)

Description RFC destination for outgoing Internet messages

4. Choose Enter.

Activity type Start on Explicit host

Program For example, “/mail/sap/OUT/mlunxsnd”

Target Host For example, “mailgwo.wdf.sap.corp”

Save As IP address

If the SAP Gateway is not running on the current application server, specify the SAP Gateway you want to use to establish the connection to the Internet Mail Gateway server.

5. Choose Destination → Gateway options.

Gateway Host <R/3 gateway host>, for example, “mailsig.wdf.sap.corp”

Gateway service <R/3 gateway service>, for example, “sapgw88”

6. Save your RFC destination.

7. Choose Test connection to test each connection.



2.3.2 Maintaining Settings in SAPconnect

Use

SAPconnect provides a standard interface for external communication. Every external communication system is represented by a node. A node represents a logical view of an external communication system in SAP R/3, for example, an e-mail system. It comprises information necessary to send messages from the SAP R/3 system via an external communication system.

The RFC destination and the Internet must be assigned as means of communication.

Procedure


SAP APO Menu Maintaining Settings in SAPconnect

Transaction Code SCOT

SAP Menu Tools → Business Communication → Communication → SAPconnect

2. To create a node for sending Internet messages, choose Create on the SAPconnect Administration screen. The Create nodes dialog box appears.

3. Enter a node and a description:

Field name User action and values

Node MAIL

Description Outgoing Internet messages

4. Choose Continue.

5. Select RFC Node, if necessary. If the RFC Node radio button is active, choose Continue.

6. Make the following entry:


RFC Destination SEND_MAIL

7. Choose Continue.

8. Select the following option:


Address type Internet

9. Choose Continue.



Address area *



11. Choose Continue.

12. Confirm the following output formats:


SAPscript/Smart Forms PDF

ABAP List HTM

Business Object/Link HTM

RAW Text TXT




Restrict send time Deselect




Set further address types? N


18. Make the following entries:


Hours 0

Minutes 0


20. Deselect the following fields:


Node can resolve path references Deselect

Node is to be monitored by the alert monitor Deselect


22. Select the following fields:


Node is ready for use Select

Node supports: Connection test, status, trace Deselect

23. Choose Continue to save the node.



2.3.3 Scheduling the Background Job

Use

The send process reads messages to be sent from the Business Communication Interface queue. Moreover, the send process determines the appropriate nodes and transfers messages to external communication systems. Therefore, messages are sent externally only if regular send processes have been scheduled.

Procedure


SAP APO Menu Scheduling the Background Job


SAP Menu Tools � CCMS � Jobs � Definition


Field Value

Job name SEND_MAIL

Job class B (Medium priority)

3. Choose Return.

4. On the Create Step 1 screen, choose ABAP program and make the following entries:

Name RSCONN01

Variant INT

5. Choose Save.

6. Choose Start condition (F5) to specify a period and start conditions:

Start time Immediate start

Periodic job Select

7. Choose Period values (F5).

8. Choose Other period to specify an individual period, for example, 5 minutes:

Month(s) 0

Week(s) 0

Day(s) 0

Hour(s) 0

Minute(s) 5

9. Choose Save to save the period values.

10. Choose Save to save the start condition.

11. Choose Save to save the job definition and release the job.



2.3.4 Assigning the Logical Web Server

Use

Assign a logical Web server to the logical system, so that collaborative planning services can be run via the SAP easy access menu.

Procedure


SAP APO Menu Assigning the Logical Web Server


SAP Menu System → Services → Table maintenance → Extended table maintenance

2. In the Maintain Table Views: Initial screen, enter TWPURLSVR in the Table/View field and choose Maintain.

3. Ignore the message “Table is cross –client”

4. In the Change view Logical Web Servers for Logical Systems screen, make the following entries:

Field Comment

LogSystem Name of the logical system you are working with (e.g. AT7CLNT001)

Web server Name of the ITS web server with the accompanying port (e.g. PGAT7F.WDF.SAP-AG.DE:1080)

Web Protocol The protocol to be used (HTTP or HTTPS)

5. Save and go back.



2.3.5 Maintaining the Internet Mail Address

Use

If you want to send e-mails from SAP APO, you need to assign your e-mail address to your user.

Procedure


SAP APO Role Menu Maintaining the Internet Mail Address

Transaction Code SU01

SAP Menu Tools → Administration → User Maintenance → Users

2. On the User Maintenance screen, enter your Internet e-mail address (e.g. [email protected]).


2.4 Collaborative Demand and Supply Planning

2.4.1 Creating and Uploading the Mail Template

Use

During the collaborative planning process, the collaboration partner is notified via e-mail that a draft demand plan is available. This procedure describes how to create and upload an e-mail template.

Procedure

1. Create a text for an e-mail in Microsoft Word and save it as a txt.file (text only *.txt) on your computer.

2. A default template for e-mails is provided: "Template_Mail.txt". You can use it, but you have to delete the URL first and enter the correct URL as described below.

3. Copy the URL of the Collaborative Planning Book into your document.

4. You can access this URL via the path Demand Advanced Planning and Optimization �

Demand Planning → Planning → Collaborative Demand Planning (transaction /SAPAPO/CLPISDP).

The Internet browser is opened and the APO Collaborative Planning screen is displayed.

5. Copy the URL and include it into your txt. file.

An example of a hyperlink: http://pgas7w1.wdf.sap-ag.de:1080/scripts/wgate/clpsdp/!?~language=en&~client=001)



6. To upload the file to the APO system, proceed in the following way:

SAP APO Menu Creating and Uploading the Mail Template

Transaction Code OAER

SAP Menu Tools → Business Documents → Miscellaneous → Business documents

7. On the Business Document Navigator screen, make the following entries:

Field Value

Class name DP_SNP

Class type OT

Object key DP_SNP

8. Choose Execute.

9. On the Create tab page, expand the folder Select a document type or application.

10. Double-click Text.

11. In the Business Document Navigator: File Selection dialog box, select the txt.file (for example C:\Template_mail.txt) and choose Open.

12. In the Business Document Navigator dialog box, enter a description and choose Continue.

13. Go back.

Troubleshooting

If the error message “Knowledge Provider error: Object does not exist” is displayed, access the transaction SBDSV1 and create the following entry:

Field Value

Class name DP_SNP

Class type Other objects

DocuClass BDS_LOC2

DocuClass BDS_POC2

DocuClass BDS_REC2

Object name BDS_CONN05



2.4.2 Creating the Distribution List

Use

This step allows you to create a distribution list containing your collaboration partner’s e-mail address.

Procedure


SAP APO Menu Creating the Distribution List

Transaction Code SO04

SAP Menu Office → Folders → Shared Folders

2. Select Shared folders.

3. Choose Folder → Create from the menu bar.

4. In the Create folder dialog box, enter the folder name CLP, the description DL CLP, and choose Transfer.

The CLP subfolder is displayed.

5. Select CLP.

6. Choose the right part of the Create document button.

7. Choose Create more...

8. In the Title screen area, enter DL CLP.

9. On the Attributes tab page, enter DLI.

10. Select the Document contents tab.

11. On the Attributes tab page, enter DL CLP.

12. On the Distr. list content tab page, in the Recip. type screen area, enter the recipient's e-mail address and choose Internet address.


2.4.3 Creating User for Collaboration Partner

Use

In this step, you create a user for your collaboration partner (e.g. partner or customer) in APO.



Procedure


SAP APO Role Menu Creating User for Collaboration Partner

Transaction Code SU01

SAP Menu Tools → Administration → User Maintenance → Users

2. Enter a user name.

3. Choose Create or Copy.

4. On the Logon data tab page, enter the initial password.

5. On the Profile tab page, assign a profile.

6. On the Parameters tab page, enter the parameter /sapapo/clp_webgraph, value X (with a capital X), which enables you to show a graphical representation of your data in the Internet planning book.

7. On the Parameters tab page, enter the parameter /sapapo/clp_webnote, value X (with a capital X), which enables you to enter notes in the Internet planning book.

8. On the Parameters tab page, enter: Parameter /sapapo/clp_webdown, value XLS (with a capital XLS), which enables you to export data and process it in Microsoft Excel.


2.4.4 Collaborative Demand Planning

2.4.4.1 Creating Macros in the Planning Book

Use

In this step, you create a macro allowing you to send e-mails directly from your planning book using a pushbutton.

Procedure


SAP APO Menu Creating Macro in Planning Book

Transaction Code /SAPAPO/SDP8B

SAP Menu Advanced Planning and Optimization � Demand Planning →

Environment → Current settings → Define Planning Book

2. Enter the planning book DP_001 and the data view DP_STANDARD.

3. Select Data view.

4. Choose Edit.



5. The Planning Book: Demand Planning – Standard dialog box is displayed. Choose MacroBuilder.

6. Choose MacroBuilder → Data view. The view APO Macro Builder is displayed.

7. Right-click on the macro node below the planning table and choose Add macro. Enter a Descriptive Text (e.g. Send mail to partner) and assign a pushbutton, which should appear in the planning book. Choose Continue.

8. Right-click the new macro and choose Add macro step. Enter a descriptive text (e.g. Mail), choose User defined (Iterations 1) and choose Continue.

9. Right-click the new macro and choose Add mail. In the dialog box, add a title (e.g. PLANNING DATA HAS BEEN CHANGED), the document text (see Chapter Mail Template) and the recipient (see Chapter Distribution List).

10. Select the new macro.

11. Choose Check.

12. Choose Generate to generate the macro.

13. Go back.

14. Choose Save and Save All.

15. Go back.

2.4.4.2 Assigning User to Planning Book

Use

This procedure enables you to assign a user to the planning book and data view. You can restrict the user’s access to one book and one view.

Procedure


SAP APO Role Menu

Assigning a User to a Planning Book

Transaction Code /SAPAPO/SDPPLBK

SAP Menu Advanced Planning and Optimization → Demand Planning →

Environment → Current Settings → Assign User to Planning Book

2. Make your first entry without a transaction code as shown in the table below:

Name Trans. Code Plng book Data view Specific book Fixed View

e.g. WEBUSER

DP_001 DP_CLP Do not select Select

e.g. WEBUSER

/SAPAPO/SDP94 DP_001 DP_CLP Do not select Select




2.4.4.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. After creating a selection of products, assign it to a user selection profile in order to make it visible to the collaboration partner in collaborative demand planning.

Procedure

1. Log on with the new user you have created in the activity "Creating User for Customer / Partner".

SAP APO Role Menu Maintaining Selection Profiles for User

Transaction Code /SAPAPO/SDP94


Planning → Interactive Demand Planning

2. Create a selection of products that are assigned to the user (i.e. to which the user will have access). Proceed in the following way:

3. Choose Selection window.

4. In the Object selection dialog box, in the Show screen area, choose APO Product.

5. Enter the planning version 000 in the field to the right of the APO Planning Version field

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

7. Choose Save selection.

8. Enter the name of the user as the selection text and choose Save.

9. Store saved selections by choosing Maintain selection profile and using drag & drop to transfer the saved selection from the right to the left area.

10. Choose Save and Copy.

You can access the objects by double-clicking the selection. The system displays them in a table.

11. Go back.



2.4.5 Collaborative Supply Planning

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

Prerequisites

You have set up the vendor master data, material master and relevant purchase scheduling agreement in the SAP R/3 system. This data needs to be transferred to SAP APO through the Integration Model.

Procedure

1. Access the activity using the following navigation options:

SAP R/3 Role Menu Change Scheduling Agreement

Transaction Code ME32L

SAP Menu Logistics → Material Management →Purchasing →Outline

Agreement → Scheduling Agreement → Change

2. Enter the number of the Scheduling Agreement, e.g. 5500000002, and choose Overview.

3. Select the line item that contains the material for which the scheduling agreement was set up and choose Additional Data.

4. In the Administration screen area, check whether the content of the Ext Planning field is 1. If

it is not, change it to this value.

5. Save your entries.

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

Procedure


SAP APO Role Menu

Procurement Relationships



Transaction Code /SAPAPO/PWBSRC1

IMG Menu Advanced Planning and Optimization → Master Data →

Procurement Master Data → Procurement Relationships

2. On the External Procurement Relationships screen, make the following entries:

Field name Description User action and values Notes

Destination Location

e.g. PLBP01/KD6416

Product Number e.g. HT61PR-1100

Scheduling Agreement

e.g. Select

3. Choose Execute to enter the Display External Procurement Relationships screen.

4. In the left screen area, under APO sch. agmt. select the document line that matches your product, location combination, then choose Display<->Change to access the change mode.

5. On the right side of the screen, choose Sch. Agmt. tab page, make the following entries:


Update LiveCache e.g. 10

Process e.g. 04

6. Choose Save to save your entries and exit.

2.4.5.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, if necessary. Transportation lanes represent the buying or selling relationship between partners. When you create the purchase scheduling agreement in SAP R/3 and transfer it to SAP APO, transportation lane between the supplier and plant has been created automatically. It is necessary to maintain a valid means of transport for this lane.

Procedure

1. Access the activity using the following navigation options:

SAP APO

Role Menu

Transportation Lane

Transaction Code /SAPAPO/SCC_TL1

IMG Menu Advanced Planning and Optimization → Master Data →

Transportation Lane→ Transportation Lane

2. On the Transportation Lane: Access screen, make the following entries:




Model Name e.g. 000

Start Location e.g. SUH6100/KD6416

Dest. Location e.g. PLBP01/KD6416

3. Choose Change icon to go on to the next screen;

4. On the Change Transportation Lane:… screen, check whether there is a valid means of transport for all product or a valid Means of Transport for your specific product. If there is, you can exit to finish this process, otherwise continue following steps to create one.

5. Choose Creation of New Entry, and make the following entries:


Means of Trans e.g. 0001

Start Date e.g. 01012004

End Date e.g. 31122005

6. Choose Copy and Close icon to save your entries.

7. Choose Save and exit.

2.4.5.4 Assigning User to Planning Book

Use

This procedure enables you to assign a user to the planning book and data view. You can restrict the user’s access to one planning book and one view.

Procedure


SAP APO Role Menu Assigning a User to a Planning Book

Transaction Code /SAPAPO/SDPPLBK


Environment → Current Settings → Assign User to Planning Book

2. On the Data view Last Selected sheet, create three new records as in following table:

Make your first entry without a transaction code as shown in the table below:

Name Trans. Code Plng book Data view Specific book

Fixed View

e.g. 9ASAS SAS (1) Do not Select



Name Trans. Code Plng book Data view Specific book

Fixed View

WEBUSER select

e.g. WEBUSER

/SAPAPO/SNPSA 9ASAS SAS (1) Do not select

Select

e.g. WEBUSER

/SAPAPO/CLPISAP 9ASAS SAS (1) Do not select

Select


2.4.5.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. After creating a selection of products, assign it to a user selection profile in order to make it visible to the collaboration partner in collaborative demand planning.

Procedure

1. Log on with the new user you have created in the activity Creating User for Customer / Partner.

SAP APO Role Menu

Maintaining Selection Profiles for User

Transaction Code /SAPAPO/SNPSA

SAP Menu Advanced Planning and Optimization → Supply Network Planning →

Planning → Scheduling Agreements (Procurement) → Interactive Scheduling Agreements

2. Choose Selection window to create a selection of products that are assigned to the user (i.e. to which the user will have access).

3. In the Object selection dialog box, in the Show screen area, choose APO Locatn. Prod. Sched. Agrmnt.

4. Enter the planning version 000 in the field to the right of the APO Planning Version field.

5. Restrict the selection to products which are assigned to the user by selecting APO Product and entering the corresponding products number.

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

7. Choose Save selection.

8. Enter the name of the user as the selection text and choose Save.

9. Store saved selections by choosing Maintain selection profile and using drag & drop to transfer the saved selection from the right to the left area.



10. Choose Save and Copy.

To access the objects double-click the selection. The system displays them in a table.

11. Go back.

2.4.6 Sending User and Password to Collaboration Partner

Use

Inform the collaboration partner about the user and password you have created.

2.5 Collaborative Transportation Planning

2.5.1 Creating User for Collaboration Partner

Use

If you want to use collaborative planning, you have to create a user in SAP APO for your collaboration partner.

Procedure

1. Access the activity by choosing one of the following navigation options:

APO Menu SAP Menu → Tools → Administration → User Maintenance → Users

Transaction code SU01

The Maintain User screen is displayed.

2. Enter a user name (e.g. S8100).

3. Choose Create (F8).

4. On the Logon data tab page, in the Password screen area, enter an initial password.


6. Repeat steps 3 to 6 for each user.

2.5.2 Maintaining Collaboration Partners

Use

The purpose of this activity is to make the necessary settings for collaborative transportation planning.



Prerequisites

You have created one or more users in the APO system for the collaboration partners to enable them to access the system.

Procedure


APO Menu SAP Menu � Advanced Planning and Optimization � Transportation Planning/Vehicle Scheduling � Environment � Current Settings � Collaborative Transportation Planning � Make Settings for Collaborative Planning

Transaction code /SAPAPO/CLP_SETTINGS

2. In the Change View “Collaboration Partners”: Overview screen, choose Collaboration Partners and New Entries.

3. Enter a business partner and a partner description (e.g. S8100).

4. Double-click Communication settings, choose New Entries and select the collaborative scenario Transportation planning.

5. Select Sending of e-mails activated.

6. Choose Possible entries <F4>, select New Internet address and enter the e-mail address of the business partner (e.g. SAP internal user S8100 as internal mail address in SAP system).

7. Enter an e-mail subject and text for Announcement of planning steps and for Undo planning steps (e.g. Shipments created/deleted, Please check. Best regards).

8. Save your entries.

A transport request for workbench is displayed.

9. Select an existing request or create a new one, if necessary. Choose Continue.

10. Double-click User Assignment and choose New Entries.

11. Assign the user of the transportation planner to the collaboration partner and select Transportation RFQs.

12. Choose Save and go back.

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

Procedure


APO Menu SAP menu � Advanced Planning and Optimization � Master Data � Location � Location



Transaction /SAPAPO/LOC3

2. On the Location Master Data: Initial Screen, choose Transportation service provider and select the TSP that is used for collaboration.

3. Choose Change.

4. In the Change Location screen area, enter the collaboration partner (e.g. S8100).

5. Choose Save and go back twice.



3 EDI Settings for Vendor-Managed Inventory

3.1 Prerequisites

Your system landscape must be set up to enable the exchange of messages via Electronic Data Interchange (EDI).


Use

Before you start with the configuration according to the manual procedures described in this configuration guide, you need to upload the configuration role and assign it to your user.

SAP Best Practices provides a configuration role for each component involved in this configuration, that is, for SAP APO or SAP R/3. 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. The following roles are available:


S32_02C Configuration role for SCM collaboration settings (SAP APO)

S32_01C Configuration role for SCM collaboration settings (SAP R/3)

Procedure


3.3 EDI Settings APO

EDI is a concept that integrates business application systems. Its objective is to electronically interchange structured business data such as purchase orders, invoices and payment orders, and to automatically process this data in the recipient’s application system.

The IDoc (intermediate document) is used as the interchange format.

3.3.1 Defining EDI Port (APO)

Use

The EDI port specifies how the IDocs are transferred to the EDI subsystem. The IDocs are read as sequential files.



Procedure


SAP APO Role Menu Defining EDI Port (APO)

Transaction Code WE21

SAP Menu Tools → Business Communication → IDoc Basis → Administration

→ Port Definition

2. On the Ports in IDoc processing screen, in the Ports screen area, select File and choose Create.

3. Enter a port, such as VMI and a description, for example, VMI Port.

4. On the Outbound File, Outbound Trigger, Inbound File, Status File tab pages, enter a physical directory (e.g. D:\usr\sap\AT7\SYS\global\ ).

Do not forget the last slash, as the file name is simply appended as a directory! AT7 is the name of the APO system in the example.

5. On the Outbound File, Inbound File, Status File tab pages, enter the EDI_PATH_CREATE_USERNAME function module.


3.3.2 Creating Partner Profiles (SAP APO)

Use

To enable IDoc communication, partners must be defined with inbound or outbound parameters.

Procedure


SAP APO Role Menu Creating Partner Profiles (APO)


SAP Menu Tools → Business Communication → IDoc Basis →

Administration → Partner Profile

2. On the Partner Profiles screen, choose Create from the application toolbar.

3. On the Partner Profiles screen, make the following entries:

Field Description Value

Partn. number Number that uniquely identifies a vendor, customer, or a logical system.

e.g. C6220

Partn. type The partner type determines the partner master data read by IDoc interface.

KU



4. Go to the Post processing: permitted agent tab page and make the following entries:


Type Classifies the recipient of error notifications US (User)

Agent Permitted users Your username

5. Choose Save.

6. In the Inbound parameters screen area, choose Create inbound parameter.

7. On the Partner Profiles: Inbound parameters screen, enter the message type PROACT.

8. Go to the Inbound options tab page and enter the process code PRAC_APO.


3.3.3 Creating IDOC Template PROACT

Use

In this step, you create an IDoc template in the SAP APO system. As the template contains only sample data, you may receive an error message, which you can ignore. This IDoc can be used as a template for further inbound processing of planning data.

Procedure

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

SAP APO menu Tools → Business Communication → IDoc Basis→ Test → Test Tools

Transaction code WE19

2. On the Test Tool for IDOC Process screen, make the following entries:

Field name User action and values Comment

Via Message Type PROACT Default message type

3. Choose Create.

4. Select the IDoc segments’ line EDIDC.



Note

Port e.g. SAPAS7 The receiving system is always an SAP system. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID> (e.g. SAPAT7)

Partner number

e.g. AS7CLNT001

Choose the logical system that is assigned to your client

Partner type LS



6. Choose Continue.

7. Change the sender data:

Field name Description User action and values Note

Port VMI

Partner number e.g. CUC6220 Choose the partner profile

Partner type KU

8. Double-click the E1ADRM1 line and make the following entries:

Field name Description User action and values Comment

PARTNER_Q Partner qualifier WE Ship-to party

PARTNER_ID e.g. CUC6220/ES7031

9. Choose Continue.

10. Select the E1ADRM1 line and choose Copy.

11. Choose Insert and select at the same level.

12. Double-click the E1ADRM1 line you have just created and make the following entries:


PARTNER_Q Partner qualifier LF Vendor

PARTNER_ID e.g. CUC6220/ES7031


14. Expand the structure of E1ADRM1.

15. Double-click the E1ADRE1 line and make the following entries:


EXTEND_Q 300 Own account number for recipient

EXTEND_D e.g. CUC6220/ES7031


17. Expand the structure of E1EDP31.

18. Double-click the E1EDP19 line and make the following entries:


Identification e.g. 002 Material number of vendor

Material e.g. APO-FERT-03

19. Double-click the E1EDP32 line, and make the following entries:


QUALF 003 Sales




QUANTITY e.g. 5000

UNIT e.g. PCE

DATE e.g. 20031101 For example, enter the values Date =’20031101’, Time = ‘000000’, Date_to = ‘20031130’ and Time_to = ‘235959’ to specify the quantity for November 2003

TIME e.g. 000000

DATE_TO e.g. 20031130

TIME_TO e.g. 235959


21. Choose Standard Inbound to enter the record.

22. In the Test inbound IDoc using partner profile dialog box, choose Continue.

23. The IDoc number…transferred to application message is displayed.

Result

One IDoc template (message type PROACT) is created in the system.



3.4 EDI Settings R/3

3.4.1 Defining EDI Port (R/3)

Use


Procedure


SAP R/3 Role Menu Defining EDI Port (R/3)


R/3 Menu Path Tools → Business Communication → IDoc Basis → Administration

→ Port Definition

2. On the Ports in IDoc processing screen, in the Ports screen area, select File and choose Create.

3. Enter a port, e.g. VMI, and a description, e.g. File Port VMI.

4. On the Outbound File, Outbound Trigger, Inbound File, Status File tabs, enter a physical directory (e.g. D:\usr\DS7\SYS\global\).

5. On the Outbound File, Inbound File, Status File tab pages, enter the function module EDI_PATH_CREATE_USERNAME.

Do not forget the last slash, as the file name is simply appended as a directory! DS7 is the name of the R/3 system in the example.




3.4.2 Creating Partner Profiles (SAP R/3)

Use

Partner profiles are necessary for IDoc inbound/outbound processing.

Procedure


SAP R/3 Role Menu Creating Partner Profiles (R/3)



Administration→ Partner Profile


3. In the Partner Profiles screen area, enter the following values:


Partn. number Number that uniquely identifies a vendor, customer, or a logical system.

e.g. C6100

Partn. type The partner type determines the partner master data the IDoc interface reads.

KU

4. Go to the Post processing: permitted agent tab page and enter the following values:


Type Classifies the recipient of error notifications. US (User)

Agent Permitted users Your username

5. Choose Save.

Outbound Parameters

1. In the Outbound parameters screen area, choose Create Outbound parameter.

2. On the Partner Profiles: Outbound parameters screen, make the following entries:


Partn fnct SP

Message type ORDRSP

Message code VMI

3. Choose Test.

4. On the Outbound options tab page, make the following entries:




Receiver port Specifies how the IDocs are transferred to the EDI subsystem. The port must be created in the port description first.

e.g. SAPES7

Transfer IDoc Immed X

Basic type ORDERS01

Syntax check X

5. On the Message control tab page, choose Insert row and make the following entries:


Application V1

Message type BAV0

Process code SD10

6. On the EDI Standard tab page, make the following entries:


EDI standard Defines the general interpretation scheme which is used as a basis for translating an IDoc type into an EDI data structure.

E (EDIFACT)

Message type ORDERS

Version 001


Inbound Parameters

1. In the Inbound parameters screen area, choose Create Outbound parameter.

2. On the Partner profiles: Inbound parameters screen, make the following entries:


Partn. funct. Using this optional parameter, you can specify the partner function containing the sender and the recipient

SP

Message type ORDCHG

Message code For further messages’ separation. VMI

Test X

3. On the Inbound options tab page, make the following entries:


Process code A process code identifies the type of data processing for inbound processing.

ORDM




Syntax check X

Trigger immediately X


3.4.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). In the standard system, order acknowledgments are generated for sales orders as messages of the type BAV0. You must create the required condition records for this.

Procedure


SAP R/3 Role Menu

Creating Condition Records

Transaction Code NACE

2. Select application V1 and choose Condition records.

3. Select BAV0 (Order confirm. VMI) and choose Condition records.

4. On the Change Order confirm. (BAV0): Selection screen, make the following entry :


Sales Organization e.g. BP01

Sales document type

5. Choose Execute.

6. On the Change condition records (Order Confirmation VMI): Fast Change screen, make the following entries:


Sales document type TAV

Partner Function SP

Partner e.g. C6100

Medium 6


8. Repeat this procedure for all VMI Customers.



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

In this step, an IDoc template is created in the R/3 system. As the template contains only sample data, you may receive an error message, which you can ignore. This IDoc can be used as a template for further inbound processing of sales order data.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP R/3 menu Tools → Business Communication → IDoc Basis→ Test → Test Tool


2. On the Test Tool for IDOC Processing screen, make the following entries:


Via Message Type ORDCHG Default message type.

3. Choose Create.

4. Select the ORDERS05 IDoc type and choose Continue.

5. Select the EDIDC line.

6. Change the recipient data:

Field name User action and values Note

Port e.g. SAPES7 The receiving system is always an SAP system. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID>)

Partner number e.g. ES7CLNT031 Choose the logical system, which is assigned to your client

Partner type LS



Port VMI

Partner number e.g. C6220 Choose the partner profile

Partner type KU

8. Enter the message code:




Message code VMI

9. Choose Continue.

10. Double-click the E1EDK01line and make the following entries:


ACTION 000

CURCY e.g. EUR


12. Double-click the E1EDK02 line and make the following entries:


Qualifier 001 Customer purchase order

Document e.g. 4711 Purchase order number of the customer’s system, which will replace the fictitious purchase order number in the sales order.


14. Select the E1EDK02 line and choose Copy.

15. Choose Insert and select at the same level.

16. Double-click on the E1EDK02 line you have just created and make the following entries:


Qualifier 002 Vendor order

Document e.g. 0000000116 Sales order number



19. In the Test inbound IDoc using partner profile screen area, choose Continue.

The message IDoc number…transferred to application is displayed.

Result

One IDoc template (message type ORDCHG) is created in the system.



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

Procedure

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

SAP R/3 menu Tools → Business Communication → IDoc Basis→ Inbound

Processing Settings t → Message/application object


2. Choose Change and confirm the messages.

3. Select the line with function module IDOC_INPUT_ORDCHG_VMI.

4. Change Basic Type to ORDERS05 if necessary.

5. Choose Save and go back.



4 EDI Settings for Collaborative Management of Delivery Schedules


Use

Before you start with the configuration according to the manual procedures described in this Configuration Guide, you need to upload the configuration role and assign it to your user.

SAP Best Practices provides a configuration role for each component involved in this configuration, that is, for SAP APO or SAP R/3. 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:


S32_02C

Configuration role for SCM collaboration settings (SAP APO)

S32_01C

Configuration role for SCM collaboration Settings (SAP R/3)

Procedure


4.2 Defining EDI Port (APO)

Use

The EDI port specifies how the IDocs are transferred to the EDI subsystem. The IDocs are read as sequential files.

Procedure


SAP APO Role Menu Defining EDI Port (APO)



Administration → PoDocrt Definition

2. On the Ports in IDoc processing screen, in the Ports screen area, select Transactional RFC and choose Create.



3. Confirm the dialog box that is displayed.

4. Enter a port e.g. A000000036 and a description, e.g. MY SAP APO Port.

5. In the Version screen area, select IDOC Record Types SAP Release 4.0x

6. Enter an RFC destination e.g. AS7CLNT001.


4.3 Creating Partner Profiles

Use


Procedure


SAP APO Role Menu Creating Partner Profiles (APO)



Administration → Partner Profile


3. In the Partner Profiles screen area, make the following entries:


Partn. number Number which uniquely identifies a vendor, a customer, or a logical system.

e.g. AS7CLNT001

Partn. type The partner type determines the partner master data read by the IDoc interface.

e.g. LS

4. Go to the Post processing: permitted agent tab and make the following entries:


Type Classifies the recipient of error notifications.

e.g. US (User)

Agent Permitted users e.g. your user ID

5. Choose Save.

6. In the Inbound parameters screen area, choose Create inbound parameter.

7. On the Partner Profiles: Inbound parameters screen, enter the message type DELINS.

8. Go to the Inbound options tab page and enter the process code /SAPAPO/DELI.

9. Choose Save.




11. In the Partner Profiles screen area, make the following entries:


Partn. number Number which uniquely identifies a vendor, a customer, or a logical system.

e.g. 0

Partn. type The partner type determines the partner master data read by the IDoc interface.

e.g. AD

12. Go to the Post processing: permitted agent tab and enter the following values:


Type Classifies the recipient of error notifications e.g. US (User)

Agent Permitted users e.g. your user ID

13. Choose Save.

14. In the Outbound parameters screen area, choose Create Outbound parameter.

15. On the Partner Profiles: Inbound parameters screen, enter the message type DELCONF.

16. On Outbound Options tab page, enter a receiver port, e.g. AS000000036, pack size, e.g. 1.

17. Select Transfer IDOC immed. for Output mode.

18. Keep the content of Basic type field as DELFOR01.


4.4 Creating IDOC Templates

Use

In this step, an IDoc template is created in the APO system. As the template contains only sample data, there may be an error message which you can ignore. This IDoc can be used as a template for further inbound processing of delivery schedules.

Procedure

1. Access the transaction choosing one of the following navigation options:

SAP APO menu Tools → Business Communication → IDoc Basis→ Test → Test Tools


2. On the Test Tool for IDOC Process screen, make the following entries:


Via Message Type DELINS Default message type

3. Choose Create.

4. Select the EDIDC line.

5. Change the recipient data:




Port e.g. SAPAS7 The receiving system is always an SAP system. The EDI subsystem must determine the system ID and write it to the field in the form SAP<SYS-ID> (e.g. SAPAT7)

Partner number e.g. AS7CLNT001 Choose the logical system, which is assigned to your client

Partner type LS



Port e.g. A000000036

Partner number e.g. AS7CLNT001 Choose the partner profile

Partner type LS

7. Choose Continue

8. Double-click the E1EDK09 line and make the following entries:

Field name Description User action and values

Contract number Partner’s (customer) contract number

e.g. 55000000

PO date e.g. current date

Dlv.schedule Partner’s contract line number e.g. 10

Dlv.schedule

Partner’s delivery schedule line number

e.g. 10

Dlv.sched.date Date of previous delivery schedule e.g. 1 day before current date

9. Choose Continue.

10. Expand the structure of E1EDK09.

11. Double-click the E1EDKA1line and make the following entries:

Field name Description User action and values

Part. Function e.g. LF

Partner Partner’s (customer) vendor number e.g. L8001




IDNKD Partner’s (customer) material number

e.g. EXT-AS82-3000




ARKTX Partner’s (customer) material description

e.g. ABS system

VRKME ISO unit e.g. PCE

LFIMG The latest quantity delivered to the customer

e.g. 1000

VEMNG The latest quantity received by the customer

e.g. 1000

ABHOR Date up to which the just-in-time delivery schedule is valid

e.g. current date + 2 weeks

JIT

Horizon

Format

YYYYMMDD

AKUEM The cumulated quantity received by the customer

e.g. 5000

SCREL Specify the release type e.g. 02 for JIT

e.g. 03 for forecast


15. Expand the structure of E1EDP10.


Field name

Description User action and values Comment

PRGRS Date type such as daily, weekly, monthly

e.g. D for JIT

e.g. W for forecast

EDATUV

The date from which the schedule line is valid

e.g. 1st day of next week for

JIT

e.g. 1st day of the week

three weeks from now for

forecast

Format

YYYYMMDD

EZEIT

Time at which the delivery schedule was created

e.g. 1200

EDATUB The date to which the schedule line is valid

e.g. 1st day of next week for

JIT

e.g. 1st day of the week 4

weeks from now for forecast

WMENG The quantity of items in the schedule line

e.g. 1000 for JIT


FZABR The cumulated quantity of the schedule line

e.g. 5000 for JIT






19. In the Test inbound IDoc using partner profile dialog box, choose Continue.

20. The message IDoc number…transferred to application is displayed.

21. Repeat steps 5 to 17 to generate a forecast delivery schedules.

Result

One operative delivery schedule and one forecast delivery schedule has been created in the system.

Date post:	03-Jan-2016
Category:	Documents
Upload:	jayakumargj
View:	141 times
Download:	14 times