Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
AC (Package) Application Development R/3 Assets: Customizing
IMG Activity
| ID | ORFA_TRANS | Define Transfer Variants |
| Transaction Code | S_ALR_87009059 | IMG Activity: ORFA_TRANS |
| Created on | 19981222 | |
| Customizing Attributes | ORFA_TRANS | Define Transfer Variants |
| Customizing Activity | ORFA_TRANS | Define Transfer Variants |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ORFA_TRANS |
In this step, you define transfer variants. Transfer variants contain the following control parameters for intercompany asset transfers:
- transaction types for posting the transactions that belong to an intercompany transfer (retirement/acquisition).
- the transfer method for the capitalization of the transferred assets in the target company code
In addition, you can specify in each transfer variant which master data fields should be copied from the transferred asset to the target asset, if a new asset has to be created in the target company code.
Note
The definition of the retirement transaction type specifies whether the retirement affects current-year acquisitions or prior-year acquisitions. For this reason, you need two different transfer variants (with different transaction types, such as 230 and 275) for the transfer of prior-year acquisitions and current-year acquisitions.
Standard settings
SAP provides sample transfer variants. These transfer variants use transaction types for the transfer of prior-year acquisitions (not for current-year acquisitions).
Activities
- Check the company code relationhip of the company codes involved:
- identical company ID => single legal entity
- different company IDs => legally independent entities
- Define transfer variants:
- Specify the transfer method to be used.
- Specify the retirement and acquisition transaction type for the intercompany asset transfer.
You can make your entries dependent on the relationship of the company codes and the cross-system depreciation area.
If you do not have cross-system depreciation areas, you can enter '*' in that key field. The system then uses this entry
- dependent on the specified company code relationship and
- for all depreciation areas that have a key that agrees with the company codes involved
- Specify the field contents that should be copied to the target asset during intercompany transfer, for
- general master data fields
- depreciation terms/cross-system depreciation area
in the asset master record.
Further notes
For more information, particularly about restrictions due to the allowed transaction types, see the SAP library FI-AA: Transactions -> System Settings for Intercompany Asset Transfers.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | ORFA_TRANS | 0 | HLA0001324 | Asset Transfer |
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 |
| VC_T082I01 | C - View cluster | SM34 | ORFA | Specify Transfer of Fields (for New Asset in Target CoCd) | ||
| VC_TA1TV01 | C - View cluster | SM34 | ORFA | Define Transfer Variant | ||
| V_001_B | V - View | OBY6 | ORFA | Check Company ID of Company Codes |
History
| Last changed by/on | SAP | 19990222 |
| SAP Release Created in |
