Create & Transport Standard Text (SO10)
CREATE & TRANSPORT STANDARD TEXT
STEP1: Create Standard Text: T-Code SO10
Enter the Text Name and then click CREATE Push Button. A Text Screen will appear where you can maintain the Text and SAVE.
STEP 2: CREATE TRANSPORT REQUEST FOR TRANSPORTING THE TEXT
T-Code:- SE09
Click on CREATE
Create a Transport Request
Also need to change the Transport Request from Unclassified to Correction or Repair. For this select your transport request (BCDK906932) and then click on Request/Task on main menu à Change Type and then select the Correction.
Now you can see that from Unclassified the request type changed to Development/Correction.
STEP 3: Include the Text in Transport Request
T-Code: SE38, run program RSTXTRAN
Following Screen will appear, enter your Transport Request No. (note that the transport request no. of Sub-Object will be entered here and not the Main Object)
Following Screen will appear:
Deselect all Objects and Select your Objects only
Press à ENTER
Your selected Objects will be shown
Click on Trsfr texts to corr. Push Buttons
Now you can Release and Import the Transport Request as usual.
it is good learning for me.
Hi,
Actually there is no need to use se09.
You can directly use T-Code: SE38, run program RSTXTRAN and create the transport request by selecting your customized TEXT id .
regards
Works like a charm.
Little pearl of wisdom shared - still valuable 10 years later! Every little bit of efficiency adds up...thank you.
Hi Amitesh,
It is not common but very informative document and the way you presented the issue and its solution is appreciable...
Kind regards,
Khushi
Hi Amitesh,
Thanks for sharing, but the screen shots are not readable can u reorganize it. Also if you can share why & where it should be used it will be beneficial for other.
Thanks
Sukant Chakraborthy
Hi Sukant,
Normally we maintain Text in Customer/Condition Type/Documents etc. and then from there it flows to other documents, which may be used for printing on some Output. These text are normally specific to that particular Customer or Document. However sometime we need to print some Text which are based on certain scenarions for example:- In case of Deemed Export, you want to print some text (like Notification No.) on Excise Invoice, so instead of asking Users to maitain it in Sales Document we can maintain it in SO10 and from there we print as per the logic. We can maintain the SO10 text on every client just like Master Data, by using the Transport Process, we can maintain the SO10 Text as configuration and and then it can be transported to other clients just like any other transport, so user is not requuired to maintain it in every client.
Hope I am able to clarify your query.
Thanks and regards,
Amitesh Anand
Thanks amitesh for replying.
Dear ,, just plz explain me exact what is the use of this plz
i understood the process but i did not i understood out put Results plz pzl z
Hi Venu,
Kindly check my response to Sukant.
Hope it clarifies your query too.
Thanks and regards,
Amitesh Anand
Thanks for sharing
Fine Explanation
It is a good practice to transport standard texts through TRs instead of maintaining directly in production system with the help of business. This will ensure uniformity across all the systems (test system and production system) and no confusion will occur.
Thanks,
Swosti Panda.
Thanks for sharing...
Thank You Amitesh for sharing this document.
Thanks for the explanation, much appreciated
Thanks for sharing this information. I followed step by step and it seemed to work with no errors. But I can't see the new text in my smartform.
Hi Tom,
Thanks for your appreciation.
Regarding smart-form, please check the logic used by ABAP.
The logic for picking the text from standard text is different from the Text of Sales Document (Order/Delivery/Billing).
Perfect step by step - thanks
Good one to anybody to follow
Very Informative document
EXCELLENT DOCUMENT - VERY INFORMATIVE
THANKYOU
GANESH
Good information and good documentation.
Thanks!
Very nice information.. in a very systematic manner. thanks.
Thanks Amitesh for the nice content !!
Amitesh ,
Thank you for making this very nice step by step document for SO10 text transport. Appreciated.
Hi all,
Very helpful and great explanation.
Thank you very much.
Catarina
Really appreciate this info, thanks!
Good Day. Thanks for the information. A great learning for me.
Hi Amitesh,
Very useful blog indeed. People who're beginners can easily understand the concept through this blog. very informative. Thanks .
Keep posting blogs like this to help the needy.
Regards
Sri Ram
Can you please help in guiding on how to transport deletion of standard texts ? Is there any way to capture deletion of standard texts in TR & move across?
Thanks Amitesh - 10 years later and your generous sharing of your knowledge is still helping others!
Tip #1 to others benefiting from this post... you can save yourself the initial steps of creating the Workbench correction and changing the Task Type to "Development/Correction": simply leave the "Name of Correction/Repair" blank when you run RSTXTRAN ... you will be prompted to create a CUSTOMISING Transport Request, which, once created, will have a Task containing the text object you specified in RSTXTRAN. From there on, the TR created will behave just like any other TR created to move configuration table changes when you release it, i.e. your text will move from DEV to QA.
So... even better.... Tip #2: if you already have a Customising TR, you can simply enter its Task number as the "Name of Correction/Repair" when you run RSTXTRAN.
Happy SAPping everyone!
RSTXTRAN: Create Customising Transport Request