Skip to Content
avatar image
Former Member

How to architect two S4 instances

What architectural options are there for potentially maintaining an S4 instance for the central finance of your business and one for the rest of the company?

Let’s just say for the sake of argument we maintained corporate finance in S4 (With the Shared services functions and MGL for CORP financeetc) but for our main operational ERP Consolidation we enabled a new client of S4 for the Best practice build?

Is this something that is even workable? And if so how would you maintain communication between the two.

How would that look and how easy would it be for the two systems to talk to each other?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Feb 13, 2018 at 10:31 AM

    Hi Milton,

    this could very well be a genuine scenario but to me this might negate the basic value proposition of simplification, single data source and data footprint reductions being promised by S4. The architecture depends on the hosting options of the instances but essentially these might boil down to using SLT and EDI based integration techniques.

    AM not very sure on the SLT because the use case is always mentioned as ERP to S/4 HANA central finance and hence the conversion and mappings on SLT might be based in ECC to S4 use case only. Enabling EDI will take us back to costly maintenance overheads and might not work because of business rules embedded within the processing layer. Looking at the information available online, SLT would be a better bet. Hope this helps...

    Add comment
    10|10000 characters needed characters exceeded