Login
Register

Home

Trainings

Fusion Blog

EBS Blog

Authors

Contact Us

All Financials Functional Documents
  • Register

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

webinar new Click here to raise Support Ticket. Get reply within 48 hours.

Search Courses

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
 
The attachment functionality via personalization has got two limitations. The first limitation has a workaround and second limitation has some proper solution. What are these limitations and how can we overcome those? We will discuss those in this article. The first limitation is that you can specify only one primary key when defining attachments via personalization. For example if you wish to capture attachments against a combination of PO Header Id and PO Line Number, then in such a case you will not be able to implement this requirement via personalization. It must be noted that this is just an example, because in real life you would rather use po_line_id as the primary key. But in some project cases we do need composite primary key to identify the attachments. The second limitation is that the view object attribute that is used as a primary key of attachment must have a value populated in it, otherwise you cannot upload the attachments. It sounds obvious that you need a primary key value to attach documents against it. This is logical because you must have the transaction_id in place before you can load attachments against that transaction. However in reality, most of the screens generate the primary key just prior to the commit taking place, which means attachments can not be uploaded until after the save/apply button has been clicked by the user.
 
In this article we will discuss the possible solutions for both these limitations
Limitation 1
When you create a new item using personalization, at the time of creating primary keys, you will notice that personalization framework does not allow more than one primary key.  
 
However, using jDeveloper, you can create a combination of 5 columns/attributes as a primary key.
 
 
In order to overcome this you have two options
Option 1 
Extend the controller and get a handle to the attachment bean. Programmatically create instances of primary key bean and attach to the attachment bean. This can be done by extending the controller.
 
Option 2
Create a stacklayout region in JDeveloper to create attachment item with multiple primary keys. Once this stacklayout has been developed, upload this region to MDS and embed the same into standard page. You 
 
can use this article to see how custom regions can be embedded within the standard regions.
http://apps2fusion.com/apps/oa-framework/151-oa-framework-screen-extension-by-embedding-a-custom-page
 
 
 
Limitation 2
In most cases, the primary key is generated "just prior" to the data being inserted into the tables. For example, if you are creating an employee record and if your business requirement is to allow users to 
 
upload documents when creating employee record, then such requirement is not feasible if employee_id gets generated after the user has applied the data in the screen. Of course some pages might be designed 
 
so as to generate the primary keys for the record at the time of data entry itself.
 

Anil Passi

Comments   

0 #1 prada Shoulder bags 2010-06-28 03:43
Your technology is so terrific!
I know an online store which has a lot of XX in this style, they are suit you very much,can reveal your personality better!
Go to have alook when some time left, there must be many surprises!,www. prada-outlet-st ore.com/prada-w allets.html
Quote
0 #2 LoweryLESLEY20 2010-07-15 17:05
I had a dream to start my company, however I did not have enough of money to do this. Thank goodness my close friend advised to utilize the loan. Thence I received the credit loan and made real my dream.
Quote
0 #3 Pooja 2010-07-21 05:45
Hi,

I have added attachment feature in Notification page using personalization .Used summary layout region for personalization (View object :AsgSummaryVO
and primary key: EmployeeNumber) .It is added in SIT.
As an example, employee raises a request in SIT which goes for approval to manager. The personalization allows manager to add attachment and approves it.
This approval will follow futher hierarchy.
Now the error comes when Employee is raising a new SIT request. The attachements which were added my manager is also visible at employee summary layout.

How can we restrict it?

How can we use transaction ID for complete hierarchy as the primary key??
Quote
0 #4 Vish 2010-10-04 02:34
Hi ,
Can any one help me to solve the following problem.
Actual ly in real business scenario , I would like to upload automatic attachment against the sales order line in form of Web Page(
This means whenver a user enters sales order line by default some url (web page) should get attach to it).
how should I achieve this.?
Quote
0 #5 Ahmed_Oracle 2011-07-19 02:07
Is there any way that we can show the same attachment in OAF page which I inserted from Oracle Forms say Quick sales order form. I see that from Forms, It is checking function security. Where as OAF page is referring to some other VO which is not at all checking form function functionality.. .Any Help on this would be appreciated..
Quote
0 #6 Pavanib 2012-04-25 01:51
how to overcome the second limitation, could you help me.
Quote

Add comment


Security code
Refresh

Search Trainings

Fully verifiable testimonials

Apps2Fusion - Event List

<<  Aug 2021  >>
 Mon  Tue  Wed  Thu  Fri  Sat  Sun 
        1
  2  3  4  5  6  7  8
  9101112131415
16171819202122
23242526272829
3031     

Enquire For Training

Fusion Training Packages

Get Email Updates


Powered by Google FeedBurner