8.2.2 ADS – Source Data Reports (DFCS - PBSMCS)

The ADS Data Visualization – Source Data Reports provide a transparent view of data being transferred from DFCS to downstream applications such as PBSMCS via ADS (Application Data Services) connectors.

This feature enables users to preview, validate, and analyze the exact dataset before it is consumed by downstream applications. It enhances transparency, improves testing efficiency, and reduces integration risks.

To review data shared via ADS:

  1. Home → Catalog → Shared folders → Data Foundation reports → Source Data → ADS_PBSM.

Within the Source Data folder, users can access reports corresponding to data delivered to various ADS-connected applications.

Purpose:
  • Provide visibility into data being shared through ADS
  • Allow users to screen and inspect data before transfer
  • Support validation and reconciliation activities
  • Improve testing efficiency during implementation and upgrades
  • Reduce data exchange errors between DFCS and PBSMCS
  • Increase confidence in data integration processes
  • Each Entity report corresponds to a specific PBSMCS entity.
  • Example:
    • Data transferred to the PBSMCS entity “Stage Assets” is available in its own dedicated report.

Source Entity Tabs

Within each report:

  • Separate tabs represent each DFCS source entity contributing data. Examples:
    • Loans
    • Bills
    • Customer Hierarchy
    • Party Master
    • Stage Payment Schedule
    • Stage Loan Commitments

Insights Provided:

Data Transparency
  • View the exact dataset version being shared via ADS
  • Validate effective dates (“As Of Date”)
  • Confirm completeness of records
  • Identify missing or duplicate entries

Hierarchy Validation

For hierarchy-based entities (e.g., Party Hierarchy):

  • Review Parent–Child relationships
  • Verify hierarchy codes
  • Confirm Leaf vs Non-Leaf structure
  • Validate correct roll-up logic

This ensures structural integrity before downstream consumption.

Data Source Traceability
  • Identify originating DFCS data source (e.g., SRC1, SRC_4)
  • Validate source system contribution
  • Confirm multi-source integration logic
Financial & Attribute Validation
  • Validate numeric fields (e.g., income, commitments)
  • Ensure correct attribute population
  • Confirm mapping consistency
LoV Mapper
  • A clear mapping view between DFCS dimension values and downstream PBSMCS values
  • Transparency into transformation logic
  • Validation of dimension harmonization
  • Assurance that codes and classifications align correctly
  • This significantly reduces reconciliation issues caused by mismatched dimensions.