SAP AFS

(1)

SAP AFS Página 1

AFS

(2)

SAP AFS Página 2

Index

2. Season

... 4

Features ... 4

Activities ... 5

Limitations ... 6

3.1.1.1 Technical Information: Grid Master Data

... 7

3.1.2.2 Material Master: Dialog Functions and their Support in ALE

... 19

3.2.2 Sales

... 25

Available Document Types ... 25

3.2.2.1 Sales Order

... 25

Features ... 25

AFS Restrictions ... 26

3.2.7 IDoc Error Handling for Inbound IDocs

... 42

Features ... 42

AFS Special Features ... 42

5. Mapping

... 84

Features ... 84

Prerequisites ... 85

8.2 Coverage Strategy

... 92

Features ... 92

9.1 Material Grids: Overview

... 94

Prerequisites ... 94

Features ... 94

Activities ... 95

9.1.1 Master Grids

... 95

Features ... 95

9.1.3 Condition Technique for the Creation of Grid Control Data

... 97

Features ... 97

Activities ... 98

9.1.5 Sort Sequence for Dimension Values

... 99

Features ... 99

9.2 Grid History

... 99

Features ... 100

9.4.1 Item-Based Dimension Value Conversion

... 103

10. Material Master

... 104

(3)

SAP AFS Página 3

10.2 Direct Input: Material Master

... 104

Prerequisites ... 105

Activities ... 105

(4)

SAP AFS Página 4

Cross-Application AFS Information

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.

(5)

SAP AFS Página 5 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

(6)

SAP AFS Página 6

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

Handling  Deallocation Rule. Here you define what action you want the system to take

when the season in an allocated sales order is changed. To attach this deallocation rule

to the order type, in Customizing choose AFS Allocation Run  Cross

Applications  SD Handling  Assign Rule to Order Type. Seasonality in MM/PP/IM

To activate seasonality for MM/PP/IM:

...

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

Seasons. Here you create a season, a collection, and a theme.

2. Maintain the 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.

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

(7)

SAP AFS Página 7

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 J3AGRI02

AFS-Specific Fields for the Grid Master

(8)

SAP AFS Página 8

E1J3AGH1 MSGFN 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 Number of bytes of dimension 2 J_3APGDH-J_3ABYT2 J_3ABYT3 Number of bytes of dimension 3 J_3APGDH-J_3ABYT3 J_3ARGTP Reference material grid type J_3APGDH-J_3ARGTP J_3ARGNR Reference material grid number J_3APGDH-J_3ARGNR J_3ARDAT Valid-from date of reference material grid J_3APGDH-J_3ARDAT

J_3AMGNR Master grid number

J_3APGDH-J_3AMGNR

J_3AMDAT Master grid validation according to date J_3APGDH-J_3AMDAT J_3ASODI1 Sort sequence for dimension 1 J_3APGDH-J_3ASODI1 J_3ASODI2 Sort sequence for dimension 2 J_3APGDH-J_3ASODI2 J_3ASODI3 Sort sequence for dimension 3 J_3APGDH-J_3ASODI3 J_3AGFILL Filler character for grid display J_3APGDH-J_3AGFILL J_3AGCONV Check if conversion desired

J_3APGDH-J_3AGCONV

J_3AGSORT Sort grid values?

J_3APGDH-J_3AGSORT J_3ADOCALL Activate change history at grid level J_3APGHD- J_3ADOCALL J_3ARECNOT Maximum number for grid history counter

J_3APGHD-J_3ARECNOT

J_3ARECNO Grid history counter

J_3APGHD-J_3ARECNO

J_3ABZD1_NEW First characteristic name J_3APGHD-J_3ABZD1 J_3ABZD2_NEW Second characteristic name J_3APGHD-J_3ABZD2 J_3ABZD3_NEW Third characteristic name J_3APGHD-J_3ABZD3 J_3ABZDX_NEW Characteristic name in Z axis of material

grid

(9)

SAP AFS Página 9 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/GRIDBLKZ /AFS/GRIDBLKZ2 Display all columns/lines during grid entry

J_3APGHD-/AFS/GRIDBLKZ2 /AFS/GRIDBLKZ3 Display all columns/lines during grid entry

J_3APGHD-/AFS/GRIDBLKZ3 J_3AGCONV2 Check if conversion desired J_3APGHD-

J_3AGCONV2 J_3AGCONV3 Check if conversion desired J_3APGHD-

J_3AGCONV3

E1J3AGE MSGFN Function No processing

J_3APGNR Material grid number J_3APGEN-J_3APGNR

J_3AVDAT AFS product grid validation according to date 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_3AUSED

J_3ATDAT Dimension display for date J_3APGEN-J_3ATDAT J_3AFDAT Dimension display: from date J_3APGEN-J_3AFDAT

E1J3AGC MSGFN Function No processing

KNUMH Number of condition record J_3AGRCD-KNUMH

J_3APGNR Material grid number J_3AGRCD-

J_3APGNR

J_3AVDAT AFS product grid validation according to date 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

(10)

SAP AFS Página 10

TAXKM Tax classification material J_3AGRCD-TAXKM

DWERK Delivery plant J_3AGRCD-DWERK

J_3AVEMA Material number of vendor J_3AGRCD-J_3AVEMA

J_3AROF Rounding factor J_3AGRCD-J_3AROF

J_3AVEMA_N

3.1.1.2 Grid 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

(11)

SAP AFS Página 11

 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

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

(12)

SAP AFS Página 12

 Targeted distribution of materials (sending data manually)

The AFS IDoc type can be used to send standard material data and AFS material data. Functions for both the receipt and issue of IDocs have been implemented. The reduction and the connection to the SMD tool have been implemented. The new WM views are also now supported.

Grid values are mapped using ALE in the same way as the mapping of the dialog transaction. It is very important that a master grid is entered for AFS materials. The master grid must be entered in the IDoc for the materials.

Categories are mapped in the system using the same method as the online transaction. It is essential that a coverage strategy is entered in the IDoc.

3.1.2.1 Technical Information: Material Master

Technical Description of the IDoc Type Document

type

Direction Logical Message

IDoc Type Process Code

Material Inbound J3AMAT /AFS/MATMAS04 MATM

Material Outbound RBDSEMAT /AFS/MATMAS04

AFS-specific fields for the material master

Segment Field Explanation Origin

E1J3MRA MSGFN Function No processing

J_3AMIND AFS material master indicator MARA-J_3AMIND

J_3AMSTAT AFS material master status MARA-J_3AMSTAT

J_3APGNR Material grid number MARA-J_3APGNR

J_3AKALSV Grid determination procedure SD MARA-J_3AKALSV

J_3AKALSM Grid determination procedure MM MARA-J_3AKALSM

J_3ASMAT Indicator for set material MARA-J_3ASMAT

J_3APROFP Plant profile

MARA-J_3APROFP

J_3APROFC Category profile

MARA-J_3APROFC

J_3APROFG Grid profile

MARA-J_3APROFG

J_3APROFT Period profile MARA-J_3APROFT

(13)

SAP AFS Página 13

J_3ANOGRID AFS material without grid (DUMMY grid

with only one dimension)

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

/AFS/SCLAS Special procurement key

MARA-/AFS/SCLAS

/AFS/SCHNITT Cut

MARA-/AFS/SCHNITT

J_4KCOVSA Coverage Strategy

MARA-J_4KCOVSA

E1J3ASE MSGFN Function No processing

J_3ASEAN Season indicator

J_3AMSEA-J_3ASEAN

J_3ASIZE AFS grid value

J_3AMSEA-J_3ASIZE

J_4KRCAT Requirements Category

J_3AMSEA-J_4KRCAT

/AFS/COLLECTION Collection

J_3AMSEA-/AFS/COLLECTION

/AFS/THEME Topic

J_3AMSEA-/AFS/THEME

E1J3AQD MSGFN Function No processing

J_3AMQCA Quota category

J_3AQDST-J_3AMQCA

E1J3MRC MSGFN Function No processing

J_3AMIND AFS material master indicator MARA-J_3AMIND

J_3AMSTATC AFS material master status MRP

MARC-J_3AMSTATC

J_3AMSTAT AFS material master status

MARC-J_3AMSTAT

J_4KCOVS Version number component MARC-J_4KCOVS

J_3ADISPKZ MRP indicator

MARC-J_3ADISPKZ

J_3AHORIZ Horizon key MARC-J_3AHORIZ

J_3APRFC Category profile MARC-J_3APRFC

J_3APRFG Grid profile MARC-J_3APRFG

J_3APRFT Period profile MARC-J_3APRFT

(14)

SAP AFS Página 14

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

MARC-J_3AEKORG

J_3APRCM Consumption priority MARC-J_3APRCM

J_3ABUND Material created with bundles MARC-J_3ABUND

J_3ACHINT Discrete batch number MARC-J_3ACHINT

J_3ABAINT Dimension used as batch number for

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

MARC-J_4KCOVS_4

J_4KDEFSC_4 Default value stock category

MARC-J_4KDEFSC_4

J_4AATPSI ATP/MRP check method (time or category) MARC-J_4AATPSI

J_3ASLHMOD Activate SKU horizon method

MARC-J_3ASLHMOD

J_3AMROUND

MARC-J_3AMROUND

J_3AMRDMENG

MARC-J_3AMRDMENG

E1J3AAD MSGFN Function No processing

J_3AKORD AFS dimension according to matrix

J_3AMAD-J_3AKORD

J_4KSCAT Stock Category

J_3AMAD-J_4KSCAT

EISBE Safety stock J_3AMAD-EISBE

BSTMI Minimum lot size J_3AMAD-BSTMI

BSTRF Purchase order quantity rounding value J_3AMAD-BSTRF

(15)

J_3AMAD-SAP AFS Página 15

J_3ASIGR

REFVAL AFS: Reference values for all categories

without special values

J_3AMAD-REFVAL

J_4ASTAT AFS: MRP status for dimension validation

J_3AMAD-J_4ASTAT

J_4ADTFR Date

J_3AMAD-J_4ADTFR

J_3ARISK AFS risk factor

J_3AMAD-J_3ARISK

LGRAD Area not further defined J_3AMAD-LGRAD

WZEIT Replenishment lead time J_3AMAD-WZEIT

WZEITSG Total replenishment lead time for SKU

group

J_3AMAD-WZEITSG

J_3APQTY AFS packing quantity – no longer used

J_3AMAD-J_3APQTY

J_3APQUN AFS unit of the packing quantity – no

longer used

J_3AMAD-J_3APQUN

J_3ACASE Standard packing type – no longer used

J_3AMAD-J_3ACASE

VMSTA Distribution chainspecific material status

no longer used

J_3AMAD-VMSTA

VMSTD Validity start date of the distribution

chain-specific material status – no longer used

J_3AMAD-VMSTD

REFSD AFS: Reference values for all categories

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 AFS: Reference values for all categories

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/NFSIZE

E1J3AKA MSGFN Function No processing

J_3AKORD AFS dimension according to grid

J_3AMADKA-J_3AKORD

J_3AMADKA-J_4KSCAT

(16)

J_3AMADKA-SAP AFS Página 16

J_3AKALSW

J_3AKALGR Valuation type (AFS)

J_3AMADKA-J_3AKALGR

TVERS Transportation indicator: planned version

J_3AMADKA-TVERS

VPRSV Price control indicator

J_3AMADKA-VPRSV

PRICE Standard price

J_3AMADKA-PRICE

EKALR Material is costed with quality structure

J_3AMADKA-EKALR

ZKPRS Future price

J_3AMADKA-ZKPRS

ZKDAT Validity start date of the price

J_3AMADKA-ZKDAT

J_3ASRD AFS: surcharges +/-

J_3AMADKA-J_3ASRD

J_3ARKALGP Reference preference group

J_3AMADKA-J_3ARKALGP

/AFS/E1MLGN1 MSGFN Function No processing

LGNUM Warehouse number/complex

/AFS/MLGN1-LGNUM

/AFS/MLGN1-J_3ASIZE

LHMG1 1. Loading equipment quantity

/AFS/MLGN1-LHMG1

/AFS/MLGN1-LHMG2

/AFS/MLGN1-LHMG3

LHME1 Unit of measure for 1. Loading equipment

quantity

/AFS/MLGN1-LHME1

quantity

/AFS/MLGN1-LHME2

quantity

/AFS/MLGN1-LHME3

LETY1 1. Storage unit type

/AFS/MLGN1-LETY1

/AFS/MLGN1-LETY2

/AFS/MLGN1-LETY1

(17)

/AFS/MLGN2-SAP AFS Página 17

LGNUM

/AFS/MLGN2-J_3ASIZE

/AFS/MLGN2-J_4KSCAT

LTKZA Storage type indicator removal from

storage

/AFS/MLGN2-LTKZA

LGBKZ Storage section indicator

/AFS/MLGN2-LGBKZ

BSSKZ Special movement indicator - Warehouse

Management

/AFS/MLGN2-BSSKZ

L2SKR Material relevance for two-step picking

/AFS/MLGN2-L2SKR

LTKZE Storage type indicator, placement in

storage

/AFS/MLGN2-LTKZE

BLOCK Bulk storage indicator

/AFS/MLGN2-BLOCK

KZMBF Indicator: Message to Inventory

Management

/AFS/MLGN2-KZMBF

KZZUL Indicator: Addition to existing stock allowed

/AFS/MLGN2-KZZUL

/AFS/MLGN3-LGNUM

/AFS/MLGN3-J_3ASIZE

/AFS/MLGN3-J_4KSCAT

MKAPV Capacity consumption

/AFS/MLGN3-MKAPV

BEZME Reference unit of measure for capacity

consumption

/AFS/MLGN3-BEZME

/AFS/E1MLGTM MSGFN Function No processing

/AFS/MLGT-LGNUM

/AFS/MLGT-J_3ASIZE

/AFS/MLGT-J_4KSCAT

LGPLA Storage bin /AFS/MLGT-LGPLA

LPMAX Maximum storage bin quantity

/AFS/MLGT-LPMAX

(18)

SAP AFS Página 18

MAMNG Control quantity

/AFS/MLGT-MAMNG

NSMNG Replenishment quantity

/AFS/MLGT-NSMNG

KOBER Picking area

/AFS/MLGT-KOBER

RDMNG Rounding quantity

/AFS/MLGT-RDMNG

E1J3MKE MSGFN Function No processing

J_3AVASG AFS VAS material group

J_3AMVKE-J_3AVASG

J_3APIND AFS pricing indicator in material master

J_3AMVKE-J_3APIND

/AFS/E1MARM MSGFN Function No processing

MEINH Unit of measure for display

/AFS/MARM-MEINH

J_3ASIZE Grid value

/AFS/MARM-J_3ASIZE

/AFS/MARM-J_4KSCAT

VOLUM Volume

/AFS/MARM-VOLUM

BRGEW Gross weight

/AFS/MARM-BRGEW

NTGEW Net Weight

/AFS/MARM-NTGEW

REFDIM AFS: Reference values for all categories

/AFS/MARM-REFDIM

/AFS/E1MEANM MSGFN Function No processing

J_3AKORDX Grid value

/AFS/MEAN-J_3AKORDX

/AFS/EANBLOCK Category value

/AFS/MEAN-/AFS/EANBLOCK

/AFS/CAT_APPL Category type

/AFS/MEAN-/AFS/CAT_APPL

/AFS/E1MVKE MSGN Function No processing

J_3ASIZE Grid value

/AFS/MVKE-J_3ASIZE

J_4KRCAT Requirement category

/AFS/MVKE-J_4KRCAT

VMSTA Distribution chain-specific material status

/AFS/MVKE-VMSTA

VMSTD Validity start date of the distribution

chain-specific material status

/AFS/MVKE-VMSTD

(19)

SAP AFS Página 19

/AFS/REFVMS AFS: Reference values for all categories

/AFS/MVKE-/AFS/REFVMS

J_3APQTY AFS packing quantity

/AFS/MVKE-J_3APQTY

J_3APQUN AFS: unit for packing quantity

/AFS/MVKE-J_3APQUN

J_3ACASE Standard packing category

/AFS/MVKE-J_3ACASE

/AFS/REFPQ AFS: Reference values for all categories

/AFS/MVKE-/AFS/REFPQ

J_3AGEND Target group

/AFS/MVKE-J_3AGEND

/AFS/REFGEND AFS: Reference values for all categories

/AFS/MVKE-/AFS/REFGEND

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:

● 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:

(20)

SAP AFS Página 20

● 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 status incorrect. If no logical error occurs, the IDoc receives the status successful.

For IDocs with the status incorrect or successful, the application log 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)

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

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.

● create a new IDoc segment Error messages

Error number Possible causes Solution

8J670 When changing or enhancing a

material by adding a plant, the wrong maintenance status is also delivered.

Check IDoc and correct the maintenance status.

8J671 Transferred data is duplicated,

for example, the same season

(21)

SAP AFS Página 21

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

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

(22)

SAP AFS Página 22

 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

AFS Special Features 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

IDoc Type Output Type Partner Type Process Code

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

(23)

SAP AFS Página 23 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.

/AFS/E1EDL24 J_3ALNGR AFS line groups indicator

The system uses this indicator to group SKUs that are to be delivered together.

J_3ADEPM Indicates the customer department for whom the SKU was

ordered. This information field is taken from the sales order.

/AFS/E1J3AKG J_3AKVGR6

to

J_3AKVGR10

Additional customer groups.

The additional customer groups are managed in the customer master in an AFS-specific view.

E1J3AI2 J_3AQFREF Indicates the type of reference document:

002: Reference to the SAP order number, item number and schedule line number

003: Reference to the customer purchase order number and the purchase order item (SKU level in field POSEX)

J30: ALE ID. Unique ID number for a schedule line in an ALE stock transfer scenario. This is an internal number and is assigned by the system.

E1J3AIM J_3AOBIDQF Indicates the type of material:

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.

J_3ATLMAT Ticketing/labeling material

J_3ACHARC Code determining the price charged when the customer pays

(24)

SAP AFS Página 24

E1J3AITX J_3ATLTXT Text that should be on the label.

J_3ATLORD Indicates that the text relates to the order

J_3ATLITEM Indicates that the text relates to the item

J_3ATLSIZE Indicates that the text relates to the size

E1J3AIP

Segment containing packing data. The fields are identical to

E1J3AIT.

E1J3AIS

Segments that contain data for special services. The fields are

identical to E1J3AIT.

E1EDL41 QUALI Indicates the reference data for the ordering party:

001: Purchase order data for the customer 002: Purchase order data for the ship-to party

POSEX Contains the customer's item number at SKU level.

Description of the IDoc Fields in the Inbound IDoc Picking Confirmation without Flow Records

The following fields must be filled in the IDoc, as a minimum requirement: E1EDL20-VBELN Delivery number

E1EDL24-POSNR Item number for the SKU (for example, 900001) E1EDL24-MATNR Material number

E1EDL24-CHARG Batch number for the SKU in the delivery E1EDL24-LIFMG Confirmed pick quantity

E1EDL19-QUALF 'QUA'

Picking Confirmation with Flow Records

In addition to the above mentioned fields, segment E1EDL18-QUALF = PIC must also be filled with data.

Other Confirmations

 Weight and volume are confirmed for the entire delivery or for each individual batch.

The item number for the SKU must be entered in field POSNR. All other fields are filled in the SAP standard.

 Indicator E1EDL18-QUALF = 'PGI' controls goods issues.

 Shipping units are confirmed in the same way as in the standard. The item number for

(25)

SAP AFS Página 25 Customer Enhancements (User Exits)

 EXIT_SAPLV56K_001

Customer enhancement for modifying the control record. The control record and all relevant tables for the delivery are transferred.

 EXIT_SAPLV56K_002

Customer enhancement called after each individual standard segment. This customer enhancement is used to fill specific z-segments. The control record, the current segment name, all the relevant delivery tables and the IDoc data records are transferred

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 Output

Type

Process Code

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

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

(26)

SAP AFS Página 26

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.

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.

(27)

SAP AFS Página 27

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 Interchange  EDI Messages  Convert SAP Item Category to IDoc Item Category.

 Using the table EDPAR, you can convert external partner numbers into internal partner

numbers as needed. Maintain the table using transaction VOE4. Read also the notes in the documentation for the segments E1EDKA1 and E1EDPA1.

 IMG: Sales and Distribution  Electronic Data Interchange  EDI Messages  Configure EDI Partners  Convert External to Internal Partner Numbers.

 You can control the determination of the sales area data (sales organization, distribution

channel, division) with the table EDSDC. Since an EDI partner will only rarely transmit this data (see notes for the documentation on segment E1EDK14), the sales area can be determined for the transfer to the application depending on the customer and vendor number. To do this call the transaction VOE2.

 IMG: Sales and Distribution  Electronic Data Interchange  EDI Messages  Configure EDI Partners  Assign Customer/Vendor To Sales Organization Data

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

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 Is transferred to the document

(28)

SAP AFS Página 28

eigenuinr VAT registration number No processing

BSARt Document type No processing

BELNR IDoc document number No processing

ntgew Net Weight No processing

brgew Gross weight No processing

gewei Weight Unit No processing

fkart_rl Remuneration list type No processing

ABLAD Unloading point No processing

BSTZD Order number addition of customer Is transferred to the document

VSART Shipping condition Is transferred to the document

VSART_BEZ Description of shipping type No processing

recipnt_no Number of recipient No processing

kzazu Indicator: order combination Is transferred to the document

autlf Complete delivery indicator Is transferred to the document

augru Order reason Is transferred to the document

augru_bez Description order reason No processing

abrvw

Is transferred to the document

abrvw_bez

No processing

fktyp Billing category No processing

lifsk Delivery note block Is transferred to the document

lifsk_bez Description: delivery note block No processing

empst Receiving point Is transferred to the document

abtnr Department number No processing

delco Agreed delivery time No processing

wkurs_m Rate with indirect quotation No processing

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

(29)

SAP AFS Página 29

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

EVERS Shipping Instruction No processing

BPUMN Denominator for the Conversion BPRME

into BME

No processing

BPUMZ Numerator for the Conversion BPRME into

BME

No processing

ABGRU Reason for item rejection Is transferred to document item.

ABGRT Description No processing

ANTLF Maximum number of permitted partial

deliveries per item

(30)

SAP AFS Página 30

FIXMG Delivery date and quantity fixed No processing

KZAZU Indicator: order combination Is transferred to document item.

J_3APOSNR Item Number Internal usage

J_3AMSOM Equal mix of products in a multi-store

order

The mix key is only then processed, if the flag J_3AMSOFLG is set in segment E1J3AHO. It is used for the grouping of store and/or distribution centers that should be delivered.

J_3ABZUS Requirements grouping Dimension requirements for an item

are grouped, if this indicator is set.

J_3ADEPM Department Is transferred to document item.

J_3ASPLIT AFS Split indicator Is transferred to document item.

J_3ASEAN Season indicator Is transferred to document item.

J_3ASIZE AFS grid value Is transferred to document item or

schedule line

J_3ALNGR AFS Line group ID (schedule lines are

delivered together)

Is transferred to document item.

J_4KRCAT Requirements Category Is transferred to document item.

J_4KSCAT Stock Category No processing

BRGEW Total Weight No processing

VOLUM Volume No processing

VOLEH Volume Unit No processing

J_3AVASIT VAS Item values ticketing/labeling (E),

packing (V), 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 application.

EMPST Receiving point Is transferred to document item.

ABTNR Department number No processing

ABRVW Usage indicator No processing

WERKS Plant Is transferred to document item.

LPRIO Delivery priority No processing

(31)

SAP AFS Página 31

ROUTE Route No processing

ROUTE_BEZ Description No processing

LGORT Storage location No processing

VSTEL Shipping point No processing

DELCO Agreed delivery time No processing

MATNR Material identification No processing

Note: The material identification and determination is controlled by using segments E1J3AIM and/or E1EDP19. The document item segment E1J3P01 starts the transfer of data per item. Below the segment you find further item-related segments with detailed information for the respective item. A prerequisite for correctly processing the segment is that the external item number in field POSEX is uniquely filled. If the field remains initial, error message /AFS/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.

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

(32)

SAP AFS Página 32

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

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.

(33)

SAP AFS Página 33

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)

Mandatory segment: NO

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