afs release notes

SAP Apparel and Footwear Release Notes

Release 5 .00

SAP AG 10.12.2004

SAP AFS 5.0 Release Notes 2

Copyright © Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP AG 10.12.2004


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

SAP AG 10.12.2004


1 IS-AFS Industry-Specific Component Apparel and Footwear ...........................................7 1.1 AFS Interface to APO (New).............................................................................................7 1.2 IS-AFS-BD Basic Data......................................................................................................9

1.2.1 BAdI for Enhanced Checks of Material Master Data (New).......................................9 1.2.2 Conversion of Grid Dimensions and Category Structure Fields to Characteristics (New) ...................................................................................................................................9 1.2.3 BW Update Methods for AFS (New) ..........................................................................9 1.2.4 Categories and Master Data: ZX Includes (Deleted) ...............................................10

1.3 IS-AFS-MM Materials Management................................................................................11 1.3.1 IS-AFS-MM-IM Inventory Management ...................................................................11

1.3.1.1 Automatic Deallocation at Goods Issue (New) ..................................................11 1.3.1.2 AFS Enhancements for Goods Movements (New) ...........................................11

1.3.2 IS-AFS-MM-IV Invoice Verification...........................................................................11 1.3.2.1 AFS Compliant BAPIs for Incoming Invoices (New)..........................................11 1.3.2.2 Balance Clearing on the Schedule Line Level for AFS Materials (New) ...........12

1.3.3 IS-AFS-MM-PUR Purchasing...................................................................................12 1.3.3.1 AFS Compliant BAPIs for Purchase Orders (New) ...........................................12 1.3.3.2 Batch Number Monitoring for AFS Subcontracting Stock (New).......................12 1.3.3.3 AFS Missing Parts List for Purchase Orders (New) ..........................................12 1.3.3.4 Purchase Order Splitting (New).........................................................................13 1.3.3.5 Report for Purchase Order Confirmations (New) ..............................................13 1.3.3.6 Season (Enhanced) ...........................................................................................13

1.4 IS-AFS-LE Logistics Execution .......................................................................................14 1.4.1 IS-AFS-LE-SHP Shipping.........................................................................................14

1.4.1.1 Reverse Goods Movements for Outbound Delivery (New) ...............................14 1.5 IS-AFS-PP Production Planning and Control .................................................................15

1.5.1 IS-AFS-PP-MAN Manufacturing...............................................................................15 1.5.1.1 Outbound IDocs for AFS Bills of Material (New) ...............................................15 1.5.1.2 Season (Enhanced) ...........................................................................................15

1.5.2 IS-AFS-PP-PPL Production Planning ......................................................................16 1.5.2.1 Replacements for Transactions J3AD, J4AD, and J4A]....................................16 1.5.2.2 Table J_3ABDBS Is Only Used For ARun (Changed) ......................................16 1.5.2.3 New User Interface for MD04/MD05 (New).......................................................16 1.5.2.4 Stock Coverage Is Now Available in /AFS/MD04 and /AFS/MD06 (New) ........16 1.5.2.5 Third Party Orders No Longer Displayed in /AFS/MD04 (Deleted) ...................16 1.5.2.6 BAdI for AFS Stock/Requirement List (New).....................................................17 1.5.2.7 User Favorites/Navigation Profile Supported in MD04/MD05 and /AFS/MD04 (Changed) ......................................................................................................................17 1.5.2.8 Exclusion of Requirement Classes from MRP and/or StockRequirements Li (New) .............................................................................................................................17

SAP AG 10.12.2004


1.5.2.9 Advanced Size Optimization (New) ...................................................................17 1.6 IS-AFS-SD Sales and Distribution ..................................................................................19

1.6.1 Deallocation for Sales Orders (Enhanced)...............................................................19 1.6.2 ATP Substitution (New) ............................................................................................19 1.6.3 Contract Call Off Handling (New).............................................................................19 1.6.4 AFS Master Data for Categories and Dimensions (Changed) .................................20 1.6.5 Check Report Renamed to /AFS/SDVBUK00 (Changed)........................................21 1.6.6 Deallocation Now Controlled by Deallocation Rule (Changed)................................21 1.6.7 Mass Document Change (New Line Items) (Changed) ...........................................22 1.6.8 Purchase Order Type for Third Party Orders (Deleted) ...........................................22 1.6.9 Fixed Category Allocation by ATP (Deleted)............................................................22 1.6.10 AFS Online Store (Deleted)....................................................................................22 1.6.11 Rejection Codes for AFS Schedule Lines (Changed)............................................22 1.6.12 Parallel Processing for Rescheduling ....................................................................22 1.6.13 Entering Same SKU Multiple Times in an MTO/PTO (New)..................................23 1.6.14 Season (Enhanced)................................................................................................23 1.6.15 Domain ZAEHK Changed Back to Two Digits (Changed) .....................................23

1.7 IS-AFS-ARUN Allocation Run.........................................................................................24 1.7.1 Access Rule (Changed) ...........................................................................................24 1.7.2 Adjust Allocation Quantities in the ARun Optimizer (New) ......................................24 1.7.3 Control of Allocation Quantities in the ARun Optimizer (New).................................24 1.7.4 Customer Sales Areas (New)...................................................................................24 1.7.5 Deallocation of Partial Quantities in the ARun Optimizer (New) ..............................25 1.7.6 Deallocation During Goods Issue Posting (New) .....................................................25 1.7.7 Allocation Against Future Receipts/Deallocation for Goods Receipts (New)...........25 1.7.8 Allocation Against Future Receipts/Deallocation for Purchase Orders (New) .........26 1.7.9 Allocation Against Goods Receipts/Deallocation for Production Orders (New).......26 1.7.10 Allocation Against Future Receipts (New)..............................................................27 1.7.11 ARun IMG Structure (Changed) .............................................................................27 1.7.12 Keep MRP Status (New) ........................................................................................29 1.7.13 Level Configuration in the ARun Optimizer (New) .................................................29 1.7.14 Log File (Changed).................................................................................................29 1.7.15 Allocation Logic (Changed) ....................................................................................29 1.7.16 Maximum Number of Values to Process in ARun Optimizer (New).......................30 1.7.17 Status Determination in the ARun Optimizer (New)...............................................30 1.7.18 ARun Optimizer (New) ...........................................................................................30 1.7.19 Parallel ARun (Enhanced)......................................................................................32 1.7.20 Permanent Grouping (Allocation Groups) (New) ...................................................33 1.7.21 Reallocation in the ARun Optimizer (New).............................................................33 1.7.22 Rejecting Schedule Lines in the ARun Optimizer (New)........................................33

SAP AG 10.12.2004


1.7.23 Rejection of Open Quantities (New).......................................................................34 1.7.24 Release Check in the ARun Optimizer (New) ........................................................34 1.7.25 Release/Block of Flagged Schedule LinesUse ......................................................34 1.7.26 Assigning Rules to Order Types (Enhanced).........................................................34 1.7.27 Branch from ARun Optimizer to Sales Order Maintenance (New) ........................35 1.7.28 Flagging Schedule Lines for Special Handling (New)............................................35 1.7.29 Stock Overview in the ARun Optimizer (New) .......................................................35 1.7.30 Stock Selection Rule (Changed) ............................................................................35 1.7.31 ARun Substitution...................................................................................................36 1.7.32 Deallocation Now Controlled by Deallocation Rule (Changed)..............................36

SAP AG 10.12.2004


1 IS-AFS Industry-Specific Component Apparel and Footwear

1.1 AFS Interface to APO (New) Use

As of SAP AFS 5.0, you can transfer demand planning data from APO to SAP R/3 at the category level as well as the dimension level for AFS materials.

The following describes the behavior of demand planning data transfer from APO to R/3 at category level:

• Case 1: Completely specified categories

Data transfer to R/3 at the category level is mapped to the exact corresponding category combinations maintained in both R/3 and APO.

Example: Assume that the category structure has three category structure fields: quality, season, and country. These have been maintained in both R/3 and APO. Also, 01JANDE is a valid category value on both sides. In this case, if planning data exists in APO for category value 01JANDE, it will be transferred to R/3 for the same category value 01JANDE.

• Case 2: Incompletely specified categories

Transfer to R/3 is done where the category value of the non-specified category field in APO is taken from the default value maintained in the Customizing table J_4KCATDYN with IR as the application. See Customizing below.

Example: Assume that the category field Country in the category structure from the above example is not specified in APO, and that the default value in the R/3 table J_4KCATDYN for category field Country has value IN. In this case, planning data for category value 01JAN in APO is transferred to R/3 with category value 01JANIN.

• Case 3: Transfer at material level

Planning data is distributed across category values according to the category distribution profile maintained in R/3.

Effects on Existing Data

There is no effect on existing data.

Effects on Data Transfer

Data transfer between an earlier APO to R/3 will not be affected, but it works with the new features as mentioned above. Effects on System Administration None

Effects on Customizing

• AFS Customizing for categories

Assign one characteristic belonging to characteristic group 'AFS characteristic for categories' to each category field. You define these characteristics via SAP menu path Cross-Application Components -> Classification system -> Master Data -> Characteristics (transaction: CT04).

• AFS Customizing for the APO Interface

Define the assignment table of the AFS characteristics for the APO characteristics (InfoObjects). You must specify the logical system and system type. To do this, select the IMG node Define AFS Interface. Then select the characteristics and assign the

SAP AG 10.12.2004


InfoObjects. You must do this for the complete set of characteristics (that is, for both dimensions and categories).

• Dynamic filling of category fields

Incompletely specified categories are accepted, provided these can be replaced by standard values in Customizing table J_4KCATDYN with application IR. You do this in IMG node Define Category Structure and Relevance. Select the category structure, then the category fields, then Dynamic filling of category fields.

SAP AG 10.12.2004


1.2 IS-AFS-BD Basic Data

1.2.1 BAdI for Enhanced Checks of Material Master Data (New) Use

As of SAP AFS 5.0, the new BAdI /AFS/BADI_MAT_CHECK can be used for enhanced checks of AFS-specific Material Master tables at the SKU level.

1.2.2 Conversion of Grid Dimensions and Category Structure Fields to Characteristics (New) Use

As of SAP AFS 5.0, basic data for grids and category structures has undergone changes. Grid dimensions have been replaced by characteristics, and category structures can only be created from characteristics. Use transaction CT04 to create characteristics for grids and category structures.

To accommodate the shift of grid dimensions to characteristics, a new grid IDoc type J3AGRI02 has been created.


Existing grid dimensions and category structure fields are converted into characteristics during upgrade.


IDoc processing for grids has changed. You must use the new grid IDoc type J3AGRI02, with the following exception: you can still use the old IDoc type J3AGRI01 for inbound processing of characteristics with names less than 8 characters long.

For outbound processing, only J3AGRI02 is used.

Effects on System Administration

None


The Customizing dialog for dimensions is no longer available. You can no longer create user-defined category fields.

1.2.3 BW Update Methods for AFS (New) Use

As of SAP AFS 5.0, three new update methods provided in the standard system are supported by AFS. Do not use the old V3 serialized update method any more.

The new update methods are:

• Queued delta

• Direct delta

• V3 unserialized

For more details on these update methods, see SAP Note 505700.

SAP AG 10.12.2004


The update methods for application AF are controlled via the LO Data Extraction Customizing Cockpit (TA LBWE).


None


This depends on the update method used. See SAP Note 505700 for more details


None

1.2.4 Categories and Master Data: ZX Includes (Deleted) Use

As of SAP AFS 5.0, some user exits that could be implemented using ZX Includes have been replaced by BAdIs. Coding from the ZX Includes must be moved to these BAdIs.

See OSS Note 750904 for details.

SAP AG 10.12.2004


1.3 IS-AFS-MM Materials Management

1.3.1 IS-AFS-MM-IM Inventory Management 1.3.1.1 Automatic Deallocation at Goods Issue (New) Use

As of SAP AFS 5.0, you can have the system automatically deallocate stock during goods issue. This allows goods issues even though the stock is allocated (for example, in case of difference postings from physical inventory or material document reversals).

Previously deallocation could only be done manually (with the ARun Management Tool) before the goods issue could be posted.


You must activate automatic deallocation at the movement type level. To do this, make the following settings in ARun Customizing:

• Assign a deallocation rule to the plant (AFS Allocation Run -> Cross Applications -> GI Handling -> Assign GI Rule to Plant).

• Activate the deallocation for the goods issue movement types (AFS Allocation Run -> Cross Applications -> GI Handling -> Assign GI Rule to Plant).

1.3.1.2 AFS Enhancements for Goods Movements (New) Use

As of SAP AFS 5.0, all of the functions in the standard goods movement transaction (MIGO) are available for AFS materials.

In addition, the transaction has been enhanced to provide the following new features, which are also supported in the old MB* transactions:

• Transfer postings and stock transfers at the SKU level

• Transfer posting of allocated stock from storage location to storage location

• Subsequent adjustment in subcontracting at the SKU level

This means that MIGO can replace all conventional transactions for posting goods movements that start with MB*. You can use both MIGO and the conventional MB* transactions at the same time without restriction.

1.3.2 IS-AFS-MM-IV Invoice Verification 1.3.2.1 AFS Compliant BAPIs for Incoming Invoices (New) Use

As of SAP AFS 5.0, the following BAPIs are fully AFS compliant:

• BAPI_INCOMINGINVOICE_CREATE

• BAPI_INCOMINGINVOICE_PARK

• BAPI_INCOMINGINVOICE_GETDETAIL

Invoices can be created with SKU data.

SAP AG 10.12.2004


1.3.2.2 Balance Clearing on the Schedule Line Level for AFS Materials (New) Use

As of SAP AFS 5.0, the standard transaction MR11 (GR/IR Balance Clearing) has been enhanced to support posting of balances on the schedule line (SKU) level for purchase order items containing AFS materials. Thus:

• For logistics invoices that were posted on the item level, MR11 proposes balance clearing on the item level

• For logistics invoices that were posted on the SKU level, MR11 proposes balance clearing on the SKU level


None

1.3.3 IS-AFS-MM-PUR Purchasing 1.3.3.1 AFS Compliant BAPIs for Purchase Orders (New) Use

As of SAP AFS 5.0, BAPI_PO_CHANGE and BAPI_PO_CREATE1 are AFS compliant. This allows you to create or change AFS purchase order items.

You can use the AFS PO Split Transaction as a template for proper call of these BAPIs

See also

Purchase Order Splitting 1.3.3.2 Batch Number Monitoring for AFS Subcontracting Stock (New) Use

AS of SAP AFS 5.0, the standard ME2O transaction for monitoring subcontracting stock also supports batch number grouping for AFS materials.

On the initial screen of the stock requirements report, you can choose whether to display the report with or without batch grouping.

• With batch grouping

The report groups the requirements by batch number, and that number is reflected at the material, plant and vendor list level. The report allows you make a transfer posting directly into the stock of material provided to the vendor.

• Without batch grouping

Although the batch information is not automatically displayed, there are icons that you choose in order to view the batches assigned to the material/plant/vendor. When you create a delivery, the system does not use stock from a specific batch. Instead it fetches the first batch it finds that suits the requirements.

1.3.3.3 AFS Missing Parts List for Purchase Orders (New) Use

As of SAP AFS 5.0, you can generate a list of purchase orders that have missing parts. The transaction is /AFS/MM_MP.

SAP AG 10.12.2004


In the selection screen, you can choose vendor, component, header data, material, and requirement date parameters. The system then displays a list of purchase orders that have subcontracting items. Partially confirmed quantities are highlighted in yellow.

You can expand the list to see the components and purchase order items involved. If you entered a component on the original selection screen, then only that component will be shown. You can further expand the list to show the delivery schedules. Only those schedules with a committed quantity less than the requirement quantity are displayed. If the component item is partially committed, it is highlighted in yellow. If the component item is not committed, it is highlighted in red

At the item level in the list, you can choose to display the requirement quantity, requirement date, quantity promised, missing part indicator, and base unit of measure.

The design of the list is similar to that for displaying ATP information in a purchase order

1.3.3.4 Purchase Order Splitting (New) Use

As of SAP AFS 5.0, there is a transaction (/AFS/SPLITPO) for splitting purchase orders. It can be easily enhanced using BAdI methods.

This transaction allows you to:

• Implement your own authority checks without modification

• Split purchase orders based on header data (for example, vendor or purchasing organization)

• Split purchase orders based on item level data (for example, plant or item category)

• Change additional customer fields on the item/schedule line level

You can also use the transaction as a template for your own custom program. It shows the proper call of AFS compliant BAPIs BAPI_PO_CHANGE and BAPI_PO_CREATE1. 1.3.3.5 Report for Purchase Order Confirmations (New) Use

As of SAP AFS 5.0, there is a new report for purchase order confirmations. It gives confirmation details at the SKU level for AFS materials.

You can access the report using transaction /AFS/ME2A. 1.3.3.6 Season (Enhanced) Use

As of SAP AFS 5.0, seasonality is no longer restricted to sales documents, but also supports documents in Purchasing and Production. You can define a common season hierarchy for all applications in Customizing. Time intervals are maintained separately for requirement/stock elements.

You activate season determination:

• At the document header level for sales documents

• In the Material Master (AFS Basic data) for stock elements

SAP AG 10.12.2004


1.4 IS-AFS-LE Logistics Execution

1.4.1 IS-AFS-LE-SHP Shipping 1.4.1.1 Reverse Goods Movements for Outbound Delivery (New) Use

In previous AFS releases, transaction VL09 (reverse goods movement) was only available for outbound delivery.

As of SAP AFS 5.0, the transaction is now fully supported for all AFS materials in both inbound and outbound deliveries.


None

SAP AG 10.12.2004


1.5 IS-AFS-PP Production Planning and Control

1.5.1 IS-AFS-PP-MAN Manufacturing 1.5.1.1 Outbound IDocs for AFS Bills of Material (New) Use

As of SAP AFS 5.0, the standard transaction BD30 has been enhanced to send an AFS bill of material (BOM) to external systems.

The following AFS segments will now be written to an IDoc if the header material is an AFS material and the SKU data and category information has been maintained:

• /AFS/E1STPOM (AFS Additional Data for BOM Item)

• E1J3ABG (Additional size grid data for items) and

• E1J3ABC (Categories for BOM items) Effects on Existing Data

None


The outbound AFS BOM IDoc created by BD30 cannot be used as an inbound IDoc in other SAP R/3 systems to create the AFS BOM. The processing of this IDOC will result in errors and the AFS BOM will not be created.

For example, suppose that System A creates an AFS BOM IDoc. If you attempt to process this in System B to create the AFS BOM, it will result in errors and the IDOC will not be processed.

The outbound IDOC created for an AFS BOM can only be used for information and/or processing in non-SAP-R/3 systems.


None


None

1.5.1.2 Season (Enhanced) Use

As of SAP AFS 5.0, seasonality is no longer restricted to sales documents, but also supports documents in Purchasing and Production. You can define a common season hierarchy for all applications in Customizing. Time intervals are maintained separately for requirement/stock elements.

You activate season determination:

• At the document header level for sales documents

• In the Material Master (AFS Basic data) for stock elements

SAP AG 10.12.2004


1.5.2 IS-AFS-PP-PPL Production Planning 1.5.2.1 Replacements for Transactions J3AD, J4AD, and J4A] Use

As of SAP AFS 5.0, the following transactions are replaced with new improved transactions: -J3AD is replaced by /AFS/MD02 -J4AD is replaced by /AFS/MD04 -J4A] is replaced by /AFS/MD06 1.5.2.2 Table J_3ABDBS Is Only Used For ARun (Changed) Use

As of SAP AFS 5.0, table J_3ABDBS is only used for ARun. In previous releases, J_3ABDBS and J_3ABDBSD were used to store protocol data from the last MRP run as well as ARun.

For current data, use function modules J_3AM_DISPOSITION_DISPL and J_3AM_GET_ALLOCATION_DISPO.

For historical data (last MRP run), use J_3AM_DISPOSITION_LOG.

1.5.2.3 New User Interface for MD04/MD05 (New) Use

As of SAP AFS 5.0, there is no longer a separate AFS view in MD04. All SKU level data is now integrated in the normal MD04/MD05 transactions.

Additional enhancements include the following:

• AFS filter redesigned to cover all needs

• Compress/expand function extended to all MRP element types

• Improved handling of exception messages

• Performance improvements Effects on Existing Data

None 1.5.2.4 Stock Coverage Is Now Available in /AFS/MD04 and /AFS/MD06 (New) Use

In previous releases, due to performance reasons, stock coverage display was available only in MD06. As of SAP AFS 5.0, this function is now available for the following transactions: -MD05 -MD06 -/AFS/MD04 -/AFS/MD06


Customizing menu path: Production -> Material Requirements Planning -> Evaluation -> Configure MRP List/Stock Requirement List

Activate Column: Days' Supply in MD06 is obsolete 1.5.2.5 Third Party Orders No Longer Displayed in /AFS/MD04 (Deleted) Use

As of SAP AFS 5.0, third party orders are not displayed in /AFS/MD04 and MD04.

SAP AG 10.12.2004


To harmonize with non-AFS R/3 systems, third party orders do not have requirements and cannot be displayed.

To check for deviations in quantity and date, refer to SD reports SDBANF02, SDBANF05 and other SD tools for third party order processing. 1.5.2.6 BAdI for AFS Stock/Requirement List (New) Use

As of SAP AFS 5.0, a new Business Add-In (BAdI) /AFS/MD_STRQ_LIST is available for the AFS Stock/Requirement List (transactions /AFS/MD02, /AFS/MD04, and /AFS/MD06). You can use it to modify the way the system displays the table information.


The AFS Stock/Requirement report user exits from previous AFS releases can no longer be used. However, you can implement the old coding in one of the new BAdI's methods.

1.5.2.7 User Favorites/Navigation Profile Supported in MD04/MD05 and /AFS/MD04 (Changed) Use

As of SAP AFS 5.0, you can add buttons to navigate into other transactions (for example, the AFS Stock Requirements List).

Some branches from MD04 to the AFS Stock Requirements List are not available by default. You can now create these branches manually by adding user navigation buttons to the screen.

NOTE: These functions are not new. However, they were not available in the previous release due to technical reasons, but have now been reactivated.


Use transaction Define Navigation Profiles to modify the settings.

1.5.2.8 Exclusion of Requirement Classes from MRP and/or StockRequirements Li (New) Use

As of SAP AFS 5.0, you can now exclude specific requirement classes from MRP and/or the Stock Requirements List.


None


Use transaction OVZG (Requirements Classes) and make an entry in the No field for each class you want to exclude. 1.5.2.9 Advanced Size Optimization (New) Use

As of SAP AFS 5.0, the Advanced Size Optimization provides a lot sizing procedure that supports a two-level rounding feature: rounding values can be maintained both at the material and SKU level. The system performs SKU level rounding first, then it rounds the stock proposal up to the material level in the second step. SKU level rounding is still considered during material level rounding as well.

SAP AG 10.12.2004


Advanced Size Optimization combines presizing with the rounding functionality. Presizing checks the rounding values maintained at either the material or size level. This leads to a purchase requisition or purchase order that is both spread to sizes as well as rounded according to rounding values already maintained in the Material Master for MRP requirements

Three user exits are available. Two can be used to control rounding based on stock category (for example, you can switch off rounding for one stock category). The third user exit determines the priority of the sizes within the size curve while spreading the extra quantity.

SAP AG 10.12.2004


1.6 IS-AFS-SD Sales and Distribution

1.6.1 Deallocation for Sales Orders (Enhanced) Use

As of SAP AFS 5.0, deallocation in SD has been enhanced. You can now make Customizing settings specifically for the deallocation function using a new IMG activity.

Previously, reductions in quantities in a sales order always resulted in a deallocation of stocks that had already been assigned. In the new deallocation rule for SD, you can still define how you want the system to respond if the requirement quantities are reduced, or if the storage location or requirements category is changed in an allocated sales document.

You can also create a sort rule that defines the sequence in which the assigned stocks are deallocated. This enables you to specify whether you want the system to deallocate purchase orders before batch stock, for example.


You make settings in Customizing for AFS Allocation Run > Cross Applications > SD Handling.

See also

Release Note for Allocation Against Future Receipts

1.6.2 ATP Substitution (New) Use

As of SAP AFS 5.0, there is a new substitution function in the SD ATP (available to promise) process that allows you to replace the material, plant, grid value or category for a sales order item or schedule line


Substitution is controlled by the substitution rule. You can enter the substitution rule on the sales order ATP screen.

For dynamic substitution control, you can link a substitution strategy to the Customer Master.

Substitution uses the master data of the material determination. You can define plant and dimension value substitution in material determination, or use the general substitution rule for plants or characteristics.

1.6.3 Contract Call Off Handling (New) Use

As of SAP AFS 5.0, there is a new, user-friendly contract release order entry screen. You can enter call off quantities directly in the Contract SKUs Overview where open quantities for each SKU are displayed and updated. It allows you to handle contracts with a large number of line items easily and quickly, giving you a clear overview of open and released quantities. Sorting and filtering features (for example, sorting line items by material) provide for very efficient processing of release orders

SAP AG 10.12.2004


1.6.4 AFS Master Data for Categories and Dimensions (Changed) Use

As of SAP AFS 5.0, basic data for grids and category structures has changed. Grid dimensions have been replaced by characteristics, and category structures can only be created from characteristics. Use transaction CT04 to create characteristics for grids and category structures.

• For category structures, the system uses characteristics of group '/AFS/SAP-C' (AFS characteristics for categories)

• For grids, the system uses characteristics of group '/AFS/SAP-D' (AFS characteristics for dimensions).

Relevancies are maintained for the characteristics regardless of whether they are associated with a grid or a category structure. In previous releases, relevancies could be maintained for the structure field even though the same reference field was used in more than one structure. Also from the current release onward, only plant-independent structures are supported.

A new grid IDoc type (J3AGRI02) has been created to accommodate the shift of grid dimensions to characteristics.


During upgrade, the following two XPRAs convert existing grid dimensions and category structure fields into characteristics: -/AFS/NDIF_CREATE_CHAR -/AFS/NDIF_CREATE_CAT_CHAR The effects on grid dimensions and category structure fields are as follows:

Dimensions

XPRA /AFS/NDIF_CREATE_CHAR: This XPRA runs across all clients and converts all dimensions into characteristics. It also updates all the relevant tables by replacing dimensions with the characteristic information. If an existing characteristic is assigned to a dimension, that characteristic replaces the dimension.

To avoid any inconsistencies in the AFS Configuration Master Data, you must run two reports in the following sequence: ...

1. Mass reorganization report /AFS/NDIF_MASS_REORG. This deletes all the existing AFS Configuration Master Data.

2. Mass update report /AFS/NDIF_MASS_UPDATE. This recreates the AFS Configuration Master Data.

In previous releases, you could maintain a sort sequence for dimension values. Now the sort sequence is the sequence in which you enter the values for the characteristics. During upgrade, however, the XPRA updates/inserts characteristic values as they were previously maintained for those dimensions that had sort sequences

The Mat.Conv. ID field (MARA-J_3AGMID) is now grayed out so that you cannot make any entries. This function will remain in SAP AFS 5.0, but will be deleted in the following release.

Categories

XPRA /AFS/NDIF_CREATE_CAT_CHAR: This XPRA runs across all clients and converts all category structure fields to characteristics and updates the category tables. Also if a reference field is used in more than one category structure and if the relevancies are different, then the XPRA creates new characteristics for each instance. Structures are not converted in the following special cases:

• When the check table category is 'F', 'E' or 'S'

Solution: Switch the structure in the older release itself. Create a new structure with characteristics. For the characteristic replacing the fields of check table category 'F', 'E'

SAP AG 10.12.2004


and 'S', ensure that all values for that field are filled in manually. Afterwards, run report /AFS/NDIF_SWITCH_STRUCTURES to replace the structures. Then upgrade will proceed smoothly.

• When a user-defined field has a user exit to populate the values

Solution: Replace the user exit and enter the values manually in Customizing for user-defined fields.

• When non-related structure fields exist

Solution: Report the problem to SAP. After evaluating the structure and category combinations, a new structure will have to be created in the older release. A report may be required to replace the problem structure with the new one.

You use report /AFS/NDIF_SWITCH_STRUCTURES to switch the plant-dependent structures over to a plant-independent structure. For existing 3.0B releases, this report can be run before upgrade. New plant-independent structures and their associated coverage strategies are created in the system and this report analyses whether the plant-dependent structures can be replaced with the new structures. An exception is raised if unrelated requirement and stock fields exist in the old plant-dependent structure.


IDoc processing for grids has changed. Use the new grid IDoc type J3AGRI02, with the following exception: you can still use the old IDoc type J3AGRI01 for inbound processing of characteristics with names less than 8 characters long.

For outbound processing, only J3AGRI02 is used.

Customizing for dimensions is no longer available. You can no longer create user-defined category fields.


None


The Details button for the category structure fields has been removed because all the relevant information is now shown on the table control itself. Dynamic Filling has been replaced by Defaults.

Overall the transaction has been simplified.

1.6.5 Check Report Renamed to /AFS/SDVBUK00 (Changed) Use

As of SAP AFS 5.0, the Check Status for Sales Documents report (/AFS/J_3ASTAT) has been renamed. The new name is /AFS/SDVBUK00.

1.6.6 Deallocation Now Controlled by Deallocation Rule (Changed) Use

In previous releases, automatic deallocation was activated by item category (TVAP-J_3AADAL). As of SAP AFS 5.0, automatic deallocation is now controlled by the deallocation rule in Customizing for AFS Allocation Run.


There is no automatic migration. You must set the allocation rule manually in the Customizing node Assign Rule to Order Type.

SAP AG 10.12.2004


1.6.7 Mass Document Change (New Line Items) (Changed) Use

As of SAP AFS 5.0, Mass Document Change now allows you to add line items with one or more schedule lines to a selection of existing sales documents. These new line items are copied from a reference document.

1.6.8 Purchase Order Type for Third Party Orders (Deleted) Use

As of SAP AFS 5.0, the AFS third party order purchase type (tvep-j_3absart) is no longer used. The field has been removed because it is no longer valid. Instead of the AFS field, the standard field will be used (tvep-bsart).

1.6.9 Fixed Category Allocation by ATP (Deleted) Use

As of SAP AFS 5.0, fixed category allocation by ATP (available to promise) is no longer supported. Use substitution of categories instead. (See release note ATP Substitution)


The corresponding fields have been removed from the Customer Master and coverage strategies.


Create substitution strategies (Customizing node Substitution Strategy) and assign them to the Customer Master

1.6.10 AFS Online Store (Deleted) Use

As of SAP AFS 5.0, the AFS Online Store is no longer available.

If you want to create and change sales orders via the Internet, use the AFS Internet Sales R/3 Edition instead.

1.6.11 Rejection Codes for AFS Schedule Lines (Changed) Use

As of SAP AFS 5.0, there are two new settings in Customizing for rejection codes:

• You can define how the system should behave if a schedule line is partly referenced or allocated

• You can define which rejection codes besides J0 should be removed before a new ATP is triggered. (J0 is always removed.)


Two new fields have been added to the Maintain Rejection Code for AFS transaction.

1.6.12 Parallel Processing for Rescheduling Use

As of SAP AFS 5.0, the Rescheduling function now supports parallel processing; that is, it is able to run in different processes or on different application servers simultaneously.

SAP AG 10.12.2004


1.6.13 Entering Same SKU Multiple Times in an MTO/PTO (New) Use

As of SAP AFS 5.0, you can now enter a SKU several times in one make-to-order/purchase-to-order item. You do this by turning off the Customizing setting that normally triggers an error message when the system finds duplicate SKU entries.


In Customizing node Define Variable AFS Messages, select application area 8W, message number 287, and leave the Cat field blank. This means that the system will generate no message if it finds a duplicate.

1.6.14 Season (Enhanced) Use

As of SAP AFS 5.0, seasonality is no longer restricted to sales documents, but also supports documents in Purchasing and Production.

You can define a common season hierarchy for all applications in Customizing. Time intervals are maintained separately for requirement/stock elements.

You activate season determination: -At the document header level for sales documents -In the Material Master (AFS Basic data) for stock elements

1.6.15 Domain ZAEHK Changed Back to Two Digits (Changed) Use

As of SAP AFS 5.0, domain ZAEHK reverts back to its original 2-digit length. Effects on Existing Data During upgrade, all database tables using ZAEKH are automatically converted to use the proper length.

Database table KONV is excluded from this conversion, since it still uses a 3-digit field.

See OSS Note 596324 for details.

SAP AG 10.12.2004


1.7 IS-AFS-ARUN Allocation Run

1.7.1 Access Rule (Changed) Use

As of SAP AFS 5.0, Customizing for access rules has been changed to provide ease of use and better classification. Each access rule is classified into one of the following:

• Material

• Partner

• Direct

• User-defined index

For the first three options; only the standard selection routines will be used. For each access rule, the system displays the program name, selection view, selection function module and preselection function module. These fields are for display only and cannot be changed.

For the user-defined index, the same fields appear, but you can change the entries. This allows you to enter your own selection reports, for example.


None


You make the settings in the Customizing node Access Rule

1.7.2 Adjust Allocation Quantities in the ARun Optimizer (New) Use

As of SAP AFS 5.0, there is an adjust function combines the allocation and deallocation processes in one step. You enter a specific quantity or percentage. All selected schedule lines are then adjusted to this level. Schedule lines with higher fillrates are deallocated first, then the schedule lines with lower fillrates.

1.7.3 Control of Allocation Quantities in the ARun Optimizer (New) Use

As of SAP AFS 5.0, you can allocate in the ARun Optimizer up to a special percentage, by a special percentage, up to a maximum quantity, and by a special quantity. You can also define which source of stock the allocation process is to consume. Possible stock sources are free available stock, own stock, and shared stock.

1.7.4 Customer Sales Areas (New) Use

As of SAP AFS 5.0, you can define Customer Sales Areas (CSA) to uniquely identify a set of allocation groups (a set of orders grouped together based on your own criteria).

SAP AG 10.12.2004


The CSA belongs to a Customer Sales Representative (CSR), who is the only person authorized and responsible for updating the orders and their allocation statuses in the ARun Optimizer. In addition, you can make Customizing settings so that when a CSR deallocates stock for orders within the CSA, the freed stock remains reserved for that CSR or the CSR's substitute. This is referred to as CSR stock and is available to the CSR for subsequent allocations.

Using authorizations, it is possible to transfer CSR stock to unrestricted stock or to another CSR.


None


You can make the appropriate Customizing settings in AFS Allocation Run > ARun Optimizer > Customer Sales Areas.

See also

For more information on assigning allocation groups to CSAs, see the Permanent Grouping (Allocation Groups) release note.

1.7.5 Deallocation of Partial Quantities in the ARun Optimizer (New) Use

As of SAP AFS 5.0, it is now possible to deallocate part of an allocated quantity by a percentage, up to a percentage, by a special quantity, or up to a special quantity. You can also set a limitation quantity at which the system should stop the deallocation process.

1.7.6 Deallocation During Goods Issue Posting (New) Use

As of SAP AFS 5.0, you can perform deallocation when posting goods issues. This function allows you to perform unplanned goods issues for a purchase order, such as scrapping or cancelling a goods receipt. It is also possible to post a goods issue for stock that has already been assigned to a sales order. You can specify in Customizing how the system should behave when posting a goods issue.

You can create a sort rule to specify the order in which the system should deallocate the orders to which this stock is already assigned. You assign deallocation and sort rules to the relevant plants. The deallocation function must be activated separately for each movement category. However, for movement types such as 601 (goods issue for deliveries) this is not necessary, as in this case the system automatically performs deallocation when changes are made.


You make Customizing settings for GI Handling in AFS Allocation Run > Cross Applications > GI Handling.

1.7.7 Allocation Against Future Receipts/Deallocation for Goods Receipts (New) Use

As of SAP AFS 5.0, you can allocate future receipts to sales orders. Previously you could only consider batch stock in an allocation run. Now, depending on the settings in Customizing, you

SAP AG 10.12.2004


can also use purchase orders, shipping notifications, and production orders for allocation. You define the stock types for which allocation is to be performed in Customizing.

NOTE: It is only possible to perform allocation against future receipts in status R (reserved).

Allocation Against Future Receipts is closely linked to the new deallocation function. For goods receipts, you define in Customizing how the system should respond in certain situations when posting goods receipt for a purchase order or shipping notification has already been allocated. For example, you can specify whether deallocation should be performed when a storage location is changed during goods receipt posting, and if so, whether the system should issue a warning or an error message. For situations in which deallocation is triggered, you can create a sort rule to specify the deallocation sequence for the orders to which the purchase order/ shipping notification for which you have posted the goods receipt is assigned. You assign deallocation and sort rules to the relevant plants.


For Customizing details, see Release Note Allocation Against Future Receipts

For Deallocation, you make settings in Customizing node AFS Allocation Run > Cross Applications > GR Handling

1.7.8 Allocation Against Future Receipts/Deallocation for Purchase Orders (New) Use

As of SAP AFS 5.0, you can allocate purchase orders and shipping notifications to sales orders. Previously you could only consider batch stock in an allocation run. Now, depending on the settings in Customizing, you can also use purchase orders, shipping notifications, and production orders for allocation. You define the stock types for which allocation is to be performed in Customizing.


Allocation Against Future Receipts is closely linked to the new deallocation function. For purchase orders and shipping notifications, you define in Customizing how the system should respond in certain situations when changes are made to a purchase order or shipping notification that has already been allocated. For example, you can specify whether deallocation should be performed when a storage location is changed, and if so, whether the system should issue a warning or an error message. You can create a sort rule to specify the sequence in which the orders to which the purchase orders or shipping notifications are assigned should be deallocated. You assign deallocation and sort rules to the relevant plants.



For Deallocation, you make settings in Customizing node AFS Allocation Run > Cross Applications > PO Handling

1.7.9 Allocation Against Goods Receipts/Deallocation for Production Orders (New) Use

As of SAP AFS 5.0, you can allocate production orders to sales orders. Previously you could only consider batch stock in an allocation run. Now, depending on the settings in Customizing, you can also use purchase orders, shipping notifications, and production orders for allocation. You define the stock types for which allocation is to be performed in Customizing.


SAP AG 10.12.2004


Allocation Against Future Receipts is closely linked to the new deallocation function. For production orders, you define in Customizing how the system should respond in certain situations when a production order has already been allocated. For example, you can specify whether deallocation should be performed when a storage location or a quantity is changed, and if so, whether the system should issue a warning or an error message. You can create a sort rule to specify the sequence in which the orders to which the production orders are assigned should be deallocated. You assign deallocation and sort rules to the relevant plants.



For Deallocation, you make settings in Customizing node AFS Allocation Run > Cross Applications > PP Handling

1.7.10 Allocation Against Future Receipts (New) Use

As of SAP AFS 5.0, you can allocate future receipts to sales orders. Previously you could only consider batch stock in an allocation run. Now, depending on the settings in Customizing, you can also use purchase orders, shipping notifications, and production orders for allocation.

NOTE: It is only possible to perform allocation against future receipts in status R (reserved). Purchase requisitions and planned orders can still only be allocated in preview mode.


To use Allocation Against Future Receipts, you must maintain the following Customizing settings:

• Stock selection

• An allocation rule that you assign to the relevant ARun Type. Using the allocation rule you can, for example, specify the timeframe within which purchase orders are to be taken into account for allocation, or in which sequence batch stock, purchase orders and shipping notifications are to be allocated. You can also make Customizing settings so that the system performs certain checks, such as a season or a category check.

This new function is closely linked to the deallocation function. You can use this function to control whether or not the system deallocates an allocated quantity when, for example, you change the confirmed delivery date in a sales order or purchase order. For more details, see the following release notes:

• Deallocation for Sales Orders

• Allocation Against Future Receipts/Deallocation for Purchase Orders

• Allocation Against Future Receipts/Deallocation for Production Orders

• Allocation Against Future Receipts/Deallocation for Goods Receipts

• Deallocation for Goods Issues

1.7.11 ARun IMG Structure (Changed) Use

As of SAP AFS 5.0, the Implementation Guide (IMG) structure for the AFS Allocation Run has changed to allow for more meaningful categorization of existing Customizing settings and addition of new ones.

• Stock Selection Rule

SAP AG 10.12.2004


The stock selection rule in ARun has been enhanced to support allocation against future receipts (early allocation). See the Stock Selection Rule Release Note.

• Access Rule

Customizing for access rules has changed for ease of use and better classification. See the Access Rule Release Note.

• Allocation Logic

Customizing for allocation logic has changed for ease of use. See the Allocation Logic Release

Note.

• Allocation Rule

The allocation rule provides the conditions and rules that define the allocation of a stock element to the requirement. This is a completely new Customizing for ARun and includes two additional aspects of stock selection compared to the previous release: Consider Batch Number and Consider Storage Location. The category check Customizing has moved under allocation rule Customizing. The allocation rule is attached to the ARun type.

• Assign Rule to Order Type

This Customizing has changed from the earlier ARun Control in SD Documents. More fields have been added to support the new ARun features in this release. See the Assigning Rules to Order Types Release Note.

• Cross Application Settings

The cross application settings include all the ARun settings pertaining to the different application areas (SD/MM/PP). These settings define how each of these areas interfaces with ARun. For more details on each application area, see the corresponding release notes.

• Reallocation

In the reallocation rule Customizing for Adjustments, two fields (columns) that are no longer relevant have been removed. These are Event and Allocatable Quantity. The rest of the reallocation function remains the same.

• Status Determination

The ARun status determination rule that was a part of the ARun type Customizing has been removed. This ensures that only the standard ARun function module for status determination is used.

• List Maintenance

Customizing settings for ARun lists and layout have been removed. The new release uses the standard ALV list for display purposes, which provides standard features that can be used for all possible configurations of list variants.


• Existing data on list variants is affected. You must reconfigure the new display variants for all the ALV displays as necessary.

• You must reconfigure the Customizing for stock selection (Consider Batch Number and Consider Storage Location) that has moved under the allocation rule.

• Category check Customizing has moved under allocation rule Customizing, without any change in function but only changes in usability.

• An XPRA is available to change the existing Customizing data to the new Customizing setup.

See also

SAP AG 10.12.2004


Release note for Permanent Grouping (Allocation Groups)

1.7.12 Keep MRP Status (New) Use

As of SAP AFS 5.0, you can fix the MRP status of an assignment (F or R) so that subsequent ARuns cannot change it. An MRP status with this attribute (Keep MRP status) will not change, even though a release check in later ARuns would determine a different MRP status. In other words, the attribute freezes the MRP status, whether or not a release check fails.


You make this setting in the Customizing node Allocation Status.

1.7.13 Level Configuration in the ARun Optimizer (New) Use

As of SAP AFS 5.0, the ARun Optimizer offers dynamic view generation for specific business tasks, meaning that a predefined configuration setting enables report data to be displayed through different drill-down paths. You can configure the view to have a maximum of four levels and three different paths. If you choose not configure the view, the ARun Optimizer will process and display the data as a simple list.


You configure the view in the Customizing node Level Configuration.

1.7.14 Log File (Changed) Use

As of SAP AFS 5.0, there are new ARun log file tables.

Due to the new Allocation Against Future Receipts function, the ARun Number field (ARNUM - 10 character) in the log file has been replaced by two new fields:

• Document Number (DOCNUM - 12 character)

• Document Type (DOCTYP - 1 character)

The addition of these fields required two new tables to be created. All exceptions are now stored in the following tables:

• /AFS/ARUN_PROT (instead of J_3APROT)

• /AFS/ARUN_PROI (instead of J_3APROI)

The old exception tables are no longer used.

1.7.15 Allocation Logic (Changed) Use

As of SAP AFS 5.0, the allocation logic has changed to enhance ease of use during configuration. One important change is that you no longer enter a function module name. The allocation run always uses the standard function modules for FIFO and spread.

The following shows the mapping between the old and new Customizing settings:

SAP AG 10.12.2004


Old Allocation Logic Mat. Rem. New Up to Alloc.Rem. Short. Qty. Logic Rel.Qty. Qty.Roll

J 3AR ALLOCATION STRATEGY FIFO FIFO J 3AR ALLOCATION STRATEGY SPRD 3 SPREAD J 3AR ALLOCATION STRATEGY SPRD 3 1 SPREAD X

J 3AR ALLOCATION STRATEGY SPRD 1 1 FIFO X J 3AR ALLOCATION STRATEGY SPRD 2 1 SPREAD X X


An XPRA is available to change the existing Customizing data to the new Customizing setup.


The settings are in Customizing node Allocation Logic.

1.7.16 Maximum Number of Values to Process in ARun Optimizer (New) Use

As of SAP AFS 5.0, you can control the maximum number of lines to be processed in the ARun Optimizer. This avoids performance problems in case the user selects a very large number of schedule lines or assignments.


In Customizing node Maximum Values to Process you can enter the ARun Optimizer application area, function code, the maximum number of lines to process, and the action.

1.7.17 Status Determination in the ARun Optimizer (New) Use

As of SAP AFS 5.0, you can have the system determine the MRP status of all assignments for the flagged schedule lines. You enter attributes that tell the system how to handle open quantities and allocated quantities. Based on thiese attributes, the standard ARun status determination applies the corresponding MRP status to the assignments. Optionally, you can decide whether the new MRP status should be kept so that no subsequent process (such as ARun or the ARun Optimizer) can change it.

1.7.18 ARun Optimizer (New) Use

As of SAP AFS 5.0, the ARun Management Tool has been replaced by the ARun Optimizer. The ARun Optimizer includes all features from the previous ARun Management tool as well as the following new ones:

• Allocation

! Absolute or proportional

! Limitation

! Stock source

! Include VAS correlation (adjust or readjust)

SAP AG 10.12.2004


• Deallocation

! Absolute or proportional

! Limitation

! Include VAS correlation (adjust or readjust)

• Reallocation

! Runs on allocation group and sales order levels

! Deallocation with subsequent allocation

! Include private/shared stock

• Adjustment

! By percentage or quantity

• Release

! Extension (include schedule lines with/without "keep" flag)

! Combination with KEEP function (without keep; overwrite existing reasons)

• Blocking


! Combination with KEEP function (without keep; overwrite existing reasons)

! Event (for status determination)

• Status determination


! Combination with KEEP function (w/o keep; overwrite existing reasons)

! Based on ARun status determination

• Release check

! Similar to ARun release check

! On the allocation group and sales order levels

• Keep MRP status

! Keep (freeze) an MRP status (for example, keep status R despite 100% fulfillment)

• Rejection of sales order schedule lines

! Flag for rejection (two-step method)

! SD mass document change report will reject the schedule lines

! Immediate rejection (based on parallel work processes, to reduce response time)

• Special handling

! Prioritize schedule lines

! Limitation (maximum quantity to be allocated)

• Sales order changes

! Branch to the SD sales order in change mode

! Reassign allocation groups

• Substitution

SAP AG 10.12.2004


! Similar to the ARun substitution

! Manual substitution (allows the user to overwrite the proposed substitution)

! VAS correlation

! Interactive or automatic (with dialog)

• Evaluation

! Allocation group level

! Similar to a user exit

! Calculate business figures (snapshot) for an allocation group first (for example, number of allocated sales order lines)

! Calculate business figures before saving

! Compare business figures, present the delta on a popup window

• "Who" function

! Show stock owned by other users

! Different stock types (for example, shared stock, assignments, and so on)

• Utilities

! Selection screen generation

! Generation of allocation group table, customer sales area table, determination table

! Assign allocation groups and customer sales areas

! Allocation group maintenance (for example, reorganization)

! Calculate allocation group totals (allocation group totals for stock with status F, R, D and T)

! Customer sales area handling (for example, split or merge)

! Customer sales area reorganization Effects on Existing Data

None


You must create a new ARun Optimizer type in Customizing for ARun Type

See also

Additional release notes for the ARun Optimizer

1.7.19 Parallel ARun (Enhanced) Use

As of SAP AFS 5.0, the final release check and posting in parallel allocation runs has been extended. Now the release check and posting are done in parallel as well in packages of assignments for one order each.

Since no grouping release check can be done with order packages (because not all assignments within one group are in one package), you can control the package size by using a Business Add-In (BAdI). In addition, you can use a BAdI to influence the package building for the allocation part (for example, to allow material substitution).


SAP AG 10.12.2004


You specify the server groups to be used for parallel processing in Customizing node Server Group Definition (Parallel Processing)

See also

Consulting notes on Parallel ARun.

1.7.20 Permanent Grouping (Allocation Groups) (New) Use

As of SAP AFS 5.0, you can permanently group specific schedule lines together during order creation, based on predefined criteria of your choosing. These permanent groups are called allocation groups. This feature is in addition to the temporary grouping function, where the groups are created dynamically during the Allocation Run.

Permanent grouping determination is controlled by the allocation group tables, and unique allocation group numbers are generated for each new combination of key fields.

You can assign multiple allocation groups to a Customer Sales Area (CSA), but an allocation group can only be assigned to one CSA. Thus, there is an n:1 relationship between allocation groups and CSAs.


You can make the appropriate Customizing settings in AFS Allocation Run > ARun Detail > Grouping/Sorting > Permanent Grouping.

See also

For more information on CSAs, see the Customer Sales Areas release note

1.7.21 Reallocation in the ARun Optimizer (New) Use

As of SAP AFS 5.0, the ARun Optimizer carries out reallocation as follows.

• The ARun Optimizer uses a dialog to configure the allocation process. If an ARun type is assigned to the Optimizer, all the allocation parameters have already been proposed on the dialog box.

• The reallocation process first deallocates all selected lines. The stock is then moved into the user's personal stock buffer.

• In a second step, the stock is allocated again, consuming the personal stock. You can also configure the ARun Optimizer to allow free available stock as second stock source as well

1.7.22 Rejecting Schedule Lines in the ARun Optimizer (New) Use

As of SAP AFS 5.0, you can reject schedule lines from ARun Optimizer by assigning them a rejection indicator.

There are two ways to do this:

• Set the rejection indicator with immediate effect.

• First flag the schedule lines for rejection. A subsequent mass processing (such as a regularly scheduled batch run) rejects the schedule lines in a separate step. If you set rejection indicators using this two-step method, you will be able to remove the rejection indicators at any time up until the mass processing is triggered.

SAP AG 10.12.2004


1.7.23 Rejection of Open Quantities (New) Use

As of SAP AFS 5.0, you can have the system automatically reject open quantities that could not be allocated. This is an extension to the existing drop function during release check (sm30, J_3AREPA_V).

The rejection is executed by the SD Mass Maintenance tool.


None


You make the setting in Open Quantity field in the Customizing node Release Rule.

1.7.24 Release Check in the ARun Optimizer (New) Use

As of SAP AFS 5.0, you can implement a release check in the ARun Optimizer. This is similar to the release check in ARun. A dialog box will ask you to enter a release rule. The system displays the parameters from the default release rule (Optimizer type). You can either accept or overwrite these parameters. The system then carries out the release check, which includes all assignments for the flagged lines.

NOTE: The release check can change the MRP status of the assignments. The release check is available on the allocation group and sales order levels only.

1.7.25 Release/Block of Flagged Schedule LinesUse

As of SAP AFS 5.0, you can release or block all flagged schedule lines at once.

• Release

This releases all assignments for the flagged lines. You can also specify whether the MRP status F should be kept so that no subsequent process (such as ARun or the ARun Optimizer) can change it.

• Block

This blocks all assignments for the flagged lines. You can also specify whether the MRP status R should be kept so that no subsequent process (such as ARun or the ARun Optimizer) can change it.

1.7.26 Assigning Rules to Order Types (Enhanced) Use

As of SAP AFS 5.0, several new fields have been added to Customizing for ARun Control in SD Documents:

• Deallocation Rule

This rule determines how the system reacts when an ARun-relevant field is modified in a sales document. You define deallocation rules in Customizing node Deallocation Rule.

• Release Rule

This rule determines the release checks carried out for the allocation and the subsequent status determination of assignment. You define release rules in Customizing node Release Rule

SAP AG 10.12.2004


• Sorting

This is the sort sequence of the stock used during deallocation when an ARun-relevant field in a sales document is modified. You define these rules in Customizing node Deallocation Sort.

• Allocation Groups

Selecting this field enables the Order Type in the sales area for the Permanent Grouping function. The system then assigns an allocation group number when a sales document is saved.

• Customer Sales Area

This specifies that the system is to assign a CSA (Customer Sales Area) when a sales document is saved.


None


The Customizing node is Assign Rule to Order Type.

1.7.27 Branch from ARun Optimizer to Sales Order Maintenance (New) Use

As of SAP AFS 5.0, the ARun Optimizer enables you to branch directly into the Sales Order Maintenance screen. Changing a sales order automatically updates the corresponding ARun Optimizer views, so that when you return to the ARun Optimizer, you have the latest data available.

1.7.28 Flagging Schedule Lines for Special Handling (New) Use

As of SAP AFS 5.0, you can flag sales order schedule lines for special handling in ARun; for example, high priority customers, special release fill rates, restrictions on the quantity to be allocated, and so on. You can enter priority information and release check rules.

You assign flag rules to the schedule line in ARun Optimizer. In the allocation run, the system handles flagged schedule lines according to these special handling instructions.


To create flag rules, use Customizing node Special Handling (Flag Orders).

1.7.29 Stock Overview in the ARun Optimizer (New) Use

As of SAP AFS 5.0, the ARun Optimizer has a special stock overview to indicate who has matching stock to cover material shortage for a selected schedule line. It includes different types of stock sources, such as the user's own stock (temporary stored in the ARun Optimizer), matching assignments (such as potential stock), assignments for which other users are responsible, and so on.

1.7.30 Stock Selection Rule (Changed) Use

SAP AG 10.12.2004


As of SAP AFS 5.0, the stock selection rule in ARun has been changed to support the new Allocation Against Future Receipts function (early allocation). This enables you to reserve a future receipt for a requirement in ARun normal mode.

In Customizing, stock is now classified into two types for processing in normal ARun mode:

• Physical stock (batch, consignment and made-to-order/purchase-to-order)

• Future receipts (purchase orders, shipping notifications and production orders)

In preview mode, you have the option of selecting purchase requisitions and planned orders.


See Customizing below.


You make the settings in the Customizing node Stock Selection The earlier Customizing for stock selection included settings for Information from Sales Order to be

considered during the allocation process. These settings (Consider Batch Number and Consider Storage Location) have been moved to a separate Customizing node for Allocation Rule.

The Customizing setting Allowed Segments from the physical stock tables remains the same as in the previous release.

An XPRA is available to adapt the existing Customizing settings to the new Customizing settings.

1.7.31 ARun Substitution Use

As of SAP AFS 5.0, there is a new substitution function in ARun that allows you to replace the material, plant, grid value or category for a requirement at time of substitution.

The new function is part of standard Online and Batch ARun. If you use Parallel ARun, you must be careful about package building for the allocation process (using BAdI /AFS/ARUN_PACKAGES).


Substitution is controlled by the substitution rule (transaction SM30, /AFS/subrule). You assign the rule to the appropriate ARun type (transaction SM30, j_3aarco). For dynamic substitution control, you can link a substitution strategy to the Customer Master.

Substitution uses the master data of the material determination. You can define plant and dimension value substitution in material determination, or use the general substitution rule for plants (transaction SM30, /AFS/SUBRPLA_VC) or dimensions (transaction SM30, /AFS/SUBRDIM_VC).

There is an option available for ensuring that stock of the same material and/or plant is allocated to all requirements within an allocation group. NOTE: This option can significantly impact runtime performance.

1.7.32 Deallocation Now Controlled by Deallocation Rule (Changed) Use

In previous releases, automatic deallocation was activated by item category (TVAP-J_3AADAL). As of SAP AFS 5.0, automatic deallocation is now controlled by the deallocation rule in Customizing for AFS Allocation Run.

SAP AG 10.12.2004



There is no automatic migration. You must set the allocation rule manually in the Customizing node Assign Rule to Order Type.