Fixed Asset Audit

SAP Data Migration - Migration of capital

1 Overview

1.1 Introduction

This document is designed as a user guide in how to overcome common problems in the migration of capital in the SAP system.

To convert a time in the SAP system, we favor using the LSMW tool. It lets you harness the power of ABAP while using the standard functions of SAP treatment, but a lot of file management and processing work automatically. However, even within LSMW there are a number of possible methods for the migration of fixed assets.

This paper will discuss the allocation of fixed assets using the standard loader RAALTD01, although two alternatives are briefly discussed below.

1.2 Methods charge

1.2.1 BDC recording the transaction AS91

This is the simplest solution and therefore it may be appropriate for transfer very basic. For example, if you do not create fixed assets in SAP, but rather updating a field in fixed assets that already exist in the system, then this might be the right approach. But it is not flexible enough to be used for creating data assets.

1.2.2 Business object BUS1022

This would create IDOCs type FIXEDASSET_CREATEINCLVALUES01 and processes through the SAP BAPI function BAPI_FIXEDASSET_OVRTAKE_CREATE.

Perhaps the SAP recommends. SAP BAPI is keen on as they are powerful, flexible and can easily be called from an external system via an RFC. But this does not necessarily make the right choice for data migration. BAPI structure is not always very intuitive and the initial development work can be complicated.

Also this method involves the processing of IDOCs. Although the standard error of treatment and reprocessing capabilities for IDOCs in SAP is impressive, it is not always transparent. Migration of fixed assets using this method would be appropriate for someone who is particularly strong in the field of BAPIs and IDOCs ..

1.2.3 loader Standard RAALTD01

This is usually the approach I would favor the migration of capital into the SAP system.

The standard loader is not perfect. As we shall see, there are one or two areas where it does not cover and as many standard SAP programs, it has its quirks: for example, when you loaded the asset, you do not have the ability to create even a BDC session if the transaction calls fail, the program will create a BDC session for these records.

However, it is a powerful and flexible, and it is relatively simple to use. The fact that you can carry the burden of the asset test mode before creating the data is also a major asset, even if the test does not always take 100% of the errors.

1.3 Assumptions

This document assumes a working knowledge of LSMW and at least some basic understanding of the data structure of fixed assets in SAP.

2 Basics

2.1 Data Structures

There are two data structures in the program for calculating assets RAALTD01 - BALTD and BALTB.

2.1.1 BALTD

This structure is mandatory and contains all the basic data set of immobilization.

2.1.2 BALTB

This structure is the so-called asset transactions. The two common scenarios in which this structure needs to be populated are:

a) An asset was capitalized after the beginning of the current year (fiscal year is the year you will migrate these assets in SAP), or

b) An asset has been eliminated in the current year

2.2 Important Fields

key areas:

number of active
Asset subnumber
Company code
asset class
Legacy main asset number
Legacy in the number of active
SAP transaction
Record Type

Baseline:

Comments

There are no comments.

Leave a Comment