The Component Explorer allows you to create a new trading partner component in a desired folder. The current document standards that you can define are X12 and EDIFACT. The trading partner component can be configured for your company or your trading partner.
Review the configuration options below to understand the differences between each type.
Trading Partner General Tab
| Field |
Description |
| Type |
Defaults to ANSI X12 EDI |
| Identifier |
Text box that holds generic identifier for trading partner or company. Generally defaults to Interchange ID. |
Trading Partner Contact Info Tab
This tab holds reference information for your trading partner or company that has no impact on input or output data.
Trading Partner X12 Options Tab
AtomSphere will automatically validate your inbound and outbound files based on the data populated within this tab. Certain envelope fields are omitted in the section because AtomSphere will automatically populate these fields when sending outbound data. Refer to the upcoming Understanding the X12 EDI Standard section to learn how the ISA/GS envelopes work with the trading partner component.
Basic X12 Options
'No Options for My Company' by default. Functional Acknowledgement options are defined at this level and are only required when constructing your trading partner.
ISA Identification and Version /Control Options
Refer to X12 EDI specifications to understand proper values for these fields. You can find info on how to differentiate data elements in the EDI Profile guide.
| Field |
Description |
| Author Info Qualifier (ISA01) |
Drop-down Value for Authorization Info ID |
| Author Info (ISA02) |
Character value for authorization information. |
| Security Info Qualifier (ISA03) |
Security Drop-down Value |
| Security Info (ISA04) |
Character value for security information |
| Interchange ID Qualifier (ISA05/07) |
Drop-down qualifier value for main Interchange ID type. The 05 or 07 data element value refers to the inbound or outbound direction of the X12 document. |
| Interchange ID ISA06/08) |
Value for main Interchange ID. The 06 or 08 data element value refers to the inbound or outbound direction of the X12 document. |
| Interchange Standard ID (ISA11) |
Value that is commonly U for all X12 standards before 5010. For 5010 and above, the qualifier is ':' |
| Interchange Version (ISA12) |
Value that identifies the version you will be transmitting. If your company uses multiple standards you will need to create an EDI profile for each; identifying the profile name with the standard you are using. Example: Version 4010: 00401 |
| Interchange Ack. Requested (ISA14) |
Check box for 1 or 0 true/false value |
| Test Indicator (ISA15) |
Character value that denotes test status of X12 document. Commonly populated as 'T' for test or 'P' for production. |
| Component Separator (ISA16) |
Value that identifies separator for data sub-element components. Commonly defaults to ':' or '>'. |
GS Version / Control Options
| Field |
Description |
| Application Code (GS02/03) |
Value for the identifier of the sender/receiver and is usually the same as the ISA06/08 |
| Responsible Agency Code (GS07 |
Value for the standard body identifier for the type of document being sent. In most cases, it is X |
| GS Version (GS08) |
Value for the version of the standard being used. Two zeros are placed in from of the version type. Example: 5010 = 005010 |
Trading Partner Document Types Tab
This tab is visible only when building a component for your trading partner.
AtomSphere manages X12 field validation based on documents sent by or sent to your trading partner. Under this tab, you must define all X12 transmissions that will be sent to or received by your trading partner.
- Transmission: Numbered transaction values that specify the data you are trading.
| Field |
Description |
| Type |
Transmission number identified upon highlighting |
| Profile |
Identifies the X12 EDI profile that represents the inbound/outbound data structure for the transmission. Required for field-level validation and acknowledgement handling. |
| Tracked Fields |
Allows for custom field tracking on the Manage tab. Refer to the upcoming Trading Partner Document Tracking section to learn how to set up these custom fields. |
Trading Partner Communication Tab
AtomSphere trading partners also control the communication protocol used to send and receive documents. There are different settings required for either your company or trading partner. Refer to the upcoming Working with Trading Partners section to understand how different communication scenarios are enabled for a trading partner process.
The 'Your Company' component contains the communication/connection settings that will be used by default when paired with 1 or more trading partners. This is useful if you use a VAN or central location to manage the sending and receiving of data for all trading partners. Communication settings for each trading partner are configurable within the direct trading partner component.
The available communication methods for B2B integration are as follows. 1 or more methods can be defined in both trading partner types. The field settings for each method are the same as what you can define in the corresponding connector. Refer to the connector links to understand the details for each.
| Communication Method |
Description |
| Disk Connector |
- Get Options: Define connection directory and disk get operation settings
- Send Options: Define connection directory and disk send operation settings
If you selected My Company it applies default options. Settings are overridden when linked Trading Partners' 'Use Default Settings' check box is unchecked.
|
AS2 Connector
- Client - for sending
- Shared Server - for listening
|
- AS2 Info: For you trading partner, you can define the URL you would like to send to and SSL certificate if using HTTPS. AS2 Info settings for your company only allow you to identify the AS2 ID and certificates because all inbound listen communication is managed by the Shared Web Server.
- Options: Define Message and MDN Options for all outbound communication to your trading partner.
- Settings: Indicator for your company that the AS2 inbound settings are managed by the Shared Web Server.
|
| FTP Connector |
- Settings: Define host connection and log-in credentials.
- Get Options: Define ftp get operation settings
- Send Options: Define ftp send operation settings
If you selected My Company it applies default options. Settings are overridden when linked Trading Partners' 'Use Default Settings' check box is unchecked.
|
Trading Partner Archiving Tab
The archiving options are similar to the connector operation archiving settings defined here. Because trading partner components can handle both inbound and outbound documents, there are separate directory setting options for each.
This page
Other pages
Account
