Hierarchy
⤷ 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
Basic Data
Data Element | ISHFUNAM |
Short Description | Name of Function Module/Check Routine to Be Executed |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FUNCNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table | TFDIR |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 8 | Check |
Medium | 10 | FM Name |
Long | 20 | Function Module |
Heading | 30 | Name of Check Routine (FM) |
Documentation
Definition
Name of the check routine/function module that is to be executed.
When the HCM monitor is called, these are, for example:
ISHCM_MONITOR_NC01
Checks whether the order file contains old orders
Possible parameters:
PARAM1 Numer of days after which a message is considered to be old
Type: integer
Default: 2
PARAM2 Number of days after which a message is considered to be old
(in combination with parameter 1)
Type: integer
Default: 0
ISHCM_MONITOR_NC02
Checks whether the dispatch table contains old dispatch messages
Possible parameters:
PARAM1 Number of days after which a message is considered to be old
Type: integer
Default: 2
PARAM2 Number of minutes after which a message is considered to be
old (combined with parameter 1)
Type: integer
Default: 0
ISHCM_MONITOR_SYS_AVAILABILITY
Monitors the availability of the partner system
Possible parameters:
PARAM1 Number of days afer which a message is considered to be old
Type: integer
Default: 2
PARAM2 Number of HCM transfer attempts. If after this number of
of attempts the message has still not been transferred, you
are informed.
Type: integer
Default: 2
PARAM3 Number of minutes after which a message is considered to be old
(im conjunction with parameter 1)
Type: integer
Default: 0
ISHCM_MONITOR_NC00
Checks how many dispatch logs exist in NC00
Possible parameters:
PARAM1 Number of entries in table NC00 which signal an overflow and
demand the start of RNCUTL09
Type: Integer
Default: 100 000
ISHCM_MONITOR_NCI0
Checks how many inbound logs exist in NCI0
Possible parameters:
PARAM1 Number of entries in table NCI0 which signal an overflow and
demand the start of RNCUTL14
Type: Integer
Default: 100 000
ISHCM_MONITOR_BDC_RECEPTION
Checks whether incorrect batch input sessions exist
Possible parameters:
PARAM1 Ending of incorrect batch input sessions
Type/length: Character 4
Default: _ERR
ISHCM_MONITOR_RECEIVER_CUST
Checks the Customizing entries of the monitor for e-mail recipient
Possible parameters:
None
ISHCM_MONITOR_301_WORKLIST
Monitors the number of EDI received messages to be processed
Possible parameters:
For monitoring the incorrect messages in table NC301W:
PARAM1: Number of messages after which the work list is considered to
be too great and fast handling is required.
Type: integer
Default: 50
PARAM2 Number days after which a message is considered to be overdue.
Type: integer
Default: 3
For monitoring the imported messages in table NC301V:
PARAM3: Number of messages after which the work list is considered to
be too great and fast handling is required.
Type: integer
Default: 200
PARAM4 Number of days after which a message is considered to be overdue.
Type: integer
Default: 3
ISHCM_MONITOR_NC301TX
Checks whether files were copied from the communications server without further processing and must still be imported.
Possible parameters:
PARAM1 Number of days from which a file is considered to be not processed
Type: integer
Default: 0
PARAM2 Number of minutes from which a file is considered to be not
processed (combined with parameter 1)
Type: integer
Default: 10
ISHCM_MONITOR_NC301P
Checks the Customizing entries (master date) of the data collection points.
Possible parameters:
none
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |