The Inbound EDI Business Process inherits two tasks. At a minimum, two additional tasks are added.
- SetRouteFieldValues – This inherited task populates Field values from the Inbound EDI Route.
- Execute Transformation – This task indicates the Ruleset to transform the source data to target format and specifies the Transformation Settings.
- Target Interface – This task uses the adapter to output the transformed data. We use our Database Adapter that contains our insert interaction.
- SetExitStatus – This inherited task sets the Exit Status as true (pass) or false (fail).
The Inbound EDI Business Process inherits three parameters, each containing data passed to it by the ReceiveEdi Business Process.
- route – This contains the Inbound EDI Route that references this Business Process. This parameter assists the SetRouteFieldValues task to populate the Field values defined within the Inbound EDI Route.
- context – This contains the values passed into the Ruleset to populate the variables on its Variables panel in the glb and env For inbound EDI processing, the env category includes the interchange and group (ISA and GS) element values.
- inputDataFragment – This contains one EDI message (ST-SE).
Indicating the Ruleset can be done in two ways. You can do so directly or indirectly (“hot swap” it at runtime via the Inbound EDI Route).
It is best practice to use a Field in this Business Process to “hot swap” the Ruleset. This way, in the trading-partner-specific Inbound EDI Route you can specify either a “core” Ruleset (one-size-fits-all)
or you can treat individual trading partner needs individually by specifying a trading-partner-specific Ruleset.