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_CCPS_DO_CUST | SG: CCPS Customizing |
| Transaction Code | S_KK4_74000431 | IMG Activity: ISH_HCM_CCPS_DO_CUST |
| Created on | 19990816 | |
| Customizing Attributes | ISH_HCM_CCPS_DO_CUST | SG: CCPS Customizing |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISH_HCM_CCPS_DO_CUST |
Procedure for Implementing CCPS Data Exchange
- Maintain the institution-specific agreements
Please specify the technical transmission data (sender specifications) for each institution. Also maintain the values for hospital identification. The following rules apply for CCPS: HP code 2 (field name ID2) contains the hospital code that is to be specified for outpatient cases; Hp code 1 (field ID1) contains the code for all other cases. If your hospital has only one code for both situations, please enter the same value in both fields.
You can store the corresponding values by choosing Maintain Agreements with the Institutions. - Create the data collection points: Master data maintenance
Before transmitting data to a recipient, you must first create this recipient as a 'data collection point'. You do this by choosing Maintain Master Data of Data Collection Points.
- 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.
- 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.
- 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.
- 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.
- Maintain communication status
In the step Maintain Communication Status, please specify the communication statuses defined by the communication procedure and assign the appropriate internal codes to them (using Possible entries). You will find the external codes in the CCPS code list for "Status of Processing".
- Maintain application status
In the step Maintain Application Status, please specify the values defined by the communication procedure and assign the appropriate internal codes to them (using Possible entries). You will find the external codes in the CCPS code list for "Status of Processing".
- Activate data collection
CCPS data transfer has to be activated explicitly 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.
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 using forms (or any other means).
If you set this flag, corresponding background processing tasks must be installed (see below). - 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 below).
The message formatting program processes all events logged since it was last executed. It checks whether or not a message was created for each event. If a message was created, the program determines which message type is required (several message types can be required for one event). All required messages are created. They are saved with the status 'ready to send' in the IS-H System.
If problems arise during message creation (e.g. required-entry fields are not filled), these problems are saved as error messages together with the formatted messages. Depending on the type of problem, the message may nevertheless be characterized as 'ready to send'.
Messages which do not correspond to the conventions specified are basically not included for file creation.
- Evaluate message administration
Before the file is created it makes sense to evaluate existing messages with errors.
The main evaluation utility is the EDI utility RNC301U2. This utility is also initiated from various places within the application.
By means of this utility, you can carry out various actions to supply missing data to the required-entry fields. You should run program RNC30100 again after
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_CCPS_DO_CUST | SG | Singapore |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | ISH_HCM_CCPS_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 |
