| Status | |
| Owner | RUFFINONI, Francois |
| Stakeholders |
Issue
Vertex O Series software is used by the current ECCs systems and will still be required for SyWay. The current solution runs on AWS as IasS but Vertex also delivers a on-demand SaaS version of the tool. This KDD aims at deciding which hosting solution would suit best SyWay. We also add a part remated to some etxra tools delivering a smoother implementation.
Recommendation
The recommendation goes for the 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.
Background & Context
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 SAP 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.
Assumptions
Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited.
Constraints
Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.
Impacts
Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.
Business Rules
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".
Options considered
Option A: IaaS/OnPremise 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, an Windows server ton execute the application and the SIC component to interface with SAP backend systems .
Syensqo technical teams must apply every months the update to the jurisdiction code, it 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 onpremise for the application itself, it relies on AWS EC2 availability)
Syensqo teams can configure the application, loads certificates of exemptions... in the Vertex web access
Access is user/pwd based.
Option B: Vertex On Demand (SaaS)
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option C: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Option D: Option Title
Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly
Evaluation
Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |
See also
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.
