enterprise structure.pptx

Copyright © 2012 Accenture All rights reserved.

Accenture Innovation Centers for SAP

consulting | technology | outsourcing


Enterprise Structure

CompanyZ_DK12

CompanyZ_DK15

CompanySED

CompanyDK07

CompanyTNI

CompanyDK02

CO.CODEDK02--

TeliaSonera Danmark A/S,Copenhagen

CO.CODEDK05-- TSIC

Denmark A/S, Copenhagen

CO.CODEDK07--Tilts

Communications A/S, Copenhagen

CO.CODEDK12 -- T Nättj

Norden AB, DK, Copenhagen

CO.CODEDK15 -- DLG Tele I/S, Copenhagen

CO.CODEDK21 -- Sergel

A/S, København

Controlling Area-- 1000

CLIENT 100

Copyright © 2012 Accenture All rights reserved.Copyright © 2013 Accenture All rights reserved

• Posting Period Varian

Accounting Principles

Accounting Principles

Co.code Company name VariantDK01 Country Template DK 0001DK02 TeliaSonera Danmark A/S DK02DK05 TSIC Denmark A/S TSICDK07 Tilts Communications A/S DK07DK12 T Nättj Norden AB, DK DK12DK15 DLG Tele I/S DK15DK21 Sergel A/S DK21


Global Parameters

Co.CdCompany Name ChAc FV VAT Reg.No CCAr FStV

DK01Country Template DK INT K4 0001

DK02TeliaSonera Danmark A/S 1000K4 DK18530740 1002 1000

DK05TSIC Denmark A/S 1000K4 DK24210413 1000

DK07

Tilts Communications A/S 1000K4 DK17260642 1002 1000

DK12T Nättj Norden AB, DK 1000K4 DK20367997 1002 1000

DK15DLG Tele I/S 1000K4 DK25813286 1000

DK21Sergel A/S 1000K4 DK35481036 1002 1000

Microsoft Excel Worksheet


General Ledger

CompanyDK12

CompanyDK15

CompanyDK21

CompanyDK07

CompanyDK05

CompanyDK02

CHART OF ACCOUNT 1000

• Chart of Accounts• G/L Account Group• Preliminary posting Workflows• Release approval for Parking Documents• Users with release authorizations• Additional rules for automatic clearings• Interest calculations• Accrual Engine Microsoft Excel

Worksheet


SM35 EXCEL

JV Parked

Run In Background

GL ApproversPost directly

ZFI09

Parked

Parked

CompleteGL Approvers Post

Journal Voucher Process


Account payables

• Accounting Groups• Number Range for Vendor group• Correspondence types• Define Document types• Define payment block reasons• Tolerance groups for Vendors• Paying Company code settings.• Sender FORMS per co. code• House banks for DK• Electronic bank statement• Below is an overview of the VIH solution with SAP Invoice Management by Open Text in SAP ERP and integrations to

Read Soft INVOICES


Account payables

• SAP Invoice Management by Open Text: For the proposed VIH solution, SAP Invoice Management (SAP IM) by Open Text (also referred to as OpenText Vendor Invoice Management (VIM)) is the selected software which will be deployed in SAP ERP. SAP Invoice Management is a packaged solution delvered by SAP as a Solution Extension, which means that SAP is providing support and maintenance in the same way as for any other SAP product. SAP IM is an add-on to SAP ERP and use SAP technology like ABAP, workflow and SAP Net Weaver Portal.


Account payables• EDI Invoices: In the existing solution, both FI (temporary) and MM invoices are received via EDI. FI invoices (XML) are routed via ReadSoft which is the

perferred solution. Credit notes are also received via EDI. There is a special solution for EDI invoices from Grid vendors for finding FO numbers for Power and Net. There is also special solution for EDI invoices for the POs originating from the Trade (new channel web shop). The file with POs from the WEB shop is uploaded in SAP ERP and the original external PO number is stored in the Sales person for the corresponding SAP PO. The invoice IDoc will contain the external web shop so a look-up is required in order to determine the SAP PO number to be used when posting the invoice.

• Return Invoice to Vendor: There can be situations where the invoice received from the vendor contain incorrect information e.g incorrect company name. In such cases, it might be difficult for the business (or, the operating group such as AP, PSS etc.) to process the invoice further. Hence, the invoice should be returned back to the vendor requesting missing/rectified information.

Return Invoice to vendor

AP Proce

ssor

Phase

Invoice Scanning

Delete VIM document in

OpenText

Manual sorting (A)

Enter reason code for deletion

Send Invoice back with front page with reason

code info

Reason codes:- Wrong company

name



Accounts Receivables

• Accounting Groups• Number Range for Customer group• Define Document types• Tolerance groups for Customers• Dunning



Revenue flow

SAP ERP

EDWm

FT

P

SURF

ARIEL

AJAX

A D I Clearinghouse

Te

liaS

on

era

Fire

wa

ll

FT

P

FT

P

FT

P

SAP BI AE

SAP BI

Cognos


Revenue flow Denmark– BILLING ( Invoice) AND AR FLOWs

SAP

AE / BI

FI

STD AR

CO-PAERP

EDW-M

AXAPTACONTRACT

BILLINGINVOICES

AXAPTACBP

AXAPTACONTRACT

BILLINGDEFERRALS

PREPAIDNOBILL

via EDW-M

HELENAPREPAIDCALL ME

CUSTOMERS

BRUCEBROADBAND IP SERVICES AR

DK12

DK12

DEFERRALSINVOICE

BALANCE

FOKUSMOBILITY

DK12DK15

ARDK12

GENEVABROADBAND

”FIXED” AR

DK12

INTERNALCUSTOMERS

MEGADISCBILLING

CIBERNETROAMING

CSCICBP

SITECONTRACT

BILLING

INCTVCDR

BILLING

MULTIBELLABROADBAND

AR

NOT IMPLEMENTED YET

SURF


ACCRUALS Data Flow

SAP

AE / BI

FI

STD AR

CO-PAERP

EDW-M

TS DKMANUAL PROCESS

AXAPTACBP

BRUCEBROADBAND IP SERVICES

FOKUSMOBILITY

DK12DK15

GENEVABROADBAND

”FIXED”

FOKUS/FSS RA

MANUAL PROCESS

BALANCE postings

MULTIBELLABROADBAND

NOT IMPLEMENTED YET

SURF


COGS FLOW

SAP

AE / BI

FI

STD AR

CO-PAERP

EDW-M

TDC EDI

WEBI MOBILE

VOLUMESDK12DK15

DK15

DK12

TS DKMANUAL PROCESS

ONLY VOLUMES SENT TO BI ARE IMPLEMENTED.

PLANNED TO BE AN AUTOMATIC

FLOW THAT CREATES STANDARD COSTS

IN SAP

HELENA MOBILE

VOLUMESDK12

ONLY VOLUMES SENT TO BI ARE IMPLEMENTED.

PLANNED TO BE AN AUTOMATIC

FLOW THAT CREATES STANDARD COSTS

IN SAP

SURF


Asset Accounting

• Chart of Depreciation• Assign input tax indicator for non taxable acquisitions• Dep Areas & FSv per Co.code• Multy level Methods for Denmark• Period Controls for DK• DEP KEYS• Validations in Asset• Substitutions in Asset• Account Determinations

CompanyDK12

CompanyDK15

CompanyDK21

CompanyDK07

CompanyDK05

CompanyDK02

CHART Depreciation DK00



Workflows

• VIH Denmark Procurement Shared Service for DK21 NPO AP Processor for DK21 Coder for DK21 PO AP Processor for DK21 Procurement Shared Service for DK02 NPO AP Processor for DK02 Coder for DK02 PO AP Processor for DK02 Procurement Shared Service for DK07 NPO AP Processor for DK07 Coder for DK07 PO AP Processor for DK07 Procurement Shared Service for DK12 NPO AP Processor for DK12 Coder for DK12 PO AP Processor for DK12 Procurement Shared Service for DK15 NPO AP Processor for DK15 Coder for DK15 PO AP Processor for DK15

• Workflows for GL Postings Approval Groups for G/L Postings DK21 - Sergel A/S G/L Doc Approvals DK21 Parked G/L Document

Complete parked document Release Amount G/L Document

DK12 - T Nättj Norden AB, DK G/L Appr DK12 Parked G/L Document


DK15 - DLG-debitel I/S G/L Appr DK15 Parked G/L Document


DK02 - Teliasonera Denmark A/S G/L Appr DK02 Parked G/L Document


DK07 - Tilts Communication A/S G/L Appr DK07 Parked G/L Document

Complete parked document Release Amount G/L Document Microsoft Excel

Worksheet


Functional Modules & Programs

• Functional Module for determining Interest rates.• Functional Modules in Accrual Engine.• Payment medium Functional Module.• List of programs for DK12• List of programs for DK12• List of programs for DK21



Inter Company transactions

• Define EDI setting for incoming invoice• T076S table update• Define conversion external Tax codes• T076M table Update• T076I table updates• T076K table updates



Master Data

• GL Masters• Vendor master• Customer Master• Asset master• Cost center• Profit center• GRU’s• Internal Orders• VIM Approvers• Bank Master record



Controlling

Company CodeDK12

Company CodeDK15

Company CodeDK21

Company CodeDK07

Company CodeDK05

Company CodeDK02

Controlling Area 1000


Interfaces

• BEA• EMU• EDW-M


BEAInbound Outbound

Legacy System (BEA)

eCenter

PI

ERP (TSP)

File with GL posting data along

with Credit Agreement id is being created.

Start

File being sent to eCenter and

received.

CFSI5222

File received at PI and being processed.

eCenter picks the file and places at PI

(designated path).

Message Type: ACC_DOCUMENTBasic Type: ACC_DOCUMENT03Message Variant: BEADirectory: /TSG_prd/SIP/R3/BEA/in/ACC/data

Idoc generated.

Idoc success: Y Idoc success: N

GL document posted. Confirmation Idoc

generated.

Acknowledgement message generated.

Ack/Conf file received at BEA.

Message Type: ZALEAUDBasic Type: ZALEAUD02Message Variant: BEADirectory: /TSG_prd/SIP/R3/BEA/out/ACC_Conf/data

File received at eCenter.

Directory: /TSG_prd/SIP/R3/BEA/out/ACC_Ack/data

Confirmation file generated.

1. FBL3n Report generated.

2. .csv file created.

Job: ZCA_RBDSTATE

Job: Z_FI_SPOOL_APPDirectory: /TSG_prd/CFS/R3/Webi/out/BEA/data

CFSI4670

Report received at BEA.

EndFile

corrected for idoc failure.


Process DescriptionCFSI5222

1. File with GL posting data along with Credit Agreement id (CA id) is being prepared & sent by vendor (BEA).

2. File sent to eCenter. eCenter sends the file to PI and place at designated path.

3. PI validates the data and sends an acknowledgement back to BEA via eCenter. PI processes the file.

4. Idoc is generated. • If idoc is successful (status 53)

-> GL accounting document being posted in ERP (TSP).

-> Confirmation idoc generated.• If failure (status 51)

-> Confirmation idoc generated.

5. Confirmation idoc gets generated through an automated background job.

6. Confirmation file being generated at PI.

7. PI sends the file to eCenter.

8. eCenter sends it back to BEA.

9. If confirmation idoc is received for idoc failure, BEA corrects the file and sends a new file to ERP via eCenter & PI.

CFSI4670

10. FBL3n report being generated in ERP through an automated background job which runs daily. .csv file gets generated and placed in a designated path.

11. eCenter picks the file from the path.

12. eCenter sends the report to BEA for their daily reconciliation.


Key PointsCFSI5222:

Inbound file:

Message Type: ACC_DOCUMENT

Basic Type: ACC_DOCUMENT03

Message Variant: BEA

Directory: /TSG_prd/SIP/R3/BEA/in/ACC/data

Outbound file (Confirmation message):

Job: ZCA_RBDSTATE

Message Type: ZALEAUD

Basic Type: ZALEAUD02

Message Variant: BEA

Directory: /TSG_prd/SIP/R3/BEA/out/ACC_Conf/data

Outbound file (Acknowledgement message):

Directory: /TSG_prd/SIP/R3/BEA/out/ACC_Ack/data

CFSI4670:

Outbound file to WebiEngine:

Job: Z_FI_SPOOL_APP

Directory: /TSG_prd/CFS/R3/Webi/out/BEA/data


Inbound

Legacy System (EMU)

Clearing House

PI System

ERP (TSP)

EMU

File with Vendor Invoice data is being created.Start

File being sent to Clearing House and

received.

Clearing House picks up the file and places at PI designated path.


Message Type: ACC_DOCUMENTBasic Type: ACC_DOCUMENT02Message Variant: EMUDirectory: /TSG_prd/CFS/R3/EMU/in/ACC_DOCUMENT02/data/

IDOC Generated.

Vendor Invoice Posted.

IDOC Success: Y

IDOC Success: N

Rectify the errors in IDOC and reprocess the same.

End

CFSI3017


EMU Process DescriptionCFSI30171. File with Vendor Invoice data is being created and sent by Legacy system(EMU). 2. File sent to Clearing house. Clearing House sends the file to PI and place at designated path.3. PI validates the data and processes the file.4. IDoc is generated.

• If IDoc is successful (status 53) -> Vendor invoice being posted in ERP (TSP).

• If failure (status 51) -> Rectify the idoc errors and reprocess the same in BD87.-> if idoc status is 53,vendor Invoice being posted in ERP (TSP)

-> if the total file is wrong, users need to ask EMU to resend the file after rectifying the errors.5. EMU corrects the file and sends a new file to ERP via Clearing House & PI.


Key Points - EMUCFSI3017:Inbound file:Message Type: ACC_DOCUMENTBasic Type: ACC_DOCUMENT02Message Variant: EMUDirectory: /TSG_prd/CFS/R3/EMU/in/ACC_DOCUMENT02/data/


Inbound

Legacy System (EDW-M)

Clearing House

PI System

ERP (TSP)

EDW-M

File with GL posting and revenue posting data is being created.Start

File being sent to Clearing House and received.

Clearing House picks up the file and places at PI

designated path.


Message Type: ACC_DOCUMENT Basic Type: ACC_DOCUMENT02Message Variant: BIR, 1B, 1BC, MEG, RD, RDM, RES, FIM, DKF, DKMDirectory: /TSG_prd/CFS/R3/EDW-M/in/ACC_DOCUMENT02/data/

IDOC Generated

Revenue Posting.

IDOC Success: Y

GL Expense Posting.

Rectify the errors in IDOC and reprocess the same.

IDOC Success: N

End

CFSI3101 (GL posting)CFSI3102 (Revenue posting)

IDOC Success: Y


EDW-M Process DescriptionCFSI3101 (GL Posting)1. File with GL posting data is being created and sent by Legacy system EDW-M. 2. File sent to Clearing house. Clearing House sends the file to PI and place at designated path.3. PI validates the data and processes the file.4. IDoc is generated.

• If IDoc is successful (status 53) -> GL document being posted in ERP (TSP).

• If failure (status 51) -> Rectify the idoc errors and reprocess the same in BD87.-> If idoc status is 53, GL documenrt being posted in ERP (TSP)-> If the total file is wrong, we have to ask EDW-M to resend the file after rectifying the errors.

5. EDW-M corrects the file and sends a new file to ERP via Clearing House & PI.

CFSI3102 (Revuenue Posting)6. File with revuenue posting data is being created and sent by Legacy system EDW-M. 7. File sent to Clearing house. Clearing House sends the file to PI and place at designated path.8. PI validates the data and processes the file.9. IDoc is generated.

• If IDoc is successful (status 53) -> Revenue document being posted in ERP (TSP).

• If failure (status 51) -> Rectify the idoc errors and reprocess the same in BD87.-> If idoc status is 53, vendor Invoice being posted in ERP (TSP)-> If the total file is wrong, we have to ask EDW-M to resend the file after rectifying the errors.

5. EDW-M corrects the file and sends a new file to ERP via Clearing House & PI.


Key Points EDM-W CFSI3101:Inbound file:Message Type: ACC_DOCUMENTBasic Type: ACC_DOCUMENT02Message Variant: BIR, 1B, 1BC, MEG, RD, RDM, RES, FIM, DKF, DKM Directory: /TSG_prd/CFS/R3/EDW-M/in/ACC_DOCUMENT02/data/

CFSI3102:Inbound file:Message Type: ACC_DOCUMENTBasic Type: ACC_DOCUMENT02Message Variant: BIR, 1B, 1BC, MEG, RD, RDM, RES, FIM, DKF, DKM Directory: /TSG_prd/CFS/R3/EDW-M/in/ACC_DOCUMENT02/data/

enterprise structure.pptx

Documents

rights reservedcopyright

sap erp

sap invoice management

sap technology

sap product

sap net weaver portal

existing solution

packaged solution