Professional Documents
Culture Documents
Date:
Release: mySAP ERP
Author:
Scenario
Convergent invoicing
History
Version
Status
Date
Table of Content
1
Description.....................................................................................3
1.1
1.2
References..............................................................................................4
Test Management....................................................................................4
General Information....................................................................19
Test Case......................................................................................21
Business Validation....................................................................23
Negative Checks..........................................................................24
324356755.doc
2/ 41
Description
1.1
Convergent Billing
1.1.1
Purpose
You can use this business process to create bills based on received and stored billable items. The billable items are created by rating systems or
other billing components, and can include event detail records, call detail records, bill detail records, and recurring and one-time charges/credits.
You use the Billing in Contract Accounts Receivable and Payable component here.
1.1.2
Process Flow
...
324356755.doc
3/ 41
1.2
References
Tester Handbook
Dev.doc
1.3
Test Management
Focus Area
Title
Test Case Key
(Technical Name):
Estimated Testing Time:
Last Modified Date/ Last
Modifier:
Review Status:
324356755.doc
4/ 41
Related Information
324356755.doc
3
4
Click on
and choose
to create properties
324356755.doc
6/ 41
Click on
and choose
to create properties
324356755.doc
7/ 41
10
11
Choose save
File ->new->billable item mapping
324356755.doc
8/ 41
12
13
14
Billable item and charged item class has been created successfully.
System displays the owner name.
324356755.doc
9/ 41
15
Choose OK and
16
324356755.doc
10/
17
18
Choose save
324356755.doc
11/ 41
19
20
21
324356755.doc
12/
22
23
24
324356755.doc
13/
25
26
27
28
and
and
29
324356755.doc
14/
30
31
under functions
32
33
34
324356755.doc
15/
35
36
Choose save.
Choose file->new->offer to create offer
37
Choose OK
Right click on talk and brouse and
choose add charge
324356755.doc
16/
38
324356755.doc
17/
39
Check
Call up transaction FQC0
Enter the posting area 8121 and check
account determination maintained
properly
324356755.doc
18/
40
324356755.doc
19/
41
PercyAccount.xml
324356755.doc
20/
42
324356755.doc
21/
43
324356755.doc
22/
44
45
324356755.doc
23/
46
324356755.doc
24/
47
subcriber
48
324356755.doc
25/
49
324356755.doc
26/
50
324356755.doc
27/
51
52
324356755.doc
28/
The data created in SAP-CC are transferred from SAP CC via the Bulk loader directly into SAP CI
1
VoiceChargeableItem
.tt
324356755.doc
29/
324356755.doc
30/
Choose execute
324356755.doc
31/
General Information
Role to Use
Logon Information
Navigation steps to start of test
CSS Component
messages
324356755.doc
for
error
32/
Customizing object:
Navigation in IMG:
<..>
<..>
Notes/ References
Background Transactions
Foreground transactions
Document status
Retesting & Validation of changes
Data integrity
Reports
Work Flow
Testing with end user profile
324356755.doc
33/
Web applications
Queues Monitoring
IDOC status monitoring
XML Monitoring
Volume & Load
Error messages
Negative testing
Test Case
If you have successfully created billable by one of the above mentioned alternatives you will be able to continue and can validate and bill these
billable items
SL
No
Expected Results
324356755.doc
34/
3a
The received
items can be
validated with
the information
of the sender
application( for
example Is the
number of items
in accordance to
the number of
items created by
SAP CC, is the
amount per
item/item type in
accordance to
the amount of
SAP-CC)
324356755.doc
35/
Enter contract
execute
account
and
Check if the
items created by
SAP CC are
stored as Raw
data.
Check if only
fields defined in
IMG can be
changed
324356755.doc
36/
1
2
5
Click on the icon
press F8
6
Select the icon
7
or all and
This steps
validates the
setting of the
grouping variant
324356755.doc
37/
to
Validate:
Is the number of
items in
accordance to
the number
which is defined
by definition if
the aggregation
group.
Is the amount
per billing
document item/
billing document
in accordance to
the amount of
the billable items
Check the tax
calculation.
Check the
currency, main
and sub
transaction
etc
Check the
presented
simulated
invoicing
document
324356755.doc
38/
In this step the validation of items not ready for billing can be executed. Billable items can be stored as raw data. Raw data
means, that the quality of the data does not allow the billing.Thats why the received items are not stored in the status billable
but in the status raw.
To test this process step you have to change the data storage definition of your billable item class. Please go to Contract
Accounts Receivable and Payable Integration Billable Item Management Define Processing Rules and Program
Enhancements. Here you select and mark your Billable item Class and change the processing rule to 1 Add all Items AS Raw
Data and save the changes.
Now you can start processing again with the process step create billable items in SAP CC.
In addition it is possible to allow changes of the received raw data. So you can define optionally the permission to change raw
data. Therefore you go to Accounts Receivable and Payable Integration Billable Item Management Define Changeable
Fields of Billable Items. Here you select you billable item class and add the field names which shall be allowed to be changed.
1
Enter contract
execute
account
and
Check if the
items created by
SAP CC are
stored as Raw
data.
Check if only
fields defined in
IMG can be
changed
324356755.doc
39/
Business Validation
Business case
BV1
BV2
BV3
BV4
BV5
BV6
BV7
BV8
BV9
Description
Business Test Cases These explain in detail the test steps to test the business cases listed above.
Test
case
324356755.doc
Description
Expected Outcome
40/
B1
B2
B3
B4
B5
B6
Negative Checks
Test
Cas
e
N1
N2
N3
N4
N5
N6
Description
Expected Result
List the output data from this test case that could be reused later on as reference for other test cases
324356755.doc
41/