Safs 6 Fueframeset

SAP Apparel and Footwear (SAP AFS)
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_afs60/helpdata/en/b2/53ae56cda511d2aca20000e829fbfe/frameset.htm
Created on October 14, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.
© 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
PUBLIC Page 1 of 77
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table
Table of content
cont ent
1 SAP Apparel
Appare l and
and Footwear (SAP AFS)
1.1
1.1 Cross-Application
Cross-Applic ation AFS Informatio
Informationn
1.1.1 Season
1.1.2 AFS-Interfaces
1.1.2.1
1.1.2.1 AFS Basic
Bas ic Data
1.1.2.1.
1.1.2.1.1
1 Grid Master Data
1.1.2.1.
1.1.2.1.1.1
1.1 Technical
Technic al Information:
Informat ion: Grid Master
Maste r Data
1.1.2.1.
1.1.2.1.1.2
1.2 Grid Master
Mas ter Data:
Data : Dialog
Dialo g Functions and their Support
Suppo rt in ALE
1.1.2.1.
1.1.2.1.2
2 Material
Mate rial Master
Mas ter
1.1.2.1.
1.1.2.1.2.1
2.1 Technical
Informat ion: Materia
Mate riall Master
Mas ter
1.1.
1.1.2.
2.1.
1.2.
2.2
2 Material
Materia l Master:
Master : Dialog Functions
Functions and their Support in ALE
1.1.
1.1.2.
2.2
2 Sales and Distribution (SD)
1.1.
1.1.2.
2.2.
2.1
1 Shipping/Transport: Transporta
Transportation
tion Interface
Interface
1.1.2.2.
1.1.2.2.1.1
1.1 Shipping/Transp
Shipp ing/Transport:
ort: Delivery
Deliv ery Interface
Interfac e
1.1.2.2.
1.1.2.2.1.1.
1.1.1
1 Customizing:
Custom izing: Delivery
Deliv ery Interfa
Interface
ce
1.1.2.2.
1.1.2.2.1.1.
1.1.2
2 Technical
Informat ion: Delivery
Deliv ery Interfa
Interface
ce
1.1.2.2.2 Sales
1.1.2.2.
1.1.2.2.2.1
2.1 Sales
Sale s Order
Orde r
1.1.2.2.
1.1.2.2.2.1.
2.1.1
1 Customizing:
Custom izing: Sales
Sale s Order
Orde r
1.1.2.2.
1.1.2.2.2.1.
2.1.2
2 Technical
Informat ion: Sales
Sale s Order
Orde r
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1
2.1 Document
Doc ument Header:
Heade r: General
Gener al Data (Segment E1EDK01)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.1
1 Document
Doc ument Header:
Header : Organizatio
Organiz ational
nal Data (Segment
(Segme nt E1EDK14)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.2
2 Document
Doc ument Header:
Heade r: Date Segment (Segment
(Segme nt E1J3K03)
E1J3K03 )
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.3
3 Document
Docum ent Header:
Header : Taxes
Taxe s (Segment E1EDK04)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.4
4 Document
Docum ent Header:
Header : Conditions
Condit ions (Segment E1EDK05)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.5
5 Document
Docum ent Header:
Heade r: Partner
Partne r Info
Info (Segment E1EDKA1)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.6
6 Document
Docum ent Header:
Heade r: Partner
Partne r Info
Info Additional
Additio nal Data (Segment E1EDKA3)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.7
7 Document
Docum ent Header:
Header : Reference
Refe rence Data (Segment
(Segme nt E1EDK02)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.8
8 Document
Docum ent Header:
Header : Terms of Delivery
Delive ry (Segment E1EDK17)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.9
9 Document
Docum ent Header:
Heade r: Terms of Payment
Paym ent (Segment E1EDK18)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.10
10 Document
Docume nt Header:
Head er: Additio
Add itional
nal Data (Segment
(Segme nt E1EDK35)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.11
11 Document
Docum ent Header:
Header : Payment
Paym ent Cards (Segment E1EDK36)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.12
12 Document
Docum ent Header:
Heade r: Text Identificatio
Identific ation
n (Segment
(Segme nt E1EDKT1)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.13
13 Document
Docume nt Header:
Header : Texts
Text s (Segment E1EDKT2)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.1.
2.1.14
14 Document
Docume nt Header:
Head er: MSO Header
Head er (Segment
(Segme nt E1J3AHO)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2
2.2 Document
Doc ument Item:
Item: General
Genera l Data (Segment E1J3P01)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.1
1 Document
Doc ument Item: Date Segme nt (Segment E1J3P03)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.2
2 Document
Doc ument Item: Schedule
Sched ule Lines (Segment
(Segme nt E1EDP20)
E1EDP20)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.3
3 Document
Docum ent Item:
Item: Schedule Lines Additional
Additi onal Data (Segment
(Segme nt E1J3P20)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.4
4 Document
Docum ent Item:
Item: Conditions
Conditio ns (Segment E1J3P05
E1J3P05))
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.5
5 Document
Docum ent Item: Configuration
Configurat ion Data (Segme nt E1CUCFG)
E1CUCFG)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.6
6 Document
Docum ent Item: Service
Serv ice Specific
Spec ificatio
ations
ns Data (Segment
(Segme nt E1EDC01)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.7
7 Document
Docum ent Item:
Item: Terms of Delivery
Deliv ery (Segment
(Se gment E1EDP17)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.8
8 Document
Docum ent Item:
Item: Multi-Store Ord
Order
er (Segment
(Segme nt E1J3AIO)
E1J3AIO)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.9
9 Document
Docum ent Item:
Item: Object
Objec t Identificat
Identifi cation
ion (Segment E1EDP19)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.10
10 Document
Docume nt Item: Object
Obje ct Ide
Identifica
ntification
tion (Segment E1J3AIM)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.11
11 Document
Docum ent Item: Partner
Partne r Info
Info Additional
Addit ional Data
Dat a (Segment E1EDPA3)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.12
12 Document
Docum ent Item: Partner
Partne r Inform
Informatio
ation
n (Segment E1EDPA1)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.13
13 Document
Docume nt Item:
Item: Reference
Refere nce Order
Orde r Item
Item (Segment
(Segme nt E1CUREF)
E1CUREF)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.14
14 Document
Docume nt Item:
Item: Reference
Refere nce Data (Segment
(Segme nt E1EDP02)
E1EDP02)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.15
15 Document
Docume nt Item:
Item: Taxes (Segment
(Se gment E1J3P04)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.16
16 Document
Docume nt Item:
Item: Totals Segment
Se gment (Segment
(Segme nt E1EDS01)
E1EDS01)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.17
17 Document
Docume nt Item:
Item: Texts (Segment
( Segment E1EDPT2)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.18
18 Document
Docume nt Item:
Item: Text Identifica tion (Segment
(Segme nt E1EDPT1)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.19
19 Document
Docume nt Item:
Item: Additionals
Additi onals (Segment
( Segment E1ADDI1)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.20
20 Document
Docume nt Item:
Item: Shipping Unit Header (Segment
(Se gment E1EDL37)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.21
21 Document
Docum ent Item: VAS Ticketing/Labe
Ticket ing/Labeling
ling (Segment E1J3AIT)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.22
22 Document
Docum ent Item: VAS Ticketing/Labe
Ticket ing/Labeling
ling Text (Segment
(Segme nt E1J3AIX)
E1J3AIX)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.23
23 Document
Docume nt Item:
Item: VAS Specia
Spe ciall Services
Servic es (Segment
(Segme nt E1J3AIS)
E1J3AIS)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.24
24 Document
Docume nt Item: VAS Packing
Pac king (Segment E1J3AIP)
PUBLIC Page 2 of 77
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.25
25 Document
Docume nt Item:
Item: Terms of Payment
Pay ment (Segment
(Segme nt E1EDP18)
E1EDP18)
1.1.2.2.
1.1.2.2.2.1.
2.1.2.2.
2.2.26
26 Document
Docume nt Item: Additiona
Addi tionall Data (Segment E1EDP35)
1.1.2.2.
1.1.2.2.2.1.
2.1.3
3 User Exits
Exi ts in the Incom
Incoming
ing Order
Orde r
1.1.2.2.2.2 Contract
1.1.2.2.
1.1.2.2.2.2.
2.2.1
1 Customizing:
Custom izing: Contract
Contra ct
1.1.2.2.
1.1.2.2.2.2.
2.2.2
2 Technical
Informat ion: Contract
Contra ct
1.1.2.2.
1.1.2.2.2.2.
2.2.2.1
2.1 Document
Doc ument Header:
Header : Organizatio
Organiz ational
nal Data (Segment
(Segme nt E1EDK14)
1.1.2.2.
1.1.2.2.2.2.
2.2.2.2
2.2 Document
Doc ument Header:
Heade r: Date Segment (Segment
(Segme nt E1J3K03)
E1J3K03 )
1.1.2.2.2.3 Quotation
1.1.2.2.
1.1.2.2.2.3.1
2.3.1 Technical
Informat ion: Quotation
Quotat ion
1.1.2.2.
1.1.2.2.2.4
2.4 Order
Orde r Change
1.1.2.2.
1.1.2.2.2.4.1
2.4.1 Customizi
Custom izing:
ng: Order
Orde r Change
1.1.2.2.
1.1.2.2.2.4.2
2.4.2 Technical
Technic al Inform
Informatio
ation:
n: Order
Orde r Change
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.1
.1 Document
Docum ent Item:
Item: General Data (Segment
(Segme nt E1J3P01)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.2
.2 Document
Docum ent Item:
Item: Multi-Store Ord
Order
er (Segment
(Segme nt E1J3AIO)
E1J3AIO)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.3
.3 Document
Docume nt Item: VAS Ticketing/Labe
Ticket ing/Labeling
ling (Segment
(Segme nt E1J3AIT)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.4
.4 Document
Docume nt Item: VAS Ticketing/Labe
Ticket ing/Labeling
ling Text (Segment
(Se gment E1J3AIX)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.5
.5 Document
Docume nt Item:
Item: VAS Packing
Pac king (Segment
(Segme nt E1J3AIP)
E1J3AIP)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.6
.6 Document
Docume nt Item: VAS Specia
Spe ciall Service
Serv ices
s (Segment E1J3AIS)
E1J3AIS)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.7
.7 Document
Docume nt Item: Partner
Partne r Informa
Information
tion (Segment E1EDPA1)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.8
.8 Document
Docume nt Item: Tex
Texts
ts (Segment E1EDPT2)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.9
.9 Document
Docume nt Header
Hea der:: Organizatio
Organiz ational
nal Data (Segment E1EDK14)
E1EDK14)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.10
.10 Document
Docume nt Header:
Head er: Partner
Partne r Information
Informat ion (Segment E1EDKA1)
E1EDKA1)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.11
.11 Document
Docume nt Header:
Head er: Referenc
Refe rence
e Data (Segment E1EDK02)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.12
.12 Document
Docume nt Header:
Head er: Payment
Pay ment Cards (Segment E1EDK36)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.13
.13 Document
Docume nt Header:
Head er: Texts
Text s (Segments E1EDKT2)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.14
.14 Document
Docume nt Header:
Head er: MSO Header
Heade r (Segment
(Segme nt E1J3AHO)
1.1.2.2.
1.1.2.2.2.4.2
2.4.2.15
.15 User Exits
Exi ts in the Incoming Order Change
1.1.2.2.
1.1.2.2.2.5
2.5 Order
Orde r Confirmatio
Confirm ation
n
1.1.
1.1.2.
2.2.
2.2.
2.5.1
5.1 General Data for the Order
Orde r Confirmation (Segment E1J3P01)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.1
.1 Multi-Store
Multi-Stor e Order (Segment E1J3AIO)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.2
.2 VAS Ticketing/Labeling
Ticketing/Labe ling (Segment E1J3AIT)
E1J3AIT)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.3
.3 VAS Ticketing/Labe
Ticke ting/Labeling
ling Text (Segment
(Segme nt E1J3AIX)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.4
.4 VAS Packing (Segment E1J3AIP)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.5
.5 VAS Specia
Spe ciall Service
Serv ices
s (Segment E1J3AIS)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.6
.6 Object
Obje ct Identificat
Identifi cation
ion (Segment
(Segme nt E1J3AIM)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.7
.7 Reference
Refe rence Data (Segment E1EDP02)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.8
.8 Date Segment (Segment E1J3P03)
E1J3P03 )
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.9
.9 Taxes
Taxe s (Segment
(Segme nt E1J3P04)
E1J3P04 )
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.10
.10 Conditions
Conditi ons (Segment
(Segme nt E1J3P05)
E1J3P05 )
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.11
.11 Schedule
Sched ule Lines (Segment
(Segme nt E1EDP20)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.12
.12 Schedule
Sched ule Lines
Lines Additional
Addit ional Data (Segment E1J3P20)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.13
.13 Partner
Partne r Informa
Information
tion (Segment E1EDPA1)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.14
.14 Partner
Partne r Info
Info Additional
Additio nal Data (Segment E1EDPA3)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.15
.15 Object
Obje ct Identi
Identifica
fication
tion (Segment
(Segme nt E1EDP19)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.16
.16 Terms of Delivery
Deliver y (Segment
(Segme nt E1EDP17)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.17
.17 Terms of Payment
Payme nt (Segment
(Segme nt E1EDP18)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.18
.18 Additiona
Addi tionall Data (Segment E1EDP35
E1EDP35))
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.19
.19 Text Identificatio
Identific ation
n (Segment
(Segme nt E1EDPT1)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.20
.20 Texts (Segment
(Se gment E1EDPT2)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.21
.21 Totals
Total s Segment (Segment E1EDS01)
1.1.2.2.
1.1.2.2.2.5.1
2.5.1.22
.22 User Exits
Exit s in the Outgoing Order
Orde r Confirmation
Confirmati on
1.1.2.2.
1.1.2.2.2.5.2
2.5.2 Document
Docum ent Header:
Head er: General
Gener al Data (Segment
(Segme nt E1EDK01)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.1
.1 Document
Docum ent Header:
Head er: Organizatio
Organiz ational
nal Data (Segment
(Segme nt E1EDK14)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.2
.2 Document
Docum ent Header:
Header : Date Segment (Segment E1J3K03)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.3
.3 Document
Docume nt Header
Hea der:: Taxes
Taxe s (Segment
(Segme nt E1EDK04)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.4
.4 Document
Docume nt Header
Hea der:: Conditions
Condit ions (Segment E1EDK05)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.5
.5 Document
Docume nt Header
Hea der:: Partner
Part ner Info
Info (Segment E1EDKA1)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.6
.6 Document
Docume nt Header
Hea der:: Partner
Part ner Info
Info Additional
Additio nal Data (Segment
(Segme nt E1EDK02)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.7
.7 Document
Docume nt Header
Hea der:: Referenc
Refe rence
e Data (Segment
(Segme nt E1EDK02)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.8
.8 Document
Docume nt Header
Hea der:: Terms of Delivery
Delive ry (Segment E1EDK17)
E1EDK17)
1.1.2.2.
1.1.2.2.2.5.2
2.5.2.9
.9 Document
Docume nt Header
Hea der:: Terms of Payment
Payme nt (Segment
(Segme nt E1EDK18)
PUBLIC Page 3 of 77
1.1.2.2.2.5.2.10 Document Header: Additional Data (Segment E1EDK35)
1.1.2.2.2.5.2.11 Document Header: Text Identification (Segment E1EDKT1)
1.1.2.2.2.5.2.12 Document Header: Texts (Segment E1EDKT2)
1.1.2.2.2.6 IDoc Error Handling for Inbound IDocs
1.1.2.2.3 Invoice
1.1.2.2.3.1 Customizing: Invoice
1.1.2.2.3.2 Technical Information: Invoices
1.1.2.2.3.3 User Exit in the Invoice
1.1.2.3 Materials Management (MM)
1.1.2.3.1 Purchasing
1.1.2.3.1.1 Request for Quotation
1.1.2.3.1.1.1 Technical Information: Request for Quotation (Purchasing)
1.1.2.3.1.2 Purchase Order
1.1.2.3.1.2.1 Technical Information: Purchase Order (Purchasing)
1.1.2.3.1.3 Purchase Order Change
1.1.2.3.1.3.1 Customizing: Purchase Order Change (Purchasing)
1.1.2.3.1.3.2 Technical Information: Purchase Order Change (Purchasing)
1.1.2.3.1.4 Order Confirmation
1.1.2.3.1.4.1 Technical Information: Order Confirmation (Purchasing)
1.1.2.3.1.5 Contracts
1.1.2.3.1.5.1 Technical Information: Contracts (Purchasing)
1.1.2.3.1.6 Contract Change
1.1.2.3.1.6.1 Technical Information: Contract Change (Purchasing)
1.1.2.3.1.7 Delivery Notification
1.1.2.3.1.7.1 Technical Information: Delivery Notification (Purchasing)
1.1.2.3.1.8 Invoice Receipt and Verification
1.1.2.3.1.8.1 Technical Information: Invoice Receipt and Verification (Purchas
1.1.2.3.2 Inventory Management
PUBLIC Page 4 of 77
!--a11y-->
SAP Apparel and Footwear (SAP AFS)
!--a11y-->
1.1 Cross-Application AFS Information

The following sections contain cross-application information for AFS.
!--a11y-->
1.1.1 Season
Use
In the fashion industry, seasons are an integral part of the business processes. O riginally, seasons were only available in Sales and Distribution (SD). It has now
been enhanced so that it can also be used for Materials Management (MM), Production Planning (PP), and Inventory Management (IM).
Now the process has even been extended for the Allocation Run (ARun), to ensure that the season-related information is considered while creating assignments.
Features
This func tion offers the following options:
Seasonality in ARun
This includes the following functions:

● If you have activated the Season field check in the allocation rule attached to the allocation type, ARun will c onsider the requirement and stock seas on before
assigning stock to requirements.
● A vali dation check is performed to chec k whether or not deallocation has to be triggered, if the seas onal information is changed in an allocated purc hase order
or production order on the basis of deallocation rule settings for purchase orders or production orders.
● A val idation is performed during goods rec eipt (G R) for an allocated purc hase order or production order when the seas on information is changed. The
deallocation rule settings for goods receipt handling will check whether the season information is appropriate, and then trigger deallocation if customized.
● A val idation is performed to check whether or not deallocation has to be triggered on the bas is of the deallocation rule settings for sales orders, when seas on
information in these allocated sales order is changed.
Seasonality in MM and PP
A season is determined when a purchase requisition or purchase order is created, either manually or by material requirements p lanning (MRP). In a purchase
requisition, the season is determined based on the delivery date of the purchase requisition. However, in a purchase order, a season is determined based on the
Creation Date and Delivery Date .
For multiple v alid seasons, MRP selects the first valid s eason.
Material enabled for a season must find a valid season as the purchase requisition or purchase order is created, otherwise the document cannot be saved.
After initially determining a season, manual changes made to the season data invokes a season check. If a season is not valid, a message (based on the
message type maintained in the condition records) is displayed. For a planned or production order, the behavior corresponds to a purchase requisition and
purchase order, respectively.
Seasonality in IM
This option is enabled only if the Season Active in IM indicator is set in the material master. The Season Fixed indicator is a disp lay only field and cannot be
set for the new materials.
PUBLIC Page 5 of 77
The information regarding season, collection, and theme is stored in the stock tables, in the batch tables, and in the material movement documents. In addition, the
season, collection, and theme fields are validated during goods movement.
Stock determination and batch determination are based on grid value, stock category, season, collection, and theme.
Limitation
Materials with Season Active in IM indicator cannot be processed using MBXX transaction.
Activities
Seasonality in ARun
To activate seasonality for ARun during allocation:

● Activate the Season field check during allocation for a particular allocation rule in Customizing by choosing AFS Allocation Run ® ARun Detail ®
Define Allocation Logic ® Allocation Rule .
To activate seasonality for ARun during deallocation:

1. Maintain the deallocation rule for a season change in allocated purchase orders (POs) in Customizing by choosing AFS Allocation Run ® Cross
App lications ® PO Handling ® Deallocation Rule . Here you define what action you want the system to take when the season in an allocated
purc hase order is changed. To attach this deallocation rule to the plant, in Customizing choose AFS Allocation Run ® Cross App lications ® PO
Handling ® Assign PO Rules to Plant .
2. Maintain the deallocation rule for a season change in allocated production/purc hase orders during goods receipt (GR) in Customizing by choosing AFS
Allocation Run ® Cross A ppli cations ® GR Handling ® Deallocation Rule . Here you define what action you want the system to take when the
season during goods receipt (GR) for an allocated production/purchase order is changed. To attach this deallocation rule to the plant, in Customizing choose
AFS Allocation Run ® Cross Ap plications ® GR Handling ® Assign G R Rules to Plant.
3. Maintain the deallocation rule for a seas on change in allocated production orders in Customizing by choosing AFS Allocation Run ® Cross
App lications ® PP Handling ® Deallocation Rule . Here you define what action you want the sys tem to take when the season in an allocated
production order is changed. To attach this deallocation rule to the plant, in Customizing choose AFS Allocation Run ® Cross Appli cations ® PP
Handling ® Assign PP Rules to Plant .
4. Maintain the deallocation rule for a season change in allocated sales orders in Customizing by choosing AFS Allocation Run ® Cross Ap plications
® SD Handling ® Deallocation Rule . Here you define what action you want the system to take when the season in an allocated sales order is
changed. To attach this deallocation rule to the order type, in Customizing choose AFS Allocation Run ® Cross Applic ations ® SD Handling ®
Assign Rule to Order Type .
Seasonality in MM/PP/IM
To activate seasonality for MM/PP/IM:

1. Create a season in Customizing by choosing Logistics - General ® Define AFS Seasons . Here you create a season, a collection, and a theme.
2. Maintain the seas on on the Season tab page of AFS Bas ic Data, to link a seas on to a material. This is also possib le at stock keep ing unit (SKU) level
depending on the relevancy for season in the characteristic. All linked seasons for the material are valid for SD and MM/PP/IM. For MM/PP/IM, the available
season depends on the season level and the validity or period for that particular season level.
3. Activ ate the seas on in the material master for MM/P P/IM by us ing the following indicators in the material master:
● Season Level
This indicator determines at which level the season is being used in MM. A season can be used only as season, season/collection, or
season/collection/theme.
● Season Active in IM
When you set the indicator, the season is used in IM by copying it into the batches and stock tables.
A season in SD can b e different from a season in MM/PP/IM. For example, a material has a season level maintained only in Season . Sales orders are created
with a season/collection/theme combination, but the purchase requisition or order can be created based only on a season.
4. Maintain the condition records related to the stock season on the SAP Easy Access screen, by choosing Logistics - General ® AFS Central
Functions ® AFS Seasons ® Change (transaction /afs/ss02).
You can maintain one record for a particular season/collection/theme combination. The creation of the record for a season is mandatory if the
season is used in MM/PP/IM. Creation Date and Delivery D ate are used for season determination and season check.
Limitations
● Avai labl e-to-Promis e (ATP) does not consider seasonality.
● Season, collec tion, and theme are not relevant for valuation.
● Season, collec tion, and theme are not present in reservation, deliveri es and warehouse management (WM).
!--a11y-->
1.1.2 AFS-Interfaces
PUBLIC Page 6 of 77
The following sections contain information on the AFS interfaces.
!--a11y-->
1.1.2.1 AFS Basic Data

The following sections contain information on the grid master data and the material master.
You can use the ALE Shared Master Data Tool for grid master data and the material master.
!--a11y-->
1.1.2.1.1 Grid Master Data

As a rule, one of the first things you should carry out during the Apparel & Footwear Solution start-up is the transfer of grid data from a legacy s ystem. This step is
required because it is usually not possible to manually create initial data in the SAP system due to the multitude of grids used. If you are using a distributed
sys tem, you must exchange data within this sy stem as well.
You can transfer grids from legacy systems via ALE. The grid data is transferred here in an IDoc. This is valid for the transfer from a non-SAP system as well as
for the transfer from an SAP system. The SMD tool is available for the distribution between SAP systems.
Here are some typical application examples:
Transfer of grid data from a non-SAP System

Distribution of changed and/or newly created grid data between SAP systems (in which, for example, a system can be located on another computer)
Providing legacy or external systems with changes and/or newly created grid data
Transfer of data from data pools
Targeted distribution of grids (sending data manually)
AFS Special Features

You can use the AFS IDoc type to send AFS grids. Functions for both the receipt and issue of IDocs have been implemented. The reduction and the connection to
the SMD tool have been implemented.
Grid values are mapped using ALE in the same way as the mapping of the online transaction. The maintenance of the dimension IDs and of the valid grid values
in Customizing is decis ive for the grids bec ause the validity of the sent IDs and grid values is checked usi ng check tables.
!--a11y-->
Technical Information: Grid Master Data

Technical Description of the IDoc Type
Document type Direction Logical Message IDoc type Operation code
Grid Receipt J3AGRI J3AGRI02 J3AN
Grid Issue J3AGRI02
AFS-Specific Fields for the Grid Master
Segment Fields Explanation Origin
E1J3AGH1 MSGFN Function No processing
J_3APGNR Material grid number J_3APGDH-J_3APGNR
J_3AVDAT AFS product grid validation according to J_3APGDH-J_3AVDAT

date
J_3AKTXT Product grid short text J_3APGDH-J_3AKTXT
J_3ADLKZ Delete indicator J_3APGDH-J_3ADLKZ
J_3AUSED AFS dimension indicator used in product J_3APGDH-J_3AUSED

matrix
J_3ACRDT Date of creation J_3APGDH-J_3ACRDT
J_3AEDDT Date changed/deleted J_3APGDH-J_3AEDDT
J_3AUSER User name J_3APGDH-J_3AUSER
J_3ABZD1 Dimension indicator for first dimension J_3APGDH-J_3ABZD1
J_3ABZD2 Dimension indicator for second dimension J_3APGDH-J_3ABZD2
J_3ABZD3 Dimension indicator for third dimension J_3APGDH-J_3ABZD3
J_3ABZDX Selection dimension ID J_3APGDH-J_3ABZDX
J_3ASGTP Material grid type J_3APGDH-J_3ASGTP
J_3ABYT1 Number of bytes of dimension 1 J_3APGDH-J_3ABYT1
PUBLIC Page 7 of 77
J_3ARGTP Reference material grid type J_3APGDH-J_3ARGTP
J_3ARGNR Reference material grid number J_3APGDH-J_3ARGNR
J_3ARDAT Valid-from date of reference material grid J_3APGDH-J_3ARDAT
J_3AMGNR Master grid number J_3APGDH-J_3AMGNR
J_3AMDAT Master grid validation according to date J_3APGDH-J_3AMDAT
J_3ASODI1 Sort sequence for dimension 1 J_3APGDH-J_3ASODI1
J_3AGFILL Filler character for grid display J_3APGDH-J_3AGFILL
J_3AGCONV Check if conversion desired J_3APGDH-J_3AGCONV
J_3AGSORT Sort grid values? J_3APGDH-J_3AGSORT
J_3ADOCALL Activate change history at grid level J_3APGHD- J_3ADOCALL
J_3ARECNOT Maximum number for grid history counter J_3APGHD-J_3ARECNOT
J_3ARECNO Grid history counter J_3APGHD-J_3ARECNO
J_3ABZD1_NEW First characteristic name J_3APGHD-J_3ABZD1
J_3ABZD2_NEW Second characteristic name J_3APGHD-J_3ABZD2
J_3ABZD3_NEW Third characteristic name J_3APGHD-J_3ABZD3
J_3ABZDX_NEW Characteristic name in Z axis of material J_3APGHD-J_3ABZDX

grid
J_3ABXDX Characteristic name in X axis of material J_3APGHD-J_3ABXDX

grid
J_3ABYDX Characteristic name in Y axis of material J_3APGHD-J_3ABYDX

grid
/AFS/GRIDBLKZ Di splay all colu mns/li nes during grid entry J_3 APGHD-/AFS/GRIDBLKZ
/AFS/GRIDBLKZ2 Di splay all colu mns/li nes during grid entry J_3 APGHD-/AFS/GRIDBLKZ2
/AFS/GRIDBLKZ3 Di splay all colu mns/li nes during grid entry J_3 APGHD-/AFS/GRIDBLKZ3
J_3AGCONV2 Check if conversion desired J_3APGHD- J_3AGCONV2
J_3AGCONV3 Check if conversion desired J_3APGHD- J_3AGCONV3
E1J3AGE MSGFN Function No processing
J_3APGNR Material grid number J_3APGEN-J_3APGNR
J_3AVDAT AFS product grid validation according to J_3APGEN-J_3AVDAT

date
J_3AKORD1 AFS coordinate first dimension J_3APGEN-J_3AKORD1
J_3AKORD2 AFS coordinate second dimension J_3APGEN-J_3AKORD2
J_3AKORD3 AFS coordinate third dimension J_3APGEN-J_3AKORD3
J_3AKORDX Grid value J_3APGEN-J_3AKORDX
J_3ADLKZ Delete indicator J_3APGEN-J_3ADLKZ
J_3AUSED
J_3ATDAT Dimension display for date J_3APGEN-J_3ATDAT
J_3AFDAT Dimension display: from date J_3APGEN-J_3AFDAT
E1J3AGC MSGFN Function No processing
KNUMH Number of condition record J_3AGRCD-KNUMH
J_3APGNR Material grid number J_3AGRCD- J_3APGNR
J_3AVDAT AFS product grid validation according to J_3AGRCD- J_3AVDAT

date
J_3ASIZE AFS grid value J_3AGRCD- J_3ASIZE
KAPPL Application J_3AGRCD-KAPPL
KSCHL Condition type J_3AGRCD-KSCHL
MINAU Minimum order quantity in basic unit of J_3AGRCD-MINAU

measure
J_3AVMNG AFS default order quantity J_3AGRCD-J_3AVMNG
VRKME Sales unit J_3AGRCD-VRKME
J_3AHSIZ AFS heart size J_3AGRCD-J_3AHSIZ
J_3ASPRO AFS dimension: Size % spread - order J_3AGRCD-J_3ASPRO
J_3ASZGR AFS SKU group for pricing J_3AGRCD-J_3ASZGR
PUBLIC Page 8 of 77
TAXKM Tax classification material J_3AGRCD-TAXKM
DWERK Delivery plant J_3AGRCD-DWERK
J_3AVEMA Material number of vendor J_3AGRCD-J_3AVEMA
J_3AROF Rounding factor J_3AGRCD-J_3AROF
J_3AVEMA_N
!--a11y-->
1.1.2.1.1.2 Grid Master Data: Dialog Functions and their

Support in ALE
Number Assignment in ALE
During the transfer and distribution of grid master data via Application Link Enabling (ALE), the following types of number assignments are supported:
internal number assignment
This type of number assignment is only relevant for the initial transfer of data. This type is never used during the distribution of data using ALE
because grids always retain their numbers from the source system during the distribution of data.
external number assignment
You can use this type of number assignment for the initial transfer of data as well as for the data distribution, provided that the grid numbers are
transferred unchanged from the legacy system.
Checks in ALE
During the transfer and distribution of data using ALE, all transferred data undergoes the same checks as in the dialog.
Error Handling in ALE
If a logical error caused by grid maintenance occurs during the processing of an IDoc, the system terminates the corresponding maintenance transaction and the
IDoc receives the status incorrect . If no logical error occurs, the IDoc receives the status succ essful .
For IDocs with the status incorrect or succes sful , the status record receives the messages that were issued during process ing. After the logical errors have
been resolved, you can rep rocess the corresponding IDocs.
You can find information on troubleshooting and resolution of technical errors in the ALE documentation. To find errors, you should first check the settings that you
have made in Customizing of the Dis tribution (ALE).
Customer Enhancements ( User Exits)
Using the following user exits, you can extend the grid master by adding your own table fields. The data in the user-defined fields can also be processed using
ALE.
In order to process user-defined data using ALE, you need to:
activate the sys tem enhancement J_3 AIMM1
You can find further information in the documentation BC - Changes to the SAP-Standard .
create the necessary source text for the user exit EXIT_SAPLJ4AI_102, which is included in the sy stem enhancement J_3 AIMM1
create a new IDoc segment
!--a11y-->
1.1.2.1.2 Material Master

As a rule, one of the first things you should do during R/3 implementation is transfer material data from a legacy sy stem. This step is required because it is
usually not possible to manually create initial data in the SAP system due to the multitude of materials used. If you are using a distributed system, you must
exchange data within this sy stem as well.
You can transfer stock from external systems in one of two ways:
Data can b e transferred in a direct input
Data can b e transferred using App lication Link Enabling (ALE)
During data transfer and distribution, you can maintain all materials with all required data exactly as you would in the dialog. This is not, however, valid for the
following data:
Configuration valuation and assignment to a configurable material

Export licenses and customs preferences
Product versions
The actual material data is transferred in an IDoc and the additional data is transferred in a separate IDoc. This is due to the following reasons:
IDocs and associated distribution and transfer functions already exist for most of the additional data.
It must be possible to distribute additional data separately because there is normally a separate maintenance option for this data in addition to the integrated
maintenance in the material master.
PUBLIC Page 9 of 77
You must therefore enter the sequence in which each related IDoc should be processed. If you do not do this, terminations may occur in the system during
processing (for example, if the system attempts to create a purchasing info record for a material that does not yet exist in the database). For this reason, you can
define dependenci es between objects i n Customizing for Dis tribution (ALE) . In doing so, you are ensuring that the changes i n a superior object are executed
simultaneously when changes are made to dependent objects so that both IDocs are created in the correct sequence. Just as is the case during the creation of the
IDocs by the sender, the IDocs are first processed by the recipient after the arrival of all related IDocs in the target system has been reported.
Typical application examples:
Transfer of material data from an R/2 system
Distribution of changed and/or newly created material data between SAP systems (in which, for example, a system can be located on another computer)
Providing legacy or external systems with changes and/or newly created material data
Transfer of data from data pools
Targeted distribution of materials (sending data manually)

The AFS IDoc type can be used to send standard material data and AFS material data. Functions for both the receipt and issue of IDocs have been implemented.
The reduction and the connection to the SMD tool have been implemented. The new WM views are also now supported.
Grid values are mapped using ALE in the same way as the mapping of the dialog transaction. It is very important that a master grid is entered for AFS materials.
The master grid must be entered in the IDoc for the materials.
Categories are mapped in the system using the same method as the online transaction. It is essential that a coverage strategy is entered in the IDoc.
!--a11y-->
1.1.2.1.2.1 Technical Information: Material Master

Document type Direction Logical Message IDoc Type Process Code
Material Inbound J3AMAT /AFS/MATMAS04 MATM
Material Outbound RBDSEMAT /AFS/MATMAS04
AFS-specific fields for the material master
Segment Field Explanation Origin
E1J3MRA MSGFN Function No processing
J_3AMIND AFS material master indicator MARA-J_3AMIND
J_3AMSTAT AFS material master status MARA-J_3AMSTAT
J_3APGNR Material grid number MARA-J_3APGNR
J_3AKALSV Grid determination procedure SD MARA-J_3AKALSV
J_3AKALSM Grid determination procedure MM MARA-J_3AKALSM
J_3ASMAT Indicator for set material MARA-J_3ASMAT
J_3APROFP Plant profile MARA-J_3APROFP
J_3APROFC Category profile MARA-J_3APROFC
J_3APROFG Grid profile MARA-J_3APROFG
J_3APROFT Period profile MARA-J_3APROFT
J_3AGMID Dimension conversion: Material MARA-J_3AGMID

indicator
J_3ANOGRID AFS material without grid (DUMMY MARA-J_3ANOGRID

grid with only one dimension)
J_3AFCC Fabric content code MARA-J_3AFCC
J_3AGEND Gender MARA-J_3AGEND
J_3ACOL Material master: Color MARA-J_3ACOL
J_4KCSGR Category structure MARA-J_4KCSGR
/AFS/SCLAS Special procurement key MARA-/AFS/SCLAS
/AFS/SCHNITT Cut MARA-/AFS/SCHNITT
J_4KCOVSA Coverage Strategy MARA-J_4KCOVSA
E1J3ASE MSGFN Function No processing
J_3ASEAN Season indicator J_3AMSEA-J_3ASEAN
J_3ASIZE AFS grid value J_3AMSEA-J_3ASIZE
J_4KRCAT Requirements Category J_3AMSEA-J_4KRCAT
/AFS/COLLECTION Collection J_3AMSEA-/AFS/COLLECTION
/AFS/THEME Topic J_3AMSEA-/AFS/THEME
E1J3AQD MSGFN Function No processing
PUBLIC Page 10 of 77
J_3AMQCA Quota category J_3AQDST-J_3AMQCA
E1J3MRC MSGFN Function No processing
J_3AMIND AFS material master indicator MARA-J_3AMIND
J_3AMSTATC AFS material master status MRP MARC-J_3AMSTATC
J_3AMSTAT AFS material master status MARC-J_3AMSTAT
J_4KCOVS Version number component MARC-J_4KCOVS
J_3ADISPKZ MRP indicator MARC-J_3ADISPKZ
J_3AHORIZ Horizon key MARC-J_3AHORIZ
J_3APRFC Category profile MARC-J_3APRFC
J_3APRFG Grid profile MARC-J_3APRFG
J_3APRFT Period profile MARC-J_3APRFT
J_3ASGRID Single grid value MARC-J_3ASGRID
J_3AVERPR Default version for presizing MARC-J_3AVERPR
J_3AVERMR Default version for MRP MARC-J_3AVERMR
J_3AVERSS Default version for MRP safety stock MARC-J_3AVERSS
J_3AVERPU Default version for Purchasing MARC-J_3AVERPU
J_3AVERSD Default version for SD MARC-J_3AVERSD
J_3AEKORG Default purchasing organization for MARC-J_3AEKORG

source allocation
J_3APRCM Consumption priority MARC-J_3APRCM
J_3ABUND Material created with bundles MARC-J_3ABUND
J_3ACHINT Discrete batch number MARC-J_3ACHINT
J_3ABAINT Dimension used as batch number for MARC-J_3ABAINT

material without coverage strategy
J_3ARISK AFS risk factor MARC-J_3ARISK
J_3ADEFSI Default grid value MARC-J_3ADEFSI
J_4KDEFSC Default value stock category MARC-J_4KDEFSC
J_4KCOVS_4 Coverage Strategy MARC-J_4KCOVS_4
J_4KDEFSC_4 Default value stock category MARC-J_4KDEFSC_4
J_4AATPSI ATP/MRP check method (time or MARC-J_4AATPSI

category)
J_3ASLHMOD Activate SKU horizon method MARC-J_3ASLHMOD
J_3AMROUND MARC-J_3AMROUND
J_3AMRDMENG MARC-J_3AMRDMENG
E1J3AAD MSGFN Function No processing
J_3AKORD AFS dimension according to matrix J_3AMAD-J_3AKORD
J_4KSCAT Stock Category J_3AMAD-J_4KSCAT
EISBE Safety stock J_3AMAD-EISBE
BSTMI Minimum lot size J_3AMAD-BSTMI
BSTRF Purchase order quantity rounding value J_3AMAD-BSTRF
J_3ASIGR AFS SKU group for lot-sizing procedure J_3AMAD-J_3ASIGR
REFVAL AFS: Reference values for all J_3AMAD-REFVAL

categories without special values
J_4ASTAT AFS: MRP status for dimension J_3AMAD-J_4ASTAT

validation
J_4ADTFR Date J_3AMAD-J_4ADTFR
J_3ARISK AFS risk factor J_3AMAD-J_3ARISK
LGRAD Area not further defined J_3AMAD-LGRAD
WZEIT Replenishment lead time J_3AMAD-WZEIT
WZEITSG Total replenishment lead time for SKU J_3AMAD-WZEITSG

group
J_3APQTY AFS packing quantity – no longer J_3AMAD-J_3APQTY

used
J_3APQUN AFS unit of the packing quantity – no J_3AMAD-J_3APQUN

longer used
J_3ACASE Standard packing type – no longer J_3AMAD-J_3ACASE

used
VMSTA Distribution chain-specific material J_3AMAD-VMSTA
status - no longer used
VMSTD Validity start date of the distribution J_3AMAD-VMSTD

chain-specific material status – no
longer used
REFSD AFS: Reference values for all J_3AMAD-REFSD

categories without spec ial values - no
longer used
BRGEW Gross weight – no longer used J_3AMAD-BRGEW
NTGEW Net weight – no longer used J_3AMAD-NTGEW
VOLUM Volume – no longer used J_3AMAD-VOLUM
REFDIM AFS: Reference values for all J_3AMAD-REFDIM

categories without spec ial values - no
longer used
AUSDT Expiry date J_3AMAD -AUSDT
NFMAT Follow-up Material J_3AMAD-NFMAT
NFWRK Value J_3AMAD-NFWRK
/AFS/NFSIZE Follow-up grid value for the MRP J_3AMAD-/AFS/NFSIZE

discontinuation
E1J3AKA MSGFN Function No processing
J_3AKORD AFS dimension according to grid J_3AMADKA-J_3AKORD
J_4KSCAT Stock Category J_3AMADKA-J_4KSCAT
J_3AKALSW Preference SKU J_3AMADKA-J_3AKALSW
J_3AKALGR Valuation type (AFS) J_3AMADKA-J_3AKALGR
TVERS Transportation indicator: planned J_3AMADKA-TVERS

version
VPRSV Price control indicator J_3AMADKA-VPRSV
PRICE Standard price J_3AMADKA-PRICE
EKALR Material is costed with quality structure J_3AMADKA-EKALR
ZKPRS Future price J_3AMADKA-ZKPRS
ZKDAT Validity start date of the price J_3AMADKA-ZKDAT
J_3ASRD AFS: surcharges +/- J_3AMADKA-J_3ASRD
J_3ARKALGP Reference preference group J_3AMADKA-J_3ARKALGP
/AFS/E1MLGN1 MSGFN Function No processing
LGNUM Warehouse number/complex /AFS/MLGN1-LGNUM
J_3ASIZE AFS grid value /AFS/MLGN1-J_3ASIZE
LHMG1 1. Loading equipment quantity /AFS/MLGN1-LHMG1
LHME1 Unit of measure for 1. Loading /AFS/MLGN1-LHME1

equipment quantity

equipment quantity

equipment quantity
LETY1 1. Storage unit type /AFS/MLGN1-LETY1
J_4KSCAT Stock Category /AFS/MLGN2-J_4KSCAT
LTKZA Storage type indicator removal from /AFS/MLGN2-LTKZA

storage
LGBKZ Storage section indicator /AFS/MLGN2-LGBKZ
BSSKZ Special movement indicator - /AFS/MLGN2-BSSKZ

Warehouse Management
L2SKR Material relevance for two-step picking /AFS/MLGN2-L2SKR
LTKZE Storage type indicator, placement in /AFS/MLGN2-LTKZE

storage
BLOCK Bulk storage indicator /AFS/MLGN2-BLOCK
KZMBF Indicator: Message to Inventory /AFS/MLGN2-KZMBF
Management
KZZUL Indicator: Addition to existing stock /AFS/MLGN2-KZZUL

allowed
J_4KSCAT Stock Category /AFS/MLGN3-J_4KSCAT
MKAPV Capacity consumption /AFS/MLGN3-MKAPV
BEZME Reference unit of measure for capacity /AFS/MLGN3-BEZME

consumption
/AFS/E1MLGTM MSGFN Function No processing
LGNUM Warehouse number/complex /AFS/MLGT-LGNUM
J_3ASIZE AFS grid value /AFS/MLGT-J_3ASIZE
J_4KSCAT Stock Category /AFS/MLGT-J_4KSCAT
LGPLA Storage bin /AFS/MLGT-LGPLA
LPMAX Maximum storage bin quantity /AFS/MLGT-LPMAX
LPMIN Minimum storage bin quantity /AFS/MLGT-LPMIN
MAMNG Control quantity /AFS/MLGT-MAMNG
NSMNG Replenishment quantity /AFS/MLGT-NSMNG
KOBER Picking area /AFS/MLGT-KOBER
RDMNG Rounding quantity /AFS/MLGT-RDMNG
E1J3MKE MSGFN Function No processing
J_3AVASG AFS VAS material group J_3AMVKE-J_3AVASG
J_3APIND AFS pricing indicator in material J_3AMVKE-J_3APIND

master
/AFS/E1MARM MSGFN Function No processing
MEINH Unit of measure for display /AFS/MARM-MEINH
J_3ASIZE Grid value /AFS/MARM-J_3ASIZE
J_4KSCAT Stock Category /AFS/MARM-J_4KSCAT
VOLUM Volume /AFS/MARM-VOLUM
BRGEW Gross weight /AFS/MARM-BRGEW
NTGEW Net Weight /AFS/MARM-NTGEW
REFDIM AFS: Reference values for all /AFS/MARM-REFDIM

/AFS/E1MEANM MSGFN Function No processing
J_3AKORDX Grid value /AFS/MEAN-J_3AKORDX
/AFS/EANBLOCK Category value /AFS/MEAN-/AFS/EANBLOCK
/AFS/CAT_APPL Category type /AFS/MEAN-/AFS/CAT_APPL
/AFS/E1MVKE MSGN Function No processing
J_3ASIZE Grid value /AFS/MVKE-J_3ASIZE
J_4KRCAT Requirement category /AFS/MVKE-J_4KRCAT
VMSTA Distribution chain-specific material /AFS/MVKE-VMSTA

status
VMSTD Validity start date of the distribution /AFS/MVKE-VMSTD

chain-specific material s tatus
/AFS/REFVMS AFS: Reference values for all /AFS/MVKE-/AFS/REFVMS

J_3APQTY AFS packing quantity /AFS/MVKE-J_3APQTY
J_3APQUN AFS: unit for packing quantity /AFS/MVKE-J_3APQUN
J_3ACASE Standard packing category /AFS/MVKE-J_3ACASE
/AFS/REFPQ AFS: Reference values for all /AFS/MVKE-/AFS/REFPQ

J_3AGEND Target group /AFS/MVKE-J_3AGEND
/AFS/REFGEND AFS: Reference values for all /AFS/MVKE-/AFS/REFGEND

!--a11y-->
Material Master: Dialog Functions and their Support in ALE
Number Assignment in ALE

During the transfer and distribution of material master data via Application Link Enabling (ALE), the following types of number assignments are supported:
● internal number assignment
This type of number ass ignment is only relev ant for the initial transfer of data. This type is never use d during the distribution of data using ALE bec ause
materials always retain their numbers from the source system during the distribution of data.
● external number assignment
You can use this type of number assignment for the initial transfer of data as well as for the data distribution, provided that the material numbers are
transferred unchanged from the legacy system.
Checks in ALE
During the transfer and distribution of data using Application Link Enabling (ALE), all transferred data undergoes the same checks as in the dialog.
The system not only c arries out the usual field c heck s, b ut also check s the foreign key s and required entry fields that are set in Customizing of the Material
Master under Maintain Field Selection Data Screens .
However, a required field check for AFS fields in AFS tables does not take place.
Field Selection in ALE

During the transfer and distrib ution of data via ALE, the field selec tion you have set in Customizing of the Material Master under Maintain Field Selec tion for
Data Screen will be interp reted exactly the same as in the dialog. However, the following different transaction references are used in ALE for the field selec tion at
the transaction level:
● MAL1 (for the creation of materials)
● MAL2 (to change materials)
The following transaction references are used for the field selection at the transaction level in the dialog:
● MM0 1 (for the creation of materials)
● MM0 2 (to change materials)
This allows you to specify a different field selection at the transaction level for the ALE and the dialog.
Fields that are defined as not ready for input in the Customizing of the Material Master are not transferred. The sys tem iss ues an app ropriate warning. Required
entry fields are then checked.
However, a required field check for AFS fields in AFS tables does not take place.
Error Handling in ALE

If a logical error caused by the material maintenance occurs during the processing of an IDoc, the system terminates the corresponding maintenance transaction
and the IDoc receives the status incorrect . If no logical error occurs, the IDoc receives the status succes sful .
For IDocs with the status incorrect or succes sful , the application log receives the messages that were issued during processing. After the logical errors have
been resolved, you can rep rocess the corresponding IDocs.
You can find information on troubleshooting and resolution of technical errors in the ALE documentation. To find errors, you should first check the settings that you
have made in Customizing of the Dis tribution (ALE).
Customer Enhancements (User Exits)

In Customizing of the Material Master under Configure Customized Material Master , you can extend the material master by add ing your own table fields. The
data in the user-defined fields c an also be distributed via App lication Link Enabling (ALE).
In order to be able to distribute user-defined data via ALE, you need to:
● activate the sys tem enhancement MGV0 000 1
You can find further information in the documentation BC - Changes to the SAP-Standard .
● create the necessary source text for the following user exits, which are included in the system enhancement MGV000 01.
○ EXIT_SAPLMV01_002
○ EXIT_SAPLMV03_002
You can find further information in the system enhancement MGV00001 and user exit documentation.
● create a new IDoc segment
Error messages
Error number Possible causes Solution
8J670 When changing or enhancing a material by adding a plant, Check IDoc and correct the main tenance status.
the wrong maintenance status is also delivered.
8J671 Transferred data is duplicated, for example, the same Check IDoc and correct dupli cate entries.
season code is used twice for the same dim ension
Material Conversion ID in Material Master
As of the 6.0 release, you cannot maintain material conversion IDs. However, the old/existing materials can c ontinue to work with conversion IDs that have already
been created.
BAPI
The BAPI /AFS/BAPI_MATERIAL_SAVEDATA cannot clear the values in the AFS views. Hence, you can use either IDocs or direct input to clear the values.
!--a11y-->
1.1.2.2 Sales and Distribution (SD)

The following sections contain information on the area of Sales and Distribution.
!--a11y-->
1.1.2.2.1 Shipping/Transport: Transportation Interface
Features
Shipment data can be sent per EDI. Shipp ing documents are generally us ed in two scenarios:
The sender transfers a partially or completely planned shipment to the forwarding agent (shipping order SHPMNT).
The sender or the forwarding agent provides the customer with information about a shipment to be expected (shipment notification SHPADV).

For AFS, only the outbound messages (SHPMNT and SHPADV) are implemented and not the inbound.
Customizing
Logical Message IDoc Type Output type Partner Type Process Code
SHPMNT/SHPADV /AFS/SHPMNT03 SEDI WE or SP SHPM (Outbound)
Technical Information
The AFS specific segments are filled in exactly the same way as in the IDoc /AFS /DELVRY02.
See also:
Technical Information: Delivery Interface
!--a11y-->
1.1.2.2.1.1 Shipping/Transport: Delivery Interface
Features
As of R/3 Standard Release 4.0 there is a completely new delivery interface. This interface groups together all messages that have a reference to the delivery.
The following logical messages are supported in AFS:
SHPORD (issue) / SHPCON (receipt): Shipping order or confirmation from an external servic e provider who can carry out packing, pick ing and shipp ing.
(EDI)
WHSORD (issue) / WHSCON (receipt): Warehouse order or confirmation from an internal warehouse (external software), in which packing, picking and
shipping are carried out. (ALE)
CARNOT (issue): Shipping order. With the notification of the forwarding agent, the delivery data is transferred so that the forwarding agent carries out the
pickup and inbound delivery of the goods according to the customer's request. (EDI)
DESADV (issue): Shipping notification. The shipping notification serves as notification of delivery to the customer. (EDI)
DESADV, CARNOT, SHPORD and WHSORD (issue) as well as SHPCON and WHSCON (receipt) are the same in terms of content and function. The
various message typ es s erve only as a semantic differentiation.
The sending of a pick order works as of Release 4.0 via message control in the delivery. PICKSD, SDPICK and SDPACK are therefore all replaced by the new
IDoc types (DELVRY02).
Non-implemented Functions
A batch sp lit is not permitted in the confirmation. The batch that must be verified is the one that is also in the delivery.
Overp icking of a stockk eeping unit (SKU) is not permitted.
Deletion of batch items in the delivery
Restrictions that arise from the application

Mapping of SKU
In the outbound IDocs of the delivery interface, an item segment (E1EDL24) is created in the IDoc for each SKU.
!--a11y-->
1.1.2.2.1.1.1 Customizing: Delivery Interface
Logical Message IDoc Type Output Type Partner Type Process Code
WHSORD WHSCON /AFS/DELVRY02 WSOR LS LS DELV (outbound) DELV

/AFS/DELVRY02 (inbound)
SHPORD SHPCON /AFS/DELVRY02 SHOR LI LI DELV (outbound) DELV

/AFS/DELVRY02 (inbound)
CARNOT /AFS/DELVRY02 CANO LI DELV (outbound)
DESADV /AFS/DELVRY02 LAVA KU DELV (outbound)
!--a11y-->
1.1.2.2.1.1.2 Technical Information: Delivery Interface
Description o f the IDoc Fields

Description of the AFS Fields in the Outbound ID oc
Outbound IDocs contain all relevant delivery information. To keep the data quantity as low as possible, you can filter out any segments that are not required.
Segment Fields Explanation
E1EDL24 KDMAT The customer material number is entered here, even

if it was entered at SKU level.
EAN11 The EAN/UPC number is entered here, even if it

was entered at SKU level.
/AFS/E1EDL24 J_3ALNGR AFS line groups indicator

The system uses this indicator to group SKUs that
are to be delivered together.
J_3ADEPM Indicates the customer department for whom the

SKU was ordered. This information field is taken from
the sales order.
/AFS/E1J3AKG J_3AKVGR6 Additional customer groups.

to The additional customer groups are managed in the
J_3AKVGR10 customer master in an AFS-sp ecific view.
E1J3AI2 J_3AQFREF Indicates the type of reference document:

002: Reference to the SAP order number, item
number and schedule line number
003: Reference to the customer purchase order
number and the purchase order item (SKU level in
field POSEX)
J30: ALE ID. Unique ID number for a schedule line
in an ALE stock transfer scenario. This is an internal
number and is assigned by the system.
E1J3AIM J_3AOBIDQF Indicates the type of material:

00 2: Indicates the SAP material number, the grid
value and the category. The customer material
number and the EAN/UPC number are entered in
the parent segment E1EDL24.
E1J3AIT J_3ASTORE Store number for ticketing/labeling.
J_3ATLTYP Ticketing/labeling type

Unique key that determines the type of label.
J_3ATLMAT Ticketing/labeling material
J_3ACHARC Code determining the price charged when the

customer pays for ticketing/labeling.
E1J3AITX J_3ATLTXT Text that should be on the label.
J_3ATLORD Indicates that the text relates to the order
J_3ATLITEM Indicates that the text relates to the item
J_3ATLSIZE Indicates that the text relates to the size
E1J3AIP Segment containing packing data. The fields are

identical to E1J3AIT.
E1J3AIS Segments that contain data for special services. The

fields are identical to E1J3AIT.
E1EDL41 QUALI Indicates the reference data for the ordering party:
001: Purchase order data for the customer
002: Purchase order data for the ship-to party
POSEX Contains the customer's item number at SKU level.
Description of the IDoc Fields in the Inbound IDoc
Picking Confirmation without Flow Records
The following fields must be filled in the IDoc, as a minimum requirement:
E1EDL20-VBELN Delivery number
E1EDL24-POSNR Item number for the SKU (for example, 900001)
E1EDL24-MATNR Material number
E1EDL24-CHARG Batch number for the SKU in the delivery
E1EDL24-LIFMG Confirmed pick quantity
E1EDL19-QUALF 'QUA'
Picking Confirmation with Flow Records
In addition to the above mentioned fields, segment E1EDL18-QUALF = PIC must also be filled with data.
Other Confirmations
Weight and volume are confirmed for the entire delivery or for each individual batch. The item number for the SKU must be entered in field POSNR. All other
fields are filled in the SAP standard.
Indicator E1EDL18-QUALF = 'PGI' controls goods issues.
Shipping units are confirmed in the same way as in the standard. The item number for the SKU must be entered in field E1EDL44-POSNR.
Customer Enhancements (User Exits)

EXIT_SAPLV56K_001
Customer enhancement for modifying the control record. The control record and all relevant tables for the delivery are transferred.
EXIT_SAPLV56K_002
Customer enhancement called after each individual standard segment. This customer enhancement is used to fill specific z-segments. The control
record, the current segment name, all the relevant delivery tables and the IDoc data records are transferred.
!--a11y-->
1.1.2.2.2 Sales
Available Document Types

The following table shows an overview of the supported document types, their assigned logical messages, and the IDoc type to be used.
Remember that this documentation always refers to the most recent version of an IDoc type, unless specified otherwise. SAP recommends,
therefore, that you use the most recent IDoc type version.
Document Type Direction Logical Message IDoc Type Output Type Process Code
Orders Inbound ORDERS /AFS/ORDERS05 J3AA
Contracts ( CQ) Inbound ORDERS /AFS/ORDERS05 J3AA
Order Ch ange Inbound ORDCHG /AFS/ORDERS05 J3AC
Order Confir mation Outbound ORDRSP /AFS/ORDERS05 BA00 SD10
Quotations Outbound QUOTES /AFS/ORDERS05 AN00 J3AJ
!--a11y-->
1.1.2.2.2.1 Sales Order
Features
Sales orders can be created and updated using IDoc interfaces. In contrast to the standard IDoc process, the AFS-specific enhancements are primarily in the
areas of dimension p rocess ing, p rocessi ng of VAS data, and MSO processing. The decisive technical difference from standard processing is the implementation
of the data transfer to the application with standardized direct input modules. On the one hand, this allows for a significantly better runtime for the process. On the
other hand, it also prevents the possib ility of running the data processing visi bly as is normally possib le in an inbound process when using batch inp ut.
An order can also be created as a contrast release order for an existing quantity contract using the IDoc interface. Individual contracts or contract items can then
be directly referenced. The corresponding dependencies are documented in the document flow. A reference to an existing quantity contract in the incoming order
via the IDoc interface can only be automatically implemented when two customer enhancements are used. For more information about the procedure, see the SAP
Notes on c ustomer enhancements EXIT_SAPLJ4AS_601 and EXIT_SAPLJ4AS_7 01.
To use enhanced error handling options, see section IDoc Error Handling for Inbound IDocs.
The current release uses IDoc type /AFS/OR DERS0 5. This IDoc type is now in the fifth version (after J3AORD01, J3AORD0 2, /AFS/O RDERS03 and
/AFS/ORDERS04).
You must always use the most recent version of an IDoc type.
AFS Restrictions
● When creating an MSO ex plosi on, the sp litting of the created order into indiv idual documents is n ot automaticall y triggered.
● The deliv ery order is not sup ported.
● Conditions in the inc oming sales order cannot be c hanged at the header level, item l evel or dimens ion level. Read the Notes in the documentation for
segments E1EDK04, E1EDK05, E1EDP04 and E1EDP05.
● You cannot use the IDoc interface to automatical ly c opy c ontracts to a sales document as an attachment with reference to a contact. A contract reference can
be made for each individual item or dimension.
● VAS data or MSOs c annot be changed in AFS.
● AFS does not sup port adding individual comp onents by means of an order change IDoc (ORD CHG) to a bill of material (BOM) that has already b een
exploded in a s ales document.
● Creating MSOs with VAS data
● In order changes p er IDoc, the partner functions AG, RE, RG, and SB c annot be changed (this is al so valid when adding new items and/or dimens ions).
● Only the partner functions RE, WE and RG are process ed at item level.
● AFS does not supp ort changes to the material number or the dimensi on of an already exis ting stock keep ing unit (SKU). SKUs can only b e flagged with one
deletion indica tor.
● Contracts: AFS does not sup port the transfer or additional contract data (table V EDA) usi ng the IDoc interface.
● The purchase order (PO) numb er will get deleted when you have created a sales order with reference to a contract via IDoc and the PO number is p ass ed at
the item level by entering the document field (BSTKD) in the segment EIEDP02 of the IDoc.
It is effective only when the PO number is pass ed at the header level.

● The Customer Material Number will be deleted if there is a change in the plant of a sales order.
● When you do a call-off via the IDoc and the reference document contains a BO M (Bill O f Material), then the component level reference does not take p lace as
IDoc does not support it. However if you implement the available user exit, this functionality will be obtained.
!--a11y-->
1.1.2.2.2.1.1 Customizing: Sales Order

The workflow basic settings for error handling must be maintained (transaction SWU3).
You must assign the EDI pricing conditions JED1 and JED2 to the pricing procedure of the respective document type of the sales area. These pricing
conditions serve to transfer the expected customer price / customer value to the sales document.
You must maintain the translation of EDI internal item categories into SD item categories in Customizing (transaction code VOE1) in the table EDPST (see
also notes for the documentation for segment E1EDP01, Field PSTYP).
IMG: Sales and Distribution ® Electronic Data Interchange ® EDI Messages ® Convert SAP Item Category to IDoc Item Category.
Using the table EDPAR, you can convert external partner numbers into internal partner numbers as needed. Maintain the table using transaction VOE4.
Read also the notes in the documentation for the segments E1EDKA1 and E1EDPA1.
IMG: Sales and Distribution ® Electronic Data Interchange ® EDI Messages ® Configure EDI Partners ® Convert External to Internal Partner Numbers.
You can control the determination of the sales area data (sales organization, distribution channel, division) with the table EDSDC. Since an EDI partner will
only rarely transmit this data (see notes for the documentation on segment E1EDK14), the sales area can be determined for the transfer to the application
depending on the customer and vendor number. To do this call the transaction VOE2.
IMG: Sales and Distribution ® Electronic Data Interchange ® EDI Messages ® Configure EDI Partners ® Assign Customer/Vendor To Sales Organization
Data.
!--a11y-->
1.1.2.2.2.1.2 Technical Information: Sales Order

The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Note that documentation is
available for the IDoc segments and fields in SAP system. Call up this documentation in transaction we60. The respective segment hierarchy (interdependency of
the segments) can also be found in the documentation.
!--a11y-->
1.1.2.2.2.5.2 Document Header: General Data (Segment

E1EDK01)
Mandatory segment: YES
Field Explanation Processing
action Action code that concerns the entire EDI message No processing
kzabs Order acknowledgment requirement indicator No processing
curcy Currency code Here you transfer an ISO currency code that is
converted in the SAP internal currency code. If the
conversion is not success ful, error VG0 14 appears.
hwaer EDI local currency No processing
wkurs Exchange rate Is transferred to the document
zterm Term of payment Is transferred to the document
kundeuinr VAT registration number No processing
eigenuinr VAT registration number No processing
BSARt Document type No processing
BELNR IDoc document number No processing
ntgew Net Weight No processing
brgew Gross weight No processing
gewei Weight Unit No processing
fkart_rl Remuneration list type No processing
ABLAD Unloading point No processing
BSTZD Order number addition of customer Is transferred to the document
VSART Shipping condition Is transferred to the document
VSART_BEZ Description of shipping type No processing
recipnt_no Number of recipient No processing
kzazu Indicator: order combination Is transferred to the document
autlf Complete delivery indicator Is transferred to the document
augru Order reason Is transferred to the document
augru_bez Description order reason No processing
abrvw Is transferred to the document
abrvw_bez No processing
fktyp Billing category No processing
lifsk Delivery note block Is transferred to the document
lifsk_bez Description: delivery note block No processing
empst Receiving point Is transferred to the document
abtnr Department number No processing
delco Agreed delivery time No processing
wkurs_m Rate with indirect quotation No processing
!--a11y-->
1.1.2.2.2.5.2.1 Document Header: Organizational Data

(Segment E1EDK14)
Mandatory segment: NO
Field Short text Explanation
QUALF Organization indicator Describes the use of the data sent in field ORGID
(for exampl e 00 6 for division, 007 for distribution
channel, 008 for sales organization). With the
qualifier 012 the order type can also be transferred
in the field ORGID.
ORGID Organization ID See field QUALF.
The following indic ators are processed in the inbound IDoc:
006 Division
007 Distribution Channel
008 Sales Organization
010 Sales Group
012 Order Type
016 Sales Office
019 Purchase Order Type (SD)
J01 Department
If no data for sales or ganization, dis tribution channel and/or division is sent in the segment, the determination of the data is called using the table EDSDC.
An entry for the key sold-to party (AG ) + vendor number (LF) is then searched for. The sold-to party and vendor number are taken from the data from segment
E1EDKA1 for the partner function ,AG‘ (sold-to party from field ‚PARTN‘, vendor number from field ‚LIFNR‘). If segment E1EDKA1 is sent for partner function ,LF‘
(vendor) as well, the vendor number is then taken from this segment (field ‚PARTN‘).
If the determination of the sales area data goes wrong, you will see the error message VG204.
The sales area data can also be determined via the customer enhancement. The corresponding data is to be transferred to the fields DXVBAK-VKORG (= sales
organization), DXVBAK-VTWEG (= distribution channel) and DXVBAK-SPART (= division). The customer enhancement exit_saplj4as_002 should be used for
this.
If the order type (indicator ,012’) is not transferred in the IDoc, it will be set as standard order (,OR’). The default setting for the purchase order type (indicator 019)
is als o DFUE. Pleas e note that the valid purc hase order typ es are to be maintained for each order typ e in the IMG (Sales and Di strib ution ® Sales ® S ales
Documents ® Sales Document Header ® As sign O rdering Types (AFS)). If this ass ignment does not exist, the error message 00058 is displayed.
!--a11y-->
1.1.2.2.2.5.2.2 Document Header: Date Segment (Segment

E1J3K03)
IDDAT Indicator for Date Segment Indicator for the use of the date / time entries in the
following fields.
DATUM Date Is transferred to the document
UZEIT Time Is transferred to the document
J_3AQUALF Indicator Indicator for the qualification of the use of the date.
The field is used for purely informative reasons and
for adding information to the date. The permitted
value table is J_3AQUALF.
The following d ate indicators are process ed:
003 Requested delivery date
005 AFS: value-added service Date
006 AFS: Cancellation Date
007 Price determination date
014 Validity start date for outline agreements
022 Date for services
023 Pick-up date for delivery order (validity start date)
024 Pick-up date for delivery order (validity end date)
The requested delivery date (003) and the cancellation date (006) are checked for validity by the inbound function. This means that if one of these dates is in
the past (the reference date is the current system date), the processing terminates with the error mess age V1437. However, this error only leads to termination
in the first processing of an IDoc (IDoc is set to status 51). If the incorrect IDoc is processed a second time (for example, with transaction BD87 or report
RBDMANI2), the incorrect date only leads to a warning message which does not interfere with the update of the data.
!--a11y-->
1.1.2.2.2.5.2.3 Document Header: Taxes (Segment E1EDK04)
Field Explanation
MWSKZ VAT ID
MSATZ Value-added tax
MWSBT Sales tax amount
TXJCD Tax Jurisdiction Code
KTEXT Text field
Although data sent in the segment E1EDP04 will first be read by the inbound process ing, it cannot be transferred to the applic ation. This leads to the error
VG200 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.
!--a11y-->
1.1.2.2.2.5.2.4 Document Header: Conditions (Segment

E1EDK05)
Mandatory segment: No
Field Explanation
ALCKZ Surcharge or discount indicator
KSCHL Condition type (coded)
KOTXT Condition description
BETRG Fixed surcharge / discount on item total gross amount
KPERC Condition percentage rate
KRATE Condition record per unit
UPRBS Price Unit
MEAUN Unit of measure
KOBTR Condition end amount
MWSKZ VAT ID
KOEIN Currency
Although data sent in the segment E1EDP05 will first be read by the inbound process ing, it cannot be transferred to the applic ation. This leads to the error
VG201 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.
!--a11y-->
1.1.2.2.2.5.2.5 Document Header: Partner Info (Segment

E1EDKA1)
PARVW Partner function (such as sold-to party, ship-to Internal (2-character) code for the partner function
party,...) (such as ‚AG‘, ‚WE‘)
PARTN Partner number Internal number of the partner
LIFNR Vendor number at the customer Normally the identification number of the order
recipient at the sold-to party. Using this field a
conversion of external partner numbers into internal
partner numbers is also p ossible (see b elow).
NAME1 Name 1 The data sent in these fields serves to transfer

possibly different address information to the partner.
NAME2 Name 2
Missing data is transferred from the existing master
<.....> records.
<.....> Additional fields for partner information. For detailed

information s ee IDoc documentation on transac tion
WE60.
KNREF Customized description of the business partner

(plant, warehouse)
ILNNR 70 Character field
PFORT Location of the P.O. Box
SPRAS_ISO Language according to ISO code 639
TITLE Form of address
Only those partner functions can be processed in the field PARVW that have been defined in table TPAR (transaction VOPA). The transfer of a non-defined
partner function leads to error message VP450.
The following is valid for the determination of the partner number:
If the partner number is sent in the field PARTN, it will be transferred as such to the document. If the field PARTN remains empty and if instead a partner number
is sent in the field LIFNR, the external partner number (LIFNR) will be converted into the internal partner number (PARTN) via table EDPAR. The partner number
from the sender information of the control record (EDPAR-KUNNR), the partner function (EDPAR-PARVW) transferred in the segment, as well as the external
partner number (EDPAR-EXPNR) are used as keys for the conversion. If the conversion is not successful, the error message VG140 appears.
If data is not sent in PARTN or in LIFNR, the partner number is determined by processing the inferior segment E1EDKA3 (see below).
For the partner functions AG (Sold-to party), WE (Ship-to party), RE (Bill-to party) and RG (Payer) address information that has not been transferred is read from
the respective master data record.
!--a11y-->
1.1.2.2.2.1.2.1.6 Document Header: Partner Info Additional

Data (Segment E1EDKA3)
Superior segment: E1EDKA1
QUALP Partner identification Only indicator 001 - International Location Number

(ILN) is processed here.
STDPN 70 Character field Identification number
The segment can be used to determine a partner number from the transfer of the International Location Number (ILN).
Prerequisite
A valid p artner function has been sent in the superior segment E1EDKA1 and the fields PARTN and LIFNR of the segment E1EDKA1 have been transferred
empty . In this case the sys tem determines the partner number via the spec ifications from the view Control in the customer master record. The complete 13 digit
ILN must be then be transferred in STDPN. If the conversion could not be successfully carried out, it will lead to error message VG140.
!--a11y-->
1.1.2.2.2.5.2.7 Document Header: Reference Data (Segment

E1EDK02)
QUALF Reference document indicator For the identification of the subsequent document
number.
BELNR Document number Document number
POSNR Item Number No processing
DATUM Date Document date
UZEIT Time No processing
The following ind icators for r eference documents are pr ocessed:
001 Order number of customer
004 Quotation number of vendor
007 Collective number
050 Delivery order
066 External order number (in external order number assignment)
The document date (field DATUM) is only transferred for reference documents for the indicator 001.
!--a11y-->
1.1.2.2.2.5.2.8 Document Header: Terms of Delivery (Segment

E1EDK17)
QUALF Terms of delivery indicator Permitted values for the indicator are 001 for
Incoterms part 1 and 002 for Incoterms part 2
LKOND Delivery condition code Terms of delivery code
LKTEXT Delivery condition text Terms of delivery text
If the text field LKTEXT is filled in addition to the terms of delivery code for the indicator 001 (=Incoterms part 1) in this segment, then this text
will first be interpreted as Incoterms part 2. These entries will, however, be overwritten again as soon as the segment is sent with the
indicator 002. For this reason it is very important to make sure that the segment is sent in the correct sequence.
!--a11y-->
1.1.2.2.2.5.2.9 Document Header: Terms of Payment (Segment

E1EDK18)
Field Explanation
QUALF Terms of payment indicator
TAGE Number of days
PRZNT Percentage for terms of payment
ZTERM_TXT Text line
Although data for terms of payment sent in the segment E1EDK18 will first be read by the inbound processing, it cannot be transferred to the
application. This leads to the error VG202 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed
incorrectly.
!--a11y-->
1.1.2.2.2.5.2.10 Document Header: Additional Data (Segment

E1EDK35)
QUALZ Indicator for IDoc additional data Indicator for additional data transferred with CUSADD
CUSADD Data element for article number
CUSADD_BEZ 40 character field No processing
The following indicators for add itional d ata are processed at document level:
001 to 005 Customer groups 1 - 5
006 to 010 Condition groups 1 - 5
J01 to J05 AFS customer groups 6 – 7
!--a11y-->
1.1.2.2.2.4.2.12 Document Header: Payment Cards (Segment

E1EDK36)
Field Explanation
CCINS Card type
CCINS_BEZEI Description
CCNUM Card number
EXDATBI Date
CCNAME Name of cardholder
FAKWR Maximum amount
The segment E1EDK36 is not supported in the incoming order.
!--a11y-->
1.1.2.2.2.5.2.11 Document Header: Text Identification

(Segment E1EDKT1)
TDID Text ID Text identification key The permitted values are

dependent on the IMG settings for the respective
document category.
TSSPRAS Language key SAP language key of the texts
TSSPRAS_ISO Language according to ISO code 639 ISO language key
TDOBJECT Texts: Application object
TDOBNAME Text name
Segment E1EDKT2 must be sent for each text line corresponding to segment E1EDKT1. Remember that the processing of texts has a considerably negative
effect on the performance of the entire inbound processing.
!--a11y-->

Superior segment: E1EDKT1
TDLINE Text line Text line for the Text ID used under E1EDKT1. The
individual text line has a maximum of 70 c haracters.
For texts with multiple lines, the segment must be
repeated acc ordingly.
TDFORMAT Tag column The tag column contains format keys which define
the output form of the text or initiate c ontrol demands.
!--a11y-->
1.1.2.2.2.4.2.14 Document Header: MSO Header (Segment
E1J3AHO)
J_3AMSOFLG Multi-store order indicator The indicator controls whether the Mix ID should be
generated automatically for an MSO or if it was
already assigned in the inbound IDoc. If the indicator
is s et, there will be no automatic Mix ID generation.
This segment generally does not control if this is a multi-store order or not. Rather, this is determined from the existence of E1J3AIO-segments. When the segment
E1J3AHO is sent with the indicator, the Mix ID from segment E1J3P01, field J_3AMSOM is used for grouping. Remember that the proper assignment of these
Mix IDs is not checked. This means that the (external) assignment of the Mix IDs must keep to the rules for grouping. (Only those items can be grouped in one
Mix ID, for which the same combination of stores order the same combination of quantities and dimensions respectively for the same material.)
!--a11y-->
1.1.2.2.2.4.2.1 Document Item: General Data (Segment

E1J3P01)
POSEX Item Number Item number of the current document. It is used for
the unique identification of the item. Normally the item
number is copied from the customer order.
ACTION Action code that concerns the item. Not relevant for incoming orders
PSTYP Item Category Indicator for the item category. The (one-digit)
numeric indicator is converted in the sales item
category depending on the order type, using the
table EDPST. Note, that an entry in this field is
always overridden by the value in field PSTYV.
KZABS Indicator for the order acknowledgment requirement No processing
MENGE Quantity Ordered quantity of the item.

Note: The quantity that is relevant for the document
item is always taken from segment E1EDP20.
MENEE Unit of Measure ISO code of the unit of measure for the order quantity
BMNG2 Quantity in Price Unit of Measure No processing
PMENE Price Unit of Measure ISO code of the price unit of measure
ABFTZ Agreed Cumulative Quantity No processing
VPREI Price (net) Customer-expected net price
PEINH Price Unit Price Unit
NETWR Value of Item (net) Customer-expected net value
ANETW Absolute Net Value of the Item No processing
SKFBP Discountable amount No processing
NTGEW Net Weight No processing
GEWEI Weight Unit No processing
EINKZ Indicator: More than one schedule line for the item No processing
CURCY Currency Currency code
PREIS Gross price No processing
MATKL Material class No processing
UEPOS Superior item in bill of material structures Link to the related superior item number for bill of
material components. Note that the value must link to
a POSEX, ex isting in the IDoc.
GRKOR Delivery group (items are delivered together) No processing
EVERS Shipping Instruction No processing
BPUMN Denominator for the Conversion BPRME into BME No processing
BPUMZ Numerator for the Conversion BPRME into BME No processing
ABGRU Reason for item rejection Is transferred to document item.
ABGRT Descrip tion No processing
ANTLF Maximum number of permitted partial deliveries per Is transferred to document item.
item
FIXMG Delivery date and quantity fixed No processing
KZAZU Indicator: order combination Is transferred to document item.
J_3APOSNR Item Number Internal usage
J_3AMSOM Equal mix of products in a multi-store order The mix key is only then processed, if the flag
J_3AMSOFLG is set in segment E1J3AHO. It is
used for the grouping of store and/or distribution
centers that should be delivered.
J_3ABZUS Requirements grouping Dimension requirements for an item are grouped, if

this indicator is s et.
J_3ADEPM Department Is transferred to document item.
J_3ASPLIT AFS Split indicator Is transferred to document item.
J_3ASEAN Season indicator Is transferred to document item.
J_3ASIZE AFS grid value Is transferred to document item or schedule line
J_3ALNGR AFS Line group ID (schedule lines are delivered Is transferred to document item.
together)
J_4KRCAT Requirements Category Is transferred to document item.
J_4KSCAT Stock Category No processing
BRGEW Total Weight No processing
VOLUM Volume No processing
VOLEH Volume Unit No processing
J_3AVASIT VAS Item values ticketing/labeling (E), packing (V), No processing

special service (S)
J_3AEBTYP Order confirmation category No processing
J_3AMSOF AFS Multi-store order: counter for partner The counter for the number of stores that should be
delivered with this item will only be then processed if
segment E1J3AHO was sent with flag
J_3AMSOFLG. You must enter the total number of
stores per item.
PSTYV Item category sales document The field directly transfers the item category to the
document item. In contrast to field PSTYP no
conversion takes place. Note that the content of field
PSTYV overrides the value of field PSTYP and
sends it directly to the application.
EMPST Receiving point Is transferred to document item.
ABTNR Department number No processing
ABRVW Usage indicator No processing
WERKS Plant Is transferred to document item.
LPRIO Delivery priority No processing
LPRIO_BEZ Description No processing
ROUTE Route No processing
ROUTE_BEZ Description No processing
LGORT Storage location No processing
VSTEL Shipping point No processing
DELCO Agreed delivery time No processing
MATNR Material identification No processing

Note: The material identification and determination is
controlled by using segments E1J3AIM and/or
E1EDP19.
The document item segment E1J3P01 starts the transfer of data per item. Below the segment you find further item-related segments with detailed information for the
respective item. A prerequisite for correctly processing the segment is that the external item number in field POSEX is uniquely filled. If the field remains initial,
error message /AFS/IDO C 0 18 is displayed. In view of automatic order changes with the message type ORDCHG you must note that the external item
number is uniquely transferred to the created document. After the creation of the order, it is the unique identification and reference criterion of an item.
Bills of Material
For the processing of bills of materials in incoming orders, there are some special features. There are basically two ways of BOM processing:
In the IDoc, only the header material of a BOM is sent.

Both header and component materials are sent.
In both cases the BOM is exploded in the sales document, according to the settings in the IMG. Make sure when using item categories that the correct item
categories are transferred for both header and component items. An automatic item category determination only takes place if neither field PSTYP nor field PSTYV
are filled in segment E1J3P01. The sales document contains more items after the transfer of IDoc data than were sent in the IDoc. This has to do with the fact that
during the BOM explosion in individual components, new items are generated.
If both header and item materials are sent as mentioned in the second case, the relation between the two can be created using field UEPOS in segment
E1J3P01. Here, the value of the superior item always refers to the external item number (POSEX) of the header material. We strongly recommend that you send
related components and their respective header material as groups in the sequence of the individual E1J3P01 segments.
It is possible to send a material as an individual item without reference to a header material, even if it belongs to a BOM as component. In this case you must not
fill field UEPOS.
The processing of BOMs in multi-store orders per IDoc interface is currently not supported.
Processing of Item Segments
There can generally be one of the following situations during the processing of the item segments: A material of the following types is sent:
Standard (= non-AFS) Material

AFS material with dimensions
AFS material without dimensions (without a grid)
In the first case a 1:1 ratio exists between the sent E1J3P01 segment and the created document item. Normally the item contains a delivery schedule line.
In the second case an n:1 relation exists between the sent E1J3P01 segment and the created document item. The ordered dimensions are first grouped by
material numbers and combined to items with the same material number. Different dimensions of the same material (for the same recipient) are combined to one
item. The individual dimension is reflected in a schedule line on the document. All the relevant data is "copied" from the item header to the schedule line for the
identification of the individual purchase order items. That means that the external item number POSEX is not connected to the document item itself, but rather to
the schedule line at dimension level.
In the third case (no grid material) the processing is similar to the standard material without combining at item level.
Sort Criteria
The grouping of AFS materials and their dimensions is controlled by the following sort criteria:
Material number
Goods recip ient
Plant
MSO Mix key
Requested delivery date
Cancellation date
Department
Item Category
If you change one of the criteria, a new document item is created.
The values of field VPREI and NETWR are interpreted as customer-expected price or item value. The entries are assigned to the condition types EDI1/EDI2 or
JED1/JED2. The assignment to the AFS-specific conditions JED1 and JED2 only takes place, if the condition type is flagged as dimension-relevant in the IMG.
When transferring the values, remember that the transferred values are checked in the sales document against the amounts determined by pricing. If there are
differences, an incompletion log for the document is created according to the settings in the IMG. You can not overwrite the values that are determined by the
pricing with the entries of the IDoc. The transfer of conditions both at header and item level is not supported by the inbound processing.
!--a11y-->
1.1.2.2.2.1.2.2.1 Document Item: Date Segment (Segment

E1J3P03)
Superior segment: E1J3P01
following fields.
The following date indicators are processed at item level:
001 Purchase order date
006 AFS Cancellation Date
020 Fixed value date
The indicator J_3AQUALF is only us ed for the date indicators 003 and 00 6.
!--a11y-->
1.1.2.2.2.1.2.2.2 Document Item: Schedule Lines (Segment

E1EDP20)
Mandatory segment: YES
WMENG Schedule line quantity Ordered quantity
AMENG Previous schedule line quantity No processing
EDATU Date Schedule line date
EZEIT Time Delivery time
EDATU_OLD Date No processing
EZEIT_OLD IDoc: Time No processing
The meaning of the E1EDP20 segment reflects one of the AFS special features of incoming orders via the IDoc interface: The ordered quantities are transferred
solely from this segment for the AFS material as well as for standard material. Quantity entries from the E1J3P01 segment are not taken into account as far as this
is concerned. The only exception is the processing of multi-store orders: The ordered quantity of the respective dimension or of the material are calculated from the
quantity entries of the segment E1J3AIO.
!--a11y-->
1.1.2.2.2.1.2.2.3 Document Item: Schedule Lines Additional

Data (Segment E1J3P20)
Superior segment: E1EDP20
Field Explanation
J_3AABGRU Reason for rejection for quotations and orders
J_4KRCAT Requirements Category
J_4KSCAT Stock Category
J_3AETENR Schedule line
J_3AVASIT VAS item values: E labeling, V packing, S special service
The segment is not processed in the incoming order.
!--a11y-->
1.1.2.2.2.1.2.2.4 Document Item: Conditions (Segment

E1J3P05)
Field Explanation
ALCKZ Surcharge or discount indicator
KSCHL Condition type (coded)
KOTXT Condition description
BETRG Fixed surcharge / discount on item total gross amount
KPERC Condition percentage rate
KRATE Condition record per unit
UPRBS Price Unit
MEAUN Unit of measure
KOBTR Condition end amount
MENGE Quantity of the pricing scale (SPEC2000)
PREIS Price per unit of measure (SPEC2000)
MWSKZ VAT ID
KOEIN Currency
CURTP Currency type and valuation view
Although data sent in the segment E1EDP05 will first be read by the inbound process ing, it cannot be transferred to the applic ation. This
leads to the error VG201 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.
!--a11y-->
1.1.2.2.2.1.2.2.5 Document Item: Configuration Data (Segment

E1CUCFG)
Field Explanation
POSEX 6 Character field
CONFIG_ID 6 Character field
ROOT_ID 8 Character field
SCE CU: Only information for the configuration transferred by SCE
The segment E1CUCFG (including the subsegments E1CUINS, E1CUPRT, E1CUVAL and E1CUBLB) is not processed in the incoming order.
!--a11y-->
1.1.2.2.2.1.2.2.6 Document Item: Service Specifications Data

(Segment E1EDC01)
Field Explanation
SGTYP Service specifications segment type
ZLTYP Service specifications line category
LVALT Service specifications alternatives
ALTNO Alternative number for service s pecifications
ALREF Assignment number for service s pecifications
ZLART Service specifications line type
POSEX Line number
RANG Hierarchy level of the group
EXGRP Outline level
UEPOS Superior item in bill of material structures
MATKL Material class
MENGE Quantity
MENEE Unit of Measure
BMNG2 Quantity in Price Unit of Measure
PMENE Price Unit of Measure
BPUMN Denominator for the Conversion BPRME into BME
BPUMZ Numerator for the Conversion BPRME into BME
VPREI Price (net)
PEINH Price Unit
NETWR Value of Item (net)
ANETW Absolute Net Value of the Item
SKFBP Discountable amount
CURCY Currency
PREIS Gross price
ACTION Action code that concerns the item.
KZABS Indicator for the order acknowledgment requirement
UEBTO Overfulfillment tolerance
UEBTK Unlimited overfulfillment
LBNUM Description of the service type
AUSGB Output of the service type
FRPOS Lower limit
TOPOS Upper limit
KTXT1 Short text
KTXT2 Short text
PERNR Personnel number
LGART Wage type
STELL Job
ZWERT Total value totals segment
The segment E1EDC01 (including the sub segments E1EDC02, E1EDC03 , E1EDC04, E1EDC05, E1EDC06, E1EDC07, E1EDCA1, E1EDC19, E1EDC17,
E1EDC18, E1EDCT1 and E1EDCT2) is not processed in the incoming order.
!--a11y-->
1.1.2.2.2.1.2.2.7 Document Item: Terms of Delivery (Segment

E1EDP17)
QUALF Terms of delivery indicator Permitted values for the indicator are 001 for
Incoterms part 1 and 002 for Incoterms part 2
LPRIO Delivery priority No processing
If the text field LKTEXT is filled in addition to the terms of delivery code for the indicator 001 (=Incoterms part 1) in this segment, then this text
will first be interpreted as Incoterms part 2. These entries will, however, be overwritten again as soon as the segment is sent with the
indicator 002. For this reason it is very important to make sure that the segment is sent in the correct sequence.
The terms of delivery at item level do not belong to the sort / grouping criteria according to which AFS dimensions are combined to form
items. This means that different terms of delivery at dimension level might not be completely transferred to the document. The only possibility
of controlling different terms of delivery at dimension level for the same material is to transfer different ship-to parties or another grouping
criterion named in the notes on segment E1J3P01.
!--a11y-->
Document Item: Multi-Store Order (Segment E1J3AIO)

J_3APARVW Partner function Partner function of the ship-to party
J_3ASTORE MSO stores Partner number of the ship-to party
J_3ADICE Customer distribution center Identification number of the customer distribution center
J_3AWMENG Schedule line quantity Ordered quantity
J_3ABMENG Delivered quantity in sales unit No processing
J_3ADEPM Department Department number (is transferred to the document)
J_3ASTCU Customer store / distribution center number Identification of the store / the customer distribution center
at the customer
J_3ABSTNK Order number of customer Order number of customer
J_3AILNNR 70 Character field International Location Number of the store
J_3AUPDKZ Update Indicator No processing
With the segment E1J3AIO the nec ess ary data for the creation of MSO s is transferred to the document. Using the sp ecific ation of the partner function it is
controlled whether the store itself is the ship-to party or if the delivery first goes to a customer distribution center. If the store itself is the ship-to party, use the
partner function WE for the ship-to party. The partner number that was maintained in the system as the ship-to party is to be transferred in the field J_3ASTORE.
If this field is not filled, you can trigger a conversion of the partner number from the specifications for the International Location Number (J_3AILNNR) (see also
segment E1EDKA3).
The customer store number can be transferred in the field J_3ASTCU. If this number is maintained in the AFS additional data for the customer master, it will be
converted into a valid partner number. The original customer store number is then transferred to the document.
For further documentation of MSOs, please see the information in Multi-Store Orders.
The quantity (J_3AWMENG) transferred in this segment is assigned to the respective store as the ordered quantity. Take note that the quantity specification in
segment E1EDP20 is not included in this c ase.
The segment can occur multiply under an E1J3P01-segment, depending on the number of stores that order the product described under this item. All further
spec ifications in sub-segments are then valid for all stores resp ectively.
The system assigns a mix ID for a group of stores (exception: in segment E1J3AHO the indicator J_3AMSOFLG has been set). With the automatic assignment of
the mix ID, a numerical numerator is used. This means that a maximum of 999 mix IDs can be assigned. The stores are grouped according to the number of the
same combinations of stores that order the same combination of dimensions and quantities for the same date. The following graphic illustrates the logic for the
automatic generation of the mix IDs.
Example of Mix ID ass ignments in MSOs
!--a11y-->
1.1.2.2.2.1.2.2.9 Document Item: Object Identification (Segment

E1EDP19)
Superior segment: E1EDPA1
QUALF IDoc object identification (such as material number, Indicator for material identification in field IDTNR
customer, and so on)
IDTNR Material identification Material number
KTEXT Short text Material short text
MFRPN Manufacturer part number No processing
MFRNR Manufacturer number No processing
The following ind icators in the field Q UALF are process ed in the specified s equence:
002 internal material number
003 EAN/UPC number
001 Customer material number
See the note for segment E1J3AIM. The segment E1EDP19 should no longer be used for object identification because AFS specific data
cannot be transferred here.
!--a11y-->
1.1.2.2.2.1.2.2.10 Document Item: Object Identification

(Segment E1J3AIM)
J_3AOBIDQF Indicator for object identification Indicator for material identification in field J_3AIDTNR
J_3AIDTNR Material identification Material identification
J_3ASIZE AFS grid value Grid value / dimension for material
J_3AKTEXT Material short text Is transferred to the document
J_4KRCAT Requirements Category Is transferred to the document
J_4KSCAT Stock Category No processing
The following ind icators in the field J_3AOBIDQF are pr ocessed in the specified sequence:
003 EAN/UPC number
001 customer material number
Take note that with this segment the object identification can also be controlled via the standard segment E1EDP19. We recommend that you
always use E1J3AIM instead of E1EDP19.
If no material number is sent to indicator 002, a material determination procedure is triggered which first looks for a material number based on the specifications of
the EAN/UPC number (indicator 003). The AFS specific table J_3 AMEAN must be maintained for this via transaction J3A^ ( Logistics ® AFS Central Functions
® Material Master ® UPC/EAN Numbers ). An incorrect UPC/EAN number leads to error message 8J308.
The material determination according to IMG settings is triggered via the customer material number. If the internal material number is already sent in the IDoc or if
it was determined using the EAN/UPC number, then the customer material number is transferred as information to the document. No further check takes place.
The transfer of a grid value in J_3ASIZE is only necessary if, for example, it is not already determinable via the EAN/UPC number or customer material number.
The grid value must, however, always be sent in connection with the internal material number, in order to guarantee the correct setting of the document item or its
dimensions.
The additional check for eligibility of a transferred material number is carried out within the document creation. Similar to the dialog entry, error messages can
occur here that put the complete IDoc in the error status 51. This means that even if, for example, only one piece of material information could not be correctly
transferred to the document, the creation of the entire document will be terminated.
!--a11y-->
1.1.2.2.2.1.2.2.11 Document Item: Partner Info Additional Data

(Segment E1EDPA3)
Superior segment: E1EDPA1
QUALP IDoc partner identification (for example Only indicator 001 - International Location Number
Dun&Bradstreet number) (ILN) is processed here.
The segment can be used to determine a partner number from the transfer of the International Location Number (ILN).
The prerequisite is that a valid partner function has been sent in the superior segment E1EDPA1 and the fields PARTN and LIFNR of the segment E1EDPA1
have been transferred empty . In this case the sys tem determines the partner number via the spec ifications from the view Control in the customer master record.
The complete 13 digit ILN must be then be transferred in STDPN. If the conversion could not be successfully carried out, it will lead to error message VG140.
!--a11y-->
1.1.2.2.2.4.2.7 Document Item: Partner Information (Segment

E1EDPA1)
PARVW Partner function (such as sold-to party, ship-to party, Internal (2-character) code for the partner function
and so on) (such as ‚AG‘, ‚WE‘)
partner numbers is also possible.

NAME2 Name 2
<.....>
<.....>

(plant, warehouse)
Only the following partner functions are transferred at item level:
WE Goods recipient
RE Bill-to party
RG Payer
You can find further information under segment E1EDKA1.
!--a11y-->
1.1.2.2.2.1.2.2.13 Document Item: Reference Order Item

(Segment E1CUREF)
Field Explanation
POSEX 6 Character field
CONFIG_ID 6 Character field
INST_ID 8 Character field
The segment is not used in the incoming order.
!--a11y-->
1.1.2.2.2.1.2.2.14 Document Item: Reference Data (Segment

E1EDP02)
number.
BELNR Document number Reference document number
ZEILE Item Number Processing only for indicator 044 (purchase order of
the ship-to party)
BSARK Organization
IHREZ Your initial (from partner) Reference number of the customer
The following ind icators are pr ocessed:
044 Purchase order of ship-to party
052 Sequence number for delivery order
J30 internal use in ALE
!--a11y-->
1.1.2.2.2.1.2.2.15 Document Item: Taxes (Segment E1J3P04)

Field Explanation
MWSKZ VAT ID
MWSBT Sales tax amount
TXJCD Tax Jurisdiction Code
KTEXT Text field
Although data sent in the segment E1EDP04 will first be read by the inbound process ing, it cannot be transferred to the applic ation. This
leads to the error VG200 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed incorrectly.
!--a11y-->
1.1.2.2.2.1.2.2.16 Document Item: Totals Segment (Segment

E1EDS01)
Field Explanation
SUMID Indicator: totals segment for shipping notification
SUMME Total value totals segment
SUNIT Unit total value totals segment shipping notification
WAERQ Currency
The totals segment E1EDS01 is not processed in the incoming order.
!--a11y-->
1.1.2.2.2.4.2.8 Document Item: Texts (Segment E1EDPT2)
Superior segment: E1EDPT1
TDLINE Text line Text line for the Text ID used under E1EDPT1. The
!--a11y-->
1.1.2.2.2.1.2.2.18 Document Item: Text Identification (Segment

E1EDPT1)
TDID Text ID Text identification key The permitted values are

dependent on the IMG settings for the respective
document category.
Segment E1EDPT2 must be sent for each text line corresponding to segment E1EDPT1. Remember that the processing of texts has a considerably negative
effect on the performance of the entire inbound processing. The correct processing of texts at item level requires that the external item number be transferred
uniquely in the field POSEX (segment E1J3P01) for the entire document.
!--a11y-->
1.1.2.2.2.1.2.2.19 Document Item: Additionals (Segment

E1ADDI1)
Field Explanation
ADDIMATNR Material number for additional
ADDINUMBER Number of additionals
ADDIVKME Sales unit of the material
ADDIFM Procedure for additionals
ADDIFM_TXT Additionals: Descrip tion for the procedure for additionals
ADDIKLART Class type dis played when editing additionals
ADDIKLART_TXT Descrip tion of class type
ADDICLASS Class with additionals ass igned to its elements
ADDICLASS_TXT Keywords
ADDIIDOC Indicator which refers to separate additionals IDoc
The segment is not used in the incoming order.
!--a11y-->
1.1.2.2.2.1.2.2.20 Document Item: Shipping Unit Header
(Segment E1EDL37)
Field Explanation
EXIDV External shipping unit ID
TARAG Tare weight of shipping unit
GWEIT Weight unit tare
BRGEW Total weight of shipping unit
NTGEW Loading weight of shipping unit
MAGEW Maximum allowed loading weight of the shipping unit
GWEIM Weight Unit
BTVOL Total volume of shipping unit
NTVOL Loading volume of shipping unit
MAVOL Permitted loading volume of shipping unit
VOLEM Volume Unit
TAVOL Tare volume of shipping unit
VOLET Volume unit tare
VEGR2 Shipping unit group 2 (freely definable)
VHILM Shipping material
LAENG Length
BREIT Width
HOEHE Height
MEABM Unit of dimension for length/width/height
INHALT Description of shipping unit content
VHART Shipping material type
MAGRV Material group: shipping materials
LADLG Length of loading platform in length of loading platform measurement units
LADEH Unit of measure to measure the length of the loading platform
FARZT Travel time
FAREH Unit of travel time
ENTFE Distance traveled
EHENT Unit of distance
VELTP Shipping unit category
EXIDV2 2. External identification of shipping unit
LANDT Country providing means of transport
LANDF Driver’s nationality
NAMEF Driver's name
NAMBE Passenger's name
VHILM_KU Customer shipping material
VEBEZ Description of shipping unit
SMGKN SMG identification for material tag
KDMAT35 Customer shipping material
SORTL Sort field
ERNAM Name of person who created object
GEWFX Weight and volume fixed
ERLKZ Status
The segment E1EDL37 (including the subsegments E1EDL39, E1EDL38 and E1EDL44) is not processed in the incoming order.
!--a11y-->
1.1.2.2.2.4.2.3 Document Item: VAS Ticketing/Labeling

(Segment E1J3AIT)
J_3ASTORE MSO stores The store for which there is ticketing/labeling.
J_3ATLTYP VAS Ticketing/label type Is transferred to the document
J_3ATLMAT VAS Ticketing/labeling material Is transferred to the document
J_3ACHARC VAS charge code Is transferred to the document
J_3AFIELD1 VAS User-Defined Field 1 Is transferred to the document
J_3AVASPQ Quantity Is transferred to the document
J_3AVASPO VAS generated sub-item number No processing
J_3AVASETE VAS Generated Sub-Schedule Line Number No processing
The segment is connected to the item segment E1J3P01. The data sent here is transferred to the document according to the created item. Independent of the data
sent here, an automatic determination of VAS data can also be triggered during the creation of a sales document.
!--a11y-->
1.1.2.2.2.4.2.4 Document Item: VAS Ticketing/Labeling Text

(Segment E1J3AIX)
Superior segment: E1J3AIT
J_3ATLTXT Additional text for ticketing/labeling Is transferred to VAS item
J_3ATLORD Order level Indicates from where in the document the entries for
the text information should be assigned in order to be
printed on the label.
J_3ATLITEM Item level
J_3ATLSIZE Dimension level
Corresponding to the previous E1J3AIX segment, additional texts can be transferred here for ticketing/labeling.
!--a11y-->
1.1.2.2.2.4.2.6 Document Item: VAS Special Services (Segment

E1J3AIS)
J_3ASTORE MSO stores The store for which there is special service
information.
J_3ASSTYP VAS Special Services: Category Is transferred to the document
J_3ASSMAT VAS Special Services: Material
J_3ACHARC VAS charge code
J_3AFIELD1 VAS User-Defined Field 1
J_3AVASPQ Quantity Internal usage
!--a11y-->
1.1.2.2.2.4.2.5 Document Item: VAS Packing (Segment

E1J3AIP)
J_3ASTORE MSO stores The store for which there is packing information.
J_3APTYP VAS packing type Is transferred to the document
J_3APMAT VAS packing material
J_3AINCREM VAS Packing Increment
J_3AMIXIND VAS Packing Mix Indicator
!--a11y-->
1.1.2.2.2.1.2.2.25 Document Item: Terms of Payment (Segment

E1EDP18)
Field Explanation
QUALF Terms of payment indicator
TAGE Number of days
PRZNT Percentage for terms of payment
ZTERM_TXT Text line
Although data for terms of payment sent in the segment E1EDP18 will first be read by the inbound processing, it cannot be transferred to the
application. This leads to the error VG202 in the first processing of an IDoc. The segment is ignored if an IDoc is repeatedly processed
incorrectly.
!--a11y-->
1.1.2.2.2.1.2.2.26 Document Item: Additional Data (Segment
E1EDP35)
QUALZ Indicator for additional data Indicator for additional data transferred with CUSADD
CUSADD Additional data
CUSADD_BEZ Text for additional data No processing
The following indicators for add itional d ata are processed at item level:
001-005 Customer groups 1 – 5
006-010 Condition groups 1 – 5
The customer groups and condition groups at item level do not belong to the sort / grouping criteria according to which AFS dimensions are
combined to form items. This means that different customer / condition groups at dimension level might not be completely transferred to the
document. The only possibility of controlling different customer/condition groups at dimension level for the same material is to transfer different
ship-to parties or another grouping criterion mentioned in the notes on segment E1J3P01.
!--a11y-->
1.1.2.2.2.1.3 User Exits in the Incoming Order

A series of customer enhancements are available in the incoming order via the IDoc interface. To activate the customer enhancement, first create a project. The
customer enhancements of the inbound processing are summarized in the SAP enhancement J_3 AEDS0.
!--a11y-->
1.1.2.2.2.2 Contract
Use
Inbound processing for contracts is implemented using the IDoc interface for the incoming order. Basically, there is no difference between the data processing and
the incoming order process. A sales document type for the sales document category G (= contract) is to be transferred in the IDoc as the order type (see
Customizing).
Features
The automatic referencing of contracts for contract release orders is controlled using two customer enhancements (EXIT_SAPMJ3AS_601 and
EXIT_SAPMJ3AS_701) (for more information, see the documentation for the appropriate function modules).
AFS Restrictions
AFS does not support the transfer of additional contract data (table VEDA) using the IDoc interface.
!--a11y-->
1.1.2.2.2.2.1 Customizing: Contract

Contracts mus t be flagged in Customizing as a sales document type for the document category contracts (G ). Choose in Customizing Sales and D istrib ution ®
Sales ® Sales Documents ® Sales Document Header ® Define Sales Document Types .
!--a11y-->
1.1.2.2.2.2.2 Technical Information: Contract

The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Note that contract handling is
almost identical to the method used when handling incoming orders. This section therefore only details the segments and fields that are used differently than in
incoming orders.
!--a11y-->
(Segment E1EDK14)
QUALF Organization Indicator Describes the use of the data sent in field ORGID
in the field ORGID.
ORGID Organization Indicator See field QUALF.
006 Division
010 Sales Group
012 Order Type
016 Sales Office
J01 Department
For the creation of contracts the order type flagged as sales document category contract (G) in Customizing must be transferred with the indicator 012. If the order
type is not sent directly with the IDoc, it can also be changed using the customer enhancement exit_saplj4as_002. The default setting for the purchase order
type (indicator 019) is also DFUE for contracts. Please note that the valid purchase order types are to be maintained for each order type in Customizing. If this
assignment does not exist, the error message 00058 is displayed.
!--a11y-->

E1J3K03)
following fields.
UZEIT Time Is transferred to the document
The following date indicators are relevant for contracts:
Please note that the AFS cancellation date for contracts is interpreted as the validity end date.
The validity start date (014) and the validity end date (006) are checked by the inbound function. This means that if one of these dates is in the past (the reference
date is the current system date), the processing terminates with the error mess age V1437. However, this error only leads to termination in the first processing of
an IDoc (IDoc is set to status 51). If the incorrect IDoc is processed a second time (for example, with transaction BD87 or report RBDMANI2), the incorrect date
only leads to a warning message which does not interfere with the update of the data.
If the end date is earlier than the start date, the error message V1444 app ears. If this occurs, please c orrect the date entries.
!--a11y-->
1.1.2.2.2.3 Quotation
Requests for quotations can be sent to the vendors via the IDoc interface. The general conditions are sent in the IDoc so that the vendor can specifically create a
quotation.
!--a11y-->
1.1.2.2.2.3.1 Technical Inf

Information:
ormation: Quotation
The IDoc outbound processing for quotations is essentially identical to that of the
order c onfirmatio
onfirmation
n The following exceptions and special features are valid for quotations:
Segment E1EDK02 Document Header Reference Data
Field Shor t text Explanation
Q UALF Referenc e doc ument indic ator For the identific ation of the s ub s equent doc ument
number.
BELNR D oc ument numb er D oc ument numb er
PO SNR Item Numb er Item numb er of the doc ument
D ATUM D ate D oc ument date
UZEIT Time Time of the doc ument
The indicator 004 is used for the quotation number.
This also applies for the item segment E1EDP02.
Segment E1EDP19 Document Item Object Identification
Field Explanation
Q UALF ID oc ob jec t identific ation (s uc h as material numb er, c us tomer, and s o on)
ID TNR Material identific ation
KTEXT Short tex t
MFRPN Manufac turer p art numb er
MFRNR Manufac turer numb er
The segment is not used in the outbound quotation. The object identification is sent with the segment E1J3AIM.
Document Item General Data
PO SEX Item Numb er Item numb er from a c us tomer order.
ACTION
ACTION Action code
code that concerns the item.
item. 00 0 - item unchanged
001 - item changed
003 - item deleted
PSTYP Item Category O ne-digit numeric al indic ator for the item c ategory .
The indicator is converted into the sales item
table EDPST.
KZABS Indic ator for the order ac k nowledgment requirement N/A
MENG E Q uantity O rdered quantity of the item.

Please note: for AFS materials with dimensions, the
quantity ordered is per dimension.
MENEE Unit of Meas ure ISO c ode of the unit of meas ure for the order quantity
BMNG 2 Q uantity in Pric e Unit of Meas ure N/A
PMENE Pric e Unit of Meas ure ISO c ode of the p ric e unit of meas ure
ABFTZ Agreed Cumulative

Cumulative Quantity
Quantity N/A
VPREI Pric e (net) Pric e p er p ric e unit. Pleas e note: for AFS materials
with dimensions,
dimensions, the p rice here is per dimension.
PEINH Pric e Unit Pric e Unit
NETWR Value of Item (net) Net v alue. For AFS materials with dimens ions , the
value here is p er dimension.
dimension.
ANETW
ANETW Absolute Net Value of
of the
the Item
Item N/A
SKFBP D is c ountab le amount N/A
NTG EW Net Weight Is c op ied from the doc ument.
G EWEI Weight Unit ISO c ode of the weight unit
EINKZ Indic ator: More than one s c hedule line for the item X, if more than one s c hedule line ex is ts for the item.
CURCY Currenc y ISO c ode for c urrenc y
PREIS G ros s p ric e N/A
MATKL Material c las s Is c op ied from the doc ument.
UEPO S Sup erior item in b ill of material s truc tures Is c op ied from the doc ument.
G RKO R D eliv ery group (items are deliv ered together) Is c op ied from the doc ument.
EVERS Ship p ing Ins truc tion N/A
BPUMN D enominator for the c onv ers ion BPRME into BME N/A
BPUMZ Numerator for the c onv ers ion BPRME into BME N/A
ABGRU Reason
Reason for
for item rejection
rejection Is copied from
from document item or
or schedule line.
ABGRT Descrip tio

tion
n Text for
for reason
reason for
for rejectio
rejection
n ABGRU
ANTLF Maximum number of permitted partial

partial deliveries per Is copied from the document.
item
FIXMG D eliv ery date and quantity fix ed Is c op ied from the doc ument.
KZAZU Indic ator: order c omb ination N/A
J_ 3 APO SNR Item Numb er Sc hedule line numb er of dimens ion
J_ 3 AMSO M Equal mix of p roduc ts in a multi-s tore order Mix ID for multi-s tore order.
J_ 3 ABZUS Requirements group ing Is c op ied from the doc ument.
J_ 3 AD EPM D ep artment Is c op ied from the doc ument.
J_ 3 ASPLIT AFS Sp lit indic ator Is c op ied from the doc ument.
J_ 3 ASEAN Seas on indic ator Is c op ied from the doc ument.
J_ 3 ASIZE AFS G rid Value N/A
J_ 3 ALNG R AFS Line group -ID (s c hedule lines are deliv ered Is copied from the document.
together)
J_ 4KRCAT Requirements Category N/A
J_ 4KSCAT Stoc k Category N/A
BRG EW Total Weight Is c op ied from the doc ument item
VO LUM Volume N/A
VO LEH Volume Unit N/A
J_ 3 AVASIT VAS Item v alues tic k eting/lab eling (E), p ac k ing (V), Is copied from the document.
special service (S)
J_ 3 AEBTYP O rder c onfirmation c ategory N/A
J_ 3 AMSO F AFS Multi-s tore order c ounter for p artner N/A
PSTYV Item c ategory s ales doc ument N/A
EMPST Rec eiv ing p oint Is c op ied from the doc ument item
ABTNR Department number

number N/A
ABRVW Usage indicator

indicator N/A
WERKS Plant N/A
LPRIO D eliv ery p riority N/A
LPRIO _ BEZ D es c rip tion N/A
RO UTE Route N/A
RO UTE_ BEZ D es c rip tion N/A
LG O RT Storage loc ation N/A
VSTEL Ship p ing p oint N/A
D ELCO Agreed deliv ery time N/A
MATNR Material identific ation N/A
In contrast to the order confirmation, the dimension values and category values are not transferred in segment E1J3P01 (J_3ASIZE, J_4KRCAT, J_4KSCAT) in the
inbound quotat
quotation.
ion.
!--a11y-->
1.1.2.2.2.4 Order Change
Features
The same special features and restrictions that apply to the incoming sales order processing via EDI apply here. In addition, please note that AFS does not
PUBLIC Page
Page 42 of 77
77
support an order change via IDoc for multi-store orders (MSO) and for value-added service (VAS) data.
AFS Restrictions
A change in MSOs and in orders
orders with VAS data
data via IDoc is not supported.
supported.
Conditions in the incoming sales order cannot be changed at the header level, item level or dimension level. Please also read the documentation of the
segments E1EDK04, E1EDK05,
E1EDK05, E1E
E1EDP04,
DP04, E1E
E1EDP05.
DP05.
AFS does not
not support changes to the material
material number or
or the dimension
dimension of
of an already
already existing stock keeping unit (SKU).
(SKU). SKUs
SKUs can only be flagged with
with one
deletion indicator.
AFS does not
not support adding
adding individual components
components by means of an order
order change IDoc
IDoc (ORDCHG) to a bill of materia
materiall (BOM) that has already
already been
exploded in a s ales document.
!--a11y-->
1.1.2.2.2.4.1 Cus
Customizing:
tomizing: Order Change
Basically the same settings are valid as fo
forr the incoming orders.
orders.
A partner profile
profile and inbound
inbound parameters
parameters for
for the output
output type
type O RDCHG must be maintained (transactio
(transaction
n WE20)
WE20) for the
the partner.
partner.
!--a11y-->
1.1.2.2.2.4.2 Technical Inf

Information:
ormation: Order Change
The following document provides descriptions of the functionality of each field and explains how the essential elements are used. Please note that the processing
for order change is for the most part identical to the processing for incoming orders. This section therefore only details the segments and fields that are used
differently than in incoming orders.
!--a11y-->
1.1.2.2.2.4.2.1 Document Item: General Data (Segment

E1J3P01)
PO SEX Item Numb er Item numb er of the c urrent doc ument. It is us ed for
the unique identification of the item. Normally the item
number is copied from the customer order.
ACTION
ACTION Action code
code that concerns the item.
item. 00 1 – item was added
added
002 = item was changed
003 = item was deleted
PSTYP Item Category See information on inc oming order
<...>
<...>
MATNR Material identific ation
The entry of the action code is decisive for processing the data for the order change. Therefore you must fill this field. If none of the three possible action codes
(001, 00 2 or 003) is s ent, the document will not
not be changed at item level.
If you want to change or delete an item, the entry of the external item number (POSEX) is mandatory. It is used for the unique identification of the item that should
be c hanged
hanged..
The same rules are valid for combining dimensions under items as are described for the incoming orders. That means that dimensions that should be newly
created can be grouped in an already existing item if the partners at item level are identical (for partner function processing see the note for segment E1EDPA1).
Changing a material number or dimension for an already existing item is not supported. If you want to change this data, you must flag the corresponding item or
schedule line with a deletion indicator and then you have to create it once more. It is also not possible to add individual components to a bill of material that has
already been exp lode
loded
d in a sales document.
If the action code 003 is sent to delete a dimension, the corresponding entry is not physically deleted from the document table, but flagged with the reason for
rejection 00. The schedule line remains in the document, but is not active. You cannot reset this deletion flag via IDoc. If you want to reactivate a schedule line,
you can only do so using the dialog transactions for changing an order.
Changes in an already rejected dimension result in the error message /AFS/IDOC 019 in the inbound processing. Before you further process the IDoc you must
manually reset the reason for rejection for the corresponding dimension.
!--a11y-->
PUBLIC Page
Page 43 of 77
77
1.1.2.2.2.4.2.2 Document Item: Multi-Store Order (Segment
E1J3AIO)
Field Explanation
J_3APARVW Partner function
J_3ASTORE MSO stores
J_3ADICE Customer distribution center
J_3AWMENG Schedule line quantity
J_3ABMENG Delivered quantity in sales unit
J_3ADEPM Department
J_3ASTCU Customer store / distribution center number
J_3ABSTNK Order number of customer
J_3AILNNR 70 Character field
J_3AUPDKZ Update Indicator
This segment is not supported during the order change.
!--a11y-->
1.1.2.2.2.4.2.3 Document Item: VAS Ticketing/Labeling

(Segment E1J3AIT)
Field Explanation
J_3ATLTYP VAS Ticketing/label type
J_3ATLMAT VAS Ticketing/labeling material
J_3AVASPQ Quantity
J_3AVASPO VAS generated sub-item number
J_3AVASETE VAS Generated Sub-Schedule Line Number
!--a11y-->
1.1.2.2.2.4.2.4 Document Item: VAS Ticketing/Labeling Text

(Segment E1J3AIX)
Superior segment: E1J3AIT
Field Explanation
J_3ATLTXT Additional text for ticketing/labeling
J_3ATLORD Order level
!--a11y-->
1.1.2.2.2.4.2.5 Document Item: VAS Packing (Segment

E1J3AIP)
Superior segment: E1J3AP01
Field Explanation
J_3APTYP VAS packing type
J_3AVASPQ Quantity
!--a11y-->
1.1.2.2.2.4.2.6 Document Item: VAS Special Services (Segment

E1J3AIS)
Field Explanation
J_3ASSTYP VAS Special Services: Category
J_3AVASPQ Quantity
!--a11y-->
1.1.2.2.2.4.2.7 Document Item: Partner Information (Segment

E1EDPA1)
PARVW Partner function (such as sold-to party, ship-to Internal (2-character) code for the partner function
party,...) (such as ‚AG‘, ‚WE‘)
partner numbers is also possible.

NAME2 Name 2
<.....>
<.....>

(plant, warehouse)
In order changes per IDoc, the partner functions AG, RE, RG, and SB cannot be changed (this is also valid for the addition of new items
and/or dimensions. However, possible partners must be transferred at item level in this segment when you change an item because they
are considered an additional identification criterion of an item.
!--a11y-->
1.1.2.2.2.4.2.8 Document Item: Texts (Segment E1EDPT2)

Superior segment: E1EDPT1
TDLINE Text line Text line for the Text ID used under E1EDPT1. The
To change already existing texts, please note that all of the texts lines must always be transferred. It is not possible to only change individual
lines of a text. If the text segments are sent to an already existing Text ID, a text that possibly already exists will be overwritten.
!--a11y-->
(Segment E1EDK14)
QUALF Organization indicator Describes the use of the data sent in field ORGID
in the field ORGID.
006 Division
010 Sales Group
012 Order Type
016 Sales Office
J01 Department
Please read the sections on the incoming order.
Sales area data and order type do not necessarily need to be sent in the order change IDoc. Rather, this data is transferred from the existing document after the
determination of the order numb er.
!--a11y-->
1.1.2.2.2.4.2.10 Document Header: Partner Information

(Segment E1EDKA1)
Field Explanation
PARVW Partner function (such as sold-to party, ship-to party,...)
PARTN Partner number
LIFNR Vendor number at the customer
NAME1 Name 1
NAME2 Name 2
<.....> Additional fields for partner information. For detailed information see IDoc
documentation on transac tion WE60.
KNREF Customized description of the business partner (plant, warehouse)
Changing the partner at header level is not supported in order changes.
!--a11y-->

E1EDK02)
number.
POSNR Item Number No processing
DATUM Date No processing
The following ind icators for r eference documents are pr ocessed:
002 Order number of vendor
This segment is extremely important for the processing of the order change. The sales document to be changed in the system is identified via the entry of
reference document numbers. There are two possibilities:
Identification via the customer purchase order number
This option requires that the customer purchase order number exists once in the system under the respective partner number of the sold-to party. A
customer order number that exists more than once leads to error message /AFS/IDO C 0 06 in the inbound processing. An invalid customer order
number leads to error mess age VG151.
Identification via the order number
As an alternative to the customer order number, the order number stored in the sys tem can also be used for the identification of the document. If this
order number cannot be determined, you will see the error message /AFS/IDO C 0 14.
!--a11y-->
1.1.2.2.2.4.2.12 Document Header: Payment Cards (Segment

E1EDK36)
Field Explanation
CCINS Card type
CCINS_BEZEI Description
CCNUM Card number
EXDATBI Date
CCNAME Name of cardholder
FAKWR Maximum amount
!--a11y-->
1.1.2.2.2.4.2.13 Document Header: Texts (Segments

E1EDKT2)
Superior segment: E1EDKT1
To change already existing texts, please note that all of the texts lines must always be transferred. It is not possib le to only change
individual lines of a text. If the text segments are sent to an already existing Text ID, a text that possibly already exists will be overwritten.
!--a11y-->
1.1.2.2.2.4.2.14 Document Header: MSO Header (Segment

E1J3AHO)
Field Explanation
J_3AMSOFLG Multi-store order indicator
!--a11y-->
1.1.2.2.2.4.2.15 User Exits in the Incoming Order Change

A series of customer enhancements are available in the incoming order change via the IDoc interface. To activate the customer enhancement, first create a
project. The customer enhancements of the inbound processing are summarized in the SAP enhancement J_3AEDS0.
!--a11y-->

All the dimensions of an AFS material (= schedule lines of the sales document) are considered items in the outbound processing of the order confirmation. This
means that for each dimension there is one item segment E1J3P01 with corresponding subsegments.
!--a11y-->
1.1.2.2.2.5.1 General Data for the Order Confirmation (Segment

E1J3P01)
POSEX Item Number Item number from a customer order.
ACTION Action code that concerns the item. 00 0 - item unchanged

001 - item changed
003 - item deleted
PSTYP Item Category One-digit numerical indicator for the item category.
The indicator is converted into the sales item
table EDPST.
KZABS Indicator for the order acknowledgment requirement N/A
MENGE Quantity Ordered quantity of the item.

For AFS materials with dimensions, the ordered
quantity here is per dimension.
MENEE Unit of Measure ISO code of the unit of measure for the order quantity
BMNG2 Quantity in Price Unit of Measure N/A
PMENE Price Unit of Measure ISO code of the price unit of measure
ABFTZ Agreed Cumulative Quantity N/A
VPREI Price (net) Price per price unit. For AFS materials with
dimensions, the pric e here is p er dimension.
PEINH Price Unit Price Unit
NETWR Value of Item (net) Net value. For AFS materials with dimensions, the
value here is p er dimension.
ANETW Absolute Net Value of the Item N/A
SKFBP Discountable amount N/A
NTGEW Net Weight - is copied from the document-
GEWEI Weight Unit ISO code of the weight unit
EINKZ Indicator: More than one schedule line for the item X, if more than one schedule line exists for the item.
CURCY Currency ISO code for currency
PREIS Gross price N/A
MATKL Material class - is copied from the document-
UEPOS Superior item in bill of material structures - is copied from the document-
GRKOR Delivery group (items are delivered together) - is copied from the document-
EVERS Shipping Instruction N/A
BPUMN Denominator for the Conversion BPRME into BME N/A
BPUMZ Numerator for the Conversion BPRME into BME N/A
ABGRU Reason for item rejection Is copied from document item or schedule line.
ABGRT Descrip tion Text for reason for rejection ABGRU
ANTLF Maximum number of permitted partial deliveries per - is copied from the document-
item
FIXMG Delivery date and quantity fixed - is copied from the document-
KZAZU Indicator: order combination N/A
J_3APOSNR Item Number Schedule line number of dimension
J_3AMSOM Equal mix of products in a multi-store order Mix key for multi-store order.
J_3ABZUS Requirements grouping - is copied from the document-
J_3ADEPM Department - is copied from the document-
J_3ASPLIT AFS Split indicator - is copied from the document-
J_3ASEAN Season indicator - is copied from the document-
J_3ASIZE AFS Grid Value - is copied from the document-
J_3ALNGR AFS Line group-ID (schedule lines are delivered - is copied from the document-
together)
J_4KRCAT Requirements Category - is copied from the document-
J_4KSCAT Stock Category The stock category is converted from the

requirements category
BRGEW Total Weight Is copied from the document item
VOLUM Volume N/A
VOLEH Volume Unit N/A
J_3AVASIT VAS Item values ticketing/labeling (E), packing (V), - is copied from the document-
special service (S)
J_3AEBTYP Order confirmation category N/A
J_3AMSOF AFS Multi-store order counter for partner N/A
PSTYV Item category sales document N/A
EMPST Receiving point Is copied from the document item
ABTNR Department number N/A
ABRVW Usage indicator N/A
WERKS Plant N/A
LPRIO Delivery priority N/A
LPRIO_BEZ Description N/A
ROUTE Route N/A
ROUTE_BEZ Description N/A
LGORT Storage location N/A
VSTEL Shipping point N/A
DELCO Agreed delivery time N/A
MATNR Material identification N/A
The output sequence of E1J3P01 segments depends on the sorting within the sales document (item number + schedule line number) and not on the sequence of
the order receipt according to the external item number. Therefore, due to the internal sort and grouping logic of the inbound processing, an outbound IDoc can
have a different sequence of items or schedule lines than the corresponding inbound document.
!--a11y-->
1.1.2.2.2.5.1.1 Multi-Store Order (Segment E1J3AIO)
J_3APARVW Partner function WE if the store is the ship-to party,

JM if a customer distribution center is the ship-to
party
J_3ASTORE MSO stores Partner number of the ship-to party
J_3ADICE Customer distribution center Identification number of the customer distribution

center
J_3AWMENG Schedule line quantity Ordered quantity
J_3ABMENG Delivered quantity in sales unit Confirmed quantity
J_3ADEPM Department Department number
J_3ASTCU Customer store / distribution center number Identification of the store / the customer distribution
center at the customer
J_3ABSTNK Order number of customer Order number of customer
J_3AILNNR 70 Character field International Location Number of the store
J_3AUPDKZ Update Indicator N/A
The segment is used (only in MSOs) for every store within a Mix ID. It can occur multiply under an E1J3P01-segment, depending on the number of stores that
have ordered the product described under this item. All further specifications in s ub-segments are then valid for all stores resp ectively.
!--a11y-->
1.1.2.2.2.5.1.2 VAS Ticketing/Labeling (Segment E1J3AIT)

J_3ASTORE MSO store The store for which there is ticketing/labeling.
J_3ATLTYP VAS Ticketing/label type Is copied from the document.
J_3ATLMAT VAS Ticketing/labeling material Is copied from the document.
J_3ACHARC VAS charge code Is copied from the document.
J_3AFIELD1 VAS User-Defined Field 1 Is copied from the document.
J_3AVASPQ Quantity Is copied from the document.
J_3AUPDKZ Update Indicator N/A
J_3AVASPO VAS generated sub-item number Internal usage
J_3AVASETE VAS Generated Sub-Schedule Line Number Internal usage
!--a11y-->
1.1.2.2.2.5.1.3 VAS Ticketing/Labeling Text (Segment

E1J3AIX)
J_3ATLTXT Additional text for ticketing/labeling Is copied from the document.
J_3ATLORD Order level Is copied from the document.
J_3AUPDKZ Update Indicator Internal usage
!--a11y-->
1.1.2.2.2.5.1.4 VAS Packing (Segment E1J3AIP)

J_3ASTORE MSO store The store for which there is packing information.
J_3APTYP VAS packing type Is copied from the document.
!--a11y-->
1.1.2.2.2.5.1.5 VAS Special Services (Segment E1J3AIS)

J_3ASTORE MSO store The store for which there is special service
information.
J_3ASSTYP VAS Special Services: Category Is copied from the document.
!--a11y-->
1.1.2.2.2.5.1.6 Object Identification (Segment E1J3AIM)

J_3AOBIDQF Indicator for object identification Indicator for material identification in field J_3AIDTNR
J_3AIDTNR Material identification Material identification
J_3ASIZE AFS grid value Grid value / dimension for material
J_3AKTEXT Material short text Is copied from the document.
J_4KRCAT Requirements Category Is copied from the document.
J_4KSCAT Stock Category The stock category is converted from the

requirements category.
The following ind icators in the field J_3AOBIDQF are pr ocessed in the specified sequence:
003 EAN/UPC number
007 Material entered (for product substitution)
008 Pricing reference material
!--a11y-->
1.1.2.2.2.5.1.7 Reference Data (Segment E1EDP02)
number.
BELNR Document number Reference document number
ZEILE Item Number Reference item number
UZEIT Time N/A
BSARK Organization Customer purchase order type
IHREZ Your initial (from partner) Reference number of the customer
The following ind icators are pr ocessed:
001 Customer purchase order

If the purchase order number does not exist at item level, it is transferred from
the document header.
002 Order
003 Quotation request (from document flow)
004 Quotation (from document flow)
006 Contract (from document flow)
044 Purchase order of ship-to party
J30 Internal use in ALE
!--a11y-->
1.1.2.2.2.5.1.8 Date Segment (Segment E1J3P03)

following fields.
DATUM Date - is copied from the document-
UZEIT Time - is copied from the document-
The following date indicators are processed at item level:
001 Purchase order date of the sold-to party
019 Entry date of the item
020 Fixed value date
021 Billing date
022 Date of services rendered
025 Purchase order date of ship-to party
!--a11y-->
1.1.2.2.2.5.1.9 Taxes (Segment E1J3P04)

MWSKZ VAT ID Is copied from the item conditions
MSATZ Value-added tax Is copied from the item conditions
MWSBT VAT amount Is copied from the item conditions
TXJCD Tax Jurisdiction Code N/A
KTEXT Text field N/A
!--a11y-->
1.1.2.2.2.5.1.10 Conditions (Segment E1J3P05)

ALCKZ Surcharge or discount indicator + = Surcharge

- = Discount
KSCHL Condition type (coded) Is copied from the item conditions
KOTXT Condition description Is copied from the item conditions
BETRG Fixed surcharge / discount on item: total gross Is copied from the item conditions
amount
KPERC Condition percentage rate Is copied from the item conditions
KRATE Condition record per unit Is copied from the item conditions
UPRBS Price Unit Is copied from the item conditions
MEAUN Unit of measure Is copied from the item conditions
KOBTR Condition end amount N/A
MENGE Quantity of the pricing scale (SPEC2000) N/A
PREIS Price per unit of measure (SPEC2000) N/A
MWSKZ VAT ID Is copied from the item conditions
MSATZ Value-added tax N/A
KOEIN Currency N/A
CURTP Currency type and valuation view N/A
!--a11y-->
1.1.2.2.2.5.1.11 Schedule Lines (Segment E1EDP20)

WMENG Schedule line quantity Ordered quantity
AMENG Previous schedule line quantity Confirmed quantity
EDATU Date Delivery date
EZEIT Time Arrival time
EDATU_OLD Date N/A
EZEIT_OLD IDoc: Time N/A
!--a11y-->
1.1.2.2.2.5.1.12 Schedule Lines Additional Data (Segment

E1J3P20)
J_3AABGRU Reason for rejection for quotations and orders Reason for rejection at schedule line level
J_4KRCAT Requirements Category Requirements category of the schedule line
J_4KSCAT Stock Category N/A
J_3AETENR Schedule line Schedule line number
J_3AVASIT VAS item values: E labeling, V packing, S special N/A

service
This segment is supp orted as of IDoc type J3 AORD0 2.
!--a11y-->
1.1.2.2.2.5.1.13 Partner Information (Segment E1EDPA1)

PARVW Partner function (for example, sold-to party, ship-to Internal (2-character) code for the partner function (for
party) example, "AG", "WE")
recipient at the sold-to party.
NAME1 Name 1 Address information of the partner
NAME2 Name 2
KNREF Customer-specific description of the business

partner (plant, warehouse)
PFORT Location of the PO Box
For more information, see the notes on the corresponding header segment E1EDKA1.
!--a11y-->
1.1.2.2.2.5.1.14 Partner Info Additional Data (Segment

E1EDPA3)
QUALP IDoc partner identification (for example, Only indicator 001 - International Location Number
Dun&Bradstreet number) (ILN) is processed here.
!--a11y-->
1.1.2.2.2.5.1.15 Object Identification (Segment E1EDP19)

QUALF IDoc object identification (for example, customer Indicator for material identification in field IDTNR
material number)
IDTNR Material identification Material number
KTEXT Short text Material short text
MFRPN Manufacturer part number N/A
MFRNR Manufacturer number N/A
The following indicators are dis played in field Q UALF:
002 Internal material number
003 EAN/UPC number
006 Pricing reference material
!--a11y-->
1.1.2.2.2.5.1.16 Terms of Delivery (Segment E1EDP17)
QUALF Terms of delivery indicator 001 for Incoterms part 1

002 for Incoterms part 2
LKOND Delivery Condition: Code Is copied from the document.
LKTEXT Delivery Condition: Text Is copied from the document.
LPRIO Delivery priority N/A
!--a11y-->
1.1.2.2.2.5.1.17 Terms of Payment (Segment E1EDP18)

QUALF Terms of payment indicator 001 – 003 for terms of payment 1-3 from the
document item
TAGE Number of days Is copied from the document.
PRZNT Percentage for terms of payment Is copied from the document.
ZTERM_TXT Text line N/A
!--a11y-->
1.1.2.2.2.5.1.18 Additional Data (Segment E1EDP35)

QUALZ Indicator for additional data Indicator for additional data transferred with CUSADD
CUSADD Additional data Is copied from the document.
CUSADD_BEZ Text for additional data N/A
The following indicators for additional data are issued at item level:
001-005 Customer groups 1 – 5
006-010 Condition groups 1 – 5
!--a11y-->
1.1.2.2.2.5.1.19 Text Identification (Segment E1EDPT1)

TDID Text ID Text identification key
Segment E1EDKT2 is sent for each text line corresponding to segment E1EDKT1.
!--a11y-->
1.1.2.2.2.5.1.20 Texts (Segment E1EDPT2)

TDLINE Text line Text line for the Text ID used under E1EDPT1
TDFORMAT Tag column Format keys for the output form of the text.
!--a11y-->
1.1.2.2.2.5.1.21 Totals Segment (Segment E1EDS01)
SUMID Indicator totals segment Indicator for the amount used under
SUMME
SUMME Total value totals segment Totals amount
SUNIT Unit, total value, totals segment, Unit of total

shipping notification
WAERQ Currency ISO code for currency
The following ind icators are used in the outbound ID oc:
001 Number of items
002 Net value of document
!--a11y-->
1.1.2.2.2.5.1.22 User Exits in the Outgoing Order Confirmation

Two customer enhancements are available in the outgoing order confirmation via the IDoc interface.
EXIT_SAPLJ4AS_101
EXIT_SAPLJ4AS_102
To activate the customer enhancement, create a project. The customer enhancements are summarized in the SAP enhancement J_3AEDS1.
!--a11y-->
1.1.2.2.2.5.2 Document Header: General Data (Segment

E1EDK01)
ACTION Action code that concerns the entire EDI message 00 0 = order unchanged
00 4 = order changed
kzabs Order acknowledgment requirement indicator N/A
CURCY Currency code ISO currency code for the entire document
HWAER EDI local currency N/A
WKURS Exchange rate Exchange rate from document header
ZTERM Term of payment Term of payment from document header
kundeuinr VAT registration number N/A
eigenuinr VAT registration number N/A
BSARt Document type Order type from order header
BELNR Document number Order number
ntgew Net Weight N/A
brgew Gross weight N/A
gewei Weight Unit N/A
fkart_rl Remuneration list type N/A
ABLAD Unloading point N/A
BSTZD Order number addition of customer Order number of customer
VSART Shipping condition Shipping condition from order header
VSART_BEZ Description of shipping type Description for shipping condition
REcipnt_no Number of recipient Customer number of the ordering party
kzazu Indicator: order combination - is copied from the document-
autlf Complete delivery indicator - is copied from the document-
augru Order reason - is copied from the document-
augru_bez Description order reason - is copied from the document-
abrvw - is copied from the document-
abrvw_bez - is copied from the document-
fktyp Billing category
lifsk Delivery note block - is copied from the document-
lifsk_bez Description: delivery note block - is copied from the document-
empst Receiving point - is copied from the document-
abtnr Department number N/A
delco Agreed delivery time N/A
wkurs_m Rate with indirect quotation N/A
!--a11y-->

(Segment E1EDK14)
QUALF Organization indicator Indicator for the data sent in the field ORGID.
The following ind icators are pr ocessed in the outbound ID oc:
006 Division
010 Sales Group
012 Order Type
013 Customer purchase order type
016 Sales Office
J01 Department
!--a11y-->

E1J3K03)
following fields.
DATUM Date - is copied from the document-
UZEIT Time Transfer from the document only for the indicator 019
The following date indicators are used:
001 Customer purchase order date
002 Order date
005 AFS value-added service Date
010 Validity start date for quotations/requests for quotations
013 Validity end date for quotations/requests for quotations
019 Entry date
!--a11y-->
1.1.2.2.2.5.2.3 Document Header: Taxes (Segment E1EDK04)

MWSKZ VAT ID - is copied from the document-
MSATZ Value-added tax - is copied from the document-
MWSBT Sales tax amount - is copied from the document-
TXJCD Tax Jurisdiction Code N/A
KTEXT Text field N/A
!--a11y-->
1.1.2.2.2.5.2.4 Document Header: Conditions (Segment

E1EDK05)
ALCKZ Surcharge or discount indicator + = Surcharge

- = Discount
KSCHL Condition type (coded) Transfer from header condition table
KOTXT Condition description Transfer from header condition table
BETRG Condition rate Transfer from header condition table
KPERC Condition percentage rate Transfer from header condition table
KRATE Condition record per unit Transfer from header condition table
UPRBS Price Unit Transfer from header condition table
MEAUN Unit of measure Transfer from header condition table
KOBTR Condition end amount N/A
MWSKZ VAT ID Transfer from header condition table
MSATZ Value-added tax N/A
KOEIN Currency N/A
!--a11y-->
1.1.2.2.2.5.2.5 Document Header: Partner Info (Segment

E1EDKA1)
PARVW Partner function (such as sold-to party, ship-to party) Internal (2-character) code for the
partner function (such as ‚AG ‘, ‚WE‘)
LIFNR Vendor number at the customer Normally the identification number of

the order recipient at the sold-to party.
NAME1 Name 1 Address information of the partner
NAME2 Name 2
<.....> Additional fields for partner information. For detailed information see IDoc
documentation on transac tion WE60.
<.....>
Only those partners are sent from the document header that are permitted for shipping per EDI via table EDPVW. You can maintain the table
in Customizing.
!--a11y-->
1.1.2.2.2.5.2.6 Document Header: Partner Info Additional Data
(Segment E1EDK02)
QUALP Partner identification Only indicator 001 - International Location Number

(ILN) is processed here.
!--a11y-->

E1EDK02)
number.
POSNR Item Number Item number of the document
UZEIT Time Time of the document
The following ind icators are used in the outbound ID oc for reference documents:
002 Order number
003 Number of request for quotation
004 Quotation number
006 Contract number
007 Collective number
053 Scheduling agreement number
!--a11y-->
1.1.2.2.2.5.2.8 Document Header: Terms of Delivery (Segment

E1EDK17)
QUALF Terms of delivery indicator 001 for Incoterms part 1

002 for Incoterms part 2
!--a11y-->
1.1.2.2.2.5.2.9 Document Header: Terms of Payment (Segment

E1EDK18)
QUALF Terms of payment indicator 001 – 003 for terms of payment 1-3 from the document header
TAGE Number of days - is copied from the document-
PRZNT Percentage for terms of payment - is copied from the document-
ZTERM_TXT Text line N/A
!--a11y-->
1.1.2.2.2.5.2.10 Document Header: Additional Data (Segment

E1EDK35)
QUALZ Indicator for IDoc additional data Indicator for additional data transferred with CUSADD
CUSADD Data element for article number - is copied from the document-
CUSADD_BEZ 40 character field N/A
The following indicators for add itional d ata are processed at document level:
001 to 005 Customer groups 1 - 5
006 to 010 Condition groups 1 - 5
J01 to J05 AFS customer groups 6 – 7
!--a11y-->
1.1.2.2.2.5.2.11 Document Header: Text Identification

(Segment E1EDKT1)
TDID Text ID Text identification key
TDOBJECT Texts: Application object N/A
TDOBNAME Text name N/A
Segment E1EDKT2 is sent for each text line corresponding to segment E1EDKT1.
!--a11y-->

For texts with multiple lines, the segment is
TDFORMAT Tag column Format keys for the output form of the text
!--a11y-->
1.1.2.2.2.6 IDoc Error Handling for Inbound IDocs
Use
Using the IDoc interface to post document data can result in incorrect IDocs. You must check and correct the IDocs before they are posted again. Using the
program described here, you can edit incorrect IDocs and post them again. A typical example is when sales orders are posted using the IDoc interface (logical
message ORDERS).
Features
If an error occurs in the IDoc inbound processing, a workflow task is triggered and the associate responsible receives a work item in their inbox. The responsible
associate is defined in the partner profile. If you run a workitem, the IDoc is displayed and it can be edited and reposted.
The most important functions are:

● Search Function for Entire IDoc and Flagging of Incorr ect Segments
Using the standard search function (Ctrl + F) any character string can be searched for throughout the entire IDoc. By doing this, incorrect segments can be
found more quickly in larger IDocs. If the error occurs in the IDoc inbound module, the incorrect segments are highlighted in red.
● Editing of the IDoc Data Records
By clicking on the number of a segment, all segment fields can be edited. A segment field can be edited by clicking on the value of that field.
● Display of all Status Records for an IDoc
● Change/Display of the Control Record
● Reserving an IDoc for Deletion (Status 68)
● Processing the IDoc
After the IDoc has been edited, it can be processed as a job either in the foreground or in the background. After the IDoc has been suc cessfully p rocessed,
the work item is deleted from the associates inbox.
The new IDoc error handling function is only delivered for the ORDERS inbox (inbound sales orders in SD). You can also use the IDoc error
handling function for other inbound IDocs with the corresponding Customizing and enhancements (new business object type).

An incorrect ORDERS IDoc cannot be processed online because the ORDERS inbox does not run using Call Transaction as it does in the standard.
A new business object type, /AFS/O RDER, has been generated. This object type has a new method AFSIDocOrders.ErrorHandling .
A new standard task, TS8020 790 3, has been created that calls object type /AFS/O RDER with method AFSIDocOrders.ErrorHandling .
Customer Enhancements ( User Exits)
All customer enhancements used in the inbound function modules can be us ed.
!--a11y-->
1.1.2.2.3 Invoice
Use
The invoice IDoc can be used for EDI communication and for the ALE sc enario Stock Transfers Between Dis tributed Sys tems .
Features
An E1J3P01 segment is created in the IDoc for each SKU in the invoice. The net and gross p rices are always calc ulated at SKU level and are independent of the
billing type (billing at SKU level or item level).
Two billing types can be used in the applic ation:
Billing at SKU Level

Billing at Item Level
Billing at SKU Level
If charges or discounts are defined at document item level, they are valid for all the affected SKUs. If this is the case, the charges are distributed among the SKUs.
One document item with two SKUs, SKU 1 with a quantity of 5 and a net value USD 50, and SKU 2 with a quantity of 10 and a net value of
USD150. The net value at item level is USD 20.
This results in a net value of USD56.67 for SKU 1 and USD163.33 for SKU 2.
Billing at Item Level
In this case, the IDoc also contains SKU net values.
A document item with two SKUs, SKU 1 with a quantity of 5, and SKU 2 with a quantity of 10.
If the prices and charges are defined at item level and the net value at item level is USD150, the result in the IDoc is a net value of USD50
for SKU 1 and USD100 for SKU 2.
Handling SKUs
If the material is an AFS material, VAS data is also sent to each SKU.
Handling Categories
If the Stock Transfer Between Distrib uted Systems sc enario is used, requirement and stock category data is sent to each SKU.
AFS Restrictions
AFS only supp orts logistical invoice verification. Other scenarios that include FI invoices are not supported by AFS.
!--a11y-->
1.1.2.2.3.1 Customizing: Invoice

Logical Message: INVOIC
Basic type: /AFS/INVOIC02
Message type: RD00
Partner function: KU
Process code: SD09 (outbound)
To send out conditions in segment E1EDP05, you must check the print indicator in the pricing procedure for the condition type.
!--a11y-->
1.1.2.2.3.2 Technical Information: Invoices

Additional segments and segment fields are to be sent with AFS-spec ific information.
Segment E1J3P01
Field Description Comments / Remarks
J_3APOSNR Item number Number of the item in the current document It is

used to uniquely identify the item.
J_3ADEPM Department indicates the department for which the customer

ordered the goods. It can be used for printing on
labels and documents.
J_3ASIZE Grid Value
J_3ALNGR AFS Line Group indicator Line Group indicator specified several schedule
lines for one delivery
J_4KRCAT Requirement Category Indicates additional information about type of

requirement
J_4KSCAT Stock category Category assigned to a stockable item.
Segment E1J3AIT - AFS IDoc: VAS Ticketing / Labelling
Segment Field Description Comments / Remarks
J_3ASTORE MSO Stores MSO Stores from J_3AVATL
J_3ATLTYP VAS Ticketing/Label – Type indicates which type of ticket or label is used
J_3ATLMAT VAS Ticketing/Labelling Material Value added service tick./label. material
J_3ACHARC VAS Charge Code Select charge code if you want to charge the
customer for value added services. Depending on
the setup of the condition records, this could then be
an abs olute or percentage based surcharge
J_3AFIELD1 VAS Field 1 for Free Use by Customer
J_3AFIELD2 VAS customer defined field 2
J_3AVASPQ Quantity
J_3AVASPO VAS generated item number
J_3AVASETE VAS generated schedule line number
Segment E1J3AIX - VAS Ticketing / Labelling Text
J_3ATLTXT Additional Text for Ticketing/Labelling Description or additional information can be

maintained for VAS Ticketing / Labeling as
additional text field.
J_3ATLORD VAS Text1 J_3ATLORD from J_3AVATLX
J_3ATLITEM VAS Text1 J_3ATLITEM from J_3AVATLX
J_3ATLSIZE VAS Text1 J_3ATLSIZE from J_3AVATLX
Segment E1J3AIP - AFS IDoc: VAS Packing
J_3ASTORE MSO Stores MSO Stores from J_3AVAP
J_3APTYP VAS Packing Type Type of packing material
J_3APMAT VAS Packing Material Value added service packing material.
J_3ACHARC VAS Charge Code Select charge code if you want to charge the
customer for value added services. Depending on
the setup of the condition records, this could then be
an abs olute or percentage based surcharge.
J_3AINCREM VAS Packing Increment Quantity that can be packed into the packaging
J_3AMIXID Mix Indicator Group for VAS Packing Types Indicates whether and how packaging can pack
items, sizes, colors etc. together. This is an
information only field.
J_3AVASPQ Quantity VAS Processed Quantity
J_3AVASPO VAS generated item number J_3AVASPO from J_3AVAP
J_3AVASETE VAS generated schedule line number J_3AVASETE from J_3AVAP
Segment E1J3AIS - AFS IDoc: VAS Special Services
J_3ASTORE MSO Stores MSO Stores from J_3AVASSO
J_3ASSTYP VAS Special Services – Type Indicates the type of special service
J_3ASSMAT VAS Special Services Material Description of material used for Special Services in
VAS
J_3ACHARC VAS Charge Code
J_3AVASPQ Quantity VAS Processed Quantity
J_3AUPDKZ Update indicator
J_3AVASPO VAS generated item number
J_3AVASETE VAS generated schedule line number
!--a11y-->
1.1.2.2.3.3 User Exit in the Invoice

exit_saplvedf_001
This User Exit sends out Invoice header and Invoice detail records along with the VAS data for any customer modifications.
!--a11y-->
1.1.2.3 Materials Management (MM)

The following sections contain information on the area of Materials Management.
!--a11y-->
1.1.2.3.1 Purchasing
The following table shows an overview of the supported document types, their assigned logical message, and the IDoc type to be used.
Remember that this documentation always refers to the most recent version of an IDoc type, unless specified otherwise. We therefore
urgently recommend that you use the most recent version of an IDoc type for the respective document type.
Document type Direction Logical Message IDoc Type Output type Process Code
Request for Quotation Outbound REQOTE /AFS/ORDERS04 NEU (new) ME12
Purchase Order Outbound ORDERS /AFS/ORDERS04 NEU (new) ME10
Purchase Order Change Outbound ORDCHG /AFS/ORDERS04 NEU (new) ME11
Purchase Order Receipt ORDRSP /AFS/ORDERS04 ORDR

Confirmation
Contracts Outbound BLAORD /AFS/BLAORD03 J3AV /AFS/ME15
Contract Change Outbound BLAOCH /AFS/BLAORD03 J3AV /AFS/ME16
Delivery Announcement Receipt DESADV /AFS/DELVRY02 DELS
Invoice Receipt Receipt INVOIC /AFS/INVOIC02 INVL
!--a11y-->
1.1.2.3.1.1 Request for Quotation

A request for quotation consists of a header and items.
Request for quotation header
Contains general information on the request for quotation such as the vendor address.
Items
Contain the total quantities and delivery dates of the requested materials or services.
Schedule line
Contains AFS data such as grid values and categories.
In contrast to other purchasing documents, you cannot enter an account assignment in the request for quotation.
!--a11y-->
1.1.2.3.1.1.1 Technical Information: Request for Quotation

(Purchasing)
Request for Quotation Outbound REQOTE /AFS/ORDERS04 NEU (new) ME12
AFS-Specific Fields for the Request for Quotation
E1J3K03 IDDAT AFS Indicator for IDoc date segment
E1J3K03 DATUM IDoc: Date

001: Purchase order date EKKO-BEDAT
003 : Requested delivery date EKKO-EINDT
004: Delivery date EKKO-EINDT
008 : Final date for app lication EKKO-BWBDT
009 : Deadline for submis sion of EKKO-ANGDT
quotations EKKO-IHRAN
010: Quotation Date SY-DATLO
012: IDoc creation date EKKO-BNDDT
013: Binding period for quotation (valid EKKO-KDATB
to) EKKO-KDATE
014: Validity start date for outline
agreement or request for quotation
015: Validity end date for outline
E1J3P01 POSEX Item Number EKPO-EBELP
PSTYP Item Category EKPO-PSTYP
KZABS Indicator for the order acknowledgment EKPO-KZABS

requirement
MENGE Quantity EKPO-KTMNG or

EKET-MENGE
MENEE Unit of Measure EKPO-MEINS
BMNG2 Quantity in Price Unit of Measure EKPO-KTMNG
PMENE Price Unit of Measure EKPO-BPRME
BPUMN Denominator for the conversion EKPO-BPUMN

BPRME into BME
BPUMZ Numerator for the conversion BPRME EKPO-BPUMZ

into BME
ABFTZ Agreed Cumulative Quantity EKPO-ABFTZ
VPREI Price (net) EKPO-NETPR or KOMV-KBETR
PEINH Price Unit EKPO-PEINH
NETWR Value of Item (net) EKPO-NETWR o.

KOMV-KWERT
AENTW Absolute Net Value of the Item EKPO-NETWR
NTGEW Net Weight EKPO-NTGEW
GEWEI Weight Unit EKPO-GEWEI
MATKL IDoc Material Class EKPO-MATKL
EVERS Shipping Instruction EKPO-EVERS
BRGEW Total Weight EKPO-BRGEW
VOLUM Volume EKPO-VOLUM
VOLEH Volume Unit EKPO-VOLEH
J_3APOSNR Item Number EKET-ETENR
J_3ASIZE AFS Grid Value EKET-J_3ASIZE
J_4KRCAT Requirements Category EKET-J_4KSCAT
J_4KSCAT Stock Category EKET-J_4KSCAT
E1J3AIM J_3AOBIDQF AFS IDoc object identification (material

number,...)
J_3ASIZE AFS grid value EKET-J_3ASIZE
J_3AIDTNR IDoc material identification

001: Customer material number EKPO-EMATN
002: Vendor material number EKET-J_3AVEMA
003: International article number (EAN) EKET-J_3AVIEAN
004: Universal Product Code UPC EKET-J_3AVIEAN
005: Universal Commercial Code UCC EKET-J_3AUCCMR
J_3AKTEXT IDoc short text EKPO-TXZ01
J_3AKRCAT Requirements Category
J_3AKSCAT Stock Category EKET-J_4KSCAT
E1EDPO02 QUALF IDoc indicator reference document
BELNR IDoc document number

J30: ALE Identifier EKET-/AFS/ALE_ID.
E1J3P03 IDDAT AFS indicator for IDoc date segment
DATUM IDoc: Date

003 : Requested delivery date EKPO-J_3ADAT
004: Delivery date EKPO-J_3ADAT
009 : Deadline for submis sion of EKPO-AGDAT
quotations EKPO-ABDAT
016: Reconciliation date for agreed SY-DATLO+EKPO-ETFZ1
cumulative quantity SY-DATLO+EKPO-ETFZ2
017: First firm/trade-off zone
018: Second firm/trade-off zone
E1EDP19 QUALF IDoc object identification (for example,

customer material number)
001: Customer material number
002: Vendor material number
IDTNR IDoc material identification

EKET-J_3AVEMA
EKPO-IDNLF
EKPO-MATNR
EKPO-EMATN
!--a11y-->
1.1.2.3.1.2 Purchase Order
The sold-to party can send the expected prices in the IDoc at the schedule line level. To do so, the pricing condition categories JED1 and JED2 must be
maintained in the price determination schema.
!--a11y-->
1.1.2.3.1.2.1 Technical Information: Purchase Order

(Purchasing)
Purchase Order Outbound ORDERS /AFS/ORDERS04 NEU (new) ME10
AFS-Specific Fields for the Purchase Ord er

to) EKKO-KDATE

requirement

EKET-MENGE

BPRME into BME

into BME
NETWR Value of Item (net) EKPO-NETWR or

KOMV-KWERT
number,...)

E1EDP02 QUALF IDoc indicator reference document

E1J3P03 IDDAT AFS Indicator for IDoc date segment
DATUM IDoc: Date



EKET-J_3A VEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
!--a11y-->
1.1.2.3.1.3 Purchase Order Change

Changes in a purchase order item are flagged using the Action Flag in segment E1J3P01. Only the changed schedule lines or all the schedule lines of the
relevant item are in the IDoc. If a change in the schedule line affects the item, all schedule lines will be sent.
The following changes are possible at header level:
Header texts
The following changes are possible at item level:
Terms of delivery
Delivery and pack ing information
Material text
Item texts
The following changes are possible at schedule line level:
Purchase order quantity

Requested delivery date
Dimension
Category
Tolerances are check ed in the sequence sc hedule line, line, document.
!--a11y-->
1.1.2.3.1.3.1 Customizing: Purchase Order Change

(Purchasing)
Special Customizing for Individual Messages: Purchase Or der Change
In the case of ALE, you must also generate an E1EDP02 segment for deleted schedule lines that contains the ALE-IDs of the deleted schedule lines. To do this,
you must regenerate the change document so that it also logs the changes made to the ALE-ID. You do this using transaction SCDO for the object BELEG.
You must make sure that the flag Doc. for indiv idual fields at delete is s et. In addition, table T166C must contain the entry EKET /AFS /ALEID. You can maintain
this in Customizing.
!--a11y-->
1.1.2.3.1.3.2 Technical Information: Purchase Order Change

(Purchasing)
Purchase Order Change Outbound ORDCHG /AFS/ORDERS04 NEU (new) ME11
AFS-Specific Fields for the Purchase Ord er Change

to) EKKO-KDATE

requirement

EKET-MENGE

BPRME into BME

into BME
NETWR Value of Item (net) EKPO-NETWR or KOMV-KWERT
J_3APOSNR Item Number EKET-ETENR or EKPO-AFS_POSNR

number,...)

DATUM IDoc: Date



EKET-J_3A VEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
!--a11y-->
Features
The confirmation with the confirmation category AB (standard, hardcoded) is integrated in the order based on various checks. Other keys are allowed but unlike
AB are not supported.
If a vendor initially sends a partial confirmation for only two schedule lines for an item that has three schedule lines, you can expect further order confirmations. As
soon as another partial confirmation arrives via EDI, all of the old confirmations will be deleted that have the same confirmation category and have been entered
via EDI. All of the old data is replaced by the data of the current confirmation.
See also
Receiving Confirmations via EDI.
In order to uniquely identify an item/schedule line in a purchase order, you need the following information:
ALE-ID E1EDP02: QUALF (J30) BELNR( ALE-ID ) or

Item E1EDP02: QUALF (001) ZEILE( Item ) BELNR ( Document ) and
Schedule line E1J3P01: J_3APOSNR ( schedule line )
All of the available material-spec ific data (for example, grid v alue, category).
If the ALE ID, item, and schedule line are not completely available, it may not be possible to assign a confirmation to a purchase order/item/schedule line.
In texts in the shipping notification, an ,&’ must be used as a placeholder for the shipping notification number in the segment E1TXTH8.
AFS Restrictions
Order Confirmation
If schedule lines have been deleted from a purchase order, the relevant confirmation will not be deleted in the case of ALE/EDI. You might have to delete these
manually from the order.
!--a11y-->
1.1.2.3.1.4.1 Technical Information: Order Confirmation
(Purchasing)
Purchase Order Inbound ORDRSP /AFS/ORDERS04 ORDR

Confirmation
AFS-Specific Fields for O rder Confirmation

to) EKKO-KDATE

requirement
MENGE Quantity EKPO-KTMNG or EKET-MENGE

BPRME into BME

into BME

number,...)


DATUM IDoc: Date



EKET-J_3A VEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
!--a11y-->
1.1.2.3.1.5 Contracts
Condition category J3AV is a copy of condition category VNEU delivered in the standard system. VNEU uses a processing program defined by SAP, whereas
J3AV uses the general processing program RSNASTED. Both condition categories are integrated in message determination schema RMBEV1.
!--a11y-->
1.1.2.3.1.5.1 Technical Information: Contracts (Purchasing)

Contract Outbound BLAORD /AFS/BLAORD03 J3AV /AFS/ME15
AFS-Specific Fields for Contracts

requirement

BPRME into BME

into BME
!--a11y-->
1.1.2.3.1.6 Contract Change

Condition category J3AV is a copy of condition category VNEU delivered in the standard system. VNEU uses a processing program defined by SAP, whereas
J3AV uses the general processing program RSNASTED. Both condition categories are integrated in message determination schema RMBEV1.
!--a11y-->
1.1.2.3.1.6.1 Technical Information: Contract Change

(Purchasing)
Contract Change Outbound BLAOCH /AFS/BLAORD03 J3AV /AFS/ME16
AFS-Specific Fields for Changing Contracts

requirement

BPRME into BME

into BME
!--a11y-->
1.1.2.3.1.7 Delivery Notification
Features
The entry of bale information in text form has also been implemented. Bale information in text form can be created in condition category J3AB for the delivery
header and the delivery items (segments E1J3ABH and E1J3ABI). You can import packaging data (segments E1EDL37 and E1EDL44). Standard header texts
and item texts can b e transferred and processed.
In contrast to purchase order confirmation, existing notifications are not overwritten in delivery notifications. It is not possible to change existing delivery notifications
via EDI: it is only possible to create new delivery notifications.
ALE ID
E1J3AI2: QUALF ("J30" ) BELNR( ALE-ID ) or
Item
E1J3AI2: QUALF (001) J_3APOSNR (item ) J_3ABELNR ( document ) and J_3AETENR ( schedule line )
All available material-specific data (for example, grid value, category).
If the ALE ID, item, and schedule line are not completely available, it may not be possible to assign a confirmation to a purchase order/item/schedule line.
!--a11y-->
1.1.2.3.1.7.1 Technical Information: Delivery Notification

(Purchasing)
Delivery Notification Inbound DESADV /AFS/DELVRY02 DELS
AFS-Specific Fields for the Delivery Notification
Segment Field Explanation
E1J3ABH J_3AEVRTN Number of the preceding document
J_3ABILNR Billing document number
J_3ABILDT IDoc: Date
J_3ABILTY Invoice category of the vendor
/AFS/LANGUA_ISO Language indicator for address
/AFS/E1EDL24 J_3ALNGR AFS line group indicator
J_3ADEPM Department
/AFS/E1J3AKG J_3AKVGR6 AFS additional data customer group 6
BEZEI6 Description
J_3AKVGR7 AFS additional data customer group 7
BEZEI7 Description
BEZEI8 Description
BEZEI9 Description
BEZEI10 Description
E1J3AI2 J_3AQFREF IDoc indicator reference document
J_3ABELNR IDoc document number
J_3APOSNR Item Number
J_3AETENR Schedule line number
J_3ADATUM Date
J_3AUZEIT Time
J_§AZUDATR Additional data
E1J3AIM J_3AOBIDQF AFS IDoc object identification (material number,...)
J_3ASIZE AFS grid value

003: International article number (EAN)
004: Universal Product Code UPC
005: Universal Commercial Code UCC
J_3AKTEXT IDoc short text
J_3AKSCAT Stock Category
E1JAIP J_3ASTORE MSO Stores
J_3APTYP VAS Packing Type
J_3APMAT VAS Packing Material
J_3AINCREM VAS Packing: Increment
J_3AMIXIND Mix ID for VAS packing types
J_3AVASPQ Quantity
J_3AVASPO VAS Generated Subitem Number
E1J3AIS J_3ASTORE MSO Stores
J_3ASSTYP VAS Special Services: Category
J_3ASSMAT VAS Special Services Material
J_3AVASPQ Quantity
J_3AVASPO VAS Generated Subitem Number
E1J3ABI J_3AUPCNR Style code / UPC
J_3AUCCNR UCC Number
J_3ABALNR Vendor bale number
J_3ADLNR Dye lot number
J_3ASHGR Shade group
J_3APCNR Piece number
J_3ACTNR Cut number
J_3ASQNR Bale sequence number
J_3AWDTH Width
J_3ASEDE Flag: Deltas
J_3ADERL Degree of color difference (darker-lighter)
J_3ADERA Degree of color difference (greener – redder)
J_3ADERB Degree of color difference (bluer – yellower

)
/AFS/LANGUA_ISO Language ID
!--a11y-->
1.1.2.3.1.8 Invoice Receipt and Verification

Note the following restrictions to invoice verification in AFS:
Zero quantities cannot be processed in the invoice receipt.

Conditions in segment E1EDP05 are only processed correctly for transfer prices. All of the other conditions (such as delivery costs, whether they are header
or item conditions) are not processed (see standard).
!--a11y-->
Technical Information: Invoice Receipt and Verification (Purch.)

ALE ID
E1J3AI2: QUALF ("J30" ) BELNR( ALE-ID ) or
Item
E1J3AI2: QUALF ("001") J_3APOSNR (item ) J_3ABELNR ( document ) and J_3AETENR ( schedule line )
All available material-specific data (for example, s ize, category)
If the ALE ID, item, schedule line are not completely available, it may not be possible to assign a confirmation to a purchase order/item/schedule line.
Document Type Direction Logical Message IDoc Type Output Type Process Code
Invoice Receipt Inbound INVOIC /AFS/INVOIC02 INVL
AFS-Specific Fields for the Invoice Receipt and Verification

requirement
BPUMN Denominator for the Conversion EKPO-BPUMN

BPRME into BME
BPUMZ Numerator for the Conversion BPRME EKPO-BPUMZ

into BME
E1JAIP J_3ASTORE MSO Stores
J_3APTYP VAS Packing Type

Safs 6 Fueframeset

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Safs 6 Fueframeset

Hochgeladen von

Copyright:

Verfügbare Formate

SAP Apparel and Footwear (SAP AFS)

PDF download from SAP Help Portal:

Created on October 14, 2014

SAP Apparel and Footwear (SAP AFS)

1.1 Cross-Application AFS Information

This includes the following functions:

To activate seasonality for ARun during allocation:

To activate seasonality for ARun during deallocation:

To activate seasonality for MM/PP/IM:

1.1.2.1 AFS Basic Data

1.1.2.1.1 Grid Master Data

Here are some typical application examples:

Transfer of grid data from a non-SAP System

AFS Special Features

Technical Information: Grid Master Data

Document type Direction Logical Message IDoc type Operation code

Grid Receipt J3AGRI J3AGRI02 J3AN

Grid Issue J3AGRI02

AFS-Specific Fields for the Grid Master

Segment Fields Explanation Origin

E1J3AGH1 MSGFN Function No processing

J_3APGNR Material grid number J_3APGDH-J_3APGNR

J_3AVDAT AFS product grid validation according to J_3APGDH-J_3AVDAT

J_3AKTXT Product grid short text J_3APGDH-J_3AKTXT

J_3ADLKZ Delete indicator J_3APGDH-J_3ADLKZ

J_3AUSED AFS dimension indicator used in product J_3APGDH-J_3AUSED

J_3ACRDT Date of creation J_3APGDH-J_3ACRDT

J_3AEDDT Date changed/deleted J_3APGDH-J_3AEDDT

J_3AUSER User name J_3APGDH-J_3AUSER

J_3ABZD1 Dimension indicator for first dimension J_3APGDH-J_3ABZD1

J_3ABZD2 Dimension indicator for second dimension J_3APGDH-J_3ABZD2

J_3ABZD3 Dimension indicator for third dimension J_3APGDH-J_3ABZD3

J_3ABZDX Selection dimension ID J_3APGDH-J_3ABZDX

J_3ASGTP Material grid type J_3APGDH-J_3ASGTP

J_3ABYT1 Number of bytes of dimension 1 J_3APGDH-J_3ABYT1

J_3ABYT3 Number of bytes of dimension 3 J_3APGDH-J_3ABYT3

J_3ARGTP Reference material grid type J_3APGDH-J_3ARGTP

J_3ARGNR Reference material grid number J_3APGDH-J_3ARGNR

J_3ARDAT Valid-from date of reference material grid J_3APGDH-J_3ARDAT

J_3AMGNR Master grid number J_3APGDH-J_3AMGNR

J_3AMDAT Master grid validation according to date J_3APGDH-J_3AMDAT

J_3ASODI1 Sort sequence for dimension 1 J_3APGDH-J_3ASODI1

J_3ASODI2 Sort sequence for dimension 2 J_3APGDH-J_3ASODI2

J_3ASODI3 Sort sequence for dimension 3 J_3APGDH-J_3ASODI3

J_3AGFILL Filler character for grid display J_3APGDH-J_3AGFILL

J_3AGCONV Check if conversion desired J_3APGDH-J_3AGCONV

J_3AGSORT Sort grid values? J_3APGDH-J_3AGSORT

J_3ADOCALL Activate change history at grid level J_3APGHD- J_3ADOCALL

J_3ARECNOT Maximum number for grid history counter J_3APGHD-J_3ARECNOT

J_3ARECNO Grid history counter J_3APGHD-J_3ARECNO

J_3ABZD1_NEW First characteristic name J_3APGHD-J_3ABZD1

J_3ABZD2_NEW Second characteristic name J_3APGHD-J_3ABZD2

J_3ABZD3_NEW Third characteristic name J_3APGHD-J_3ABZD3

J_3ABZDX_NEW Characteristic name in Z axis of material J_3APGHD-J_3ABZDX

J_3ABXDX Characteristic name in X axis of material J_3APGHD-J_3ABXDX

J_3ABYDX Characteristic name in Y axis of material J_3APGHD-J_3ABYDX

J_3AGCONV2 Check if conversion desired J_3APGHD- J_3AGCONV2

J_3AGCONV3 Check if conversion desired J_3APGHD- J_3AGCONV3

E1J3AGE MSGFN Function No processing

J_3APGNR Material grid number J_3APGEN-J_3APGNR

J_3AVDAT AFS product grid validation according to J_3APGEN-J_3AVDAT

J_3AKORD1 AFS coordinate first dimension J_3APGEN-J_3AKORD1

J_3AKORD2 AFS coordinate second dimension J_3APGEN-J_3AKORD2