Friday, 16 January 2015

COBOL

COBOL stands for Common Business Oriented Language.The US Department of Defense, in a conference, formed CODASYL (Conference on Data Systems Language) to develop a language for business data processing needs which is now known as COBOL.
COBOL is used for writing application programs and we cannot use it to write system software. The applications like those in defense domain, insurance domain, etc. which require huge data processing make extensive use of COBOL.
COBOL is a high-level language. One must understand the way COBOL works. Computers only understand machine code, a binary stream of 0s and 1s. COBOL code must be converted into machine code using a compiler. Run the program source through a compiler. The compiler first checks for any syntax errors and then converts it into machine language. The compiler creates a output file which is known as load module. This output file contains executable code in the form of 0s and 1s.

Evolution of COBOL

During 1950s, when the businesses were growing in the western part of the world, there was a need to automate various processes for ease of operation and this gave birth to a high-level programming language meant for business data processing.
  • In 1959, COBOL was developed by CODASYL (Conference on Data Systems Language).
  • The next version, COBOL-61, was released in 1961 with some revisions.
  • In 1968, COBOL was approved by ANSI as a standard language for commercial use (COBOL-68).
  • It was again revised in 1974 and 1985 to develop subsequent versions named COBOL-74 and COBOL-85 respectively.
  • In 2002, Object-Oriented COBOL was released, which could use encapsulated objects as a normal part of COBOL programming.

Importance of COBOL

  • COBOL was the first widely used high-level programming language. It is an English-like language which is user friendly. All the instructions can be coded in simple English words.
  • COBOL is also used as a self-documenting language.
  • COBOL can handle huge data processing.
  • COBOL is compatible with its previous versions.
  • COBOL has effective error messages and so, resolution of bugs is easier.

Features of COBOL

Standard Language

COBOL is a standard language that can be compiled and executed on machines such as IBM AS/400, personal computers, etc.

Business Oriented

COBOL was designed for business-oriented applications related to financial domain, defense domain, etc. It can handle huge volumes of data because of its advanced file handling capabilities.

Robust Language

COBOL is a robust language as its numerous debugging and testing tools are available for almost all computer platforms.

Structured Language

Logical control structures are available in COBOL which makes it easier to read and modify. COBOL has different divisions, so it is easy to debug.


A COBOL program structure consists of divisions as shown in the following image:
Program Structure
A brief introduction of these divisions is given below:
  • Sections are the logical subdivision of program logic. A section is a collection of paragraphs.
  • Paragraphs are the subdivision of a section or division. It is either user-defined or a predefined name followed by a period, and consists of zero or more sentences/entries.
  • Sentences are the combination of one or more statements. Sentences appear only in the Procedure division. A sentence must end with a period.
  • Statements are meaningful COBOL statement that performs some processing.
  • Characters are the lowest in the hierarchy and cannot be divisible.

Divisions

COBOL program consists of four divisions.

Identification Division

It is the first and only mandatory division of every COBOL program. The programmer and the compiler use this division to identify the program. In this Division, PROGRAM-ID is the only mandatory paragraph. PROGRAM-ID specifies the program name that can consist 1 to 30 characters.

Environment Division

Environment division is used to specify input and output files to the program. It consists of two sections:
  • Configuration section provides information about the system on which the program is written and executed. It consists of two paragraphs:
    Source computer : System used to compile the program.
    Object computer : System used to execute the program.
  • Input-Output section provides information about the files to be used in the program. It consists of two paragraphs:
    File control : Provides information of external data sets used in the program.
    I-O control : Provides information of files used in the program.

Data Division

Data division is used to define the variables used in the program. It consists of four sections:
  • File section is used to define the record structure of the file.
  • Working-Storage section is used to declare temporary variables and file structures which are used in the program.
  • Local-Storage section is similar to Working-Storage section. The only difference is that the variables will be allocated and initialized every time program a starts execution.
  • Linkage section is used to describe the data names that are received from an external program.

Procedure Division

Procedure division is used to include the logic of the program. It consists of executable statements using variables defined in the data division. In this division, paragraph and section names are user-defined.
There must be at least one statement in the procedure division. The last statement to end the execution in this division is either STOP RUN which is used in the calling programs orEXIT PROGRAM which is used in the called programs.

EXAMPLE

000100 INDENTIFICATION DIVISION.
     000110 PROGRAM-ID.    EXAMPLE-1-PROG.
     000120 AUTHOR.    ZINGMATTER.
     000130 INSTALLATION.  XYZ GROUP.
     000140 DATE-WRITTEN.  17/5/00.
     000150 DATE-COMPILED.
     000160 SECURITY.      LOCAL GROUP.

000260 ENVIRONMENT DIVISION.
     000270 CONFIGURATION SECTION.
     000280 SOURCE-COMPUTER.   IBM PC.
     000290 OBJECT-COMPUTER.   IBM PC.
     000300 INPUT-OUTPUT SECTION.
     000310 FILE-CONTROL.
     000320    SELECT INPUT-FILE ASSIGN TO 'input.dat'
     000330      ORGANIZATION IS LINE SEQUENTIAL.
     000340    SELECT PRINT-FILE ASSIGN TO PRINTER.

000400 DATA DIVISION.
     000410 FILE SECTION.
     000420 
     000430 FD INPUT-FILE.
     000440 01 CUSTOMER-DATA.
     000450       03 NAME       PIC X(12).
     000460       03 ADDRESS.
     000470             05 HOUSE-NUMBER   PIC 99.
     000480             05 STREET         PIC X(19).
     000490             05 CITY           PIC X(13).
     000500       03 CUST-NUMBER PIC 9(6).

000900 PROCEDURE DIVISION.
     000910 CONTROL-PARAGRAPH.
     000920       PERFORM READ-DATA-FILE
     000930       PERFORM CALULATE-PRICES
     000940       PERFORM PRINT-PRICE-REPORT
     000950       STOP RUN.





CP-22 LINE LOSSES REPORTS

CP-22 LINE LOSSES REPORTS


            The electricity, generated in Power Houses, is distributed among the consumers via grid stations through 11 KV Feeders.  The total electricity generated in Power Houses is not 100% assessed in the billing.  Some losses may occur due to the following reasons:-

          TECHNICAL LOSSES:-
           
These are the losses, which may occur due to continuous sparking on sub-standard lines.  This is merely because of obsolete transmission system.

          ADMINISTRATIVE LOSSES:-
           
Some dishonest consumers involve in the theft of electricity i.e. physically the electricity is consumed but not taken into account for the purpose of billing.  These losses are called as administrative losses.

            A procedure has been introduced for accumulation of such losses. Line losses reports called as CP-22 reports are prepared in the computer centres. These reports reflect monthly/progressive number of units received, billed and lost in respect of each feeder. Percentage losses are calculated on the basis of units received at feeder, sub division, division, circle and company level. 

UNITS RECEIVED:-

These are the units sent out by the grid stations for the purpose of distribution among the consumers.  For this purpose meters are installed against each 11 KV feeder at the grid stations.  The reading is recorded by the SSO / in-charge of the grid station on the last date of the month exactly at 24:00.  Units received are the difference of present reading and the reading recorded in the previous month after proper application of multiplying factor. 

UNITS BILLED:-

The units, which are accounted for the purpose of billing in one billing cycle, are called as units billed.  These are the units actually sold to the consumers and are taken from the monthly billing statements at the end of each billing cycle.

UNITS LOST:-

            This is the difference of units received from grid stations and units billed in that billing cycle in respect of each feeder.  These are the units, which are actually lost during transmission due to technical / administrative reasons.

The reading of each feeder of the grid is recorded at the grid stations and is supplied to the computer centre through following inputs:-

            CP-22 B                      11 KV Feeder wise units sent out from Grid Stations.
            CP-22 C                      Grid station meter change/meter reading correction statement.

DISPATCH OF CP-22B PRE-ENTRY LIST:-

After processing the additions / changes received (i.e. allotment of new feeder or any change in feeder particulars) CP-22B pre-entry list is processed at least five or six days prior to the date of reading.  This list acts like blank meter reading list having feeder code, name of feeder, previous reading, meter range and multiplying factor pre-printed and keeping the present reading, units sent out, round completion code and meter status code column blank.  CP-22B pre-entry list is checked in the following manner before dispatch to S.S.&T. divisions:-

-           Check the billing month printed in the list as current billing month ended
-           Confirm that all the changes / additions have been effected successfully.
-           Verify the previous reading in few cases from the readings of CP-22B of previous month.
-           Check the printing quality of the list.
CP-22B pre-entry list is printed grid station wise.  This list is sorted according to the jurisdiction of S.S.&T. divisions.  The page numbers are recorded in the dispatch register and sent to concerned S.S.&T. division by mail.

RECORDING OF READINGS IN CP-22B PRE-ENTRY LIST:-

After receiving from computer centre the concerned S.S.&T. division handed over the CP-22B pre-entry list to the SSO/In-charges of grid stations.  They record present reading in the respective columns against each feeder on last day of the month at 24:00.  Units sent out are calculated after proper application of multiplying factor and entered in the relevant column.  Round completion code “C” is also entered in the round completion code column where the meter has completed its round.  In case, where the old meter replaced by new one, code “R” is entered in the meter status code column. Each page of CP-22 B pre-entry list is to be signed by the Deputy Manager, S.S.&T. division concerned.  Meter readings are recorded as per range of the meter upto maximum 13 digits keeping the right three digits as decimal points.  Units sent out are recorded upto maximum 13 digits and have no decimal point at all.

FILLING OF CP-22C GRID STATION METER CHANGE/METER READING CORRECTION STATEMENT:-

CP-22C Grid Station meter change / meter reading correction statement is filled in all the cases where old meter is being replaced by a new one.  Following procedure is adopted to fill in the CP-22C statement:-

-           Enter the billing month on the top of CP-22C as current billing month ended.
-           The name of grid station must also be entered on the top of the form.
-           Enter a valid feeder code existing in the feeder table as well as in CP-22 master file.
-           Name of the feeder is also entered.
-           Meter number of the new meter installed must be filled in the meter number column.
-           Two digits maximum range of the meter is required to be entered in the meter range column.  The range of the meter must be from “04” up to “10”.
-           Multiplying factor of new meter installed upto maximum “9” digits must be entered in the respective column.  The right three digits represent the decimal points.
-           Enter the reading at which the old meter is removed as final reading.  The reading must be entered upto maximum “13” digits keeping the last three digits as decimal points.
-           Enter the initial reading of new meter installed upto maximum “13” digits keeping the right side three digits as decimal points.
-           CP-22C statement must also to be signed by the Deputy Manager S.S. & T. division concerned.

RECEIPT OF CP-22B AND CP-22 C IN COMPUTER CENTRE:-

After recording the reading in CP-22B pre-entry list and after proper filling of CP-22C statement, these inputs are received in the Computer Centre upto 3rd day of each month.  Following checks are performed in computer centre while receiving the CP-22 inputs:-

-           Check the month end printed in the list as the current billing month ended.
-           The signatures of concerned Deputy Manager S.S.&T. division must be available along with stamp in case of 66 KV/132 KV grid stations on each page of CP-22B Pre-entry list.  In case of 220 KV grids these pages are to be signed by the Senior Engineer.
-           The writing must be legible and there should be no cutting / over writing in the present reading and units sent out recorded.  If due to some reason, cutting / overwriting is accepted, it must be signed by the Deputy Manager S.S.& T. division, Senior Engineer or any other official authorized by them.
-           The number of pages in respect of each S.S.&T. division must be checked as recorded in the dispatch register at the time of initial dispatching of CP-22 B pre-entry list.  It must be ensured that no page of CP-22 B pre-entry list is missing.
-           Present reading and units sent out as recorded in the CP-22 B pre-entry list must be verified in respect of each feeder in the following manner:-

Units sent out  =  (Present reading – Previous reading) x multiplying factor.
In case of any discrepancy matter must be consulted with the official of S.S.&T. division concerned.
-           It must be ensured that readings are recorded with three decimal points and are within the limits of maximum “13” digits according to the meter range.
-           It must be ensured that recorded readings are not greater then their respective ranges in any case.
-           The present reading recorded must always be greater than or equal to the previous reading except in case of round completion or replacement.
-           The present reading should not be left blank in any case.
-           The units sent out must always be recorded within the range of maximum “13” digits.
-           The total of units sent out in respect of all the feeders of a grid Station is entered at the bottom of the page as page total.
-           Calculation of units sent out must be verified in case of round completion code “C”.
-           It must be ensured that complete information in CP-22C statement is properly recorded in all the cases where meter status code “R” is entered.
-           Check the feeder codes entered in the CP-22C statement.  These feeder codes must be valid existing in feeder table as well as present on CP-22 master file.  It must also be ensured that status code “R” is entered in CP-22B pre-entry list against the feeder codes entered in CP-22 C statement.
-           The range of new meter recorded in CP-22C statement must be within the range of “04 to 10”.
-           The multiplying factor of the new meter recorded in CP-22C statement must be upto the maximum “9” digit with “3” decimal points.
-           The final reading of meter removed in CP-22C must be greater than or equal to the previous reading.  It must be recorded upto maximum “13” digits with 3 decimal points.
-           The initial reading of new meter recorded in CP-22C must be less than or equal to the present reading recorded in CP-22B pre-entry list.  It must be recorded upto maximum “13” digits with 3 decimal points.
-           The units sent out in case of meter replacement must be verified in the following manner:-

A “Units sent out of removed meter” =  (Final reading of old meter – Previous
    reading) X Multiplying factor of old
    meter.

B “Units sent out of installed meter” =  (Present reading of new meter – Initial
    reading of new meter) X Multiplying
    factor of new meter.
Total units sent out by the feeder        =         A + B

When CP-22B and CP-22C is received and checked 100% in respect of all S.S.&T. divisions. CP-22 B is arranged in the order of page number.  Then complete CP-22B pre-entry list along with CP-22 C of all divisions is sent to data entry section for entry purposes.  When it is intimated by the Data Entry Supervisor, that entry of CP-22 B and CP-22 C is completed, proof lists are requested in the machine room.

NOTE:-          For each entry of CP-22 C, the code “R” must be entered against the relevant feeder during the entry of CP-22 B other wise the record will not be created in CP-22 C entry file.
 
CP-22 C PROOF LIST CHECKING:-

After receiving the proof list of CP-22C “Grid Station meter change / meter reading correction statement” from the machine room, it is required to be got edited 100 % from the source data. Complete information regarding the “replaced meter” is to be checked.  Billing month printed in the list must also be checked.  Data entry errors must be marked in red ink.  The following types of error messages may appear in the proof list.
           

ERROR CODE
MESSAGE TEXT
ACTION REQUIRED
01
Feeder code not available in feeder table.
It may be due to the wrong entry of feeder code or replacement code “R” is not entered in CP-22B pre-entry list against the respective feeder code.  The feeder code may be got corrected in CP-22C after consulting from source data or enter the replacement code “R” against the relevant feeder code.
02
Previous (Final) reading must be greater than zero.
Correct the reading as per source data.  Previous (final) reading in CP-22C must be greater than zero as well as pervious reading in CP-22B
03
Multiplying factor should not be less than “1.000”.
Correct the multiplying factor of new meter installed in CP-22C after consulting the source data.  However, multiplying factor of digital meter having range as “8” is acceptable less than “1.000” as “0.500”
16
CP-22C record must be given if meter status code is one of “R”, “U” and “N”.
Status code “U” and “N” are not in use.  If meter status code “R” is given, CP-22C record must be added after consulting from source data.
17
Non of the fields in CP-22C is left blank when meter status code is “R”.
If the meter status code is “R”, all columns of CP-22C i.-e. meter number, range, multiplying factor, final reading and initial reading must be filled.
22
Adjusted units incorrect according to new reading.
Not in use.

            After marking all the errors / corrections in CP-22C proof list and after making additions of all missing entries, proof list is sent to data entry section for correction purpose.  When it is intimated that corrections / additions are got entered, a fresh proof list is again requested.  This process is repeated again and again till the 100% correctness is ensured.  When it is ensured that CP-22C is error free and no error message is appearing in the final proof list, it is retained as office record.



CP-22B PRE-ENTRY PROOF LIST CHECKING:-

After receiving the proof list of CP-22B from the machine room, 100% checking of present reading and units sent out from the source data is required.  The billing month printed in the list is also checked being the current billing month ended.  It must be checked that entries are available in the proof list for all the new feeder codes allotted. Round completion code “C” is required to be checked where the meter has completed its round.  Units sent out in such cases must also be checked.  Meter status code “R” is also checked against the feeders reflecting in CP-22C proof list.  Units sent out in replacement cases must also be got checked from the source data of CP-22B.  Data entry errors must be marked in red ink.  Following errors messages may appear in the proof list and are required to be removed.
           
01
Feeder code not available in feeder table.
Add the feeder code in the feeder table if it is allotted first time, otherwise the record must be got deleted from CP-22B proof list.
02
Previous reading must be greater than zero.
If a new record is added in CP-22 B proof list, previous reading must be greater than zero. Correction required after consultation from source data.
03
Multiplying factor should not be less than “1.000”.
If a new record is added, multiplying factor should not be less than 1.000.  However, in case of digital meter. 0.500 MF is also acceptable.  Correction required after consultation from source data.
04
Previous reading should not be greater than final reading.
Check the final (present) reading from the source data and reading must be got corrected in CP-22B proof list.
05
Present reading must be equal to the previous reading if meter status code is “D”.
Meter status code “D” is not in use
06
Units sent out / computed must be equal to the units given.
Check the present reading as well as units sent out from the source data and correction must be made accordingly if it is due to data entry error otherwise present reading must be entered as per source data of CP-22 B pre-entry list.
07
Round completion code must be either “C” or left blank.
Check the round completion code column. Enter “C” if the round is completed otherwise left blank.
08
Meter status code must be “R”, ”U”, ”N” or “D”.
Check the meter status code column.  Enter “R” in case of replacement of meter otherwise left blank as codes “U”, “N” and “D” are no more in use.
09
First Sub Division code cannot be left blank.
Check the column of first sub division and enter the relevant valid Sub division code of the feeder.
10
Sub division code should be available in sub division table.
Check the sub division code and correction must be made accordingly
11
% age of share should be equal to or less than 100.
If a feeder is shared by two sub divisions the sum of % ages of all sub divisions must be equal to 100.
12
% age of share not provided for the sub division.
If a feeder is shared by more than one sub division  % age share must be given for each sub division according to the share.
13
% age of share should be left blank for blank sub division.
If a feeder is not a sharing feeder, % age column should be left blank and computer will charge 100% to the relevant sub division.
14
% age of share should be greater than zero.
In case of sharing of feeder, % age share of each sub division must be greater than zero
15
Sum of all % ages should be equal to 100.
In case of sharing of feeder, sum of % ages of all sub divisions must be equal to 100.
16
Verified reading or not numeric for adjustment.
Adjustment of units is no more in use
17
Verified reading incorrect for adjusted units.
-do-
18
Adjusted units blank or not numeric.
-do-
19
Units sent out not numeric.
Check the units sent out from the source data and required to be entered in the respective column.
20
Units sent out incorrect after adjustment.
Adjustment of units is no more in use.

NOTE:-          In case of sharing feeder, Sharing sub division code & relevant % must be entered in CP-22 B entry file and principal sub division must not be updated in any case.

After removing all the error messages, CP-22B list is sent to data entry section for correction purposes.  When all the marked corrections and additions are entered, proof list of CP-22 B is again requested.  This process is repeated again and again upto 100 % correctness.  When it is ensured that CP-22 B proof list is error free and no error message is appearing, % ages of shares in respect of each sub division is properly entered in case of all sharing feeders and in case of creation of new sub division or bifurcation, the sub division codes are properly updated in feeder table as well as CP-22B entry file, final proof list of CP-22B is obtained and retained as office record. 

PROCESSING OF CP-22A AND CP-22 REPORTS:-

            When it is ensured that CP-22B and CP-22C are error free, feeder codes and sub division codes are got corrected in feeder table as well as in CP-22B entry file, and total files from all the circles are received and merged in the re-tot step, CP-22A list is requested in the machine room.



CP-22A FEEDER WISE LINE LOSSES ANALYSIS:-

This is an important report, which reflects line losses in respect of each feeder relating to a division.  This report provides load in KW, total number of consumers, monthly units received and billed, progressive units received and billed, monthly % age losses and progressive % age losses of all the feeders.  This report projects the feeder wise losses at each division.  At the end of each division, an abstract showing the sub division wise load, number of consumers, units received, units billed, units lost and % age losses is printed.  Totals are also printed at division, circle and company level.  Following checks are performed to ensure the accuracy of report:-

-           Check the month printed in the list as current billing month ended.
-           Verify the names of Sub Divisions, Divisions, Circles and Company from the tables.
-           Load in KW must be equal to the load printed in CP-95 (balance pages) of all the circles.
-           Units received must be equal to the units received as per OK proof list of CP-22B.
-           Units billed / sold must be equal to the sum of units billed as per CP-94, CP-95 (balance section) and CP-41 section “B” of all the circles.
-                      Units lost         =          units received  – units sold
-                      % age losses = units lost / units received x 100
-                                                                                                                                              Progressive Units received     =          Progressive units received of previous month + Current month units received
-                                                                                                                                              Progressive Units billed          =          Progressive units billed of previous month + Current month units billed
-                      Progressive Units lost             =          Progressive units received – Progressive units billed
-                      Progressive % age losses         =          Progressive units lost / progressive units
received x 100
-                      Total number of consumers must be equal to the sum of total consumers as per CP-95, CP-110 of all the circles.
-                      It is ensured that new feeders added (if any), are included in the CP-22A report. Progressive units received, billed and lost against new feeders must also be verified from source data.
-                      Check the % age of the units in case of sharing feeders.

            When CP-22A report is found satisfactory, it is presented to the Manager Commercial for confirmation.  After confirmation from the Manager Commercial, four copies of this report are sent to Assistant Managers (C.S) for onward submission to field offices.

Note:-  If any invalid feeder code is appearing in CP-22A report, the matter may be got resolved with the help of programming section.

                        Feeder code 666666 represents the batch “26”
                        Feeder code 888888 represents the un-identified feeder
                        Feeder code 999999 represents the WAPDA Employee

CP-22 LINE LOSSES, BILLING AND ARREAR ANALYSIS:-

After successful processing of CP-22A report and merging of payments of all the circles, CP-22 “Line Losses, Billing and Arrear Analysis report” is requested in the machine room.  This is an important report which reflects the monthly and progressive units received, billed, adjusted and lost as well as calendar month assessment, payments, spillover, and receivable in respect of each feeder.  Tariff wise break-up of receivables are also reflected.  This list is printed sub division wise.  Sub division / Division / Circle and Company totals of these information are also printed.  Unit rate is also calculated by dividing total assessment by net units billed.  Following checks are performed to ensure the accuracy of this report:-

-                      Check the billing month printed in the list as current billing month ended.
-                      Monthly units received, billed and lost must be equal to the CP-22A report.
-                      Progressive units received, billed and lost must also be compared with the CP-22A report
-                      Monthly and progressive % age losses must be equal to the monthly and progressive % age losses printed in the CP-22A report.
-                      Total units adjusted must be equal to the sum of units adjusted as per CP-95 (bill adjustment section) of all the circles.
-                      Progressive units adjusted       =         Progressive units adjusted of previous month + Current month units adjusted
-                      Average unit rate                    =          Assessment / Net units billed
-                      Total assessment must be equal to the sum of the assessments of all the circles as per CP-41 section “A”.
-                      Total payment must be equal to the total payment of MIS-RPT 1 & 3.
-           Spillover must be equal to the spillover amount as per MIS-RPT 1 & 3, CP-41 or CP-120A of the region.
-                      Total receivable amount must be equal to receivable amount as per MIS-RPT 1 & 3, CP-41 or CP-120A of the region.
-                      Total number of consumers must be equal to the sum of consumers of all the circles as per CP-95, CP-110 and CP-41 of the region.
-                      Total connected load in KW of CP-22 report must be equal to the sum of load of all the circles as per CP-95 (balance section).

When CP-22 report is found 100% correct, it is required to be dispatched to field offices through circle computer centers. 


NOTE.

i):         There must be no feeder in CP-22 reports with zero consumer, which  resulting 100 % losses. This may be due to the reason that new feeder is physically energized and consumers have been shifted to new feeder but their feeder codes are not updated on General & Industrial Master files. Necessary updation on billing Master Files is required before processing of CP-22 reports.

ii):        For line losses purpose July to June is considered as financial year.  Progressive information at any stage are considered as total from the month of July to date in each year.

PROCESSING OF MONTHLY REPORTS

PROCESSING OF MONTHLY REPORTS.

            After successful completion of bills of all batches, posting of all miscellaneous inputs data, complete cash posting of all dates and successful completion of WAPDA employee departmental billing and dead defaulter’s billing, monthly statistical file is generated to process month end reports. These reports are considered to be very important and are used for accountability of performances at different level. Following special steps are required to be run before generating statistical files.

MONTHLY BILL ADJUSTMENT POSTED LIST (CP-88 S):-

            All the “after billing adjustments” are accumulated in monthly reports except “after billing detection adjustments” posted under card types “C, D, and E”. These adjustments are processed at month end and as a result, a list named as CP–88 S, is printed. This list reflects the units adjusted, component wise amount adjusted, and closing balance before and after the posting of adjustments in respect of each consumer. This list is printed batch wise in each sub division. An abstract of above information is also printed at sub division, division and Circle level. Following checks are implemented to ensure the accuracy.

-           Check the billing month printed in the list.
-           Circle totals, i-.e number of records, units adjusted and amount adjusted in respect of each batch must be verified from the totals of “remaining adjustment (normal)” as recorded batch wise in the bill adjustment register, after addition of PTV Fee adjusted through CP-52 T and subtraction of W105 adjustment in the following ways:

a)         Units adjusted of each   =   Normal unit adjusted of each batch from
batch (CP-88 S)                  adjustment register    
b)                  Amount adjusted of each =  Normal amount adjusted of each batch  +  After batch (CP- 88 S)                 billing PTV fee adjusted through CP-52 T of
each batch  - W105 adjustment created.
 

SCARP IOT POSTING:-

A Special procedure has been introduced for the payment of electricity dues against scarp tube-wells of provincial Government. In this step total outstanding amount against scarp connections is retrieved and posted as IOT payments on the master file. The amount posted in this step is adjusted out of the electricity duty payable to Provincial Government. The following reports are printed.

-           Single page summary of amount retrieved.
-           Page showing posted statistics.
-           Reference number wise list of scarp tube wells.

Check the billing month printed in these lists. Total amount printed in above lists must be same.

POSTING OF PAYMENTS AT SOURCE (Adjuster):-

            Some Government departments (Federal as well as provincial) pay their electricity bill through adjuster. These payments are called as “at source payment”. The adjuster files are prepared at WAPDA Computer Centres (HQ) WAPDA House Lahore at the format of CP-139 entry file i-e “X139TEF1.dat”. The payments are posted on computer master file as   IOT under special Adjustment Note number and bank codes as “80000”, “82000”, “90000” and “92000”. The “at source payment” of each department is distributed among its electricity connections throughout the country on the basis of last month outstanding amount as appeared in the previous month Master Files (General & Industrial) of each DISCO available at WCC, (HQ) Lahore. Then these adjuster entry files are sent to the regional computer centers of all DISCOs. At regional computer centers these files are sorted Circle-wise and are sent to circle computer centers for onward posting on master file of current month. The adjuster payments are posted before the processing of weekly cash reports of last week ending. These payments must be posted 100 % and it is ensured that no record of adjuster is rejected. Any error message (if appearing) must be got cleared as per normal procedure of CP-139. In case of change of reference, old reference number is required to be corrected by new reference number. Adjuster amount cannot be posted against consumer appearing in Batch number 26. In such cases the said amount is posted against any other reference of same department.  When a consumer is converted from Government to private, the adjuster amount is posted against any other reference of same department.
 
POSTING OF PAYMENT MADE BY GOVERNMENT OF PAKISTAN AGAINST SUBSIDY (GOP PAYMENTS:-

            Government of Pakistan is providing subsidy for GST calculated in the electricity bills of following consumers:-

-           Residential consumers falling under tariff A-1 having monthly consumption up to 100 units.
-           Agricultural Tube wells falling under tariff D-2 (i).

When Government of Pakistan make some payments against GST subsidy amount, Company wise sharing of this amount is done on the basis of outstanding subsidy amount existing on the Master Files of previous month available at WAPDA Computer Centres (HQ) WAPDA House Lahore and Company wise share files are sent to Regional Computer Centres. At Regional Computer Centres, share files of all Computer Centres are created and newly created share file along with a list indicating the GOP Subsidy payment of each circle is sent to each Computer Centre of the DISCO.

            The step-wise posting procedure of GOP payment is as under:

SHARE FILE UPDATION:-

                        
In this step GST Subsidy Receivables are updated on share file as per current Master File. A single page statistical list reflecting the up-to date GST Subsidy receivable amount is also printed in this step.

 

 




GST SUBSIDY FILE CREATION:-


In this step, the payment received against GST Subsidy Receivables, is shared consumer-wise by using updated share file and current Master File. A payment retrieval file is created as a result of this step.

GST SUBSIDY PAYMENT FILE LISTING:-


The payment retrieval file created in the above step is sorted and listed in this step. The payment shown in this list must be equal to the amount appearing in the list of share file received from WCC, (HQ), Lahore.

GST SUBSIDY POSTING ON MASTER FILE:-


In this step, the payment shown in the payment retrieval file is posted on General as well as Industrial Master File of current month. A payment summary file is created in this step and is required to be merged in the monthly PSUM-MERG-MMCCYY.dat before sorting step.

 

SPECIAL CP-135 LISTING:-


In this step, a special listing at the pattern of monthlyCP-135 is printed from payment summary. This list reflects the sub division wise amount posted against GST Subsidy. The total amount of special CP-135 must be equal to the payment shown in the list of share file received from WCC, (HQ), Lahore.
 
INVALID FEEDER STEP:-


In this step a list is printed showing all reference numbers added on master file with invalid feeders. A feeder is said to be invalid if it does not exist in feeder table under same sub division code. Feeder codes of such consumers must be updated according to the sub division code. After updation this step is repeated. Before starting the month end proceedings, this list must be printed with nil reference number.