Types of Transport Requests

Can some one elaboratley explain me what are the different types of transport requests and the significance of their statuses.
Thanks in advance

Changes to cross-client Customizing objects and to Repository objects are recorded in Workbench requests
In workbench request .... it can be programs(repository objects) and cross client data (ie not specific to one client).
Changes to client-specific Customizing objects are recorded in Customizing requests.
Customer customized data designed for a specific client is transported to another client using customizing request. Most of the cases these requests are something like changing values in tables (that too client specific).
Once the Transport request is created it will be "Modified" Status.
Before a request can be transported it should be "Released".
Once the request is released no other changes pertaining to the object saved in the request can be saved to the same request. you have to create a new request for that.
After transporting to the required system, you can check the log of the transport to see if this was transported without errors.
Hope this helps you.

Similar Messages

HOW MANY TYPES OF transportable requests?

HOW MANY TYPES OF transportable requests?

Hi,
In R/3 Release 4.0, SAP has introduced the Change and Transport System (CTS), comprising the following tools:
1. Change and Transport Organizers(CTO)
2. Transport management system(TMS)
The Change and Transport Organizer (CTO) provides functions for organizing software development projects. It is designed to support projects of all sizes, whether they are carried out centrally or in a distributed environment.
The Transport Management System (TMS) organizes, monitors, and performs transports for allR/3 Systems within a system landscape. In addition, TMS is used to configure and manage the setting up of R/3 Systems and transport routes within a system landscape.
The Transport Management System (Transaction STMS) enables you to:
1. Define an R/3 System's role within a system landscape or transport domain
2. Configure the transport routes using either a graphical editor or hierarchical editor
3. Configure the transport tool transport control program tp.
4. Display the import queues of all R/3 Systems in the transport domain
5.Decide whether the quality assurance testing was successful in the QA System
6.Start the import of change requests in an import queue
The transports request can be of two types :
1. Customizing
2. Workbench
Customizing adapts the R/3 software to meet a company's individual business requirements by setting up the business transactions the company requires in R/3. Most Customizing is client-specific and affects only a particular client.
Workbench - Development changes are saved to Workbench change requests. Workbench change requests concern changes to R/3 Repository objects, such as ABAP programs, screens, data dictionary objects and global documentation.
To access the Workbench Organizer, use Transaction SE09
For more details go through the following link :
http://help.sap.com/erp2005_ehp_03/helpdata/EN/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Thanks,
Nitesh Jain

Wat r d types of transport requests

wat r d types of transport requests in development class

Hi,
Change Requests
Change requests are managed by the Transport Organizer. Changes to Repository and Customizing objects are recorded in change requests.
So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Request Types and Task Types
When you transport an object in a request, the objects transport attributes must match the transport attributes of the request (local or transportable).
Different object types have different transport attributes:
Repository objects and cross-client Customizing objects
Each Repository object has an object directory entry. This object directory entry contains the package to which the object is assigned. In turn, the package is assigned to a transport layer.
If a consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a transportable change request.
If no consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a local change request.
If the change request is transportable, the target of the request must be the same as the consolidation target of the object.
If the current system is the original system of the object, the object will be assigned to a task of the type correction.
If the current system is not the original system of the object, the object will be assigned to a task of the type repair.
Client-specific Customizing objects
Client-specific Customizing objects are recorded in tasks that belong to Customizing requests.
If a consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a transportable Customizing request.
The system uses the consolidation route of the standard transport layer to determine the transport target of the Customizing request. However, you can change this target.
If no consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a Customizing request without transport target.
SAP Help Link...
http://help.sap.com/saphelp_nw2004s/helpdata/en/09/88f330db9911d2b41a00609419f767/frameset.htm
Thanks and Regards,
Bharat Kumar Reddy.V

Object type in transport request

Hi all,
I created 2 diffrent structure(not table type) in DDIC, but in the transport request, one is included as table definition and the other as table. I have very confused with the 2 concept, anyone can answer my question, thank you.

It is input help(F4 help) or search help .The user can display the list of all possible input values for a screen field with this help.
for detailed information refer:-
http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee2b446011d189700000e8322d00/content.htm
regards
Gokila

Object type and Transport request for Category group.

Dear All,
I have configured category group for objective setting and appraisal (PD module) in development serverwhich is to be transported to quality. Can any body let me know how to generate the tranport request for that?
What is the object type for Category group and category?
Regards,
Jyoti

Thanks Dilek,
In objectice setting the top most hierarchy for appraisal catalog is category group followed by category and then template (VA) .
My query is related to category group. For category and template system has standatd upload/download utility for transport, but for category there is no as such option therfore in such a scenario how to transport category group.
Also I want to know the object type for criteria group and criteria.
Regards,
Jyoti.

About transport requests

how many types of transport requests are there,is it possible to customise the request,plz send me the answer..

Hi
You mainly have 2 types of requests:-
1. Workbench Request.
2. Customizing Request.
Depending on the type of work these requests will be allocated, for example if you create an object in your abap development workbench(Se80), then it gets stored under workbench, if you save any customizing Changes(SPRO), those requests will be stored in customizing requests.
Change Requests
Change requests are managed by the Transport Organizer. Changes to Repository and Customizing objects are recorded in change requests.
So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Request Types and Task Types
When you transport an object in a request, the objects transport attributes must match the transport attributes of the request (local or transportable).
Different object types have different transport attributes:
Repository objects and cross-client Customizing objects
Each Repository object has an object directory entry. This object directory entry contains the package to which the object is assigned. In turn, the package is assigned to a transport layer.
If a consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a transportable change request.
If no consolidation route leading from the current system is defined in the TMS for this transport layer, then the object is recorded in a task belonging to a local change request.
If the change request is transportable, the target of the request must be the same as the consolidation target of the object.
If the current system is the original system of the object, the object will be assigned to a task of the type correction.
If the current system is not the original system of the object, the object will be assigned to a task of the type repair.
Client-specific Customizing objects
Client-specific Customizing objects are recorded in tasks that belong to Customizing requests.
If a consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a transportable Customizing request.
The system uses the consolidation route of the standard transport layer to determine the transport target of the Customizing request. However, you can change this target.
If no consolidation route leading from the current system is defined in the TMS for the standard transport layer of the system or the current client, then the object is recorded in a task belonging to a Customizing request without transport target.
SAP Help Link...
http://help.sap.com/saphelp_nw2004s/helpdata/en/09/88f330db9911d2b41a00609419f767/frameset.htm

Transport Request - QA Server

Hi,
I couldnt understand why Log files are not created for a Request in QA - Quality server.
In SE09 there are 4 types of Request Types exists - how to know which one to choose while creating a new Request.
I appreciate ur time.
Regards
Krithika

> Hi Sanjay,
> Thanx
> 1)In Dev - Server i can goto SE09 and be able to
> o view the Logs by choosing on the Request no and
> clicking the Transport Logs button , but in QAS it is
> not possible to view Logs for any Request numbers.
<b> see my other response</b>
> 2) say for ex i want to create a transport request
> t - for transporting Variants / Table contents
> ......
> Which request type i should choose - customising /
> workbench/..., will it vary according to the
> transporting object?
Typically you will not go to SE09 to create a request unless you know exactly what you are doing. When you change any object, system will recognize whether it is a transportable object and if so, it will prompt you to create or choose an existing transport request number. System will also know what type of transport request it needs to create. But just for your understanding, you will create a customizing request if your changes are related to tables that are customizing tables(it is an attribute of the table). You will create a workbench request for all those objects that you work on using the workbench tools(including programs, tables, screens, status etc)
Srinivas

Writing objects to a transport request

Hi all,
I generate structures and table types in an ABAP Program and I want to record these objects to a transport request. I use the function modules 'TR_OBJECTS_CHECK' and 'TR_OBJECTS_INSERT' to write the objects to a transport request, but in this case, for each object the dialog for entering the package name and transport request is shown. I want that all objects are saved in the same package and transport requests. Is there another function module by which I can record all generated objects in a transport request after the request and package number is asked only once?
Regards,
Sükrü

Hi Suekrue,
I think 'TR_APPEND_TO_COMM' is the one. We did something similar. First choose/Create the Request, then append objects:
*&      Form TR_REQUEST_CHOICE
FORM tr_request_choice CHANGING pv_trkorr TYPE trkorr.
TYPE-POOLS:
    trwbo. "complex types for transport request display
DATA:
    ls_request                            TYPE trwbo_request_header.
CALL FUNCTION 'TR_REQUEST_CHOICE'
    EXPORTING
*   IV_SUPPRESS_DIALOG                    = ' '
*   IV_REQUEST_TYPES                      =
*   IV_CLI_DEP                            = ' '
*   IV_REQUEST                            = ' '
*   IT_E071                               =
*   IT_E071K                              =
*   IV_LOCK_OBJECTS                       = ' '
      iv_title                            = 'Auftrag auswählen, Aufgabe wird gefunden'
*   IV_START_COLUMN                       = 3
*   IV_START_ROW                          = 7
*   IV_WITH_ERROR_LOG                     = 'X'
*   IV_NO_OWNER_CHECK                     = ' '
    IMPORTING
      es_request                          = ls_request
    EXCEPTIONS
      invalid_request                     = 1
      invalid_request_type                = 2
      user_not_owner                      = 3
      no_objects_appended                 = 4
      enqueue_error                       = 5
      cancelled_by_user                   = 6
      recursive_call                      = 7
      OTHERS                              = 8
IF sy-subrc                             = 0.
    SELECT trkorr
      INTO pv_trkorr UP TO 1 ROWS
      FROM e070
      WHERE trfunction = 'S'
        AND trstatus = 'D'
        AND as4user = sy-uname
        AND strkorr = ls_request-trkorr.
      EXIT.
    ENDSELECT."rkorr into pv_trkorr
ENDIF.
ENDFORM.                    " TR_REQUEST_CHOICE
*&      Form TR_APPEND_TO_COMM
FORM tr_append_to_comm
CHANGING ps_alv                         TYPE LINE OF ty_t_alv.
DATA:
    ls_e071                               TYPE e071,
    lv.
ls_e071-pgmid                           = 'LIMU'.
ls_e071-object                          = 'FUNC'.
ls_e071-obj_name                        = ps_alv-funcname.
CALL FUNCTION 'TR_APPEND_TO_COMM'
    EXPORTING
      pi_korrnum                          = p_trkorr
      wi_e071                             = ls_e071
      wi_simulation                       = p_test
*   WI_SUPPRESS_KEY_CHECK                 = ' '
* TABLES
*   WT_E071K                              =
    EXCEPTIONS
      no_authorization                    = 1
      no_systemname                       = 2
      no_systemtype                       = 3
      tr_check_keysyntax_error            = 4
      tr_check_obj_error                  = 5
      tr_enqueue_failed                   = 6
      tr_ill_korrnum                      = 7
      tr_key_without_header               = 8
      tr_lockmod_failed                   = 9
      tr_lock_enqueue_failed              = 10
      tr_modif_only_in_modif_order        = 11
      tr_not_owner                        = 12
      tr_no_append_of_corr_entry          = 13
      tr_no_append_of_c_member            = 14
      tr_no_shared_repairs                = 15
      tr_order_not_exist                  = 16
      tr_order_released                   = 17
      tr_order_update_error               = 18
      tr_repair_only_in_repair_order      = 19
      tr_wrong_order_type                 = 20
      wrong_client                        = 21
      OTHERS                              = 22
IF sy-subrc                             <> 0.
    MESSAGE ID sy-msgid                   TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
            INTO ps_alv-tr_message.
ENDIF.
ENDFORM.                    " TR_APPEND_TO_COMM
Pleas adapt to your needs.
Regards,
Clemens

Transport Request for Analysis Authorization

Hello Everyone,
When a trasport request is created for any BI analysis authorization ( including the Z*), the type of trasport request created
is workbench request. What is the reason behind this because when any Customised Role / Profile is included in transport request this will be customised request unlike analysis authorization.
Thanks in advance.....

Hi Rashmi,
The difference is In BI, the AA authorizations are independent. Any objects that are independent of the client will be captured in the workbench type of transport request, when they are required in the other client. Hence you can see the Workbech type request for transporting changed Repository objects and changed system settings from cross-client tables. However, customizing requests involve changes recorded to client-specific Customizing objects .
The Analysis authorizations are always captured in a Workbench type of transport request by default due to the above design.
You can still transport both the PFCG role, and AA in a single transport request, you can do the same by following the steps mentioned in the below Wiki:
https://wiki.sdn.sap.com/wiki/display/BI/HowtotranportroleandAAtogetherinBI
Regards,
Raghu

Transport request coming at the time of creating doc type

Dear all;
Here is a serious problem ,I am currently working in development server ,I was trying to create a new purchase order document type from Standard PO document type .after copid the NB i have done the required change ,but at the time of saving no transport request is cominmg it is direcly saving by the system.I have checked in IDES there it is coming fine.Whatmay be the problem?It is serious problem ,because I canot check in sand box due to I am unable to **** it to Sandbox .Please suggest.
Thanking you;
Joydeep Mukherjee

Hi,
Use T.code:SCC4, check whether development client setting done for not generating transport request!
Here,select your development client and double click; system will take to new screen
Now check u201Cchanges and transport for client specificsu201D Tab and select u201Cautomatic recording of changesu201D and save.
Better consult your Basis Consultant for above.
Regardsm
Biju K

Create transport request based on SDMI transaction type

Hello,
a customer of mine intends to use transaction type SDMI in a kind of unusual way. He only creates SDMIs without creating projects, cycles or change requests in ChaRM. He uses a customized copy of the normal correction to track his changes and now needs to activate the functionality to create transport requests as an auditor requirement.
As I'm not proficient in ChaRM, I would like to know if that is at all possible.
Assuming it is possible, what would be the preferences to use action "Create Transport Request" regarding IBase etc.?
Assuming it is not possible, what would be necessary as a minimum to establish the link to the respective system in which the transport request should be created to get that action working, a maintenance cycle? How is the maintenance cycle linked to the ticket?
That are a lot of questions, and it would be highly appreciated if somebody could lighten up the fog there for me.
Thank you in advance!
Kind regards,
Emanuel

Hi,
1) Do I need to perform any steps in the task list before ChaRM can be used?
No once task list is in active state and sdmn is created for ur project u can start using charms
2) How is the maintenance cycle ticket (SDMN) linked to the change requests? Is this linkage done in the SDCR ticket via the maintenance project in the "Customer fields", where solution, maintenance project etc. can be assigned? Or is this implicitly done by the chosen IBase?
Yes everything is dependent on IBASE and logical component.
Check this links
https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
Check SMP/SDN
https://websmp208.sap-ag.de/changecontrol
Resources on CTS+ [original link is broken]
Hope it solves ur queries
Regards
Prakhar

Regarding transport request type

Hi
In t.cde SE-09 there 4 types of requet types explaine me about last two types .i.e
thansport of copies and relocation
Thanks &Regards
Ravi

Hi,
hi,
Change requests:- Changes to Repository and Customizing objects are recorded in change requests
Have a look at this
[http://help.sap.com/saphelp_erp2005/helpdata/en/4b/b155e40c3e11d3959a00a0c930dcc1/frameset.htm]
Transporting Customizing Settings
All system setting changes are put in project-specific change requests. You can transport the system settings into other SAP Systems with the change requests. The change requests are managed in the Transport Organizer.
There are two types of Customizing change requests:
Customizing request
Customizing requests contain changes to client-dependent tables.
Workbench request
Workbench requests contain changes to client-independent tables.
You can monitor the change requests by project in the project management. The Transport requests tab contains the following functions for the current client:
Activate CTS functionality
As prerequisite for creating change requests. When the CTS functionality is active, the pushbutton label changes to Display CTS project data. When the CTS project is finished, the pushbutton label changes to Reactivate CTS functionality.
Assigned CTS requests
Go to Transport Organizer request overview, where you can create requests for a project.
CTS project object list
The project object list is unchanged. When the customizing project is finished, the complete object list can be exported.
CTS project status switch
Sets the project status switch.
End CTS project
End your customizing project. You can reactivate it later.
See transport control by project for further information about the Change and Transport System (CTS) for customizing projects.
[http://help.sap.com/saphelp_erp2005/helpdata/en/09/88f330db9911d2b41a00609419f767/frameset.htm]
HTH,
Regards,
Dhruv Shah

Error while assigning objects to Transport Request

Hi All,
while assigning a Transfromation to a Treq i am getting an error saying
Object '7KU37C7IG3T7AQ5NHSLEZVC91' (ROUT) of type 'Routine' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '7KU37C7IG3T7AQ5NHSLEZVC91' (in transport request ROUT) of type 'Routine' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing.
Kindly advice how to rectify this error

Hi,
You see the which infoobejct contains that routine and first collect that infoobejct and transport it then transport Transfromation. I hope you are missing some Routines while collecting the Transformations into request.
See OSS Notes:
Note 613581 - Transfer structure does not exist in version 'D'
Note 508921 - P11:Content transfer:RSO 252 or RSO 296:InfoObject
Note 1157873 - BI7.0(SP18) Message RSO 252 using transport connection
Thanks
Reddy

Error while Releasing a transport request - DSO 0SD_O03: Active version

Hi all,
I am getting below error when I am trying to release a transport request.
Object ODSO 0SD_O03: Active version differs from modified version.
I activated DSO again,but I was not successful to correct the error.Please help me correcting this error.
Regards,
Bob

check
match and copy while installing the business content
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.With the most important object types, the active version and the SAP delivery version can be matched.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually.
A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.
When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Installindicator separately.
The active version is overwritten with the delivery version if
 the match indicator is not set and
 the install indicator is set.
check following thread
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
Thanks and regards
Kiran

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

Types of Transport Requests

Similar Messages

Maybe you are looking for