SAP S4 Hana - Integration

Configuration Guide | PUBLIC
Document Version: 2.5 – 2023-06-07
Configuration Guide IS-H - SAP S/4HANA

Integration
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Find Relevant SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 High Level Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Useful BC Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4 Keep Customizing and Master Data Synchronized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3 Logical Systems and RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4 Customizing IS-H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1 Define Connected Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 Assign Systems to Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 Define Default Values for FI Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4 Display the FI Customer Number of the Insurance Provider in the SAP Business Partner. . . . . . . . . . 19
4.5 Post Fees in Transaction NWCH97_API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.6 Define Special Function Module for Presetting FI Data for Self-Payer. . . . . . . . . . . . . . . . . . . . . . . . 20
4.7 Adaption of Customer-Specific Formatting Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5 Customizing SD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1 Output Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Create New Distribution Model (Client-Dependent). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Create Port in IDoc Processing for Transactional RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Edit Partner Profile for Logical Receiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Generate Partner Profile for new Distribution Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Distribute Model View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 Define Institution-Specific Control Parameters (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
5.3 Source Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Implement BAdI ISH_ERP_FI_INVOICE2ACC_OUT (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . 26
Implement BAdI ISH_ERP_FI_TECH_CALL (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.4 Control Unavailability of SAP S/4HANA (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.5 Application Log (SAP ERP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6 Customizing SAP S/4HANA Financial Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6.1 Inbound Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Define Inbound Processing Code for ACC_DOCUMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Configuration Guide IS-H - SAP S/4HANA Integration

2 PUBLIC Content
Edit Partner Profile for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.2 Enabling System Standard Inbound Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Activate BAdI Implementation ISH_ERP_FI_LOCAL_ACC_DOC_ISHIA. . . . . . . . . . . . . . . . . . . . .29
6.3 Enabling Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Configure Master Data Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
6.4 Source Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Implement BAdI ISH_ERP_FI_INVOICE2ACC_IN (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.5 Application Log (SAP S/4HANA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.6 Electronic Dunning Notice (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Trusted RFC Connection from SAP S/4HANA to SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
BTE Customizing in SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Customizing for Callback to SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
User Authorization for SAP ERP RFC Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7 User Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.1 User Authorization for SAP S/4HANA RFC Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.2 Authorization Control for SAP S/4HANA IS-H Patients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9 Implications on Business Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

9.1 Functional Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10 Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
10.1 Prevent Transfer of Invoices to FI System in SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
10.2 Check Customer-Specific Function Modules for Document Text. . . . . . . . . . . . . . . . . . . . . . . . . . . 40
10.3 FI Posting Status in Invoice Overview and Case-Specific Settlement. . . . . . . . . . . . . . . . . . . . . . . . 40
10.4 Copy Reversal Reason for FI Documents to SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
10.5 Check Requirements Before Invoice Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.6 Replacement for the User Exits in the Financials Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
10.7 Set Default Value for Base Unit of Measure for FI Documents to SAP S/4HANA. . . . . . . . . . . . . . . . 42
10.8 Classification of IS-H-Only Users in IS-H and SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
11 Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
11.1 Overview and General Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Transition Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Simplification Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Project System Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Impact on Master Data and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Impact on Cutover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Impact on Data Migration Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Custom Code Adaption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
11.2 Technical Considerations and Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Content PUBLIC 3
Number Ranges for FI Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Stronger Consistency Checks in SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Specific Hints for Master Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

4 PUBLIC Content
1 Document History
This section provides details about the changes made in each version of this document.
 Note
This document is updated regularly. Make sure that you are using the latest version of this
document, which you can access on SAP Help Portal at https://help.sap.com/viewer/product/
SAP_FOR_HEALTHCARE/.
 Note
Version 2.0, or higher refers to the new posting interface ACC_DOCUMENT (instead of INVOIC). The
configuration of the previous posting interface is described in the version 1.5 of this guide assigned to
previous support packages. For information on how you can switch from INVOIC to ACC_DOCUMENT, see
SAP Note 3147855 .
Document History
Document Version Date Important Changes
2.5 June, 7th 2023 Updated section:
About This Guide [page 10]
2.4 March, 8th 2023 New section:
Specific Hints for Master Data Migra

tion [page 48]
2.3 November, 30th 2022 Updated sections:
• About This Guide [page 10]

• User Authorization for SAP
S/4HANA RFC Function Modules
[page 34]
• FI Posting Status in Invoice Over
view and Case-Specific Settlement
[page 40]
New section:
Classification of IS-H-Only Users in IS-H

and SAP S/4HANA [page 43]

Document History PUBLIC 5
2.2 September, 8th 2022 Updated sections:
• Edit Output Determination for Bill

ing Documents
• Functional Restrictions [page 38]
New section:
Implement BAdI
ISH_ERP_FI_TECH_CALL (Optional)
[page 27]
2.1 June, 9th 2022 Updated sections:

• Useful BC Sets [page 12]
• Keep Customizing and Master
Data Synchronized [page 13]
• Assign Systems to Applications
[page 17]
• Define Institution-Specific Control
Parameters (Optional) [page 26]
• Implement BAdI ISH_ERP_FI_IN
VOICE2ACC_OUT (Optional) [page
26]
• Impact on Data Migration Activities
[page 46]
• Stronger Consistency Checks in
SAP S/4HANA [page 48]
New sections:
• Control Unavailability of SAP

S/4HANA (Optional) [page 27]
• Application Log (SAP ERP) [page
27]
• Application Log (SAP S/4HANA)
[page 31]
• Electronic Dunning Notice (Op
tional) [page 31]

6 PUBLIC Document History
2.0 March, 9th 2022 Updated sections:

• Find Relevant SAP Notes [page
11]
• Useful BC Sets [page 12]
• Keep Customizing and Master
Data Synchronized [page 13]
• Logical Systems and RFC Destina
tions [page 15]
• Create New Distribution Model
(Client-Dependent) [page 22]
• Edit Partner Profile for Logical Re
ceiver [page 24]
• Edit Partner Profile for Logical
Sender [page 29]
• Copy Reversal Reason for FI Docu
ments to SAP S/4HANA [page
41]
• Replacement for the User Exits in
the Financials Interface [page 42]
New sections:
• Define Institution-Specific Control

Parameters (Optional) [page 26]
VOICE2ACC_OUT (Optional) [page
26]
• Define Inbound Processing Code
for ACC_DOCUMENT [page 29]
• Activate BAdI Imple
mentation ISH_ERP_FI_LO
CAL_ACC_DOC_ISHIA [page 29]
VOICE2ACC_IN (Optional) [page
30]
• Set Default Value for Base Unit of
Measure for FI Documents to SAP
S/4HANA [page 42]

1.5 November, 30th 2021 Updated sections:
• Logical Systems and RFC Destina

tions [page 15]
• Define Special Function Module for
Presetting FI Data for Self-Payer
[page 20]
• Adaption of Customer-Specific
Formatting Routines [page 20]
•
• User Authorization [page 34]
• Implications on Business Proc
esses [page 37]
• Best Practices [page 40]
New sections:
• Adaption of Customer-Specific
Formatting Routines [page 20]
• Authorization Control for SAP
S/4HANA IS-H Patients [page
35]
• Migration [page 44]
1.4 September, 09th 2021 Updated section:
Functional Restrictions [page 38]
New section:
Find Relevant SAP Notes [page 11]
1.3 March, 10th 2021 Updated sections:
• Useful BC Sets [page 12] (also

renamed from Switch BC Sets)
New section:
Define Special Function Module for Pre

setting FI Data for Self-Payer [page
20]

8 PUBLIC Document History
1.2 November, 25th 2020 Updated section:
Define Connected Systems [page 16]
New sections:
• Implications on Business Proc

esses [page 37]
• Best Practices [page 40]
1.1 September, 4th 2020 Updated sections:

• Define Default Values for FI Cus
tomers [page 18]
• Edit Output Determination for Bill
ing Documents (also renamed from
Create Condition for Billing Type
“Cancel Invoice”)
• Create Supplier Master (General
Section) for Logical Sender
• Replacement for the User Exits in
the Financials Interface [page 42]
New section:
Activate BAdI Implementation

ISH_ERP_FI_LOCAL_ACC_DOC_BKPFF
1.0 November, 29th 2017 First Version

2 Introduction
2.1 Getting Started
This Configuration Guide contains instructions on how to configure a two-system scenario that comprises
a local IS-H system (SAP Patient Management as part of ERP) and the Financial Accounting and Logistics
components of SAP S/4HANA.
This scenario enables you to access the functionalities of an on-premise SAP S/4HANA system from your
existing IS-H system.
2.1.1 About This Guide
 Note
Version 2.0, or higher refers to the new posting interface ACC_DOCUMENT (instead of INVOIC). The
configuration of the previous posting interface is described in the version 1.5 of this guide assigned to
previous support packages. For information on how you can switch from INVOIC to ACC_DOCUMENT, see
SAP Note 3147855 .
Validity:
This guide is valid as of:
• IS-H 617 SP 043 (SAP ERP 6.0, Industry Extension Healthcare, SAP Enhancement Package 7, Support
Package 043)
• IS-H 618 SP 032 (SAP ERP 6.0, Industry Extension Healthcare, SAP Enhancement Package 8, Support
Package 032)
• SAP S/4HANA 1709 SPS12
• SAP S/4HANA 2022 FPS01
 Note
Inform yourself about the availability of the listed SAP S/4HANA versions. For more information,
see the SAP Support Portal at https://support.sap.com/en/release-upgrade-maintenance/maintenance-
information/schedules-for-maintenance-deliveries.html under Schedules for Support Package Stack.

10 PUBLIC Introduction
System Requirements:
For information about dependencies and release combinations of SAP ERP and SAP S/4HANA, see SAP Note
3282721 .
Abbreviations:
ERP system components:
• CO: Controlling
• FI: Financial Accounting
• MM: Materials Management
• SD: Sales and Distribution
2.1.2 Find Relevant SAP Notes
Context
To find the SAP Notes related to the IS-H – SAP S/4HANA integration, do the following:
Procedure
1. Go to SAP Support Portal and access the expert search.

2. You can find SAP Notes for the IS-H - SAP S/4HANA integration under the component IS-H-CM-S4 as of
2022.
For previous SAP Notes, enter the following:
• Search Term: IS-H: S/4HANA Integration

• Fuzzy Threshold: Exact Match (1.0)
• Components (Start with): IS-H
3. Execute the search.
2.2 High Level Architecture
In this side-by-side scenario, two partner systems are integrated in a way that users of an IS-H system can
access the functionalities of an on-premise SAP S/4HANA system.

Introduction PUBLIC 11
High Level Architecture IS-H - SAP S/4HANA Integration
IS-H is part of your local SAP Business Suite. In this side-by-side scenario, IS-H continues to connect to all
clinical systems that you have connected.
IS-H does not access the FI/CO/MM components of your local ERP system any more. Instead, IS-H now
connects to the remote SAP S/4HANA Financial Accounting and Logistics components.
The only local ERP component that IS-H still accesses is SD. To create invoices, IS-H accesses SD to push
IDocs to the remote SAP S/4HANA Financial Accounting.
2.3 Useful BC Sets
SAP provides predefined BC Sets for the IS-H – SAP S/4HANA integration. You can use these Customizing
entries to simplify the activation of the integration. Depending on your implementation approach and system
landscape, you need to decide whether you want to use these settings. SAP delivers configuration through
Switch BC Sets or regular BC Sets.
In the IS-H system:
• You can use the Switch BC Sets ISH_V_TN01_V (IS-H: Institutions) and ISH_TN02A_S (IS-H: Define Appl.
and Their Asgmt to a System) to create an example institution and activate the SAP S/4HANA integration
for this institution.
• You can use the Switch BC Set ISH_ERP_FI_VEDI_EDPV1_V (IS-H: ERP-IF Fin: Proposal for outbound
Partner profiles) to simplify the creation of the distribution model. For information about how to activate
the Switch BC Set, see SAP Note 3017401 .
• You must use the Switch BC Set ISH_ERP_FI_BAL (IS-H ERP-IF Fin: Application Log Configuration) to
create Customizing entries to enable the application log for the IS-H – SAP S/4HANA integration.
• You can use the Switch BC Set ISH_ERP_FI_C_S4_CTL (IS-H ERP-IF Fin: Controlling of S/4HANA
unavailability) to initialize the Customizing for SAP S/4HANA unavailability checks.

In the SAP S/4HANA system:
• You must activate the client-independent BC Set ISH_ERP_FI_LOCAL_BCSET_ISHIA (IS-H: ERP-IF Fin
local: BC-Set Invoice to Accounting) to create client-independent entries for the handling of the new posting
interface ACC_DOCUMENT and the client-specific BC Set ISH_ERP_FI_LOCAL_BCSET_ISHIA_CS (IS-H:
ERP-IF Fin local: BC-Set Invoice to Accounting Client) to create client-specific entries for the handling of the
new posting interface ACC_DOCUMENT.
• You can use the BC Set ISH_ERP_FI_LOCAL_BCSET_SAMPLES (IS-H: ERP-IF Fin local: BC-Set Entry
Samples ) to create sample entries for the inbound configuration.
• You must activate the client-independent BC Set ISH_ERP_FI_LOCAL_BAL (IS-H ERP-IF Fin local BC-Set:
Application Log Configuration) to create Customizing entries to enable the application log for the IS-H –
SAP S/4HANA integration.
2.4 Keep Customizing and Master Data Synchronized
Both the local IS-H system and the Financial Accounting and Logistics components in the remote SAP
S/4HANA system use Customizing and Master Data.
 Caution
Ensure that all FI/MM/CO settings and master data that you use in IS-H Customizing tables must remain
synchronous. It is the task of the customer to determine and realize the synchronization requirements
according to the processes used. You must also check your own programs and partner products created
after the activation of the IS-H - SAP S/4HANA integration to see whether they can deal with a distributed
system and then adapt them if necessary.
In particular pay attention to the following:
• Customizing
• company codes
• chart of accounts
• posting keys
• document types
• controlling areas
• Periodic settings
• Period closing (transaction FAGL_EHP4_T001B_COFI) and period lock CO (transaction OKP1) need to
be done in SAP ERP and SAP S/4HANA in parallel. For more information, see SAP Note 3141205 .
• If you handle foreign currencies, you must keep the currency rates in SAP ERP and SAP S/4HANA
identical (table TCURR: Exchange Rates). We recommend that you run transaction RFIMPECB
(report Upload Exchange Rates from ECB) regularly and simultaneously in both systems. For more
information, see the report documentation and SAP Note 3195481 .
• Master Data
• G/L account
• order
• material

Introduction PUBLIC 13
• cost center

3 Logical Systems and RFC Destinations
In both IS-H and SAP S/4HANA, you need a logical system each for the system itself and the respective target
system. (That means, altogether you need four logical systems.) However, you need only one RFC connection
from IS-H to SAP S/4HANA. All entries are client independent.
To set up the logical system and the RFC connection, do the following:
• To create new logical systems, execute transaction code BD54 (Maintaining Logical Systems). In both
IS-H and SAP S/4HANA, create one logical system for the system itself and one logical system for the
respective partner system.
If entries already exist, you can use those, or you can still create new ones.
• To create, in IS-H, a trusted connection to SAP S/4HANA, execute transaction code SM59 (RFC
Destinations (Display/Maintain).
The SAP system expects you to set up a Trusted RFC connection. This requires that the IS-H users who use
functions in SAP S/4HANA (for example, when they change address data of the SAP S/4HANA customer
by changing the address data of the patient) also have an appropriate SAP user of type Dialog with
sufficient authorizations in SAP S/4HANA. The existence of individual SAP users in SAP S/4HANA simplify
meeting several requirements, for example, of the data protection and privacy and also of the auditability.
• To assign an RFC destination for synchronous method calls, execute transaction code BD97 (Assign RFC
dest. to Logical Systems).
• In IS-H, assign the RFC ABAP destination of SAP S/4HANA to the logical system of that SAP S/4HANA
system as Standard RFC destination for BAPI calls.
• In SAP S/4HANA, assign the RFC ABAP destination of IS-H to the logical system of this IS-H system as
special method destination for object type ACCDocument and method Display.

Logical Systems and RFC Destinations PUBLIC 15
4 Customizing IS-H
IS-H uses a framework to support various accessing types (so called “Events”) to read or update FI/CO/MM
application data on SAP S/4HANA system for the requested institution.
To integrate the SAP S/4HANA system into this framework, go to the Customizing activity SAP Healthcare
– Industry-Specific Components for Hospitals Basic Settings Configuration / Systems / Events and make
the settings described in the following topics.
4.1 Define Connected Systems
To define the connected systems and characteristics, execute transaction code ONK6 (IS-HCM: Maintain
System Attributes) and do the following:
1. Create a new entry for the SAP S/4HANA system with type SAP S/4HANA System.
2. Select External System.
3. Enter the RFC destination of the SAP S/4HANA system (client independent).
You can simply copy the sample entries for the system REMOTES4.

16 PUBLIC Customizing IS-H
Define Connected Systems
4.2 Assign Systems to Applications
To assign an institution and the applications CO, FI, and MM, to the system, execute transaction code ONK1
(ISH: Assign Application to System).
 Caution
You have to assign an institution for every client and institution separately.
Only an activation of all institutions in one client is supported. This means that you can't integrate one
institution with SAP S/4HANA and another one with local SAP ERP in the same client.
You can use the sample entries for the institution BSS4 and the system REMOTES4.

Customizing IS-H PUBLIC 17
Assign Systems to Applications
4.3 Define Default Values for FI Customers
This activity is a prerequisite for the business partner groupings that are required for the creation of the
business partners of the FI customers by the SAP S/4HANA system.
 Note
The following minimum versions are required for this activity:
• IS-H 617 Support Package 34 or IS-H 618 Support Package 19

• SAP S/4HANA 1709 Support Package 5
For lower versions, you can implement the following SAP Notes:
• 2792476 IS-H: S/4HANA integration - IS-H components - overriding a business partner grouping
• 2792478 IS-H: S/4HANA integration - S/4 components - business partner grouping
1. In the IS-H system, go to the Customizing activity SAP Healthcare – Industry-Specific Components for
Hospitals Patient Accounting FI Customers Preset Values for FI Customers .
2. For the business partner groupings that are required for creating the business partner of the FI customers,
specify the following parameters instead of the account groups:
• KOGR_SZ
Business partner grouping for self-payers and copayers
• KOGR_FR
Business partner grouping for third-party payers
• KOGR KTR
Business partner grouping for insurance providers
 Recommendation
We generally recommend that the business partner number and the customer number are derived from
the respective objects in IS-H (patient number, insurance provider number). Therefore, you must configure
the number range assignment for the relevant business partner groupings and account groups in SAP
S/4HANA as external. For the insurance provider, this configuration is mandatory.

4.4 Display the FI Customer Number of the Insurance
Provider in the SAP Business Partner
Context
If you use the SAP Business Partner in the IS-H system, you have to make the following client-depending
settings to display the number of the FI customer in the SAP S/4HANA system as the customer number.
Procedure
1. Open transaction BUS3.

2. Double-click on CVIC21 to open the view Customer: Customer Number (CVIC21).
3. In the section Function Module, change the value of the Before Output field, from CVIC_BUPA_PBO_CVIC21
to NCUS_BUPA_PBO_CVIC21.
4. Save your settings.
4.5 Post Fees in Transaction NWCH97_API
Use the Post Fees (API) transaction (NWCH97_API) to update fees, since this transaction posts the data to the
correct SAP S/4HANA system using an API interface. Do not use the Post Fees transaction (NWCH97), since it
only posts data to the local ERP system.
For more information, see the documentation for the Post Fees (API) transaction.

4.6 Define Special Function Module for Presetting FI Data
for Self-Payer
Prerequisites
You have implemented one of the following options:
• IS-H 618 SP 025

• IS-H 617 SP 036
• SAP Note 3018947
Context
This activity improves the existing transfer of specific data from IS-H to allocate an FI customer in SAP S/
4HANA (especially separate first and last name).
 Note
If you have special requirements how to fill the fields of the FI customer master (business partner) in SAP
S/4HANA, you can replace the function module for presetting FI customer data with your own function
module during implementation.
Procedure
1. In the IS-H system, go to the Customizing activity SAP Healthcare – Industry-Specific Components for
Hospitals Patient Accounting FI Customers Define Function Modules for Presetting FI Data .
2. For the relevant institutions, replace the value of the parameter KNA1_SZ from ISH_FILL_KNA1_SZ_DEBI
to ISH_ERP_FI_FILL_KNA1_SZ_DEBI.
4.7 Adaption of Customer-Specific Formatting Routines
IS-H provides the feature to use customer-specific routines to transfer individual content to text fields of FI
documents. This affects the following Customizing views:
• V_TN22R (Copayment)

• V_TN22Q (Copayment request)
• V_TN22S (Down payment request)
• V_TN22P (Down payment)
 Example
When you insert the name of a customer-specific routine (for example, ZZ_POSTING_STRING into the
field V_TN22P-TXTAP) you can transfer specific content into the field BSEG-SGTXT of down payment
documents.
In the context of the SAP S/4HANA integration, you need to adapt these function modules to the requirements
of the SAP S/4HANA integration (for example, provide remote access).

5 Customizing SD
IS-H also uses the existing infrastructure to determine if the current Institution uses Financial Accounting on
SAP S/4HANA.
In this case, IS-H does not call local posting for invoice or reversal, but uses SD Output Control for synchronous
processing. It creates and sends Invoice IDocs to the remote SAP S/4HANA Financial Accounting component.
5.1 Output Handling
5.1.1 Create New Distribution Model (Client-Dependent)
 Caution
If you want to create a new distribution model, log on to the system with language EN (English). The sample
text of the tables are available in English only.
To create a new distribution model, execute transaction code BD64 (Maintenance of Distribution Model) and do
the following:
1. Switch to edit mode.

2. 2. Go to Menu Edit Model View Create using Template .
3. Select the template REMOTES4 and choose Continue.
4. On the first screen of the dialog window, choose Continue.
5. On the second screen of the dialog window, enter the following:
Field Entry
Model View -> Technical name System name from access infrastructure for remote S/4 (see Define
Connected Systems [page 16])
Partner -> Sender Name of the logical system of the IS-H system
Partner -> Receiver Name of the logical system of the SAP S/4HANA system
Choose Continue.
6. On the next screen of the dialog window, choose Complete

7. On the main screen, choose Save.
After you completed these steps, the screen may look like this:

22 PUBLIC Customizing SD
Create New Distribution Model
 Note
Message type INVOIC is only defined here for compatibility reasons. You can delete it, if you want.
5.1.2 Create Port in IDoc Processing for Transactional RFC
Execute transaction code WE21 (Port definition) and do the following:
1. In the folder Transactional RFC, check if a port has already been for the RFC destination of the S/4 system.
• If there is already a port, exit the transaction.
• If there is no port yet, continue.
2. Choose Create and do one of the following:
• Enter a port name.
• Let the system generate a port name.
3. Fill in the following fields:
• Description: Enter a short description, for example "Integration of IS-H with Remote S/4 Financial
Accounting".
• Version: Choose IDoc record types SAP Releases 4.x.
• RFC Destination: Enter the name of the S/4 system that is the destination of the RFC.

Customizing SD PUBLIC 23
Create Port in IDoc Processing for Transactional RFC
5.1.3 Edit Partner Profile for Logical Receiver
To edit the partner profile for the logical receiver, execute transaction code WE20 (Partner Profiles) and do the
following:
1. In the folder Partner Type LS, choose Fast Data Entry ( ) and fill in the following fields:
• Partner No.
Enter the name of the logical system of the SAP S/4HANA system.
• Partner Type
Enter LS.
Choose Continue.
2. Only in the line with message type ACC_DOCUMENT, enter the name of the SAP S/4HANA system in the
field Port. Choose Continue.
3. Check that the outbound parameters match the values from Create Port in IDoc Processing for
Transactional RFC. If necessary, change the outbound parameters.
4. Copy the outbound parameter with partner role LS and message type ACC_DOCUMENT:
1. Select the assigned line and choose Copy outbound parameter.
1. Clear field Partner Role.
2. Select tab Message Control, choose Insert row, and enter the following:
• Application: V3
• Message type: RD00
• Processing code: ISH_INVOICE2ACC_OUT
2. Choose Save.

5.1.4 Generate Partner Profile for new Distribution Model
To generate a partner profile for a new distribution model, execute transaction code BD82 (Generate Partner
Profiles) and enter the name of the new model view and execute the report.
Generate Partner Profile for new Distribution Model
5.1.5 Distribute Model View
To distribute a new model view, execute transaction code BD64 (Maintenance of Distribution Model) and do the
following:
1. Choose New Model and choose in the menu Edit Model View Distribute .
2. Check that the logical system of the receiver is correct. Choose Continue.
Distribute Model View

5.2 Define Institution-Specific Control Parameters
(Optional)
This optional activity is available in Customizing under SAP Healthcare - Industry-Specific Components
for Hospitals Basic Settings Configuration / Systems / Events SAP S/4HANA Connection Define
Institution-Specific Control Parameters .
In this Customizing activity, you can edit parameters that are relevant for the IS-H - SAP S/4HANA integration.
The values are institution-specific.
If you activate the Credit Memo option, you can transfer credit memos instead of invoice reversals. This applies
to the following reversals:
• Reversals of non-migrated invoices

• Reversals of invoices with closed posting periods
• Reversals of invoices according to your own definition
To do this, you must implement method REVERSAL_VS_CREDIT_MEMO of BAdI
ISH_ERP_FI_INVOICE2ACC_OUT.
For more information, see the Customizing documentation.
5.3 Source Enhancements
5.3.1 Implement BAdI ISH_ERP_FI_INVOICE2ACC_OUT

(Optional)
This optional activity is available in Customizing under SAP Healthcare - Industry-Specific Components for
Hospitals Basic Settings Configuration / Systems / Events SAP S/4HANA Connection Business Add-Ins
BAdI: BAPI IDoc “Invoice to Accounting" Outbound .
With the Business Add-In IS-H: ERP-IF Fin - BAPI IDoc "Invoice to Accounting" Outbound, you can change data
of invoices and cancellation of invoices in the IS-H system before it is transferred to your financial accounting
system.
If you have activated the Credit Memo option in the Customizing activitiy Define Institution-Specific Control
Parameters (see Define Institution-Specific Control Parameters (Optional) [page 26]), you can define with the
REVERSAL_VS_CREDIT_MEMO method your own criteria when an invoice reversal is to be transferred as a
credit memo to FI in the SAP S/4HANA system.
For more information, see the BAdI documentation.

5.3.2 Implement BAdI ISH_ERP_FI_TECH_CALL (Optional)
Hospitals Basic Settings Configuration / Systems / Events SAP S/4HANA Connection Business Add-Ins
BAdI: Define Technical RFC Calls to SAP S/4HANA .
With the Business Add-In IS-H ERP-IF Fin - Technical RFC Calls, you can change the RFC destination for calls to
SAP S/4HANA.
For more information, see the BAdI documentation and SAP Note 3222250 .
5.4 Control Unavailability of SAP S/4HANA (Optional)
You can use a customizable SAP S/4HANA availability check for certain IS-H reports, transactions, and EDI
procedures. You can configure that the system checks the SAP S/4HANA system availability when accessing a
report or a transaction. The system can then issue a message with a configurable message type (for example,
“Error”) to the user if SAP S/4HANA isn't available.
The Customizing is activated by the Switch BC Set ISH_ERP_FI_C_S4_CTL (IS-H ERP-IF Fin: Controlling of
S/4HANA unavailability).
Hospitals Basic Settings Configuration / Systems / Events SAP S/4HANA Connection Control for S/4
Connection Issues .
In this Customizing activity, you change the entries or create your own entries, specifically for customer-
specific reports in case they support this check.
For more information, see the Customizing documentation and SAP Note 3204364 .
5.5 Application Log (SAP ERP)
You can use an application log in the SAP ERP system to log invoice transfers and erroneous RFC function
module calls.
The application log is activated by the Switch BC Set ISH_ERP_FI_BAL (IS-H ERP-IF Fin: Application Log
Configuration).
For analyzing, you can use the following transactions:
• Standard transaction SLG1 (object ISH_ERP_FI, subobjects IDOC and RFC)

• Specific transactions N_ERP_FI_LOG_IDOC_O (Logs - Invoice Transfer Outbound) and
N_ERP_FI_LOG_RFC_O (Logs - Function Calls Outbound)

You must regularly reorganize the log using transaction SLG2. The log entries for the IS-H - SAP S/4HANA
integration are configured with a lifetime of 10 days by default.
The activation of the application log is required to execute the retransfer or reposting of invoices and
cancellations.

6 Customizing SAP S/4HANA Financial
Accounting
6.1 Inbound Handling
6.1.1 Define Inbound Processing Code for ACC_DOCUMENT
To define the inbound processing code for the posting interface ACC_DOCUMENT, execute transaction code
SCPR20 (Activate BC Sets) for the BC Set ISH_ERP_FI_LOCAL_BCSET_ISHIA (IS-H: ERP-IF Fin local: BC-Set
Invoice to Accounting) in the independent client and for the BC Set ISH_ERP_FI_LOCAL_BCSET_ISHIA_CS
(IS-H: ERP-IF Fin local: BC-Set Invoice to Accounting Client) in the specific client.
6.1.2 Edit Partner Profile for Logical Sender
To edit the partner profile for the logical receiver, execute transaction code WE20 (Partner Profiles) and do the
following:
1. In the folder Partner Type LS, choose Fast Data Entry ( ) and fill in the following fields:
• Partner No.: Enter the name of the logical system of the IS-H system.
• Partner Type: Enter LS.
• Direction: Select Inbox.
Choose Continue.
2. Select the line with the message type ACC_DOCUMENT. Choose Continue.
6.2 Enabling System Standard Inbound Processing
6.2.1 Activate BAdI Implementation

ISH_ERP_FI_LOCAL_ACC_DOC_ISHIA
When you use the processes down payments, copayments, or partial payments, you must activate the
Business Add-In (BAdI) implementation ISH_ERP_FI_LOCAL_ACC_DOC_ISHIA.

Customizing SAP S/4HANA Financial Accounting PUBLIC 29
To activate this BAdI implementation, execute transaction code SE19 (Business Add-Ins: Implementations) and
do the following:
1. Enter enhancement implementation EI_ERP_FI_LOCAL_ACCOUNTING, and choose Display.

2. Activate the BAdI implementation ISH_ERP_FI_LOCAL_ACC_DOC_ISHIA.
The system displays a confirmation message and the runtime behavior is set to “Execution depends on
runtime filter values”.
6.3 Enabling Business Partner
6.3.1 Configure Master Data Synchronization
If you create a new customer in SAP S/4HANA, the system creates for each customer a business partner with
the roles Customer and FI Customer (for company code data). You must ensure that the system also generates
classic customer master data.
To generate customer master data in SAP S/4HANA, execute transaction code SM30 (Call View Maintenance)
and do the following:
1. In field Table/View enter MDSV_CTRL_OPT_A.

2. Choose Maintain.
3. Select the customizing activity Cross-Application Components Master Data Synchronization
Synchronization Control Synchronization Control Activate Synchronization Options
4. Check the Act. Incl. box for the following target objects:
• CUSTOMER
• VENDOR
6.4 Source Enhancements
6.4.1 Implement BAdI ISH_ERP_FI_INVOICE2ACC_IN

(Optional)
With the Business Add-In IS-H: ERP-IF Fin - BAPI IDoc "Invoice to Accounting" Inbound, you can process
received invoices and cancellation of invoices from an IS-H system in your financial accounting system.
For more information, see the BAdI documentation.
To create an implementation of this BAdI, execute transaction code SE19 (Business Add-Ins: Implementations)
and do the following:
1. Enter enhancement spot ES_ISH_ERP_FI_INVOICE2ACC_IN and choose Create.

30 PUBLIC Customizing SAP S/4HANA Financial Accounting
2. Enter the name of the new enhancement implementation, a short text, and choose Enter.
3. Enter the name of the new BAdI implementation and the new implementation class, choose BAdI definition
ISH_ERP_FI_INVOICE2ACC_IN, and choose Enter.
4. Implement the BAdI methods IF_EX_ERP_FI_INVOICE2ACC_IN~CHANGE_IDOC_BEFORE_POSTING and
IF_EX_ERP_FI_INVOICE2ACC_IN~PROCESS_IDOC_AFTER_POSTING and choose Activate.
6.5 Application Log (SAP S/4HANA)
You can use an application log in the SAP S/4HANA system for the IS-H - SAP S/4HANA integration to log
invoice transfers and erroneous RFC function module calls.
You activate the application log in the SAP S/4HANA system using transaction SCPR20 (Activate BC Sets) for
the BC Set ISH_ERP_FI_LOCAL_BAL (IS-H ERP-IF Fin local BC-Set: Application Log Configuration).
For analyzing, you can use the following transactions:
• Standard transaction SLG1 (object ISH_ERP_FI, subobjects IDOC and RFC)

• Specific transactions N_ERP_FI_LOG_IDOC_I (Logs - Invoice Transfer Inbound) and
N_ERP_FI_LOG_RFC_I (Logs - Function Calls Inbound)
You must regularly reorganize the log using transaction SLG2. The log entries for the IS-H - SAP S/4HANA
integration are configured with a lifetime of 10 days by default.
6.6 Electronic Dunning Notice (Optional)
You can use a standardized electronic dunning notice for the IS-H - SAP S/4HANA integration and an
implemented version for the following communication procedures:
• §301 for the local version Germany

• MEDIDATA 4.0 for the local version Switzerland
Depending on the required communication procedures, dunning notices must be transmitted electronically to
insurance companies or public authorities.
Typically, this communication is realized by technical tools residing in IS-H (EDI framework) in the SAP ERP
system. Data and process trigger are also located in the SAP ERP system.
Dunning (or payments) processes run in the SAP S/4HANA system. To trigger the relevant dunning notice in
IS-H, the dunning run in SAP S/4HANA (transaction F150) must inform the communication tool in the SAP
ERP system using the interface.
You can find the required components in the following.

6.6.1 Trusted RFC Connection from SAP S/4HANA to SAP
ERP
To call the RFC function module in the SAP ERP system, you must provide a trusted RFC connection, which you
must assign to the logical system name of the sending SAP ERP system.
6.6.2 BTE Customizing in SAP S/4HANA
Check the following for the BTE Customizing:
• The relevant application in the Business Transaction Event (BTE) is IS-H.

Call transaction BF11 and check whether an entry exists and is active for the application IS-H with the text
“IBU Public Sector – Healthcare”. If not, add this entry.
• The following BTE function modules must be assigned to the events in the BTE framework:
Event Application Function Module
00001720 IS-H ISH_ERP_FI_PS_BTE_00001720
Call transaction BF31 and check whether the required function modules exist there. If not, enter them.
6.6.3 Customizing for Callback to SAP ERP
In the Customizing activity ERP-IF Fin - Basic Settings sending System, you must define the country code and
the callback RFC function module for each combination of logical system name of the sending SAP ERP system
and company code.
To access this Customizing activity, execute transaction SM30 with table TNERP_FI_SRC_CTL and choose
Customizing.
6.6.4 User Authorization for SAP ERP RFC Function Modules
If the SAP S/4HANA system calls the RFC function modules in the SAP ERP system, the calling user ID (online
or batch) requires authorization for the SAP ERP system.

32 PUBLIC Customizing SAP S/4HANA Financial Accounting
To authorize SAP S/4HANA users for the SAP ERP system, do the following:
1. Execute transaction PFCG (Role Maintenance).

2. In the SAP ERP system, add the authorization object S_RFC to the role or profile of each SAP S/4HANA
user group that is to access the SAP ERP system.
3. Select or enter the following attributes:
• Function group N_ERP_FI_PROXY_2
• Activity 16 (Execute)

7 User Authorization
7.1 User Authorization for SAP S/4HANA RFC Function

Modules
If IS-H calls new RFC function modules on the SAP S/4HANA system, the calling user ID (online or batch)
requires authorization for the SAP S/4HANA system.
To authorize IS-H users on the SAP S/4HANA system, execute transaction code PFCG (Role Maintenance) and
do the following:
1. In the SAP S/4HANA system, add the authorization object S_RFC to the role or profile of each IS-H user
group that is to access the SAP S/4HANA system.
2. Select or enter the following attributes:
• Function group N_ERP_FI_LOCAL
• Activity 16 (Execute)
User Authorization
 Note
The IS-H users that don't use functions of SAP S/4HANA beyond the IS-H - SAP S/4HANA integration
don't have to be licensed separately.
For ERP pricing (SAP ERP and SAP S/4HANA), SAP defines the following types of access:
• Direct Human Access

• Indirect/Digital Access
• SAP Application Access
SAP Application Access occurs when humans, or any device or systems indirectly use the SAP's
enterprise resource management system via another licensed SAP application. SAP applications refer
to line of business and industry applications, such as SAP Patient Management (IS-H).

34 PUBLIC User Authorization
Provided ERP is otherwise licensed, SAP Application Access doesn't require additional ERP user
licenses for use resulting from access by properly licensed SAP applications.
For more information, see SAP Digital Access and especially Indirect Access Guide for SAP Installed
Base Customers .
7.2 Authorization Control for SAP S/4HANA IS-H Patients
To protect the personal data of the patient, consider the -PAT authorization group in your authorization
concept (authorization object B_BUPA_GRP). To make sure you can manage the user authorization regarding
business partners, check whether the entry -PAT is available in table TB037 Authorization Groups (transaction
S_AEC_66000257).
For more information about authorization check enablement in the business partner search help, see SAP Note
2441447 .

User Authorization PUBLIC 35
8 Monitoring
To monitor the interaction of IS-H SD and SAP S/4HANA Financial Accounting when posting invoices, do one,
or both, of the following:
• To check for not-sent or erroneous outbound messages from the IS-H system, execute report RSNAST0F
Monitoring for Incorrectly Processed Output.
We recommend that you configure in the IS-H a system workflow for IDoc error handling for outbound
messages.
• To check all sent and received messages, you can execute on either system transaction code BD87 (Status
Monitor for ALE Messages).
If access from IS-H to the configured function modules on SAP S/4HANA fails, you will get a synchronous
response message. Therefore, you do not need to set up a monitor for this.

36 PUBLIC Monitoring
9 Implications on Business Processes
This section lists implications on various business processes that are affected by the IS-H – SAP S/4HANA
integration. These implications can be functional restrictions (for example, due to functions that are no
longer supported in SAP S/4HANA or in the integration scenario), changes, or improvements (for example,
by benefiting from superior SAP S/4HANA capabilities).
Billing
• Display FI/CO documents from an invoice

You can display the FI/CO documents from the SAP S/4HANA system that belong to an invoice from the
invoice overview (transaction NA30N) in the IS-H system. To do this, choose Accounting:
If there is only one document for an invoice, the system displays it.
If there are several documents for an invoice, the system displays a dialog box List of Documents in
Accounting:
• If you select a document number and choose Details, the system displays the document in the same
session.
• If you select a document number and choose Separate, the document is displayed in a new session
directly in the SAP S/4HANA system.
• If you choose Source Document, the system closes the List of Documents in Accounting dialog box.
Prerequisite: You use the same user in the IS-H and SAP S/4HANA systems.
• Cancel IS-H invoices of already cleared FI documents
If you want to be able to cancel invoices in IS-H even if the corresponding FI documents are already
cleared in SAP S/4HANA Financial Accounting, you have to make the following settings in Customizing
under SAP Healthcare – Industry-Specific Components for Hospitals Basic Settings Configuration /
Systems / Events SAP S/4HANA Connection Define Institution-Specific Control Parameters :
Set the Canc. Inv. indicator and specify the Type (document type) and PK (posting key). With this
document type and posting key, the system creates a credit memo in the SAP S/4HANA system during
cancellation of an invoice.
• Posting of a service to a balance sheet account
If a service is posted to a balance sheet account in SAP S/4HANA Financial Accounting during billing, CO
data (cost center, plant, order number) isn't transferred to the SAP S/4HANA system.
Prerequisite: The master data in the IS-H and SAP S/4HANA systems must be the same.
• Prevent manual editing of billing documents of type NF01 and NS01
If you use the IS-H - SAP S/4HANA integration, specific SD standard transactions, such as VF01, VF02,
and VFX3, must not be used for document type NF01 and NS01. You must set the authorization for these
transactions in a way that SD documents created from IS-H can't be edited manually.

Implications on Business Processes PUBLIC 37
9.1 Functional Restrictions
The integration of IS-H and SAP S/4HANA is possible only with the following minor functional restrictions.
• Customizing settings and Master Data that is maintained in IS-H must be replicated and synchronized in
the SAP S/4HANA system.
• While the system processes an insurance relationship or its proposal (transaction codes NV32 (IS-H:
Display insurance relationship) and NV33 (IS-H: Maintain insurance relatshp)), it doesn’t support the
creation of new Bank Master Data.
• From the copayment dialog (transaction code NE11 (Maintain Copayment)), you can’t access the FI
document (transaction code FB03 (Display Document)) by double-clicking the document number of the
copayment request. Instead, some information about the FI document is displayed in a dialog box.
• The planning functionality for cost planning of internal orders (Base objects costing) is replaced by Easy
Cost Planning (no Totals or Arithmetical Operations).
• Suspense accounts (DE: CpD: Conto pro Diverse) accounts for one-time customers aren’t supported.
• The report RNLMAT02 (Ad Hoc Purchasing and Consumption Analysis) isn’t supported.
• Revenues can’t be posted directly to the CO profitability segment in SAP S/4HANA (EN: direct account
assignment, DE: Direktkontierung) when patient billing is executed.
• Maintenance access to Order Master Data not possible (transaction code NCO4 (HCO: Status Monitoring
Case-Bsd Ord)).
• Classification isn’t supported (transaction code NCO7 (HCO: Case-Based Order Classification)).
• Customizing links in messages still point to IS-H system, and not to the SAP S/4HANA system. Therefore,
they can’t be used.
• Report RNMPICK0 (EN: IS-H: Pick List, DE: IS-H: Kommissionierliste) isn’t supported.
• If you use the SAP Business Partner in the IS-H system to maintain IS-H insurance provider master data
(business function ISH_BP_OM):
• The deletion indicator in the “HC customer” role of the insurance provider doesn’t affect the
corresponding SAP S/4HANA business partner and the assigned FI customer master.
• The IS-H BAPIs for the object “HC BusinessPartner” only works locally in the IS-H system and don’t
access data in the SAP S/4HANA system.
• The standard posting status of a billing document (VBRK-RFBSK) is always D or E. So, you can’t see
whether the FI document has been created within the SAP S/4HANA system. Therefore, you can include
additional fields into your invoice overview. For more information, see Best Practices [page 40].
• You can’t set a posting block for SD billing documents created by IS-H, not in the transactions NA30N
(Case-Related Invoice Processing) or NA01 (IS-H: Patient Billing) and also not by configuring the billing type
(V_TVFK-RFBFK = X). The system prevents live billing for those cases.
• Transaction NA04 (IS-H: Release Billing Document into Financial Accounting) isn't supported. If an SD billing
document can’t be posted to SAP S/4HANA, you can use the invoice overview in transaction NA30N (Case-
Related Invoice Processing) to find and correct the root cause. Then you can postprocess accordingly.
• Only relevant for the local version Switzerland: The transfer of electronic dunning notices (DE: e-Mahnung)
requires additional configuration according to the attachment of SAP Note 2844547 .
• The global system parameter DEB_ERR for controlling the behaviour of FI transactions called in the
background is not taken into account.

38 PUBLIC Implications on Business Processes
• During actual settlement of a CO-PA order (transaction code KO88 (Actual Settlement: Order)) system
calls two enhancements COPA0001 and COPA0002. The enhancements need to be implemented in SAP
S/4HANA.
The samples in the IS-H system can’t simply be copied. It’s ok to use them as template, but make sure
that, in SAP S/4HANA, each enhancement implementation accesses IS-H as a remote system.
• During import of bank statement (DE: Kontoauszug) report RFEBKA00 calls enhancement FEB00001. The
enhancement needs to be implemented in the SAP S/4HANA system. The code must access IS-H as a
remote system.
• The enhancement of the material master delivered with IS-H (append structure ISH_MARA_APP, views,
configuration tables), is not available in SAP S/4HANA. To prepare for the required replication of the
material master from the SAP S/4HANA to the SAP ERP system, you need to create this enhancement in
your namespace and consider it in the data migration and in the ongoing master data distribution.
• The IS-H – SAP S/4HANA integration expects that the configuration of the control data for the ISR
procedure (table T049E: Control Data for Swiss ISR Procedure) is maintained in the SAP ERP system.
• You can use messages 116 and 117 of message class N8 to prevent the live billing and cancellation of invoice
documents (see SAP Note 107609 ). These messages do not prevent billing when IS-H works with SAP
S/4HANA.

Implications on Business Processes PUBLIC 39
10 Best Practices
10.1 Prevent Transfer of Invoices to FI System in SAP

S/4HANA
You can prevent an invoice from being transferred to SAP S/4HANA Financial Accounting. For this purpose,
the field ISH_NO_IDOC is available in the table VBRK. You can make a customer-specific setting for this field in
the user exit include RV60AFZC (subroutine userexit_fill_vbrk_vbrp). If you select the indicator (value
X), the system doesn’t post a document in the SAP S/4HANA system. In the Invoice Overview, the invoice is
assigned the FI posting status E (Do not post to FI).
10.2 Check Customer-Specific Function Modules for

Document Text
In Customizing under SAP Healthcare - Industry-Specific Components for Hospitals Patient Accounting
Co-Payment / Down Payment , customer-specific function modules can be configured to set the text in the
resulting FI documents. To ensure that these formatting routines still work correctly, you must check whether
they read any information from (local) FI. If they do so, adapt the formatting routines so that they read the
information from SAP S/4HANA instead.
10.3 FI Posting Status in Invoice Overview and Case-Specific

Settlement
To ensure that the status of the corresponding FI posting in SAP S/4HANA is displayed in the transactions
Case-Related Invoice Processing (NA30N) and Invoice Overview (NA05) in IS-H, add the “FI posting status code”
and the “FI posting status” (as icon) to the ALV field list and remove the standard posting status of a billing
document (VBRK-RFBSK) from the list.
You can activate a more transparent status for data transfer to Financial Accounting in these transactions
(NA30N and NA05). This status also allows you to access the data directly when problems arise. In the Invoice
Overview, you can find the FI posting status as an additional selection criterion. For more information, see the
field help (F1) for the status and the assigned icon.

40 PUBLIC Best Practices
You can use the IDoc Processing transaction (WLF_IDOC) completely for monitoring and postprocessing in
connection with the IDoc invoice interface ACC_DOCUMENT.
To activate FI posting status version 2, select the FS 2 checkbox in Customizing under SAP Healthcare
- Industry-Specific Components for Hospitals Basic Settings Configuration / Systems / Events SAP
S/4HANA Connection Define Institution-Specific Control Parameters . Once you've done this, the system
allows you to access SAP S/4HANA so that you can change IDocs where there's an issue with posting.
Any manual changes made to IDocs within the context of the IS-H - SAP S/4HANA integration are the
responsibility of the customer. Contact your IT auditors to clarify when changes are allowed.
If you want to use this function, you must make the relevant Customizing settings for the IDoc Processing
transaction (WLF_IDOC), for example, which fields are editable, in SAP S/4HANA. You can make these
settings in Customizing under Cross-Application Components IDoc Monitor Specify Settings for IDoc
Maintenance . For more information, see the corresponding Customizing documentation. You should also
perform detailed checks on the effects of a manual change in connection with follow-up activities, for example,
when canceling a changed document.
For more information, see the following SAP Notes:
SAP Notes for SAP ERP:
• 3266868
• 3227580
• 3227578
SAP Note for SAP S/4HANA: 3227611
10.4 Copy Reversal Reason for FI Documents to SAP

S/4HANA
The current situation is as follows:
An invoice was created in SAP ERP and the invoice document was posted successfully to SAP S/4HANA.
However, the invoice has now been reversed in SAP ERP, which means the FI document will also be reversed in
SAP S/4HANA. A reversal reason is required for a reversal document in SAP S/4HANA.
You now have the following options:
• Enter a reversal reason in table T041C in SAP S/4HANA. This will be used as a default value. You
can edit the table in Customizing under Financial Accounting General Ledger Accounting Business
Transactions Adjustment Posting/Reversal Define Reasons for Reversal . The system will search for a
reason where the Alt.pos.dt checkbox is not selected.
Please note that the system only allows reversals if the reversal date is the same as the invoice date.
• Implement method CHANGE_IDOC_BEFORE_SENDING of BAdI ISH_ERP_FI_INVOICE2ACC_OUT in SAP
ERP and use it to determine the reversal reason you require. You will then need to define the reversal
reason determined by the BAdI in SAP S/4HANA (table T041C). For more information, see SAP Note
3101712 .

Best Practices PUBLIC 41
10.5 Check Requirements Before Invoice Creation
The dispatch of IS-H billing document works asynchronously. When SAP S/4HANA is not properly configured
or master data is missing, the FI document in SAP S/4HANA cannot be created. The defective IDocs can
be found in the inbound processing (transaction BD87) and can be reprocessed after correction. It's a best
practice to prevent the creation of IS-H billing documents if important requirements for posting are not fulfilled
(for example, expected G/L accounts or cost center) or not available in SAP S/4HANA.
You can use the following BAdIs to perform these remote checks before invoice creation:
• ISH_INVOICE_CHECK for the creation of billing documents

• ISH_INV_CANCEL_CHECK_CUST for the creation of cancellation documents
10.6 Replacement for the User Exits in the Financials

Interface
In a non-distributed scenario, you can use the user exits SDVFX001 to SDVFX011 to manipulate an FI
document (for example, change the way the reference and assignment fields are filled, dunning data). If
the requirements implemented with the mentioned enhancements still exist in SAP S/4HANA, you can
supplement or change the content of the IDoc in the SAP ERP system already. To do this, you can use the
method CHANGE_IDOC_BEFORE_SENDING of BAdI ISH_ERP_FI_INVOICE2ACC_OUT. This makes sense, for
example, if data from IS-H is to be written to the segment text of the FI document. For more information, see
the documentation of the IDoc basic type ACC_DOCUMENT04 in transaction WE30.
If you want to process the content in the SAP S/4HANA system, you can implement
the methods CHANGE_IDOC_BEFORE_POSTING and PROCESS_IDOC_AFTER_POSTING of BAdI
ISH_ERP_FI_INVOICE2ACC_IN.
10.7 Set Default Value for Base Unit of Measure for FI

Documents to SAP S/4HANA
The current situation is as follows:
In SAP ERP you can create an invoice with services where the quantity field is filled but the according unit of
measure is kept empty. Such an invoice cannot be posted successfully to SAP S/4HANA.
You now have the following options:
• Customize base unit of measure in the service master data.

• Create a service rule, which determines and fills the unit of measure during billing when it is empty.

42 PUBLIC Best Practices
• Implement method CHANGE_IDOC_BEFORE_SENDING of BAdI ISH_ERP_FI_INVOICE2ACC_OUT in SAP
ERP and use it to determine the unit of measure you require. You will then need to define the unit of
measure determined by the BAdI in SAP S/4HANA.
• Implement method CHANGE_IDOC_BEFORE_POSTING of BAdI ISH_ERP_FI_INVOICE2ACC_IN in SAP
S/4HANA and use it to determine the unit of measure you require. You will then need to define the unit of
measure determined by the BAdI in SAP S/4HANA.
For more information, see SAP Note 3149831 .
10.8 Classification of IS-H-Only Users in IS-H and SAP

S/4HANA
In accordance with your license agreement, users can be classified as special user in IS-H and as engine user
(HE) in SAP S/4HANA so that they aren't counted twice in system measurement. For more information, see
User Classification in the SAP Support Portal or consult the system measurement team.

Best Practices PUBLIC 43
11 Migration
11.1 Overview and General Considerations
Although the integration of IS-H is a very specific subject, it needs to be seen in the context of a general path to
SAP S/4HANA. Based on the overall transition approach, IS-H must be handled as one interface among others.
The following document provides an introduction: Mapping Your Journey to SAP S/4HANA - A Practical Guide
for Senior IT Leadership . We highly recommend that you read this document and understand it as a basis for
all other considerations.
11.1.1 Transition Scenarios
There are three scenarios:
• New implementation (greenfield approach): The new implementation is generally possible for IS-H
customers but they need to keep the master data and configuration in the SAP S/4HANA and the SAP ERP
system in synch, at least for the interface-related parts. This reduces the flexibility of the system setup of
the new SAP S/4HANA system. Especially the implementation options based on SAP Best Practices are
reduced as this kind of implementation would result in system settings that most probably deviate from
the legacy SAP ERP ones.
• Conversion (brownfield approach): The conversion is currently not supported for IS-H customers. For more
information, see SAP Note 2689873 .
• Selective data transition: The selective data transition is possible for all IS-H customers. Customers should
contact a specialized service partner. For more information, see SAP Note 3018442 .
11.1.2 Simplification Items
SAP S/4HANA comes with several simplification items (that is, relevant changes in SAP S/4HANA). You can
use SAP Readiness Check to evaluate the relevancy of the simplification items for your current SAP ERP
installation. For more information, see SAP Readiness Check.
In the preparation step of the project, the implications of these items also need to be evaluated in the IS-H
context, which is not visible in SAP Readiness Check. For example, simplification item Business Partner
Approach explains that all customer master data are represented as business partners in SAP S/4HANA.
For more information, see SAP Note 2265093 . In the context of IS-H, this requires alignment of IS-H number
ranges to the number ranges of business partners (as part of the customer/vendor integration configuration).

44 PUBLIC Migration
11.1.3 Project System Setup
A typical SAP S/4HANA implementation takes several months to two years. The SAP S/4HANA
implementation project requires changes to the SAP ERP repository and IS-H configuration relevant for the
SAP S/4HANA go-live. During this period, IS-H needs to be maintained as well because of regular changes of
business requirements and legal changes. Therefore, a double maintenance phase is required, during which
typically separate transport paths are required.
The project system setup needs to consider this to effectively support the requirement of ongoing
maintenance and project activities.
11.1.4 Impact on Master Data and Configuration
Several FI/CO/MM artifacts (master data and configuration used in the integration interface) need to be the
same in SAP ERP and SAP S/4HANA. These are:
• Structures, such as company codes, plants, controlling areas, and charts of accounts
• Configuration, such as document types, posting keys, and G/L-indicators
• Master data, such as customer master, G/L accounts, cost centers, and material master
If different configuration settings and master data are required in the two systems, there are several options.
Which option is most suitable needs to be decided on a case-by-case basis:
• Change IS-H configuration to new settings via transport during go-live

• Replace interface components (copy standard function modules to custom ones)
• Enhance the standard interface modules with mapping features
• Change settings and data in SAP ERP (also in IS-H, if necessary) within a preliminary project for data
cleansing
To keep relevant configuration settings and master data of the SAP ERP system and the SAP S/4HANA system
in synch also during productive usage, an update of SAP ERP objects needs to be established (manually or by
distributing master data using ALE). For more information, see Overview of ALE Integration Scenarios.
11.1.5 Impact on Cutover
You must choose one of the following go-live approaches:
• The go-live date is the end of the fiscal year.

• The go-live date is not the end of the fiscal year (typically during the fiscal year after the previous fiscal year
has been completely closed and the closing has been certified by the accounting company).
Both approaches have advantages and disadvantages. After comparing the two approaches, your entire
organization must take an informed decision. You also need to consider that the IS-H interface has no time
dependency. This means that IS-H only posts in SAP S/4HANA after activating the integration and no longer
posts to the SAP ERP system. This also applies to postings that would have to be assigned to the previous

Migration PUBLIC 45
fiscal year (from a business perspective). This fact needs to be considered in the overall SAP S/4HANA
go-live decision and as part of the end-of-year closing activities planning. From an IS-H perspective, the go-live
scenario during the fiscal year tends to result in easier implementations.
11.1.6 Impact on Data Migration Activities
The implementation of the IS-H – SAP S/4HANA integration must always be seen in the context of the overall
SAP S/4HANA data migration strategy. You can find a good introduction to tools and approach in the openSAP
course S4H16 (https://open.sap.com/courses/s4h16 ).
The IS-H architecture is mostly based on a strong and close integration to SAP ERP components. In several
areas, the IS-H application does not have its own persistence. It relies on the existence of respective data
residing in other applications. For example, IS-H can help to post down payments to a financial application
such as SAP ERP or SAP S/4HANA without storing this information. IS-H creates respective documents
representing the down payment only in the financial application. Also, a display function for down payments
simply reads the FI documents. In a later process step, the down payment can be deducted from the final
invoice, which technically creates a reference in IS-H for the documents involved. This has a strong impact on
the data migration approach.
To ensure a consistency of business, the SAP ERP objects need to be migrated in a way that IS-H can recognize
the migrated data. This approach differs from the “typical” idea of a new implementation where usually only
master data and data of “open processes” is migrated. For more information about available migration objects
in SAP S/4HANA, see Available Migration Objects.
For an implementation of the IS-H – SAP S/4HANA integration, you typically also need to migrate a certain
set of data belonging to “completed processes”, for example cleared FI document items. Typically, the data
migration also needs to ensure that data is imported with their original key (for example, document number or
customer number) and a wide range of identical attributes (due to references in IS-H and strong synchronous
integration).
As IS-H customers currently cannot “convert” their systems to SAP S/4HANA, they need to set up the system
as a new implementation. Otherwise, customers can execute a selective data transition with the help of
specialized partners. In both scenarios, customers need to plan their data migration very carefully because this
affects the implementation in terms of approach, costs, and duration.
SAP Note 3196450 explains how FI documents are created depending on the integration scenario. This
information can help you to prepare a mapping as part of FI document migration activities.
11.1.7 Custom Code Adaption
Custom and partner code adaption is an important part of all SAP S/4HANA transition projects. For more
information, see the Custom Code Migration Guide for SAP S/4HANA.
For IS-H, additional facts must be considered:
• The enhancements in your SAP ERP system are primarily enhancements in IS-H. Most of them can run
completely without any problems because they do not interact with SAP ERP at all. You need to identify the

46 PUBLIC Migration
critical ones. It might be useful to identify whether the enhancement is still in use and what the purpose of
the enhancement is.
• The IS-H enhancements often contain direct calls on SAP ERP tables or use functions without using the
event/distribution mechanism. In these cases, we recommend that you implement calls of the distribution
mechanism or enhance the event configuration by additional events for the SAP S/4HANA integration.
• There are often enhancements of SAP ERP that require IS-H data. These enhancements should be
transferred to SAP S/4HANA. You need to replace the IS-H artifacts with custom-specific ones because
IS-H artifacts, such as domains and data elements, do not exist in SAP S/4HANA anymore. Additionally,
you need to trigger callbacks to retrieve current data from IS-H using remote call. We recommend that you
do not create additional persistence for patient data in SAP S/4HANA.
• When complete processes (supported by custom or partner-specific development) start in IS-H and shall
be continued in SAP S/4HANA, the coding needs to be split into an IS-H part and an SAP S/4HANA part
including reference feedback and error handling.
 Example
Replenishment of stock locations within care units that are integrated in clinical workplace: The logistic
process of stock management should take place in SAP S/4HANA, the patient-related documentation
process should still be part of IS-H.
• The same applies to the other direction, from SAP S/4HANA to IS-H:
 Example
Use of EDI messages (for Country Version DE: §301 SAMU message) in the function that assigns
incoming payments to open items of the customer (using electronic bank statements).
• Simplifications in functions and technical changes in SAP S/4HANA, for example, changes of database
structures, can require custom code adaption in lS-H as well.
Examples:
• Using the business partner instead of simple customer master data may trigger the need to change a
customer function to store additional customer attributes.
• Replacement of FI document storage by the universal journal in SAP S/4HANA Finance triggers the
need to change a customer function to enrich the FI document.
11.2 Technical Considerations and Details
This section gives some specific technical hints.
11.2.1 Number Ranges for FI Documents
Ensure that FI document numbers are unique (for example, per company code and fiscal year) across SAP ERP
and SAP S/4HANA. The reason is that the FI document numbers can be references (internally or externally).
As a solution, you can define a number range in SAP S/4HANA with a starting range that is greater than the
last document number used in SAP ERP.

Migration PUBLIC 47
11.2.2 Stronger Consistency Checks in SAP S/4HANA
If IS-H runs without SAP S/4HANA integration, the interface for invoices uses internal APIs to trigger the
posting of FI documents for invoices. If the IS-H – SAP S/4HANA integration is running, the interface uses
BAPIs or CALL_TRANSACTION instead. This results in stronger consistency checks in the FI inbound interface.
Therefore, you need to be prepared to enhance the SAP S/4HANA configuration based on the test outcome.
Examples:
• When IS-H triggers a reversal of an FI document for invoices, a reversal reason is mandatory in SAP
S/4HANA. You need to ensure that the reversal reason can be determined by the interface.
• When IS-H triggers the creation of an FI document for invoices, the unit of measurement is transferred and
inserted into the respective field in the document. When the field is not editable, the transfer of the invoice
data fails. Therefore, the maintenance of the field status groups needs to be carefully considered since the
field status groups can prevent postings.
• When IS-H triggers the creation of an FI document for invoices, the check for tax relevance of G/L accounts
is stricter than before.
11.2.3 Specific Hints for Master Data Migration
Customer Master Data
When migrating the existing customer master to SAP S/4HANA, consider the following:
Customer master data representing third-party payers (typically recognizable by a specific account group)
must be created as business partners of the type Person. You can't change the business partner type once it
has been created. IS-H always creates third-party payers as Person.

48 PUBLIC Migration
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Important Disclaimers and Legal Information PUBLIC 49
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP S4 Hana - Integration

Uploaded by

Copyright:

Available Formats

SAP S4 Hana - Integration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP S4 Hana - Integration

Uploaded by

Copyright:

Available Formats

Configuration Guide | PUBLIC

Document Version: 2.5 – 2023-06-07

Configuration Guide IS-H - SAP S/4HANA

THE BEST RUN

3 Logical Systems and RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6 Customizing SAP S/4HANA Financial Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuration Guide IS-H - SAP S/4HANA Integration

9 Implications on Business Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuration Guide IS-H - SAP S/4HANA Integration

Configuration Guide IS-H - SAP S/4HANA Integration

Document Version Date Important Changes

2.5 June, 7th 2023 Updated section:

About This Guide [page 10]

2.4 March, 8th 2023 New section:

Specific Hints for Master Data Migra­

2.3 November, 30th 2022 Updated sections:

• About This Guide [page 10]

Classification of IS-H-Only Users in IS-H

Configuration Guide IS-H - SAP S/4HANA Integration

2.2 September, 8th 2022 Updated sections:

• Edit Output Determination for Bill­

2.1 June, 9th 2022 Updated sections:

• About This Guide [page 10]

• Control Unavailability of SAP

Configuration Guide IS-H - SAP S/4HANA Integration

2.0 March, 9th 2022 Updated sections:

• About This Guide [page 10]

• Define Institution-Specific Control

Configuration Guide IS-H - SAP S/4HANA Integration

1.5 November, 30th 2021 Updated sections:

• Logical Systems and RFC Destina­

1.4 September, 09th 2021 Updated section:

Functional Restrictions [page 38]

Find Relevant SAP Notes [page 11]

1.3 March, 10th 2021 Updated sections:

• Useful BC Sets [page 12] (also

Define Special Function Module for Pre­

Configuration Guide IS-H - SAP S/4HANA Integration

1.2 November, 25th 2020 Updated section:

Define Connected Systems [page 16]

• Implications on Business Proc­

1.1 September, 4th 2020 Updated sections:

• About This Guide [page 10]

Activate BAdI Implementation

1.0 November, 29th 2017 First Version

Configuration Guide IS-H - SAP S/4HANA Integration

2.1 Getting Started

2.1.1 About This Guide

This guide is valid as of:

Configuration Guide IS-H - SAP S/4HANA Integration

ERP system components:

2.1.2 Find Relevant SAP Notes

1. Go to SAP Support Portal and access the expert search.

For previous SAP Notes, enter the following:

• Search Term: IS-H: S/4HANA Integration

2.2 High Level Architecture

Configuration Guide IS-H - SAP S/4HANA Integration

2.3 Useful BC Sets

In the IS-H system:

Configuration Guide IS-H - SAP S/4HANA Integration

Specific Hints for Master Data Migra

• Edit Output Determination for Bill

• Logical Systems and RFC Destina

Define Special Function Module for Pre

• Implications on Business Proc