Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the understanding of the system logic and requirements in relation to trace ODP extraction. 

Overview

Important SAP Note

Ensure that SAP Note 1916612 is applied before starting with tracing.

The following Support Packages contain the correction already:

PI_BASIS2005_1_700SAPKIPYJ7R
PI_BASIS2006_1_700SAPKIPYM20
PI_BASIS701SAPK-70115INPIBASIS
PI_BASIS702SAPK-70215INPIBASIS
PI_BASIS730SAPK-73011INPIBASIS
PI_BASIS731SAPK-73111INPIBASIS
PI_BASIS740SAPK-74005INPIBASIS

General Purpose

The general purpose of activating the trace is to log the interface parameters when calling the functions RODPS_REPL_SOURCE_OPEN and RODPS_REPL_SOURCE_FETCH.

This is especially helpful in case of problems where it is unclear whether the problem is on subscriber or provider side.

To answer questions regarding:

  • Wrong data selection: Which selection was passed from the subscriber, e.g. Data Services ?
  • Processing mode: A repeat was expected, but a delta was done. What was requested from the subscriber ? 

Setting RSADMIN parameter as prerequisite

To set the parameter use the ABAP program in SE38 transaction: SAP_RSADMIN_MAINTAIN

After executing () this program the following screen appears:

 

Here it is possible to define which object needs to be inserted to RSADMIN table. In this case

OBJECT = RODPS_REPL_TRACE

VALUE = X

  •  INSERT

To confirm the changes, use .

As a confirmation of the change on the next screen the following information will be shown:

To double check it, it is possible to look for the entry in the RSADMIN table in SE16:

and as confirmation, the value X will be shown for the entry RODPS_REPL_TRACE:

Next step: Perform the extraction

After the parameter is set, the extraction can be performed. In this case there are a lot of possibilities for this therefore (e.g. with testing report: RODPS_REPL_TEST or real testing), no more details will be provided in this section. 

The Trace file: RODPS_REPL_TRACE.TXT

The system writes the logs under the file name RODPS_REPL_TRACE.TXT to the directory DIR_HOME that you can display using transaction AL11. This is particularly suitable for sporadic errors; you can also leave the trace activated for several days.

ScreenshotParameters

Open Start

call: 32 character long unique identifier

date/time: in Universal Time Coordinated / Universal Coordinated Time (UTC)

wpinfo: Work Process Information (application server instance, WP number, userID)

subscriber_type: replication test with RODPS_REPL_TEST in SE38

subscriber_name: TestRepository_DoesNotExist is an identifier for replication test

subscriber_process: TestDataFlow_DoesNotExist is the identifier for the replication test process 

context: SAPI -> BW target subscriber

odpname: technical name of the DataSource/Extractor

maxpackagesize: 0 -> not set, unlimited

extraction_mode: f -> FULL

recovery_pointer: 0.000000 -> not set

Open End

call: 32 character long unique identifier

date/time: in Universal Time Coordinated / Universal Coordinated Time (UTC)

wpinfo: Work Process Information (application server instance, WP number, userID)

pointer: A request is a data request from a subscriber and is identified by a request ID in the form of a time stamp ID.

Related SAP Note

SAP Note: 1580242