Tender Response Integration fails when OTM generates a new Tender Id instead of using the existing T
We are piloting tender integration with an external system (of a service provider)
OTM generates a new TenderId for a Tender Modify or a Tender Withdraw instead of using the existing TenderId.
Internally it seems to have repurposed the i_transaction_no in the i_transaction table for the TenderId.
The transmission that goes out of OTM for a TenderWithdraw or a TenderModify seem to hold no reference to the existing TenderId.
Short of sending all existing TenderIds for the ShipmentGid from the SHIP_TENDER_COLLAB_BOV as part of Shipment Remarks in the TenderOffer Payload, I cannot think of anything else. Integration then as part of the TenderResponse can use the appropriate one for the ITransactionNo while sending the Tender Accept/Decline to OTM.