Issue

Decision is required as the when to deploy the SAP In-House-Bank.

Recommendation

Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.

Background & Context

The existing IHB within ECC resides in PI1, within the legal entities SSA and ????.   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

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

Participation in the IHB will continue to 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: Option Title

Describe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option B: Option Title

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	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con 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.

Change log

Workflow history