Faulty STO in BOP

[Former Member]

Hi,

When someone creates a STO without a net price in ECC, the STO is faulty in ECC but still visible in SCM. Since SCM has this STO, the STO requirement is in the BOP and all this is fine.

The problem is during the update. ECC does not allow any update on the STO from SCM BOP. The main reason ... STO is still faulty in ECC.

How can we avoid this noise in the post processing of SCM? Is there anyway to make this update happen anyway? or can we make this STO ''Not MRP Relevant'' since it's faulty in ECC?

Please let me know if you have any idea.

Thanks

David

[sourabh_jain66]

Hi David,

There can be multiple ways you can tackle this issue.

1) while creating STO use some development to not allow to save STO without net price, which should be a small development.

2) Use CIF ECC outbound exit to control what STOs goes to APO.

3) In BOP filter criterion if you can bring net price as one of the filtering criterion, would solve your issue.

Now depending on business requirement and other things you have you can select suitable option.

Rgds

Sourabh

[Former Member]

OSS Note: 1665875

[andy_yeri]

Says not released?