...

There are two differences between CCTS definition and actual table definitions.

1. ACC table has based_acc_id to support hierarchical type reference. The reason we introduced this is that most data exchange libraries have use the notion of inheritance to maximize reusability and ease of conceptualization. For example, both Customer Party and Supplier Party can share a common based ACC Party.

2. Core Data Type (CDT) and Business Data Type (BDT) are both represented in DT table. In practice, standard developers have defined their BDT as standard definitions based on the UN/CEFACT standard CDTs, and end-users use them without further manipulations in BIEs. Therefore, Score provides the functionality to define BDTs only for the standard developer user and BDTs can be used directly with the CCs as no further customization is enabled when defining a BIE.

Core Components (CCs) Naming Rules

...

• Finally, bdt_pri_restri and bdt_sc_pri_restri tables have the domain restrictions of BDTs to define value domains of BBIE and BBIE_SC.

...

A top-level ASBIEP is a concept BIE to indicate the root of the BIE hierarachy hierarchy tree. The following diagram describes the relationship between top_level_asbiep and BIE tables. When the Create BIE menu is invoked on the UI, a is created and also its descendant BIEs including the ABIEP, ABIE, BBIE, etc.

...

Module is an entity representing a directory and file structure that Score uses to express schemas into a file system. From this definition, each module has two types: ‘File’ and ‘Directory’, and only ‘File’ type modules can contain components, and ‘Directory’ type modules can contain ‘File’ modules. A set of modules can be used in one or more releases, so each module set is associated with release manifests. The following diagram shows these relationships. Note that the digram did not display all manifest tables in the database schema by a lack of space.

...

Every module-manifest relational table on the right (such as module_ASCCP_manifest)has the same pattern, that it has module_id and module_set_release_id to indicate which module entities and sets are associated with specific manifest components for releases.

...

...

Now, all (traverse/insert/remove) operations in seq_key follow the same logic in doubly linked list. For example, if a new ASCC is inserted before the Party. Employee Contract. Contract, it can have 101 seq_key column but the actual order is kept in the seq_key table..

Business Contexts

Business context is a discriminator for categorizing BIEs according to their use in business circumstances. In CCTS, business contexts could be described for the BIE by assigning context categories and its scheme values. The following diagram illustrates the relationship between BIEs and business contexts.

...