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_ISHCM_GD_ERRS | Troubleshooting |
| Transaction Code | S_KK4_74000160 | IMG Activity: SIMG_ISHCM_GD_ERRS |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_ISHCM_GD_ERRS | Troubleshooting |
| Customizing Activity | SIMG_ISHCM_GD_ERRS | Troubleshooting |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHCM_GD_ERRS |
IS-HCM Troubleshooting
This documentation describes how you can troubleshoot errors which occur with the non-SAP system connection to IS-H. It essentially comprises a list of the checks you have to carry out.
- Is the HCM transceiver installed correctly in the non-SAP system?
Was the local installation successfully tested using the local test? You must be able to start the program under the gateway user id. The gateway user must be able to access the target computer from the gateway host via remsh.
For more information on this topic, see Installation Instructions for the Transceiver. The special characteristics of the IS-H System must be taken into account here. These are listed under Information on the SAP Communication Module.
Change the setting of parameter INTERF_DEB from 0 to 3 in the corresponding script and call this script remotely under the gateway user id (using remsh from the gateway host). A trace must have been written in the directory INTERF_PRK. The trace must show an error with a CMACCP. The installation is all right so far only if such a CMACCP error exists. Now delete the trace.
If other errors exist, please correct these. Once you have corrected these errors it may be worthwhile to carry out a complete test. If no errors are reported, reset the value of parameter INTERF_DEB to 0.
You should continue troubleshooting only if an error situation still exists after the test has been carried out successfully. To do this, leave the value of parameter INTERF_DEB set to 3.
At this stage, check if the transceiver has been correctly installed.
- Carry out IS-HCM installation check (program RNCCHK01)
You should now carry out the Installation Check. Please take note of any warnings or error messages issued.
If other errors exist, please correct these. Once you have corrected these errors it may be worthwhile to carry out a complete test. If this is successful, reset the value of parameter INTERF_DEB to 0.
You should continue troubleshooting only if an error situation still exists after the test has been carried out successfully. To do this, leave the value of parameter INTERF_DEB set to 3.
- Configuration overview - extended check (program RNCLST01)
By means of program RNCLST01, generate an overview of the configuration (of this system). Take note of any warnings and error messages issued here.
If you archived a hardcopy of this list after your system was correctly connected, please check if the configuration has been modified.
If other errors exist, please correct these. Once you have corrected these errors it may be worthwhile to carry out a complete test. If this is successful, reset the value of parameter INTERF_DEB to 0.
You should continue troubleshooting only if an error situation still exists after the test has been carried out successfully. To do this, leave the value of parameter INTERF_DEB set to 3.
- Check background jobs
Branch to the job overview. Search for jobs whose name starts with ISHCM*, irrespective of the user name. If you have not kept to the IS-H naming conventions, you'll have to check all jobs.
Check whether these jobs were correctly and completely set up and released.
If other errors exist, please correct these. Once you have corrected these errors it may be worthwhile to carry out a complete test. If this is successful, reset the value of parameter INTERF_DEB to 0.
You should continue troubleshooting only if an error situation still exists after the test has been carried out successfully. To do this, leave the value of parameter INTERF_DEB set to 3.
- Analyze system log
The system log also provides a trace of all communication errors. Search for entries with
communication error, CPIC-RC=xxx, SAP-RC=yyy,
and, to be on the safe side, irrespective of user name. You should take a closer look at the most recent of these CPIC blocks. Double-clicking the corresponding CPIC-RC=xxx line allows you to discern the meaning of the specified SAP-RC=yyy (top right). You may have to scroll. Does this help?
- Check TXCOM
Please make sure the syntax of the specifications in the table TXCOM is correct. As a general guideline: GW service usually in lower case, GW host under Unix also usually in lower case, but in upper case under NT.
- Analyze gateway trace
Communication with the transceiver is basically routed via an SAP gateway. Should errors occur, the gateway records these in a trace called "dev_rd". This developer trace is in a specific directory on the host on which the gateway is running. Usually, you can log on to this host in the SAP system and display this trace by choosing the function Developer traces. Alternatively, you can access the Gateway Monitor menu (transaction SMGW) and view the trace by choosing Goto -> Trace -> Gateway -> Display file. Does this help?
- Perform complete test
Have you got this far without having to change/maintain/delete anything in the previous steps?
Or have you changed something?
In both cases, now is the time to carry out a complete test again.
If no errors are found, your changes were successful. If this is the case, please reset the value of parameter INTERF_DEB in the program script to '0'. Delete all transceiver program logs that were created. It is also recommended to archive a hardcopy of error-free configurations.
Still no success?
Your next step is to check whether there is already a note relating to your problem in the SAP OSS. When searching for a note, you can enter the application area IS-H-CM directly. In particular after release upgrade actions, please refer to the collective note maintained by the IS-H development team.
If you do not find any appropriate notes for your problem, please assemble all the information required for reporting a problem to SAP. This includes:
- First and foremost, an in-depth description of the symptoms which can be observed. In particular, the number of the error message issued (specified in the long text, for instance NC711) is important.
- A statement to the effect that you have worked through the various steps described in this troubleshooting checklist and the results of the various steps.
- Any hunches you may have regarding the area in which the error occurs.
- All specifications which could be considered as contributing to the error (for example, software, changes in Customizing, shared mounts/ links, power failures, network problems).
- The relevant parts of the list printout from program RNCLST01 ( the first page with the system settings is usually enough)
- All following system specifications:
- operating system/version on IS-H side (application-, database server);
- SAP gateway release specification (see dev_rd);
- operating system/version on the non-SAP system side;
- transceiver release specification (see tracefile);
- Any "particular" messages (for instance from the system log, "CPIC-RC=" block, dev_rd, trace of the PUT_TAB program) (which could be) related to this error.
- Specify IS-H-CM as the application and report the current IS-H Release.
- Please classify the problem according to the following priority scale:
- Priority 1: "very high" (system stop!);
- Priority 2: "high" (considerable loss of production, functions missing or cannot be executed);
- Priority 3: "medium" (defective individual functions);
- Priority 4: "low" (development request, additional information).
Please fax all information only to the central SAP hotline.
If you are a user of the Online Service System (OSS), create your problem message in the usual way. Mention that you are sending additional information by fax (if this is the case). Please mark the first page of your fax clearly with Additional information for problem no...... (please ensure the problem number is legible). Once again, this information should only be faxed to the central SAP hotline. Upon receipt, this information is scanned and assigned to the problem directly.
The IS-H development team will then contact you as soon as possible.
Business Attributes
| ASAP Roadmap ID | 211 | |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-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_ISHCM_GD_ERRS | 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 |
| IMGDUMMY | D - Dummy object | ONC5 | 4 | Perform Installation Check | ||
| IMGDUMMY | D - Dummy object | ONCE | 4 | Create List of Partner System Settings | ||
| IMGDUMMY | D - Dummy object | SM21 | 1 | Evaluate System Log | ||
| IMGDUMMY | D - Dummy object | SM37 | 4 | Display Overview of Background Jobs | ||
| IMGDUMMY | D - Dummy object | ST11 | 1 | Evaluate Gateway Trace dev_rd |
History
| Last changed by/on | SAP | 20021206 |
| SAP Release Created in |
