Compare upgraded transports

Hi Experts,
iam wrking on an upgradation from 4.7E to ECC6.0,
my task is to check the upgraded transports and compare the objects in DEV and QAS (quality) systems using the tranport number, i have a plan to check every transport no in SE01( transport organizer) and compare the obejcts in both systems.
now my query is the procedure which iam following is currect or is there any trascation codes to compare the objects and request in both DEV and QAS systems? if yes please explain in detail.
Thanks in advance
regards
neeru
Message was edited by:
neeru

I still don't know what you are trying to do
The normal way would be:
- Upgrade your DEV system
- Do SPDD during and SPAU after the upgrade and create transports for changes
- Upgrade QAS
- BIND the transports into the upgrade
- check if everything worked
- use the same transports for PRD
I don't know what you want to "compare" between your DEV and QA...
Markus

Similar Messages

Post Upgrade transport

We're currently in our upgrade project. I have a concern about our transport system after upgrading to ECC 5.0. Here is my scenario. We are currently upgrading from 4.6C to ECC 5.0. All systems are central installations no app servers. Production server consist of PRD. Second server contains DEV and QA. The transport directory is shared between these server.
Upgrade landscape is on another server containing a Dev 5.0 and QA 5.0 system. Our go live plan is to upgrade PRD after testing on QA 5.0. I will manually add post upgrade transports to PRD and then import. My question is, will I run into any problems by manually adding the transports to PRD?
Yes, I know 6.0 is the better upgrade version but it's a long story.
Thank you in advance.

Hi Martin,
What do you mean by post upgrade transport if it is SPDD & SPAU fixes then for this you will get option during the upgrade to add a single transport request.
If you are talking @ the development happening into DEV & QA system during the production system upgrade the you just need to keep track of the transport sequance and need to import in a same sequance in the PRD after the upgrade
Hope this will help you, do revert if you need any more info.
Best Regards,
Sachin.

Upgrade - Transport Directory Strategy

Hello All,
We are having the below 4.7 Landscape,
DEV -> QAS -> PRD
We are having central Transport Directory. /usr/sap/trans is present in PRD which is mounted to DEV and QAS.
Now, we are doing DEV Upgrade.
So, we have created a Temporary Development DVP for 4.7 (which is a copy of DEV) so that we can continue our 4.7 Developments. Basically a approach of Dual Landscapes for Upgrades, one for 4.7 and one for ECC6.
Now, DEV has its local /usr/sap/trans, while we have mounted /usr/sap/trans(of PRD) to DVP. So new 4.7 Landscape is
DVP-> QAS -> PRD
After I do my QAS Upgrade, 4.7 Landscape will be turned to a 2 System landscape. Because of H/W constraints we cannot have two QAS (one for 4.7 and other for ECC6).
My question is,
After I do my QAS Upgrade, should my QAS DIR_TRANS point to /usr/sap/trans of DEV or PRD?
I am planning to point it to that of DEV, we will have dual Central Trans Directories,
one for 4.7 Landscape (/usr/sap/trans in PRD) for DVP-> PRD
and the other for ECC 6 (/usr/sap/trans in DEV) for DEV -> QAS
What do I do after PRD upgrade? should my DIR_TRANS for ECC 6 PRD point to /usr/sap/trans of DEV ?
Thanks!

if you are upgrading in a parallel landscape , you really dont need to worry about the transport directory of the 4.7 landscape.
as soon as you upgrade the DEV , i guess you can have a DIR_TRANS pointing locally
and you can make that the Central transport directory for the ECC landscape
As i said earlier , you need to keep track of changes that are performed in the 4.7 landspace after the DEV upgrade and make sure they are recreated(if necessary) in the ECC landspace as part of the Dual maintanence.
As long as you keeo track of the changes that are happening in the 4.7 landspace and manage it approriately , you are fine.
Planning would be crucial.
Gerard

How to upgrade transports from one sp to other

Hi,
I have transports which are created in support pack 11 for example. My whole system is the upgraded to support pack 12. I have large number of transports which are not moved to quality. Is there any program or any step where I can regenerate these transports from one support pack to other. I know I can make any small change in the program and save them which will create a new transports but I have huge list. Please advise.
Regards,

You need to create the transports again, You can move the existing transports simply into Quality system.
Well as per SAP theory during transports both the system should be equal in the Application level, but really it is not possible every time, becasue there are lots of update are coming regularly and you cannot create so many environement to test it first, so usually we are doing the same. we import the request between two support release,
Regards
Subhash

How to compare the transports requests in the same system

HI ,
Is there any option to compare transport requests in the same system whether both contain the same objects or not.

Ambarish, you can perform check in two ways.
-you can go to /usr/sap/trans compare the data files and cofiles andcheck the physical size whether it is same or not.
-you open the TR in SE01 tcode, select the sub TR and expand it it will show you the list of objects/programs included in that TR.
Hope it addresses your query.
Regards, Amber S | ITL

How to handle delta SPDD & SPAU adjustments in the 2nd Upgrade QA & PRD

Dear all,
We have successfully upgraded our development box and we have made the SPDD changes into a single transport requests and also the SPAU requests in a different requests.
Our ABAP team has made the SPDD adjustments comparing the objects with production and QA.
Now when we upgrade our QA box we have included the SPDD & SPAU transports and now we found that we have about 8 extra objects that needs to be modified manually in SPDD phase? out of 79 objects 71 is adjusted my out SPDD transports and it has left out 8 more objects.
These 8 objects were never shown in SPDD phase of our development box.
Can you please suggest us, like how to handle these delta objects, so that we won't phase the same issue when we move to production. (offcourse we will do 2-3 dry runs before going to production)
I have read the below note, but it is for the older version (without shadow instance)
Note 124522 - Importing a modification adjustment in 2nd upgrade
Thanks &
Regards
Senthil

1.If you have choosen strategy resource-minimized, they are adjusted during downtime before the ABAP Dictionary is activated.
copy the cofiles and datafiles in the respective directories. List all the requests in umodauto.lst.
In PREPARE phase ADJUSTPRP the following screen appears
For automatically maintaining your modification in your ystem during the upgrade transport request from earlier upgrades are searched in the umoauto.lst in directory /usr/sap/trans/bin..
The file could not be read
There are several reason why this may be correct
eg: 'this is your first upgrade' or 'your system is not modified'.
Did you expect a list of transports being found?
->Confirm a list of transports to be included in the upgrade
Select Yes & OK
Click on Yes to include the transport
Click Yes to stop the ACT_700 phase and check the results of SPDD
2.You can add additional requests to umodauto.lst
3. Regarding why its how in QA.? Reasons could be
1modification could have been done only in QA
2)Are the DEV and QA are on the same kernel & SP level's

Not able to transport the BI Content(Dev) to Production.

Hi Gurus,
<h6>I'm transporting BI Admin Cockpit to prod and its ending with errors.
I've successfully moved it to QA but while moving to Production it is ending with errors.</h6>
<h5>I'm trying to push the below listed objects:</h5>
<h6>0TCT_VC11                    InfoCube</h6>
<h6>0TCT_IS11                     InfoSources </h6>
<h6>0TCT_DS11     DW1CLNT500           Transfer_structure/Transfer_Rules</h6>
<h6>0TCT_DS11      DW1CLNT500           DataSources(3X)</h6>
<h6>ZPAK_4D8CABGMHNNDBZR20LDDZB07Y      InfoPakage </h6>
<h5>Along with these I've collected all the objects which were being used in InfoSource/Communication_Struct.</h5>
<h5>After moving it to Prod it ended with below mentioned error:</h5>
<h6>Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)</h6>
<h6>DataSource 0TCT_DS11 does not exist in source system PW2CLNT100 of version A</h6>
<h6>Mapping between data source 0TCT_DS11 and source system PW2CLNT100 is inconsistent</h6>
<h6>DataSource 0TCT_DS11 does not exist in source system PW2CLNT100 of version A</h6>
<h6>P.S. The DataSource is not from R/3 its BI DataSource.</h6>
<h6>Kindly help me in transporting it to Prod.
Many thanks in advance.</h6>
Regards,
Akhil

Hi Srikanth,
Compare the transport request which imported in QA & PRD from dev then you can find .
If you transported the same request from DEV to QA & DEV to PRD then this might be possible.
because of mapping of source system.
if you have transported same req from DEV to QA & DEV to PRD then plz import that request from QA to PRD.
Please check mapping of source systems in TX: RSA13 in DEV & QA systems.
Hope this will help you.
Thanks,
Vijay.

Program to Track the Transport Request

Hi Experts,
I got a requirement to write a program which can track and compare the Transport Request between the servers(Development ,Test and Production) .
If in case is there any descrepancy between the versions (In the server) it should throw an error saying that particular thing is missing or not synchronized.
For ex: If the program which is in Development server has some structure dependent to the code which is address to single TR.
where as same version of the program in Test don't have structure ,it has to throw an mismatch error.
If you guys have any clue on this please throw some light.
Higher points will be rewarded for every useful inputs.
Thanks in Advance,
Dharani

Hi Dharani,
Some sample Code. This I got debugging the SAP Standard.
TYPE-POOLS: strhi.
Data varaints for remote compare
INCLUDE rvscdcom.
INCLUDE rsvcutct.                      "Utilities, Constants, Types
INCLUDE rsvcvcct.                      "General Constants Types
INCLUDE rsvcvdct.                      "VRSD Constants Types
INCLUDE rsvctrct.                      "Tables for transports details
INCLUDE rsvcditd.
INCLUDE ole2incl.
DATA: application TYPE ole2_object.
DATA: remote_info_line LIKE abaptext-line,
      remote_info_line_a LIKE vrsinfolna,
      remote_info_line_b LIKE vrsinfolnb,
      remote_versno     LIKE vrsd-versno,
      remote_objname    LIKE vrsd-objname,
      remote_objtype    LIKE vrsd-objtype,
      remote_system     LIKE tadir-srcsystem,
      returncode        LIKE sy-subrc.
DATA: srcsys            LIKE tadir-srcsystem,
      author            LIKE tadir-author,
      mslang            LIKE tadir-masterlang,
      devcla            LIKE tadir-devclass,
      notfnd            LIKE bool.
INCLUDE rsvceudb.
INCLUDE rsvcvdtd.                      "VRSD Constants Types
INCLUDE rsvctrtd.                      "Tables for transports details
INCLUDE rsvctrfo.                      "Interface for transport details
INCLUDE rsvcrmck.                      "Remote Access Utilities: Checks
    PERFORM get_rfc_destination   USING    srcsys
                                  CHANGING w_destination1.
    SELECT SINGLE objname objtype korrnum FROM vrsd
           INTO CORRESPONDING FIELDS OF it_transports
           WHERE objname = it_abap_hdr-obj_name
          AND   objtype = it_abap_hdr-object
           AND   versno = '00000'.
   it_transports-trkorr = it_transports-korrnum.
Open tranport number with object name
    SELECT SINGLE trkorr pgmid object obj_name FROM e071
           INTO CORRESPONDING FIELDS OF it_transports
          WHERE trkorr   = it_transports-trkorr
          WHERE trkorr   NE 'SW3_P00001'
           WHERE pgmid    EQ it_abap_hdr-pgmid
           AND   object   EQ it_abap_hdr-object
           AND   obj_name EQ it_abap_hdr-name
           AND   lockflag EQ 'X'.
Open tranport number with object name
    SELECT SINGLE as4user as4date FROM e070
           INTO CORRESPONDING FIELDS OF it_transports
           WHERE trkorr   = it_transports-trkorr.
Remote compare
    IF p_rcomp = 'X'.
      CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
          text = 'Remote Comparison started'.
      IF w_destination1 NE space.
        PERFORM remote_compare USING w_destination1.
        IF it_transports-korrnum EQ it_transports-trkorr.
          it_abap_hdr-in_qa = 'Same version'.
        ELSEIF it_transports-korrnum IS INITIAL.
          it_abap_hdr-in_qa = 'Not found'.
        ELSE.
          it_abap_hdr-in_qa = 'Not Same version'.
        ENDIF.
        MODIFY it_abap_hdr.
      ENDIF.
FORM get_rfc_destination USING    pi_orgsys
                         CHANGING po_destination.
Baustein zur Auswahl von R/3-Destinationen.
FUNKTION(EN):
ruft einen FB, der den Anwender eine Destination für den
Aufruf der Versionsverwaltung als REMOTE-Function-Call
auswählen läßt.
Parameter:
PI_ORGSYS LIKE TADIR-SRCSYSTEM
PO_DESTINATION LIKE RFCDES-DESTINATION
DATA: dest_note(60).                 " für STRA Baustein
IF pi_orgsys = space.
    po_destination = space.
    dest_note = space.
ELSE.
    IF pi_orgsys <> sy-sysid.
      po_destination = pi_orgsys.
    ENDIF.
    CONCATENATE
      'Note: The original system of the object is the system'(l11)
      pi_orgsys INTO dest_note SEPARATED BY space.
    CONCATENATE dest_note '.' INTO dest_note.
ENDIF.
CALL FUNCTION 'SVRS_GET_RFC_DESTINATION'
    EXPORTING
      p_text         = dest_note
    IMPORTING
      remote_dest    = po_destination
    EXCEPTIONS
      no_destination = 1
      OTHERS         = 2.
IF sy-subrc <> 0.
Falls keine Destination ausgewählt wurde:
    po_destination = space.
ENDIF.
ENDFORM.                    "get_rfc_destination
INCLUDE LSVRLF07                                                   *
FORM get_version_list_remote USING pi_objtype pi_objname
                             CHANGING po_no_entry.
DATA: old_state LIKE bool.
REFRESH: vrs_dir_vrs, logvers_dir.
PERFORM check_vc_state_remote CHANGING old_state.
IF old_state = true.
    PERFORM get_old_fashioned_versdir USING pi_objtype pi_objname
                                      CHANGING po_no_entry.
ELSE.
    CALL FUNCTION 'SVRS_GET_VERSION_DIRECTORY_46'
      EXPORTING
        destination            = dir_destination
        objname                = pi_objname
        objtype                = pi_objtype
      TABLES
        version_list           = vrs_dir_vrs
        lversno_list           = logvers_dir
      EXCEPTIONS
        no_entry               = 1
        system_failure         = 2
        communication_failure_ = 3.
    CASE sy-subrc.
      WHEN 0.
        po_no_entry = false.
      WHEN 1.
        po_no_entry = true.
      WHEN 2.
       'Fehler im Zielsytem'.
       MESSAGE W123.
       LEAVE.
      WHEN 3.
       'Keine Verbindung zum Zielsystem'.
       MESSAGE W124.
       LEAVE.
    ENDCASE.
ENDIF.
ENDFORM.                    "get_version_list_remote
      FORM CHECK_VC_STATE_REMOTE                                    *
FORM check_vc_state_remote CHANGING po_old_state.
DATA: head_entry LIKE vrsd.
PERFORM get_vrsd_entry_remote
          USING head_type head_objname head_versno
          CHANGING head_entry po_old_state.
ENDFORM.                    "check_vc_state_remote
      FORM GET_VRSD_ENTRY_REMOTE                                    *
FORM get_vrsd_entry_remote USING pi_objtype pi_objname pi_versno
                           CHANGING vrsd_entry po_no_entry.
CALL FUNCTION 'GET_VRSD_ENTRY_46'
    EXPORTING
      destination           = dir_destination
      objname               = pi_objname
      objtype               = pi_objtype
      versno                = pi_versno
    IMPORTING
      vrsd_entry            = vrsd_entry
    EXCEPTIONS
      no_entry_found        = 1
      system_failure        = 2
      communication_failure = 3.
CASE sy-subrc.
    WHEN 0.
      po_no_entry = false.
    WHEN 1.
      po_no_entry = true.
    WHEN 2.
     'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 3.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
ENDFORM.                    "get_vrsd_entry_remote
      FORM GET_OLD_FASHIONED_VERSDIR                                *
--> PI_OBJTYPE                                                    *
--> PI_OBJNAME                                                    *
--> PO_NO_ENTRY                                                   *
FORM get_old_fashioned_versdir USING pi_objtype pi_objname
                               CHANGING po_no_entry.
DATA: vrsd_entry LIKE vrsd.
DATA: object_not_found LIKE bool.
PERFORM get_vrsd_entry_remote
          USING pi_objtype pi_objname null_versno
          CHANGING buffer0 po_no_entry.
IF po_no_entry = false.
    CALL FUNCTION 'GET_VERSION_LIST_46'
      EXPORTING
        destination           = dir_destination
        objname               = pi_objname
        objtype               = pi_objtype
      TABLES
        version_list          = vrs_dir_vrs
      EXCEPTIONS
        system_failure        = 1
        communication_failure = 2.
    CASE sy-subrc.
      WHEN 1.
       'Fehler im Zielsytem'.
       MESSAGE W123.
       LEAVE.
      WHEN 2.
       'Keine Verbindung zum Zielsystem'.
       MESSAGE W124.
       LEAVE.
    ENDCASE.
    SORT vrs_dir_vrs DESCENDING BY versno.
    LOOP AT vrs_dir_vrs.
      logvers_dir-versno = vrs_dir_vrs-versno.
      APPEND logvers_dir.
    ENDLOOP.
    READ TABLE vrs_dir_vrs INDEX 1.
    IF vrs_dir_vrs-versmode = impt_mode.
     Es gibt einen offenen Import, setze Flag zurück:
      vrs_dir_vrs-versmode = corr_mode.
    ENDIF.
    vrs_dir_vrs-versno = 0.
    MODIFY vrs_dir_vrs INDEX 1.
ENDIF.
vrsd_entry = buffer0.
PERFORM add_active_version_remote
          CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
    po_no_entry = false.
ENDIF.
Möglicherweise gibt es eine überarbeitete Version.
PERFORM add_modif_version_remote
          CHANGING vrsd_entry object_not_found.
IF object_not_found = false.
    po_no_entry = false.
ENDIF.
ENDFORM.                    "get_old_fashioned_versdir
      FORM ADD_ACTIVE_VERSION_REMOTE                                *
--> VRSD_INFO                                                     *
--> PO_NOT_FOUND                                                  *
FORM add_active_version_remote CHANGING vrsd_info STRUCTURE vrsd
                                        po_not_found.
DATA: object_not_found LIKE vrsd-versmode.
DATA: nplus1           LIKE vrsd-versno.
DATA: retcode          LIKE bool.
CALL FUNCTION 'FIND_OBJECT_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      object_not_found      = object_not_found
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
       'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
       'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.                             " SY-SUBRC.
IF object_not_found = space.
    po_not_found = false.
ELSE.
    po_not_found = true.
ENDIF.
CLEAR: vrsd_info-korrnum, vrsd_info-author,
         vrsd_info-datum,   vrsd_info-zeit.
IF po_not_found = false.
    IF vrsd_info-versmode = impt_mode.
    Es gibt einen offenen Import, und einen Satz n+1 der
    uns verschwiegen wurde. Er beschreibt die aktive Version
      nplus1 = vrsd_info-lastversno + 1.
      PERFORM get_vrsd_entry_remote
              USING vrsd_info-objtype vrsd_info-objname nplus1
              CHANGING vrsd_info retcode.
    ELSE.
      PERFORM get_korrinfo_remote CHANGING vrsd_info.
    ENDIF.
    MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
    vrs_dir_vrs-versno    = null_versno.
    logvers_dir-versno    = acti_versno.
    INSERT vrs_dir_vrs INDEX 1.
    INSERT logvers_dir INDEX 1.
ENDIF.
ENDFORM.                    "add_active_version_remote
      FORM ADD_MODIF_VERSION_REMOTE                                 *
FORM add_modif_version_remote CHANGING vrsd_info STRUCTURE vrsd
                                       po_not_found.
DATA: mod_dd_exists LIKE vrsd-versmode.
CALL FUNCTION 'TEST_MOD_DD_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      mod_dd_exists         = mod_dd_exists
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
      'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
IF mod_dd_exists <> space.
    po_not_found = false.
    PERFORM get_korrinfo_remote CHANGING vrsd_info.
    MOVE-CORRESPONDING vrsd_info TO vrs_dir_vrs.
    vrs_dir_vrs-versno    = modi_versno.
    logvers_dir-versno    = modi_versno.
    INSERT vrs_dir_vrs INDEX 1.
    INSERT logvers_dir INDEX 1.
ELSE.
    po_not_found = true.
ENDIF.
ENDFORM.                    "add_modif_version_remote
      FORM GET_KORRINFO_REMOTE                                      *
FORM get_korrinfo_remote CHANGING vrsd_info STRUCTURE vrsd.
CALL FUNCTION 'GET_KORRNUM_AUTHOR_DATUM_40'
    EXPORTING
      destination           = dir_destination
      objname               = vrsd_info-objname
      objtype               = vrsd_info-objtype
    IMPORTING
      author                = vrsd_info-author
      datum                 = vrsd_info-datum
      korrnum               = vrsd_info-korrnum
      zeit                  = vrsd_info-zeit
    EXCEPTIONS
      system_failure        = 1
      communication_failure = 2.
CASE sy-subrc.
    WHEN 1.
      'Fehler im Zielsytem'.
     MESSAGE W123.
     LEAVE.
    WHEN 2.
      'Keine Verbindung zum Zielsystem'.
     MESSAGE W124.
     LEAVE.
ENDCASE.
IF vrsd_info-korrnum <> space.
    Korrektur ist offen, Zeitstempel korrigieren:
    vrsd_info-datum = sy-datum.
    vrsd_info-zeit = sy-uzeit.
ENDIF.
ENDFORM.                    "get_korrinfo_remote

Missing AQ and JMS Transport protocols

Hi,
It seems that after a Purge the AQ and JMS transport protocols have disappeared from the user interface. I recall something similar happened with the SFTP protocol a few patches ago. That could be solved by running $ORACLE_HOME/jdk/bin/java oracle.tip.seed.SFTPSeedDriver. Can something similar be done for the AQ and JMS transport protocols?
Thanks

Thanks for the reply.
the patch number is 7556011.
It is possible that it is as you say and something went wrong during patching. I assumed it was deleted because of the Purge since the AQ and JMS were missing similar to the SFTP case described earlier. When comparing the transport protocols with another installation (with the same patch level and that has not had any purges done) only these two protocols were missing. Worth noting is that the SFTP and TCP transport protocols are still visible in the GUI.

Check STMS Customizing Transport request for equal entries

Hi
We use the BADI "CTS_REQUEST_CHECK" for some precheck before create and / or release customizing TA to inform the user that someone else is using the same customizing object in transport xy.
Following scenario:
Transport request 4711 is created 20.01.10 contains object "A" and released for testing in integrationsystem
Transport request 4715 is created 10.04.10 contains object "A" and released for testing in integrationsystem
When importing transport 4715 into productivsystem with STMS single transport there should be an error message that it's not allowed until transport 4711 is in productivsystem.
Which BADI or Userexit could help me?
Thanks in advance
Michael

Hi Diego,
Thanks for your reply.
I tranported the 'Default values for tax codes', are we suppose to do any pre/post activity to tranport this request.
@Ravi: As you suggested i compared the transported before and after transport in our Dev and QA server. there is no mismatch.
Many Thanks,
Shanthosh

Transport having Transformations & DTPS errored out with RDDEXECL code 12

Hi Friends,
I am importing a Transport request containing Transfromations, DTPs from Dev to QC system and it is erroring out with Code 12 and error is as follows
Program terminated (job: RDDEXECL, no.: 19103500) See job log
When I looked at Job log i can see the folowing details
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server sht014a5 were synchronized
ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED_NO
Job cancelled
I looked at ST22 and I found the following details
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "IF_RSBK_TPL_OPTIONAL~SET_LOGSYS" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component.
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
I am working on SAP NW 2004 S BI 7.0 with support package level at SAPKW70018
Please let me know how to resolve this error.
Thanks
mv_d

Hi MV,
Please check below Notes:
Number: 943957
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=943957
Number: 992032
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=992032
Note: As you are re-importing the Transport Request, there may be a chance of the deletion of some of DTP's or Transformations in DEV system.
Please check whether all the DTP's and Transformations are present in the DEV system (and active also) by comparing with transport request.
Regards,
Ravi Kanth
Edited by: Ravi kanth on Apr 30, 2009 11:54 AM

Transports issue

Dear friends,
we have to extract the transports whcih are not in production but are transported to QA.
Now after the refresh, QA is copy of PRD. So we need to compare the transports from dev to prd and check the missing transports. This transports are nearly 1200 transports.
Is there any way we extract the list of transports which are not transported to PRD but transported to QA before refresh.
Thanks,
Kris

Hi,
just thinking if you got to /usr/sap/translog
Each transport will have a suffix.
In my system a system that has been transported to QA and PROD will have a log :
UDSI949699.UPS
UDSI949699.UQS
So if you can sort your logs out you should be able to tell, assuming you have all your logs that is..
Mark

Crm 7.0 webchannel ,define catalog type query

Hi all,
m facing a problem in webchannel (crm),if any of you can guide me in this regard, i would greatly appriciate it..the problem is :
While performing "define catalog type" ,under the "Folder Template" tab when m trying to assign my newly created AREA & ITEM m getting the message "no values selected, maintain entries" & when i click yes m getting a window "choose customizing project". There is a button stating "continue w/o specifying project", if i click on that its taking me to "Define template for forlder" under basic functions in spro crm.I have already maintained folder for area & item which are saved then why are they not showing when m pressing f4.
regards,
Nitin

I am assuming that your requirement is to create a new catalog type
Normally, the CRM system comes with few standard catalog types - such as, AUTO and MANU. These catalog types usually have the respective "Areas" and "Items" predefined. For example, the Catalog type MANU has MANU-AREA and MANU-ITEM. The message here is, the standard system does come with several values predefined for these configuration tasks.
Now, coming to your requirement, if you don't see any standard values in your configuration steps, then there is some issue you should look into.
In your case, since no standard values are available for the "For Areas" and "For Items" - which actually should be in CRMD_KW_TEMPL table, I think you have to check if everything has been done correctly as far as the upgrade transport or installation transport goes.
What is the version of CRM are you in? Though the following note is old, it is worth investigating.
[Note 751751 - Content Management: Error TK295 in Customizing|https://service.sap.com/sap/support/notes/751751]

Read statement

what is the exact use of read statement. How it is used in int.table & database table.

Hi
Reading Lines of Tables
To read a single line of any table, use the statement:
READ TABLE <itab> <key> <result>.
For the statement to be valid for any kind of table, you must specify the entry using the key and not the index. You specify the key in the <key> part of the statement. The <result> part can specify a further processing option for the line that is retrieved. If the system finds an entry, it sets SY-SUBRC to zero, if not, it takes the value 4, as long as it is not influenced by one of the possible additions. If the internal table is an index table, SY-TABIX is set to the index of the line retrieved. If the table has a non-unique key and there are duplicate entries, the first entry is read. Specifying the Search Key The search key may be either the table key or another key.
Using the Table Key To use the table key of <itab> as a search key, enter <key> as follows:
READ TABLE <itab> FROM <wa> <result>.
or as follows
READ TABLE <itab> WITH TABLE KEY <k1> = <f1> ... <kn> = <fn> <result>.
In the first case, <wa> must be a work area compatible with the line type of <itab>. The values of the key fields are taken from the corresponding components of the work area. In the second case, you have to supply the values of each key field explicitly. If you do not know the name of one of the key fields until runtime, you can specify it as the content of a field <ni> using the form (<ni>) = <fi>. If the data types of <fi> are not compatible with the key fields, the system converts them. The system searches for the relevant lines as follows:
Standard tables
Linear search, where the runtime is in linear relation to the number of table entries.
Sorted tables
Binary search, where the runtime is in logarithmic relation to the number of table entries.
Hashed tables
The entry is found using the hash algorithm of the internal table. The runtime is
independent of the number of table entries.
Using a Different Search Key
To use a key other than the table key as a search key, enter <key> as follows:
READ TABLE <itab> WITH KEY = <f> <result>.
or as follows
READ TABLE <itab> WITH KEY <k1> = <f1> ... <kn> = <fn> <result>.
BC - ABAP Programming SAP AG
In the first case, the whole line of the internal table is used as the search key. The contents of the entire table line are compared with the contents of field <f>. If <f> is not compatible with the line type of the table, the value is converted into the line type. The search key allows you to find entries in internal tables that do not have a structured line type, that is, where the line is a single field or an internal table type. In the second case, the search key can consist of any of the table fields <k1>...<kn>. If you do not know the name of one of the components until runtime, you can specify it as the content of a field <ni> using the form (<ni>) = <fi>. If <ni> is empty when the statement is executed, the search field is ignored. If the data types of <fi> are not compatible with the components in the internal table, the system converts them. You can restrict the search to partial fields by pecifying offset and length.The search is linear for all table types. The runtime is in linear relation to the number of table lines. Specifying the Extra Processing Option
You can specify an option that specifies what the system does with the table entry that it finds. Using a Work Area You can write the table entry read from the table into a work area by specifying <result> as follows:
READ TABLE <itab> <key> INTO <wa> [COMPARING <f1> <f2> ...
|ALL FIELDS]
[TRANSPORTING <f1> <f2> ...
|ALL FIELDS
|NO FIELDS].
If you do not use the additions COMPARING or TRANSPORTING, the contents of the table line must be convertible into the data type of the work area <wa>. If you specify COMPARING or TRANSPORTING, the line type and work area must be compatible. You should always use a work area that is compatible with the line type of the relevant internal table. If you use the COMPARING addition, the specified table fields <fi> of the structured line type are compared with the corresponding fields of the work area before being transported. If you use
the ALL FIELDS option, the system compares all components. If the system finds an entry with the specified key <key> and if the contents of the compared fields are the same, SY-SUBRC is set to 0. If the contents of the compared fields are not the same, it returns the value 2. If the system cannot find an entry, SY-SUBRC is set to 4. If the system finds an entry, it copies it into the target work area regardless of the result of the comparison. If you use the TRANSPORTING addition, you can specify the table fields of the structured line type that you want to transport into the work area. If you specify ALL FIELDS without RANSPORTING, the contents of all of the fields are transported. If you specify NO FIELDS, no fields are transported. In the latter case, the READ statement only fills the system fields SYSUBRC and SY-TABIX. Specifying the work area <wa> with TRANSPORTING NO FIELDS is unnecessary, and should be omitted.
In both additions, you can specify a field <fi> dynamically as the contents of a field <ni> in the form (<ni>). If <ni> is empty when the statement is executed, it is ignored. You can restrict the search to partial fields by specifying offset and length.
Using a Field SymbolYou can assign the table entry read from the table to a field symbol by specifying <result> as
follows:
READ TABLE <itab> <key> ASSIGNING <FS>.
After the READ statement, the field symbol points to the table line. If the line type is structured, you should specify the same type for the field symbol when you declare it. This allows you to address the components of the field symbol. If you cannot specify the type statically, you must use further field symbols and the technique of assigning components of structures to address the components of the structure.For further information about assigning table lines to field symbols, refer to Access Using Field Symbols.
SORT ITAB.
READ TABLE ITAB WITH KEY VAR1 <= SYDATUM BINARY SEARCH.
OR
READ ITAB WITH KEY VAR1 <= SYDATUM
YOU CAN USE ANY ONE READ STATEMENT
1ST ONE IS BINARY SEARCH IT IS BETTER IN PERFORMANCE
YOU HAVE TO SORT THAT ITAB BEFORE THIS STATEMENT
2ND ONE IS NORMAL SEARCHIN TECH IT IS NOT GOOD IN THE PERFORMANCE POINT OF VIEW

Ability to sort by image similarity.

Ability to sort by actual image similarity. This is the only way I can think of to identify duplicates in the catalog. I know I have perhaps 5,000 dupplicate RAW images in my catalog and I can think of no other way to find them (so I can delete them and free up the space). This could also be very handy for picking similar subject matter for a client. This sounds like it would be very slow, but there is math for greatly speeding up the identification of similar images.

You've got my vote for this as a feature, but I guess a definition of 'similarity' would be needed to implement. One way would be to allow sorting by some user-defined combination of metadata fields, but I don't know if this is what you had in mind. Anyhow, if this did come to be, it'd be nice to also be able to filter and see only 'similar' images.
Short of a new feature, I've found that working with 'All Photographs', sorting by capture time, and visually scanning for duplicates works pretty well if the dups may have different names. Otherwise sorting by filename works. You can use metadata filters at the top to keep the number of images you review at one time reasonable. Obviously, the smaller your catalog, the more manageable this is.
There are a couple of plug-ins that may be helpful. The "Duplicate Finder" plug-in will let you select from some metadata options and then run through the entire catalog, putting identified duplicates in a Smart Collection for you to review. My personal experience with a previous version was that this took a very long time and failed to finish on a really large catalog (60k+).
If you've got a lot of files to compare, LR/Transporter can be useful. It lets you create a text file report on selected images containing whatever metadata fields you specifiy. I found it helpful in some cases to output the filenames, capture time, edit time, etc. If you are able to work with this data in Excel, Access, or some other database, you can whittle down your list of potential duplicates this way. You then use LR/Transporter to import a list of images you want to flag, and you can then filter on that flag.
Tedious no matter how you do it.
Paul Wasserman

Compare upgraded transports

Similar Messages

Maybe you are looking for