Requirement Type & Availability check

Hi all
In our company I would like to use new Requirement type for Spares of Finished product
System should consider the replenishment period mentioned in the material master and give me the availability date . Same time even though there is stock , system should not consider the same because the component may be available for finished product.
Is it possible .? is there any such type of Requirement type available in SAP which will not consider PIR and available stock . But consider the order requirement of spares parts only and give me the availabily based on replenishment period
Please help me in this regard
Malhar

In OPJJ, You can define which stocks have to be considered in availabilty checkand which should not be..
You can even create a new requirement type if needed... and can select the options according to ur requirement..
Also check the tab: in/out movement" here also you have options to exclude materials from consideration...
hope this clarifies..
karthick

Similar Messages

MDVP - Plan order (NB type) Availability check problem

Hello GUru's,
I received one issue, the transaction MDVP does not select the plan orders for Availability check.
DUring my analysis I found that, materials have procurement type is "F". Plan orders are generated by system,
It has order type "NB" (generally our plan order type is LA - stock order).
When user check the plan orders (NB type) in the transaction code MDVP or COMAC, system shows the message
no plan order is available in the system but I checked in the MD12, plan order is available.
What could be the reason, system is showing like this message and not selecting the plan order for coll. Avl check.?
Procurement type is F and plan order type is NB this is the reason?
Kindly help me.
Thanks in advance.

Dear,
Yes collective availability check has only been implemented for in-house production only.
Order type NB with F will be for the subcontracting. Also the collective availability check (Transaction CO28, MDVM) takes no subcontract orders or subcontracting purchase requisitions into account.
If you want planned orders with special procurement subcontracting into account during the collective availability check then you need to activate the modification, set the variable MOD_SUBCON to 'X' in the include PPIOHF02 after the implementation.
For more details refer the OSS Note 198398 - Collect. availability check w/o subcontracting planned ords.
Regards,
R.Brahmankar

Disable Availability Check Based on Sales Order Type

Hi All SD experts,
Usually ( correct me if i'm wrong ) availability check is set via schedule lines item type. Is there any way that I can disable the availability check based solely on Sales Order Type ? Meaning no matter what item category or schedule lines assigned to materials, availability check will still be disable.
Besides setting in schedule lines type, what are others config that might trigger availability check ? MRP settings ? Movement type ?
Any valuable feedback will be great and much appreciated. A big thank you in advance.
Warmest Regards,
Edie

HI EDIE
    In order for the availability check to happen,the following configuration settings are required.
Availability check:
     a) you have to define requirement class & requirement type.
     b) you have to activate at scheduline category level
     c) in deleviry item.cat ,there is availability check off field,,,,, if u dont mention any values here,then system checks for availability.if u mention 'x' here,then system dont check for availability.
    d) you define checking group and checking rule ,these determine how availability check is going to be performed
MRP:
   MRP determines how material is planned,whether it is inhouse production or external procurement.MRP also determines the time taken for the material to become available for ready use.When ever an order is rised,the requirement is passed to MRP through transfer of requirements(TOR), here MRP determines the inhouse production time or external procurement time.
Movement Type: Movement type determines the type of material movement ,whether it is Goods Issue ,,, or ,, Goods Recipt,,,,, stock transfer between two plants etc.Movement type is determined in schedule line category level.
                  Award points if it is useful
                    Prasad.G

Sales order availability check considering the ROH stock/procurement time

Hi Gurus,
Our client's Production process requires the availability check at order level to consider the procurement time required for the Rawmaterial (BOM component of the FERT, whose sales order is taken) in cases when this RM is not available in the plant, and Availability check should not consider this procurement time when this RM is available in the plant.
ie in first case, it should consider the total time for in-house production as well as the time required to procure the rawmaterials, along with all other times that we use like Gr processing time, packing picking etc.
In second case it should not consider the RM procurement time, but only the inhouse production time and other times as applicable.
To my understanding, Availability check at order level will only check the time given in the MRP view of the FERT, and it does not check anything about RM stock or RM procurement time.
Can you please give me some suggestions to meet this requirement of the client (client is into Food Product Manufacturing).
Your quick response will be very helpful
Thanks
Jobi

Jobi,
Our client is not following Assemble to order or even make to order. The typical production process followed is neither make to order nor make to stock.
Understood, although I am not sure why you are telling me what he has today; since your client has already told you his existing solution is unsatisfactory. I have described a solution that seems to meet the short list of business requirements that you described in your first post. I suggest you offer this solution to your client, unless he has already told you that ATO is not acceptable for some other reason not mentioned in your post.
As already mentioned by the other experts Saurabh and Kiran and Mariano, the requested functionality in general is not supported for MTS in standard ECC. As always, anything is possible through enhancement or 'workaround', as long as the client has enough time and money, and you have sufficient skills to implement.
If the client is willing to implement APO, which is the standard SAP advanced planning system, such a solution (multi-level availability checking with MTS) is possible as standard. Within the Global Available To Promise Module of APO there are a couple of ways to get at this type of ATP solution.
Best Regards,
DB49

What is the relation between req type and checking group

Could any1 please explain me the link between requirement type and checking group?
Also please throw some light on the other terms in ATP like requirement class and checking rule.
Thanks in advance

Dear VGR,
The requirement type refers to the origin type, for example, goods receipt for purchase order (Type B) or goods issue to cost centers (Type K).
The criterion that groups together all checking rules for all application areas for a material.
In conjunction with the checking rule, the checking group 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.
Checking rule
A rule that defines how the availability check is performed.
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 included in the availability check and whether the check is performed with or without the replenishment lead time.
I hope this will help you,
Regards,
Murali.

Disable Availability Check on Sales Order But Activate on Outbound Delv

Greetings all experts !
Currently, there's a new request to create a new processes whereby during the sales order creation, no availability check will be in place but material will still be posted to production planning ( TOR ).
Availability check instead should be activated during the creation of outbound delivery.
I have already configured in such a way that the relevant sch line item ( VOV6 ) - availability check is unchecked and TOR is checked.
But during creation of sales order, availability check is still in place for material specified.
I have check on the necessary requirement class and requirement type settings. Fyi, requirement class used - availability check is ticked. Could this be the reason even though i have disabled availability check on sch line ?
I have tried to untick the availability check setting in requirement class ( OVZG ), and while this can disable the availability check in Sales order, but that configuration will also disable availability check in outbound delivery.
My queries :
1 ) What are the configurations that I need to look into to cater to the above request. To disable availabilty in sales order but instead, run availability in outbound delivery ?
2 ) Is there any way I can disable the availability check on based on sales order type using userexit or function module ?
3 ) Is there any additional function module/bapi/userexit that i can implement to force outbound delivery to run availability check ?
My apologies for such lenghty message here but really really need some valuable feedback here as I'm totally at lost with the new requirement for now.
Many thanks in advance.
Warmest Regards,
Edie O

In SPRO
goto SD>Schedule line>Define schedule line categories
here check if the schedule line category associated with your mentioned order has a flag ticked for Availability.
Availability check for sales
You must carry out an availability check for the following transaction.
The indicator is determined as a proposal in conjunction with the respective requirements type. It can be changed in individual shipping transactions. However, only one restriction is effective.
Example
You do not set an indicator for maintaining the requirements type. In this case, no availability check is carried out. This is independent of the selection in the respective transaction.
You set an indicator for maintaining the requirements type. In this case you can decide whether or not you require an availability check for the relevant transaction.
reward points if it helps
regards
Biju

Requirement Type not populated in Sale Order

Hi,
In our sales order a requirment type 041 is not getting populated into the sales order for one particular item category.
Regards,
Jagan

Requirement type determination in standard SAP is performed using a six-level hierarchical
sequence:
1. First, SAP tries to determine the requirement type using the strategy group from
the material master record.
2. If the strategy group is not maintained, SAP determines the requirement type
using the MRP group from the material master record.
3. If this is not maintained either, the SAP system determines the requirement type
using the material type from the material master record.
4. If this also fails, the SAP system determines the requirement type using a combination
of the item category and MRP type.
5. If this rule is not maintained, the SAP system at last tries to determine the
requirement type using the item category itself.
6. If no requirement type is found at this level, the system treats the transaction
as not relevant for the transfer of requirements or availability check.
Regards
Deb

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

SD Availability check for item

Hi,
during the change of an on order the system not always executes availability check after my changes. So in userexit MV45AFZZ I'm trying to enforce SAP to execute it, but how should I call standard availablity check (CTRL + F5 in VA02) ?
Marek

Hi,
Welcome to SCN!!!
This can be achieved by customization. No special coding is required. Availability check can be triggered automatically on changing the order. Please ask your SD functional consultant to check the customization.
Thanks,
Vinod.

Authorization Object - Availability Check in Sales Order

Hi,
Restriction is required for availability check (i.e. button 'check item availability') in sales order for a given user.
Is there authorization object to control the same ?
Regards,
RS

Hello RS,
Availability check is controller by FM AVAILABILITY_CHECK_CONTROLLER and there is no authority check in it. As per previous reply you can add additional checks in user exit EXIT_SAPLATPC_001 which is called before an atp is run.
Thanks
Amber

Availability check in PM order

Hi,
In a PM refurbishment order with components, when I press the 'Availibility Check' button before release of the order, I am getting the message "No check exists for planning (item: 0010, mat.:XXXXX" (Message no. C2119). I have already maintained the configuration for the plant and the order type in Maintenance and Service Orders-Functions and settings for order types-Availability check for material, PRTs and capacities-Define inspection control as 1 (Check during order creation) and component check type as 1 (check against preliminary planning) and collective conversion as 1 (User decides on creation if material is missing) for material availibility. Checking rule is PM (Checking rule for plant maintenance).
Please tell me what I am missing and what additional configuration I need to maintain. Our business purpose is to ultimately perform an ATP check before the components are committed from the warehouse for consumption after order release. But before that I need to ensure that the availability check is working correctly and not giving error as above.
Thanks and regards,
Abhijit

Hello
You have to mantain the additional Availabilty Check 02 for 'Release' control parameters
Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Maintenance and Services Orders-> Functions and Settings for Order Types -> Availability Check for Material, PRTs and Capacities -> Define Inspection Control.
Then
Availabilty Check 02
Checking Rule:Which your using earlier
Release Material:2
Regards,
Rakesh

Availability Check in VC

Hi Experts,
I am a SD Consultant ..and have started working with VC functionalities lately...had a question on AC for component items of the configurable material. How do we control AC for a configurable material at the sales order level? As far I know, we need to have the components availability check activated at the configurable profile level...in case, we have it checked will it trigger TOR and AC for ALL components?
Thanks,
Mandeep

Dear Mandeep,
The check box "component availability" in the configuration profile has nothing to do with the TOR or AC in a sales order. If this check is enabled, then during configuration simulation, a push button "Availability" will be displayed. If you click this it will show the component availability.
It is just for a quick check to see if the components required as per the characteristic value selection, are in stock or not.
In the sales order, system will consider the TOR , AC as per the settings maintained for the requirement class & Availability check control.
Regards,
Senthilkumar SD

Regarding skip the availability check in BAPI_PO_CREATE1

Hi Abapers,
Can you suggest any enhancement, to skip the availability check in function module BAPI_PO_CREATE1?
(My requirement is, availability check should not be triggered, because delivery has been completed already).
Regards
Subash
Edited by: subash Arthanari on Dec 2, 2008 10:56 AM

u can pass field Delivery Completed" Indicator
structure BAPIMEPOITEM
field NO_MORE_GR
like:-
wa_item-material = p_matnr.
wa_item-plant = '3200'.
wa_item-quantity = 100.
wa_item-conf_ctrl = 'Z01'.
wa_item-ACKN_REQD = 'X'.
WA_ITEM-ERS = ''.
wa_item-NO_MORE_GR= 'X'.
APPEND wa_item TO it_item.
wa_itemx-po_item = p_int.
wa_itemx-material = c_x.
wa_itemx-plant = c_x .
wa_itemx-stge_loc = c_x .
wa_itemx-quantity = c_x .
wa_itemx-item_cat = c_x .
wa_itemx-acctasscat = c_x .
wa_itemx-conf_ctrl = 'X'.
wa_itemx-ACKN_REQD = 'X'.
WA_ITEMX-ERS = 'X'.
wa_itemx-NO_MORE_GR= 'X'.
APPEND wa_itemx TO it_itemx.

Availability Check for Mov.type

Dear All,
Can we configure Availability check for Mov.type?? If yes what are the settings to be done??
Points will be awarded!
Regards,

Hi,
Thanks a lot for the quick response. As you have mentioned I have done the above steps. Now I have doubt that actually my requirement is to activate the Dynamic Availability check for a Mov.type. So in the above transactions OMCM & OMCP in the mov type tab we have a Dynamic Availability check Column where we can set the message as Warning, Error etc..
As per your above points If I assign the check rule to my transaction code system will do Availability check when I execute the transaction irrespective of material.
So Do I have to do the above step? Or shall I assign the Checking Rule to my mov.type in OMJJ ( update Control) tab?
Kindly reply your valuable suggestions?
Regards,

Availability check box at schedule line level and requirement class level

Hi All
What is the significance of availability check field at schedule line level and requirement type level.
If I remove the check box at schedule line level, then there won't be any availability check carried out in the sales order, even though in requirement class it is checked. Is it for doing availability once the requirement is passed to MRP...
In make to stock scenario, no availability check is active at schedule line level.
scenario 1. stock is 0 in plant, when i place an order for 10 quantity, does system give any confirmed quantity on so and so date...or the confirmed quantity will be zero or as there is no availability check carried out, it confirms 10 quantity on customer requested delivery date and the time of creation of delivery, it gives an error message stating zero quantity is available. which one is correct in all the above.
In make to order scenario, no availability check is active at schedule line level.
order was created for 10 qty, as there is no availability check active, does the system give some date based on the lead times maintained in the material master or not?
Regards
Sree

Hi sreekar
The significance of availability check at schedule line level is to determine weather availability check and TOR should be carried out for sales orders or not.
If you remove check box at schedule line level , availability check and TOR wont be carried out at sales order level.
Coming to the scenario you said , make to stock , i think the availability check you are using is 01 make it 02. which is planned requirements. and stratergy group as 10. in MRP3 view in MMR. .
as the availability check u have put 01 & stratergy group as 10 availability check doesnt carry
coming to the scenario 2 , if the stock is 0 in plant and if you create a sales order, then the confirmed quantity should be 0 and that particular order will go to backorder processing.
sometimes it confirms the ordered quantity as the confirmed qunatity, and it gives a confiremed delivery date on which the stock is confirmed , but that date is a tentative date.
all these unconfirmed orders will go to backorders. once the qunatity is confirmed automatically , delivery date also will be done
Coming to scenario 3 , when you create MTO order there will be availability check checked at the schedule line level. can you tell wat is the schedule line you are getting is it CP or ND?
for schedule lines , ND - no availability check will be there , PD - availability check will be there
Note: plz check 1st the availability check you have entered in MMR , if it is 01 make it as 02. and then run these cycles.
Reward points if useful and if Any queries let me know
Regards
Srinath
Edited by: sri nath on Mar 21, 2008 7:53 PM

Requirement Type & Availability check

Similar Messages

Maybe you are looking for