Tag Archives: SAP

The ABAP Debugger is used tool to execute and analyze programs line by line. Using it we can check the flow logic of a program and display runtime values of the variables. Currently, SAP offers two types of Debuggers:

• The Classic ABAP Debugger
• The New ABAP Debugger

The Classic ABAP Debugger, with its old user interface and its limitations to debug certain types of ABAP program is now not in use by many new and old ABAP developers.

Learn How To Use The ABAP Debugger In This Training Course

The New ABAP Debugger, with its state of the art and flexible user interface, can be used to debug all types of ABAP programs. It provides many new features which improve our efficiency of debugging, both in ABAP support and development.

In this article, we will learn how to use these new features and discover some tips and tricks to efficiently use ABAP debugger.

Switching between the ‘Classic Debugger’ and ‘New Debugger’

You can switch between both the debugger and make any one your default debugger. To do this, go to ABAP Editor (SE38)→ Utilities → Settings.

Now in the user-specific settings pop up box click on ABAP Editor tab and then click on Debugging.

The Purpose Of The FBL3N Report

The FBL3N report is used to list line items for multiple accounts across multiple company codes. This functionality is provided by the selection screen of the report. It is also possible to display items from more than one General Ledger account in a customized layout. This report allows changes to individual documents or to carry out mass changes to posted line items displayed in the report.

Search help is available to enable a detailed selection of General Ledger accounts which allows access to various possible entries. The search help screen is shown in figure 1 below.

Concept Of A Vendor Master

The vendor master stores all the data pertaining to a particular vendor in SAP. This data is made available to other transactions and modules as and when required by SAP via the inter-module integration. The vendor master contains the following data sets:

• GENERAL DATA: The general data consists of the vendor address, country, contact person, bank account, etc.
• COMPANY CODE DATA: The company code data contains the data specific to a company code like the payment terms, payment methods, dunning procedures, tax details, etc.
• PURCHASING ORGANIZATION DATA: The purchasing organization data contains information like the sales purchasing organization, partner functions, pricing, etc.

The vendor master is extremely important for the materials management, logistics as well as the Financial Accounting module. The details of the vendor such as the payment terms, address, purchasing organization, purchasing group, payment methods, etc. are picked up from the vendor master and provided to the other modules as and when necessary.

The total data for a vendor master is stored in multiple tables. The General data pertaining to a vendor is stored in the LFA1 table while the company code data is stored in the LFB1 table. The purchasing organization data for a vendor is stored in the LFM1 table. All these tables are accessed for information about the vendor by the FI and the MM module.

DSO or Data Store Object is a SAP BW object primarily used to store detailed transactional data on an atomic level. Unlike multidimensional data storage InfoCubes, it’s designed as a 2-dimensional flat database table that contains key fields and data fields. Data is normally held in a DSO for several years. There are 3 types […]

The sales & distribution (SD) module in SAP allows the supply chain process for the business to be mapped into the software. SAP provides various components like the sales area, distribution channel, division, etc. for setting up the sales and distribution organizational structure. The sales and distribution enterprise structure does not exist in isolation from the rest of the modules in SAP. The sales and distribution module is closely integrated with the other modules like FI and MM. SAP best practices dictate that a good organizational structure must meet the company’s current needs and at the same time must be flexible enough to incorporate any future requirements. This makes the organizational structure scalable and ready to change with the growth of the company.

The sales and distribution organizational structure is set in two steps. First of all the organizational elements are created and then they are linked to each other by specific assignments. For e.g. a sales organization is created first, and then it is assigned to a company code.

Concept Of A Sales Organization

A sales organization is the highest entity in the sales and distribution organizational structure. A sales organization represents the sales department in a company and is primarily responsible for the sale and distribution of its products and services. A sales organization needs to be mentioned while creating any sales related documents and needs to be assigned to a company code. The other sales and distribution organizational elements are assigned to the sales organization.

As a part of the best SAP business practices, it is recommended to keep the number of sales organizations to a minimum. Ideally there should be only a single sales organization for a single company code. Having a single sales organization makes the reporting process simple.

The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel. You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries.

Full Course – Click Here
Subsequently, you can analyze the selected Info Provider data by navigating to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or add multiple queries to a workbook and save them there.

You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer. Beyond that you can distribute the workbook by e-mail to recipients.

In this document we will learn how to access and run BEx queries in addition to introducing some reporting functionalities used within BEx.
Access BEx Analyzer

To start the BEx Analyzer, choose Start→ All Programs → Business Explorer →Analyze. This will open Microsoft Excel with the SAP BEx plugins enabled.
Login

Click on the Add-ins tab

Add-Ins Tab

Choose the Open Icon in the BEX Analysis toolbox

Open Icon In The BEX Analysis Toolbox

In the Opened menu click on “Open Query”

Open Query

A window will pop up asking you to log on to the BW system. Insert your SAP BW username and password?Note that the User for BW client is different from the user in ERP client.

There are many reasons why a run-time error can occur such as un-handled exceptions, a resource or system problem or an error in coding. Let’s look a little deeper…

Tools for Troubleshooting Your ABAP Code

System Logs (TCODE – SM21)

When faced with a program that crashes, developers end up spending a lot of time debugging ABAP code to find and trace what went wrong. But they should know that SAP records all the warnings, exceptions and system errors in the System Log. So, when we get an error we can make best use of time by taking a good look at the System Logs first to help find and correct the errors in our code quickly and easily.

System Logs Go To Transaction SM21