Skip to Content
0
Former Member
Feb 25, 2009 at 07:40 AM

XPRA ERRORS and RETURN CODE in SAPR701WD1.CRM

105 Views

Hi All - I am upgrading to CRM70 on linux and Oracle platform. On phase XPRAUPG I am getting the following error messages on table activation which I am not familiar with.

Could you please help me how to activate the tables or deal with the errors.

Thank you for your help in advance.

more XPRASUPG.ELG

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

  • LIST OF ERRORS AND RETURN CODES *******

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

XPRA ERRORS and RETURN CODE in SAPR701WD1.CRM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""BO""SAP0

0001"

Long text:

Cause

Activation of the condition table with the parameters application &V#&,

usage &V#& and table number &V#& failed.

System Response

The processed import is terminated.

What to do

<ZH>Customer</>

Inform your system administrator.

<ZH>Developer</>

Check the data transferred.

Tasks for system administration

Inform your responsible support organization.

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""BO""SAP0

0002"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""BO""SAP1

2130"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""PR""SAP1

2130"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""BO""SAP1

2131"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""PR""SAP1

2131"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""BO""SAP1

2132"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""PR""SAP1

2132"

Long text: see above

A2AE/SAPCND/TRANSPORT 047 Activation of the condition table failed"CRM""CD""SAPS

UNIL"

Long text: see above

2EEPU133 Errors occurred during post-handling "/SAPCND/TRN_AFTER_IMPORT_OW" for

"CTFR" "L"

Long text:

Cause

During the upgrade, import post-processing &V#& was performed for

object &V#& &V#&. Errors were reported.

System Response

The upgrade is interrupted.

What to do

You will find the error messages for post-processing &V#& directly

before this message. First read these error messages and the respective

long texts. You will find further information there on correcting the

errors.

If this information is not sufficient, look for error notes in the

SAPNet - R/3 Front End. Keywords you can use for the search are

the name of post-processing &V#& or

the message numbers of the preceding error messages. The message number

appears in the header of the long text display.

If you enter a problem message for the error, enter the following

information:

the name of post-processing &V#&

the message numbers of the preceding error messages

the components in which the error occurred

2EEPU136 The errors affect the following components:

Long text:

Cause

During the upgrade or import of a transport request, errors occurred

which affect particular components of the SAP System.

The following messages list the components in which the errors

occurred.

System Response

The upgrade or import of the transport request is interrupted.

What to do

Read the preceding error messages and their long texts for more

information on correcting the errors.

2EEPU137 "AP-PRC-CON" ("Condition Technique")

Long text:

Cause

During the upgrade or import of a transport request, errors occurred in

the component

&V#& (&V#&).

System Response

The upgrade or import of the transport request is interrupted.

What to do

Read the preceding error messages and their long texts for more

information on correcting the errors.

1 ETP111 exit code : "12"

>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

XPRAs are application reports that run at the end of an upgrade.

Most XPRA reports have a report documentation that explains what

the report does and how errors can be corrected.

Call transaction se38 in the SAP system, enter the report name,

select 'Documentation' and click the 'Display' button.

>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<