WFLOAD syntax for UPLOAD and DOWNLOAD

1. Navigate to the Submit Requests form in Oracle Applications to submit the Workflow Definitions Loader concurrent program. When you install and set up Oracle Applications and Oracle Workflow, your system administrator needs to add this concurrent program to a request security group for the responsibility that you want to run this program from.

2. Submit the Workflow Definitions Loader concurrent program as a request.

3. In the Parameters window, enter values for the following parameters:

Mode         Specify "Download" to download a process definition from the database to a flat file.
        Specify "Upgrade" to apply a seed data upgrade to a database from an input file. The Workflow Definitions Loader assumes the access level of the file's creator (seed data provider) and overwrites any objects protected at a level equal to or above the upgrade file's access level. The Loader program preserves any customizations made to customizable seed data in the database.
        Specify "Upload" to load a process definition from a flat file into the database. The upload mode is useful to someone who is developing a workflow process. It allows the developer to save definitions to the database without concern that accidental customizations to existing objects might prevent the upload of some process definition elements. The Workflow Definitions Loader uses the access level defined by the input file to upload the process definitions from the file and therefore will overwrite objects in the database that are protected at a level equal to or higher than that file's access level.
        Specify "Force" to force an upload of the process definitions from an input file to a database regardless of an object's protection level You should be certain that the process definition in the file is correct as it overwrites the entire process stored in the database. The Force mode is useful for fixing data integrity problems in a database with a known, reliable file backup.

File         Specify the full path and name of the file that you want to download a process definition to, or upgrade or upload a process definition from.

Item Type     If you set Mode to "Download", use the List button to choose the item type for the process definition you want to download.

4. Choose OK to close the Parameters window.

5. When you finish modifying the print and run options for this request, choose Submit to submit the request.

6. Rather than use the Submit Requests form, you can also run the Workflow Definitions Loader concurrent program from the command line by entering the following commands:

    To upgrade-- WFLOAD apps/pwd 0 Y UPGRADE file.wft

    To upload-- WFLOAD apps/pwd 0 Y UPLOAD file.wft

    To force-- WFLOAD apps/pwd 0 Y FORCE file.wft

    To download-- WFLOAD apps/pwd 0 Y DOWNLOAD file.wft ITEMTYPE1 [ITEMTYPE2 ...ITEMTYPEN]

    Replace apps/pwd with username and password to the APPS schema, replace file.wft with the file specification of a workflow process definition file, and replace ITEMTYPE1, ITEMTYPE2, ... ITEMTYPEN with the one or more item type(s) you want to download. You can also download all item types simultaneously by replacing ITEMTYPE1 with '*' (make sure you enclose the asterisk in single quotes).

Responsibilities missing in Oracle Applications

Some Tested hints

1. Make sure that the latest ATG_RUP patch has been applied.
2. Run Concurrent Program System: Administrator Responsibility->Request->'Synchronize WF LOCAL tables'
3. Run Concurrent Program: 'Workflow Directory Services User/Role Validation'. (with the parameters 10000,Y,N,N and 10000,N,Y,N)
4. Restart the Workflow Agent Listeners: WF_DEFERRED and WF_JAVA_DEFERRED

Check the responsibilities for the user, if the issue still exist do the following steps

1). Run the following script to check if there is a discrepancy between the tables:

select ura.user_name, ura.role_name
from wf_local_user_roles ur, wf_user_role_assignments ura
where ur.user_name = ura.user_name
and ur.role_name = ura.role_name
and ura.relationship_id = -1
and ((ur.effective_start_date is null or ur.effective_start_date <>
ura.effective_start_date)
or (ur.effective_end_date is null or ur.effective_end_date <> ura.effective_end_date));

If the above script returns any rows, proceed to the next step.

2) One must take a backup of the two tables :

WF_LOCAL_USER_ROLES
and
WF_USER_ROLE_ASSIGNMENTS

3) Run the following update script to correct the discrepancy :

UPDATE WF_USER_ROLE_ASSIGNMENTS set effective_end_date = to_date(null)
where rowid in (select ura.rowid
                from wf_local_user_roles ur, wf_user_role_assignments ura
                where ur.user_name = ura.user_name
                  and ur.role_name = ura.role_name
                  and ura.relationship_id = -1
                  and ((ur.effective_start_date is null or ur.effective_start_date <>ura.effective_start_date)
                  or (ur.effective_end_date is null or ur.effective_end_date <>ura.effective_end_date)));


4) Run the "Workflow Directory Services User/Role Validation" concurrent program to resolve the issue.

5. Re-test the issue.