Follow Us


News and Events

“The party domain can represent any kind of person or organization, including customers, suppliers, employees, distributors, and organizations. Each of these kinds of party shares a common set of attributes, such as the name of the party, where it is located (a party may have multiple locations), how to contact it, what kind of relationship the organization has with the party, and so forth. The account domain describes how a party is related to a product or service that the organization offers.

“The domains of party, product, and account overlap. Areas of overlap indicate relationships. For example, when we define a product, we often need to specify the party that supplies that product. Explicitly capturing these relationships within the same environment allows us to address business questions that may be otherwise difficult to resolve. If we record the party that supplies a product as well as the parties that we sell products to, then we can determine which of our suppliers are also our customers. Understanding the full set of linkages that an organization has with a partner can be valuable in all aspects of working with that partner, from establishing mutually beneficial agreements to ensuring an appropriate level of support. Indeed, the key benefit of supporting multiple domains of master data within the same system is that it clarifies these cross-domain relationships.”

- TechTarget

GM-X Trading Relationships Features

GM-X integrates party data management for organizations, customers, suppliers, distributors and employees with product data management for both products and services, including work effort assignments.

For businesses conducting external operations, traditional ERP, accounting, customer relationship management (CRM) and supplier relationship management (SRM) applications are not fit for purpose because they keep organizations, customers, suppliers, distributors in separate domains. The GM-X party data management architecture captures and clarifies the cross-domain relationships necessary for conducting external operations efficiently.

Party subsystem for organizations, people and locations [top]

Party data management:

•  Any number of parties can be defined

•  Parties may represent organizations or persons

•  Maintains corporate registration and tax registration information for organizations

•  Maintains identity and other personal information for persons

•  Maintains-user defined terms of trade for each party

•  Supports effective and discontinue dates

•  Allows credit checks to be performed for a party

•  Optionally allows a party to be blocked or prevented from trading

•  Allows entry of free-form notes as well as user-defined fields and values for parties

•  Allows organizations to be classified by user-defined type and sub-type

•  Allows any number of party categories and sub-categories to be defined

•  Allows each party to have any number of categories or sub-categories

Party identification:

•  Supports standard GS1 (company prefix or GLN) and other alternate identity types

•  Allows alternate identities, including account numbers, to be provided for each party

Party relationships:

•  Allows any number of party roles to be defined such as customer, supplier, employee

•  Roles can apply to organizations, persons or both

•  Allows each role to be broken down into sub-types such as bill-to and ship-to customer

•  Allows any number of roles to be assigned to each party

•  Allows any number of party relationship types and priorities to be defined

•  Allows any number of party relationship statuses (active, inactive, on hold) to be defined

•  Maintains roles, relationships, priorities and status of relationships (party pairs)

•  Supports effective and discontinue dates for party relationships

Party collaboration:

•  Supports any number of contact mechanisms (address, phone, fax, E-mail, URL)

•  Supports any number of contact purposes as in primary and secondary address or phone

•  Allows any number of contact mechanisms to be assigned to each party, by role sub-type

•  Contact mechanisms, assignments and purposes can have effective and discontinue dates

•  Tracks all incoming and outgoing E-mail messages for specific parties, orders or invoices

•  Supports any number of E-mail queues for different business areas or individual users

•  Supports the definition of signatures and signature attachments for each user and queue

•  Supports automatic attachment of specific documents to outgoing E-mail messages

•  Identifies E-mail accounts to be scanned for incoming E-mail messages

•  Maintains an optional blacklist for specified E-mail accounts to block auto-acknowledgment

•  Tracks E-mail topics, threads or conversations as E-mail cases

•  Retains the content of all sent and received E-mail messages including attachments

Party addresses and territories:

•  Maintains details for any number of postal addresses

•  Supports any number of territory types (country, state, province, postal code, sales area)

•  Allows any number of geographic areas and aliases to be defined for each territory type

•  Allows multi-level hierarchies of geographic areas to be maintained

•  Links each postal address to the geographic area(s) where it is located

•  Postal address format can be specified by country, to comply with postal agency standards

•  Supports alternate East Asian address formats for China, Japan, Korea and Taiwan

Product subsystem for goods and services provided by parties [top]

•  Identifies which products and services are available from which suppliers

•  Maintains preferences and priorities that may be linked to replenishment details

•  Rates the overall performance of a product or service obtained from a specific supplier

Work Effort subsystem for assigning party roles [top]

•  Identifies each party’s role when assigned to a work effort