What to do when transport request reached to DEVK999999

Hi All
        What should i do to create workbench or customizing request after it reached to maximum value i.e
DEVK999999.how should i further create request.
Plz help me out.

Hi
>
pranav kumar wrote:
> Is there any sql command to change the transport reuest range in table E07l .i have heard abut that but i dont know exactly about that.
>
> plzz help me out
to change transport number you can follow below procedure:
This is possible via ABAP report RSWBO301. Its documentation is straightforward. Go to transaction sE38, enter RSWBO301, choose documentation display
Program Documentation
This report program searches for a free interval for numbering requests. If the search is successful, you can save the interval. The request numbers are then taken from this interval.
Requirements
For customers the number range interval includes the following areas:
900000-999999 (just numerals)
9A0000-9ZZZZZ for ASCII character set or
9AAAAA-9Z9999 for EBSDIC character set.
You only need to execute this program if you have come to the end of the number range interval, but there are still large gaps in the range that you want to use up.
Example
Why you might get into this situation:
The customer has the SAP system C11. The last number assigned is C11K900115. The customer now imports transport request C11K9ZZZZA from an external SAP system C11 into the customer system C11. The next request created in this system will have the number C11K9ZZZZB.
Procedure
Proceed as follows:
Execute this program in transaction SE38.
Enter the interval limit, for example 5000. You can change this limit at any time.
Choose Execute.
If you entered an interval limit of 5000, the report searches for a free interval with a size of 5000.
If the search was successful, you can save this interval. If not, repeat the search with a smaller interval.
Thanks
Sunny

Similar Messages

  • Issue when transport request of Text Control

    Dear Gurus,
    I have some problem when modified Text controls.
    Requirement
    My customer want to copy item text from Quotation which is use access sequence 9000 to item text in Sale Order
    What I do.
    1. I go to SPRO -> Sale and Distubution -> Basic Function -> Text Control -> Define Access Sequences For Deermining Texts -> Sales Document -> Item -> Textproceture -> Text ID's in procedure of Sale order Item
    2. I input Access squence 9000 to sepecific Text ID and ticked "Refer/Duplicate"
    3. I save and I get the Transport Request
    4. I create sale order reference Quotation and the result is system copy text.
    5. Then, I transport request to Simulation Server.
    6. I create sale order reference Quotation but this time system does not copy text
    I want to know why problem is occurs. if you have reference document about this issue please tell me.

    Hi,
    Run the program 'RSTXTRAN' using transaction SE38 and attach the Text object to your TR.
    Last time I faced the same problem.
    Everything gets transported except Text object.
    Hope it will be useful to u.
    Revert if not resolved.
    Regards
    Amit
    Edited by: Amit Gupta on May 14, 2009 7:31 AM

  • MEssage when Transport request is released

    Hello,
    I want to get a message, when a transport request is released. But this throws no Event (Object CTREQUEST ) .
    Is there any possibility ?
    Thanks and best regards
    Stefanie

    Hi Stefanie,
    Go to SE24 and open the class CL_EXITHANDLER, in the method get_instance, put a breakpoint on the statement
    CALL METHOD cl_exithandler=>get_class_name_by_interface
    Line 14 and release your request and see if the BADI CTS_EXPORT_FEEDBACK is called.
    I cannot check this in my system as i don't have any request to release.
    Regards
    Rajvansh

  • What to do when you have reached you're 5 out of 5 iTunes authorisations

    I have had to re-install a few times recently on my Desktop PC but have noticed that I have now reached my 4th out of 5 Computer Authorisations in iTunes.
    What happens when I reach the 5th one and is there a way of re-setting this counter?
    Thanks

    Hi crofty, Welcome to the Forum.
    What happens when I reach the 5th one and is there a way of re-setting this counter?
    Regarding for this matter, you could read this article:
    [About iTunes Store authorization and deauthorization|http://support.apple.com/kb/HT1420]
    Hope this could give you an idea.
    Regards,
    MCM

  • What happens when counter for transport requests is exhausted ?

    Hi,
    Just a simple question: Do you know what happens if the counter for transport requests reaches it's limit ?
    Actually our development system has created E30K999205 as a last request/task. What will happen after E30K999999 ?? This will happen in two months...
    Regards,
    Joan

    Hi,
    Look at the below note .
    SAP Note:  106911.
    Thanks.

  • Transport request prompt details

    Whenever there is a modification to existing reports or new reports being created, SAP prompts for a request number to be captured. Apart from capturing the request number, I want to capture other details like technical person name, functional person name, plant, transaction code, etc. as such details will be very useful in drafting the charts like how many modifications / new reports made per plant, how many modifications / new reports done by a technical person, etc.
    Is there any userexit that is called when transport request pop-up screen comes up ? Any other ideas ?
    Please clarify.
    Regards,
    Tom Jerry.

    For the transport details, please check the tables E070 and E071.
    Just pass the <Program name >in the field E071-OBJ_NAME and get all the transport order details.
    and also check the table TRDIR for all reports and pass the TRDIR-UNAME is username where you can get the Reports done by the person.
    TRDIR for all reports and pass the TRDIR-CNAME is username where you can get the Reports changed  by the person.
    TFDIR where all the function module are stored
    DD03l where all tables are stored.
    Prabhudas

  • XI Transport request

    What to create the transport request for objects developed in IR & ID for Dev to Q to Prod.....jena

    Hi,
    There are two ways to Transport XI objects-
    1) File Import/Export
    2) CMS--- now CTS+ is also available
    CMS is somewhat standard way to do. Becuase you can track the objects. But for this you need to install the CMS separately.
    just go thru these quick links-
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/69a740aa053a13e10000000a155106/frameset.htm
    /people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
    Also check in service.sap.com- for how to guides-
    https://websmp201.sap-ag.de/nw-howtoguides
    CMS Transport
    CMS for SAP Exchange Infrastructure
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
    Configuration of CMS in Central NWDI & SLD to transport XI objects
    /people/praveen.mayalur/blog/2007/05/31/configuration-of-cms-in-central-nwdi-sld-to-transport-xi-objects
    How to Use CMS in XI 3.0.pdf
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
    CMS based transport in XI
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d8f7b2-0701-0010-b09a-cda4cca2c98e
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    Change and Transport Lists for CMS Transports
    How To…Transport XI Content Using CMS
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
    File Transport
    there is not much to do if you're using file transport IR, you just export (from the menu) and import the same way in the target IR
    ID you just have to specify transport targets (so names of your business systems will change)
    Configuring Groups and Transport Targets.
    http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
    also have a look at: Transporting XI Objects
    http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/content.htm
    if you're having one SLD
    if not then you should also copy sld
    so that all sld's data will be consistent
    Thanks
    Swarup
    Edited by: Swarup Sawant on Mar 30, 2008 6:25 AM

  • What checkbox "import again" when adding an transport request to import que

    Hello
    I wander what checkbox "import again" when adding an transport request to import queue means?
    Thank you in advance

    Hello Jan,
    Well you should have searched in help.sap.com before posting here for basic concepts. Anyways, import again means after successful import also you can reimport that particular request.. Please see the below link for other options as well.
    http://help.sap.com/saphelp_nw04/helpdata/en/5c/d21880fe3c11d2b461006094b9ea64/content.htm
    Thanks,
    Siva Kumar

  • Error in FM DDIF_NAMETAB_GET when deleting BI objects via transport request

    Dear all,
    when importing a transport request in which several types of BI objects are deleted (Infocubes, DSO's, transformations, routines, DTP's, query elements, infosets, process chains). The import terminates only when transporting from acceptance to production with return code 12 due to an uncaught exception:
    Transporting from development to acceptance did not raise this exception.
    The ST22 dump (see below) refers in the "contents of system fields" section to a DSO, and to post-import activities. The DSO and the associated tables could not be found (rsa1 & se16), since they are deleted as desired.
    Some of the relevant notes that I have found do refer to DSO related problems, but they all indicate to install SP19 which we already have installed (BW 7.0 Patch Level 23)
    Could you please assist in pointing out potential solutions based on the information from the ST22 Runtime Error below?
    Kind regards,
    PJ
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_RS_PROGRAM_ERROR
    Date and Time          08.02.2011 10:48:14
    Short text
        An exception occurred that was not caught.
    What happened?
        The exception 'CX_RS_PROGRAM_ERROR' was raised, but it was not caught anywhere
        along the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
        'CL_RSDD_DS====================CP' has to be
        terminated.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RS_PROGRAM_ERROR', was not caught
        and therefore caused a runtime error.
        The reason for the exception is:
        Error in BW: Error in DDIF_NAMETAB_GET
    How to correct the error
        If the error occurs in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "UNCAUGHT_EXCEPTION" "CX_RS_PROGRAM_ERROR"
        "CL_RSDD_DS====================CP" or "CL_RSDD_DS====================CM001"
        "APPEND_DS_TEC_FIELDS"
    System environment
        SAP-Release 700
        Application server... "dp1ci"
        Network address...... "<removed>"
        Operating system..... "HP-UX"
        Release.............. "B.11.23";
        Hardware type........ "ia64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 45
        Shortdump setting.... "full"
        Database server... "spisap02"
        Database type..... "ORACLE"
        Database name..... "DP1"
        Database user ID.. "SAPBIW"
        Terminal................. " "
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 14 2009 20:47:35"
        create on........ "HP-UX B.11.23 U ia64"
        Database version. "OCI_102 (10.2.0.1.0) "
        Patch level. 236
        Patch text.. " "
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
        SAP database version. 700
        Operating system..... "HP-UX B.11";
        Memory consumption
        Roll.... 5979936
        EM...... 0
        Heap.... 1459888
        Page.... 40960
        MM Used. 6988880
        MM Free. 415648
    User and Transaction
        Client.............. 000
        User................ "DDIC"
        Language key........ "E"
        Transaction......... " "
        Transactions ID..... "4D5111661004210BE10000000AFA2502"
        Program............. "CL_RSDD_DS====================CP"
        Screen.............. "SAPMSSY0 1000"
        Screen line......... 6
    Information on where terminated
        Termination occurred in the ABAP program "CL_RSDD_DS====================CP" -
         in "APPEND_DS_TEC_FIELDS".
        The main program was "RDDEXECU ".
        In the source code you have the termination point in line 61
        of the (Include) program "CL_RSDD_DS====================CM001".
        The program "CL_RSDD_DS====================CP" was started as a background job.
        Job Name....... "RDDEXECL"
        Job Initiator.. "DDIC"
        Job Number..... 10475900
    Source Code Extract
    Line  SourceCde
       31         RAISE EXCEPTION TYPE cx_rs_program_error
       32           EXPORTING
       33             text = 'Invalid DSO subtype'.                   "#EC NOTEXT
       34     ENDCASE.
       35
       36 *   get table name from DDIC
       37     CALL METHOD cl_rsd_odso=>get_tablnm
       38       EXPORTING
       39         i_odsobject = n_infoprov
       40         i_tabt      = l_tab
       41       IMPORTING
       42         e_tablnm    = l_tablnm
       43       EXCEPTIONS
       44         OTHERS      = 1.
       45
       46     IF sy-subrc <> 0.
       47       RAISE EXCEPTION TYPE cx_rs_program_error
       48         EXPORTING
       49           text = 'Error in CL_RSD_ODSO=>get_Tablnm'.        "#EC NOTEXT
       50     ENDIF.
       51
       52     CALL FUNCTION 'DDIF_NAMETAB_GET'
       53       EXPORTING
       54         tabname   = l_tablnm
       55       TABLES
       56         dfies_tab = l_t_comp
       57       EXCEPTIONS
       58         not_found = 1
       59         OTHERS    = 2.
       60     IF sy-subrc <> 0.
    >>>>>       RAISE EXCEPTION TYPE cx_rs_program_error
       62         EXPORTING
       63           text = 'Error in DDIF_NAMETAB_GET'.        "#EC NOTEXT
       64     ENDIF.
       65
       66
       67   ELSE.
       68 *   model table only needed for standard datastore objects, for
       69 *   write optimized DSOs target table is a changelog that is fully described by
       70 *   dta_pro (infoobjects)
       71     CHECK n_s_dta-odsotype = rsdod_c_type-standard.
       72
       73 *   get model table fields to add
       74     CALL METHOD cl_rsd_odso=>get_mod_tab
       75       IMPORTING
       76         e_mod_fld_ur = l_t_comp.
       77   ENDIF.
       78
       79 * according to T.B. ( 13.04.2007) the correct position is
       80 * not needed in the D version
    Contents of system fields
    Name     Val.
    SY-SUBRC 0
    SY-INDEX 0
    SY-TABIX 1
    SY-DBCNT 1
    SY-FDPOS 0
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE Execute Post-Import Methods and XPRAs for Transport Request
    SY-MSGTY E
    SY-MSGID DA
    SY-MSGNO 300
    SY-MSGV1 /BIC/AV_AMOFCB40
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20110208
    SY-UZEIT 104759
    SY-XPROG SAPLSYST
    SY-XFORM SYSTEM_HOOK_OPEN_DATASET

    Hi All
    We are also experiencing this same error when transporting deletions of multiple objects.
    Although the transport was cancelled in the destination system (production) it appears to have largely deleted all objects successfully except for DSOs.
    The DSOs still appear in the table RSDODSO (via SE11) but are not visible anywhere else.  When you try to view the DSO via RSDODS a warning appears saying "DataStore object to be deleted by transport -> delete only allowed".  If you try to delete them in this transaction the same ABAP runtime error as the transport appears.
    Any assistance would be greatly appreciated!
    Regards
    David

  • RFC error when trying to add transport request in queue in STMS..

    Hi,
    When I try to add a Transport request in queue in STMS transaction. I get RFC error saying some problem with tp program.
    But when I go and check the RFC connection through STMS in system overview -> Communication -> RFC setting, it says RFC connection Ok.
    What may be the issue  ? I really need some light on this..
    Regards,
    Rajesh.

    Hi Rajesh,
    At times when u try to add the TR to a queue there would be 2 reasons.
    1. If u have imported a TR into a system say QTY and it needs to be re imported, then we delete it fromthe STMS queue and add it again to re import it.
    2. If u have some transport from external sap system to be imported here we place the data and Co files in the trans directory and then add the TR to this queue.
    A TP failure happens if the data and co files does not exist in the TP directory or else, the TR target system is incorrectly mentioned.
    Hope it helps.
    Br,
    Sri
    Award points for helpful answers

  • Error when creating transport request in 000 clinet

    Hi All,
    I am getting the below message when creating a transport request manually in 000 client
    Requests can only be created from ChaRM!
    Message no. 38001
    How can I deactivate charm for short time and then activate it again?
    Please let me know your suggestion.
    Thanks
    Amair

    Hi Sanjai,
    Thanks for the quick response.
    But I think it will disable charm process for the entire landscape. What we need to do if we want to disablke for particular system like one development system?
    Thanks again
    Amair

  • Error Code 12 When Transport BW Request

    Dear All,
    I am getting a return code 12 when I execute a BW transport request from DEV to QA.  When the transport starts, it actually calls a job , RDDEXECL to run.  The job fails with the error :
    01.08.2006 14:05:05 Job started
    01.08.2006 14:05:05 Step 001 started (program RDDEXECL, variant , user ID DDIC)
    01.08.2006 14:05:05 All DB buffers of application server gdcs002q were synchronized
    01.08.2006 14:14:57 STDO: Log  could not be written on output device T
    01.08.2006 14:22:14 Communication Structure /BIC/CS8ZEOPRO02 activated
    01.08.2006 14:22:19 Transfer Rule(s) 8ZEOPRO02_AA activated
    01.08.2006 14:22:23 Communication Structure /BIC/CS8ZEOPRO02 activated
    01.08.2006 14:22:25 ABAP/4 processor: MESSAGE_TYPE_X
    01.08.2006 14:22:25 Job cancelled
    A ABAP dump was created due to the job failure.
    Runtime Error          MESSAGE_TYPE_X
    Date and Time          01.08.2006 16:56:51
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Serious internal error:
    Technical information about the message:
    Diagnosis
    A serious internal error occurred. It could not be corrected.
    Procedure
    The following information is available on this error:
    1.
    2.
    3.
    4.   OSS note
    Check the OSS for corresponding notes and create a new problem
    message if necessary.
    Message classe...... "RSAR"
    Number.............. 001
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPLRSAC" or "LRSACU75"
    "RSAR_TRANSTRUCTURE_ACTIVATE"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "gdcs002q"
    Network address.......... "192.168.188.71"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x AMD64 Level"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 29
    Short dump setting....... "full"
    Database server.......... "GDCS002Q"
    Database type............ "MSSQL"
    Database name............ "BQ1"
    Database owner........... "bq1"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "May 21 2006 22:47:47"
    Created in............... "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version......... "SQL_Server_8.00 "
    Patch level.............. "129"
    Patch text............... " "
    Supported environment....
    Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory usage.............
    Roll..................... 16192
    EM....................... 146644960
    Heap..................... 0
    Page..................... 2547712
    MM Used.................. 82234648
    MM Free.................. 51831952
    SAP Release.............. "640"
    User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLRSAC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSAC" in
    "RSAR_TRANSTRUCTURE_ACTIVATE".
    The main program was "RDDEXECU ".
    The termination occurred in line 536 of the source code of the (Include)
    program "LRSACU75"
    of the source code of program "LRSACU75" (when calling the editor 5360).
    The program "SAPLRSAC" was started as a background job.
    Job name........ "RDDEXECL"
    Job initiator... "DDIC"
    Job number...... 16421301
    Source Code Extract
    Line
    SourceCde
    506
    IF g_subrc NE 0.
    507
    MESSAGE x001.
    508
    ENDIF.
    509
          Check new version neccessary
    510
    l_curr_version = c_s_is_admin-odsversion.
    511
    512
    IF l_new_version EQ rs_c_true.
    513
    IF i_without_versioning EQ rs_c_true.
    514
    MESSAGE e023 WITH c_s_is_admin-odsname_tech
    515
    c_s_is_admin-isource
    516
    RAISING no_psa_version_allowed.
    517
            ELSEIF i_without_versioning EQ 'C' AND
    518
                   i_without_transport  EQ rs_c_true.
    519
    *--         special handling for migration.
    520
    *-          current system is target system no transport request
    521
    *-          necessary if a new version is needed
    522
    ELSEIF i_without_versioning EQ 'C'        AND
    523
    i_without_transport  EQ rs_c_false.
    524
    RAISE inconsistency.
    525
    ENDIF.                   .
    526
    527
    IF i_objtype = rsa_c_istype-data.
    528
              check type of InfoSource first
    529
    SELECT SINGLE issrctype FROM rsis
    530
    INTO l_isrctype
    531
    WHERE isource = c_s_is_admin-isource
    532
    AND objvers = rs_c_objvers-active.
    533
    IF sy-subrc <> 0 OR l_isrctype = rsarc_c_issrctype-ods.
    534
                if generated ODS InfoSource,
    535
                no PSA versioning possible
    >>>>>
    MESSAGE x001.
    537
    ENDIF.
    538
    ENDIF.
    539
    l_next_version = l_curr_version + 1.
    540
    c_s_is_admin-odsversion = l_next_version.
    541
    l_transtru_odsname+13(3) = l_next_version.
    542
            Don't use old progname but create new one
    543
    CLEAR l_progname_ods.
    544
    ELSE.
    545
    l_next_version = l_curr_version.
    546
    ENDIF.
    547
    548
    ENDIF.
    549
        set transtru_names for IDoc
    550
    c_s_is_admin-odsname       = i_transtru_name.
    551
    c_s_is_admin-odsname_tech  = l_transtru_odsname.
    552
    WHEN OTHERS.
    553
    ENDCASE.
    554
    555
    save Transfer rules as active version
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    10
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Execute Post-Import Methods and XPRAs for Transport Request
    SY-MSGTY
    X
    SY-MSGID
    RSAR
    SY-MSGNO
    001
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FUNCTION     SAPLRSAC                            LRSACU75                              536
    RSAR_TRANSTRUCTURE_ACTIVATE
    12 FORM         SAPLRSAC_TRANSPORT                  LRSAC_TRANSPORTF02                   1709
    ACTIVATE_ISTS
    11 FUNCTION     SAPLRSAC_TRANSPORT                  LRSAC_TRANSPORTU68                    124
    RSAR_CODS_INFOSOURCE_ACTIVATE
    10 FUNCTION     SAPLRSAC_TRANSPORT                  LRSAC_TRANSPORTU67                    134
    RSAR_EXPORT_METADATA_GEN
    9 METHOD       CL_RSD_ODSO===================CP    CL_RSD_ODSO===================CM00M    52
    CL_RSD_ODSO=>IF_RSO_TLOGO_MAINTAIN_INT~AFTER_ACTIVATION
    8 METHOD       CL_RSO_TLOGO_COLLECTION=======CP    CL_RSO_TLOGO_COLLECTION=======CM010   333
    CL_RSO_TLOGO_COLLECTION=>ACTIVATE_ONE_STEP
    7 METHOD       CL_RSO_TLOGO_COLLECTION=======CP    CL_RSO_TLOGO_COLLECTION=======CM009   216
    CL_RSO_TLOGO_COLLECTION=>ACTIVATE_INTERNAL
    6 METHOD       CL_RSO_TLOGO_COLLECTION=======CP    CL_RSO_TLOGO_COLLECTION=======CM004     6
    CL_RSO_TLOGO_COLLECTION=>ACTIVATE
    5 FUNCTION     SAPLRSDG_ODSO                       LRSDG_ODSOU02                          98
    RS_ODSO_AFTER_IMPORT
    4 FUNCTION     SAPLRSVERS                          LRSVERSU03                            127
    RS_AFTER_IMPORT
    3 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      138
    CALL_IMP_METHODS
    2 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPU02                       94
    TRINT_CALL_AFTER_IMP_METHOD
    1 EVENT        RDDEXECU                            RDDEXECU                              186
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FUNCTION
    Name  RSAR_TRANSTRUCTURE_ACTIVATE
    I_DM_SEVERITY
    2
    0
    0
    0
    I_LOGSYS
    BQ1CLNT200
    4534445333
    2113CE4200
    0000000000
    0000000000
    I_NO_PROG_GENERATE
    2
    0
    0
    0
    I_OBJECT
    8ZEOPRO02
    354455433222222222222222222222
    8A5F02F02000000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    I_OBJTYPE
    D
    4
    4
    0
    0
    I_SEGMENT_ID
    2
    0
    0
    0
    I_TRANSTRU_NAME
    8ZEOPRO02_AA
    354455433544222222222222222
    8A5F02F02F11000000000000000
    000000000000000000000000000
    000000000000000000000000000
    I_T_TSFIELD
    Table IT_1551158[17x632]
    FUNCTION=RSAR_TRANSTRUCTURE_ACTIVATEDATA=I_T_TSFIELD
    Table reference: 4904
    TABH+  0(20) = 88666064FE070000000000000000000000000000
    TABH+ 20(20) = 2813000036AB17001100000078020000FFFFFFFF
    TABH+ 40(16) = 046E01000038000010000000C9248400
    store        = 0x88666064FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 4904  (0x28130000)
    label        = 1551158 (0x36AB1700)
    fill         = 17    (0x11000000)
    leng         = 632   (0x78020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000285
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x1857B168FE070000
    pghook       = 0x80E67064FE070000
    idxPtr       = 0x70C90864FE070000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x20000000)
    lineAlloc    = 32    (0x20000000)
    store_id     = 957569 (0x819C0E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I_T_TSMAPPING
    Table IT_1551159[17x2372]
    FUNCTION=RSAR_TRANSTRUCTURE_ACTIVATEDATA=I_T_TSMAPPING
    Table reference: 4956
    TABH+  0(20) = B0932263FE070000000000000000000000000000
    TABH+ 20(20) = 5C13000037AB17001100000044090000FFFFFFFF
    TABH+ 40(16) = 046E01008036000004000000C9248400
    store        = 0xB0932263FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 4956  (0x5C130000)
    label        = 1551159 (0x37AB1700)
    fill         = 17    (0x11000000)
    leng         = 2372  (0x44090000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000277
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x70FB0564FE070000
    pghook       = 0xE0E77064FE070000
    idxPtr       = 0x60EB1E64FE070000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x20000000)
    lineAlloc    = 20    (0x14000000)
    store_id     = 957570 (0x829C0E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I_USE_PROPOSAL
    X
    5
    8
    0
    0
    I_WITHOUT_LOG
    X
    5
    8
    0
    0
    I_WITHOUT_TRANSPORT
    X
    5
    8
    0
    0
    I_WITHOUT_VERSIONING
    2
    0
    0
    0
    C_S_IS_ADMIN
    8ZEOPRO02_AA               M    T 8ZEOPRO02_AA                  000/BIC/CAAA8ZEOPRO02
    3544554335442222222222222224222252354455433544222222222222222222333244424444354455433222222222
    8A5F02F02F11000000000000000D0000408A5F02F02F11000000000000000000000F293F31118A5F02F02000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_S_IS_ADMIN-ISOURCE
    8ZEOPRO02
    354455433222222222222222222222
    8A5F02F02000000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    G_S_RSIS-COMSTRU
    8ZEOPRO02
    354455433222222222222222222222
    8A5F02F02000000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    RS_C_OBJVERS-ACTIVE
    A
    4
    1
    0
    0
    L_ISRCTYPE
    O
    4
    F
    0
    0
    SY-SUBRC
    0
    0000
    0000
    SYST-REPID
    SAPLRSAC
    5454554422222222222222222222222222222222
    310C231300000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    RSARC_C_ISSRCTYPE-ODS
    O
    4
    F
    0
    0
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSAC
    5454554422222222222222222222222222222222
    310C231300000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY-MSGID
    RSAR
    55452222222222222222
    23120000000000000000
    00000000000000000000
    00000000000000000000
    MAXCHARLEN
    000255
    333333
    000255
    000000
    000000
    SPACE
    2
    0
    0
    0
    SY-MSGNO
    001
    333
    001
    000
    000
    RS_C_OBJ_TABL
    TABL
    5444
    412C
    0000
    0000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000
    L_CURR_VERSION
    000
    333
    000
    000
    000
    L_NEXT_VERSION
    000
    333
    000
    000
    000
    DB6_MIN
    003800
    333333
    003800
    000000
    000000
    L_PROGNAME_ODS
    GP9HAHZJDTVMUODQUVHPSYC02JZ
    4534445445545445554555433452222222222222
    709818AA446D5F41568039302AA0000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    No.      12 Ty.          FORM
    Name  ACTIVATE_ISTS
    L_NO_PROG_GENERATE
    2
    0
    0
    0
    L_T_TR_PROT
    Table[initial]
    E_SUBRC
    0
    0000
    0000
    SYST-REPID
    SAPLRSAC_TRANSPORT
    5454554455544554552222222222222222222222
    310C2313F421E30F240000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    L_S_ISOSMAP-LOGSYS
    BQ1CLNT200
    4534445333
    2113CE4200
    0000000000
    0000000000
    L_S_ISOSMAP-OLTPSOURCE
    8ZEOPRO02
    354455433222222222222222222222
    8A5F02F02000000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    L_S_ISOSMAP-ISTYPE
    D
    4
    4
    0
    0
    P_SEGID
    2
    0
    0
    0
    L_TRANSTRU_NEW
    8ZEOPRO02_AA
    354455433544222222222222222
    8A5F02F02F11000000000000000
    000000000000000000000000000
    000000000000000000000000000
    L_T_TSFIELDSEL
    Table IT_1551115[17x632]
    FUNCTION-POOL=RSAC_TRANSPORTFORM=ACTIVATE_ISTSDATA=L_T_TSFIELDSEL
    Table reference: 4207
    TABH+  0(20) = 88666064FE070000000000000000000000000000
    TABH+ 20(20) = 6F1000000BAB17001100000078020000FFFFFFFF
    TABH+ 40(16) = 046E01000038000010000000C9248400
    store        = 0x88666064FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 4207  (0x6F100000)
    label        = 1551115 (0x0BAB1700)
    fill         = 17    (0x11000000)
    leng         = 632   (0x78020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000285
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x1857B168FE070000
    pghook       = 0x80E67064FE070000
    idxPtr       = 0x70C90864FE070000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x20000000)
    lineAlloc    = 32    (0x20000000)
    store_id     = 957569 (0x819C0E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_T_TSMAPPING
    Table IT_1551116[17x2372]
    FUNCTION-POOL=RSAC_TRANSPORTFORM=ACTIVATE_ISTSDATA=L_T_TSMAPPING
    Table reference: 3062
    TABH+  0(20) = B0932263FE070000000000000000000000000000
    TABH+ 20(20) = F60B00000CAB17001100000044090000FFFFFFFF
    TABH+ 40(16) = 046E01008036000004000000C9248400
    store        = 0xB0932263FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 3062  (0xF60B0000)
    label        = 1551116 (0x0CAB1700)
    fill         = 17    (0x11000000)
    leng         = 2372  (0x44090000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000277
    occu         = 4     (0x04000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x70FB0564FE070000
    pghook       = 0xE0E77064FE070000
    idxPtr       = 0x60EB1E64FE070000
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x20000000)
    lineAlloc    = 20    (0x14000000)
    store_id     = 957570 (0x829C0E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    P_SUGGEST_AND_SAVE
    X
    5
    8
    0
    0
    RS_C_TRUE
    X
    5
    8
    0
    0
    L_WITHOUT_TRANSPORT
    X
    5
    8
    0
    0
    L_S_ADMIN
    8ZEOPRO02_AA               M    T 8ZEOPRO02_AA                  000/BIC/CAAA8ZEOPRO02
    3544554335442222222222222224222252354455433544222222222222222222333244424444354455433222222222
    8A5F02F02F11000000000000000D0000408A5F02F02F11000000000000000000000F293F31118A5F02F02000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SY-REPID
    SAPLRSAC_TRANSPORT
    5454554455544554552222222222222222222222
    310C2313F421E30F240000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    No.      11 Ty.          FUNCTION
    Name  RSAR_CODS_INFOSOURCE_ACTIVATE
    I_DATCLS
    22222
    00000
    00000
    00000
    I_SIZCAT
    22
    00
    00
    00
    I_T_OSFIELDMAP
    Table IT_1547853[17x204]
    FUNCTION=RSAR_EXPORT_METADATA_GENDATA=L_T_OSFIELDMAP
    Table reference: 3042
    TABH+  0(20) = 88FF0A64FE070000A8FC4164FE07000000000000
    TABH+ 20(20) = E20B00004D9E170011000000CC000000FFFFFFFF
    TABH+ 40(16) = 04900300603B000010000000C1248400
    store        = 0x88FF0A64FE070000
    ext1         = 0xA8FC4164FE070000
    shmId        = 0     (0x00000000)
    id           = 3042  (0xE20B0000)
    label        = 1547853 (0x4D9E1700)
    fill         = 17    (0x11000000)
    leng         = 204   (0xCC000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000303
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x007EF563FE070000
    pghook       = 0xA0BD2565FE070000
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x30000000)
    lineAlloc    = 48    (0x30000000)
    store_id     = 956282 (0x7A970E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0xC8FFF263FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x904C8864FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    E_T_MESSAGES
    Table IT_1549098[6x1376]
    FUNCTION=RSAR_EXPORT_METADATA_GENDATA=L_T_MESSAGES
    Table reference: 4318
    TABH+  0(20) = 705E1064FE070000000000000000000000000000
    TABH+ 20(20) = DE1000002AA317000600000060050000FFFFFFFF
    TABH+ 40(16) = 04AD0000D010000008000000C1308000
    store        = 0x705E1064FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 4318  (0xDE100000)
    label        = 1549098 (0x2AA31700)
    fill         = 6     (0x06000000)
    leng         = 1376  (0x60050000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000076
    occu         = 8     (0x08000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x88731964FE070000
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8     (0x08000000)
    lineAlloc    = 8     (0x08000000)
    store_id     = 956709 (0x25990E00)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    E_T_TLOGO

    Hi Mike,
    We have had this problem. Please delete the change log table of the ODS in the QA or Prod system (whichever is the target for your transport request) and then reimport the transport request.
    <i>
    534
    if generated ODS InfoSource,
    | 535|* no PSA versioning possible |</i>
    Hope this helps...

  • Problem when creating a transport request

    Hello
    I copied productive BR3 to test BR1 system(it is a BW3.5 system). Test BR1 existed also before(only the main client was 003).
    Now main client is on both 001(I do not know if this matter). I replicated with transport controller and everything went fine.
    When I want to create a transport request I have problem "Extended transport contrl is not active . Cannot specify target client". when I wannt further explanation I get:
    "Extended transport control is not active: Cannot specify target client
    Msg.nr.TR067
    Diagnosis
    Extended transport control is not active. This means that you can only release transport requests for the following transport targets:
    Target group
    R/3 System without specifying a client
    Procedure
    Change the transport target of the request by removing the client (for example, "C11" instead of "C11.010").
    The simplest way of doing this is to use F4."
    When I use F4 for "Target" field I get "BR3.001" as only option. If I choose BR3.001 I get above message. If I use "BR3" I get "BR3 is not a consolidation target". For further explanation I get :
    "BR3 is not a consolidation target
    Msg.nr TK658
    Diagnosis
    Transport target BW3 is not configured as a consolidation target of this SAP System. If you do not stick to configured transport routes, you may cause inconsistencies between the SAP Systems in the system landscape.
    If you use extended transport control, you also need to specify a configured target client.
    If the configured consolidation target is a target group, you also need to specify the target group as the transport target, if the target group consists of a single target system, or a single target client.
    Procedure
    Choose a configured transport target, or change the transport route configuration in the Transport Management System.
    What to do?

    Hi Jan,
    Please check whether parameter CTC=1 has been set in Transport tool,If not set it.
    Also check whether your transport group is configured properly
    regards,
    Jai

  • The transport request is running all the time, what is the problem

    I have a transport request which can transport from DEV to QAS successfully ,but failed when the request transport to PRD, I found the request running for several hours.   I do not know what the problem?    how can I check this problem?
    need your help                            thanks

    Hi
    The background job Rddimpdp is not scheduled in the system for client 000...And you want to investigate what happend to the job..
    The background job details are kept in table TBTCO..So if you goto SE16 and try to choose the fields which are of your interest..as it(this table)  has lot of fields. And in this we have fields like last run time,scheduled by,last job change time etc.So with the above information i hope you will be able to get the information you want.
    And if everything is fine ..the backgrouns job alone can vanish someone manually might have done done something ..and that can be found out by above investigation on the table.
    Hope this info helps...
    Regards
    Vani

  • When is the entire function group added to the transport request

    When you modify a functionmodule in a function group, only the object of the functionmodule( LIMU FUNC) is added to the transport request.
    When you modify an include of the function group, the reportsource of that include (LIMU REPS) is added to the transport request.
    But under some circumstances the entire function group is added to the transport request (R3TR FUGR).
    Can somebody clarify under what circumstances the entire Function Group is added to the transport request?

    I was actually looking for the reason why I would find R3TR FUGR objects in requests for existing function groups.
    What I found out is that R3TR FUGR is added to the request when :
    - the function group is created
    - a function is renamed
    - the function group is deleted
    - you choose : Write Transport Entry, in the context menu of the Function group.
    The <b>actual problem </b> was that in our upgraded system (<b>ERP2005</b>) we had a transport containing the function group (R3TR FUGR) and <b>we thought</b> none of these actions had been taken.  After talking to the developer in question, I found out he did rename a function module, so I have my solution.
    But thanks everybody for the insight.
    Message was edited by: Dries Horions

Maybe you are looking for