Sap Afs

AFS
Manual for new joinners
Index
SAP AFS
Page1
2.
Season
.......................................................................................................... 3
Features................................................................................................................. 3
Activities................................................................................................................. 4
Limitations.............................................................................................................. 5
3.1.1.1 Technical Information: Grid Master Data
...................................................6
3.1.2.2 Material Master: Dialog Functions and their Support in ALE

3.2.2 Sales
...................18
..........................................................................................................24
Available Document Types....................................................................................24

3.2.2.1 Sales Order
.............................................................................................24
Features...............................................................................................................24
AFS Restrictions...................................................................................................25
3.2.7 IDoc Error Handling for Inbound IDocs
......................................................41
Features...............................................................................................................41
AFS Special Features...........................................................................................41
5.
Mapping
......................................................................................................83
Features...............................................................................................................83
Prerequisites.........................................................................................................84
8.2 Coverage Strategy
........................................................................................91
Features...............................................................................................................91
9.1 Material Grids: Overview
...............................................................................93
Prerequisites.........................................................................................................93
Features...............................................................................................................93
Activities...............................................................................................................94
9.1.1 Master Grids
..............................................................................................94
Features...............................................................................................................94
9.1.3 Condition Technique for the Creation of Grid Control Data
........................96
Features...............................................................................................................96
Activities...............................................................................................................98
9.1.5 Sort Sequence for Dimension Values
.........................................................98
Features...............................................................................................................98
9.2 Grid History
...................................................................................................99
Features...............................................................................................................99
9.4.1 Item-Based Dimension Value Conversion
10.
Material Master
................................................102
......................................................................................103
Features.............................................................................................................104
10.2 Direct Input: Material Master
SAP AFS
.....................................................................104
Page2
Prerequisites.......................................................................................................104
Activities.............................................................................................................104
Cross-Application AFS Information

SAP AFS
Page3
1. General Business Processes

General business processes play a role for Sales and Distribution and for Materials
Management and Production. These processes are based on the R/3 Standard and have been
enhanced in order to meet the special requirements of the Apparel and Footwear industry. AFS
gives you the possibility of taking the AFS Specific data (grid values and categories) into
account at every level of the process and therefore of including them in the entire process.
The following actions trigger such general business processes:
Purchase-to-Order
Make-to-Order
Third-Party Order Processing
Stock Transport Order with SD Processing
You can find information on these topics in the documentation of Sales and Distribution and
Materials Management.
2. Season
In the fashion industry, seasons are an integral part of the business processes. Originally,
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 function 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 consider the requirement and stock season before assigning
stock to requirements.
A validation check is performed to check whether or not deallocation has to be triggered,
if the seasonal information is changed in an allocated purchase order or production order
on the basis of deallocation rule settings for purchase orders or production orders.
A validation is performed during goods receipt (GR) for an allocated purchase order or
production order when the season 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 validation is performed to check whether or not deallocation has to be triggered on the
basis of the deallocation rule settings for sales orders, when season information in these
allocated sales order is changed.
SAP AFS
Page4
Seasonality in MM and PP
A season is determined when a purchase requisition or purchase order is created, either
manually or by material requirements planning (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 theCreation Date and Delivery Date.
For multiple valid seasons, MRP selects the first valid season.
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 display only field and cannot be set for the new materials.
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
Applications PO
Handling Deallocation Rule. Here you define what action you want the system to take
when the season in an allocated purchase order is changed. To attach this deallocation
rule to the plant, in Customizing choose AFS Allocation Run Cross
Applications PO Handling Assign PO Rules to Plant.
2.
Maintain the deallocation rule for a season change in allocated production/purchase

orders during goods receipt (GR) in Customizing by choosing AFS Allocation
Run Cross Applications GR Handling Deallocation Rule. Here you define what
action you want the system to take when the seasonduring 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 Applications GR
Handling Assign GR Rules to Plant.
3.
Maintain the deallocation rule for a season change in allocated production orders in
Customizing
by
choosing AFS
Allocation
Run Cross
Applications PP
SAP AFS
Page5
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
Applications 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
Applications SD
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
Applications SD Handling Assign Rule to Order Type.
Seasonality in MM/PP/IM
To activate seasonality for MM/PP/IM:
...
1.
2.
3.
Create a season in Customizing by choosing Logistics - General Define AFS

Seasons. Here you create a season, a collection, and a theme.
Maintain the season on the Season tab page of AFS Basic Data, to link a season to a
material. This is also possible at stock keeping 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.
Activate the season in the material master for MM/PP/IM by using 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 be 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 Date are used for season determination
and season check.
Limitations
Available-to-Promise (ATP) does not consider seasonality.

Season, collection, and theme are not relevant for valuation.
Season, collection, and theme are not present in reservation, deliveries and warehouse
management (WM).
SAP AFS
Page6
3. AFS-Interfaces
The following sections contain information on the AFS interfaces.
3.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.
3.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 system. 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 system, you must exchange data within this system 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 decisive for
the grids because the validity of the sent IDs and grid values is checked using check tables.
3.1.1.1 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
SAP AFS
J3AGRI02
Page7
AFS-Specific Fields for the Grid Master

Segment
Fields
Explanation
Origin
Function
No processing
J_3APGNR
Material grid number
J_3APGDH-J_3APGNR
J_3AVDAT
AFS product grid validation according to date
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 matrix 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_3ABYT2
J_3APGDH-J_3ABYT2
J_3ABYT3
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
J_3APGDH-J_3ASODI2
J_3ASODI3
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_3APGHDJ_3ADOCALL
J_3ARECNOT
Maximum number for grid history counter
J_3APGHDJ_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
E1J3AGH1 MSGFN
grid
SAP AFS
Page8
E1J3AGE
J_3ABXDX
Characteristic name in X axis of material

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

grid
J_3APGHD-J_3ABYDX
/AFS/GRIDBLKZ
Display all columns/lines during grid entry
J_3APGHD-/AFS/GRIDB
LKZ
/AFS/GRIDBLKZ2 Display all columns/lines during grid entry
J_3APGHD-/AFS/GRIDB
LKZ2
/AFS/GRIDBLKZ3 Display all columns/lines during grid entry
J_3APGHD-/AFS/GRIDB
LKZ3
J_3AGCONV2
J_3APGHDJ_3AGCONV2
J_3AGCONV3
J_3APGHDJ_3AGCONV3
MSGFN
Function
No processing
J_3APGNR
J_3APGEN-J_3APGNR
J_3AVDAT
J_3APGEN-J_3AVDAT
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_3ATDAT
Dimension display for date
J_3APGEN-J_3ATDAT
J_3AFDAT
Dimension display: from date
J_3APGEN-J_3AFDAT
MSGFN
Function
No processing
KNUMH
Number of condition record
J_3AGRCD-KNUMH
J_3APGNR
J_3AGRCD- J_3APGNR
J_3AVDAT
J_3AGRCD- J_3AVDAT
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 measure J_3AGRCD-MINAU
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
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_3AUSED
E1J3AGC
J_3AVEMA_N
SAP AFS
Page9
3.1.1.2Grid Master Data: Dialog Functions and their

Support in ALE
You can use the ALE Shared Master Data Tool for grid master data and the material master.
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 successful.
For IDocs with the status incorrect or successful, the status record receives the messages that
were issued during processing. After the logical errors have been resolved, you can reprocess
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 Distribution (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 system enhancement J_3AIMM1
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 system enhancement J_3AIMM1
create a new IDoc segment
SAP AFS
Page10
3.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 system. 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 system as well.
You can transfer stock from external systems in one of two ways:
Data can be transferred in a direct input
Data can be transferred using Application 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.
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 dependencies between objects in Customizing
for Distribution (ALE). In doing so, you are ensuring that the changes in 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
Targeted distribution of materials (sending data manually)
SAP AFS
Page11

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.
3.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
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 indicator
MARA-J_3AGMID
J_3ANOGRID
AFS material without grid (DUMMY grid with MARAonly one dimension)
J_3ANOGRID
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
SAP AFS
Page12
E1J3ASE
E1J3AQD
E1J3MRC
SAP AFS
/AFS/SCLAS
Special procurement key
MARA-/AFS/SCLAS
/AFS/SCHNITT
Cut
MARA-/AFS/SCHNI
TT
J_4KCOVSA
Coverage Strategy
MARA-J_4KCOVSA
MSGFN
Function
No processing
J_3ASEAN
Season indicator
J_3AMSEAJ_3ASEAN
J_3ASIZE
AFS grid value
J_3AMSEAJ_3ASIZE
J_4KRCAT
Requirements Category
J_3AMSEAJ_4KRCAT
/AFS/COLLECTION Collection
J_3AMSEA-/AFS/C
OLLECTION
/AFS/THEME
Topic
J_3AMSEA-/AFS/T
HEME
MSGFN
Function
No processing
J_3AMQCA
Quota category
J_3AQDSTJ_3AMQCA
MSGFN
Function
No processing
J_3AMIND
AFS material master indicator
MARA-J_3AMIND
J_3AMSTATC
AFS material master status MRP
MARCJ_3AMSTATC
J_3AMSTAT
AFS material master status
MARC-J_3AMSTAT
J_4KCOVS
Version number component
MARC-J_4KCOVS
J_3ADISPKZ
MRP indicator
MARCJ_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 source

allocation
MARCJ_3AEKORG
J_3APRCM
Consumption priority
MARC-J_3APRCM
J_3ABUND
Material created with bundles
MARC-J_3ABUND
Page13
E1J3AAD
SAP AFS
J_3ACHINT
Discrete batch number
MARC-J_3ACHINT
J_3ABAINT
Dimension used as batch number for

material without coverage strategy
MARC-J_3ABAINT
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
MARCJ_4KCOVS_4
J_4KDEFSC_4
Default value stock category
MARCJ_4KDEFSC_4
J_4AATPSI
ATP/MRP check method (time or category)
MARC-J_4AATPSI
J_3ASLHMOD
Activate SKU horizon method
MARCJ_3ASLHMOD
J_3AMROUND
MARCJ_3AMROUND
J_3AMRDMENG
MARCJ_3AMRDMENG
MSGFN
Function
No processing
J_3AKORD
AFS dimension according to matrix
J_3AMADJ_3AKORD
J_4KSCAT
Stock Category
J_3AMADJ_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_3AMADJ_3ASIGR
REFVAL
AFS: Reference values for all categories

without special values
J_3AMAD-REFVAL
J_4ASTAT
AFS: MRP status for dimension validation
J_3AMADJ_4ASTAT
J_4ADTFR
Date
J_3AMADJ_4ADTFR
J_3ARISK
AFS risk factor
J_3AMADJ_3ARISK
LGRAD
Area not further defined
J_3AMAD-LGRAD
WZEIT
Replenishment lead time
J_3AMAD-WZEIT
WZEITSG
Total replenishment lead time for SKU

group
J_3AMADWZEITSG
J_3APQTY
AFS packing quantity no longer used
J_3AMADJ_3APQTY
J_3APQUN
AFS unit of the packing quantity no

longer used
J_3AMADJ_3APQUN
Page14
E1J3AKA
/AFS/E1MLGN1
SAP AFS
J_3ACASE
Standard packing type no longer used
J_3AMADJ_3ACASE
VMSTA
Distribution chain-specific material status

- no longer used
J_3AMAD-VMSTA
VMSTD
Validity start date of the distribution chainspecific material status no longer used
J_3AMAD-VMSTD
REFSD

without special values - no longer used
J_3AMAD-REFSD
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

without special values - no longer used
J_3AMAD-REFDIM
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

discontinuation
J_3AMAD-/AFS/NF
SIZE
MSGFN
Function
No processing
J_3AKORD
AFS dimension according to grid
J_3AMADKAJ_3AKORD
J_4KSCAT
Stock Category
J_3AMADKAJ_4KSCAT
J_3AKALSW
Preference SKU
J_3AMADKAJ_3AKALSW
J_3AKALGR
Valuation type (AFS)
J_3AMADKAJ_3AKALGR
TVERS
Transportation indicator: planned version
J_3AMADKATVERS
VPRSV
Price control indicator
J_3AMADKAVPRSV
PRICE
Standard price
J_3AMADKAPRICE
EKALR
Material is costed with quality structure
J_3AMADKAEKALR
ZKPRS
Future price
J_3AMADKAZKPRS
ZKDAT
Validity start date of the price
J_3AMADKAZKDAT
J_3ASRD
AFS: surcharges +/-
J_3AMADKAJ_3ASRD
J_3ARKALGP
Reference preference group
J_3AMADKAJ_3ARKALGP
MSGFN
Function
No processing
Page15
/AFS/E1MLGN2
/AFS/E1MLGN3
SAP AFS
LGNUM
Warehouse number/complex
/AFS/MLGN1LGNUM
J_3ASIZE
AFS grid value
/AFS/MLGN1J_3ASIZE
LHMG1
1. Loading equipment quantity
/AFS/MLGN1LHMG1
LHMG2
/AFS/MLGN1LHMG2
LHMG3
/AFS/MLGN1LHMG3
LHME1
Unit of measure for 1. Loading equipment

quantity
/AFS/MLGN1LHME1
LHME2

quantity
/AFS/MLGN1LHME2
LHME3

quantity
/AFS/MLGN1LHME3
LETY1
1. Storage unit type
/AFS/MLGN1LETY1
LETY2
/AFS/MLGN1LETY2
LETY1
/AFS/MLGN1LETY1
MSGFN
Function
No processing
LGNUM
/AFS/MLGN2LGNUM
J_3ASIZE
AFS grid value
/AFS/MLGN2J_3ASIZE
J_4KSCAT
Stock Category
/AFS/MLGN2J_4KSCAT
LTKZA
Storage type indicator removal from storage /AFS/MLGN2LTKZA
LGBKZ
Storage section indicator
/AFS/MLGN2LGBKZ
BSSKZ
Special movement indicator - Warehouse

Management
/AFS/MLGN2BSSKZ
L2SKR
Material relevance for two-step picking
/AFS/MLGN2L2SKR
LTKZE
Storage type indicator, placement in storage /AFS/MLGN2LTKZE
BLOCK
Bulk storage indicator
/AFS/MLGN2BLOCK
KZMBF
Indicator: Message to Inventory

Management
/AFS/MLGN2KZMBF
KZZUL
Indicator: Addition to existing stock allowed
/AFS/MLGN2KZZUL
MSGFN
Function
No processing
Page16
LGNUM
/AFS/MLGN3LGNUM
J_3ASIZE
AFS grid value
/AFS/MLGN3J_3ASIZE
J_4KSCAT
Stock Category
/AFS/MLGN3J_4KSCAT
MKAPV
Capacity consumption
/AFS/MLGN3MKAPV
BEZME
Reference unit of measure for capacity

consumption
/AFS/MLGN3BEZME
Function
No processing
LGNUM
/AFS/MLGTLGNUM
J_3ASIZE
AFS grid value
/AFS/MLGTJ_3ASIZE
J_4KSCAT
Stock Category
/AFS/MLGTJ_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/MLGTMAMNG
NSMNG
Replenishment quantity
/AFS/MLGTNSMNG
KOBER
Picking area
/AFS/MLGT-KOBER
RDMNG
Rounding quantity
/AFS/MLGTRDMNG
MSGFN
Function
No processing
J_3AVASG
AFS VAS material group
J_3AMVKEJ_3AVASG
J_3APIND
AFS pricing indicator in material master
J_3AMVKEJ_3APIND
MSGFN
Function
No processing
MEINH
Unit of measure for display
/AFS/MARM-MEINH
J_3ASIZE
Grid value
/AFS/MARMJ_3ASIZE
J_4KSCAT
Stock Category
/AFS/MARMJ_4KSCAT
VOLUM
Volume
/AFS/MARMVOLUM
BRGEW
Gross weight
/AFS/MARMBRGEW
NTGEW
Net Weight
/AFS/MARMNTGEW
/AFS/E1MLGTM MSGFN
E1J3MKE
/AFS/E1MARM
SAP AFS
Page17
REFDIM

/AFS/MARMREFDIM
Function
No processing
J_3AKORDX
Grid value
/AFS/MEANJ_3AKORDX
/AFS/EANBLOCK
Category value
/
AFS/MEAN-/AFS/E
ANBLOCK
/AFS/CAT_APPL
Category type
/
AFS/MEAN-/AFS/C
AT_APPL
MSGN
Function
No processing
J_3ASIZE
Grid value
/AFS/MVKEJ_3ASIZE
J_4KRCAT
Requirement category
/AFS/MVKEJ_4KRCAT
VMSTA
Distribution chain-specific material status
/AFS/MVKE-VMSTA
VMSTD
Validity start date of the distribution chainspecific material status
/AFS/MVKEVMSTD
/AFS/REFVMS

/
AFS/MVKE-/AFS/R
EFVMS
J_3APQTY
AFS packing quantity
/AFS/MVKEJ_3APQTY
J_3APQUN
AFS: unit for packing quantity
/AFS/MVKEJ_3APQUN
J_3ACASE
Standard packing category
/AFS/MVKEJ_3ACASE
/AFS/REFPQ

/
AFS/MVKE-/AFS/R
EFPQ
J_3AGEND
Target group
/AFS/MVKEJ_3AGEND
/AFS/REFGEND

/
AFS/MVKE-/AFS/R
EFGEND
/AFS/E1MEANM MSGFN
/AFS/E1MVKE
3.1.2.2 Material Master: Dialog Functions and their Support in

ALE
You can use the ALE Shared Master Data Tool for grid master data and the material master.
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:
SAP AFS
Page18
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 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 carries out the usual field checks, but also checks the foreign keys 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 distribution of data via ALE, the field selection you have set in
Customizing of the Material Master under Maintain Field Selection for DataScreen will be
interpreted exactly the same as in the dialog. However, the following different transaction
references are used in ALE for the field selection 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:
MM01 (for the creation of materials)
MM02 (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 system issues an appropriate 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
For IDocs with the status incorrect or successful, the application log receives the messages that
Customizing of the Distribution (ALE).
In Customizing of the Material Master under Configure Customized Material Master, you can
extend the material master by adding your own table fields. The data in the user-defined fields
can also be distributed via Application Link Enabling (ALE).
In order to be able to distribute user-defined data via ALE, you need to:
activate the system enhancement MGV00001
SAP AFS
Page19
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 MGV00001.
EXIT_SAPLMV01_002
EXIT_SAPLMV03_002
You can find further information in the system enhancement MGV00001 and user exit
documentation.
Error messages
Error number Possible causes
Solution
8J670
When changing or enhancing a Check IDoc and correct the maintenance

material by adding a plant, the
status.
wrong maintenance status is also
delivered.
8J671
Transferred data is duplicated, for Check IDoc and correct duplicate entries.
example, the same season code
is used twice for the same
dimension
Material Conversion ID in Material Master

As of the 6.0 release, you cannot maintain material conversion IDs. However, the old/existing
materials can continue 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.
3.2 Sales and Distribution (SD)

The following sections contain information on the area of Sales and Distribution.
3.2.1 Shipping/Transport: Transportation Interface

Shipment data can be sent per EDI. Shipping documents are generally used 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
SAP AFS
Page20
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.
3.2.1.1 Shipping/Transport: Delivery Interface

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

service provider who can carry out packing, picking and shipping. (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 types serve 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 split is not permitted in the confirmation. The batch that must be verified is the
one that is also in the delivery.
Overpicking of a stockkeeping 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.
Customizing: Delivery Interface
Logical
Message
SAP AFS
IDoc Type
Output Type
Partner Type
Process Code
Page21
WHSORD
WHSCON
/AFS/DELVRY02
/AFS/DELVRY02
WSOR
LS LS
DELV (outbound)
DELV (inbound)
SHPORD
SHPCON
/AFS/DELVRY02
/AFS/DELVRY02
SHOR
LI LI
DELV (outbound)
DELV (inbound)
CARNOT
/AFS/DELVRY02
CANO
LI
DELV (outbound)
DESADV
/AFS/DELVRY02
LAVA
KU
DELV (outbound)
Technical Information: Delivery Interface

Description of the IDoc Fields
Description of the AFS Fields in the Outbound IDoc
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.
J_3ALNGR
AFS line groups indicator
/AFS/E1EDL24
The system uses this indicator to group SKUs that are to be

delivered together.
/AFS/E1J3AKG
J_3ADEPM
Indicates the customer department for whom the SKU was

ordered. This information field is taken from the sales order.
J_3AKVGR6
Additional customer groups.
to
The additional customer groups are managed in the customer

master in an AFS-specific view.
J_3AKVGR10
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
SAP AFS
Page22
stock transfer scenario. This is an internal number and is

assigned by the system.
E1J3AIM
J_3AOBIDQF
Indicates the type of material:

002: 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.
E1J3AITX
J_3ATLMAT
Ticketing/labeling material
J_3ACHARC
Code determining the price charged when the customer pays for
ticketing/labeling.
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'
SAP AFS
Page23
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.
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
3.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
Orders
Inbound
ORDERS
/AFS/ORDERS05
J3AA
Contracts (CQ) Inbound
ORDERS
/AFS/ORDERS05
J3AA
Order Change Inbound
ORDCHG
/AFS/ORDERS05
J3AC
Order
Confirmation
Outbound
ORDRSP
/AFS/ORDERS05
BA00
SD10
Quotations
Outbound
QUOTES
/AFS/ORDERS05
AN00
J3AJ
SAP AFS
Output Type Process

Code
Page24
3.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 processing,
processing 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 possibility of running the data processing visibly as is
normally possible in an inbound process when using batch input.
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 customer enhancements EXIT_SAPLJ4AS_601 and
EXIT_SAPLJ4AS_701.
To use enhanced error handling options, see section IDoc Error Handling for
Inbound IDocs.
The current release uses IDoc type /AFS/ORDERS05. This IDoc type is now in the fifth version
(after J3AORD01, J3AORD02, /AFS/ORDERS03 and /AFS/ORDERS04).
You must always use the most recent version of an IDoc type.
AFS Restrictions
When creating an MSO explosion, the splitting of the created order into individual
documents is not automatically triggered.
The delivery order is not supported.
Conditions in the incoming sales order cannot be changed at the header level, item level
or dimension level. Read the Notes in the documentation for segments E1EDK04,
E1EDK05, E1EDP04 and E1EDP05.
You cannot use the IDoc interface to automatically copy contracts 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 cannot be changed in AFS.
AFS does not support adding individual components by means of an order change IDoc
(ORDCHG) to a bill of material (BOM) that has already been exploded in a sales
document.
Creating MSOs with VAS data
In order changes per IDoc, the partner functions AG, RE, RG, and SB cannot be
changed (this is also valid when adding new items and/or dimensions).
Only the partner functions RE, WE and RG are processed at item level.
AFS does not support changes to the material number or the dimension of an already
existing stock keeping unit (SKU). SKUs can only be flagged with one deletion indicator.
Contracts: AFS does not support the transfer or additional contract data (table VEDA)
using the IDoc interface.
The purchase order (PO) number will get deleted when you have created a sales order
with reference to a contract via IDoc and the PO number is passed at the item level by
entering the document field (BSTKD) in the segment EIEDP02 of the IDoc.
SAP AFS
Page25
It is effective only when the PO number is passed 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 BOM (Bill Of
Material), then the component level reference does not take place as IDoc does not
support it. However if you implement the available user exit, this functionality will be
obtained.
3.2.2.2 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
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
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
Messages Configure
Organization Data
Interchange EDI
Data
Interchange EDI
EDI Partners Assign Customer/Vendor To Sales
3.2.2.3 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.
Document Header: General Data (Segment E1EDK01)
Mandatory segment: YES
SAP AFS
Page26
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 successful,
error VG014 appears.
hwaer
EDI local currency
No processing
wkurs
Exchange rate
Is transferred to the document
zterm
Term of payment
kundeuinr
VAT registration number
No processing
eigenuinr
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
VSART
Shipping condition
VSART_BEZ
Description of shipping type
No processing
recipnt_no
Number of recipient
No processing
kzazu
Indicator: order combination
autlf
Complete delivery indicator
augru
Order reason
augru_bez
Description order reason
No processing
abrvw
abrvw_bez
No processing
fktyp
Billing category
No processing
lifsk
Delivery note block
lifsk_bez
Description: delivery note block
No processing
empst
Receiving point
abtnr
Department number
No processing
delco
Agreed delivery time
No processing
wkurs_m
Rate with indirect quotation
No processing
SAP AFS
Page27
Document Item: General Data (Segment E1J3P01)

Mandatory segment: NO
Field
Short text
Explanation
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,
existing in the IDoc.
GRKOR
Delivery group (items are delivered

together)
No processing
SAP AFS
Page28
EVERS
Shipping Instruction
No processing
BPUMN
Denominator for the Conversion BPRME

into BME
No processing
BPUMZ
Numerator for the Conversion BPRME into No processing

BME
ABGRU
Reason for item rejection
Is transferred to document item.
ABGRT
Description
No processing
ANTLF
Maximum number of permitted partial

deliveries per item
FIXMG
Delivery date and quantity fixed
No processing
KZAZU
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 set.
J_3ADEPM
Department
J_3ASPLIT
AFS Split indicator
J_3ASEAN
Season indicator
J_3ASIZE
AFS grid value
Is transferred to document item or

schedule line
J_3ALNGR
AFS Line group ID (schedule lines are

delivered together)
J_4KRCAT
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), special service (S)
No processing
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
SAP AFS
Page29
application.
EMPST
Receiving point
ABTNR
Department number
No processing
ABRVW
Usage indicator
No processing
WERKS
Plant
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
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/IDOC 018 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.
SAP AFS
Page30
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 recipient
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.
3.2.2.4 User Exits in the Incoming Order
SAP AFS
Page31
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_3AEDS0.
3.2.3 Contract
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.
3.2.3.1 Customizing: Contract

Contracts must be flagged in Customizing as a sales document type for the document category
contracts
(G).
Choose
in
Customizing Sales
and
Distribution Sales Sales
Documents Sales Document Header Define Sales Document Types.
3.2.3.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.
Document Header: Organizational Data (Segment E1EDK14)
Field
Short text
Explanation
QUALF
Organization Indicator
Describes the use of the data

sent in field ORGID (for
example 006 for division, 007
for distribution channel, 008 for
sales organization). With the
SAP AFS
Page32
qualifier 012 the order type can

also be transferred in the field
ORGID.
ORGID
Organization Indicator
See field QUALF.
The following indicators 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
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.
Document Header: Date Segment (Segment E1J3K03)
Field
Short text
Explanation
IDDAT
Indicator for Date Segment
Indicator for the use of the date

/ time entries in the following
fields.
DATUM
Date
UZEIT
Time
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 date indicators are relevant for contracts:

006
AFS Cancellation Date
014
Validity start date for outline

agreements
Please note that the AFS cancellation date for contracts is interpreted as the validity end date.
SAP AFS
Page33
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 message 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 appears. If this occurs,
please correct the date entries.
3.2.4 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.
3.2.4.1 Technical Information: Quotation

The IDoc outbound processing for quotations is essentially identical to that of the order
confirmation The following exceptions and special features are valid for quotations:
Segment E1EDK02 Document Header Reference Data
Field
Short text
Explanation
QUALF
Reference document indicator
For the identification of the subsequent

document number.
BELNR
Document number
Document number
POSNR
Item Number
Item number of the document
DATUM
Date
Document date
UZEIT
Time
Time of the document
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
QUALF
IDoc object identification (such as material

number, customer, and so on)
IDTNR
KTEXT
Short text
MFRPN
Manufacturer part number
MFRNR
Manufacturer number
The segment is not used in the outbound quotation. The object identification is sent with the
segment E1J3AIM.
SAP AFS
Page34
Document Item General Data

Field
Short text
Explanation
POSEX
Item Number
Item number from a customer order.
ACTION
000 - 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 category
table EDPST.
KZABS

requirement
N/A
MENGE
Quantity

Please note: for AFS materials with
dimensions, the quantity ordered is per
dimension.
MENEE
Unit of Measure

order quantity
BMNG2
N/A
PMENE
ABFTZ
N/A
VPREI
Price (net)
Price per price unit. Please note: for

AFS materials with dimensions, the
price here is per dimension.
PEINH
Price Unit
Price Unit
NETWR
Value of Item (net)
Net value. For AFS materials with

dimensions, the value here is per
dimension.
ANETW
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

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
UEPOS
GRKOR

together)
EVERS
N/A
SAP AFS
Page35
BPUMN
Denominator for the conversion BPRME

into BME
N/A
BPUMZ
Numerator for the conversion BPRME into

BME
N/A
ABGRU
Is copied from document item or

schedule line.
ABGRT
Description
Text for reason for rejection ABGRU
ANTLF

deliveries per item
FIXMG
KZAZU
N/A
J_3APOSNR
Item Number
Schedule line number of dimension
J_3AMSOM
Equal mix of products in a multi-store order Mix ID for multi-store order.
J_3ABZUS
J_3ADEPM
Department
J_3ASPLIT
AFS Split indicator
J_3ASEAN
Season indicator
J_3ASIZE
AFS Grid Value
N/A
J_3ALNGR
AFS Line group-ID (schedule lines are

delivered together)
J_4KRCAT
N/A
J_4KSCAT
Stock Category
N/A
BRGEW
Total Weight
Is copied from the document item
VOLUM
Volume
N/A
VOLEH
Volume Unit
N/A
J_3AVASIT

J_3AEBTYP
N/A
J_3AMSOF
AFS Multi-store order counter for partner
N/A
PSTYV
N/A
EMPST
Receiving point
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
N/A
SAP AFS
Page36
MATNR
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 quotation.
3.2.5 Order Change

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 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 with VAS data via IDoc is not 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, E1EDP04, E1EDP05.
AFS does not support changes to the material number or the dimension of an already
existing stock keeping unit (SKU). SKUs can only be flagged with one deletion indicator.
AFS does not support adding individual components by means of an order change IDoc
(ORDCHG) to a bill of material (BOM) that has already been exploded in a sales
document.
3.2.5.1 Customizing: Order Change

Basically the same settings are valid as for the incoming orders.
A partner profile and inbound parameters for the output type ORDCHG must be maintained
(transaction WE20) for the partner.
3.2.6 Order Confirmation

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.
General Data for the Order Confirmation (Segment E1J3P01)
Field
Short text
Explanation
POSEX
Item Number
Item number from a customer order.
ACTION
000 - item unchanged

001 - item changed
003 - item deleted
PSTYP
SAP AFS
Item Category
One-digit numerical indicator for the

item category. The indicator is
converted into the sales item category
Page37

table EDPST.
KZABS

requirement
N/A
MENGE
Quantity

For AFS materials with dimensions, the
ordered quantity here is per dimension.
MENEE
Unit of Measure

order quantity
BMNG2
N/A
PMENE
ABFTZ
N/A
VPREI
Price (net)
Price per price unit. For AFS materials

with dimensions, the price here is per
dimension.
PEINH
Price Unit
Price Unit
NETWR
Value of Item (net)
Net value. For AFS materials with

dimensions, the value here is per
dimension.
ANETW
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

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
UEPOS
GRKOR

together)
EVERS
N/A
BPUMN

into BME
N/A
BPUMZ
Numerator for the Conversion BPRME into N/A

BME
ABGRU
Is copied from document item or

schedule line.
ABGRT
Description
Text for reason for rejection ABGRU
ANTLF

deliveries per item
FIXMG
KZAZU
N/A
SAP AFS
Page38
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
J_3ADEPM
Department
J_3ASPLIT
AFS Split indicator
J_3ASEAN
Season indicator
J_3ASIZE
AFS Grid Value
J_3ALNGR
AFS Line group-ID (schedule lines are

delivered together)
J_4KRCAT
J_4KSCAT
Stock Category
The stock category is converted from

the requirements category
BRGEW
Total Weight
VOLUM
Volume
N/A
VOLEH
Volume Unit
N/A
J_3AVASIT

J_3AEBTYP
N/A
J_3AMSOF
AFS Multi-store order counter for partner
N/A
PSTYV
N/A
EMPST
Receiving point
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
N/A
MATNR
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.
Document Header: General Data (Segment E1EDK01)
Field
SAP AFS
Short text
Explanation
Page39
ACTION
Action code that concerns the entire EDI

message
000 = order unchanged

004 = 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
N/A
eigenuinr
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
autlf
Complete delivery indicator
augru
Order reason
augru_bez
Description order reason
abrvw
abrvw_bez
fktyp
Billing category
lifsk
Delivery note block
lifsk_bez
Description: delivery note block
empst
Receiving point
abtnr
Department number
N/A
delco
N/A
wkurs_m
Rate with indirect quotation
N/A
SAP AFS
Page40
3.2.7 IDoc Error Handling for Inbound IDocs

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 Incorrect 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 successfully processed, 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/ORDER, has been generated. This object type has a new
method AFSIDocOrders.ErrorHandling.
A new standard task, TS80207903, has been created that calls object type /AFS/ORDER with
method AFSIDocOrders.ErrorHandling.
All customer enhancements used in the inbound function modules can be used.
3.2.8 Invoice
The invoice IDoc can be used for EDI communication and for the ALE scenario Stock Transfers
Between Distributed Systems.
SAP AFS
Page41
Features
An E1J3P01 segment is created in the IDoc for each SKU in the invoice. The net and gross
prices are always calculated 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 application:
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 USD20.
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 Distributed Systems scenario is used, requirement and stock
category data is sent to each SKU.
AFS Restrictions
AFS only supports logistical invoice verification. Other scenarios that include FI invoices are not
supported by AFS.
3.2.8.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.
SAP AFS
Page42
3.2.8.2 Technical Information: Invoices

Additional segments and segment fields are to be sent with AFS-specific 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 absolute or percentage based
surcharge
J_3AFIELD1
VAS Field 1 for Free Use by Customer
J_3AFIELD2
VAS customer defined field 2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AVASPO
VAS generated item number
J_3AVASETE
VAS generated schedule line number
Segment E1J3AIX - VAS Ticketing / Labelling Text

Segment Field
Description
Comments / Remarks
J_3ATLTXT
Additional Text for

Ticketing/Labelling
Description or additional information can be

maintained for VAS Ticketing / Labeling as
additional text field.
SAP AFS
Page43
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

Segment Field
Description
Comments / Remarks
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 absolute 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_3AFIELD1
J_3AFIELD2
J_3AFIELD3
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

Segment Field
Description
Comments / Remarks
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_3AFIELD1
J_3AFIELD2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AUPDKZ
Update indicator
SAP AFS
VAS Processed Quantity
Page44
J_3AVASPO
VAS generated item

number
J_3AVASETE
VAS generated schedule

line number
3.3 Materials Management (MM)

The following sections contain information on the area of Materials Management.
3.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.
SAP AFS
Page45
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
Confirmation
Receipt
ORDRSP
/AFS/ORDERS04
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
ORDR
3.3.2 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.
3.3.2.1 Technical
(Purchasing)
Information:
Request
for
Quotation

Logical
Message
IDoc Type
Output type
Process
Code
Request for
Quotation
REQOTE
/AFS/ORDERS04
NEU (new)
ME12
Outbound
AFS-Specific Fields for the Request for Quotation

Segment
Field
Explanation
E1J3K03
IDDAT
AFS Indicator for IDoc date segment
SAP AFS
Origin
Page46
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 application
EKKO-BWBDT
009: Deadline for submission of quotations
EKKO-ANGDT
010: Quotation Date
EKKO-IHRAN
012: IDoc creation date
SY-DATLO
013: Binding period for quotation (valid to)
EKKO-BNDDT
014: Validity start date for outline agreement or request

for quotation
EKKO-KDATB
EKKO-KDATE
015: Validity end date for outline agreement or request

for quotation
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS
Indicator for the order acknowledgment requirement
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
Denominator for the conversion BPRME into BME
EKPO-BPUMN
BPUMZ
Numerator for the conversion BPRME into BME
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
EKPO-NETPR or KOMVKBETR
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR o.
KOMV-KWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
SAP AFS
Page47
E1J3AIM
EVERS
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
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
J_3AOBIDQF
AFS IDoc object identification (material number,...)
J_3ASIZE
AFS grid value
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
J_3AKSCAT
Stock Category
E1EDPO02 QUALF
BELNR
E1EDP19
IDDAT
AFS indicator for IDoc date segment
DATUM
IDoc: Date
QUALF
SAP AFS
EKET-J_4KSCAT
IDoc indicator reference document
J30: ALE Identifier

E1J3P03
EKET-J_3ASIZE
EKET-/AFS/ALE_ID.
EKPO-J_3ADAT
004: Delivery date
EKPO-J_3ADAT
EKPO-AGDAT
016: Reconciliation date for agreed cumulative quantity
EKPO-ABDAT
017: First firm/trade-off zone
SY-DATLO+EKPO-ETFZ1
018: Second firm/trade-off zone
SY-DATLO+EKPO-ETFZ2
IDoc object identification (for example, customer

material number)
Page48

IDTNR

EKET-J_3AVEMA
EKPO-IDNLF
EKPO-MATNR
EKPO-EMATN
3.3.3 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
3.3.3.1Technical Information: Purchase Order (Purchasing)

Logical
Message
IDoc Type
Output type
Process
Code
Purchase Order
ORDERS
/AFS/ORDERS04
NEU (new)
ME10
Outbound
AFS-Specific Fields for the Purchase Order

Segment
Field
Explanation
E1J3K03
IDDAT
E1J3K03
DATUM
IDoc: Date
SAP AFS
Origin
EKKO-BEDAT
EKKO-EINDT
004: Delivery date
EKKO-EINDT
EKKO-BWBDT
EKKO-ANGDT
010: Quotation Date
EKKO-IHRAN
SY-DATLO
Page49
EKKO-BNDDT
014: Validity start date for outline agreement or request for EKKO-KDATB
quotation
EKKO-KDATE
015: Validity end date for outline agreement or request for
quotation
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
EKPO-BPUMN
BPUMZ
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or
KOMV-KWERT
E1J3AIM
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
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
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
J_3AOBIDQF
J_3ASIZE
AFS Grid Value
SAP AFS
EKET-J_3ASIZE
Page50
J_3AIDTNR
E1EDP02

EKPO-EMATN
EKET-J_3AVEMA
EKET-J_3AVIEAN
EKET-J_3AVIEAN
EKET-J_3AUCCMR
J_3AKTEXT
IDoc short text
EKPO-TXZ01
J_3AKRCAT
J_3AKSCAT
Stock Category
QUALF
BELNR

J30: ALE Identifier
E1J3P03
E1EDP19
IDDAT
DATUM
IDoc: Date
QUALF
EKET-J_4KSCAT
EKET-/AFS/ALE_ID.
EKPO-J_3ADAT
004: Delivery date
EKPO-J_3ADAT
EKPO-AGDAT
EKPO-ABDAT
SY-DATLO+EKPO-ETFZ1
SY-DATLO+EKPO-ETFZ2
IDoc object identification (for example, customer material

number)
IDTNR

EKET-J_3AVEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
SAP AFS
Page51
3.3.4Purchase 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 packing information
Material text
Item texts
The following changes are possible at schedule line level:
Purchase order quantity

Requested delivery date
Dimension
Category
Tolerances are checked in the sequence schedule line, line, document.
3.3.4.1 Customizing: Purchase Order Change (Purchasing)

Special Customizing for Individual Messages: Purchase Order 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 individual fields at delete is set. In addition, table
T166C must contain the entry EKET /AFS/ALEID. You can maintain this in Customizing.
3.3.4.2 Technical Information: Purchase Order Change

(Purchasing)
Logical Message IDoc Type
Output type
Process Code
Purchase Order
Change
ORDCHG
NEU (new)
ME11
Outbound
/AFS/ORDERS04
AFS-Specific Fields for the Purchase Order Change

SAP AFS
Page52
Segment
Field
Explanation
E1J3K03
IDDAT
E1J3K03
DATUM
IDoc: Date
Origin
EKKO-BEDAT
EKKO-EINDT
004: Delivery date
EKKO-EINDT
EKKO-BWBDT
EKKO-ANGDT
010: Quotation Date
EKKO-IHRAN
SY-DATLO
EKKO-BNDDT
014: Validity start date for outline agreement or request for

quotation
EKKO-KDATB
EKKO-KDATE

quotation
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
EKPO-BPUMN
BPUMZ
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or KOMVKWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
SAP AFS
Page53
E1J3AIM
E1EDP02
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
EKPO-EVERS
BRGEW
Total Weight
EKPO-BRGEW
VOLUM
Volume
EKPO-VOLUM
VOLEH
Volume Unit
EKPO-VOLEH
J_3APOSNR
Item Number
EKET-ETENR or EKPOAFS_POSNR
J_3ASIZE
AFS grid value
EKET-J_3ASIZE
J_4KRCAT
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
J_3AOBIDQF
J_3ASIZE
AFS grid value
J_3AIDTNR

EKPO-EMATN
EKET-J_3AVEMA
EKET-J_3AVIEAN
EKET-J_3AVIEAN
EKET-J_3AUCCMR
J_3AKTEXT
IDoc short text
EKPO-TXZ01
J_3AKRCAT
J_3AKSCAT
Stock Category
QUALF
BELNR

J30: ALE Identifier
E1J3P03
EKET-J_3ASIZE
IDDAT
DATUM
IDoc: Date
SAP AFS
EKET-J_4KSCAT
EKET-/AFS/ALE_ID.
EKPO-J_3ADAT
004: Delivery date
EKPO-J_3ADAT
EKPO-AGDAT
EKPO-ABDAT
SY-DATLO+EKPO-ETFZ1
SY-DATLO+EKPO-ETFZ2
Page54
E1EDP19
QUALF

number)
IDTNR

EKET-J_3AVEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
3.3.5 Order Confirmation

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.
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-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.
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.
SAP AFS
Page55
3.3.5.1
Technical
(Purchasing)
Information:
Order
Confirmation

Document type
Direction
Purchase Order
Confirmation
Inbound
ORDRSP
Output type
/AFS/ORDERS04
Process Code
ORDR
AFS-Specific Fields for Order Confirmation

Segment
Field
Explanation
E1J3K03
IDDAT
E1J3K03
DATUM
IDoc: Date
Origin
EKKO-BEDAT
EKKO-EINDT
004: Delivery date
EKKO-EINDT
EKKO-BWBDT
EKKO-ANGDT
010: Quotation Date
EKKO-IHRAN
SY-DATLO
EKKO-BNDDT
014: Validity start date for outline agreement or request for

quotation
EKKO-KDATB
EKKO-KDATE

quotation
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or EKETMENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
EKPO-BPUMN
BPUMZ
EKPO-BPUMZ
SAP AFS
Page56
E1J3AIM
E1EDP02
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or KOMVKWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
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
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
J_3AOBIDQF
J_3ASIZE
AFS grid value
J_3AIDTNR

EKPO-EMATN
EKET-J_3AVEMA
EKET-J_3AVIEAN
EKET-J_3AVIEAN
EKET-J_3AUCCMR
J_3AKTEXT
IDoc short text
EKPO-TXZ01
J_3AKRCAT
J_3AKSCAT
Stock Category
QUALF
BELNR

J30: ALE Identifier
E1J3P03
EKET-J_3ASIZE
IDDAT
DATUM
IDoc: Date
SAP AFS
EKET-J_4KSCAT
EKET-/AFS/ALE_ID.
Page57
E1EDP19
QUALF
EKPO-J_3ADAT
004: Delivery date
EKPO-J_3ADAT
EKPO-AGDAT
EKPO-ABDAT
SY-DATLO+EKPO-ETFZ1
SY-DATLO+EKPO-ETFZ2

number)
IDTNR

EKET-J_3AVEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
3.3.6 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.
3.3.6.1 Technical Information: Contracts (Purchasing)

Document type
Direction
Output type
Process Code
Contract
Outbound
BLAORD
J3AV
/AFS/ME15
/AFS/BLAORD03
AFS-Specific Fields for Contracts

Segment
Field
Explanation
Origin
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
SAP AFS
Page58
KZABS

requirement
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
Denominator for the conversion BPRME into

BME
EKPO-BPUMN
BPUMZ
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
EKPO-NETPR or
KOMV-KBETR
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or
KOMV-KWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
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
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
3.3.7 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.
3.3.7.1 Technical Information: Contract Change (Purchasing)

SAP AFS
Page59
Output type
Process Code
Contract Change Outbound
BLAOCH
J3AV
/AFS/ME16
/AFS/BLAORD03
AFS-Specific Fields for Changing Contracts

Segment
Field
Explanation
Origin
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS
Indicator for the order acknowledgment requirement EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN
EKPO-BPUMN
BPUMZ
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
EKPO-NETPR or
KOMV-KBETR
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or
KOMV-KWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
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
EKET-J_4KSCAT
SAP AFS
Page60
J_4KSCAT
Stock Category
EKET-J_4KSCAT
3.3.8 Delivery Notification

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 be 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.
information:
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.
3.3.8.1
Technical
(Purchasing)
Information:
Delivery
Notification

Delivery
Notification
DESADV
Inbound
Output type
/AFS/DELVRY02
Process Code
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
SAP AFS
Page61
/AFS/E1EDL24
/AFS/E1J3AKG
E1J3AI2
E1J3AIM
J_3ABILTY
Invoice category of the vendor
/AFS/LANGUA_ISO
Language indicator for address
J_3ALNGR
AFS line group indicator
J_3ADEPM
Department
J_3AKVGR6
AFS additional data customer group 6
BEZEI6
Description
J_3AKVGR7
BEZEI7
Description
J_3AKVGR8
BEZEI8
Description
J_3AKVGR9
BEZEI9
Description
J_3AKVGR10
BEZEI10
Description
J_3AQFREF
J_3ABELNR
J_3APOSNR
Item Number
J_3AETENR
Schedule line number
J_3ADATUM
Date
J_3AUZEIT
Time
J_AZUDATR
Additional data
J_3AOBIDQF
AFS IDoc object identification (material

number,...)
J_3ASIZE
AFS grid value
J_3AIDTNR

E1JAIP
SAP AFS
J_3AKTEXT
IDoc short text
J_3AKRCAT
J_3AKSCAT
Stock Category
J_3ASTORE
MSO Stores
Page62
E1J3AIS
E1J3ABI
SAP AFS
J_3APTYP
VAS Packing Type
J_3APMAT
J_3ACHARC
VAS Charge Code
J_3AINCREM
VAS Packing: Increment
J_3AMIXIND
Mix ID for VAS packing types
J_3AFIELD1
VAS User-Defined Field 1
J_3AFIELD2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AUPDKZ
Update Indicator
J_3AVASPO
VAS Generated Subitem Number
J_3AVASETE
VAS Generated Sub-Schedule Line Number
J_3ASTORE
MSO Stores
J_3ASSTYP
VAS Special Services: Category
J_3ASSMAT
VAS Special Services Material
J_3ACHARC
VAS Charge Code
J_3AFIELD1
J_3AFIELD2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AUPDKZ
Update Indicator
J_3AVASPO
J_3AVASETE
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)
Page63
J_3ADERA
Degree of color difference (greener redder)
J_3ADERB
Degree of color difference (bluer yellower )
/AFS/LANGUA_ISO
Language ID
3.3.9 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).
3.3.9.1 Technical Information: Invoice Receipt and Verification

(Purch.)
information:
ALE ID
E1J3AI2: QUALF ("J30") BELNR(ALE-ID) or
Item
E1J3AI2: QUALF ("001")
J_3AETENR (schedule line)
J_3APOSNR (item)
J_3ABELNR
(document)
and
All available material-specific data (for example, size, 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
Invoice
Receipt
Inbound
/AFS/INVOIC02
INVOIC
Output Type
Process
Code
INVL
AFS-Specific Fields for the Invoice Receipt and Verification
SAP AFS
Page64
Segment
Field
Explanation
Origin
E1J3P01
POSEX
Item Number
EKPO-EBELP
PSTYP
Item Category
EKPO-PSTYP
KZABS

requirement
EKPO-KZABS
MENGE
Quantity
EKPO-KTMNG or
EKET-MENGE
MENEE
Unit of Measure
EKPO-MEINS
BMNG2
EKPO-KTMNG
PMENE
EKPO-BPRME
BPUMN

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

BME
EKPO-BPUMZ
ABFTZ
EKPO-ABFTZ
VPREI
Price (net)
EKPO-NETPR or
KOMV-KBETR
PEINH
Price Unit
EKPO-PEINH
NETWR
Value of Item (net)
EKPO-NETWR or
KOMV-KWERT
AENTW
EKPO-NETWR
NTGEW
Net Weight
EKPO-NTGEW
GEWEI
Weight Unit
EKPO-GEWEI
MATKL
IDoc Material Class
EKPO-MATKL
EVERS
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
EKET-J_4KSCAT
J_4KSCAT
Stock Category
EKET-J_4KSCAT
J_3ASTORE
MSO Stores
J_3APTYP
VAS Packing Type
J_3APMAT
J_3ACHARC
VAS Charge Code
J_3AINCREM
VAS Packing Increment
E1JAIP
SAP AFS
Page65
E1J3AIS
J_3AMIXIND
VAS Packing Mix Indicator
J_3AFIELD1
J_3AFIELD2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AUPDKZ
Update Indicator
J_3AVASPO
J_3AVASETE
J_3ASTORE
MSO Stores
J_3ASSTYP
VAS Special Services Category
J_3ASSMAT
VAS Special Services Material
J_3ACHARC
VAS Charge Code
J_3AFIELD1
J_3AFIELD2
J_3AFIELD3
J_3AVASPQ
Quantity
J_3AUPDKZ
Update Indicator
J_3AVASPO
J_3AVASETE
3.3.10 Inventory Management

As a rule, one of the first things you should carry out during the SAP system start-up is the
transfer of stock from a legacy system. This step is necessary because it is usually not possible
to manually create initial data in the SAP system due to the multitude of stocks, or because you
would like to post goods movements using IDocs.
You can transfer stock from external systems in one of two ways:
via direct input
via Application Link Enabling (ALE)
During the data transfer you can maintain all stock with all required data exactly as you would in
the dialog. If you use the data transfer with ALE, the data is transferred in an IDoc.
Typical application examples are:
The transfer of stock from an R/2 system or from external systems.

The transfer of goods movements from external systems.
SAP AFS
Page66
AFS special features

With the AFS IDoc type you can process goods movements of standard materials as well as
those of AFS materials. Only the inbound IDoc is implemented.
The mapping of the grid values using ALE works the same as in the dialog transaction. The
mapping of the categories also works the same as in the dialog transaction.
3.3.10.1 Technical Information: Inventory Management

Document type
Direction
Goods movement Inbound
Logical
Message
IDoc type
Process Code
WMMBXY
/AFS/WMMBID02
WMMB
AFS-Specific Fields for Goods Movement

Segment Field
Explanation
E1J3XYI
LFBJA
Fiscal year of a reference document (required field MSEG-LFBJA

for cancellations)
LFBNR
Document number of a reference document

(required field for cancellations)
MSEG-LFBNR
LFPOS
Item of a reference document (required field for

cancellations)
MSEG-LFPOS
J_3ASIZE
AFS grid value (required field for AFS material with MSEG-J_3ASIZE
dimensions)
J_3ABZUS
MSEG-J_3ABZUS
J_3AUANR
AFS group requirements
MSEG-J_3AUANR
J_3AUPOS
AFS origin main item
MSEG-J_3AUPOS
J_3AUEPS
AFS origin plan
MSEG-J_3AUEPS
J_4KSCAT
Stock category (required field for AFS materials

with category)
MSEG-J_4KSCAT
J_3AETENR
Schedule line number (required field for all

materials)
MSEG-J_3AETENR
J_3AVBELN
Sales document number
MSEG-J_3AVBELN
J_3APOSNR
Item number of the sales document
MSEG-J_3APOSNR
J_3ALINUM
Delivery number
MSEG-J_3ALINUM
J_3ALIPOS
Delivery item
MSEG-J_3ALIPOS
J_3AUMSIZ
AFS: receiving/issuing grid value (required field for MSEG-J_3AUMSIZ

stock transfer of AFS materials with grid values)
J_4KUMSCA
AFS: receiving/issuing stock category (required

field for stock transfer of AFS materials with
category)
J_4KUMSCA_4 AFS: receiving/issuing stock category

SAP AFS
Origin
MSEG-J_4KUMSCA
MSEG-J_4KUMSCA_4
Page67
Dialog Functions and their Support in ALE

When data is transferred using Application Link Enabling (ALE), it is subject to the same checks
as in dialog.
If a logical error caused by the material maintenance occurs when an IDoc is processed, the
system terminates the relevant maintenance transaction and the IDoc is assigned the
For IDocs with the status incorrect or successful, the application log receives the messages that
were output during processing. After the logical errors have been resolved, you can reprocess
Customizing for Distribution (ALE).
activate the system enhancement MWMIDO08

For more information, see the documentation BC Changes to the SAP
Standard.
create the necessary source text for the user exit EXIT_SAPLLMDE_002, which is
included in the system enhancement MWMIDO08
You can find further information in the system enhancement MWMIDO08 and
user exit documentation.
3.4 Planning and Production (PP)

The following sections contain information on Planning and Production (PP).
3.4.1 Master Data: Material BOM

For an integrated materials management and shop floor control, BOMs and work plans contain
critical basic or master data. In the engineering/design department the functional and production
conform design takes place for a new product to be produced. The results of this product phase
are drawings and a list of all necessary parts, the BOM.
BOMs are found in varying forms everywhere where end products are composed of several
basic parts or materials.
One of the steps you should carry out when you start up PP in the SAP system is the transfer of
BOMs from a legacy system. This step is required because it is not usually possible to create
initial data manually in the R/3 system due to the multitude of BOMs used.
Typical application examples are:
Transfer of BOMs from a non-SAP system


SAP AFS
Page68
You can use the new AFS IDoc type to create AFS material BOMs. Only material BOMs are
created. AFS does not currently support changing and deleting BOMs.
Mapping of Grid Values
Using ALE, grid values are mapped in the same way as in the dialog
transaction.
Mapping of Categories
Using ALE, categories are mapped in the same way as in the dialog
transaction.
3.4.1.1 Technical Information: Bill of Materials

Document
type
Direction
Logical
Message
IDoc Type
Process Code
Bill of material
Inbound
J3ABOM
J3ABOM01
J3AP
AFS-Specific Fields for Bills of Materials

Segment
Field
Explanation
Origin
E1J3ABG
MSGFN
Function
No processing
J_3APGNR
J_3ABOMD-J_3APGNR
J_3AKORDX
Grid value
J_3ABOMD-J_3AKORDX
E1J3ABC
J_3AKORDXL Grid value
J_3ABOMDJ_3AKORDXL
MEINS
Unit of Measure
J_3ABOMD-MEINS
MENGE
Quantity
J_3ABOMD-MENGE
J_3AZFLG
Quantity is zero
J_3ABOMD-J_3AZFLG
MSGFN
Function
No processing
J_4KSCAT
Stock Category
J_4KBOMC-J_4KSCAT
J_4KKZEXCL
Categories: excluding
indicators
J_4KBOMC-J_4KKZEXCL
J_4KKZINCL
Categories: including
indicators
J_4KBOMC-J_4KKZINCL
ALE
as in dialog.
If a logical error caused by BOM maintenance occurs when the IDoc is processed, the system
terminates the corresponding maintenance transaction and the IDoc receives the
SAP AFS
Page69
Using the following user exits, you can enhance the BOM creation function by adding your own
table fields. The data in the user-defined fields can also be processed using ALE.
Activate system enhancement J_3ABOM

For more information, see the documentation BC Changes to the SAP
Standard.
create the required source text for user exit EXIT_SAPLJ4AI_003 contained in system
enhancement J_3ABOM
3.4.2 Planning: Distribution of Requirements

With the IDoc /AFS/DISREQ01 you can exchange (export and import) the distribution of
requirements data between an AFS and a third-party system. This allows a third-party system to
access data that you defined with the function AFS Maintain Distribution of
Requirements (transaction J4A1).
The IDoc contains all data for the distribution of requirements with reference to a material or to a
material-independent distribution profile.
3.4.2.1 Technical Information: Distribution of Requirements

Technical description of the IDoc Type
Direction
Logical Message
IDoc Type
Operation code
Inbound and
Outbound
/AFS/DISREQ
/AFS/DISREQ01
/AFS/DISREQ
AFS-Specific Fields
Segment
Field
Explanation
Origin
/AFS/E1DR_HDR
STYPE
Distribution Type (material or profile)
Value determined by
generation program
SPROF
Distribution Profile
J_3APLPR-PROFP or
J_3ACAPR-PROFC or
J_3AGRPR-PROFG or
J_3APEPR-PROFT
SAP AFS
Page70
MATNR
Material
J_3APLPR-MATNR or
J_3ACAPR-MATNR or
J_3AGRPR-MATNR or
J_3APEPR-MATNR
/AFS/E1DR_TEXT
SP_M_DESCR
LANGU_ISO
Description of the distribution profile

or material
MAKT-MAKTX or
Language, ISO code
MAKT-SPRAS or
J_3ASPRT-SPRTX
J_3ASPRT-SPRAS
/AFS/E1DR_OVR
SPRTP
Profile Category
Value determined by
generation program
WERKS
Plant
J_3ACAPR-WERKS or
J_3AGRPR-WERKS or
J_3APEPR-WERKS
RCATE
J_3AGRPR-RCATE or
J_3APEPR-RCATE
SEASO
Validity for Presizing
J_3APLPR-SEASO or
J_3ACAPR-SEASO or
J_3AGRPR-SEASO or
J_3APEPR-SEASO
VERSB
Version Number of the Distribution of

Requirements
J_3APLPR-VERSB or
J_3ACAPR-VERSB or
J_3AGRPR-VERSB or
J_3APEPR-VERSB
PRGRS
Date Type (day, week, month, time

period)
J_3APEPR-ENTLI
ENTLUE
Period Indicator
J_3APEPR-ENTLI
converted with table TPRG
COVST
Coverage Strategy
J_3ACAPR-COVST
Material Grid Number
MARA-J_3APGNR or
/AFS/E1DR_PGHD J_3APGNR
J_3ASPR-MGRID
SAP AFS
J_3AVDAT
Material Grid Valid from date
J_3AGRPR-VDATE
J_3ABZD1
ID of the first dimension
J_3APGHD-J_3ABZD1
J_3ABZD2
ID of the second dimension
J_3APGHD-J_3ABZD2
Page71
J_3ABZD3
/AFS/E1DR_PLPR
ID of the third dimension
J_3APGHD-J_3ABZD3
J_3ABZD1_NEW ID of the first dimension
J_3APGHD-J_3ABZD1
J_3ABZD2_NEW ID of the second dimension
J_3APGHD-J_3ABZD2
J_3ABZD3_NEW ID of the third dimension
J_3APGHD-J_3ABZD3
WERKS
Plant
J_3APLPR-WERKS
FLWEI
Distribution Profile Weight
J_3APLPR-FLWEI
PERCE
Distribution Profile Percentage
Value determined by
generation program
SISQU
Quantity of the last SIS selection
J_3APLPR-SISQU
ISOCODE_UNIT
Base Unit of Measure
J_3APLPR-MEINS
Function:
J_4KG_GET_VALID_CAT
/AFS/E1DR_CAPR RCATE
Parameter:
J_3ACAPR-WERKS,
J_3ACAPR-COVST,
R and PRC
FLWEI
J_3ACAPR-FLWEI
PERCE
Value determined by
generation program
SISQU
J_3ACAPR-SISQU
ISOCODE_UNIT
J_3ACAPR-MEINS
Grid value
J_3APGEN-J_3AKORDX
J_3AKORD1
AFS: Coordinates of the first

dimension
J_3APGEN-J_3AKORD1
J_3AKORD2
AFS: Coordinates of the second

dimension
J_3APGEN-J_3AKORD2
J_3AKORD3
AFS: Coordinates of the third

dimension
J_3APGEN-J_3AKORD3
FLWEI
J_3AGRPR-FLWEI
PERCE
Value determined by
generation program
SISQU
J_3AGRPR-SISQU
ISOCODE_UNIT
J_3AGRPR-MEINS
Period Part
J_3APEPR-PPART
FLWEI
J_3APEPR-FLWEI
PERCE
Value determined by
generation program
SISQU
J_3APEPR-SISQU
/AFS/E1DR_GRPR J_3AKORDX
/AFS/E1DR_PEPR PPART
SAP AFS
Page72
ISOCODE_UNIT
/AFS/E1DR_DITX
J_3ABZD1_NEW
J_3APEPR-MEINS
J_3APGHD-J_3ABZD1 or
J_3APGHD-J_3ABZD2 or
J_3APGHD-J_3ABZD3
J_3ABEZT
Description of the dimension
J_3ADITY-J_3ABEZT
LANGU_ISO
Language, ISO code
J_3ADITY-J_3ASPRA
Material number
Generated from MARA

and MARC
WERKS
Plant
Generated from MARA

and MARC
IDPL
Indicator: Distribution of
Requirements to Plants
Value determined by
generation program
IDCA
Requirements to Categories
Value determined by
generation program
IDGR
Requirements to Grid Values
Value determined by
generation program
IDPE
Requirements to Periods
Value determined by
generation program
MSGFN
Function
No processing
SPRAS
Language Key
MAKT-SPRAS
MAKTX
Description of the Material
MAKT-MAKTX
SPRAS_ISO
Language, ISO code
MAKT-SPRAS
WERKS
Plant
J_3ASEAS-WERKS
SEASO
Validity Period for Presizing
J_3ASEAS-SEASO
NPERI
Number of Occurrence
J_3ASEAS-NPERI
DATE_FROM
Date starting on which the validity

period applies
J_3ASEAS-DATE1
DATE_TO
Date up to which the validity period

applies
J_3ASEAS-DATE2
PRGRS
Date Type (day, week, month,

interval)
J_3APEPR-ENTLI
PRGBZ
External Date Type
TPRG-PRGBZ
PRGTX
Description of the Date Type
TPRG-PRGTX
PRITX
Period description in printout
TPRG-PRITX
LANGU_ISO
Language, ISO code
TPRG-SPRAS
/AFS/E1DR_USED MATNR
E1MAKTM
/AFS/E1DR_SEAS
/AFS/E1DR_PRG
Remember that there are seven user exits for the IDoc /AFS/DISREQ01. You can find a
description of these user exits in the enhancement J_3ADREQ. To see the relevant
documentation, call transaction SMOD.
SAP AFS
Page73
3.4.3 Shop Floor Control: Confirmations

SAP provides the automatic data transfer via IDoc (type CONF21) for the confirmation of
production orders from subsystems.
For AFS confirmations, SKU data must also be transferred. The SKU data is stored in
segment /AFS/CONF21. When the IDocs are processed, the data is stored temporarily in table
RUECK and the AFS data table /AFS/RUECK.
Data can be transferred automatically when the IDoc is received. We advise against this,
however, as most of the subsystems can only send one confirmation per IDoc. The processing
of the confirmation is therefore usually scheduled as a job using report CIBDVERB to provide
specific support to mass data processing.
Actual confirmation processing occurs as mass processing in the same way as the dialog
transaction. The same checks are also run.
Overview: The AFS IDoc type can be used to create AFS confirmations.
Mapping grid values: The mapping of the grid values using ALE works the same as in
the dialog transaction.
Mapping categories: Categories cannot be entered.
Cancellation of confirmations: A cancellation of confirmations per IDoc is not possible.
3.4.3.1 Technical Information: Confirmations

Logical Message
IDoc type
Process Code
Confirmation
CONF21
/AFS/CONF21
CON2
Inbound
AFS-Specific Fields for Confirmations

Segment
Field
Explanation
Origin
AFS grid value
/AFS/RUECKJ_3ASIZE
J_3AMKID
Marker indicator in planned

orders/production orders
/AFS/RUECKJ_3AMKID
J_3AMKNR
Marker number
/AFS/RUECKJ_3AMKNR
J_3AMSECT
Marker section
/AFS/RUECKJ_3AMSECT
J_3ALMNGA
Yield IST in ASCII
/AFS/RUECKJ_3ALMNGA
/AFS/E1MARKER J_3ASIZE
SAP AFS
J_3AXMNGA Scrap quantity IST in ASCII
/AFS/RUECKJ_3AXMNGA
J_3AMEINH
/AFS/RUECKJ_3AMEINH
Unit of Measure
Page74
For technical reasons, you are required to use unique marker indicators for each size for
production orders that were created with markers. (The marker indicators are created based on
the field contents of the marker ID, marker number and marker section.) If this is not done, the
data record cannot be uniquely identified in the database.
The reason for this is that the markers in the production order are identified internally using a
sequence number. In the case of the IDocs, however, only the user ID can be used.
ALE
as in the dialog.
If a logical error caused by confirmation maintenance occurs when processing the IDoc, the
system terminates the corresponding maintenance transaction and the IDoc receives the
Note that the PDC data records should be posted later to ensure that this is done efficiently.
This can be done manually using the menu option or automatically in a batch job. You can
configure your system via Customizing settings to ensure that the data records are posted
immediately. We would recommend, however, that you do not do this to ensure that data and
performance are not negatively affected. IDoc handling only creates the data records. You must
process errors that occur when posting is done subsequently, using the error handling function
for confirmations.
3.5 Warehouse Management

The following logical messages are supported in warehouse management in AFS:
Action/Object
Logical Message
IDoc Type
Transfer orders (issue and receipt)
WMTORD
/AFS/WMTOID01 for the issue

WMTOID01 for receipt
Transfer requirements (receipt)
WMTREQ
WMTRID01
Confirmation of transfer orders

(receipt)
WMTOCO
WMTCID02
Cancellation of a transfer order

(issue and receipt)
WMCATO
WMCAID01
Create physical inventory (receipt)
WMINVE
WMIVID01

SAP AFS
Page75
Before using WM IDocs, ensure that each batch is assigned to a grid value and a category
(SKU). In all inbound IDocs, the batch number is a required field and must be transferred in the
IDoc.
4. Archiving AFS Data

The following sections contain descriptions of the standard archiving objects that have been
enhanced for AFS, and information on AFS grid archiving.
The enhancements are limited to additional archiving of AFS-specific database tables for the
relevant SAP standard database tables. This means that AFS tables are archived along with the
standard tables, if necessary.
Archiving in AFS is carried out using the standard objects and standard tools. However, there is
an AFS-specific archiving object for grid archiving.
Example: Archiving material master data
Material master segments A and C (MARA and MARC) are archived using this archiving object.
The following AFS tables are updated in the application along with the two standard tables, and
must also be archived along with the standard tables:
Standard table
AFS tables
MARA
J_3AQDST
J_3AMSEA
SAP AFS
Page76
J_3AGMD
MARC
J_3AMAD
J_3AMADKA
J_3ATRAME
For application-specific information on archiving, please see the SAP library under CrossApplication Components Archiving Application Data, then the relevant application area, for
example, Logistics General (LO) or Materials Management (MM).
For general information on archiving, visit the SAP Marketplace at http://sapnet.sap.com/dataarchiving.
4.1 Archiving AFS Data in SD

AFS tables are archived in MM for order processing, billing, and delivery note processing.
The relevant AFS tables are listed below for the respective archiving object.
Archiving Object SD_VBAK (Orders/Documents: Standard Tables VBAK and VBAP)
J_3ABOML
BOM additional item data MM/SD (application V1)
J_3AMSO
Multi-store order (MSO)
J_3AVBUE
SD status for schedule lines
J_3AVBFAE
Sales document flow for schedule line
With application V1
J_3AVATL
VAS: ticketing/labeling data in sales order
J_3AVAP
VAS: packing data in sales order
J_3AVATLX
VAS: ticketing/labeling data additional text data in sales order
J_3AVASSO
VAS: special services data in sales order
Affected programs (AFS-enhanced):
S3VBAKWR write and archiving program

S3VBAKDL delete program
S3VBAKRL reload program
Archiving Object SD_VBRK (Billing/Invoices: Standard Tables VBRK and VBRP)

J_3AVBUE
SD status for schedule lines
J_3AVBFAE
Sales document flow for schedule line
With application V3
J_3AVATL
VAS: ticketing/labeling data in order
J_3AVAP
VAS: packing data in order
SAP AFS
Page77
J_3AVATLX
VAS: ticketing/labeling data additional text data in order
J_3AVASSO
VAS: special services data in order
S3VBRKWR write and archiving program

S3VBRKDL delete program
S3VBRKRL reload program
Archiving Object SD_LIKP (Deliveries: Standard Tables LIKP and LIPS)

With application V2
J_3AVATL
VAS: ticketing/labeling data in order
J_3AVAP
VAS: packing data in order
J_3AVATLX
VAS: ticketing/labeling data additional text data in order
J_3AVASSO
VAS: special services data in order
S3LIKPWR write and archiving program

S3LIKPDL delete program
S3LIKPRL reload program
4.2 Archiving AFS Data in MM

AFS tables are archived in MM for purchasing documents/ purchase orders, purchase
requisitions, and in the material master (segments A and C).
Affected development classes: J3AS and J3AZ.
The relevant AFS tables are then listed for the respective archiving object.
Archiving Object MM_EKKO (Purchasing Documents/Orders: Standard Tables EKKO and
EKBE)
J_3ABSSI
AFS stock (SKUs) stock type B
J_3ABDSI
AFS order (SKUs) requirements type LB (subcontracting) and TB (stock

transfer), plan type B
J_3AWESBS
AFS goods receipt: blocked stock at SKU level
J_4AFLELKPO
AFS: Subitem in AFS contract
RM06EW30 write and archiving program

RM06ED30 delete program
Archiving Object MM_EBAN (Purchase Requisitions: Standard Table EBAN)

SAP AFS
Page78
J_3ABSSI
AFS stock (SKUs) stock type A
J_3ABDSI
AFS order (SKUs) requirements type LB (subcontracting)

and TB (stock transfer), plan type A
RM06BW30 write and archiving program

RM06BD30 delete program
Archiving Object MM_EINA (Purchasing Info Records: Standard Table EINE)

J_3AVIET
AFS vendor info record: SKU information
RM06IW30 write and archiving program

RM06ID30 delete program
Archiving Object MM_MATNR (Material Master: Segments A and C)

MARA
J_3AQDST
AFS material master: quota category for destination
J_3AMSEA
AFS material master: seasons
MARC
J_3AMAD
AFS material master: additional data
J_3AMADKA
AFS material master: valuation data
J_3ATRAME
AFS material master: stock in transit at SKU level
MLGN
/AFS/MLGN1
Material data for each warehouse number: dimension-specific
/AFS/MLGN2
Material data for each warehouse number: season-specific
/AFS/MLGN3
Material data for each warehouse number
MLGT
/AFS/MLGT
Material data for each warehouse type
MVKE
/AFS/MVKE
AFS sales data for material
MARM
/AFS/MARM
Units of measure for material
Affected programs/function groups (AFS-enhanced):
Function group WSO8

Function module REORGANISATION_MATERIAL
Programs WSREOnnn (nnn for sequence number)
SAP AFS
Page79
4.3 Archiving AFS Data in PP

AFS tables are archived in PP for:
Production orders (AFKO/AFPO)

Confirmations (AFRU)
Operations (AFW)
Reservations (RESB)
Routings (PLKO)
BOMs (STKO/STPO)
Affected development classes: J3AP, J4KP, and J3AZ.

The relevant AFS tables are then listed for the respective archiving object.
Archiving Object PP_ORDER
AFKO/AFPO (production order)
J_3ABSSI
AFS stock (SKUs) stock type F
J_3ABUNDL
AFS bundles for production orders
AFRU (confirmation)
J_3ABUAFRU
AFS order completion confirmations for bundles
AFVV (operation)
J_3ABUAFVV
AFS structure of bundles in the operation
RESB (reservation)
J_3AFSRESB
AFS: additional data for production order (RESB)
J_3ABDSI
AFS order (SKUs), stock type FA (production

order), plan type F
SAPLCOAH (COAH) archiving and delete program: order header

SAPLCOAK (COAK) archiving and delete program: completion confirmations
SAPLCOAO (COAO) archiving and delete program: operations
SAPLCOAM (COAM) archiving and delete program: components/reservations
The actual archiving programs (PPARCHP1/preparation program, PPARCHA1/archiving

program) were not/did not need to be enhanced here.
Archiving Object PP_PLAN (Routings: Standard Table PLKO)
SAP AFS
Page80
J_4KPLKOC
AFS categories

SAPLCPRE (CPRE) archiving and delete program
The actual archiving programs (RCPREWR1/archiving program, and RCPREDE1/deletion
program) were not/did not need to be enhanced here.
Archiving Object CS_BOM (BOMs: Standard Tables STKO and STPO)
J_3ABOMD
AFS BOMs: additional SKU data for items
J_4KBOMC
AFS categories for BOM items
RCSARCH1 write and archiving program

RCSARCH2 delete program
RCSARCH3 evaluation program
4.4 Grid Archiving in AFS

Material grids are archived as in standard archiving, that is, you use the same tools and
transactions to prepare and start archiving (SARA, for example).
If you are archiving grids for the first time, it is important that you carry out extensive tests
before you use the function productively.
AFS Grid Archiving: Archiving Object J_3AGRID

Tables
J_3APGHD
Grid header
J_3APGEN
Grid items
J_3APGTX
Grid texts for items
Programs
J_3AGRIA
Archive grids
J_3AGRID
Delete grids
J_3AGRIR
Reload grids
The above programs provide detailed documentation on the scope of functions in grid archiving
and how to carry it out.
SAP AFS
Page81
5. Mapping
The aim of mapping is to arrive at the most accurate distribution profiles for a material or set of
materials based on historical sales data. In the AFS system mapping means to copy SKU data
with quantities and periods from SIS into distribution profiles. The system uses the total
quantities for certain SIS data to calculate the corresponding ratios in the distribution profiles.
Mapping enables you to create an accurate distribution profile based on any desired
combination of SIS data for materials, plants, categories, grid values and periods.
Features
You can save the information about which source criteria you want to base a distribution profile
on in variants and any particular emphasis of certain criteria inmapping profiles.
The S430 info structure has been enhanced with SKU fields.
When defining the periods for the SIS source data you can use presizing validity
periods or enter time intervals.
You can also set up mapping to run as a batch job by creating a variant in MultiProfile Mapping.
When maintaining distribution of requirement versions you must also take into
account that they determine which SIS interface variant is used in mapping.
Procedure
There are two main transactions to carry out mapping:
You can use the SIS interface in distribution profile maintenance for single profile
mapping. If you access mapping from distribution profile maintenance you can only copy
the SIS data to that particular distribution profile version and context which you are
maintaining, such as distribution profile periods-00001version 00 for periods in
plant 0002.
You can use Multi-Profile Mapping for mass processing to compute all of the relevant
distribution profiles for multiple materials according to all 4 criteria at once.
Prerequisites
You must set up SIS and record sales quantities to use as a source.
You must have created a distribution profile for the target material or grid, made an entry
and saved. When mapping you overwrite any entries in distribution profile.
5.1 Mapping Profiles

Mapping Profiles
If you want to base your target distribution profile on a differing set of quantities in SIS other
than those specified in the distribution, you can create mapping profiles. That is if you want to
create a distribution profile for grid values for material B and base it on material A in SIS you
have to create a material mapping profile to assign material B to material A in the mapping
process. This tells the system that when performing the mapping calculation it is to look at an
alternative material to base the calculation on. You could similarly base a plant mapping profile
for plants 0010 and 0011 on plants 0001 and 0002. You can define a ratio within the mapping
profile as to how the system should handle the SIS quantities. In this case you could use the
following ratio:
Target Plant
Source Plant
Percentage
0011
0001
105%
0012
0002
100%
SAP AFS
Page82
The system reads the actual SIS quantities for plants 0001 and 0002 and then adds 5% to 0001
and then copies the ratio to the distribution profile for plants 0011 and 0012.
You can base a distribution profile for plants (winter-plants) on the SIS quantities for all
materials during a certain period from the previous year and emphasize the quantities found for
plant 0002 by 10% and reduce 0003 by 10% in the plant mapping profile (plant 0001 - 100%,
plant 0002 - 110%, plant 0003 - 90%).
You only need mapping profiles when there is not a one-to-one relationship between the data in
SIS and in the distribution profile. That is, for example, if you have the same grid values for the
source material in SIS and the target material, you do not need to define a mapping profile for
grid values. The system only needs a mapping profile to define any deviations in the
relationships between characteristics to map.
The goal of mapping to arrive at a ratio between certain criteria for the distribution profiles. If you
create new grid values or plants there is no way to base the new ratio on the old. You must run
mapping for all old values and then manually define how the new values such as plants or grid
values appear in relation to the others in the distribution profiles.
Grid Value Mapping Profile
White is a new grid value and is to be based on red.
Target Grid Value
Source Grid Value
Percentage
Blue
Blue
100%
Green
Green
100%
Red
Red
100%
White
Red
100%
Results based on SIS Quantities and Mapping Profile

SIS Grid Values
SIS Quantities
Profile
Qty after Profile Result
Blue
1000
Blue
1000
25%
Green
1000
Green
1000
25%
Red
1000
Red
1000
25%
White
1000
25%
Period selection data for the source must be maintained completely. If a validity period
is not found in the reference mapping profile, no data will be selected.
Names of mapping profiles are unrelated to the names of distribution profiles.
You cannot have differing grids for the source and target material, but you can have grid
values in the target which differ from the grid values in the same grid in the source.
You cannot assign categories in one coverage strategy to one in another coverage
strategy.
5.2 Multi-Profile Mapping
SAP AFS
Page83
To carry out mapping, you can use the SIS Interface from the distribution profile maintenance or
use the Multi-Profile Mapping for mass processing. The latter gives you the option of carrying
out mapping for multiple distribution profiles simultaneously. This is useful when updating
mapping regularly. To use this function, you need to select the mapping criteria as to whether
mapping is to be based on materials or grids and the distribution of requirements version. The
distribution of requirements version contains all important data on the source and targets. In this
mass calculation transaction, you enter the distribution profile version that the system uses to
determine the mapping variants (AFS Customizing). The system then uses these mapping
variants to determine the relevant mapping profile and target distribution profiles. You must
maintain the distribution of requirements versions and profiles in order to carry out this
transaction.
The figure below shows the relationship between the individual objects in the mapping process:
The main difference between using mass processing to perform mapping and using the SIS
Interface from distribution profile maintenance is that in the mass processing screen, the
distribution profile version determines the target distribution profiles, and in individual mapping
you enter the target information when maintaining the distribution profile to be mapped.
For more information on the distribution of requirements versions, see Mapping and the IMG
text for SIS in AFS Customizing.
5.3 Carrying Out Single Profile Mapping

Defining the Target
The link between distribution profiles and mapping for single distribution profiles in distribution
profile maintenance is based on all of the entries by category, period, plant, material or master
grid and also the distribution profile versions. The system first checks for relevant mapping
profiles to determine how to adjust the quantity data taken from SIS in the mapping calculation
and if no mapping profile is found, the system uses a one-to-one ratio between criteria. That is,
the system assumes you want to based material 001 on the SIS data for material 001, for
example, and category 001 on category 001 in SIS etc. You can also define mapping profiles to
provide an alternative source for the current target.
Source Data
You define the distribution profiles by the target (material or grid) and then access the SIS data
for source data. You can limit the selection of SIS data as the source to any particular
combination of data. You can also use variants and save them in distribution profile versions to
save the source. If you use a different source other than the target you must create a mapping
profile to define the relationship between the two items.
You must enter a time period for the source data but all other entries are only necessary if you
want to limit the selection data. If you make no entries for the plant, for example, the system
takes all SIS data for all relevant plants for the current context of the distribution profile.
The system uses the version of the distribution profile to access any entries in
Customizing Maintain selection variant for SIS interface for further interpreting the SIS
quantities. Refer to the IMG text for more information.
SAP AFS
Page84
SIS Interface Data Flow for Single Profile Mapping

The following illustration depicts how the system determines the correct source data based on
the context and distribution of requirements version. The criteria is which type of distribution
profile you maintain such as for grid values. The context defines which distribution profile the
system is to copy the results of the mapping calculation to. The distribution of requirements
version defines the source (material) or you can enter the source manually.
6. Distribution Profile
Distribution profiles are templates, which you can, for example, apply to materials when trying to
determine the SKU data for a material quickly and easily. If you have a quantity for an AFS
material and want to specify the SKU data for a purchase order, for example, you can carry out
presizing based on distribution profiles to speed up the process and maintain accuracy. You
can create distribution profiles based on historical data by using mapping. Distribution profiles
are either material-dependent or material-independent. You can manage distribution profiles for
the ratio of an AFS material in multiple plants according to the validity period and version. You
can only use distribution profiles for plants, categories and periods in conjunction with AFS
planned independent requirements.
The system offers the following levels for maintaining distribution profiles:
Plants
Version
Validity Period
Categories
Plants
SAP AFS
Validity Period
Version
Page85
Grid values
Plants
Validity Period
Version
Category
Periods
Plants
Validity Period
Version
Category
Period Part
You can manage distribution profiles at client or material level. That is, you define which
distribution profile the system is to use by defining which distribution profiles are valid for a
particular plant and category, for example, and which are valid for the entire client if no specific
plant version exists.
In a distribution profile, you determine a relationship for a particular AFS material or set of
materials with the same grid between multiple
Plants
Categories
Periods
Grid values
After carrying out presizing and copying a quantity from material level to SKU level in an
application such as the purchase order, you can make manual changes to the quantity.
Presizing describes how to bring a quantity from material level to SKU level, based on the
relevant distribution profiles but does not prevent you from making exceptions and overriding
the quantities at SKU level after presizing has run. The distribution profile is therefore only a
template for breaking down material quantities to SKU level. You can also make changes to the
distribution profiles themselves at any time and at any level.
Distribution profile versions also play a decisive role in mapping.
Prerequisites
You must create valid versions and validity periods for distribution profiles in AFS Customizing.
Features
You can maintain default distribution profile versions for presizing to access the following three
levels (material level has the highest priority and client level the lowest):
Material Master and Plant Level AFS MRP view
Material Master Level AFS Basic Data
Client Level Customizing
You can override the default distribution profile when accessing presizing from planned
independent requirements maintenance. You cannot override the default distribution profile in
Purchasing.
By accessing Input Help for material-independent distribution profiles, you gain an overview of
which profiles have been maintained for categories, grid values and so on.
7. Presizing
Various forms of presizing are supported in the following areas:
SAP AFS
Page86
PP Planned Independent Requirements, MRP (safety stock and procurement

proposals)
Purchasing documents (for grid values)
SD sales orders
Presizing in Planned Independent Requirements

Presizing lets you automatically spread requirements based on distribution profiles to different:
Plants
Categories
Periods
Grid values
This can be done without distribution profiles or increasing certain factors, for example,
categories, grid values or periods.
When you carry out presizing, the system searches for the relevant distribution profile based on
the plant and category for one or more materials, recalculates the quantities based on the
distribution profile, then rounds all values according to the settings. From the maintenance
transaction for the planned independent requirements, you can manually choose a rounding
strategy, distribution profile per factor and target period, for example, when running presizing in
the system. If no corresponding distribution profile version is determined for a factor, the
requirements are evenly distributed for the valid factor (for example, plant, category, period and
grid value). When running presizing in your system, you can also change the requirement
quantities by using all four factors at the same time. You can determine different distribution
profile versions for each individual factor.
You can copy requirements to new versions of the planned independent requirements as soon
as presizing has been run in the system. Alternatively, you can replace existing versions. You
can also work with requirement plans.
Presizing for Single or Multiple Materials
There are two main methods for running presizing for planned independent requirements. You
can access presizing from planned independent requirements maintenance, or carry out
presizing for multiple materials.
You can use distribution profiles to define customers purchasing behavior, for example. If
customers usually purchase more goods at the end of the week, you can define the distribution
profile to put more weigh on delivery dates at the end of the week or you can distribute more
quantities to a certain plant or category.
Planned Independent Requirement Versions
You can maintain different versions of planned independent requirements and run presizing for
all versions together or for each version separately.
Prerequisites
You have to assign a default distribution version for all applications that use presizing. The
default version can be assigned at client or plant level (in Customizing) or in the material master
record.
Example: Presizing for Planned Independent Requirements for Plants
SAP AFS
Page87
In this example, you define a distribution profile to define the requirements for individual plants.
When you carry out presizing in the maintenance function for planned independent
requirements, you must define the plants and categories. You can, however, choose if you also
want to run presizing for grid values and periods.
8.
Categories
AFS materials are based on a large volume of data. To order this data volume, AFS uses
categories. Categories are used to logically segment materials. You can enter a specific
schedule line for a material per grid value. You can distinguish a material by color and size, for
example. Using categories you can also order the grid values at different quality levels,
customer segments, and countries of origin.
SAP AFS
Page88
Features
There are two types of categories:
Requirements categories
Stock categories
Requirements categories are important in Sales, for example in sales orders, planned
independent requirements, and dependent requirements.
You can subdivide your requirements into the following criteria: quality and customer segment.
Incoming requirements, for example sales orders, are divided by the requested quality 001, 002,
or 003, and by customer segment A, B, or C.
Stock categories are used for the logical distribution of the existing and planned stock.
Therefore stock categories are assigned both to the physical stock and the procurement
proposals, such as planned orders, production orders, purchase requisitions, and purchase
orders.
You segment your stock by the same criteria as the requirement, by quality and country of
origin, for example. You subdivide your stock into different quality levels 001, 002 or 003 and
into countries of origin, for example, Australia, Canada, and Germany.
The categories influence the entire logistic chain. You can include or exclude components in the
bill of material or processes from routing on the basis of categories.
The difference between grid values and categories should be emphasized at this point. You
assign a certain grid to a material in the material master. The grid values defined here are
assigned to this material and do not change during the entire logistic process.
You assign categories to a material using the category 'structure' and the Coverage Strategy in
the material master. Within the coverage strategy you define the sequence in which the stock
categories satisfy the requirements categories. Depending on availability, the system assigns
different stock categories to the requirements categories in the defined sequence, meaning that
the category can change in the logistic process.
SAP AFS
Page89
8.1 Category Structures

Categories have their own structure which you define in Customizing. You can create different
category structures and assign them to materials depending on the material type, for instance.
8.2 Coverage Strategy

To efficiently plan your requirements it is necessary to fulfill newly arising requirements (such as
sales orders) with the existing or future stock (for example purchase requisitions). If you have
defined categories for your material you can assign the stock to the requirements using these
categories. The coverage strategy determines how the requirements categories are assigned to
the stock categories. This assignment takes place during the availability check, the MRP and
the allocation run.
The coverage strategy is also important for the following requirements elements and stock
elements and their MRP-relevant procedures:
For internally and externally procured materials during the planning run. That means
during the creation of planned orders and purchase requisitions.
For their components. That is, the dependent requirements and the fulfillment of those
requirements.
For the consumption of the planned independent requirements by means of the actual
customer requirements during the planning run.
Features
During the planning run, the system determines which requirement categories can be covered
by which stock categories. You can specify a certain sequence for the above mentioned stock
and requirements elements and their MRP-relevant procedures.
For example, you determine the following sequence for your categories using your coverage
strategy: You receive a requirement, such as a sales order, for category 001A. Category 001A
includes the following information: The customer requesting the requirement belongs to your
customer segment A. This customer has a requirement for quality 1 (which is the best quality).
Using the coverage strategy, you define that this customer will receive the requested category
first if you have the category in stock. If the requested category is not in stock, you decide that
the customer will then receive the next lower quality.
Using the coverage strategy, you can uniquely assign the stock to the requirement in the MRP
run. You can read the status of the assignment of the requirements categories to the stock
categories after a planning run in the MRP list using the MRP status.
SAP AFS
Page90
For example, the MRP status T (temporary) means that a requirements category is temporarily
assigned to a stock category. A sales order that arrives later and is subject to an earlier
requirements date than the sales order that has already been planned, can be reassigned to the
already planned stock. The assignment of a requirements category to a stock category is not
fixed until after the allocation run. This requirement is then open for the delivery.
You define your coverage strategy in Customizing. You assign the coverage strategy to a
material in the material master in the AFS Basic Dataview at client level. If you set the AFS
status, no other coverage strategy can be assigned to this material.
9. Material Grids
You use material grids to determine the characteristic values in which you carry a material within
the entire logistics. The mapping of your AFS materials in the form of grid values simplifies the
maintenance of large volumes of data.
Features
This is a basic enhancement of the material master that affects the entire chain of logistics. AFS
materials are processed and valuated using their grid data in:
Production Planning in the processing of planned orders

Materials Management in inventory management
Sales and Distribution in sales order processing
9.1 Material Grids: Overview

You use material grids to map each of your materials in all of its characteristic values in the
system.
There are different grid types available in AFS:
SAP AFS
Page91
Prerequisites
You have defined characteristics by going to the SAP Easy Access screen for
characteristics
and
choosing Cross-Application
Components Classification
System Master Data Characteristics (Transaction CT04) and assigned them
characteristic values.
Features
Grid structure
You determine the structure of your grids in the AFS system using dimensions. A maximum of
three dimensions is allowed of which the total length must not exceed eight characters. You
form grid values using a combination of individual dimension values
For your material jeans which you carry in various colors, (waist) sizes, and lengths, you create
a three-dimensional grid from the dimensions color, size, and length. In the header lines of your
grid you enter the individual dimension values that are relevant for your material - color shades,
individual sizes, and different lengths. By combining these dimension values, you enter the grid
values of your material. A valid grid value of your jeans could in this case be RED3432.
Grids in the Application
Using the one time assignment of a master grid to a material, you specify the grid values in
which this material can occur. This assignment applies as long as you carry your material.
The actual control of your material takes place via grids. You can thus maintain sales and
purchasing related condition records, for example, using master grids and application grids.
Using the application grids you can also specify which grid values you want to have in stock or
sell in which season.
You specify the valid application grids for your material depending on the master grid for the
material. In contrast to the master grid, you can replace the application grids of your material
with other ones. Only grids that are based on the master grid of the material are permitted. You
enter the reference between application grids and materials via grid control data.
Grid views
Grid values for AFS materials are entered, maintained, and processed in logistical processes
such as MRP, sales order processing, and others using two views:
In the line entry view the system lists the grid values vertically from top to bottom. You
can determine which values are listed at the top by defining sorting sequences for the
individual dimension values. For example, you use this view for the availability check.
In the grid entry view, the system shows the grid values in the pattern, that is, how you
have combined them in the grid maintenance. For example, you use this view to enter
quantities in the sales order.
Activities
To create grids, go to the SAP Easy
Functions Grids Material Grid Create
Access screen
and
choose AFS
Central
Follow the steps below:

SAP AFS
Page92
1.
2.
3.
Create grid dimensions.

Create a grid.
Assign the grid to the material master.
9.1.1 Master Grids

You use the master grid to enter all grid values in which a material can occur.
Features
You define one master grid for each of your AFS materials in the AFS Basic Data view in the
material master. Once you have confirmed this assignment, you can no longer replace the
master grid with another one.
The master grid is valid across all plants for your material. Using the master grid you specify:
Which dimensions characterize the material
How many dimensions are contained in a grid value
Which combinations of dimension values you want to allow as grid values
You can add grid values to the master grid any time. These values then apply for all referenced
materials.
For each dimension you can also specify (and change any time):
The axis on which it appears in the grid entry screen
Which ranking it has in the sorting sequence of the line entry screen
Whether you want the dimension values to be converted
Whether you want all dimension values to be displayed in the grid entry or only the valid
ones
9.1.2 Application Grids

An application grid is always a segment from a master grid.
Using application grids you specify which of the grid values that you have permitted for your
material in the master grid you want to purchase or sell.
Prerequisites
Before you can use control options in the application via purchase or sales and distribution
grids, you must have maintained the grid determination for Purchasing and Sales and
Distribution in Customizing and you must have entered the corresponding grid determination
procedure in the material master.
Features
Maintenance
When you create an application grid, you must refer directly or indirectly to a master grid. In the
latter case, you create the new application grid with reference to another application grid. The
system copies all the grid values of the referenced application grid. It does not generate an
interdependence between the two application grids, but assigns the new grid to the same
master grid that is decisive for the referenced application grid.
Each application grid is either an identical copy of a master grid or a segment from a master
grid. An application grid cannot contain more dimension values than the original master grid, nor
can it be made up of entirely different dimensions than the master grid. Grid values not
permitted in the master grid are also excluded from the application grid.
SAP AFS
Page93
Application grid as segment of a master grid
Changes in the master grid also affect all application grids that refer to the master grid
You decide to create your material with the master grid displayed in the above graphic and
include gray as well. You add the color gray to the master grid as an additional dimension value
and enter additional grid values. The system automatically updates all dependent application
grids, but does not transfer the new combinations of grid values. You can decide in which
application grids you want to permit the new grid values.
Application
Application grids allow you to coordinate and plan the purchasing and sale of materials.
You want to wait to sell your material until you have purchased sufficient stock. You do this by
assigning the material a purchasing grid whose validity corresponds to the time period that you
have planned for the purchasing. You also enter a sales grid for this material and make it valid
for the time period during which you want to sell the material.
The validity periods of the two grids can overlap in this case. If you want a material to be
discontinued, for example, you can extend the validity of the sales grid over that of the purchase
grid. You thus ensure that the remaining stock continues to be available for sale, but that
purchasing does not replenish the material.
The connection between material and application grids is variable, unlike the master grid, which
is a fixed component of the basic data of your AFS material and which you must enter when you
create an AFS material in order to be able to work with the material. You can assign sales or
purchasing grids to a material, but you do not have to. You can also undo or change a
connection any time.
You create a relationship between application grids and a material by using the Condition
Technique for Creating Grid Control Data. Here you specify the period for which you want a
purchasing or sales grid to be valid for a certain material. You can also restrict the validity of the
application grid according to criteria of your choice (for example, sales organization and sales
area).
You can also enter additional information for purchasing and sales.
You know that customer A never requests variants of size XS of your material Y with the master
grid in the above graphic. For this case you can create a sales grid in which you exclude all the
grid values combined with XS. Using the grid control data SD, you condition the sales grid within
the relevant sales area for customer A and material Y. When creating an order for this customer,
the system only offers you the grid values for material Y that you have permitted in the sales
grid.
SAP AFS
Page94
9.1.3 Condition Technique for the Creation of Grid Control

Data
This function is the basis for creating grid control data.
Use the grid determination procedure for purchasing and sales and distribution to ensure that
the system finds the requested application grids and control data in the application and uses
them correctly.
Condition records are used to create grid control data. They are used to determine the
duration and area of validity of your application grid and control data.
Features
Grid Determination Procedure
AFS provides two set determination procedures for grid determination in purchasing and sales
and distribution. In both procedures the system accesses one condition type for master grids,
and, according to the application area, another for purchasing or sales grids.
In the AFS basic data view in the material master, you enter appropriate grid determination
procedures for purchasing and sales and distribution.
On basis of the determination procedure, the system checks in the application whether there is
grid control data for the material in the current situation. The relevant access sequence for each
condition type is set independently of the determination procedure. This means that the system
assumes the most concrete key combination when it checks for grid control data. If there is no
grid control data, the system accesses the next key combination, and so on.
Using the grid determination log during order entry in sales and distribution, you can see the key
combination for which the system found valid grid control data.
You can enhance the standard access sequences in AFS purchasing or sales Customizing to
optimally map your business processes.
Creation of Grid Control Data
You create grid control data for:
Master grids when you create the grid
Application grids using condition records
Grid control data for master grids are normally valid at material level. As soon as you have
specified control data for a master grid, and the grid has been assigned to a material, the control
data for the master grid is also valid for the material. The master grid and the grid control data
for the material are valid for all plants.
A number of different key combinations are available for the condition types for maintaining grid
control data for the application grids. You use the key combinations to determine the area of
validity of your grid control data.
You can define grid control data for Sales, for example, according to a key combination Service
Area - Customer - Material. This is useful if one of your customers always orders particular grid
values of this material.
If you use a material in different service areas but only sell certain grid values of the material
according to the service area, you can create grid control data on the basis of a key combination
Service Area - Master Grid. Here you can enter a service grid containing the material grid values
in which the material exists in this service area. Only these grid values are permitted during
order entry.
Activities
In AFS purchasing or sales Customizing, check whether the existing settings for grid
determination meet the requirements of your company. Make new settings if required.
You can maintain grid control data from the AFS application menu
SAP AFS
Page95
9.1.4 Grid Control Data (Content)

With this function you can further specify the content of your grid control data.
When you created your grid control data based on the condition technique, you specified the
area of validity of the grid control data. You can make additional entries for each grid value in
the grid control data. This makes the processing of the grid values in the application much
easier.
Features
Depending on whether you create grid control data for Purchasing or Sales, you have different
possibilities of how to specify the content of your grid control data. The possible entries are
grouped as modes.
Purchasing
You buy a material piecewise and sell it in packs of two. You therefore want to control that
Purchasing only buys the grid values of the material in even numbers so that no single units
remain when you sell two grid values together. You can do so by assigning grid control data to
the material based on a purchasing grid. You enter the content of the grid control data by
entering a rounding factor for each grid value.
Sales
Some of your customers do not enter how many pieces they want per grid value of a material.
They order a total quantity per material in percentages. Thus they indicate which grid values
they want to have more pieces of. You want to carry out this presizing procedure during the
order creation as quick as possible. You can do so by assigning grid control data which is based
on a sales grid to these customers and to the corresponding materials. Here the content is the
distribution profile, on which the presizing is based in the application.
9.1.5 Sort Sequence for Dimension Values

You can define any number of dimension values per dimension. The alphabetical sort order
often does not correspond to the order in which the dimension values should appear. Therefore
you can control the sort sequence to suit your requirements.
Features
The sorting order is defined by the order in which the characteristic values are created. For
example, you have four characteristic values L, M, S and XL. You want the grid / applications to
display the order as S, M, L and XL. You must then enter them exactly in this order during
characteristic value creation.
Sort Sequence for Dimension Values Line Entry
You have a two-dimensional grid with dimension color with the values white (WHT)and black
(BLCK) and dimension size from the previous example. The sort sequence for the color values
is BLCK, WHT. You have allowed all possible combinations as grid values.
In the line entry the system sorts the grid values as follows:
SAP AFS
Page96
By changing the sort sequence in the master grid you can sort the grid values according to the
second dimension, which in this example is size.
9.2 Grid History

If the grid history is activated you can display information on when the grid was changed, who
changed it, and what was changed.
Features
You can make changes to a grid if you have not yet used it, for example, combine additional grid
values or cancel existing combinations. You can also add dimension values to master grids.
Once you have used a grid, you cannot change settings for dimensions or grid values, but you
can add new dimension values and combine other grid values.
If you activate the grid history in Customizing and in the grid, the system logs all changes. You
can query the changes any time using reports.
Grid History in General
Under Grid Number Ranges and Grid History in Customizing, you decide whether you want to
use the function in your system and whether it should be active for all grid types or certain types
only.
The grid history is activated for all grid types in standard Customizing.
Grid History per Grid
If you keep the default settings in Customizing, you can specify whether or not you want the
system to record changes when you create or enter a grid.
SAP AFS
Page97
9.3 Grid Reports

AFS System provides three reports you can use to get an overview of:
The materials in which you used a master grid
Which application grids are dependent on a master grid or vice versa which master
grid belongs to an application grid
The changes you made to material grids
Features
Report: Usage of Master Grids in the Material Master
Using this report you get an evaluation showing you the materials for which you have used the
master grids you entered in your selection.
Report: Dependency between Master and Application Grids
Using this report you get:
All dependent application grids for the master grids you entered in your selection
All superior master grids for the application grids you entered in your selection
You can make your selection in one evaluation using master and application grids at the same
time. In this case you get a report in two parts. The application grids appear on the left, and the
master grids on the right. The application grids are highlighted on the right in the first part of the
report; the master grids are highlighted on the left in the second part. If you want information on
certain interdependencies, this division makes the results list easier to use.
Report: Display of Changes in Material Grids
Using this report you can display the changes you have made to grids. You only get results for
grids for which you have explicitly entered in the grid maintenance that you want the system to
log future changes.
With this report you can find out when you added or removed grid values, and with which
dimension values you combined them.
9.4 Dimension Value Conversion

Dimension value conversion enables you to display the grid values determined in the system
differently. Depending on the vendor, customer or user, dimension values in documents and
reports are displayed in different languages or country-dependent standard sizes, for example.
Dimension value conversion changes how the grid values are displayed in AFS.
In the AFS entry screens, you can display data on the current document conversion type by
selecting
Document Conversion Type. The system defaults the conversion type that then
converts the grid values based on a user/vendor or customer/vendor combination.
All
Conversion Types is used to run dimension conversion based on a different conversion type. If
you have not defined conversion values in Customizing for some dimension values, you cannot
process any entries for these dimension values in AFS documents.
Definition of Customer, Vendor and User IDs
Customer/Vendor
ID
You can define a customer/vendor ID in Customizing: Logistics General AFS
SAP AFS
Page98
Material Grids Conversion Define dimension value conversion.Assign the ID to a

customer/vendor master if you want to use a specific conversion type for this customer
or vendor.
User
ID
You can define a user ID by selecting System User profiles Own Data. On
the Parameter tabstrip, enter J31 in the Parameter column and a user ID consisting of
up to three characters in the Value column.
User Parameters
Description
J31
Defines a user ID
J35
Enables the system to print converted

dimension values.
/AFS/No_size_conv
Completely deactivates dimension value

conversion
Assignment of Conversion Types

When determining valid conversion types in AFS, the system checks the assignment table in
Customizing (Logistics - General AFS Material Grids Conversion Control Conversion
Type Determination Assign Conversion Types). In this screen, you can define which
conversion type is used in which conditions. This is done by linking customer, vendor or user
IDs to conversion types. By doing this, you can determine that dimension values are converted
in a certain way in documents containing a specific combination of customer/vendor and user.
Note that the customer ID has higher priority than the user ID.
The system uses the following logic to determine the valid conversion type:
Customer/vendor ID
User ID
Sequence
1
2
3
4
Base Values
If the system cannot determine any conversion types defined by you, it uses conversion
type SY Base Values. The grid values are then displayed exactly as they were created in the
system. You can also select conversion type SY Base Values manually to enter grid values for
which conversion into a different conversion type has not been fully maintained.
If you create and process new material grids, always use the base values and do not work with
converted values.
Selection Screen: Document Conversion Type
In every AFS program with dimension conversion you can display a list containing all relevant
conversion types by selecting
Base Values and
All Conversion Types. You can then
choose a different conversion type from the default conversion type.
For example, if you use user ID 01 to process a document for customer C1, the system only
displays the conversion types to which:
SAP AFS
Page99
User ID 01 or Blank is assigned

Customer ID C1 or Blank is assigned
The system highlights the conversion types assigned user ID 01 and customer ID C1.
Prerequisites
To be able to use dimension value conversion, you must:
1. Activate conversion in the material grid:
a. Select Logistics AFS Central Functions Grids Material Grid Change.
b.
Enter the material grid number and the validity date and confirm your entries by
choosing Continue.
c.
Select the Grid Value Conversion indicator and save your changes.
2. In Customizing, define and update the user, customer/vendor or material IDs (only for
item-specific conversion).
3. Define the conversion types in Customizing.
4. Make a clear assignment of base values to conversion values for each conversion type.
You can also make these assignments using a special function in Customizing. To do
this, select Check Conversion.
Features
Current Grid Value Display
To see how a specific grid value has been converted, what the base value is, and which criteria
have been used to determine the conversion type, select a grid value in the line display for the
LMW detail screen, then choose
Document Conversion Type. The system documents the
conversion type and the grid value at the time at which it was first created, meaning that the
user can always check the conversion type used in a specific conversion and how the grid value
was originally created.
If you change a document with converted grid values, the system determines the conversion
type again and does not automatically display the original conversion type. If you can select a
grid value and choose
Document Conversion Type, you can display the conversion type
used when the document or item was created.
Checking Converted Entries

If you have activated conversion in AFS, the system checks if all dimension values have been
successfully converted. If you have not entered conversion values for particular dimension
values in Customizing, grid values made up of these dimension values are not ready for input.
In the grid entry screen, red traffic lights identify grid values with dimension values that cannot
be converted.
9.4.1 Item-Based Dimension Value Conversion

Dimension Conversion
If you have several materials in a single sales order or purchase order, the system defines the
conversion type for each material in the document if you are usingitem-based dimension
value conversion, based on the material indicator and the appropriate conversion type.
SAP AFS
Page100
Item-based dimension value conversion is inactive if you have set up a document conversion
type. You can switch off the document-based conversion method completely in the user
parameters.
User Parameters
Description
/AFS/No_Auto_Convtyp
Dimension value conversion can be used for each

item or schedule line. System does not propose a
conversion type for a complete document.
The system uses the following logic to determine the conversion type for the dimension value
conversion where a material ID is used:
Material ID
Customer/vendor ID
User ID Sequence
Material Conversion ID
The material conversion ID is a key that links the material with a conversion type. You can
create a material conversion ID and then use it for multiple materials for which you want to
convert dimension values.
You can enter the material conversion ID in the screen AFS Basic Data in the material master.
You cannot enter the material conversion ID when you are creating new materials. However, if
material conversion ID were already entered before the upgrade to this release, it would still
work.
AFS recommends using document-based conversion as this involves less maintenance and
ensures that all conversion entries are maintained consistently.
10. Material Master

AFS has added several views to the material master for storing AFS-specific data. You set a
material as an AFS material by choosing any of the AFS views. You may not subsequently
choose an AFS view in order to add it to a standard material. Once a material has been used
you can no longer remove its AFS status if you have created it as such.
The new views that have been added are AFS Foreign Trade view and AFS Quality
Management (QM) view. You can assign commodity codes at the SKU level from the AFS
Foreign Trade view on the material master and can use the AFS QM view to control inspection
lot creation at SKU level.
SAP AFS
Page101
The AFS Basic Data view has also been enhanced for the Retail data. You can assign the
merchandise category to the AFS material, which is used while creating articles in Retail by
doing the AFS material transfer to Retail.
Features
In addition to the additional views, AFS has also added direct input capabilities and an
EAN/UPC number generation program specifically for AFS materials.
You can also control AFS warning messages by industry to warn the user that they are creating
either a standard material or an AFS material in a certain industry. This is useful if you want to
only create AFS materials in one industry and only standard materials in another. Refer to
Customizing for more information about setting up the AFS warning messages.
Converting Standard Materials to AFS Materials
With this function you can convert an AFS material to a standard material and vice versa, as
long as the material has not been used in any documents, nor has any basic data been
maintained for this material, such as a BOM or routing. You can convert materials to AFS or
standard at material level or you can set AFS MRP at plant level and run the program in
simulation mode or update mode.
10.1Mass Data Change: Material Master

AFS has redeveloped the mass data change function for the material master to include AFSspecific fields and selection criteria. Similar to the standard function, it allows you to select a
large number of materials and either add certain values or change existing values into new
values. In the selection screen, you enter the materials you want to change and then select the
tables and views which include the fields you want to fill or change. The system then displays all
relevant fields and you can use the Select feature to select only those materials with a particular
value and the Change feature to actually enter the new value.
For example, you select lot size 1,000 and then select Change and enter 1,100 to increase the
lot size from 1,000 to 1,100. This is changed for all the materials that were selected in the initial
selection screen and that have 1,000 as their fixed lot size. If you want to set 1,100 as the fixed
lot size for all materials, you can leave out the selection and simply choose Change.
10.2 Direct Input: Material Master

The function for transferring material master data by direct input is available for AFS materials.
You can also generate a transfer file based on existing materials and make changes to the
transfer file.
Prerequisites
To create an AFS material by direct input, you must select the AFS views in structure BMM00.
J_3ADIBAS for AFS Basic Data

J_3ADIMRP for AFS MRP
J_3ADISD for AFS Sales Data
J_3ADIKAL for AFS Valuation
J_3ADIWM for AFS Warehouse Management (only for AFS Release V2.5x)
/AFS/DIFT for AFS Foreign Trade Data
Activities
All AFS specific data at material level, plant level, and sales organization level can be
transferred using structure BMMH1. The following transfer structures are available for AFS data
at SKU level and quota categories:
SAP AFS
Page102
SAP AFS
Structure
Description
Record type
J_3ADI1
Quota categories
J_3ADI2
AFS SKU data (MRP, sales, dimensions)
J_3ADI3
Season
J_3ADI5
AFS SKU valuation data
/AFS/DI6
AFS WM palletization data
/AFS/DI7
AFS WM storage strategy
/AFS/DI8
AFS WM general data
/AFS/DI9
AFS WM storage bin stock
/AFS/DI12
AFS Foreign Trade
/AFS/DI13
AFS Retail Data
Page103

Sap Afs

Uploaded by

Copyright:

Available Formats

Sap Afs

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Afs

Uploaded by

Copyright:

Available Formats

AFS

Manual for new joinners

3.1.2.2 Material Master: Dialog Functions and their Support in ALE

Available Document Types....................................................................................24

Cross-Application AFS Information

1. General Business Processes

Third-Party Order Processing

Stock Transport Order with SD Processing

Maintain the deallocation rule for a season change in allocated production/purchase

Create a season in Customizing by choosing Logistics - General Define AFS

A season in SD can be different from a season in MM/PP/IM. For example, a

Available-to-Promise (ATP) does not consider seasonality.

3.1 AFS Basic Data

3.1.1 Grid Master Data

Transfer of grid data from a non-SAP System

Transfer of data from data pools

Targeted distribution of grids (sending data manually)

AFS Special Features

3.1.1.1 Technical Information: Grid Master Data

AFS-Specific Fields for the Grid Master

Material grid number

AFS product grid validation according to date

Product grid short text

AFS dimension indicator used in product matrix J_3APGDH-J_3AUSED

Dimension indicator for first dimension

Dimension indicator for second dimension

Dimension indicator for third dimension

Material grid type

Number of bytes of dimension 1

Number of bytes of dimension 2

Number of bytes of dimension 3

Reference material grid type

Reference material grid number

Valid-from date of reference material grid

Master grid number

Master grid validation according to date

Sort sequence for dimension 1

Sort sequence for dimension 2

Sort sequence for dimension 3

Filler character for grid display

Check if conversion desired

Sort grid values?

Activate change history at grid level

Maximum number for grid history counter

Grid history counter

First characteristic name

Second characteristic name

Third characteristic name

J_3ABZDX_NEW Characteristic name in Z axis of material

Characteristic name in X axis of material

Characteristic name in Y axis of material

Display all columns/lines during grid entry

/AFS/GRIDBLKZ2 Display all columns/lines during grid entry

/AFS/GRIDBLKZ3 Display all columns/lines during grid entry

Check if conversion desired

Check if conversion desired

Material grid number

AFS product grid validation according to date