Release strategy for account assingned PO

[Former Member]

Dear Friends,

The release strategy is stable in our organisation. I want to incorporate one special release strategy.

A separate person should always release a capex PO. The PO has account assignment as internal order. But he should be responsible for those internal orders having order type capex. For that we are using only one G/L in the PO.

Is there any way out so that we can use account assignment & G/L account as characteristics to incorporate the new strategy without touching the existing strategies.

Answars will be well appreaciated.

Regards

Rutabhadra Panda

[Former Member · Accepted solution]

Thanks For your reply.

We have a separate order type for capex PO. For that different release strategy is there. The problem is client wants a different strategy for POs which has account assignment as internal order & the order type of that internal order should be capex.

Regards

Rutabhadra Panda

[Former Member · Accepted solution]

Hi Rutabhadra,

There is a easier method. You can use exit M06E0004. USRC1, and USRC2 are char fields with 20 character width and USRN1 and USRN2 are numeric fields. All you have to do is read Internal order master data using IT_EKKNU-AUFNR and populate USRC1 field with the order type. Once this is done, you have create a new characteristic in your release strategy for USRC1 field and assign the order type to this.

That is it. Can be achieved in 1 to 2 days including testing.

Ravi

[Former Member · Accepted solution]

Dear Ravi,

Thanks a lot for your suggestion.

If I am correct then you are suggesting to create user id as one characteristic. But my problem is that same user can create a normal PO & also an account assigned PO.

In that case will it work? Can we use exits for multiple t-codes?

Regards

Rutabhadra Panda

[Former Member · Accepted solution]

Hi Rutabhadra,

No No No. I am not asking to check user id. The field name is USRC1. This is given such name to indicate that it is not populated by SAP. It is for users like you who want to design release strategy based on fields that are not available.

Let me make it more clear.

Suppose you create an Internal order for capex - order number -000001 Order type "CAP".

In the exit you will insert an abap code to read 00001 order from the order table, assuming that the po would have been created with this order number in the account assignment. You read the order table for this internal order number and you can get the order type "CAP". populate the USRC1 field in the exit with this value "CAP". For each PO line this field will be populated. You can decide to use "NA" meaning not applicable for other account assignments.

Then create a characteristic for this field in the Po Release class. Create a release strategy with this caharcteristic value = "CAP".

You can speak to your technical people, they might able to quicly do a prrof of concept.

Ravi

[Former Member · Accepted solution]

Dear Ravi,

Thanks a ton for such a valuable suggestion.Now I got a clear idea.

I will need a little more help from you. You have suggested to use exit M06E0004. But my users use not only ME21N but also ME21 to create purchase orders.Will the exit consider both the T-codes.

Suppose any user created a PO with an internal order of capex order type. Then system will find the special strategy meant for capex PO.

Aftrerwards in ME22N or in ME22, if somebody changes the internal order which might not be of order type "Capex", then in that case will the release strategy change.

So my query is will this exit work for all these T-codes.

These queries will resolve my problem. Awaiting your valuable suggestion.

Regards

Rutabhadra Panda

[Former Member · Accepted solution]

Hi Rutabhadra,

Spot on. You got it all correct. All tcodes me21n, me22n, me23n, me21, me22 use this exit. Any change will redetermine release strategy.

Take my word and go ahead.

Just as a note of caution, you decide what do you want to do in case one line in PO is capex and another line is non-capex?

Ravi

http://raviinsap.blogspot.com

[Former Member · Accepted solution]

Dear Ravi,

Thank you so much.Your proposition has cleared my doubts.

I will get it done & will get back to you.

Regards

Rutabhadra Panda

[Former Member]

Define a Z* document type, and

you can use this BAdI

The Business Add-In (BAdI) ME_PROCESS_PO_CUST enables you to extend the business logic of the Enjoy purchase order on an individual basis.

You can thus influence the dialog transactions ME21N, ME22N, ME23N, and ME29N, and the BAPIs BAPI_PO_CREATE1 .

Use the method for the PROCESS_ITEM, this method enables you to make the Z* document type

mandatory for Account assignment PO.

So that the user can create an Account assinment PO with the Z* doc type only.

Then Create a New Release strategy by including the Z* doc type ..

[Former Member]

Dear Raju,

Thanks a lot for your very valuable suggestion.

If I am not mistaken you are suggesting to create a new document type for capex PO. The BADI will check if there is account assignment then it will make that document type mandatory in PO.

Is it possible that the BADI will check the account assignment first. Then it will check if it is "Z" then it will check the master data of the internal order number.Then if it finds that the internal order is of order type Capex then it will call a particular release strategy. My query is is this possible if we do not create a new order type for capex PO.

Your answrs are well appreaciated.

Regards

Rutabhadra Panda

[Former Member]

Hi,

You may try create a characteristics for a separate Document type for CAPEX POs alone and confogure new release strategy instead of using account assignments.

Regards,

Ram