Issue

Decision is required as the when to deploy the new S4\HANA In-House-Bank.

Recommendation

Background & Context

The existing IHB within ECC resides in PI1, within the legal entities SSA and SFA.   Interfaces are current in place to link PF1 and WP1 to the IHB in PI1. 

All entities are mandated to participate in the IHB process, except where it's not legally possible.  For example, China, x ,x ,x , is not part of the IHB due to legal restrictions.

A high level of complexity exists with IHB largely due to the internal factoring process. Internal factoring brings benefits in the way of cash concentration and tax savings.

Internal factoring is not a common process and not supported by standard SAP, hence the current solution is supported by nemerous complex custom developements.  To "to-be" design will aim to streamline and simplify, hwever it is epected that some level of custom delopments will still be required. 

Cash movements related to payments and receipts is a higher risk area of any ERP implementation. The internal factoring complexity increases the risk.

Assumptions

IHB and internal factoring will continue in S4HANA.

Constraints

Nil 

Impacts

Depending on the approach,  interfaces from S4HANA to PI1 need to be considered. If they are required, the existing interfaces from PF1 \ WP1 will need to be replicated for S4HANA.

Business Rules

Participation in the IHB will continue to be mandatory unless not legally supported.

Options considered

Early deployment of IHB was considered, however  due to its impact on extending the overall ERP project imeline, and also requiring early 

Option A: (Overall Deployment = "Phased" OR "All-in-one") Defer the deployment of IHB until after all GBUs/entities are live. 

Option B: (Overall ERP Deployment = "Phased") Deploy IHB for live GBUs/entities in-line with the Phased Releases.

This option entails running two IHBs.  One IHB in PI1 for entites still on ECC,  and a second IHB for GBUs\entities that have S4HANA for transitioned to S4HANA.

This allow

Option C: (Overall ERP Deployment = "Phased") Deploy IHB for live GBUs/entities in the second Release with the Phased Releases.

Option D: 

(Overall ERP Deployment = "All-in one") Deploy IHB for live GBUs/entities in line with th all-in-one go-live.

Evaluation

	Option A	Option B	Option C	Option D	Option A	Option B	Option C	Option C
Lowest Risk	PI1 will be available to as a contigency should there be significants issues with the S4HANA IHB.	PI1 will not be a possible fall back.    Phased transitioned will less entities go-live in first phase is a lower risk. if there is a significtn issue, it will only impact the entities which have transitioned to S4HANA.	PI1 will be available to as a contigency should there be significants issues with the S4HANA IHB.  (only for Release 1 entities)	PI1 will not be a possible fall back.	High	Medium	High	Low
Complexity Level  (Higher complexity due to interim interfaces)	Requires interfaces to be built for integration with S4HANA. Interfaces are required for all GBUs\Enttites.	New interfaces are not required.	New interfaces are required for GBUs\Entities transitioning in Release 1.	New interfaces are not required.	Low	High	Low	High
Cost	With the go-live of IHB deferred, relevant resources will be required for an extended period.	No additional project costs.	No additional project costs.	No additional project costs.	Low	High	High	High
Ability to run Productions Simulations	Production simulation possible, for all entities, which contributes to lowering the risk.	Unable to excute production simulations prior to go-live.	Production simulation possible, for Release 1 entities,  which contributes to lowering the risk.	Unable to excute production simulations prior to go-live.	High	Low	High	Low
Ease of Consolidation	Consolidation of the entities on PI1 will require an interim solution.	Consolidation of the entities on PI1 will require an interim solution.	Consolidation of the entities on PI1 will require an interim solution.	No impact on consolidation.	Low	Low	Low	High
Cut-over impact (less payments outages).	One payment outage as only one cut-over is required.	Two payment outages to manage.	One payment outage as only one cut-over is required.	One payment outage as only one cut-over is required.	High	Low	High	High
Business resource impact	No additional\adverse impact on business resources	Additional resourcs likely required to run two IHBs.  Business resources will likely need to perform manual clearing payment sub-ledgers.	No additional\adverse impact on business resources	No additional\adverse impact on business resources	High	Low	High	High
Stabilisation on integrated process (Sales\Accounts Receivable, Payments\Accounts Payables)	Integrated processes will have had time to stabilise.	No additional time for integrated process to stabilise, and higher probability of integration issues.	Integrated processes will have had time to stabilise, (for GBUs\Entities from Release 1).	No additional time for integrated process to stabilise, and higher probability of integration issues.	High	Low	High	Low

See also

Change log

Workflow history