cancel
Showing results for 
Search instead for 
Did you mean: 

TDMS and Report painter forms

Former Member
0 Kudos

After transfering data from our QAS environment to our DEV environment, our functional team members have noticed that their report writer transactions are short dumping.

Using the debugger I verified that the unique ID returned from call function REPORT_DIRECTORY_READ is actually the ID number from the QAS system. So in DEV users are seeing a short dump that the program they are trying to execute does not exist

Unique ID in QAS system included for example:

GP3QZ0TTGHMJTUA4F8K0NQ8GKTL

Unique ID from DEV system that we do not want to overwrite:

GP3PGY5D2M93WHMFBSYGVUGZWHT

Does anyone known which table we need to exclude during the extract or if there is an OSS fix for this problem?

Thanks,

Anthony

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

These objects can simply be re-generated in the system after TDMS completes

Clemenss
Active Contributor
0 Kudos

Hi Anthony,

sorry, I do not remember the details.

When transporting Report Painter reports (SAP Easy access -> Accounting à Controlling -> Cost Center Accounting ->

Information system -> Tools -> Report Painter -> Utilities -> Transport -> Report

groups -> GCTR - Transport request), the transport will include an object of type/class XPRA. The name of the object is an executable report that will do some adjustments/generations so that the programs run in target system.

You may create a transport and ccjek the object list for the XPRA object name or scan old transport requests in E071 for XPRA objects.

Regards,

Clemens

Former Member
0 Kudos

Hi,

The table details can be obtained by running a SQL trace for that function module or raise an OSS message to analyse the issue.

Srila.