Standard Rule Tab - select Function

The Select function enables you to select entries from a location table, cross-reference table, partner table, or lookup table (all tables created in the Sterling Gentran:Server® Partner Editor). You can then map the fields/elements in those tables to one or more fields/elements in the data.

The Select function uses the value of the current field, element, or TFD to perform the selection.

The Select function allows you to use information from the Sterling Gentran:Server Partner Editor in your maps or forms. You can map information from your partner’s profile or Internal System Partner in the Partner Editor to a selected element or field in the map or form. The definition information and location tables that you define for the internal system partner can be used for all partners. The information that you can use includes:

  • Partner or Internal System Partner Definition (Name, EDI Code, Application Code)
  • Partner or Internal System Partner Location Table Fields
  • Lookup Table Fields
  • Cross-Reference Table Fields
  • Interchange, Group, or Document Record
Table 1. Select standard rule parts and functions
Part Function
table and key (or group) Specifies the table and key the system uses to select data. This table lists the valid values.
name of sub-table Contains the sub-table name, if appropriate. (See the table below.)

The sub table box is only active if you select Partner Lookup, Partner cross-reference by my item, Partner xref by partner item, Division lookup, Division cross-reference by my item, or Division cross-reference by partner item from the table and key list.

Raise compliance error Specifies whether you want the system to generate an error if the Select does not find a valid table entry.
Note: The default is cleared (do not generate an error if the Select is not successful).
Map from Specifies the element/field/TFD from the specified table entry from which you want to map the contents.
Note: Entries are displayed in the map from list only after you select a table and key.
Map to Specifies the element/field/TFD to which you want to map the contents of the map from box.
Notes:
  • A total of eight fields can be mapped using one Select rule.
  • Entries are displayed in the map to list only after you select a table and key, and these entries are activated only after you highlight an entry in the map from box.
Table 2. Types of sub-tables
Name Description
Partner by EDI code Indicates that the key is the partner's EDI Code and enables you to map from one of three fields for this partner (Name, EDI Code, Alternate Code) from the partner table.
Partner by alternate code Indicates that the key is the partner's Application Code and enables you to map from one of three fields for this partner (Name, EDI Code, Alternate Code) from the partner table.
Partner by partner key Indicates that the key is the partner's Profile ID enables you to map from one of three fields for this partner (Name, EDI Code, Alternate Code) from the partner table.
Partner location by name Indicates that the name on the Locations dialog box (for the current partner) of the Partner Editor is the key and enables you to map from any field in that table.
Partner lookup Indicates that the key is the partner lookup table name for this partner and enables you to map from any field in that table.
Partner cross-reference by my item Indicates that the key is the your item (value) on the partner cross-reference table for this partner and enables you to map from any field in that table.
Partner cross-reference by partner item Indicates that the key is the your partner's item (value) on the partner cross-reference table for this partner and enables you to map from any field in that table.
Division Enables you to map from one of three fields (Name, EDI Code, Alternate Code) for the <Internal System User> (system partner) in that table.
Division location by name Indicates that the key is the name on the Locations dialog box of the Partner Editor for the <Internal System User> and enables you to map from any field in that table.
Division lookup Indicates that the key is the partner lookup table name for the <Internal System User> partner and enables you to map from any field in that table.
Division cross-reference by my item Indicates that the key is the your item (value) on the partner cross-reference table for the <Internal System User> partner and enables you to map from any field in that table.
Division cross-reference by partner item Indicates that the key is the your partner's item (value) on the partner cross-reference table for the <Internal System User> partner and enables you to map from any field in that table.
Document record Enables you to map from any of the fields within the current document record.
Notes:
  • This sub-table can only be accessed from the following map types: Transaction Break/Build, Import, Export, Print, Screen, Group Build, and Interchange Build.
  • The information that is accessed will be the information of the last document that was processed at the table level accessed by the rules. This must be taken into consideration when using rules that access these tables.
Generic envelope segment Enables you to map from any of the fields within the current envelope information, regardless of the EDI standard used.
Note: This function is normally not used unless you are familiar with the generic envelope table structure for a given standard.
Interchange Enables you to map from any of the fields within the current interchange record.
Notes:
  • This sub-table can only be accessed from the following map types: Interchange Break or Build, Group Break, Transaction Break, and Export.
  • The information that is accessed will be the information of the last interchange that was processed at the table level accessed by the rules. This must be taken into consideration when using rules that access these tables.
Group Enables you to map from any of the fields within the current group record.
Notes:
  • Can only be accessed from the following map types: Group Break or Build, Transaction Break, Export, and Interchange Build.
  • The information that is accessed will be the information of the last group that was processed at the table level accessed by the rules. This must be taken into consideration when using rules that access these tables.