Scheduling Agreement Documentation

EDI Scheduling Agreement Documentation

Document Number: SAPGENIE1Authored by: Kevin Wilson

([email protected])

Revision: 17/4/2002

Deviations incorporated in this revision.Listed below are changes since the 10th of May 2001 release of the document1) REVISION 1 – 7/4/2002

Original document for release

CONFIDENTIAL – DO NOT DUPLICATE

mailto:[email protected]

IT Document, Work Instructions, Designs Document number: SAPGENIE1Document deemed to be current on date printed: 4/28/2023 Rev: 1CONFIDENTIAL – DO NOT DUPLICATE Page 2 of 7

TABLE OF CONTENTS TABLE OF CONTENTS------------------------------------2

CHAPTER 1 INTRODUCTION 3

1.1 PURPOSE--------------------------------------------31.2 AUDIENCE-------------------------------------------31.3 SCOPE-------------------------------------------------3

CHAPTER 2 EDI PROCESS 4

2.1 TRADING PARTNER X---------------------------42.1.1 SD PROCESS ASSUMPTIONS.....................4

CHAPTER 3 SAP DETAIL 5

3.1 SAP CONFIGURATION---------------------------53.1.1 OVERVIEW................................................53.1.2 SAP CUSTOMERS (XD01)........................5

Appendix A. Test 830 & 862 7

CONFIDENTIAL – DO NOT DUPLICATE

CHAPTER 1 INTRODUCTION1.1 PURPOSE This document attempts to describe the EDI solution for an inbound forecast or release on a scheduling agreement.

1.2 AUDIENCE The primary audience of this document is intended to be the configuration consultant, but the intention is that the explanations provided in this document will be explicit enough that anyone should be able to come away with an understanding of the EDI solution.

1.3 SCOPE This document covers the implementation of the EDI solution with emphasis on the following areas:

SAP Configuration

AUTHOR: KEVIN WILSON CONFIDENTIAL – DO NOT DUPLICATE

CHAPTER 2 EDI PROCESS2.1 TRADING PARTNER X

2.1.1 SD Process Assumptions2.1.1.1 Scheduling AgreementThe following information needs to be configured in order for our 830s to work.

Ship to code. See section 3.1.2.1 on page 5. Account at customer. See section 3.1.2.3 on page 5. Sold to customer. See section 3.1.2.2 on page 5.

The following information needs to be entered in the Scheduling Agreement in order for our 830s to work. The SP Partner (Forwarding agent) needs to be entered at the Scheduling Agreement Header Level in the

partner tag. The partner needs to have the SCAC code entered in the vendor master. The CO Partner (Commissionable rep) needs to be entered at the Scheduling Agreement Header Level in the

partner tag. The partner needs to have a relevant email address loaded in the relevant customer master record. This will be used for emailing of order details and scheduling agreement details.

Contract number in the PO Number field. Material determination implemented. We use the customer’s material number to determine our material

number. Ship to code must appear on the partner description of the ship to partner. It should be brought across from the

customer master Only 1 line item allowed per scheduling agreement

2.1.1.2 Scheduling Agreement Response (E-Mail)When a scheduling agreement is updated via EDI a snapshot is sent to the commissionable rep (rep-firm).

EDIUSER must have a valid mail address assigned in SAP (tx: SU01) The CO Partner (Commissionable rep) needs to be entered at the Scheduling Agreement Header Level in the


AUTHOR: CONFIDENTIAL – DO NOT DUPLICATE

CHAPTER 3 SAP DETAILThe following section details the SAP configuration that describes the EDI implementation solution.

3.1 SAP CONFIGURATION The following section describes the configuration that is required in order to enable EDI.

3.1.1 Overview3.1.1.1 Trading Partner XScenario \ Interface Configuration summary SectionInbound 830 1. Sold to Customer “ship to code”

2. Sold to Customer “account at customer”3. Sold to Customer “Lookup value”4. Scheduling agreement settings5. Partner profile – TRADING PARTNER X LS\ DELINS (FST)6. Partner profile – TRADING PARTNER X LS\ DELINS (JIT)7. ONCE OFF: Inbound SAP Job scheduling

3.1.2.13.1.2.33.1.2.23.1.2.4

3.1.2 SAP Customers (XD01)3.1.2.1 Ship to codeThe number is sent by the EDI partner in the N104 segment where the qualifier is ‘ST’ (IDoc field E1EDP10-KWERK). The Partner description values must match the entries in table T661W (transaction OVAI)3.1.2.1.1Transaction: VD02

Enter Sold to customer number. Click on [Partners] For each ship to partner on the partner view enter the ship to code as the partner description.

EG: 0000000003

3.1.2.2 Sold to3.1.2.2.1Transaction: OVAICreate entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.)Vendor Xxx (N104 segment where the qualifier is ‘SE’)Partner Description 0000000003 (N104 segment where the qualifier is ‘ST’)Unloading point <empty>Sold-to Party Yyy (SAP Sold to Customer Number)This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.

3.1.2.3 Account at customerThe number is sent by the EDI partner in the N104 segment where the qualifier is ‘SE’ (IDoc field E1EDKA1-PARTN where PARVW=LF)3.1.2.3.1Transaction: VD02

Enter Sold to customer number. Click on [Sales area data]. On the Sales view, enter the Acct. at Cust. (KNVV-EIKTO)


EG: 0000100740

3.1.2.4 Scheduling agreement configuration3.1.2.4.1 AssumptionsThe following information needs to be configured in order for our 830s and 862s to work.

Ship to code. See section 3.1.2.1 on page 5. Account at customer. See section 3.1.2.3 on page 5. Sold to customer. See section 3.1.2.4.2 on page 6.

The following information needs to be entered in the Scheduling Agreement in order for our 830s and 862s to work. The SP Partner (Forwarding agent) needs to be entered at the Scheduling Agreement Header Level in the

partner tag. The partner needs to have the SCAC code entered in the vendor master. The CO Partner (Commissionable rep) needs to be entered at the Scheduling Agreement Header Level in the


3.1.2.4.2Transaction: OVA9Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement.This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.3.1.2.4.3OPTIONAL : Transaction: OVAJThis option is currently NOT implemented at CO. Y. If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.

AUTHOR: KEVIN WILSON ERROR: REFERENCE SOURCE NOT FOUND ERROR: REFERENCE SOURCE NOT FOUND

APPENDIX A. TEST 830 & 862ISA*00* *00* *12*12341234112 *01*22123412341T *010806*1146*U*00401*000000187*0*T*|~GS*PS*12341234112*22123412341T*20010806*1146*3*X*004010~ST*830*0786~BFR*05*1072411111**DL*A*20010815*20010927*20010724***G00156~PER*BD*PAUL*TE*121-123-121212~N1*ST*BLD 2*92*S02~LIN*001*BP*Q110560***VP*HK10J~UIT*EA*0.02*PE~REF*IT*KO~FST*190000*D*D*20010815~FST*70000*D*D*20010927~SE*10*0786~GE*1*3~GS*SS*12341234112*22123412341T*20010806*1146*3*X*004010~ST*862*0618~BSS*00*10731112*20010731*DL*20010815*20010815**10731112**G00156~N1*ST* BLD 2*92*S02~LIN*001*BP*Q110560***VP*HK10J~UIT*EA*0.02*PE~REF*IT*KO~FST*190000*C*D*20010815~CTT*1~SE*9*0618~GE*1*3~IEA*2*000000187~


Documents

Scheduling Agreement Documentation