AFS Allocation Settings:

Requirement Selection
Use
In this section you determine how the system is to select requirements records during an allocation run.
Requirements records for a specific SKU of an AFS material can be created by various applications. For
example, requirements are created when you enter sales documents in Sales and Distribution (sales order
requirements) and in production (planned independent requirements).
Therefore, for each rule of the requirements selection, you must uniquely specify the origin of the
requirements records that the system is to consider for the allocation run.
You also specify whether the selected requirements records are locked for other users or processes during
the allocation run. SAP recommends that you set the indicator exclusive lock. This is especially important if
you want to execute several allocation runs at the same time in the background. Only the exclusive lock
ensures that two allocation runs that are processing in parallel do not select the same requirement record.
Otherwise, the same requirements record might be allocated twice.
Activities
Define your rule for the requirements selection by assigning an alphanumeric key (maximum of four
characters) and a description. Then go to the detail screen to create the rule.
Stock Selection
Use
In this section you specify how the system is to select stock elements during an allocation run.
Different types of stock elements can exist for each SKU of an AFS material within each application. Stock
elements include batch stock, which is freely available in the warehouse, as well as batch stock that is
blocked (for example, because it is still in quality check or because it is special stock for a specific
customer). Future incoming stock (for example, from purchase orders or production orders) is another
example of stock elements.
For each stock selection rule, you must uniquely specify which stock elements the system should use for
requirements coverage during an allocaton run.
Activities
1. Define your rule for the stock selection by assigning an alphanumeric key (maximum of four
characters) and a description.
2. Go to the detail screen to create the rule.
3. Select the rule that you want to use for the requirements selection with your basic allocation
type in the detail view under Free available batch stock.
4. Assign only the free available batch stock type (element MCHB with characteristic CLABS) to
this rule.
5. Activate the entry.

Access Rule
In this IMG activity you define an access rule for each allocation type. With this access rule, you specify
how the system accesses the database to read the individual requirements.
Define Access Rule
There are three different access methods in the standard:
Material index [program J_3AARS1]
Partner index [program J_3AARS2]
Direct access [program J_3AARS3]
Each allocation type must be assigned an access rule. The type of access has an influence on system
performance. Access using an index can lead to an improvement in performance, whereas direct access
can greatly diminish performance.
Activities
1. Define your access rule by assigning an alphanumeric key with a maximum of four characters
and a descriptive text.
2. Specify which index should be used for access.
3. Also specify the requested selection view. You can define your own variants for taking away
fields from the complete selection view.
4. Activate your access rule.

Action Rule


Using the action rule you make sure that an allocation can take place when the release check has failed.
The assignments the ARun proposes can be kept with help of the action rule, because the ARun would
otherwise dismiss them due to the failed release rule.
See also: Allocation Control when Allocation Criteria are not fulfilled
The allocation rule works with the reallocation rule included in the allocation type. Subsequent allocation
runs can then continue to fill stock until the release rules are fulfilled and the result of the release check is
therefore positive
Example
The standard example of the action rule reserve quantity until fulfillment keeps up stock assignments if:
Release check fails for any object
ARun message type has an error setting
Allocation run event R occurs
Rounding

In this section you can define special rounding rules to be used during an allocation run. With the
ARun rounding rules you set whether the system should round up or down to the nearest multiple
of a unit of measurement. You also control that it rounds before actually allocating the stock. The
rounding takes place during the release check.
Example
You sell a material in boxes of 12 only. Your customer ordes 1,200 pieces of this material.
However, there are only 1000 pieces available in stock at the time of the allocation. Using the
corresponding rounding rule, you can control that the stock is allocated in a quantity that can be
delivered in boxes of 12. In this case, only 996 pieces will be allocated, resulting in 83 boxes of 12.
Activities
1. Define your rounding rule by assigning an alphanumeric key with a maximum of four characters
as well as an explanatory text.
2. Make the necessary settings in your rule (enter the level at which the system should round,
whether it should round up or down, and so on).
3. Assign your rounding rule to a release rule.

VAS
Use
In this section you can customize the VAS(Value Added Service) correlation rule to be applied during the
Allocation Rule. The VAS rule that is created is attached to the release rule for the ARun Type.




BOM
Use
In this section you can customize the BOM (Bill of Material) correlation rule to be applied during the
Allocation Run. The BOM correlation rule is attached to the release rule that is used in the ARun Type. The
BOM Rule in ARun is valid only for assortments (LUMF).

Allocation Event

The allocation run event is relevant if the release check has failed. The entries in the fields Allocatable
Quantity and Open Quantity within the release rule as well as the allocation run event ultimately determine
the MRP status for the partial quantity of the requirement, for which batch stock is still available.
Activities
Define the allocation run event required for your processes by assigning an alphanumeric key with a
maximum of four characters as well as an informative text.
For each allocation run event enter the area in the allocation run environment for which it should be valid.
Further notes
See also: Allocation Control when Release Criteria are not Fulfilled



Release Rule




In the release rule you determine percentage-based minimum or maximum delivery quantities per release
level according to your company philosophy. These minimum delivery quantities are required to release an
order. You can define these percentage rates at order header level, sales order item level, sales order
dimension level, delivery group level, scheduling group level, and allocation group level, and respectively
for the corresponding heart sizes. You can define release rules for individual grouping rules, for special
customers, or for a certain allocation type.
Example
The majority of your customers is satisfied with a delivery quota of 80% per ordered item. In this case you
first define a release rule, enter the value of 80% at sales order item level, and then enter the release rule
in the allocation type. If an order from a normal customer is selected, the system checks whether 80% of
the ordered items can be delivered on a quantity basis. If this is the case, the item is released and can be
delivered. At the same time you can define a release rule for special customers with higher requirements.
This rule will only release orders if, for example, the ordered quantities are 100% fulfilled. If an order from a
special customer is selected by the same allocation run as above, the system checks whether 100% of the
total quantity is available.
Further notes
You must assign a release rule to each allocation type. If you did not maintain release rules for certain
allocation groups and certain customers, the release rule in the allocation type is used as default.


User Exits






In this section you can define additional release checks within the release rule, in addition to the standard
checks. The additional customer fields are designed for the user exits of the release rule. That means that
you can maintain additional data in order to recheck them in the release rule with help of the user exits.
You can do this at all release levels of the release rule.
Example
You only want to release orders with a delivery value of 5,000 DM and more.
Requirements
The user exits of the release rule must be filled accordingly.

Determination Table Generation





Use
This IMG setting is used to declare a release determination table, define the fields, and generate the table.
You can generate multiple release determination tables, but only one can be the default table and only that
one is used to determine release rules..
Activities
1. Declare the table and specify whether or not it is the default table. Make sure that the table
name is entered in the Customer name.
2. Select the table and define the fields to be used for release determination.
3. Select the table name and the field name and enter the sequence in which you want these fields
to be created in the table. Mark a field as a key if you want it to be used as a criterion for release
rule determination.
4. Go to the display mode and and choose Generate Table at the top node. You can now generate
the table.
Example
You can create a determination table for the following fields:
VBAK-AUART Sales Document Type
VBAK-AUGRU Order reason (reason for the business transaction)
VBAK-VKGRP Sales Group
When you generate the table, the following fields are generated:
MANDT Client
RESGY Release Strategy
AUART Sales Document Type
AUGRU Order reason (reason for the business transaction)
VKGRP Sales Group
REREG Release Rule
J_3AAWDG Application

Determination Table Maintenance

Use
In this step you maintain the mapping for determination of release rules. This can be done in two ways:
Default determination table maintenance
This is a simple one-to-one mapping of release strategies and release rules. You enter the release
strategy and the corresponding release rule to be used for this release strategy.
Generated determination table maintenance
This is a more customizable mapping where the release determination tables are used to
determine the release rules. You can create these determination fields and their values in the
corresponding table in Customizing for Determination Table Generation.
Release Strategy



Use
In this Customizing step you define the release strategy to be used during allocation for dynamic
determination of release rules. Here you only enter a name for your release strategy. No attributes exist
and none can be created in this area. You then assign the strategy to the Customer Master in the Sales
Area Data (AFS Additional Data). The system is then able to use this strategy during the allocation run to
determine the release rule. You control this by mapping the release rule to the release strategy.

Allocation Status




In this section you determine the allocation status. The allocation status is determined from
the allocation run event (from the action rule)
the control parameter for the field Allocatable Quantity (from the release rule)
the control parameter for the field Open Quantities (from the release rule).
A combination of certain parameters of these three fields results in the MRP status for the allocatable
quantity. Which MRP status should result is uniquely specified in the allocation run status.
See also: Allocation Control when Release Criteria are not Fulfilled
Example
If you want to reserve quantities that have already taken part in the allocation run, but were not allocated
because of the release rule, you can define that here.
Further notes
The allocation status is only for information. In the application, for example, it is displayed in the allocation
run screen, and is a selection criterion in the management tool and the reorganization.

LOG:
Logfile Rule






In this section you decide where the logs (exceptions) of the performed allocation runs are to be updated
should you need them.
Example
Basically logs can be stored in a database table or in a file. In a file the update is more compressed and not
as detailed as in a database, but the database must be reorganized on a regular basis. When updating in a
database, the log can be evaluated by its own programs. The exceptions are also available in the
management tool.
Standard settings
If an update of the performed allocation runs should take place, it must be defined in the respective
allocation type.

Statistics:
Statistic Rule


Use
In this section you determine how the result of an allocation run can be summarized and displayed as a set
of informative statistics. These statistics serve as a basis for evaluating an allocation run.
You determine the type of evaluation you want by using allocation statistics. If you use the function
modules provided, you will have a quality evaluation and/or value evaluation.
You can also implement different statistics using function modules you have defined yourself.
Statistic Group

Use
You need statistics groups to use several sets of statistics for each allocation run. You assign a statistics
group to an allocation type so that an evaluation is available after you have saved.
Statistic Assignment


Use
You assign multiple allocation statistics (value or quantitity statistics) to a statistics group. This enables you
to assign your own evaluations to an ARun type.
When you store statistic groups for your allocation type, the system updates the log files for each allocation
run based on the statistics you have defined.
ARUN TYPE

ARun Type



In this section you define the allocation type that forms the structure of the allocation run. In the allocation
type, you enter all the rules that you have defined in the previous IMG sections and with which you want to
control the allocation process in the system.
In the application, you must assign exactly one allocation type to each allocation run. That way you
determine the rules according to which the system carries out each individual allocation run. You can
define your own allocation types for different business processes.
Activities
Define the allocation types necessary for your processes by assigning an alphanumeric key with a
maximum of four characters as well as an explanatory text.
Assign the rules to your allocation type with which you want to control the individual steps during the
allocation. The following rules are mandatory for each allocation type:
Requirements selection rule
Stock selection rule
Access rule
Requirements sorting rule
Allocation logic rule (strategy)
Allocation status determination rule
If you want to execute special release checks for each allocation run, enter a release rule in your allocation
type. SAP recommends that you also specify that a final release check should take place in the application.
In addition, you should make entries for the determination of the release rule.
Permanent Grouping:
Grouping Strategy

Use
Temporary Grouping
In this Customizing step you define the grouping strategy to be used during allocation for dynamic
determination of groups. Here you only enter a name for your grouping strategy. No attributes exist
and none can be created in this area. You then assign the strategy to the Customer Master in the
Sales Area Data (AFS Additional Data). The system is then able to use this strategy during the
allocation run to determine the grouping rule. You control this by mapping the grouping rule to the
grouping strategy.
Permanent Grouping
With permanent grouping, the system uses the allocation groups (AG) tables to determine the
allocation group numbers according to the grouping strategy.

Activate Permanent Grouping










In this step you can assign various ARun-specific functions to the document categories.
Allocation
If you assign an allocation type to the sales document, the system tries to allocate a requirement
immediately when a sales document is entered or changed. The same conditions apply to the online
allocation as to the separate allocation run. A requirement can only be successfully allocated if there is
sufficient batch stock. If a special release procedure is activated for the relevant allocation type, the release
procedure is carried out in the online allocation. Note that the document must contain all delivery-related
data when it is saved. If it does not, the allocation is cancelled, the requirement is assigned the MRP status
and cannot be delivered immediately.
An online allocation is particularly useful for rush orders. Requirements for this type of document are
assigned MRP status F if the allocation is successful and can be delivered immediately.
If there is not sufficient batch stock when the order is entered or changed, the release rule used in the
allocation type determines whether or not an allocation can be made and if so, whether a fixed
requirements/stock assignment is made (MRP status F) or just a reservation (MRP status R). If the AFS
availability check is active, it is not run for the remaining allocatable quantity of the requirement. Depending
on the settings for the scope of the ATP check and on the stock situation, the remaining quantity is
confirmed or rejected for the date of the next stock receipt or RLT.
Example
o Assignment of an ARun type for immediate, automatic allocation when the document is
saved
o Activation of the "restore" function (contracts)
o Automatic creation of AGs (allocation groups) for use in ARun grouping
ARUN optimise control



Selection Report Generation
Use
In this section you can define and generate a selection report for ARun Optimizer. The selection report
selects data from database tables and passes it to ARun Optimizer for further processing.
Activities
The field application determines what the selection report selects. Valid options are:
Assignments = Select assignments
Allocation Groups = Select schedule lines
Requirements = Select requirements
The field set is a collection of tables and fields for selection.
1. Enter an application and a set and choose Tables/Fields.
2. For Application 1, select the tables and the corresponding fields for the selection report . These
tables and fields form the set. For Application 2, only the AG tables are available for configuration
and all the valid fields in the AG table would be considered for the selection report generation.
3. Choose Header and then choose Details.
4. Choose Simulation to check whether the selection report can be generated without error.
5. Choose Generate Report and enter the report name.
If the report is generated successfully, it can be used in the ARun Optimizer type.
Selection Report Generation




Use
In this section you can define and generate a selection report for ARun Optimizer. The selection report
selects data from database tables and passes it to ARun Optimizer for further processing.
Activities
The field application determines what the selection report selects. Valid options are:
Assignments = Select assignments
Allocation Groups = Select schedule lines
Requirements = Select requirements
The field set is a collection of tables and fields for selection.
1. Enter an application and a set and choose Tables/Fields.
2. For Application 1, select the tables and the corresponding fields for the selection report . These
tables and fields form the set. For Application 2, only the AG tables are available for configuration
and all the valid fields in the AG table would be considered for the selection report generation.
3. Choose Header and then choose Details.
4. Choose Simulation to check whether the selection report can be generated without error.
5. Choose Generate Report and enter the report name.
If the report is generated successfully, it can be used in the ARun Optimizer type.
Release Rule
In the release rule you determine percentage-based minimum or maximum delivery quantities per release
level according to your company philosophy. These minimum delivery quantities are required to release an
order. You can define these percentage rates at order header level, sales order item level, sales order
dimension level, delivery group level, scheduling group level, and allocation group level, and respectively
for the corresponding heart sizes. You can define release rules for individual grouping rules, for special
customers, or for a certain allocation type.
Example
The majority of your customers is satisfied with a delivery quota of 80% per ordered item. In this case you
first define a release rule, enter the value of 80% at sales order item level, and then enter the release rule
in the allocation type. If an order from a normal customer is selected, the system checks whether 80% of
the ordered items can be delivered on a quantity basis. If this is the case, the item is released and can be
delivered. At the same time you can define a release rule for special customers with higher requirements.
This rule will only release orders if, for example, the ordered quantities are 100% fulfilled. If an order from a
special customer is selected by the same allocation run as above, the system checks whether 100% of the
total quantity is available.
Further notes
You must assign a release rule to each allocation type. If you did not maintain release rules for certain
allocation groups and certain customers, the release rule in the allocation type is used as default.
Configure ARun Optimizer Type
Use
With ARun Optimizer, you can check and manually change the allocations made by allocation runs. The
settings in the ARun Optimzer type control the behavior of the ARun Optimizer.
Activities
Define the ARun Optimizer type and enter a descriptive text.
The following fields are mandatory for each ARun Optimizer type:
Mode
Selection program
Display group
Stock selection
The Mode determines whether the ARun Optimizer processes normal data or data from assignments
created by ARun in preview mode.
The Program field in the selection section can contain a generated selection report.
The Checks section contains different checks that are executed before the data is displayed in ARun
Optimizer. The results of these checks are displayed with traffic signals.
The Parallel Process section controls the work processes for release check and reallocation.
The Allocation Type field in the Proposals section controls reallocation.
The Stock Selection field controls stock selection during allocation.
The Release Rule field controls the release check.