Disable Forms Personalization

-
Sometimes when you are developing a Forms Personalization it will error out before the form is opened. When this happens you cannot disable custom code to get the form to open and fix the problem.

The easiest way to fix this is to disable it directly in the core table.
UPDATE fnd_form_custom_actions SET enabled = 'N' WHERE action_id = your action id;
Now your form will open and you can fix the problem.

Comments

Post a Comment

Popular posts from this blog

How to create a custom integration interface in SOA Gateway

-
Image
This example will illustrate on how to develop a simple interface using PL/SQL. The Integration Repository will recognize integrations through annotations in the code (details about annotations can be found in the Integrated SOA Gateway Developer's Guide, Appendix A). You can annotate *.pls and *.pkh files. For PL/SQL packages, only the package spec should be annotated. Do not annotate the body. Example of a annotated package spec: CREATE OR REPLACE PACKAGE xx_test_soagway AS /* $Header: $ */ /*# * This package returns different data from Financials (GL). * @rep:scope public * @rep:product gl * @rep:displayname xx_test_soagway * @rep:lifecycle active * @rep:compatibility S * @rep:category BUSINESS_ENTITY GL_ACCOUNT_COMBINATION */ /*# * Returns CCID * @param P_SEGMENT1 varchar2 Segment 1 * @param P_SEGMENT2 varchar2 Segment 2 * @param P_SEGMENT3 varchar2 Segment 3 * @param P_SEGMENT4 varchar2 Segment 4 * @param P_SEGMENT5 varchar2 Segment 5 * @return CCID ...
Read more

Status of a customer

-
Image
One of my clients who run the Finance modules (AR, ARP, GL etc), Service Contracts and Field Service in E-Business Suite R12 had some issues with customers who were inactive. The issue arised when they were creating Service Requests (through API cs_servicerequest_pub.Create_ServiceRequest) and got an error reported by the API that the request could  not be created due to the customer was invalid. The reason that a customer is invalid can vary but one reason is that some level of the customer is inactive. In AR and the TCA model the customer (party) status can be set in the following tables: hz_parties (TCA) hz_party_sites (TCA) hz_party_site_uses (TCA) hz_cust_accounts (TCA-AR) hz_cust_acct_sites_all (TCA-AR) hz_cust_site_uses_all (TCA-AR) In my clients case status was Active in all tables except  hz_party_site_uses . Below I will explain how it's possible to change the statuses. Set status in Account Receivables If you inactivate an Account Site Address/Acc...
Read more

Fix for java.sql.SQLException: Invalid column type when extending a VO

-
Image
When you are extending a view object (VO) in OA Framework it's possible that you will run in to the problem  java.sql.SQLException: Invalid column type , especially if it's an LOV VO you are trying to extend. When you click on the LOV torch for the first time it is working fine. But whenever you click on the GO button in the LOV Region it gives an error. The error can look like this: oracle.apps.fnd.framework.OAException: oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation.   Statement: SELECT * FROM (SELECT ca.location LocId, ca.party_site_number LocNumber, ca.party_name PartyName, ca.party_number PartyNumber, ca.address1 Address1, ca.address2 Address2, ca.address3 Address3, ca.address4 Address4, ca.city City, ca.state State, ca.zip PostalCode, ca.country Country, ca.party_id partyId, hzp.site_use_type CurrSiteUsage FROM csi_hzpty_addresses_v ca, hz_party_site_uses hzp, hz_cust_acct_sites_all hcas, hz_cust_site_uses_all hcsu W...
Read more