Setting Up Hierarchical Configurations

Access the Hierarchical Configuration Definition Revisions form.

Address Number

Enter a number that identifies an entry in the Address Book system, 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 present in the Ship Notice/Manifest. This field is made up of a combination of 2 character Hierarchical Level Codes (HLC) (values from the X12 specification for data element 735 - HLC). There can be up to 9 combinations of HLCs in this field.

Hierarchical Structure Code

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

Level

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

Field Name

Enter a UDC (47/FD) for the 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.

Special characters are not allowed as part of the data item name, except #, @, $.

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

Ascending Descending

Enter an A: to designate ascending sorting sequence or D: for descending sorting sequence.

Note: For use within OPNQRYF command to designate the UNIQUEKEY parameter. The number of key sequence fields specified with these codes represent the number assigned to the UNIQUEKEY parameter. This parameter eliminates duplicate records for the specified keys.

U: Ascending

V: Descending

Total Level

Enter a level break, not to be confused with Account Master or Business Unit Master level of detail concept. You might specify the level of totaling to place on this field. Up to 9 levels of totals are permissible. If levels of totals are not specified in an order consistent with the sequence parameters, unpredictable results may occur.

For example:

Level 01 - Department Totals - Sort Sequence 03

Level 02 - Branch Totals - Sort Sequence 03

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 1st 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)