Process Order Availability Check Setting

[Former Member]

Dear Team

I have scenario that the material BO* is the part of IO* BOM.

Now I am creating & releasing the process order of BO* but no confirmation, No GI, No GR. Only Release & Save. Here i will get one Batch Number for BO*..

Now I am creating the process order for IO* & doing availability check but error of stock not available. I am expecting the stock come from process order of BO* will get assign to IO* before confirmation of process order of BO*. Will it possible to do in SAP?..

Setting Available-

We have Batch Search Strategy in place

We have Batch determination

We have logic of same batch number carry forward from BO* to FG...

Eg... BO* Batch is 870AB001 then IO* batch is also 870AB001 base on available stock assignment.

Tried at my end..

Change is made in availability check setting & Inc. Production order ="X" (Take all production order into account).

But no benefit.. Still system shows missing material stock error in IO* process order.

Please guide, how I can achieve it?.

[kiran_kumar179 · Accepted solution]

Girish,

First thing you need to ensure you BO* and IO* have same checking group assigned in MRP3 view and In OVZ9 for order Creation and Release with above checking group and Checking rule combination you have included to consider all open orders.

Also check BO* order completion(material availability) date is with in IO* order release date(component available date)?

BR
KK

[Former Member · Accepted solution]

Dear Team

Now I have made changes i OPJK.. Here I made changes in material availability "Release Material=2" & Batch Assignment "Release Material=2". Now system is asking for batch but here i have to put manually the batch of BO*.. Will it possible that system suppose to pick automatically rather asking for manual batch assignment. Please guide..

For reference screen shot of OPJK is attached.

[kiran_kumar179 · Accepted solution]

Girish,

What happened to your initial original issue is that resolved?

BR

KK

[Former Member · Accepted solution]

No.. It is in addition to same.. I made some selection change now in OPJK.. Here now system allow me to assing the batch manually but not doing it in automation as per availability check process.

[Former Member · Accepted solution]

No.. It is in addition to same.. I made some selection change now in OPJK.. Here now system allow me to assing the batch manually but not doing it in automation as per availability check process.

[Former Member · Accepted solution]

Hi Girish,

Basically, the released production order of BO* should be considered when the material availability check is carried out while saving the production order of material IO*, if this is so, then I feel the scope of check maintained is correct but the rescpective checking group needs to be assigned in the material master of BO*, the above screen shots shows, that you have assigned the checking group to material IO*.

Could you please confirm on this, whether you have assigned the checking group to material BO* as well.

Regards,

Chinna.

[Former Member · Accepted solution]

Yes I have maintain the checking group is same for both the case. For more detail please consider below comment also for batch logic work.. I am not sure but is there anything that i am missing to maintain? If you feel then please guide me step by step.. I will check all cases.

Below screen shot attached for activity done at my end..

1) New Order type created

2) New prod. scheduler group created with assignment of order type for default order type while creation of process order.

3) Order type dependant parameter also maintain as perrequirement.

4) New Checking group is created

5) Checking rule also defined

6) Scope of check also maintain

7) Order control also maintain.

😎 In material master the checking group is maintain for BO as well as IO.

[Former Member · Accepted solution]

Hi Girish,

All your config settings sounds good. Now what is the issue, because the original post is associated with availability check but where in then later, it swithced to automatic batch creation and splits

With this configuration settings, system should consider the BO order as reciept element and should not list this material in missing parts. also an auto batch determination should takeplace.

Regards,

Chinna.

[Former Member · Accepted solution]

Dear Here system is not considering the BO process order as receipt element & providing message of material shortage, why so? Is there any mistake done at my end in this configuration?

[Former Member · Accepted solution]

Hi Girish,

Still, if system is listing the material BO* in missing parts list, then probably the production order finish date is later than when it is actually required by the order of material IO*.

For example,

According to the production order of IO*, the component BO* might be required on 12.10.2014, but the production order of BO* could have a finish date or date available for planning later than 12.10.2014.

Could you please post the screen shot of missing parts list of order IO*.

Regards,

Chinna.

[Former Member · Accepted solution]

Dear, please find screen shot for dates.

BO process order finish date is 30.09.2014

IO Process order start date is 08.10.2014.. Then also missing part error.

[Former Member · Accepted solution]

Hi Girish,

Though the order 45540 of BO* is completing on 30.09.2014, but it is not comitted to the order which you are creating for material IO*, probably the quantity of 45540 has been used for some other pegged requirement.

For the order which you are creating for material IO*, the BO* material is comitting on 14.10.2014, but where in the requirement is on 08.10.2014, that is the reason system is listing this material in missing part list. This is clear from the screen shot of missing part list.

Could you please post the screen shot of MD04 for the material BO*?

Because it is necessary to check is there any demand or pegged requirement in between 30.09.2014 and 08.10.2014.

Regards,

Chinna.

[Former Member · Accepted solution]

Dear As desired. Pleas find screen shot of MD04 for BO

[Former Member · Accepted solution]

Hi Girish,

From MD04, it is clear that though the finish date of process order 91210045440 of material BO* is 30.09.2014 but it is available for planning only on 14.10.2014. This is the only reason for system to list the material in missing parts list.

So, it is necessary to check why and how system is picking the date 14.10.2014 for which the production finish date is 30.09.2014. The possibilities could be "Schedule margin key" - But I could see that SMK is 000. So, here I am not sure on other places where we can provide float to process orders. Check any planning calendar are assigned to the BO* material or any time phased planning is activated for this material or check any queue time is maintained for last operation of the material BO*

For ex, if you rescedule the BO* order, in such a way that in MD04 the date should be 8.10.2014 or earlier, then system will not list the material in missing parts. Or it is possible by creating the order for IO* later than 14.10.2014 start date.

Regards,

Chinna.

[Former Member · Accepted solution]

Hi Girish,

Did you try re-scheduling any of the orders and any luck on finding why the order is available on 14.10.2014 while finish date of the order is 30.09.2014. Because I am intrested to understand the system behaviour behind determining the available date.

Regards,

Chinna

[Former Member · Accepted solution]

Dear Chinna

Thanks for your help.. After changing date i got the auto batch detect in IO.. But still i am struglig to get the reason for 14.10.2014 date.

1) Zero Float in material master

2) Zero queue time as well a move time in work center.

3) Unable to locate the queue time field in recipe. In routing this filed appear but recipe unable to locate.If possible please guide with screen shot..

[Former Member · Accepted solution]

Dear Chinna

The date 14.10.2014 becuse of GR processing time is 14 days maintain in material master.. Thanks a lot.. Now I am adding the schedule margine key with 15 days as float before production

[Former Member · Accepted solution]

Hi Girish,

A very wild guess, as your business scenario is dealing with batch management, could you please confirm that any "minimum remaining shelf life" has been maintained for the material BO* in material master under the tab "Proddata/Stor1".

If you want to see the queue time in recipe then double click the operation or phase and under standard values, this should be available, but you can check this in production order itself.

Regards,

Chinna

[Former Member · Accepted solution]

Hi Girish,

I did not see your latest post. Thats great to hear from you.

Have a nice day ahead.

Regards,

Chinna

[maheshkumar_komatineni]

hi Girish,

if your requirement is to consume the sub assembly directly without doing GR and Confirmation then you need to maintain Special procurement key 52 in your BO* material master MRP 2 view you need to tick collective  order in your order type (OPJK).

you need to raise PRD ord fot you IO* system automatically creats order for BO* use use it in IO*

Regards,

Mahesh.

[Former Member]

Dear we have Batch management with logic of batch carriforward from BO to IO. For Example IF BO batch number is 870001 then IO batch number must be 870001A ( A indicate the split) hence the BO process order is first activity to get the batch number for further process order, I am not aware how collective order scenario will work in this case. Please guide me in more detail, if you feel the collective order will work for me with keeping above scenario as it is...

[former_member215620]

Dear Girish M,

I think you can use collective order in this case.

Regards,

Saurabh Kumar

[Former Member]

Dear I think for collective order also need same setting of available check.. Will you please guide on this. Screen shot added for more detail.

[dejoy]

Hello,

checking indicator Include Prod Order is ok. Have you assigned correct availability check into material master? Please share OPJJ snap of your availability check.

Regards,

[dejoy]

another case would be that you have "include dep reservation" checked in OPJJ and you have another older order for IO* created/exist already.

Regards,

[Former Member]

[Former Member]