Enforcing free text in Transport request

Hello Experts,
I would like to inquire if there is a possible way to restrict or control the Short description of transport request? We have a naming convention but users are not adharing to standard standard name convension. Standard naming convention is a necessity so that we can identify quickly the ones that needs to be transported, or the ones that needs to be deleted during clean up activities. This should be strictly followed by users, instructors, trainees and developers. This naming convention needs to be strictly followed by developers to avoid their asset objects to be deleted in the system.
For example, Our Standard name convension is <string><md><c><9999999>FREETEXT
String = 2 char alpha numberic charactor
MD = Module
C = One charactor
9999999 = Incident or CR number
Then free text
we want to restrict this. so if the end-user named the TR with anything else that does not follow the naming convention we have established, the end-user should encounter an error stating the he/she must change the name of the TR and follow our naming convention before he/she could proceed.
Looking for good solution which can be easily implemented.
regards
Kishore

Hi,
Double click the request and change. There is a documentation tab. Enter the text there and save.
Pranav

Similar Messages

Standard text last transport request

Hi Friends,
I want to know the standard text(SO10) last Transport Request Kindly let me know if any one knows.
Awaiting your response.
Thanks,
Vijay

Get all the requests for the Standard text from view V_E017EU with TRSTATUS = 'R' and PGMID = 'R3TR' and OBJECT = 'TEXT' and OBJ_NAME = 'TEXT,ZSTEXT,ST,E' ( ZSTEXT is the name of the Standard text - replace with your Standard text name, E for English) and from the requests hope you can figure out the latest one.

Why to save standard texts in customization requests only?

Hi Experts,
I have copied standard text of SAP SCRIPTfrom one system to other development system through the report RSTXSCRP.But I want to save the standard text in Transport Request.
I have tried to do it by using report RSTXTRAN.But Its asking for customization request.
Is it mandatory to store the standard texts in Custimization requests itself?Is it not possible to save it in workbunch request?
Thanks in advance
Harika

Hi Harika,
No we can save Standard texts in BOTH Workbench request and Customizing request. It will work.
But in to save a Standard text in a Workbench request, the Sub task type has to either Development/Correction or Repair
Thanks..

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

Error during transport request import - how to get it's text at runtime?

Good day to you, Ladies and Gentlemen!
Would be glad if someone can give me an advice.
Suppose we are importing a transport request to a system. And an error occurred during import.
In my program I want to display why the transport failed. How can I get the error message text with description of what is wrong? The same we can see at the transport log?

Hi
If you mean reading the Transport Log of a request you can use this FM
data: lines type table of TRLOG.
CALL FUNCTION 'TR_READ_LOG'
EXPORTING
   IV_LOG_TYPE             = 'FILE'
   IV_LOGNAME_FILE         = '/usr/sap/trans_UE6/log/E7DG900147.UE6'
TABLES
    et_lines                = lines
EXCEPTIONS
   INVALID_INPUT           = 1
   ACCESS_ERROR            = 2
   OTHERS                  = 3
You just have to figure out which directory is you system using to store the Transport Logs. Also note that in this case UE6 it would be the logical name of your system and E7DG900147 the transport request number.

How to attach a standard text to a Transport request?

Dear all,
Please let me know, How to attach a standard text(created in tcode SO10) to a Transport request?
Thanks in advance.

Hellö,
Run the report RSTXTRANS and give the standard text name and execute. A popup will be dispalyed which asks for the TR
Regards,
Vasanth

How to create transport request for standard text created using SO10.

Hi,
How to create transport request for standard text created using SO10?
Regards
Ramakrishna L

Hi,
For the Standard text created in SO10,
please go to transaction SE78 -> FORM GRAPHICS->STORED AS TEXT->STANDARD TEXTS->
Double click on ADRS or ST or what ever your type of text->
Enter your standard text name
Click on transport button->SHIFT+f6-> It will ask you for a transport request.
Best regards,
Siva

How to get the transport request for a particular standard text?

Hi,
i want to know, how we get the transport request which associated for standard text.
Please note already the standard text is assigned to the TR using RSTXTRAN program.
i have a std text. i want to find the related TR for that!
rds,
Siva.

Refer the link. It might tellsa about attaching to transport request but using the way you can find also -
Re: How To Transport STANDARD TEXTS??
Regards,
Amit
Reward all helpful replies

Assign standard text (SO10) in transport request

Hi Experts,
How can i assign the standard text i've created in SO10 to a transport request. Thanks!
Best Regards,
Kurtt

Hi,
Refer note 3355 in OSS for a complete explanation. The SAPscript objects that should be transported must be written in a transport request.
The entries are as follows:
R3TR FORM NAME (NAME = Name of the layout set)
R3TR STYL NAME (NAME = Name of the style)
R3TR TEXT OBJECT,NAME,ID,L
(OBJECT = Text object, NAME = Text name, ID = Text ID, L = Text language)
If you want to transport a number of texts, you can use report RSTXTRAN to insert the individual text keys into a correction. The transport request must be entered and released via the transport system.
Regards
Sudheer

Importing standard SAPScript text - not asking for transport request!

Hi!
I tried to import some standard SAPScript text running program RSTXSCRP.
Everything was fine, but I was not asked for package and for a transport request... is it ok?
How can I send this standard text to Quality system?
Will reward,
Mindaugas

You can use program : RSTXTRAN
Navigation -> goto SE38 -> enter RSTXTRAN -> execute ->
Name of correction -
text key -object - TEXT
text key- name - enter standard text name
Text id - ST
Text key language - EN
execute now -> select text here -> enter -> now click on push button trsfr texts to corr -> you will get pop up window( request)
Thanks
Seshu

Doubt in creating the transport request for "STANDARD TEXT""

HI ALL,
i used the standard text in scripts but i am getting the problem while creating the transport request for that,
i am not able to create the transport request for that,if anybody knows plzlet me know,
this is very urgent,
thanks and regards,
saikrishna.

HI SURESH ,
THANKS FOR UR IMMEDIATE REPLY ,
i executed that report in that i have given
Name of Correction : ZREPST
Textkey-object:
Text key name:
Text key - ID: ST
Text key - language :EN
Here Textkey-object,Text key name
wat i have to ,give after that ,can i execute that ,
will it create the request.
plz let me know,now ur answer is very valueble ,because ,now i have to release everything,
plz let me know immediately,
thanks and regards,
saikrishna.

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

To change the Transport Request Number Range.

<b>Hi Experts,</b>
My customer needs a typical solution.
He wants SAP to create the Future Transport Requests starting from 10000. ( Ten thousand)
now the sequential order is 321
that is <SID><K9>00321. From now on the new transport request should start from 10000
i.e.
<SID><K9>100000
<SID><K9>100001
<SID><K9>100002
etc.
Is it possible. ?
Thanks for your help.
Best Regards,
Raghunahth L

Hi
Check the report RSWBO301 and check its documentation..
Press "I" button in the selection screen to get the documentation..
I believe this might solve your problem...
Program documentation
Short text
Number Assignment for Requests: Find Free Interval
Description
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.
Requirement
For customers the number range interval includes the follwing areas:
o   900000-999999 (just numerals)
o   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 R/3 System C11. The last number assigned is
         C11K900115. The customer now imports transport request C11K9ZZZZA
         from an external R/3 System C11 into the customer system C11. The
         next request created in this system will have the number C11K9ZZZZB
                                                                                Procedure
Proceed as follows:
1. Execute this program in transaction SE38.
2. Enter the interval limit, for example 5000. You can change this
         limit at any time.
3. Choose Execute.
         If you entered an interval limit of 5000, the report searches for a
         free interval with a size of 5000.
4. If the search was successful, you can save this interval. If not,
          repeat the search with a smaller interval.
Thanks,
Naren
Thanks,
Naren

Unable to capture the Data Source into a Transport Request

Hi All,
We have a product hierarchy and we are using the data source :4R_PRODH_D_LGEN_HIER for the hierarchy.
Now we need to transport this structure to the quality environment but we were not able to capture the datasource:4R_PRODH_D_LGEN_HIER into a transport request.
When ever we activate the data source:4R_PRODH_D_LGEN_HIER it is asking for the Package and the Transport Request Number.If we give these details and save it, data source is not getting captured in the request, only the "bject Directory Entry" is getting captured.
Can someone please guide me on how to capture the datasource under "Data Sources in BW" in a transport request.
Regards,
Sachin Dehey.

Hi Sachin,
Hierarachy datasource is not captured as Attributes and Text Datasource. So what ever you have done is correct.
What ever is captured in Object Directory Entry is correct. So go ahead with your transports, once transport is done check the Hierarchy Infopackage with Available OLTP hierarchies and load the data.
Most important thing first see that the all Master & Transactional Datasources are transported in R/3 Dev to QA to PRD
In BW, datasources are not transported, only their replica is transported.
Transportation of Datasource is done in R/3. Only their replica is transported in BW.
So wht ever you have done till now is correct. So go ahead.
While attaching Hierarchy Datasource it is captured only in "Object Directory Entry"
Regards,
Vishnu.

Copy contents of a txt file into a transport request

I am implementing the steps of the 990534 note.
The note says "Create a new transport request (transaction SE09) in the source client of your Solution Manager system. Unpack file SOLMAN40_MOPZ_TTYP_SLMO_000.zip, which is attached to this note. Copy the contents of the SOLMAN40_MOPZ_TTYP_SLMO_000.txt file into the transport request."
can anyone tell me how can I copy the contents of a txt file into a transport request?

Hello,
I don't know the OSS note, but I think they mean, that you have to go into the object list of your transport (in transaction SE09), switch to change mode and insert the objects from the text file.
I guess the text file looks like:
R3TR PROG xyz
R3TR TABL abc
Best regards
Stephan

Enforcing free text in Transport request

Similar Messages

Maybe you are looking for