What (action) changed the Planned Order?

[Former Member]

Dears

We always create Planned Orders in APO. We are happy when we see Production Planned Key Figure updated with planned orders with category EE: SNP Plnd Order. I see these planned orders in MD04 instantly. So all is good.

But there are cases where Planned Orders show under Production Confirmed with ATP category AI, for no apparent provocation! Neither in APO nor in ECC. So some event / action elsewhere must be poking it and making it Planned Order AI.

The thing that I see unique is in RRP3 where the application that 'created' the planned order. For one that appears under production confirmed key figure, has a value 2. PPDS order. for the other it is 4- SNP order.

Question:

What made this order a PPDS order when several other planned orders for the same product x location created 100% in APO continue to exist as EE SNP Planned orders under the key figure Production Planned.

I am using standard SNP planning book.

[Former Member]

An action includes "check material availability"

No Material Availability Check is done on planned order

"explode BOM", for example can change it to PPDS planned oreder.

No BOM Explosion is done on Planned Order

Please check if there are any changes in planned order MD12 or PLAF table.

PLAF Table shows creation Date. If you notice for the planned order AI, the PLAF shows it was created on 9/1/2019, 13:01:27 but in APO RRP3 it was created on 9/3/2019, 6:25:37 but under the action control tab in MD13, I see the date of Action = 09/01/2019. Time of Action = 21:01:25 and Action = APCR (means APO Created)

How can the document creation date in APO be latter than the document creation date in ECC? When creation happens only in APO to begin with?

Have you maintained PP/DS horizon

Its zero

or SNP production horizon in product master?

Its zero

transaction /SAPAPO/SNP2PPDS

We do not convert planned orders in APO

or the report /SAPAPO/RRP_SNP2PPDS is used to convert SNP orders to PP/DS orders.

We do not convert planned orders in APO

Planned orders were transferred from ERP, which will assign the APO application "PP/DS" automatically.

Planned Orders are always created in APO and transferred to ERP via CIF

And Planned Order was sent to APO via CIF Deltareport.

Sometimes we user delta report but Planned orders always move neatly and instantly. But may be I can keep a watch.

*****

So issue is I am not able to interpret the 'creation' date and 'Action' date in planned order in ECC and the creation date in APO.

Creation Date and Time in ECC in PLAF table: 09/01/2019, 13:01:27

Action Date in MD13 Action tab: 09/01/2019, 21:01:25

Creation Date and time in APO (GT_IO RRP3): 09/03/2019, 6:25:37

How can Creation Date in APO be later than Creation date in PLAF?

What does Action Date and time later than Creation Date and time mean?

Both systems are in same time zone

No user has touched this order

CIF delta report ?

CFM2 report ?

Something looks out of sequence here ?

Its the same planned order!

Thanks

Amit

[rupesh_brahmankar]

Hello,

This could be due to order was transfer by CCR delta report.

How can Creation Date in APO be later than Creation date in PLAF?

Order first created in APO with local APO number then it goes to ECC and created order with ECC number and then it come back to APO system. By any means if order does not CIF to APO from ECC and then executed the delta CCR report then you can have such difference of creation date and time. This could be also reason that order transferred in PPDS application.

As ECC systems do not know the difference between applications PP/DS and SNP. Both are used in APO only

Initially there is a Planned Order, that was created in APO by SNP application.

For some reason this planned order is missing in APO, which is detected by delta report using /SAPAPO/CCR.

When resending the missing planned order directly from delta report by pressing button 'Send to APO' it will be created in APO with application indicator '2' (PP/DS)

If you want order should be in SNP application then,

You can customer exit EXIT_/SAPAPO/SAPLCIF_ORD_001 there has to be set parameter CF_SNP_PLAF = 'X'.

For further details please refer SAP KBA 2477239 - Application Indicator of SNP Planned Order changed after retransfer from ECC to APO

Best Regards,

R.Brahmankar

[Former Member]

Thanks Rupesh

This sounds very fluid. sticky sticky.

How can say a 'normal' supervisor in the factory understand what happened to the planned order? In normal course of system operations, planned orders are highly likely to be 'confirmed' without the knowledge of the line manager who is responsible to confirming the production by looking at the planned orders.

I mean how do I make a list of 10 activities he/she needs to do?

- Evaluate Planned Production

- Go to MD04

- Click here/ Click here

- Do this. Do that

- Check Capacity. Go there

- Convert Planned order to production order

- Release the production order

.. ..

Now I know why no one likes to useAPO.

Thanks

Amit

[rupesh_brahmankar]

Hello,

Ok, then what is the issue here to have planned order as EE: SNP Plnd Order or AI PPDS planned order?

Best Regards,

R.Brahmankar

[Former Member]

"then what is the issue here to have planned order as EE: SNP Plnd Order or AI PPDS planned order?"

Unless the planned order is manually firmed by the planner in ECC, it should always show in the key figure "Production Planned" in APO SNP planning book. Whatever be the ATP category- EE or AI. Because of programs like CCR that we need to run once a while, some planned orders move to the row production confirmed. Users complain how on earth did it get confirmed when they did not even open it in ECC. It confused the heck out of them.

How do I accomplish this?

Thanks

Amit

[rupesh_brahmankar]

Hello,

If you want order should be in SNP application then,

You can customer exit EXIT_/SAPAPO/SAPLCIF_ORD_001 there has to be set parameter CF_SNP_PLAF = 'X'.

For further details please refer SAP KBA 2477239 - Application Indicator of SNP Planned Order changed after retransfer from ECC to APO

Best Regards,

R.Brahmankar

[rupesh_brahmankar]

Hello,

An action includes "check material availability" and "explode BOM", for example can change it to PPDS planned oreder.

Please check if there are any changes in planned order MD12 or PLAF table.

Change time and user also any action.

Have you maintained PP/DS horizon or SNP production horizon in product master?

transaction /SAPAPO/SNP2PPDS or the report /SAPAPO/RRP_SNP2PPDS is used to convert SNP orders to PP/DS orders.

Planned orders were transferred from ERP, which will assign the APO application "PP/DS" automatically.

And Planned Order was sent to APO via CIF Deltareport.

Best Regards,

R.Brahmankar