SRM 7.0 EHP2 -> MAIN_POSTP/UEXP_SPDD

[Former Member]

Dear all,

we are experiencing a problem during the SUM phase "MAIN_POSTP/UEXP_SPDD".

During the SPDD phase, our developer created CR <***K904371>, (we suppose, correctly marked for transport)

So now, in the phase UEXP_SPDD we are facing this severe error:

%BEGIN MAIN_POSTP/UEXP_SPDD TEXT

  Warning: APPEND_SAPCOMPONENT returned message: "Wrong Request type.".

With the SUM tool the system got certain components, component releases and Support

Package levels. This information is in an internal table. The components, component

releases and Support Package levels, which the system has now are different. When the

SPDD and/or SPAU transport was exported, the SUM tool noticed, that the information

differs. This could be e.g. if further updates were done via SAINT or SPAM after the SUM

was (almost) finished and before the export for the SPDD/SPAU request was done. If this

SPDD/SPAU request shall be included in a further SUM procedure, it is important that the

components, component releases and Support Package levels of the SPDD/SPAU request

fit to the target status of that SUM procedure.

The details of other logs:

1 ETQ201 Entering upgrade-phase "MAIN_POSTP/UEXP_SPDD" ("20130615173820")

2 ETQ399 Setting SQL connect to standard DB.

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '20', GwService = 'sapgw**' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399   dbs_ora_schema=SAPSR3

4 ETQ399   auth_shadow_upgrade=<null>

1 ETQ200 Executing actual phase 'MAIN_POSTP/UEXP_SPDD'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'SPDD'

2 ETQ399 Arg[1] = ''

1 ETQ399 Using error summary log 'UEXPNEWSPDD.ELG'.

1 ETQ000 ==================================================

1 ETQ005 EXPORT AND SAVE A TRANSPORT ORDER

4 ETQ430 START reading "umodauto.lst" in directory "/usr/sap/trans/SDR/abap/bin"

4 ETQ431       "1" entries read

4 ETQ432       read: rc="1"

3 ETQ433 END   reading "umodauto.lst" in directory "/usr/sap/trans/SDR/abap/bin"

3 ETQ031 START EXPORT PROCEDURE for "***K904371"

2 ETQ399 Using 'tp' from path '/usr/sap/***/DVEBMGS**/exe'.

2 ETQ399 Requested task ID is 'SEL_TRAS4USER'.

2 ETQ399 Skipping execution and scanning cached output '/usr/sap/trans/SDR/abap/log/SEL_E070_SPDD.LOG'.

3 ETQ399 Reading selections from 'SEL_E070_SPDD.LOG'.

4 ETQ399 Read 1 entries for table 'LIST'.

3 ETQ399 Reading selections from 'SEL_E070_SPDD.LOG'.

4 ETQ399 Read 1 entries for table 'LIST'.

4 ETQ010       User UPGRADE

2 ETQ399 Using 'tp' from path '/usr/sap/***/DVEBMGS**/exe'.

2 ETQ399 Requested task ID is 'CHG_TRANSOWNER'.

3 ETQ399 Generating TQL file 'UPDATEE070PRE.TQL' with log file 'UPDATEE070PRE.LOG'.

4 ETQ276 Executing SQL-script "UPDATEE070PRE.TQL"

3 ETQ399 20130615173820: PID 3091 execute '/usr/sap/***/DVEBMGS**/exe/tp pf=/usr/sap/trans/SDR/abap/var/DEFAULT.TPP execdbscript *** -x ../var/UPDATEE070PRE.TQL' , output written to '/usr/sap/trans/SDR/abap/log/TPSQLSTD.OUT'.

3 ETQ399 20130615173822: PID 3091 exited with status 0

3 ETQ399 Reading SQL output from 'UPDATEE070PRE.LOG'.

1 ETQ359 RFC Login to: System="***", AsHost="hostname" Nr="20", GwHost="hostname", GwService="sapgw**"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130615173822 

1 ETQ233 Calling function module "SBUF_GENERIC_RESET" by RFC

2 ETQ374 parameter "BUFF_ID" = "0"

2 ETQ373 parameter "RESET" = " "

2 ETQ373 parameter "SYNC" = "X"

2 ETQ373 parameter "TABNAME" = "E070"

2 ETQ374 parameter "KEY_L" = "0"

1 ETQ234 Call of function module "SBUF_GENERIC_RESET" by RFC succeeded

4 ETQ010 Date & Time: 20130615173822 

1 ETQ359 RFC Login to: System="***", AsHost="hostname" Nr="20", GwHost="hostname", GwService="sapgw**"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130615173822 

1 ETQ233 Calling function module "FUNCTION_EXISTS" by RFC

2 ETQ373 parameter "FUNCNAME" = "APPEND_SAPCOMPONENT"

1 ETQ234 Call of function module "FUNCTION_EXISTS" by RFC succeeded

4 ETQ010 Date & Time: 20130615173822 

1 ETQ359 RFC Login to: System="***", AsHost="hostname" Nr="20", GwHost="hostname", GwService="sapgw**"

2 ETQ232 RFC Login succeeded

4 ETQ010 Date & Time: 20130615173822 

1 ETQ233 Calling function module "APPEND_SAPCOMPONENT" by RFC

2 ETQ399 Table IT_TRKORR (#1):

3 ETQ399 "***K904371","","",""

1 ETQ234 Call of function module "APPEND_SAPCOMPONENT" by RFC succeeded

4 ETQ010 Date & Time: 20130615173822 

2 ETQ374 parameter "EV_RC" = "-1"

2 ETQ373 parameter "EV_MESSAGE" = "Wrong Request type."

1EETQ399 Last error code set is 'Issues occured calling 'APPEND_SAPCOMPONENT' - check phase log for details'

1EETQ204 Upgrade phase "UEXP_SPDD" aborted with severe errors ("20130615173822")

tp_exec_statement: UPDATE E070 SET AS4USER = 'DDIC' WHERE TRKORR = '***K904371'

tp_exec_statement: COMMIT

tp_exec_dbscript: 2 statement(s) successfully processed.

### Phase MAIN_POSTP/UEXP_SPDD:

***adm       20130615173821    : tp pf=/usr/sap/trans/SDR/abap/var/DEFAULT.TPP execdbscript *** -x ../var/UPDATEE070PRE.TQL  (pid=3091)

I have already take a look into the KBA1735879

the CR is correctly into the 000 Client and the umodeauto.lst has the right value

SPDD 731  ***K904371

Could you please give us a support?

Thanks and regards

Cristian

[Former Member · Accepted solution]

Solved with KBA1735879

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

Unfortunately, the sleepless nights for these first dry run did leave out the MOST important line of the article:

• Cause B: A task is mentioned in umodauto.lst file instead of the SPAU request.

So changind the task with the correct one, the SUM continued normally.

before

SPDD 731  ***K904371

after

SPDD 731  ***K904370