Steps

Navigate to the Escalations application and create a new Escalation:

In this example, we are using the INVOICETRANS table.  Note that this logic will be the same for other transaction objects. Check which attribute of the desired table you will update which will not affect your business logic. In this example, we are using the externalrefid attribute, this attribute is null for all records in this scenario.

In the Applies To field, set the value to the destination table, in this case, it is INVOICETRANS.

Next, set your Condition:

Since we updated externalreid values in the table directly, we want this escalation to find all records containing this value.  In the Condition field, enter:

externalrefid ='TOEXPORT'

Next, set the Schedule.  This escalation will only affect records on the first run of the cron task because all records will be updated by it to have a new value which will no longer match the criteria for this escalation to find any records on the second or subsequent runs.

Click the New Row button in the Escalation Points table window. You do not need to fill in any values.

Click on the Action tab and create a New Row. Go to Actions application and create a new Action as below:

In the above example of the action for this escalation to take when it finds matching records, we are changing the externalrefid value from TOEXPORT to EXPORTED.

Click Return with value and Save. Your Escalation will look similar to the screenshot below:

Click on Select Action => Validate. If everything is OK click on Select Action => Activate/Deactivate Escalation.
Once the escalation cron runs, the desired records will be updated causing the event listener to fire, and the records to be sent to their external system.

After the records are updated successfully, you can disable the escalation.

Using the Oracle Adapter:

The Oracle Adapter uses a non-persistent attribute called SOURCEMBO to validate some business rules. This attribute will not be automatically populated by the Escalation.  For that reason, we will need to create an additional action to populate the expected information.

In our example, we are using the INVOICETRANS table.  Create a second action as shown below:

Set the Parameter/Attribute value to SOURCEMBO and the value to ‘INVOICETRANS’.

This action must be executed before the EXTERNALREFID action. Check the value of the sequence and ensure that you set the sequence value for this action to a value lower than the sequence value of the action that populates the EXTERNALREFID attribute.

Next, navigate to Object Structure application and search for MXGLTXN. That object structure has an Outbound Definition Class. (psdi.iface.app.gl.MoutGLProcess). This class is responsible for skipping updates to GL transactions and has no other purpose. For that reason, this class will always evaluate these records has having been updated rather than created/inserted resulting in updated records being skipped from going outbound.  Remove this class file and save the object structure.

Next, you will activate the escalation.

Once all records have been sent to the external system, deactivate the escalation and restore the outbound class file on the object structure.

We strongly recommend that this process be performed when no other transactions are flowing to your external system since removing the class file can cause unintended results for transactions that originate inside Maximo.