SAP ABAP IMG Activity SIMG_CFMENUOKCMOKCC (Define sender structure for transaction data)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KC (Package) Cost Accounting Controlling EIS

IMG Activity

ID	SIMG_CFMENUOKCMOKCC	Define sender structure for transaction data
Transaction Code	S_ALR_87000045	IMG Activity: SIMG_CFMENUOKCMOKCC
Created on	19981222
Customizing Attributes	SIMG_CFMENUOKCMOKCC	Define sender structure for transaction data
Customizing Activity	SIMG_CFMENUOKCMOKCC	Define sender structure for transaction data

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUOKCMOKCC

CONCEPT INFORMATION

For every sender structure, you need to define the makeup of the records which will be transferred from a source system into R/3. This depicts the data record structure of the data to be transferred, which includes the order and technical description of the fields (field category, length, and text). In defining these structures, you can use existing structures and tables from the ABAP Dictionary (for example, receiver structures), or define your own sender structure. When using SAP structures and tables please note that these can change with a new release.

This Customizing function as well as the one for defining the transfer rules are used in various applications (such as EC-EIS, CO-PA, TR-TM and IS Banking). For each individual application there are several small differences in the functions, each of which is noted in the application.

Initial screen

On the initial screen you see a table of the sender structures already defined. When you implement R/3, this may be empty.

Overview screen

The input fields on this screen are divided into three areas:

• The upper part contains the input fields for the name (user-defined) of the sender structure to be defined, and for a short descriptive text.
• The middle part differs in the individual applications. It serves, for example, to assign the sender structure to an object (transfer type, aspect, characteristic, etc.), and also to enter necessary details.
• The lower part shows a table (in EC-EIS, several tables) in which you input the names of structures which already exist in the ABAP Dictionary, or the names of ones which you wish to define as new. If you use an existing structure, it has the disadvantage that you can not change it subsequently. If you want to define and include a new ABAP dictionary structure, the name always has to begin with 'RKCT'. You must then add three additional alpha-numeric characters of your choice. You define the new ABAP Dictionary structure in a detail screen.

Detail screen

In the detail screen you can define a new ABAP Dictionary structure or change one that you defined before.

To define the structure, you can either use a template in this screen, or define the structure yourself. The system will automatically generate a receiver structure based on the specifications for the object in the middle part of the previous screen.

If you want to define the sender structure yourself, you have two options. You can either define the sender fields yourself or use ones from the ABAP Dictionary.

In the first instance, you can choose the name yourself. Then you have to complete the following entries in the column:

• Meaning, as a short descriptive text;
• Category, field category (C, N, P, X, D, T, I, F);
• Length of the field;
• Decimal place, the number of decimal places (only for field category P).

In the second instance you enter the name of a field from the ABAP Dictionary in the column sender field in the table, and the name of the table in which it is found (reference table) in the column table. The entries are then automatically taken from the ABAP Dictionary.

For general information on creating structures see the SAP Library: BC-ABAP Workbench -> BC-ABAP Dictionary.

Actions

Edit the transfer structures in the following steps:

1. If you wish to edit an already existing sender structure, select the structure on the initial screen and choose Goto -> Select. If you wish to create a new sender structure, choose Edit -> New entries. In both cases you go to the initial screen for defining sender structures.
2. Enter the following information in the upper part of the initial screen:
• To create a new sender structure, determine the technical name and a descriptive text.
• To import data into an aspect in the current system, enter the number of the aspect. In this case you must leave the transfer category field empty.
• To export data from the current system enter the transfer category field. In this case you must leave the aspect number field empty.
• If you wish to have a validation carried out during data transfer, enter the name of a validation or matrix validation. (see also Maintain validations).
• If you wish to allow records with double keys in data transfer, set the indicator Double key. If the indicator is not set, data records whose keys already exist in the target system, will not be transferred.

3. In the bottom part of the screen enter one or more Dictionary structures. A Dictionary structure can be either a table, a structure or an EIS Dictionary structure. If you are using only a Dictionary structure in your sender structure, you can ignore the other fields in this area.
   If for example, you wish to transfer data from a file with header and position data, you must enter several Dictionary structures.

   
   Example:
   You wish to transfer data from an invoice. The invoice number, invoice date, customer number and company code are all contained in the invoice header. The positions contain the product number, the respective sales volume and the revenue. You wish to form data records in an aspect. These records should contain the information from both the header and the positions. In this case, you create one Dictionary structure for the header data and one for the position data.

   
   Each structure is indicated by a certain characteristic value from one specific position and in a defined length. Therefore it can be uniquely identified. When importing the data the system assumes that each record is formed exactly according to one of the structures. Internally, the different records are summarized to one logical record and processed.
   If you use several Dictionary structures, enter the position and, depending on the structure of the file, the offset, the length and the characteristic value, that should identify a record.

• If there is a table in the ABAP Dictionary which has an identical structure to the sender structure to be defined, you can refer to this table or structure. If you refer to a structure defined in the ABAP Dictionary, you can generate a remote function call (RFC) for this sender structure and use the RFC for a user-defined data transfer program. If the ABAP Dictionary structure contains only fields of type CHAR and NUMC, you can generate a C environment in the development environment. This C environment will call up the function module from C programs. The function modules are called:
  EIS_DATA_TRANSFER<ABAP Dictionary structure>.
  See also 'Programmer notes for data
  transfer'.
• If a sender program exists that uses a similar transfer structure, you can use it as a reference.
• If a structure exists in the ABAP Dictionary which has a similar structure to the structure which is to be maintained, you can enter this Data Dictionary structure under 'reference table'.

In the upper section of the maintenance screen, you must enter: the aspect to be supplied with data OR the transfer path that determines the type of data transfer. the name of a validation or a matrix validation, if you wish to employ

1. To define a Dictionary structure that you have just generated, highlight it and select 'Goto -> File'. On the next screen the structure of the sent record is described field by field. You must now maintain the following data for each field:
• the name of the field
• (if there is a field with the same properties in the Data Dictionary), the table in which it occurs (reference table).
  In this case, data from the ABAP Dictionary is put into the remaining fields of the line.
  If there is no field with the same attributes in the ABAP Dictionary, you need to enter
• the field name
• the field type (C, N, P, X, D, T, I, F),
• the length of the field and
• the number of decimal places (field type 'P' only).

  
  Notes:
  With the functions Sender structure -> Comparison with R/3 and Sender structure -> Comparison with R/2 , you can transfer a sender structure from an R/2 System or another R/3 System. When comparing with R/2, you must enter the system's transfer method in the following dialog box. When comparing with R/3, you must select an RFC destination. (You maintain the possible RFC destinations in the SAP R/3 menu under Tools -> Administration -> Administration -> Network -> RFC destinations).

2. Save the changes.

Further notes
Transport of settings

Business Attributes

ASAP Roadmap ID	252	Prepare Data Transfer Fields
Mandatory / Optional	2	Optional 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_CFMENUOKCMOKCC	0	HLA0009491	Data Collection

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
KCDM	L - Logical transport object	OKCC	OKCC	☐	☐	SAP-EIS: Sender programs and environment

History

Last changed by/on	SAP	19981222
SAP Release Created in