Mapping of inbound ORDERS messages

This document describes the Gentran mapping for inbound ORDERS messages from partner XXX (XXX Company). This partner uses standard
003010 transaction 850 for purchase orders.

Logical Mapping
This section describes the logical mappings from EDI 3010 transaction 850 data to SAP ORDERS01 IDocs (message type ORDERS).

Application Record: PO Header (Repetitions indicated)

Application ID: P3ORDERSI
Transaction ID: 850MTN3040
Application Application Description XFer Special
Standard Segment Field
Element
[] = Constant
E2EDK01 Document header general data (F020)
[‘000’] No action ACTION Action code for the whole EDI message
[‘USD’] CURCY Currency
[‘EDI’] BSART Document type
E2EDK14 Document header organizational data (F030)
[‘012’] Order type QUALF IDoc qualifier organization
[‘ZTSO’] ORGID IDoc organization
E2EDK14 Document header organizational data (F030)
[‘019’] PO type (SD) QUALF IDoc qualifier organization
[‘EDI’] ORGID IDoc organization
Application Record: PO Header (Repetitions indicated)
Application ID: P3ORDERSI
Transaction ID: 850MTN3040
Application Application Description XFer Special
Standard Segment Field
Element
[] = Constant
NOT USED!!! These segment values are not used any more.
Instead the inbound processing uses the
default order type “DFUE” since the IDoc does
not provide the order type. The “DFUE” order
type needs to be configured in the IMG
(OVSB).
E2EDK03 Document header date segment (F040)
[‘002’] Delivery date IDDAT Qualifier for IDoc date segment
DTM02 DATUM IDoc: Date
UZEIT IDoc: Time
E2EDKA1 Document header partner information (F070)
[‘LF’] Vendor PARVW Partner function
REF02 PARTN Partner number
E2EDK02 Document header reference data (F080)
[‘001’] Customer PO QUALF IDoc qualifier organization
BEG03 BELNR IDoc document number
BEG05 DATUM IDoc: Date
UZEIT IDoc: Time
Application Record: PO Detail (Repetitions NOT indicated)
Application ID: P3ORDERSI
Transaction ID: 850MTNC3040
Application Application Description XFer Special
Standard Segment Field
Element
[] = Constant
E2EDP01 Document item general data
PO101 POSEX Item number
PO102 MENGE Quantity
PO103 MENEE Unit of measure
E2EDP19 Document item object identification
[‘002’] Mat# at vend QUALF IDoc object identification
PO109 (PO107?) IDTNR IDoc material ID
Physical Mapping
This section describes the physical Gentran segment mapping.

Segment ID: BEG

Application ID: P3ORDERSI
Transaction ID: 850MTNC3040
Application Description Used Special
Field
Standard Element
[] = Constant
F010.TABNAM [‘EDI_DC’] Done in BEG extended mapping 100/10/0
F020.ACTION [‘000’] No action Done in BEG extended mapping 100/10/1
F020.CURCY [‘USD’] Done in BEG extended mapping 100/10/2
F020.BSART [‘EDI’] Done in BEG extended mapping 100/10/3
F080.QUALF [‘001’] Done in BEG extended mapping 100/10/4
F070.PARVW [‘LF’] Done in BEG extended mapping 100/10/5
F030.QUALF [‘012’] Order type Done in BEG extended mapping 100/10/6
F030.ORGID [‘ZTSO’] Done in BEG extended mapping 100/10/7
F080.BELNR BEG03
F080.DATUM BEG05
Segment ID: REF
Application ID: P3ORDERSI
Transaction ID: 850MTNC3040
Application Description Used Special
Field
Standard Element
[] = Constant
F070.PARTN REF02

Segment ID: DTM

Application ID: P3ORDERSI
Transaction ID: 850MTNC3040
Application Description Used Special
Field
Standard Element
[] = Constant
F040.IDDAT [‘002’] Delivery date Done in DTM extended mapping 1400/10/0
F040.DATUM DTM02
Segment ID: PO1
Application ID: P3ORDERSI
Transaction ID: 850MTNC3040
Application Description Used Special
Field
Standard Element
[] = Constant
F130.POSEX PO101
F130.MENGE PO102
F130.MENEE PO103
F200.QUALF [‘002’] Mat# at vendor Done in PO1 extended mapping 4100/10/1
F200.IDTNR PO109 (PO107?)
003010 Transaction 850 Standard
The documentation for the 003010 (ANSI X12 VERSION 3 RELEASE 1) standard transaction
850 (PURCHASE ORDER) can be found in Gentran under standards.

ORDERS01 IDoc Structure

This section of the document describes the ORDERS01 IDoc structure in SAP ver 3.1I. The
structure only includes relevant segments and fields, and does not display the complete
ORDERS01 structure. Note that the logical and physical mapping in the previous section only
contains the fields needed for the specific scenario at Thomson Industries and for EDI with the
specified partner.

 Purchasing/Sales

O
R
D
E
R
S
0
1
E1
ED
K01
 
IDo
c:
Doc
ume
nt
hea
der
gene
ral
data
  S
  e
g
m
e
n
t
fi
el
d
s
 AC 
Acti TI
on ON
cod
e
for
the
who
le
EDI
mes
sage
  KZABS    Indicator for order acknowledgment requirement
CURCY    Currency

  E1EDK14
IDo
c:
Doc
.hea
der
orga
niza
tion
al
data
 S
 e
g
m
e
n
t
fi
el
d
s

 QU 
ID AL
OC F
qua
lifer
org
aniz
atio
n
 ORGID    IDOC organization

  E1EDK03
IDo
c:
Doc
ume
nt
hea
der
date
seg
men
t
 S
 e
g
m
e
n
t
fi
el
d
s

 ID 
Qua DA
lifie T
r
for
ID
OC
date
seg
men
t
 DATUM    IDOC: Date

UZEIT    IDOC: Time

  E1EDKA1
IDo
c:
Doc
.hea
der
part
ner
info
rma
 S
 e
g
m
e
n
t
fi
el
d
s

 PA 
Par RV
tner W
fun
ctio
n
(e.g.
sold
-to
part
y,
ship
-to
part
y, ...
)
 PARTN    Partner number

LIFNR    Vendor number at customer location

  E1EDK02
IDo
c:
Doc
ume
nt
hea
der
refe
renc
e
data
 S
 e
g
m
e
n
t
fi
el
d
s
 QU 
ID AL
OC F
qua
lifie
r
refe
ren
ce
doc
ume
nt
 BELNR    IDOC document number
POSNR    Item number

DATUM    IDOC: Date

UZEIT    IDOC: Time

  E1EDP01
IDo
c:
Doc
.ite
m
gen
eral
data

 S
 e
g
m
e
n
t
fi
el
d
s
 P 
Item O
num S
ber E
X
MENGE    Quantity
MENEE    Unit of measure

  E1EDP19
IDo
c:
Doc
.ite
m
obje
ct
iden
tif
 S
 e
g
m
e
n
t
fi
el
d
s

 QU 
ID AL
OC F
obje
ct
iden
tific
atio
n
suc
h as
mat
eria
l
no.,
cust
ome
r
 IDTNR    IDOC material ID
KTEXT    IDOC short text