Forecast Consumption Issue

[Former Member]

Hi gurus, I have an issue about forecast consumption when sales order coming in. I'll try to explain it as clear as I can.

Cuz we doesn't use SAP R/3 as our OLTP system, so we have to pass our sales order and sales history from JDE ERP to APO through BAPI. Daily We get sales orders into SCM-APO and consumption happens for these orders against forecast which is released from DP. Once these sales orders are closed that means goods got issued against this sales order, How can I deal these sales orders to disappear in the product view and remain consuming the forecast number(From Allocatec Qty to Withdrawal Qty)?

My current situation is: I set ATP category, BR & BM in the category group "K01" and use BAPI to transfer our sales orders and it will consume the the forecast. But when the sales order is closed(shipped out), I try to use BAPI to change the ATP category of sales order to be "BR". Then the consumed forecast is coming back and increasing my forecast.

I want these sales orders to be disappeared(Cuz they are closed right now) in the product view and remain consuming the forecast number(From Allocatec Qty to Withdrawal Qty)?

Please guiding me,

Thanks in advance.

Regards,

Scott Chen

[former_member788297 · Accepted solution]

Hi Scot Chen,

Two steps involved during Forecast Consumption. It needs to be differenciated

between

a.) forecast consumption

b.) forecast reduction

a.)

The forecast consumption that I mean is

It is done using BAPI_SLSRVAPS_SAVEMULTI. That means if you have a

forecast of 200 and you creat a sales order with quantity 5

using BAPI_SLSRVAPS_SAVEMULTI, then the forecast will be "changed"

to 195. But this is no permanent reduction. It is only there

because the forecast qty + sales order qty together are the

"previous" forecast. "Not permanent" means, that this is only there

as long as the sales order quantity is there. That means if you

change the quantity to 10 (maybe customer now wants 10 instead of 5)

or the sales order is deleted (maybe because the customer cancelled

the order). So in case of changiing to 10, the forecast will be shown

as 190 and in case of deletion it will be back to 200. This is

abolutely ok as otherwise (if you would immediately and permanent

change the forecast qty) the result would be wrong.

b.)

This is the process after e.g. the sales order is "completed" (not

cancelled or deleted). That means the qty of 5 gets shipped to

the customer. As this also will result (one time) in a deletion of the

sales order, you need to tell the system, that now the forecast needs

to be reduced (permanently) and that it is now 195 rather then 200.

Typically this is done together with a goods issue (but could also be

sometime different, dependant on your scenario).

This can be done using /SAPAPO/CIF_IRQ_REDUCT_INBOUND.

Also the quantity is incremental and not absolute! (e.g. as you

can also issue a reversal and also as a GI is done incremental).

So you need to differenciate between a.) and b.)

You also should not call b.) while and sales order from a.) is still

there as then the forecast qty will be too low (as e.g. the sales

order consumes the forecast and you at the same time reduce the

forecast).

In your scenario you need to decide:

- when and how you call BAPI_SLSRVAPS_SAVEMULTI (e.g. to

consume forecast)

- when to delete the sales order

(e.g. BAPI_SLSRVAPS_DELEMULTI)

- when to adjust the stock (e.g. BAPI_STSRVAPS_SAVEMULTI)

- when and how to call /SAPAPO/CIF_IRQ_REDUCT_INBOUND to

permanent reduce the forecast.

Regards,

Chava

[kenneth_snyder]

You need to investigate how APO stores the goods issues...

There are tables that maintain these values.

I will do some research and let you know what I find out.

Ken Snyder