Company INTERNAL

Page 1 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Architecture Outline [enter Project Name] v0.1

Analysis and high-level-design
Telenor Global Shared Services

Project name: Self billing and Reclassification functionality in AIM

Project number: <Project number, e.g., BR0123>

This is Template version 2.24, date 9.5.2014

This text and embedded guidelines on how to use this template are
included in blue text and should be removed before finalizing the
document.
The Architecture Outline is owned by the change/project manager
and is to be developed as a part of the change/project.

Please use the following document name when saving this document:
Architecture Outline Project Name v0.x
(where x is a number between 1 and 9)

Table of contents
Telenor Global Shared Services Architecture Outline Template v2.24
 Company INTERNAL
Page 2 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

1. Revision Log.........................................................................................................3
1.1 Changes............................................................................................................3
2. Introduction..........................................................................................................4
2.1 Background.......................................................................................................4
2.2 Project Roles.....................................................................................................4
2.3 Terminology......................................................................................................4
3. Proposed Solution...............................................................................................6
3.1 Solution Architecture.......................................................................................6
3.2 Information Architecture..................................................................................8
3.3 Technology Architecture.................................................................................9
4. Security...............................................................................................................12
4.1 Information Security......................................................................................12
4.2 Application Security.......................................................................................12
4.3 Accommodation of Risk Measures..............................................................12
4.4 Technical Security..........................................................................................12
4.5 Security testing...............................................................................................12
4.6 Regulatory Constraints..................................................................................13
5. Transition..............................................................................................................14

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 3 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

1. REVISION LOG
Version Date Prepared by Description
0.1 20.04.2018 Saurabh Mahajan First version

1.1 Changes

1.1.1 Version <n>

1. First version

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 4 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

2. INTRODUCTION

2.1 Background
There are two requirements discussed with Telenor Norway during AIM implementation
project. These functionalities were not present in JANUS (replaced by AIM) hence these were
not made available with AIM implementation.
 Self Billing functionality:
Self billing is needed for paying out commission to partners where exact amount is
known to Telenor. This functionality will allow Telenor to upload AP invoices in excel
and payment made to supplier. In future this functionality can replace/extend FPS /
multisys integration
Note: This document does not cater to Integration Requirements
Supplier will be able to view/download these invoices via iSupplier portal
Attached document will give detailed requirements

High Level Design -

Selfbilling in AIM.pdf

 Reclassification functionality
Reclassification of invoices are needed to correct any wrong accounting reported in
GL. Current reclassification is done in GL (without any link to subledger) OR a
manual 0 amount invoice in AP (without any link to original invoice)

Reclassification in
AIM V2.0.pdf

2.2 Project Roles

Project Role Name Organization Unit

Project Owner
Project Manager
Project Architect
System Owner
TSS Solution Architect
Contributor(s) Saurabh Mahajan Tieto

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 5 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

2.3 Terminology
Explain all acronyms used in this document.
Acronyms Meaning
AP Accounts Payable
GL General Ledger
Tn Norway Telenor Norge AS
Tieto Tieto Norway AS
GSS Telenor Global Shared
Services AS

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 6 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

3. PROPOSED SOLUTION
Both the functionalities will be build around Oracle AP and AIM.
Business Justification for requirements:
Self-Billing: Currently it is not possible to self-upload commission invoices via Excel.
Alternative is doing manual payments outside of ERP. This is completely manual and prone to
human errors. Tracking such payment is also major pain.

Reclassification:
Current reclassification done in GL or AP has no link to existing invoice. This is not possible
to check if an invoice has already been reclassified. This results in missing reclassification /
double reclassification. Current task is done using AP Responsibility which is restricted P2P
team in Pakistan.
After this functionality BU’s can perform self-reclassification without depending on raising
Service now request with Pakistan.

3.1 Solution Architecture

Self Billing Solution

The solution will consist of following technical elements
1. Excel Upload
2. Payables Open Import Process
3. Invoice Batch Approval
4. Invoice view in AIM History
5. Invoice view in iSupplier
6. Self billing Invoice Report

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 7 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Re-classification solution
The solution will consist of following technical elements
7. New Page in AIM to reclassify invoice

3.1.1 Discussion of Main Issues

1. The design uses AIM programs as base for data processing and flow
2. AIM will remain single interface to customer for all AP related tasks

3.1.2 Impacted Systems

Table showing impacted systems, including proposed changes.
System No. Role and Functionality in the Proposed Proposed Changes
and Name Solution
S00000 ATLAS New Customization linked with AIM

3.1.3 Customizations

Name Type Dist. Description Rationale

WebADI Y R Excel based interface for AP
Invoice upload

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 8 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Name Type Dist. Description Rationale

Batch approval Y R Batch level approval for self-billing
on Invoice invoices
Payables open G R Standard Oracle AP interface
interface
Invoice view in Y R Existing page needs modification
AIM History for Selfbilling solution
Invoice view in Y R Addition of Invoice image in
iSupplier iSuplier page
BI Report G R New excel based report
Reclassification Y R New OAF page in AIM to
Page reclassify invoice

3.1.4 Impacted Integrations (supporting business processes)

NA

3.2 Information Architecture

WebADI will upload data in staging table, whech will then get imported as per existing AIM
process. Interface to Basetable import is performed via Open Interface program provided by
Oracle

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 9 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

3.3 Technology Architecture

The solution plan to use WebADI for AP invoice upload and Custom OAF pages for
Reclassification invoice creation.

WebADI is UI based configuration, the data loaded will be landing on Custom staging table
(already used for AIM)

3.3.1 Infrastructure
Existing ATLAS Infrastructure to be used

3.3.2 Central network infrastructure

Existing Infrastructure to be used

3.3.3 End User Connectivity

Existing connectivity for ATLAS to be used.

3.3.4 Integration Connectivity

Existing connectivity to be used, no new additional

Question Answer
What modes of access will be provided  Telenor WAN: [Yes]
for the solution?
 SSL encryption: [Yes]
 Citrix over Telenor WAN: [Yes]
 Citrix over Internet: [Yes]
 Other (please specify)
How many users are planned for the  <50 for Commission invoice
service?
 Approx. 400 users for reclassification
Are non-functional requirements for  NA
performance, availability and user
experience defined?
Does the project require browser/device  Other than Internet Explorer: [No]
specific testing?
 IE version required: as per Oracle support policy
 Mobile phones: [Na]
 iPad: [No]

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 10 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

 Galaxy Pad: [No]

Does the test plan include availability No
and performance testing?
Does the test plan include user Yes
experience testing?
Does the test plan include business No
continuity testing? (e.g., testing
switchover to redundant instance and/or
network carrier)

3.3.5 Identity and Access Management (IAM)

NA as users access already in place for AIM
Question Answer
Will the TSS IAM platform be used for
access requests, attestation processes and
automated provisioning? (please specify)
Will the TSS IAM platform be used for
authentication and single sign-on?
Does the project have functional or
technical requirements that are not
implemented in the IAM platform today?
(please specify)
Does the project have specific reporting
requirements for IAM for compliance
reasons or otherwise?
Does the project include activities to
change IAM processes in the Business
Unit?
Does the project include activities to
change IAM processes in TSS?

3.3.6 Integration Development

NA, As no integration in scope
Question Answer
Who is responsible for integration
development in the project? (role and
name)
If external vendor, is the internal staffing
sufficient to perform quality assurance?
Will the project introduce integrations
between data centers/ vendors? (see
connectivity)

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 11 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Is TSS’ governance for integrations

followed?
Will the project utilize TSS’ integration
platform Cassini?
Do the integrations require full end-to-
end monitoring?
Will the project ensure ITIL support
process implementation to third parties
(target systems)?

3.3.7 Performance and Robustness

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 12 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

4. SECURITY
NA, Existing ATLAS security, confidentiality and Integrity to be followed.

4.1 Information Security

4.1.1 Confidentiality

4.1.2 Integrity

4.1.3 Availability
Existing ATLAS SLA to be applied for availability

4.2 Application Security

ATLAS application security model to be used, only authorized users will be able to get
Invoice upload responsibility

4.2.1 Authentication
Existing ATLAS password management and Authentication to be used

4.2.2 Authorization
Authorization will be based on ATLAS responsibility. A new dedicated responsibility will be
created for this purpose

4.2.3 Access Control

ATLAS access control to be used

4.2.4 Audit and Traceability

Same as ATLAS

4.2.5 Logging and Monitoring

Same as ATLAS

4.3 Accommodation of Risk Measures

Copy the “Proposed actions” from the security risk assessment including responsibility and
timeframe to accomplish the proposed activities.

4.4 Technical Security

NA, ATLAS mechanism to be used

4.5 Security testing

NA, ATLAS mechanism to be used

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 13 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

4.6 Regulatory Constraints

NA
.

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 14 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

5. TRANSITION
Include important considerations related to project dependencies, migration, and roll-out.
Refer to the project dependency analysis document [Error: Reference source not found].

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 15 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Appendix 1 GSS IT Architecture Principles Compliance

A set of IS architecture principles will be adopted by GSS IT. This document will in a later version refer to the current summary of these principles.
An example is Integration Strategy.

Indicate Project Compliance for all principles, Y (=yes), N (= no), P (= partial) or N/A (=not applicable). Comment on all entries that are not obvious
Note that non-compliance with governing principles must be approved by TSS IT Architectural Board.

Strategic Principles
ID Principle Guiding/ Project Comments
Governing Compliance

Telenor Global Shared Services Architecture Outline Template v2.24

 Company INTERNAL
Page 16 of 16
Prepared by Project Document
<Project short name> Architecture Outline
Approved by Date Status Version TSSid.
Doc.
<Approver> 0.1

Appendix 2 GSS IT Architectural Control Process

1 2 3

Architecture Board meeting

1 – Solution approval

Risk assessment 2 – Approval of changes

3 – Reporting and
final approval
Architecture Board Guiding Meeting

Architecture Control Introduction Meeting

Telenor Global Shared Services Architecture Outline Template v2.24