document.xls Template

Page 1 of 7

830 Forecast Schedule ReleaseX12 Transaction: 830X12 Version: 3020

IDoc: DELFOR01Message Type: DELINSDirection: Inbound

Description: IDoc mapping for transaction 830Comments: Please log all changes to this document in the Change Log worksheet, explaining reason for changes.

This document assumes receipt of forecast with embedded release.Note that the map must store the header data from each 830 and create a separate DELFOR01/DELINS IDoc for each LIN loop.

Only segments and fields that are actually mapped will be shown

EDI Field IDoc Segment IDoc Field Condition IDoc Field Constant Value Comments

EDI_DC40 MANDT 110 DEV110 value - instance dependent EDI_DC40 DOCREL 46CEDI_DC40 STATUS SAP-assigned on creation of database IDocEDI_DC40 DIRECT 2EDI_DC40 IDOCTYP DELFOR01EDI_DC40 MESTYP DELINSEDI_DC40 MESCOD FST or JIT Split from one 830 by mapEDI_DC40 STD XEDI_DC40 STDVRS 003020EDI_DC40 STDMES 830EDI_DC40 SNDPOR Trading partner and instance-specific (eg. A000000025)EDI_DC40 SNDPRT LS

EDI_DC40 SNDPRN EDI_DC40 RCVPRT LSEDI_DC40 RCVPRN DEV110YPCC DEV110 value - instance dependent EDI_DC40 CREDAT System DateEDI_DC40 CRETIM System Time

BFR 01 00 = Original02 E1EDK09 LABNK Release no.04 DL = Delivery-based05 A = Actual Discrete Qtys

06 E1EDP10 ABRAB yymmdd (only if FST02=C) ccyymmdd

07 E1EDP10 ABRBI yymmdd (only if FST02=C) ccyymmddE1EDP10 ABHOR yymmdd (only if FST02=D) ccyymmdd

08 E1EDK09 BSTDK Release date

10 E1EDK09 VTRNR11 E1EDK09 USR01 Company X AG PO number - needs to flow through to 810 & 856

EDI Seg

From Gentran "trading partner : SAP sold-to number" cross-reference table (eg. 'Company X')

FST ONLY - Begin forecast horizon - Map must add century - Release valid from

FST ONLY - End forecast horizon - Map must add century - Release valid toJIT ONLY - End forecast horizon - Map must add century - JIT Horizon

Contract (PO) no. (If 'check PO' flag is set in transaction OVA9, SAP will make sure that PO no. on SA matches PO no. sent)

document.xls Template

Page 2 of 7

EDI Field IDoc Segment IDoc Field Condition IDoc Field Constant Value CommentsEDI Seg

N1 01 E1EDKA1 PARVW BY = Buying party AG = Buying party 02 E1EDKA1 NAME103 92 = Assigned by Buyer04 E1EDKA1 LIFNR

PER 01 E1EDK11 TDNAME BD = Buyer name or dept Zxxx = EDI Contact

E1EDK11 SPRAS EN = English02 E1EDK11 TXT0103 TE = Telephone no.04 E1EDK11 TXT02

N1 01 E1EDKA1 PARVW BT = Bill-to party RE = Bill-to party 02 E1EDKA1 NAME103 92 = Assigned by Buyer

04

N1 01 E1EDKA1 PARVW SE = Selling party LF = Selling party 02 E1EDKA1 NAME103 92 = Assigned by Buyer04 E1EDKA1 PARTN

N1 01 E1EDKA1 PARVW ST = Ship-to party WE = Ship-to party02 E1EDKA1 NAME103 92 = Assigned by Buyer04 E1EDKA1 LIFNR

04 E1EDP10 KWERK

LIN 01 E1EDK09 USR0402 BP = Buyer's part no.03 E1EDP10 IDNKD

04 Optional - If EC is sent here, VP is sent (if available) in LIN06/0705 not processed06 VP = Vendor's part no. Optional - only if available and not sent in LIN04/0507 not processed

UIT 01 EA = Each02 Unit price - not processed

03

REF 01 CO = Customer Order no. Segment sent only on firm releases

02 E1EDK09 USR02

Not sent for BT (Bill-to) - Without a code, the bill-to will default to the customer master bill-to in SAP.

SAP ignores the ship-to (WE) partner sent in, so if we want to keep separate S.A.'s per ship-to, we'll need to call the ship-to code the "plant" code for a unique match on the S.A.

Line item is data not posted - the customer line item no. on the S.A. is the contract item no. - there is no field for the release item no.

EC = Eng. Change levelVP = Vendor's part no.

CT = ContractPE = Price per each

Receiving Company X site PO no. - Line item no. (needs to print on packslip, but NOT on 810 or 856)

document.xls Template

Page 3 of 7

EDI Field IDoc Segment IDoc Field Condition IDoc Field Constant Value CommentsEDI Seg

FST 01 E1EDP16 WMENG Quantity

E1EDP10 LABKY

02 E1EDP10 SCREL

03 E1EDP16 PRGRS Same codes used by SAP

04 E1EDP16 EDATUV yymmdd ccyymmdd04 E1EDP16 EDATUB yymmdd ccyymmdd

04 E1EDP10 ABRAB yymmdd ccyymmdd

CTT 01 Total number of line items (LIN) in 830 - not evaluated by SAP

1 = Append, if FST02 = C2 = Replace, if FST02 = D

Needs confirmation that Company X does not resend undelivered schedule lines

C = FirmD = Planning

02 = JIT schedule03 = Forecast schedule

D = DiscreteM = Monthly bucketW = Weekly bucket

Delivery date - If FST03 = M or W (first Monday of bucket). Map must add century.Delivery date - If FST03 = D (discrete date). Map must add century.

JIT ONLY - Valid from date. Map must add century. Map first occurrence of firm FST ONLY - required for append processing

Inbound EDI Schedule Release Set-up

document.xls - Config Notes 4

Step Action Considerations

1 VD02

2 VA31 Create schedule agreements.

3 OVAI

4 OVA9

5 WE20

6 OVAJ

TransCode

Maintain the customer master data for the sold-to:Enter sold-to customer number.Click on [Sales area data].On the Sales view, enter the Acct. at Cust. (KNVV-EIKTO) - This value must match what the customer sends in the N104 field where N101=SE. (IDoc field E1EDKA1-PARTN where PARVW=LF)On the Partner functions view, enter the ship-to code that the customer sends in the N104 field where N101=ST into the Partner description field for each Ship-to partner. (IDoc field E1EDP10-KWERK)

The Partner description values must match the entries in table T661W (transaction OVAI).

Note that the Partner description values must be entered into the master data before the schedule agreements are created for this sold-to to be copied into the partners on the schedule agreement. (SAP uses the partner descriptions to match the incoming schedule releases to the correct schedule agreement.)

Schedule releases for which SAP cannot determine a unique schedule agreement will go to workflow. Line number on 856 and 810 come from PO line item number on scheduling agreement. Buyer’s part number goes on PO Data at line item level in the Customer material field.

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

This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.

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.

Create a partner profile for the sold-to partner logical system:Partner type: LSMake 2 Inbound parmtrs. for Partn.funct. 'SP' and Message type 'DELINS' -1. Message Variant: FST Process code: DELI Syntax check: x Trigger Immediately: x 2. Message Variant: JIT Process code: DELI Syntax check: x Trigger by background program: x (see Considerations ->)

There may be a timing issue posting the schedule releases. Issue one is that SAP requires a forecast schedule before it will accept a delivery schedule. Issue two is that a delivery schedule release trying to update a schedule agreement immediately following a forecast schedule IDoc may find the schedule agreement still locked.Possible solution:Create delivery schedules with EDIDC-MESFCT = 'JIT' and forecast schedules with EDIDC-MESFCT = 'FST'. Check "trigger immediately" on the inbound parameters record for DELINS/FST, but check "trigger by background program" for DELINS/JIT. (The JIT IDocs would be processed into the schedule agreements in batch at predetermined times.) This should ensure correct sequence and spacing of the releases.

Optional:Enter delivery intervals

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.

Sample Data DEV

5

Trading Partner Release Number NotesScheduling Agreement

IDoc Number

Logical Message Type

Date Name Version Revision

Nature of Change