Documente Academic
Documente Profesional
Documente Cultură
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.
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.
3. 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
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:
...
Limitations
● Available-to-Promise (ATP) does not consider seasonality.
● Season, collection, and theme are not present in reservation, deliveries and warehouse
management (WM).
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.
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.
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.
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.
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.
You can find further information in the documentation BC - Changes to the SAP-Standard.
You can transfer stock from external systems in one of two ways:
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:
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.
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
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:
○ EXIT_SAPLMV03_002
You can find further information in the system enhancement MGV00001 and user exit
documentation.
● create a new IDoc segment
Error messages
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).
Customizing
Logical Message IDoc Type Output type Partner Type Process Code
Technical Information
The AFS specific segments are filled in exactly the same way as in the IDoc /AFS/DELVRY02.
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
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.
002: Indicates the SAP material number, the grid value and the
category. The customer material number and the EAN/UPC
number are entered in the parent segment E1EDL24.
E1J3AIT J_3ASTORE Store number for ticketing/labeling.
J_3ATLTYP Ticketing/labeling type
J_3ACHARC Code determining the price charged when the customer pays
for ticketing/labeling.
E1EDL19-QUALF 'QUA'
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.
Shipping units are confirmed in the same way as in the standard. The item number for
the SKU must be entered in field E1EDL44-POSNR.
EXIT_SAPLV56K_001
Customer enhancement for modifying the control record. The control record and all relevant
tables for the delivery are transferred.
EXIT_SAPLV56K_002
Customer enhancement called after each individual standard segment. This customer
enhancement is used to fill specific z-segments. The control record, the current segment name,
all the relevant delivery tables and the IDoc data records are transferred
3.2.2 Sales
Available Document Types
The following table shows an overview of the supported document types, their assigned logical
messages, and the IDoc type to be used.
Remember that this documentation always refers to the most recent version of an IDoc type,
unless specified otherwise. SAP recommends, therefore, that you use the most recent IDoc
type version.
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.
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
abrvw_bez No processing
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 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.
The processing of BOMs in multi-store orders per IDoc interface is currently not supported.
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
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.
006 Division
007 Distribution Channel
008 Sales Organization
010 Sales Group
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.
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.
Field Explanation
QUALF IDoc object identification (such as material
number, customer, and so on)
IDTNR Material identification
KTEXT Short text
MFRPN Manufacturer part number
MFRNR Manufacturer number
The segment is not used in the outbound quotation. The object identification is sent with the
segment E1J3AIM.
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.
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.
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
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.
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).
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.
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.
To send out conditions in segment E1EDP05, you must check the print indicator in the pricing
procedure for the condition type.
Segment E1J3P01
J_3ALNGR AFS Line Group indicator Line Group indicator specified several schedule
lines for one delivery
J_4KRCAT Requirement Category Indicates additional information about type of
requirement
J_4KSCAT Stock category Category assigned to a stockable item.
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.
In contrast to other purchasing documents, you cannot enter an account assignment in the
request for quotation.
EKET-MENGE
MENEE Unit of Measure EKPO-MEINS
KOMV-KWERT
AENTW Absolute Net Value of the Item EKPO-NETWR
EKET-J_3AVEMA
EKPO-IDNLF
EKPO-MATNR
EKPO-EMATN
EKET-MENGE
MENEE Unit of Measure EKPO-MEINS
KOMV-KWERT
EKET-J_3AVEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
Header texts
Terms of delivery
Delivery and packing information
Material text
Item texts
Document type Direction Logical IDoc Type Output type Process Code
Message
Purchase Order Outbound ORDCHG /AFS/ORDERS04 NEU (new) ME11
Change
014: Validity start date for outline agreement or request for EKKO-KDATB
quotation
EKKO-KDATE
015: Validity end date for outline agreement or request for
quotation
E1J3P01 POSEX Item Number EKPO-EBELP
PSTYP Item Category EKPO-PSTYP
EKET-MENGE
MENEE Unit of Measure EKPO-MEINS
EKET-J_3AVEMA or
EKPO-IDNLF
EKPO-MATNR or
EKPO-EMATN
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:
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.
Document type Direction Logical IDoc Type Output type Process Code
Message
Purchase Order Inbound ORDRSP /AFS/ORDERS04 ORDR
Confirmation
014: Validity start date for outline agreement or request for EKKO-KDATB
quotation
EKKO-KDATE
015: Validity end date for outline agreement or request for
quotation
E1J3P01 POSEX Item Number EKPO-EBELP
PSTYP Item Category EKPO-PSTYP
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.
Document type Direction Logical IDoc Type Output type Process Code
Message
Contract Outbound BLAORD /AFS/BLAORD03 J3AV /AFS/ME15
Document type Direction Logical IDoc Type Output type Process Code
Message
Contract Outbound BLAOCH /AFS/BLAORD03 J3AV /AFS/ME16
Change
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
Item
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.
Document type Direction Logical IDoc Type Output type Process Code
Message
Delivery Inbound DESADV /AFS/DELVRY02 DELS
Notification
BEZEI7 Description
BEZEI8 Description
BEZEI9 Description
BEZEI10 Description
J_3ADATUM Date
J_3AUZEIT Time
J_3AVASPQ Quantity
J_3AVASPQ Quantity
J_3AWDTH Width
ALE ID
Item
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.
J_3AVASPQ Quantity
J_3AVASPQ Quantity
You can transfer stock from external systems in one of two ways:
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.
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.
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).
create the required source text for user exit EXIT_SAPLJ4AI_003 contained in system
enhancement J_3ABOM
create a new IDoc segment
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 MAKT-MAKTX or
or material
J_3ASPRT-SPRTX
LANGU_ISO Language, ISO code MAKT-SPRAS or
J_3ASPRT-SPRAS
/AFS/E1DR_OVR SPRTP Profile Category Value determined by
generation program
WERKS Plant J_3ACAPR-WERKS or
J_3AGRPR-WERKS or
J_3APEPR-WERKS
RCATE 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 J_3APLPR-VERSB or
Requirements
J_3ACAPR-VERSB or
J_3AGRPR-VERSB or
J_3APEPR-VERSB
J_3ASPR-MGRID
J_3AVDAT Material Grid Valid from date J_3AGRPR-VDATE
Parameter:
J_3ACAPR-WERKS,
J_3ACAPR-COVST,
J_3APGHD-J_3ABZD2 or
J_3APGHD-J_3ABZD3
J_3ABEZT Description of the dimension J_3ADITY-J_3ABEZT
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.
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.
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.
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.
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:
MARA 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 Cross-
Application Components Archiving Application Data, then the relevant application area, for
example, Logistics General (LO) or Materials Management (MM).
The relevant AFS tables are listed below for the respective archiving object.
With application V2
MARA
The relevant AFS tables are then listed for the respective archiving object.
Tables
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.
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 Multi-
Profile Mapping.
When maintaining distribution of requirement versions you must also take into
account that they determine which SIS interface variant is used in mapping.
Procedure
There are two main transactions to carry out mapping:
You can use the SIS interface in distribution profile maintenance for single profile
mapping. If you access mapping from distribution profile maintenance you can only copy
the SIS data to that particular distribution profile version and context which you are
maintaining, such as distribution profile periods-00001version 00 for periods in
plant 0002.
You can use Multi-Profile Mapping for mass processing to compute all of the relevant
distribution profiles for multiple materials according to all 4 criteria at once.
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.
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.
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.
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.
The system offers the following levels for maintaining distribution profiles:
Plants
Categories
Grid values
Periods
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
After carrying out presizing and copying a quantity from material level to SKU level in an
application such as the purchase order, you can make manual changes to the quantity.
Presizing describes how to bring a quantity from material level to SKU level, based on the
relevant distribution profiles but does not prevent you from making exceptions and overriding
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):
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:
Plants
Categories
Periods
Grid values
This can be done without distribution profiles or increasing certain factors, for example,
categories, grid values or periods.
When you carry out presizing, the system searches for the relevant distribution profile based on
the plant and category for one or more materials, recalculates the quantities based on the
distribution profile, then rounds all values according to the settings. From the maintenance
transaction for the planned independent requirements, you can manually choose a rounding
strategy, distribution profile per factor and target period, for example, when running presizing in
the system. If no corresponding distribution profile version is determined for a factor, the
requirements are evenly distributed for the valid factor (for example, plant, category, period and
grid value). When running presizing in your system, you can also change the requirement
quantities by using all four factors at the same time. You can determine different distribution
profile versions for each individual factor.
You can 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.
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.
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.
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.
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.
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:
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.
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
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.
Changes in the master grid also affect all application grids that refer to the master grid
You decide to create your material with the master grid displayed in the above graphic and
include gray as well. You add the color gray to the master grid as an additional dimension value
and enter additional grid values. The system automatically updates all dependent application
grids, but does not transfer the new combinations of grid values. You can decide in which
application grids you want to permit the new grid values.
Application
Application grids allow you to coordinate and plan the purchasing and sale of materials.
You want to wait to sell your material until you have purchased sufficient stock. You do this by
assigning the material a purchasing grid whose validity corresponds to the time period that you
have planned for the purchasing. You also enter a sales grid for this material and make it valid
for the time period during which you want to sell the material.
The 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.
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.
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.
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.
If the grid history is activated you can display information on when the grid was changed, who
changed it, and what was changed.
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.
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.
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.
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.
The system uses the following logic to determine the valid conversion type:
1
2
3
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.
For example, if you use user ID 01 to process a document for customer C1, the system only
displays the conversion types to which:
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:
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.
Dimension Conversion
If you have several materials in a single sales order or purchase order, the system defines the
conversion type for each material in the document if you are usingitem-based dimension
value conversion, based on the material indicator and the appropriate conversion type.
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.
The system uses the following logic to determine the conversion type for the dimension value
conversion where a material ID is used:
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.
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.
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.
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.
● J_3ADIWM for AFS Warehouse Management (only for AFS Release V2.5x)