Disable Availability Check on Sales Order But Activate on Outbound Delv

[Former Member]

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

[Former Member · Accepted solution]

You should have the availability checked at the requirements level. You should uncheck at the schedule line level. This way system will not do an availability check in the sale order.

Despite these settings if availability check is being carried out in SO, check the schedule line category that is determined.

In the delivery item category you can control whether availability check should be carried out at the time of creating the delivery document. Make sure that you have availability check switched on in your delivery item category.

For the different sales document type trigger a different item category so that you can assing different shcedule line categories for the respective item category. In one of the schedule line categories you can stop the availability check. If this is not feasible then you can trigger the different schedule line category usning the exit USEREXIT_MOVE_FIELD_TO_VBEP present in include MV45AFZZ.

I dont think there will be any need to use exits to trigger availability check at the time of creation of delivery document if you use the procedure mentioned above.

Regards,

GSL.

[Former Member · Accepted solution]

Hi GSL,

Thanks for the input.

To further elaborate, in requirement level, availability is checked whereas in schedule line ( Z1 ) - availability is not ticked. Delivery item category ZTAN is with availability check in place.

Problem is during creation of sales order for a material with the schedule line Z1, availability is still being proposed even by right, it shouldn't.

Do you have any idea what could be the root cause here ?

Regards,

Edie

[Former Member · Accepted solution]

Edie,

There should not be any availability check happening in your SO if the av.check is deactivated for the schedule line category Z1 (hope Z1 is really being determined in the SO). Despite this if av.ch is happening then there might be some exits running the back ground which you might not be aware of. Please check that.

Regards,

GSL.

[Former Member · Accepted solution]

Hi GSL,

Sorry for the late reply. Yeah, initially, that's what i understand. Once sch line is marked as unchecked availability, by right availability check for a particular material with that sch line will be off. But it is still running.

I've done some additional config - creating new requirement class and type and assigned it accordingly. It was able to resolve the issue but I'm worried what will be the impact of a new requirement class and type introduced.

Warmest Regards,

Edie

[Former Member · Accepted solution]

Be careful when using new requirements class and type. I hope all the assignments are done as per the earlier requiremnts class and type. If it is Make to Order then ensure that FICO related settings are also done properly in the requirements class.

If creating a new requirements class and type has solved the problem then probably user exit might have been used which is reading the requirements class/type and activating the av.check irrespective of the setting in the sch.line category.

Regards,

GSL.

[Former Member · Accepted solution]

Hi GSL,

You are really the man ! Really really appreciate the feedback. I'm currently asking the abaper to check for any userexit created.

As for now, thanks once again for the valuable feedback.

Cheers,

Edie