You are on page 1of 7

210627797.xls.

ms_office

Template

830 Forecast Schedule Release


X12 Transaction: X12 Version: IDoc: Message Type: Direction: Description: Comments: DELFOR01 DELINS Inbound IDoc mapping for transaction 830 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. 830 3020

Only segments and fields that are actually mapped will be shown EDI Seg EDI Field

IDoc Segment EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40 EDI_DC40

IDoc Field MANDT DOCREL STATUS DIRECT IDOCTYP MESTYP MESCOD STD STDVRS STDMES SNDPOR SNDPRT SNDPRN RCVPRT RCVPRN CREDAT CRETIM

Condition

IDoc Field Constant Value Comments 110 46C 2 DELFOR01 DELINS FST or JIT X 003020 830 LS From Gentran "trading partner : SAP sold-to number" cross-reference table (eg. 'Company X') LS DEV110YPCC System Date System Time DEV110 value - instance dependent DEV110 value - instance dependent SAP-assigned on creation of database IDoc

Split from one 830 by map

Trading partner and instance-specific (eg. A000000025)

BFR 01 02 04 05 06 07 08 10 11

00 = Original E1EDK09 LABNK DL = Delivery-based A = Actual Discrete Qtys E1EDP10 E1EDP10 E1EDP10 E1EDK09 E1EDK09 E1EDK09 ABRAB ABRBI ABHOR BSTDK VTRNR USR01 Page 1 of 7 yymmdd (only if FST02=C) yymmdd (only if FST02=C) yymmdd (only if FST02=D) ccyymmdd ccyymmdd ccyymmdd FST ONLY - Begin forecast horizon - Map must add century - Release valid from FST ONLY - End forecast horizon - Map must add century - Release valid to JIT ONLY - End forecast horizon - Map must add century - JIT Horizon Release date 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) Company X AG PO number - needs to flow through to 810 & 856 Release no.

210627797.xls.ms_office EDI Seg EDI Field IDoc Segment IDoc Field Condition IDoc Field Constant Value Comments

Template

N1

01 02 03 04

E1EDKA1 E1EDKA1 E1EDKA1 E1EDK11 E1EDK11 E1EDK11 E1EDK11 E1EDKA1 E1EDKA1

PARVW NAME1 LIFNR TDNAME SPRAS TXT01 TXT02 PARVW NAME1

BY = Buying party 92 = Assigned by Buyer

AG = Buying party

PER 01 02 03 04 N1 01 02 03 04 N1 01 02 03 04 01 02 03 04

BD = Buyer name or dept

Zxxx = EDI Contact EN = English

TE = Telephone no.

BT = Bill-to party 92 = Assigned by Buyer

RE = Bill-to party

Not sent for BT (Bill-to) - Without a code, the bill-to will default to the customer master bill-to in SAP. E1EDKA1 E1EDKA1 E1EDKA1 E1EDKA1 E1EDKA1 E1EDKA1 PARVW NAME1 PARTN PARVW NAME1 LIFNR 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. BP = Buyer's part no. E1EDP10 IDNKD EC = Eng. Change level VP = Vendor's part no. VP = Vendor's part no. Optional - If EC is sent here, VP is sent (if available) in LIN06/07 not processed Optional - only if available and not sent in LIN04/05 not processed ST = Ship-to party 92 = Assigned by Buyer WE = Ship-to party SE = Selling party 92 = Assigned by Buyer LF = Selling party

N1

04

E1EDP10

KWERK

LIN

01 02 03 04 05 06 07

E1EDK09

USR04

UIT

01 02 03

EA = Each Unit price - not processed CT = Contract PE = Price per each CO = Customer Order no. E1EDK09 USR02 Page 2 of 7 Segment sent only on firm releases Receiving Company X site PO no. - Line item no. (needs to print on packslip, but NOT on 810 or 856)

REF 01 02

210627797.xls.ms_office EDI Seg EDI Field IDoc Segment IDoc Field Condition IDoc Field Constant Value Comments

Template

FST 01

E1EDP16 E1EDP10

WMENG LABKY SCREL C = Firm D = Planning D = Discrete M = Monthly bucket W = Weekly bucket yymmdd yymmdd yymmdd 1 = Append, if FST02 = C 2 = Replace, if FST02 = D 02 = JIT schedule 03 = Forecast schedule

Quantity Needs confirmation that Company X does not resend undelivered schedule lines

02

E1EDP10

03 04 04 04 CTT 01

E1EDP16 E1EDP16 E1EDP16 E1EDP10

PRGRS EDATUV EDATUB ABRAB

ccyymmdd ccyymmdd ccyymmdd

Same codes used by SAP 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 Total number of line items (LIN) in 830 - not evaluated by SAP

Page 3 of 7

Inbound EDI Schedule Release Set-up


Step Trans Code
1 VD02

Action
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) Create schedule agreements.

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

VA31

OVAI

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. Buyers 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 This transaction updates table T661W. SAP uses this table to determine the sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) 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. Create a partner profile for the sold-to partner logical system: Partner type: LS Make 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 ->) Optional: Enter delivery intervals This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.

OVA9

WE20

OVAJ

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

210627797.xls.ms_office - Config Notes

Sample Data
Trading Partner Scheduling Agreement IDoc Number Logical Message Type Release Number Notes

DEV

Date

Name

Version Revision

Nature of Change