Release Strategy

[Former Member]

Hi friends,

I have created a release strategy. It is working. But I have a condition. If account assignment category is X release strategy must use xxxxx method, or other account assignment category strategy will be yyyyy method.

How can I manage this. CEKKO table not containt account assignment category.

Thanks for your answer.

[Former Member]

Created new z field and use it in standarc customization

[mauro_bianchi]

Hi Mehmet,

The reason why the release strategy is not consistent when using

account assignment as a classification is because the PO release

strategies have to be maintained at the document header level (table

EKKO), because unlike requisitions, the release takes place at the

header level and not the item level. Field KNTTP comes from table EKPO,

and it's value may be different from one postion to another, within the

same PO.This can cause conflicts at the time of determining the release

strategy because all the positions in the document have to be linked to

the same release strategy. Therefore neither Account Assignment

Category nor Item Category are available in CEKKO.

As work-around you can use the following user-exit:

MM06EF0S_STRATEGIE_CEKKO

(enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).

In this user-exit the data are available in structure I_CEKKO.

The hand-over from I_CEKKO to the calling program is via structure

E_CEKKO.

In the user-exit I_CEKKO has to be copied to E_CEKKO , e.g.

E_CEKKO = I_CEKKO.

Regards,

Mauro

[Former Member]

Merhaba Mehmet,

You are right. CEBAN include this field but CEKKO is not.

So you should add this field to CEKKO sturucture and use M06E0004 user exit.