To find pending resource transactions:You can view, update, delete, and resubmit resource transactions that have failed validation and remain in the Open Resource Transaction Interface table (WIP_COST_TXN_INTERFACE). You can also resubmit transactions whose concurrent process has failed and have a processing phase of Complete and process status of Error. You can view error messages associated with failed records. Error messages can assist you in updating failed records before resubmission.
To find pending resource transactions: To view pending resource transaction records:Navigate to the Pending Resources Transactions window. The Find Pending Resource Transactions window appears.
You can find pending records by Transaction Date range, by Organization, by Job, Schedule Name, and production Line. You can also search for records that have a specific Process Phase (Move validation, Move processing, or Backflush setup, Process Status (Pending, Running, or Error), Source Code, Source Line ID, or Transaction ID.
Enter any combination of search criteria and choose the Find button. The Pending Resource Transactions window appears with the results of your query.
To view pending resource transaction records:For each pending record displayed, you can view the following information using the Pending Resource Transactions window's tabbed regions:
Processing: Group ID, processing Phase, processing Status
Source: Source Code, Source Line (if applicable), Created By
Concurrent Request: Request ID, Phase, Status, Message
Job or Schedule Name: Organization, Job, Schedule Name, Line
Operations: Operation Sequence, Department, resource Sequence, resource Name, resource Type, Employee Number
Resource: Activity, Charge Type, PO Number, Currency, Actual Rate
Transaction: UOM, Quantity, Date and Time, Type
You can also view the descriptive flexfield information entered for the transaction record. See: Setting Up Descriptive Flexfields.
To view error details for failed resource transactions:In the Pending Resource Transactions window, select the failed record.
Choose the Errors button. The Pending Resource Transactions Error window appears.
All errors for the selected transaction are displayed. Column indicates the name of the column in the resource transaction interface table that failed validation. Message indicates why the transaction failed.
Messages that are not specific to a Column, for example processing errors, may also be displayed. In such cases, a Message but no Column is shown.
To update failed resource transaction records:Select the record to update.
You can update records with a processing status of Error.
In the Source tabbed region, enter the Source Code and Source Line.
When you insert records into the Open Resource Transaction Interface table, you can optionally identity a record's source using the source code and source line. For example, you can enter a different source code and source line for records from a bar code reader versus those from a radio frequency device.
Select the Created By identifier.
The name of the user that created the transaction is displayed. This field can be updated.
In the Job or Schedule Name tabbed region, select the Organization.
You can only select enabled organizations. See: Creating an Organization.
In the Operations tabbed regions, select the Operation Sequence for the resource.
You can select any operation defined for the job or repetitive schedule.
Select or enter the resource Sequence.
You can update this field with any resource sequence defined for your operation or you can add a resource ad hoc by entering a new resource sequence. If you choose a predefined resource sequence, all fields specific to that resource are automatically populated.
Select the Name.
If you inserted an 'ad hoc' resource requirement into the Open Resource Transaction Interface table by entering a new resource sequence, you can select resources associated with the department of the operation or multi-departmental resources. All related fields are automatically populated based on your selection.
If you choose a resource of type Person and the employee number has no value, you are prompted to enter an employee number.
If you choose a resource type other than Person and the employee number has a value, you are prompted to clear the employee number.
Select the Employee Number.
If you have entered a person-type resource, you can update this field with any valid employee number.
In the Resource tabbed region, select the Activity.
You can select an activity defined for your organization or an activity that is not tied to any specific organization and is not inactive.
Select the Currency code. .
Enter the Actual Rate for your resource.
This rate is used to determine the cost of a resource when the resource's standard rate option is set to No.
In the Transaction tabbed region, select the UOM. See: Overview of Units of Measure.
You can update this field with any resource alternate UOM that is not inactive.
Enter the transaction Quantity.
This is a quantity of the UOM which you are charging to a job or schedule. The job/schedule is costed at the resource standard, the employee rate, or the actual rate. You can update this field with any number.
Enter the transaction Date and time.
The date and time must fall within an open accounting period. It cannot be greater than the current date or less than the release date of the job or the earliest valid repetitive schedule.
In the Comments tabbed region, select the Reason code. See: Defining Transaction Reasons.
Enter the transaction Reference.
References can be used to identify transactions on standard reports. They can be up to 240 characters of alpha numeric text.
Save your work.
To resubmit individual failed resource transaction records:In the Pending Resource Transactions window, check the transaction's Resubmit check box.
You can resubmit transactions of any processing status. If you leave the check box unchecked you can still update your transaction record but the transaction manager does not process it again when polling the resource interface table.
Save your work to resubmit the transaction.
When you resubmit a transaction, the system nulls the Transaction ID, Group ID, and concurrent Request ID and changes the processing status to Pending. The resubmit level of the Resource Cost Transaction Manager determines at what specific start date and time or at what specific intervals transactions are processed.
To select and resubmit all failed resource transactions:In the Pending Resource Transactions window, chose Select All for Resubmit from the Tools menu. .
You can deselect selected transactions as required.
Save your work to resubmit the transactions.
When you resubmit transactions, the system nulls their Transaction IDs, Group IDs, and concurrent Request IDs, and changes their processing Statuses to Pending. The resubmit level of the Resource Cost Transaction Manager determines at what specific start date and time or at what specific intervals transactions are processed.
To delete pending resource transaction records:In the Pending Resource Transactions window, select the transaction.
Choose Delete from the Edit Menu
You can delete failed records that have a processing status of Error regardless of their processing phase. When you delete transaction records, their corresponding error messages are also deleted.
Other Sources
Open Resource Transaction Interface, Oracle Integration Repository at http://irep.oracle.com
