Outlining aATP with Check Against Allocation

Objective

After completing this lesson, you will be able to outline aATP with check against allocation

Advanced Available-to-Promise with Check Against Allocation

Elements of an Allocation Process

Product Allocation in aATP

Being able to deliver the required quantity of a material to the customer at the requested time demands precise planning and control mechanisms. Unpredictable problems, such as breakdowns in production or increased demand, can lead to critical situations in order processing and must be avoided wherever possible.

In advanced Available-to-Promise (aATP) in SAP S/4HANA, you can use Product Allocation (PAL) to avoid critical situations in demand and procurement by allocating materials in short supply to, for example, specific regions and customers for a specific time period. This can help avoid the situation whereby, for example, the entire available quantity of a material in short supply is allocated to a single customer, thereby making it impossible for you to confirm subsequent order requirements for the same material from other customers.

However, the functionality of an allocation check exists in earlier releases of SAP ERP, and so is not new.

Diagram illustrating the elements of an allocation process.

Unfortunately, the data modeling process in SAP ERP has been complex and included significant limitations.

In SAP ERP the allocation process was based on the data model in Logistic Information System (LIS).

LIS has the following limitations:

  • LIS operates on redundant data. Every business transaction not only updates the business documents, but also pre-aggregated data in LIS.

    Performance suffers, locking conflicts might occur, and memory is wasted. Whether or not LIS causes locking conflicts depends on the frequency of change of the aggregated information. If several transactions want to update the same aggregated dataset in parallel, then you will experience a locking conflict.

  • LIS operates on pre-aggregated data. It is not possible to drill down into the individual business documents. Multi-dimensional reporting (aka Slicing and dicing) is only possible for dimensions provided in the pre-aggregated data.

  • LIS uses an old UI technology making multi-dimensional reporting clumsy.

  • LIS only supports material numbers with up to 30 characters.

Therefore a new solution was requested.

What is the main idea behind the check against allocation?

Product allocation enables you to control the confirmation behavior of the advanced available-to-promise (aATP) check by specifying restrictions. It is usually combined with the product availability check. The table Features of Product Allocation provides an overview of its main features and advantages.

Features of Product Allocation

FeaturesAdvantages
  • Planning quantity restrictions.

  • Flexible aggregation level at which the restrictions are planned.

  • By defining periods, time-related rationing is possible.

  • Can determine the requested quantity from another period and if previous or subsequent periods are considered.

Combination of restrictions:

  • Logical AND

  • Logical OR

Ensures a fair distribution of goods in short supply (not "first come first served").

In defining the restrictions in product allocation, you have flexibility regarding the characteristics that you can use. You can also combine several restrictions. For products where there is a bottleneck (for example, in stock or production), you can use these restrictions to ensure that goods in short supply are correctly distributed.

Definition of Product Allocation

Demand and supply graph shown over a four day period. Supply cannot meet demand for two of the days. To avoid hoarding, supply needs to be rationed according to specific criteria.

Competitive order processing—which aims to deliver the requested quantity to the customer at the requested time—demands precise planning and control mechanisms. Unpredictable problems, such as drops in production or increased demand, can lead to critical situations in order processing. In order processing, they must be identified and controlled early on.

Product allocation provides this sort of control. It enables your company to avoid critical situations in demand and procurement. It must be possible to have both an equal allocation of products that are in short supply. It must also be possible to have a speedy reaction to bottlenecks or changing market situations.

You can use product allocation to allocate products on a period-specific basis—for example, for specific customers or regions. If you use product allocation in situations in which a product is in short supply, you can avoid allocating the entire available quantity to the first customer. Allocating all of the quantity to the first customer would either delay the confirmation of subsequent sales orders or make confirmation impossible.

The product allocation function allows you to manage the supply of scarce products to customers so that each customer receives an allocated amount.

A product allocation check can act as a secondary check against the quantity requested in the sales order. First, a basic ATP check can be performed against stock and receipts, possibly resulting in a lower confirmed quantity due to insufficient stock. This confirmed quantity can be checked against the product allocation quota, possibly further reducing the confirmed quantity.

Check Against Product Allocations

A sales order graph showing quantity versus time.

Product allocation encompasses internal product allocations for sales organizations and distribution channels, as well as for external customer groups and specific customers. For example, the control process for product allocations enables the user to manage product allocations at specific product levels. It also enables management allocations for different product groups.

During the overall constraint period, the system takes into account the different control phases that exist for product allocations. There might be phases without constraints. There might be a change over time in the reason for the check against product allocations.

Discrete Product Allocation

If you use discrete product allocation, only single-level product allocation is possible.

Cumulative Product Allocation

Graph showing the cumulative product allocation over a five month period from March to July. The current period is April and shows available production allocation as 750 pieces.

If you set the Cumulative indicator in the Customizing activity Maintain Product Allocation Procedure, then the system uses the cumulative product allocation method.

Through the cumulative product allocation method, you can use the following:

  • Product allocation steps: You can define multiple product allocation steps with different product allocation groups.

  • A consumption period: You can define a number of past and future periods to be used as valid consumption periods.

    The number of past periods identifies the number of periods before the product allocation date (taken from the order) that can be used for calculating unused product allocations. The unused product allocation quantities of these past periods are then cumulated before product allocation is checked for the current period. The number of future periods identifies the number of periods after the product allocation date. It can be used to calculate future product allocations. If the requested quantity is not confirmed within the future periods, then it remains unconfirmed.

Product Allocation Consumption Period

Graph showing the product allocation over a five month consumption period from March to July. An order of 100 pieces has a confirmed quantity of 80 pieces and an actual order quantity of 20 pieces.

If you are using cumulative product allocation, then you can define a consumption period for each product allocation group. The consumption period defines how many past and future periods are accounted for in the check against product allocations. Unused product allocation quantities from past periods are cumulated. Future periods can only be used for creating a delivery proposal consisting of multiple partial deliveries.

Product Allocation Procedure

Multilevel Product Allocations

Product allocation can be single-level or multilevel.

Single-Level Versus multilevel Product Allocation

  • Single-level product allocation uses a sequence group which is linked to the Sales sequent goups. Sales sequent groups can contain multiple sequence groups. The allocation object is linked to the sequence groups.

Diagram showing the Multilevel Product Allocation - Multiple Sequences for a confirmed quantity of 65 pieces.

For an allocation check using multiple sequence groups (sales and capacity) the system calculates the sum of the allocation in the Sales Sequence Group and in the Capacity Sequence Group and confirms the minimum of both.

Therefore Sequence Groups are linked with a logical "AND".

Multilevel Product Allocation with the AND Link

Diagram showing the Multilevel Product Allocation with the AND Link for a confirmed quantity of 50 pieces.

Multilevel steps of product allocation groups form product allocation procedures. When a new order is checked, each step in the procedure–a step which is a product allocation group—is evaluated. The result of the preceding step is applied to the subsequent step. The final result of the product allocation check in the product allocation procedure is calculated from a logical AND link proposed by each of the product allocation groups.

For example, in the figure Product Allocation: Multilevel with AND Link, the smallest quantity (50 pieces) is determined by the product allocation group in regards to the characteristics combinations of the customer.

However, in SAP APO, you can use a sequence of product allocation procedures to confirm additional quantities that have been planned in a different planning area. Product allocation procedures containing more than one allocation group are only possible for a cumulated check against product allocations.

Multilevel Product Allocation with the OR Link

Setup Structure of Allocation in SAP S/4HANA

Allocation – a Prime Example for Simplification

An example of Simplification. The image on the left shows how more than 30 transactions were necessary to maintain product allocation configuration and planning data in the SAP ERP system. The image on the right shows how in SAP S/4HANA, only 4 apps are necessary.

The new setup of allocation in SAP S/4HANA is a prime example of Simplification

In the SAP ERP system, more than 30 transactions were necessary to maintain product allocation configuration and planning data, most of them to execute in the customizing (IMG). An extension of the characteristics catalog required programming skills.

In SAP S/4HANA, only 4 apps are necessary. There is no need for the generation of database tables, database access, or other program artifacts.

Product Allocation Object

App. 1: Product Allocation Object

The product allocation object is the main business object in the product allocation functionality and describes the business reason (for example, fair share, prioritized share, or ranked share of a resource in limited supply, such as stock) for using product allocation. The product allocation object is used to specify the product allocation schema and contains data relating to:

  • Periodicity

  • Characteristic combinations and their hierarchy

  • Unit of measure of the planned allocation quantity

  • Requested date type used for availability checks against the product allocation object

  • Can a collective allocation be set up manually or automatically if it is not required to explicitly maintain characteristic values during the maintenance of the planning data

Product Allocation Object screen. The product allocation object is the main business object, and describes the business reason (such as fair share, prioritized share or ranked share of a resource in limited supply, such as stock.

The product allocation object also contains planning data consisting of the following:

  • The characteristic value combinations (CVCs), which are either made up of explicitly specified characteristic values or, if collective CVCs are being used, a combination of explicit characteristic values and collective values represented by #.

  • The time series which is made up of time periods with planned allocation quantity. Each time series is assigned to a CVC.

Manage Product Allocation Planning Data

App. 2: Manage Product Allocation Planning Data (1)

In the Manage Product Allocation Planning Data app the system can now move planned allocation quantities and corresponding assigned quantities.

Based on the selected Product Allocation Object, you can interactively change, delete or re-assign quantities from one CVC to other CVCs.

Product Allocation. Automatically reorganize planning and assignment data. For example, if you set the marked CVC to Inactive, the system queries if the quantities should be transferred to the collective allocation.

Manage Product Allocation Sequence

App. 3: Manage Product Allocation Sequence

Assign Product to Product Allocation

App. 4: Assign Product to Product AllocationAssign Product to Product Allocation screen.

The fourth app is responsible to create the link between the product and the maintained planning data above:

App. Product Allocation Overview

Last but not least, the whole process can be reviewed by using the last app: Product Allocation Overview.

Product Allocation Overview. New apps for analyzing and understanding the product allocation situation.

This app delivers you the most important information about the allocation situation at a glance:

Product Allocation Overview application.

App. Product Allocation Overview as a Cockpit

From this "cockpit" it is possible to navigate in several detail views without navigating away from the tile:

Monitor Product Allocation Periods, Monitor Product Allocation Characteristic Value Combinations, and Monitor Product Allocation Order Items apps can be opened from the Product Allocation Overview application.

Apply Allocation Check During Sales Order Processing

Multiple Allocation Objects During Sales Order Processing

Multiple sequence constraints in a sequence group can be used simultaneously as sources of supply to ensure that a minimum confirmation is possible for all of the constraints in the sequence group when the required quantity in an order document is checked against the sequence group during an availability check.

If a sequence group contains more than one valid constraint, the constraints are checked and automatically considered to be equal. From the check results of all constraints, a common confirmation valid for all constraints is calculated (minimum possible for all constraints). This means the availability check against product allocation confirms the latest date on which quantity can be confirmed by all constraints in the sequence group. Before availability is checked for an order document, the group validity for the requirement is determined by the system: all valid constraints and the consumption ranges defined for each constraint are aligned into a common validity range for the whole group. Each constraint is then checked by considering this group validity, meaning that available quantities of a constraint which lie outside the group validity will not be consumed and cannot be used to confirm required quantity.

Multiple Allocation - Facts. Each product allocation object is checked and the results are combined into one final confirmation which is the minimum of all determined confirmations. Maintenance just adds multiple overlapping sequence constraints within one sequence group of a sequence. It is possible to combine sequence constraints with different check date time types and periodicities.

The usage of multiple allocation will be influenced on one hand by the allocation quantities, and on the other hand by the setting of the consumption overlapping parameter in the sequence group. If this parameter is set to Yes, then only quantities are taken into account which are available in the same period for all constraints. A common confirmation is determined which fulfills all constraints.

The usage of Multiple Allocation Objects with different settings for the overlapping consumption parameters is explained in the following simplified example:

Multiple Allocation - Initial Situation graphs. Constraint 1 and Constraint 2 consumption levels over time.

There are two constraints in different periods (weeks). For these two constraints, different figures for allocation are maintained. Therefore only an overlapping quantity of 20 pieces is planned for the week starting November 5th. Depending on the settings of the consumption parameter this leads to the following results:

Align Confirmation Dates Only graphs. Constraint 1 and Constraint 2 consumption levels over time.

Due to a possible backward consumption of two weeks constraint 1 leads to a confirmation of 45 pieces on November 5th, which can be also covered by constraint 2. This leads to an overall confirmation of 45 pieces on November 5th.

Consume Overlapping Quantity Only graphs. Constraint 1 and Constraint 2 consumption levels over time.

The same scenario but with the usage of the consumption method consume overlapping quantity only leads to the result that the quantity from previous periods of the constraint 1 could not longer be taken into account. The confirmation quantity would be reduced to 20 pieces for November 5th.

Consume Overlapping Quantity Only - Result graphs. Constraint 1 and Constraint 2 consumption levels over time.

This logic can also be used for multiple allocation objects maintained in different period types with one allocation check.

Consume Overlapping Quantity Only graphs. Constraint 1 and Constraint 2 consumption levels over time.

For the alignment of confirmation dates a backward consumption is possible. However the usage of Consume overlapping quantity only leads to the result that only the quantities in the overlapping period can be consumed.

Consume Overlapping Quantity Only graphs. Constraint 1 and Constraint 2 consumption levels over time.

Apply Multiple Allocation Checks During Sales Order Processing

Vertical Consumption Strategies

By maintaining different consumption parameters for the product allocation objects used in sequence constraints and by using the same product allocation object several times in different sequence constraints/groups, you can configure a sequence in which the same allocation object is checked multiple times with a different consumption strategy for available quantity.

Vertical Consumption Strategies - Facts. A vertical consumption strategy defines when and how product allocation alternatives (sequence groups) are checked.

This gives a lot of flexibility in defining how the allocation check consumes the product allocation objects. Doing so may increase the possibility of generating an on-time confirmation for an order requirement.

In the Manage Product Allocation Sequences app, you define a sequence which, in order to increase the possibility of generating an on-time confirmation, first searches periods which occur before the requested delivery date. Only if insufficient quantity is available in earlier time periods will the system continue to search in later time periods. The sequence contains four sequence groups as alternative sources of supply:

  • Two of the sequence groups use one product allocation object, PAO_1.

  • Two of the sequence groups use another product allocation object, PAO_2.

You define differing backward and forward consumption for each of the sequence groups as follows:

PrioritySequence GroupBackward ConsumptionForward ConsumptionAllocation Object
11020PAO_1
22020PAO_2
33002PAO_1
44002PAO_2

This setup can lead to the following result of an allocation check:

First the system executes an allocation check using the first product allocation object, PAO_1. This check will be executed based on the current period of the material availability date. In the case of insufficient allocation quantity, the check will be extended to the two upstream periods based on the settings regarding backward consumption.

In case of insufficient allocation also in these periods the system switches the product allocation object automatically and checks the second product allocation object, PAO_2, first in the current period, then taking into account the two upstream periods also for this product allocation object.

If the allocation is still insufficient then the sequence groups 30 and 40 will be relevant and the checks will be executed with a forward consumption of two periods.

Example 1 Strategy check alternatives backwards first. Product Allocation Object A and Product Allocation Object B showing request date within consumption range.

Therefore it is possible to build up complex strategies to support your business requirements.

Example 2 Strategy step-wise forward. Product Allocation Object A and Product Allocation Object B showing request date within consumption range.

Here you have the full flexibility to set up your own strategies and the system supports you in maximizing the on-time confirmation.

Apply Multiple Allocation Checks with Different Consumption Strategies

Management of Characteristic Catalogs

Characteristics correspond to the fields in the data model for sales and stock transport orders and are populated by values from the corresponding fields in the relevant business document. They are used to determine the matching characteristic value combination and its time series when an availability check against product allocation is run, against which the requirement item is then checked.

Manage characteristic catalogs used within different aATP applications.

When you create a new product allocation object, you select the characteristics for the product allocation object on the Select Characteristics dialog and maintain the hierarchy of the characteristics by defining an ordinal number for each characteristic.

Catalogs for different document types and different usages within ATP are displayed with the Manage Characteristic Catalogs screen.

The resulting combination of characteristics, their values and sequence, as well as the use of collective allocation, enable the system to identify the characteristic value combination which is used to check availability for a sales or stock transport order against product allocation.

Add or remove characteristics to/from mixed catalogs. These characteristics can be used in allocation checks for both document types (sales order and stock transport order).

A validation check can be executed on demand.

In the SAP Fiori app Manage Characteristic Catalogs it is possible to specify if an existence check for characteristic values shall be executed or not.

Manage Characteristic Catalog for Allocation Check

Log in to track your progress & complete quizzes