LOAD_PROGRAM_NOT_FOUND Short dump in R/3

[Former Member]

Hi frnds,

I am facing some short dump problem while loading the data from R/3 BW, its a master data.

The short dumps are LOAD_PROGRAM_NOT_FOUND and RAISE_EXCEPTION in R/3.

Not able to find the exact problem and please suggest some OSS Notes.

Thanks

Hari

[Former Member · Accepted solution]

Hi,

use tcode ST22 to analyze the dump, there must be a message like: program xxxxxxxxxxxx not found, try to find out what program it is.

/manfred

[Former Member]

Hi A.H.P,

Right now we are in support pack 14, applied all the OSS notes related to this support pack.

Thanks

Hari

[Former Member]

Hi,

u can see the dumps in st22 and sm21 for sys logs

i think this is Sounding like rfc source system (sm59).

from SM37 take a look at the job (job name from Request ID)

What messages do you get in the request monitor?

Check OSS Note 832057. It may be helpful to ur query

-Shreya

[edwin_harpino]

hi Hari,

check if helps oss note 899405-Master data extrctn: LOAD_PROGRAM_NOT_FOUND in source system

Symptom

You are loading master data in delta mode from an SAP source system. The DataSource uses generic extraction in the process.

The request is displayed in the monitor as being incorrect. The status indicates that the extraction process has probably terminated with a runtime error.

In the source system, you find the runtime error LOAD_PROGRAM_NOT_FOUND with the exception CX_SY_PROGRAM_NOT_FOUND. The point of termination is in the function module RSA3_GEN_GET_DATA.

The short dump occurs only if there is no data available for the delta.

Other terms

OLTP, extractor, data extraction, DataSource, service API, SAPI, dump, SAPLRSA3, LRSA3U03, RSAPTM2, EXTRACTOR_FETCH, EXTRACTOR_INIT, NO_MORE_DATA

Reason and Prerequisites

This is caused by a program error.

When you implemented Note 853001, calls for function modules were relocated to subroutines. This changed the query for the exception NO_MORE_DATA in such a way that it is not caught when the extractor is initialized. The extraction process then tries to start the program, but the program has not been generated because data is missing. The system issues the short dump.

Solution

After you have implemented the correction specified below, you must reactivate the transfer rules for the affected DataSource. It is only by doing this that the correction is also implemented in the generated program for the extraction process.

To correct the problem, you need to have Support Package 07 in the relevant source system Service API 7.00. The attached composite note informs you of the software components that contain Service API 7.0 and specifies the corresponding Support Packages for these components.

As an alternative, you can also implement the advance correction from the attachment.

You must implement the correction in the BW system only if it is affected in its role as a source system for itself (myself connection) or for another BW system.

Note: Service API is an internal component. It is not delivered separately, but as part of other software components: PI, CRM, PI_BASIS and a number of others. For this reason, a composite note has been created which tells you in which Support Packages of the above-mentioned software components the SAP correction note is contained. However, the composite note is not released until the release date of the corresponding SAPI Support Package. Different SAPI versions are delivered for Basis Releases 3.1I, 4.0B, 4.6D, 6.20 and 6.40. The version for 4.0B is also valid for R/3 Releases 4.6B and 4.6C.