My Oracle Support Banner

B2B 11g: How To Support Flexible Filename Formats When Using FTP Transport (Doc ID 1610826.1)

Last updated on JUNE 18, 2018

Applies to:

Oracle B2B (Business to Business) - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal

 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:

   %FROM_PARTY%_%ACTIONNAME%_%TIMESTAMP%.xml

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 (11.1.1.7.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.

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.