Analysis Specification-FIN-InTGAPN03 - BSS To AR Invoices ...

OUM
AN.100 ANALYSIS SPECIFICATION

AIMS Ref: MD050
Sri Lanka Telecom
INT/GAP/N03
BSS To AR Invoices Interface
Author:
Abhishek Mathur
Creation Date:
October 28, 2015
Last Updated:
January 26, 2016
Document Ref:
300440451/INT/GAP/N03/AN100
Version:
Issue1
Approved by: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _______________
Mr. Sarath Silva
Mrs. Ramani Chandrika
GM / Revenue and Collection
GM / Business Support
AN.100 Analysis Specification
Doc Ref: 300440451/INT/GAP/N03/AN100

January 18, 2016
DOCUMENT CONTROL
1.1
Change Record
4
Date
1.2
Author
Version
11-Dec-15
Abhishek Mathur
1.0
05-Jan-16
Kalpana Penmetcha
1.1
Change Reference
BSS Meeting Minutes, Review

comments by Ganes
Reviewers
Name
Position
Mr. LSSK Silva
SLT Business Process Owner
Mr. Bandaranayake
SLT Key Users
Mr. Ramani Chandrika
SLT BSS Owner
Mr. Manorathne
SLT BSS Key User
Ms. Shamalee
SLT BSS Key User
Mr. N.B.G. Wimalarathna
SLT Track Lead AP
Mr. T. Ganes
SLT ERP Architect
Amit Bhushan
OCS ERP Architect
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Document Control
ii

January 18, 2016
1.3 Sign-off
This Analysis Specification (AN-100) related to FIN Sub-Track is aligned to the requirements provided /given by
SLT during the To-Be process and CRP-2 sessions and also the subsequent session held with OCS to collect the
requirement implement the customized function or feature or report as details out in this document.
The customized function / feature / report that are going to be developed based on the Specification given by SLT
must be developed and shown during the CRP-3 session and the same will be tested by SLT during the User
Acceptance Test.
Name
Role in the Project
Mr. LSSK Silva
SLT Business Process owner
Mr. S. M. Bandaranayake
SLT Key User
Ms. Shamalee
SLT BSS Key User
Mr. P. Manorathne
SLT BSS Key User
Mr. Wimal Wimalarathna
SLT Track Lead
Mr. T. Ganes
SLT ERP Solution Architect
Suresh Vadlamudi
ERP Project Manager / OCS
Z.A.M. Nawzar
ERP Project Manager / SLT
INT/GAP/N03
Signature
Document Control
iii

January 18, 2016
Contents
1
Document Control ...................................................................................................... ii
1.1
1.2
1.3
Change Record ............................................................................................................ ii

Reviewers ..................................................................................................................... ii
Sign-off ........................................................................................................................ iii
Overview ...................................................................................................................... 1
2.1
2.2
2.3
2.4
2.5
2.6
Business Objectives ..................................................................................................... 1

Major Features ............................................................................................................. 1
Scenarios ...................................................................................................................... 1
Business Rules ............................................................................................................. 3
Assumptions ................................................................................................................. 5
Changes to be done at BSS system level .................................................................... 6
Functional Specifications .......................................................................................... 7
3.1
3.2
3.3
Component Description ................................................................................................ 7

Process Flow ................................................................................................................ 7
Custom Interface Design .............................................................................................. 8
Open and Closed Issues .......................................................................................... 17
4.1
4.2
Open Issues ............................................................................................................... 17

Closed Issues ............................................................................................................. 17
INT/GAP/N03
Document Control
iv

January 18, 2016
OVERVIEW
SLT will use BSS system for bill generation for Telecom customers, whom rating involve in general.. SLT has
decided to transfer the Bills (Invoice) of the B2B customer to ERP to manage these customers using advance
credit control feature in ERP.. B2C Customer invoice or receipts will not be taken to ERP AR.
2.1
Business Objectives
This document provides the features you need to satisfy the following basic business objectives. You will be
able to address the following:
1. Create an interface to transfer B2B related BSS invoices (BSS Bills) to ERP AR Module based on
certain conditions
2.2
Major Features
All the B2B related Bills generated in BSS (CBIS and ICON instances) for below categories of customers
would be transferred from BSS to AR. The below Customers categories / Business Lines will be considered
as B2B Customer in ERP perspective.
1. Operators - Local Infrastructure Sharing (BSS-CBIS)
2. Interconnect - International Voice Customers (BSS-ICON)
3. Interconnect - Domestic Customers (BSS-ICON)
4. B2C Corporate (BSS-CBIS)
2.3
Scenarios
Please find the scenarios that describe to accomplish the functions within this package:
S/N
Conditions to be Tested
Expected Result
Create a B2B bill for Operator

Local Infrastructure sharing
customer in the BSS system.
The AR invoice should be created as desired with

Source as BSS. Debit Account should be Debtor Local Infrastructure Sharing account and credit lines
will be revenue and tax lines respectively coming from
BSS system
Create a B2C Bill for end

customer in BSS System
The AR invoice should not be created as its a B2C

customer.
3.
Create a B2B invoice in the

BSS system for the customer
The record will be held at staging level validation stating

Customer does not exist and The BSS team review
the customer that they had selected for this record. If
INT/GAP/N03
Overview
1
S/N

January 18, 2016
Conditions to be Tested
Expected Result
who does not exist in oracle
the information is correct in BSS, then they will send

request to oracle to create the same. Once customer is
created the record will be reprocessed in Oracle.
4.
Create a B2B bill in BSS

system and then cancel the
invoice next run day
The AR invoice will be created for original bill with a

combination of bill number and version number from
BSS. Once the cancellation request come from BSS
system in AR a credit note will be generated with the
same invoice number and applied against the original
invoice
5.
Create a B2B Bill credit

adjustment/credit note for a
domestic customer
The AR Credit Memo invoice will be created for

negative amount. The invoice number will be with a
combination of bill number +Version number
6.
Create a
adjustment
customer.
The AR Invoice will be created for positive amount. The

invoice number will be with a combination of bill number
+ Version number
7.
Create a B2B Bill credit

adjustment for a International
customer
The AR Credit Memo invoice will be created for

negative amount. The invoice number will be with a
combination of bill number + Version number
8.
Create a B2B Bill Debit

adjustment for a International
customer
The AR Debit Memo will be created for positive amount.

The invoice number will be with a combination of bill
number + Version number
9.
Create a B2B bill along with tax.
The AR invoice will be created along with separate tax

lines. There will be a separate line item for tax
B2B Bill Debit

for a domestic
INT/GAP/N03
Overview
2
2.4

January 18, 2016
Business Rules
Only B2B Customers Invoice will be interface to ERP AR Module. are in scope for the records to be
processed
As per the RD-11 finalization, the following customers are considered as B2B customers in ERP Perspective
S/N
BSS Customer
Receivable Account in ERP
Enterprise - Medium
Debtors - B2C Corporate
Enterprise - Medium - Managed Services
Enterprise - Revenue Sharing
Enterprise - Large
Enterprise - Large - Managed Services
Enterprise - Large - Revenue Sharing
Enterprise - Government Inst.
Enterprise - Government Inst. - Managed
Services
9
Enterprise - Government Inst. - Revenue
Sharing
10
Subsidiaries
Intercompany Receivables (with

Intercompany segment)
11
Other Operators - Interconnect Domestic
Debtors - Interconnection Domestic
12
Other Operators - Infrastructure Sharing
Debtors - Operators-Infrastructure
Sharing
13
International
Debtors - International Voice
The same should be provided while extracting records from BSS.

New Transaction Source of BSS will be created in AR
Accounting Entries
Invoice
type
Source
Accounting Entry
Summary/Detail
BSS New
Invoices
Dr Debtor A/c
Based on transaction type mapping this will
billed
transferred to
Cr Revenue A/c
be populated
INT/GAP/N03
Overview
3
Invoice

January 18, 2016
AR from BSS
Cr Tax A/c
Based on revenue line mapping these

account will be populated
BSS
Credit Note
Dr Revenue A/c
Based on transaction type mapping this will
Canceled
Creation
Dr Tax A/c
be populated
Cr Debtor A/c
Based on revenue line mapping these
billed
Invoice
account will be populated
For Revenue Account, the below logic will be applied for B2B Invoices
S/N
Segment Name
Rules/Logic
Associated BSS Fields
Company
01 will be Hard Coded for SLT
NA
Cost Center
Customer Billing Account level from
Geographical Cost Center
BSS
Location
Product level from BSS
Profit Center
4.
Business Line
Customer Account level from BSS
GL Sub segment (New Attribute to be

created in BSS)
5.
Product Category
Product Level from BSS
Segment-2 of Revenue Code
6.
Natural Account
Product Event Level from BSS
7.
Technology
8.
Intercompany
Customer Account Level from BSS
ERP will default this based on the

Business Line
9.
000 will be Hard Coded
Future1
NA
For the following Product Categories, Deferred Revenue Account will be credited instead of Revenue Account
(same will be sent by BSS instead of Revenue code)
Megaline Voice Prepaid
Megaline Voice Postpaid
DNR (Domain Name Registration)
Backhauling
IRU
Only invoices that are Billed in BSS system should appear in Oracle AR. Unbilled invoices will not be picked
from the BSS system.
For invoice creation the status in BSS system will be Created and creation date will be system date.
INT/GAP/N03
Overview
4

January 18, 2016
For invoice cancellation, the status in BSS is 'Cancelled' and cancellation date would be system date. The
invoice number will be created with same invoice number and depending on Cancelled date (System Date),
system will pick the record and create a credit note with the same invoice number and apply the credit note to
the invoice to make the balance zero.
For invoice adjustment:

For negative adjustments, in BSS credit notes would be created for negative adjustments and same
will be interfaced in oracle
For positive adjustment there are 2 things
a. Debit notes will be created for "international" customers and same will be interfaced in
Oracle AR
b. Regular positive invoice would be created for domestic customers. Same will be interfaced
in Oracle AR.
Tax account will be populated at the line level in BSS and same will be incorporated in AR with tax amount as
Credit line item.
Invoice number + plus version number will be Oracle AR Invoice (Transaction) number
2.5
Assumptions
For all the B2B Customer; their respective accounts and site are created in Oracle AR before transactions can
be interfaced.
Customer Account Number in ERP should exactly match customer account number in BSS.
All invoice related data like payment terms should be present.
BSS will maintain the ERP Chart of account values as its account and product level attributes, such that these
Values can be used to create the bill level COA combinations
The invoices created in AR will be in complete state and cannot be modified.
For any correction the same should be rectified in BSS system and then it will be reflected in Oracle in AR in
form of either cancellation or adjustment.
All the values of Oracle Chart of Accounts which are required to be derived from BSS will be maintained as
attributes in BSS (Cost center, Location, Business Line, Product Category, Account, Technology,
Intercompany)
Extracting the invoices related to B2B customer should be done by both Instances of BSS (Both in CBIS and
ICON)
Separating of customer category OR Business Line at invoice level has to be done by BSS and same will be
mapped in oracle as Transaction Type. Logic to extract data based on Customer category OR Business Line
has to be done by BSS team
INT/GAP/N03
Overview
5

January 18, 2016
Interface will be scheduled to run daily once in both system and can be run manually also if required.
All the data required for this interface (Customer Name, Address, Transaction Type, Invoice Currency Code,
Terms Name, UOM, Tax Code and Accounting Class Code) has one to one mapping between BSS and ERP.
However if required necessary Mapping will be maintain in ERP.
Transaction Type for the Invoice should be identified based on the Business Line value sent by BSS:
One Transaction Type will be created for each Business Line
2.6
Changes to be done at BSS system level

The Changes required in the BSS to manage this Interface is same as the Changes required by the
Interface between BSS to ERP GL. Therefore doing the changes mentioned in the Interface document
(AN-100) SLT-AN100 Analysis Specification-FIN-INTGAPN05 - BSS to GL.doc in BSS will fulfill the
requirement of this Interface as well. Therefore there is no need for the changes to be specific for this
interface.
INT/GAP/N03
Overview
6

January 18, 2016
FUNCTIONAL SPECIFICATIONS
The following defines the user interface elements of this custom extension.
3.1
Component Description
The following components are required to support this custom extension:
1. Concurrent program to put data to staging table
o Component Type: Concurrent program
o Name: XXSLT Import B2B Invoices from BSS to staging
2. Concurrent program to validate and insert data into interface table
o Component Type: Concurrent Program
o Functional Name: XXSLT B2B AR Invoices Import from staging
3. Concurrent program to run Autoinvoice and import program to moved data in the base table
o Component Type: Concurrent Program
o Functional Name: Autoinvoice Master Program and Autoinvoice Import program
3.2
Process Flow
B2B Invoices will be created in BSS (both in CBIS and ICON Instance) system in Created Status and
billed
The BSS system (both in CBIS and ICON Instance) will extract B2B invoices which will be picked as
a part of interface program by both instance and then the same will be moved to the data in the
staging table in ERP.
In the staging table system will perform validations
Once validation is completed and passed the records will move to the interface table.
At interface levels also it would performs certain validations
Once data is processed by interface tables the same will go and hit the base tables
The Interface program will give summary output giving total count and total amount of the Invoices
received from CBIS and ICON separately.
Once the interface is completed and all records are successfully transferred to ERP base tables,
another concurrent program will run containing interface detail report stating details of invoices
imported by the concurrent program. This will be run when all records are successfully processed.
For any interface exception, the output of interface exception report will come with the log of interface
program stating exact reason leading to exception
INT/GAP/N03
Functional Specifications
7
3.3
3.3.1

January 18, 2016
Custom Interface Design

DATA FILE
A flat file with the data required to be processed should be sent to ERP for processing from both
BSS-CBIS Instance and BSS-ICON Instance.
3.3.2
Validation/ Derivation Rules
3.3.3
DEFAULT VALUES
This section lists the default value rules that are to be used in the integration of B2B AR Invoices from
BSS. The default value rules explain the logic behind why a certain default value has been selected.
Target Application Table
3.10.4
Target Application Table

Column
Default Value
RA_INTERFACE_LINES_ALL
ORIG_SYSTEM_BATCH_NAME
BSS
RA_INTERFACE_LINES_ALL
Operating Unit
PROCESSING RULES
This section lists the processing rules that are to be used in the transfer of B2B Invoices from BSSCBIS and BSS-ICOM Instances to ERP AR Module.
RULES:
PR1: Records will be processed in batches (once in a day). Extract of B2B Invoices is done once a
day and the details are populated in staging tables
PR2: Validate records in staging table and place the records that passed validation to Interface table
PR3: If there are any errors in the records, the entire file will be rejected and email will be sent to the
mailing list and the BSS team can correct the errors and resend the file again
PR4: Once records are processed to Interface table, Autoinvoice Import Program will be
automatically run to pick the processed records from Interface tables to base tables
INT/GAP/N03
8
3.3.5

January 18, 2016
EXTRACTION PROGRAM LOGIC
All B2B Invoices which are eligible to be created as Receivable Invoices in ERP to be extracted by
BSS system.
Invoices for the Customers belong to the following Business Line (Business Line maintained at
Customer Level in BSS) has to be extracted from BSS. (At Present there is no Attribute in BSS to
capture the Business Line at Customer Level. However it has been decided to create a new
Attribute in BSS to capture the Business Line of the Customer in Customer Account)
S.No
Customer Business Line
Enterprise Medium
Enterprise - Medium - Managed Services
Enterprise - Revenue Sharing
Enterprise Large
Enterprise - Large - Managed Services
Enterprise - Large - Revenue Sharing
Enterprise - Government Inst.
Enterprise - Government Inst. - Managed Services
Enterprise - Government Inst. - Revenue Sharing
10
Subsidiaries
11
Other Operators - Interconnect Domestic
12
Other Operators - Infrastructure Sharing
13
International
Only invoice that are Billed in BSS system should be transferred to Oracle AR. Unbilled invoices
will not be picked from the BSS system.
3.3.6
INTERFACE/VALIDATION PROGRAM LOGIC

This section describes the logic for the conversion programs that will be built to support the interface.
The interface of AR Invoices is done through following concurrent programs:
XXSLT B2B AR Invoices from BSS

Auto Invoice Master and Import Program
Following are the concurrent programs:
INT/GAP/N03
9

January 18, 2016
1. Validation Program Name XXSLT B2B AR Invoices from BSS

Validate Staging table records and mark unvalidated records as REJECTED. The validation
program will pick all the records with status NEW for processing.
2. Interface Program Name Autoinvoice Master and Import Program.
This program is the standard AR Interface program to import invoices from Interface to base
tables. This program will perform all the standard validations and import successful records into AR
Invoices tables. Any rejected records have to be corrected by BSS team and will be processed in the
next run of the program
3.3.7
CLEAN-UP CRITERIA
Below is a list of clean-up criteria for the Interface:
The records must be deleted from staging table if they are successfully validated.
The records must be deleted from receivable open interface tables if they are successfully
imported.
The records in open interface table can be manually purged by running the program
AutoInvoice Purge.
Any Data from the staging table, which is older than 60 days, must be automatically deleted.
3.3.8
INTERFACE MAPPING
3.3.9
FILE STRUCTURE DETAILS

The file provided to ERP must contain Header, Detail and Trailer as mentioned below:
The File Header must contain the following fields:

Sr.
No.
Field
name
Size
(max)
Data
Type
Nullable
Allowed
Values
Field Description
Record
Type
30
String
No
Identifier for start of file
FILEHEADER
Extract
Timestamp
30
DateTime
No
Datetimestamp when
the extract is generated
should be provided in
the format : YYYY-MMDD HH24:MI:SS
NA
Source
System
String
No
Identifier to identify the

source system
BSS
INT/GAP/N03
10
Sr.
No.

January 18, 2016
Field
name
Size
(max)
Data
Type
Nullable
Allowed
Values
Field Description
Interface
Type
30
String
No

integration
BSSERPARINV
Extract
Reference
30
String
Yes

extract in the source
system
NA
The File Detail must contain the following fields:
S/
N
1
Field name
Record Type
Batch Name
Invoice Type
Size
(max)
30
40
Data
Type
String
String
Null
able
No
Field Description in
ERP
Allowed
Values
Identifies the data records
FILE
in the file
DETAIL
Yes
BSS
No
Standard/
BSS Field Name

-
DEBIT /
CREDIT
3
Customer Name
240
Customer Account
String
No
Customer Name
String
No
Billing Account
Number
4
Invoice Number
Number
20
String
No
Invoice Number +
Version Number
Invoice Date
String
No
Invoice Date should be
Actual Bill Date
provided in the format :

YYYYMMDD
6
Accounting date
String
No
Accounting Date should be
Bill To Date

YYYYMMDD
As per Billing period,
identify Bill from and Bill to
dates. And Accounting
date will be Bill To date
7
Invoice
240
String
Yes
15
String
No
Description of the Invoice
Invoice Description
Description
8
Currency Code
INT/GAP/N03
Currency
11

January 18, 2016
Terms Name
15
String
No
10
Conversion Date
String
Yes
Payment terms
Conversion Date should be
Bill To Date

YYYYMMDD
11
Conversion Rate
15
Numb
Yes
er
If currency <>LKR and no
Exchange Rate
exchange rate populated

by BSS, ERP will extract
the rate from GL for the
Conversion Date
12
Line Number
15
Numb
No
Line Number
er
13
Line Type
20
String
No
Possible values ITEM,
ITEM/TAX
TAX
14
Quantity
15
Numb
Yes
Quantity. The expected

decimal separator is . and
er
no group separator is
expected.
15
Unit Selling Price
15
Numb
No
er
Selling Price. The
Line Amount
expected decimal
separator is . and no
group separator is
expected.
16
UOM
25
String
Yes
Unit of Measure Ex: Each
17
Amount
15
Numb
No
Amount. The expected
Line Amount
decimal separator is . and
er
no group separator is
expected.
18
Tax Code
50
String
Yes
Required
if Line
Type is
TAX
19
Interface Line
150
String
Yes
Attribute1
20
Related Invoice
Number
Unique reference from

BSS side
20
String
Yes
Reference of Original
Required
Invoice number (required
if
for Adjustments)
Adjustme
nts are
being
sent,
INT/GAP/N03
12
21
Company

January 18, 2016
25
String
No
ERP will populate the
01
Value
22
Cost Center
25
String
No
Cost Center will be picked
Geographical Cost
from BSS customer
Center
account level and to be
(At Account Level)
populated for revenue lines

23
Location
25
String
No
Location will be picked
Profit Center (At
from BSS customer
Product Level)

24
Business Line
25
String
No
Business Line will be
New Attribute in
picked from BSS customer
BSS at Customer
Level
25
Product Category
25
String
No
Product Category will be
Segment 2 of the
picked from BSS and to be
Revenue code
26
Account
25
String
No
Segment 3 of the
and to be populated for
Revenue code
revenue lines
27
Technology
25
String
No
Segment 4 of the
and to be populated for
Revenue code
revenue lines
28
Intercompany
25
String
No
ERP will change this value
BSS to
based on Business Line
send
00
default
value as
00
29
Future1
25
String
No
BSS to
000
send
default
value as
000
30
Revenue Code
Extension
Yes
It will be captured in DFF
Segment 5 of the
Attribute -1 of the Invoice
Revenue code
line level.
00 If Type is
Receipt
INT/GAP/N03
13

January 18, 2016
The file Trailer should contain the following fields:
Sr.
No.
Field
name
Size
(max)
Data
Type
Nullable
Field Description
Allowed
Values
Record
Type
30
String
No
Identifier for end of file
FILETRAILER
Record
Count
15
Number
No
Total Number of records

in the file including
header and trailer
records.
NA
Note: If one Invoice has 5 lines in BSS (3 Item lines + 2 Tax lines), the same should be sent to ERP as 5
lines specifying in the Line type field whether it is ITEM/TAX line.
The data should be provided in a flat file.

Each of the fields in the file in the row is separated from the next field by a pipe (|) character and if the
value itself contains one or more pipe characters then the value must be enclosed by double quotes (").
If a field has no value, the file should not provide any characters but still terminate the field with a pipe
character.
A new line character should be provided to terminate each row.
The file name must contain the source system, target system, interface and timestamp details as
mentioned below:
BSSERPARINVYYYYMMDDSEQ.dat
Date should be in the format YYYYMMDD.
SEQ should contain sequence of the file for the day.
Sample File Name: BSSERPARINV2015112401.dat
3.3.10
DETAILS OF THE LEGACY SYSTEM

Net Cracker Billing System
3.3.11
INTEGRATION STRATEGY
Below will be the integration approach used for this integration:
The source system (Both CBIS and ICON Instances) will extract the B2B invoices on daily
basis.
The BSS-CBIS Instance and BSS-ICON Instance will transfer extracted file to staging area
on ERP application server
INT/GAP/N03
14
3.3.12

January 18, 2016
A program will be scheduled on ERP to pick and process the file at a particular time of the
day. This program will read the data from file and puts into staging table.
At staging table, the validations will be performed and pushed to interface table.
During the processing of the interface in ERP, if there is any validation error, then an error
report will be generated and a notification will be sent via e-mail with the details of the reason
for Validation failure.
For successfully processed records another concurrent program will run which will display
BSS to AR invoices successfully processed.
ERROR HANDLING
On completion of running the program, any errors detected will be reported in the log file
Error Type
Key Field not populated in Oracle staging
table (eg Customer_name,
Customer_Account,
trx_number,
Invoice_Currency_Code
Action
Invoice will not be processed to the interface table
Error Text :
Customer name/Customer site code/Invoice
Num/Invoice Amount/Invoice Currency Code is null in
the Invoice&XXXX
Amount
Invoice_currency_code <> LKR but
Exchange Rate is not populated
Invoice will not be processed to the interface table

Error Text:
Exchange Rate is required for foreign currency invoices
Unexpected Errors while processing invoice

data (ie unhandled exceptions)
Invoice will not be processed to Interface table
Unexpected Program Error
Process will complete with status of Error. No records

will be processed to interface table. Program needs to
be rerun
During validation, if any records fail validation error the entire file will be rejected and the error details will be
displayed in the output of program.
If the standard interface program fails, the errors have to manually corrected and re-processed as per the
standard interface guidelines.
If any errors are detected during the processing of the validation program, an e-mail with the failed program
name and request details will be sent to mailing list identified in the profile option XXSLT: BSS to ERP
Receivable Invoice Interface Error Mailing List.
INT/GAP/N03
15

January 18, 2016
The output of the error file will be as follows:
The email sent to the mailing list will be in the below format:
Dear Support Team,

The file <BSSERPARINV2015112401.dat> for importing Receivable invoices from BSS to ERP has
failed validation errors. For details, please review the output of the concurrent request : <23456> in
ERP system.
3.3.13
VOLUMES AND PERFORMANCE

A daily batch of a volume of approx 10000 records is expected.
3.3.14
ACCEPTANCE CRITERIA
All validated records from Staging to Interface
INT/GAP/N03
16

January 18, 2016
OPEN AND CLOSED ISSUES
4.1
Open Issues
ID
4.2
ID
Issue
Resolution
Responsibility Target Date
Impact Date
Responsibility Target Date
Impact Date
Closed Issues
Issue
Resolution
INT/GAP/N03
Open and Closed Issues

17

Analysis Specification-FIN-InTGAPN03 - BSS To AR Invoices ...

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Analysis Specification-FIN-InTGAPN03 - BSS To AR Invoices ...

Hochgeladen von

Copyright:

Verfügbare Formate

OUM

AN.100 ANALYSIS SPECIFICATION

Sri Lanka Telecom

October 28, 2015

January 26, 2016

Mr. Sarath Silva

Mrs. Ramani Chandrika

GM / Revenue and Collection

AN.100 Analysis Specification

Doc Ref: 300440451/INT/GAP/N03/AN100

BSS Meeting Minutes, Review

Mr. LSSK Silva

SLT Business Process Owner

SLT Key Users

Mr. Ramani Chandrika

SLT BSS Owner

SLT BSS Key User

SLT BSS Key User

Mr. N.B.G. Wimalarathna

SLT Track Lead AP

SLT ERP Architect

OCS ERP Architect

AN.100 Analysis Specification

Doc Ref: 300440451/INT/GAP/N03/AN100

Role in the Project

Mr. LSSK Silva

SLT Business Process owner

SLT Key User

SLT BSS Key User

SLT BSS Key User

Mr. Wimal Wimalarathna

SLT Track Lead

SLT ERP Solution Architect

ERP Project Manager / OCS

ERP Project Manager / SLT

AN.100 Analysis Specification

Doc Ref: 300440451/INT/GAP/N03/AN100

Document Control ...................................................................................................... ii

Change Record ............................................................................................................ ii

Business Objectives ..................................................................................................... 1

Functional Specifications .......................................................................................... 7

Component Description ................................................................................................ 7

Open and Closed Issues .......................................................................................... 17

Open Issues ............................................................................................................... 17

AN.100 Analysis Specification

Doc Ref: 300440451/INT/GAP/N03/AN100

Create a B2B bill for Operator

The AR invoice should be created as desired with

Create a B2C Bill for end

The AR invoice should not be created as its a B2C

Create a B2B invoice in the

The record will be held at staging level validation stating

AN.100 Analysis Specification

Doc Ref: 300440451/INT/GAP/N03/AN100

who does not exist in oracle

the information is correct in BSS, then they will send

Create a B2B bill in BSS

The AR invoice will be created for original bill with a

Create a B2B Bill credit

The AR Credit Memo invoice will be created for

The AR Invoice will be created for positive amount. The

Create a B2B Bill credit

The AR Credit Memo invoice will be created for