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

Configuration Guide | PUBLICDocument Version: 1.3 – 2021-03-10

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

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 High Level Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Useful BC Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.4 Keep Customizing and Master Data Synchronized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Logical Systems and RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

4 Customizing IS-H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.1 Define Connected Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2 Assign Systems to Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114.3 Define Default Values for FI Customers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.4 Display the FI Customer Number of the Insurance Provider in the SAP Business Partner. . . . . . . . . . 134.5 Post Fees in Transaction NWCH97_API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.6 Define Special Function Module for Presetting FI Data for Self-Payer. . . . . . . . . . . . . . . . . . . . . . . . 14

5 Customizing SD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.1 Edit Output Determination for Billing Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.2 Output Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Create New Distribution Model (client dependent). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Create Port in IDoc Processing for Transactional RFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Edit Partner Profile for Logical Receiver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Generate Partner Profile for new Distribution Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Distribute Model View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

6 Customizing SAP S/4HANA Financial Accounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.1 Inbound Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Edit Partner Profile for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.2 Enabling System Standard Inbound Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Create Forwarding Inbound for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Set EDI-INVOIC program parameters for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Create FI-EDI G/L Account for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Create Supplier Master (General Section) for Logical Sender. . . . . . . . . . . . . . . . . . . . . . . . . . . 23Activate BAdI Implementation ISH_ERP_FI_LOCAL_ACC_DOC_BKPFF. . . . . . . . . . . . . . . . . . . . 23Map External Tax Rate to Tax Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2 PUBLICConfiguration Guide IS-H - SAP S/4HANA Integration

Content

6.3 Enabling Business Partner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Configure Master Data Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.4 Source Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Activate BAdI Implementation EI_ERP_FI_LOCAL_PROC_INV_IDOC. . . . . . . . . . . . . . . . . . . . . . 25Replacement for the User Exits in the Financials Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

7 User Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

8 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

9 Implications on Business Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289.1 Functional Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

10 Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Configuration Guide IS-H - SAP S/4HANA IntegrationContent PUBLIC 3

1 Document History

This section provides details about the changes made in each version of this document.

NoteThis 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/.

Document History

Document Version Date Important Changes

1.3 March, 10th 2021 Updated sections:

● Useful BC Sets [page 7] (also renamed from Switch BC Sets)

● Functional Restrictions [page 28]

New section:

Define Special Function Module for Presetting FI Data for Self-Payer [page 14]

1.2 November, 25th 2020 Updated section:

Define Connected Systems [page 10]

New sections:

● Implications on Business Processes [page 28]

● Best Practices [page 31]


Document History

https://help.sap.com/viewer/product/SAP_FOR_HEALTHCARE/

https://help.sap.com/viewer/product/SAP_FOR_HEALTHCARE/

Document Version Date Important Changes

1.1 September, 4th 2020 Updated sections:

● About this Guide [page 6]● Define Default Values for FI Cus

tomers [page 12]● Edit Output Determination for Bill

ing Documents [page 15] (also renamed from Create Condition for Billing Type “Cancel Invoice”)

● Create Supplier Master (General Section) for Logical Sender [page 23]

● Replacement for the User Exits in the Financials Interface [page 25]

● Functional Restrictions [page 28]

New section:

Activate BAdI Implementation ISH_ERP_FI_LOCAL_ACC_DOC_BKPFF [page 23]

1.0 November, 29th 2017 First Version

Configuration Guide IS-H - SAP S/4HANA IntegrationDocument History PUBLIC 5

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

Validity:

This guide is valid as of:

● IS-H 617 SP 034 (SAP ERP 6.0, Industry Extension Healthcare, SAP Enhancement Package 7, Support Package 034)

● IS-H 618 SP 012 (SAP ERP 6.0, Industry Extension Healthcare, SAP Enhancement Package 8, Support Package 012)

● SAP S/4HANA 1709 FPS01

System Requirements:

You need the following systems:

● IS-H 617 SP 034, or higher or IS-H 618 SP 012, or higher● SAP S/4HANA 1709 FPS01, or higher

Abbreviations:

ERP system components:

● CO: Controlling● FI: Financial Accounting● MM: Materials Management● SD: Sales and Distribution


Introduction

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.

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 Customizing tables with client 000 of 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 .

Configuration Guide IS-H - SAP S/4HANA IntegrationIntroduction PUBLIC 7

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/3017401

In the SAP S/4HANA system:

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.

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.

CautionEnsure 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

● Master Data○ G/L account○ order○ material○ cost center


Introduction

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).If entries already exist, you can use those, or you can still create new ones.

● 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.If entries already exist, you can use those, or you can still create new ones.

Configuration Guide IS-H - SAP S/4HANA IntegrationLogical Systems and RFC Destinations PUBLIC 9

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.


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).

CautionYou have to assign an institution for every client and institution separately.

You can use the sample entries for the institution BSS4 and the system REMOTES4.

Configuration Guide IS-H - SAP S/4HANA IntegrationCustomizing IS-H PUBLIC 11

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.

NoteThe 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

RecommendationWe 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.


Customizing IS-H



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.

Configuration Guide IS-H - SAP S/4HANA IntegrationCustomizing IS-H PUBLIC 13

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).

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.


Customizing IS-H


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 Edit Output Determination for Billing Documents

As a prerequisite, you have to maintain respective output determination procedures (for example, V10000), output types (RD00), access sequence (for example, 0001), and, if necessary, also new output condition tables. We recommend that you use the existing table 008 (billing type). You can use the Customizing activities under

Sales and Distribution Basic Functions Output Control Output Determination Output DeterminationUsing the Condition Technique Maintain Output Determination for Billing Documents .

The SAP S/4HANA integration of the billing documents requires configuration of output management (NAST), which uses condition technique. Basically, the Idoc communication scenario uses the output type RD00 (Invoice), which triggers an EDI medium for a partner function “LS” (Logical system). As this is a standard SD function, the specific handling of IS-H invoices needs to be separated from other billing scenarios.

Therefore, the output determination needs to be configured so that only for IS-H billing types NF01 and NS01 (plus additional conditions, if necessary) the Idoc generation is triggered.

Then, you need to maintain condition records for the IS-H billing types using transaction VV32.

To create a condition for the billing type Cancel Invoice, execute transaction code VV32 (Change output: Billing). Alternatively choose in the SAP Menu Logistics Sales and Distribution Master Data Output Billing Documents Change (client dependent) .

1. For output type Invoice, enter RD00.2. Choose Execute.3. Check the entries for the following billing types or add them if they don't exist yet:

Billing Types

Billing Type Name

NF01 IS-H: Invoice (Case)

NS01 IS-H: Cancel (Case)

If an entry already exists, you don’t need to change the values for Medium and Date/Time.

Configuration Guide IS-H - SAP S/4HANA IntegrationCustomizing SD PUBLIC 15

5.2 Output Handling

5.2.1 Create New Distribution Model (client dependent)

CautionIf 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 10])

Partner -> Sender Name of the logical system of IS-H system

Partner -> Receiver Name of the logical system of the S/4 system

Choose Continue.

6. On the next screen of the dialog window, choose Complete7. On the main screen, choose Save.

After you completed these steps, the screen may look like this:

Create New Distribution Model


Customizing SD

5.2.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.


Create Port in IDoc Processing for Transactional RFC

5.2.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 S/4 system.○ Partner Type

Enter LS.


Choose Continue.2. Only in lines with message types INVOIC and SYNCH, enter the name of the of the S/4 system into 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.

5.2.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.2.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.


Customizing SD


Distribute Model View


6 Customizing SAP S/4HANA Financial Accounting

6.1 Inbound Handling

6.1.1 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 INVOIC. Choose Continue.

6.2 Enabling System Standard Inbound Processing

6.2.1 Create Forwarding Inbound for Logical Sender

To create a Forwarding Inbound for logical, execute transaction code SM30 (Call View Maintenance) and do the following:

1. In field Table/View enter VEDI_EDILO.2. Choose Maintain.3. Create a new entry and fill in the following fields:

○ Logical address: Enter the name of the logical system of the IS-H system.○ Application: Enter FI.○ Destination in SAP system: Enter the name of the logical system of the IS-H system.

20 PUBLICConfiguration Guide IS-H - SAP S/4HANA IntegrationCustomizing SAP S/4HANA Financial Accounting


Create Forwarding Inbound for Logical Sender

6.2.2 Set EDI-INVOIC program parameters for Logical Sender

To set the EDI-INVOIC program parameters for the logical sender, execute transaction code SM30 (Call View Maintenance) and do the following:

1. In field Table/View enter V_T076S.2. Choose Maintain.3. For each possible company, create a new entry and fill in the following fields:

○ Partner Type: Enter LS.○ Partner No.: Enter the name of the logical system of the IS-H system.○ Company Code: Enter one company code.

Configuration Guide IS-H - SAP S/4HANA IntegrationCustomizing SAP S/4HANA Financial Accounting PUBLIC 21


Set EDI-INVOIC program parameters for Logical Sender

6.2.3 Create FI-EDI G/L Account for Logical Sender

To create an FI-EDI G/L account for the logical sender, execute transaction code SM30 (Call View Maintenance) and do the following:

1. In field Table/View enter V_T076I.2. 2. Choose Maintain3. For each possible company, create a new entry and fill in the following fields:

○ Partner Type: Enter LS.○ Partner No.: Enter the name of the logical system of the IS-H system.


○ Company Code: Enter one company code.4. Select New Entries and fill in the following fields:

○ Goods/Services No.: Enter * (an asterisk).○ Goods/Serv ID Text: Leave this field empty.○ G/L Account: Enter a valid G/L Account.○ Company Code: Enter the company code as in the G/L Account.

6.2.4 Create Supplier Master (General Section) for Logical Sender

Use transaction XK01 (Create Vendor) to create a supplier (general data are sufficient), which technically creates a business partner with role FLVN01 (Vendor). The ID of the supplier and business partner must be the logical system (for example, QIHCLNT212). You must also enter an address with at least a value for country/region.

6.2.5 Activate BAdI Implementation ISH_ERP_FI_LOCAL_ACC_DOC_BKPFF

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_BKPFF.

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 checkbox Implementation is activated in Customizing (IMG) for the BAdI implementation

ISH_ERP_FI_LOCAL_ACC_DOC_BKPFF.

The system will display a confirmation message and the runtime behavior is set to “Execution depends on runtime filter values”.

6.2.6 Map External Tax Rate to Tax Code

To map external tax rates to the tax code, execute transaction code OBCD (Maintain Table T076M) and do the following:

Create a mapping entry for each possible "outgoing" tax code of an invoice that comes from the logical system of the IS-H system.

● After you completed these steps, the screen may look like this:


Map External Tax Rate to Tax Code

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 SynchronizationSynchronization 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 Activate BAdI Implementation EI_ERP_FI_LOCAL_PROC_INV_IDOC

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_PROC_INV_IDOC, and choose Display.2. Activate the checkbox Implementation is activated in Customizing (IMG).

The system will display a confirmation message.

6.4.2 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). In a side-by-side scenario, you need to define these adjustments as follows:

You have the following options for invoice posting:

● Substitution Framework (transactions GGB1 and OBBH)● Business Transaction Event 1120 “POST DOCUMENT: Field Substitution Header/Lines”● Function exit EXIT_SAPLIEDI_102 in enhancement FEDI0001 “Function Exits for EDI in FI”


7 User Authorization

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 / enter the following attributes:○ Function group N_ERP_FI_LOCAL○ Activity 16 (Execute)


User Authorization


User Authorization

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.

Configuration Guide IS-H - SAP S/4HANA IntegrationMonitoring PUBLIC 27

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 invoiceYou 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 accountIf 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.

9.1 Functional Restrictions

The integration of IS-H and SAP S/4HANA is possible only with some minor functional restrictions.

In the IS-H system, please note the following:


Implications on Business Processes

● 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 the additional fields “FI posting status code” and “FI posting status” (as icon) into your invoice overview. For more information, see SAP Note 2706908 .

● 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.

● The release/post function (subsequent posting of SD billing documents) isn’t useable because all invoices created by IS-H have the posting status D (not relevant for Accounting) or E (billing document cancelled). This affects the release/post function within the invoice overview in transaction NA30N (Case-Related Invoice Processing) as well as the complete transaction NA04 (IS-H: Release Billing Document into Financial Accounting). If an SD billing document can’t be posted to SAP S/4HANA, you have to find and correct the root cause and then postprocess accordingly. If the root cause is a wrong SD billing document (for example, a wrong account or cost object assignment), then you typically have to cancel and recreate the document.

● 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 .

● Only relevant for the local version Germany: The transfer of electronic dunning notices as part of EDI communication according to §301 (message type MAHN) isn’t supported. The dunning program F150 doesn’t automatically trigger the respective P301 event when the insurance provider has been dunned.

Configuration Guide IS-H - SAP S/4HANA IntegrationImplications on Business Processes PUBLIC 29



● The global system parameter DEB_ERR for controlling the behaviour of FI transactions called in the background is not taken into account.

In the SAP S/4HANA system, please note the following:

● 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.


Implications on Business Processes

10 Best Practices

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).

You can also implement various conditions under which the transfer of invoices to FI in SAP S/4HANA should be blocked.

Configuration Guide IS-H - SAP S/4HANA IntegrationBest Practices PUBLIC 31

Important Disclaimers and Legal Information

HyperlinksSome 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 a 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 PlatformsSome 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 FeaturesExperimental 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 CodeAny 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.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

Configuration Guide IS-H - SAP S/4HANA IntegrationImportant Disclaimers and Legal Information PUBLIC 33

www.sap.com/contactsap

© 2021 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

https://www.sap.com/about/legal/trademark.html

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

Documents

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