Академический Документы
Профессиональный Документы
Культура Документы
INT/GAP/N03
BSS To AR Invoices Interface
Author:
Abhishek Mathur
Creation Date:
Last Updated:
Document Ref:
300440451/INT/GAP/N03/AN100
Version:
Issue1
Approved by: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _______________
GM / Business Support
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
Reviewers
Name
Position
Mr. Bandaranayake
Mr. Manorathne
Ms. Shamalee
Mr. T. Ganes
Amit Bhushan
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Document Control
ii
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
Mr. S. M. Bandaranayake
Ms. Shamalee
Mr. P. Manorathne
Mr. T. Ganes
Suresh Vadlamudi
Z.A.M. Nawzar
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Signature
Document Control
iii
Contents
1
1.1
1.2
1.3
Overview ...................................................................................................................... 1
2.1
2.2
2.3
2.4
2.5
2.6
3.1
3.2
3.3
4.1
4.2
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Document Control
iv
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
3.
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
1
S/N
Conditions to be Tested
Expected Result
4.
5.
6.
Create a
adjustment
customer.
7.
8.
9.
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
2
2.4
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
Enterprise - Medium
Enterprise - Large
Services
9
Sharing
10
Subsidiaries
11
12
Debtors - Operators-Infrastructure
Sharing
13
International
Source
Accounting Entry
Summary/Detail
BSS New
Invoices
Dr Debtor A/c
billed
transferred to
Cr Revenue A/c
be populated
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
3
Invoice
AR from BSS
Cr Tax A/c
BSS
Credit Note
Dr Revenue A/c
Canceled
Creation
Dr Tax A/c
be populated
Cr Debtor A/c
billed
Invoice
For Revenue Account, the below logic will be applied for B2B Invoices
S/N
Segment Name
Rules/Logic
Company
NA
Cost Center
BSS
Location
Profit Center
4.
Business Line
5.
Product Category
6.
Natural Account
7.
Technology
8.
Intercompany
9.
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)
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
4
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.
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
5
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
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Overview
6
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.
Once validation is completed and passed the records will move to the interface table.
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
7
3.3
3.3.1
3.3.2
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.
3.10.4
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
8
3.3.5
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
Enterprise Medium
Enterprise Large
10
Subsidiaries
11
12
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
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
9
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
Field
name
Size
(max)
Data
Type
Nullable
Allowed
Values
Field Description
Record
Type
30
String
No
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
BSS
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
10
Sr.
No.
Field
name
Size
(max)
Data
Type
Nullable
Allowed
Values
Field Description
Interface
Type
30
String
No
BSSERPARINV
Extract
Reference
30
String
Yes
NA
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
FILE
in the file
DETAIL
Yes
BSS
No
Standard/
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
Accounting date
String
No
Bill To Date
Invoice
240
String
Yes
15
String
No
Invoice Description
Description
8
Currency Code
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Currency
Functional Specifications
11
Terms Name
15
String
No
10
Conversion Date
String
Yes
Payment terms
Bill To Date
Conversion Rate
15
Numb
Yes
er
Exchange Rate
12
Line Number
15
Numb
No
Line Number
er
13
Line Type
20
String
No
ITEM/TAX
TAX
14
Quantity
15
Numb
Yes
er
no group separator is
expected.
15
15
Numb
No
er
Line Amount
expected decimal
separator is . and no
group separator is
expected.
16
UOM
25
String
Yes
17
Amount
15
Numb
No
Line Amount
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
20
String
Yes
Reference of Original
Required
if
for Adjustments)
Adjustme
nts are
being
sent,
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
12
21
Company
25
String
No
01
Value
22
Cost Center
25
String
No
Geographical Cost
Center
Location
25
String
No
Product Level)
Business Line
25
String
No
New Attribute in
BSS at Customer
Level
25
Product Category
25
String
No
Segment 2 of the
Revenue code
26
Account
25
String
No
Segment 3 of the
Revenue code
revenue lines
27
Technology
25
String
No
Segment 4 of the
Revenue code
revenue lines
28
Intercompany
25
String
No
BSS to
send
00
default
value as
00
29
Future1
25
String
No
BSS to
000
send
default
value as
000
30
Revenue Code
Extension
Yes
Segment 5 of the
Revenue code
line level.
00 If Type is
Receipt
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
13
Sr.
No.
Field
name
Size
(max)
Data
Type
Nullable
Field Description
Allowed
Values
Record
Type
30
String
No
FILETRAILER
Record
Count
15
Number
No
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.
BSSERPARINVYYYYMMDDSEQ.dat
3.3.10
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
14
3.3.12
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
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
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
15
The email sent to the mailing list will be in the below format:
3.3.13
3.3.14
ACCEPTANCE CRITERIA
All validated records from Staging to Interface
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices
Functional Specifications
16
4.1
Open Issues
ID
4.2
ID
Issue
Resolution
Impact Date
Impact Date
Closed Issues
Issue
Resolution
INT/GAP/N03
File Ref: SLT-Mobitel-AN100 Analysis Specification-FIN-INT-GAP-N03 - BSS to AR Invoices