Release strategy for PO

[Former Member]

Hi,

I have configured release strategy in Dev server.Now I want to know what are the different master data that I need to maintain again in QA and prod server and also the reason for it ( like class, characteristics, CL20N etc) so that release strategy works successfully

[BijayKumarBarik · Accepted solution]

Hi,

As Release strategy for PO works fine in DEV Server. You need to create again SAME all Release characteristics & a Release Class in PRD Server and also you need to transfer all VALUE for individual release strategy with release group with release class in CL20N/CL24N..

For more check this blog

/people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues

Regards,

Biju K

[Former Member · Accepted solution]

Hi,

Since we use same communication structure for PO and contract then how do I set up release strategy for the two and how can I differentiate

[BijayKumarBarik · Accepted solution]

Hi,

You can use document type( For PO document type NB,ZNB,YNB,ZCPC,ZCCC but for contract document type is MK & WK) very well to differentiate between PO & contract and design your release strategies.

Also you can Purchasing Document Category to to differentiate between PO & contract and create Release characteristic with CEKKO with BSTYP. For PO purchasing document category is F & for contract purchasing document category is K.

Regards,

Biju K

[Former Member · Accepted solution]

Hi,

Do we need to create different release group for PO and contract release strategy

[BijayKumarBarik · Accepted solution]

Hi,

Yes, you are right. You need create different release group for PO & Contract and also different release strategy for PO & contract.

Regards,

Biju K

[Former Member]

closed

[Former Member]

Hi

While creating Rel Strategy system will raise TR (Transport Request) note that number forward it to basis cunsultant for tranport from DEV to Qlty

Regards

Avinash