Overview

Under Master Data, you can manage master data from the ERP system that must be adapted or cannot be provided by the ERP system. This data is used to enable special business processes in the functional areas of the application.

Additionally, you can manage code lists and codes that are used to configure the application.

Additional item, customer, carrier, ship to, and contact master data

Usually, master data is automatically imported from an ERP system. Sometimes, special master data cannot be provided by the ERP system. This information can be stored and managed in the Master Data area. You can add, for example, the preferential trade agreement, the preference criterion, the commodity code, and the customs procedure to the item master. The information is used by the Shipping area to process and print export-related documents.

You can also use the master data management as a stand-alone solution. For example: For packaging material that cannot be imported from the ERP system, you can create and manage your own item master data.

Before you can import master data from the ERP system, you must complete these steps:

  • Define the fields that are imported and updated automatically by the ERP system.
  • Define the fields that you manage without being overwritten by the master data import.
  • Activate the master data import.

Code Lists and Codes

Additional data is stored in code lists and codes. These code lists and codes are exclusively used by the application to configure business processes for special trading partners. Code lists and codes represent data that is required to run the application properly. This information is not contained in BOD messages that are processed by the application and is not provided by an ERP system. For example, style sheet rules are used by the functional area Transformation to transform messages of special trading partners. The properties of style sheet rules are defined in a code list and the associated codes:

  • Style Sheet File Name
  • Source Format File Description
  • Target Format File Description
  • Message Standard

Code lists include this information:

  • Header information
  • Individual properties

Codes include this information:

  • Code key entries
  • Individual property values for codes

A search hierarchy structure is used to store codes and to access the code information. You can select a hierarchy from the predefined hierarchy code lists, for example:

  • CodeListHierarchyAE with hierarchy tenant, accounting entity, and location: This search hierarchy structure is used in the code list TimeZonesOwn to determine the time zone of a user who is logged on to the application.
  • CodeListHierarchyTradingPartner with hierarchy tenant and trading partner: This search hierarchy structure is used in the code list UnitsOfMeasures to determine the trading partner-specific code mapping for units of measures.

Sequential Numbers

This function enables users to control the creation of sequential numbers in the application.

General Data Protection Regulation

The purpose of General Data Protection Regulation (GDPR) is to harmonize data privacy laws in the European Union (EU). Its goal is to put EU residents in control of their data, by regulating how that data is collected, processed, stored, and transferred. To support this regulation, you can anonymize any selected personal data from the application.

Inbound BODs

This function displays the list of inbound BODs that the Master Data Service received from ION. You can delete or reprocess the imported BODs.