FND Responsibility Upload

FND Responsibility Upload creates and updates Oracle E-Business Suite responsibilities directly from Excel, and maintains their menu and function exclusions – the same definitions you would otherwise enter one at a time in the System Administrator Responsibilities form. In a single template you can define new responsibilities (application, key, name, effective dates, data group, menu, request group and more) and, on separate rows, exclude specific menus or functions from those responsibilities. It is also a quick way to review existing responsibilities and their exclusions.

When to use it

• Create responsibilities in bulk – define many new responsibilities in one pass.
• Update responsibilities – change the name, description, menu, request group, data group or effective dates.
• Maintain menu and function exclusions – add or remove the menus and functions a responsibility must not access.
• Disable a responsibility – set an Effective Date To (responsibilities are never deleted).
• Download and review existing responsibilities and their exclusions without uploading any changes.

Before you start

• Blitz Report is installed and you are signed in to a responsibility with System Administrator level access (the one that opens the Responsibilities form).
• Any Application, Data Group, Menu, Request Group, function or menu you reference already exists – each value is validated against its list.
• You know each responsibility’s Key – the short internal identifier that is fixed once the responsibility has been created.

Step 1 – Open the upload and choose a mode

Run FND Responsibility Upload from the Blitz Report menu and choose an Upload Mode:

• Create – an empty template for defining brand-new responsibilities.
• Create, Update – downloads existing responsibilities (and their exclusions) so you can review or change them.

Each row is automatically treated as a create or an update by checking whether the responsibility (Application plus Responsibility Key) already exists – you do not set an action yourself.

Step 2 – Set the parameters and download the template

In Create, Update mode the parameters limit what is downloaded:

Step 3 – Choose a Row Type

Every row has a Row Type that says what it defines:

• Responsibility – the row creates or updates a responsibility.
• Menu/Function Exclusion – the row adds or removes one menu or function exclusion for a responsibility.

Both row types start with the same two columns – Application and Responsibility Key – which identify the responsibility the row applies to. When you create a new responsibility and its exclusions in the same file, put the Responsibility row above its Menu/Function Exclusion rows so the responsibility exists before its exclusions are processed.

Step 4 – Define a responsibility (Responsibility rows)

On a Responsibility row, enter Application, Responsibility Key, Responsibility Name and an Effective Date From (required), plus the Data Group, Data Group Application and Menu. Available From defaults to Oracle Applications and can be switched to Oracle Self Service Web Applications or Oracle Mobile Applications. Optionally add a Description, an Effective Date To to disable the responsibility, a Request Group (with its Request Group Application), and Web Host / Web Agent Name. The Responsibility Key is fixed once created – to rename a responsibility, change its Name, not its Key.

Step 5 – Add or remove an exclusion (Menu/Function Exclusion rows)

On a Menu/Function Exclusion row, identify the responsibility with Application and Responsibility Key, then set Exclusion Type (Function or Menu) and Exclusion Name (the function or menu to exclude). Leave Exclude blank to add the exclusion; set Exclude to Yes to remove it. Adding an exclusion that already exists, or removing one that is not there, is reported as “No change.”

Step 6 – Validate and Save

Click Validate and Save. This checks for missing required values and runs any extra validation the upload defines, then saves the file. Correct anything it flags before continuing.

Step 7 – Upload and view the result

Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which processes each row independently. When it finishes, a result report opens showing each row as success or error with a message.

What’s produced

• New or updated responsibilities – including their translated name and description, data group, menu, request group and effective dates – and their menu and function exclusions.
• A result report listing every row with a status (success or error) and a message, for example “Responsibility created.”, “Responsibility updated.”, “No change.”, “Exclusion added.” or “Exclusion removed.”, so you can see which rows succeeded and why any failed.

Common questions

How do I rename a responsibility?
Change its Responsibility Name and keep the Responsibility Key the same. Editing the Key creates a different responsibility, because the Key is the stable identifier that never changes once a responsibility is created.

How do I disable a responsibility?
Set an Effective Date To. Responsibilities are not deleted by this upload, because they are referenced by users, concurrent requests and grants.

How do I exclude a menu or a function?
Add a Menu/Function Exclusion row for the responsibility, set Exclusion Type to Menu or Function and pick the Exclusion Name. To restore access later, set Exclude to Yes on the same exclusion.

Do the Responsibility row and its exclusions have to be in the same file?
No, but they can be. If you create a responsibility and its exclusions together, put the Responsibility row first so the responsibility exists before its exclusion rows are processed.

What is Data Group Application?
A responsibility’s Data Group has both a name (usually Standard) and an application whose database schema it uses. Choose the Data Group first; the Data Group Application list then shows the applications valid for that data group.

Do I need to fill in Request Group or Web Host / Agent Name?
No. Request Group is optional – if you use it, enter both the Request Group and its Application together. Web Host and Web Agent Name apply only to older self-service setups and are normally left blank.

Troubleshooting