SAP AFS 6.

0
Release Notes
______________________________________________________________

Copyright
Copyright(c) 2006 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of SAP AG. The
information contained in this document is subject to change without notice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registered
trademarks of their respective companies.
Release Notes Table of Contents SAP AG
_____________________________________________________________

1 IS-AFS Industry-Specific Component Apparel

and Footwear 1
1.1 IS-AFS-INT AFS Interfaces 1
1.1.1 IS-AFS-INT-GTS AFS Interface to GTS 1
1.1.1.1 AFS GTS Master Data Integration (New) 1
1.1.2 IS-AFS-INT-RET AFS Interface to Retail 1
1.1.2.1 AFS Retail Integration (Changed) 1
1.2 IS-AFS-QM Quality Management 2
1.2.1 Enabling QM for Goods Receipt (GR) Process for AFS (New) 2
1.3 IS-AFS-BD Basic Data 2
1.3.1 Commodity Codes at the SKU Level (New) 2
1.3.2 Material Master Enhancements (New) 3
1.4 IS-AFS-MM Materials Management 4
1.4.1 IS-AFS-MM-IM Inventory Management 4
1.4.1.1 Seasonality Roundoff - Inventory Management (IM) - (New) 4
1.4.1.2 Stock Selection Available in Transaction MIGO (New) 5
1.4.1.3 Consumption of PIRs by TPO, MTO and PTO - (New) 5
1.4.2 IS-AFS-MM-PUR Purchasing 6
1.4.2.1 Purchasing BAPIs (Changed) 6
1.5 IS-AFS-PP Production Planning and Control 8
1.5.1 IS-AFS-PP-MAN Manufacturing 8
1.5.1.1 BAPI for Bill of Material (BOM) Maintenance (New) 8
1.5.1.2 Transaction for Grouping PO using Combined Order Number
(New) 9
1.5.1.3 BAPIs for AFS Planned Orders - Create, Change and Get
Details (Changed 9
1.5.1.4 BAPI for Production Orders - Create, Change and Get Details
(Changed) 10
1.5.2 IS-AFS-PP-PPL Production Planning 12
1.5.2.1 Consumption of PIRs by TPO, MTO and PTO - (New) 12
1.6 IS-AFS-SD Sales and Distribution 12
1.6.1 BAdI for Contract Selection (New) 12
1.6.2 BAPI for AFS Material Availability (New) 13
1.6.3 Consumption of PIRs by TPO, MTO and PTO - (New) 14
1.6.4 Display of Allocated Quantities (New) 14
1.6.5 BAdIs in Mass Document Change (MDC) (New) 15
1.6.6 Condition Table Display (Changed) 15
1.6.7 AFS Sales and Distribution (SD) IDOCS (Changed) 15
1.6.8 MDC - Supporting the Change of Single Characteristic (New) 16
1.6.9 Partial Quantity Reductions in Sales Order (New) 16
1.7 IS-AFS-ARUN Allocation Run 17
1.7.1 Seasonality Roundoff - Allocation Run (New) 17

______________________________________________________________
SAP AG iii
Release Notes Table of Contents SAP AG
______________________________________________________________

1.7.2 BAPI for Individual Allocation and/or Deallocation (New) 18

______________________________________________________________
SAP AG iv
 SAP-System
______________________________________________________________

1 IS-AFS Industry-Specific Component Apparel and

Footwear

1.1 IS-AFS-INT AFS Interfaces

1.1.1 IS-AFS-INT-GTS AFS Interface to GTS

1.1.1.1 AFS GTS Master Data Integration (New)

Use
As of SAP AFS 6.0, you can integrate the SAP Global Trade Services 7.1 (SAP GTS 7.1) master data to
the AFS data. If at least one characteristic in the stock keeping unit (SKU) of the AFS material master is
relevant for GTS (commodity codes could be assigned at the SKU level), this SKU would be transferred
as a separate product in GTS. The commodity codes can be assigned to such an SKU product transferred
to GTS. The commodity codes assigned in this way in the GTS system are then transferred back to AFS
and are assigned for the corresponding SKU. The GTS system is the leading system for the maintenance
of the commodity code.

Effects on Existing Data

AFS SKUs are transferred as separate products in GTS. Commodity codes maintained in GTS are
transferred back to AFS and mapped to the right SKU.

See also
For more information see, Commodity Codes at the SKU level.

1.1.2 IS-AFS-INT-RET AFS Interface to Retail

1.1.2.1 AFS Retail Integration (Changed)

Use
As of SAP AFS 6.0, the integration of Apparel and Footwear Solution (AFS) with Retail has been
enhanced by the following functions:
- One SAP Retail Logical system is mapped to multiple Customer in SAP AFS system, which
ensures that each Customer can be mapped to a different purchase organization. It allows multiple
prices to be maintained for each material (article in retail) at Customer level in SAP AFS, and
consequently multiple prices for each article at purchase organization level in SAP Retail.
- You can maintain the retail merchandise category in the AFS material master for each retail logical
system.

______________________________________________________________
SAP AG 1
 SAP-System
______________________________________________________________

- The variant numbers created in the retail for the article (material in AFS) have the number with the
category and grid combination. A new BAdI method is used to allow the user to change the variant
numbering as required.
- The material type of the generic article created is the same as the AFS material. A new BAdI method
is used to set the material type of the article as required.

Effects on Customizing
- To change the variant numbering as required and to set the material type of the article as required,
implement the BAdI methods in Customizing by choosing Logistics - General -> AFS Interface ->
BAdI: Transfer of Master Data to Retail.
- To maintain the Customizing for the AFS and Retail interface, choose Logistics - General -> AFS
Interface -> AFS Interface to Retail -> Interface Mapping.

1.2 IS-AFS-QM Quality Management

1.2.1 Enabling QM for Goods Receipt (GR) Process for AFS (New)

Use
As of SAP AFS 6.0, you can activate the inspection type at material level and control the inspection lot
creation at stock keeping unit (SKU) level during the goods receipt process. You must set the relevancy
for quality management (QM) for at least one characteristic of the grid or category.
Additionally, during posting of quality inspection stocks, you can directly post stock of one SKU to
unrestricted stock of another SKU.

Effects on Existing Data

Presently, inspection lots are created for all SKUs of the material once the inspection type is active for the
material. The function of posting to new material can be used as a work around to post quality inspection
stock of one SKU into unrestricted stock of another SKU.

______________________________________________________________
SAP AG 2
 SAP-System
______________________________________________________________

1.3 IS-AFS-BD Basic Data

1.3.1 Commodity Codes at the SKU Level (New)

Use
As of SAP AFS 6.0, you can maintain commodity codes at the SKU level in the material master. A new
relevancy Global Trade Services (GTS) is allotted to the characteristics attached to the grid and
categories. If this new relevancy is set then the commodity codes can be assigned at the SKU level.
You can also assign commodity codes of different countries other than the country in which the plant is
located.

Effects on Existing Data

It is possible to make the already used characteristics in grids and categories relevant for maintenance of
commodity codes at the SKU level. You can run the report for category characteristics
(J_4K_CHANGE_RELEVANCY) and grid characteristics
(/AFS/RCHNGE_RELEVANCY_GRIDCHAR) for GTS application, and based on the analysis by the
report run, you can set the relevancy.

Effects on Data Transfer

The AFS material master IDoc and BAPI have been enhanced to handle commodity codes at the SKU
level.

See also
For more information see, AFS GTS Master Data Integration.

1.3.2 Material Master Enhancements (New)

Use
As of SAP AFS 6.0, the following enhancements have been made in the material master:
- You can maintain commodity codes at the stock keeping unit (SKU) level.
- You can maintain the retail data merchandise category and characteristic profile at the material
master level. This is used to create article in retail.
- You can maintain quality management (QM) inspection type at SKU level.
- You can enable Seasons for inventory management (IM).

Effects on Data Transfer

GTS, Retail and Seasonality
- The IDoc type /AFS/MATAMS05 for message type J3AMAT must be used.
- New segment /AFS/E1MARC is available to handle SKU commodity codes.

______________________________________________________________
SAP AG 3
 SAP-System
______________________________________________________________

- New segment /AFS/E1MCAT is available to handle the retail data, that is, merchandise category and
characteristic profile for a retail logical system.
- New segment E1J3MRA is available to maintain the seasonality indicator for IM.
- The mass maintenance and direct input functionality in material master have been enhanced to
handle the commodity codes at the SKU level, retail and seasonality.
- The material master BAPIs have been enhanced with new optional parameters.
QM
- The IDoc type MATQM02 must be used.
- New segment E1BP1001004_AFSQMAT01 is available to handle inspection type at SKU level.
- The QM BAPIs have been enhanced with new optional parameters.

1.4 IS-AFS-MM Materials Management

1.4.1 IS-AFS-MM-IM Inventory Management

1.4.1.1 Seasonality Roundoff - Inventory Management (IM) - (New)

Use
As of SAP AFS 6.0, season functionality is extended to Inventory Management (IM). This enables you to
gain an overview of material movements during each season. You can maintain stocks for different
seasons separately. To enable this functionality, you have to activate the Season Active in IM indicator
for a material in the material master. This indicator can be set only for materials created in AFS 6.0. If the
season is maintained for an SKU in the material master, you can obtain season information for the SKUs
in batches, in material movement documents and in stock tables.
Also, as of AFS 6.0, you cannot set the Season Fixed indicator for new materials. However, for old
materials (materials created in AFS 5.0 with Season Fixed indicator) the behaviour remains the same.
You can run the report /AFS/R_SEASON_STOCK_FILL to change from Season Fixed indicator to
Season Active in IM. You must not set grid values as batch numbers if you want to convert Season
Fixed indicator to Season Active in IM.

Limitations
This functionality has the following limitations:
- Seasonality will not be enabled in WM.

______________________________________________________________
SAP AG 4
 SAP-System
______________________________________________________________

- Seasonality will not be enabled in reservation.

- Grid value as batch number is not possible when Season Active in IM is set.
- Season Fixed indicator cannot be set for material that is created in AFS 6.0.

1.4.1.2 Stock Selection Available in Transaction MIGO (New)

Use
As of SAP AFS 6.0, the goods movement transaction MIGO has been enhanced with Stock Selection
for AFS materials. Goods movement here implies only goods issued/transfer postings without document
reference.
This feature means considerably less effort is required from the end-user. It determines relevant stock
lines (with batch number and stocks available in the batches) and proposes it for the posting. If no suitable
stock lines are available then there is no proposal.

1.4.1.3 Consumption of PIRs by TPO, MTO and PTO - (New)

Use
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item
category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO
(purchase-to order) to consume normal planned independent requirements (PIRs). You can use this
indicator for activating and deactivating PIR consumption for TPO, MTO and PTO sales orders. Details
of PIR consumption by TPO/MTO/PTO sales order is displayed in Consumed Planned Requirements
tab of AFS stock requirements list and AFS MRP list. The reduction of PIRs happens during goods
movement (statistical goods receipt in the case of third-party orders). The consumption functionality of
normal PIRs by TPO/MTO/PTO sales orders is only available for new data created in the present release.
For upgrade customers, existing TPO/MTO/PTO sales orders cannot consume normal PIRs.

Effects on Existing Data

The Independent Requirements Reduction indicator at requirement class level no longer influences
how TPO/MTO/PTO sales orders influence the control of PIR consumption.

Effects on Customizing

______________________________________________________________
SAP AG 5
 SAP-System
______________________________________________________________

To enable TPO/MTO/PTO sales order items to consume normal PIRs, activate the indicator Consume
PIR in Customizing by choosing Sales and Distribution -> Sales -> Sales Documents -> Sales Document
Item -> Maintain Item Categories for AFS.

1.4.2 IS-AFS-MM-PUR Purchasing

1.4.2.1 Purchasing BAPIs (Changed)

Use
The following are the list of Purchasing BAPIs - Purchase Order, Purchase Requisition, Contract, and
Scheduling Agreement:
1. Purchase Order BAPI
The interface of the purchase order (PO) BAPIs mentioned below have been enhanced with optional
parameters to handle the AFS data.
- AFSPurchaseOrder.GetDetail1 (BAPI_PO_GETDETAIL1)
The following features will be supported:
- Item season information
- SKU details (grid value and category)
- Tolerances for individual schedule lines
- Status of the Delivery Completed indicator for individual schedule lines
- AFS price conditions
- Confirmations (SKU data - grid value and category)
- History (SKU data - grid value and category)
Limitation
The following features will not be supported:
- Cannot display data for AFS subcontracting components (SKU data - grid value and category)
- AFSPurchaseOrder.Change (BAPI_PO_CHANGE)
The following features will be supported:
- Item season information
- SKU details (grid value and category)
- Tolerances for individual schedule lines
- Status of the Delivery Completed indicator for individual schedule lines
- AFS price conditions

______________________________________________________________
SAP AG 6
 SAP-System
______________________________________________________________

- Confirmations (SKU data - grid value and category)

- History (SKU data - grid value and category)
Limitation
The following feature is not supported:
- Cannot change or display data for AFS subcontracting components (SKU data - grid value and
category)
- AFSPurchaseOrder.CreateFromData1 (BAPI_PO_CREATE1)
The following features will be supported:
- Item season information
- SKU details (grid value and category)
- Tolerances for individual schedule lines
- Status of the Delivery Completed indicator for individual schedule lines
- AFS price conditions
Limitation
The following feature is not supported:
- Cannot create AFS subcontracting components (with SKU data - grid value and category)

2. Purchase Requisition BAPIs

The following requisition BAPIs are supported for AFS:
- PurchaseRequisition.CreateFromData (BAPI_REQUISITION_CREATE)
You can create purchase requisition with SKU data - grid value and category.
- PurchaseRequisition.Change (BAPI_REQUISITION_CHANGE)
You can change the SKU data (grid value and category) for requisition.
- PurchaseRequisition.Delete (BAPI_REQUISITION_DELETE)
You can delete an purchase requisition with AFS data (schedule lines - grid value and category)
Limitation
The following requisition BAPIs are not supported/enhanced for AFS:
- PurchaseRequisition.Change1 (BAPI_PR_CHANGE)
- PurchaseRequisition.CreateFromData1 (BAPI_PR_CREATE)
- PurchaseRequisition.GetDetail1 (BAPI_PR_GETDETAIL)

3. Contract BAPIs
Limitation

______________________________________________________________
SAP AG 7
 SAP-System
______________________________________________________________

The following BAPIs for contracts are not supported/enhanced for AFS:
- PurchasingContract.Change (BAPI_CONTRACT_CHANGE)
- PurchasingContract.Create (BAPI_CONTRACT_CREATE)
- PurchasingContract.GetDetail (BAPI_CONTRACT_GETDETAIL)

4. Scheduling Agreement BAPIs

Limitation
The following BAPIs for scheduling agreements are not supported/enhanced for AFS:
- PurchSchedAgreement.Change (BAPI_SAG_CHANGE)
- PurchSchedAgreement.Create (BAPI_SAG_CREATE)
- PurchSchedAgreement.GetDetail (BAPI_SAG_GETDETAIL)
- PurchSchedAgreement.Maintain (BAPI_SCHEDULE_MAINTAIN)

Effects on Existing Data

The above mentioned BAPIs work with data created in lower releases like AFS 3.0B, AFS 5.0.

1.5 IS-AFS-PP Production Planning and Control

1.5.1 IS-AFS-PP-MAN Manufacturing

1.5.1.1 BAPI for Bill of Material (BOM) Maintenance (New)

Use
As of SAP AFS 6.0, you use this BAPI (AFSMaterialBOM.AFSMatBomMaintain) to maintain a
material BOM. You can also use this BAPI for the following functionalities:
- Creating a standard or AFS BOM
- Changing a standard or AFS BOM
- Updating a quantity distribution profile for AFS BOM components
- Maintaining SKU deviation quantities or zero quantities (if relevant) for AFS BOM components
- Maintaining categories (if relevant) for AFS BOM components

______________________________________________________________
SAP AG 8
 SAP-System
______________________________________________________________

Effects on Existing Data

The above mentioned BAPI is compliant with data created in AFS 3.0B and AFS 5.0 releases.

Effects on Data Transfer

To enable the AFS functionalities with this BAPI, you must transfer data to the appropriate AFS
parameters of the BAPI, in addition to the standard parameters as required. For a standard material BOM,
the AFS parameters are ineffective and are ignored.

1.5.1.2 Transaction for Grouping PO using Combined Order Number (New)

Use
As of SAP AFS 6.0, you can use transaction /AFS/CORD to assign a combined order number to a set of
production orders (PO) for further processing as a collection. You can select the production orders to be
grouped based on various criteria available on the initial screen. Furthermore, you can group the orders
with or without performing batch assignment for the order components.

Effects on Existing Data

Until SAP AFS 6.0, there were two separate transactions to perform the above tasks with minor
variations. The new transaction replaces both of them and provides a better and more intuitive interface.

Effects on Customizing
To set the internal and external number ranges before grouping the production orders, in Customizing
choose Production -> Shop Floor Control -> Master Data -> Order-> Define Number Range for
Combined Orders (AFS).

1.5.1.3 BAPIs for AFS Planned Orders - Create, Change and Get Details
(Changed

Use
As of SAP AFS 6.0, the interface of the following planned order BAPIs have been enhanced with
additional parameters to enable AFS functionalities:
- PlannedOrder.Create (BAPI_PLANNEDORDER_CREATE)
You can create planned orders with SKU, bundle and season information.
- PlannedOrder.Change (BAPI_PLANNEDORDER_CHANGE)

______________________________________________________________
SAP AG 9
 SAP-System
______________________________________________________________

The system supports the following changes to AFS planned orders:

- SKU data (grid values and categories)
- Marker information
- Season information
- PlannedOrder.GetDetail (BAPI_PLANNEDORDER_GET_DETAIL)
In addition to the standard details of the planned orders, the BAPI returns the following AFS details:
- SKU data (grid values and category)
- Marker information
- Season information
- Component SKU details

Effects on Existing Data

The above mentioned BAPI methods can be used with data created in AFS 3.0B and AFS 5.0 releases.

Effects on Data Transfer

To enable the AFS functionalities with these BAPIs, you must transfer data to the appropriate AFS
parameters of the BAPIs, in addition to the standard parameters.

1.5.1.4 BAPI for Production Orders - Create, Change and Get Details (Changed)

Use
As of SAP AFS 6.0, the following production order BAPI methods have been enhanced with optional
parameters to handle AFS functionalities:
- ProductionOrder.Create1 (BAPI_PRODORD_CREATE)
You can create the AFS production orders with the following information:
- SKU, bundle and season information
- Reference to sales order
- User-defined combined order number
- ProductionOrder.Change (BAPI_PRODORD_CHANGE)
You can change the following information in an AFS production order:
- SKU (grid values/category)
- Bundle and marker information

______________________________________________________________
SAP AG 10
 SAP-System
______________________________________________________________

- Season information
- Tolerances for individual SKUs
- Delivery Completed Indicator (DCI) for individual SKUs
- ProductionOrder.GetDetail (BAPI_PRODORD_GET_DETAIL)
You can retrieve the following details for AFS production orders, in addition to the standard information:
- SKU (Grid values/ Category) information
- Bundle and marker information
- Season information
- Tolerances for individual SKUs
- Status of the Delivery Completed Indicator (DCI) for individual SKUs
- SKU details for the components
- Batch assignment details for the components
Additionally, you can retrieve all the above details for a set of production orders which have a common
combined order number.
- ProductionOrder.CreateFromPlord (BAPI_PRODORD_CREATE_FROM_PLORD)
- Production order can be created from a planned order for an AFS material

As of SAP AFS 6.0, the following production order BAPI methods are supported for AFS orders:
- ProductionOrder.Close (BAPI_PRODORD_CLOSE)
- Production order status is set to Closed (CLSD)
- ProductionOrder.CompleteTechnically (BAPI_PRODORD_COMPLETE_TECH)
- Production order status is set to Complete Technically (TECO)
- ProductionOrder.Release (BAPI_PRODORD_RELEASE)
- Production order status is set to Released (REL)
- ProductionOrder.SetDeletionFlag (BAPI_PRODORD_SET_DELETION_FLAG)
- Production order status: Deletion Flag (DLFL) is set
Limitation
This BAPI method (ProductionOrder.SetDeletionFlag) does not support deletion of batch assignments
for the production orders, and related updation of reserved quantities in stock tables. Thus, it is not
recommended to use this BAPI to set deletion flag for AFS production orders which has batch fixed
assignments.
- ProductionOrder.SetDeletionIndicator (BAPI_PRODORD_SET_DEL_INDICATOR)
- Production order status: Deletion Indicator (DLT) is set
- ProductionOrder.Schedule (BAPI_PRODORD_SCHEDULE)

______________________________________________________________
SAP AG 11
 SAP-System
______________________________________________________________

- Production order is Scheduled (DSPT)

Effects on Existing Data

The above mentioned BAPI methods can work with data created in previous releases like AFS 3.0B and
AFS 5.0.

1.5.2 IS-AFS-PP-PPL Production Planning

1.5.2.1 Consumption of PIRs by TPO, MTO and PTO - (New)

Use
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item
category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO
(purchase-to order) to consume normal planned independent requirements (PIRs). You can use this
indicator for activating and deactivating PIR consumption for TPO, MTO and PTO sales orders. Details
of PIR consumption by TPO/MTO/PTO sales order is displayed in Consumed Planned Requirements
tab of AFS stock requirements list and AFS MRP list. The reduction of PIRs happens during goods
movement (statistical goods receipt in the case of third-party orders). The consumption functionality of
normal PIRs by TPO/MTO/PTO sales orders is only available for new data created in the present release.
For upgrade customers, existing TPO/MTO/PTO sales orders cannot consume normal PIRs.

Effects on Existing Data

The Independent Requirements Reduction indicator at requirement class level no longer influences
how TPO/MTO/PTO sales orders influence the control of PIR consumption.

Effects on Customizing
To enable TPO/MTO/PTO sales order items to consume normal PIRs, activate the indicator Consume
PIR in Customizing by choosing Sales and Distribution -> Sales -> Sales Documents -> Sales Document
Item -> Maintain Item Categories for AFS.

1.6 IS-AFS-SD Sales and Distribution

1.6.1 BAdI for Contract Selection (New)

______________________________________________________________
SAP AG 12
 SAP-System
______________________________________________________________

Use
As of SAP AFS 6.0, you can use this BAdI to filter contracts for display when a sales order is created
without giving reference to the contract, and when there are open contracts for the material.
This functionality is also available for the sales order created by IDocs.

Example
By implementing this BAdI you can cross check call-off's requested delivery date with that of the
contract's requested delivery date, and can also restrict some of the contracts from display.

1.6.2 BAPI for AFS Material Availability (New)

Use
As of SAP AFS 6.0, you can use this BAPI method MaterialAFS.AFSAvailabilityCheck
(/AFS/BAPI_MAT_AVAILABILITY) to determine the available quantity for an AFS material in a certain
plant according to ATP (available-to-promise) logic. The result is same as ATP simulation in case the
caller_application is V (sales).
You can carry out availability check for the AFS material, plant and unit-of-measure (for display). The
scope of the check, that is, which stocks, receipts and issues are to be included in the check is defined by
the combination of checking group (material master) and checking rule. In the function module, the
system uses the default checking rule defined in sales & distribution (A).
The results of the availability check are recorded in the output table. This table contains dates and
available receipt quantities (ATP quantities) along with SKU information.
The results of the check depend on the following entries:
- If no date is transferred, the system displays the ATP situation from today's date into the future date
as the result.
- If a date is transferred, the system displays the ATP situation from the corresponding date as the
result.
The system also displays the end of the replenishment lead time (ENDLEADTME) if the check with
replenishment lead time is switched ON.

______________________________________________________________
SAP AG 13
 SAP-System
______________________________________________________________

1.6.3 Consumption of PIRs by TPO, MTO and PTO - (New)

Use
As of SAP AFS 6.0, the Consume PIR Customizing indicator at sales and distribution (SD) item
category level enables special orders like TPO (third-party order), MTO (make-to order) and PTO
(purchase-to order) to consume normal planned independent requirements (PIRs). You can use this
indicator for activating and deactivating PIR consumption for TPO, MTO and PTO sales orders. Details
of PIR consumption by TPO/MTO/PTO sales order is displayed in Consumed Planned Requirements
tab of AFS stock requirements list and AFS MRP list. The reduction of PIRs happens during goods
movement (statistical goods receipt in the case of third-party orders). The consumption functionality of
normal PIRs by TPO/MTO/PTO sales orders is only available for new data created in the present release.
For upgrade customers, existing TPO/MTO/PTO sales orders cannot consume normal PIRs.

Effects on Existing Data

The Independent Requirements Reduction indicator at requirement class level no longer influences
how TPO/MTO/PTO sales orders influence the control of PIR consumption.

Effects on Customizing
To enable TPO/MTO/PTO sales order items to consume normal PIRs, activate the indicator Consume
PIR in Customizing by choosing Sales and Distribution -> Sales -> Sales Documents -> Sales Document
Item -> Maintain Item Categories for AFS.

1.6.4 Display of Allocated Quantities (New)

Use
As of SAP AFS 6.0, you can find the allocated quantity information of the contract in the Contract
Reference Overview screen. You can allocate these contract requirements against the batch stock or
against the future receipts. Thus both the above types of allocated quantity information are displayed
separately.

Effects on Existing Data

This functionality is possible in the existing allocated contracts.

______________________________________________________________
SAP AG 14
 SAP-System
______________________________________________________________

1.6.5 BAdIs in Mass Document Change (MDC) (New)

Use
As of SAP AFS 6.0, the following Business Add-Ins (BAdIs) are provided:
- BAdI for adding custom selection fields in MDC (/AFS/MDC_SELECT_CUSTOM_FIELDS) -
You use this BAdI to implement your business process-specific logic in selecting data in Mass
Document Change transaction (/AFS/MDC).
- BAdI for adding custom change fields in MDC (/AFS/MDC_CHANGE_CUSTOM_FIELDS) -
You use this BAdI for implementing your business process-specific logic in changing custom fields
data in transaction /AFS/MDC.
- BAdI for adding custom fields to the Adjust Update tab in MDC
(/AFS/MDC_ADJ_UPD_CUSTOM_FIELDS) - You use this BAdI to implement custom processes
that are specific to your business scenario.

1.6.6 Condition Table Display (Changed)

Use
As of SAP AFS 6.0, in transaction J3A9 it is possible to display condition tables for value-added service
(VAS) and multi-store order (MSO) condition types beyond the existing limit of 19 condition tables. The
Conditions Info display in transactions J3A4 and J3AN can be viewed in an ALV list.

______________________________________________________________
SAP AG 15
 SAP-System
______________________________________________________________

1.6.7 AFS Sales and Distribution (SD) IDOCS (Changed)

Use
As of SAP AFS 6.0, the function modules J_4A_IDOC_INPUT_ORDERS and
J_4A_IDOC_INPUT_ORDCHG are not supported. The standard function module
IDOC_INPUT_ORDERS are used instead J_4A_IDOC_INPUT_ORDERS and standard function module
IDOC_INPUT_ORDCHG are used instead of J_4A_IDOC_INPUT_ORDCHG. There is no change in the
IDOC type /AFS/ORDERS05 which is presently used to create/change sales orders.
Accordingly, you must use inbound process code ORDE for message type ORDERS and inbound process
code ORDC for message type ORDCHG.

1.6.8 MDC - Supporting the Change of Single Characteristic (New)

Use
As of SAP AFS 6.0, you can use transaction /AFS/MDC, to select sales documents by specifying a single
characteristic name and value range in the same ways as you select sales documents by specifying grid
value. You can use the transaction to change the single characteristic value of the schedule line across
different sales documents. After the mass document change (MDC) using single charecterestics change is
performed, the user can see the status in the change and the error logs as before.

1.6.9 Partial Quantity Reductions in Sales Order (New)

Use
As of SAP AFS 6.0, you can find the quantity changes done for a schedule line from the sales order screen
itself without navigating to the change logs. This is possible only when you reduce the quantity of a
schedule line.

______________________________________________________________
SAP AG 16
 SAP-System
______________________________________________________________

This functionality is available only in the change mode of the sales order in the complete structure.

Effects on Customizing
To maintain the entered rejection code for the quantity reduction mode, in Customizing choose Sales and
Distribution -> Sales -> Sales Documents -> Schedule Lines -> Maintain Rejection Code for AFS.

1.7 IS-AFS-ARUN Allocation Run

1.7.1 Seasonality Roundoff - Allocation Run (New)

Use
As of SAP AFS 6.0, season functionality is available in the allocation run (ARun) to ensure the season
information is considered while creating assignments, and to cause deallocation as per the settings in the
deallocation rule on change in season information in the future receipts, sales order or while performing
goods receipt (GR). This functionality is available only with online ARun.

Effects on Existing Data

This functionality is possible for existing sales orders, purchase orders and production orders, if:
- Season information is maintained
- Allocation has not yet happened
- Changes are made to existing allocations

Effects on Customizing
The following Customizing settings need to be performed:
1. Allocation
To activate the Season Check for the allocation rule attached to the allocation type, in Customizing choose
AFS Allocation Run -> ARun Detail -> Define Allocation Logic -> Allocation Rule.
Note: If the season check is not activated in Customizing for the allocation rule, and there are two batches
of stock - one with the same season as in requirement and the other with a season different from that in
the requirement, then both have the same priority and are sorted as per the stock sort rule maintained in
ARun Customizing.
2. Deallocation
The respective deallocation rules should be maintained to handle the change in season information in the
future receipts, sales order, and while performing goods receipt.
- Purchase Order Handling
- In Customizing, choose Deallocation Rule

______________________________________________________________
SAP AG 17
 SAP-System
______________________________________________________________

- In Customizing, choose Assign PO Rules to Plant

- Production Order Handling
- In Customizing, choose Deallocation Rule
- In Customizing, choose Assign PP Rules to Plant
- Goods Receipt Handling
- In Customizing, choose Deallocation Rule
- In Customizing, choose Assign GR Rules to Plant
- Sales Order Handling
- In Customizing, choose Deallocation Rule
- In Customizing, choose Assign Rule to Order Type

Limitation
Seasonality with ARun Optimizer
If a new allocation is being made with the ARun Optimizer (season check is maintained in the allocation
rule attached to the ARun type which in turn is attached to optimizer type), the optimizer takes care of the
field check for the season.
However, for partial and completely allocated sales orders field check for season does not happen.

1.7.2 BAPI for Individual Allocation and/or Deallocation (New)

Use
As of SAP AFS 6.0, you can use the BAPI /AFS/BAPI_INDIVIDUAL_ARUN to handle
allocation/deallocation of specified sales order quantities for single or multiple orders. This enables you to
make:
- new allocations
- allocations from a particular storage location/batch number
- allocations for a quantity less than equal to the requirement quantity
- deallocations for a quantity less than equal to the requirement quantity
- a total deallocation

Limitations
Grouping and spread logic is not implemented.

______________________________________________________________
SAP AG 18
 SAP-System
______________________________________________________________

______________________________________________________________
SAP AG 19