Using PeopleSoft metadata to model Customer Master

This is the latest in our occasional series of data models which we have produced using Safyr®. These give some insight into those common business areas in SAP and ORACLE applications for which an understanding of how the underlying metadata is structured are often required for Information Management projects.

It’s a group of tables in the form of a data model from a PeopleSoft system showing a set of Customer tables and relationships.

I used Safyr® for PeopleSoft to achieve this very quickly and easily.

The model was created following some analysis in Safyr and then exported to Safyr’s own ERDiagrammer tool. The diagram is shown at the ‘Primary and Foreign Key’ display level. This masks some of the complexity of having a diagram showing all the attributes of each table, especially as some of the PeopleSoft tables have a lot of attributes.

You can download it here.

PeopleSoft Customer Master Data Model

I can easily make the same set of tables available in ERwin, ER/Studio or PowerDesigner formats – please feel free to ask if you would like to see it in one of those formats. There is no obligation and I’d be happy to provide.

The starting point for this model was a search for ‘Customer’ on the PeopleSoft descriptive name in Safyr. This quickly identified ‘Customer Header’ as a key table, and it was easy to then look at related tales to get a clear picture of the extended set of tables holding customer information.

As we have mentioned before in other blog posts, part of the problem is knowing where to stop. The tables and relationships required for any given project will depend on the scope of the work involved – and only the project team know what that is. And that’s the real purpose of Safyr:  to allow project teams to do their own analysis and ‘scoping’, without having to be an expert in the package.

This is why Safyr is so effective in reducing the time and resource needed to locate the right tables from the source application in the context of the project requirement. In addition it provides benefits to the organisation in terms of quality of data and the business’ trust in the data.

As we are providing something which is usable in some contexts… here is the legal bit. In no event will Silwood Technology Ltd be liable for any indirect, special or consequential loss arising out of or in any way relating to the use or performance or the use or misuse of the information presented in this model.

You can find other example models from other ERPs in earlier blog posts.

Please let me know what you think.

Nick Porter
Technology Director