You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Status

  Approved

Owner
Stakeholders
LeanIX Link

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 regionCloser to S/4 for performance reason
SSO setupEnhance 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


Network Architecture

System Landscape

System Access

Application Security

Authentication

Authorisation

Communication Security

Data Security

Other Controls


Operation Architecture

Change and Configuration Management

Monitoring

Sizing

High Availability & Disaster Recovery

Backup/Restore

Maintenance Plan


Exceptions


See also

No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 3) Mar 18, 2026 08:37 RUFFINONI, Francois
v. 46 Mar 11, 2026 09:36 WENNINGER-ext, Sascha
v. 45 Mar 04, 2026 10:05 RUFFINONI, Francois
v. 44 Mar 04, 2026 10:02 WENNINGER-ext, Sascha
v. 43 Mar 04, 2026 09:48 WENNINGER-ext, Sascha
v. 42 Mar 04, 2026 09:42 WENNINGER-ext, Sascha
v. 41 Mar 04, 2026 08:22 RUFFINONI, Francois
v. 40 Mar 04, 2026 08:21 RUFFINONI, Francois
v. 39 Mar 04, 2026 08:21 RUFFINONI, Francois
v. 38 Feb 24, 2026 08:39 RUFFINONI, Francois

Go to Page History

  • No labels