BW4HANA Open ODS view - master data

[MartinZluky]

Hi all,

how does the Open ODS view for master data work? We are trying to use it as a time-dependet infoobject. But here is the problem. The valid period is set by time-stamp fields. When we asociate this Open ODS view with Open ODS view facts it shows empty values for the infoobject. As soon as we move the valid period fields from valid period folder to characteristics folder (aka attributes), data is showing. I tried to find something on the net, but there is not much info about it. I found only this:

• Key date-based access to time-dependent master data is not supported in the Open ODS views

I dont understand this. How is it not supported? What is the point of having a valid period folder in the open ods view for master data? How does it work? Can anyone explain it? Maybe the time-stamp field is the problem? And we should change it to calday?

Best regards,

Martin Zluky

[vishalakshmi · Accepted solution]

Open ODS Views do not automatically apply key-date-based filtering like standard BW InfoObjects, requiring explicit filtering in queries. Moving valid period fields to attributes makes them visible since they are no longer interpreted as validity periods. Replacing time-stamps with CALDAY may enhance filtering efficiency. If Open ODS Views prove too restrictive, consider using an ADSO or a Composite Provider as an alternative.

Thanks,

Vishala.

[MartinZluky · Accepted solution]

Thank you. Can you please explain the "requiring explicit filtering in queries"? what must be done so the validity fields in validity folders are taken into consideration.

[vishalakshmi · Accepted solution]

1. Apply Filtering in BW Queries (Analysis for Office, Query Designer)

In Query Designer, create a restricted key figure or filter that explicitly filters records based on a key date. Use a filter condition such as:

Valid_From <= Key Date AND

Valid_To >= Key Date

Example: If your Open ODS View has fields: VALID_FROM (timestamp or date) VALID_TO (timestamp or date) CUSTOMER_ID Then, create a filter on CUSTOMER_ID where: [VALID_FROM] <= [Key Date] AND [VALID_TO] >= [Key Date]

This ensures that only the correct master data records valid at the key date are used.

2. Use a Calculation View in SAP HANA (If Using HANA-Based Open ODS)

If your Open ODS View is based on an SAP HANA table/view, create a calculated column that dynamically checks whether a record is valid on a given key date.

Sample SQL code: CASE WHEN CURRENT_DATE BETWEEN VALID_FROM AND VALID_TO THEN 'Active' ELSE 'Inactive' END AS Valid_Status You can then filter the Open ODS View to include only rows where Valid_Status = 'Active'.

3. Transform the Data in a Composite Provider or ADSO If Open ODS Views alone do not work, you can create a Composite Provider or ADSO to store the master data with pre-applied filtering.

Load the data into an ADSO with a calculated field that applies the same filtering logic (VALID_FROM <= KEY DATE AND VALID_TO >= KEY DATE).

Then, use this ADSO in reports instead of the Open ODS View.

4. Consider Using CALDAY Instead of Timestamps If you’re using timestamps (YYYY-MM-DD HH:MM:SS), BW queries might struggle with date-based filtering. Convert timestamps into CALDAY format (YYYYMMDD) so you can use standard date-based filters in BW. Finally to make Open ODS Views respect the validity period:

Apply explicit filter conditions in BW Queries (VALID_FROM <= KEY DATE AND VALID_TO >= KEY DATE).

Use a HANA Calculation View if working with HANA-based data. If filtering in Open ODS View is insufficient, store the data in a Composite Provider or ADSO.

Convert timestamps to CALDAY for easier date-based filtering.

Hope it should resolve the issue.