Customized DEFAULT OTM/GTM BN Rules Are Not Working After Migrating From On-Prem To Cloud
(Doc ID 3036806.1)
Last updated on JULY 23, 2024
Applies to:
Oracle Transportation Management Cloud Service - Version 19.3 and laterOracle Global Trade Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.
Symptoms
Customer was using On-Prem OTM or GTM and they had customized the Definition of the DEFAULT BN Rules per their business need.
For an Example :
BN Rule => SHIPMENT_XID.DEFAULT
Rule Definition => {dddddddd:id=1}-{nnnn:contexts=1:start=1}
Now, customer has migrated from On-Prem to Cloud and they have migrated those BN Rules into Cloud version to cascade the desired customizations as well.
After this, the observation is System is NOT considering the BN Rules on creation of different Transactional data like Shipment, Ship Unit etc.
Some sample BN Rules are as-
SHIPMENT_XID.DEFAULT
S_SHIP_UNIT_XID.DEFAULT
ORDER_MOVEMENT_XID.DEFAULT etc.
However, if they create a fresh Custom BN Rule and make that Default - then that is triggered and working properly.
Changes
No Change.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |