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_CFMENUNMO4SM36 | Define Background Jobs |
| Transaction Code | S_KK4_74000140 | IMG Activity: SIMG_CFMENUNMO4SM36 |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_CFMENUNMO4SM36 | Define Background Jobs |
| Customizing Activity | SIMG_CFMENUNMO4SM36 | Define Background Jobs |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUNMO4SM36 |
Use
In this IMG activity, you define jobs for background processing (batch operation). This is the same function that you can call from the system menu.
Prerequisites
Depending on their purpose, you should respect the following naming conventions for the IS-HCM jobs. "xxx" is the client in which the job was defined and runs. This specification is important if you operate several clients, but can be omitted if only one client is operated.
ISHCM_DISPATCH_xxx (RNCBLD00, RNCSND01)
ISHCM_GET_DIAGS_xxx (RNCCDERR, RNCGET02)
ISHCM_GET_OUSRV_xxx (RNCCDERR, RNCGET04)
ISHCM_GET_SERVS_xxx (RNCCDERR, RNCGET01)
ISHCM_GET_SURGS_xxx (RNCCDERR, RNCGET05)
ISHCM_CLEAR_PROTOCOLS_xxx (RNCUTL09A, RNCUTL14, RNCUTL16, RSBTCDEL)
Activities
- Specify job class "C". Do not save yet.
- Choose Steps. The Create Step 1 dialog box appears. Enter the name of the program in the Name field. If required, enter a variant and choose Save. If no variants exist, create a variant in accordance with your requirements. You exit the displayed step list by choosing Back.
- In the Job Start group box, specify the date/time when the job is first to run (Immediate or Date/Time). Flag the Periodic Job checkbox. You can then specify the required frequency under Period Values and save.
Note
For the different cases, check precisely which frequency is the most useful. Shorter periods immediately result in a higher system load; longer periods are better in this respect.
SAP recommends the following frequency:
- Format existing dispatch orders for messages and distribute them directly at six-minute intervals;
- Do not retrieve case-related diagnoses from partner systems. Instead, these diagnoses should be 'delivered' by the subsystems (up-to-date). If you want to retrieve them, set a ten-minute interval;
- Retrieve performed services once a day (in the evening or at night);
- Retrieve surgical data once a day (in the evening or at night);
- Delete "older than...days" logs once a week.
Save your start values, and then the job request itself. Your job is now scheduled.
Business Attributes
| ASAP Roadmap ID | 401 | |
| Mandatory / Optional | 2 | Optional 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_CFMENUNMO4SM36 | 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 | SM36 | 1 | Define/Create Background Jobs |
History
| Last changed by/on | SAP | 20021206 |
| SAP Release Created in |
