You created a generic DataSource. ZWEATHER_DATA in SAP ERP using a function module. You tried to replicate the DataSource in SAP BW/4HANA, but it is not available in the ODP_SAP context. Which…

Question

Options

• AIt must be defined with a delta-specific field durutg data source creation.
• BIt must have a delta queue entry transaction ODQMON
• CIt must be released for OOP with program RODPS_OS_EXPOSE
• DIt must be released for ODP with program BS_ANLY_DS_RELEASE_ODP

• B
  4% (1)
• C
  12% (3)
• D
  85% (22)

Explanation

Generic DataSources created via function modules (Z-prefixed custom DataSources) are not automatically registered in the Operational Data Provisioning (ODP) framework. Running program BS_ANLY_DS_RELEASE_ODP in the SAP ERP source system explicitly registers the DataSource for ODP, making it visible under the ODP_SAP context in BW/4HANA for replication. Without this release step, the DataSource simply does not appear as a selectable source, regardless of how it was built.

Why the distractors are wrong:

• A - A delta-specific field affects how data is extracted (delta vs. full), not whether the DataSource is exposed to ODP at all.
• B - ODQMON is a monitoring transaction for the Operational Delta Queue; it's an observability tool, not a prerequisite for DataSource availability.
• C - RODPS_OS_EXPOSE is a plausible trap, but it is used to expose DataSources for ODP in the context of SLT (SAP Landscape Transformation) replication, not for releasing generic function-module-based DataSources in the ODP_SAP context.

Memory tip: Think of BS_ANLY_DS as "Business Suite Analytics DataSource" - you need to release your custom DS from the Business Suite side before BW/4HANA can see it. If you built it yourself (Z*), you must release it yourself.

No community discussion yet for this question.