Oracle Forms Plsql Error 49
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this bad bind variable in oracle trigger site About Us Learn more about Stack Overflow the company Business Learn more bad bind variable error in pl/sql about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x pls-00049 bad bind variable Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error 49 bad bind variable oracle forms up vote 2 down vote favorite I would like to ask regarding this error... Error 49 at line 5, column 6 bad bind variable 'S_ORD.payment_type' Here is the code: DECLARE N NUMBER; v_credit S_CUSTOMER.credit_rating%type; BEGIN IF :S_ORD.payment_type = 'CREDIT' THEN SELECT credit_rating INTO v_credit FROM S_CUSTOMER WHERE :S_ORD.customer_id = id; IF v_credit NOT IN ('GOOD', 'EXCELLENT') THEN :S_ORD.payment_type:= 'CASH'; n:=SHOW_ALERT('Payment_Type_Alert'); END IF; END IF; END; I'm new to oracle forms so I'm not sure if I have a missing setup or anything. S_ORD table exist and has a column payment_type, which consists of 'CREDIT' and 'CASH' value. Thank you. sql forms oracle variables bind share|improve this question asked Jul 5 '12 at 3:39 mysticfalls 12511222 The IF statement references :S_ORD.payment_type, which isn't declared/etc before. It's seen as a BIND variable because of the colon ":". How are you attempting to run this? A script is the only way that makes sense to me ATM. –OMG Ponies Jul 5 '12 at 3:49 @OMG Ponies I'm executing a form named ORDERS...should this be declared or is there anything else I can check that may cause this error..thanks –mysticfalls Jul 5 '12 at 4:07 I don't know Forms, sorry –OMG Ponies Jul 5 '12 at 4:26 add a comment| 4 Answers 4 active oldest votes up vote 0 down vote Oracle Forms doesn't allow the use of bind variables when the code is in a library or a menu. Here is a quote from the Orac
onXXXXXXXdata block... Compilation error on KEY-NXTBLK trigger onXXXXXXXdata block: PL/SQL ERROR 49 at line 1, column 1 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 1, column 1 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 3, column 1 bad bind variable 'parameter.G_query_find' Compiling WHEN-NEW-BLOCK-INSTANCE trigger on XXXXXXX data block... Compilation error on WHEN-NEW-BLOCK-INSTANCE trigger onXXXXXXXdata block: PL/SQL ERROR 49 http://stackoverflow.com/questions/11337582/error-49-bad-bind-variable-oracle-forms at line 3, column 2 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 3, column 2 bad bind variable 'parameter.G_query_find' PL/SQL ERROR 49 at line 5, column 2 bad bind variable 'parameter.G_query_find' ....Compilation errors have occurred. Form not created ********************** Cause :FORMS60_PATH not properly set or incorrect http://www.oracleebs.net/2011/07/forms-error-bad-bind-variable.html Solution: SetFORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource In your shell simply execute FORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource This should solve the problem Posted by Ranjith prabu at 4:12:00 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: f60gen, FORMS60_PATH, Oracle applications, parameter.G_query_find 4 comments: NataliaFebruary 17, 2012 at 7:20 AMI do have encountered these errors many times and finally found a solution and the reason behind it through your post. I tried to manipulate so many things to remove this error but everything failed. Thanks for suggesting this nice solution.sap software trainingReplyDeleteRanjith prabuFebruary 17, 2012 at 9:57 PMNatalia. Happy that it helped you..ReplyDeleteBlue_23July 4, 2012 at 1:52 AMHello,I am new to oracle.. I would like to ask what do you mean by this.."In your shell simply executeFORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resource"How is this done?Thank you.ReplyDeleteRepliesRanjith prabuAugust 29, 2012 at 4:00 PMHi Blue, Sorry for the late reply. If you are still facing the problem :
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You https://community.oracle.com/thread/487509 can not post a blank message. Please type your message and try http://oracleappstechnology.blogspot.com/2009/03/forms-compilation-errors.html again. More discussions in LCM: Managing Oracle Applications All PlacesOracle ApplicationsE-Business SuiteE-Business Suite TechnologyLCM: Managing Oracle Applications This discussion is archived 7 Replies Latest reply on Sep 8, 2008 2:16 PM by 658649 Branched to a new discussion. TEMPLATE.fmb - no fields show up 139072 Mar 14, 2007 6:05 PM Hi, bad bind I'm trying to develop a custom form but having trouble with the template. 1. Copy template to my directory in Unix and compile. 2. I run it through the applications but no fields show up on the template. Is this normal? I don't think it is but I haven't created a new form from the template in a couple of years. 3. Messing around bad bind variable with the form I removed the sub-class and was able to get a couple of fields to display but I changed so many things I don't seem to be able to duplicate. And I really want to be able to use the standard sub-classes which still didn't work when I set the fields manually. Thanks for any help. Andy ................................ Additional information: I've also concluded that when I compile an existing form FNDSCAPP.fmb errors occur so it is not limited to the template.fmb. See error below, there was only one. Any ideas as to what would cause this? Compiling PRE-INSERT trigger on APPLICATION data block... No compilation errors. Compiling PRE-QUERY trigger on APPLICATION data block... Compilation error on PRE-QUERY trigger on APPLICATION data block: PL/SQL ERROR 49 at line 1, column 5 bad bind variable 'parameter.g_query_find' PL/SQL ERROR 49 at line 1, column 5 bad bind variable 'parameter.g_query_find' PL/SQL ERROR 49 at line 3, column 3 bad bind variable 'parameter.g_query_find' Compiling PRE-UPDATE trigger on APPLICATION data block... No compilation errors. Message was edited by: Andy123 4387Views Tags: none (add) This content has been marked as final. Show 7 replies
parameter.G_query_find Recently all custom forms compilation failed with errors like these:FRM-18108: Failed to load the following objects.Source Module:APPSTAND Source Object: STANDARD_PC_AND_VASource Module:APPSTAND Source Object: STANDARD_TOOLBARSource Module:APPSTAND Source Object: STANDARD_CALENDARCompiling package specification APP_CUSTOM... No compilation errors.orCompiling KEY-NXTBLK trigger on QUERY_FIND data block...Compilation error on KEY-NXTBLK trigger on QUERY_FIND data block:PL/SQL ERROR 49 at line 1, column 1bad bind variable 'parameter.G_query_find'PL/SQL ERROR 49 at line 1, column 1bad bind variable 'parameter.G_query_find'PL/SQL ERROR 49 at line 3, column 1bad bind variable 'parameter.G_query_find'It turned out that FORMS60_PATH was not set correctly. Whenever forms are compiled FORMS60_PATH is set to:FORMS60_PATH=$FORMS60_PATH:$AU_TOP/forms/US:$AU_TOP/resourceIn context file it was set as:$AU_TOP/resource:$AU_TOP/resource/stubAfter correcting this and compiling manually it worked. To make this permanent change the s_f60path to include $AU_TOP/forms/US:$AU_TOP/resource Posted by Vikram Das at 9:32 AM Labels: FRM-18108, parameter.G_query_find 2 comments: Galarza said... thanks June 29, 2009 at 11:43 AM Anonymous said... Hi i am facing the same problem FRM-18108: Failed to load the following objects. Source Module:APPSTAND.fmb Source Object: STANDARD_FOLDERSource Module:APPSTAND Source Object: STANDARD_PC_AND_VASource Module:APPSTAND Source Object: STANDARD_TOOLBARSource Module:APPSTAND Source Object: STANDARD_CALENDARCompiling package specification APP_CUSTOM... No compilation errors. Compiling package specification XXFIN_GBL_CREDITMEMO_PKS... No compilation errors. Compiling package specification XXFIN_GBL_QUERY_PKS... No compilation errors. Compiling pac