Activation Policy gives error for missing attribute

Hello!

I have added attributes for purchase order from Sales Order BOD and within activation policy. (SalesOrder/SalesOrderHeader/AlternateDocumentID/ID for oeeh.custpo). Within Condition I am checking if this attribute is empty.

PO is required for our normal stock order but when the purchase order is empty (e.g. for return merchandise type order) AP is giving below error for missing attribute. Is there any way to avoid this error so that I do not need to clean up these unhandled errors manually?

AP Error.

com.infor.ion.container.common.exception.ServiceContainerException: Dispatching BOD message fails with MonitorException(s) detected in monitor(s) APforCustytypeHAW: APforCustytypeHAW Missing mandatory attribute(s): PO(SalesOrder/SalesOrderHeader/AlternateDocumentID/ID) ;
at com.infor.ion.process.monitorengine.logic.EngineMonitorManager.handleMessage(EngineMonitorManager.java:752)
at com.infor.ion.container.element.base.adapter.BaseElement.process(BaseElement.java:105)
at com.infor.ion.broker.process.channel.queue.internal.MessageDistributor.handleMessage(MessageDistributor.java:666)
at com.infor.ion.broker.process.channel.queue.internal.MessageDistributor.run(MessageDistributor.java:497)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.infor.ion.process.monitorengine.logic.MonitorException: APforCustytypeHAW: APforCustytypeHAW Missing mandatory attribute(s): PO(SalesOrder/SalesOrderHeader/AlternateDocumentID/ID) ;
at com.infor.ion.process.monitorengine.logic.EngineMonitorManager.dispatch(EngineMonitorManager.java:319)
at com.infor.ion.process.monitorengine.logic.EngineMonitorManager.handleMessage(EngineMonitorManager.java:739)
... 4 more

Find more posts tagged with

ION Connect

Accepted answers

All comments

Legacy Contributor

When there is no PO# as an alternate document ID does your BOD have a SyncSalesOrder->DataArea->SalesOrder[0]->SalesOrderHeader->AlternateDocumentID[] section and a null or missing SyncSalesOrder->DataArea->SalesOrder[0]->SalesOrderHeader->AlternateDocumentID[]->ID ?

If so can you remove the entire SyncSalesOrder->DataArea->SalesOrder[0]->SalesOrderHeader->AlternateDocumentID[] section and see if you still get the error?

Legacy Contributor

When there is no PO# the alternate document ID section is missing from the BOD, so it is not even adding that section when the order for return merchandise is entered, and then it gives error.

But the problem is I am not even looking for RM orders I need the stock orders with particular condition to activate my policy and it is generating the unhandled errors for RMs, which I need to make it handled manually.

Thanks,

Jyoti

Legacy Contributor

Hello Keith!

Wanted to give you update on this.

I updated the SAABN as shown in below picture, I enabled level 1 extra fields to everything – send all level 1 extra fields.

After doing this when it sends the new BOD I got the oeeh.custpo field in BOD under UserArea as below

<NameValue name="oeeh.custpo" type="string">testing BOD</NameValue>

</Property>

Can I use this property instead of Alternate Document ID to get the customer PO#?

Thanks,

Jyoti

Copyright © 2025 Infor. All rights reserved.