Availability Check with ATP Logic or Against Planning-reg

[Former Member]

hi gurus,

what is the difference between

Availability Check with ATP Logic

or

Against Planning

means can we have two types of check?

how can we do against planning?

rajendra

[Former Member]

Given customised solution

[Former Member]

Hi,

Check the checking group. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Availability Check - Availability Check with ATP Logic or Against Planning - Define Checking Groups.

The value A must be set for the TotalSales and TotalDlvReqs fields.

The Block QtRq indicator must be set in both systems. Otherwise, the unlocking routines are not called in SAP APO, and the temporary quantity assignments remain in the SAP APO system.

Specify the default value for the checking group. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Availability Check - Availability Check with ATP Logic or Against Planning - Define Checking Groups Default Value.

Make sure that there is a checking group set for individual requirements in the material master.

Check the assignment of schedule line categories to the item category, which the system proposes automatically when it creates the item. In Customizing for Sales and Distribution under Sales - Sales Documents - Schedule Lines - Assign Schedule Line Categories.

Check the assigned schedule line category. In Customizing for Sales and Distribution under Sales - Sales Documents - Schedule Lines - Define Schedule Line Categories.

Define a requirements class of your own if required. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Transfer of Requirements - Define Requirements Classes.

Define your own requirements type if required, and assign this to the requirements class. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Transfer of Requirements - Define Requirements Types.

If required, specify determination of the requirements type using the transaction. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Transfer of Requirements - Determination of Requirement Types Using Transaction.

Check the control for the availability check. In Customizing for Sales and Distribution choose Basic Functions - Availability Check and Transfer of Requirements - Availability Check - Availability Check with ATP Logic or Against Planning - Carry Out Control for Availability Check.

Define a strategy of your own if required. In Customizing for Production choose Material Requirements Planning - Master Data - Independent Requirements Parameters - Planning Strategy- Define Strategy.

regards,

Siddharth.

[Former Member]

Hi Prasad,

I think it would not possible to maintain to procedures at the same time for single material.

availability check against ATP is allowcation of material based on certain rules like which we set under basic functions - AC.

In this process you cant allocate the stock for specific customer.

In case of AC against planning you can allocate each and every material along with qty to specific customers.

Please see the configuration required for planning.

1. Allocation Procedure (OV1Z) the product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation.

2. Allocation Object (OV2Z) the allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material

3. Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed

4. Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check.

5. Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials

6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant.

7. Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant

8. Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified.

9. Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy

10. Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors

11. Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered

12. List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).

Reward if helpful.

Regards

Raj