Removing Send process from MEC agreements

Does anyone know how to remove the "send" process from a MEC agreement?

We are using custom BODs to update M3 data triggered from a specific event. Currently all mappings for these BODs contain an input and output schema. However, there is no need for the output document because the BOD is only used to update M3 data.

We would like to remove the output schemas from the mappings, but when a mapping is published from the Mapping tool the send process is automatically added, even though there is nothing to be send to ION.

Find more posts tagged with

Accepted answers

All comments

Maxime Richard

Hello,

As far as i know, you can't. Don't have access to "Processes" steps when dealing with BODs.

Why did you choose BOD to update data in M3 based on an event ? Classic (ANY) IEC mapping should do the trick.

Fons Van Aert

Hi Maxime, thanks, could you explain further how we can use Classic IEC in the Cloud. I found an old document from 2019 which is referring to "Extensibility 4" (see below), but at that time it was not delivered yet.

"Extensibility 4 will provide most of the functionality from the on-prem version of IEC, minus external communication, in IEC CE. ION CE will handle all external communication instead. You will be able to set up partner agreements in IEC CE almost like you do for on-prem IEC. This functionality is being implemented and is not delivered yet."

Maxime Richard

Sure.

1) IEC mapper. Like on-premise. Your input schema is EventData, no output schema in your case. Give your mapping a name that does not include Verb/Noun. Publish like usual.

2) Build your own agreement under this folder:

You can create sub-folders. Select the sub-folder / configuration line and click "+" to add an agreement.

At the agreement level, you will define General information / Detection / Processes tabs, just like on-premise. Custom detections can be defined in Enterprise collaborator configuration (administrative tools menu). If you trigger your mapping based on an event going through EventAnalytics (best practise), you must select XML detection / AnalyticsHubPublisherDocName per default and enter the publisher + the document name you have defined in the rule

Save, activate.

Fons Van Aert

Thanks, we will try this.

Nichlas Karlsson

Hi,

Good and valid answers by Maxime and Tim!

Please note that triggering an IEC agreement from an Event Hub event without sending a message to ION is not integration. Instead, you are using IEC to enhance M3 "workflow" processing, which is not the purpose of IEC. Consider using XtendM3 instead.

/Nichlas

Copyright © 2025 Infor. All rights reserved.