cancel
Showing results for 
Search instead for 
Did you mean: 

XPRA_EXECUTION tp_step_failure return code 12

Former Member
0 Kudos

hi there !!

we are encountering XPRA_EXECUTION tp_step_failure return code 12 while importing new patches SAPUI in SPAM. Our SPAM is already at 49 (latest patch level). NW 7.31.

We have tried $sync, restarted the system, suspend all the jobs, this is a new system so there are no SAP notes applied yet so no conflict with that. Checked SPAU and nothing needs to be adjusted/reset due to no notes applied.

Has anyone else seen this issue ? any help would be greatly appreciated

we looked at note 1597765 - spau modifications doesn't apply to us (there's none in system yet)

thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Jyoti

can you paste the extended log?

did you update kernel, R3trans and tp after the installation?

Let me know

a

former_member185239
Active Contributor
0 Kudos

Hi  Jyoti,

Please paste the job log of RDDEXECL.

You can check the Note 1597765 - Known problems with Support Packages in SAP NW 7.31 AS ABAP.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Our Kernel is at patch level 423 (433 is the latest and just came out few days back)

Here's what we are seeing in ST22

The current ABAP program "CL_CHIP_CATALOG===============CP" had to be

     terminated because it has

    come across a statement that unfortunately cannot be executed.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_METHOD', was

     not caught in

    procedure "INIT_PROVIDER" "(METHOD)", nor was it propagated by a RAISING

     clause.

    Since the caller of the procedure could not have anticipated that the

    exception would occur, the current program is terminated.

    The reason for the exception is:

    It was tried to call the method "IF_CHIP_PROVIDER~GET_PROVIDER" of the class

     "/UI2/CL_CHIP_PROVIDER_GADGET". However, in the

    class "/UI2/CL_CHIP_PROVIDER_GADGET", the method

     "IF_CHIP_PROVIDER~GET_PROVIDER" could not be found.

Former Member
0 Kudos

Hi Ashutosh,

I have reviewed note 1597765, we don't have any SPAU adjustments --"it says no objects for adjustment to be found " - new system

Job log for

RDDEXECL

Date       Time     Message text                                                                        Message class Message no. Message type

24.06.2013 11:10:32 Job started                                                                              00           516          S

24.06.2013 11:10:32 Step 001 started (program RDDEXECL, variant , user ID xxxxx)                              00           550          S

24.06.2013 11:10:32 All DB buffers of application server xxx-xxx were synchronized                           PU           170          S

24.06.2013 11:10:33 Internal session terminated with a runtime error DYN_CALL_METH_NOT_FOUND (see ST22)      00           671          A

24.06.2013 11:10:33 Job cancelled                                                                            00           518          A

    The current ABAP program "CL_CHIP_CATALOG===============CP" had to be

     terminated because it has

    come across a statement that unfortunately cannot be executed.

former_member185239
Active Contributor
0 Kudos

Hi Jyoti,

I think the belw sapnote might reslve the issue.

Note 1860742 - Implementation of UI2_700: Dump DYN_CALL_METH_NOT_FOUND

Please check the above note.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,

Thanks a lot , Note # 1860742 looks exactly the problem we are facing. However the note doesn't provide fix if you are stuck with this syntax error in middle of the upgrade. SPAM version 50 will be out in end of July.

FYI- we had followed everything in note 1666369

Let me know your thoughts

thanks

Jyoti

former_member185239
Active Contributor
0 Kudos

Hi Jyoti,

You can raise a message with SAP.

They will guide you properly.

If you have manage to resolve the issue , please do let us know.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi there !!

We were able to resolve the issue with the help of SAP support. Fix is coming in end of July in SPAM 50 but in the meantime, SPAM queue can be reset and apply these together UI2_700-731, UI INFRA & UI FND.

thanks for help

Jyoti

former_member185239
Active Contributor
0 Kudos

Hi Jyoti,

great

Please mark this thread as answer.

With Regards

Ashutosh Chaturvedi

0 Kudos

got the same error, with SPAM 7.31/50 and the newest kernel files.. any idea?

0 Kudos

No Solution in these notes .. my runtime error  on ST22 displays:

Category               ABAP Programming Error

Runtime Errors         SYNTAX_ERROR

ABAP Program           /UI2/CL_CHIP_PROVIDER_GADGET==CP

Application Component  CA-UI2-INT-BE

Date and Time          06.08.2013 13:35:46

What happened?

     Error in the ABAP Application Program

     The current ABAP program "CL_CHIP_CATALOG===============CP" had to be

      terminated because it has

     come across a statement that unfortunately cannot be executed.

     The following syntax error occurred in program

      "/UI2/CL_CHIP_PROVIDER_GADGET==CP " in include

      "/UI2/CL_CHIP_PROVIDER_GADGET==CM003 " in

     line 1:

     "Die Klasse "/UI2/CL_CHIP_PROVIDER_GADGET" besitzt kein Interface "/UI2"

     "/IF_CHIP_PROVIDER". Es existiert aber das Interface "IF_CHIP_PROVIDER""

     " mit ähnlichem Namen."

     " "

     The include has been created and last changed by:

     Created by: "SAP "

     Last changed by: "SAP "

     Error in the ABAP Application Program

     The current ABAP program "CL_CHIP_CATALOG===============CP" had to be

      terminated because it has

     come across a statement that unfortunately cannot be executed.

Former Member
0 Kudos

Hi

if you spam is up2date, open a message to sap

Let me know your thought

cheers

a

Former Member
0 Kudos

Hi Steffen,

See if you can reset the SPAM queue and then apply these together

UI2_700-731, UI INFRA & UI FND. The UI2 version 700 should also be applied together , although you are doing 731.

This will resolve the issue

thanks

Jyoti

Former Member
0 Kudos

Hi Steffen,

Upload the ACP UI2_700 100 in eps/in and continue.

Thanks.

Best Regards,

Anita

Answers (0)