topic Re: BAdI ME_PROCESS_REQ_CUST: subtle behaviour in PROCESS_HEADER in Application Development and Automation Discussions

BAdI ME_PROCESS_REQ_CUST: subtle behaviour in PROCESS_HEADER

Former Member — Thu, 17 Jan 2008 18:21:34 GMT

Hi all,

I'm using BAdI ME_PROCESS_REQ_CUST to make custom checks during PReq processing via ME51N transaction.

When I change the PReq type as very first change made in transaction the method PROCESS_HEADER doesn't return the PReq type just modified but the default one.

If I change another time the PReq type the method, this time, returns the correct PReq type.

I have already get an official answer saying that this is not a correct behaviour.

A suggested workaround it is to read the variable my_state->flow in the object lcl_req_header that is instantiated by transaction: but how I can read this object ? In other words I have my object related to BAdI implementation and from there I need to read an attribute of another object to which I have a variable to which (object) is a ref.

I know that is it very complicate to explain the situation...

Thanks a lot,

Antonino

Re: BAdI ME_PROCESS_REQ_CUST: subtle behaviour in PROCESS_HEADER

uwe_schieferstein — Fri, 18 Jan 2008 02:48:41 GMT

Hello Antonino

A similar problem has been described previously in thread:

[Access to class-attribute by Interface-reference|;.

I explained the solution in more detail in my Wiki posting

[ Accessing the Inacessible - Local Classes within Global Classes|https://wiki.sdn.sap.com/wiki/display/ABAP/AccessingtheInacessible-LocalClasseswithinGlobalClasses]

Since MY_FLOW is a public attribute of MY_STATE like MY_ITEM the solution should work here, too.

Regards,

Uwe

Re: BAdI ME_PROCESS_REQ_CUST: subtle behaviour in PROCESS_HEADER

Former Member — Fri, 18 Jan 2008 13:08:18 GMT

Hi Uwe,

the thread you suggested fully solved the problem !

Thanks a lot,

Antonino