PO Release to be triggered based on Requirement tracking number

[Former Member]

Hi,

I want to trigger my release strategy for PO for Requirement tracking number....The problem i am facing is only in characterstics....

What i did is:

I created characterstic : ZPO_tracking_number

1st i tried table as CEKKO BEDNR....My release strategy was not working...

2nd i tried MEPO1211 BEDNR....My release strategy was not working...

3rd i tried

CEKKO BEDNR

MEPO1211 BEDNR

....My release strategy is again not working...

What should i do....?

Utsav

[Former Member · Accepted solution]

Hi Utsav,

Requirement tracking number is an item field. As release strategy for PO is based mainly on header fields you have to consider the following:

1º Use CEKKO-BEDNR for the characteristic

2º This field is going to contain data only if every requirement tracking number for every position is the same. If there is one item which has a different RTN the field on CEKKO structure is going to have a blank value.

If this things work for you then great. You can ask an ABAP to help you watch CEKKO-BEDNR value on a debug.

If this is not working for you, you can always implement a user exit an one of the user fields on CEKKO to determine the RTN based on the values of EKPO-BEDNR.

Regards,

Nelson.

[Former Member · Accepted solution]

Hi,

I tried Creating characterstics with CEKKO-BEDNR, but in PO my release startegy is not triggering...If i am taking other field such as GNETW..etc...My release startegy is triggering...

[Former Member · Accepted solution]

It is very much silly to ask but still have you assigned the value for the release strategy.Please check cl20n,cl24n

Regards,

Indranil

[Former Member · Accepted solution]

Yes it is mapped.

[Former Member · Accepted solution]

Then do one thing....don't use the BEDNR field and instead of that with the help of your ABAPer use USRC2 field from CEKKO.Check this in your test client.

Regards,

Indranil

[Former Member · Accepted solution]

Hi i did the same as per your instruction..I maintained charactersticZ_PO_TRACKING_NUMBER2 for USRC2 field from CEKKO

Now i am getting this message in Check Release Strategies:

You must maintain a customer exit for characteristic Z_PO_TRACKING_NUMBER2

Message no. ME_RELCHK038

Diagnosis

You have linked the characteristic Z_PO_TRACKING_NUMBER2 with field USRC2 of the communication structure CEKKO. In the standard system, this field is not populated. The data must therefor be determined in a customer exit.

Example

The person responsible for a cost center in a purchase requisition is to be determined. The name of this person is read from the cost center master record, placed in the field USRC1, and passed on to communication structure CEBAN.

The following customer exits are available to you:

Purchase requisition M06B0002

PO, RFQ, contract,

scheduling agreement M06E0004

Procedure

Check that you have maintained the relevant customer exit.

Note:

My Abaper has added BEDNR field in CEKKO struture, now i created PO, still my release startegy is not triggering...?

Edited by: Utsav.agra on Sep 9, 2009 6:51 AM

[Former Member · Accepted solution]

Take the hrlp of ABAP er and use Uer exit M06E0004 where yoy have to include a component of allmost the logic as i_cekko-usrc2 = w_bekpo-bednr

Regards,

Indranil