Friday, December 9, 2011

Master Data Management "the how"

Master Data Management 
You may have a Master Data Management suite to compliment the item and party master in ERP;

Lesson Learned - It is critical and vital to understand the difference between "a point in time or one time event" captured via a transaction record.  The one time event DOES NOT authorize a change to the master record.

A segregation of duties "key control" must be monitored and a design in place to prevent un-authorized person's and consistently test the technology ecosystem to ensure no workarounds have been introduced into the ecosystem.

A change to a master record is governed by a duly signed master agreement between two legal entities.  A legal liability and court proceedings hold the executives of your company responsible for failing to adhere to the protection of customer, suppliers and employees.

A person must perform and document with an authorized change request any changes to a customer, supplier and employee record.

The requirements are stated as a corporate policy and should have associated procedures.  Data quality issues around the customer records often will be sourced from an unauthorized back-end update process.

The process is very much a human set of activities performed as a task in a process, based on a predefined procedure.  Point of Sales processing may be an exception, in this case all records are point of sale and the master relies upon the person capturing the transaction.

The sole purpose of a customer record intends to enable a revenue transaction.

The sole purpose of supplier record intends to enable an expense transaction.  

Pricing, Tax and entitlement may be reduced based on an adjustment to the master record.

A one time discount DOES NOT enable a new customer discount.  

The sole purpose of an item intends to determine cost of an offer and the result will be a series of revenue transactions.


Hierarchies
You are not going to replicate the ERP setup or the derived relationships in the structured hierarchies.
  • The key to success ensures the designed functions in ERP do not get devalued by failing to adhere to the procedures and process in your master record setup process limited to ERP for a number of reasons.   
  • Changes MUST not be allowed nor would replicate outside the system of record be enabled.
    • A single golden copy parsed into country segments allows for rapid deployment of daily updates and a historical view by management hierarchy.  
Party 
  • Organization and users
  • Customer and users (guest)
  • Suppliers and users (guest) 

Offer
  • Hardware-Immediate revenue recognition
  • Software-Based on registration of software or download confirmation
  • Service-Based on split by 12 months and recognized over each month in increments. 

No comments:

Post a Comment