Extending and Customizing the Mobile PO Receipt form

Authors

Oracle Gold Partners, our very popular training packages, training schedule is listed here
Designed by Five Star Rated Oracle Press Authors & Oracle ACE's.

Search Courses

Details: Published: 28 February 2009

A recent project required me to extend and customize the PO Receipt page in the MWA MSCA. The extension of the RcptGenPage and RcptGenFListener was a little more complicated than some of the examples you see out there. It requires a lot more customization and bringing over oracle seeded attributes and private methods. It also requires you to have patience and using the trace debugging method that MWA provides. In this article I hope to help you learn more about how I was able to get this extended and customize the page to allow for a new field and calling pl/sql functions/procedures from within the mobile application.

Source code is available here

The business requirement was pretty simple, but the task was quite daunting. I needed to display an “Item Weight” field after the population of the “Item Number” LOV was populated. The item weight field is required and pre-populated from the item master table (if it exists). The most difficult task for me to do was actually getting the standard functionality of the PO Receipt page implemented. It always seemed to call the original seeded Listener code instead of my listener. I couldn’t figure out why until I brought over every “Private” method that the original listener used. Once I was able to do this it would make a call to my listener first.

Up until now all the code has been “extended” from the oracle seeded receipt pages. Now the customized code processing of this customization starts at the Item text field. When the Item LOV is exited it calls a method fieldExited(). This determines if the INV.ITEM LOV field was the field that was exited. Since it was it called my page code to actually “display” it, then it calls my custom itemExitedX() method. Note, that this method is copied directly from the Oracle seeded code, but has been changed just be executed specifically for the PO RECEIPT page. If you want to implement it for different pages (ie. RMA) then you’ll need to copy it over and insert debug statements to find out its flow through the method call.

Within the itemExitedX() method it does some code handling to determine if the mOrigitemWeightValue variable has been populated. If it hasn’t then it executes another custom method setItemWeight(). This call actually uses a CallableSTatement to call a function I created to pass in the item and return the “unitWeight” stored in the item master table.

Now when the item weight field is modified and exited it always calls another custom method called updItemWeight(). This is called in the locationEntered() method because it is the field that is entered when the Item Weight field is exited.

This is about the gist of the customization I needed to do for the PO Receipt form. If you look through my code you may have done some things different and you may need to change the way things are done. If you know other ways (maybe more efficient ways) to do things please let me know. I always want to learn better ways to do things. We all know that the documentation out there isn’t all that great and doesn’t work for every customization we need to do.

If you need consulting help in MSCA/MWA extensions/OAF customizations or any other consulting needs please contact us. You can also visit us at www.luciditycg.com

Materials & Mfg  Receipts  PO

Kyle Thomas

Comments

0 #1 Rohini 2009-02-28 16:28

Excellent work Kyle.

Thanks and Regards,
Senthi l

<< Apr 2024 >>
Mon	Tue	Wed	Thu	Fri	Sat	Sun
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30

Home

Trainings

Fusion Blog

EBS Blog

Authors

CONTACT US

Search Courses