Further Person Information not Displaying on People | Enter And Maintain Form

Oracle Human Resources - Version: 11.5.10
Issue with Perwshrg.fmb , further person information DDF

Problem:

further person information DFF modifications means display different information are not displaying under the Employment Tab of the People Form.This is restricted functionality.

Solution :

Further person Information flexfield is not a Descriptive Flexifield it's a Developer Descriptive Flexifield. This is a restricted functionality.

Developer Descriptive flexfields are reserved for Development & should not be modified.You can see this flexfield information for 'US' legislation's , in PUI on person form, inthe 'Empolyment' tab,All fields with in this tab belongs to this flexifield.

By
Srinivas Ramineni
Oracle APPS DBA

Purging Related to SYS ADMIN & WORKFLOW

This document describes archiving across applications, how to submit the purge processes, purging criteria for records, what information does and does not get purged, the tables information is purged from and how to restore archived information.

System Administration

Archiving Audit Data:

Auditing is the main feature that produces high impact on Applications But it is a very useful tool use it with proper planning.

Disable auditing using the “Disable – Prepare for Archive” and running the Audit Trail Update Tables report.

Archiving it.

Set the Archive group to Disable Purge Table and running the Audit Trail Update tables report.

Purge Concurrent Request and/or Manager Data:

Use this program to delete:

1. Request log files, concurrent manager log files, ad report output files from your product directories maintained by the operating system

2. Records (rows) from Application Object Library database tables that contain history information about concurrent requests and concurrent manager processes.

Use this program to compute performance statistics for each of the concurrent programs, if the Concurrent: Collect Request Statistics profile option is set to “Yes”.

Purge Signon Audit Data:

Use this program to purge Sign-On Audit information created before a specified date.

The following data is deleted:

1. Data for who signs on and for how long

2. Data for who is selecting what responsibility and when they do it

3. Data for who uses which forms in an application and when

Purge Obsolete Generic File Manager Data:

To purge uploaded files form the Generic File Manager, run the concurrent program, Purge Obsolete Generic File Manager Data.

This concurrent program should also be used to periodically delete obsolete data. It is recommended that you schedule this program to run every day or so, using the default parameter values.

Workflow

To purge the workflow runtime tables use the standard concurrent program FNDWFPR ”Purge Obsolete Workflow Runtime Data”.

Instructions

Navigate to the Submit Requests form in Oracle Applications to submit the Purge Obsolete Workflow Runtime Data concurrent program.

You can supply the following parameters for the Purge Obsolete Workflow Runtime Data concurrent program:

Item Type----The item type to purge. Leaving this field blank defaults to purging the runtime data for all item types.

Item Key----The item key to purge. Leaving this field blank defaults to purging the runtime data for all item keys.

Age----Minimum age of data to purge, in days.

Persistence Type----The persistence type to be purged, either ’TEMP’ for Temporary or ’PERM’ for Permanent. The default is ’TEMP’.

Note: If you have implemented Oracle Applications Manager, you can use Oracle Workflow Manager to submit and manage the Purge Obsolete Workflow Runtime Data concurrent program.

By
Srinivas Ramineni
Oracle Apps DBA

Provide Access to "AME Tranaction Types" to a user

Hi,
This is Srinivas Ramineni.

These steps flourishes the way to "How to Provide Access to "AME Tranaction Types" to a user

1) AME restricts access to "AME Transaction Types" using Data Security. To access AME and useit,the user needs to select a transaction type. But the transaction types that the user can select inthe AME Dashboard is restricted by data security.

2) Access to AME transaction types to a user can be setup as follows:
· Login as Administrator
· Select Functional Administrator responsibility
· Select Grants Tab
· Click on Create Grant
· Select "Specific User" as grantee type
· Select the User as grantee key
· Select "AME Transaction Types" as object
· In the next page there will be 3 options for instance type:
1. All rows: This grants access to all AME Transaction Types to the User

2. Instance: This grants access to the AME Transaction Type(1) specified by the following parameters:

FND_APPLICATION_ID => Application ID of the application to which the transaction type belongs

TRANSACTION_TYPE_ID => Unique identifier of the AME Transaction type within application

3. Instance set: This grants access to AME Transaction Types(>=1) specified by the following parameters:

* Use the seeded instance set "AME Transaction Type Instance Set"

* In the next page select FND_APPLICATION_ID as Parameter1 and a wild card search string for TRANSACTION_TYPE_ID as Parameter2.

In the next page, select "AME Calling Applications" as the permission set
· Review and Finish.

NOTE: Please note that it is possible that AME screens fail to appear for the user even after doing the above setup. This can happen if the workflow event system is not properly setup.

If u have any doubts please feel free to contact.