This chapter contains these topics:
For every revision of a transaction that you create as you process workfile transactions, the system stores a copy of the previous transaction in Billing Workfile - History (F4812H). You can review this audit trail to see all the changes you have made to a transaction. For example, if you change a markup and include a reason for the change, you can access the workfile history to review the markup change reason.
Working with the workfile history includes the following tasks:
Reviewing transaction revisions
Moving a transaction out of history
As you review the workfile history, you can reactivate eligible transactions. When you reactive a transaction, you move it from history back to the active workfile. For example, if you move a transaction to history in error, the transaction is eligible to be moved back to the workfile. After you move the transaction back to the workfile, you can include the transaction on an invoice.
To maintain the integrity of the workfile, the system determines whether a transaction is eligible for reactivation based on the Billing Control ID (BCI) number and a combination of other factors.
The following transactions are not eligible for reactivation:
Invoiced transactions
Voided transactions
Transactions copied to history during the split process
Transactions copied to history during the modification process
From Contract Billing Processing (G52), choose Workfile Generation
From Workfile Generation (G4822), choose Revisions (P4812)
For every revision of a transaction that you create as you process workfile transactions, the system stores a copy of the previous transaction in Billing Workfile - History (F4812H). You can review this audit trail to see all the changes you have made to a transaction. The system displays the revision history of a transaction starting with the most recent revision to the original transaction.
To review transaction revisions
On Revisions
Complete the steps for reviewing workfile transactions.
Choose Transaction History Inquiry (Option 7) for a specific transaction.
Figure 20-1 Inquire Workfile History screen
On Inquire Workfile History, review the revision history for the transaction.
If text, components, tax, or burden are associated with the transaction, the Option field for the transaction is highlighted on the form.
From Contract Billing Processing (G52), choose Workfile Generation
From Workfile Generation (G4822), choose Detail History (P4812H)
As you review the workfile history, you can move transactions that you previously assigned as nonbillable out of history. When you move a transaction out of history, you reactivate the transaction. When you reactivate a transaction, the system:
Makes the transaction and all its associated components, burden, tax, and text eligible for processing
Marks the historical transaction as reactivated
Moves a copy of the historical transaction from the Billing Workfile - History table (F4812H) to the Billing Workfile table (F4812)
To move a transaction out of history
On Detail History
To locate a transaction, complete any of the following fields:
Customer Number
Account Number
BCI Number
Contract Number
Employee/Supplier
Choose Reactivate (Option 8) for the transaction.
After you reactivate a transaction, the system continues to display the transaction on Detail History until you re-inquire on the form.
Topic | Description |
---|---|
Limiting the records that display | You can use the Display All (#DS1) field to display all the transactions in the Billing Workfile - History table. If you use this field, the number of records to display often exceeds the maximum number allowed.
JD Edwards World recommends that you enter additional criteria to narrow your search when you review the history for workfile transactions. |
Displaying eligible transactions | You can use a processing option to control whether the system initially displays all transactions or only those eligible for reactivation. |
Billing status for reactivated transactions | Reactivated transactions are nonbillable when they return to the active workfile. You must manually update the eligibility code before you can further process the transaction. |