B2B Document Identification Issue for Custom Document over Generic Protocol
(Doc ID 1146635.1)
Last updated on OCTOBER 26, 2018
Applies to:Oracle B2B (Business to Business) - Version 10.1.2.0.2 and later
Information in this document applies to any platform.
Usecase: implmenting a process for custom flat files (contents of which are delimited by pipe) though B2B SFTP.
There is a need to identify the inbound document type with a "tag" and mention the tag value and their start-end indices within the document type parameters.
The goal is for any files to get processed, and don't want to provide any tag for identification.
However, this makes B2B to reject the FTPed document with "AIP-50083: Document protocol identification error".
Is there a way to use File Format tokens to make this work?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|