If you need to understand how to find the right data within your packaged ERP or CRM system to help you with an Information Management project, then Safyr is the only practical way to achieve this without calling on your application implementation or support team, engaging expensive external consultants or spending time trying to find it manually.
Safyr has no direct competitors. Its features and capabilities for making packaged application metadata discoverable and usable are unique. Other traditional approaches include:
Template based solutions are a good starting point, however their value will depend on whether the version of the application is the same as yours, how customised your application is and of course whether a template exists for what you are working on. Even so, there would be a need to compare what is in the template to what is in your system.
In theory that will work, but the Table and Column names will be those in the ‘physical’ database, not the ‘logical’ names that describe what each table/column is for. Also there will be no relationships defined, as these are enforced by the application, not the database. Finally, even if you could make sense of the physical names and somehow determine the relationships between tables the sheer number of tables involved would make the model unusable. For example, an SAP application will have in excess of 90,000 tables making use of a data modeling tool completely inpractical. Even a relatively small enterprise Salesforce application will have several hundred tables. These are too large for a data model to be of any value.
Safyr uses a database (typically Oracle, SQL Server or DB2) to store the metadata it extracts from the ERP (this is called the Safyr repository). So the installation steps are: Install the Safyr software Create a new database or schema for the Safyr repository Configure the Safyr software to communicate with the repository Connect to the ERP to extract the metadata. Download the Safyr documentation for free here: https://www.silwoodtechnology.com/downloads-categories/product-documentation/
For SAP systems including SAP BW and SAP on HANA, Safyr uses an ABAP function to extract the metadata. These functions are certified by SAP. For Salesforce, Safyr uses the Salesforce metadata API. For the packaged applications from Oracle which are supported, Safyr uses SQL calls to extract the metadata from the ERP data dictionary. In all cases, only a small number of ERP ‘data dictionary’ tables are accessed to provide a full picture of the ERP system.
Safyr retrieves metadata from the Data Dictionary tables of each supported application. These tables do not normally change in structure from release to release. When a new version of an application is installed, its metadata can be loaded into Safyr, simply be doing another re-extraction. Safyr also offers capabilities to compare full or partial repositories containing metadata from the same application. This will help you to understand differences between versions or instances.
Safyr extracts metadata from the application Data Dictionary tables. Using this approach, will include any new or changed tables developed by the customer.
That will work, but the Table and Column names will be those in the ‘physical’ database, not the ‘logical’ names that describe what each table/column is for. And there will be no relationships defined, as these are enforced by the application, not the database. Only by looking at the proprietary data dictionary of the ERP can a useful, logical view of the ERP be obtained.
Yes, the metadata is contained within the packaged application, however it is not in a readily accessible or easy to understand form. In fact, SAP have told customers that the data model for their application is “not available”. Safyr provides powerful search facilities for searching and utilizing metadata that are just not available in the packaged applications. It also has a range of export facilities to create fully detailed models in a range of data modeling tool and Repository environments.
The Safyr Repository can be established in an Oracle, DB2, Microsoft SQL Server, Sybase SQLAnywhere or SQLite database.
This depends on the ERP. If the ERP supports multi-language texts then Safyr can extract the descriptive texts for each object (Table, Field…) in the language(s) of choice.
Yes, Safyr now has an ‘ETL for Metadata’ capability which means that metadata from other packaged applications can be imported into a repository. Once the process has been completed for one instance of the source application, it can be repeated for other instances. For example, Safyr can now import metadata from Microsoft Dynamics using this mechanism. The value of this exercise will depend on the quality of the metadata itself. Please contact Silwood Technology or your normal Safyr reseller for more information.
Reduced risk of project delay or poor data being introduced into the information ecosystem because all metadata can be easily found and used. Increased productivity of up to 90% when comparing source data analysis using Safyr with other methods. Reduced risk of poor data being introduced into the information ecosystem because all metadata can be easily found and used. Faster delivery of Information Management projects because data professionals are in control of finding accurate metadata. Reduced costs because of reduced reliance on other internal and external resources.
Safyr is used by hundreds of companies to help them deliver Information Management projects more efficiently. Examples include: Boeing – Costco – RS Components – AMD – Hydro Tasmania – RBS – Commscope – Procter & Gamble – BP.
If you cannot find the answer to your question, please contact us.
You must be registered to receive support
Please login or Register Here »
Note: The token is a unique string for each Safyr license and can be found on your product delivery instructionsAlready registered? Login here »
Enter your username
to receive your password