Ansicht
Dokumentation

The table is split into two logical parts:

• The left part shows the fields of the receiver structure, it has a gray background and cannot be changed. The receiver structure is determined by the details you specified when you defined the sender structure.
  
  

• The right part shows the fields of the sender structure and other fields for defining the rules.

If the sender structure of the data to be transferred matches the receiver structure, you can have the system generate an explicit MOVE rule (Rules-> Generate rule proposal). Fields for which no assignment could be generated appear with a color background.

Otherwise, in the column sender field, you can enter the name of the sender field that you want to assign to the relevant receiver field.

You can define that a value is only assigned to the receiver field if the sender field value contains a specific value that you define. Make the required entries here.

You can define further rules on a detail screen. To do this, you must select the row containing the receiver field for which you wish to define special rules.

There are two different detail screens for defining transfer rules. The one you use depends on whether the field for which you wish to define a rule is filled by a characteristic or a key figure:

• Characteristic fields are fields which fill the role of characteristics, attributes or classification terms in the R/3 System, for example company code, posting date, order number. From a technical point of view, these are fields of data type 'C', 'N', 'D' or 'T', which are generally not unit or currency keys, and have no purely technical significance, for example the client number.

• Key figure fields are fields which fill the role of key figures, values or balances in the R/3 System, for example sales, revenue, or headcount. From a technical point of view, these are mostly fields of data type 'P', and can be used in calculations.

You can use the following rules for characteristics:

1. Transfer sender field
   You assign the values of the sender field to the receiver field. However, you can only assign those sender fields whose type is compatible with that of the receiver field. For example, you cannot assign a field of type 'C' (any character string) to a field of type 'T'(used to store times). This prevents the field from acquiring invalid values. Using Restrict value area you can determine that only the sender field value specified by you is transferred to the receiver field. You can also specify conditions for other sender structure fields so that the transfer will only take place if the data record contains certain values.
2. Set constants
   You assign a fixed value to the receiver field from the range of permitted characteristic values. This value is then used for all transferred data records.
3. Set variable
   You assign a variable to the receiver field (see "Create variables" below). This allows you to fill the field when you are carrying out the transfer. You can for example, specify the company or the company code for each file to be imported.
   Besides this, it is also possible to enter a fixed value for the variable. In this case the behavior during data transfer is similar to that of a set constant - the difference is that the constant fixed value can be used elsewhere in the system using the variable name. This way you can improve the consistency of data transfers.
4. Convert sender fields
   You assign certain sender field values to a receiver field value. You must specify the sender fields that are to be included in the conversion.
   By specifying an Offset and a Length, you can determine that only a part of the sender field is used.
   It is also possible to specify a conversion routine. This is carried out on the sender field value before the conversion. The conversion routine is required to fill fields with leading zeros for example.
   Choose Conditions to get to a screen where you specify what values the sender fields must have, in order to be converted to a certain receiver field value. Enter the target values for the receiver field in the left column. In the following columns enter the individual values or intervals for the sender fields. For a receiver field to receive the specified value, all sender fields must have their specified values. If different sender fields are to be converted to the same receiver field value, you select the row and choose the pushbutton to the right of the field. A symbol to the right of the field and the color of the pushbutton itself shows that there are several conditions.
   You can specify complex rules of several lines for receiver field values. When the rules are worked through, the first suitable one is applied. However, the sequence in which the rules are worked through is not defined. You can also explicitly set the initial value as the receiver field value.
5. Use general rule
   For the data transfer, you specify a general rule that is already defined. You can define general rules when you use one of the options above. You make the settings and then determine them to be a general rule. Enter a unique technical name and a description in the field Use rule defined here as a general rule. After you have saved it, you can use this general rule for other transfers.
   Suppose for example that in data transfers you always wish to assign company code 0002 to company code 0003. You have created a general rule for this and you now reference this rule for the characteristic company code. When you select this rule, the fields to be converted are displayed.
   Note: whenever a general rule is referenced, it can no longer be deleted. If you still wish to delete it, you can compound it with the referencing rule.

In some applications you can decide what happens when a characteristic value contains no value in spite of the rules.

• Set at initial value
  The field acquires the initial value.

• Classify as an error
  The field is registered as an error. In this case the transfer terminates.

• Set constants
  You assign a constant value to the field from the range of permitted characteristic values.

• Copy sender field
  You assign the value of a predetermined sender field to the field.

EC-EIS only:

You can determine whether a receiver field value is to be validated or if it is to undergo a special output/ conversion routine. For more information about conversion routines, see F1-Help.

In the detail screen, you determine how the key figure values are to be aggregated, how currencies or units are to be translated, and how the key figure is to be mapped to the receiver key figure.

EC-EIS only:

You can determine whether the key figure in the database is to be overwritten or not. If it is to be overwritten, then the value determined from the sender records overwrites the value in the database. If the key figure in the database is not to be overwritten, then the key figure value is read from the database. This value is taken as the starting value for the total operation. This option may or may not be desirable depending on the application.

Specify a total operation. The following alternatives are available:

• SUM
  The sum of the sender field values is transferred to the receiver
  record.

• MIN
  The smallest sender field value transferred is entered in the receiver record.

• MAX
  The largest sender field value transferred is entered in the receiver record.

• FIRST
  The first sender field value transferred is entered in the receiver record.

• LAST
  The last sender field value transferred is entered in the receiver record.

• COUNT
  The number of sender field values transferred is entered in the receiver record. This total operation is usually only logical in connection with formula '1' (see 'Formulas' below).

Using conditions, you can determine that a key figure is only filled when a sender field accepts specific values. This function is necessary in the following example:
The sender structure contains the fields balance sheet item and balance. The receiver structure contains the key figures AKTIVA and PASSIVA. You can now define that the key figure AKTIVA is only filled when the balance sheet item field contains the value 10000000.

Other applications:

Enter the total operation SUM. The sender field value is transferred to the receiver field.

Enter a unit for quantity fields where no proposal exists.

For quantity fields, you can have a unit translation carried out and for currency fields, a currency translation.

Concerning the currency translation, you can determine which exchange rate, which exchange rate type and which currency you wish to translate into the target currency. You can either specify fixed values for the currency and the translation date, or reference fields which contain the currency and the translation date. You can also use a variable for the currency translation key.

Note: For all users of external data transfer except in the CO-PA application, the following applies to the amount fields:

In the SAP System, currency amounts are always written to the database with two decimal places. Amounts in currencies that, according to the currency definition, have more or less than two decimal places, must be transformed to this SAP format. See example:

The SAP System expects currency amounts to be delivered with the regular decimal places. To store the currency amounts in SAP format in the database, the field reference sender field must be filled in the transfer rule for currency amounts (this also applies if you transfer the fields without explicit rules using identical names). This guarantees that, after the conversion, the amount is available to the SAP System with the correct number of decimal places for the specified currency. If you import currency amounts from an SAP System (data in binary format), the host system expects the data to be in the correct format for storing in the database.

In some applications you can specify one of the sender fields as a currency reference field. This way you can make the target currency dependent on the specified reference field, rather then fixing it.

You define the formula in the field Key figure-formula row. The key figure formulas are created according to the valid ABAP rules for terms. You can calculate with the sender fields. To see the valid sender fields, position the cursor on the entry field and press F4. You can also use formula variables in the formula.

As with transfer rules for characteristics, you can save the current rule as a general rule. To do this, enter a name for the rule in the field 'Use as a general rule'.

If you want to use a general rule for the transfer, enter the name of a rule stored in the system in the field General rule. The sender fields to be converted will appear.

You can create variables for characteristic values, formulas, and translation keys to be used for transfer rules. Variables for formulas and translation keys can be used globally. Variables for characteristic values can only be used for the object that you are currently working on. To create variables, on the detail screen choose Goto → Variables → Translation key or Goto → Variables → Formula variables. On the next screen, choose Edit → Insert row or use an empty row if available. To define a variable, proceed as follows:

1. Enter the variable name in the column Variable name. The first character of the name must be '&', followed by a letter (the system will place the '&' before the name automatically if necessary). The total length of the name may not exceed 10 characters (including the '&').
2. Select the desired Replacement type. With replacement type 2, you can determine the variables at the start of the data transfer (this is currently supported only for the import of files and for aspect summarizations). With replacement type 5, you must also enter a fixed value in the next column. To use the replacement type 3, you must activate the function module EXIT_SAPFKCIM_003 as part of a User Exit.
3. Enter a description for the variable.
4. Save your entries.