Release object 2 - Release strategy - MM

[former_member585802]

We are working with Purchase orders and schedulling agreement.

Because of business needs we add purchasing order field "requisitioner (EKPO.AFNAM)" as a reléase parameter.

But, this field is not existing on the scheduling agreement (ME31L), so I cannot enter there any value.

And , because we can used only 1 Class for the release object 2. And looks its not posible to avoid AFNAM characteristic on SE strategies.

How can I make reléase strategy works for PO and SE at the same time ? On this scenario?? Thanks a lot,

[JL23 · Accepted solution]

Don't you just need to add a characteristic value "blank" for AFNAM to have the strategy work for both?

From my personal point of view I would never setup strategies based on people names, especially not on the AFNAM field as it has no check table and allows to enter any value.

[Prasoon]

Hi,

Since AFNAM field is in EKPO and not available in standard CEKKO, hope you have enhanced the communcation structure. In this case, you need to check what value getting passed in case of SA through the custom code. You may simply debug during SA creation or value change and check what value is showing for the field AFNAM in the communication structure CEKKO. You may maintain the same in CL24N and check the behavior.

Note: Instead of using an item level field, you could have used any header field like collective number (SUBMI), with a search help Ztable for the header level release.

Regards,

Prasoon

[former_member585802]

Hi Jurgen,

Thanks for your answer. No, I try with the "blank", but that is not working. Just test writing " ".

We used AFNAM to represent an area and not a user name, also we develop a Z table that support the possible options to be enter here.

What would you do if you need different characteristics for purchase order / scheduling agreement or RFQ ??? Because we have only one class and therefore, same characteristics for all purchasing documents.

Kind regards,

[JL23]

Actually, if I were you, working for the same company which developed the programs, I would ask the colleagues right away.