Code inspector - Release of transport

Hi,
When we release the transport request, default variant of code inspector is executed.
Is there any customization for this ? If yes, were do we do setting for this? I need to use own created variant instead of default.
Regards,,,
Sunil Joyous

Hi,
You can create your own default variant in transaction SCI. If you create a local variant instead of a global one and call it DEFAULT it will be used instead of the standard one.
Regards,
Nick

Similar Messages

Check code inspector results after release

Hello experts,
I introduced the Code Inspector upon release of a workbench transport request.
All transport requests are released by developers, but the team lead sometimes wants to very the result afterwards.
Is there a way to get the code inspector results after a few days after the release?
Thanks a lot.
Dimitri

Dear Dimitri,
You can test released transport via SCII just as you can test unreleased transports.
Go to SCII, check 'Request/Task' and give the name of the released transport in the Object Selection tab and press F8 or the execute button.
I know that this is long after you asked the question but perhaps somebody here can use the information.
Regards,
Hans

Releasing a Transport Request ends with error code 0012.

Hi,
We have a Development system and a Production System (both running on separate windows machine) but they are not connected in STMS. We perform transporting of Requests at o.s level and NOT through STMS.
We are facing this new problem - We are trying to release a Transport Request in SE01 and it ends with error code 0012. The task inside the Request is released without any error. There is no Notes in SAP Marketplace for this.
Test call of transport control program (tp) ended with return code 0012
Message no. TK094
Diagnosis
Your transport request could not be exported, since all requirements were not fulfilled.
Calling the transport control program tp
"tp EXPCHK EFIK900025 pf=E:\usr\sap\trans\bin\TP_DOMAIN_EFI.PFL -Dtransdir=E:\usr\sa"
which checks the export requirements, returned the following information:
Return code from tp: 0012
Error text from tp: ERROR: Buffer check failed.
System Response
Further processing is terminated.
Procedure
Check the following points:
Feasibility of the transport control program tp
Parameter settings in the transport profile
Availability of the transport directory and the subdirectories (cofiles, data, log, sapnames, bin)
Write authorization for the subdirectories
Write authorization for the files of the subdirectories cofiles, data, log, sapnames
Release the request again when the error has been removed
Please help.
Regards,
Mohan.

Hi Mohan,
Nice to hear that that your problem is resolved.
For Pamater CTC, please check the below links:
Automatic transport between DEV clients ?
http://sapsolutions.searchsap.com/kw;ExtendedTransportControl/content-sap.htm
Regards,
Hari Kishan

How to create and transport my own globel check variant for Code Inspector

Hi,
I want to create my own global check variant with Code Inspector, so that I can transport the Variant in other systems, but I can not save my variant whitout registering a SSCR-Key.
Can anybody help me?
Best regards
Marcus

I have solved it myself and will post the solution here soon.

Transport Organizer Syntax Check using the Code Inspector

dear fellows,
i'm facing a problem when i check the syntax of transport. When i'm using the option to check the syntax within the transaction se01 the system starts no longer the extended check but the code inspector.
is there any possibility to turn this code inspector check off and to get the extended syntax check again?
or on the othe hand, which variant is used for the check and is there any possibility to change the variant that is used?
thanks for your answers,
Robert

Nope... this is SAP standard code so I will reply to the OSS and wait for them to come back to you.
Regards
Juan

Code Inspector Issue - "MODIFY - without TRANSPORTING was found in line "

Hi all
I am new to abap and my transports are unable to move further because of code inspector error
"MODIFY - without TRANSPORTING was found in line ". Help me resolve the issue.
For example
LOOP AT i_user_add.
 i_user_add-mandt = sy-mandt.
 MODIFY i_user_add.
ENDLOOP.
<removed_by_moderator>
Edited by: Julius Bussche on Oct 16, 2008 3:23 PM

Hi ,
 while modifying the internal table specify wich field you are modifying
modify <internal table > from <work area> transporting <fields>.
regards
naveen

Multiple transports in Code Inspector object set

I'd like to be able to put a Code Inspector object set together with multiple transports and my current version (46c)only supports a single input. Anyone know how to input multiple transports?
Tim Barrow
ADP

Tim,
Even the current version (7.0) supports just one transport request. Looks like that is ruled out, then.
You could use the first tab (Select object set) to include multiple packages? Or you could use the 'free selection' to specify objects..
Hope this helps.
Sudha

Code Inspector Error in program

Hi All,
When I released the transport for a program through solution manager, it showed a warning as "program contains code inspector error. Release anyway?" and I released it since the subtask was already released and changing the program will not be possible in that transport request. Now the program is in Quality system. But my concern is that what problem a program can cause when it is moved to production if it contains Code Inspector error? Since I have no much experience in ABAP. Please advise on this.
Regards,

It depends on what kind of errors you got in Dev system .
You can again check the program for code inspector errors and if there are Priority 1 errors fix them in a ne wTr.

Field Label error in code inspector

Hello ,
I am working in release 6.0 . An i tring to release one transport
Code inspector is giving following error on screens .
"Field label has a fixed font instead of proportional font
When I press on info button i got following message
A field name that has the attribute "Equidistant font" was found. Field names should all be output in proportional font.
Procedure
Correct the "Equidistant" flag for this field in the Screen Painter.
Do you know how we can correct Equidistant flag ?
Please advice
Krsto

You get this error because one of the labels have the "Fixed Font" set and the visible length is less than the default length.
You can find all this fields on the properties of the label.
To avoid this warning, set the visible length as the default length.
Regards,
Naimesh Patel

My first Code Inspector extension

I'm trying to write my first own extension of Code Inspector. I don't like to discover again new wheel so I'm asking You:
Is in ABAP any test which check how long is procedure (how many lines is beetwene FORM ENDFORM statement?) which return warnings when length is just a little bit to big and errors when exceed a lot maximum length?
I'm only interesting that is already in SAP this kind of test.
Cheers, Tomek

Hello Thomasz,
you will see all SAP checks when starting SCI. Only with the newer releases there is a check on program metrics.
Regards,
Klaus
Documentation
Determining Complexity of Procedures in ABAP Programs
The check calculates different complexity measurements for procedures in ABAP programs. These measurements are:
Number of Statements. Cyclical complexity. Here there is also the variant through a test parameter as to whether a CASE statement is treated as a simple or multiple branch.
Number of Versions. This measurement can only be determined in the original system of the respective program since these versions are only there.
In the results display, there is only one single information message. The results list is displayed when you double-click this message. In this list, the above-mentioned complexity measurements are specified after the procedure type and the procedure name. In addition, the Include and the line where the respective procedure begins are displayed. By double-clicking here, you can branch to the source code. The list can be sorted, as usual, by any column you wish. In addition, the standard procedures for exporting (for example, to Excel) are provided.
The test specifies the various procedure types in the results list in the following manner:
METH : Methods
FORM: Forms
FUNC: Function modules
MOD: Modules
STAS: START-OF-SELECTION event
TOPS: TOP-OF-PAGE event
Some code excerpt
method RUN .
data:
 L_EXCP type ref to CX_EXCEPTION,
 L_NAME type STRING,
 L_CLASS type STRING.
if REF_SCAN is initial.
 check GET( ) = 'X'.
endif.
check REF_SCAN->SUBRC = 0.
if PA_VERSION = 'X'.
 GET_PROC_VERSIONS( ).
endif.
STATEMENT_INDEX = 1.
try.
 do.
 read table REF_SCAN->STATEMENTS index STATEMENT_INDEX into STATEMENT_WA.
 if SY-SUBRC <> 0. exit. endif.
 add 1 to STATEMENT_INDEX.
 check STATEMENT_WA-FROM <= STATEMENT_WA-TO.
*-- avoid native SQL
 check STATEMENT_WA-TYPE na 'EMPSDR'.
 case KEYWORD( ).
 when 'PROGRAM'
 or 'REPORT'
 or 'START-OF-SELECTION'.
 CHECK( P_PROC_TYPE = 'SSEL' P_PROC_NAME = '%' ).
 when 'END-OF-SELECTION'.
 CHECK( P_PROC_TYPE = 'ESEL' P_PROC_NAME = '%' ).
 when 'FORM'.
 L_NAME = GET_TOKEN_REL( 2 ).
 CHECK( P_PROC_TYPE = 'FORM' P_PROC_NAME = L_NAME ).
 when 'FUNCTION'.
 L_NAME = GET_TOKEN_REL( 2 ).
 CHECK( P_PROC_TYPE = 'FUNC' P_PROC_NAME = L_NAME ).
 when 'METHOD'.
 L_NAME = GET_TOKEN_REL( 2 ).
 concatenate L_CLASS '=>' L_NAME into L_NAME.
 CHECK( P_PROC_TYPE = 'METH' P_PROC_NAME = L_NAME ).
 when 'MODULE'.
 L_NAME = GET_TOKEN_REL( 2 ).
 if GET_TOKEN_REL( 3 ) = 'OUTPUT'.
 CHECK( P_PROC_TYPE = 'MODO' P_PROC_NAME = L_NAME ).
 else.
 CHECK( P_PROC_TYPE = 'MODI' P_PROC_NAME = L_NAME ).
 endif.
 when 'CLASS'.
 L_CLASS = GET_TOKEN_REL( 2 ).
 when 'INITIALIZATION'.
 CHECK( P_PROC_TYPE = 'INIT' P_PROC_NAME = '%' ).
 when 'GET'.
 L_NAME = GET_TOKEN_REL( 2 ).
 if GET_TOKEN_REL( 3 ) = 'LATE'.
 CHECK( P_PROC_TYPE = 'GETL' P_PROC_NAME = L_NAME ).
 else.
 CHECK( P_PROC_TYPE = 'GET' P_PROC_NAME = L_NAME ).
 endif.
 when 'AT'.
 L_NAME = GET_TOKEN_REL( 2 ).
 if strlen( L_NAME ) > 2 and L_NAME(2) = 'PF'.
 L_NAME = L_NAME+2.
 CHECK( P_PROC_TYPE = 'ATPF' P_PROC_NAME = L_NAME ).
 else.
 case L_NAME.
 when 'USER-COMMAND'.
 CHECK( P_PROC_TYPE = 'ATUC' P_PROC_NAME = '%' ).
 when 'LINE-SELECTION'.
 CHECK( P_PROC_TYPE = 'LISE' P_PROC_NAME = '%' ).
 when 'SELECTION-SCREEN'.
 L_NAME = GET_TOKEN_REL( 3 ).
 if L_NAME is initial.
 CHECK( P_PROC_TYPE = 'ATSS' P_PROC_NAME = '%' ).
 else.
 CHECK( P_PROC_TYPE = 'ATSS' P_PROC_NAME = L_NAME ).
 endif.
 endcase.
 endif.
 when 'TOP-OF-PAGE'.
 if GET_TOKEN_REL( 2 ) = 'DURING'.
 CHECK( P_PROC_TYPE = 'TOPS' P_PROC_NAME = '%' ).
 else.
 CHECK( P_PROC_TYPE = 'TOPA' P_PROC_NAME = '%' ).
 endif.
 when 'END-OF-PAGE'.
 CHECK( P_PROC_TYPE = 'ENPA' P_PROC_NAME = '%' ).
 when 'LOAD-OF-PROGRAM'.
 CHECK( P_PROC_TYPE = 'LDPR' P_PROC_NAME = '%' ).
 endcase.
 enddo.
 catch CX_EXCEPTION into L_EXCP.
 raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_EXCP->INCLUDE
 P_LINE = L_EXCP->LINE
 P_COLUMN = L_EXCP->COLUMN
 P_KIND = C_WARNING
 P_TEST = C_MY_NAME
 P_CODE = 'SYNTAX'.
endtry.
endmethod.
method CHECK .
data:
 L_INCLUDE type PROGRAM,
 L_LINE type I,
 L_COLUMN type TOKEN_COL,
 L_COMPLEXITY type I value 1,
 L_STMNTS type I,
 L_VERSIONS type I,
 L_COMPLEXITY_C type SYCHAR10,
 L_STMNTS_C type SYCHAR10,
 L_VERSIONS_C type SYCHAR10,
 L_NESTED_C type SYCHAR10,
 L_PARAM_1 type STRING,
 L_TOKEN type STRING,
 L_PROC_VERSION like line of PROC_VERSIONS,
 L_NESTED type I,
 L_MAX_NESTED type I.
L_INCLUDE = GET_INCLUDE( ).
L_LINE = TOKEN_WA-ROW.
L_COLUMN = TOKEN_WA-COL.
do.
 read table REF_SCAN->STATEMENTS index STATEMENT_INDEX into STATEMENT_WA.
 if SY-SUBRC <> 0.
 exit.
 endif.
 add 1 to STATEMENT_INDEX.
 check STATEMENT_WA-FROM <= STATEMENT_WA-TO.
 check STATEMENT_WA-TYPE na 'PS'.
*-- avoid native SQL
* check STATEMENT_WA-TYPE na 'EMDR'.
 case KEYWORD( ).
 when 'IF' or 'WHILE' or 'LOOP' or 'DO' or 'PROVIDE'.
 if TOKEN_WA-ROW <> 0.
 add 1 to L_COMPLEXITY.
 add 1 to L_NESTED.
 if L_NESTED > L_MAX_NESTED.
 L_MAX_NESTED = L_NESTED.
 endif.
 endif.
 when 'ELSEIF'.
 if TOKEN_WA-ROW <> 0.
 add 1 to L_COMPLEXITY.
 endif.
 when 'ENDIF' or 'ENDWHILE' or 'ENDLOOP' or 'ENDDO' or 'ENDTRY'.
 subtract 1 from L_NESTED.
 when 'TRY'.
 add 1 to L_NESTED.
 if L_NESTED > L_MAX_NESTED.
 L_MAX_NESTED = L_NESTED.
 endif.
 when 'SELECT'.
 when 'ENDSELECT'.
 if TOKEN_WA-ROW <> 0.
 add 1 to L_COMPLEXITY.
 add 1 to L_NESTED.
 if L_NESTED > L_MAX_NESTED.
 L_MAX_NESTED = L_NESTED.
 endif.
 subtract 1 from L_NESTED.
 endif.
 when 'CHECK'.
 if TOKEN_WA-ROW <> 0.
 add 1 to L_COMPLEXITY.
 endif.
 when 'CASE'.
 if PA_WITH_CASE = 'X'.
 add 1 to L_COMPLEXITY.
 endif.
 add 1 to L_NESTED.
 if L_NESTED > L_MAX_NESTED.
 L_MAX_NESTED = L_NESTED.
 endif.
 when 'ENDCASE'.
 subtract 1 from L_NESTED.
 when 'WHEN'.
 if PA_WITH_CASE <> 'X' and TOKEN_WA-ROW <> 0.
 if GET_TOKEN_REL( 2 ) <> 'OTHERS'.
 add 1 to L_COMPLEXITY.
 endif.
 endif.
 when 'ENDFORM' or 'ENDFUNCTION' or 'ENDMETHOD' or 'ENDMODULE'.
 exit.
 when 'FORM'
 or 'FUNCTION'
 or 'MODULE'
 or 'START-OF-SELECTION'
 or 'END-OF-SELECTION'
 or 'TOP-OF-PAGE'
 or 'END-OF-PAGE'
 or 'LOAD-OF-PROGRAM'
 or 'INITIALIZATION'
 or 'CLASS'.
 subtract 1 from STATEMENT_INDEX.
 exit.
 when 'GET'.
 if GET_TOKEN_REL( 2 ) <> 'TIME'.
 case GET_TOKEN_REL( 3 ).
 when 'LATE' or 'FIELDS' or ''.
 subtract 1 from STATEMENT_INDEX.
 exit.
 endcase.
 endif.
 when 'AT'.
 L_TOKEN = GET_TOKEN_REL( 2 ).
 if strlen( L_TOKEN ) > 2 and L_TOKEN(2) = 'PF'.
 subtract 1 from STATEMENT_INDEX.
 exit.
 else.
 case L_TOKEN.
 when 'USER-COMMAND'.
 subtract 1 from STATEMENT_INDEX.
 exit.
 when 'LINE-SELECTION'.
 subtract 1 from STATEMENT_INDEX.
 exit.
 when 'SELECTION-SCREEN'.
 subtract 1 from STATEMENT_INDEX.
 exit.
 endcase.
 endif.
 add 1 to L_NESTED.
 if L_NESTED > L_MAX_NESTED.
 L_MAX_NESTED = L_NESTED.
 endif.
 add 1 to L_COMPLEXITY.
 when 'ENDAT'.
 subtract 1 from L_NESTED.
 endcase.
 if PA_VERSION = 'X'.
 loop at REF_SCAN->TOKENS from STATEMENT_WA-FROM to STATEMENT_WA-TO into TOKEN_WA.
 check TOKEN_WA-ROW <> 0.
 CL_CI_PROVIDE_CHECKSUM=>GEN_CHKSUM_FROM_STRING( exporting P_PARAM = TOKEN_WA-STR
 changing P_CRC_VALUE = L_PROC_VERSION-CRC ).
 endloop.
 endif.
 add 1 to L_STMNTS.
enddo.
L_PROC_VERSION-PROC_TYPE = P_PROC_TYPE.
L_PROC_VERSION-PROC_NAME = P_PROC_NAME.
collect L_PROC_VERSION into PROC_VERSIONS.
loop at PROC_VERSIONS transporting no fields where PROC_TYPE = P_PROC_TYPE and PROC_NAME = P_PROC_NAME.
 add 1 to L_VERSIONS.
endloop.
L_COMPLEXITY_C = L_COMPLEXITY.
L_NESTED_C = L_MAX_NESTED.
L_STMNTS_C = L_STMNTS.
L_VERSIONS_C = L_VERSIONS.
concatenate P_PROC_TYPE P_PROC_NAME L_STMNTS_C L_COMPLEXITY_C L_NESTED_C L_VERSIONS_C into L_PARAM_1 separated by ' '.
condense L_PARAM_1.
raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_INCLUDE
 P_LINE = L_LINE
 P_COLUMN = L_COLUMN
 P_KIND = C_NOTE
 P_TEST = C_MY_NAME
 P_CODE = C_CODE_SUMMARY
 P_PARAM_1 = L_PARAM_1.
if L_COMPLEXITY >= PA_COMPLEXITY.
 raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_INCLUDE
 P_LINE = L_LINE
 P_COLUMN = L_COLUMN
 P_KIND = C_WARNING
 P_TEST = C_MY_NAME
 P_CODE = C_CODE_COMPLEXITY
 P_PARAM_1 = L_COMPLEXITY_C.
endif.
if L_STMNTS >= PA_STMNTS.
 raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_INCLUDE
 P_LINE = L_LINE
 P_COLUMN = L_COLUMN
 P_KIND = C_WARNING
 P_TEST = C_MY_NAME
 P_CODE = C_CODE_STMNTS
 P_PARAM_1 = L_STMNTS_C.
endif.
if L_NESTED >= PA_NESTED.
 raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_INCLUDE
 P_LINE = L_LINE
 P_COLUMN = L_COLUMN
 P_KIND = C_WARNING
 P_TEST = C_MY_NAME
 P_CODE = C_CODE_NESTED
 P_PARAM_1 = L_NESTED_C.
endif.
if L_VERSIONS >= PA_VERSIONS.
 raise event MESSAGE exporting
 P_SUB_OBJ_TYPE = C_TYPE_INCLUDE
 P_SUB_OBJ_NAME = L_INCLUDE
 P_LINE = L_LINE
 P_COLUMN = L_COLUMN
 P_KIND = C_WARNING
 P_TEST = C_MY_NAME
 P_CODE = C_CODE_VERSIONS
 P_PARAM_1 = L_VERSIONS_C.
endif.
endmethod.

We couldn't release any transport request!

Hi experts,
We could't release any transport request on DEV from today.
We could do it until yesterday.
We have never changed any settings.
Except release, we can use SAP system, and
we can import released transport request to QAS .
Also I could tp addtobuffer on DEV.
[Operation]
SE10 -> select transport request -> click [release] button
and, we can see the error message as below.
Error Message *****************************************************
Test call of transport control program (tp) ended with return code
[Transport Log]
We can see the log as below.
ERROR: No connect due to DbSl Load Lib Failure
ERROR: environment variable dbms_type is not set.
ERROR: Connect to RDV failed (20090220140504).
ERROR: Connect to RDV failed (20090220140740), failed to read table SVERS.
[Our Action]
1. Change Environment variable & Restart SAP (note 351586)
2. replace tp & saptrans
3. change parameter (note 175627)
4. add full control to everyone on sap/trans
5. see note 534765，98678，128126，592514，799058，879941，508140，610640
Thank you in advance.
BR,
Toshi

Hi,
Thank you for your reply.
I did r3trans -d, and the result is as belllow.
F:\usr\sap\RDV\SYS\exe\run>r3trans -d
This is r3trans version 6.13 (release 640 - 07.01.08 - 14:25:00).
unicode enabled version
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
r3trans finished (0012).
Also I checked TP_DOMAIN.pfl, but it seems that there is no problem.
But I found doubtful point.
It is environmental variable, and now it is differnt from last friday.
Example, last friday , there was variable as bellow,
but today I couldn't find them
In the meantime , I will deal with them.
dbms_type=MSS
MSSQL_DBNAME=RDV
MSSQL_SCHEMA=rdv
MSSQL_SERVER=<hostname>\RDV
Toshi

Error 12 when releasing a transport

I am trying to release a transport, but get an error 12 "The request's target VBQ.500 is client dependant but the target system cannot handle that". VBQ.500 is a virtual system. Anyone have any suggestions for me to check out? I'm at a loss.
Thanks,
-- Jackie

Hello Jackie
I cannot tell you the reason for the error code. Somehow the CTS "believes" that the target system cannot handle clients and client-dependent objects.
For the moment I think your main problem is to release your customizing request (or is it a workbench request containing client-dependent repository objects?). Try to change the target of your request. Perhaps the CTS can handle that. It might be necessary to adjust transport routes (transaction STMS) in order to get a "decent" target.
Is your virtual system VBQ.500 a consolidation system? If not then try to change this (Note: this is a critical SAP basis activity).
As soon as the request is released you can try to import it into your VBQ.500 system.
Regards
Uwe

Error when releasing a transportation order

Good morning.
I am trying to release a transportation order that contains a nonstandard table which has been added two fields, and the corresponding data elements and dominions of the new fields.
When releasing the order, dumps an error and cancels the export.
The status of the order now is "Initiated liberation".
The error code is:
"Error SQL 932 when accesing SPROXDAT: ORA-00932: inconsistent datatypes: expected %s got." And makes reference to data elements, but i think they are OK.
Please, ¿someone can help me?
Thanks a lot.
Regards.

well the problem is very likeley that the table has enhancement options which allow only character and NUMC append fields.
you most probably violated those preferences.

How to retire/archive/status a released workbench transport for an OSS note

My Question: Is there a best practice for the "retiring" or "archiving" or "statusing" of released workbench transports for OSS notes that have been imported into the quality environment, but should never be imported into the production environment?
For example an OSS note is applied and imported into QS1, but then a CRT Hotpack is applied as an entire patch upgrade, so that the prior individual transport is no longer needed. Best Business practice indicates to not delete a released transport, but unless there is a way to permanently segregate them from the remaining legitimately viable transports, there is always a risk that the "stale" code could inadvertently slip through thus overwriting good code.

Hello.
Well, you have confirmed what I suspected when I read the descriptions - wrong forum.
I chuckled and couldn't stop a broad smile from creeping across my face when I read your response though: "the old BASIS type questions". I knew we were a bit behind the times here; you have definitely confirmed this suspicion.
Thank you again. I'll try another search of the OSS notes or put in a customer message just for the heck of it.

Problem releasing workbench transports

We had created a number of changelists in our workbench and are trying to release these to transport them into out test system. When we release the transports which are created without issue in the development workbench we get the following message:
Preparation for export
Transport request : CRDK903862
System : CRD
tp path : tp
Version and release: 372.04.57 700
Execution of the export pre-processing methods for request CRDK903862
Start: Execution of object-specific export pre-processing methods
Changelist C647D7C9CCE64307AFC4F46272840107 is not complete in this system
Request CRDK903862 is modifiable after error during release
Preparation for export
End date and time : 20090925164345
Ended with return code: ===> 8 <===
The Transport Agent Service is already activated.
Has anyone any idea what the problem could be
Thanks in advance

Hi,
You need to first check which TranportOrder ID was not getting released on the server .
Then fire the below query to find the changelists associated with that TransportOrder in the ARS database-
select * from changelist where state <>0 and transportorderid ='<Name of that Transport Order ID>'
Then follow these steps -
1. Stop the Transport Agent in Source repository.
2. Cleanup the blobs from WBTRCL, WBTRBLOB, WBTRBSEG tables
 in ars repository for the changelists, which were associated with
that specific transport order.
DELETE FROM WBTRCL WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
DELETE FROM WBTRBSEG WHERE CLID = <cHANGELIST ID> (GIVE WITHOUT 0X)
3. Use the transaction SMOBDELCL to remove details of this
 changelist from the CRM server. This transaction
 would require you to enter the id of the changelist.
 The id should be entered without 0x.
4. Create a new change request in the CRM server and add these
changelists to the change request.
5. Steps 1-5 of Note 568624 can be followed for this but NOT steps
 6 and 7.DO NOT release the change request. There is no need to modify
 the TransportOrderId field in changelist table in ARS repository to
 reflect the new change request id.The field is there for
 documentation purpose only.
6. Update the state of the changelist in ARS repository to 1 so that
 Transport Agent can pickup the changelist and send it to server as
 soon as it is started.
Eg:
UPDATE CHANGELIST SET STATE = 1 WHERE CHANGELISTID = <0XChangelistID>
(GIVE WITH 0X)
7. Start the Transport Agent on both Source repository.
Also, you need to make sure that whenever you release a changelist from Mobile Application Studio then
you should not chose this transport Order(which was not getting released earlier) while choosing the transport
Order.

Code inspector - Release of transport

Similar Messages

Maybe you are looking for