Ansicht
Dokumentation

ISH_TNHCO - Maintain Basic Settings

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

In this IMG activity, you make basic settings to enable the integration of IS-H with Controlling (CO) for your institution, should you want to use the interface with Controlling.

• In the IAA Inpatient Cases group box, you specify what form internal activity allocation (IAA) is to take for inpatient cases.

• In the IAA Outpatient Cases group box, you specify what form internal activity allocation is to take for outpatient cases.

• The IAA Screen Variant, Individual Posting Text, and Other group boxes contain further settings for internal activity allocation that are not dependent on the case type.

• In the Automatic Postings group box, you make settings that are important for automatic postings to CO.

• If you want to transfer statistical key figures from IS-H into CO, you need to maintain the settings in the Statistical Key Figures group box.

• You can, in particular, specify whether Cost Center Accounting or Cost Object Controlling is to be supported.

• In addition, here you need to make a number of settings that enable the IS-H system to automatically execute CO functions in the background.

Before maintaining the basic settings, you have made the required settings in Customizing for CO.

No standard settings are delivered.

The activities described below mainly involve declaring the settings you made in Customizing for CO to the IS-H system.

We therefore recommend that you test all relevant transactions in CO first. These include:

• Internal activity allocation

• Maintenance of order master data

• Preliminary costing

• Planning

• Actual postings

This is the only means of making sure that the settings made here function later when automatic postings are made from the IS-H system into CO.

1. Together with your CO project team, determine the organizational form of Controlling that is to be used for integration with IS-H.
2. Make the necessary settings in CO, and test (at least roughly) the relevant transactions by executing the CO function manually.
3. Apply these CO settings in the basic settings and further Customizing settings:
   

IAA Inpatient Cases

In the IAA Inpatient Cases group box, select to which objects account assignments are to be made for inpatient cases. The setting relates to the receiver of an activity.

• Inactive - do not perform IAA for inpatient cases

• Cost Centers - account assignment to cost centers only

• Orders- account assignment to order only

• Cost Centers and Orders - account assignment to cost center and order

If you want to make account assignments to orders, you also need to specify here if you only want to work with case-based orders, or also with cost object-based orders (caution: cost object-based orders are not released for production operation). If you set either of these indicators, you must also specify the relevant CO order type that you want to use for these orders.

IAA Outpatient Cases

In the IAA Outpatient Cases group box, select to which objects you want to make account assignments for outpatient cases. The setting relates to the receiver of an activity.

• Inactive - do not perform IAA for outpatient cases

• Cost Centers - account assignment to cost centers only

The following two functions are only available if you are using SAP Ambulatory Care Management.

• Orders- account assignment to order only

• Cost Centers and Orders - account assignment to cost center and order

If you want to make account assignments to orders, you also need to specify here if you only want to work with case-based orders, or also with collective orders. If you set either of these indicators, you must also specify the relevant CO order type that you want to use for these orders.

These order types must accommodate internal number assignment so that orders can be automatically created in CO, for example, when invoices for outpatient cases are canceled, or when the collective order definition is copied into another validity period.

When collective orders are used, the orders must have been created beforehand and the criteria table for collective order determination must have been maintained.

Dependent on the type of internal activity allocation selected, you need to specify CO list screen variants in the IAA Screen Variant group box.

Other
In the Other group box, you can stipulate whether a collective cost center is to be taken into account when the system determines the sender and receiver. For more information, see the F1 Help for the SendColl. CC and Rec. Coll. CC fields.

By setting the No Part.Transf indicator, you stipulate that transfer is not to take place if an error occurs for an account assignment rule when multi-account assignment is active.

By setting the No Buffering indicator, you can prevent the IS-H Services - CO Activity Types (NLAZ) assignment table from being fully buffered by the transfer program. It is recommended that you set this indicator if you have maintained many rules in the assignment table.

Individual Posting Text

When internal activity allocation takes place, the CO segment text is filled as follows in the standard system:

• Case number

• /

• Sequence number of the service

If required, you can create your own structure using a FORM routine. If you want to use your own formatting routine, specify the name of the FORM and the program in the FORM Routine and Program fields in the Individual Posting Text group box.

Note that the FORM routine must have a defined structure. Refer to the sample SGTEXT in the RNHCO000program.

Automatic Postings

• You can specify when the order is to be created (Order Creation field). Two settings are currently supportedt:

- 09 - on request, in other words, after the event, using the Create Case-Based Order function

- 01 - in the background, when an inpatient case is admitted

• By setting the Tech. Complete After Final Billing indicator, you stipulate that when final billing has been successfully performed for an inpatient case, the relevant case-based order and, if available, the cost object-based orders of the case are to be technically completed. This is recommended, for example, if you subsequently want to settle these orders in CO using collective settlement. In such cases, you can make your selection based on the order status.

• The No Partial Settlement to CO-PA indicator allows you to stipulate that you do not want partial settlement of IS-H case-based orders to Profitability Analysis (CO-PA). If you set this indicator, when you transfer IS-H services, peform billing in IS-H, and cancel the resulting invoices, the IS-H system checks whether account assignments are to be made to an order that has already been settled to CO-PA. If corresponding settlements exist, the IS-H system reverses them before making account assignments to the order.

• You can control that, when final billing has been successfully performed for a case, the transfer of services to CO for this case is to be automatic. You can choose whether service transfer is to be triggered after single billing only, after collective billing only, or after both methods of billing. To do this, enter the appropriate value in the Svce Trans. field.
  

Costing

To be able to assign a preliminary costing to an order using the Transfer Preliminary Costing function, you need to specify a costing variant in the Cstg Variant field.

Screen Variants for Statistical Key Figures

If you want to use statistical key figures, you need to stipulate a screen variant for the actual postings for cost centers and for case-based orders.

1. Now test the integration of IS-H with CO by launching the transactions from the IS-H system.
2. Make any further changes to the settings in CO and IS-H only with the consent of the IS-H and CO project teams.

SAP provides the NHCO0000 enhancement for you to implement an alternative account assignment logic. For more information, see the enhancement documentation.

PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 11552 Date: 20240424 Time: 044721     sap01-206 ( 165 ms )