My Oracle Support Banner

E1: 52: FAQ - Frequently Asked Questions Contract Billing Lump Sum Billing Lines (Doc ID 632989.1)

Last updated on DECEMBER 18, 2019

Applies to:

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

Purpose

The purpose of this document is to answer Frequently Asked Questions about Lump Sum Pricing Type records in Contract Billing

Questions and Answers

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
Questions and Answers
 Question 1:  When Journal generation (R48131) for a Lump Sum invoice (Pricing Type "L"), the system is looking at Billing AAI 4811 (Actual Revenue Credit) instead of Billing AAI 4832 (Accrued Receivables). Should invoice journal generation program be looking at Billing AAI 4832, Accrued Receivables for a Lump Sum billing invoices as it does for T&M, not Billing AAI 4811?
 Question 2: Why is it possible to add a lump sum pay type billing detail line without an amount in schedule of values and only a warning is received, but an error is received with Unit Price Pay Types?
  Question 3:  How can a Recurring Billing line be set up in Contract Billing(P5202) so that it will calculated through the contract end date?  Can an end date be set up for the recurring amount or how does the system know when to stop processing the recurring amount?
  Question 4:  When using Lump sum Billing functionality in Contract billing module and defining frequency of billing like Monthly, Yearly, Quarterly etc.  the system does not prevent the billing if  mistakenly run again during the month.  How can this be prevented?

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