confidential

Sequans – Glob‘Sys Project

Multi-company issues

Wolfgang Schaefer Project Manager – FS EMEA 2 + 3

May 2009

© SAP 2008 / Page 2 confidential

Sequans OM Structure

Sequans Communication

Sequans UK

Sequans France

Sequans US

Central Teamfor all countries

UK Team

Processes and Responsibility

Sequans runs FIN, CRM, SRM, SCM, HCM and PRO. Not all processes are required in all countries France is the headquarter. The central team coordinates all processes across all countries, i. e.

French employees need to access all data and create transactions for all companies. France includes a Purchasing Organisation and a Sales Organisation

US is a small company. The processes are fully managed by the team in France. US includes a Sales Organisation

UK employees may access data (transactions and reports) only for UK, e. g. Finance or SRM. UK includes a Sales Organisation

© SAP 2008 / Page 3 confidential

Sequans CRM Scenario

Pain Points

Relevant Processes

Sales Quote Sales Order Customer Invoice

Determination of responsible sales unit in manual invoice not flexible enough -> high risk of postings to wrong company

Search helps: System lists all data independent from context and responsibility, e. g. customers, partners, etc.

Users can access to all account and product master data. Access control for all objects (incl. Master data objects) required.

Use cases

All sales orders are managed by France, i. e. all customers are assigned to sales unit of Sequans France, manual invoices for customers are also required.

Sequans US and UK don’t manage sales orders. There is manual customer invoices from US and UK used only for intercompany sales to France. Invoices are created by French employees

A further country will go live at the end of 2009 which will manage CRM processes similar to France, i. e. sales orders

Access control for customer data (master data, prices, transaction data) should be definable by customer/employee

Sales Representative (French) creates Sales Quote/Sales Order/Manual Invoice for France using a foreign customer. System should determine the responsible Sales Unit and employee

Sales Representative can view documents, master data, transaction data and reports only for customer which are defined in access control

Sales Employee can select only print forms defined for the relevant company respectively sales unit

© SAP 2008 / Page 4 confidential

Account Master Data

Access control on company or sales unit level missing for Account, Partner & Contact data. (Display/Change)

Access control must apply also to details in account, e. g. prices by sales unit. (Display/Change)

© SAP 2008 / Page 5 confidential

Product Master Data

Access control must apply also to details in product, e. g. prices by sales unit. (Display)

Access control on company or sales unit level missing for Material & Service data. (Display/Change)

© SAP 2008 / Page 6 confidential

Account Search Helps

Acess control for accounts on company or sales unit level missing in search helps. Only relevant accounts should be visible

© SAP 2008 / Page 7 confidential

Product/Service Search Helps

Access control for material/service on company or sales unit level missing in search helps. Only relevant products should be visible

© SAP 2008 / Page 8 confidential

Involved Parties Determination

More flexible definition of determination by process required. E. g. User creates objects for various sales units -> Determination could be based on customer data

© SAP 2008 / Page 9 confidential

Reporting

Reports and search helps for variables in reports have to respect access control on company/sales unit level.

© SAP 2008 / Page 10 confidential

Sequans SRM Scenario

Pain Points

Relevant Processes

Shopping cart Purchase Request / Order Goods and services receipt Supplier Invoice

Determination of responsible purchase unit in manual invoice not flexible enough -> high risk of postings to wrong company

Search helps: System lists all data independent from context and responsibility, e. g. suppliers

Users can access to all supplier and product master data. Access control for all objects (incl. Master data objects) required

Country specific scoping

Use cases

purchase orders for multiple companies are managed by employees in France, manual invoices for suppliers are also required.

Access control for supplier data (master data, transaction data) should be definable by supplier/employee

Purchase responsible (French) creates Purchase Order/Manual Invoice for US using a foreign supplier. Neither no purchase unit determination or based on flexible rule

Purchase responsible can view documents, master data, transaction data and reports only for suppliers which are defined in access control

Purchase responsible can select only print forms defined for the relevant company respectively purchase unit

Employees can only see self-services which are relevant, e. g. shopping cart might not be used in all countries

Multi-step approval for shopping cart by different management levels

© SAP 2008 / Page 11 confidential

Supplier Master Data

Access control on company or purchasing unit level missing for Suppliers & Service Agent data. (Display/Change)

Access control must apply also to details in supplier, e. g. bank and payment data. (Display/Change)

© SAP 2008 / Page 12 confidential

Product Master Data

Access control on company or purchasing unit level missing for Material & Service data. (Display/Change)

© SAP 2008 / Page 13 confidential

Supplier Search Helps

Acess control for suppliers on company or purchasing unit level missing in search helps. Only relevant suppliers should be visible

© SAP 2008 / Page 14 confidential

Product/Service Search Helps

Access control for material/service on company or purchasing unit level missing in search helps. Only relevant products should be visible

© SAP 2008 / Page 15 confidential

Involved Parties Determination

More flexible definition of determination by process required. E. g. User creates objects for various purchasing units -> Current rules are not sufficient

© SAP 2008 / Page 16 confidential

Sequans FIN Scenario

Pain Points

Relevant Processes

General Ledger Payables Receivables Payment Management Fixed Assets

Search help lists all available master data for all companies, e. g. all cost centers in the system

Search help is not pre-filled based on dependent master data, e. g. manual posting in General Ledger: all cost centers listed although company was pre-selected

Use cases

Finance for all countries except UK is managed by French employees User wants to see only the master data for the US company when

working with the US data, e. g. based on SOBs or company

© SAP 2008 / Page 17 confidential

FIN General Ledger - defaulting

SOBs should be defaulted based on company since only one SOBs exists

© SAP 2008 / Page 18 confidential

FIN General Ledger – dependent value help

Value help lists all costs centers from all companies although the company was already defined. Same for profit centers and project tasks

Value help lists all costs centers from all companies although the company was already defined. Same for profit centers and project tasks

© SAP 2008 / Page 19 confidential

FIN Reporting – variable defaulting and dependencies

Value help lists all costs centers from all companies although the company was already defined. Same for profit centers and project tasks

Variables should be defaulted if only one value exists, e. g. SOBs, currency, Chart of Accounts, etc. Only allowed combinations should be available in value help, e. g. SOBs