Organizational Structure In MM Module 1.What is the organizational structure in the MM module?

The organizational structure in the MM module is a hierarchy in which various or ganizational units are arranged according to their tasks and functions. The diff erent organizational units that constitute the organizational structure of the c ompany are as follows: Client A self-contained unit in the SAP system with separate master recor ds and its own set of tables. Company code The smallest organizational unit. You can create an independ ent set of accounts for this unit for the purpose of external reporting. Plant An organizational unit where materials are produced or goods and se rvices are provided. You can divide an enterprise into various plants according to production, procurement, maintenance, and materials planning. Storage location lant are stored. An organizational unit where the goods produced in the p

Warehouse number An alphanumeric key that represents a warehousing system , which is made up of different organizational and technical storage areas. Storage type An area such as a goods receipt area, goods issue area, or p icking area. Also the physical or logical division of a complex warehouse. Purchasing organization An organizational unit that procures materials and services and negotiates with vendors to purchase materials or goods. Purchasing group An alphanumeric key for a buyer or a group of buyers who are involved in purchasing activities. The purchasing group is responsible for materials procurement and dealing with vendors. ======================================================== Problem is that after goods receipt and AFTER invoice verification, reversal of goods receipt is being done. Client wants this more controlled as the GRIR accou nt is being affected. So no reversals to be done after Invoice verification. Ho w to approach this? Make this setting: SPRO > Materials Management > Inventory Management and Physic al Inventory > Goods Receipt > For GR-Based IV, Reversal of GR Despite Invoice Here remove the tick against Mvt 102 & 122. Now the system will not allow to return the Good at any case. *-- B.Anand daiva raja I have created a new vendor. Later I found that there were some mistakes and th at I want that the system should not allow me to make any PO or post any entries to this vendor. How to deactivate this vendor? You can block a vendor at the following levels: All company code Single company code All Purchase org

Single Purchase org Where to Get the Goods Movement Type List? Step 1) Run spro command/TC Step 2) Then move to "SAP Reference IMG" screen Step 3) Then navigate following path: IMG --> Materials Management --> Inventory Management and Physical Inventory --> Movement Types --> Copy, Change Movement types Here with "Copy, Change Movement types" option a help tutorial is available (rec tangular blue colour icon). In that go to "Further information" section where y ou can find a big list of movement types with some brief explanation. Where the schedule margin key is customized? You define the order float in the scheduling margin key, The scheduling margin k ey is copied from the material master. The float before production or float afte r production and the release period are defined in the scheduling margin key For Customizing for Shop Floor Control, by choosing Operations --> Scheduling -> Define Scheduling Margin Key . The scheduling margin key is assigned to the material ( MRP area in the material master) and is transferred when the production order is created. These values can be changed in the production order. What is the function of OBYC? Function of the OBYC stand for Configure Automatic Postings. In this step, you enter the system settings for Inventory Management and Invoice Verification tran sactions for automatic postings to G/L accounts. Postings are made to G/L accounts automatically in the case of Invoice Verificat ion and Inventory Management transactions relevant to Financial and Cost Accounting. For example, Posting lines are created in the Stock account and Consumption acco unt. Tell me what is *make to order*? Make-to-order production is a process in which a product is individually manufac tured for a particular customer. In contrast to mass production for an unspecifi ed market where a material is manufactured many times, in make-to-order producti on a material is created only once though the same or a similar production proce ss might be repeated at a later time. In global trade, you often need to process several different kinds of transactio ns at the same time. The Trading Execution Workbench (TEW) provides a central co ckpit where traders can process trading contracts and their subcomponents, such as purchase orders and sales orders and follow-on documents. In addition, TEW au tomates a large part of the data entry, making processing quicker, easier, and m ore error-free. How to delete a material completely? Try MMDE transaction but be careful this will remove all material from Client. What is the use of Tables in MM. i.e. How the tables get created? Through SE11 you can create a new Table. In MM if you create a Material Master M

ARA, MARM, MARC,MARD, MBEW & MVKE will updated. In Vendor Master LFA1, LFB1 & LF M1 will be updated. The same applies to EKKO,EKPO for P.O, MSEG & MKPF for MIGO & RBKP for MIRO. If in any error, only the message no. ! or the table no. is shown , then how to resolve the error using message no. or table no.? Contact ABAP or BASIS person to resolve this. How to create new transaction codes? In transaction code SE93 you can create, Change & Display a Transaction Code. ======================================================================= Client: Within one SAP instance, a number of clients could be created. The m aster data cannot be accessed from outside the client. In SAP we have objects th at are used by all the clients in a SAP system called client independent and obj ects that are used by only one client called client dependent. SAP delivers the software with three clients: 000, 001 and 066. During the implementation, normal ly we will have one client for development and testing, one client for training and another client for production. Some facts about the client: Highest hierarchical level in SAP All areas of an organization that are to be integrated into the SAP R/3 production system should be included under one client There is a common set of rules in one client Common tables Common master files Common databases Standardized Data Across the client A vendor number and name is common across the client A customer is common across the client A general ledger number and description is common across the client A material number and description is common across the client Company Code: SAP defines a company and a company code separately. A company can contain one or more company codes, but they must use the same chart of acco unts and the same fiscal-year breakdown. The company code will represent legally independent companies. The company field is defined in transaction OX15 and the company code is created in transaction OX02. To maintain the company code addre ss you need to use transaction OBY6. Some facts about the company code: Balance sheet, profit loss statements require by law are created at comp any code level. To create a company code we can easily copy the standard one and then cu stomized it. Plants: A plant it is a location that holds valuated stock or contains servi ce or maintenance facilities. A four-character string defines the plant field -t r. OX10-. Tip: When creating a plant just copy the standard plant which automati cally make the entry in the plant table and all others depended tables. The valu ation level it is an important configuration step because it specifies the level at which material stock are valuated for the whole client -tr. OX14-. There are two options: plant level or company code level. Once a valuation is determined, it should not be changed. Once a valuation level has been stablished, it is pos sible to assign a plant to an existing company code -tr. OX18-. Storage Locations: It is a place where stock is physically kept within a pla nt. There will be always at least one storage location defined for one plant -tr . OX09-. It is the lowest level of location definition and organizational struct

ure within the MM module, but it is not the lowest level in the SAP system, sinc e the Warehouse Management (WM) module provides the opportunity to manage invent ory at a bin level (Warehouse ? Storage Type ? Storage Sections ? Storage Bins). It is possible to create storage locations automatically (for each plant where this is needed) when an inward goods movement for a material is performed, but o nly for normal stock, not special stock -tr. OMB3-.