Status
Owner	RUFFINONI, Francois CABELLO MARTOS-ext, Gabino
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name
LeanIX Link	Insert the name of the LeanIX Application Factsheet and hyperlink to the factsheet.

Introduction

Scope & Objectives

This document aims at describing the overall architecture of Vertex application in the SyWay context.

As per KDD093, SyWay will run Vertex Cloud solution (SaaS).

It is connected to S/4 RoW instance.

Key Decisions and Requirements

Description	Rationale
Vertex Cloud runs in EU region	Closer to S/4 for performance reason
SSO setup	Enhance security

Terminology

VERTEX is an external software used by Syensqo to calculate taxes on customer and vendor invoices for US and Canadian legal entities. Tax Rules are customized by legal entities in VERTEX, based on Syensqo's Sales and Procurement processes. The tax rules customized in VERTEX are based on directions from the Syensqo USA Tax Department. Tax Jurisdiction Codes linked to the Country/State or Province/County/City/Postal Code are assigned to US and Canadian Customer and Vendor master data in SAP. Tax jurisdiction codes also are assigned to company codes, shipping points, and storage locations for the US and CA.

When a sales order, customer invoice/credit memo, purchase order, or vendor invoice/credit memo are processed in SAP, there is a Remote Function Call (RFC) from SAP to VERTEX to determine taxability of the transaction based on the customization. If the transaction is determined to be taxable, the tax rate is determined by the tax jurisdiction code specified on the customer, vendor, or plant/delivery address master record.

VERTEX issues monthly updates for tax rule changes, tax jurisdiction code changes, and tax rate changes. These monthly updates are applied to the VERTEX development, quality, and production servers to ensure tax calculations are correct.

Vertex Cloud is connected to its respective S/4 system through a component named SIC (SAP Interface Component).

Application Architecture

Overview

Application Architecture Components

Provide the details of each and every major component used in the Application Architecture. Below are some of the sample application components provided as a reference.

Network Architecture

Optional Section if application requires a network design.

System Landscape

Describe the landscape. For example DEV, QAS, PRD. Create subsection for each tier if required.

System Access

Describe how systems will be access by the different end-users.

List down all URL and access details.

Application Security

Authentication

Provide the details of authentication architecture used for the application

Authorisation

Provide the authorization guidelines/principles followed for the application

Communication Security

Provide the details of the communication security controls implemented based on the classification

Data Security

Provide the details of the data security controls implemented based on the classification

Other Controls

Provide the details of any other controls implemented based on the classification

Operation Architecture

Change and Configuration Management

This section will include the details related to change and configuration management of SAP and non-SAP systems.

Monitoring

This section will include the details related to monitoring enabled for the application (System and Application monitoring)

Sizing

Provide the details of sizing approach and the future recommendations

High Availability & Disaster Recovery

Provide the details of HA and DR. List down related metrics like RPO/RTO and availability SLA.

Backup/Restore

Provide the details of Backup/Restore. You may provide a reference to other document or attach a document, if the section contains lot of content

Maintenance Plan

Provide the details of system and application maintenance plan. This should follow the upgrade strategy

Exceptions

This section covers any exceptions to the reference architecture. Some Applications may have limitations and may not meet the Enterprise Architecture, Reference Architecture and IT Policy guidelines. All exceptions should be included in this section.