NexCommand AINexCom Knowledge Base
Field reference

Common Code

How to use Common Code in Shared Reference Data: access, working steps, fields, related records and troubleshooting.

Purpose and access

Maintain approved reference lists and directory relationships. For locations, select country, region and city from the directory. For classifications, preserve the parent-child hierarchy and code identifiers.

This page is a record page in System Admin → Shared Reference Data. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Prepare the required information: Code List, Title, Common Code.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open Common Code from System Admin → Shared Reference Data, or use ERP Search.
  2. Filter the list and open the relevant record. To add a record, use Add/New when your role provides that action.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Add the required child rows. Review each row’s identifiers, linked records and values, using the child-table field reference below.
  5. Save the record and address validation messages. Reload and verify the saved values and relationships.
  6. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
Code Listcode_listLink
Required
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: Code List

Canonical URIcanonical_uriData
Optional
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
TitletitleData
Required
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
Common Codecommon_codeData
Required
Enter the identifier or short text requested by the label. Preserve external reference numbers accurately.
DescriptiondescriptionSmall Text
Optional
Provide concise contextual information relevant to the record. Avoid unrelated personal or confidential data.
Additional Dataadditional_dataCode
Optional · Read-only
Administrator/integration field. Use a validated configuration or supported script and test its impact before deployment.
Applies Toapplies_toTable
Optional
Add the relevant child rows and review required columns, quantities and references before saving.

Linked record: Dynamic Link

Child tables

Applies To — child-row fields
FieldType / behaviorHow to use it
Link Document Typelink_doctypeLink
Required
Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

Link Namelink_nameDynamic Link
Required
Select the record identified by the associated document-type field. Verify both the type and the linked record.
Link Titlelink_titleRead Only
Optional · Read-only
System-provided value; correct its source record or calculation rather than overwriting the displayed result.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.