SNP optimizer - supply shortage at source with procurement type P

[Former Member]

Hi Experts,

I am having a situation like below.

Network: 1 source (proc. type P), 1 destination (proc. type F)

Demand at destination > Supply at source

Demand is present in the form of dependent demand. Supply at source cannot be altered.

Optimizer run: Discrete

Dependent demand for fixed orders: treat as pseudo-hard constraint

Distribution demand for fixed orders: treat as customer demand

Stock transfer to destination is pull based

ND penalty is maintained both at source and destination, a bit higher at source

Supply shortage is seen at source, whereas it is expected that supply shortage should only be seen at destination location when demand > supply

Can anyone help?

Regards,

Biplab

[sourabh_jain66]

Hi Biplab,

Please refer one of the older thread for this,

http://scn.sap.com/thread/3373113

Rgds

Sourabh

[m_manimaran]

Hi Biplab,

The procurement type 'P' is not planned by APO. Please see the definition for procurement type 'P' from SAP help.

-----------------------------------

Definition: external procurement planning

APO Cross-Application Components (SCM-APO-CA)

The product is not produced in the location, nor are orders created for
it.

Unlike in-house production or external procurement, the planning does not
take place in APO. Instead, stock shortfalls are replenished by the OLTP
system.

---------------------------------

I do not understand what do you mean by supply at source cannot be altered. Is it because of the procurement type 'P'? In this case, if the supply available at source is less than the demand, then the supply shortage will appear.

In Destination location, since the procurement type is F, it is planned by optimizer. That is why there is no supply shortage in destination location.

Regards,

Manimaran M.

[Former Member]

Hi Biplab,

As per the info provided by you,at source location, Procurement Type is 'P',does optimiser considers source location for planning as it has Proc Type 'P'?

Thanks,

Sandeep