![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
2. Click New Message Type.The Operation Type list is displayed with Notification selected. The Type selection cannot be modified because only Notification transactions are supported.
3. Click OK.
• Delimited This format defines files that contain a consistent delimiter all throughout the file.
• Positional This format defines files that have a defined position (or size) for each field in the file This tab allows you to configure message guidelines and validator profiles. Click change to select the guideline file associated with this message type.
• For Uploaded File, click Browse to select a configuration file from the local file system.
Load a guideline file, such as Positional_4040_850.sef.
• None Select when this type of translation is not used
• TEXT to EDI Select for the TEXT files to be converted to X12 or to EDIFACT protocol. To perform this conversion, the trading partner must enable both the TEXT and the X12 or EDIFACT protocol.See also TIBCO BusinessConnect EDI Protocol powered by Instream User’s Guide, "TEXT to EDI Conversion." Note For any request that is being sent from the private process to TIBCO BusinessConnect for TEXT documents, an appropriate OperationID must be specified instead of EDI/Outbound. Select a guideline file, such as X12_4040_850.sef.Click change to select the schema file associated with this message type. You can select the file type: File Reference or Uploaded File.
• For Uploaded File, click Browse to select a configuration file from the local file system.
Table 4 Notification Message: Schema Tab The fixed value T-LAYOUT is used since all TEXT guidelines use LAYOUT as the root element in EDISIM Standards Editor. Load a map file, such as PO_Positional_X12_4040_850.map.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |