cancel
Showing results for 
Search instead for 
Did you mean: 

PO Release Strategy

Former Member
0 Kudos

Hello Gurus,

I am having a question on PO release strategy. I am using characteristics and like doc type(NB), PO net value and along with this we are having a custom field on the header level of the PO called ZContract and grouping it to class 032.

The ZContract field is a place holder for a PO having a contract or not. Based on whether a value is entered in this field on the PO the relevant release strategy has to be followed. It is a dummy field and will not be validated. It can take in any dummy value. below mentioned is the release codes and dollar limits required

Contract codes Non contract codes dollar limits

C1 P1 100K

C2 P2 250K

C3 P3 500K

-


I want to know i this is possible to do and any help would be greatly appreciated.

Thanks in advance

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Check if the field KONNR in the strcture CEKKO will help you. The field shows the outline agreement used for the PO. You can define one more characteristic with this field and use that in your class.

Careful if ur PO is having multiple line items , some with contract reference and some without.

Let me know if it worked.

Mohit

Former Member
0 Kudos

Dear Pradip,

go for the Transaction code SE12 and Display component for CEKKO table.

Find out is there your Zcontract field is available or not.

If Yes Then it is possible to maintain release strategy for your Zcontract field otherwise it is not possible to maintain release strategy for this

Rewards if helpful

Regards

Sanjay L

Former Member
0 Kudos

Hi

I understand the Zcontract field is filled with the avaiable contract number, is it right?

You may maintain characteristic for the contract and maintain the custom table and custom field in additional data of the characteristic. Assign the characterisitc to the class.

Please try this and furnish feedback on your observations.

warm regards

sairam akundi

Former Member
0 Kudos

Hi,

let me Rephrase my question . Is it possible to have 2 legs of approvals for the same dollar amounts and based on whether the contract field is empty or filled the relevant leg of release strategy to be selected.

C1 P1 100000 - 200000

C1 if Contract field is filled.

P1 if Contract field not filled.

Thanks

Former Member
0 Kudos

Hi,

yes, but you would need two release strategies.

The first one should check for spaces in the contract field (and any other checks you want, value etc.)and then specify the release codes you want for this situation.

Then a second strategy will be required that checks for the field to NOT equal spaces (again plus any other checks, these can be the same checks with the same values as the first strategy) and this then uses a different set of release codes.

Steve B

Former Member
0 Kudos

Hi Steve,

Thanks for your response. Can you give me a detailed procedure to define this particular characteristic for the contract field. Particularly the additional values screen and the table and field value screen.

Thanks

Former Member
0 Kudos

Hi,

Sorry, I leave that to the technical guys and so I can't give you any detailed instructions.

basically you have to add the characteristic to the class used by the PO release and use the additional values screen to point the characteristic value to the new header field. The part I am not sure about is that I think that it has to be a field on the CEKKO structure and thats the technical bit I am unsure about.

Perhaps one of the other experts has done this and can help?

Steve B