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_CFMENUNMO4ONRB | Data Transfer - Define Structures |
| Transaction Code | S_KK4_74000154 | IMG Activity: SIMG_CFMENUNMO4ONRB |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_CFMENUNMO4ONRB | Data Transfer - Define Structures |
| Customizing Activity | SIMG_CFMENUNMO4ONRB | Data Transfer - Define Structures |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUNMO4ONRB |
This IMG activity tells you how to describe the record structure of the sequential data set you are using. You need to have made this description for the transfer program to process the data correctly.
This description essentially involves assigning the data from the data set to the fields of the transaction. You make this assignment by specifying the field length and offset.
If the data is to reformatted prior to transfer, you can specify a format conversion routine for this purpose.
You can use the identifications delivered in the standard system (RNIPST, EBM, etc.) as templates for your own identifications (name range Z...).
Example
Date record structure for the patient master record: (# are filler fields)
PAT#Miller#######Peter#555555####
- The length of the Last Name field is 13 and its offset 4.
- The length of the First Name field is 6 and its offset 17.
- The length of the Patient Number field is 10 and its offset 23.
Activities
You make an entry for the data structure definition by specifying:
- The identification in the ID field.
- The record type in the RT field. This step is optional, in other words, it is not required for a file with a single structure.
- A subrecord type in the SR field. This step is necessary only if your sequential data set contains subrecord types.
- The technical name of the screen field you want to fill with data from your record in the Screen Fd. field.
- For fields that are repeated in a screen (known technically as step loop fields), for example several columns of a service catalog, specify the line number in the Cl.
- The number of characters before the start of the field in the Offset field.
- The length of the field in the Lngth field.
- If you want to reformat the data that has been imported before transferring it to the transaction, specify a FORM routine and a program for this purpose. Please refer to the documentation on this fields that contains information about creating FORM routines. Program RNILSI20 contains examples of FORM routines.
Further notes
In the data structure description, you only describe the position of the data you want to transfer. You specify the position of the record types on the selection screen of the transfer program.
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| 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_CFMENUNMO4ONRB | 0 | I041002051 | Tools |
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 |
| TNT2 | S - Table (with text table) | ONRB | 1 | Maintain Structure Definition for Data Transfer |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
