SAP ABAP IMG Activity SIMG_CFMENUOKCMOKCG (Define transfer rules)

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_CFMENUOKCMOKCG	Define transfer rules
Transaction Code	S_ALR_87000033	IMG Activity: SIMG_CFMENUOKCMOKCG
Created on	19981222
Customizing Attributes	SIMG_CFMENUOKCMOKCG	Maintain transfer rules
Customizing Activity	SIMG_CFMENUOKCMOKCG	Maintain transfer rules

Document

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

In this step you specify how fields of a source object are mapped onto a target object. Objects can, for example, be master data, a transaction data record or an IDOC segment. The rule maintenance is used for different purposes. For example, it serves to define how the records of a file are mapped to master data or to define derivation rules for transaction data. With a derivation a transaction data record is supplemented with missing characteristic values (derived). Another application is the definition of the conversion of IDOC segments. Here, the values of the fields of a segment are changed.

Different options per object

The objects have different structural properties. For example, the validity of transaction data depends on master data. Therefore, the option of validating the values against master data is offered with the maintenance of the rules for transaction data. With the rule maintenance for master data this option is not necessary and is not offered. This means that different options are offered with the rule maintenance, depending on which object is being edited.

Sender and receiver structure

With the maintenance you determine how the fields of the sender structure are mapped to fields of a receiver structure. We refer to a receiver structure as we are dealing with a number of selected fields that define an object in R/3. The sender structure displays the record layout of the transferred data. It describes the formation of the transferred data byte for byte. Contrary to this, the fields of a receiver structure are derived from the object that is to be updated. Either you enter this object in the sender structure maintenance or it is fixed for some applications. Therefore, some fields do not appear, such as the client, the last changer, the change date or the currency keys that are supplied on an application-specific basis. You assign a variable to the receiver field. This allows you to enter the field when executing the data transfer. You could, for example, enter the company or the company code for each file to be imported.

The initial screen

The initial screen is application-specific. On the first screen, you establish either the sender structure for the data transfer, or the conversion rule for the segment conversion or the aspect for the derivation. You have to decide on the type of the editing.

The overview screen

On the second screen you will find a tabular arrangement of the fields of the receiver structure. Here, you can enter the most commonly used rules. These rules differ depending on the type of the field:

With characteristic fields you can enter a sender field that should be transferred. Characteristic fields are those that have the role of characteristics, attributes or evaluation groups in R/3, such as company code, posting date, order number. Technically speaking, we are dealing with fields that have data type 'C', 'N', 'D', or 'T', and as a rule are not unit or currency keys and do not have a purely technical meaning like the client.
With fields that take on the role of key figures, values or balances in R/3, you establish a formula. Technically speaking, we are dealing with fields that can be calculated. The data type is usually 'P'. In addition, you can determine a currency translation key or a target unit. You must enter a total operation. The total operation determines what happens to the values if several records are mapped to the same receiver. The sender field has a different meaning here to in the characteristic fields. The entry of a sender field only makes sense together with the entry of a sender field value. The entries mean that a value for the receiver record can only be calculated if the sender field possesses the sender field value.

If you want to define other rules, you must highlight the field in order to get to the detail screens of the rule maintenance.

The detail screen of the rule maintenance of characteristics

You can use the following rules for characteristics:

Transfer sender field
You assign the values of the sender field to the receiver field. You can not assign every sender field. The system checks whether the types are compatible. For example, a type 'C' field (various combinations of letters) may not be assigned to a type 'T' field (used for storing times). This prevents fields from receiving invalid values. With Restrict value area you can restrict the values of the sender field that are to be transferred to the receiver field. In addition, you can enter the conditions for other fields so that the data transfer only takes place if the data record also contains certain values.
Set constants
You assign a fixed value to the receiver field.
Set variable
You assign a variable to the receiver field. This allows you to enter the field when executing the data transfer. For example, you can enter the company or the company code per file to be imported. In addition, it is possible to supply the variable with a fixed value.
Convert sender fields
You assign certain values of the sender field to a value of the receiver field. Within 'Sender fields to be converted' you establish the selection conditions for the values of the sender fields, that should be assigned to the receiver field value. For this, you must enter the sender fields that are to be converted.
With the entry of an offset and a length, you can determine that only part of the sender field is used.
It is also possible to enter a conversion routine. This is executed before the conversion to the sender field value. The conversion routine can be required for filling fields with leading zeros.
With Conditions you get to a screen upon which you fix which values the sender fields should have for values of the receiver field. In the left column you enter the (target) values of the receiver field. In the following columns you enter single values or intervals for the sender fields. So that a receiver gets a values, all sender fields must accept the specified values. If it should be allowed to accept more than one value, you can highlight the rows and depress the push-button on the right of the field. An icon to the right of the field indicates that there are several conditions. You can maintain several rows for a receiver field value. With the rule processing, the first suitable rule is used. However, the sequence of the rules in the processing is not defined. The initial value can be explicitly set for a receiver field value as well.

Using the general rule
You enter a rule that should be used for several transfers. For example, you want to always assign company code 0002 to company code 0003 with transfers from an R/2 System to an R/3 System. You have created a general rule for this that you now reference for the characteristic company code. If you choose this rule the sender fields to be converted of the general rule will be displayed.

You can decide that the rule that you are currently maintaining should be used as a general rule. Enter a name and description for it in the field 'Use rule defined here as general rule'. As soon as this rule is referenced it can no longer be deleted. If you want to delete the rule anyway you can reassign it to the referencing rule.

Application-dependent options

With some applications you can decide what happens if a characteristic value does not contain any values, in spite of rules:

Set to initial value
The field contains the initial value.
Classify as error
The case is registered as an error.
Set constants
A constant value is assigned to the field.
Transfer sender field
The value of an exceptional sender field is transferred.

Depending on the application, it is possible to establish whether a receiver field value should be validated or whether the receiver field value should run through a special (output) conversion routine. You can find detailed information on conversion routines in the F1 help.

Application-specific peculiarities

If you maintain transfer rules for compound characteristics, you should note some peculiarities:

You must maintain rules for each field. Therefore, no differences are made between compound and non-compound characteristics. If you convert sender fields, the characteristic value that is converted, is not validated in the rule maintenance. You must make sure that this characteristic value is correct.
However, with the data transfer a complete validation is carried out for the compound characteristic. Meaning, a check is made as to whether a c

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_CFMENUOKCMOKCG	0	HLA0009491	Data Collection

Maintenance Objects

Maintenance object type

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	OKCG	9999999999			Maintain transfer rules

History

Last changed by/on	SAP	19990115
SAP Release Created in

Object Hierarchy

Used by

Advertise Links