my client customer already using SAP system, (client customer) they will make scheduling agreement which should update in my client system also through EDI.
Give your exact requirment as to what would be your sales flow. You have to speak to your EDI team for the configuration. From your end i think you have maintain the partner profiles and partner description.
For example: my client is MMM, supplying tires to the client customer FFF, both are using SAP system. currently we are doing scheduling agreement manually. and from the reference to scheduling agreement we create order.
now my client (MMM) wants make scheduling agreement with customer (FFF) though already using SAP system both ends. if customer (FFF) creating scheduling agreement it should get update automatically in my client system (MMM) through EDI.
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:
u2022 SAP Configuration
CHAPTER 2 EDI PROCESS
2.1 TRADING PARTNER X
2.1.1 SD Process Assumptions
2.1.1.1 Scheduling Agreement
The following information needs to be configured in order for our 830s to work.
u2022 Ship to code. See section 3.1.2.1 on page 5.
u2022 Account at customer. See section 3.1.2.3 on page 5.
u2022 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.
u2022 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.
u2022 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.
u2022 Contract number in the PO Number field.
u2022 Material determination implemented. We use the customeru2019s material number to determine our material number.
u2022 Ship to code must appear on the partner description of the ship to partner. It should be brought across from the customer master
u2022 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).
u2022 EDIUSER must have a valid mail address assigned in SAP (tx: SU01)
u2022 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.
CHAPTER 3 SAP DETAIL
The 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.
Inbound 830 1. Sold to Customer u201Cship to codeu201D
2. Sold to Customer u201Caccount at customeru201D
3. Sold to Customer u201CLookup valueu201D
4. Scheduling agreement settings
5. Partner profile u2013 TRADING PARTNER X LS\ DELINS (FST)
6. Partner profile u2013 TRADING PARTNER X LS\ DELINS (JIT)
7. ONCE OFF: Inbound SAP Job scheduling 3.1.2.1
3.1.2.3
3.1.2.2
3.1.2.4
3.1.2 SAP Customers (XD01)
3.1.2.1 Ship to code
The number is sent by the EDI partner in the N104 segment where the qualifier is u2018STu2019 (IDoc field E1EDP10-KWERK). The Partner description values must match the entries in table T661W (transaction OVAI)
3.1.2.1.1 Transaction: VD02
u2022 Enter Sold to customer number.
u2022 Click on [Partners]
u2022 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 to
3.1.2.2.1 Transaction: OVAI
Create 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 u2018SEu2019)
Partner Description 0000000003 (N104 segment where the qualifier is u2018STu2019)
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 customer
The number is sent by the EDI partner in the N104 segment where the qualifier is u2018SEu2019 (IDoc field E1EDKA1-PARTN where PARVW=LF)
3.1.2.3.1 Transaction: VD02
u2022 Enter Sold to customer number.
u2022 Click on [Sales area data].
u2022 On the Sales view, enter the Acct. at Cust. (KNVV-EIKTO)
EG: 0000100740
3.1.2.4 Scheduling agreement configuration
3.1.2.4.1 Assumptions
The following information needs to be configured in order for our 830s and 862s to work.
u2022 Ship to code. See section 3.1.2.1 on page 5.
u2022 Account at customer. See section 3.1.2.3 on page 5.
u2022 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.
u2022 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.
u2022 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.
3.1.2.4.2 Transaction: OVA9
Create 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.3 OPTIONAL : Transaction: OVAJ
This 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.