After upgrading to Tools Release 9.2.0, our EDI inbound shipment processing is failing with status code 037. The EDI Inbound Processor (R47011) runs but doesn’t create receipts automatically like before.
Before the upgrade, we had Event Rules configured for automated receiving when EDI 856 ASN files arrived. Now the flat files process successfully through the EDI subsystem, but the receipts aren’t being generated. The processing options for R47011 seem to have reset during the upgrade.
I’ve verified the NER (Named Event Rules) are still active in the Event Rules Design application, but something about the compatibility with Tools 9.2.0 appears broken. The EDI transactions sit in status 037 (processed but not completed) indefinitely.
EDI Transaction: 856-ASN-2025031501
Status: 037 - Processed, awaiting receipt
Processor: R47011 (EDI Inbound Processor)
Error Log: No errors recorded in JDELOG
Has anyone encountered Event Rule compatibility issues after upgrading to 9.2.0? Our warehouse operations depend on this automated receiving workflow.
One more thing to check - the EDI subsystem configuration itself. In P90CD01 (EDI Configuration), verify that the transaction set for 856 ASN is still properly mapped to R47011. Sometimes the upgrade process can modify or remove custom transaction mappings. Also look at the EDI processing sequence - if there’s a custom UBE or NER in the chain, make sure it’s still being called in the correct order.
Status 037 typically indicates the EDI transaction processed successfully but downstream automation failed. After Tools 9.2.0 upgrades, I’ve seen processing options reset to default values which can break automated workflows. Check your R47011 processing options - specifically the options that control automatic receipt creation and GL posting behavior. These often revert during major upgrades.
The BSFN version compatibility is critical here. After Tools upgrades, custom or modified BSFNs can point to outdated versions. In OMW, check your Event Rule BSFNs to ensure they’re compiled against the current Tools Release. Also, verify in the Event Rules subscription that the event type for EDI inbound (typically EDIINBOUND or custom event) hasn’t changed its internal identifier. I’ve seen cases where the event type GUID changes during upgrades, breaking the subscription even though it looks active in the UI. Run a quick test by manually triggering the Event Rule from P9070 to see if it executes independently of the EDI flow.