Availability check & TOR

hi
can anyone tell me whether availability check is first or TOR. Explain in one scenario.
please urgent
regards
murali

hi,
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

Similar Messages

REG: Availability Check & TOR

I have a doubt that whether TOR happens first or Availability Check.
As per my knowledge, first TOR then Availability Check.
If I am wrong then please guide me.
NAYAK

Dear Nayak
While creating sale order, first Availability Check happens and once you save the order, TOR comes into picture. Of course, two types of TOR are there
- Transfer of requirements with individual requirements
- Transfer of requirements with collective requirements
You are defining the above in material master in Sales : General / Plant view whether each requirement is forwarded individually to planning or whether the requirements for one material in one plant are be combined.
thanks
G. Lakshmipathi

Difference between TOR & Availability check

Hi all,
what is difference between availability check & TOR?????
when i create sales order what TOR will do for the material & what availability check will do for the same material????? i hope my point is clear.
Pl dont paste configuration material .
Pt will rewarded accordingly

Dear Neil,
Before answering your question let me tell you that " pts will be rewarded " this word is against the forum rule, we all are here for helping each other and not for collecting "pts" .
now coming to your question, this is will tell you with an example of TAP and WATER. Till then TAP wont be Open Water wont come out from the TAP.
Similarly TOR and Availability check works. While creating the sales order the first thing is Requirement will pass to the MRP, i,e TOR will function. Then it will check the availability of the stock, means availability check will happen.
I hope its clear your doubt.
thanks,
Raja

Avilability Check ,TOR & MRP

Hi,
Can any one tell the complete logic and concept of availability Check ,TOR & MRP in SD poin of view
Regards'
Hemant

Dear Hemant
Please check these links
[Working with the Availability Check in Sales and Distribution Processing |http://help.sap.com/saphelp_47x200/helpdata/en/93/744b7d546011d1a7020000e829fd11/frameset.htm]
[Working with Requirements in Sales and Distribution Processing|http://help.sap.com/saphelp_47x200/helpdata/en/93/744c6c546011d1a7020000e829fd11/frameset.htm]
[MRP Procedures |http://help.sap.com/saphelp_47x200/helpdata/en/6d/d20d3801a01f2ee10000009b38f842/frameset.htm]
thanks
G. Lakshmipathi

Error in va01 for transfer of reeqirement and availability check

hi every one when i have done TOR and availabilty check configuration it is not reflecting in va01 can any one help out with configuration step by step

HI
Kindly check the Google with Same text so you can find out so many documents which is related to Availability Check & TOR
Coming to your Question , try to check the Schedule line Category (VOV6) , you need to TICK the Field *"Availability" * Requirement/Assembly"*
and also kindly check the Below
link [Availability Check (ATP) and Transfer of Requirement (TOR)|http://wiki.sdn.sap.com/wiki/display/ERPLO/AvailabilityCheck(ATP)andTransferofRequirement+(TOR)]
[Available to Promise (ATP)|http://wiki.sdn.sap.com/wiki/display/ERPLO/AvailabletoPromise+(ATP)]
Regards,
Prasanna

Availibility check for sales orders created simultaneously

Hi SD experts,
When a sales order is being created with an item "A", while a second sales order is being created too, at the same time, with the same item "A", the system can't carry out the availibilty check.
It displays the following message : "The material A (plant M500) in item 000010 which you entered for processing is blocked for another transaction. The system is therefore unable to carry out either the availability check or the transfer of requirements."
This is quite logic... But for example for a call center where the operators create orders simultaneously how can we make it possible??
Any suggestions please ?
Thank you,
Bahia.

Hi there,
In SPRO -> SD --> Basic functions --> Availability check & TOR --> Avaliability check --> Avaliability with ATP --> Define material block for other users.
Here you make the settings for different availability check types 02 for individual requirements etc. If you check the field Block, system will block the material for other remaining sales orders if availability check is being carried for one sales order. It is set at plant level. If same material is available at other plants, it will be available there.
Regards,
Sivanand

Availabilty check & tor

Hi sd gurus,
can anyone plz send me screen shots for availabilty check and tor in sd point of view ,plz help me am having the theory part idea but am not geting complete picture plz send me

Hello Srinu,
I cant provide you any screen shots for the topics you have asked. But pls go through the following notes. Its really good and you'll have a clear Picture on the topics.
 Availability check is considered as a pre-sale activity, where as TOR and MRP are post sale activities.
Materials Requirements Planning (MRP) and Transfer of Requirements (TOR).
1. A schedule line in a sales order represents the customers intended delivery date and quantity to be delivered. In a standard sales order processing, the system transfers requirements (TOR) to Material Requirement Planning (MRP).
2. MRP - then determines if there is enough quantity of stock available for the scheduled delivery date. The TOR aims to ensure that the materials ordered are ready for the requested delivery date.
3. The TOR is closely integrated to Materials Management and Production Planning modules thus it must be configured in association with the respective teams.
4. The TOR can be set either for individual requirements or for collective requirements in MMR (Sales: general/plant and MRP3 views).
5. Individual requirements are the transference of requirement to MRP for each schedule line of the sales order. An advantage of this is that the availability overview (CO09 logistics material management environment stock availability overview) will show the order quantity, sales document number, item number and requirements class for each schedule line for which a demand has been created.
6. Collective requirements are a collective grouping of requirements created either daily or weekly that are transferred to MRP; but the documents processed in collective requirements cannot be individually identified from the availability overview (CO09). Collective requirements are useful to a business that deals with a large volume of sales orders per day, as it allows the business to have a clearer view of the availability overview and speeds up the response time within the system as well.
7. The system will automatically create individual requirements (irrespective of the collective requirements indicated in MMR) in case of special stock items such as consignment, returnable packaging, make to order stock etc.
8. The control elements that are used for Transfer of Requirements (TOR) and Availability Check are
 the requirements class
 the requirements type
 the checking group
 the schedule line category
9. The requirements class is the controlling factor for TOR and the availability check for all sales document types. It determines if the system has to perform TOR, Availability check and product allocation to any particular sales order.
10. The requirements class is determined from the requirements type of the material.
11. The checking group in general is the criterion that groups together all the checking rules from all application areas for a material. In conjunction with the checking rule, it defines the scope of the availability check for each business event; that is, which stocks, goods receipts and goods issues are taken into account in the availability check, and whether replenishment lead time is checked. The checking group must be defined and allocated to the material master record in the sales: general/plant view in the availability check field.
12. for TOR to be carried out, you need to ensure the following criteria are met
 The TOR must be switched on at the requirements class level.
 The schedule line category must be switched on for the TOR (fine tuning).
 A plant must be assigned to the sales document line item level.
 A checking group must be defined and allocated to the material master record in the sales: general/plant view in the availability check field.
Planning materials
 It is possible to create a common planning material and assign similar materials to it (MRP 3).Independent requirements are created for the planning material to cover the requirements that are expected for the materials assigned to the planning material. This means that you do not have to create independent requirements for each material. Instead create a material and assign the same to the planning material already created with similar properties.
 A valid material master record must exist for the planning material in the planning plant. The material master record of the planning material cannot contain a planning material as this procedure can only be carried out at single-level.
 An appropriate strategy group must also be entered in the MRP 3 screen for planning with planning materials. The strategy group groups all the planning strategies that can be used for a particular material. The planning strategy represents the procedure used for planning a material and is (technically speaking) controlled by the MRP types.
 Consumption mode defines whether and in which direction on the time axis from the requirements date (corresponds to the date when the sales order items were created) the consumption of customer requirements with planned independent requirements should occur. Consumption period must exit between 1 and 999 days.
 Backward consumption only: starting from the requirements date, backward consumption is carried out within the relevant consumption period specified in MMR i.e. the system reduces the planned independent requirements that lie in the past. Likewise forward consumption only represents starting from the requirements date, the system reduces the independent requirements that lie in the future within the consumption period.
 Backward/forward consumption: in this case backward consumption is performed first and forward consumption is performed later depending on the availability of the independent requirements in the past. Forward/backward consumption is vice-versa of the above.
Stock requirements list
1. Stock requirements list is the central table for planning and stock control. It is invaluable to the interpretation of the available stock and the situation of stock levels in a plant.
2. Menu path: MD04 logistics material management inventory management environment stock stock requirements list. Here you can see the order number or delivery number as well as the line item and schedule line placing the demand on the given plant. It also shows the required and available quantity of material per order.
3. Another view of the stock situation in plant can be obtained from MMBE (stock overview). This view will show you total stock per company code, then at the plant, storage location and at batch level.
4. A useful tool in MMBE is material movements, which can be viewed by selecting stock line and proceeding to environment, material movements.
Configuring Transfer of Requirements 
1. IMG sales & distribution basic functions availability check & TOR transfer of requirements define requirements classes.
2. Requirements class (OVZG) is the controlling factor for the availability check and TOR for all sales documents. It determines whether the system should perform the transfer of requirements, availability check and product allocation when a sales order is created.
3. The system uses the entries used at this level as default and brings the data into the sales order. The same entries made at the schedule line category level (VOV6) are only used to fine tune the entries previously made at the requirements class level. The standard requirement class is 041 (order/delivery requirement).
4. Requirements type (OVZH) (displayed in the sales order beside schedule line category) requirements types identify the different requirements, such as sales order requirements, delivery requirements or individual customer requirements. The requirements types can be changed, for example, in order to represent customer-specific terms.
5. The first step in the process of configuring TOR is to define a requirements class (041 standard) by copying the standard one. It contains the preconditions for performing availability check, TOR and product allocation.
6. Next step is to create a requirements type, which is based on item category and MRP type of the material and allocate the previously defined requirements class to it. A requirements class can be allocated to more than one requirements type. It is possible to change the requirements type manually at the time of creating the sales order.
7. MRP type in the MMR determines how a material is planned for requirements i.e. automatic reorder point planning, manual reorder point planning or forecast based planning.
8. Determination of requirements types using transaction: when a sales order is created, the system looks for a relevant requirement type by using its own search strategy. Either it uses the following search strategy or you can make the system skip this entire process and straight away search for item category and MRP type by selecting 1 in the Q field while configuring determination of requirements types using transaction.
9. First attempt is to find the requirements type using strategy group in MMR.
10. If strategy group is not found, it will look for MRP group (MRP group groups together material with similar planning requirements and allocates special control parameters for planning such as strategy group, planning horizon and the creation indicator for planning run.
11. If MRP group is not found, it will try to access MRP type.
12. If no requirements type is found using MRP type, the system will use material type when accessing the corresponding tables.
13. Failing to find the requirements type even at this stage, it will try to get the requirements type using the item category and MRP type.
14. If this doesnt work either, then it will try to determine requirements type using only item category.
15. If the last attempt fails, the system determines the transaction is not relevant for availability check or transfer of requirements.
16. As discussed earlier TOR and availability check are fine tuned at the item category level. This is done at this stage i.e. define procedure for each schedule line category as a next step.
17. Block quantity confirmation in delivery blocks (linked to VD05 customer block): in the standard sales order processing, the system transfers the requirements to MRP, but in some cases you may need to block a transaction due to a bad result of the credit check.
18. When requirements are transferred to MRP, the confirmed quantity is also reserved for confirmed sales documents . If a transaction is blocked for delivery, the required stock will be blocked so it cannot be used elsewhere. To prevent this, you can block the transfer of requirements for a delivery block in this step.
19. You can set a limit on the number of days you would want the system to postpone this block on confirmation of requirements. This can be done by setting the number of days to the block in the Def. period column.
20. Maintain requirements for TOR: can be used to determine that the TOR to MRP is not carried out unless a number of conditions are met. For example in a standard sales order processing, a purchase order may need to be created in order to meet the demands of the customer. This purchase order is used to purchase new stock in order to meet the demand on MRP for particular customers sales order. Here you define requirements that must be met in order for the purchase order or assembly order to be created.
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 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.
Reward points if helpful
Regards
Sai

Reg available check and tor

Hi Friends,
Can any one explain me which one trigger first among available check and tor and how it works.
thanks
nitchel

Hi all,
I think TOR can't come first.
Let's assume a simple example at Plant.
Customer places an order for 50 pcs of a material, say XYZ.
The first thing what will one do is to check the quantity available in the stock for that material and if any shortage is there then only the requirement will be passed to prodution.
There will be two cases as a result:
1. Quantity in stock >= quantity ordered
The sales order will be easily executed for delivery of the material to customer.
2. Quantity in stock < quantity ordered
As the quantity in stock is less, a requirement then will be transfered/ passed to production to produce more pieces of the material to meet out the delivery.
So, an avaibality check is always carried out first over TOR.
Thanks & Regards,
Vijay
Edited by: VijayPrakash on May 27, 2009 12:46 PM

Reg TOR & Availability Check

How does system carries out TOR & Availability Check in sales order through foreground & background ? what is the logic it follows....?

Hi Ramesh,
To know entire scenarion of materail avalablity check
http://help.sap.com/saphelp_crm40/helpdata/en/e3/1e053883ccbc3ae10000009b38f8cf/content.htm
http://help.sap.com/saphelp_crm40/helpdata/en/b6/de3efc6bbcdc4b948d466857a10323/content.htm
SD material Determination based on availability check
For SD material Determination you can create a Substitution reason and on the Strategy field, the following info. is available:
Product selection in the background is performed on the basis of the availability check.
We want to have the material determination only in case on material shortage. We expect the Substitution reason to give us this functionallity. It does not hovever take the availabilty into account before substitution.
We thought the worse case is to create a ABAP which is linked to the "requirement" field in the Procedure (OV13).
Has anyone had the same requirement? Is this a bug or just incorrectly documented?
I also encountered this abnormally recently using material determination. In order to combat the problem, the first product substitution should be for the original material. I've illustrated this below:
Original Product: ABC
Substitutes: DEF, XYZ
In order to perform product substitution ONLY in the case of ATP failure for product ABC, structure the Material Determination record as follows:
Material Entered: ABC Substitutes: ABC
DEF
XYZ
There seems to be a devaition at availability check and or on a conceptual note still.
Availability check can be configured both at requiremnt class and at the schedule line categories level.
Whilst the availabilty check at the requirement class level via global and mandatory configuration the schedule line catgry availability check deals with the order.
It is mandatory that the reqmnt class is flagged off for avlblty check and the schdelu line cat need not be.
The following are the mandatory for Availability check to happen--
1. Must be swithced on at the requirment class level and at the schedule line level.
2. Reqmnt type must exist by which a requiremnt class can be found
3. There must exist a plant and is defined
4.Checking group must be defined in Material Master records(it controls whthr the system is to create individual or collective reqmnt)
A combination of checking gropup and checking rule will determine the scope of availbaility check.
Hope this will help.
Thanks,
Raja

TOR & Availability check

can any one tell me the step by step process flow and how the system checks and confirm the ordered quantity and delivery date by using the TOR and Availability check and what is the difference between the RLT and WIth out RLT in the Availability check
Edited by: prasanna_sap on Sep 7, 2010 12:42 PM

Hi,
this common topic
TOR & Availability check
is already discussed many times on forum please read related thread and for steps already a well written wiki is on SDN - [Availability Check (ATP) & Transfer of Requirement (TOR) |http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=29323]
please search the forum before asking already discussed concept. while you can discuss any term or problem which you facing under that concept.
difference between the RLT and WIth out RLT in the Availability check
RLT - Replenishment Lead Time
the concept is nicely explained in this thread - [RLT - Replenishment Lead Time|RLT;
for example go thru this wiki -
[ATP with RLT|http://wiki.sdn.sap.com/wiki/display/ERPLO/AvailabletoPromise+(ATP)]
please let me know your detail scenerio if you are facing any problem.
REgards,
Rajeev

Availability check in make to order

Hi,
Iam in the process of configuring sales order process for one of my finnish customer. The scenario is make to order. Few things are troubling me. I need to know how is the availablity check is done in case of make to order scenario. questions are as follows-
a) The stock is not available since it will be made as and when sales order is created and requirements t/f to PP/MM. So there is no point in switching on availability check in sales order. Only TOR shud be switched on for sales order schedule line. If availibility check is switched off , then there will be no delivery/transport scheduling too or I think i need to switch off delivery/transport shceduling seprarately too since there is no point in calculation of material availability date............ Am i right ?
If you disagree, then why AC needs to be swithced on and what ATP settings shud be flagged( i mean sales requirments, opening stock, planned stock etc) !
b) If you agree that AC needs to be switched off, then how is the stock confirmed in sales order. Is it after production order is made and then the schedule lines are confirmed.
c) If one agrees on both points a and b, then if my customer wants a delivery date after creating a sales order, then how the system will calculate the delivery date in sales order since availibility check and delivery schdeuling both are switched off.
regds

Hi,
If you carry out ATP in MTO,
system will give you probable date of material available date,confirm date,schedule date,
it will not confirm material immediately and give schedule line as like STO.
Kapil

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
Devender

Hello 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

Availability check and Batch Determination

Dear Experts
Would you provide me help documents with screen shots on Availability check and Batch Determination to customize one of our projects
Thanks in Advance
Regards
Ravi

Hi ravi
Check the Availability check and batch configurations .
Availability check and TOR
[https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=29323]
Batch configuration
[https://wiki.sdn.sap.com/wiki/display/ERPLO/Batch+Determination]
[https://wiki.sdn.sap.com/wiki/display/ERPLO/batchdeterminationin+sd]
NOTE : Kindly search the configuration part before posting
Regards
Srinath

Error in Availability Check

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?
thanks

There 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:
Define business transaction
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.
Assign business transaction to sales order type 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,

Availability check & TOR

Similar Messages

Maybe you are looking for