Sunday, February 14, 2021

How to fix Buyer page issues in R12.2.8

In R12.2.8, many of the seeded OAF pages now have a sort of 'Infinite Scroll' feel for table based data sets. While this is a nice to have change, it sometimes hinders some of the seeded functionalities and there has not been a concrete solution to overcome this.


One of such places is the Buyers page in Purchasing where we can see all existing buyers as well as create new ones. Since the 'Infinite Scroll" has been baked into this page as a default scrolling format, we have been encountering issues in creating new buyers. This issue is so annoying that at times we were just unable to create new buyers.


Below are the details of the issue and the solution to overcome it. I hope it helps many of you who might be facing similar issue on Buyer page in 12.2.8.

In fact, this solution can be applied to any page in 12.2.8 as needed.


Issue details -


In 12.2.8, click on Add Buyer (+) Button as shown below -



Once clicked, the list of existing Buyers is loaded and cursor automatically goes to highlighted field and not to the empty row where we should be entering new buyer details –





Sometimes the blank row cannot be found anywhere even if we scroll up or down.

At times, it's seen somewhere on top or in the middle or even end of the list but it’s very inconsistent and at times simply doesn’t work.

Also, if users click + sign multiple times (assuming it didn't work in first attempt), then it adds multiple blank rows making the form completely unusable as it prevents you from saving your entry because it expects you to populate values in all blank rows (generated by multiple clicks) and there is no delete option to get rid of these blank rows.



Issue fix -


The only way of fixing this buggy behavior is to personalize the page in question. Please follow below steps to do so.


1. Personalize Buyers Table on Buyer page -


2. Personalize Advanced Table: Buyers Table -


3. Set ‘Row Navigation Policy’ to ‘Page’ at desired levels (Default is Scroll) -


4. Click Apply and Return to Application


5. Now if you click on + sign to add a new buyer, the new blank row will appear on top and the frame will show Previous and Next options and eliminating the above issue. This can be done on any other pages as needed.




Hope this helps you in fixing the issues caused by Scroll navigation policy in 12.2.8 pages. You can implement this solution on any 12.2.8 OAF page to revert to page level navigation.

Share:

Thursday, January 21, 2021

Make Interactive Grid work like Excel or Google Sheets in Oracle APEX

Interactive grid (IG) is arguably one of the best components available in newer versions of Oracle APEX. IG is an awesome blend of a form and an interactive report that lets users view the data in IR format as well as make DML operations (CRUD) to the dataset.


By default, user needs to explicitly click the Save button after each change made in the IG...but what if you want to make IG behave like an online excel or google sheet where all the changes are automatically saved ?


We can certainly do this by incorporating below changes. Lets see the steps -


1. First, assign a static ID to your Interactive Grid e.g. ig_test


2. Now, lets create a Dynamic Action on this IG and set event details as below -

Event - Change

Selection Type - Region

Region - <IG region>


3. For the True event of this DA, select Action as Execute JavaScript Code -


4. Enter below JS code. Note - Here we've used static ID of our IG (ig_test) to invoke Save action.

apex.region( "ig_test" ).widget().interactiveGrid( "getActions" ).invoke( "save" );


5. Save and run the application.

Now, as soon as you make any modifications to the data and navigate to the next item by tabbing out or with a mouse click, you'll see the changes are automatically saved and standard 'Changes saved' message is shown.


By implementing this solution, users don't have to click Save button every time they make any changes in Interactive Grid and it delivers an experience that's very close to Excel online or Google Sheets.

Share:

Wednesday, January 6, 2021

Deployment process for OAF controller classes in R12.2.x

 - When it comes to deployment of OAF classes, R12.2.x moves away from conventional Oracle Applications Server setup to Weblogic server and jar concept comes into the picture.

- Here are the steps to follow to deploy controller classes in 12.2 –

1. Move the controller class file to the desired product top under JAVA_TOP

(e.g. $JAVA_TOP/oracle/apps/xxcustom/oracle/apps/icx/por/req/webui)


2. Attach extended controller to OAF page via personalization


3. Generate the product jar file. This can be done by running ‘adcgnjar’ utility in UNIX.

This needs WebLogic credentials so DBA team needs to perform below task -


Run adcgnjar utility and regenerate product jar file (customall.jar) for <product> (e.g. XXAP)

adcgnjar generates and signs a file named customall.jar file containing the custom Java and BC4J code and extensions. The customall.jar file resides on $JAVA_TOP as indicated by CLASSPATH.


It internally performs the following steps:

- Creates a temporary custom.zip file that contains all the directories under $JAVA_TOP except the oracle, META-INF, and policies directories.

- Generates and signs the customall.jar file with the contents of the custom.zip file.

- Deletes the temporary custom.zip file.

4. Bounce oacore and apache server, as needed.


Please note, since introduction to WebLogic in 12.2, adcgnjar utility and oacore bounce require WebLogic password, hence usually DBA team performs these two tasks.

Share:

Friday, December 11, 2020

Creating and maintaining Custom Tables in R12.2.x

 1. To create a custom table in custom schema – XXCUSTOM

CREATE TABLE XXCUSTOM.TABLE_NAME (COL1 NUMBER,….);


2. To generate editioning view and synonym for the table execute below script


exec AD_ZD_TABLE.UPGRADE('XXCUSTOM','TABLE_NAME');


This will create two new objects:


(i) An editioned view (having # in the end) in XXCUSTOM schema (e.g. XXCUSTOM.TABLE_NAME#)

(ii) A synonym (same as table_name) in APPS schema (APPS.TABLE_NAME)


3. If you alter the table definition in future then after running the alter table command, run below script to regenerate the editioning view and sync the table changes -


exec AD_ZD_TABLE.PATCH('XXCUSTOM','TABLE_NAME');


4. To see the objects across all editions, please query all_objects_ae or user_objects_ae


SELECT * FROM all_objects_ae WHERE OBJECT_NAME like 'TABLE_NAME%';


5. To issue Grants/Revokes use below commands (Please request DBA team to execute below commands):


Connect to XXCUSTOM schema and run below commands -

grant <grant> on XXCUSTOM.TABLE_NAME to APPS WITH GRANT OPTION;


grant <grant> on XXCUSTOM.TABLE_NAME# to APPS WITH GRANT OPTION;


Connect to APPS and run below commands to perform Grant or Revoke operations –

execute APPS.AD_ZD.GRANT_PRIVS('<grant>','TABLE_NAME','<SCHEMA_RECEIVING_GRANT');


execute

APPS.AD_ZD.REVOKE_PRIVS('<grant>', 'TABLE_NAME','SCHEMA_TOBE_REVOKED');


Share: