Follow Us

Resources

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 Sales and Delivery Features



GM-X integrates requests and quotations, sales order processing, inventory control, shipping and receiving and customer invoicing into end-to-end sales and delivery workflows.

In seller-side deployments, GM-X is utilized only by a client organization’s own employees. Documents originating from customers, such as requests for information (RFI), requests for quotation (RFQ), requests for proposals (RFP) and purchase orders, may be entered into the client organization’s GM-X system for tracking purposes, but the sales and delivery workflow process is confined to the client organization. This is the way traditional ERP systems work.

Because the GM-X party data management architecture captures collaborative trading relationships, and its inventory subsystem is able to track each organization’s own stock as well as in-transit, consignment, field and trunk stock managed by its trading partners, GM-X can be utilized by employees of both customers and suppliers. For collaborative supply chain trading execution deployments, the sales and delivery workflow process embraces both organizations. Traditional ERP systems were never designed to meet this requirement, but GM-X handles collaborative supply chain trading execution with ease.


Request subsystem for customer requests and supplier quotes [top]

Requests:

•  Supports multiple user-defined request types (RFI, RFP, RFQ and others)

•  Maintains and tracks requests and request details

•  Supports response deadlines and required-by dates for request details

•  Supports free-form request notes

•  Supports multiple user-defined request roles such as manager, originator, preparer, QA

•  Identifies the parties who may respond to a request, and their respective roles

•  Supports multiple request statuses such as pending, in progress, completed

•  Automatically tracks the status history for each request

Quotes:

•  Supports multiple user-defined quote types, such as proposals or quotations

•  Maintains and tracks quotes and quote details for goods, services or features

•  Allows quotes to be created by copying the relevant requests and request details

•  Links quote details to the relevant request details

•  Supports issue, validity and estimated delivery dates

•  Supports multiple user-defined terms of trade for quotes

•  Allows terms of trade for quotes to be linked to quotes or individual quote details

•  Allows entry of user-defined fields and values for quotes and quote details

•  Supports multiple user-defined quote roles such as issuer, receiver, approved by

•  Identifies respective roles of a quote’s issuing and receiving parties

•  Supports multiple quote statuses such as pending, submitted, on hold, approved

•  Automatically tracks the status history for each quote and its details


Order subsystem for sales orders [top]

Sales order entry and management:

•  Supports multiple user-defined sales types such as Internet, catalog, wholesale, retail

•  Maintains and tracks sales orders and details for goods, services or features

•  Optionally links each sales order to the relevant request

•  Links sales order details to the relevant quote details or to related order details

•  Maintains order date, due date, earliest ship date and contacts for sales orders

•  Automatically adds standard or required features to sales order details

•  Allows user selection of optional features for sales order details

•  Automatically determines applicable prices, discounts and allowances

•  Supports and automatically applies discount vouchers for promotional campaigns

•  Automatically determines applicable surcharges and taxes

•  Maintains estimated delivery dates for sales order details

•  Maintains shipping instructions and comments for sales order details

•  Maintains supplier notes and supplier part numbers for sales order details

•  Supports sample sales

•  Supports multiple user-defined terms of trade for sales orders

•  Allows terms of trade for sales orders to be linked to sales orders or sales order details

•  Allows entry of user-defined fields and values for sales orders and sales order details

•  Supports multiple user-defined sales order roles such as buyer, salesperson, authorizer

•  Identifies respective roles of a sales order’s issuing and receiving parties

•  E-mails can be sent automatically to customers on change of order status

•  Supports sales order statuses such as pending, confirmed, on hold, approved, invoiced

•  Allows user-defined rules governing allowable sales order status changes

•  Automatically tracks the status history for each sales order and its details

Online sales (B2C or B2B):

•  Can receive new orders automatically from front-end/external Web sites via Web services

•  Ability to retain sales orders and details in a customer’s shopping cart prior to checkout

•  For Cart details, retains information about selected products, services and features

•  Supports any number of online payment gateways such as PayPal® or credit cards

•  Optional customer payment by bank transfer and acceptance of bank transfers

•  Supports any number of online payment statuses received from payment gateways

Sales reporting:

•  Sales totals by period and group with optional spreadsheet download

•  Sales totals by product, period and group with optional spreadsheet download


Inventory subsystem for picking and receiving [top]

Sales order fulfillment:

•  Optionally allows inventory to be reserved for a sales order when the order is entered

•  Uses configurable rules to determine the required approvals before generating pick lists

•  Optionally allows inventory to be reserved for a sales order when pick lists are generated

•  Supports multiple user-defined inventory picking roles such as stock clerk or manager

•  Issues stock from inventory to fulfill sales orders, together with related features

•  Tracks the inventory picking roles and parties involved in each stock issue

Receiving (collaborative GM-X deployments):

•  Receives stock into inventory that was previously issued to fulfill sales order details

•  Supports non-conformance statuses such as issued, response required/received, closed

•  Maintains and tracks non-conformance reports when problems are found during receiving


Shipment subsystem for shipping, returns and delivery [top]

Outbound customer order shipping:

•  Supports outbound customer shipments (goods being sent to a customer)

•  Supports drop shipments (goods shipped direct from supplier to customer by distributor)

•  Links each shipment to the relevant sales order

•  Each shipment contains one or more outbound packages

•  Each outbound package contains quantities packed for one or more sales order details

•  Automatically tracks the status history for each shipment

•  Supports identification of carriers as parties

•  Supports multiple user-defined transport modes and assignment of modes to carriers

•  Supports multiple user-defined delivery vehicle types

•  Maintains information for any number of individual vehicles in a delivery fleet

•  One or more shipments may be despatched together

•  Supports one or more despatches per shipment for multi-modal shipments

•  Each despatch has a specific carrier and may optionally be linked to a vehicle

•  Prints bar-coded despatch labels with optional status

•  Tracks the outbound packages in the shipments for each despatch

•  Tracks delivery date and time with optional rejection reason and notes

•  Optionally tracks transit times, mileage and fuel consumption for each despatch

Inbound customer order returns:

•  Supports inbound customer returns (goods being returned by a customer)

•  Maintains and tracks return material authorizations (RMA) and details

Inbound and outbound shipping (collaborative GM-X deployments):

•  Supports inbound supplier shipments (goods being received from a supplier)

•  Supports outbound purchase returns (goods being returned to a supplier)

•  Supports multiple user-defined rejection reasons

•  Shipments have one or more inbound packages with accepted and rejected quantities

•  Inbound packages may identify order details, products and their related features

•  Supports multiple user-defined receiving roles such as signing, inspecting and put away

•  Tracks the inventory receiving roles and parties involved in each receipt


Invoice subsystem for customer invoicing [top]

Invoice creation from sales orders:

•  Maintains and tracks invoices and details for goods, services or features

•  Optionally links each invoice to the relevant sales order

•  Maintains invoice date and tax date

•  Supports multiple user-defined terms of trade for invoices

•  Allows terms of trade for invoices to be linked to individual invoices or invoice details

•  Supports automatic creation of invoices directly from sales orders

•  Supports multiple user-defined invoicing roles such as data entry clerk, approver, receiver

•  Identifies respective roles of an invoice’s issuing and receiving parties

•  Constructs invoices as PDF documents that can be sent to customers by E-mail

•  Maintains E-mail subject and message text for invoices sent to customers by E-mail

•  Supports invoice statuses such as pending, approved, sent, void

•  Automatically tracks the status history for each invoice

Manual invoice and credit note creation:

•  Automatically adds standard or required features to invoice details

•  Allows user selection of optional features for invoice details

•  Automatically determines applicable prices, discounts and allowances

•  Automatically determines applicable surcharges and taxes

•  Supports manual creation of credit notes and details