SAP ABAP IMG Activity SIMG_CFMENUNMO4ONCV (Configure Receipt Control w/o Org. Unit Dependency)
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 SIMG_CFMENUNMO4ONCV Configure Receipt Control w/o Org. Unit Dependency  
Transaction Code S_KK4_74000130   IMG Activity: SIMG_CFMENUNMO4ONCV 
Created on 19990816    
Customizing Attributes SIMG_CFMENUNMO4ONCV   Configure Receipt Control w/o Org. Unit Dependency 
Customizing Activity SIMG_CFMENUNMO4ONCV   Configure Receipt Control w/o Org. Unit Dependency 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUNMO4ONCV    

Use

In this IMG activity, you determine from which partner systems which messages are to be retrieved or can be received.

Note

Note that the specifications you make here are client-dependent. If you operate a test client in the same system as your production client, it is recommended that you create corresponding "test" partner systems (in the IMG activity Maintain System Attributes, or using the report HCM Precustomizing (RNCUTL19). Otherwise, data can be transferred into the wrong client.

Activities

  1. Enter the logical system name (not the TXCOM name) in the System field.

    Here you specify the assigned event by entering the:

    • Application (A field, always "N" for IS-H)
    • Event key (Event field)

      At present, IS-H supports the transfer of:

    • Case-related diagnoses
    • Case-related services
    • Organizational unit-related services
    • Surgical data

      You may find the term "event" somewhat confusing here. However, it is appropriate. The event Maintain Actual Services (key NL10I0) or Maintain Case-Related Diagnoses (key NP6100) in fact occur.

  2. You can specify message types of the supported standard in relation to the event. Select the appropriate standard from the value help.

    At present, message receipt is only supported for the SAP-HCM format.

  3. Determine the format of the transmitted data using the message type owner code OC.
  4. You should only specify special characters if you do not use those predefined by the standard. At present, special characters are not supported by the SAP-HCM standard.
  5. The data from the partner system has to be made available in relevant files. These files have mandatory names (irrespective of the message standard/format used):
    • "NT021.dat"     for case-related diagnoses
    • "NT101.dat"     for case-related services 1
    • "NT102.dat"     for case-related services 2
    • "NT103.dat"     for surgical data
    • "NT104.dat"     for surgeries 2
    • "NT150.dat"     for OU-related services

      The data received is stored in batch input sessions. You can specify your own names for these sessions.

Dependencies

You can only process/receive those message types listed in the section entitled Display Receipt Options (SAP) (call the value help).

Recommendation

You do not have to specify a name for a session. If make no explicit name specification, the default name is assigned. The default names are:

  • "ISH_DIAGS"     for case-related diagnoses;
  • "ISH_SERVS"     for case-related services 1 and 2
  • "ISH_SURGS"     for surgical data 1 and 2 (surgeries)
  • "ISH_OUSRV"     for OU-related services

If you prefer to use your own session name, we recommend that you start it with 'ISH'. This greatly facilitates checking the sessions because you can use the generic search option.

Business Attributes
ASAP Roadmap ID 205    
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUNMO4ONCV 0 I010004207 Communication 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TNCI1 V - View SM30 1 Maintain Receipt Control Without Dependency 
History
Last changed by/on SAP  19990816 
SAP Release Created in