Sync.M3EDIInvoice custom BOD not triggering / MBMInitiator / EventAnalyticRules

Hello,

I am trying to create a custom BOD based on the standard M3EDIInvoice BOD with the name M3EDIInvoiceCustom.

After changing the name in MEC, publishing, activating the agreement. I went to event Analytics rules and duplicated the Standard Rules for M3EDIInvoice MBMInitiator_REQUEST_M3EDIInvoice and changed the BOD Verb to M3EDIInvoiceCustom.

But when triggering creating an invoice, only the standard one M3EDIInvoice is triggering and not the custom one. As a test I duplicated the same rules and left the criteria empty; one with the standard and one with the custom verb and only the custom verb is not triggering.

I would like to know if there's any additional step up that needs to be done when dealing with MBMInitiator.

Thank you.

Find more posts tagged with

Accepted answers

All comments

Legacy Contributor

Hi Ismail, Did you

Legacy Contributor

Hi Ismail, Did you

sean-scanlon

check settings in Bod processor administration?

Legacy Contributor

Hi Ismail, did you add your custom BOD to BOD-processor?

Nichlas Karlsson

According to your naming you have either created a custom noun, "M3EDIInvoiceCustom", or you are using the "variant" "Custom" with the standard noun M3EDIInvoice. You need to create a custom BOD in BOD Processor, enable it for your CONO + DIVI, save and then reload. When you published the mapping (which for example can have the name M3EDI_M3EDIInvoiceCustom_Sync_Out_Custom), the custom agreement "M3_M3EDIInvoiceCustom_Sync_Out" was generated. You need to activate this agreement in MEC. Then it should work.

Legacy Contributor

Hi Ismail,

Did you change the MAP_ION_BOD_TYPE to 'Sync.M3EDIInvoiceCustom'?

Legacy Contributor

Hi,

Check if you have the BOD Processor entry created for the BOD with company, and division enabled and reloaded.

Legacy Contributor

Hello,
Yes i added the new BOD in BOD Processor Administration and enabled it for my Company/Division.

Legacy Contributor

Hello, Thank you for your response.

I did add it in BOD Processor Administration as a new BOD with name SyncM3EDIInvoiceCustom but the result stays the same.

Legacy Contributor

Hello Sudhakaran, thank you for your response,

Indeed I have created an entry in BOD Processor Admin and enabled it with my company and division and reloaded.

Legacy Contributor

Hello Premkumar,

Thank you for your response, indeed I have changed the MAP_ION_BOD_TYPE to Sync.M3EDIInvoiceCustom.

Maxime Richard

Hello Ismail,

Did same as you and it's working fine here:

2 standards agreements + 1 custom agreement triggered: 1 message for the standard EA session, 2 messages for the custom session (which contains 2 rules)

Did you check the EventAnalytics:M3BEBOD event creation in EventHub log ? Just to locate where the problem is.

Copyright © 2025 Infor. All rights reserved.