Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-DP-EDT (Application Component) External Data Transfer⤷
JBB (Package) SAP Banking: External Data Transfer; Generated Objects
IMG Activity
| ID | UEBERTRAG_BANK | Define Carry Forward Rules |
| Transaction Code | S_KFM_86000080 | (empty) |
| Created on | 20000629 | |
| Customizing Attributes | UEBERTRAG | Define Transfer Rule |
| Customizing Activity | UEBERTRAG_BANK | Define Carry Forward Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFJB01JBLK |
Note:
You should only define the transfer rules here if you intend to deviate from the standard 1:1 assignment or if you wish to transfer currency amount fields.
If you do not make any definitions here, then the standard transfer will run, with a 1:1 transfer of fields from sender to receiver structure. This method has clear performance advantages.
There are, however, certain restrictions:
- The contents of some fields will be transferred even though they should not be. In this case, you have to define the transfer rules for the receiver fields which should not be filled with data (which should remain initial). To do this, you assign the rule "set at initial value" to the relevant receiver fields in the detail screen (see below). If you do not assign a rule to a receiver field, the system will use the default assignment of 1:1.
Alternatively, you can fill the fields in your sequential file so that they do not contain any data which is not to be transferred.
- No technical conversions will be made (for example, currency translations or decimal place corrections for currency entries).
- As before, no consistency checks are carried out for the sender field values: Are the date values or the packed numbers plausible? Initial fields must, therefore, be initial to start with. Number, date, or time fields are always initialized with zeroes.
To summarize: If no transfer rules are defined, then the entire conversion part of the external data transfer is replaced, from a technical point of view, by move-corresponding instructions from the sender to the receiver structures. Usually, this will only lead to a correct result if the data has already been specially prepared for R/3, or if it originates from another R/3 System.
Note:
If you use the function Start With File Splitting, in the case of transfer types with header position structures, the fields that clearly identify the object to be transferred must be taken (with unchanged names) from the sender structure proposal and delivered with contents. These field names are listed in the documentation on the transfer types.
If you start the transfer Without File Splitting, these fields must still be delivered but their names may be changed in the sender structure.
CONCEPT INFORMATION
In this activity you define how and which sender structure fields are mapped to the receiver structure fields.
Requirements
You must define the sender structure before you can determine the transfer rules.
Initial screen
Here you assign the transfer rules to the relevant sender structures. Enter the name of the sender structure for which you want to define or change the transfer rules. Choose Rules-> Maintain to get to the overview screen Maintain rules for <name of sender structure
Overview screen
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.
Detail screen
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.
Detail screen for 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. 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. - 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. - 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. - 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. - 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
Business Attributes
| ASAP Roadmap ID | 308 | Transfer Data to Live System |
| 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_CFJB01JBLK | 0 | I290007530 A N AEC0000003 |
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 |
| KCFR | T - Individual transaction object | KCFR |
History
| Last changed by/on | SAP | 20000629 |
| SAP Release Created in | 462_10 |
