Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
IMG Activity
| ID | _FICABFCA_BULK | Define Carryforward Rules |
| Transaction Code | S_KK4_74002317 | IMG Activity: _FICABFCA_BULK |
| Created on | 19990816 | |
| Customizing Attributes | _FICABFCA_BULK | Define Carryforward Rules |
| Customizing Activity | _FICABFCA_BULK | Define Carryforward Rules |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _FICABFCA_BULK |
In this activity, you specify how the sender structure fields are to be shown in the receiver structure fields. If the sender and receiver structure are similar, then transfer rules will usually not be necessary. Field contents are generally transferred 1:1. If you still want to make changes, you can define transfer rules.
You can adapt transfer rules to new requirements at any time. When you change the transfer rules, you do not need to regenerate the transfer programs.
There are two aspects to maintaining transfer rules:
- Supplying the characteristics of a receiver structure with data
- Supplying key figures (value fields and quantity fields) of a receiver structure with data.
Recommendation
Generate a rule proposal and adapt it to your requirements (in maintenance mode for characteristics or key figures, choose Utilities -> Generate rule proposal). The rule proposal produces a 1:1 allocation of sender and receiver fields. Fields that could be allocated are highlighted in gray. Fields shown in red indicate that allocation was not possible.
Requirements
You must have defined a sender structure .
Activities
- Enter the name of the transfer program (such as DI_ACCOUNT).
- From the menu select: Rules -> Maintain.
- The left column Receiver fields contains default values. This comes from selecting type 73 in the activity Define Sender Structure.
- From the menu select Rules -> Generate rule proposal
- The right column Sender fields is provided with entries following the settings made in the activity Define sender structure.
- Select Save. This provides a 1:1 transfer between the sender fields and the receiver fields.
- Select Back.
Further notes
We recommend that the sender structure and the receiver structure are as much alike as possible. To ensure this, select the corresponding format beforehand in the data selection programs.
If your operational system sender structure does not provide data in the proposed structure, you can change this data if necessary.
To obtain more information on the points to be changed and on processing the rules, we suggest that you create an OSS message.
Business Attributes
| ASAP Roadmap ID | 253 | Create Data Transfer Programs |
| 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 | _FICABFCA_BULK | 0 | I210007303 | Contract Accounts |
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 |
| OKCG | T - Individual transaction object | OKCG | FICA0001KK | Carryforward Rules |
History
| Last changed by/on | SAP | 19990816 |
| SAP Release Created in |
