Transport request

Dear all,

I had released a customizing request from my DEV -> QTY system. I can find the request in STMS -> imports -> QTY system.In the import queue , if i select the particular request and import that request. It is not importing,no entries in QTY system. The status of that particular request is moved to green( Request waiting to be imported) again after that transport . I had moved some workbench request and it is been successfully moved and the status for that is changed to yellow (Request is ready for import again).

How to sort out the error , kindly suggest me.

Thanks and regards,

Rakesh.

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

hii

request is ready for import again means that you can import that trasnport again if you want.this is not an error

Also green means it has been successfully done,so there should not be any issues

and yellow means done with warnings which should not be an issue

Also a transport with status red only is the one which completes with error and you need to look at that one

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ,

The contents which i had transported to this QTY system is not found. While i said my functional peopel to check they said it is not been found in QTY system.

i guess :

yellow - Request is ready for import again

Red - Request will not be imported

Green - Request waiting to be imported

and once the request is imported succesfull to that particular system the status is changed from green to yellow. Correct me if i am wrong.

here in my case it is been in green after i give Import. the import is also chaging the status from Import running- > Request waiting to be imported in few seconds once i give import request.

Thanks and regards,

Rakesh.

Rakesh

green mean it has been imported successfully and can also be reimported if you want

yellow means the transport has finished with warnings and also can be reimported again

red means that the transport finished with errors and can not be reimported

gray means the transport is yet be imported

Also check with your functional people that whether the transport was made correctly.I guess it was juct a blank transport containing nothing and it was not made correclt by your guys

Ask them to make a new transport and again import

Rohit

Hi ,

Actually it had contents in that(Huge contents). I only released that request from DEV -> QTY system.How to trace that request is been transported or what is the error log been happened.

The transport configuration is good only.

Is that i need to shedule that in background. I had selected immediate .

Regards,

Rakesh.

no need for background scheduling

just go to import histroy in STMS screen and double click in the request to check the logs

and see if any errors exists

Rohit

Hi ,

This is the log found for that request.

23.03.2009 10:01:46 IMPORT XX5900146 XX4clires B5Q U0

Transport log is in RED. Maximum Return Code: 0211 - tp ended .

tp finished: no info about transport request found.

Kindly suggest me a solution pls.

Thanks and regards,

Rakesh.

Hi Rakesh,

After you released the request in DEV, are you able to see that request number in QAS(STMS Import Queue)

If you are able to see then select the request and click Queue ---> Adjust.

Now try to Import the Request.

Kalyan

Hi,

Ya i did , i am getting an error code "Maximum Return Code: 0211 - tp ended "

Kindly suggest me a solution for this pls.

Thanks and regards,

Rakesh.

Hi,

Paste the latest SLOG....log file which you can find at /usr/sap/tran/log directory

Kalyan

green mean it has been imported successfully and can also be reimported if you want
yellow means the transport has finished with warnings and also can be reimported again

A green check means the the transport has been imported, a yellow triangle means that the system is configured for mass transports instead of single ones, in any case it means is imported... now if the transport returnes to a green circle means that it was not posible to execute the transport.

Read the tp logs.. and post the errors here.

Regards

Juan

TP LOG for the request :

1 ETP199X######################################

1 ETP182 CHECK WRITEABILITY OF BUFFERS

1 ETP101 transport order : "XX5K900146"

1 ETP102 system : "XX5"

1 ETP108 tp path : "tp"

1 ETP109 version and release : "340.16.37" "640"

1 ETP198

4 ETP201 Check target systems buffer: "C:\usr\sap\trans\buffer\I04"

3 ETP203 Buffer "C:\usr\sap\trans\buffer\I04" is writeable

1 ETP182 CHECK WRITEABILITY OF BUFFERS

1 ETP110 end date and time : "20090323095702"

1 ETP111 exit code : "0"

1 ETP199 ######################################

1 ETP199X######################################

1 ETP183 EXPORT PREPARATION

1 ETP101 transport order : "XX5K900146"

1 ETP102 system : "XX5"

1 ETP108 tp path : "tp"

1 ETP109 version and release : "340.16.37" "640"

1 ETP198

2 EPU230XExecution of the export pre-processing methods for request "XX5K900146"

4 EPU111 on the application server: "XXXX01"

4 EPU138 in client : "XXX"

2 EPU233XStart: Execution of object-specific export pre-processing methods

3 EPU242XStart: Execution of method "BEFORE_EXP_CUST_ADDRESS"

4 EPU243 End: Execution of method "BEFORE_EXP_CUST_ADDRESS"

3 EPU234 End: Execution of object-specific export pre-processing methods

2 EPU235XStart: Version creation of the objects of the request "XX5K900146"

3 EPU237 Version creation started as update request

2 EPU236 End: Version creation of the objects of the request "XX5K900146"

2 EPU231XStart: Adjusting the object directory for the objects of the request "XX5K900146"

2 EPU232 End: Adapting the object directory for the objects of the request "XX5K900146"

1 ETP183 EXPORT PREPARATION

1 ETP110 end date and time : "20090323095718"

1 ETP111 exit code : "0"

1 ETP199 ######################################

1 ETP199X######################################

1 ETP150 MAIN EXPORT

1 ETP101 transport order : "XX5K900146"

1 ETP102 system : "XX5"

1 ETP108 tp path : "tp"

1 ETP109 version and release : "340.16.37" "640"

1 ETP198

4 ETW000 R3trans.exe version 6.13 (release 640 - 10.07.07 - 13:48:00).

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time : 23.03.2009 - 09:57:24

4 ETW000 control file: C:\usr\sap\trans\tmp\XX5KK900146.XX5

4 ETW000 > #pid 2932 on ides01 (APServiceXX5)

4 ETW000 > export

4 ETW000 > file='C:\usr\sap\trans\data\R900146.XX5'

4 ETW000 > client=XXX

4 ETW000 > buffersync=yes

4 ETW000 >

4 ETW000 > use comm 'XX5K900146'

4 ETW000 R3trans was called as follows: R3trans.exe -w C:\usr\sap\trans\tmp\XX5E900146.I05 C:\usr\sap\trans\tmp\XX5KK900146.XX5

4 ETW000 Connected to DBMS = MSSQL --- SERVER = 'XXXX01' DBNAME = 'XX5' --- SYSTEM = 'XX5'.

4 ETW690 "0" "0"

4 ETW000 COMMIT (0).

4 ETW000 trace at level 1 opened for a given file pointer

4 ETW000

4 ETW000 ================== STEP 1 =====================

4 ETW000 date&time : 23.03.2009 - 09:57:24

4 ETW000 function : EXPORT

4 ETW000 data file : C:\usr\sap\trans\data\R900146.XX5

4 ETW000 buffersync : YES

4 ETW000 client : XXX

4 ETW000 Language : ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdefghijklmnopqrstuvwxyz(),./:;& (ISO-ARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVBGLTLVZ1SRZHTHKOROSLHRMSUKETAFISCASH????????ID??????????????????????????????????Z2Z3Z4Z5Z6Z7Z8Z9)

4 ETW000 Compression : L

4 ETW000 l.s.m. : VECTOR

4 ETW000 commit : 100000

4 ETW000 table cache : dynamic

4 ETW000

4 ETW000 GetDBMigrateCodePagesLangs uses TCP0D, TCPDB, TCP0C.

3 ETW673XUse Commandfile "XX5K900146"

4 ETW000 /* Configuration request for MM */

4 ETW000 trfunction: 'W' (customizing transport)

4 ETW000 trstatus : 'O'

4 ETW000 tarsystem : XX4

4 ETW000 user : XXXXXXX

4 ETW000 date : 23.03.2009 - 09:57:02

4 ETW000 [dev trc ,00000] Mon Mar 23 09:57:26 2009 1393191 1.393191

4 ETW000 [dev trc ,00000] Provider SQLNCLI could not be initialized. See note #734034 for more information.

4 ETW000 34 1.393225

4 ETW000 [dev trc ,00000] Using provider SQLOLEDB instead. 17 1.393242

4 ETW000 1 entry from E070 exported (XX5K900146 ).

4 ETW000 708 entries from E071 exported (XX5K900146 *).

4 ETW000 120256 entries from E071K exported (XX5K900146 *).

4 ETW000 2248 entries from E071KF exported (XX5K900146 *).

4 ETW000 1 entry from E070C exported (XX5K900146 ).

4 ETW000 0 entries from E070A exported XX5K900146 *).

4 ETW000 0 entries from CTS_SERIAL exported (XX5K900146 *).

4 ETW000 1 entry from E07T exported (XX5K900146 *).

3 ETW678Xstart export of "R3TRCDATCAREAMAINT" ...

4 ETW000 0 entries from STABULOG exported (CDATCAREAMAINT *).

4 ETW000 0 entries from TADIR exported (R3TRCDATCAREAMAINT ).

4 ETW000 1 entry from T001 exported (XXXSIRU); as part of view V_TKA02

4 ETW000 1 entry from T001 exported (XXXVN01); as part of view V_TKA02

4 ETW000 1 entry from T001 exported (XXXWM01); as part of view V_TKA02

4 ETW000 1 entry from TKA00 exported (XXXSIRU2009); as part of view V_TKA00

4 ETW000 1 entry from TKA00 exported (XXXWM012008); as part of view V_TKA00

4 ETW000 1 entry from TKA01 exported (1210001); as part of view V_TKA01_GD

.....

....

3 ETW678Xstart export of "R3TRCDATVC_SHPH" ...

4 ETW000 0 entries from STABULOG exported (CDATVC_SHPH *).

4 ETW000 0 entries from TADIR exported (R3TRCDATVC_SHPH ).

4 ETW000 1 entry from TVLK exported (121LF ); as part of view V_TVLK_TXT

4 ETW000 1 entry from TVLKT exported (121ELF ); as part of view V_TVLK_TXT

4 ETW679 end export of "R3TRCDATVC_SHPH".

4 ETW000 XX5K900146 touched.

4 ETW000 XX5K900146 released.

4 ETW000 3592589 bytes written.

4 ETW000 Transport overhead 48.7 %.

4 ETW000 Data compressed to 4.2 %.

4 ETW000 Duration: 2:45 min (21773 bytes/sec).

4 ETW000 0 tables in P-buffer synchronized.

4 ETW000 0 tables in R-buffer synchronized.

4 ETW000 E071-OBJFUNCs 000261 - 000261 updated ('D').

4 ETW690 "95616" "95616"

4 ETW000 COMMIT (3592589).

4 ETW000

4 ETW000 Summary:

4 ETW000

4 ETW000 1 COMML exported

4 ETW000 1 COMMT exported

4 ETW000 8951 DELETE commands exported

4 ETW000 Totally 122158 tabentries exported

4 ETW000

4 ETW000 [dev trc ,00000] Mon Mar 23 10:00:09 2009 163721901 165.115143

4 ETW000 [dev trc ,00000] Disconnecting from ALL connections: 16 165.115159

4 ETW000 [dev trc ,00000] Mon Mar 23 10:00:10 2009 10282 165.125441

4 ETW000 [dev trc ,00000] Disconnected from connection 0 29 165.125470

4 ETW000 [dev trc ,00000] statistics db_con_commit (com_total=2, com_tx=2)

4 ETW000 24 165.125494

4 ETW000 [dev trc ,00000] statistics db_con_rollback (roll_total=0, roll_tx=0)

4 ETW000 22 165.125516

4 ETW000 Disconnected from database.

4 ETW000 End of Transport (0004).

4 ETW000 date&time: 23.03.2009 - 10:00:10

4 ETW000 37 warnings occured.

1 ETP150 MAIN EXPORT

1 ETP110 end date and time : "20090323100010"

1 ETP111 exit code : "4"

1 ETP199 ######################################

HEREWITH I HAD POSTED THE TRANSPORT LOG IN /usr/sap/tran/log .

As far as i can see the transport finished successfully but with a warnings. You need to review the warnings in the transport log with the developer.

Regards

Juan

Hi can u help me that what are the changes needed to be done in the transport. Since many customization are saved hereso i cant make it in a new request.

Is there any option to change the request ID alone and do retransport.I had released it correctly from DEV system.

kindly suggest me pls.

Thanks and regards,

Rakesh.

Rakesh,

it seems what you posted here is the export log from your DEV system;

look for the import log from your QTY system!

Hi ,

I am searched with the request ID in the QTY system. The particular request is not found there. Is that can i do any manual transport from these two systems. Is that recommended .

But it is been released from DEV system and not found in QTY system.How to change the released objects now.

Kindly suggest me.

Thanks and regards,

Rakesh.

But it is been released from DEV system and not found in QTY

maybe it was released as a local request... check the request type in SE09

Regards

Juan

Hi ,

No it is released under QTY system only. I can see that request in import queue in QTY system, My issue is i am not able to import it to the QTY system.If i give import in few seconds it changes the status to green and if i check it is not updated in QTY system.

Can i do manual transport at OS level is that possible.

Thanks and regards,

Rakesh.

Can i do manual transport at OS level is that possible.

It's not going to make any difference.

Can you post the errors on the transport log?

Regards

Juan

Hi transport log :

23.03.2009 10:03:07 IMPORT XX5K900146 XX4 clires XXX U0

Last activity: 23.03.2009 10:03:09

Target client = Source Client

Maximum Return Code: 0211 - tp ended

tp finished: no info about transport request found

######################################

Main export

Transport request___: XX5K900146

System______________: XX5

tp path : tp

Version and Release: 340.16.37 640

Main export

End date and time : 20090323100010

Ended with return code: ===> 4 <===

######################################

Thanks and regards,

Rakesh.

Ended with return code: ===> 4 <===

This means that the transport finished with warnings... check the warnings on the Import log.

Regards

Juan

tp finished: no info about transport request found

Make sure data file (in /usr/sap/trans/data) and cofile (in /usr/sap/trans/cofiles) exist, and are readable; and cofile writable as well.

Hi,

The files and co-files are available in DEV system Log and it is not available in QTY system. how to clear the warnings of the transport.

Thanks and regards,

Rakesh.

Rakesh

Warnings should not be an issue,the only thing is whther the data has come in QTY or not

Rohit

Hi ,

I cant find the request in the log of QTY system.Is that any way now to bring it to the QTY system since it is been released in DEV system. It is not possible to save all again in a new request since , many customizing are saved in this particular request.

Kindly suggest me,

Thanks and regards,

Rakesh.

Once again... return code 4 means that the transport went though successfully but with warnings... you need to check the warnings... so go to STMS -> mark the transport -> click on logs -> double click on import and analize the warnings.

Juan

Hi ,

Start export R3TRTEXTOCS,V1ZBA0,STAM,H ...

Start export R3TRTEXTOCS,V1ZBA0,STAM,I ...

0 entries from SMODILOG exported (TEXTOCS,V1ZBA0,STAM,I *).

0 entries from TADIR exported (R3TRTEXTOCS,V1ZBA0,STAM,I ).

0 entries from SMODISRC exported (CITEXTOCS,V1ZBA0,STAM,I *).

0 entries from SMODISRC exported (CUTEXTOCS,V1ZBA0,STAM,I *).

0 entries from SMODISRC exported (CVTEXTOCS,V1ZBA0,STAM,I *).

0 entries from SMODISRC exported (PRTEXTOCS,V1ZBA0,STAM,I *).

0 entries from SMODISRC exported (SVTEXTOCS,V1ZBA0,STAM,I *).

0 entries from STXB exported (121TXOCS V1ZBA0 STAMI*).

0 entries from STXH exported (121OCS V1ZBA0 STAMI*).

0 entries from STXL exported (121TXOCS V1ZBA0 STAMI*).

R3TRTEXTOCS,V1ZBA0,STAM,I not found, object also deleted in target system

End of export R3TRTEXTOCS,V1ZBA0,STAM,I

Actuallly this is the warning i am getting in that exports. I cant able to understand this log. Can u pls giv me a solution or any clue how to solve this pls.

Thanks and regards,

Rakesh.

Check if SAP note 426303 is helpful to you.

Also try attaching the objects from your old request into the new one.

goto SE01, create new customizing request.

Delete the attached task. Select the request and from the top menu select:

Request/Task --> Object List ---> Include Objects and then enter the request number you have released.

Once it is done, you have new request with all the customization done attached. Release this request and try importing it again into the QTY system. See if this fails or you are successful.

Rahul

Ask a Question

Top Q&A Solution Author

User

Count