B2B 11g: How To Support Flexible Filename Formats When Using FTP Transport
Last updated on SEPTEMBER 09, 2017
Applies to:Oracle B2B (Business to Business) - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When using Custom Document over Generic Exchange with FTP transport, trading partners are restricted to use the following filename convention to send inbound and outbound messages:
This format tights the file name to B2B metadata like FROM_PARTY and ACTIONNAME which represents an unnecessary constrain. Trading partners should have the flexibility to follow a naming convention that does not contain B2B metadata.
A new patch was released for PS6 (18.104.22.168.0) that allows B2B to accept any file formats while using Custom Document over Generic exchange for FTP transport both in inbound and outbound directions.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms