3PL Billing - Test Plan

Functional Test Script Template 49281731.
doc – 3PL Billing
FUNCTIONAL TEST SCRIPT

Test Plan
TEST FLOW: 3PL BILLING
Application Release: R12.1+
Author: Sunil Mididoddi
Creation Date: 1-Feb-2010
Last Updated: 5-Feb-2010
File URL: [Click here and type the File URL]
Version: 1.0
Execution Start Date: [optional]
Execution Completion Date: [optional]
Test Executor: [Click here and type the name of test executor]
Status: APPROVED (IN PROGRESS, DRAFT, IN REVIEW, APPROVED)
Disclaimer: The following information is confidential and is for internal use only. The development, release, and timing of any
features or functionality described for Oracle's products remains at the sole discretion of Oracle.
12/8/2021 12/8/2021 Oracle Confidential - For internal use only Page 1

Functional Test Script Template 49281731.doc – 3PL Billing
1 Document Control
1.1 Change Record
Name Position Date Document Description of Change Including Section of Script

Version
Sunil Mididoddi QA Engineer 5-Feb-2010 1.0 Initial draft
1.2 Document Review and Approval History
Name Role Position Document Review Date Comments Incorporated

Status (Completed / Reviewed
Approved)
Sunil Mididoddi Author QA Engineer
Contributor
Reviewer/
Approver
Reviewer/
Approver
1.3 Document References
Name Type of Reference Location

1.4 Resource Estimates [Optional]

Resource Estimate (Hrs) for Manual Execution of this Test Script is
Resource Estimate (Hrs) for Automated Execution of this Test Script is

2 Table of Contents
1 DOCUMENT CONTROL..................................................................................................2
1.1 CHANGE RECORD..................................................................................................................................................2
1.2 DOCUMENT REVIEW AND APPROVAL HISTORY....................................................................................................2
1.3 DOCUMENT REFERENCES .....................................................................................................................................2
1.4 RESOURCE ESTIMATES [OPTIONAL].....................................................................................................................3
2 TABLE OF CONTENTS....................................................................................................4
FUNCTIONAL TEST OVERVIEW...................................................................................5

2.1 INTRODUCTION/OVERALL TEST OBJECTIVES........................................................................................................5
2.2 TEST OUTLINE.......................................................................................................................................................5
2.3 PROCESS FLOW [OPTIONAL]................................................................................................................................18
3 DEPENDENCIES/REQUIREMENTS............................................................................19
3.1 TEST SCRIPT LIMITATIONS..................................................................................................................................19
3.2 TEST SCRIPT DEPENDENCIES / ASSUMPTIONS.....................................................................................................19
3.3 DEFAULT SETUP [OPTIONAL]..............................................................................................................................19
4 TEST SCENARIOS ..........................................................................................................21
4.1 [CLICK HERE AND TYPE THE NAME OF THE SCENARIO].......................................................................................21
4.1.1 [Click here and type the name of the Test Case].........................................................................................21
5 SUMMARY OF RESULTS/ISSUES...............................................................................22
5.1 ISSUES LOG .........................................................................................................................................................22
6 APPENDIX........................................................................................................................23
6.1 APPENDIX A - TEST SCRIPT REVIEW TEMPLATES...............................................................................................23
6.1.1 Outline Review Template.............................................................................................................................23
6.1.2 Test Script Review Template (after first Draft)...........................................................................................24
6.1.3 Test Script Review Template (after first Round Testing).............................................................................25

Functional Test Overview
2.1 Introduction/Overall Test Objectives
This script is intended to verify that the following functionality is working successfully:
[Click here and type the overall test objectives of this process]
2.2 Test Outline

Scenario 5.1: Billing rule for Client/Warehouse/Transaction Priority Effort Effor Effort  Automated
(H,M,L) Requi t Required to Y/N?
red to Requ Record
write ired Automated
detail to Script (in
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Description / Objective: Billing rule for Client/Warehouse/Transaction  
Test Case Description    
Define a billing rule Define a billing rule for receipt/ put    

away/picking/shippinh/inspection/ transactions
or labor/insurance services by selecting the
appropriate billing source
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Update (rule name) of a billing rule Update (rule name) of a billing rule
Update (description) of a billing rule Update (description) of a billing rule
Update (billing source) of a billing rule Update (billing source) of a billing rule before
before billing billing
Query a billing rule and hit fetch lines Query a billing rule and hit fetch lines from
from agreement button. On clicking this agreement button. On clicking this button,
button, fetch and insert all the new fetch and insert all the new Usage based
Usage based Service item lines from the Service item lines from the service agreement.
service agreement. If multiple counters If multiple counters attached to the usage line,
attached to the usage line, fetch the first fetch the first available counter only. Only 1
available counter only. Only 1 counter counter per usage service is supported
per usage service is supported
Check the values of the service Check the values of the service agreement
agreement LOV in the billing rule form: LOV in the billing rule form: Only service
contracts to be shown; LOV to pull up active
service agreements numbers LOV should
display Number, Version, Party Name,
description, start date, end date)The Number,
Version and Party Name should be shown as
one field separated by ‘:’ and description, Start
Date and End Date should be shown as
different columns.
Verify the behavior of operating unit Verify the behavior of operating unit LOV in
LOV in the billing rule form when the billing rule form when MOAC is disabled:
MOAC is disabled When MOAC is not enabled – Only one value
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
should be shown and the field should be a
view only field.
Verify the behavior of operating unit Verify the behavior of operating unit LOV in
LOV in the billing rule form when the billing rule form when MOAC is disabled:
MOAC is disabled: When MOAC is enabled the LOV should
show all the Operating Units user has access
to.
Create a service agreement with Create a service agreement with multiple
multiple accounts for a client. Create a accounts for a client. Create a billing rule for
billing rule for that contract. Verify if that contract. Verify if the lines fetched show
the lines fetched show the details the details properly(The client name should be
properly(The client name should be shown as concatenated Account Number and
shown as concatenated Account Client Name separated by ‘:’ )
Number and Client Name separated by
‘:’ )
Verify that the lines fetched from the Verify that the lines fetched from the billing
billing rule do not have end dated rule do not have end dated records..
records..
Update the service contract with a new Update the service contract with a new item.
item. Ensure that the fetch lines show Ensure that the fetch lines show this record
this record also also
Create rule1 for Service contract A and Create rule1 for Service contract A and save.
save. Create Rule2 for the same service Create Rule2 for the same service contract A.
contract A. Error shown : ‘Billing Rule exists for the
contract. Query the rule to view/update the
details’
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
After one billing cycle, update billing After one billing cycle, update billing source
source on one record to null in the on one record to null in the fetched records.
fetched records. Warning: Billing Unit calculation program has
been executed previously. Do you really want
to update the Billing Source? YES or No
buttons.
Delete a billing rule: Delete a billing rule: Warning: Do you really
want to Delete this rule? YES or NO to
Continue
Scenario 5.2: Calculate billing units Priority Effort Effor Effort  Automated
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Description / Objective: Calculate billing units  
Execute the “Calculate billing units” Execute the “Calculate billing units” program    
program by giving service contract by giving service contract
Execute the “Calculate billing units” Execute the “Calculate billing units” program    
program by giving service item by giving service item
Execute the “Calculate billing units” Execute the “Calculate billing units” program
program by giving client code by giving client code
program by giving billing rule by giving billing rule
program without any optional without any optional parameters
parameters
Execute the “Calculate billing units” User should not be allowed to run for a future
program for a future date date
Verify the behavior of service contract Contract LOV should show only active
LOV contracts
Execute the “Calculate billing units” After execution for Rule1 verify the last
program by giving billing rule. Execute computation date for the rule...Execute the
the program again after checking the program again and ensure that the from date is
dates last computation date
Scenario 5.2: Calculate billing units Priority Effort Effor Effort  Automated
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Verify that the transactions done with Verify that the transactions done with respect
respect to any UOM are reflected while to any UOM are reflected while billing in the
billing in the number of transactions number of transactions (Ex: RCV/PICK/SHIP)
(Ex: RCV/PICK/SHIP)
Verify that the transactions are Verify that the transactions are converted
converted properly into the billing properly into the billing UOM (Ex: 2
UOM (Ex: 2 transactions of 3 and 5 transactions of 3 and 5 boxes each, should be
boxes each, should be considered as 8 considered as 8 billing units)
billing units)
Scenario 5.3: End to End billing flows Priority Effort Effor Effort  Automated
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Description / Objective: End to End billing flows  
Create a service agreement for multiple Create a service agreement for multiple lines;    
lines; ensure that billing is done weekly ensure that billing is done weekly for few lines
for few lines and monthly for other. and monthly for other. Invoice client
Invoice client
Invoice the customer after few
transactions/days
Create a service agreement for fixed Create a service agreement with a client by    
space utilization. Invoice client specifying the usage item for fixed space
utilization. Associate billing source and billing
rules. Compute billing units and invoice the
transactions/days
client
transactions/days
Create a service agreement for actual Create a service agreement with a client by    
space utilization. Invoice client specifying the usage item for actual space
utilization. Associate billing source and billing
rules. Compute billing units and invoice the
transactions/days
client
transactions/days
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Create a service agreement for Create a service agreement with a client by    
minimum space charge and excess specifying the usage item for minimum space
utilization. Invoice client charge and excess utilization. Associate billing
source and billing rules. Compute billing
units and invoice the client
transactions/days
transactions/days
Create a service agreement for receipt Create a service agreement with a client by
transaction. Invoice client specifying the usage item for receipt txn.
Associate billing source and billing rules.
Compute billing units add service charges for
transactions/days
wrapping/insurance and invoice the client
transactions/days
Create a service agreement for put away Create a service agreement with a client by
transaction. Invoice client specifying the usage item for put away txn.
Compute billing units, add additional handling
transactions/days
costs for perishable goods and invoice the
client
transactions/days
Create a service agreement for Create a service agreement with a client by
inspection transaction. Invoice client specifying the usage item for inspection txn.
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
transactions/days Compute billing units and invoice the client
transactions/days
Create a service agreement for picking Create a service agreement with a client by
transaction. Invoice client specifying the usage item for picking txn.
Compute billing units and invoice the client
transactions/days
transactions/days
Create a service agreement for shipping Create a service agreement with a client by
transaction. Invoice client specifying the usage item for shipping txn.
Compute billing units, add handling and
transactions/days
freight costs and invoice the client
transactions/days
Create a service agreement for receipt Create a service agreement with a client by
transaction (UOM: BOX). Invoice specifying the usage item for receipt txn
client (UOM:BOX). Associate billing source and
billing rules. Compute billing units add
service charges for wrapping/insurance and
transactions/days
invoice the client
transactions/days
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Create a service agreement for cycle Create a service agreement with a client by
count transaction. Invoice client specifying the usage item for cycle count txn.
Compute billing units and invoice the client
transactions/days
transactions/days
Verify billing for multiple accounts for Verify billing for multiple accounts for one
one party on a single service agreement party on a single service agreement
Create a service agreement for any Create a service agreement for any transaction.
transaction. Perform multiple billing Perform multiple billing operations and one
operations and one invoice operation invoice operation
Scenario 5.4: Change management on billing flows Priority Effort Effor Effort  Automated
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Description / Objective: Change management on billing flows  
Create a service agreement for receipt Create a service agreement with a client by    
transaction. Compute billing units. Edit specifying the usage item for receipt txn.
the contract and enter a new usage item. Associate billing source and billing rules.
Invoice client Compute billing units. . Edit the contract and
enter a new usage item for packing. Compute
billing units and invoice the client
Create a service agreement for space Create a service agreement with a client by    
utilization. Compute billing units. Edit specifying the usage item for space utilization.
the contract and enter a new usage item. Associate billing source and billing rules.
Invoice client Compute billing units. . Edit the contract and
enter a new price adjustment. Compute billing
units and invoice the client
Create a service agreement for any Create a service agreement for any transaction.    
transaction. Perform billing operation, Perform billing operation, edit the service
edit the service contract, and make contract, and make modification to pricing
modification to pricing attributes, attributes, approce the contract. Ensure the
approce the contract. Ensure the new new pricing is considered in the next billing
pricing is considered in the next billing
Scenario 5.5: Others Priority Effort Effor Effort  Automated
red to Requ Record
test execu hours)
script te
(in man
hours) ual
test
scrip
t (in
hour
s)
Description / Objective: Others  
Define a new test billing source Create a billing source ' Test Source'. Specify    
the source to return a constant number say 100
Verify that "Third Party Logistics Verify that "Third Party Logistics Billing"    
Billing" seeded menu is available and seeded menu is available and shows all the
shows all the expected functions expected functions
   
2.3 Process Flow [Optional]

Use a flow diagram to illustrate the overall flow of the test script
3 Dependencies/Requirements
3.1 Test Script Limitations

[Click here and type the limitations of this test script. List any pertinent functionality that it does not test. Provide any relevant reasons]
3.2 Test Script Dependencies / Assumptions

[Click here and type the name of the test script/scenarios/cases that need to be run before running this script or None]
3.3 Default Setup [Optional]
Test Environment
Database:
Base Release:
XX Release:
RDBMS Version:
Jinitiator Version:
Browser:
Freeze Date:
Login / Responsibilities
Login: [Click here and type the user name /password]
Resp: [Click here and type the responsibility]
Other Products
[Click here and type the names of other products that need to be installed during testing]
Profile Options
Fill in the table below with any necessary profile options setups
Profile Site Level User

WMS: Enable 3PL Billing Yes
Operating Units
[Click here and type the name of all the needed Operating Units to run this script]
Security Rules
[Click here and type the name of the Security Rules]
Additional Test Data

[Click here and type any additional test data or setup document names]
4 Common Setups
4.1 Service Contract
4.1.1 Create a Service Contract
Detail Description [Optional]

Step Navigation Path Actions Expected Results / Issues and Comments Pass/
No. Data – Field: Value(s) Check Points (Automation) Fail
Login: mfg/welcome
Resp: Third Party Logistics Billing Administrator
1 Create a Service contract 1. Start Launch Contracts. Launch Pad should open
Summary 2. Select Tools from Menu. successfully.
Service Agreement -> Launch Pad 3. Click New.
4. Make sure Create a New Contract Create a New Contract form
Manually radio button is checked. should open successfully.
5. Select Service Agreement from Category LOV.
6. Click Create button. Service Contracts Authoring
(Vision Operations, USD) should
open successfully.
2 1. Enter Sysdate + 6 Month for Start Date. Contract should be saved
2. Enter 1 in Duration field. successfully.
3. Select Year from Period LOV.
4. Enter QA of Service Contract in Short Contract Number should be
Description field. automatically generated
5. Save the record. (Ctrl+S)
Contract number XXXX
3 1. Click Summary tab. Vendor, Vision Operations
2. Click Parties tab. should be automatically
3. Click Role field. populated in the first row of
4. Click Role field in the second row. Party.
5. Select Customer from Role LOV.
6. Select Business World from Name LOV.
7. Select Business World / Business World Party Number 2813 should be
from Account / Party LOV of Bill To section. populated automatically.
8. Select San Jose (OPS) from Location
LOV. Bill To address and Ship To
9. Select Business World / Business World address should be
from Account / Party LOV of Ship To automatically populated.
section.
10. Select San Jose (OPS) from Location All values should be saved
LOV. successfully.
4 1. Click Pricing / Billing tab. All values should be saved
2. Select Corporate from Price List LOV. successfully.
3. Select Immediate from Accounting Rule
LOV.
4. Select Immediate from Payment Terms
LOV.
5. Verify that Advance Invoice is selected in
Invoicing Rule.
1. Click Administration tab. Description should be
2. Select Business World from Group Name automatically populated.
field of Contract Group section.
5 3. Select Approve from Type LOV of All values should be saved
Process section. successfully.
4. Select OKCAUKAP from Workflow Name.
5. Verify that DEFAULT QA CHECK LIST is

selected in Quality Assurance Checklist
LOV.
6 Add Usage items to lines The number of lines is according to Bill To and Ship To fields
convenience should be automatically
populated as following:
Click Lines tab.
Click Accounts tab. Account: 1608
Select Usage from Line Type LOV. Location: San Jose (OPS)
Select SER_XXX_1 from Name LOV.
Set the Usage type remain as “Fixed per Account: Business World
Period”/”Actual per Qty” 2391 L STREET SAN JOSE
Santa Clara CA 95106 Unites
Click the second row and select Usage States
and SER_XXX_2from Line Type and
Name LOVs. Note:
Go to Lines-Effectivities tab For future reference within this
Set the Usage type remain as “Fixed per TC, the four lines are referred
Period”/”Actual per Qty” as Line1, 2,3 and 4
(or)
Click the third row and select Usage and
SER_XXX_3 from Line Type and Name
LOVs.
Go to Lines-Effectivities tab
Change the Usage type to “Actual per
Period”
(or)
Click the fourth row and select Usage and
SER_XXX_4 from Line Type and Name
LOVs.
Go to Lines-Effectivities tab
Change the Usage type to “Negotiated
price”
7 Associate counters to the usage 1. Click Pricing / Products tab.
items 2. Select the Line.
3. Click LOV button in Name field in
Products section.
4. Select any instance of of the
corresponding counter.
5. Click OK.
6. Enter 1000 in Default field.
2. Enter price breaks
Repeat above steps for all the usagelines

8 Select the number of periods for 1. Select the Line
billing 2. Click Billing button. In the Schedule section, there
3. Verify that Top Covered is selected in should be 4 scheduled
Level field and LOV is disabled. quarterly bills, each with 0
4. Verify Arrears Invoice is selected in amount.
Invoicing Rule field.
5. Enter 1 in Seq No.
6. Enter 4 in Periods.
7. Enter 1 UOM/period.
8. Select Quarter from UOM LOV.
9. Click Schedule button.
10.Click OK.
 Click on action main menu to select It should display QA result
9
submit for approval form without any errors listed
under results section
 Click on continue approval This should close QA result
form and Authoring form
should get into disable mode
 Close Authoring form Authoring form should get
closed without any errors
Oracle contracts->inbox  Click on “respond” button to view all This should open notification
contracts for approval to invoke work list window with “approve”, reject
window and reassign button in enable
 Click on above created contract in that list mode
Oracle contracts->inbox->  Click on approve button This should approve the
notification window contract and open work list
window where in a notification
stating that the contract is
ready for signing
Oracle contracts->inbox->  Click on above created contract which is This should make the contract
work list now ready for signing and close the an active contract, which can
window be confirmed by searching
above contract using search
template form and observing
the status.
4.1.2 Update a Service Contract

Login: mfg/welcome
Update a Service contract Query for Contract XXXX Contract should become editable
Summary . Click Open for Update and under QA Hold status.
Service Agreement -> Launch Pad
Make either of the following changes
Add a line to contract
Follow 6 7 and 8 steps of 4.1.1
Approve Follow all steps after 9 of 4.1.1

5 Test Scenarios
5.1 Billing rule for Client/Warehouse/Transaction
5.1.1 Define a billing rule

Login: mfg/welcome
1. Setup> Billing Billing Rules Click on add button
2. Enter a new Billing Rule Name (Rule_RCV)
3. Enter the Billing Rule Description
4. Enter the Service Agreement Details Will be defaulted based on
the MO Operating Unit and
Operating Unit MO Default Operating Unit
profile.( Check TDD For
more details )
5. Service Agreement Select the service agreement
from LOV
6. Start Date and End Date Populated automatically.
7. The rule lines will be
Click on Button: Fetch lines from agreement populated.
8. Go to billing source Select from LOV.
9. Save the record. Pass
5.1.2 Update (rule name) of a billing rule

Login: mfg/welcome
1 Setup> Billing Billing Rules Query for Billing rule (Rule_RCV) The Rule is fetched
2 Update the Rule name to Rule_RCV_X Transaction saved
And save
3 Query for Billing rule (Rule_RCV) No records exist
4 Query for Billing rule (Rule_RCV_X) The Rule is fetched Pass
5.1.3 Update (description) of a billing rule

Login: mfg/welcome
2 Update the Rule Description to XYZ Transaction saved
And save
3 Query for Billing rule (Rule_RCV) The Rule is fetched Pass
And it shows the updated
description
5.1.4 Update (billing source) of a billing rule before billing

Login: mfg/welcome
2 The rule lines will be
3 Ensure that no billing is done(last computed
date is null)
Update the billing source by selecting another
value from LOV
Save the record. Transaction saved Pass
5.1.5 Query a billing rule and hit fetch lines from agreement button. On clicking this button, fetch and insert all the new Usage based Service item lines from
the service agreement. If multiple counters attached to the usage line, fetch the first available counter only. Only 1 counter per usage service is
supported

Login: mfg/welcome
1 Setup> Billing Billing Rules Click on add button
2 Enter a new Billing Rule Name (Rule_TEST)
3 Enter the Billing Rule Description
4 Enter the Service Agreement Details
Operating Unit
5 Service Agreement: Select the service
agreement from LOV which has multiple
counters associated to the item
Start Date and End Date will be Populated

automatically.
6 The rule lines will be Pass
Click on Button: Fetch lines from agreement populated. The lines should
fetch one counter only
5.1.6 Check the values of the service agreement LOV in the billing rule form

Login: mfg/welcome
2 Enter a new Billing Rule Name (Rule_TEST_1)
4 Enter Operating Unit
5 Click on the service contract LOV Only service contracts to be Pass
shown
LOV to pull up active service
agreements numbers LOV
should display Number, Version,
Party Name, description, start
date, end date)The Number,
Version and Party Name should
be shown as one field separated
by ‘:’ and description, Start Date
and End Date should be shown
as different columns.
5.1.7 Verify the behavior of operating unit LOV in the billing rule form when MOAC is disabled

Login: mfg/welcome
4 Click on Operating Unit LOV When MOAC is not enabled – Pass
Only current OU should be
shown and the field should be a
view only field.
5.1.8 Verify the behavior of operating unit LOV in the billing rule form when MOAC is enabled

Login: mfg/welcome
4 Click on Operating Unit LOV When MOAC is enabled the Pass
LOV should show all the
Operating Units user has access
to.
5.1.9 Create a service agreement with multiple accounts for a client. Create a billing rule for that contract. Verify if the lines fetched show the details
properly

Login: mfg/welcome
1 Create a Service contract Contract with multiple lines for a client with Contract number XXXX
different account for each line
3 Enter a new Billing Rule Name (Rule_RCV)
5 Enter Operating Unit
6 Service Agreement: CONXXXX
automatically.
The client name should be
shown as concatenated Account
Number and Client Name
separated by ‘:’
5.1.10 Verify that the lines fetched from the billing rule do not have end dated records

Login: mfg/welcome
Operating Unit
agreement from LOV

automatically.
Click on Button: Fetch lines from agreement populated. Verify that the lines
fetched from the billing rule do
not have end dated records
5.1.11 Update the service contract with a new item. Ensure that the fetch lines show this record also

Login: mfg/welcome
Operating Unit
agreement from LOV(CONXXXX)

automatically.
7 Update the contract Update the contract by adding a new item
Click on Button: Fetch lines from agreement populated. Ensure that the fetch
lines show the new ithem record
along with old ones
5.1.12 After one billing cycle, update billing source on one record to null in the fetched records

Login: mfg/welcome
3 Ensure that no billing is done (last computed
date is null)
4 Compute Billing Units Enter Request number XXXXXX
Third Party Logistics Billing Service contract OU: Vision operations Should complete normally
Administrator-> Calculate Billing Client: ClientXX
Units Rule: Either the rule in step 1
Service Contract: CONXXXX
Source to date: sysdate
Submit the request
5 Verify the last computed date Query for Rule (Rule_RCV) The last computed date on the
Setup> Billing Billing Rules fetched lines should updated to
the “Source to date” given in step
4
6 Update billing source to null Warning: Billing Unit Pass
calculation program has been
executed previously. Do you
really want to update the
Billing Source? YES or No
buttons.
5.1.13 Delete a billing rule

Login: mfg/welcome
2 Hit delete on tool bar Warning: Do you really want Pass
to Delete this rule? YES or
NO to Continue.
Rule should be deleted if YES is
hit
5.2 Calculate billing units

5.2.1 Execute the “Calculate billing units” program by giving service contract

Login: mfg/welcome
1 Compute Billing Units Enter Request number XXXXXX Pass
Administrator-> Calculate Billing Client: null
Units Rule name: null
Service item: null
Submit the request
5.2.2 Execute the “Calculate billing units” program by giving service item

Login: mfg/welcome
Service Contract: NULL
Service item: ITEMXXX
Submit the request
5.2.3 Execute the “Calculate billing units” program by giving client code

Login: mfg/welcome
Administrator-> Calculate Billing Client: Client1
Service item: NULL
Submit the request
5.2.4 Execute the “Calculate billing units” program by giving billing rule

Login: mfg/welcome
Units Rule name: Rule_TEST
Service item: NULL
Submit the request
5.2.5 Execute the “Calculate billing units” program without any optional parameters

Login: mfg/welcome
Service item: NULL
Submit the request
5.2.6 Execute the “Calculate billing units” program for a future date

Login: mfg/welcome
1 Compute Billing Units Enter Not allowed Pass
Third Party Logistics Billing Service contract OU: Vision operations
Service item: NULL
Source to date: sysdate+3
Submit the request
5.2.7 Verify the behavior of service contract LOV

Login: mfg/welcome
1 Compute Billing Units Enter Contract LOV should show only Pass
Third Party Logistics Billing Service contract OU: Vision operations active contracts
Administrator-> Calculate Billing
Units Click on the Service Contract LOV
5.2.8 Execute the “Calculate billing units” program by giving billing rule. Execute the program again after checking the dates

Login: mfg/welcome
Service item: NULL
Source to date: sysdate-5
Submit the request
2 Verify the last computed date Query for Rule (Rule_TEST) The last computed date on the
the “Source to date” given in
step1
Service item: NULL
Submit the request
4 Verify the last computed date Query for Rule (Rule_TEST) The last computed date on the
step3
5.2.9 Verify that the transactions done with respect to any UOM are reflected while billing in the number of transactions

Login: mfg/welcome
Service Contract: CONXXXX(with service item
UOM as transaction)
Service item: null
Submit the request
2 Verify the last computed date Query for Rule (Rule_TEST) The last computed date on the Pass
step1
The update in counters should
consider all the transactions
irrespective of the received UOM
5.2.10 Verify that the transactions are converted properly into the billing UOM (Ex: 2 transactions of 3 and 5 boxes each, should be considered as 8 billing
units)

Login: mfg/welcome
Service Contract: CONXXXX(with service item
UOM as BOX)
Service item: null
Submit the request
2 Verify the last computed date Query for Rule (Rule_TEST) The last computed date on the Pass
step1
The update in counters should
consider all the transactions that
happened for that UOM
5.3 End to End billing flows
5.3.1 Create a service agreement for multiple lines; ensure that billing is done weekly for few lines and monthly for other. Invoice client. Invoice the costomer
after few transactions/days

Login: mfg/welcome
1 Create a Service contract Contract for two lines for service items Contract number XXXX
SERXXX1- Storage in Volume
SERXXX2- material handling (labour)
2 Create a billing rule for contract Enter a new Billing Rule Name
Setup> Billing Billing Rules (Rule_CONXXXX )
3 Enter the Billing Rule Description Start Date and End Date will be
Operating Unit populated
Select the Service Agreement XXXX from
LOV
And Save
4 Press the Fetch lines button The rule lines will be populated
with respect to the entered service
contract
5 Select the Billing source (SOURCE_XX_VOL, Rule is saved
SOURCE_XX_MAT_HAND,) from lines LOV
and save
6 WMS transactions Perform Misc receipt for material for ClientXX Store the material for 1
into X.1.1 Locator of XXSUB in W1 day
7 Perform Misc receipt for some more material Store the material for 1
material for ClientXX into X.1.2 Locator of day
XXSUB in W1
Submit the request
9 Verify the last computed date Query for Rule (Rule_CONXXXX ) The last computed date on the
step8
10 Verify that the counters are View ->Find Search should fetch the matching
updated in contract Operating Unit: Vision Operations contract record
Service Agreement ->Launch Pad Contract: CONXXXX
Press ‘Search Button’
11 Select the contract The counter reading should be
Move to the lines tab updated according to the locator
Check the counter reading history occupancy
12 Run the billing program Name: Service Contracts Main Billing Request number XXXXXX
Third Party Logistics Billing Contract Number: CONXXXX Should complete normally
Administrator-> Generate Preview: Yes
Charges Submit the request The log should show tha counter
value and the calculated price.
The price calculated should
include price modifiers if any.
Administrator-> Generate Preview: No
Charges Submit the request
14 Auto Invoice Name: Autoinvoice Master Program Request number XXXXXX

Third Party Logistics Billing Transaction Source: OKS_CONTRACTS Should complete normally
Administrator-> Auto-Invoice (LOW) Sales Order Number: CONXXXX
(HIGH) Sales Order Number: CONXXXX
Submit the request

15 Verify invoice information View ->Find Search should fetch the matching
Service Agreement ->Launch Pad Operating Unit: Vision Operations contract record
Contract: CONXXXX
16 Select the contract Invoice details window should
Move to lines tab show the transaction type and
Tools-> Invoice Details amount, the invoice number is not
seen.
Line details are not populated yet.
17 Fectch Receivables NAME: Service Contracts Fetch Receivables Info Request number XXXXXX
Third Party Logistics Billing for Billing Should complete normally
Administrator-> Fectch
Receivables Information Submit the request
18 Verify billing information View ->Find Search should fetch the matching
Contract: CONXXXX
19 Select the contract The details should show the
Select the Billing details number of units billed, the
Move to History tab amount that is calculated and the
invoice number and invoiced date
etc.
Contract: CONXXXX
Tools-> Invoice Details amount, the invoice number is
populated now
22 Press Line Details button Invoice lines window should Pass
show the list of items invoiced
with bill amount, unit price and
UOM.
5.3.2 Create a service agreement for fixed space utilization. Invoice client. Invoice the customer after few transactions/days

Login: mfg/welcome
1 Create a Service contract Contract for two lines Contract number XXXX
SERXXX1- Storage in area
Usage type: fixed per period
SERXXX1- Insurance
LOV
And Save
contract
5 Select the Billing source Rule is saved
(SOURCE_FIXED_AREA ,
and save
This billing source shd calculate unts for a
partucular subinventory irrespective of the
occupancy(fixed space)
XXSUB in W1
Submit the request
step8
Check the counter reading history capacity

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Perform Misc issue of complete material for
ClientXX from X.1.1 Locator of XXSUB in W1
24 Issue all the client material out of stores
Submit the request
step25
Check the counter reading history capacity
Charges Submit the request The log should show the latest
counter value and the calculated
price.

Submit the request

Contract: CONXXXX
Tools-> Invoice Details amount; the invoice number is not
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.3 Create a service agreement for actual space utilization. Invoice client. Invoice the customer after few transactions/days

Login: mfg/welcome
1 Create a Service contract Contract for one line Contract number XXXX
SERXXX1- Storage in area
Usage type: Actual by qty
Apply a price adjustment of 5%
LOV
And Save
contract
5 Select the Billing source (SOURCE_XX_AREA, Rule is saved
and save
XXSUB in W1
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Perform Misc receipt for material for ClientXX
into X.1.1 Locator of XXSUB in W1
24 Perform Misc issue for material for ClientXX into
X.1.2 Locator of XXSUB in W1
Submit the request
step25
Move to the lines tab updated according to the latest
Check the counter reading history locator occupancy
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.4 Create a service agreement for minimum space charge and excess utilization. Invoice client

Login: mfg/welcome
5.3.5 Create a service agreement for receipt transaction. Invoice client. Invoice the customer after few transactions
Login: mfg/welcome
SERXXX1- Rev transactions
UOM: TXN
Apply a price adjustment (discount) of -5%
SERXXX1- Handling charges
Setup> Billing Billing Rules (Rule_CONXXXX)
LOV
And Save
contract
(SOURCE_XX_REC_TXN,
and save
6 WMS transactions Receive material against PO
7 Receive material against RMA/ASN
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
24 Receive material against PO
Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.6 Create a service agreement for put away transaction. Invoice client. Invoice the customer after few transactions

Login: mfg/welcome
SERXXX1- Put Away transactions
UOM: BOX
SERXXX1- Packing
LOV
And Save
contract
(SOURCE_XX_PUT_AWAY_TXN,
SOURCE_XX_MAT_PACK,) from lines LOV
and save
6 WMS transactions Put away LPNs into storage area
7 Put away LPNs into storage area
Submit the request
9 Verify the last computed date Query for Rule (Rule_CONXXXX) The last computed date on the
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Put away LPNs into storage area
24 Put away LPNs into storage area
Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.7 Create a service agreement for Inspection transaction. Invoice client. Invoice the customer after few transactions

Login: mfg/welcome
SERXXX1- Inspection transactions
UOM: TXN
LOV
And Save
contract
(SOURCE_XX_INS_TXN,) from lines LOV and
save
6 WMS transactions Inspect material
7 Inspect material
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Inspect material
24 Inspect material
Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.8 Create a service agreement for picking transaction. Invoice client. Invoice the customer after few transactions

Login: mfg/welcome
SERXXX1- Pick transactions
UOM: TXN
LOV
And Save
contract
(SOURCE_XX_PICK_TXN,
and save
6 WMS transactions Pick drop material against a SO
7 Pick drop material against a ISO
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Pick drop material against a SO
24 Pick drop material against a ISO
Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.9 Create a service agreement for shipping transaction. Invoice client. Invoice the customer after few transactions

Login: mfg/welcome
SERXXX1- Ship transactions
UOM: BOX
SERXXX1- Frieght charges
LOV
And Save
contract
(SOURCE_XX_SHIP_BOX,
SOURCE_XX_FRIEGHT) from lines LOV and
save
6 WMS transactions Ship material against a SO
7 Ship material against a ISO
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
23 WMS transactions Ship material against a SO
24 Ship material against a ISO
Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.10 Create a service agreement for receipt transaction. Perform multiple billing operations. Invoice client.

Login: mfg/welcome
UOM: BOX
LOV
And Save
contract
(SOURCE_XX_REC_TXN,
and save
Submit the request
step8

Submit the request
step25
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.3.11 Verify billing for multiple accounts for one party on a single service agreement.

Login: mfg/welcome
SERXXX1- Rec transactions
UOM: BOX
SERXXX2- Put away txns
UOM: TXN
Attatch different account to each line
LOV
And Save
contract
The lines should show the
account information
properly(client code shd show
account number also)
(SOURCE_XX_REC_TXN,
SOURCE_XX_PUT_AWAY,) from lines LOV
and save
7 Put away material against PO
Item : SERXXX1
Submit the request
step8
Move to the lines tab updated according to the number
Check the counter reading history of boxes received

15 Putway material against PO
Item: SERXXX1
Submit the request
step25
Move to the lines tab updated according to the number
Check the counter reading history of putwaya transactions
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.4 Change management on billing flows

5.4.1 Create a service agreement for receipt transaction. Compute billing units. Edit the contract and enter a new usage item. Invoice client

Login: mfg/welcome
UOM: TXN
LOV
And Save
contract
(SOURCE_XX_REC_TXN)from lines LOV and
save
Submit the request
step8
Move to the lines tab updated according to thenumber
Check the counter reading history of transactions

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
Edit the Contract Add one more service item
SERXXX2- Handling
Edit a billing rule for contract Query for (Rule_CONXXXX)
Setup> Billing Billing Rules
Press the Fetch lines button The rule lines will be populated
contract (new line is seen for the
new item)
Select the Billing source Rule is saved
(SOURCE_XX_HAND_CHARGE) from lines
LOV and save
Submit the request
step25
Move to the lines tab updated according to the new
Check the counter reading history transactions and the handling
charges
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.4.2 Create a service agreement for space utilization. Compute billing units. Edit the contract and enter a new usage item. Invoice client

Login: mfg/welcome
SERXXX1- Storagetransactions
UOM: AREA
LOV
And Save
contract
5 Select the Billing source (SOURCE_XX_AREA) Rule is saved
from lines LOV and save
6 WMS transactions Perform misc receipt of material into X.1.1
7 Perform misc receipt of material into X.1.2
Submit the request
step8

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
Edit the Contract Add one more service item
SERXXX2- Spl charges for temperature control
new item)
Select the Billing source (SOURCE_XX_STORE) Rule is saved
from lines LOV and save
23 WMS transactions Perform misc receipt of material into X.1.1
24 Perform misc issue of material from X.1.2
Submit the request
step25
Move to the lines tab updated according to the changes
Check the counter reading history in storage conditions and the
locator occupancy
price.

Submit the request

Contract: CONXXXX
seen.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.4.3 Create a service agreement for shipping transaction. Perform billing operation, edit the service contract, and make modification to pricing attributes,
approce the contract. Ensure the new pricing is considered in the next billing

Login: mfg/welcome
SERXXX1- Shipping transactions
UOM: BOX
Pricing – Type 1(15$ / BOX)
LOV
And Save
contract
(SOURCE_XX_SHIP_TXN) from lines LOV and
save
6 WMS transactions Ship material against SO
7 Ship material against ISO
Submit the request
step8
Move to the lines tab updated according to thenumber
Check the counter reading history of transactions

Submit the request

Contract: CONXXXX
seen.
The amount should be calculated
by no. of units * $ 15
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
Edit the Contract Update pricing
Pricing – Type2(use price breaks)
new item)
Select the Billing source Rule is saved
(SOURCE_XX_HAND_CHARGE) from lines
LOV and save
23 WMS transactions Ship material against SO
24 Ship material against ISO
Submit the request
step25
Move to the lines tab updated according to the new
Check the counter reading history transactions and the handling
charges
price.

Submit the request

Contract: CONXXXX
seen.
Line details are not populated yet
The amount should be calculated
according to price breaks.
Contract: CONXXXX
etc.
Contract: CONXXXX
populated now
UOM.
5.5 Others
5.5.1 Define a new test billing source

Login: mfg/welcome
1 Create a billing source Click on add button Transaction saved Pass
Setup> Billing Billing Source Enter a new Billing Source Name:
TEST_SOURCE
Description: Test source
Associated Procedure: Select Custom
Procedure Name: Enter the complete procedure
name like (TEST_Proc.TEST). This test procedure
should return a constant value say 100
And save
2 Assigh a billing source to billing Query for billing rule Rule_XX Transaction saved Pass
rule Hit on fecth lines button and associate the billing
Setup> Billing Billing Rule source to one of its lines
5.5.2 Verify that "Third Party Logistics Billing" seeded menu is available and shows all the expected functions

Login: mfg/welcome
1 Verify that the menu structure is It should be:
proper 1. Service Agreement
1.1 Launch Pad

1.2Administrator Workbench
2.Calculate Billing Units
3.Generate Charges
4. Auto-Invoice
5. Fetch Receivables Information
6. Setup
6.1Billing
6.1.1.Billing Sources
6.1.2 Billing Rules
6.2 Counters
6.2.1 Item Instance
6.2.1.1. Item Instances
6.2.1.2. Systems
6.2.1.3. Transactions
6.2.2 Counters
6.2.2.1. Counter Instance
6.2.2.2. Mass Readings
6.2.2.3. Template
6.2.2.4. Groupings
6.2.2.3. Estimation Methods
6.3 Pricing
6.3.1 Enter Price Lists
6.3.2 Enter Modifiers
6.4 Service Agreement

6.4.1 Lookups
6.4.2 Global Contract Defaults
6.4.3 Status and Operations
6.4.4 Billing Profile
6.4.5 Termination Reason
6.4.6 Quality Assurance
6.4.7 Process Definition
6.4.8 Communication Templates
6.4.9 Categories and Sources
6.4.9.1 Categories
6.4.9.2 Party Roles
6.4.9.3 Contract Roles
6.4.9.4 Role Sources
6.4.10 Time Units
6.4.10.1 UOM Classes
6.4.10.2 UOM
6.4.10.3 Time Unit of Measure
6.4.11 Autonumbering
Global Contract Defaults
Status and Operations
Billing Profile
Termination Reason
Quality Assurance
Process Definition
Communication Templates
6 Summary of Results/Issues
This section is used for any problems or issue found during the testing. It may also include any bugs or enhancements that were logged and any comments on the
functionality, ease of use, etc.
6.1 Issues Log
Test Case Issue Description Resolution / Action Status Bug Number

Reference
[Click here and type Open or Closed]
[Click here and type Open or Closed]

7 Appendix
7.1 Appendix A - Test Script Review Templates
7.1.1 Outline Review Template
Page Step Action Taken Status

No. No. Issue Description (by QA)
1 [Click here and type Open or Closed]
2
3
4
5

7.1.2 Test Script Review Template (after first Draft)

No. No. Issue Description (by QA)
2
3
4
5

7.1.3 Test Script Review Template (after first Round Testing)

No. No. Comments (by QA)
2
3
4
5

3PL Billing - Test Plan

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3PL Billing - Test Plan

Uploaded by

Copyright:

Available Formats

Functional Test Script Template 49281731.

doc – 3PL Billing

FUNCTIONAL TEST SCRIPT

Author: Sunil Mididoddi

Creation Date: 1-Feb-2010

Last Updated: 5-Feb-2010

File URL: [Click here and type the File URL]

Execution Start Date: [optional]

Execution Completion Date: [optional]

Status: APPROVED (IN PROGRESS, DRAFT, IN REVIEW, APPROVED)

12/8/2021 12/8/2021 Oracle Confidential - For internal use only Page 1

1.1 Change Record

Name Position Date Document Description of Change Including Section of Script

1.2 Document Review and Approval History

Name Role Position Document Review Date Comments Incorporated

1.3 Document References

Name Type of Reference Location

12/8/2021 12/8/2021 Oracle Confidential - For internal use only Page 2

1.4 Resource Estimates [Optional]

12/8/2021 12/8/2021 Oracle Confidential - For internal use only Page 3

FUNCTIONAL TEST OVERVIEW...................................................................................5

12/8/2021 12/8/2021 Oracle Confidential - For internal use only Page 4

2.1 Introduction/Overall Test Objectives

2.2 Test Outline

Test Case Description    

Define a billing rule Define a billing rule for receipt/ put    

Update (description) of a billing rule Update (description) of a billing rule

Test Case Description    

Test Case Description    

Test Case Description    

Test Case Description    

2.3 Process Flow [Optional]

3.1 Test Script Limitations

3.2 Test Script Dependencies / Assumptions

3.3 Default Setup [Optional]

Profile Site Level User

Additional Test Data

4.1 Service Contract

4.1.1 Create a Service Contract

Detail Description [Optional]

5. Verify that DEFAULT QA CHECK LIST is

Repeat above steps for all the usagelines

4.1.2 Update a Service Contract

Detail Description [Optional]

Approve Follow all steps after 9 of 4.1.1

5.1 Billing rule for Client/Warehouse/Transaction

5.1.1 Define a billing rule

Detail Description [Optional]

5.1.2 Update (rule name) of a billing rule

Detail Description [Optional]

5.1.3 Update (description) of a billing rule

Detail Description [Optional]

5.1.4 Update (billing source) of a billing rule before billing

Detail Description [Optional]

Detail Description [Optional]

Start Date and End Date will be Populated

Detail Description [Optional]

Detail Description [Optional]

Detail Description [Optional]

Detail Description [Optional]

Detail Description [Optional]

Start Date and End Date will be Populated

Detail Description [Optional]