Explaining Supply Assignment

The figure illustrates the position of the topic in the complete training scenario.

Your demand of wholesale and / or other channels exceeds your stock. You need to ensure the best usage of the existing stock by assigning it to the most important demand. You want to use various criteria to define which demand is considered to be "most important".

In cases where a full delivery is not possible you want the system to decide is the fulfillment rate is sufficient for a delivery.

Supply Assignment (ARun) ensures that supply is assigned to orders according to the changing requirements. In a supply shortage situation, supply assignment ensures an optimal assignment of supply to the open requirements and distributes available supply to the respective sales orders or stock transport orders (STO). Supply assignment offers options for minimizing losses due to inventory stock-outs by utilizing the visibility on the demand and supply situation and offers an automated release process for assigned items to which supply has been assigned and are ready for delivery.

The figure shows screenshots of the screens, in which the relevant settings for the ARun are made.

Supply Assignment (ARun) ensures that supply is assigned to orders according to the changing requirements.

Supply Assignment is part of the aATP portfolio where it is performed during BOP. It can be run with or without a preceding reATP step in BOP.

Supply assignment can be run before delivery of stock by setting the ARun relevancy in material master data.

Relevant customizing is maintained in IMG → Cross-Application Components → Advanced Available-to-Promise (aATP) → Supply Assignment (ARun).

The assignment process can be executed in the following ways:

1. In Backorder Processing (BOP), then generally followed by a release check in ITA. These two steps will typically be executed in background jobs. In this scenario the following is executed by the system:

   • The supply assignment as such creates a fix link between a demand element and a supply element. This link is written to a table and ensures the supply will not be used to fulfill other demand.

   • The release check validates the actual supply assignment quantities vs. requirement quantities to decide if an OBD should be created or not.

2. Manually in the Insight to Action tool.
3. Using immediate assignment process during document creation.

Fashion contracts can undergo supply assignment. If a call-off order is created with reference to an assigned contract the ARun status will get copied.

Demand can be assigned to future stock like POs. Status is hard-coded to R. This assignment will generally be kept when an inbound delivery / ASN (advanced shipping notification) is created for this PO. When a goods receipt is posted for this the status will again be kept ensuring the immediate availability of the stock to fulfill the demand.

Main MSO document behavior:

• Main MSO document is not applicable for supply assignment

• Main MSO document can inherit supply assignment if created with reference to an assigned contract

• Main MSO is not relevant for delivery. Assignment status can only be R – Reserve

• Even if ATP confirms additional referenced quantity, immediate assignment will not be triggered

Child document behavior:

• Child SO can be assigned through BOP, ITA and immediate assignment

• The assigned quantities in the Main MSO document are transferred to the Child SO document

• Child SO are applicable for delivery, assignment status is determined by the release checks

During configuration of the BOP variant you can select if the resulting assignments will be relevant for a release check.

You have the following options:

Inbound delivery for outbound delivery (IFO) assignment is a goods flow-through process in which the inbound goods are directly used for creating outbound shipping orders, eliminating the need to store them in the warehouse.

You can create outbound delivery for sales orders (SO) or stock transport orders (STO) which are assigned against inbound deliveries using the ARun Insight to Action (ARUNITA) tool. You can manually identify the assignments and move them into a new IFO Assignment status (C). Once the status is set to C, the outbound deliveries can be created.

IFO process allows you to map the outbound delivery with the inbound stocks in advance. Without IFO process, outbound delivery can only be created using assignments with physical stocks which are in Ready for Delivery (F) status.

• Articles/materials must be non-batch managed or batch managed and where the Supply Assignment (ARUN) does not assign the batches.

• Only assignments with inbound deliveries are applicable for IFO assignment.

• Only sales order, Stock transport order, and Free of Charge order are supported.

• IFO process is supported only in normal mode.

• Outbound delivery is possible with inbound delivery in sales order/stock transport order/Free of charge orders by setting the status to IFO Assignment (C) through ARUNITA. If you have order that is assigned to an inbound delivery, change the status from On Reservation (R) to IFO Assignment (C) using IFO button in ARUNITA tool. This allows follow on deliveries to be created for that order.

• Un-assignment rules remain the same when order is in C status.

• Once Outbound deliveries are created from Orders with C status, then the supply assignment fields of assigned inbound delivery cannot be changed or reduced below the delivered quantity.

• If you have integrated SAP ERP systems with SAP EWM systems, then the inbound delivery reference of the outbound delivery is sent to the SAP EWM system when the delivery is complete.

The figure shows a screenshot of the BOP Monitor SAP Fiori App, which illustrates the supply assignment results.

Features of the Supply Demand Overview (Detailed Analysis) app:

• Enables the end user to visualize, and analyze the Overall Supply , Overall

• Demand and the Supply-Demand Assignment situation based on

• Pre-Configured Steps and KPIs.

Supply Demand Overview (Flexible Analysis) app:

• The User can select the dimensions (such as Sales Organization, Plant,

• Material, Company Code, Customer Group, etc. ) and

• Measures (such as Open Demand Quantity, Open Supply Quantity,

• Confirmed Quantity, Assigned Quantity, Delivered Quantity, etc.) and proceed with analysis.

Supply assignment can be executed in different modes:

• The normal mode can use warehouse stock, Pos, ASNs and production orders as supply and typically this mode will be chosen as a preparation step for outbound delivery creation.

• The preview mode can also use purchase requisitions and planned orders as supply and typically this mode will be used as an outlook to evaluate how well demand will be covered on a longer time horizon.

• BOP always allows for execution in simulation mode. The results can be stored so that they can be evaluated and compared.

The figure illustrates the possible supply assignment specific settings in the BOP variant.

During the assign action, ATP scheduling logic is used to assign the stock if no specific stock sorting rule is maintained for ARun.

However, if the sorting is maintained it will replace the generic ATP logic. You can choose sorting criteria from the drop down list and combine them if necessary. In the picture sorting is performed based on the stock type. For batch stock you could sort in a second step by the shelf life expiration date.

Use the transaction ARUN_STKSORT.

ITA performs release checks in background mode and thus prepares the outbound delivery process. ITA can also mass change existing ARun statuses and provides the toolset for manual changes.

Release checks are performed using the ITA Tool in background mode.

You have to enter a default release rule that will be used for the selected requirements.

You can choose from four options for the determination logic of the release rule:

• Use the default rule always.
• 1st from sales order, 2nd default.
• 1st from determination, 2nd default.
• 1st from sales order, 2nd determination, 3rd default.

The calculationmethod can either consider already failed quantities or include all quantities.

The calculation base can either be the (ATP-)confirmed quantity or the requested quantity.

Transactions are:

• ARUNITA - Insight to Action Tool.
• ARUN_ITAR - Maintain Release Rules for Insight to Action.
• ARUN_ITARD - Determine Release Rules for Insight to Action.

The figure shows a screenshot, illustrating the screen to maintain the selection criteria.

Transaction: ARUNITA - Insight to Action Tool

The release rule determines if an allocation is considered a success. Checks can be performed on various levels of the documents:

• PSST Group (SO only)
• Document Header
• Delivery Group (SO only)
• Generic Materials
• Material
• Item Materia Availability Date

Transaction: ARUN_ITAR - Maintain Release Rules for Insight to Action.

The figure illustrates an example of an release rule.

The figure illustrates the possible manual actions.

In background mode update features are available to change larger selections of existing assignments:

• Unassign will delete supply assignments
• Release will change any of the selected ARun statuses (O, H, R) into either status H or status F
• Block will change any of selected statuses H and F into either R or H
• Email Exceptions will send notifications resulting from exceptions which have been identified by an exception rule

Transaction name: ARUNITA - Insight to Action Tool

Starting the tool for either displaying results or to manual change results uses the same selection criteria.

In the upper part of the screen more general selections are performed:

• Assignment run mode
• Orders with exceptions/unassigned
• SOs and/or STOs
• Stock types (in case manual supply assignment will be done)

In the lower part detailed selection criteria are available.

Transaction names:

• ARUNITA - Insight to Action Tool
• ARUN_ITAH - Maintain Hierarchy Levels for Insight to Action

The graphic shows the definition of drill down levels on the left-hand side. In this example both demand and supply are organized in four levels.

The result is displayed in the picture on the right-hand side.

It is always possible to display the result of selection in a flat view (i.e. in a line by line display) by pressing the corresponding button.

Transaction names:

• ARUN_ITAH - Maintain Hierarchy Levels for Insight to Action
• ARUNITA - Insight to Action Tool

The result screen displays three items of a sales order which were assigned during a BOP execution and are therefore in status O.

Note that the screen is in change mode and therefore the change options are displayed in the menu bar:

• Assign will perform supply assignment for selected items
• Unassign will undo assignments
• Release can change statuses O, R and H into F or H
• Block can change statuses F and H into R or H
• Release Check offers all levels of the release check rule as in background execution
• Create Deliveries will create outbound delivery for selected items

The graphic displays the details of three ITA features:

Assign

Allows to select the kind of supply (physical / future) that can be uses to fulfil the selected demand. Detailed selection by storage location, future document number or batch number is supported. If multiple supplies are selected the stock sort rule can decide in which sequence the supply is assigned. It is possible to assign by a delta quantity or percentage. The 100% in the screenshot will lead to full assignment if enough supply is available.

Unassign

Removes assignments. The user can choose how much will be unassigned. The 50% in the screenshot will remove half of the assigned quantity of each selected item.

Release Status To

Allows to change already existing assignment statuses O, R and H into F or H. The settings in the screenshot will change all (100%) selected items in status O into status H.

You can define an exception rule using the Maintain Exceptions for Insight to Action (ARUN_ITAE) transaction.

Exceptions can be deviation between delivery dates and/or quantities of orders (such as sales orders, stock transport orders, purchase orders, and so on).

You can define an exception rule for deviations that occur in dates using the comparison operators. For example, an exception can be created if the delivery date of the purchase order is beyond the delivery date of a sales order.

A sales order is assigned using a purchase order. If you want an exception to occur when the requested delivery date of a purchase order is greater than the confirmed delivery date of the sales order, then you should define an exception rule for this scenario.

You can define an exception rule for deviations that occur in quantities using the comparison operators. For example, an exception can be created if assigned quantity is less than the requirement quantity or the assigned quantity is less than confirmed quantity.

Transaction MD04P is enhanced to show fashion specific information. This includes supply assignment statuses. The screenshot shows a sales order which has been assigned in status F to a batch with the displayed stock segment. MD04P can be executed with a generic material therefore the variant of the material is also displayed.

This report can be used to drop open requirements of sales order and stock transfer orders for ARun relevant materials/articles only.

The report will drop open requirements for partially assigned/non-assigned order items.

Non-assigned order items will be completely rejected with the specified rejection code.

For partially assigned order items, a new item is created with rejected open quantities and rejection code

Selection logs will show orders which were locked and couldn't be processed

Execution logs will show order items which were successfully dropped and order items which couldn't be dropped due to specified reason

Transaction name: ARUN_DROP_REQ - Drop Open Requirements

Whenever there are changes in requirement or stock quantities this may result in the need of deleting existing allocations.

Examples:

1. A sales order is completely allocated. The customers inform that some materials are not wanted any more.
2. A purchase order has been allocated to several sales orders as future stock. The vendor informs about a short shipment which will also be delayed.
3. Stock is to be posted from unrestricted to blocked stock because it is damaged.
4. During the picking of an outbound delivery the necessary stock can not be found and a short-shipment has to be created.

In case 1. it is sufficient to just de-allocate the quantities during removal of Materials

In case 2. it has to be decided if the purchase order is still arriving early enough to fulfill the sales orders. If yes it has to be decided which sales orders are to be de-allocated.

In case 3. it has to be decided which sales orders are to be de-allocated.

In case 4. automatic de-allocation from the effected sales order can be set up. A sorting rule is not required because an individual delivery/sales order is to be managed.

The above screenshot shows the set up for sales orders, similar screens exist for:

• Sales order
• STO
• Purchase Order
• GR
• GI

Customizing is maintained in: Cross-Application Components → Advanced Available-to-Promise (aATP) → Supply Assignment (ARun) → Cross-Applications.

In the example above the orders will be sorted by delivery priority (LPRIO) and by order date (AUDAT) the settings in column "priority" indicate that demand will be first sorted by LPRIO and if multiple documents exist with the same delivery priority they will be sorted by order date. The checkbox next to this indicated descending order. I.e. orders with lowest priority and latest order date will be sorted to the top of this list and will be un-assigned first.

In the case of automatic un-assignment for the sales document handling the rules can be linked per sales document and per sales area

Customizing is maintained in: Cross-Application Components → Advanced Available-to-Promise (aATP) → Supply Assignment (ARun) → Cross-Applications.

The table overview shows which checks can be used per object and by which organizational level the can be linked to the various object.

The general idea of supply assignment is to guarantee supply availability for selected demand.

The Subcontracting cockpit is enhanced to support assignment, un-assignment and delivery creation operations for the subcontracting purchase order components:

• Assignment can be done for batch managed components with ARun fixing the batches.

• Assignments can be done against physical stocks only. Future / incoming supplies are not assigned here.