This discussion is archived
2 Replies Latest reply: Jan 9, 2013 11:27 PM by ajoo RSS

Does manual punching of meter reads require MDS batch ?

ajoo Newbie
Currently Being Moderated
Hi,

Our client is having a large number of consumers (more than 90% ) as Non-AMR based meters,i.e. meter reads for these consumers are being taken manually (meter reading diaries) and are getting punched manually in the system.
For this scenario ,is it mandatory to run MDS batch before Billing Batch?
  • 1. Re: Does manual punching of meter reads require MDS batch ?
    Gurumoorthy Explorer
    Currently Being Moderated
    Not necessary. The MDS process used to extract meter details for HHU or any other system which reads the meter read.
  • 2. Re: Does manual punching of meter reads require MDS batch ?
    ajoo Newbie
    Currently Being Moderated
    True, but when we are not running MDS batch for consumers whose readings are punched manually , the Billing Batch "Skips" the accounts for Billing.Also the same thing has been raised by me on Oracle support as well. Please find below the reply of Oracle support Team(in italics),which depicts that scheduling is must.



    SR Number- SR- 3-4859324851
    +"Let's take a look at the Acct Id '0019000000' highlighted in yellow in the uploaded SR_Batch_Billing_Error.xlsx as the one with no bill generated.+

    +Before we start going through the billing trace, please familiarize yourselves with the On-line User Help, Business Process, Billing --> The Big Picture of Billing --> How The System Determines How Much Was Consumed. It is very important to have a clear understanding of the topics explained in this help documentation.+

    +According to the BILLING.20111101101221.34.THD1.stdout, Acct Id '0019000000' is on the Bill Cycle 'BC99':+

    +10:12:24,855 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLHelper) SQL execution 'open dynamic cursor' request for cobol program 'CIPBBILB' SQL name 'S_ACCT'+
    +SQL from cobol: SELECT ACCT_ID, BILL_CYC_CD FROM CI_ACCT WHERE ACCT_ID BETWEEN @SPL_VAR1@ AND @SPL_VAR2@ AND BILL_CYC_CD IN ( 'BC99') ORDER BY ACCT_ID+
    +Indexed SQL from metadata: null+
    +Inputs:+
    +xEND-ACCT-ID : '9999999999' [ParamMetaData {name='xEND-ACCT-ID', type='C', size=10, scale=0, column=-1, isNullUsed=false, offset = 16}]+
    +xSTART-ACCT-ID : '0000000000' [ParamMetaData {name='xSTART-ACCT-ID', type='C', size=10, scale=0, column=-1, isNullUsed=false, offset = 4}]+
    +10:12:24,859 [CobolThread 45] INFO (COBOL.CIPBBILB) 2011-11-01-10.12.21 User: SYSUSER 10:12:24.85 SQL E: S_ACCT -> O+
    +10:12:24,859 [CobolThread 45] INFO (COBOL.CIPBBILB) 2011-11-01-10.12.21 User: SYSUSER 10:12:24.85 SQL S: S_ACCT -> F+
    +10:12:24,859 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLClient) Fetch results for CIPBBILB SQL S_ACCT+
    +xACCT-ID : '0019000000' (Char) [ParamMetaData {name='xACCT-ID', type='C', size=10, scale=0, column=1, isNullUsed=false, offset = 4}]+
    +xBILL-CYC-CD : 'BC99'+


    +Note that the previous bill for the account was created for Bill Cycle 'BC01' (different from the current one).+
    +The new bill Id being added is '001901145536'.+

    +Acct Id '0019000000' has three SAs:+

    +1. The first SA retrieved for the account is SA-ID '0019000892'. It is a Cash Deposit SA:+
    +xSPECIAL-ROLE-FLG : 'CD'+
    +It has no recurring charges, so there is nothing to bill. This SA is skipped.+

    +2. The second SA retrieved is SA-ID '0019000893'. Its SA Type is not eligible for billing:+
    +xSA-TYPE-CD : 'CM_JLPC '+
    +xALLOW-BILLING-SW : 'N'+

    +3. The third SA retrieved is SA-ID '0019000894'.+

    +xSA-TYPE-CD : 'CM_JPMGD'+
    +xALLOW-SP-SW : 'Y'+
    +xBILL-SEG-TYPE-CD : 'SP-RATED'+
    +xALLOW-EST-SW : 'Y'+

    +Note that the previous bill segment was created for a different bill cycle 'BC01':+
    +10:12:25,251 [CobolThread 45] INFO (COBOL.CIPBBLSG) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.25 SQL S: S_PREVBS -> F+
    +10:12:25,251 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLClient) Fetch results for CIPBBLSG SQL S_PREVBS+
    +xBSEG-ID : '001900217346' (Char) [ParamMetaData {name='xBSEG-ID', type='C', size=12, scale=0, column=1, isNullUsed=false, offset = 4}]+
    +xSTART-DT : '2011-07-24' (Date) [ParamMetaData {name='xSTART-DT', type='D', size=10, scale=0, column=2, isNullUsed=true, offset = 18}]+
    +xEND-DT : '2011-08-19' (Date) [ParamMetaData {name='xEND-DT', type='D', size=10, scale=0, column=3, isNullUsed=true, offset = 30}]+
    +xBILL-CYC-CD : 'BC01' (Char) [ParamMetaData {name='xBILL-CYC-CD', type='C', size=4, scale=0, column=4, isNullUsed=false, offset = 42}]+
    +xWIN-START-DT+

    +The previous bill segment's End Date is 2011-08-19.+

    +The SA's Rate Schedule RS-CD 'LV1.2 ' uses 'MONTHLY' Frequency with the Min Offset Days equal to 15 an Max Offset Days equal to15.+

    +The SA's SP is on Service Cycle MR-CYC-CD 'SH72'.+

    +Determine the SP Start Read for the new bill segment (get Latest meter read for the SP on the previous frozen bill segment):+
    +10:12:25,289 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.28 SQL S: S_SPLATRD -> O+
    +10:12:25,289 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLHelper) SQL execution 'open cursor' request for cobol program 'CIPBBSR1' SQL name 'S_SPLATRD'+
    +SQL from cobol: SELECT C.MR_ID, C.READ_DTTM FROM CI_BSEG_READ A, CI_REG_READ B, CI_MR C WHERE A.BSEG_ID = :xBSEG-ID AND A.SP_ID = :xSP-ID AND A.END_REG_READ_ID = B.REG_READ_ID AND B.MR_ID = C.MR_ID ORDER BY C.READ_DTTM DESC+
    +Indexed SQL from metadata: SELECT C.MR_ID, C.READ_DTTM FROM CI_BSEG_READ A, CI_REG_READ B, CI_MR C WHERE A.BSEG_ID = ? AND A.SP_ID = ? AND A.END_REG_READ_ID = B.REG_READ_ID AND B.MR_ID = C.MR_ID ORDER BY C.READ_DTTM DESC+
    +Inputs:+
    +xBSEG-ID : '001900217346' [ParamMetaData {name='xBSEG-ID', type='C', size=12, scale=0, column=-1, isNullUsed=false, offset = 4}]+
    +xSP-ID : '0019000479' [ParamMetaData {name='xSP-ID', type='C', size=10, scale=0, column=-1, isNullUsed=false, offset = 18}]+
    +10:12:25,290 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.29 SQL E: S_SPLATRD -> O+
    +10:12:25,290 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.29 SQL S: S_SPLATRD -> F+
    +10:12:25,290 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLClient) Fetch results for CIPBBSR1 SQL S_SPLATRD+
    +xMR-ID : '001900130255' (Char) [ParamMetaData {name='xMR-ID', type='C', size=12, scale=0, column=1, isNullUsed=false, offset = 4}]+
    +xREAD-DTTM : '2011-08-19-00.00.00.000000'+


    +Determine the SP End Read for the new bill segment:+
    +Determine the Read Search Period (RSP) for the end read:+
    +The system looks for the next scheduled meter read date. Not just any date can be used, the system attempts to find a read that meets the following criteria:+

    +• Is after the end date of the last bill segment plus the rate’s frequency’s minimum offset days (2011-08-19 + 15 days = 2011-09-03), and+

    +• Is on/before the cutoff date of the bill (2011-11-01):+

    +10:12:25,293 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.29 SQL S: S_SPMRSCH -> O+
    +10:12:25,293 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLHelper) SQL execution 'open cursor' request for cobol program 'CIPBBSR1' SQL name 'S_SPMRSCH'+
    +SQL from cobol: SELECT SCHED_READ_DT FROM CI_MR_SCHED WHERE MR_CYC_CD = :xMR-CYC-CD AND SCHED_READ_DT > :xSTART-DT AND SCHED_READ_DT <= :xEND-DT AND SCHED_READ_DT <= :xPROCESS-DT ORDER BY SCHED_READ_DT DESC+
    +Indexed SQL from metadata: SELECT SCHED_READ_DT FROM CI_MR_SCHED WHERE MR_CYC_CD = ? AND SCHED_READ_DT > ? AND SCHED_READ_DT <= ? AND SCHED_READ_DT <= ? ORDER BY SCHED_READ_DT DESC+
    +Inputs:+
    +xEND-DT : '2011-11-01' [ParamMetaData {name='xEND-DT', type='D', size=10, scale=0, column=-1, isNullUsed=false, offset = 22}]+
    +xPROCESS-DT : '2011-11-01' [ParamMetaData {name='xPROCESS-DT', type='D', size=10, scale=0, column=-1, isNullUsed=false, offset = 34}]+
    +xMR-CYC-CD : 'SH72' [ParamMetaData {name='xMR-CYC-CD', type='C', size=4, scale=0, column=-1, isNullUsed=false, offset = 4}]+
    +xSTART-DT : '2011-09-03' [ParamMetaData {name='xSTART-DT', type='D', size=10, scale=0, column=-1, isNullUsed=false, offset = 10}]+
    +10:12:25,295 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.29 SQL E: S_SPMRSCH -> O+
    +10:12:25,295 [CobolThread 45] INFO (COBOL.CIPBBSR1) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.29 SQL S: S_SPMRSCH -> F+
    +10:12:25,295 [CobolThread 45] INFO (com.splwg.base.support.cobol.host.sql.CobolSQLClient) Fetch results for CIPBBSR1 SQL S_SPMRSCH+
    +End of rows+

    +The above statement shows that there are no scheduled reads between 2011-09-03 and 2011-11-01 for MR-CYC-CD 'SH72'.+

    +If no such meter read date could be found, the service agreement is skipped (if the SP has no meter read cycle schedule within the bill segment period, then just skip the SA. Note: there must be meter read cycle schedules for all SPs of the SA for the SA to be billed).+

    +There are no other financial transactions to be swept on this bill, so the bill (initially created) is deleted. The trace shows that the account has been processed:+
    +10:12:25,428 [CobolThread 45] INFO (COBOL.CIPBBILG) 2011-11-01-10.12.21 User: SYSUSER 10:12:25.42 End : CIPBBILG+
    +10:12:25,428 [CobolThread 45] INFO (COBOL.CIPBBILB) 0019000000 - updated but not billed"+


    Kindly suggest.



    Regards,
    Ajeet Thakur
    ajeetthakur03@gmail.com
    Ph No 9424926167

    Edited by: 979273 on Jan 9, 2013 11:23 PM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points