Custom BOD (EDU_PurchaseOrder_Custom) not triggering via Event Analytics Rules on PPS200 Create

Question

Hi everyone,

I am having trouble getting a custom BOD to trigger and show up in Event Analytics Rules. Here is a breakdown of my current setup and configuration:

1. Development & Publishing

* Created a custom BOD using the Eclipse mapping tool and published it.
* BODNoun: EDU_PurchaseOrder_Custom
* BODVerb: Sync
* findDIVI: FACI

2. Enterprise Collaborator (EC) Configuration

* ECAgreement: Added a dedicated folder in agreements, configured for both detection and processes.
* ECConfiguration: Successfully subscribed to the custom event.

3. Event Analytics Rule & Subscription

* Publisher: M3
* Document: MPHEAD
* Operation: Create
* Criteria Rule: PUSL = '15' AND (currentProgram != 'PPS601' AND currentProgram != 'PPS608' AND currentProgram != 'PPS201')

The Issue: All configurations above have been fully activated and validated. However, when I go into PPS200 to add a new Purchase Order (setting the status to 15 upon creation), the BOD does not show up at all in the Event Analytics Rules logs.

Am I missing a specific step in the MEC/Event Analytics handshake, or is there an issue with how MPHEAD handles the currentProgram variable during a PPS200 creation?

I have attached screenshots of my rules and configuration for reference. Any advice or guidance would be greatly appreciated!

Screenshot 2026-06-11 162839.png

Screenshot 2026-06-11 162905.png

Screenshot 2026-06-11 162918.png

Screenshot 2026-06-11 162947.png

Screenshot 2026-06-11 163001.png

Screenshot 2026-06-11 163017.png

Screenshot 2026-06-11 163055.png

Erik van der Vlugt · Answer

Hi Harrison, Glad you got it a few steps further. Your question unfortunately is not my strong point. But no doubt there are others here that can help?

Gr, Erik

Harrison Hay · Answer

Hi Erik,

Quick update on this: I did a test using the standard out-of-the-box M3 PurchaseOrder BOD with the Update operation and the following rule:

OLD(PUSL) < '20' AND PUSL >= '20' AND (currentProgram != 'PPS601' AND currentProgram != 'PPS608' AND currentProgram != 'PPS201')

When I process the PO in PPS200, the standard M3 BOD successfully fires. However, my custom BOD (EDU_PurchaseOrder_Custom) still does not trigger.

Since the Event Analytics rule is clearly capturing the event, the issue seems to be down the line with MEC/ION routing or how my custom BOD subscription is set up.

Are there any specific routing rules or configurations I need to check to ensure the Event Hub routes this change to my custom BOD instead of (or in addition to) the standard one?

Thanks again for your help

Exported Event.txt

Erik van der Vlugt · Answer

Hi Harrison,

On create your order is created with status 6 or so, not directly on 15. So if you want to catch the change to 15 you need to trigger the bod on Update, not create.

Might want to check DataLake Compass on this to see the sequence, something like

select * from infor.allvariations('mphead') where puno = 'xxxxx' order by variationNumber

If you want to act when the order gets to status 15 you can set in filtering to only get the change from lower to 15 something like OLD(PUSL) < '15'

Copyright © 2025 Infor. All rights reserved.