Skip to Content
author's profile photo Former Member
Former Member

Form existing in client 000

Hi All Experts,

I have a requirement to use form sd_packing_list which is actually existing in client 000. Requirement to use this form is in another client. This form is not existining in another client where I want to do the development copying this form and make some changes. What is the way out.

Should I copy the form from client 000 to the required client. I also want to know is it possible that if some transaction inside (VL74) uses this form in the client in which this form is not existing, will it work I mean will transaction be able to make use of that form.

One more thing as I know script is client dependent it means if form does not exist in a client then it must be copied from the root client which is 000 and then make the necessary change further on.

Thanks,

Mark

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Sep 21, 2007 at 07:03 AM

    hi

    mark

    we can copy the script from the 000 client

    and we can use it our client as per our requirement

    to do this go to edit -


    copy client

    it will ask to which client u want give the clinet and language

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 21, 2007 at 07:07 AM

    hi

    use report RSTXR3TR

    Report RSTXR3TR allows SAPscript objects (texts, styles, forms) and device types to be transported between R/3 and a local or central file. Which objects are to be transferred is taken from a transport request created in the transport system.

    The entries in the transport request appear as follows:

    Forms are transported using R3TR FORM NAME, where NAME stands for the name of the form.

    Styles are transported using R3TR STYL NAME, where NAME stands for the name of the style.

    Texts are transported using R3TR TEXT OBJECT,NAME,ID,L, where OBJECT stands for the text object (from table TTXOB), NAME for the text name, ID for the text ID (from table TTXID), and L for the language key of the text.

    Device types are transported using R3TR PRIN NAME, where NAME stands for the name of the device type.

    Note: Texts, styles, and forms are client-specific! They are always read from the current client when exported and to thecurrent client when imported. Printer definitions are not client-specific. The current client is therefore not significant when exporting/importing device types.

    reaward for use ful answers

    regards

    Nagesh.Paruchuri

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.