Show TOC

 Feasibility Check

Use

The feasibility check is a production-related check, which you can use to check whether customer requirements from sales scheduling agreement items are feasible; in other words, whether they can be met.

Therefore, the feasibility check is carried out on the basis of the current requested quantities ( due delivery schedule) in order to check whether new customer requests can be met.

If the result of the feasibility check is positive, the system generates full (matching) confirmations automatically.

If the result of the feasibility check is negative, then the system does not generate a confirmation and the planner has to confirm the requirements from the sales scheduling agreement items manually.

For more information see Confirmations .

If sales scheduling agreements and sales orders for a product exist, these requirements are taken into account in the feasibility check.

A confirmation is only possible for requirements for sales scheduling agreement items.

Sales orders can only be confirmed within the ATP.

The feasibility check is the generic term for a range of possible checks based on heuristics.

For more information, see Heuristics and Heuristics for Sales Scheduling Agreement Processing .

You can create your own checks for the feasibility check without making any modifications.

For more information see Create Heuristics with Your Own Algorithms

You can check the availability of requirements from sales scheduling agreement items not only by using the feasibility check, but also by using the Global ATP Check (check method product availability check).

Prerequisites

You have made the necessary settings in Customizing for Advanced Planning and Optimization (SAP APO),under Supply Chain PlanningDelivery Schedule Processing for Sales Scheduling Agreement.

See also Prerequisites for the Sales Scheduling Agreement

Features

In the SAP APO system the following checks are delivered:

Fully confirm without check (Heuristic SAP_CDS_F01)

This means that the complete requirements are regarded as feasible without a check being carried out.

Matching confirmations are generated for all requirements from sales scheduling agreement items.

Days’ supply check (Heuristic SAP_CDS_F02)

The quantities and dates are only fully confirmed if the feasibility can be guaranteed on the basis of the days’ supply check.

The system calculates the actual days’ supply for the product in question and compares it with the minimum days’ supply defined in Customizing.

Feasibility OK => Confirmation

If the actual days’ supply is greater than or equal to the minimum days’ supply defined (minimum days’ supply error in the days’ supply type) then the current product requirements can definitely be covered and matching confirmations are generated for all requirements from sales scheduling agreement items.

You can define what stocks, receipts and requirements are included in the calculation of the actual days’ supply in the days’ supply type.

Using the customer exit APOCV001 you can define that the replenishment lead time from the product master is used for the minimum days’ supply.

Feasibility OK => No confirmation

If the actual days’ supply is less than the minimum days’ supply defined (minimum days’ supply error in the days’ supply type), the system does not generate any confirmations and the planner must manually reprocess the requirements from the sales scheduling agreement items.

Product heuristic with days’ supply check (Heuristic SAP_CDS_F03)

This means that the system first carries out the product heuristic saved in the location product master and then a days’ supply check.

The quantities and dates are only fully confirmed if the feasibility can be guaranteed on the basis of the days’ supply check.

Taken Current Status and Planning File Entry for Feasibility Check into Account

For all checks, you can define that the feasibility check is only carried out if:

All sales scheduling agreement items for a product have an admissible current status and which statuses you want to allow

The product has a Planning File Entry for the Admissibility Check.

This means that only those products for which an MRP-relevant change has taken place since the last feasibility check are checked.

Activities

The feasibility check can be carried out:

Directly after inbound processing(as a part of inbound processing in the background), if SA releases are received by Electronic Data Interchange (EDI) or are manually created in master data maintenance.

Check feasibility in interactive production planning (in the dialog).

You access the feasibility check as follows:

In the Product View: Periodic , choose Feasibility Check in the context menu for Sales Scheduling Agreement Processing.

The system taken into account the control profile settings and checks the feasibility of a sales scheduling agreement.

In the menu choose (Interactive) PlanningHeuristics.

You can select one of the heuristic for the assigned heuristic profile. This heuristic is then carried out for all selected products.

Variable Heuristic

You can select one of the heuristic for the assigned heuristic profile. This heuristic is then carried out for all selected products.

Check Feasibility in Automated Production Planning

In the production planning run you can define that the system should carry out multiple heuristics, one after the other.

Choose Production PlanningAutomated Production Planning and Optimization Production Planning Run or Production Planning Run in the Background .

Enter the heuristic you want to use for the object Product (4) and enter additional selection criteria, such as product or location.

You can look at the logs for the production planning run under Production PlanningReportingLogs

In the Product View or the Product Planning Table you can define how detailed the log should be by choosing SettingsPlanning Log.

See Production Planning Run and Production Planning Run in the Background .

Result

The result of the feasibility check controls whether or not a confirmation is generated.

Feasibility OK => Confirmation

The system generates a full (matching) confirmation. The current status of the scheduling agreement item changes to 40 – Full Confirmation.

If you want, the confirmation can be sent to the customer by EDI.

You can use the planning procedure in the location-dependent product master to define for customer requirements whether the requirement quantity or the confirmed quantity is pegging-relevant.

If you carry out planning on the basis of the requested quantity, then customer requirements are planning-relevant when you receive the SA release.

If you carry out planning on the basis of the confirmed quantity, then customer requirements only become planning-relevant when they have been confirmed, regardless of whether this confirmation has been sent to the customer or not.

See Determine the Pegging-Relevant Quantity for Customer Requirements

Feasibility OK => No confirmation

The system does not generate a confirmation.

A distinction is made between the following cases:

If the feasibility check is carried out in interactive production planning then the current status of the sales scheduling agreement item does not change.

If the feasibility check is carried out in automated production planning or directly after inbound processing then the current status of the sales scheduling agreement item changes to 31 – Feasibility not OK .

If the feasibility check was not successful then the last confirmation sent is valid and the planner is informed of the result of check by means of an alert.

For more information, see Alert Monitor for Sales Scheduling Agreement and the SAP Library: Supply Chain Monitoring under Alert Monitor

The planner must manually process these requirements. When the planner has checked the availability, he can confirm this manually. This confirmation can either be compliant (full) or non-compliant (partial). The current status of the scheduling agreement item changes accordingly. If required, the confirmation can be sent to the customer by EDI.

If the planner confirms too much or too little then he or she can be informed of under- and over-confirmation situations by means of an alert.

See Alert Monitor for the Sales Scheduling Agreement