Form routine problem

what is the exact use of the form routine assigned in nace?
eg:
o/p type                                     script drv prog   form routine  formname
NEU        (Purchase order)     SAPFM06P     ENTRY_NEU     MEDRUCK
if i create any modifications in the form routine using itcsy then will i have to write all the code within this form routine?
eg:
perform <form routine name> in program zprog1.
using
changing
endperform.
i have searched sdn but cudnt find a suitable answer. pls explain with an example.

Hi,
The routine mentioned in the Nace will have the logic to Get the data required to ptint on the form and also it call the Form using the function modules lije Open_Form Start_form Write_form. If it is a smartform it calls the Smart form generated FM.
Ex NACE--> ENTRY_NEU
Driver Program in NACE is ZSAPFM06P
This prgram contains the form  ENTRY_NEU
Form ENTRY_NEU.
*get the data
*Call the form
Endform.
I hope it is clear.

Similar Messages

  • Global variable declaration in form routines

    Hi All,
    i am new of the smartforms, i have a small problem in smartforms.
    i need to display the one text based on the condtions, already i have putted the condtions in the condition tab for the text, i need to compare the one more condtion, the condtion is TB_INFORMATION IS NOT INITIAL.
    the code was devaloped in the formroutines , i need to implement the one condtion in the form routines,
    the condition is if TB_INFORMATION IS NOT INITIAL is not initial
                                  va_information = x.
                                endif.
    already i declared the variable in the global defination ,but i am getting the error.
    where can i declare the global variable in form routines.
    Please help me,
    Thanks & Regards
    charan

    declare in global data and it will be visible and available in form routines too.

  • Adobe Form Formatting Problem

    Hi ,
    I am printing a Custom Adobe Form(ZPTRV_EXPENSE_FORM), which is a copy of standard form(PTRV_EXPENSE_FORM), through PR05. The problem here is in the subform for additional trip information, where the comments entered by the user are getting displayed, is not getting frmatted properly.
    for example.
    2.Had a joint meeting with Mr.ABC, Mr.PQR, Mr.XYZ.
    is getting displayed as
    2.Had a joint meeting with Mr.ABC, Mr.PQR, M       r.XYZ.
    I have not changed any property of the said text area.
    I found a SDN post which says it has been done in the interface. In this case, I am using a standard interface which does not
    have any code in code initialization or Form routine.
    Could you please guide me through.
    Regards,
    Sagar

    Hi Otto,
    First of all thanx for your prompt and kind reply. As I said the text hs been copied from MS Word. There are two boxes in the
    text, wierd characters as you pointed out. But there is a part of text which does not hav those characters, yet there is a space
    infact multiple spaces that appear in the preview.
    I tried typing the part of the text manually in the comments box without the spaces. Then too, some of my words are split into
    two or two words put togather.
    I have also checked changing the font, but that didnt help. And the binding of the text field is set to 'EDITOR'. But if you check
    the context, there is no element called 'EDITOR' not does the form interface have a parameter which passes the long text meant
    for comments . That was the reason I was asking, what are the possible ways we can populate data in a form.
    Regards,
    Sagar

  • Workbench request when creating new form routine in TMG

    Dear SCN,
    I have build a TMG for a custom table ZSPFLI_1 with fields.
    Field Name          Data Element
    MANDT               S_MANDT
    CARRID              S_CARR_ID
    CONNID              S_CONN_ID
    COUNTRYFR       LAND1
    CITYFROM         S_FROM_CIT
    DOC                   ERDAT
    ERNAM              ERNAM
    TIME                   UZEIT.
    I have created a form routine.  ZCREATE_ENTRY to auto populate DOC, ERNAM, TIME.
    FORM ZCREATE_ENTRY.
    ZSPFLI3-DOC = SY-DATUM.
    ZSPFLI3-ERNAM = SY-UNAME.
    ZSPFLI3-TIME  = SY-UZEIT.
    ENDFORM.
    The TMG and Function group and table are saved and activated as local objects.
    I want to add another form routine that will modify the DOC, ERNAM, TIME for any record that is edited by TMG for the custom table ZSPFLI_1.
    Every object was saved as local object.
    The problem is when I am creating a new form routine, it is asking for workbench request and I don't have the option to save it as local object in the dialog box.
    Regards,
    Soumen Das.

    Dear SCN,
    Is the issue due to the fact that we can only add form routine once when defining the TMG. I think this should not be the limitation as fields may be added afterwards, and this may require to modify the form routine events.
    Regards,
    Soumen.

  • FORM ROUTINE in Output Types

    Hi group,
      there is a requirement in which after the generation of accounting document(after saving VF01), we need to immediately reverse some of the lines in the accounting document by using F-02.  We have thought of using the Output Type Program to write our code as that was the only genuine place we could find to write our enhancement ( searched for user-exits after accounting doc is generated but cudn't find any). In the program , we shall write the BDC for aor reversal process. Now, when we SAVE VF01, this program(RLB_INVOICE, output type RD00) gets triggered. I thought instead of  writing something in the standard program( or even a Z version of it ), we wud write our code in a new program & then assign this program in NACE. I tried with some dummy program(zxxxxx), but there is an error log which says 'Processing Routine Entry does not exist for program zxxxxx).
    what is the significance of this FORM Routine 'ENTRY' in the output type???  wat is the solution for my problem??
    hope i am clear enough
    ur valuable inputs awaited...
    Thanks & Regards,
    Bikash Agarwal

    Hi
    The routine ENTRY is the start form called by the progam runs the print (RSNAST00 for example), that routine has to be defined in the program is assigned to output type.
    See the program RLB_INVOICE, here you can find the form ENTRY.
    So the program manages the print for the output type RD00 run a comand like this:
    PERFORM ENTRY IN PROGRAM RLB_INVOICE USING .......
    I don't think there's an exit after accounting document is created, there are some BTE (trx FIBF) are triggered just before it is generated, for example in BTE 1030: here you can know all accounting number and data (but the document isn't stored in database yet).
    I don't know if it's a good idea to insert the code in the routine of the print: remember all the process of saving of account document are running in update tusk, so while the output is been printing you can't be sure the accounting document is really stored in database.
    Max

  • Output Types Replacement of text symbols: program, FORM routine needed

    Hello,
    I'm searching for a program and/or FORM routine that will replace &EKKO-EBELN& and &EKKO-LIFNR& (from Mail title and texts) .
    Example: Hochland Rahmenvertrag &EKKO-EBELN& / &EKKO-LIFNR&
    Replaced with: Hochland Rahmenvertrag 4600012345 / 712888
    I have problems filling the eMail subject when creating a Outline agreement (Apllication EV)...
    For purchase orders it's working without FORM routine (Apll. EF) !!!
    SAP provides this (empty) fields in transaction NACE (or NACT).
    Output type > Detail
    General Data > Replacement of text symbols
    appreciating any hints in this topic
    regards
    Jörg
    from SAP F1 context help:
    Program for creating or changing an output text
    Use
    In order to analyse parameters in titles of e-mails or faxes, you have to store a special program and a form routine in the field FORM routine. System fields like SY-UNAME or SY-DATUM are are excluded from this: They will be automatically analysed by the system.
    Example
    On New Year's Day 2000, you send the purchase order 4711 by fax. The title of the corresponding output type is "Purchase order no. VBAK-VBELN on SY-DATUM" (put a "&" before and after the fields). In the outbound message you therefore have the output "Purchase order no. 4711 on 01/01/2000". The field VBAK-VBELN has been filled with global data by a form routine.

    shital phadake wrote:
    > here are some hints
    > PR - SAPMM06B - Include MM06BFTE_TEXT_EDITIEREN - ?????
    > PO - SAPMM06E - Include MM06EFTE_TEXT_EDITIEREN - Form text_symbol_replace
    Great - these where the hints i was searching for
    NACE ...
    program = SAPMM06E
    form routine = TEXT_SYMBOL_REPLACE
    ...now the eMail subject is filled with PO-number and supplier-number as demanded ... and all just using SAP standard
    thx to you guys assisting me
    special thx to shital phadake
    Jörg

  • Form Routines

    Hi  ABAP Gurus,
                             i am new to abap.i Have some small doubts.please explain me some doubts.please do explain me in simple words dont send links.
    1. what is a FORM Routine?
    2. what is importing ,Exporting?
    3. what is the diff. b/w exporting & Returning?
    4.what is changing?
    5. what is returning ,receiving?
    6.what is PERFORM Statement?
    7.explain me about public,protected and private?
    note:please do explain me these with simple coding so that i can be familiar to know where to use them.

    Check this link -
    http://www.geocities.com/rmtiwari/Resources/Utilities/ABAPReference/ABAPReference.html
    PERFORM
    Variants:
    1. PERFORM form.
    2. PERFORM form IN PROGRAM prog.
    3. PERFORM n OF form1 form2 form3 ... .
    4. PERFORM n ON COMMIT.
    5. PERFORM n ON ROLLBACK.
    6. PERFORM form(prog).
    Variant 1
    PERFORM form.
    Extras:
    1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
    3. ... TABLES   itab1 itab2 ...
    Effect
    Calls the subroutine form defined usng a FORM statement. After the subroutine has finished, processing continues after the PERFORM statement. The parameters of the subroutine are position parameters, and must be passed in the call according to the definition of the formal parameters in the corresponding FORM statement.
    Example
    PERFORM HELP_ME.
    FORM HELP_ME.
    ENDFORM.
    The PERFORM statement calls the subroutine HELP_ME.
    Note
    Non-Catchable Exceptions:
    PERFORM_PARAMETER_MISSING: The subroutine called has more parameters than you passed to it.
    PERFORM_TOO_MANY_PARAMETERS: You passed more parameters to the subroutine than it was expecting.
    PERFORM_CONFLICT_TYPE,
    PERFORM_CONFLICT_TAB_TYPE,
    PERFORM_STD_TAB_REQUIRED,
    PERFORM_CONFLICT_GENERIC_TYPE,
    PERFORM_BASE_WRONG_ALIGNMENT,
    PERFORM_PARAMETER_TOO_SHORT,
    PERFORM_CAST_DEEP_MISMATCH,
    PERFORM_TABLE_REQUIRED: The type of a parameter did not correspond to the type specified in the FORM statement.
    Addition 1
    ... USING    p1 p2 p3 ...
    Addition 2
    ... CHANGING p1 p2 p3 ...
    Effect
    These two additions have an identical function. However, you should always use the same addition as is used in the corresponding FORM definition (for documentary reasons).
    The statement passes the parameters p1 p2 p3 ... to the subroutine. A subroutine may have any number of parameters.
    The order in which you list the parameters is crucial. The first parameter in the PERFORM statement is passed to the first formal parameter in the FORM defintion, the second to the second, and so on.
    You can specify offset and length of a parameter as variables. If you use the addition ' ...USING p1+off(*)', the parameter p1 will be passed with the offset off, but the length will not exceed the total length of the field.
    Example
    DATA: NUMBER_I TYPE I VALUE 5,
          NUMBER_P TYPE P VALUE 4,
          BEGIN OF PERSON,
            NAME(10)      VALUE 'Paul',
            AGE TYPE I    VALUE 28,
          END   OF PERSON,
          ALPHA(10)       VALUE 'abcdefghij'.
    FIELD-SYMBOLS <POINTER> TYPE ANY.
    ASSIGN NUMBER_P TO <POINTER>.
    PERFORM CHANGE USING 1
                         NUMBER_I
                         NUMBER_P
                         <POINTER>
                         PERSON
                         ALPHA+NUMBER_I(<POINTER>).
    FORM CHANGE USING VALUE(PAR_1)
                      PAR_NUMBER_I
                      PAR_NUMBER_P
                      PAR_POINTER
                      PAR_PERSON STRUCTURE PERSON
                      PAR_PART_OF_ALPHA.
      ADD PAR_1 TO PAR_NUMBER_I.
      PAR_NUMBER_P = 0.
      PAR_PERSON-NAME+4(1) = ALPHA.
      PAR_PERSON-AGE = NUMBER_P + 25.
      ADD NUMBER_I TO PAR_POINTER.
      PAR_PART_OF_ALPHA = SPACE.
    ENDFORM.
    Field contents after the PERFORM statement:
    NUMBER_I    = 6
    NUMBER_P    = 6
    <POINTER>   = 6
    PERSON-NAME = 'Paula'
    PERSON-AGE  = 25
    ALPHA       = 'abcde    j'
    Notes
       1. If you want to pass the body of an internal table itab that has a header line, you must use the notation itab[] (see Data Objects). If you do not use the brackets, the header line of the tabel is passed.
       2. The field types and lengths of the parameters remain the same. If a parameter is changed within the subroutine, it will still have the changed value after the subroutine has finished. This does not apply to parameters passed using VALUE. werden.
       3. If you pass literals, they may not be changed unless you pass them to a formal parameter defined with USING VALUE.
    Addition 3
    ... TABLES itab1 itab2 ...
    Effect
    TABLES allows you to pass internal tables to a subroutine.
    Example
    TYPES: BEGIN OF ITAB_TYPE,
             TEXT(50),
             NUMBER TYPE I,
           END OF ITAB_TYPE.
    DATA:  ITAB TYPE STANDARD TABLE OF ITAB_TYPE WITH
                     NON-UNIQUE DEFAULT KEY INITIAL SIZE 100,
           BEGIN OF ITAB_LINE,
             TEXT(50),
             NUMBER TYPE I,
           END OF ITAB_LINE,
           STRUC like T005T.
    PERFORM DISPLAY TABLES ITAB
                    USING  STRUC.
    FORM DISPLAY TABLES PAR_ITAB STRUCTURE ITAB_LINE
                 USING  PAR      like      T005T.
      DATA: LOC_COMPARE LIKE PAR_ITAB-TEXT.
      WRITE: / PAR-LAND1, PAR-LANDX.
      LOOP AT PAR_ITAB WHERE TEXT = LOC_COMPARE.
      ENDLOOP.
    ENDFORM.
    Within the subroutine DISPLAY, you can use any internal table operation to work with the internal table that you passed to it.
    Note
    If you use TABLES, it must always be the first addition in a PERFORM statement.
    Variant 2
    PERFORM form IN PROGRAM prog.
    Extras:
    1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
    3. ... TABLES   itab1 itab2 ...
    4. ... IF FOUND
    Passsing SY-REPID not allowed and Receiving SY-SUBRC not allowed.
    Effect
    This variant is similar to variant 2 (external perform). However, here you can specify the names of both the subroutine and the program in which it occurs dynamically at runtime. If you do this, you should place the variables form and prog in parentheses. The names in form and prog must be entered in uppercase, otherwise a runtime error occurs. If you do not specify any additions (such as USING) you do not need to specify the program after IN PROGRAM. In this case, the system looks for the subroutine in the current program.
    Example
    DATA: RNAME(30) VALUE 'WRITE_STATISTIC',   "Form and program
                                               "names must
          PNAME(8)  VALUE 'ZYX_STAT'.          "be written in
                                               "upper case
    PERFORM (RNAME)         IN PROGRAM ZYX_STAT.
    PERFORM WRITE_STATISTIC IN PROGRAM (PNAME).
    PERFORM (RNAME)         IN PROGRAM (PNAME).
    All three PERFORM statements have the same effect, that is, they call the subroutine 'WRITE_STATISTIC', which is defined in the program 'ZYX_STAT'.
    Notes
    Dynamic PERFORM statements require more CPU time, since the system has to locate the subroutine each time.
    Note
    Non-Catchable Exceptions:
    PERFORM_NOT_FOUND: Unable to find the specified subroutine.
    LOAD_PROGRAM_NOT_FOUND: Unable to find the specified main program.
    PERFORM_PROGRAM_NAME_TOO_LONG: The specified program cannot exist because the program name is longer than 40 characters.
    Addition 1
    ... USING p1 p2 p3 ...
    Effect
    See variant 1, addition 1.
    Addition 2
    ... CHANGING p1 p2 p3 ...
    Effect
    See variant 1, addition 2.
    Addition 3
    ... TABLES itab1 itab2 ...
    Effect
    See variant 1, addition 3.
    Addition 4
    ... IF FOUND
    Effect
    The system only calls the subroutine if it and its main program exist. If this is not the case, the statement is ignored.
    Variant 3
    PERFORM n OF form1 form2 form3 ... .
    Effect
    Calls the subroutine with the index n from the list of subroutines in the statement. At runtime, n must contain a value between 1 (first name) and the total number of subroutines listed in the PERFORM statement (last name). The list can contain up to 256 subroutines.
    Note
    Non-Catchable Exceptions:
    PERFORM_INDEX_0: The specified index was too small.
    PERFORM_INDEX_NEGATIVE: The specified index was negative.
    PERFORM_INDEX_TOO_LARGE: The specified index was too big.
    Variant 4
    PERFORM n ON COMMIT.
    Extras:
    1. ... LEVEL idx
    Effect
    Calls the specified subroutine at the next COMMIT WORK statement. This allows you to delay the subroutine until the logical transaction is finished. Even if you register the same subroutine more than once, it is only executed once. For further information, refer to COMMIT WORK. The ROLLBACK WORK statement deregisters all subroutines registered using this addition.
    Notes
       1. You cannot use USING or CHANGING with the ... ON COMMIT addition. If you need to pass data to the subroutine, you must place it in global variables or use the EXPORT ... TO MEMORYstatement.
       2. The PERFORM ... ON COMMIT statement can also be used during update. The corresponding subroutine is called at the end of the update task.
    Addition 1
    ... LEVEL idx
    Effect
    The LEVEL addition, followed by a field, determines the sequence in which the specified subroutines will be executed at the COMMIT WORK statement. The subroutines are called in ascending order of their level. If you do not use the LEVEL addition, the subroutine assumes the level zero. If two or more subroutines have the same level, they are executed in the sequence in which they are called in the program. You assign levels by defining constants in an include program. The level must have type I.
    Variant 5
    PERFORM n ON ROLLBACK.
    Effect
    The specified subroutine is executed if a ROLLBACK WORK occurs. This allows you, for example, to delete data, such as an internal table or data in memory, that was intended for use in PERFORM...ON COMMIT. If you register the same subroutine more than once, it will still only be executed once per ROLLBACK WORK.
    Notes
       1. Subroutines registered using PERFORM... ON COMMIT cannot have USING or CHANGING parameters. Any data you want to pass to them must be contained in global variables or buffered using EXPORT ... TO MEMORY.
       2. If you catch a type A message ( MESSAGE) using the EXCEPTIONS..ERROR_MESSAGE addition in the CALL FUNCTION statement, a ROLLBACK WORK occurs, in which the subroutines registered using PERFORM ... ON ROLLBACK are executed.
    Variant 6
    PERFORM form(prog).
    Extras:
    1. ... USING    p1 p2 p3 ... 2. ... CHANGING p1 p2 p3 ...
    3. ... TABLES   itab1 itab2 ...
    4. ... IF FOUND
    PERFORM form(prog) not allowed.
    Effect
    Calls the subroutine form defined in program prog ("external PERFORM").
    Notes
       1. You pass parameters to the external subroutine as described in variant 1.
       2. However, you can also do it using a shared data area ( DATA BEGIN OF COMMON PART).
       3. Please consult Data Area and Modularization Unit Organization documentation as well.
       4. You can use nested calls, including several different subroutines in different programs.
       5. When you call a subroutine that belongs to a program prog, prog is loaded into the PXA buffer (if it has not been loaded already). To minimize the possibility of memory problems, try not to use too many external subroutines from a large number of different programs.
    Hope this helps.
    ashish

  • Use of us_screen in the form routine :  FORM entry USING retcode us_screen

    Hello All,
    I have one print program entry routine as below.
    FORM entry USING retcode us_screen.
    Some code to print the form data...
    EndForm.
    When i Check the value of us_screen in the debuging, its value is coming as blank.
    When i checked the other form routine the value of us_screen is coming as 'X.
    I am my getting why in my case value of us_screen is coming as blank.
    What is significant of this field.
    Thanks & Regards
    Sachin Yadav

    Cusomization might be missing for that output type in transaction NACE.
    us_screen is blank because below query fails due to missing entry in table TNAPR.
    SELECT SINGLE * FROM TNAPR WHERE KSCHL = P_KSCHL
                               AND   NACHA = P_NACHA
                               AND   KAPPL = P_KAPPL.
    First assign the output type with a Transmission medium, Program, Form Routine, Form in transaction NACE
    Take the help of your functional consultant.

  • Form routines in CRM down loaded from R/3 for pricing

    Hi all,
    we have the following scenario:
    1) We have created an access sequence for tax condition in R/3 using standard form routines / requirements 7 (domestic) and 8 (export).
    2) The cutsomizing and conditions are down loaded to CRM (4.0) and the prices are calculated using the IPC.
    In R/3 the tax is determined correctly:
    check: komk-aland = komk-land1 -> domestic tax is determined.
    check: komk-aland ne komk-land1-> export tax is determined.
    In VOFM (R/3) it is possible to see the ABAP code of the requirement and set break points to check how the access is fullfilled.
    _Problem
    In CRM domestic tax is determined even though sold-to and ship-to party have different country codes. The same scenario that determines export tax in R/3 determines domestic tax in CRM.
    The pricing analysis in the transaction in CRM displays that the access is found and that requirement 7 is fullfilled which makes no sense.
    Does any one know where to find the code of the requirement in CRM and make a similar analysis with break points as in R/3 to see how the fields of the access are filled and the requirements are checked ? In customizing and the IPC only the form routine number is displayed but the code is not visisble.
    Thanks in advance,
    /Annette

    Hi Annette,
    I do not know what version of CRM you are running but I assume it is > 4.0. In all circumstances we are talking Java IPC developments which are not as easy to debug as ABAP. I will refer you to OSS note 809820 for further info.
    You can upload and download the Java devlopments to the CRM server in transaction /N/SAPCND/UE_DEV.
    Debugging is unfortunately not as easy as in R/3. I have not done it myself but I think you have to install Eclipse or NWDS on your machine. And then it should be possible to link it to CRM.
    There is some additional information here:
    http://help.sap.com/saphelp_nw04s/helpdata/en/f7/928f9e77da4588b9bf5e65d73bd674/content.htm
    But you definately need Java knowledge to do this
    Br,
    Anders

  • TRANSMISSION MEDIUM AND FORM ROUTINE IN CASE OF NACE TRANSACTION

    While saving a invoice, I have created a routine which will pick an output type when a certain condition is met.
    A custom report (Zprogram) needs to be triggered automatically during this invoice save. So we need to attach this Zprogram to output type.
    Could anybody tell me the transmission medium to be selected and also what needs to be entered in the field Form routine for this program which I have created in the transaction NACE->V3(Billing)->Output types->Processing routines?
    Thanks in advance.

    HI Shah,
    Form routine is nothing but a sub routine in your Z program (Driver Program). Simply one driver program can be used in multiple Layouts by using Form routines. If you are using the driver program only for one layout, then the routine declaration is not necessary.
    Simply select the transmission medium as Print out in case of print. Special function means whether you want trigger this form for only Bill-to-party or Ship-to-party etc.. I hope you need to maintain as SH or BP, check with your functional people once.
    You can check the below link for further customization reference.
    Link: [output type configuration;
    You can check the below link to know the exact meaning for Form routine.
    Link: [https://forums.sdn.sap.com/click.jspa?searchID=13772541&messageID=5319599]
    Regards,
    Raghu..

  • Error-handling in form routines to be called from maintenance  view

    hello,
    i have created a table maint. dialog. Under 'enviroment->modification->events' you can create form-routines for your own coding.
    I have the maint.event '01 - Before saving the data in the database'. Here i do some checks if entered values in some fields are okay or not etc.....
    When the users enters 'wrong' data i do a "message e000 with 'text' " So i got a error-message and the user is not able to save the data before changing it.
    BUT: i get the right error-message in the status-line, but i got an EMPTY screen, all the fields disapear. I have to go back with enter or the red cancel button. But then i 'fall back' to the selection screen of the maint. view. Thats not very user-friendly.
    Any ideas ?

    hi,
    think you have place your module not correct:
    try that: (without event)
    PROCESS AFTER INPUT.
      LOOP AT EXTRACT.
        FIELD VIM_MARKED MODULE LISTE_MARK_CHECKBOX.
        CHAIN.
          FIELD Y789.
          FIELD Y012.
          MODULE LISTE_UPDATE_LISTE.
        ENDCHAIN.
    *begin of insertation
        CHAIN.
          FIELD Y123.
          FIELD Y456.
          module check_field  ON CHAIN-input.
        ENDCHAIN.
    *end of insertation
      ENDLOOP.
    Andreas

  • How to delete a Form Routine in Table Maintenance?

    Hello,
    Very Good Morning!
    How to delete a Form Routine in Table Maintenance?
    I had created a Form Routine at Environment>Modifcation>Events.
    I want to delete a Form Routine that I had created. Can any one please explain me the way I can delete it.
    Any suggestions are appreciated!
    Thanks & Regards
    Kittu

    Hello Rudra,
    Very Good morning!
    I am in Environment>Modification>Events.
    Here is had created a form routine ie...
    01   From_entry    Editor Icon
    In Editor Icon we will write the code.
    This will create a Include in the Function group.
    I had already comented that Include from the Function group. I can even delete it. But, I want to delete the Form Routine that I had created....
    01   From_entry    Editor Icon
    Can any one hepl me please...
    Thanks & Regards,
    Kittu

  • Regarding form routines IN ECC 6.0

    Hi Abapers,
                       I am currently working in ECC 6.0. I have come through an error as
    se old_entry_xxx as a form routine if you use an own print program
    I have a form routine in my include program as follows...
    FORM ENTRY_NEU USING ENT_RETCO ENT_SCREEN.
      XSCREEN = ENT_SCREEN.
      IF NAST-AENDE EQ SPACE.
        XDRUVO = '1'.
      ELSE.
        XDRUVO = '2'.
      ENDIF.
      CLEAR: XFZ, XOFFEN, XLMAHN, XLPET.
      CLEAR ENT_RETCO.
      PERFORM LESEN USING NAST.
      MOVE RETCO TO ENT_RETCO.
    ENDFORM.   
    Can anyone give any hints regarding how to come out of this error, i guess its a unicode error but not sure.
    Frnds looking for ur help.
    thanks
    & regards,
    kamal

    Hi ,
           I have'nt come up with any solutions yet. But wht i consider is the perform doesnt exist for that form routine.I m wondering , Is that a form routine has any "perform". Frnds if anyone is having any clues plzz provide.
    Its basically a Upgrade task.
    thanking u all.
    regards,
    kamal

  • Perform a form routine within a sap script form

    Hi!
    How can I
    perform a form routine within a sap script form.
    Regards
    sas

    OK,
    many thanks for your kindly reply.
    But basically there is a matter which I don't understand.
    Which way is the better way to loop at internal table:
    Solution1:
    FORM xxx.
    CALL FUNCTION 'OPEN_FORM'
    EXPORTING
       DEVICE                           = 'PRINTER'
       FORM                             = 'ZSD_PACKING_LIST'
       LANGUAGE                     =  SY-LANGU   .
    LOOP AT gt_versand_plan INTO gw_versand_plan.
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
       ELEMENT                        = 'SHELEM'
       FUNCTION                       = 'SET'
       TYPE                           = 'BODY'
       WINDOW                         = 'MAIN' .
    ENDLOOP.
    CALL FUNCTION 'CLOSE_FORM'.
    ENDFORM.
    Solution 2:
    Having the LOOP within the  sapscript form -> 'ZSD_PACKING_LIST'
    Regards
    sas

  • Form Routine in User Exit

    Hi
    I would like to include a form routine in user exit inlcude ZXTXWU01 but I guess that is not possible, so I created a new include ZXTXWZZZ in which I have developed the code for the form routines...
    But I still get the error in the main user exit ZXTXWU01 stating that the Form... End Form can be only after the End Function which obviously refers to the function module containing the main user exit..
    Please let me know how to over come this ....

    Hi,
    You cannot create another Form...EndForm if the first include ZXTXWU01 is already inside a Form..Endform.
    Meaning following structure is invalid:
                 Form first_form.
                       Include  zzzz
                 Endform.
    In  Include zzzz.
         Form  second_form.
         Endform.
    Instead of a Form..Endform subroutine...directly have the statements in the Include program and remove the Form..Endform.
    Regards,
    Subramanian

Maybe you are looking for