Fair share logic in Backorder Processing - APOBO040 -

[Former Member]

We are thinking to use backorder processing in GATP process. However, one of the expectations of our customer is "fair share logic" during the confirmation of sales orders. Let me clarify what I mean:

1- We have following sales orders in hand with the mentioned sorting.

_________Req. Quantity

SO1________20 pieces

SO2________20 pieces

SO3_________1 piece

SO4_________1 piece

2 - Assume that the total of our stocks and planned orders are 40 pieces. Then the system will give confirmation to the orders as follows:

__________Req. Quantity______Confirmed Quantity

SO1________20 pieces___________20 pieces

SO2________20 pieces___________20 pieces

SO3_________1 piece____________No confirmation

SO4_________1 piece____________No confirmation

3 - However we want to achieve such a confirmation distribution.

__________Req. Quantity______Confirmed Quantity

SO1________20 pieces___________19 pieces

SO2________20 pieces___________19 pieces

SO3_________1 piece_____________1 piece

SO4_________1 piece_____________1 piece

As we have seen from the in the customizing of APO this is somehow possible with the user exit "EXIT_/SAPAPO/SAPLBOP_040" - scope of check-

(APO Customizing / GATP / Enhancements / Backorder Processing / Define Scope of Check for Batch Backorder Processing)

Do you have information about this topic, have you tried this solution before, is it working???

If anybody can help, we really appreciate.

Thanks in advance and Best Regards

[Former Member · Accepted solution]

Hello There,

We have a similar requirement like the one below .. Were you able to do that In the User exit EXIT_/SAPAPO/SAPLBOP_040 that says can be used for fair share ??

The last line in the documentation below says that "This is only possible for the basic methods product availability check and product allocation."" ....

Can I implement the same for Rules Based ATP .. actually we are using Rules Bases Sustn in cunjunction with BOP.

Please let me know if u were successfull in doing fair share by the user exit.

Regards,

Amit -- amit.chug@gmail.com

> We are thinking to use backorder processing in GATP

> process. However, one of the expectations of our

> customer is "fair share logic" during the

> confirmation of sales orders. Let me clarify what I

> mean:

>

> 1- We have following sales orders in hand with the

> mentioned sorting.

> _________Req. Quantity

> SO1________20 pieces

> SO2________20 pieces

> SO3_________1 piece

> SO4_________1 piece

>

> 2 - Assume that the total of our stocks and planned

> orders are 40 pieces. Then the system will give

> confirmation to the orders as follows:

>

> __________Req. Quantity______Confirmed Quantity

> SO1________20 pieces___________20 pieces

> SO2________20 pieces___________20 pieces

> SO3_________1 piece____________No confirmation

> SO4_________1 piece____________No confirmation

>

> 3 - However we want to achieve such a confirmation

> distribution.

>

> __________Req. Quantity______Confirmed Quantity

> SO1________20 pieces___________19 pieces

> SO2________20 pieces___________19 pieces

> SO3_________1 piece_____________1 piece

> SO4_________1 piece_____________1 piece

>

>

> As we have seen from the in the customizing of APO

> this is somehow possible with the user exit

> "EXIT_/SAPAPO/SAPLBOP_040" - scope of check-

> (APO Customizing / GATP / Enhancements / Backorder

> Processing / Define Scope of Check for Batch

> Backorder Processing)

>

> Do you have information about this topic, have you

> tried this solution before, is it working???

>

> If anybody can help, we really appreciate.

>

> Thanks in advance and Best Regards

[Former Member]

I dont know If you have gone through this document:

The lines in bold explains clearly uptill what extent you can do the FAIR SHARE RULE.

I believe we cannot do <b>EXACTLY</b> what you have stated in your example.

Availability Check is the core for comfirmation of a sales order.

Whatever customizing you do in the user exit, donot attemp to do your own availability check logic...

GOOD LUCK and let us know when you have done the coding.

*************************************************************************************

<b>EXIT_/SAPAPO/SAPLBOP_040 :</b>

ATP, BOP: Scope of Check for Backorder Processing Functionality

The user exit is called in backorder processing before the availability check is called.

The requirements to be checked and the correction quantities of the separate basic methods are transferred to the function module.

Depending on the settings for backorder processing, the requirements to be checked are either the original requirement (requirement check) or the current confirmation of the document (confirmation check). Scheduling has already been performed (according to the settings for the check parameters).

The requirements are transferred into four tables. The contents of these tables are linked to each other by indexes.

<b>The requirements to be checked can be changed, for example, if you want to implement a fair share logic. Changing the requirements has no effect on the quantities originally required in the documents. <u><i>The change only limits the maximum quantity you can allocate to a document.</i></u>

The correction quantities are determined for each basic method. By reducing the correction quantities you can prevent the total quantity being divided between the documents to be checked.

You must not change the adjustment entries for planning.</b>

***************************************************

APOBO040 scope of check:

Scope of Check for Batch Backorder Processing

The function module EXIT_/SAPAPO/SAPLBOP_040 is called before the availability check in backorder processing. The documents have already been selected (filter) and sorted.

Environment

The requirements to be checked and the corresponding correction quantities of the individual basic methods are transferred to the function module.

By changing (reducing) the requirements, a fair share logic can be implemented using this function module.

By changing (reducing) the correction quantities, quantities can be protected from distribution via backorder processing. This is only possible for the basic methods product availability check and product allocation.

Message was edited by:

Kumar Ayyagari

[Former Member]

Hello there, This is in refrence to the doc posted in the link

I actually have the same requirement and want to implement the fair share logic by using the below mentioned User Exit... .But the last line in the documentation below says that "This is only possible for the basic methods product availability check and product allocation."" ....

Can I implement the same for Rules Based ATP .. actually we are using Rules Bases Sustn in cunjunction with BOP.

Please let me know if you any idea about this fair share ?? Can this be done ??

Regards,

Amit -- amit.chug@gmail.com

> I dont know If you have gone through this document:

> The lines in bold explains clearly uptill what extent

> you can do the FAIR SHARE RULE.

>

> I believe we cannot do <b>EXACTLY</b> what you have

> stated in your example.

> Availability Check is the core for comfirmation of a

> sales order.

>

> Whatever customizing you do in the user exit, donot

> attemp to do your own availability check logic...

>

> GOOD LUCK and let us know when you have done the

> coding.

> ******************************************************

> *******************************

> <b>EXIT_/SAPAPO/SAPLBOP_040 :</b>

>

> ATP, BOP: Scope of Check for Backorder Processing

> Functionality

> The user exit is called in backorder processing

> before the availability check is called.

>

> The requirements to be checked and the correction

> quantities of the separate basic methods are

> transferred to the function module.

>

> Depending on the settings for backorder processing,

> the requirements to be checked are either the

> original requirement (requirement check) or the

> current confirmation of the document (confirmation

> check). Scheduling has already been performed

> (according to the settings for the check

> parameters).

> The requirements are transferred into four tables.

> The contents of these tables are linked to each other

> by indexes.

> <b>The requirements to be checked can be changed, for

> example, if you want to implement a fair share logic.

> Changing the requirements has no effect on the

> quantities originally required in the documents.

> <u><i>The change only limits the maximum quantity you

> can allocate to a document.</i></u>

> The correction quantities are determined for each

> basic method. By reducing the correction quantities

> you can prevent the total quantity being divided

> between the documents to be checked.

> You must not change the adjustment entries for

> planning.</b>

>

> ***************************************************

> APOBO040 scope of check:

>

> Scope of Check for Batch Backorder Processing

> The function module EXIT_/SAPAPO/SAPLBOP_040 is

> called before the availability check in backorder

> processing. The documents have already been selected

> (filter) and sorted.

>

> Environment

> The requirements to be checked and the corresponding

> correction quantities of the individual basic methods

> are transferred to the function module.

>

> By changing (reducing) the requirements, a fair share

> logic can be implemented using this function module.

>

> By changing (reducing) the correction quantities,

> quantities can be protected from distribution via

> backorder processing. This is only possible for the

> basic methods product availability check and product

> allocation.

>

> Message was edited by:

> Kumar Ayyagari