Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

MD04 Shortdmup

Former Member
0 Kudos


Following is the message I am getting in short dump while saving formula in material quantity calculation using t-code MD04.




>> Short dump has not been completely stored. It is too big.


Invalid partial field access: Offset + length too large


What happened?


Error in ABAP application program.

The current ABAP program "SAPLCO09" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Error analysis


An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_RANGE_OUT_OF_BOUNDS',

was neither

caught nor passed along using a RAISING clause, in the procedure



Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The system tried to access field "P_FORMULA" with type "C" and length

250 in the current program "SAPLCO09" using offset 111 and length 153.

Partial field access is not allowed with offset and length

specifications that are

larger than actual field length.


How to correct the error


The exception must either be prevented, caught within the procedure


"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Make the offset or the length with which you want to access the field


If the error occurred in one of your own programs or in an SAP program

that you modified, try to correct it yourself.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:



"SAPLCO09" or "LCO09FF7"



If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.


2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant


3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Thanks in advance,



Active Contributor
0 Kudos


SAP applications same as any other software have some bugs. So firstly you should search for related OSS notes when you get a dump in standard application and you are sure that it's not caused by custom code such as BADI implementation. If you enter SAPLCO09 and DATA_OFFSET_LENGTH_TOO_LARGE into search form on then you get just one OSS note. So I would start with that one. It might be relevant for your system and fix your problem.


Active Contributor
0 Kudos

Nice summary by Martin.

Please investigate yourself before just dumping your dumps here.

Thread locked.