Data Integration mappings for custom files with Intelligent Structure Discovery
When you use Intelligent Structure Discovery to receive incoming Excel, TXT, and CSV files from customers, Intelligent Structure Discovery writes the files to interface files on the B2B Gateway document store. You can use a process-to-backend Data Integration custom mapping to read the interface files from the document store and write the data to the backend system.
When you define an outbound flow you must use a custom mapping to read the data to send to the partner from the backend system. The mapping writes the data to an interface file on the B2B Gateway document store. You can use an additional, outbound custom mapping to send the data to the partner. For more information, see Rules and guidelines for custom file mappings.
Creating a custom mapping for inbound custom files with Intelligent Structure Discovery
Create a mapping that processes all incoming files for a message structure from the B2B Gateway document store to the backend system.
You can create as many mappings as required, one mapping for each message structure for which you want to process the interface files to the backend system.
When you create the mapping you select the B2B Gateway document store as the source, select the fields that you want to use in the mapping, and define the sample interface files of the structure as source parameters. You configure the organization backend system as the mapping target and map fields. You can add other elements to the mapping, based on your business logic, for example, filters and joiners.
To define the B2B Gateway document store as a source, you select a flat file connection that accesses the interface files. You must parameterize the connection. You can add as many connections to interface files as required.
Optionally, you can add more sources to the mapping. You can use any Informatica connection that isn't a B2B Gateway connection. Do not parameterize the connections.
Note: Parameterizing connections other than B2B Gateway connections might result in errors at run time.
After you add all the required elements to the mapping save and validate the mapping.
Step 1. Create the mapping
Create the mapping for inbound flows.
1Click New > Mappings, and then click Create.
2In the mapping Properties panel, enter the mapping name and description, and change the location to save the mapping.
You can use alphanumeric characters and underscores (_) in the mapping name.
Step 2. Configure the sources
Create source transformations to specify the sample interface files on the B2B Gateway connection as the source objects.
Optionally, add other sources to the mapping.
1Add a source to the mapping canvas.
2Click the Source tab and then select the following options:
Option
Selection
Connection
Flat file connection that accesses the interface files.
Source Type
Single Object
Object
A sample interface file.
Note: You must parameterize the flat file connection that accesses the interface files.
3Repeat steps 1 and 2 for all the sample interface files.
4Optionally, add more Source transformations to the mapping and configure them. You can use any Informatica connection that isn't a B2B Gateway connection. Do not parameterize the connections.
Note: Connecting additional sources to a B2B Gateway connection or parameterizing them might result in errors at run time.
Step 3. Select incoming fields
For each sample interface file, select the incoming fields to use in the mapping.
1Add an object to the mapping canvas and connect one of the source transformations you created to the object you add. You can add any type of object, based on the business logic that you want to add to the mapping. For example, a filter or a joiner. The object can also be the target of the mapping.
2Select the object you added. Select the Incoming Fields tab and, in the Field Rules table, select the following options:
Option
Selection
Operator
Include
Field Selection Criteria
Named Fields
Click anywhere outside of the Field Selection Criteria selection box.
3In the Field Rules table, under Details, click Configure.
The Include Named Fields dialog box appears, listing all the fields in the sample interface file.
4Select the incoming fields to use in the mapping and then click OK.
The Include Named Fields dialog box closes.
5If required, add more elements to the mappings to build the business logic of the mapping.
Note: If you selected incoming fields in a target transformation, do not add elements after the target. The target must be the last element in the mapping.
6Repeat steps 1 through 5 for all the sample interface files that you defined as sources in the mapping.
Step 4. Configure the targets
Create target transformations to specify your backend systems as the target objects for the interface files. Each sample interface file that you defined as a source in the mapping must be mapped to a target.
Note: If you added target transformations when you selected incoming fields, you do not need to add more target transformations.
1Add a target to the mapping canvas and connect the last element on the mapping to the target, or, if you already added a target to the mapping, select the existing target.
2Click the Target tab and configure target details.
3Click the Field Mapping tab and map incoming fields to target fields.
Step 5. Parameterize the sources
Parameterize the sources. Name each source parameter by the name of the sample interface file that is the source object.
1Click the Source tab, select a source element, and then select the following options:
Option
Selection
Connection
B2B Gateway Document Store
Source Type
Parameter
2Click New Parameter.
The New Input Parameter dialog box appears.
3In the Name field, enter the name of an output group in the structure. Click OK.
4Repeat steps 1 through 3 for all the sources in the mapping.