Scribd
Upload
686 views25 pages

Balance Forward Billing Setup

This doc provides an overview, required setup, sample screenshots of the Balance Forward Billing feature in Oracle Receivables Release 12.

Uploaded by

nachuthan_1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
686 views25 pages

Balance Forward Billing Setup

This doc provides an overview, required setup, sample screenshots of the Balance Forward Billing feature in Oracle Receivables Release 12.

Uploaded by

nachuthan_1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

9/12/2016

Document761180.1

BalanceForwardBillingSetupandUsageGuideforOracleReceivablesUsers(DocID761180.1)
InthisDocument
Abstract
History
Details

1.Overview

2.Features

3.Setup

a.DefineBalanceForwardBillingCycles

b.DefineBalanceForwardBillingPaymentTerms

c.DefineCustomerProfiles(OPTIONAL)

d.DefineBalanceForwardBillingEnabledCustomer

e.DefineSystemOptions

4.SimulationforBalanceForwardBilling

5.GeneratingaBalanceForwardBill

6.BalanceForwardBillinginAutoInvoice

7.DebuggingTips

8.CodeListing

9.CodeFlowchart

10.BalanceForwardBillingTemplates

11.FAQ

StillHaveQuestions?

Summary
References

APPLIESTO:
OracleReceivablesVersion12.0.0andlater
Informationinthisdocumentappliestoanyplatform.

ABSTRACT
ThiswhitepaperprovidesanoverviewoftheBalanceForwardBillingfeatureinOracleReceivablesRelease12.Itdiscusses
requiredsetup,providessamplescreenshots,debuggingtips,codewalkthroughaswellasotherpertinentinformationrelated
tothefeature.

HISTORY
Author:VictoriaCrisostomo
CreateDate14Jan2009
UpdateDate01Mar2016
ExpireDatenone

DETAILS
1.Overview
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

1/25

9/12/2016

Document761180.1

BalanceForwardBilling(BFB)isanewfeatureintroducedinRelease12.ItreplacesthefunctionalityprovidedbyConsolidated
BillingInvoices(CBI)inRelease11i.
BalanceForwardBillingisenabledwhendefiningacustomer.OnceacustomerrecordisBalanceForwardBillingenabled,you
canprintasingledocument,referredtoasaBalanceForwardBillwhichincludesallofacustomer'stransactionsand
paymentscreatedwithinthebillingperiodaswellasanybalancecarriedforwardfromthepreviousbillingperiod.Thisallows
youtosendoneconsolidateddocumenttothecustomerinsteadofindividualinvoicespertransaction.
DependingonhowBalanceForwardBillingissetup,youcanconsolidateintoonebillalltransactionsandpaymentsofa
customeracrossmultiplesites,oryoucanconsolidatepersite.
Itprovides:
abeginningbalancecarriedoverfromthepreviousperiod
anitemizedlistofallactivitiessuchasinvoices,debitmemos,creditmemos,adjustmentsandreceipts
anoutstandingbalanceforthecurrentbillingperiod
agingofoutstandingbalance

2.Features
1.BalanceForwardBillingcanbesetupateithertheCustomerAccountorSitelevel.
2.TheformatofthebillcanbeDetailedorSummarized.
3.Billingcyclescanbedefinedtoreflectyourbusinessrequirementsonhowoftenacustomershouldbebilled.Billing
CyclescanbeMonthly,WeeklyorDaily.
4.Itprovidestheflexibilityofexcludingaparticularsite.Italsoallowsyoutopickspecificinvoicesthatyoudonotwantto
beincludedintheBalanceForwardBill.
5.YoucanqueryusingtheBalanceForwardBillingnumberintheTransactionsWorkbench.
6.YoucanapplyreceiptstoaBalanceForwardBillviatheReceiptsWorkbenchaswellasAutomaticReceipts.

3.Setup
Thefollowingsetupneedstobeperformedintheorderlisted.

a.DefineBalanceForwardBillingCycles
NavigationPath:Setup>PrintBalanceForwardBillingCycles
YoucandefineacyclewithaFrequencyofMonthly,WeeklyorDaily.Youalsospecifyhowfrequentlythecycle
shouldrepeat.
Thecyclebelow,billsonthe18thofeverymonth.Inthissetup,cycledateswillbecreatedfor18JAN2008,18
FEB2008,18MAR2008andsoon.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

2/25

9/12/2016

Document761180.1

Thecyclebelow,billseveryMonday.Inthissetup,cycledateswillbecreatedfor07JAN08,14JAN08,21
JAN08andsoon.

Whenacycleisdefined,recordsarecreatedinthetables:AR_CONS_BILL_CYCLES_Band
AR_CONS_BILL_CYCLE_DATES.Tenyearsworthofcycledaterecordsarestoredinthetable.
ThecycledateislaterreflectedintheTransactionworkbenchasBillingdate.
Note:
Thereare2typesofBillingCycles:RECURRINGandEVENT.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

3/25

9/12/2016

Document761180.1

UserscanonlycreatecycleswithRECURRINGtype,andOracleseedsoneEVENTtypenamedEXTERNAL.
TheEXTERNALcyclecanbeusedforimportedtransactionsviaAutoInvoice,seesectionbelowonBalance
ForwardBillinginAutoInvoice.

b.DefineBalanceForwardBillingPaymentTerms
NavigationPath:Setup>Transactions>PaymentTerms
AbalanceforwardpaymenttermneedstobedefinedwiththeBillingCyclefieldpopulated.OncetheBillingCycle
fieldispopulatedthistermisconsideredaBalanceForwardbillingterm.
ThisfollowingpaymenttermusestheBFBMTHcyclewedefinedearlier.TheDuedaysindicatesthenumberof
daysaftertheBillingDatetheinvoicebecomesdue.Inthissetup,transactionsthatusethistermwillbebilled
onthe18thandwillbedueonthe28th.

Inthefollowingsetup,transactionsthatusethistermwillbebilledeveryMondayandwillbedue5daysafter
that.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

4/25

9/12/2016

Document761180.1

c.DefineCustomerProfiles(OPTIONAL)
NavigationPath:Customers>ProfileClasses
SettingupacustomerprofileclassisanoptionalstepforBalanceForwardbillingsetup.Havingacustomer
profileclasssimplifiesthesetupofBalanceForwardBillingenabledcustomers,asthevaluesforfields
pertainingtoBalanceForwardBillingareusedtodefaultthevaluesintothecustomerrecord.Youcanoverride
valuesdefaultedinfromtheprofileclass.
WhendefiningacustomerprofileclassforBalanceForwardBilling,youshouldchecktheEnablecheckbox.Once
enabled,thefieldsforBillLevelandTypeareenabledandonlyBalanceForwardPaymenttermswillbeavailable
inthelistofvalues.
ThesetupbelowisforacustomerprofileusingBilllevel=Account,whereinconsolidationisdoneatthe
accountlevel,allactivityfromBalanceForwardEnabledsitesarereportedinonebill

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

5/25

9/12/2016

Document761180.1

ThesetupbelowisforacustomerprofileusingBilllevel=Site,whereinconsolidationisdoneatthesitelevel,
andseveralbillsarecreated,oneforeachBFBenabledsite.

FollowingprovidesanoverviewofthedifferencebetweentheBillLevelvalues:
BillLevel=ACCOUNT

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

6/25

9/12/2016

Document761180.1

WhenBalanceforwardBillingisenabledattheAccountlevel,theresultwouldbethecreationofoneBalance
ForwardBill.ThisbillwillconsolidatealltheactivitiesacrossalltheBFBenabledsitesforthisaccount.Inthe
scenarioabove,therearefoursites.ThreeofthesitesareBFBenabled.Thefourthsiteisnot.Notethatfor
eachBFBenabledsite,aBFBpaymenttermandtypewasdefined.However,becausetheexpectationinthis
setupisonlyonebillwillbecreated,thesettingsattheAccountleveltakesprecedenceoverthesettingsatthe
sitelevel.Insuchasetup,aBalanceForwardBillwillconsolidatealltransactionsfromthesethreesitesand
addressthebilltothethirdsitesinceitisthePrimaryBilltosite.Alltransactionsforthefourthsitewillbe
excludedfromtheBalanceForwardbill,andinsteadeachtransactionwillprintaninvoice.
BillLevel=SITE

WhenBalanceforwardBillingisenabledattheSitelevel,theresultwouldbethecreationofseveralbills.Each
BFBenabledsitewillgetitsownbill.Eachbillwillconsolidatetheactivitiesforthatsite.Inthescenarioabove,
therearefoursites.ThreeofthesitesareBFBenabled.Thefourthsiteisnot.NotethatforeachBFBenabled
site,thesettingsdefinedatthesitelevelwillbeusedtocreateitsbill.Alltransactionsforthefourthsitewillbe
excludedfromthebillandinsteadeachtransactionwillprintaninvoice.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

7/25

9/12/2016

Document761180.1

d.DefineBalanceForwardBillingEnabledCustomer
NavigationPath:Customers>Customers
WhencreatingaBFBCustomer,youhavetheoptiontouseaBFBProfileclass,suchastheonescreatedearlier,
oryoucanuseanyprofileclassandjustoverridethefieldshighlightedunderBalanceForwardBillingandTerms.
Below,weusedthecustomerprofileclass:BFBACCTLEVELPROFILE,fromwhichtheformgetsdefaultvalues
forBFBrelatedfields.NotethecheckboxOverrideTerms.Bycheckingthisbox,youaresayingthatwhenauser
createsaninvoiceforthiscustomer,heisallowedtochangethePaymentTermthatdefaultsin.Thisfeature
allowsyoutocreatenonbalanceforwardtransactionswithinaBFBenabledsite.

Note:WhetheryouuseacustomerprofileclasstodefaultBalanceForwardBillingrelatedfields,orupdate
theAccount/SiteProfiletabmanually,itismandatorythatyouprovidevaluesforthefieldshighlightedinthe
redboxabove.

TodemonstratethescenariodescribedintheoverviewforBillLevel=ACCOUNT,wewilldefine4sitesforthis
customer:
Site

BillLevel

PaymentTerm

OverrideTerms

SITE1:BFB

Account

BFBMTH

checked=Y

SITE2:BFB

Account

BFBMTH

unchecked=N

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

8/25

9/12/2016

Document761180.1

SITE3:BFB

Account

BFBWEEKLY

checked=Y

SITE4:NONBFB

notset

30NET

checked=Y

Below,weusedthecustomerprofileclass:BFBSITELEVELPROFILE,fromwhichBFBrelatedfieldshave
defaultedfrom.NotethecheckboxOverrideTerms.Bycheckingthisbox,youaresayingthatwhenauser
createsaninvoiceforthiscustomer,heisallowedtochangethePaymentTermthatdefaultsin.Thisfeature
allowsyoutocreatenonbalanceforwardtransactionswithinaBFBenabledsite.

TodemonstratethescenariodescribedintheoverviewforBillLevel=SITE,wewilldefine4sitesforthis
customer:
Site

BillLevel

PaymentTerm

OverrideTerms

SITE1:BFB

Site

BFBWEEKLY

checked=Y

SITE2:BFB

Site

BFBWEEKLY

unchecked=N

SITE3:BFB

Site

BFBMTH

checked=Y

SITE4:NONBFB

notset

30NET

checked=Y

IMPORTANTNOTES:
1.IMPORTANTCHANGEINBEHAVIOR:
Patch12325638:"BALANCEFORWARDBILLINGENABLEDATACCNTLVLBUTAUTOINVOICE
ERROR,"changesthevalidationsuchthatsettingsattheAccountLevelcascadetoSiteLevel.
OncePatch12325638isapplied,#2belowisnolongerapplicable.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

9/25

9/12/2016

Document761180.1

2.BeforePatch12325638:WhenyouenableBalanceForwardBillingattheACCOUNTlevel,itisstill
necessarytocreateaprofileattheSITElevel.IfyoudonotexplicitlysetupaSITElevelprofile,you
willencountertheerrorbelowwhenyouattempttocreateatransaction:
Balanceforwardbillingisenabledforthiscustomerattheaccountlevel,
butiseitherdisabledornotdefinedatsitelevel.

3.WhenBalanceForwardbillingwasoriginallyintroducedinRelease12,featuressuchascutoffdate
termsandconsolidatinginvoiceswereonlyavailableforcustomerswhowereBalanceForwardBilling
enabled.Thiswasveryrestrictiveandrequiredadditionalsetupthatwasunnecessaryforcustomers
whowerenotinterestedinthefeaturesprovidedbyBalanceForwardBilling,butjustwantedtousea
balanceforwardpaymenttermthatimplementedcutoffdays.
Toliftthisrestriction,changesweremadethatallowednonBalanceForwardBillingEnabled
customerstouseBalanceForwardBillingtermswithcutoffdates.Thisrestoresthe
functionalitythatwasavailableinRelease11.5.Tousethesefeatures,youneedtoapplythe
followingpatches:
Patch9343518:PROXIMAPAYMENTTERM(AR)INR12NEED5415213WORKEDAND
RELEASED.
Patch9571316:WRONGDUEDATECALCULATEDONINVOICESWITHOUTBFB
ENABLED
Patch9538417:PAYMENTTERMSWITH'BALANCEFORWARDBILLING'GIVINGERROR
DURINGAUTOINVOICE
AdditionalinformationonusingcutofftermscanbereviewedinNote1052906.1,Howto
implementpaymenttermswithcutoffdaysinR12

e.DefineSystemOptions
IfinthetransactionsformyouwouldliketheBFB#displayedforinvoices,thenyoushoulddothefollowing
setup.
NavigationPath:Setup>SystemOptions
NavigatetotheTransandCustomersTab,andcheckShowBillingNumber

Bydoingtheabovesetup,whenyourunaqueryintheTransactionworkbenchforatransactionthathasbeen
consolidatedintoaBalanceForwardBill,youwillseetheBFBnumberasshownbelow.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

10/25

9/12/2016

Document761180.1

4.SimulationforBalanceForwardBilling
Afterdoingtherequiredsetupabove,youcanstartcreatingtransactionsfortheseBFBenabledcustomers.
ForBFBCUST1(AccountLevel):TodemonstratethedifferencesinbehaviorduetothesettingsdefinedattheSitelevel,
severalinvoicesarecreatedacrosseachofthesites.
ForSITE1:BFB,2invoicesarecreated,todemonstratethatthePaymentTermcanbeoverwrittenduetoOverrideTerms
beingchecked.
ForInvoice12294below,theBillingdateiscalculatedusingthesetupoftheBFBCycle:BFBMTH,whichwesetupasthe
18thofthemonth.ThebillingdatehastobeonoraftertheTransactionDateandiscalculatedas18MAY08.TheDuedateis
calculatedusingthesetupoftheBFBPaymentTerm:BFBMTHwhichwesetuptobeduein10days.TheDuedateis
determinedtobe28MAY08,whichis10daysafterthebillingdate.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

11/25

9/12/2016

Document761180.1

FortheInvoice12295below,wedemonstratethateventhoughBFBisenabledforSITE1:BFB,auserisallowedtocreatea
nonBFBinvoicebychangingthepaymenttermtoanonBFBterm.ThisisallowedbecauseOverrideTermsischeckedinthe
SiteProfile.

ForSITE2:BFB,wecreateoneinvoice,thescreenshotshowstheLOVforPaymenttermshowingthattheonlyavailableterm
isBFBMTH.ThisisbecausetheOverrideTermscheckboxforthissiteisunchecked,soalltransactionswillhavetousethe
termdefinedattheSiteprofile.ForSITE2:BFB,allinvoiceswillhavethepaymenttermBFBMTH.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

12/25

9/12/2016

Document761180.1

ForSite3:BFB,wecreateoneinvoice,thescreenshotdemonstratesthatthePaymentTermusedisBFBWEEKLYasdefined
intheCustomerSiteprofile.NotethattheBillingDateandDuedatearedifferentfromthatcalculatedforBFBMTH,thisis
determinedbythesetupforthePaymentTermBFBWEEKLY.

ForSite4:NONBFB,notethatthefieldBillingdateisnotevendisplayed,thefieldBillingDateispresentonlyforBFB
transactions.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

13/25

9/12/2016

Document761180.1

ForBFBCUST2(SiteLevel),thefollowinginvoicesarecreated:
Site

Invoice#

PaymentTerm

BillingDate

DueDate

SITE1:BFB

12312

BFBWEEKLY

05MAY08

10MAY08

12313

BFBMTH

18MAY08

28MAY08

SITE2:BFB

12314

BFBWEEKLY

05MAY08

10MAY08

SITE3:BFB

12315

BFBMTH

18MAY08

28MAY08

SITE4:NON_BFB

12316

30NET

notapplicable

28MAY08

Aftercreatingtheabove,wearereadytorunasimulatedtestofGeneratingtheBalanceForwardBill.

5.GeneratingaBalanceForwardBill
NavigationPath:PrintDocumentsBalanceForwardBilling
Inanactualbusinessscenario,BalanceForwardBillswillbegeneratedonaregularbasis.Abusinessprocesswillbedefined
sothattheprocessissubmittedatregularintervals.Inthisexample,thebillsforBFBMTHhaveneverbeengenerated.
Uponinvokingthismenuitem,youhavethefollowingthreeoptions:
BPABalanceForwardPrintProgramenablesyoutoreprintanyBalanceForwardBill
ConfirmBalanceForwardBillenablesyoutoconfirmorrejectDraftBills
GenerateBalanceForwardBillsenablesyoutogeneratenewbills

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

14/25

9/12/2016

Document761180.1

NotethattheBillingdateisnotamandatoryfield.Ifyoudonotspecifyabillingdate,thecodewillpickthelatestvalueofthe
Billingdateforthecyclethatisonorbeforethesystemdate.Inthisexample,ifIrantheprocesson14JAN09anddidnot
provideabillingdateparametervalue,thecodewouldhaveruntheprocesswithabillingdateof18DEC08.Thisisexpected
behaviorforBFB.Itwillnotprintbillsforeachofthecyclesdatesdefinedthatyouhavenotyetprinted,butratheritwillfast
forwardtothelatestvaluepossible.
Thisprocesswillspawn3requests:firsttocollectandprocessthedatafortheBFB,secondtokickoffBillPresentment
Architecture(BPA)Printprocessandthirdtoactuallycreatetheoutput.
FollowingistheoutputforBFBCUST1,invoicesacrossthethreeBFBenabledsitesareincluded.ItshowsPreviousBalance=
0.00becausethisisthefirstrunforthisbillingcycle.ThethreeinvoicesqualifiedforinclusionintotheBillarethosethatused
BFBTerms.NotethateveniftheinvoiceforSite3:BFBwasusingthetermBFBWEEKLY,itwaspulledintothisbillanyway.
ThisisduetothesettingofBillLevel=Account.WhichcausesallsettingsattheSiteleveltobeignored,andinsteadsettings
attheAccountlevelareused.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

15/25

9/12/2016

Document761180.1

FollowingisoneoftheoutputsforBFBCUST2,whensubmittedforBFBWEEKLY,eachsiteusingBFBWEEKLYpayment
termgetsitsownbill:

DataassociatedwithaBalanceForwardbillisstoredinthefollowingtables:
AR_CONS_INV_ALL:arowiscreatedforeveryBFBsiteincludedinthebill.EachsitewillhaveitsownCONS_INV_ID.
WhenBilllevel=Account,severalCONS_INV_IDvaluescanhavethesameCONS_BILLING_NUMBERvalue.
AR_CONS_INV_TRX_ALL:arowiscreatedforeverytransaction,adjustment,receiptpulledintothebill
AR_CONS_INV_TRX_LINES_ALL:arowiscreatedforeveryinvoicelinepulledintothebill
ThecorrespondingCONS_INV_IDvalueswillbestampedintoAR_PAYMENT_SCHEDULES.CONS_INV_IDofall
invoicesincludedinthebill.
SincewegeneratedthebillinDraftmode,weneedtosubmitanotherprocessshownbelowtoacceptit.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

16/25

9/12/2016

Document761180.1

TheConfirmBalanceForwardBillprocessenablesyoutoeitherAcceptorRejectaDraftbill.Ifyouchoosetoaccept,the
invoicesincludedinthebillarefinalized.Youcannolongermakeanychanges,ormodificationstotheseinvoicesevenifyour
SystemProfile:AllowsChangetoPrintedTransactionsisYes.
Important:WheninvokingtheConfirmBalanceForwardBilltoAcceptorRejectDraftbills,notethattheonlyparameter
markedasmandatoryistheConfirmOptionparameter.However,thefollowingfieldshavearequirementdependencyupon
eachother:
CustomerNumberLow/High(requiredifbillnumberorconcurrentRequestIDisnotspecified):Confirmoneormore
accountlevelbalanceforwardbills.Thelistofvaluesincludesallbalanceforwardbillingcustomers.
BillNumberLow/High(requiredifcustomernumberorconcurrentrequestIDisnotspecified):Confirmoneormore
balanceforwardbills.
ConcurrentRequestID(requiredifnootherparametersarespecified):SelecttheconcurrentrequestIDforthe
GenerateBalanceForwardBillprogramtoacceptorrejectabatchofbalanceforwardbills.
IfyouhappentosubmitAcceptorRejectwithoutprovidingadditionalparameters,theprocesswillstillrunbut
willnotdoanything.Theprocesswillcompletenormal,butifyouviewthelogfile,youwillseeamessagelike:
ACCEPT:CannotAcceptBills,userneedstoprovideadditionalparameters.
PleasemonitorERbug8520340whichisarequesttohavetheconcurrentprocessendinwarning,insteadof
normal,sousersarealertedtoa"problem"encounteredduringtheAccept/Rejectprocess.

Ifyouchoosetorejectthebill,theinvoicesincludedinthebillarereleased,andtheycanbepickedupbyasubsequentrunof
BalanceForwardBilling.However,anyinvoicewhoseBFBdatawasoverriddenbytheGenerateBillprocesswillretainthenew
BFBdata,itwillnotrestoretheoriginalvalues.
Subsequentactivitysuchasadjustments,creditmemoapplications,receiptapplicationstotheinvoicesincludedinthebillwill
bereflectedinfuturebillsgenerated.
ThefollowingoutputillustratesthenextBillcreatedfortheBFBMTHcycle.Itshowsthatpriortothenextbillingdateof18
JUN08,anewinvoicewascreatedandanadjustmentandareceiptwerecreatedagainst2oftheinvoicesincludedinthebill.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

17/25

9/12/2016

Document761180.1

Onceaninvoicehasbeenincludedintoabill,youcanusetheViewInvoiceIcon(highlightedbelow)toviewtheoutputofthe
billtowhichtheinvoiceisassociatedwith.Notethatthisiconwillonlydisplayoutput,aftertheGenerateBalanceForwardBill
processhasbeensubmitted,andthisinvoicehasbeenincludedinabill.

6.BalanceForwardBillinginAutoInvoice
WhenimportingtransactionsviaAutoInvoice,thefollowingfieldsinRA_INTERFACE_LINES_ALLarerelatedtotheBalance
ForwardBillingfeature:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

18/25

9/12/2016

FieldName

Document761180.1

Description

CONS_BILLING_NUMBER IftheBalanceForwardBillwasgeneratedoutsideofOracleReceivables,butyouwanttokeeptrack
oftheBillingnumberwithinOracleReceivables,thenyoucanprovideavaluein
RA_INTERFACE_LINES_ALL.CONS_BILLING_NUMBER.
AutoInvoicewillvalidatewhetherthisnumberalreadyexistsinAR_CONS_INV_ALLwhere
CONS_INV_TYPE='MINV'.Ifsucharecorddoesnotyetexist,onewillbecreatedtokeeptrackof
thisexternallygeneratedBalanceForwardBillingNumber.
BILLING_DATE

IfusingtheBalanceForwardBillingfeature,andthebillingcycleassociatedtothepaymenttermof
thistransactionhasBillingtype:
EVENT,thenyouarerequiredtopassinaBillingdate.ABillingcyclewithtypeEVENTis
consideredanEXTERNALcycle,wherebytheBalanceForwardBillwasgeneratedoutsideof
OracleReceivables.
Note804334.1,AutoinvoiceError:AutoInvoiceValidationReportShowsanErrorwithBlank
Text,discussesanissueaddressedinAutoInvoicewhereinablankerrorwasraisedforthe
casewheretheBillingType=EVENT.
RECURRING,thenyoushouldnotpassinavalueandAutoInvoicehandlesderivingthe
billing_dateforyou.

TERM_IDor
TERM_NAME

IfyoupassapaymenttermthatisassociatedtoaRECURRINGBillingCycle,thenitislikeyouare
simulatingamanuallyenteredtransaction.AutoInvoicewilltakecareofdeterminingtheDueDatefor
thetransaction,basedupontheBillingDatederivedfromthebillingcycleinformation.
Pleasenotethatvalidationofthisfieldagainstabalanceforwardbillingenabledcustomerchanged
afterRelease12wasoriginallyreleased.RefertoNoteBoxinsetupstep:DefineBalanceForward
BillingEnabledCustomerforadditionalinformationforadditionalinformation.

7.DebuggingTips
ThelogfilegeneratedbytheGenerateBFBprocesscontainsnumerousdebugmessagesprovidinganarrativeofwhatthe
codeisdoing.Reviewingthelogfilewillassistyouindeterminingwhythecodedidnotpickupaninvoiceyouwereexpecting
toseeinthebill(orviceversa).Byreviewingthelogyoucanunderstandwhatlogicwasappliedtoeachtransaction.
FollowingisasampleoftheloggeneratedforthefirstBFBoutputshownabove,andannotationsonhowtouse/readthe
output.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

19/25

9/12/2016

Document761180.1

Themaincursorc_site_stmt,drivestheselectionofdata,youcancopythisstatementandrunitstandaloneinSQL*Plusto
determineifthesiteofyourinvoiceisinthemainselectioncriteria.
Furtherdownthelogitshowstheloopsofprocessingthecodegoesthrough,itfirstloopsthroughtheBFBenabledsites,and
thenloopsthroughalltransactionswithinthatsite.Thenitpicksupactivities(adjustment,creditmemoapplications,receipt
applications)againstthetransactionsincluded:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

20/25

9/12/2016

Document761180.1

ThelogwillalsoshowwhenitoverridesBFBrelateddataandwhy,aswellaswhenitcannotoverridedata.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

21/25

9/12/2016

Document761180.1

YoucanalsoreviewthePL/SQLpackageslistedbelow.

8.CodeListing
BalanceForwardBillingfeatureiscontrolledbythefollowingPL/SQLcode:
ARPBFBIB.pls/ARPBFBIBs.pls:DefinesthepackageARP_BF_BILLwhichcontrolsthemainprocessusedbytheconcurrent
processes:GenerateBalanceForwardBillsandConfirmBalanceForwardBill
ARBFBUTB.pls/ARBFBUTS.pls:DefinesthepackageAR_BFB_UTILS_PVT,whichcontainsalltheutilityproceduresand
functions
ARBPBFBB.pls/ARBPBFBS.pls:DefinesthepackageAR_BPA_BFPRI_CONC,whichhandlestheBillPresentmentprocessused
togeneratetheBFBoutput

9.CodeFlowchart
ThefollowingrepresentsingraphicalformthelogicdefinedinARP_BF_BILLpackage.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

22/25

9/12/2016

Document761180.1

ItisimportanttonotethatthecodewillattempttomakealltransactionsofaBFBenabledcustomertoconformtothesettings
definedattheAccountorSitelevel(dependingontheBFBlevel).ThisistosatisfytheobjectiveofhavingaBFBenabled
customerwhichistoensureallhistransactionsarebilledanddueatthesametimeandareconsolidatedintoonebill.
Whenatransaction'sterm/dateisoverriden,themodifiedvalueswillbereflectedwhenyouquerythetransactioninthe
Transactionsform.

10.BalanceForwardBillingTemplates
TheoutputforBalanceForwardBillsishandledbyBillPresentmentArchitecture.Toaccessthesetemplates,youneedtouse
theBPAresponsibility.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

23/25

9/12/2016

Document761180.1

TheBalanceForwardfeaturewasreleasedwithtwoseededtemplatesshownabove.Thesetemplateshandletheoutput
requirementsforthetwoBillTypes:DetailandSummary.
Youcancreateyourowntemplatesbyduplicatingtheseededtemplatesandmodifyingyourversionasrequired.Pleasereview
BPAUser'sGuideformoreinformationonhowtocustomizethetemplates.
Youcangenerateamockversionofthebill,byusingtheInteractivePreviewIcon,andthenprovidingthevaluesforthe
parametersrequired.
ThefollowingisasampleoftheSummaryversionofthesamebillwegeneratedearlierasDetailed.

11.FAQ
Foralistoffrequentlyaskedquestions(FAQ),issuesandconcerns,Note1080423.1,FAQ:BalanceForwardBilling(BFB)
CommonIssuesandConcerns

StillHaveQuestions?

TodiscussthisinformationfurtherwithOracleexpertsandindustrypeers,weencourageyoutoreview,joinorstarta
discussionintheMyOracleSupportReceivablesCommunity.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

24/25

9/12/2016

Document761180.1

Toprovidefeedbackonthisnote,clickontheRatethisdocumentlink.

SUMMARY
Insummary,thiswhitepaperprovidedadefinition,overviewandsetuprequiredforusingthenewfeatureBalanceForward
Billing.
Itprovidessetupstepsrequired,discussedthedifferencesbetweenthetwoBillinglevels:AccountandSiteatwhichbillscan
begenerated,itincludesscreenshotstoprovideclearexamples.Italsoprovidesprogramlistings,debuggingtipsand
informationonthetemplatesused.
Copyright2008Oracle.Allrightsreserved.OracleisaregisteredtrademarkofOracle.Variousproductand
servicenamesreferencedhereinmaybetrademarksofOracle.Allotherproductandservicenames
mentionedmaybetrademarksoftheirrespectiveowners.
Disclaimer:Thisdocumentisprovidedforinformationpurposesonlyandthecontentshereofaresubjectto
changewithoutnotice.Oracledoesnotwarrantthatthisdocumentiserrorfree,nordoesitprovideanyother
warrantiesorconditions,whetherexpressedorallyorimpliedinlaw,includingimpliedwarrantiesand
conditionsofmerchantabilityorfitnessforaparticularpurpose.Oraclespecificallydisclaimsanyliabilitywith
respecttothisdocumentandnocontractualobligationsareformedeitherdirectlyorindirectlybythis
document.Thisdocumentmaynotbereproducedortransmittedinanyformorbyanymeans,electronicor
mechanical,foranypurpose,withoutthepriorwrittenpermissionofOracle.

REFERENCES
BUG:8520340CHANGEBEHAVIORWHENBFBCONFIRMFAILSTOCONFIRMDUEMISSINGPARMS
NOTE:1052906.1HowtoImplementPaymentTermswithCutoffDaysinR12
NOTE:761180.1BalanceForwardBillingSetupandUsageGuideforOracleReceivablesUsers
NOTE:804334.1AutoinvoiceError:AutoInvoiceValidationReportShowsanErrorwithBlankText
Didn'tfindwhatyouarelookingfor?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d6g8c7tjj_198&id=761180.1

25/25

Common questions

Powered by AI

Balance Forward Billing in Oracle allows configuration to exclude specific sites from consolidated billing. Each site can be individually flagged as BFB-enabled or not, meaning invoices for non-enabled sites will be handled separately. The billing setup can be tailored at the Account or Site level to suit business needs .

Careful decision-making between Account-level and Site-level setups is crucial as it impacts billing consolidation and customer communication. Account-level billing offers strategic advantages in reducing administrative overhead by consolidating all transactions into a single bill. In contrast, Site-level billing provides more detailed breakdowns per site, which can benefit tracking and resolving site-specific account issues .

Balance Forward Billing allows businesses to consolidate multiple transactions and payments into one bill per customer, reducing the need for multiple invoices. Businesses can customize bill documents using Bill Presentment Architecture (BPA) templates, with options for Detail and Summary types. Custom templates can be created by duplicating and modifying existing ones .

The 'Override Terms' option allows users to change the default BFB Payment Term on individual invoices. This facilitates creating non-BFB transactions within a BFB-enabled site if needed. When this option is checked, it provides flexibility in handling diverse customer requirements by allowing alterations at the transaction level .

Potential challenges include ensuring that Balance Forward Billing terms with cutoff dates are correctly applied, as older versions required specific patches to restore functionality. Additionally, businesses may encounter errors related to due date calculations for non-BFB invoices and managing the consolidation of transactions without disrupting AutoInvoice processes .

Businesses can customize Balance Forward Billing templates by using Bill Presentment Architecture to duplicate and modify pre-existing Detail and Summary templates. While customization offers tailored billing documents, businesses must ensure that changes comply with system constraints and do not disrupt essential billing functions .

Balance Forward Billing accommodates varying business requirements by allowing users to define billing cycles that can be Monthly, Weekly, or Daily. This flexibility enables companies to choose the frequency that best aligns with their operational needs and customer agreements, facilitating more efficient billing processes .

To display the Balance Forward Billing number for invoices, users must configure System Options accordingly. This feature benefits businesses by enhancing transparency in billing records, allowing easier tracking and management of invoices within the Transactions workbench, thus streamlining financial operations and audits .

When generating Balance Forward Bills, if no billing date is specified, the system defaults to the latest billing date in the cycle on or before the current system date. It 'fast forwards' to the latest period rather than printing bills for each unprinted cycle date. This ensures that the most current data is always included, potentially skipping intermediate billing periods .

At the Account level, Balance Forward Billing consolidates all activities across BFB-enabled sites into one bill, addressing it to the primary Bill-to site. Activities from non-BFB-enabled sites are excluded and invoiced separately. In contrast, the Site level setup creates separate bills for each BFB-enabled site, using the payment terms defined at the site level. Each site's activities are consolidated into its own bill, excluding non-BFB sites .

You might also like