cancel
Showing results for 
Search instead for 
Did you mean: 

PO Release Strategys'

Former Member
0 Kudos

Hi all,

We are using release strategy 6 for PO release. When there is an increase in quantity or net price PO again goes for approval. If there is any decrease in quantity and net price workflow doesnu2019t start since its situation. But management wants that when a PO is changed in any field such as quantity, net price, plant, or etc it must again go for approval. I think PO doesnu2019t have any sensitive field customizing such as vendor. I would like to hearing from you.

Best regards,

Melih

Accepted Solutions (1)

Accepted Solutions (1)

former_member210560
Active Contributor
0 Kudos

Dear Melih,

basically based on your description, the strategy will only be determine or reset again if you have

define the classification in customizing.

For example if vendor you have to define cekko-LIFNR in as your characteristic and assign it

to the class you create.

Then vendor A assign to release strategy A and vendor B assign to release strategy B.

Then if you change the vendor A to B, the release strategy will get reset and your

release strategy will change from A to B. You may check the structure CEKKO via transaction SE11

for the available field in the system can be define as characteristic.

Best Regards,

Ian Wong

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

If the particular field that you want change is part of the release characteristic defined then only it controlls the release procedure (via Release indicator)

To determine new release strategy whenever there is change in the PO you have to maintain release indicator as 4:Changeable, new release in case of new strat. or val. change or 6:Changeable, new rel. if new strat. or value change/outputted.

Regards

Ravi Shankar.

Former Member
0 Kudos

Normally its not possible for decreasing values