DISPLAYING MATERIAL MASTER DATA JPG IMAGES
TCODE: OMT3B CHOSE ONE SECTION AND SAPLMGD1 –> ZZ2 THEN CREATE THIS REPORT
YOU SHOUL PLACE A CUSTOM CONTAINER NAMED : C100 IN YOUR SUBSCREEN (001 ).
*&———————————————————————*
*& Report ZZ2
*&
*&———————————————————————*
*&
*&
*&———————————————————————*
One of the most asked question in a SAP interview is whether it is possible to have a self defined transaction code in SAP. The answer to the question is simple and if given tactfully can impress the interviewers.
To start with, yes, self-defined reports, transactions or functions are possible within SAP. There might be numerous reasons why a company might go in for customized transaction codes or for that matter reports.
Bill of material form an important component of the Production Planning SAP PP module. In many SAP interviews candidates are asked to explain the concept of Bill of material.
Q). What is a Bill of Material BOM in the SAP Production Planning PP module?
In SAP MM materials management, Plant represents a location where valuated stocks are maintained. In other cases, plant can also be looked at as a location for maintaining or servicing. Transaction code OX10 can be used to define a plant in SAP. However, SAP MM requires certain pre-requisites before a plant can be defined in SAP. The three maiin requirements for configuring plant are country keys, factory calendar and region keys.
Internal tables are a way to store variable datasets of a fixed structure in the working memory of ABAP. The data is stored on a row-by-row basis, where each row has the same structure.
Internal tables provide the functionality of dynamic arrays and relieve the programmer of the expenditure of a program-controlled dynamic memory management (see Memory management of deep data objects. Internal tables are preferably used to store and format the content of database tables from within a program. Furthermore, internal tables in connection with structures are the most important means of defining very complex data structures in an ABAP program.
Release Procedures (approval) can be used for Purchase Requisitions (PR), Purchase Orders (PO), RFQ’s, Outline Agreements and Service Entry Sheets. The principle is exactly the same for all. If you can master one, you will know them all.
This guide contains an example of release procedures for Purchase Requisition
Create Purchase Order Automatically in Purchasing
For creation of purchase Order automatically from Purchase Requisitions we need to do the following additional settings in addition to our standard ones.
Activate ‘auto PO’ indicator for material master
Activate ‘auto PO’ indicator for vendor master
Create Purchase Requisitions using T Code ME51 or ME51N
Use T. Code ME59 or ME59N for auto conversion of PR into purchase order