Inbound 997 Transaction Is Successful But Payload File Is Not Written To Target FTP Location
(Doc ID 2058068.1)
Last updated on JUNE 02, 2016
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
There are few inbound 997 transactions which are created and deployed. B2B is processing these transactions and
moving these to a FTP location using a FTP channel at host partner level in the agreement. Please note that here B2B will
not handle 997s. Its job is to move the 997 files to a FTP location as mentioned above.
Have exported these agreements and imported in to QA B2B and deployed the agreements. When tested these 997 transactions
in QA B2B, these are successful but the file is not written to the FTP target location. But in the B2B reports, the
status of the transaction is showing as MSG_COMPLETE. Also there is no error in the logs but the file is not written to
the target FTP location.
The same channel is used by other agreements like 850 and in this case the files are getting moved to the target location.
The problem is with the 997 transactional agreements only.
Also, you want to identify the sender and have the backend application process the EDI 997s sent by B2B.
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