Upload
ksureshkumar
View
502
Download
81
Embed Size (px)
Citation preview
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 1/19
AuthorWhileworkinginSAPISUbillingprojectteamat,Ihavecomeacrossvariousissuesandsolutionsthatmaybeofinteresttoanyonewhoisworkinginthisareaofbusiness.Ithoughtofsharingitwithall.IfyouhavecomeacrossotherissuesinSAPISUandsolvedthem,pleasesharewithmewithyoucommentsandIwillpostitwithyournameonthisblog.Togetherwecanmakeadifference!YourfriendinSAPprojects
ArchivesDecember2014
CategoriesAll
RSSFeed
SAPISUBilling
12/27/2014 0CommentsSAPISUBillingerrors
YouhavesentBQrequestusingtransactionZBQRbutitisnotshowingupinBQtable.
Solution:
OneoftheissuecouldbeMROsthatyoucreatedarenotinorder.CheckiftheMROSyoucreatedarewithinthecurrentdateperiod.Example,todayisDemember10,2014andoneoftheMROsyoucreatedisforJanuary2015.Ifthisisso,removeJanuaryMROandsendBQrequestagain.
Anotherissuecanbethatthedevicedateandcontractdatedoesnotmatch.ForexampledevicedateisJanuary2014andcontractstartdateisDecember2013.ThismeansthattherewasnodeviceinstalledatthispremiseinDecember2013whencustomerwasmovedintothispremise.Wecannotbilltheaccountwithouthavingameterinstalled.Inthissituation,investigateandcheckrecordsandupdatethedeviceinstallationdateorcontractstartdateinsuchawaythatthecontractstartdateisonorafterthedeviceinstallationdate.
AnotherissuecanbethatthereisnoUSDPIDassignedtotheaccount.SocheckinES32,underpointofdelivery,clickonGrid,andcheckifUSDPIDisshowingup.Ifnot,arrangetoassignonetotheaccount.
WhileinvoicingyouaregettingtheerrorEXTUIfromINTUI
Solution:
ThisisnormallyindicatingthatthepointofdeliverydateisnotmatchingwithcontractstartdateorUSDPIDdate.InSApmanyoftheerrorsarerelatedtothedatesmismatchornotinorderwithrelatedevents.Sohere,checkthecontractstartdateandmakesurethatpointofdeliverydateisonorBEFOREthecontractstartdate.Ifitisnotso,reverseallbilldocsandthenusingtransactionES31,youcanchangethepointofdeliverydateanditwouldsolvetheproblem
Whenthescheduledbilldatefallsonthesamedatewithmeterremovalornewmeterinstallationdate,andyoutrytoinvoicetheaccount,youmayreceiveerror"existingbillingdocumentscannotbeinvoiced"
Solution:
Inthissituation,wenormallydeletetheschedulebilldateMROsothatwecankeeponlyoneeventforthatdate.Budoingthis,weareessentiallyinvoicing2periodtogetherinsteadofoneandthiswayitwillallowyoutoinvoice.However,whentheaccountisonbudgetbilling,itismandatorythatitneedstobebilledmonthlyandhenceevenafterremovingscheduledbilldateassuggestedabove,itwon'tletyouinvoiceit.
Forbudgetbillingaccounts,weneedtochangetheMRUsothatwehaveadifferentscheduledbilldatethantheearlierscenario.ForexampleifthescheduledbillingdateandCMOfallsonDecember10,thenchangeMRUandnowyouhavescheduledbilldatefallsonDecember9andCMOonDecember10.ReverseallMROsandsendBQrequestsoyoucangetallthereadings.Nowinvoicetheaccountandoncedonesuccessfully,changetheMRUbacktowhatitoriginallywas.Thisisaworkaroundwhichwouldpreventhavingproblemsininvoicingwhentherearemultipleallocationsfallingonthesamedate.
Segmentmissingerror
Whilecreatinginvoices,theuseisgettingthiserror.
SAPISUBillingerrors SAPISUtables SAPISUBillingconcepts RTPBilling Myfriend'spage MetertoCash
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 2/19
Solution:
Thereare3possibilities.
1)TheratecategoryisNONTOUandregistersareTOUoviceversa.Ifthisisso,updatethemcorrectlyandthiserrorshouldnotappearagain.
2)OntheregistertabinES32,oneormoreofthecomponentismissing.Forexample,ForaTOUratecategory,onpeakrateregisterismissing.Ifthisisso,updateitcorrectlyandthisshouldberesolvednow.
3)TherearemultipleinstallationsattachedtoCAandinthecontract,jointinvoicingconditionissetasmandatory.Butwhenyouinvoicetheaccount,itismissingbillingforoneoftheinstallations.Ifthisisso,invoicetheaccounttogetherandthisshouldberesolved.
IFvariantincompatibilityerror
Whileinvoicingthisaccount,theuserreceivesthiserror.
Solution:
Thiserrornormallyindicatesthatthereisagapbetweenthedatesofmeterremovalandnewmeterinstalled.Example:MeterremovedonDecember5andsubsequentnewmeterisinstalledonDecember11.Normallynewmetershouldbeinstalledontheverynextdaytometerremovalsothatthecustomercanbebilledcontinuouslyontheircontract.
Tosolvethiserroryoucaneitherterminatethecontractwiththemeterremovalandenteranewcontractwiththenewmeterinstalled.Thisisrecommendedifthegapbetweenmeterremovalandnewmeterinstallationislarge.Otherwiseyoucanchangethenewmeterinstalleddateonthenextdaytometerremovaldateandshouldbeabletoinvoicetheaccountwithoutanyerrors.
Theactualerrortextwouldlooklikethis.
IFvariantfoundwithincompatiblevalidityperiod
Messageno.AH437
Diagnosis
SchemaUNMwasanalyzedduringbilling.ThisschemacontainsanIFvariant.TheconditionalexecutionofthestepsbetweentheIFandENDIFvariantsrequiressuitablevalidityperiods.ThestepsbetweentheIFandENDIFvariantscannothavealongervalidityperiodthanthestepwiththeIFvariant.Thiswasnotthecase.
SystemResponse
Billingofthecontractisterminated.
Procedure
TheIFENDIFstepsandthestepsbetweenthemcanbelongtodifferentrates.However,youmustthenensurethatthevalidityperiodfortherateoftheIFvariantisnotshorterthanthevalidityperiodfortherateofthestepsbetweentheIFENDIFsteps.
1.Checkthehistoryoftheratedetermination.
2.Forthecurrentcontract,checkthevalidityperiodsfortheratetypesusedtodeterminebothoftherates.
Iftheerrorhasoccurredeventhoughallstepsbelongtothesamerate,thereisprobablyagapinthevalidityperiodfortheratetype.
Example
Youbilltheperiodfrom01/01/1999to12/31/1999.
TheratewiththeIFvariantisdeterminedusingaratetypeoftheregister.
Theregisterisremovedon05/10/1999,andanewregisterisnotinstalleduntil05/12/1999.
TheratewiththeIFvariantisdeterminedinbillingfrom01/01/1999to05/10/1999andfrom05/12/1999to12/31/1999.GapsarenotpermittedforrateswithIFvariants.
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 3/19
Existingbillingdocumentscannotbeinvoicederror
Solution:
Thisiserrorisdueto3possibilities.
1)Whenyoutrytoinvoicemanualdoc(creditmemo)alonewithoutselectingbillingdoc...youcancorrectitbyselectingbillingdocandmanualdoctogether
2)Whenyouhaveanoutsortthatisnotreleased/reversedyet.Tocorrectit,usingtransactionEA05,youcaneitherreleaseorreversetheoutsortandtrytoinvoiceagainanditshouldallowyoutodosonow
3)TheCA(contractaccount)hasmultipleinstallations/contractsattachedtoitwithjointinvoicingconditionandwhileinvoicingyouareselectingonly1contracttoinvoice.Tocorrectthis,sortthebillstart/enddatesothatyoucaninvoiceallthebilldocsforthesameperiodstogether.Ifyouseebillingdocsofonly1contractwhileinvoicing,itmeansthattheothercontractmayhavebeeninvoicedalone.Ifitisso,reversethoseinvoicesusingtransactionEA15andtheninvoicebothcontractstogethernow.
Veryhighamountinvoice
Solution:
Therecanbe2possibilities.
1)Meteroverflowcausingthisissue.Normallywhenyouentermeterreadings,theyareinorderandcurrentmonthreadingishigherthanpreviousmonthreading.Butdueanincorrectmeterreadingentryordeviceissue,thecurrentmonthreadingislowerthanpreviousmonth,whenyoutrytoinvoiceforcurrentmonth,youwouldseeaveryhighamountofinvoice.Tocorrectthis,checkthereadingsagainandcorrectthereadingsandinvoiceagain.
2)Theremaybeanactualreadingthatshowsveryhighconsumptionforaparticularbillingperiod.Forexample,duringfestivaltime,whencustomersdisplaylightingsattheirhomes,theconsumptionistendtobehigherthannormalorseasonallyforsummermonthsduetohigherusageofairconditioning,theconsumptiontendtobehigherthannormal.Checkhistoricalpatterntoseeifthishigherconsumptionmakessense.Ifitismultipletimeshigherthannormalthanthisneedstobeverifiedbyrereadingthemeterorinvestigatinganydeviceissue.
Howtoidentifysyncissuesinbilling?Solution:OnceyousendBQrequestusingZBQR,itcomesbackwithresults/readingsdataintheBQtable.Asshownbyblueline,forsomeperiodsweseeagapandnoBQresponsecode00,itmeansthatthedevicedidnotsyncwithsapforthatperiod.
OnceweresyncitandsendBQrequestagain,thatperiodofdataisfilledbythesystem.Nosynccanalsoresultfromnoncompliantdevice(meter)provisionedontheaccount.Ifthisisso,thenremovethatdeviceandthenoncecorrectdeviceisinstalled,resendtheBQrequestandtheseperiodsshouldfillwithreadings.
IfwereceiveBQresponsecodeas02,itwouldmeanthatthereisadataissueandthedataforthatperiodneedstobecorrected/estimatedasperpredefinedcriteriasasMDMRdoesnothavethedataforthatperiod.
HowtodoIP(Installmentplan)reversalinbilling
FPL9:TogetdocnumberforIP
FPR2:RemoveIP
FP8:Reversecreditclearobstructions
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 4/19
Howtocorrectreplicationerrorinbilling
Solution:
Sometimes,whendataischangedinCRMandintheprocessofreplicationtoISU,itdoesnotgetreplicatedandendsinanerror.ThiserrorisdisplayedandprocessedinISUerrormonitor.
CreatingParkedDocuments
Whenyousavedatathatyouenteredintheacceleratedentryinterface,thesystemcreatesaparkeddocument.Youreceiveamessagetoinformyouifthedataisincorrectorincomplete.Youcanalsocreateaparkeddocumentiferrorsarise.Thisdocumenthasthestatus
FollowUpProcessingforParkedDocuments
Afteryouhavesavedtheparkeddocument,thefollowupprocessingbegins(thecreationofspecificmoveoutsand/ormoveinsinthesystem).Aprerequisiteforthefollowupprocessingisthattheparkeddocumentdatamustbefreeoferrors.
Themoveinandmoveoutdocumentsarenotcreatedimmediately.Thisisdoneusingthemasterdatageneratorandcontractmodels.Theadvantageofthisisthattheagentdoesnothavetowaituntilthemoveinormoveouthasbeencreated,butcancontinuewithhis/herworkassoonastheparkeddocumenthasbeensaved.
TransactionECRMREPL
Errors
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 5/19
AredtrafficlightindicatesthatanerroroccurredduringthereplicationAyellowtrafficlightindicatesthatareplicationattemptalreadyexistsforthereplication,andthatthistransactionwasinsertedinthequeuewithoutstartingthemasterdatagenerator.
Oncewedoubleclickontheerrorandcheckthelog,itmentionstherethereasonfortheerror.Forexample,mismatchofdevicedateandcontractdateetc.Fixthemasnecessaryandthenrestart/resendtheerror.Torestartselectiveormasserrors,clickontheseoptionsfromtopmenu.
Whenrestartingareplicationthatcontainserrors,themasterdatageneratoriscalled,alongwiththeparametersthatmayhavebeenchangedinthedetailedview.Thereplicationisrestartedgenerically,dependinguponthereplicationobject.Thismeansthatwhenyourestartacontractreplication,arestartfunctionmoduleiscalledthatisdifferentto,forexample,therestartforpointsofdelivery,connectionobjectsorparkeddocuments.
ThedifferentfunctionmodulesarestoredintheECRM_FBRESTtable
ThetablekeyisthefieldMD_ORIGOBJ(TransactionECRMREPL),whichisstoredinthetableEVER_CRMQforeachqueueentry.Inthisway,forexample,theincorrectreplicationofapointofdeliveryinthequeuehastheentryEPODinthefieldEVER_CRMQMQ_ORIGOBJ.ThefunctionmoduleISU_CRMQ_RESTART_PODiscalledviathisentryduringtherestart
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 6/19
Examplesofsomeoftheportionsconfiguredforbilling
Consideringinarealprojectscenario,therearemonthly/bimonthly/quarterlybillcyclesandasperclient'srequirement,theyneedtobespacedputtoensurethatthebillsaresentconvenientlywithoutoverloadingthesystem,wemayendupcreatinganumberofportions.
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 7/19
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 8/19
_____________________________________________________________Howtocorrectoutofbalanceinvoicesinbilling_____________________________________________________________Whenthetotalsintheinvoicesdonotaddup,theyareusuallytermedasoutofbalanceinvoice.Someofthereasonswhyinvoicesareoutofbalanceinclude,
Invoicecurrencyandpaymentcurrencyaredifferentthenwhenthepaymentisposted,thesystemcalculatesthat days currencyexchange rate.Nowwhen this invoiceandpaymentwas reversed for some reasonat alaterdateandrecreatedagainandpaymentapplied,thenthesystemconsiderstheexchangerateonthatday.Sonowwehavea$amountdifferencewhichmakesinvoiceoutofbalance.
Another scenariowouldbe, therearecertain itemsupdatedon theaccountbutnotposted fullyor reversed,thenalsoitwouldshowadifferenceof$amount.
Sometimesifthemigrationdocumentwasreversedduetoausererror,thenalsowewouldhaveOOBinvoiceoccur.
Anotherscenariowouldbe if the IPbalancedoesnotmatchupwith theIPamountonthe invoice, thenalsoOOBwouldoccur.
Most of the time, we would use transaction codes fpl9, fpe2, fpr3, ek94, fpd2 and look for necessaryinformationfromthosescreenstoupdatetherdifilesforinvoice.
Givenbelowaresomescenarios.
Whenyoutrytosimulatetheinvoiceandtheerrorlogshowsthatit isoutofbalance,itwillshowtheamountthatitisoutofbalancewith.
Thesameamountyouwouldalsobeabletoseeonrdifile.Forthebelowcase,theoutofbalanceamountis$937.18.Nowweneedtofindoutwherethisdifferenceiscomingfrom.
Therewasamigrationdocumentforthecreditamount$937.18wasreversedinMarch2013,duetowhichtheinvoiceissuedformarchapril2013isshowingoutofbalancewiththatamount.
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%20100 9/19
And we correctedthe RDI file with thesame amount$937.17 with thetext reason asrefund issued sinceyour last bill. Onceyou add the credit(937.17) on theaccount, then your
totaladjustmentalsowouldchangetothateffect.Sototaladjustmentshavebeenupdatedas$2811.65minus$937.17=$1874.47
Scriptforcorrection:
DZCL_BI_PWB=>GS_HDRBAL_FWD2,771.90
DZCL_BI_PWB=>GS_HDRNEW_CHG897.43
DZCL_BI_PWB=>GS_HDRBBP_TTL0.00
DZCL_BI_PWB=>GS_HDRTTL_ADJ2,811.65>>Changeto1874.47
DZCL_BI_PWB=>GS_HDRTTL_DUE0.00
DZCL_BI_PWB=>GS_HDROOB_DIF937.18
DZCL_BI_PWB=>GS_HDRADD_NM1
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_ACC_ADJADJ_TXTBillCorrection
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT924.05
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_ACC_ADJADJ_TXTAmounttransferredtoanotheraccount
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT642.14
DZCL_BI_REG=>GS_FMTDBA_FLGX
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_ACC_ADJADJ_TXT Refund issued since your last bill >> Change to Arrear sinceyourlastbill
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT3,093.56
DZCL_BI_REG=>GS_FMTDBA_FLGX
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
AddtheseRedline
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 10/19
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_ACC_ADJADJ_TXTcreditissuesinceyourlastbill
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT937.18
DZCL_BI_REG=>GS_FMTDBA_FLGX
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_INV_TTLACC_ADJ2,811.65>>Changeto1874.47
DZCL_BI_REG=>GS_INV_TTLACC_TXEX
DZCL_BI_REG=>GS_INV_TTLADJ_TTL2,811.65>>Changeto1874.47
DZCL_BI_PWB=>GC_DOC_ENDX
Anotherscenario:
Below is another scenariowhere the amountwas transferred fromanother account to this account and thatresultedintoanoutofbalanceamountof$8616.90
TherewasaTransferpostingdocument$8616.90.Thedocumenthassubsequentlyreversed.PWBcouldntpickuptransactionproperlyastherewerestatisticalwrittenoffdocuments.
In this case,wehaveadded that amounton the invoiceby removing the sameamount (in red colour lines)totalingthesameamountandatthesametime(ingreencolourlines),showingthesameamountascreditanddebitontheinvoicesocustomercanseethat.Andagain,thetotaladjustmentamountiscorrectedtotheeffectof$8616.90
|DZCL_BI_PWB=>GS_HDRDSP_TYPP
|DZCL_BI_PWB=>GS_HDRLOV_FLGX
|DZCL_BI_PWB=>GS_HDRAMT_LST_BIL0.00
|DZCL_BI_PWB=>GS_HDRNON_ELE_AMT0.00
|DZCL_BI_PWB=>GS_HDRBAL_FWD4,308.45
|DZCL_BI_PWB=>GS_HDRNEW_CHG603.99
|DZCL_BI_PWB=>GS_HDRBBP_TTL0.00
|DZCL_BI_PWB=>GS_HDRTTL_ADJ8,984.80>>changeto>>367.90
|DZCL_BI_PWB=>GS_HDRTTL_DUE4,072.36
|DZCL_BI_PWB=>GS_HDROOB_DIF8,616.90
|DZCL_BI_PWB=>GS_HDRADD_NM1
|DZCL_BI_PWB=>GS_HDRADD_NM2
|DZCL_BI_REG=>GS_TOTALSNEW_ELECTR603.99
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTAccountsetupcharge
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT30.00
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
>>AddthelinesinGREEN>>
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 11/19
DZCL_BI_REG=>GS_ACC_ADJADJ_TXTAmounttransferredfromanotheraccount
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT8,616.90
DZCL_BI_REG=>GS_FMTDBA_FLGX
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCancel:Amounttransferredfromanotheraccount
DZCL_BI_REG=>GS_ACC_ADJADJ_AMT8,616.90
DZCL_BI_REG=>GS_FMTDBA_FLGX
CINCENDZBI_BPC_ACC_ADJTEXTSTEN
>>DeletethelinesinRED>>
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCancel:
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT364.14
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCancel:
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT7,199.32
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCancel:
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT1,053.44
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCreditappliedsinceyourlastbill
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT401.80
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTHST(870865821RT0001)
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT3.90
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_INV_TTLACC_ADJ8,984.80>>changeto>>367.90
|DZCL_BI_REG=>GS_INV_TTLACC_TXEX
|DZCL_BI_REG=>GS_INV_TTLADJ_TTL8,984.80>>changeto>>367.90
|DZCL_BI_PWB=>GC_DOC_ENDX
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 12/19
Anotherscenario
Onthisinvoice,theOOBdifferenceis$33.90whichiseasytoidentifyasinourcompany,wecharge$30asaccountsetupfeeand13%taxonthatwouldmakeitatotalof$33.90.SonowwewillbelookingforaccountsetupchargeentriesonFPL9.
TheinvoiceincludesAccountsetupchargeofcontract400248528butthischargeshouldbeincludedinthefirstperiodicinvoiceofthecontract400248528.Thenewaccountsetupchargehascorrectlybeenincludedininvoicefirstperiodicinvoice60001890876ofcontract400248528.
The account setup charge is wrongly included in invoice 60001924616. I have removed the account setupchargeintheRDIfile
And we did in earlier invoice corrections, we need to adjust the total adjustment amount to the effect of$33.90.
|DZCL_BI_PWB=>GS_HDRNON_ELE_AMT0.00
|DZCL_BI_PWB=>GS_HDRBAL_FWD315.11
|DZCL_BI_PWB=>GS_HDRNEW_CHG217.83
|DZCL_BI_PWB=>GS_HDRBBP_TTL0.00
|DZCL_BI_PWB=>GS_HDRTTL_ADJ163.33>>Changeto>>129.43
|DZCL_BI_PWB=>GS_HDRTTL_DUE662.37
|DZCL_BI_PWB=>GS_HDROOB_DIF33.90
|DZCL_BI_PWB=>GS_HDRADD_NM1MRS.ELIZABETHARMSTRONG
|DZCL_BI_PWB=>GS_HDRADD_LN11561ORMSBEERD
|DZCL_BI_PWB=>GS_HDRADD_LN2BATTERSEAONK0H1H0
|DZCL_BI_PWB=>GS_HDRZIP_CODK0H1H0
|DZCL_BI_REG=>GS_TOTALSNEW_ELECTR217.83
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTBillCorrectionInstalment(remainingbalance$778.70)
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT129.79
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
>>DeletethelinesinRED>>
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTAccountsetupcharge
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT30.00
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTInterestearnedonyoursecuritydeposit
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT0.36
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
>>DeletethelinesinRED>>
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTHST(870865821RT0001)
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 13/19
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT3.90
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_INV_TTLACC_ADJ163.33>>Changeto>>129.43
|DZCL_BI_REG=>GS_INV_TTLACC_TXEX
|DZCL_BI_REG=>GS_INV_TTLADJ_TTL163.33>>Changeto>>129.43
|DZCL_BI_PWB=>GC_DOC_ENDX
AnotherscenarioHerewecanseetheOOBdifferenceamountis$141.
OnthepaymentstabinFPL9,
The payment received on Aug 2014 was $298.99 but the payment showing on the invoice for that date is$157.99.Sothatsadifferenceof$141whichisouroutofbalanceamount.
Thesecuritydepositwasrequested$422.00andpaid.Thesecuritydeposit$141.00wasreturned/reversedon20150120whichisafterperiodicbillgeneratedforperiodbill forDecember2014(i.e.20141119to20141217).
|DZCL_BI_PWB=>GS_HDRAMT_LST_BIL0.00
|DZCL_BI_PWB=>GS_HDRNON_ELE_AMT0.00
|DZCL_BI_PWB=>GS_HDRBAL_FWD1,066.72>>changeto>>1,207.72
|DZCL_BI_PWB=>GS_HDRNEW_CHG77.26
|DZCL_BI_PWB=>GS_HDRBBP_TTL0.00
|DZCL_BI_PWB=>GS_HDRTTL_ADJ173.37>>changeto>>455.37
|DZCL_BI_PWB=>GS_HDRTTL_DUE675.09
|DZCL_BI_PWB=>GS_HDROOB_DIF141.00
|DZCL_BI_PWB=>GS_HDRADD_NM1
|DZCL_BI_PWB=>GS_HDRADD_LN1
|DZCL_BI_PWB=>GS_HDRADD_LN2
|DZCL_BI_PWB=>GS_HDRZIP_COD
|DZCL_BI_PWB=>GS_HDRCOUNTRY
|DZCL_BI_PWB=>GS_HDRCMP_ACT_CNT0
|CINCENDZBI_BPC_HDRTEXTSTEN
|CINCBEGINZBI_BPC_PYM_DTLTEXTSTEN
|DZCL_BI_REG=>GS_PYMDAT08/18/2014
|DZCL_BI_REG=>GS_PYMAMT157.99>>changeto>>298.99
|CINCENDZBI_BPC_PYM_DTLTEXTSTEN
|CINCBEGINZBI_BPC_PYM_DTLTEXTSTEN
|DZCL_BI_REG=>GS_PYMDAT09/25/2014
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 14/19
|DZCL_BI_REG=>GS_PYMAMT212.99
|CINCENDZBI_BPC_PYM_DTLTEXTSTEN
|CINCBEGINZBI_BPC_PYM_DTLTEXTSTEN
|DZCL_BI_REG=>GS_PYMDAT01/15/2015
|DZCL_BI_REG=>GS_PYMAMT695.74
|CINCENDZBI_BPC_PYM_DTLTEXTSTEN
|DZCL_BI_PWB=>GS_HDRMKT_INS1000000000
|DZCL_BI_REG=>GS_TOTALSNEW_ELECTR77.26
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTSecurityDepositInstalmentPlancreatedonJuly03,2014
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT281.00
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXT Security Deposit Instalment (remaining balance $46.83) >>changeremainingbalanceto>>$0.00
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT281.00
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTAccountsetupcharge
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT30.00
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTInterestearnedonyoursecuritydeposit
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT0.53
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTSecuritydeposit
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT281.00>>changeto>>422.00
|DZCL_BI_REG=>GS_FMTDBA_FLGX
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
>>Deletethelinesinred
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTCancel:Securitydeposit
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT141.00
|DZCL_BI_REG=>GS_FMTDBA_FLGX
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 15/19
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|CINCBEGINZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_ACC_ADJADJ_TXTHST(870865821RT0001)
|DZCL_BI_REG=>GS_ACC_ADJADJ_AMT3.90
|CINCENDZBI_BPC_ACC_ADJTEXTSTEN
|DZCL_BI_REG=>GS_INV_TTLACC_ADJ173.37>>changeto>>455.37
|DZCL_BI_REG=>GS_INV_TTLACC_TXEX
|DZCL_BI_REG=>GS_INV_TTLADJ_TTL173.37>>changeto>>455.37
|DZCL_BI_PWB=>GC_DOC_ENDX
Invoice60002187484:
On thebelow invoice,wecansee that thepaymentamountonApril 2014hasbeenposted incorrectly.Thepayment received was $150 but the posted amount is $49.93 and hence we have a OOB difference of$100.07.Ithasbeencorrectedasbelow.
|CINCBEGINZBI_BPC_PYM_DTLTEXTSTEN
|DZCL_BI_REG=>GS_PYMDAT04/07/2014
|DZCL_BI_REG=>GS_PYMAMT49.93>>>>>changeto150.00
|CINCENDZBI_BPC_PYM_DTLTEXTSTEN
|CINCBEGINZBI_BPC_HDRTEXTSTEN
|DZCL_BI_PWB=>GS_INDINV_OOBX
|DZCL_BI_PWB=>GS_INDOOB_PDFX
|DZCL_BI_PWB=>GS_INDSTD_SUPX
|DZCL_BI_PWB=>GS_HDRSAP_SYSPEC
|DZCL_BI_PWB=>GS_HDRSAP_CLT101
|DZCL_BI_PWB=>GS_HDRUSR_NAM004014
|DZCL_BI_PWB=>GS_HDRFMT_TYPREGULATED_BILL
|DZCL_BI_PWB=>GS_HDRNUM_CPS1
|DZCL_BI_PWB=>GS_HDROUT_DVCZSTRS_TST
|DZCL_BI_PWB=>GS_HDRSPL_NAMInvoice60002187484
|DZCL_BI_PWB=>GS_HDRLGG_PRFEN
|DZCL_BI_PWB=>GS_HDRACT_CNT2
|DZCL_BI_PWB=>GS_HDRBIL_CNT1
|DZCL_BI_PWB=>GS_HDRINV_NUM60002187484
|DZCL_BI_PWB=>GS_HDRACT_NUM200080981328
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 16/19
|DZCL_BI_PWB=>GS_HDRBIL_DAT02/26/2015
|DZCL_BI_PWB=>GS_HDRINV_MTH02/01/2014
|DZCL_BI_PWB=>GS_HDRSTR_DAT01/24/2014
|DZCL_BI_PWB=>GS_HDREND_DAT02/15/2014
|DZCL_BI_PWB=>GS_HDRREP_DAT02/26/2015
|DZCL_BI_PWB=>GS_HDRBIL_CYC07
|DZCL_BI_PWB=>GS_HDRSRV_NM1
|DZCL_BI_PWB=>GS_HDRSRV_ADD
|DZCL_BI_PWB=>GS_HDRCSV_INQ3
|DZCL_BI_PWB=>GS_HDRCSV_ARR0.00
|DZCL_BI_PWB=>GS_HDRDUE_DAT02/26/2015
|DZCL_BI_PWB=>GS_HDRGLS_TYP4
|DZCL_BI_PWB=>GS_HDRDSP_TYPP
|DZCL_BI_PWB=>GS_HDRLOV_FLGX
|DZCL_BI_PWB=>GS_HDRAMT_LST_BIL349.93
|DZCL_BI_PWB=>GS_HDRNON_ELE_AMT0.00
|DZCL_BI_PWB=>GS_HDRBAL_FWD1,175.00>>>>>changeto1,275.07
|DZCL_BI_PWB=>GS_HDRNEW_CHG332.68
|DZCL_BI_PWB=>GS_HDRBBP_TTL0.00
|DZCL_BI_PWB=>GS_HDRTTL_ADJ64.83
|DZCL_BI_PWB=>GS_HDRTTL_DUE877.56
|DZCL_BI_PWB=>GS_HDROOB_DIF100.07
|DZCL_BI_PWB=>GS_HDRADD_NM1MRS.JOANHERMER
|DZCL_BI_PWB=>GS_HDRADD_LN17610HWY509
|DZCL_BI_PWB=>GS_HDRADD_LN2RR1
|DZCL_BI_PWB=>GS_HDRADD_LN3PLEVNAONK0H2M0
|DZCL_BI_PWB=>GS_HDRZIP_CODK0H2M0
|DZCL_BI_PWB=>GS_HDRCOUNTRYCanada
|DZCL_BI_PWB=>GS_HDRSCN_LIN2000809813280000000007
|DZCL_BI_PWB=>GS_HDRSTB_TTL0.00
|DZCL_BI_PWB=>GS_HDRCMP_ACT_CNT0
|CINCENDZBI_BPC_HDRTEXTSTEN
0Comments
12/27/2014 0CommentsSAPISUbillingconcepts
BelowaresomeimportantbasicterminologyforSAPISUBillinganditneedstobeconfiguredfirst.
Tweet
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 17/19
Billingschema
Rate
Facts
Ratefactsgroup
Pricekey
Operand
Ratecategory
Ratetype
Ratedetermination
Masterdatacreation(BMD+TMD)
0Comments
12/27/2014 0CommentsSAPISUtables
Masterdata:
EKUNISUbusinesspartnerdata
BUT050Businesspartnerrelationships
BUT100Businesspartnerroles
BUT020Businesspartneraddress
ADRCAddresses
BUT000Businesspartner
DFKKLOCKSBusinesslocks
FKKVKPContractaccountforpartner
FKKVKContractaccount
Billingandinvoicing:
ERDKPrintdocheader
ERDOOutsortingforinvoices
ERDBCAdocumentforprintdocument
ERCHOOutsortingforbillingdocument
ERCHCInvoicingreversalhistory
ERCHBillingdocheader
DBERCHZ(18)Billingdoclines
Tweet
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 18/19
DBERDLPrintdoclines
DBERDLBBillingdocprintdoclinereference
Billingmasterdata:
ETTARatecategory
ETTAFRatecategoryfacts
TE221Operands
ETRFRates
EKDIRatefacts
ESCHSBillingschemasteps
ESCHSBillingschemaheader
EPREIHPricehistory
EPREIPricesheader
TE069Ratetypes
ETTIF/ETTIFN/ETTIFBInstallationfacts
ERTFNDRatedetermination
Technicalmasterdata
EANLInstallation
EVBSPremise
EHAUISUConnectionobject
EANLHInstallationtimeslice
EGPLTXDevicelocations
EUIHEADPoDs
EUITRANSPoDinternaltoexternalIds
DeviceManagement
ETDZRegisters
EPROFASSRegistersprofiles
EASTIRegisterrelationships
EUILZWRegisterPod
EASTSInstallationregister
6/4/2015 SAPISUBillingSAPISUBillingerrors
data:text/htmlcharset=utf8,%3Cdiv%20id%3D%22wrapper%22%20style%3D%22minheight%3A%20100%25%3B%20margin%3A%200px%200px%2010 19/19
sap,isu,sapisu,utilities,saputilities,RTPbilling,billingerrors,sapbillingerrors,saptables,sapforums,saptraining,sapisutraining,india,canada,US,england,germany,rajivjani,lifecoachformysuccess,saphelp
EADZMultipleinstallationbillingdataregisters
EZWDRegisterGroups
EZUZDeviceallocationforregisters
EGERHHistoricaldevicedata
EGERSmasterdevicedata
EGERRDeviceinfoforPod
EUILNRDevicePod
ETYPDevicecategorymaterialdata
EZUGDeviceallocationfordevice
Scheduling
TE422Meterreadingunits
TE418Schedulerecordsmeterreadingunits
TE420Portions
TE419Parameterrecords
TE417Schedulerecordsforportion
ETRGBillingorders
EABLMeterreadingdocument
EABLGMeterreadingreasons
0Comments
FREEWEBSITE POWEREDBY