E1: 48S/52: FAQ - Frequently Asked Questions Workfile Generation (R48120) (Doc ID 652336.1)

Last updated on OCTOBER 05, 2022

Applies to:

JD Edwards EnterpriseOne Contract and Service Billing - Version 8.0 and later
Information in this document applies to any platform.

The Purpose of this document is to Answer Frequently Asked Questions about Workfile Generation, R48120

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Purpose

Question 1: How does the Workfile Generation (R48120) work?

Question 2: After running R48120 over a transaction originating in Work Order Entry (P48201), with the Work Order Status (SRST) is set so that the work order is non-billable (X in first position of Description 2 of UDC 00/SS ). The results in the F0911 GLBC field is being updated with a Z, but no transaction is created in the Billing Workfile (F4812). Why?

Question 3: After implementing Service Billing, when running Workfile Generation, the following error is received; "Non-coexistence error occurred." Error #142P.

Question 4: Is it possible to bill the T3 burden records associated with the T2 records, however the labor itself is not billable. Is there any way to run the R48120 to pull the burden but exclude the labor component?

Question 5: When generating the Billing Workfile (F4812) for the next month, is it possible to determine the total amount that will be billed for each contract?

Question 6: Is there a way to determine which contracts are eligible for Workfile Generation billing based on a particular period and Billing Frequency Code?

Question 7: Does Contract or Service Billing select records from a Ledger Type other than AA?

Question 8: Does Contract Billing exclude any document types or how does the functionality to process records work?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.