| Status | |
| Owner | RUFFINONI, Francois |
| Stakeholders |
Vertex O Series software is used by the current SAP ECCs systems and will still be required for SyWay. The current solution runs on AWS as IaaS, but Vertex also delivers an "On-Demand" SaaS version of the tool. This KDD aims at deciding which hosting solution would suit SyWay the best, with additional reference to some extra tools that could help with a smoother implementation and a better user experience.
This KDD does NOT include the Vertex Tax Returns tool.
The recommendation goes for the option B --> Vertex On-Demand (i.e SaaS) solution. It will lower the internal workload without compromising on any features. Plus we recommend using the additional extra toolsets provided by Vertex in the form of the Vertex Plus Tools and the Vertex SAP Accelerator.
Both those tools will also simplify the integration between S/4 and Vertex and reduce the workload, while enhancing the user experience.
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.
Other critical updates are issued by VERTEX and are applied when requested by the Syensqo USA Tax Department. Reporting functionality is provided, as are tax return filing capabilities.
Vertex On-Demand might require additional licences
The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order".
Option A: IaaS/On-Premise solution
This is the current solution used by the ECCs systems.
It is made of a 3-tier landscape (DEV+TEST+PROD). Vertex application requires a Database as a Service, a Windows server to execute the application, and the SIC component to interface with SAP backend systems.
Syensqo technical teams must apply every month the update of jurisdiction codes, which requires synchronization between technical teams and application teams.
Backup/Restore policies, High Availability and DRPs are designed by Syensqo teams (today there is no high availability on premise for the application itself, it relies on AWS EC2 availability).
Syensqo teams can configure the application, load certificates of exemptions, etc, in the Vertex web access
Access is user/pwd based.
Licensing is based on company revenues.

Vertex On-Demand solution is offered as a SaaS.
Vertex takes care of the monthly updates and service releases.
High availability, DRP, backups/restore are managed by Vertex .
Syensqo teams can configure the application, load certificates of exemptions, in the Vertex web access. It offers the same features as the On-Premise version.
Vertex SIC component must be installed on a Syensqo server to communicate between O Series and S/4.
SSO can be integrated.
Licensing element will be confirmed together with Procurement team

Cons
Cons

Option A | Option B | |
|---|---|---|
| Vertex O Series features and UX |
|
|
| Installation and configuration |
|
|
| Regular maintenance |
|
|
| Infrastructure footprint, HA, DRP... |
|
|
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
