Skip to Content
0
Former Member
Dec 10, 2009 at 09:13 AM

Errors in phase MAIN_SHDIMP/SHADOW_IMPORT_INC for upgrade ERP 6.0 EHP4

40 Views

Hello,

I am executing the upgrade to ERP 6.0 EHP4-Stack4 and in the phase MAIN_SHDIMP/SHADOW_IMPORT_INC, i have the follow error:

*******************************************************************************************************

"SHADOW IMPORT ERRORS and RETURN CODE in SAPK-40001INCPRXRPM.FSD

2EETW165 Function "/RPM/RELATION_MODIFY (/RPM/CONFIG|15)" does not fit into the existing function group "(/RPM/RELATION_DATA|02)".

Long text:

Cause

A function module with LIMU FUNC ... was transported in the transport

request.

An import is only possible if this function module belongs to the same

function group in the target system and

has the same internal number as in the source system.

These conditions were not observed in the target system.

This problem can occur,

if an entry LIMU FUNC ... is included in a transport request manually

in the object list editor,

or if a function module is deleted, and then created again under the

same name in another function group, and deletion and creation are

recorded in the same change request.

System Response

The function module was not imported.

What to do

You can remove the error by making another transport from the source

system. Transport the affected function groups once more in their

entirety. To do this, use the transport object R3TR FUGR ... .

You can avoid the second type of error (deletion and creation in

another function group) as follows:

In the ABAP Workbench use the function <LS>Reassign</>, or record the

deletion and the new creation in separate change requests.

Release the change request with the deletion before you release the

change request with the new creation.

1 ETP111 exit code : "8"

***********************************************************************************************************************************

I don't found the function module or function group in the system, this system is the development instance.

Regards, Alberto.