Skip to main content

Hi Community,

I hope you can assist with an issue I am having with Aurena Apps10 UP9.  I have created a Custom Projection based upon a Custom LU.  I have defined my Custom Projection as shown below:

Custom Projection

I have then defined a Custom Page based upon this projection which is a simple overview screen which works fine logged in as the App Owner.  Everything is synced and published:

Custom Page Configuration

I now want to grant access to this new page to an end-user via a permission set.  I have created a new permission set and can grant my custom projection to it but the problem is that it says there are no associated pages:

It claims that there are no pages defined for the Projection…
​​​​​​

The result is my end-user cannot access the new custom page.  When I click Manage By Page option I cannot see my Custom Page “TestLu” listed and I cannot grant access to it.

Has anyone else encountered this problem?

Regards

Mike, 

We’re you able to find out what the problem is? I am having the same issue. 
 

Appreciate if you could share your fix for this if you have one already. 
 

Thanks, 

A

Hi Ayaan,

After some investigation I found that when I defined my custom page against my custom projection the view FND_PROJECTION_USAGE was not populated.  This view appears to link your custom page to the projection.  The workaround manually adds that missing record to the view.  Please note, I have only deployed this to a test environment and it is not an official fix but it does work!  In the meantime I have raised a case with IFS.

Workaround for Granting Access to a Custom Page in Aurena (Apps10 UPD9)

To add missing information to FND_PROJECTION_USAGE run the script below as IFSAPP (note you need to change the attribute values according to your own circumstances)

DECLARE

   info_ VARCHAR2(4000);
   attr_ VARCHAR2(4000);
   objid_ fnd_projection_usage.objid%TYPE;
   objversion_ fnd_projection_usage.objversion%TYPE;
   
BEGIN
   
   Client_SYS.Clear_Attr(attr_);
   Client_SYS.Add_To_Attr('PROJECTION_NAME', 'TestProjection', attr_);
   Client_SYS.Add_To_Attr('CLIENT', 'TestLu', attr_);
   Client_SYS.Add_To_Attr('ARTIFACT_NAME', 'TestLuPage', attr_);
   Client_SYS.Add_To_Attr('ARTIFACT', 'page', attr_);
   Client_SYS.Add_To_Attr('ARTIFACT_LABEL', 'Test Lu', attr_);
   
   Fnd_Projection_Usage_API.New__(info_, objid_, objversion_, attr_, 'DO');
   
END;

Where the attribute values are derived from:

PROJECTION_NAME attribute value
CLIENT attribute value​​​
ARTIFACT_NAME attribute value
ARTIFACT_LABEL attribute value

ARTIFACT attribute value is hard coded to “page”.

Once script has been run system now reports that my Custom Projection has a related page when granting access to a permission set.

No of Pages is now correctly reported

I can now manage my grant using the Manage by Page function:

Can now search for my Custom Page
Set access level for custom page

To make available to an end-user I then use the Navigator Designer to add a navigator option for my new page:

Add navigator option for custom page

Finally, I need to grant access to that navigator option to my permission set:

Use Manage by Navigator option
Edit access for new navigator option

Once permission set has been granted, end-user should now see new navigator option and custom page.

Hope this helps.  I'll update further when I get an official fix from IFS.

Regards,

Terms & ConditionsCookie settings