E – Enterprise R – Resource or Department P – Planning ERP is a continuous activity in each enterprise (Organization) to make sure that everything is going properly and efficiently. i.e. the purchase department must plan.        1. What to purchase.        2. When to purchase.         3. How much to purchase.        4. From where to purchase. To make sure that they can get the quality material for the right price and in right time because many other departments waits for this material to start their activities such as production, sales etc... And similarly, department must plan their activities properly as the success of the enterprise depends on how best the departments plan their activities. ERP can be done manually or automation. Manually: where human being involves in the planning so that it is.         1. Time consuming.       ...

Web Dynpro (WD) for ABAP is the SAP standard user interface technology developed by SAP AG. It can be used in the development of web-based applications in the SAP ABAP environment that utilizes SAP development tools and concepts. It provides a front-end web user interface to connect directly to backend SAP R/3 systems to access data and functions for reporting. Web Dynpro for ABAP consists of a run-time environment and a graphical development environment with specific development tools that are integrated in the ABAP Workbench (transaction: SE80). Architecture of Web Dynpro The following illustration shows the overall architecture of Web Dynpro − Following are a few points to keep in mind regarding Web Dynpro − Web Dynpro is the SAP NetWeaver programming model for user interfaces. All Web Dynpro applications are structured as per the Model View Controller (MVC) programming model. The model defines an interface to the main system and the Web Dynpro application can ha...

In some cases, special functions need to be predefined in a software application to enhance the functionality of various applications. There are many Microsoft Excel add-ins to improve the functionality of MS Excel. Similarly, SAP facilitates some predefined functions by providing  Business Add-Ins  known as BADIs. A BADI is an enhancement technique that facilitates a SAP programmer, a user, or a specific industry to add some additional code to the existing program in SAP system. We can use standard or customized logic to improve the SAP system. A BADI must first be defined and then implemented to enhance SAP application. While defining a BADI, an interface is created. BADI is implemented by this interface, which in turn is implemented by one or more adaptor classes. The BADI technique is different from other enhancement techniques in two ways − Enhancement technique can be implemented only once. This enhancement technique can be used by many customers simultaneously....

User exits are used in an extraction if the standard SAP extractors do not provide the expected data or the required functionality, for instance in authorizations or time checks. User exits are commonly used in Sales and Distribution (SD) modules. There are many exits provided by SAP in the areas of sales, transportation, shipping and billing. A user exit is designed to make some changes when standard SAP is not capable of fulfilling all the requirements. To be able to access what exits are available in each area of sales, go to IMG using this path: IMG → Sales and Distribution → System Modifications → User Exits. The documentation for each exit in the areas of SD is explained thoroughly. For instance, if you want to find user exits in Sales Document Processing (contract, quotation or sales order), follow the path mentioned above and continue to expand the node User Exits in Sales → User Exits. Click on icon documentation to see all user exits available in Sales Document Processi...

Customer exits could be considered as hooks to the SAP standard programs. We do not need an access key to write the code and there is no need to modify the SAP standard program. These exits don't have any functionality and they are empty. Business logic could be added in order to meet various client requirements. However, Customer Exits are not available for all programs. Customer Exits for Standard Transactions Following are the steps to find customer exits as far as standard transactions are concerned. Let’s identify customer exits available in MM01 (Material Master Creation). Step 1  − Go to transaction MM01 and identify the program name of MM01 by going to Menu bar → System → Status as shown in the above screenshot. Step 2  − Get the program name from the popup screen. The program name is 'SAPLMGMM'. Step 3  − Go to transaction SE38, enter the program name and click Display. Step 4  − Navigate to Go to → Properties and find out the package of this ...

The SAPscript tool of the SAP system can be used to build and manage business forms such as invoices and purchase orders. The SAPscript tool provides numerous templates that simplify the designing of a business form to a great extent. The SAP system comes with standard SAPscript forms that are delivered with the SAP standard client (generally as client 000). Following are a few examples of standard SAPscript forms delivered with client 000 − S.No. Form Name & Description 1 RVORDER01 Sales Order Confirmation Form 2 RVDELNOTE Packing List 3 RVINVOICE01 Invoice 4 MEDRUCK Purchase Order 5 F110_PRENUM_CHCK Prenumbered Check The structure of a SAPscript form consists of 2 main components − Content  − This can be either text (business data) or graphics (company logo). Layout  − This is defined by a set of windows in which the form content appears. SAPscript – Form Painter Tool The Form Painter tool provides the graphical layout of a SAPsc...

SAP Smart Forms tool can be used to print and send documents. This tool is useful in developing forms, PDF files, e-mails and documents for the Internet. The tool provides an interface to build and maintain the layout and logic of a form. SAP also delivers a selection of forms for business processes such as those used in Customer Relationship Management (CRM), Sales and Distribution (SD), Financial Accounting (FI) and Human Resources (HR). The tool allows you to modify forms by using simple graphical tools instead of using any programming tool. It means that a user with no programming knowledge can configure these forms with data for a business process effortlessly. In a Smart Form, data is retrieved from static and dynamic tables. The table heading and subtotal are specified by the triggered events and the data is then sorted before the final output. A Smart Form allows you to incorporate graphics that can be displayed either as part of the form or as the background. You can als...

Dialog programming deals with the development of multiple objects. All these objects are linked hierarchically to the main program and they are executed in a sequence. Dialog program development makes use of tools in the ABAP workbench. These are the same tools used in standard SAP application development. Here are the main components of dialog programs − Screens Module pools Subroutines Menus Transactions The Toolset Dialog programs should be developed by the object browser (transaction: SE80) so that all objects become linked to the main program without having to explicitly point each object. Advanced navigation techniques enhance the process of moving from one object to the other. Screens are made up of screen attributes, screen layout, fields and flow logic. The module pool consists of modularized syntax that is placed inside include programs of the dialog program. These modules can be invoked by the flow logic, which is processed by the dialog processor. Creati...

A  report  is a presentation of data in an organized structure. Many database management systems include a report writer that enables you to design and generate reports. SAP applications support report creation. A classical report is created by using the output data in the WRITE statement inside a loop. They do not contain any sub-reports. SAP also provides some standard reports such as RSCLTCOP that is used to copy tables across clients and RSPARAM that is used to display instance parameters. These reports consist of only one screen as an output. We can use various events such as INITIALIZATON & TOP-OF-PAGE to create a classical report, and each event has its own importance during the creation of a classical report. Each of these events is associated to a specific user action and is triggered only when the user performs that action. Following is a table describing the events and descriptions − S.No. Event & Description 1 INITIALIZATON Triggered before di...