| Status | |
| Owner | Antonio Zappone |
| Stakeholders | The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name |
Issue
Treasury was recently approved to be part of the SyWay project scope. A decision is now required as to when to deploy Treasury activities, whether in Group 1, Group 2, or after Group 2 with the In-House Bank deployment.
Recommendation: Option F: Deploy; Treasury (TRM & CM) with Group 2, IHB in Group 2, Syensqo SA in Group 2
Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.
Background & Context
DD075 - Future system to support Treasury activities
CR0003 - Transition Treasury from Quantum to S/4HANA
The above KDD and Change Request were approved to bring Treasury activities into the scope of the SyWay project,
A decision in now required as to when the deploy the Treasury modules within the SyWay deployment Groups. There are currently two official deployment groups, Group 1 and Group 2.
Relevant Treasury Modules in S/4HANA
- Treasury Risk Management (TRM)
- Cash Management (CM)
Assumptions
SyWay deployment for Release 4 will be execute in two groups, Group 1 & Group 2. Multiple group go-lives adds significant complexity in regards to Treasury deployment.
Constraints
Existing Quantum License expires 14th June 2028.
Impacts
KDD070 - Deployment Approach for In-House Bank (IHB)
Extract from KDD070
Option E: Defer the deployment of In-House Bank functionality for all GBUs and Entities until after the second group go-live.
This Conceptual Design recommendation will be re-assessed during Detailed Design when more information will be available to support a decision. Options B, C, and E will form part of the reassessment. Any long lasting impacts on S/4HANA from the legacy interim IHB requirements will also be considered at this time.
Impact
Treasury and In-House bank and heavily integrated, as such the deployment timing of the In-House Bank comes into consideration.
For the purpose of this KDD, IHB go-live will be referred to as Group 3. Note: there is no official Group 3
Entity 2002 Syensqo SA (ECC Company code 2002)
Local Statutory Reporting for this entity is performed in 2002 \ PF2.
Treasury
This holds the accounting for both Treasury and the In House Bank.
Accounting entries from the PI2 system are interfaced into 2002 in PF2 to produce statutory accounts, and also interfaced to BFC from PF2 Group Consolidation.
Non- Treasury
Relevant non Treasury Activities also occurs in this entity, including Head Office activities and Intercompany service billing which 1) receives charges from other entities 2) send invoices to WP2.
SyWay will introduce a new process for Intercompany Service Billing. This process will receive input from other Syensqo entities, and will also need to send Invoices. This process will also have the complexity of multiple systems in the interim (between Group 1 and Group 2 Go-Lives).
Impact
The current system design for this entity adds complexity to the deployment approach for Treasury, which is one part of the Syensqo SA entity.
Analysis conducted for this KDD highlights that it is easier (less interim interfaces) to deploy entity Sysensqo SA with the rest of Treasury and IHB.
Go-Live Timing
Entity 2002 Syensqo SA resides in PF2 and hence is currently scheduled to go-live with Group 1.
The Go_-Live timing decision for the Sysensqo SA entity will be decided post this KDD. Should Sysensqo Go-Live in Group 1, recommended option moves to Option F. Option F still recommends Treasury going live in Group 2. The difference between Option E & F, is when the sysensqo entity goes live, and the increased number of interim interfaces.
Systems
Quantum: is the current Treasury systems
PI2: The treasury accounting and also the IHB reside in this separate system. The company codes is this system are 2232 & 4044.
PF2: The legal entity for Treasury and IHB is Syensqo SA, and this entity resides in PF1. The relevant company code in this system is 2002. Local Statutory reporting is performed from this entity\system.
WP2: For Treasury exposure management, the non IHB exposures for the entities within WP2 are required.
BFC: for Consolidation purposes, Syensqo SA (2002), send packages to BFC for Consolidation
Business Rules
There are no relevant business rules at this point in time.
Options considered
The main deployment consideration is Treasury TRM & CM.
However the decision requires consideration of
a) go-live timing of IHB
b) go-live timing of the Syensqo SA entity.
The below table represents the go-live timing.
Options Summary
| Activity to Deploy | Option A | Option B | Option C | Option D | Option E | Option F | Option G |
|---|---|---|---|---|---|---|---|
| Treasury (TRM & CM) | Group 1 | Group 1 | Group 2 | Group 2 | Group 3 | Group 3 | Group 3 |
| IHB | Group 3 | Group 3 | Group 3 | Group 3 | Group 2 | Group 2 | Group 3 |
| Entity Syensqo SA (2002) | Group 1 | Group 2 | Group 1 | Group 2 | Group 1 | Group 2 | Group 1 |
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.
| Criteria | Option A | Option B | Option C | Option D | Option E | Option F | Option G |
|---|---|---|---|---|---|---|---|
Treasury: Group 1 | Treasury: Group 1 | Treasury: Group 2 | Treasury: Group 2 | Treasury: Group 2 | Treasury: Group 2 | Treasury: Group 3 | |
IHB: Group 3 | IHB: Group 3 | IHB: Group 3 | IHB: Group 3 | IHB: Group 2 | IHB: Group 2 | IHB: Group 3 | |
Syensqo SA: Group 1 | Syensqo SA: Group 2 | Syensqo SA: Group 1 | Syensqo SA: Group 2 | Syensqo SA: Group 1 | Syensqo SA: Group 2 | Syensqo SA: Group 1 | |
| Ease of integration of Cash Management (CM) |
|
|
|
|
|
|
|
| Rating | Low | Low | Medium | Medium | High | High | High |
|
|
|
|
|
|
| |
| Efficient Management of IHB Exposures | IHB/PI2 goes live in Group 3
|  As Option A |
|
| IHB and TRM go-live in S4 together.
|
|
|
| Rating | Low | Low | Low | Low | High | High | High |
|
|
|
|
|
|
| |
| Efficient Management non-IHB Exposures |
| As Option A |
| As Option C | As Option C | |
|
| Rating | Medium | Medium | Medium | Medium | Medium | Medium | Low |
Ease of Accounting for Treasury Deals (from Header Entity) |
|
|
|
|
|
|
|
| Rating | High | Low | Medium | High | Medium | High | Medium |
| Ease of Accounting for IHB entities (2232 & 4044). |
|
|
|
|
|
| As Option E |
| Rating | Low | High | Low | High | Low | High | Low |
| Ability and ease to implement and manage Intercompany Loans |
| As Option A |
| As Option C |
|
|  As Option E |
| Rating | Low | Low | Medium | Medium | High | High | High |
| Ability and ease to perform Treasury transactions outside of central Treasury Entity | TRM goes live in Group 1.
|
| TRM goes live in Group 2.
Existing Process with Deal in Quantum to continue in the interim period. | As Option C | As Option C | As Option C |
|
| Rating | Low | Low | Medium | Medium | Medium | Medium | Medium |
| Ease of Cut-over at implementation |
|
|
|
|
|
|
|
| Rating | Medium | Medium | Medium | Medium | High | High | Low |
SUMMARY | High x 1 Medium x 2 Low x 5 | High x 1 Medium x 2 Low x 5 | High x 0 Medium x 6 Low x 2 | High x 2 Medium x 5 Low x 1 | High x 4 Medium x 3 Low x 1 | High x 6 Medium x 2 Low x 0 | High x 3 Medium x 2 Low x 3 |
| OVERALL RATING | Low | Low | Medium | Medium | Medium | High | Medium |
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.
