The most important settings for product availability check (PAC) in SAP S/4HANA are as follows.
For the PAC, the checking group along with the checking rule/business event determine the scope of check to be used for determining material availability, as shown in this figure.
The combination of checking rule and checking group determine the scope of the availability check.
Companies use different strategies for confirming orders in different business scenarios. In certain cases, only available stock and firmed receipts are considered for confirming the orders, whereas certain businesses use planned orders or RLT to provide expected delivery dates for the requirements to their customers. The Scope of Availability Check screen helps businesses define which demand and supply elements should take part in the ATP check.
As shown in the next figure, the Scope of Availability Check screen is divided into several sections. Some of the important sections are described below.
In this section, you can define what stock should be considered during PAC along with the available stock in the plant or warehouse. The different types of stock that can be selected are safety stock, stock in transfer (incoming stock), quality inspection stock, blocked stock, and restricted-use stock.
If the business wants to confirm the orders based on future supplies (i.e., planned orders or production orders for in-house manufacturing, or purchase requisitions or purchase orders for internal/external procurement), that can be defined in this section.
In this section, you can define for which of the demand elements PAC should be active, including sales documents (i.e., sales orders), deliveries, and material reservations.
When there are no adequate supplies available to fulfill the demand, you can indicate here if the order should be confirmed based on the RLT maintained in the material master.
During PAC, you can consider SUP, check at the storage location, or stock at the subcontractor location.
This enables the quantity distribution feature.
Editor’s note: This post has been adapted from a section of the book Available-to-Promise with SAP S/4HANA by Sujeet Acharya, Sandeep Mandhana, and Jibi Joseph Vadakayil.