Setting Up Hierarchical Configurations

Access the Hierarchical Configuration Definition Revisions form.

Address Number

Enter a number that identifies an entry in the address book, such as employee, applicant, participant, customer, supplier, tenant, or location.

Hierarchical Configuration

Enter the EDI 856 transaction set-hierarchy configuration-codes that specify the levels that are present in the Ship Notice/Manifest. This field is made up of a combination of two-character hierarchical level codes (values from the X12 specification for data element 735 - Hierarchical Level Code). Up to nine combinations of HLC codes can be in this field.

Hierarchical Structure Code

Enter a code indicating the hierarchical application structure of an EDI transaction set that uses the HL segment to define the structure of the transaction set.

Level

Enter a number to organize the table into a logical group for online viewing and reporting.

Field Name

Enter a data dictionary item name. Examples include F#MMCO or F#CO for company, F#MMCU or F#MCU for business unit, and F#RP01-30 for business unit category codes 01 through 30.

With the exception of #, @, and $, the system does not allow special characters as part of the data item name.

To create protected data names that software updates do not overwrite, use $xxx and @xxx, where xxx is user-defined.

Note: For report writer, on the Processing Options Setup form, the system uses the field name during data entry to edit the field size and other field attributes.

Ascending Descending

Enter a code to designate sorting sequence as ascending or descending. Values are:

A: Ascending

D: Descending

Note: This field is for use within the OPNQRYF command to designate the UNIQUEKEY parameter. The number of key sequence fields that you specify with the proceeding codes represent the number that is assigned to the UNIQUEKEY parameter. This parameter eliminates duplicate records for the specified keys.

Total Level

Enter a level break. You might specify the level of totaling to place on this field. The system allows up to nine levels of totals. If you do not specify levels of totals in an order that is consistent with the sequence parameters, unpredictable results might occur, for example:

Level 01 - Department Totals - Sort Sequence 03

Level 02 - Branch Totals - Sort Sequence 02

Level 03 - Division Totals - Sort Sequence 01

Level 10 - Grand Totals

If you specify the same totaling level on multiple data fields, you must enter a 1 in the first position of total level for all secondary fields, for example:

Level 01 - Business Unit (description comes from here).

Level 11 - Object (description ignored).

Level 11 - Subsidiary (description ignored).

Do not confuse this with account master or business unit master level-of-detail concept.