Datasource enhancement working good in Dev and giving error in Test system

[Former Member]

Hi all,

I have issue with Datasource enhancement. We have existing custom datasource which was created on view (joining of two tables). Now we need to add one more field from other table. I joined one more table with common field from one of the existing tables and everything looks good. I changed datasource and unhide that field and extracted data in RSA3 and data looks good.

I replicated into BI and everything went smooth upto here. We transported this modified datsource from Dev to Test enviroment and didn't receive any warnings also. I checked in RSO2, RSA6 and everything looks good, but when I tried to run this enhanced datsource in RSA3 it is giving ABAP Dump as below.

Runtime Errors PERFORM_PARAMETER_TOO_SHORT

Except. CX_SY_DYN_CALL_ILLEGAL_TYPE

Date and Time 05/23/2011 11:35:24

Short text

Actual parameter too short when passing parameter in PERFORM.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLXRSA" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was

not caught in

procedure "EXIT_SAPLRSAP_001" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The field which is supposed to receive a structured parameter is

shorter than the structure of the parameter. This is not supported.

This is parameter no. 4 of the FORM "EXECUTE_USER_EXIT" in program

"ZBWDS_XXXXX".

The actual parameter is 650 bytes long, the formal parameter 860 bytes.

Missing RAISING Clause in Interface

Program SAPLXRSA

Include LXRSAU01

Row 1

Module type (FUNCTION)

Module Name EXIT_SAPLRSAP_001

Trigger Location of Exception

Program SAPLXRSA

Include LXRSAU01

Row 21

Module type (FUNCTION)

Module Name EXIT_SAPLRSAP_001

Source Code Extract

Line SourceCde

1 FUNCTION EXIT_SAPLRSAP_001.

2 *"----

---

3 ""Lokale Schnittstelle:

4 *" IMPORTING

5 *" VALUE(I_DATASOURCE) TYPE RSAOT_OLTPSOURCE

6 *" VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE

7 *" VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE

8 *" TABLES

9 *" I_T_SELECT TYPE SBIWA_T_SELECT

10 *" I_T_FIELDS TYPE SBIWA_T_FIELDS

11 *" C_T_DATA

12 *" C_T_MESSAGES STRUCTURE BALMI OPTIONAL

13 *" EXCEPTIONS

14 *" RSAP_CUSTOMER_EXIT_ERROR

15 *"----

---

16

17

18 INCLUDE ZXRSAU01.

19

20

>>>>> ENDFUNCTION.

I didn't do anything with components in CMOD where as datasource was created on view and we have already one project is there for all BI dat sources enhancements.

Please advice what to do. Where as it is working good in Dev and giving error in test enviroment.

Thanks

[Former Member]

Solved problem, when transporting enhanced extractor need to transfer all related components (datasource, view, table, source code & append structure). Initially I forgot to transport append structure, so it was giving dump when ever I ran the extractor in RSA3. Again I moved append structure, so it solved the problem.

Thanks