BOP sorting to confirmed date

[Former Member]

Hello,

In the past, our sales requirements in the BOP run were sorted based upon their requested date via the standard sort criteria field LFTMS.

Now, we’d like to sort the sales requirements in the BOP run based upon their confirmed date.

For this, we use userexit EXIT_/SAPAPO/SAPLBOP_SORT_020 and fill the field USEREXIT with the confirmed date of the last schedule line of the sales order item. If the sales order item doesn’t have confirmed dates, we set the date to 99991231 (sales order items without confirmed date are sorted at the end of our sorted list). To read the confirmed dates of a sales order item, we use BAPI BAPI_SLSRVAPS_GETLIST2.

Functionally everything is working properly, but we experience some performance issues: the BOP run takes double as long as what it takes when sorting to the requested date.

Most of the time is “lost” in reading the sales order item data via BAPI BAPI_SLSRVAPS_GETLIST2.

Is there a faster way on APO to read the schedule line data for a sales order item, e.g. directly in a table.

The table /SAPAPO/SCHEDLIN only contains the requested date (type O) and the “confirmation, first version” (type C), but not the actual “confirmed date”.

Thanks for any advice.

Best Regards,

Alexander

[babu_kilari4 · Accepted solution]

Hello Alexander,

Confirmed date is nothing but the MBDAT of the order line. Did you try using the field VALIDITY as the sorting criteria ?

Didn't that fulfill your requirement ?

Thanks & Best Regards,

Babu Kilari

[Former Member · Accepted solution]

Hi Babu,

Thanks for your reply!

I also thought that the field "MBDAT" which is available as a standard sorting criteria would correspond to the material availability date of your confirmed schedule line. However, it corresponds to the material availability date of your requested schedule line.

See screenshots for quotation 20062134/10:

- MAV date of requested schedule line = 27.10.2015

- MAV date of the confirmed schedule line = 16.11.2015

If you have a look at the value of the sorting criteria for MBDAT, it contains date 20151027.

The field USEREXIT which we use as our sorting field now is filled with the "last" confirmed date of the sales requirement.

I guess it is not foreseen in the standard sort criteria to sort against the confirmed date as a sales requirement can have multiple confirmed dates?

I don't know what you mean by using field "VALIDITY" as the sort criteria. I don't see this field as a sorting field?

Best Regards,

Alexander

[babu_kilari4 · Accepted solution]

Hello Alexander,

Sorry - The field validity corresponds to MBDAT for ODLs. For BOP, I guess the standard field MBDAT is the right one. But, that is also true that system always looks at the first schedule line because the original design as I understood would be is to improve the confirmation situation of a customer demand element based on first suggested date. I don't see a straight forward solution to your requirement without a custom developments. But, using heavy FMs and BAPIs in the filtering and sorting criteria exits would indeed slow down the BOP performance. Will share if there is anything that comes to my mind

Thanks & Best Regards,

Babu Kilari