Вы находитесь на странице: 1из 105

AFS

Manual for new joinners

SAP AFS

Pgina 1

2.

Season

Index ......................................................................................................... 4

Features ................................................................................................................ 4 Activities ................................................................................................................ 5 Limitations ............................................................................................................. 6 3.1.1.1 Technical Information: Grid Master Data .................................................. 7 .................. 19

3.1.2.2 Material Master: Dialog Functions and their Support in ALE 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 10. Material Master ............................................... 103

..................................................................................... 104

Features ............................................................................................................ 104


SAP AFS Pgina 2

10.2 Direct Input: Material Master

.................................................................... 104

Prerequisites...................................................................................................... 105 Activities ............................................................................................................ 105

SAP AFS

Pgina 3

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

SAP AFS

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. Maintain the deallocation rule for a season change in allocated production orders in Customizing by choosing AFS Allocation Run Cross Applications PP Handling Deallocation Rule. Here you define what action you want the system to take
Pgina 5

3.

SAP AFS

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:


...

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

Pgina 6

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 Grid Grid Direction Receipt Issue Logical Message J3AGRI IDoc type J3AGRI02 J3AGRI02 Operation code J3AN

AFS-Specific Fields for the Grid Master Segment Fields Explanation Origin

SAP AFS

Pgina 7

E1J3AGH1 MSGFN
J_3APGNR J_3AVDAT J_3AKTXT J_3ADLKZ J_3AUSED J_3ACRDT J_3AEDDT J_3AUSER J_3ABZD1 J_3ABZD2 J_3ABZD3 J_3ABZDX J_3ASGTP J_3ABYT1 J_3ABYT2 J_3ABYT3 J_3ARGTP J_3ARGNR J_3ARDAT J_3AMGNR J_3AMDAT J_3ASODI1 J_3ASODI2 J_3ASODI3 J_3AGFILL J_3AGCONV J_3AGSORT J_3ADOCALL J_3ARECNOT J_3ARECNO J_3ABZD1_NEW J_3ABZD2_NEW J_3ABZD3_NEW

Function
Material grid number AFS product grid validation according to date Product grid short text Delete indicator

No processing
J_3APGDH-J_3APGNR J_3APGDH-J_3AVDAT J_3APGDH-J_3AKTXT J_3APGDH-J_3ADLKZ

AFS dimension indicator used in product J_3APGDH-J_3AUSED matrix Date of creation Date changed/deleted User name Dimension indicator for first dimension Dimension indicator for second dimension Dimension indicator for third dimension Selection dimension ID 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_3APGDH-J_3ACRDT J_3APGDH-J_3AEDDT J_3APGDH-J_3AUSER J_3APGDH-J_3ABZD1 J_3APGDH-J_3ABZD2 J_3APGDH-J_3ABZD3 J_3APGDH-J_3ABZDX J_3APGDH-J_3ASGTP J_3APGDH-J_3ABYT1 J_3APGDH-J_3ABYT2 J_3APGDH-J_3ABYT3 J_3APGDH-J_3ARGTP J_3APGDH-J_3ARGNR J_3APGDH-J_3ARDAT J_3APGDHJ_3AMGNR J_3APGDH-J_3AMDAT J_3APGDH-J_3ASODI1 J_3APGDH-J_3ASODI2 J_3APGDH-J_3ASODI3 J_3APGDH-J_3AGFILL J_3APGDHJ_3AGCONV J_3APGDHJ_3AGSORT J_3APGHDJ_3ADOCALL J_3APGHDJ_3ARECNOT J_3APGHDJ_3ARECNO J_3APGHD-J_3ABZD1 J_3APGHD-J_3ABZD2 J_3APGHD-J_3ABZD3 J_3APGHD-J_3ABZDX

J_3ABZDX_NEW Characteristic name in Z axis of material

grid
SAP AFS Pgina 8

J_3ABXDX J_3ABYDX /AFS/GRIDBLKZ

Characteristic name in X axis of material grid Characteristic name in Y axis of material grid
Display all columns/lines during grid entry

J_3APGHD-J_3ABXDX J_3APGHD-J_3ABYDX J_3APGHD/AFS/GRIDBLKZ J_3APGHD/AFS/GRIDBLKZ2 J_3APGHD/AFS/GRIDBLKZ3 J_3APGHDJ_3AGCONV2 J_3APGHDJ_3AGCONV3 No processing J_3APGEN-J_3APGNR J_3APGEN-J_3AVDAT J_3APGENJ_3AKORD1 J_3APGENJ_3AKORD2 J_3APGENJ_3AKORD3 J_3APGENJ_3AKORDX J_3APGEN-J_3ADLKZ

/AFS/GRIDBLKZ2 Display all columns/lines during grid entry /AFS/GRIDBLKZ3 Display all columns/lines during grid entry J_3AGCONV2 J_3AGCONV3 E1J3AGE MSGFN J_3APGNR J_3AVDAT J_3AKORD1 J_3AKORD2 J_3AKORD3 J_3AKORDX J_3ADLKZ J_3AUSED J_3ATDAT J_3AFDAT E1J3AGC MSGFN KNUMH J_3APGNR J_3AVDAT J_3ASIZE KAPPL KSCHL MINAU J_3AVMNG VRKME J_3AHSIZ J_3ASPRO J_3ASZGR Dimension display for date Dimension display: from date Function Number of condition record Material grid number AFS product grid validation according to date AFS grid value Application Condition type Minimum order quantity in basic unit of measure AFS default order quantity Sales unit AFS heart size AFS dimension: Size % spread - order AFS SKU group for pricing Check if conversion desired Check if conversion desired Function Material grid number AFS product grid validation according to date AFS coordinate first dimension AFS coordinate second dimension AFS coordinate third dimension Grid value Delete indicator

J_3APGEN-J_3ATDAT J_3APGEN-J_3AFDAT No processing J_3AGRCD-KNUMH J_3AGRCDJ_3APGNR J_3AGRCD- J_3AVDAT J_3AGRCD- J_3ASIZE J_3AGRCD-KAPPL J_3AGRCD-KSCHL J_3AGRCD-MINAU J_3AGRCDJ_3AVMNG J_3AGRCD-VRKME J_3AGRCD-J_3AHSIZ J_3AGRCD-J_3ASPRO J_3AGRCD-J_3ASZGR

SAP AFS

Pgina 9

TAXKM DWERK J_3AVEMA J_3AROF J_3AVEMA_N

Tax classification material Delivery plant Material number of vendor Rounding factor

J_3AGRCD-TAXKM J_3AGRCD-DWERK J_3AGRCD-J_3AVEMA J_3AGRCD-J_3AROF

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

You can find further information in the documentation BC - Changes to the SAP-Standard.

SAP AFS

Pgina 10

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 Transfer of data from data pools

SAP AFS

Pgina 11

Targeted distribution of materials (sending data manually)

AFS Special Features 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 Material Material Direction Inbound Outbound Logical Message J3AMAT RBDSEMAT IDoc Type /AFS/MATMAS04 /AFS/MATMAS04 Process Code MATM

AFS-specific fields for the material master Segment E1J3MRA Field MSGFN J_3AMIND J_3AMSTAT J_3APGNR J_3AKALSV J_3AKALSM J_3ASMAT J_3APROFP J_3APROFC J_3APROFG J_3APROFT J_3AGMID Explanation Function AFS material master indicator AFS material master status Material grid number Grid determination procedure SD Grid determination procedure MM Indicator for set material Plant profile Category profile Grid profile Period profile Dimension conversion: Material indicator Origin No processing MARA-J_3AMIND MARA-J_3AMSTAT MARA-J_3APGNR MARA-J_3AKALSV MARA-J_3AKALSM MARA-J_3ASMAT MARAJ_3APROFP MARAJ_3APROFC MARAJ_3APROFG MARA-J_3APROFT MARA-J_3AGMID

SAP AFS

Pgina 12

J_3ANOGRID J_3AFCC J_3AGEND J_3ACOL J_4KCSGR /AFS/SCLAS /AFS/SCHNITT J_4KCOVSA E1J3ASE MSGFN J_3ASEAN J_3ASIZE J_4KRCAT

AFS material without grid (DUMMY grid MARAwith only one dimension) J_3ANOGRID Fabric content code Gender Material master: Color Category structure Special procurement key Cut Coverage Strategy Function Season indicator AFS grid value Requirements Category MARA-J_3AFCC MARA-J_3AGEND MARA-J_3ACOL MARA-J_4KCSGR MARA/AFS/SCLAS MARA/AFS/SCHNITT MARAJ_4KCOVSA No processing J_3AMSEAJ_3ASEAN J_3AMSEAJ_3ASIZE J_3AMSEAJ_4KRCAT J_3AMSEA/AFS/COLLECTION J_3AMSEA/AFS/THEME No processing J_3AQDSTJ_3AMQCA No processing MARA-J_3AMIND MARCJ_3AMSTATC MARCJ_3AMSTAT MARC-J_4KCOVS MARCJ_3ADISPKZ MARC-J_3AHORIZ MARC-J_3APRFC MARC-J_3APRFG MARC-J_3APRFT MARC-J_3ASGRID
Pgina 13

/AFS/COLLECTION Collection /AFS/THEME E1J3AQD MSGFN J_3AMQCA E1J3MRC MSGFN J_3AMIND J_3AMSTATC J_3AMSTAT J_4KCOVS J_3ADISPKZ J_3AHORIZ J_3APRFC J_3APRFG J_3APRFT J_3ASGRID
SAP AFS

Topic Function Quota category Function AFS material master indicator AFS material master status MRP AFS material master status Version number component MRP indicator Horizon key Category profile Grid profile Period profile Single grid value

J_3AVERPR J_3AVERMR J_3AVERSS J_3AVERPU J_3AVERSD J_3AEKORG J_3APRCM J_3ABUND J_3ACHINT J_3ABAINT J_3ARISK J_3ADEFSI J_4KDEFSC J_4KCOVS_4 J_4KDEFSC_4 J_4AATPSI J_3ASLHMOD J_3AMROUND J_3AMRDMENG E1J3AAD MSGFN J_3AKORD J_4KSCAT EISBE BSTMI BSTRF J_3ASIGR
SAP AFS

Default version for presizing Default version for MRP Default version for MRP safety stock Default version for Purchasing Default version for SD Default purchasing organization for source allocation Consumption priority Material created with bundles Discrete batch number Dimension used as batch number for material without coverage strategy AFS risk factor Default grid value Default value stock category Coverage Strategy Default value stock category ATP/MRP check method (time or category) Activate SKU horizon method

MARCJ_3AVERPR MARCJ_3AVERMR MARCJ_3AVERSS MARCJ_3AVERPU MARCJ_3AVERSD MARCJ_3AEKORG MARC-J_3APRCM MARC-J_3ABUND MARC-J_3ACHINT MARC-J_3ABAINT MARC-J_3ARISK MARC-J_3ADEFSI MARCJ_4KDEFSC MARCJ_4KCOVS_4 MARCJ_4KDEFSC_4 MARC-J_4AATPSI MARCJ_3ASLHMOD MARCJ_3AMROUND MARCJ_3AMRDMENG

Function AFS dimension according to matrix Stock Category Safety stock Minimum lot size Purchase order quantity rounding value AFS SKU group for lot-sizing procedure

No processing J_3AMADJ_3AKORD J_3AMADJ_4KSCAT J_3AMAD-EISBE J_3AMAD-BSTMI J_3AMAD-BSTRF J_3AMADPgina 14

J_3ASIGR REFVAL J_4ASTAT J_4ADTFR J_3ARISK LGRAD WZEIT WZEITSG J_3APQTY J_3APQUN J_3ACASE VMSTA VMSTD REFSD BRGEW NTGEW VOLUM REFDIM AUSDT NFMAT NFWRK /AFS/NFSIZE E1J3AKA MSGFN J_3AKORD J_4KSCAT J_3AKALSW AFS: Reference values for all categories without special values AFS: MRP status for dimension validation Date AFS risk factor Area not further defined Replenishment lead time Total replenishment lead time for SKU group AFS packing quantity no longer used AFS unit of the packing quantity no longer used Standard packing type no longer used Distribution chain-specific material status no longer used Validity start date of the distribution chainspecific material status no longer used AFS: Reference values for all categories without special values - no longer used Gross weight no longer used Net weight no longer used Volume no longer used AFS: Reference values for all categories without special values - no longer used Expiry date Follow-up Material Value Follow-up grid value for the MRP discontinuation Function AFS dimension according to grid Stock Category Preference SKU J_3AMAD-REFVAL J_3AMADJ_4ASTAT J_3AMADJ_4ADTFR J_3AMADJ_3ARISK J_3AMAD-LGRAD J_3AMAD-WZEIT J_3AMADWZEITSG J_3AMADJ_3APQTY J_3AMADJ_3APQUN J_3AMADJ_3ACASE J_3AMAD-VMSTA J_3AMAD-VMSTD J_3AMAD-REFSD J_3AMAD-BRGEW J_3AMAD-NTGEW J_3AMAD-VOLUM J_3AMAD-REFDIM J_3AMAD-AUSDT J_3AMAD-NFMAT J_3AMAD-NFWRK J_3AMAD/AFS/NFSIZE No processing J_3AMADKAJ_3AKORD J_3AMADKAJ_4KSCAT J_3AMADKA-

SAP AFS

Pgina 15

J_3AKALSW J_3AKALGR TVERS VPRSV PRICE EKALR ZKPRS ZKDAT J_3ASRD J_3ARKALGP /AFS/E1MLGN1 MSGFN LGNUM J_3ASIZE LHMG1 LHMG2 LHMG3 LHME1 LHME2 LHME3 LETY1 LETY2 LETY1 /AFS/E1MLGN2 MSGFN LGNUM
SAP AFS

Valuation type (AFS) Transportation indicator: planned version Price control indicator Standard price Material is costed with quality structure Future price Validity start date of the price AFS: surcharges +/Reference preference group Function Warehouse number/complex AFS grid value 1. Loading equipment quantity 2. Loading equipment quantity 3. Loading equipment quantity Unit of measure for 1. Loading equipment quantity Unit of measure for 2. Loading equipment quantity Unit of measure for 3. Loading equipment quantity 1. Storage unit type 2. Storage unit type 3. Storage unit type Function Warehouse number/complex

J_3AMADKAJ_3AKALGR J_3AMADKATVERS J_3AMADKAVPRSV J_3AMADKAPRICE J_3AMADKAEKALR J_3AMADKAZKPRS J_3AMADKAZKDAT J_3AMADKAJ_3ASRD J_3AMADKAJ_3ARKALGP No processing /AFS/MLGN1LGNUM /AFS/MLGN1J_3ASIZE /AFS/MLGN1LHMG1 /AFS/MLGN1LHMG2 /AFS/MLGN1LHMG3 /AFS/MLGN1LHME1 /AFS/MLGN1LHME2 /AFS/MLGN1LHME3 /AFS/MLGN1LETY1 /AFS/MLGN1LETY2 /AFS/MLGN1LETY1 No processing /AFS/MLGN2Pgina 16

LGNUM J_3ASIZE J_4KSCAT LTKZA LGBKZ BSSKZ L2SKR LTKZE BLOCK KZMBF KZZUL /AFS/E1MLGN3 MSGFN LGNUM J_3ASIZE J_4KSCAT MKAPV BEZME /AFS/E1MLGTM MSGFN LGNUM J_3ASIZE J_4KSCAT LGPLA LPMAX LPMIN AFS grid value Stock Category Storage type indicator removal from storage Storage section indicator Special movement indicator - Warehouse Management Material relevance for two-step picking Storage type indicator, placement in storage Bulk storage indicator Indicator: Message to Inventory Management Indicator: Addition to existing stock allowed Function Warehouse number/complex AFS grid value Stock Category Capacity consumption Reference unit of measure for capacity consumption Function Warehouse number/complex AFS grid value Stock Category Storage bin Maximum storage bin quantity Minimum storage bin quantity /AFS/MLGN2J_3ASIZE /AFS/MLGN2J_4KSCAT /AFS/MLGN2LTKZA /AFS/MLGN2LGBKZ /AFS/MLGN2BSSKZ /AFS/MLGN2L2SKR /AFS/MLGN2LTKZE /AFS/MLGN2BLOCK /AFS/MLGN2KZMBF /AFS/MLGN2KZZUL No processing /AFS/MLGN3LGNUM /AFS/MLGN3J_3ASIZE /AFS/MLGN3J_4KSCAT /AFS/MLGN3MKAPV /AFS/MLGN3BEZME No processing /AFS/MLGTLGNUM /AFS/MLGTJ_3ASIZE /AFS/MLGTJ_4KSCAT /AFS/MLGT-LGPLA /AFS/MLGTLPMAX /AFS/MLGT-LPMIN

SAP AFS

Pgina 17

MAMNG NSMNG KOBER RDMNG E1J3MKE MSGFN J_3AVASG J_3APIND /AFS/E1MARM MSGFN MEINH J_3ASIZE J_4KSCAT VOLUM BRGEW NTGEW REFDIM /AFS/E1MEANM MSGFN J_3AKORDX /AFS/EANBLOCK /AFS/CAT_APPL /AFS/E1MVKE MSGN J_3ASIZE J_4KRCAT VMSTA VMSTD

Control quantity Replenishment quantity Picking area Rounding quantity Function AFS VAS material group AFS pricing indicator in material master Function Unit of measure for display Grid value Stock Category Volume Gross weight Net Weight AFS: Reference values for all categories without special values Function Grid value Category value Category type Function Grid value Requirement category Distribution chain-specific material status Validity start date of the distribution chainspecific material status

/AFS/MLGTMAMNG /AFS/MLGTNSMNG /AFS/MLGTKOBER /AFS/MLGTRDMNG No processing J_3AMVKEJ_3AVASG J_3AMVKEJ_3APIND No processing /AFS/MARMMEINH /AFS/MARMJ_3ASIZE /AFS/MARMJ_4KSCAT /AFS/MARMVOLUM /AFS/MARMBRGEW /AFS/MARMNTGEW /AFS/MARMREFDIM No processing /AFS/MEANJ_3AKORDX /AFS/MEAN/AFS/EANBLOCK /AFS/MEAN/AFS/CAT_APPL No processing /AFS/MVKEJ_3ASIZE /AFS/MVKEJ_4KRCAT /AFS/MVKEVMSTA /AFS/MVKEVMSTD
Pgina 18

SAP AFS

/AFS/REFVMS J_3APQTY J_3APQUN J_3ACASE /AFS/REFPQ J_3AGEND /AFS/REFGEND

AFS: Reference values for all categories without special values AFS packing quantity AFS: unit for packing quantity Standard packing category AFS: Reference values for all categories without special values Target group AFS: Reference values for all categories without special values

/AFS/MVKE/AFS/REFVMS /AFS/MVKEJ_3APQTY /AFS/MVKEJ_3APQUN /AFS/MVKEJ_3ACASE /AFS/MVKE/AFS/REFPQ /AFS/MVKEJ_3AGEND /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:

SAP AFS

Pgina 19

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 SAPStandard. 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 8J670 Possible causes When changing or enhancing a material by adding a plant, the wrong maintenance status is also delivered. Transferred data is duplicated, for example, the same season Solution Check IDoc and correct the maintenance status.

8J671
SAP AFS

Check IDoc and correct duplicate entries.


Pgina 20

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

AFS Special Features For AFS, only the outbound messages (SHPMNT and SHPADV) are implemented and not the inbound. Customizing Logical Message SHPMNT/SHPADV IDoc Type /AFS/SHPMNT03 Output type SEDI Partner Type WE or SP Process Code 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)

SAP AFS

Pgina 21

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

IDoc Type

Output Type

Partner Type

Process Code

/AFS/DELVRY02 /AFS/DELVRY02

WSOR

LS LS

DELV (outbound) DELV (inbound) DELV (outbound) DELV (inbound) DELV (outbound) DELV (outbound)

SHPORD SHPCON

/AFS/DELVRY02 /AFS/DELVRY02

SHOR

LI LI

CARNOT

/AFS/DELVRY02

CANO

LI

DESADV

/AFS/DELVRY02

LAVA

KU

SAP AFS

Pgina 22

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 E1EDL24 Fields KDMAT EAN11 /AFS/E1EDL24 J_3ALNGR Explanation The customer material number is entered here, even if it was entered at SKU level. The EAN/UPC number is entered here, even if it was entered at SKU level. AFS line groups indicator The system uses this indicator to group SKUs that are to be delivered together. J_3ADEPM /AFS/E1J3AKG J_3AKVGR6 to 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 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 J_3ATLTYP Store number for ticketing/labeling. Ticketing/labeling type Unique key that determines the type of label. J_3ATLMAT J_3ACHARC Ticketing/labeling material Code determining the price charged when the customer pays for ticketing/labeling. Indicates the customer department for whom the SKU was ordered. This information field is taken from the sales order. Additional customer groups. The additional customer groups are managed in the customer master in an AFS-specific view.

SAP AFS

Pgina 23

E1J3AITX

J_3ATLTXT J_3ATLORD J_3ATLITEM J_3ATLSIZE

Text that should be on the label. Indicates that the text relates to the order Indicates that the text relates to the item Indicates that the text relates to the size Segment containing packing data. The fields are identical to E1J3AIT. Segments that contain data for special services. The fields are identical to E1J3AIT.

E1J3AIP E1J3AIS E1EDL41 QUALI

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

POSEX

Contains the customer's item number at SKU level.

Description of the IDoc Fields in the Inbound IDoc Picking Confirmation without Flow Records The following fields must be filled in the IDoc, as a minimum requirement: E1EDL20-VBELN Delivery number E1EDL24-POSNR Item number for the SKU (for example, 900001) E1EDL24-MATNR Material number E1EDL24-CHARG Batch number for the SKU in the delivery E1EDL24-LIFMG Confirmed pick quantity E1EDL19-QUALF 'QUA' Picking Confirmation with Flow Records In addition to the above mentioned fields, segment E1EDL18-QUALF = PIC must also be filled with data. Other Confirmations Weight and volume are confirmed for the entire delivery or for each individual batch. The item number for the SKU must be entered in field POSNR. All other fields are filled in the SAP standard. Indicator E1EDL18-QUALF = 'PGI' controls goods issues. Shipping units are confirmed in the same way as in the standard. The item number for the SKU must be entered in field E1EDL44-POSNR.
Pgina 24

SAP AFS

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 Orders

Direction Inbound

Logical Message ORDERS ORDERS ORDCHG ORDRSP QUOTES

IDoc Type /AFS/ORDERS05 /AFS/ORDERS05 /AFS/ORDERS05 /AFS/ORDERS05 /AFS/ORDERS05

Output Type

Process Code J3AA J3AA J3AC

Contracts (CQ) Inbound Order Change Order Confirmation Quotations Inbound Outbound Outbound

BA00 AN00

SD10 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
SAP AFS Pgina 25

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.

SAP AFS

Pgina 26

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 action kzabs curcy Explanation Action code that concerns the entire EDI message Order acknowledgment requirement indicator Currency code Processing No processing No processing 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. No processing Is transferred to the document Is transferred to the document No processing
Pgina 27

hwaer wkurs zterm kundeuinr


SAP AFS

EDI local currency Exchange rate Term of payment VAT registration number

eigenuinr BSARt BELNR ntgew brgew gewei fkart_rl ABLAD BSTZD VSART VSART_BEZ recipnt_no kzazu autlf augru augru_bez abrvw abrvw_bez fktyp lifsk lifsk_bez empst abtnr delco wkurs_m

VAT registration number Document type IDoc document number Net Weight Gross weight Weight Unit Remuneration list type Unloading point Order number addition of customer Shipping condition Description of shipping type Number of recipient Indicator: order combination Complete delivery indicator Order reason Description order reason

No processing No processing No processing No processing No processing No processing No processing No processing Is transferred to the document Is transferred to the document No processing No processing Is transferred to the document Is transferred to the document Is transferred to the document No processing Is transferred to the document No processing

Billing category Delivery note block Description: delivery note block Receiving point Department number Agreed delivery time Rate with indirect quotation

No processing Is transferred to the document No processing Is transferred to the document No processing No processing No processing

Document Item: General Data (Segment E1J3P01) Mandatory segment: NO Field POSEX Short text Item Number Explanation 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. Not relevant for incoming orders Indicator for the item category. The (one-digit) numeric indicator is converted in the sales item category
Pgina 28

ACTION PSTYP

Action code that concerns the item. Item Category

SAP AFS

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 MENGE Indicator for the order acknowledgment requirement Quantity No processing Ordered quantity of the item. Note: The quantity that is relevant for the document item is always taken from segment E1EDP20. MENEE BMNG2 PMENE ABFTZ VPREI PEINH NETWR ANETW SKFBP NTGEW GEWEI EINKZ CURCY PREIS MATKL UEPOS Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Discountable amount Net Weight Weight Unit Indicator: More than one schedule line for the item Currency Gross price Material class Superior item in bill of material structures ISO code of the unit of measure for the order quantity No processing ISO code of the price unit of measure No processing Customer-expected net price Price Unit Customer-expected net value No processing No processing No processing No processing No processing Currency code No processing No processing 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. No processing No processing No processing

GRKOR EVERS BPUMN BPUMZ ABGRU ABGRT ANTLF

Delivery group (items are delivered together) Shipping Instruction Denominator for the Conversion BPRME into BME

Numerator for the Conversion BPRME into No processing BME Reason for item rejection Description Maximum number of permitted partial deliveries per item Is transferred to document item. No processing Is transferred to document item.

SAP AFS

Pgina 29

FIXMG KZAZU J_3APOSNR J_3AMSOM

Delivery date and quantity fixed Indicator: order combination Item Number Equal mix of products in a multi-store order

No processing Is transferred to document item. Internal usage 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. Dimension requirements for an item are grouped, if this indicator is set. Is transferred to document item. Is transferred to document item. Is transferred to document item. Is transferred to document item or schedule line Is transferred to document item. Is transferred to document item. No processing No processing No processing No processing No processing No processing 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. 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. Is transferred to document item. No processing No processing Is transferred to document item. No processing No processing
Pgina 30

J_3ABZUS J_3ADEPM J_3ASPLIT J_3ASEAN J_3ASIZE J_3ALNGR J_4KRCAT J_4KSCAT BRGEW VOLUM VOLEH J_3AVASIT J_3AEBTYP J_3AMSOF

Requirements grouping Department AFS Split indicator Season indicator AFS grid value AFS Line group ID (schedule lines are delivered together) Requirements Category Stock Category Total Weight Volume Volume Unit VAS Item values ticketing/labeling (E), packing (V), special service (S) Order confirmation category AFS Multi-store order: counter for partner

PSTYV

Item category sales document

EMPST ABTNR ABRVW WERKS LPRIO LPRIO_BEZ


SAP AFS

Receiving point Department number Usage indicator Plant Delivery priority Description

ROUTE ROUTE_BEZ LGORT VSTEL DELCO MATNR

Route Description Storage location Shipping point Agreed delivery time Material identification

No processing No processing No processing No processing No processing 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:
SAP AFS

Standard (= non-AFS) Material AFS material with dimensions AFS material without dimensions (without a grid)
Pgina 31

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.

SAP AFS

Pgina 32

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 QUALF Short text Organization Indicator Explanation 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. See field QUALF.

ORGID

Organization Indicator

The following indicators are processed in the inbound IDoc: 006 007 008 010 Division Distribution Channel Sales Organization Sales Group

SAP AFS

Pgina 33

012 016 019 J01

Order Type Sales Office Purchase Order Type (SD) 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) Mandatory segment: NO Field IDDAT Short text Indicator for Date Segment Explanation Indicator for the use of the date / time entries in the following fields. Is transferred to the document Is transferred to the document 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.

DATUM UZEIT J_3AQUALF

Date Time Indicator

The following date indicators are relevant for contracts: 006 014 AFS Cancellation Date Validity start date for outline agreements

Please note that the AFS cancellation date for contracts is interpreted as the validity end date. The validity start date (014) and the validity end date (006) are checked by the inbound function. This means that if one of these dates is in the past (the reference date is the current system date), the processing terminates with the error 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.

SAP AFS

Pgina 34

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 QUALF BELNR POSNR DATUM UZEIT Short text Reference document indicator Document number Item Number Date Time Explanation For the identification of the subsequent document number. Document number Item number of the document Document date 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 QUALF IDTNR KTEXT MFRPN MFRNR Explanation IDoc object identification (such as material number, customer, and so on) Material identification Short text Manufacturer part number Manufacturer number

The segment is not used in the outbound quotation. The object identification is sent with the segment E1J3AIM. Document Item General Data Field POSEX ACTION Short text Item Number Action code that concerns the item. Explanation Item number from a customer order. 000 - item unchanged 001 - item changed

SAP AFS

Pgina 35

003 - item deleted PSTYP Item Category One-digit numerical indicator for the item category. The indicator is converted into the sales item category depending on the order type, using the table EDPST. N/A Ordered quantity of the item. Please note: for AFS materials with dimensions, the quantity ordered is per dimension. MENEE BMNG2 PMENE ABFTZ VPREI Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Agreed Cumulative Quantity Price (net) ISO code of the unit of measure for the order quantity N/A ISO code of the price unit of measure N/A Price per price unit. Please note: for AFS materials with dimensions, the price here is per dimension. Price Unit Net value. For AFS materials with dimensions, the value here is per dimension. N/A N/A Is copied from the document. ISO code of the weight unit X, if more than one schedule line exists for the item. ISO code for currency N/A Is copied from the document. Is copied from the document. Is copied from the document. N/A N/A N/A Is copied from document item or

KZABS MENGE

Indicator for the order acknowledgment requirement Quantity

PEINH NETWR

Price Unit Value of Item (net)

ANETW SKFBP NTGEW GEWEI EINKZ CURCY PREIS MATKL UEPOS GRKOR EVERS BPUMN BPUMZ ABGRU

Absolute Net Value of the Item Discountable amount Net Weight Weight Unit Indicator: More than one schedule line for the item Currency Gross price Material class Superior item in bill of material structures Delivery group (items are delivered together) Shipping Instruction Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Reason for item rejection

SAP AFS

Pgina 36

schedule line. ABGRT ANTLF FIXMG KZAZU J_3APOSNR J_3AMSOM J_3ABZUS J_3ADEPM J_3ASPLIT J_3ASEAN J_3ASIZE J_3ALNGR J_4KRCAT J_4KSCAT BRGEW VOLUM VOLEH J_3AVASIT J_3AEBTYP J_3AMSOF PSTYV EMPST ABTNR ABRVW WERKS LPRIO LPRIO_BEZ ROUTE ROUTE_BEZ LGORT VSTEL DELCO MATNR
SAP AFS

Description Maximum number of permitted partial deliveries per item Delivery date and quantity fixed Indicator: order combination Item Number Equal mix of products in a multi-store order Requirements grouping Department AFS Split indicator Season indicator AFS Grid Value AFS Line group-ID (schedule lines are delivered together) Requirements Category Stock Category Total Weight Volume Volume Unit VAS Item values ticketing/labeling (E), packing (V), special service (S) Order confirmation category AFS Multi-store order counter for partner Item category sales document Receiving point Department number Usage indicator Plant Delivery priority Description Route Description Storage location Shipping point Agreed delivery time Material identification

Text for reason for rejection ABGRU Is copied from the document. Is copied from the document. N/A Schedule line number of dimension Mix ID for multi-store order. Is copied from the document. Is copied from the document. Is copied from the document. Is copied from the document. N/A Is copied from the document. N/A N/A Is copied from the document item N/A N/A Is copied from the document. N/A N/A N/A Is copied from the document item N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Pgina 37

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 POSEX ACTION Short text Item Number Action code that concerns the item. Explanation Item number from a customer order. 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 depending on the order type, using the table EDPST. N/A

KZABS

Indicator for the order acknowledgment

SAP AFS

Pgina 38

requirement MENGE Quantity Ordered quantity of the item. For AFS materials with dimensions, the ordered quantity here is per dimension. MENEE BMNG2 PMENE ABFTZ VPREI Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Agreed Cumulative Quantity Price (net) ISO code of the unit of measure for the order quantity N/A ISO code of the price unit of measure N/A Price per price unit. For AFS materials with dimensions, the price here is per dimension. Price Unit Net value. For AFS materials with dimensions, the value here is per dimension. N/A N/A - is copied from the documentISO code of the weight unit X, if more than one schedule line exists for the item. ISO code for currency N/A - is copied from the document- is copied from the document- is copied from the documentN/A N/A

PEINH NETWR

Price Unit Value of Item (net)

ANETW SKFBP NTGEW GEWEI EINKZ CURCY PREIS MATKL UEPOS GRKOR EVERS BPUMN BPUMZ ABGRU ABGRT ANTLF FIXMG KZAZU

Absolute Net Value of the Item Discountable amount Net Weight Weight Unit Indicator: More than one schedule line for the item Currency Gross price Material class Superior item in bill of material structures Delivery group (items are delivered together) Shipping Instruction Denominator for the Conversion BPRME into BME

Numerator for the Conversion BPRME into N/A BME Reason for item rejection Description Maximum number of permitted partial deliveries per item Delivery date and quantity fixed Indicator: order combination Is copied from document item or schedule line. Text for reason for rejection ABGRU - is copied from the document- is copied from the documentN/A

SAP AFS

Pgina 39

J_3APOSNR J_3AMSOM J_3ABZUS J_3ADEPM J_3ASPLIT J_3ASEAN J_3ASIZE J_3ALNGR J_4KRCAT J_4KSCAT BRGEW VOLUM VOLEH J_3AVASIT J_3AEBTYP J_3AMSOF PSTYV EMPST ABTNR ABRVW WERKS LPRIO LPRIO_BEZ ROUTE ROUTE_BEZ LGORT VSTEL DELCO MATNR

Item Number Equal mix of products in a multi-store order Requirements grouping Department AFS Split indicator Season indicator AFS Grid Value AFS Line group-ID (schedule lines are delivered together) Requirements Category Stock Category Total Weight Volume Volume Unit VAS Item values ticketing/labeling (E), packing (V), special service (S) Order confirmation category AFS Multi-store order counter for partner Item category sales document Receiving point Department number Usage indicator Plant Delivery priority Description Route Description Storage location Shipping point Agreed delivery time Material identification

Schedule line number of dimension Mix key for multi-store order. - is copied from the document- is copied from the document- is copied from the document- is copied from the document- is copied from the document- is copied from the document- is copied from the documentThe stock category is converted from the requirements category Is copied from the document item N/A N/A - is copied from the documentN/A N/A N/A Is copied from the document item N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A 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.

SAP AFS

Pgina 40

Document Header: General Data (Segment E1EDK01) Field ACTION Short text Action code that concerns the entire EDI message Order acknowledgment requirement indicator Currency code EDI local currency Exchange rate Term of payment VAT registration number VAT registration number Document type Document number Net Weight Gross weight Weight Unit Remuneration list type Unloading point Order number addition of customer Shipping condition Description of shipping type Number of recipient Indicator: order combination Complete delivery indicator Order reason Description order reason Explanation 000 = order unchanged 004 = order changed kzabs CURCY HWAER WKURS ZTERM kundeuinr eigenuinr BSARt BELNR ntgew brgew gewei fkart_rl ABLAD BSTZD VSART VSART_BEZ REcipnt_no kzazu autlf augru augru_bez abrvw abrvw_bez fktyp lifsk lifsk_bez
SAP AFS

N/A ISO currency code for the entire document N/A Exchange rate from document header Term of payment from document header N/A N/A Order type from order header Order number N/A N/A N/A N/A N/A Order number of customer Shipping condition from order header Description for shipping condition Customer number of the ordering party - is copied from the document- is copied from the document- is copied from the document- is copied from the document- is copied from the document- is copied from the document-

Billing category Delivery note block Description: delivery note block - is copied from the document- is copied from the documentPgina 41

empst abtnr delco wkurs_m

Receiving point Department number Agreed delivery time Rate with indirect quotation

- is copied from the documentN/A N/A N/A

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). AFS Special Features 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.
SAP AFS Pgina 42

Customer Enhancements (User Exits) 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. 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.

SAP AFS

Pgina 43

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.

3.2.8.2 Technical Information: Invoices


Additional segments and segment fields are to be sent with AFS-specific information. Segment E1J3P01 Field J_3APOSNR J_3ADEPM Description Item number Department Comments / Remarks Number of the item in the current document It is used to uniquely identify the item. indicates the department for which the customer ordered the goods. It can be used for printing on labels and documents. Grid Value AFS Line Group indicator Line Group indicator specified several schedule lines for one delivery Requirement Category Stock category Indicates additional information about type of requirement Category assigned to a stockable item.

J_3ASIZE J_3ALNGR J_4KRCAT J_4KSCAT

Segment E1J3AIT - AFS IDoc: VAS Ticketing / Labelling Segment Field J_3ASTORE J_3ATLTYP J_3ATLMAT J_3ACHARC Description MSO Stores VAS Ticketing/Label Type VAS Ticketing/Labelling Material VAS Charge Code Comments / Remarks MSO Stores from J_3AVATL indicates which type of ticket or label is used Value added service tick./label. material 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 VAS Field 1 for Free Use by Customer VAS customer defined field 2 VAS customer defined field 3
Pgina 44

J_3AFIELD1 J_3AFIELD2 J_3AFIELD3


SAP AFS

J_3AVASPQ J_3AVASPO J_3AVASETE

Quantity VAS generated item number VAS generated schedule line number

Segment E1J3AIX - VAS Ticketing / Labelling Text Segment Field J_3ATLTXT Description Additional Text for Ticketing/Labelling VAS Text1 VAS Text1 VAS Text1 Comments / Remarks Description or additional information can be maintained for VAS Ticketing / Labeling as additional text field. J_3ATLORD from J_3AVATLX J_3ATLITEM from J_3AVATLX J_3ATLSIZE from J_3AVATLX

J_3ATLORD J_3ATLITEM J_3ATLSIZE

Segment E1J3AIP - AFS IDoc: VAS Packing Segment Field Description MSO Stores VAS Packing Type VAS Packing Material VAS Charge Code Comments / Remarks MSO Stores from J_3AVAP Type of packing material Value added service packing material. 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. Quantity that can be packed into the packaging Indicates whether and how packaging can pack items, sizes, colors etc. together. This is an information only field. VAS Field 1 for Free Use by Customer VAS customer defined field 2 VAS customer defined field 3 Quantity VAS generated item number VAS generated schedule line number VAS Processed Quantity J_3AVASPO from J_3AVAP J_3AVASETE from J_3AVAP

J_3ASTORE
J_3APTYP J_3APMAT J_3ACHARC

J_3AINCREM J_3AMIXID

VAS Packing Increment Mix Indicator Group for VAS Packing Types

J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AVASPO J_3AVASETE

Segment E1J3AIS - AFS IDoc: VAS Special Services Segment Field J_3ASTORE
SAP AFS

Description MSO Stores

Comments / Remarks MSO Stores from J_3AVASSO


Pgina 45

J_3ASSTYP J_3ASSMAT J_3ACHARC J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AUPDKZ J_3AVASPO J_3AVASETE

VAS Special Services Type VAS Special Services Material VAS Charge Code

Indicates the type of special service Description of material used for Special Services in VAS

VAS Field 1 for Free Use by Customer VAS customer defined field 2 VAS customer defined field 3 Quantity Update indicator VAS generated item number VAS generated schedule line number VAS Processed Quantity

SAP AFS

Pgina 46

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. Document type Direction Request for Quotation Outbound Logical Message REQOTE ORDERS ORDCHG ORDRSP BLAORD BLAOCH DESADV INVOIC IDoc Type /AFS/ORDERS04 /AFS/ORDERS04 /AFS/ORDERS04 /AFS/ORDERS04 /AFS/BLAORD03 /AFS/BLAORD03 /AFS/DELVRY02 /AFS/INVOIC02 J3AV J3AV Output type NEU (new) NEU (new) NEU (new) Process Code ME12 ME10 ME11 ORDR /AFS/ME15 /AFS/ME16 DELS INVL

Purchase Order Outbound Purchase Order Outbound Change Purchase Order Receipt Confirmation Contracts Contract Change Delivery Announcement Invoice Receipt Outbound Outbound Receipt Receipt

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.

SAP AFS

Pgina 47

3.3.2.1 Technical (Purchasing)

Information:

Request

for

Quotation

Technical Description of the IDoc Type Document type Direction Request for Quotation Outbound Logical Message REQOTE IDoc Type /AFS/ORDERS04 Output type NEU (new) Process Code ME12

AFS-Specific Fields for the Request for Quotation Segment E1J3K03 E1J3K03 Field IDDAT DATUM Explanation AFS Indicator for IDoc date segment IDoc: Date 001: Purchase order date 003: Requested delivery date 004: Delivery date 008: Final date for application 009: Deadline for submission of quotations 010: Quotation Date 012: IDoc creation date 013: Binding period for quotation (valid to) EKKO-BEDAT EKKO-EINDT EKKO-EINDT EKKO-BWBDT EKKO-ANGDT EKKO-IHRAN SY-DATLO EKKO-BNDDT Origin

014: Validity start date for outline agreement or request EKKO-KDATB for quotation EKKO-KDATE 015: Validity end date for outline agreement or request for quotation E1J3P01 POSEX PSTYP KZABS MENGE Item Number Item Category Indicator for the order acknowledgment requirement Quantity EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKET-MENGE MENEE BMNG2 PMENE Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure EKPO-MEINS EKPO-KTMNG EKPO-BPRME

SAP AFS

Pgina 48

BPUMN BPUMZ ABFTZ VPREI PEINH NETWR

Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net)

EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMVKBETR EKPO-PEINH EKPO-NETWR o. KOMV-KWERT

AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT E1J3AIM J_3AOBIDQF J_3ASIZE J_3AIDTNR

Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS Grid Value Requirements Category Stock Category AFS IDoc object identification (material number,...) AFS grid value IDoc material identification 001: Customer material number 002: Vendor material number 003: International article number (EAN) 004: Universal Product Code UPC 005: Universal Commercial Code UCC

EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

EKET-J_3ASIZE

EKPO-EMATN EKET-J_3AVEMA EKET-J_3AVIEAN EKET-J_3AVIEAN EKET-J_3AUCCMR EKPO-TXZ01

J_3AKTEXT J_3AKRCAT J_3AKSCAT E1EDPO02 QUALF


SAP AFS

IDoc short text Requirements Category Stock Category IDoc indicator reference document

EKET-J_4KSCAT

Pgina 49

BELNR

IDoc document number J30: ALE Identifier EKET-/AFS/ALE_ID.

E1J3P03

IDDAT DATUM

AFS indicator for IDoc date segment IDoc: Date 003: Requested delivery date 004: Delivery date 009: Deadline for submission of quotations 016: Reconciliation date for agreed cumulative quantity 017: First firm/trade-off zone 018: Second firm/trade-off zone SY-DATLO+EKPOETFZ2 EKPO-J_3ADAT EKPO-J_3ADAT EKPO-AGDAT EKPO-ABDAT SY-DATLO+EKPOETFZ1

E1EDP19

QUALF

IDoc object identification (for example, customer material number) 001: Customer material number 002: Vendor material number

IDTNR

IDoc material identification EKET-J_3AVEMA EKPO-IDNLF EKPO-MATNR EKPO-EMATN

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.1 Technical Information: Purchase Order (Purchasing)


Technical Description of the IDoc Type Document type Direction Purchase Order
SAP AFS

Logical Message ORDERS

IDoc Type /AFS/ORDERS04

Output type NEU (new)

Process Code ME10


Pgina 50

Outbound

AFS-Specific Fields for the Purchase Order Segment E1J3K03 E1J3K03 Field IDDAT DATUM Explanation AFS Indicator for IDoc date segment IDoc: Date 001: Purchase order date 003: Requested delivery date 004: Delivery date 008: Final date for application 009: Deadline for submission of quotations 010: Quotation Date 012: IDoc creation date 013: Binding period for quotation (valid to) 014: Validity start date for outline agreement or request for quotation 015: Validity end date for outline agreement or request for quotation E1J3P01 POSEX PSTYP KZABS MENGE Item Number Item Category Indicator for the order acknowledgment requirement Quantity EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKET-MENGE MENEE BMNG2 PMENE BPUMN BPUMZ ABFTZ VPREI PEINH NETWR Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMVKBETR EKPO-PEINH EKPO-NETWR or KOMV-KWERT
SAP AFS Pgina 51

Origin

EKKO-BEDAT EKKO-EINDT EKKO-EINDT EKKO-BWBDT EKKO-ANGDT EKKO-IHRAN SY-DATLO EKKO-BNDDT EKKO-KDATB EKKO-KDATE

AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT E1J3AIM J_3AOBIDQF J_3ASIZE J_3AIDTNR

Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS Grid Value Requirements Category Stock Category AFS IDoc object identification (material number,...) AFS Grid Value IDoc material identification 001: Customer material number 002: Vendor material number 003: International article number (EAN) 004: Universal Product Code UPC 005: Universal Commercial Code UCC

EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

EKET-J_3ASIZE

EKPO-EMATN EKET-J_3AVEMA EKET-J_3AVIEAN EKET-J_3AVIEAN EKET-J_3AUCCMR EKPO-TXZ01

J_3AKTEXT J_3AKRCAT J_3AKSCAT E1EDP02 QUALF BELNR

IDoc short text Requirements Category Stock Category IDoc indicator reference document IDoc document number J30: ALE Identifier

EKET-J_4KSCAT

EKET-/AFS/ALE_ID.

E1J3P03

IDDAT DATUM

AFS Indicator for IDoc date segment IDoc: Date 003: Requested delivery date 004: Delivery date EKPO-J_3ADAT EKPO-J_3ADAT

SAP AFS

Pgina 52

009: Deadline for submission of quotations 016: Reconciliation date for agreed cumulative quantity 017: First firm/trade-off zone 018: Second firm/trade-off zone E1EDP19 QUALF IDoc object identification (for example, customer material number) 001: Customer material number 002: Vendor material number IDTNR IDoc material identification

EKPO-AGDAT EKPO-ABDAT SY-DATLO+EKPO-ETFZ1 SY-DATLO+EKPO-ETFZ2

EKET-J_3AVEMA or EKPO-IDNLF EKPO-MATNR or EKPO-EMATN

3.3.4 Purchase Order Change


Changes in a purchase order item are flagged using the Action Flag in segment E1J3P01. Only the changed schedule lines or all the schedule lines of the relevant item are in the IDoc. If a change in the schedule line affects the item, all schedule lines will be sent. The following changes are possible at header level: Header texts

The following changes are possible at item level: Terms of delivery Delivery and 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.

SAP AFS

Pgina 53

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)


Technical Description of the IDoc Type Document type Direction Purchase Order Change Outbound Logical Message ORDCHG IDoc Type /AFS/ORDERS04 Output type NEU (new) Process Code ME11

AFS-Specific Fields for the Purchase Order Change Segment E1J3K03 E1J3K03 Field IDDAT DATUM Explanation AFS Indicator for IDoc date segment IDoc: Date 001: Purchase order date 003: Requested delivery date 004: Delivery date 008: Final date for application 009: Deadline for submission of quotations 010: Quotation Date 012: IDoc creation date 013: Binding period for quotation (valid to) 014: Validity start date for outline agreement or request for quotation 015: Validity end date for outline agreement or request for quotation E1J3P01 POSEX PSTYP Item Number Item Category EKPO-EBELP EKPO-PSTYP EKKO-BEDAT EKKO-EINDT EKKO-EINDT EKKO-BWBDT EKKO-ANGDT EKKO-IHRAN SY-DATLO EKKO-BNDDT EKKO-KDATB EKKO-KDATE Origin

SAP AFS

Pgina 54

KZABS MENGE

Indicator for the order acknowledgment requirement Quantity

EKPO-KZABS EKPO-KTMNG or EKET-MENGE

MENEE BMNG2 PMENE BPUMN BPUMZ ABFTZ VPREI PEINH NETWR AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT E1J3AIM J_3AOBIDQF J_3ASIZE J_3AIDTNR

Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS grid value Requirements Category Stock Category AFS IDoc object identification (material number,...) AFS grid value IDoc material identification 001: Customer material number 002: Vendor material number 003: International article number (EAN)

EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMVKBETR EKPO-PEINH EKPO-NETWR or KOMV-KWERT EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR or EKPOAFS_POSNR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

EKET-J_3ASIZE

EKPO-EMATN EKET-J_3AVEMA EKET-J_3AVIEAN

SAP AFS

Pgina 55

004: Universal Product Code UPC 005: Universal Commercial Code UCC J_3AKTEXT J_3AKRCAT J_3AKSCAT E1EDP02 QUALF BELNR IDoc short text Requirements Category Stock Category IDoc indicator reference document IDoc document number J30: ALE Identifier E1J3P03 IDDAT DATUM AFS Indicator for IDoc date segment IDoc: Date 003: Requested delivery date 004: Delivery date 009: Deadline for submission of quotations 016: Reconciliation date for agreed cumulative quantity 017: First firm/trade-off zone 018: Second firm/trade-off zone

EKET-J_3AVIEAN EKET-J_3AUCCMR EKPO-TXZ01

EKET-J_4KSCAT

EKET-/AFS/ALE_ID.

EKPO-J_3ADAT EKPO-J_3ADAT EKPO-AGDAT EKPO-ABDAT SY-DATLO+EKPOETFZ1 SY-DATLO+EKPOETFZ2

E1EDP19

QUALF

IDoc object identification (for example, customer material number) 001: Customer material number 002: Vendor material number

IDTNR

IDoc material identification EKET-J_3AVEMA or EKPO-IDNLF EKPO-MATNR or EKPO-EMATN

SAP AFS

Pgina 56

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.

3.3.5.1 Technical (Purchasing)

Information:

Order

Confirmation

Technical Description of the IDoc Type Document type Purchase Order Confirmation Direction Inbound Logical Message ORDRSP IDoc Type /AFS/ORDERS04 Output type Process Code ORDR

AFS-Specific Fields for Order Confirmation Segment E1J3K03 E1J3K03 Field IDDAT DATUM Explanation AFS Indicator for IDoc date segment IDoc: Date 001: Purchase order date EKKO-BEDAT Origin

SAP AFS

Pgina 57

003: Requested delivery date 004: Delivery date 008: Final date for application 009: Deadline for submission of quotations 010: Quotation Date 012: IDoc creation date 013: Binding period for quotation (valid to) 014: Validity start date for outline agreement or request for quotation 015: Validity end date for outline agreement or request for quotation E1J3P01 POSEX PSTYP KZABS MENGE MENEE BMNG2 PMENE BPUMN BPUMZ ABFTZ VPREI PEINH NETWR AENTW NTGEW GEWEI MATKL EVERS BRGEW Item Number Item Category Indicator for the order acknowledgment requirement Quantity Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight

EKKO-EINDT EKKO-EINDT EKKO-BWBDT EKKO-ANGDT EKKO-IHRAN SY-DATLO EKKO-BNDDT EKKO-KDATB EKKO-KDATE

EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKETMENGE EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMVKBETR EKPO-PEINH EKPO-NETWR or KOMVKWERT EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW

SAP AFS

Pgina 58

VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT E1J3AIM J_3AOBIDQF J_3ASIZE J_3AIDTNR

Volume Volume Unit Item Number AFS grid value Requirements Category Stock Category AFS IDoc object identification (material number,...) AFS grid value IDoc material identification 001: Customer material number 002: Vendor material number 003: International article number (EAN) 004: Universal Product Code UPC 005: Universal Commercial Code UCC

EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

EKET-J_3ASIZE

EKPO-EMATN EKET-J_3AVEMA EKET-J_3AVIEAN EKET-J_3AVIEAN EKET-J_3AUCCMR EKPO-TXZ01

J_3AKTEXT J_3AKRCAT J_3AKSCAT E1EDP02 QUALF BELNR

IDoc short text Requirements Category Stock Category IDoc indicator reference document IDoc document number J30: ALE Identifier

EKET-J_4KSCAT

EKET-/AFS/ALE_ID.

E1J3P03

IDDAT DATUM

AFS Indicator for IDoc date segment IDoc: Date 003: Requested delivery date 004: Delivery date 009: Deadline for submission of quotations 016: Reconciliation date for agreed cumulative quantity 017: First firm/trade-off zone 018: Second firm/trade-off zone EKPO-J_3ADAT EKPO-J_3ADAT EKPO-AGDAT EKPO-ABDAT SY-DATLO+EKPO-ETFZ1 SY-DATLO+EKPO-ETFZ2

E1EDP19

QUALF

IDoc object identification (for example, customer material number)

SAP AFS

Pgina 59

001: Customer material number 002: Vendor material number IDTNR IDoc material identification 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)


Technical Description of the IDoc Type Document type Contract Direction Outbound Logical Message BLAORD IDoc Type /AFS/BLAORD03 Output type J3AV Process Code /AFS/ME15

AFS-Specific Fields for Contracts Segment E1J3P01 Field POSEX PSTYP KZABS MENGE MENEE BMNG2 PMENE BPUMN BPUMZ Explanation Item Number Item Category Indicator for the order acknowledgment requirement Quantity Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Origin EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKET-MENGE EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ

SAP AFS

Pgina 60

ABFTZ VPREI PEINH NETWR AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT

Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS grid value Requirements Category Stock Category

EKPO-ABFTZ EKPO-NETPR or KOMV-KBETR EKPO-PEINH EKPO-NETWR or KOMV-KWERT EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT 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)


Technical Description of the IDoc Type Document type Direction Contract Change Outbound Logical Message BLAOCH IDoc Type /AFS/BLAORD03 Output type J3AV Process Code /AFS/ME16

SAP AFS

Pgina 61

AFS-Specific Fields for Changing Contracts Segment E1J3P01 Field POSEX PSTYP KZABS MENGE MENEE BMNG2 PMENE BPUMN BPUMZ ABFTZ VPREI PEINH NETWR AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT Explanation Item Number Item Category Indicator for the order acknowledgment requirement Quantity Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the conversion BPRME into BME Numerator for the conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS grid value Requirements Category Stock Category Origin EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKET-MENGE EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMV-KBETR EKPO-PEINH EKPO-NETWR or KOMV-KWERT EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

SAP AFS

Pgina 62

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. In order to uniquely identify an item/schedule line in a purchase order, you need the following 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

Technical Description of the IDoc Type Document type Direction Delivery Notification Inbound Logical Message DESADV IDoc Type /AFS/DELVRY02 Output type Process Code DELS

AFS-Specific Fields for the Delivery Notification Segment E1J3ABH Field J_3AEVRTN J_3ABILNR J_3ABILDT J_3ABILTY /AFS/LANGUA_ISO /AFS/E1EDL24 J_3ALNGR Explanation Number of the preceding document Billing document number IDoc: Date Invoice category of the vendor Language indicator for address AFS line group indicator

SAP AFS

Pgina 63

J_3ADEPM /AFS/E1J3AKG J_3AKVGR6 BEZEI6 J_3AKVGR7 BEZEI7 J_3AKVGR8 BEZEI8 J_3AKVGR9 BEZEI9 J_3AKVGR10 BEZEI10 E1J3AI2 J_3AQFREF J_3ABELNR J_3APOSNR J_3AETENR J_3ADATUM J_3AUZEIT J_AZUDATR E1J3AIM J_3AOBIDQF J_3ASIZE J_3AIDTNR

Department AFS additional data customer group 6 Description AFS additional data customer group 7 Description AFS additional data customer group 8 Description AFS additional data customer group 9 Description AFS additional data customer group 10 Description IDoc indicator reference document IDoc document number Item Number Schedule line number Date Time Additional data AFS IDoc object identification (material number,...) AFS grid value IDoc material identification 001: Customer material number 002: Vendor material number 003: International article number (EAN) 004: Universal Product Code UPC 005: Universal Commercial Code UCC

J_3AKTEXT J_3AKRCAT J_3AKSCAT E1JAIP J_3ASTORE J_3APTYP

IDoc short text Requirements Category Stock Category MSO Stores VAS Packing Type

SAP AFS

Pgina 64

J_3APMAT J_3ACHARC J_3AINCREM J_3AMIXIND J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AUPDKZ J_3AVASPO J_3AVASETE E1J3AIS J_3ASTORE J_3ASSTYP J_3ASSMAT J_3ACHARC J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AUPDKZ J_3AVASPO J_3AVASETE E1J3ABI J_3AUPCNR J_3AUCCNR J_3ABALNR J_3ADLNR J_3ASHGR J_3APCNR J_3ACTNR J_3ASQNR J_3AWDTH J_3ASEDE

VAS Packing Material VAS Charge Code VAS Packing: Increment Mix ID for VAS packing types VAS User-Defined Field 1 VAS User-Defined Field 2 VAS User-Defined Field 3 Quantity Update Indicator VAS Generated Subitem Number VAS Generated Sub-Schedule Line Number MSO Stores VAS Special Services: Category VAS Special Services Material VAS Charge Code VAS User-Defined Field 1 VAS User-Defined Field 2 VAS User-Defined Field 3 Quantity Update Indicator VAS Generated Subitem Number VAS Generated Sub-Schedule Line Number Style code / UPC UCC Number Vendor bale number Dye lot number Shade group Piece number Cut number Bale sequence number Width Flag: Deltas

SAP AFS

Pgina 65

J_3ADERL J_3ADERA J_3ADERB /AFS/LANGUA_ISO

Degree of color difference (darker-lighter) Degree of color difference (greener redder) Degree of color difference (bluer yellower) 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.)


In order to uniquely identify an item/schedule line in a purchase order, you need the following 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. Technical Description of the IDoc Type Document Type Invoice Receipt Direction Logical Message Inbound INVOIC IDoc Type /AFS/INVOIC02 Output Type Process Code INVL

SAP AFS

Pgina 66

AFS-Specific Fields for the Invoice Receipt and Verification Segment E1J3P01 Field POSEX PSTYP KZABS MENGE MENEE BMNG2 PMENE BPUMN BPUMZ ABFTZ VPREI PEINH NETWR AENTW NTGEW GEWEI MATKL EVERS BRGEW VOLUM VOLEH J_3APOSNR J_3ASIZE J_4KRCAT J_4KSCAT E1JAIP J_3ASTORE J_3APTYP Explanation Item Number Item Category Indicator for the order acknowledgment requirement Quantity Unit of Measure Quantity in Price Unit of Measure Price Unit of Measure Denominator for the Conversion BPRME into BME Numerator for the Conversion BPRME into BME Agreed Cumulative Quantity Price (net) Price Unit Value of Item (net) Absolute Net Value of the Item Net Weight Weight Unit IDoc Material Class Shipping Instruction Total Weight Volume Volume Unit Item Number AFS Grid Value Requirements Category Stock Category MSO Stores VAS Packing Type Origin EKPO-EBELP EKPO-PSTYP EKPO-KZABS EKPO-KTMNG or EKET-MENGE EKPO-MEINS EKPO-KTMNG EKPO-BPRME EKPO-BPUMN EKPO-BPUMZ EKPO-ABFTZ EKPO-NETPR or KOMV-KBETR EKPO-PEINH EKPO-NETWR or KOMV-KWERT EKPO-NETWR EKPO-NTGEW EKPO-GEWEI EKPO-MATKL EKPO-EVERS EKPO-BRGEW EKPO-VOLUM EKPO-VOLEH EKET-ETENR EKET-J_3ASIZE EKET-J_4KSCAT EKET-J_4KSCAT

SAP AFS

Pgina 67

J_3APMAT J_3ACHARC J_3AINCREM J_3AMIXIND J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AUPDKZ J_3AVASPO J_3AVASETE E1J3AIS J_3ASTORE J_3ASSTYP J_3ASSMAT J_3ACHARC J_3AFIELD1 J_3AFIELD2 J_3AFIELD3 J_3AVASPQ J_3AUPDKZ J_3AVASPO J_3AVASETE

VAS Packing Material VAS Charge Code VAS Packing Increment VAS Packing Mix Indicator VAS User-Defined Field 1 VAS User-Defined Field 2 VAS User-Defined Field 3 Quantity Update Indicator VAS Generated Subitem Number VAS Generated Sub-Schedule Line Number MSO Stores VAS Special Services Category VAS Special Services Material VAS Charge Code VAS User-Defined Field 1 VAS User-Defined Field 2 VAS User-Defined Field 3 Quantity Update Indicator VAS Generated Subitem Number VAS Generated Sub-Schedule Line Number

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:
SAP AFS

via direct input via Application Link Enabling (ALE)


Pgina 68

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.

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


Technical Description of the IDoc Type Document type Direction Logical Message WMMBXY IDoc type /AFS/WMMBID02 Process Code WMMB

Goods movement Inbound

AFS-Specific Fields for Goods Movement Segment Field E1J3XYI LFBJA LFBNR LFPOS J_3ASIZE J_3ABZUS J_3AUANR J_3AUPOS J_3AUEPS J_4KSCAT J_3AETENR J_3AVBELN J_3APOSNR Explanation Origin

Fiscal year of a reference document (required field MSEG-LFBJA for cancellations) Document number of a reference document (required field for cancellations) Item of a reference document (required field for cancellations) AFS grid value (required field for AFS material with dimensions) Requirements grouping AFS group requirements AFS origin main item AFS origin plan Stock category (required field for AFS materials with category) Schedule line number (required field for all materials) Sales document number Item number of the sales document MSEG-LFBNR MSEG-LFPOS MSEG-J_3ASIZE MSEG-J_3ABZUS MSEG-J_3AUANR MSEG-J_3AUPOS MSEG-J_3AUEPS MSEG-J_4KSCAT MSEG-J_3AETENR MSEG-J_3AVBELN MSEG-J_3APOSNR

SAP AFS

Pgina 69

J_3ALINUM J_3ALIPOS J_3AUMSIZ J_4KUMSCA

Delivery number Delivery item

MSEG-J_3ALINUM MSEG-J_3ALIPOS

AFS: receiving/issuing grid value (required field for MSEG-J_3AUMSIZ stock transfer of AFS materials with grid values) AFS: receiving/issuing stock category (required field for stock transfer of AFS materials with category) MSEG-J_4KUMSCA

J_4KUMSCA_4 AFS: receiving/issuing stock category

MSEG-J_4KUMSCA_4

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 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 output 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 for Distribution (ALE). Customer Enhancements (User Exits) In order to process user-defined data using ALE, you need to: 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. create a new IDoc segment

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.

SAP AFS

Pgina 70

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 Transfer of data from data pools

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


Technical Description of the IDoc Type Document type Bill of material Direction Inbound Logical Message J3ABOM IDoc Type J3ABOM01 Process Code J3AP

AFS-Specific Fields for Bills of Materials Segment E1J3ABG Field MSGFN J_3APGNR J_3AKORDX Explanation Function Material grid number Grid value Origin No processing J_3ABOMD-J_3APGNR J_3ABOMD-J_3AKORDX J_3ABOMDJ_3AKORDXL J_3ABOMD-MEINS J_3ABOMD-MENGE J_3ABOMD-J_3AZFLG No processing J_4KBOMC-J_4KSCAT

J_3AKORDXL Grid value MEINS MENGE J_3AZFLG E1J3ABC MSGFN J_4KSCAT Unit of Measure Quantity Quantity is zero Function Stock Category

SAP AFS

Pgina 71

J_4KKZEXCL J_4KKZINCL

Categories: excluding indicators Categories: including indicators

J_4KBOMCJ_4KKZEXCL J_4KBOMC-J_4KKZINCL

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 BOM maintenance occurs when the IDoc is processed, 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 for Distribution (ALE). Customer Enhancements (User Exits) 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. In order to process user-defined data using ALE, you need to: 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 create a new IDoc segment

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 Inbound and Outbound Logical Message /AFS/DISREQ IDoc Type /AFS/DISREQ01 Operation code /AFS/DISREQ

SAP AFS

Pgina 72

AFS-Specific Fields Segment /AFS/E1DR_HDR Field STYPE SPROF Explanation Distribution Type (material or profile) Distribution Profile Origin Value determined by generation program J_3APLPR-PROFP or J_3ACAPR-PROFC or J_3AGRPR-PROFG or J_3APEPR-PROFT MATNR Material J_3APLPR-MATNR or J_3ACAPR-MATNR or J_3AGRPR-MATNR or J_3APEPR-MATNR /AFS/E1DR_TEXT SP_M_DESCR Description of the distribution profile or material Language, ISO code MAKT-MAKTX or J_3ASPRT-SPRTX LANGU_ISO MAKT-SPRAS or J_3ASPRT-SPRAS /AFS/E1DR_OVR SPRTP WERKS Profile Category Plant Value determined by generation program J_3ACAPR-WERKS or J_3AGRPR-WERKS or J_3APEPR-WERKS RCATE Requirements Category 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
SAP AFS Pgina 73

PRGRS ENTLUE

Date Type (day, week, month, time period) Period Indicator

J_3APEPR-ENTLI J_3APEPR-ENTLI converted with table TPRG J_3ACAPR-COVST MARA-J_3APGNR or J_3ASPR-MGRID

COVST /AFS/E1DR_PGHD J_3APGNR

Coverage Strategy Material Grid Number

J_3AVDAT J_3ABZD1 J_3ABZD2 J_3ABZD3

Material Grid Valid from date ID of the first dimension ID of the second dimension ID of the third dimension

J_3AGRPR-VDATE J_3APGHD-J_3ABZD1 J_3APGHD-J_3ABZD2 J_3APGHD-J_3ABZD3 J_3APGHD-J_3ABZD1 J_3APGHD-J_3ABZD2 J_3APGHD-J_3ABZD3 J_3APLPR-WERKS J_3APLPR-FLWEI Value determined by generation program J_3APLPR-SISQU J_3APLPR-MEINS Function: J_4KG_GET_VALID_CAT Parameter: J_3ACAPR-WERKS, J_3ACAPR-COVST, R and PRC

J_3ABZD1_NEW ID of the first dimension J_3ABZD2_NEW ID of the second dimension J_3ABZD3_NEW ID of the third dimension /AFS/E1DR_PLPR WERKS FLWEI PERCE SISQU ISOCODE_UNIT /AFS/E1DR_CAPR RCATE Plant Distribution Profile Weight Distribution Profile Percentage Quantity of the last SIS selection Base Unit of Measure Requirements Category

FLWEI PERCE SISQU ISOCODE_UNIT /AFS/E1DR_GRPR J_3AKORDX J_3AKORD1

Distribution Profile Weight Distribution Profile Percentage Quantity of the last SIS selection Base Unit of Measure Grid value AFS: Coordinates of the first dimension

J_3ACAPR-FLWEI Value determined by generation program J_3ACAPR-SISQU J_3ACAPR-MEINS J_3APGEN-J_3AKORDX J_3APGEN-J_3AKORD1

SAP AFS

Pgina 74

J_3AKORD2 J_3AKORD3 FLWEI PERCE SISQU ISOCODE_UNIT /AFS/E1DR_PEPR PPART FLWEI PERCE SISQU ISOCODE_UNIT /AFS/E1DR_DITX J_3ABZD1_NEW

AFS: Coordinates of the second dimension AFS: Coordinates of the third dimension Distribution Profile Weight Distribution Profile Percentage Quantity of the last SIS selection Base Unit of Measure Period Part Distribution Profile Weight Distribution Profile Percentage Quantity of the last SIS selection Base Unit of Measure

J_3APGEN-J_3AKORD2 J_3APGEN-J_3AKORD3 J_3AGRPR-FLWEI Value determined by generation program J_3AGRPR-SISQU J_3AGRPR-MEINS J_3APEPR-PPART J_3APEPR-FLWEI Value determined by generation program J_3APEPR-SISQU J_3APEPR-MEINS J_3APGHD-J_3ABZD1 or J_3APGHD-J_3ABZD2 or J_3APGHD-J_3ABZD3

J_3ABEZT LANGU_ISO /AFS/E1DR_USED MATNR WERKS IDPL IDCA IDGR IDPE E1MAKTM MSGFN SPRAS MAKTX SPRAS_ISO /AFS/E1DR_SEAS WERKS SEASO
SAP AFS

Description of the dimension Language, ISO code Material number Plant Indicator: Distribution of Requirements to Plants Indicator: Distribution of Requirements to Categories Indicator: Distribution of Requirements to Grid Values Indicator: Distribution of Requirements to Periods Function Language Key Description of the Material Language, ISO code Plant Validity Period for Presizing

J_3ADITY-J_3ABEZT J_3ADITY-J_3ASPRA Generated from MARA and MARC Generated from MARA and MARC Value determined by generation program Value determined by generation program Value determined by generation program Value determined by generation program No processing MAKT-SPRAS MAKT-MAKTX MAKT-SPRAS J_3ASEAS-WERKS J_3ASEAS-SEASO
Pgina 75

NPERI DATE_FROM DATE_TO /AFS/E1DR_PRG PRGRS PRGBZ PRGTX PRITX LANGU_ISO

Number of Occurrence Date starting on which the validity period applies Date up to which the validity period applies Date Type (day, week, month, interval) External Date Type Description of the Date Type Period description in printout Language, ISO code

J_3ASEAS-NPERI J_3ASEAS-DATE1 J_3ASEAS-DATE2 J_3APEPR-ENTLI TPRG-PRGBZ TPRG-PRGTX TPRG-PRITX TPRG-SPRAS

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.

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


Technical Description of the IDoc Type Document type Confirmation
SAP AFS

Direction Inbound

Logical Message CONF21

IDoc type /AFS/CONF21

Process Code CON2


Pgina 76

AFS-Specific Fields for Confirmations Segment Field Explanation AFS grid value Marker indicator in planned orders/production orders Marker number Marker section Yield IST in ASCII Origin /AFS/RUECKJ_3ASIZE /AFS/RUECKJ_3AMKID /AFS/RUECKJ_3AMKNR /AFS/RUECKJ_3AMSECT /AFS/RUECKJ_3ALMNGA /AFS/RUECKJ_3AXMNGA /AFS/RUECKJ_3AMEINH

/AFS/E1MARKER J_3ASIZE J_3AMKID J_3AMKNR J_3AMSECT J_3ALMNGA

J_3AXMNGA Scrap quantity IST in ASCII J_3AMEINH Unit of Measure

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 When data is transferred using Application Link Enabling (ALE), it is subject to the same checks 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 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 for Distribution (ALE). 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.

SAP AFS

Pgina 77

3.5 Warehouse Management


The following logical messages are supported in warehouse management in AFS: Action/Object Transfer orders (issue and receipt) Logical Message WMTORD IDoc Type /AFS/WMTOID01 for the issue WMTOID01 for receipt Transfer requirements (receipt) Confirmation of transfer orders (receipt) Cancellation of a transfer order (issue and receipt) Create physical inventory (receipt) WMTREQ WMTOCO WMTRID01 WMTCID02

WMCATO

WMCAID01

WMINVE

WMIVID01

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

SAP AFS

Pgina 78

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 MARA AFS tables J_3AQDST J_3AMSEA 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 J_3AMSO J_3AVBUE J_3AVBFAE
SAP AFS

BOM additional item data MM/SD (application V1) Multi-store order (MSO) SD status for schedule lines Sales document flow for schedule line
Pgina 79

With application V1 J_3AVATL J_3AVAP J_3AVATLX J_3AVASSO VAS: ticketing/labeling data in sales order VAS: packing data in sales order VAS: ticketing/labeling data additional text data in sales order 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 J_3AVBFAE With application V3 J_3AVATL J_3AVAP J_3AVATLX J_3AVASSO VAS: ticketing/labeling data in order VAS: packing data in order VAS: ticketing/labeling data additional text data in order VAS: special services data in order SD status for schedule lines Sales document flow for schedule line

Affected programs (AFS-enhanced): 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 J_3AVAP J_3AVATLX J_3AVASSO VAS: ticketing/labeling data in order VAS: packing data in order VAS: ticketing/labeling data additional text data in order VAS: special services data in order

Affected programs (AFS-enhanced): S3LIKPWR write and archiving program S3LIKPDL delete program S3LIKPRL reload program

SAP AFS

Pgina 80

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 J_3ABDSI J_3AWESBS J_4AFLELKPO AFS stock (SKUs) stock type B AFS order (SKUs) requirements type LB (subcontracting) and TB (stock transfer), plan type B AFS goods receipt: blocked stock at SKU level AFS: Subitem in AFS contract

Affected programs (AFS-enhanced): RM06EW30 write and archiving program RM06ED30 delete program

Archiving Object MM_EBAN (Purchase Requisitions: Standard Table EBAN) J_3ABSSI J_3ABDSI AFS stock (SKUs) stock type A AFS order (SKUs) requirements type LB (subcontracting) and TB (stock transfer), plan type A

Affected programs (AFS-enhanced): 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

Affected programs (AFS-enhanced): RM06IW30 write and archiving program RM06ID30 delete program

Archiving Object MM_MATNR (Material Master: Segments A and C) MARA J_3AQDST J_3AMSEA MARC AFS material master: quota category for destination AFS material master: seasons

SAP AFS

Pgina 81

J_3AMAD J_3AMADKA J_3ATRAME MLGN /AFS/MLGN1 /AFS/MLGN2 /AFS/MLGN3 MLGT /AFS/MLGT MVKE /AFS/MVKE MARM /AFS/MARM

AFS material master: additional data AFS material master: valuation data AFS material master: stock in transit at SKU level

Material data for each warehouse number: dimension-specific Material data for each warehouse number: season-specific Material data for each warehouse number

Material data for each warehouse type

AFS sales data for material

Units of measure for material

Affected programs/function groups (AFS-enhanced): Function group WSO8 Function module REORGANISATION_MATERIAL Programs WSREOnnn (nnn for sequence number)

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 J_3ABUNDL AFRU (confirmation) AFS stock (SKUs) stock type F AFS bundles for production orders

SAP AFS

Pgina 82

J_3ABUAFRU AFVV (operation) J_3ABUAFVV RESB (reservation) J_3AFSRESB J_3ABDSI

AFS order completion confirmations for bundles

AFS structure of bundles in the operation

AFS: additional data for production order (RESB) AFS order (SKUs), stock type FA (production order), plan type F

Affected programs/function groups (AFS-enhanced): 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) J_4KPLKOC AFS categories

Affected programs/function groups (AFS-enhanced): 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 J_4KBOMC AFS BOMs: additional SKU data for items AFS categories for BOM items

Affected programs (AFS-enhanced): 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.
SAP AFS Pgina 83

AFS Grid Archiving: Archiving Object J_3AGRID Tables J_3APGHD J_3APGEN J_3APGTX Programs J_3AGRIA J_3AGRID J_3AGRIR Archive grids Delete grids Reload grids Grid header Grid items Grid texts for items

The above programs provide detailed documentation on the scope of functions in grid archiving and how to carry it out.

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

SAP AFS

Pgina 84

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 0011 0012 Source Plant 0001 0002 Percentage 105% 100%

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 Blue Green Red White Source Grid Value Blue Green Red Red Percentage 100% 100% 100% 100%

SAP AFS

Pgina 85

Results based on SIS Quantities and Mapping Profile SIS Grid Values Blue Green Red SIS Quantities 1000 1000 1000 Profile Blue Green Red White Qty after Profile 1000 1000 1000 1000 Result 25% 25% 25% 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


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.
SAP AFS Pgina 86

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

SAP AFS

Pgina 87

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

Version

Categories Plants

Validity Period

Version

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 application such as the purchase order, you can make manual Presizing describes how to bring a quantity from material level to relevant distribution profiles but does not prevent you from making
SAP AFS

level to SKU level in an changes to the quantity. SKU level, based on the exceptions and overriding
Pgina 88

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: 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.
SAP AFS Pgina 89

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

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.

SAP AFS

Pgina 90

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.

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.

SAP AFS

Pgina 91

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.

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.

SAP AFS

Pgina 92

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

SAP AFS

Pgina 93

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:

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.
SAP AFS Pgina 94

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. Access screen and choose AFS Central

Activities To create grids, go to the SAP Easy Functions Grids Material Grid Create Follow the steps below: 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

SAP AFS

Pgina 95

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

SAP AFS

Pgina 96

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.

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.

SAP AFS

Pgina 97

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

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.
SAP AFS Pgina 98

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:

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.
SAP AFS Pgina 99

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.

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.

SAP AFS

Pgina 100

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 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. Description Defines a user ID Enables the system to print converted dimension values. Completely deactivates dimension value conversion

User Parameters J31 J35

/AFS/No_size_conv

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

SAP AFS

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

SAP AFS

Pgina 102

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 using item-based dimension value conversion, based on the material indicator and the appropriate conversion type. 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 /AFS/No_Auto_Convtyp

Description 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 1 2 3 4 5 6 7 8

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.

SAP AFS

Pgina 103

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

SAP AFS

Pgina 104

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:

Structure J_3ADI1 J_3ADI2 J_3ADI3 J_3ADI5 /AFS/DI6 /AFS/DI7 /AFS/DI8 /AFS/DI9 /AFS/DI12 /AFS/DI13

Description Quota categories AFS SKU data (MRP, sales, dimensions) Season AFS SKU valuation data AFS WM palletization data AFS WM storage strategy AFS WM general data AFS WM storage bin stock AFS Foreign Trade AFS Retail Data

Record type A B C D G H F J E N

SAP AFS

Pgina 105