Sei sulla pagina 1di 6

End to End – Basic Meter to Cash

The following test plan will validate the basic meter to cash process is working correctly; starting with
meter reads all the way through to reconciliation.

Steps:

1. Create the Meter Read Orders in mass using transaction EL09. Follow the steps below:
a. Determine the date range of meter reads in IEE Test by talking with Phil Jossis, Benjamin
Eells, or Lewis McKillop
b. Verify there are no IEE test exceptions, which would keep the reads from uploading.
Work with Phil Jossis to verify this.
c. Determine which read date to use based on the cycle that is being billed.
d. Pull up transaction EL09 and copy the template with Date ID of 1/1/2013 and
Identification of IEEWD.
e. In the General Selections tab, type in a Meter Reading Period date 2 business days prior
to the intended read date. For example, read date is 12/3/2014, so type in 12/1/2014.
f. Save the run information and run the job in the background.

2. Create the Meter Read Orders for MVRS and MV90 in mass using transaction EL09. Follow the
steps below:
a. Determine date range of meter reads for MVRS and MV90 with Drew Barboza.
b. Pull up transaction EL09 and copy the template Identification of MVRSWD.
c. In the General Selections tab, type in a Meter Reading Period date 2 business days prior
to the intended read date. For example, read date is 12/3/2014, so type in 12/1/2014.
d. Save the run information and run the job in the background.

3. For MVRS Download run ZMVRS_CLEAR with MRU’s that are applicable. This is performed to
delete the tables for the upcoming download.

4. Execute transaction ZDM_BILLORDER_VAL with the current run date which will identify the
installations with missing periodic MROs. Validate that any missing MROs are explainable and
document why they are missing. Also use table EABL to validate the meter read documents
were created successfully and table ETRG to validate the billing orders were created
successfully.

5. Create Meter Read order File to IEE in mass using transaction EL16. Follow the steps below:
a. Pull up transaction EL16 for creation of output file and copy the template with date ID of
1/1/2013 and Identification of IEEWD.
b. In the General Selections tab, enter the actual read date into the Scheduled Meter
Reading Date field.
c. In the Technical Settings tab, verify the number of jobs is set to 80.
d. Save the run information and run the job in the background.
e. Confirm file is created in EntIntUat>IEE81>DB>Import>AMI_Billing>Backup
f. Once the job is complete, IEE Test should start responding immediately. It usually takes
1-2 hours for all the reads to upload after the EL16 job is complete.

6. Run EL16 for MVRS Download to populate 3 custom tables for creation of the MVRS File (actual
creation of file is in next step).
a. Pull up transaction EL16 and copy the template MVRSWE.
b. In the General Selections tab, enter the actual read date into the Scheduled Meter
Reading Date Field.
c. Save the run information and run the job in the background.

7. Run ZMVRS_DOWN to create file for download. Input applicable MRU and execute. Confirm file
is generated in EntIntUAT>MVRS>Out.

8. For the inbound MVRS File, confirm that file is placed by Reg Ops in the fillmore directory to
download. Run ZDM_MVRSU.

9. For inbound MV90 File, confirm file placed by reg ops in fillmore to download. Run ZMV90 to
download reads.

10. Query for missing reads using transaction EL31. Follow the steps below:
a. Access transaction EL31 and click on Meter Reading Unit, and then click on Meter
Reading Order.
b. In the Meter Reading Unit field, type AM followed by the cycle and then a *. For
example cycle 19 would show AM19*.
c. Type the scheduled meter reading date and the meter reading reason (01 for periodic).
d. Click the execute button and the query will return a list of MRUs that still have MROs.
e. Once the missing reads are found, work with the Regional Operations group to resolve
the issue and resubmit the reads if necessary.

11. This will be the point where the CAMC reps will work the implausible reads and release them
accordingly using transaction EL70. Follow the steps below:
a. The CAMC reps will work there normal process for releasing implausible reads.
b. Any left over implausibles that they don’t get to will be released in mass. To do this, pull
up transaction EL70 and fill in the Portion, Sched MR Date, Read Reason, and a
maximum number of 200.
c. Once the information is displayed, select all rows and release without correction.

12. Now that the meter reads have been created, the billing process can begin. Follow the steps
below to execute the mass billing transaction EA38:
a. Pull up transaction EA38 and copy a previous run from Production. In the General
Selections tab enter the portion/cycle that will be billed.
b. In the Billing Parameters tab, enter today’s date in both date fields. Also verify the Log
checkmarks are checked with No Success Messages and No Info Message.
c. In the Technical Settings tab, select object ABR_AUFTR with the Variant of ZBILL. The
number of jobs should be set to 20.
d. Save the run information and run the job in the background.
e. Once the transaction is complete, use tables ERCH, DBERCHZ1, and DBERCHZ3 to
validate that the billing data was created successfully. Spot check individual bills to
ensure the information is correct. Also check the SLG1 logs to ensure there are no
unexplainable errors.

13. Now that the bills have been created and validated, the invoicing process can begin. Follow the
steps below to execute the mass invoicing transaction EA26:
a. Pull up transaction EA26 and copy a previous run from Production. In the General
Selections tab leave all fields blank.
b. In the Add. Parameters tab, enter today’s date in all date fields.
c. In the Technical Settings tab, select object AR_ACCT_MX and Variant of ZINVD. The
number of jobs should be set to 20.
d. Save the run information and run the job in the background.
e. Once the transaction is complete, use table ERDK to validate that the invoicing data was
created successfully. Spot check individual invoices to ensure the information is correct.
Also make sure to validate the data is displayed correctly in tables DFKKOP and
DFKKOPK. Validate table DFKKOPK has accurate data populated in the Account
Assignment field as well as all other custom fields in the table (tax city, SA type, division,
cost center, etc). Also validate the due dates are correct for both Idaho and Oregon.
Spot check accounts and count the days to make sure the due dates are correct. Also
check the SLG1 logs to ensure there are no unexplainable errors.

14. Now that the invoices have been created and validated, the invoice print process can begin.
Follow the steps below to execute the mass invoice print transaction EA29.
a. Pull up transaction EA29 and copy a previous run from Production. In the General
Selections tab the Creation Reason should be set to 01 and the Document Posted
checkbox should be checked.
b. In the Technical Settings Tab, Select object BIPR_DX and Variant of ZINPP. The number
of jobs should be set to 30.
c. Save the run information and run the job in the background.
d. Once the transaction is complete, use table ZTA_EX_COMM_HIST to validate that the
invoice print process worked correctly. Also use this table to review the errors and
ensure they are valid. Spot check individual spools to ensure the information is correct.
15. Once the invoices have been printed and validated, it is time to run mass Dunning. Follow the
steps below:
a. Pull up transaction FPVA and copy a previous run from Production. In the Dunning
Parameters tab verify the Start Current Run checkbox is checked.
b. In the Technical Settings Tab, verify object GPART and Variant of ZBP_100 are selected.
The number of jobs should be set to 30.
c. Save the run information and run the job in the background.
d. Once the transaction is complete, use table FKKMAKO to validate the collection steps
were created correctly. Spot check accounts and validate the collection strategies are
correct.

16. Once dunning is complete, it is time to run transaction FPCOPARA to print the account
statements generated from the dunning run. Follow the steps below:
a. Access transaction FPCOPARA and copy a production run using the NUT01 identification
name. Save the parameters and execute the transaction.
b. Once completed, spot check accounts that had collection steps created of W104, W105,
WO04, and WO05 and check the spools in SP01 to make sure they are valid.
c. Then access transaction FPCOPARA again and copy a production run using the DUN01
identification name. Save the parameters and execute the transaction.
d. Once completed there will be spools created for reminder notices and FDNs. Spot check
accounts that had collection steps created of C002, C006, C102, and C106 and validate
the spools in SP01 are accurate.

17. Now that the invoices and account statements have been printed and validated, it is time to run
the spool merge program ZSPMERGE.
a. Pull up transaction ZSPMERGE and enter in today’s date for the Spool Creation Date.
Also make sure the Exclude Printed and Print Immediately checkboxes are checked.
b. Execute the transaction in the background. Once the transaction is complete validate
the bill print file was created successfully by searching folder
\\fillmore\EntIntUAT\Statements\Out. Validate the file is in the correct format and
compare to a Production file to ensure it looks accurate.

18. Now that the spool merge program is complete, the mass BPEM creation job can be executed.
**This transaction will be executed twice, once for the prepare and once for the generate.**
a. Pull up transaction FPEMMAMA and copy a previous run from Production.
b. In the General Selections Tab, make sure Prepare Jobs is selected. The Business proc.
Area field should be populated with be populated with the following: EBB, EBI, ECS, EIN,
EMMA, EMR, FFWD, PAYP, ZBI, ZCS, ZFI
c. In the Technical Settings Tab, select object EMMA_JOB and Variant of ZBPEMP. The
number of jobs should be set to 20:
d. Save the run information and run the job in the background.
e. Then create a new run for the Generate process. In the General Selections Tab make
sure Create Clarification Cases is selected. The Business proc. Area field should be
populated with following: EBB, EBI, ECS, EIN, EMMA, EMR, FFWD, PAYP, ZBI, ZCS, ZFI
f. In the Technical Settings Tab, select object EMMA_JOB and Variant of ZBPEMG. The
number of jobs should be set to 20.
g. Save the run information and run the job in the background.

19. Now that the BPEMS have been created it will be necessary for the CAMC reps to work a set of
the BPEMs to ensure they can still work them successfully The functional team will also work
out of balance BPEMs at this time.
a. Billing BPEMs
b. Invoicing BPEMS
c. Out of Balance BPEMS
i. Validate an invoice out of balance error can be fixed and printed by using the
ZFICA_OOB solution.
ii. Validate an account statement out of balance error can be fixed and printed by
using the ZFICA_OOB solution.
iii. Validate a converted balance error can be fixed and printed by using the ZPAC
solution.

20. The CAMC reps will also work a selection of invoicing and billing outsorts to ensure they can still
work them successfully.
a. They will access transaction EA05 and work the outsorts just as they normally would in a
real life scenario.

21. At this point the invoicing process is complete and it is time to process a mass payment file.
Follow the steps below:
a. Use a recent original payment file from Production (found in this link:
\\fillmore\EntIntPrd\Payments\In\Archive\Original) and copy it to your desktop.
b. Replace about 30 or so account numbers in the file with accounts that were invoiced in
the recent mass invoicing run that was complete above.
c. Place the file in the following UAT directory: \\fillmore\EntIntUat\Payments\In
d. Pull up transaction ZPAYMENTS and make sure the ZPAYMENTS variant is selected. Run
the transaction in the background. Monitor the directory as the program is running and
make sure the individual payment lot files are created and processed automatically.
e. Once the job is complete make sure the original payment file was moved to the
following folder: \\fillmore\EntIntUat\Payments\In\Archive\Original and also make sure
the individual payment lot files were moved to this folder:
\\fillmore\EntIntUat\Payments\In\Archive\Transformed.
f. Spot check accounts in the file and make sure the payments were posted correctly. Also
make sure to check the accounts that were in the payment file that also had invoices
created from the mass invoicing run.
22. Once the payment processing is complete it is time to run the Reconciliation process. Follow the
steps below:
a. Run transactions FP09FIK, FP05FIK, and FPG4, and make sure the normal batch variants
are used when running. Once the transactions are complete, verify all open rec keys are
closed successfully. Review any errors and make sure they are acceptable. Once the rec
keys are closed, run transaction FPG1M using the batch variant and ensure the closed
rec keys are transferred to FIGL correctly. Next, run transaction ZPEOPLESOFT using the
batch variant and validate the output is correct. It will be necessary to compare the
ZPEOPLESOFT output to data within CR&B Tables.
i. Compare the Peoplesoft Revenue Loaded Report to the data in table
ZFINANCIAL_SUM3 and verify the amounts match.
ii. Compare the Peoplesoft Financial Summary Report to the data in table
ZFINANCIALSUM for record ID 1, and verify the amounts match.
iii. Compare the data in ZFINANCIAL_SUM3 and verify it matches the data entered
into table FALGFLEXA.
iv. Verify with the finance department (TJ Kindall) that the data is transferred
successfully in the correct format.
b. Run transaction FPO2 with the BAL_FICA-FIGL variant. Review the output and verify the
‘Difference’ column nets to 0 for each GL account displayed.