B2B Gateway

Back Next

Custom files with custom mappings

B2B Gateway

uses custom

Data Integration

mappings, which you create, to validate and handle custom file exchanges between the organization and its partners.

Custom mappings for inbound custom files: Use an inbound mapping to receive files from partners. If you use the two-step processing method, the inbound mapping writes the files to an interface file on the
B2B Gateway
document store. If you use the single-step method, the inbound mapping writes the data to the backend system. The source of the inbound mapping is the incoming files, and the target is either an interface file on the
B2B Gateway
document store or the backend system, based on the method that you use.; If the target of the mapping is
B2B Gateway
, you can use a process-to-backend mapping to read the files from the gateway and write the data to the backend system. The source of the process-to-backend mapping is the interface file on
B2B Gateway
, and the target is the backend system.
For inbound Excel, TXT, and CSV files, instead of creating custom mappings to process the incoming files, you can use Informatica Intelligent Structure Discovery to automatically discover the file structure and create CSV interface files. You can then create custom mappings that process the data to your backend system.

For more information about the processing methods, see Inbound process for custom files.
Custom mappings for outbound custom files: Use a process-from-backend mapping to read outgoing data from the backend system and write the data to an interface file on the
B2B Gateway
document store.; You can use an additional, outbound mapping to read the data from the gateway and send it to the partner. The source of the outbound mapping is the interface file on
B2B Gateway
, and the target is the target location for the partner that you send the data to.