SAP ABAP IMG Activity SIMG_CFMENUNMO4ONCZ (Maintain Master Data of Data Collection Points)
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_CFMENUNMO4ONCZ | Maintain Master Data of Data Collection Points |
Transaction Code | S_KK4_74000116 | IMG Activity: SIMG_CFMENUNMO4ONCZ |
Created on | 19990816 | |
Customizing Attributes | SIMG_CFMENUNMO4ONCZ | Maintain Master Data of Data Collection Points |
Customizing Activity | SIMG_CFMENUNMO4ONCZ | Maintain Master Data of Data Collection Points |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUNMO4ONCZ |
Use
In this IMG activity, you create or maintain the master data of data collection points for Electronic Data Interchange (EDI).
Activities
- Enter a 10-character mnemonic key for the data collection point (DCP). You can enter a short descriptive text for this DCP in the adjacent short text field.
- A validity period applies to each data collection point. Specify a period that is sufficiently long. It is recommended to specify the high date 12/31/9999 as the Valid To date. This achieves unrestricted validity.
- The institute indicator of the data collection point is of particular importance and is checked by the respective communication partner system. This institute indicator should not be confused with the institute indicator of the associated health insurance fund. In this way, one computer center can serve a number of health insurance funds or hospitals.
- You control actual data exchange using the type of data collection point:
- If the data collection point is authorized to decode, data is assembled for this collection point.
- A data collection point that is not authorized to decode (3rd party data collection point) will receive data for a number of (decoding) data collection points. The third party data collection point cannot decode this data. It simply forwards the different files by means of the associated (non-encoded) order files to the corresponding receivers (the actual users (transaction DCPs)).
These are two different categories of transaction DCPs:
- The one receives the data directly.
- The other uses a third party data collection point. For this type of DCP, the DCP key and institute indicator of 3rd party DCP must be specified as a reference. It is not possible to specify a 3rd party DCP for another 3rd party DCP.
- You can specify the data on contact person here. However, this data is not processed.
- You should maintain the address correctly so as to enable dispatch notes to be printed at a later date. However, this functionality is not yet supported.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
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_CFMENUNMO4ONCZ | 0 | I010004233 | Communication with Systems Outside the Hospital |
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_NC301P | V - View | SM30 | 1 | Maintain Data Collection Points for EDI |
History
Last changed by/on | SAP | 19990816 |
SAP Release Created in |