SAP ABAP IMG Activity ISH_HCM_301_DO_CUST (DE: §301 Customizing)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
IMG Activity
ID ISH_HCM_301_DO_CUST DE: §301 Customizing  
Transaction Code S_KK4_74000440   IMG Activity: ISH_HCM_301_DO_CUST 
Created on 19990816    
Customizing Attributes ISH_HCM_301_DO_CUST   DE: §301 Customizing 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ISH_HCM_301_DO_CUST    

This IMG activity is relevant for the country version Germany only.

Procedure for Implementing §301 Data Exchange (Germany)

  1. Maintain the institute indicator of health insurance companies/ insurance providers

    Of particular importance to the EDI procedure is the correct specification of the institute indicator for each participating insurance provider. You have to specify this number in the Inst. ind. field.
    You can obtain a corresponding overview (and branch directly into the insurance provider maintenance function) by means of the EDI utility RNC301U1. For more information, please refer to the program documentation.
    Before proceeding to assign data collection points, please first refer to the corresponding topic below.

  2. Create the data collection points: Master data maintenance

    You must first create the data collection point before being able to assign it to an insurance provider. You do this in Maintain master data of data collection points.

    Create all third-party data collection points before creating the decoding data collection points. This way you can assign the correct third-party collection points to the decoding collection points right away.

  3. Maintain agreements with the data collection points

    All temporary specifications regarding the data collection points are combined under Agreements. These include agreements with the data collection points (special characters, compression, etc.) and processing parameters within your installation (path definition, code page, etc.).

    Regular automatic processing requires the specification of a separate directory for inbound and outbound data per data collection point in your filesystem. The directory name should include the key of the data collection point in order to facilitate the work not only during the test phase, but during the productive phase as well.

  4. Maintain insurance provider - data collection point assignment

    Once the data collection points have been created, they have to be assigned to the insurance providers. For this purpose the DKG provides a CD with a complete insurance provider and hospital directory together with all assignment information for data collection points. This database is called ISD301 and can be obtained only from the DKG in Düsseldorf (www.dktig.de).

    By means of program RNC301C3 you can assign insurance providers to data collection points on the basis of this file. Please read the program documentation, since you must create a data extract beforehand.

The following two alternatives also exist:

  1. By means of the EDI utility RNC301C1, you can store data collection points for selected insurance providers. This means you do not have to maintain each insurance provider individually (see second alternative). Please refer to the program documentation. You can branch into this maintenance activity from the EDI Utility RNC01U1 mentioned above.
  2. You can access a general maintenance transaction (transaction code ONCEDI5) from the Communication area level menu by choosing EDI -> Data collection point -> Insurance provider asgmt -> Change. Here you can modify, delete or add all assignments.

  1. Maintain Number Range ISH_NC301

    Define the number range for EDI message administration in the number range object ISH_NC301.

    Note the following conditions:

    • Do not specify an institution. The number range is institution-independent.
    • The transaction mode must always be "N".
    • Specify an asterisk (*) in the Obj. Key field.
    • Enter the two-digit identification of an internal number range (e.g. "01") in the NI field.
    • Leave the NE field blank.
    • Do no select the A attribute.

      You maintain the number range interval by choosing Maintain Number Range and then Insert Interval. The system checks in each case whether the intervals overlap.

      Define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

  2. Maintain Number Range ISH_NC301D

    Define the number range for EDI file administration in the number range object ISH_NC301D.

    Note the following conditions:

    • Do not specify an institution. This number range is institution-independent.
    • The transaction mode must always be "N".
    • Specify an asterisk (*) in the Obj. Key field.
    • Enter the two-digit internal identification of an internal number range (e.g. "01") in the NI field.
    • Leave the NE field blank.
    • Do not select the A attribute.

      You maintain the actual number range interval by choosing Maintain Number Interval and then Insert Interval. The system checks in each case whether the intervals overlap.

      You have to define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

  3. Maintain Number Range ISH_NC301X

    If you connect an external transfer system which can process the files from one directory only, you also have to define a number range for this. The number range object ISH_301X is predefined for this purpose.
    If you do not use this 'all in one' directory logic, you do not need to create the number range.

    Note the following conditions:

    • Specify an institution. This number range is institution-dependent.
    • The transaction mode must always be "N".
    • Specify the respective EDI procedure (e.g. 'P301' for data exchange according to §301 SGB V in Germany) in the Obj. Key field.
    • Enter the two-digit internal identification of an internal number range (e.g. 01) in the NI field.
    • Leave the NE field blank.
    • Do not select the A attribute.

      Maintain the actual number range interval by choosing Maintain Number Range and then Insert interval. The system checks in each case whether the intervals overlap.

      Define an internal purely numeric number range here so that the system automatically determines a number in the corresponding situation.

      Please consult the manufacturer of the transfer system when defining the number interval for the number range, since both systems will work with this number.

      In particular, when several EDI procedures are active in the one institution, and in instances when several institutions exist, you have to use different intervals for different EDI procedures.

In such cases, the use of a single number range interval is not sufficient to ensure contiguous number assignment per institution and EDI procedure. Define the number range in relation to the capabilities of the transfer system.

SAP recommends that you use a number range as great as possible (from '000...000' through '999...999') for this purely technical number. This will ensure trouble-free functionality for the long-term.

SAP makes the following recommendation when several different intervals are used: distinguish these intervals using the initial two or three digits. The remaining digits should again make for as great an interval as possible.

Example:

  • Institution 1, P301: 0110000000 through 0119999999, institution 1, P302: 0120000000 through 0129999999
  • Institution 2, P301: 0210000000 through 0219999999, institution 2, P302: 0220000000 through 0229999999.

  1. Activate data collection

    Data transfer via EDI has to be explicitly activated in the system. You activate this option in the Customizing activity Activate communication procedure. In the corresponding Customizing table you can specify for which communication procedure you want to carry out data exchange. For Germany, only data exchange according to §301 is relevant. For this, please specify the current institution and the procedure P301.

    Please note that the previously used parameter Activate EDI in the institution control parameter table is no longer evaluated.
    You should activate data collection only if data exchange takes place electronically. On no account activate this file creation if you are still exchanging data with health insurance companies using forms (or any other means).
    If you set this flag, corresponding background processing tasks must be installed (see below).

  2. Create messages

    Program RNC30100 is responsible for message creation. In a productive environment, this program should be run regularly at 5-15 minute intervals. This makes it easier to check the current status (see belo

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
ISH_HCM_301_DO_CUST DE Germany
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ISH_HCM_301_DO_CUST 0 I010004233 Communication with Systems Outside the Hospital 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990816 
SAP Release Created in