Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« ETL vs. ELT | Main | Automate your File based Data Loads in FDMEE with Open Batches »

Avoid Validation failures with DRM Validation checks

Avoid Validation failures with DRM Validation checks

Data Relationship Management (DRM) as a master data management solution has been a favorite in a complex EPM and EBS landscape for its audit and versioning features along with other unique features. Now that DRM is available in cloud, its adaption for customers is expected to increase multifold. This blog would help you in understanding validation checks configuration in DRM that would help in finding any issues before your target systems get impacted.

Whenever a metadata update is done in DRM, it is advisable to do a few checks. The most vital of these checks is to ensure that all the target system exports that may be affected by the metadata update are frisked for any validation failures. This is especially important when new members are added or any existing members are deleted. This blog talks in detail about the process of validating the exports and hierarchies after a masterdata update. It also highlights how to go about fixing a validation failure, if there is any.

You may ask as to why is this this important? DRM Hierarchies and Exports are used for supplying various downstream systems with masterdata. These hierarchies and target system exports in DRM have validations applied to them. These validations are to ensure that certain business requirements are being met during masterdata maintenance. So, whenever there is a masterdata update done to the system, it becomes imperative for the DRM Admins to validate all the hierarchies and exports that may have got affected by the update.

Detailed Process for Validation Check:

Doing the validation check is a very simple process. Let us assume that some metadata update was done in the 'Total_AuditTrail' hierarchy. So, our next steps would be:

  • Open the related exports. In this case, let us assume that the export that is affected is 'HFM_AuditTrail_ParentChild'.

  • Click on the 'Run Export Validations' icon at the top left corner of the screen (shown below as well).


  • DRM would run a check to ensure that the metadata changes are meeting the criterion of all the validations that are applied on the Hierarchy or the export. If all the validations are being met, we will get a success message like below.

Note: Running the validation check does not mean that we are exporting anything to any target system, and is completely unrelated to any metadata being exported to the target. So, feel free to run this check as many times as required.

Now, let's consider a scenario in which the Validation check returns error.

  • Let us assume that we are running the validation check on the export HFM_Area_MemberAttributes'. Click the 'Run Export Validations' icon.

  • DRM would run a check to verify whether all the validations are being met and return you to the home screen.



  • Click on the 'Validation Results' tab.

  • The Validation Results tab will highlight all the members which have failed the validations check.


  • Click on the Go icon to be directed to the nodes that have failed the validation check.


  • Clicking on the GO Icon again will take you to the position of that particular member in the Hierarchy.

The above process will help you in identifying the error within minutes so that it may be fixed at the earliest. After making the required modifications, run the validation checks again to ensure that the export has no more validation failures.

Alternately, you may also run the Validation Check at the Hierarchy Level as well.

  • In the below example, let us assume that we had made some metadata updates in the ar.NVCLS hierarchy. When you have finished making the metadata changes, select the top member of the hierarchy, and right click. In the validate option, select 'Assigned'.






  • This will also highlight the validation errors in the same way.

    Note: Running the validation check whenever metadata is updated is a best practice suggested by Oracle.


Hi, I found that your post about validation is very helpful, thanks!. Though I have few questions regarding. I am trying to run an export validation, but it says that that "validations were run because the Batch Validation mode is set to None.". I've already assigned validations to the version and even each hierarchies. It would be very nice if you can help with this issue. Thank you.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles