Step by Step Procedure for Archiving IDocs

IDocs are archived in several tables and to reduce the load on Database without losing any IDocs, you can store them in archives at the operation level. Keep in mind that IDocs with error status can not be archieved. You can archive IDocs with status 3,18,19,21,31,33,38,40,41,53,57,68,70,73. If you are not able to archive IDocs with these status codes you can enable archiving option by using transaction code WE47. You are recommended to archive your IDocs if they are not older than 5 years, for those older than 5 years you may not need them anymore so you can delete them at your own risk. Read more

LSMW Overview

Legacy System Migration Workbench (LSMW) is a graphical tool provided by SAP R/3 for migrating data from a Legacy System into SAP. This tool is available through an SAP standard transaction code ‘LSMW’.

-The actual data upload takes place from a specific transaction depending upon the requirement such as MM01 (Create Material Master).
-The data to be uploaded is entered in a Flat File (such as a text file). This text file is uploaded into a Batch Input Structure through the interface of LSMW.
-After populating the data into the Batch Input ructure, the LSMW transaction generates a Batch Input Session with a name. The session is then executed through transaction SM35 (Batch Input: Session Overview). Read more

ABAP/4 Query

ABAP/4 Query is powerful tool to generate simple reports without the need for any coding. This is a very handy tool for the functional
consultants who don’t have any prior programming experience. This document is not meant to teach ABAP/4 Query completely but is meant to give a lead to learn it.
In order to create an ABAP/4 Query, one has to do the following:
1. Create an User Group
2. Create and Functional Area.

In the functional Area, one has to mention how the data in the query is coming from (i.e. through a logical database or from an individual table using a program or joins etc.). Within the functional area you also have the functional groups categorizing fields from the tables into different groups.

Read more

Unplanned Delivery Cost in Logistics Invoice Verification

Unplanned delivery costs are not known at the time of purchase order creation and hence these are not specified in the purchase order. These are only entered at the time of vendor invoice posting. For these cost no provision is made while posting the goods receipt. In case of unplanned delivery costs, the system does not check the purchase order for planned delivery costs. These costs are posted in exactly the same manner as subsequent debits/credits.
Find below end-user manual for this process

Read more

Transaction History Executed by a User in SAP

If you want to see what transactions are executed by a user in a specific time period do the following steps;

  • Go to ST03. Select choose for analysis. Choose only one application server at a time in case you have multiple application servers. Choose time period of your choice.
  • In the next screen from menu choose GO TO–>PROFILES->-USER PROFILES. Here you will get the list on users who have worked on that application server.
  • Double click on the required user and you will get all the transactions he/she has executed.
  • In case you select TOTAL in step 1 and then follow the steps 2 and 3 you will only get the list of application server on which the user has worked and not the transaction details.
  • Stopping Payment With Cancellation of Invoice in SAP

    Accounts Payable vendor checks are created in the SAP system via automatic payment program execution (transaction F110) or via manual check generation (transactions F-53 and FCH5). Sometimes there are business scenarios where a check must be voided in the SAP system. For example, a check may have ripped during printing or was reported as stolen. The Accounts Payable (AP) Supervisor or Lead will be notified of the need to void an AP check(s). The Supervisor or Lead will verify the business requirement and complete the Cancel Check Payment (FCH8) transaction in SAP. It is important to note that the FCH8 transaction not only voids the check but also reverses the payment document. Because the payment document is reversed, the corresponding invoice(s) are put back to an open status in the system. The open invoice will then be included on the next automatic payment program run or can be cleared manually via transaction F-53 and FCH5 (Quicken check). Read more

    Practical Guide for SAP Controlling (German Language E-Book)

    practical-guide-to-sap-controllingThis is a 363 pages German language book which will guide you to practice SAP Controlling with the following chapters;

    • I. Introduction to the Controlling
    • II Organizational Structure
    • III Controlling Overview
    • IV Product Cost Planning
    • V Profitability Analysis
    • VI Authorization Check

    Read more