How to Change Component on a SNP Planned Order ( Just 1 time )

[Former Member]

Hello,

We are trying to change a component on a SNP Planned Order just 1 time.

So we do not want to change the PDS since this is one time change only.

We tried changing it in R/3. Once we do that, R/3 shows new component but APO still shows dependant demand on old component ( May be because APO SNP Planned order is still connected with the PDS ) .

Then we went to APO and tried to change the component in /sapapo/rrp3. Here you can delete the old component but doesn't let me add new component.

Next thing we tried was to convert it to PPDS Order. Once converted, we went to change mode and tried to remove old component and add new component. It lets me do this. Only issue with this route is that, it puts correct start and end dates on the order dependning on the order quantity and so order moves the dates which we do not like.

Is there any other better way to fix this issue ?.

Thanks.

Ketan Doshi.

[somnath_manna · Accepted solution]

Unfortunately not.

SNP does not allow you to change component.

If its a Planned Order created in PPDS then you can add/delete/change components and to reasonable extent the schedule (operation start and end dates) - but this functionality is not possible in SNP.

To change the schedule of PPDS order in past you need to get in Planning Board with a Time Profile having negative offset. This will allow you to move the operation/order in past.

Note all this is possible only for a Planned or Production order in created status. Subsequently R/3 takes over any Production Order changes.

Hope this helps.

Somnath

[srinivas_krishnamoorthy]

This being a very unique requirement, I would use one-off approaches usually not followed. You may need to explore the use of BAPI BAPI_MOSRVAPS_CREATESNPORDER. This will help you point the source of planned order to a PPM or a PDS that you may want to create in APO system on a one-off basis. PPMs can be maintained in APO, however PDS are usually CIFed from R3. You can try to create PDS (based on the new component) in APO system only using backend tables. Try do some little research on /sapapo/curto tables to create the PDS in APO. Then use the BAPI to point the source to this new PDS. (better you also try the PPM approach since there are no issues keeping the PPM in APO)