Transparent table. From SAP help: There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary agree. All the business and application data is stored in transparent tables. Structure. From SAP help: No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs. Cluster table. From SAP help: Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table category. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database. Pooled table. From SAP help: Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored. General view structure. From SAP help: A structure is generated for a view during activation. This structure is used as the interface for the runtime environment. It is not usually displayed in the ABAP Dictionary. Append structure. From SAP help: An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.

SAP Enterprise Structure SAP enterprise structure is organizational structure that represents an enterprise in SAP ERP system. It consists of some organizational units which, for legal reasons or for other specific business-related reasons, are grouped together. Organizational units include legal company entities, sales offices, profit centers, etc. Organizational units handle specific business functions. Organizational units may be assigned to a single module (such as a sales organization is assigned to Sales and Distribution (SD) module, or to several modules (such as a plant is assigned to Materials Management (MM) and Production Planning (PP) module). SAP ERP system can represent a complex enterprise structure. Enterprise structure design is a fundamental process in a SAP implementation project. The design is mainly determined by the business scenarios performed in an enterprise. Once the design is determined, it will affect many things such as how to perform a transaction and generate reports on SAP system. Although it’s possible, it requires great effort to change the enterprise structure. So , we must ensure that the enterprise structure designed in the SAP implementation project can accommodate all business scenarios and enterprise’s requirements for current and future situation. The SAP Enterprise Structure is a fundamental setting and needs a comprehensive understanding of the business processes and their integration. We have to work with other departments and SAP modules, such as Accounting department (FI), and Sales department (SD). This book explains in details about the basic concept of SAP Enterprise Structure (MM and related modules such as FI, Logistics, and SD) and step by step how to configure it in SAP ERP system. To make it more understandable, it is supplied with a case study and the screen shots of each configuration step. It's written in a simple-to-understand way, so you can learn it easily. You don't need to have extensive SAP configuration skill and experience to be able to configure the SAP Enterprise Structure. Table of contents of the e-book: Chapter 1: Case Study Business Scenario Chapter 2: SAP Enterprise Structure Enterprise Structure in Financial Accounting Enterprise Structure concept in Financial Accounting Define Company Define Company Code Assign Company Code to Company Define Business Area...page 13 Enterprise Structure in Logistics – General Enterprise Structure concept in Logistics Define Plant Define Valuation Level Define Division Assign Plant to Company Code Assign Business Area to Plant/Valuation Area and Division Enterprise Structure in Sales and Distribution (SD) Enterprise Structure concept in Sales and Distribution Define Sales Organizations Define Distribution Channel Assign Sales Organization to Company Code Assign Distribution Channel to Sales Organization Assign Division to Sales Organization Setup Sales Area Assign Sales Organization – Distribution Channel - Plant Business Area Account Assignment Enterprise Structure in Material Management (MM) Enterprise Structure concept in Material Management Maintain Storage Location Maintain Purchasing Organization Assign Purchasing Organization to Company Code Assign Purchasing Organization to Plant Assign Standard Purchasing Organization to Plant Assign Purchasing Organization to Reference Purchasing Organization

SAP MM Config - Create a New Plant IMG for SAP Plant Maintain How to Configure a New Plant in SAP? Plant 0001 is the SAP default provide for your reference. OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes) Most company take the SAP recommended choice - Value Material Stock at Plant level Value Material Stock at Plant or Company Level If you valuate material stocks at plant level, the plant is the valuation area. If you valuate material stocks at company code level, the company code is the valuation area. The decision you make applies to the whole client. OX10 - Create / Change / View Plants OVXB - Create / Change / View Division OX18 - Assign Plant to company code e.g. 0001 - 0001 - All Plants Px1 - Plant Px1 Px2 - Plant Px2 OX19 - Assignment of company code to the Controlling Area OB38 - Assign company code to Credit Control Area OMJ7 - Assign business area to Plant/Valuation area and division e.g. Plant Px1 - Business Area Bx1 Bx2 Assign Valuation area to the Business Area .e.g. Valuation area Vx1 - Business Area Bx1 Business Area Bx2 OMS0 - Assign Factory Calendar to the Plant and Business Area The plant plays an important role in the following areas: Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination. Inventory Management - The material stocks are managed within a plant. MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants. Production - Each plant having they own production/planning. Costing - In costing, valuation prices are defined only within a plant. Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants). If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level. The valuation level that you choose affects the maintenance of material master records the G/L accounts in which material stocks are managed the G/L accounts to which transactions are posted in Materials Management Effect on the maintenance of material master records: Depending on the valuation level chosen, you maintain accounting data in the material master record for each plant or for each company code you define a valuation price for the material in each plant or in each company code Effect on G/L accounts: If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code. If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination. If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.

MM Configuration: Define Plant Step-by-Step SAP Material Management (MM) Configuration: Define Plant This post will explain a step by step SAP MM configuration of how to define a plant in an SAP client. A plant is the place of production, or branch of a company, or simply a collection of several locations of material stocks in close physical proximity. A plant is represented by a client-unique 4-digit alpha-numeric. Plant is used in Material Management (MM), Production Planning (PP), Sales and Distribution (SD), and Plant Maintenance (PM) module. A plant is assigned to one company code. One company code can have more than one plant. One Business Area is assigned to plant. Several plants can have same business area. We can define Plant in a SAP R/3 client with T-code: SPRO. SAP Screenshots of How to define a plant are: Go to the menu: IMG – Enterprise Structure – Definition – Logistic-General – Define, Copy, Check, Delete Plant: The above image is © SAP AG 2010. All rights reserved Click Execute button, the next screen is: The above image is © SAP AG 2010. All rights reserved Select “Define Plant” if we want to create a plant from the scratch, or select “copy, delete, check plant” if we want to copy a plant from an existing plant. In this example we will create a plant from the scratch. The next screen is: The above image is © SAP AG 2010. All rights reserved Click “New Entries” button. The next screen is: The above image is © SAP AG 2010. All rights reserved Fill the Plant code that we want to create (client-unique 4-digit alpha-numeric) in the plant field. Then click “address” icon. The next screen is: The above image is © SAP AG 2010. All rights reserved Fill the required field as above image, and click “OK” button or press “Enter”. The next screen is: The above image is © SAP AG 2010. All rights reserved Click the “save” button. And the next screen is: The above image is © SAP AG 2010. All rights reserved The GC01 plant has been created. Then we need to assign this plant to a company code and business area. SAP Study Materials Series e-Book To get more details on SAP Enterprise Structure, you can buy my e-book (50 pages .pdf file) at SAP Study Materials Store. The e-book explains in details about the SAP Enterprise Structure (MM and related modules such as FI, Logistics, and SD) Concept and Configuration Guide. Just like other articles on my SAP Study Materials blog, I wrote the e-book in a simple-to-understand way, so you can learn it easily. You don’t need to have extensive SAP knowledge and experience to be able to configure the SAP Enterprise Structure, as the e-book start explaining each step with the basic concept behind it. After understanding the concept, the e-book will show the step-by-step configuration with the screen shots.

Maintaining Vendor Master Records Use If you wish to store information on your vendors in the SAP System, the following functions are available: Create vendor master record Change vendor master record Block vendor master record Use one-time vendor Display list of vendors Procedure Create Vendor Master Record Choose Master data Vendor Central Create from the Purchasing menu. Enter the purchasing organization and an account group. If you want to use another vendor master record as a reference, enter the account number of that vendor in the Vendor (creditor) field (under Reference). Press ENTER . The Create Vendor: Address screen appears. Enter the address and press ENTER . The Create Vendor: Control screen appears. On this screen, enter the accounting data needed by the payment and dunning program, and data for declarations to the tax authorities. Also populate the Debtor (customer) field where necessary (the data in this field is needed in the case of deliveries to the vendor in connection with Returns and Subcontracting Components. Press ENTER and enter the necessary data on the subsequent screens that appear. On the Purchasing Data screen, enter purchasing-specific data such as the order currency or the key for the terms of payment and then press ENTER . You can record the Terms of Payment that you agree with a vendor in the vendor master record. They automatically appear as default values in any purchase orders created for the vendor in question; however, you can change them as needed. Terms of payment can also be entered in the vendor's invoice. These are then applied by the payment program. The Create Vendor: Partner Roles (partner functions) screen appears. Maintain the necessary partner roles on this screen. (See Partner Roles in Purchasing.) Click to save the vendor master record. Change Vendor Master Record Choose Master data Vendor Purchasing ® Change. Enter the vendor number and the purchasing organization, and select the data you wish to change. Press ENTER . Enter your changes and click to save your input. Block Vendors Suppose you would like to prevent further deliveries from a vendor who has supplied goods of poor quality. You can freeze or "block" the vendor account in the vendor master record. Once you have set the blocking indicator in the vendor master record, purchase orders can no longer be placed with this vendor. The "blocked" status for the vendor applies until such time as you cancel the blocking indicator. To block a vendor, proceed as follows: Choose Master data ® Vendor ® Purchasing ® Block. Enter the vendor number and the purchasing organization. Then press ENTER . A screen appears, on which you can indicate whether the vendor is to be blocked for a specific purchasing organization or for all purchasing organizations. If QM is active within the procurement function, you can impose a block for quality reasons. (See the documentation Quality Management (QM) Overview of Procurement Activities) Click to save your input. You can block a vendor for an individual material via the source list. For more information, refer to the section Optimized Purchasing. Use One-Time-Vendor You can create special vendor master records for vendors from whom you procure goods only once or rarely, so-called One-Time Vendor Master Records. For example, suppose you order goods from a vendor with whom you usually do not place orders, because your main vendor was not able to supply the required items. In this case, you would use a "one-time vendor" master record. In contrast to other master records, a "one-time vendor" master record is used for several vendors. The purpose of this is to avoid the unnecessary creation of an excessive number of individual vendor master records. For this reason, you may not store any vendor-specific data in a "one-time vendor" master record. When creating a "one-time vendor" master record, you must assign a one-time account group. This account group determines that the vendor-specific fields are suppressed. You don’t need to enter this data until the time a purchasing document (e.g. a PO) is created. When you create a purchasing document with a one-time vendor, you will be asked to enter the vendor address. Enter the vendor’s name and address. Like all other master records, you can display, block, or delete one-time vendor master records. Display List of Vendors You can create a list of different vendors. This list contains important information on individual vendors: the purchasing organizations for which material was procured from a vendor, the terms of payment, and the blocking status of the vendor, for example. Choose Master data ® Vendor ® List displays, then Purchasing list. Enter your selection criteria and run the analysis.

Parameters Syntax PARAMETERS name(length) [TYPE type or LIKE obj] DECIMALS d. Examples PARAMETERS: char1(20) TYPE C, date1 LIKE SY-DATUM, number1 TYPE P DECIMALS 2. Options DEFAULT Example: PARAMETERS p1(5) TYPE C DEFAULT ’we’. MEMORY ID Example: PARAMETERS p2(5) TYPE C MEMORY ID pid. LOWER CASE Example: PARAMETERS f1(10) LOWER CASE. VISIBLE LENGTH Example: PARAMETERS f1(10) TYPE C VISIBLE LENGTH 4. OBLIGATORY Example: PARAMETERS f1(10) TYPE C OBLIGATORY. MATCHCODE OBJECT Example: PARAMETERS p_belnr LIKE BKPF-BELNR MATCHCODE OBJECT zsh_f4_belnr. VALUE CHECK Example: PARAMETERS p_belnr LIKE BKPF-BELNR OBLIGATORY VALUE CHECK. AS CHECKBOX Example: PARAMETERS: c1 AS CHECKBOX DEFAULT ’X’. RADIOBUTTON GROUP Example: PARAMETERS: r1 RADIOBUTTON GROUP rad1 DEFAULT ’X’, r2 RADIOBUTTON GROUP rad1, r3 RADIOBUTTON GROUP rad1. NO-DISPLAY Example: PARAMETERS: f1(10) TYPE C NO-DISPLAY. MODIF ID Example: PARAMETERS: f1(10) MODIF ID GR1.

SAP System Landscape:
(Kind Note: In this post i going to give a short hint about SAP system landscape don't consider this as a SAP Architecture. Often
times, SAP users, especially new comers misunderstands these two concepts.)
They system landscape basically is the set-up or arrangement of your SAP servers. Ideally, in an SAP environment, a three-system
landscape exists. A three-system landscape consists of the Development Server-DEV, Quality Assurance Server-QAS and the
Production Server-PROD. This kind of set-up is not primarily designed to serve as server clusters in case of system failure, the
objective to enhance "configuration pipeline management".
A Typical SAP Three-System Landscape would consist of one or two development system ==> one Quality system ==> Production
system. (but it is not must to keep separate server for each systems, you can configure DEV & QAS on a same server but it is
not advisable to keep PROD too in the same server)
Pipeline is the environment where the configuration in the development system is moved to the quality assurance system and finally
to the production system. The whole idea is to sync the configuration of these systems at any point in time.
Devlopment/configuration/changes are first made in the Development system, thoroughly tested in the Quality Assurance system
then loaded into the production system. TMS Does this process nicely. Transport management system is the coordination of the
movement of objects and configuration changes from the development system to the Quality Assurance system and then to the
Production system.