Availability Check with ATP Logic or Against Planning-reg
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
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
Similar Messages
-
Availablity check with ATP logic
Hi everybody
Can any one tell me where where we assign Checking rule (A - sales order) in availablity check.dear srikanth
please gothough this
TOR AND AVAILANBILITY CHECK
To confirm the quantities for a particular line item in the sales order on particular day system carried out transfer of requirements (TOR) & AVAILABILITY check, so has to confirm the quantity on particular day as system should know what are there requirement of the sale order and delivery with MRP then system carries out availability check function, to confirm the quantity on particular day. Depending upon the IMG setting system carries out availability check function based on 3 methods:
A) Availability Check with ATP logic or against planning:
In ATP logic systems ATP Qty while carrying out availability check function for
Particular line item (ATP qty=warehouse stock +planned receipts planned issues)
Planned Receipts: EX: - purchase requisitions, purchase orders, stock in transfer stock at inspection etc.
Planned Issues: - EX: - open sales order & open delivers
B) Availability check against product allocation:
Availability check can be carried out against product allocations in which system automatically restrict the user to confirm the quantity beyond reserved quantities per particular customer. EX:- Availability qty =100, existing orders=10,then system automatically distributes to items evenly to the sales order.
C) Rule based Availability check:
Rule based availability check can be carried out based on the business transaction.
EX: - For normal sales order system has to carry out availability check for special sales order ex: - cash sales and rush order systems need not to be carry out availability check,
In rule based availability check system in which system carried out Global availability to promise in all plants. In this check system transfers the requirements to APO system where GATP takes place and the result of the availability check transferred to R/3 system. This process takes place with the transaction code CIF(central inter face) inR/3.After carrying out availability check function system proposes(by using ATP logic) default values of ATP check result to the user in a dialog box, in which system gives the choice to the user to take the decision in contest of insufficient stock.
a) One time delivery:
If the user chooses one time delivery and the order Quantity is 100 units system confirms 50 units then systems automatically confirms as a zero. If the user saves the document with the zero confirm qty then system trace the sales order as aback order (V_RA), which can be confirmed later by RESCHEDULLING (V_V2).
b) Complete Delivery:
If order Qty=100, Availability stock = 50, system says that remaining can be given after one week. Then if the user selects this option then system push up existing confirmed qty to after one week and the total qty can be confirmed after one week only.
c) Delivery Proposal:
If order qty=100, system confirms 50, and remaining 50 can be confirmed after one week. If the user chooses this option then system confirms 50 Qty today allows the user to delivery 50 quantities today remaining 50 can be delivered after one week.
CONFIGURATION SETTINGS FOR TOR:
Define Requirement Class:
Path: Img  S&D  Basic functions  Availability Check & Transfer of requirements  Transfer of requirements  Define Requirement classes
Requirement classes control MRP, Requirement consumption, strategy, relevance for planned. It specifics whether the availability check & TOR to be Called out for transactions. Ex: Sales Order
It determines whether requirements relevant for MRP or not, the allocation indicator from the sales view which controls the settlement of customers requirements with planned independent requirements. It determines the item b to be settled as an availability heck. Assignment, the settlement profiles the results analysis key. The TOR and Availability check functions are globally controlled using the requirement class for all the Sales documents. The values from the Requirements class are transferred to scheduled the of the sales documents class are transferred to scheduled the of the sales document default values and can be over written there.
Define Requirements Classes:
Requirement class defines whether the system has to carry out availability check based on the STP Qty. Ex:
Define Requirement Types:
Here we define requirement type, Ex: and Assign to Requirement class that we defined in the promote step.
Determination of Requirement types using Transaction:
Requirement type is going to be determined for sales document by following a search strategy. .
First System checks strategy group in MRP3 view if it trend requirement type then system takes from it, otherwise.
It will go to MRP group in MRP1 view, otherwise
It will check to Material type, otherwise
It will go to item Category + MRP type, otherwise
It will go to Item category only, otherwise
Finally system determines the transaction b not relevant for TOR & Availability check.
Choose Item category TAN+MRP type PD=Requirement type =0
Define Procedure for each schedule the category:
Here we define respective schedule the category of the sales documents, whether an availability check and TOR should be carried out. This setting is relevant for sales documents only. It is fine tuning of availability check for sales documents TOR & Availability check function can be activated at sales order level those are proposed in to schedule line category level. If u wants to deactivate TOR availability check function at schedule the category level and want to deactivate at requirement class level it b impossible.
Ex: If u wants to check availability w/o transferring the requirement we can use it.
Choose schedule line category CP & Activate Availability check, requirement & Product Allocation
Block Quantity confirmation in delivery Blocks:-
When we transfer requirements to MRP then confirmed quantities is also reserved for confirmed sales documents, if transaction is blocked for delivery the reserved quantities are also blocked so that the conformed quantities cannot be used by any other purpose. So has to avoid this situation we can block the transfer of requirements(TOR) for delivery blocks, in this case requirements transferred to MRP but will not be reserved, that will be cleared once we save the documents then system shows confirmed qty as zero.
When we remove the delivery block then system automatically carries out availability check & confirms the qty.
A) Deliveries: Blocking region for sales Area:
Here we define blocking regions for TOR ex:-credit limits
B) Reasons for scope of delivery blocks: TOR. Block:
Ex: - 01 credit limits-check confirmation block.
Maintain Requirements for TOR:-
Here we can define our own requirement with the help of ABAPer for TOR
Ex: - a) 102- prevent reservation in the event of credit block
b) 102-purchase requisitions.
System doesnt create purchase requisitions for sales order line items if it has a credit limit.
Availability check:
Configuration setting:-
Availability check with ATP logic or against planning:-
A) Define checking group:
Checking group defines what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records
Individual requirement records: that means system creates requirement record for each S&D document.
Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:
Summarized requirement records for each day.
Summarized requirement records for each week
Define checking Action;
Here we define 01- daily requirement -B 02- Individual requirements -A
Where B-total record per day
A-single record per day
B) Define material Block for other users:
When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block
C) Define checking group default values:
Checking group is going to be determined depending upon the material type & plant.
-Go to new entries, specify material type, ex;-FERT
& plant = checking group of availability check: 02
D) Carry out for Availability check:
Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.
*Select checking group of availability check-02, checking rule=01
*Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check
*save it, exit.
E) Define procedure by Requirement class:
Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There settings automatically copied into define from of requirement class and vice versa.
*Choose requirement class: 041 & check availability check & TOR (requirement)
F) Define procedure for each schedule line category:
Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.
Ex: - if we want to implement availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR
G) Determine procedure for each Delivery Item category:
Here we switch on or switch off availability check functions of a delivery item category
*choose item category TAN. & specify the appropriate value.
H) Checking group for updating back orders:
Here we assign checking group to a plant that rule specifies for individual application, according to which the availability check is carried out;
I) Define Default settings:
Here we define the result of the availability check.
*Choose your sales Area, & check fixed dates& Qty options & specify D or E
Where: D- Dialog box in the case of shortages (one time delivery)
E- Dialog box in the shortages (delivery proposal).
rewards if it helps
siva -
hello friends,
please send any body "Availability check with atp" configaration steps.
mail id "[email protected]"hello friends,
please send any body "Availability check with atp" configaration steps.
mail id "[email protected]" -
Availability check with Purchase Requisition / Production Or
Hi,
I want to configure the availability check in such a way that, system should first check the stock available. If there is no stock system should generate the Purchase requisition or Production order.
Can you tell me the solution on the same.
Regards
RahulHi,
We have the similar requirement & achieved through development.
Eg: M1- stock = 55 ea
order qtty M1- 100
system confirms for 55 ea & remaining qtty, seperate line item will be created with TAB item category i.e. 45 ea.
Used FM: AVAILABILITY_CHECK ( MV45AFZZ) & BAPI_MATERIAL_AVAILABILITY to find the ATP stock in Include:MV45AFZB
Regards,
Reazuddin MD -
Availability check with storage location
Hi experts,
I have one problem in availability check.I will explain in steps.
There are two storage locations
RMMU: main storage location where GR will happen from vendor.
WPMU:WIP storage location from where material will be issued to production order.
A is fert material.
B is bom item (raw material) and in material master maintained WPMU production storage location.
Now after sales order(100 nos) and after mrp run we will get the Planned order for 100 nos and Purchase requisition for 100 nos for material B.Now we will do the GR for "B" in Storage location RMMU.
Now we will create the Production order for ''A''.After availability check in production order ,it will show the material availability.
The problem is that we maintained the prod.storage location as "WPMU''and in that no stock is there.It is in RMMU.Still it is giving availability of material.
Requirement is it check the stock in prod.storage location i.e. WPMU
Please throw some light on it.
Thanks in advance.
Regards
VILASFind out your checking rule maintained in Order Control OPJK for your order type and plant combination for both
Create(1) and Release purpose.
Then in t.code OPJJ and for that Checking rule and Checking group combination(Maintain in material Master) go to detail screen and don't activate check box for No Storage location inspection.
In this case system will check the available stock in Production storage location only.If it is not maintain then system will check at plant level in all storage locations.
If production storage location is not maintained either in material master or in BOM then maintain it.
karthick -
Availability check with reservation transfer
Dear all
I have a problem with availability check.
Reservation transfer, generated from processing MRP (from MRP area Z002 to MRP Area Z001).
Availability check doesn't consider reservation transfers generated from processing MRP.
if fixed the requirement, simply by saving for example, the availability check works. Of course, if I create it manually (MB21) works.
This behavior is normal?
many thanks!Dear all
I have a problem with availability check.
Reservation transfer, generated from processing MRP (from MRP area Z002 to MRP Area Z001).
Availability check doesn't consider reservation transfers generated from processing MRP.
if fixed the requirement, simply by saving for example, the availability check works. Of course, if I create it manually (MB21) works.
This behavior is normal?
many thanks! -
Availability check with Packing Instructions
Hi everybody:
Is possible to check the stock availability with Packing Instructions?
And if the answer is yes, what I need to do for?
I have PP, SD and MM(inventory management) I don't have WM.
Is there an special configuration in the IMG?
Thanks in advance
Omar Perea
Edited by: Omar Perea on May 15, 2009 12:46 AMHi everybody:
Is possible to check the stock availability with Packing Instructions?
And if the answer is yes, what I need to do for?
I have PP, SD and MM(inventory management) I don't have WM.
Is there an special configuration in the IMG?
Thanks in advance
Omar Perea
Edited by: Omar Perea on May 15, 2009 12:46 AM -
Availability check with MRP area at Sloc level
HI We have MRP area at storage location level maintained for materials. Stock exists in the plant in the storage location which is part of the MRP area.
Now when I create STO and try to create delivery for the same, system is giving message 0 stock available and not creating delivery. Material has 02 Avl Chck group.If I deactivate the MRP area in the material master, it allows creation of delivery.
How can I ensure that system creates delivery even though stocks exist in MRP area relevant sloc only in the plant?
SriramI am sure you have already moved on from this issue, but what you mention is a limitation prior to ECC 6. You can not identify on the purchasing document the source sloc of the supplying plant. This is why you can not create the STO between sloc MRP areas. I was told this was resolved in ECC 6.
Jon -
Make to order availability check scenario with production order
We have a make-to order scenario where we build custom products for our customers.
In SAP, we specify a strategy group so a production order is automatically generated when an sales order item is entered. However, we sometimes create a small amount of stock, in anticipation of an order. I would like the system to first check available stock in the system, beofre proposing a production order.
Is something like thi spossible thru configuration of the strategy group, or perhaps another method?
Regards
KenHi,
In SPRO->Sales and Distribution->Basic Functions->Availability Check and Transfer of Requirements->Availability Check->Availability Check with ATP Logic or Against Planning->Carry Out Control For Availability Check
Select the Availability check and the Checking rule combination of intrest and if you select the details,here you define that stocks that are to be considered during availability check. -
Set Availability Check to Exclude Planned Order
Hi All,
anyone know how to set the availability check so it will not include the planned order in the calculation ?
I find one setting in SPRO, the path is :
Sales & distribution ==> Basic functions ==> availability check and Transfer of Requirements ==> Availability Check ==> Availability Check with ATP Logic or Against Planning ==> Carry Out Control for Availability Check
select one of the record, and update filed "Incl. Planned Orders".
I've uncheck that field, but I can't get the appropriate result. When I create a new sales order, the availability check still take the planned order I created before into account.
The problem is, my user want to prevent creating delivery before the goods are already put in the stock. So the planned order should not be considered in the availblity check.
Thank you in advance
RudyHi Rudy,
Concept of availability check is to verify if the stock is available at the time of creation of sales order. If available, when it can be ready for delivery (as Packing, arranging for transportation, etc may have lead time) & if not available, when it would be available considering Packing, arranging for transportation, etc lead time.
Availability check whether material is available on required delivery date (backward scheduling) or not. If not available on required delivery date, system will propose next available date (forward scheduling)
1. Define Checking Groups
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups
You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries
2. Define Material Block for Other Users
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.
3 .Define Checking Groups Default Value
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.
4. Carry out Control for Availability Check
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.
5. Define Procedure by Requirements Class
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.
6. Define Procedure for Each Schedule Line Category
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.
7. Determine Procedure for Each Delivery Item Category
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.
8. Checking Rule for Updating Backorders
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.
9. Define Default Settings
Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.
Availability checks
1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
3. Rescheduling: is a proposal of how confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics sales & distribution sales environment availability overview.
5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
7. There are three types of availability checks
Check on basis of ATP quantities.
Check against product allocation.
Check against planning.
Configuring Availability check through Checking Groups
1. The checking group + checking rule determine how the availability check is to be performed.
2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
5. Briefly explaining the above checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
6. Advantages of individual processing over summarized processing
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
7. Required data for the Availability check to be carried out
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
8. Configuring Availability check and defining Checking Groups
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 summarized requirements and 02 individual requirements or you can create your own by copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
9. Defining material block for other users the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
11. Controlling Availability Check in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order is a good indicator of receiving stock on a specified date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
Please Reward If Helpful,
Thanks and Regards,
Sateesh.Kandula -
Stock confiramtion at sales order level for future date- Availability Check
Hi all
Here is the scenario
This setting is available in the system:
Stock is available
Sales order created with Requested delivery date in future-> not confirmed
Sales order created with Requested del date today -> confirmed
The requirement :
how and where to change this setting in IMG so that also orders with Requested Delivery Date in future are confirmed if stock is available.
As this is urgent request to respond quickly.
Regards
DevenderHello Devender,
You can achieve the mentioned scenario by configuring ATP. You can do ATP with RLT or ATP without RLT.
In ATP with RLT, system will check and confirm the quantities from existing stock only and if quantities are insufficient then the system will consider inline POs or manufacturing time to confirm remaining quantitites.
Else you will be getting schedule lines for only items in stock and remaining will be unconfirmed as ATP without RLT will be activated i.e., system will check and confirm the quantities from existing stock only.
Types of Availability Check in Sales and Distribution
Processing
There are three types of availability check:
_ Check on the basis of the ATP quantities
_ Check against product allocation
_ Check against planning
The following SD-specific control features need to be maintained in Customizing:
_ Checking group
The checking group controls whether the system is to create individual or collective
requirements in sales and shipping processing. In addition, a material block for the
availability check with transfer of requirements can be set here. The checking group can
also be used to deactivate the availability check. This option was created especially for
the assembly order so that when the bill of material is exploded in the assembly order,
the individual components, if necessary, can be classified as non-critical parts as far as
procurement is concerned.
The checking group specifies in combination with the checking rule the scope of the
availability check. It is proposed in the material master record on the basis of the material
type and the plant, and copied into the sales and distribution documents.
_ Checking Rule
You use the checking rule to control the scope of the availability check for each
transaction in sales and distribution. You also specify whether the check should be
carried out including or excluding replenishment lead time. The individual checking rules
define by transaction, which stock and inward and outward movement of goods should
be taken into account for the availability check.
_ Schedule line category
You can control with the schedule line category whether an availability check and
transfer of requirements should be carried out in the sales documents. The possible
settings for this at schedule line level are dependent on the settings in the requirements
class which is determined from the requirements type of the material.
_ Delivery item category
The delivery item category can be used to control whether an availability check takes
place in deliveries.
Requirements type
The various requirements are identified by their requirements type. The requirements
type refers to the requirements class and its control features.
_ Requirements Class
The requirements class contains all control features for planning such as relevance for
planning, requirements planning strategy and requirements consumption strategy. In
addition, it is specified at a global level whether an availability check is to take place for
the material in the sales and distribution documents on the basis of the ATP quantity
(ATP = available to promise) and whether requirements are to be passed on. A finer
degree of control can be obtained for sales documents using the schedule line category.
Replenishment lead time is only included in the check performed on the basis of the
ATP quantity.
Prerequisites
An availability check can only be carried out if the following prerequisites have been fulfilled:
_ The control elements described above for the availability check must be maintained in
Customizing for Sales and the relevant assignments made to the sales transactions
_ The availability check must be switched on at requirements class level and - for the
availability check in the sales documents - at schedule line category level
A requirements type must exist by which the requirements class can be found
_ A plant must be defined. It can either be proposed from the customer or material master
record or can be entered manually in the document.
_ A checking group must be defined in the material master record on the Sales/plant data
screen in the Availability check field
Configuring entries of the Availability Check
IMGSDBasic fncsAvailability check and TORAvailability checkAvailability check with ATP logic or against planningDefine checking groups
You can use SAP std checking groups of 01 for summarized reqts or 02 for daily reqts or u can create ur own.
The columns total sales and total deliveries are selection options whereby u can configure a checking rule to sum up reqts to post to MRP either individually or by day or week.
Column 5, Block qty; set this block if u want several users to be able to process the material simultaneously in different transactions without blocking each other. The No Check indicator is used when u want a material to not be relevant for an ATP check.
Defining a material block for other users. The Block checkbox is an indicator that enables u to block the particular material from being checked for availability if it is already being checked at the same time by another user.
Defining the default value for checking groups. However should no entry exist for the checking group in the material master record, one can set a default value per material type and plant.
Controlling the availability check. In this section, u tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sd transaction. The carry out control for the availability check must be maintained for both the sales order and delivery.
Reward points if helpful.
Regards,
Priyanka -
I am getting the error in Sales Order - "No control Information maintained for Checking Group (ZP) and Checking rule A"
Actually my checking group is 01 not A. I Have configured Transfer of Requiremenst and Avaialability Check.Hi Gurus,
Availabilty Check Configuration ( More Informative )
Types of Availability Check in Sales and Distribution
ProcessingThere are three types of availability check:
_ Check on the basis of the ATP quantities
_ Check against product allocation
_ Check against planning
The following SD-specific control features need to be maintained in Customizing:
_ Checking group
The checking group controls whether the system is to create individual or collective
requirements in sales and shipping processing. In addition, a material block for the
availability check with transfer of requirements can be set here. The checking group can
also be used to deactivate the availability check. This option was created especially for
the assembly order so that when the bill of material is exploded in the assembly order,
the individual components, if necessary, can be classified as non-critical parts as far as
procurement is concerned.
The checking group specifies in combination with the checking rule the scope of the
availability check. It is proposed in the material master record on the basis of the material
type and the plant, and copied into the sales and distribution documents. It is specified in MMR in MRP3 screen, availability check tab.
_ Checking Rule
You use the checking rule to control the scope of the availability check for each
transaction in sales and distribution. You also specify whether the check should be
carried out including or excluding replenishment lead time. The individual checking rules
define by transaction, which kinds of stocks and inward - outward movement(receipts and issues) of goods should
be taken into account for the availability check.
_ Schedule line category
You can control with the schedule line category whether an availability check and
transfer of requirements should be carried out in the sales documents. The possible
settings for this at schedule line level are dependent on the settings in the requirements
class which is determined from the requirements type of the material.
_ Delivery item category
The delivery item category can be used to control whether an availability check takes
place in deliveries.
Requirements type
The various requirements are identified by their requirements type. The requirements
type refers to the requirements class and its control features. it is assigned to requirement class.
_ Requirements Class
The requirements class contains all control features for planning such as relevance for
planning, requirements planning strategy and requirements consumption strategy. In
addition, it is specified at a global level whether an availability check is to take place for
the material in the sales and distribution documents on the basis of the ATP quantity
(ATP = available to promise) and whether requirements are to be passed on. A finer
degree of control can be obtained for sales documents using the schedule line category.
Replenishment lead time is only included in the check performed on the basis of the
ATP quantity.
Prerequisites
An availability check can only be carried out if the following prerequisites have been fulfilled:
_ The control elements described above for the availability check must be maintained in
Customizing for Sales and the relevant assignments made to the sales transactions
_ The availability check must be switched on at requirements class level and - for theavailability check in the sales documents - at schedule line category level
A requirements type must exist by which the requirements class can be found
_ A plant must be defined. It can either be proposed from the customer or material master
record or can be entered manually in the document._ A checking group must be defined in the material master record on the Sales/plant data
screen in the Availability check field
Configuring entries of the Availability CheckIMGàSDàBasic fncsàAvailability check and TORàAvailability checkàAvailability check with ATP logic or against planningàDefine checking groups
You can use SAP std checking groups of 01 for summarized reqts or 02 for daily reqts or u can create ur own.
The columns total sales and total deliveries are selection options whereby u can configure a checking rule to sum up reqts to post to MRP either individually or by day or week.
Column 5, Block qty; set this block if u want several users to be able to process the material simultaneously in different transactions without blocking each other. The No Check indicator is used when u want a material to not be relevant for an ATP check.
Defining a material block for other users. The Block checkbox is an indicator that enables u to block the particular material from being checked for availability if it is already being checked at the same time by another user.Defining the default value for checking groups. However should no entry exist for the checking group in the material master record, one can set a default value per material type and plant.
Controlling the availability check. In this section, u tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sd transaction. The carry out control for the availability check must be maintained for both the sales order and delivery
Regards,
Sarosh -
Changing Availability Checks in Sales orders
hi there,
Can i easily change the Availability Check in a sales order?
i have 5 sales orde rtypes, and I sometimes want to change the Availability Check, how can i manage this?
thanksThere are three types of availability checks
1. Availability Check with ATP Logic or Against Planning
2. Availability Check Against Product Allocation
3. Rule-based Availability Check
For ATP logic, the Checking group and Checking rule combination determines the availability check parameters. The checking group is maintained in the material master, and not to Sales order type. Hence you can control by having different groups attached to different materials.
If you have Advanced Planner Optimiser (APO) then you can use the Rule based availability check. You can attach a Business transaction to a Sales document type and thus control the availability check in sales order level also.
Refer the below extracts:
<b>Define business transaction</b>
Path : spro -- img -- sd -- BF -- Av chk and TOR --- Rule based availabilty check
In this step you can define the business transactions. These transactions must also be available in the APO planning system. Here the availability check control is carried out for the transactions.You can find the business transactions in the APO planning system (Field BPROC) under:
Global ATP -> Settings -> Rule-based ATP -> Conditions -> Assign rule strategy.
<b>Assign business transaction to sales order type</b> t code VOV8
In this IMG activity, you assign the actions you defined previously to the order types. This activates the availability check settings for this order type, that were maintained in the APO planning system.
Regards, -
hi
can anyone tell me whether availability check is first or TOR. Explain in one scenario.
please urgent
regards
muralihi,
Availability Check & TOR configuration is done hand in hand..
To confirm the quantities for a particular line item in the sales order on particular day system carried out transfer of requirements (TOR) & AVAILABILITY check, so has to confirm the quantity on particular day as system should know what are there requirement of the sale order and delivery with MRP then system carries out availability check function, to confirm the quantity on particular day. Depending upon the IMG setting system carries out availability check function based on 3 methods:
A) Availability Check with ATP logic or against planning:
In ATP logic systems ATP Qty while carrying out availability check function for
Particular line item (ATP qty=warehouse stock +planned receipts-planned issues)
Planned Receipts: EX: - purchase requisitions, purchase orders, stock in transfer, stock at inspection etc.
Planned Issues: - EX: - open sales order & open delivers
B) Availability check against product allocation:
Availability check can be carried out against product allocations in which system automatically restrict the user to confirm the quantity beyond reserved quantities per particular customer. EX: - Availability qty =100, existing orders=10, then system automatically distributes to items evenly to the sales order.
C) Rule based Availability check:
Rule based availability check can be carried out based on the business transaction.
EX: - For normal sales order system has to carry out availability check for special sales order ex: - cash sales and rush order systems need not to be carry out availability check,
In rule based availability check system in which system carried out Global availability to promise in all plants. In this check system transfers the requirements to APO system where GATP takes place and the result of the availability check transferred to R/3 system. This process takes place with the transaction code CIF(central inter face) inR/3.After carrying out availability check function system proposes(by using ATP logic) default values of ATP check result to the user in a dialog box, in which system gives the choice to the user to take the decision in contest of insufficient stock.
a) One time delivery:
If the user chooses one time delivery and the order Quantity is 100 units system confirms 50 units then systems automatically confirms as a zero. If the user saves the document with the zero confirm qty then system trace the sales order as aback order (V_RA), which can be confirmed later by RESCHEDULLING (V_V2).
b) Complete Delivery:
If order Qty=100, Availability stock = 50, system says that remaining can be given after one week. Then if the user selects this option then system push up existing confirmed qty to after one week and the total qty can be confirmed after one week only.
c) Delivery Proposal:
If order qty=100, system confirms 50, and remaining 50 can be confirmed after one week. If the user chooses this option then system confirms 50 Qty today allows the user to delivery 50 quantities today remaining 50 can be delivered after one week.
CONFIGURATION SETTINGS FOR TOR:
Define Requirement Class:
Path: SImg & Availability Check Basic functions D & Transfer of Define Requirement classes Transfer of requirements requirements
Requirement classes control MRP, Requirement consumption, strategy, relevance for planned. It specifics whether the availability check & TOR to be Called out for transactions. Ex: Sales Order
It determines whether requirements relevant for MRP or not, the allocation indicator from the sales view which controls the settlement of customers requirements with planned independent requirements. It determines the item b to be settled as an availability heck. Assignment, the settlement profiles the results analysis key. The TOR and Availability check functions are globally controlled using the requirement class for all the Sales documents. The values from the Requirements class are transferred to scheduled the of the sales documents class are transferred to scheduled the of the sales document default values and can be over written there.
Define Requirements Classes:
Requirement class defines whether the system has to carry out availability check based on the STP Qty. Ex:
Define Requirement Types:
Here we define requirement type, Ex: and Assign to Requirement class that we defined in the promote step.
Determination of Requirement types using Transaction:
Requirement type is going to be determined for sales document by following a search strategy. .
First System checks strategy group in MRP3 view if it trend requirement type then system takes from it, otherwise.
It will go to MRP group in MRP1 view, otherwise
It will check to Material type, otherwise
It will go to item Category + MRP type, otherwise
It will go to Item category only, otherwise
Finally system determines the transaction b not relevant for TOR & Availability check.
Choose Item category TAN+MRP type PD=Requirement type =0
Define Procedure for each schedule the category:
Here we define respective schedule the category of the sales documents, whether an availability check and TOR should be carried out. This setting is relevant for sales documents only. It is fine tuning of availability check for sales documents TOR & Availability check function can be activated at sales order level those are proposed in to schedule line category level. If u wants to deactivate TOR availability check function at schedule the category level and want to deactivate at requirement class level it b impossible.
Ex: If u wants to check availability w/o transferring the requirement we can use it.
Choose schedule line category CP & Activate Availability check, requirement & Product Allocation
Block Quantity confirmation in delivery Blocks:-
When we transfer requirements to MRP then confirmed quantities is also reserved for confirmed sales documents, if transaction is blocked for delivery the reserved quantities are also blocked so that the conformed quantities cannot be used by any other purpose. So has to avoid this situation we can block the transfer of requirements(TOR) for delivery blocks, in this case requirements transferred to MRP but will not be reserved, that will be cleared once we save the documents then system shows confirmed qty as zero.
When we remove the delivery block then system automatically carries out availability check & confirms the qty.
A) Deliveries: Blocking region for sales Area:
Here we define blocking regions for TOR ex:-credit limits
B) Reasons for scope of delivery blocks: TOR. Block:
Ex: - 01 credit limits-check confirmation block.
Maintain Requirements for TOR:-
Here we can define our own requirement with the help of ABAPer for TOR
Ex: - a) 102- prevent reservation in the event of credit block
b) 102-purchase requisitions.
System doesnt create purchase requisitions for sales order line items if it has a credit limit.
Availability check:
Configuration setting:-
Availability check with ATP logic or against planning:-
Define checking group:
Checking group define what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records
Individual requirement records: that means system creates requirement record for each S&D document.
Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:
Summarized requirement records for each day.
Summarized requirement records for each week
Define checking Action;
Here we define 01- daily requirement -B 02- Individual requirements -A
Where b-total record per day
A-single record per day
B) Define material Block for other users:
When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block
C) Define checking group default values:
Checking group is going to be determined depending upon the material type & plant.
-Go to new entries, specify material type, ex;-FERT
& plant = checking group of availability check: 02
D) Carry out for Availability check:
Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.
Action:
*Select checking group of availability check-02, checking rule=01
*Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check
*save it, exit.
E) Define procedure by Requirement class:
Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There settings automatically copied into define from of requirement class and vice versa.
Action:
*Choose requirement class: 041 & check availability check & TOR (requirement)
F) Define procedure for each schedule line category:
Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.
Ex:- if we want to implement a availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR
G) Determine procedure for each Delivery Item category:
H) Checking group for updating back orders:
CHAN -
Availability Check configuration
Hi All,
I want to configure availabiliy check but I am a bit confused with the config part. Soneone plz explain the config process.
Also tell me what is the exact link ( in config ) by which the availabilty check gets triggered.
Regards,
Danny.Dear Danny,
Hope the material pasted here helps you... :
Availability Check & Transfer of Requirements
Availability check
1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
3. Rescheduling: is a proposal of how u2013 confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) u2013 planned issues (outgoing stock). To examine stock on hand (T-Code - CO09) proceed to logistics u2013 sales & distribution u2013 sales u2013 environment u2013 availability overview.
5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
7. There are three types of availability checks u2013
Check on basis of ATP quantities.
Check against product allocation.
Check against planning.
Configuring Availability check through Checking Groups u2013
1. The checking group + checking rule determine how the availability check is to be performed.
2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
5. Briefly explaining the above u2013 checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
6. Advantages of individual processing over summarized processing u2013
Backorder processing is possible.
You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
The system automatically uses individual requirements in case of special stock items.
7. Required data for the Availability check to be carried out u2013
The Availability check must be switched on at the requirement class level.
The Availability check must be set at the schedule line level.
A requirements type must exist by which the requirements class can be found.
A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
8. Configuring Availability check and defining Checking Groups u2013
Checking groups are introduced into the sales order based on the setting in the material master record.
SAP standard checking groups are 01 u2013 summarized requirements and 02 u2013 individual requirements or you can create your own by copying the standard ones.
Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
9. Defining material block for other users u2013 the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
If an entry exists, this default value is over written by MMR.
11. Controlling Availability Check u2013 in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under u2013
When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
A shipping notification on the other hand - a confirmed purchase order u2013 is a good indicator of receiving stock on a specified date.
It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
ATP
Types of Availability Check in Sales and Distribution
Processing
There are three types of availability check:
_ Check on the basis of the ATP quantities
_ Check against product allocation
_ Check against planning
The following SD-specific control features need to be maintained in Customizing:
_ Checking group
The checking group controls whether the system is to create individual or collective
requirements in sales and shipping processing. In addition, a material block for the
availability check with transfer of requirements can be set here. The checking group can also be used to deactivate the availability check. This option was created especially for the assembly order so that when the bill of material is exploded in the assembly order, the individual components, if necessary, can be classified as non-critical parts as far as procurement is concerned.
The checking group specifies in combination with the checking rule the scope of the availability check. It is proposed in the material master record on the basis of the material type and the plant, and copied into the sales and distribution documents. _ Checking Rule
You use the checking rule to control the scope of the availability check for each
transaction in sales and distribution. You also specify whether the check should be
carried out including or excluding replenishment lead time. The individual checking rules define by transaction, which stock and inward and outward movement of goods should be taken into account for the availability check. _ Schedule line category
You can control with the schedule line category whether an availability check and
transfer of requirements should be carried out in the sales documents. The possible settings for this at schedule line level are dependent on the settings in the requirements class which is determined from the requirements type of the material. _ Delivery item category
The delivery item category can be used to control whether an availability check takes place in deliveries. Requirements type
The various requirements are identified by their requirements type. The requirements type refers to the requirements class and its control features.
_ Requirements Class
The requirements class contains all control features for planning such as relevance for planning, requirements planning strategy and requirements consumption strategy. In addition, it is specified at a global level whether an availability check is to take place for the material in the sales and distribution documents on the basis of the ATP quantity (ATP = available to promise) and whether requirements are to be passed on. A finer degree of control can be obtained for sales documents using the schedule line category.
Replenishment lead time is only included in the check performed on the basis of the ATP quantity.
Prerequisites
An availability check can only be carried out if the following prerequisites have been fulfilled:
_ The control elements described above for the availability check must be maintained in Customizing for Sales and the relevant assignments made to the sales transactions
_ The availability check must be switched on at requirements class level and - for the availability check in the sales documents - at schedule line category level
A requirements type must exist by which the requirements class can be found
_ A plant must be defined. It can either be proposed from the customer or material master record or can be entered manually in the document.
_ A checking group must be defined in the material master record on the Sales/plant data screen in the Availability check field
Configuring entries of the Availability Check
IMG > SD > Basic fncs > Availability check and TOR > Availability check with ATP logic or against planningAvailability check > Define checking groups
You can use SAP std checking groups of 01 for summarized reqts or 02 for daily reqts or u can create ur own.
The columns total sales and total deliveries are selection options whereby u can configure a checking rule to sum up reqts to post to MRP either individually or by day or week.
Column 5, Block qty; set this block if u want several users to be able to process the material simultaneously in different transactions without blocking each other. The No Check indicator is used when u want a material to not be relevant for an ATP check.
Defining a material block for other users. The Block checkbox is an indicator that enables u to block the particular material from being checked for availability if it is already being checked at the same time by another user.
Defining the default value for checking groups. However should no entry exist for the checking group in the material master record, one can set a default value per material type and plant.
Controlling the availability check. In this section, u tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sd transaction. The carry out control for the availability check must be maintained for both the sales order and delivery.
TOR
IMG > SD > Basic fncs > Availability check and TOR > TOR
A line item in the sales order creates a schedule line. The schedule lines in the sales order transfer the requirements through to MRP. You can select the docs on which you want the TOR to happen. For ex, not for quotations.
The TOR aims to ensure the ordered materials are available for the requested delivery date. The TOR can be set for individual or for collective requirements (materials sales/plant view).master
The TOR is dependent on the following data:
The reqts type, reqts class, checking group and schedule line category.
The reqts type and class are determined in the strategy group MRP3)(material master
For TOR to be carried out, a few criteria need to be met:
Plant assigned to line item level, schedule line category should be switched on at TOR, TOR must be switched on at the reqts class level, checking group must be defined and allocated to the material master record (sales/plant view in the availability check field)
The reqts class is the controlling factor for the availability check and the TOR for all sd types.
Configuring the TOR:
1) Use std 041 reqts class or copy and rename it. Use the indicators to select if this reqts class must carry out an availability check and/or a TOR.
2) Define the reqts types. A reqts type is allocated to a single reqts class and not vice versa. It is based on the item category and the MRP type of the material.
3) Assign the rqts type to the relevant item category in the sales order and the MRP type found on the material master record.
You can select an alternative search strategy where u assign the reqts type to item category and MRP type. Can select source as 0, 1 or 2. (1 = Item type and MRP type strategy).
4) The TOR and Availability check can be selected/de-selected at the schedule line category level.
5) Block qty confirmation in delivery blocks. This is used to block the reservation of the TOR from MRP.
6) Maintain requirements for TOR. Requirements can be used to determine that the TOR to MRP is not carried out unless a number of conditions are met.
Availability Overview = CO09 > order qty, sd doc no, item no, requirements class.
sd no or dly no, lineStock requirements list = MD04 item, schedule line placing the demand
Stock overview = MMBE > total stock per company, then plant followed by storage location, and finally a breakdown per batch.
Transfer of requirments:
for TOR to happen the folowing control elements must be defined
1. requirmrent type.
2.requirement class.
3.checking group
4.schedule line category.
apart from the above the TOR must be switched on at
1.reqt class level.
2.schedule line level
3.checking group level.
4.plant must defined at the document item level
once order is raised the requirments are transfered from order to MRP by TOR,
various reqts are identified thru reqt type, reqt type are identified in the system thru
1. strategy group--MRP1 --mmr
2.MRP group.
3.material type.
4. ITEM category +mrp type
5.item category
once reqt type is identified it points to reqt class.
reqt class contains all the control factors suchas planing strategy,consumption strategy etc
basing on the item category group+ mrp type-- schedule line categories are identified.
if it is relevant for availability check, then the system does ATP CHECK(warehousestockplanned ordersproduction ordersconfirmed receiptsconfirmed goods issues) and decides whether goods are availabile on
the requested delivered date of the customer, if not system does a backward scheduling and confirms when material is available (materual availability date),
so if material is not available then system proposes 2 dates
1.customer delivery date
2.material availability date.
for availability check to happen the following pre-requistes must be there:
1.availability check must be swithched on at the requirment class level
2.schedule line level itmust be switched on
3.reqt type must be defined
4.checking group must be defined.
5.plant must be defined
6. the system takes by default checking group if not defined as material type and plant.
from SD the following componenets are importants
1.checking group:defines whether indivual orcollective req are to be passed
2.checking rule: defines scop of the check(what type of stock+with or without RLT)
3.schedule line category: this fine tunes whether availability check should be carried on at the sales document level or not.
4. delivery item category.
for config:
SPROSALES&DIST-BASIC FUNCTIONS--TOR&AVAILABILITY CHECK.
In material master the below mentioned must be defined also
1.strategy group.
2.scheduling margin key.
3.in house production time.
4. RLT time.
5.MRP group
Hope this above helps...
Give points if userful...
Thanks,
Jignesh Mehta
Maybe you are looking for
-
Converting the WAD applications into PDF format
Hi SAPians, I'm in need to convert WAD results into PDF Format using SAP BW 3.5 and Acrobat Reader 7.0. And I've referred some documents in Net, But,they gave ideas only for 3.5 and Acorobat 5 version. But i've to convert the WAD results into PDF for
-
Wireless Mighty Mouse has stopped selecting, cutting or pasting
My batteries ran out two days ago. I changed the batteries but since then my wireless Mighty Mouse will not select text, cut or paste. It has other erratic behavior. Any help and advice welcomed.
-
ERR: HTTP_RESP_STATUS_CODE_NOT_OK - 401 Unauthorized
Hi All, I have a scenario which transfers data from ABAP Proxy(client 200 of XI) to XI(client 100 of XI) IS using the interface "ValueMappingReplicationOut" and the receiver adapter is XI. While executing an ABAP program from client 200 (to trig
-
Mapping users from ActiveDirectory
Hello, I'm trying to build a prototype using WebLogic that uses the Negotiate Identity Assertion provider for SSO with IE clients. According to the documentation at http://e-docs.bea.com/wls/docs100/dvspisec/ia.html#ia300, the provider maps the token
-
I'm trying to load photos from iPhoto to my mother's new Christmas present digital photo frame which is not Mac compatible. I made a new iPhoto folder of the photos I want, then tried dragging that onto the camera device icon in iPhoto. No go. Then I