Migrating Fixed Assets into SAP

This document will discuss loading fixed assets using the standard load program RAALTD01, although two alternatives are briefly discussed. You will also be guided for how to overcome the common problems in migrating fixed assets into SAP. Following are covered in this guide;

  • Load Methods (BDC recording of transaction AS91, Business object BUS1022, Standard load program RAALTD01)
  • Data structures in the asset load program RAALTD01 – BALTD and BALTB
  • Common problems (Alpha conversion, Missing customising, Legacy asset number, NBV – Net book value, Time-dependent data, Mid-year asset migration, Assets created in this year, Asset disposals, Depreciation areas

Read more

Yet Another Great Step by Step LSMW Tutorial

In an SAP R/3 implementation the data from legacy system (non SAP R/3) needs to be transferred to the SAP system. Periodic data transfer between R/3 and other system (interfacing) is also required. Both of the above form a part of data migration. In SAP, known tools for data migration are:

  • BDC (Batch Data Communication)
  • LSMW (Legacy System Migration Workbench)

This document presents high level view of LSMW and to provides you information about how to use this functionality. Following are the headlines from this study material:

  • Difference between BDC & LSMW
  • What is LSMW ? Principles, Features and Pre-Requisities for LSMW
  • Import methods defined: IDOC’ s,BAPI’s, Standart/Direct Input, Batch Input
  • Step by step procedures for using conversion tool LSMW
  • Step by step procedures for Direct Input Method, Batch Input Method, BAPI in LSMW and so on..

Read more

SAP Press Books Sample Chapter Collections – Part 3

If you are new to this series, click to see all parts created under SAP Press Sample Chapter Downloads. Here is the third part of series you will find useful information about

  • Enterprise SOA definition and Enterprise Data Management’s role in it
  • An extended overview of SAP ERP HCM Components
  • Specs and business processes for 850-Interface ORDERS interface within EDI
  • An Overview of Procurement in Logistics
  • Special features of SAP APO and Advantages of planning with APO-PP/DS.
  • Introduction to SAP Upgrade Tools

Read more

IDOC Structures

The Idoc Structure consists of 3 parts –

1) The Administration Part – It  has information about the type of idoc,message type, the current status,the sender, receiver,direction (inbound or outbound),channel etc.This is   referred to as the Control record.

Read more

IDOC Useful Notes

1, In main business scenario of using IDOC: Company A(R/3)–(IDOC)–EDI Subsystem–(Message)–EDI subsystem–(IDOC)–Company B(R/3)
In this scenario: Both companies have R/3 system and must configure their IDoc interface accordingly. The IDoc are to be translated into another EDI standard form.

2, IDoc stand for intermediate document. It is intermediate in two respects:
Message-oriented–Data is also stored in application, only in other formats(the application documents).
Asynchronous–Data can be stored in IDocs before an application document is created.

Read more

Basics of IDoc

An IDoc (intermediate document) is a standard data structure for electronic data interchange (EDI). IDocs are used for the data interchange between SAP systems as well as between an SAP system and an external system. IDocs serve as the vehicle for data transfer in SAP’s Application Link Enabling (ALE) system. The contents, structure, sender, receiver, and current status of the IDoc are defined in the IDoc header.Data acquisition from an SAP source system is a very common scenario in SAP BW. This process involves extracting the data using either standard business content-provided extractors or custom-built extractors.
Failure of data to load usually leads to loss of productive time in re-triggering the extraction.

Read more