Relevance Condition for released P.O. Don´t create the EH in EM

Hello Experts,

I have the following issue, I create a Relevance condition For an Application Object Type, in this case acording to ZPCM10_ITEM. The condition works like this:

(

&UEKPO-Purchasing Doc& > 1999999 and

&UEKPO-Purchasing Doc& < 3000000

) and

&UEKPO-Plant& = BPXX

The condition works well, only create the PO into the range of numbers and with the plant. My problem is when i include into the condition the “Release indicator: Purchasing Document” according this:

(

&UEKPO-Purchasing Doc& > 1999999 and

&UEKPO-Purchasing Doc& < 3000000

) and

&UEKPO-Plant& = BPXX and

&/SAPTRX/MM_PO_HDR-Re& = 1

I include the condition of the indicator = 1 (Released). In theory in EM we can only see the Purchase orders in Released Status, but when i execute ME28 Transaction, nothing happen and the P.O. don´t work in Event Management.

Do i forget other step to reach the objective?

I appreciate a lot your help and support.

Thanks a lot and best regards.

Julián.

Hello Experts,I have the following issue, I create a Relevance condition For an Application Object Type, in this case acording to ZPCM10_ITEM. The condition works like this:(&UEKPO-Purchasing Doc& > 1999999 and&UEKPO-Purchasing Doc& < 3000000 ) and&UEKPO-Plant& = BPXXThe condition works well, only create the PO into the range of numbers and with the plant. My problem is when i include into the condition the "Release indicator: Purchasing Document" according this:(&UEKPO-Purchasing Doc& > 1999999 and&UEKPO-Purchasing Doc& < 3000000 ) and&UEKPO-Plant& = BPXX and&/SAPTRX/MM_PO_HDR-Re& = 1I include the condition of the indicator = 1 (Released). In theory in EM we can only…

Relevance Condition for released P.O. Don´t create the EH in EM

Very Helpfull

User Rating: Be the first one !
Doctor Asked on November 8, 2016 in event management.
Add Comment
1 Answer(s)

Hello Julián,

 

yes you are right – the condition looks ok and I also think it should work. To make sure that the error is due to the condition can you just set a breakpoint on function module /SAPTRX/CONDITION_EVALUATOR and check if the result is F for false or T for true?

 

If the result is F for fales then somehow the condition does not work correctly.

 

By the way depending on your data volume I would rather recommend to use a function module as condition than the condition editor. The function module is performance wise much faster than the condition editor. So if it is possible for you to also use the function module I would recommend to go for this option.

 

Regards

Berthold

 

Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.