Managing Global and Local Data Elements. Gavin Cockayne and Ash Patel, IBM-Consulting Hans Kolbe, Celantra Systems. Global Data Elements – What is the problem ? .
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Managing Global and Local Data Elements
Gavin Cockayne and Ash Patel, IBM-Consulting
Hans Kolbe, Celantra Systems
OAUG Multi-National SIG Group
Global Data Elements –
What is the problem ?
Global Data Elements –
All data elements must be included in the analysis. In most cases, potential issues regarding “Global Data Elements” can be resolved using the following methods:
Naming convention - Develop a global naming convention so that users are aware of their elements.
Restricted setups - In some cases, restriction to certain setups can avoid issues.
Education – Educating ALL parties of the potentials issues they could cause and other could cause them is sufficient.
Global Police - A team of functional experts who role is to monitor and control global elements
Automation of Data Visibility and Access Control – what tools are available?
Perspectives for Naming Conventions and Data Access Process Definition
Example Listing of Data Elements
Example of Identification Needed
Examples of Solutions - GL
Journal Sources - Sources can be used globally and in most cases seeded sources are used globally, however, if changes are made to one of these sources e.g., requires approval then this change will affect all locations that use this source.
Cross Validation rules – Since cross validation rules can be accessed by anyone who has access to setup, it is critical that access is restricted and users are educated in the potential issues this could cause if not taken seriously.
Solutions Police all seeded sources and do not allow changes to any seeded source.
Use naming conventions to differentiate sources belonging to different entities.
Examples of Solutions – AR, AP, OM
AR Payment terms: Since this is functionality drives credit checking, discounts and due dates, it is imperative that this is looked at globally.
Solution: Education and Naming convention.
Customer headers - Customer headers are Global since some critical info is held at this level this could cause serious problems. For example if you are using “Sales Channel” as a qualifiers in pricing, if this is changed all pricing will be affected.
Solution: Custom pll – to associate customer to responsibility and restrict changes to customer setups if it is not your customer.
AP Payment terms - Since this drives when you pay your suppliers and discount you take, changes to this could be costly.
Solution: Naming convention , education
OM Price Lists – Price lists headers are global and if the same items are used in various orgs then the prices for those styles are available to all orgs
Solution: Custom pll - to associate pricelist header to responsibility and restrict changes to price lists if it is not your price list.
Pricing Modifiers are global - Access to modifiers and qualifiers are global
Solution: Functionality - Use Selling Org as first qualifier..
Detail –Customer Naming Convention - 1 -
Detail – Customer Naming Convention - 2 -
Questions - Discussion