Error in IT0764 Poortwachter - form routine check_generate

When trying to create a record in infotype 0764 Poortwachter (parallel to an illness record in 2001), we get an error message when trying to save:
Other exception within form routine CHECK_GENERATE Message no. 5N016
Does anyone have ideas what could be causing this error?
(release 7.0.)
Thanks in advance for your reply!
Regards, Nanja

Solved
Message was edited by:
Nanja Schouten

Similar Messages

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

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.

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

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

Smartform - Form routines tab

Hi experts,
I had written a perform stmt in programl lines and had written FORM...ENDFORM in the form routines tab. But system throws a comliation error that the valriable does not exist even i had declared in GLOBAL defn..etc.
Pls some one give an example of how to use the FORM routines tab?
thanks

HI
DAN
Could you plese send me the coading of form routines tab.
i have to define a form routine in my smart form report may be i can get help from your coading.
thanks
pardeep

Error in a formula function (routine 66 ), record 4,161 RSAR 535

Hi Experts,
I am facing this issue while loading form DSO to Cube. So i am using
Maximum Number of Errors per Pack more then 1000 to skip the error records.
In Error stack i get the below error :
Error in a formula function (routine 66 ), record 4,161 RSAR 535
Can any body help me on this.
Thanks in advance
Mohan.

i am doing datamart load ie DSO to cube
so while loading in DTP in update tab i have selected max no of error recods to be skipes = 9000 this will ignore the records if at all there are error records in the flow.
i know there are few records. but what i want is to identify wht the error in the record is
when i try to chk the records in Error stack if i selet a record to change with change mode i also get a pop up with the error msg
Re: Error in a formula function (routine 66 ), record 4,161 RSAR 535
Which i dont really under stand what and were the error is
i even compared the data of correct record which is alredy processed to the cube.
I could not find much difference
mohan.

Urgent: Selection-screen within Form routines

Hi Experts,
Within Form routines can i declare selection-screen statements. If no how should i declare my objects on selection screen within form routines bcoz when i declared with selection screen statements within form routines iam getting the error as "Within FORM routines and function modules, the SELECTION-SCREEN statement is not allowed".
Regards.
AADI.

Hi Aditya,
U cannot use the Selection-screen in Forms and Function Modules.
Try to use it in an include program and call it from ur program.
Reward if Helpful,
Jagadish.

Calling form-routines

Hello ABAP gutus,
i am using 10 form-routines to get some data, in all subroutines code is same, but i am passing different internal tables to all form-routines with USING, CHANGING parameters.
for example
perform get_header1 using itab changing jtab.
perform get_header2 using itab1 changing jtab1.
FORM get_header1 USING    P_ITAB
                  CHANGING P_JTAB.
   CALL METHOD cl_salv_table=>factory
    IMPORTING
      r_salv_table = r_alvtab
    CHANGING
      t_table      = itab[].
CALL METHOD r_alvtab->get_columns
    RECEIVING
      value = r_col.
CALL METHOD r_col->get
    RECEIVING
      value = r_cols.
loop at r_cols into wa_col.
    ref_col = wa_col-r_column.
    CALL METHOD ref_col->get_medium_text
      RECEIVING
        value = lv_text.
    jtab-header = lv_text.
    APPEND jtab.
    endloop.
endform.
FORM get_header2 USING    P_ITAB
                  CHANGING P_JTAB.
   CALL METHOD cl_salv_table=>factory
    IMPORTING
      r_salv_table = r_alvtab
    CHANGING
      t_table      = itab1[].
CALL METHOD r_alvtab->get_columns
    RECEIVING
      value = r_col.
CALL METHOD r_col->get
    RECEIVING
      value = r_cols.
loop at r_cols into wa_col.
    ref_col = wa_col-r_column.
    CALL METHOD ref_col->get_medium_text
      RECEIVING
        value = lv_text.
    jtab1-header = lv_text.
    APPEND jtab1.
    endloop.
endform.
as above i used 10 form-routines.but i passed different internal tables.after these subrotines i am using those internal table in function modules.
now my client wants me to maintain one form-routine instead of 10 form-routines.
Is it possible that? please tell me . its urgent
Regards
Mahesh

Hello Naredran.
see the below code
perform get_header1 using it changing it1.
perform get_header1 using itab changing it2.
*&      Form get_header1
      text
     -->P_IT text
     <--P_IT1 text
FORM get_header1 USING    P_IT
                  CHANGING P_IT1.
    FIELD-SYMBOLS : <FS>.
CALL METHOD cl_salv_table=>factory
    IMPORTING
      r_salv_table   = r_alvtab
    CHANGING
      t_table        = p_it.
CALL METHOD r_alvtab->get_columns
    receiving
      value = r_col
                   CALL METHOD r_col->get
                     receiving
                       value = r_cols
loop at r_cols into wa_col.
    ref_col = wa_col-r_column.
CALL METHOD ref_col->get_medium_text
   receiving
     value = lv_text.
assign IT1 to <FS>.
<FS> = lv_text.
append it1.
endloop.
ENDFORM.                    " get_header1
bellow error is coming while use the code which you said.
A USING reference parameter should not be used. Instead, define the
parameter as a USING-VALUE(...) or CHANGING parameter.
please let me know waht is wrong .

Form routine name to give fax for Contract (ME31 & ME32)

Hello All,
What is the form routine name to be used for faxing the Contract form (ME31 & ME32) in program SAPFM06P?
Thanks & Best Regards,
Phani Kumar. S

Hi,
Thanks for your replies. But when i give ENTRY_NEU and then try to issue the output for fax, the process is stopped with following error message: Error in OPEN_FORM for document.
Any idea?
Thanks & Kind Regards,
Phani Kumar. S

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

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

Error when starting Adobe Form

I have an Adobe Form which works Ok in the development SAP Portal, but that, when I log in the production portal gives the following error:
Error when reinitializing the form (I guess, it's Error al reinicializar el formulario, in Spanish)
I think maybe there is something missing to transport, or some misconfiguration, but I haven't been able so far to find it...
Can someone give me a hand?
Thank you in advance,
S.

Hi,
Can you tell me when does the error message comes? Does it comes when you are trying to open the Form or when you are trying to execute it.
Please check if it is still working in the development box?
Regards,
Susanta

Error when opening Data Form

Hi All,
Also I have tried by removing access for that user and opened the Dta Form but still it throwing me the same error:
You are trying to open the data form, but cannot because all of the required dimensions are not present. Possible causes may be that you do not have access to at least one member of a required dimension, or the member selection resulted in no members present. Contact your administrator
Kindly guide me.
Thanks and Regards
ChiDam

duplicate post - Error while opening Data form
Cheers
John
http://john-goodwin.blogspot.com/

Error When Opening Any Form

Hi All.,
Im facing some issue while opening any form..its stuck in below mention file while opening any form i tried all the ways still im not able to fix the issue.
Application:11.5.10.2
OS-----------HP-UX
DB-----------10.2.0.4.0
File Name:
oracle/forms/ui/FLWTextArea
Work Around
Relink the all the files
Regenerated the jar files
Regenerated the forms
f60gen help=y
Forms 6.0 (Form Compiler) Version 6.0.8.28.0 (Production)
Forms 6.0 (Form Compiler): Release - Production
(c) Copyright 1999 Oracle Corporation. All rights reserved.
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Metalink Doc id
java.lang.NoClassDefFoundError: oracle/forms/ui/FLWTextArea Error When Opening Any Form [ID 1219663.1]

Thanks,
From the below doc id we are currently in patch set 19 but im not able see that in ad_bugs.,
Note: 232313.1 - Information on Previous Versions of Developer 6i Patchsets
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=232313.1
Here is an example:
If you have Forms: 6.0.8.27.x --> You are on Developer 6i Patch 18
If you have Forms: 6.0.8.26.x --> You are on Developer 6i Patch 17
If you have Forms: 6.0.8.25.x --> You are on Developer 6i Patch 16
If you have Forms: 6.0.8.24.x --> You are on Developer 6i Patch 15
SQL> select bug_number from ad_bugs where bug_number='&BUG_NUMBER';
Enter value for bug_number: 9935935
old 1: select bug_number from ad_bugs where bug_number='&BUG_NUMBER'
new 1: select bug_number from ad_bugs where bug_number='9935935'
no rows selected
SQL>

Error in IT0764 Poortwachter - form routine check_generate

Similar Messages

Maybe you are looking for