Debugging EXIT_SAPLRSAP_001 and FUNCTION ZXRSAU01

[Former Member]

Hello All

I have made an enhancement to extractor 0FI_gl_4 using EXIT_SAPLRSAP_001 and FUNCTION ZXRSAU01 in our DEV Client. I've been specific in the WHERE clause of the coding to restrict the result set to a specific document number. I've inserted a Breakpoint in the code and ran RSA3 the results from the checker agree to the results given in (SE16) for BSEG.

I then changed the WHERE SQLstatement, to try and enlarge the test result set and also changed the the Data Records/Calls from 100 to 1000 in (RSA3) and ran the checker. These changes resulted in a short dump and subsequent debugging showed that the p_s_idoc_parameters u2013maximum_size system limit of 100 was exceeded. I then changed back the Records/Call setting to 100 and reverted back to the original WHERE SQL for the same specific document number. However, I continue to get the same short dumps ( DBIF_RSQL_INVALID_RSQL ) with the same error message. Forums suggest that the change I made exceeded the limit that the system allocates for tablespace and requires resetting by the BASIS Team?? But in what transaction / where would BASIS change the setting?

We are using SAP_BASIS Component release 640 and are at support patch level 23. For info the original SQL is as follows

>>>>> IF lv_lines GT 0.

SELECT bukrs belnr gjahr buzei EBELN

FROM bseg INTO TABLE lZ_bseg

WHERE bukrs = 1000

AND belnr = 5000000314.

Which I then changed to

>>>>> IF lv_lines GT 0.

SELECT bukrs belnr gjahr buzei EBELN

FROM bseg INTO TABLE lZ_bseg

WHERE bukrs = 1000

AND belnr = 5000000314.

AND gjahr = 2007.

And then back to the original.

Thank you for any help and suggestions

[Former Member]

For anyone who might have a similar error, here is what I did to resolve.

Rather than the ABAP Dump (ST22) which can be a little general in its messages, I checked the System Log: Local Analysis entries (SM21) for my USERID and executing server around the time the error occurred. If the resulting message doesn't initially make any sense, use the Previous and Next entry buttons to scroll through your entries. In my example the error message pointed to a difference to the internal table declarations for the coding I added and the fields selected for extraction. The extractor was essentially trying to add numeric data to a characteristic field... I amended the select statement and resolved.

Next time I have a similar error I'll look to (SM21) as my first port of call...

Embarrassingly simple when you know how

Regards to all

Helen