The purpose of this page is to clarify the understanding of the system logic and requirements in relation to ABAP program RODPS_REPL_TEST
When to use it?
The ABAP report RODPS_REPL_TEST is used to rule out and troubleshoot ODP problems in ODP source side (extraction and fetch of data) by creating of a new subscriber to a provider in ODQMON. Whereas transaction RSA3 is the classic extractor checker, used only for pure DataSources data issues (Full mode and independent from ODP), the report RODPS_REPL_TEST acts as a separate additional subscriber. Therefore, execution of this report is not a simulation. This mechanism enables the report to be used not only for checking ODP as context from the perspective of BW Subscriber but also from another consumer's perspective.
The features available for the report are dependent on the ODP API release in the Source System. After a successful execution, the queue entries in ODQMON, with corresponding table entries for RODPS_REPL_TEST, are created and adjusted, the application data is physically written to the queue. The created requests are subject to the regular ODQ CLEAN-UP job and will disappear after the retention time.
Attention: Be careful when using RODPS_REPL_TEST and Init/Delta replication mode and reset the subscription which was created by your tests. Reason: An ODP source uses only one delta queue, which is shared between several subscribers. The delta data is only cleaned up if ALL subscribers picked the delta. This will not happen for subscriber RODPS_REPL_TEST, therefore the delta table ODQDATA might grow big over time, impacting general ODQ loading performance.
This section contains all the relevant selections fields on the main screen.
The context is the provider of data and represents a source of ODPs. The currently available ODP-Contexts are described. In your system you might found more or fewer options comparing to image below, since it is depends on the release and environment details (such as having SLT as context).
|Available ODP Context||Description|
|ABAP Core Data Services|
With ABAP 7.40, SP05 the ABAP Core Data Services, short ABAP CDS, were introduced. The ABAP Core Data Services implement the general CDS concept of SAP (that is also available for HANA as HANA CDS) for AS ABAP. They use a DDL to define CDS views that implement a semantic data model in the ABAP Dictionary. The power of ABAP CDS is, that it is open, meaning database independent (with some exceptions if the databases do not yet cover all the functionalities as e.g. views with parameters). You can use the DDL of ABAP CDS in Eclipse based ADT to create rather complex views that exceed the capabilities of the classical database views created in SE11 by far. Technically, from the source code of a CDS view, a classical database view is generated. We call this the CDS database view.
|SAP NetWeaver Business Warehouse|
SAP NetWeaver Business Warehouse (SAP_BW) is available as of ODP API 2.0. The minimum requirements for this are the following:
At least one of the following releases of the component PI_BASIS is required:
PI_BASIS 730 SP 8 (part of SAP NetWeaver 7.30 SP 8)
PI_BASIS 731 SP 5 (part of SAP NetWeaver 7.03 SP 5 and 7.31 SP 5)
PI_BASIS 740 SP 2 (part of SAP NetWeaver 7.40 SP 2).
|HANA Information Views|
SAP HANA Information Views ODP Context is available for customer as of 7.30 SP8, 7.31 SP5 and 7.40 SP3. SAP HANA View ODP Scenario is only intended for SAP Systems running on HANA. SAP_BW software component is required in source system. By creating an ODP HANA source system, a RFC-connection is required to a SAP-system running on HANA. A HANA View name is not unique. ODP Hana Views follow therefore for uniqueness the naming convention: Package name\View Name. If the name is longer than 25(27) characters, a Hash code is generated. There is no specific Customizing necessary to enable ODP HANA view functionality.
Three main types:
Attribute Views: are like Dimension in the SAP BW area, but with difference is that attribute views are fully reusable throughout the system and not stuck up to a single model. These are views on one or more table that can be reused for different purpose.
Analytical Views: comparable with InfoCubes or InfoSets. As same it joins together one central fact table which contains transaction data to report on, with number of tables or attribute views. You can create variables in an analytical view.
Calculation Views: can be referred as combination of tables, attributes views and analytical views to deliver a complex business requirement. They offer to combine different analytical views into one source of data for reporting.
|ODP Introspection||ODP infrastructure for metadata introspection.|
|Random Data||"Random" in this context means that this data can be selected from any (dynamically specified) DB table.|
|DataSources/Extractors||DataSources (extractors) from SAP systems for transferring data to BW with help of ODP framework. Check 2232584 for more details.|
|SAP LT Queue Alias <SLT SystemID>|
Using the operational data provisioning infrastructure and trigger-based replication of SAP Landscape Transformation Replication Server (SAP LT Replication Server), you can transfer data from SAP systems to the BW system in real-time. SAP LT Replication Server is a provider for the operational data provisioning infrastructure. It can make tables from SAP sources available as delta queues. BW can be a subscriber to this delta queue and can access the data replicated using the operational data provisioning infrastructure for further processing.
Name of the ODP, in Service API (SAPI) context the DataSource name.
ODP names for SAP HANA modelling views must adhere to the following naming convention: <package name in SAP HANA>_<name of the view in SAP HANA>. As the length of technical names in BW is restricted, we recommend keeping package name and names of views in SAP HANA as short as possible if they are relevant for replication into BW. If the package name and view name exceed the limit, the BW system assigns a 25-character hash code as the ODP name. This code is made up of the package name and the view name.
The ODP descriptions of the ODPs are taken over from SAP HANA. If there is no description for a modelling view in SAP HANA, the BW system uses <package name>/<name of the view in SAP HANA> as the description.
Selections / Projections
Selections: Optional parameter to enter selection criteria. Current restriction: If the ODP has more than 75 selection fields, no selection is offered.
Projections: restrict the field list.
Read Open Pointer
Field to enter a pointer to repeat a delta. This pointer relates to subscriber RODPS_REPL_TEST. It is currently not possible to enter a pointer of another subscriber (e.g. SAP_BW or BOBJ_DS).
Settings for Execution
Parallel Extraction Using ODQ: data will be extracted in parallel mode using data in the Operational Delta Queue.
Serial Extraction Using ODQ: data will be extracted in serial mode using data in the Operational Delta Queue.
Direct Extraction Without ODQ: data will be extracted without accessing Operational Delta Queue.
The application data is stored in the queue in a highly compressed format. With this option you can simulate the output for different wrapping and unwrapping options.