Solution : https://service.sap.com/sap/support/notes/49563 (SAP Service marketplace login required)
Summary :
The SAP note discusses methods for subsequent data transfer to Asset Accounting after a company code is already productive. Techniques include dealing with data stored in different systems or merging company codes. It applies to a staggered transfer scenario into the SAP R/3 system. SAP proposes two solutions; the first ensures consistent and clear financial statements, showing such transfers as current year acquisitions. The second allows using the legacy data transfer function with conditions like closing fiscal years before transfer and not reopening them. However, the second option restricts accurate data extraction into Business Warehouse and impacts period reporting.
Key words :
subsequent fiscal year solution sap supports, transfer fixed assets assigned, obtaining consistent financial statements, legacy data incremental reason, incremental data transfer carried, terms legacy data transfer, legacy data transfer function, consistent financial statements, solution produces clear, legacy data transfer
Related Notes :
| 1500830 | Extracting 0FI_AA_12 after mid-year legacy data transfer |
| 762911 | 0FI_AA_12: Extraction for subannual data transfer |
| 757228 | 0FI_AA_12, cost center, internal order, CO Controlling area |
| 738741 | 0FI_AA_12: Extraction during mid-year data transfer |
| 728479 | 0FI_AA_12: Extraction during mid-year convers. is incorrect |
| 550176 | FAQ note legacy data transfer asset master records |
| 110373 | Production startup with local currency Euro |
| 69225 | Reconciliation difference financial/asset accounting |