http://www.gotothings.com/sapmm001.htm 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 c hanges) 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 valuati on area. If you valuate material stocks at company code level, the company code i s 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 stock s are valuated at plant level. Each plant can have its own material prices and a ccount determination. Inventory Management - The material stocks are managed within a plant. MRP - Material requirements are planned for each plant. Each plant has its o wn 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, i t is defined as a maintenance planning plant. A maintenance planning plant can a lso carry out planning tasks for other plants (maintenance plants). If you want to use the application PP (production planning) or product costing a nd 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 compa ny code Effect on G/L accounts: If material stocks are valuated at company code level, all plant stocks of a mat erial are managed in a joint stock account for each company code. If material stocks are valuated at plant level, you can manage the material stoc ks for each plant in different accounts. For each plant, you can define a separa te determination. If several plants are to use account determination, you can group these plants i n "Valuation and Account Assignment" Customizing. ================================================================================ =========================================== http://www.erpgreat.com/materials/procedures-for-copying-one-plant-to-another.ht m Procedures for copying One Plant to Another Can anyone give me a step by step process of creating another plant or storage l ocation by copying from an existing one. Celani Ndlovu Plants Definition : /NSPRO-IMG---Enterprise Structure---Definition---Logistic General---Define,copy, delete,check plant---Define Plant (In this, we are defining plants(s) under comp any which is defined earlier) /NSPRO-IMG---Enterprise Structure---Definition---Logistic General---Define,copy, delete,check plant--- copy,delete,check plant---F6 to copy org. object from plan t 0001 to defined plant(s). Storage Location : /NSPRO-IMG---Enterprise Structure---Definition---Materials Management---Maintain Storage Location-New Entries (Define required storage location(s) under differe nt plant(s) ) /NSPRO-IMG---Enterprise Structure---Definition---Materials Management---Maintain Storage Location---Storage Location Description---- New Entries ( enter here ad dresses of each plants) Rahul Copy Organizational object Plant using Transaction: EC02. (recommended to Copy from a standard sap plant) Create or copy storage location using :OX09 Shipra

1. Copy existing plant A to new plant B. All of plant A s data in throughout the IMG will be created/copied for plant B. In some cases with plant A data that is not desired. In step 3 you must go through and correct invalid entries 2. Correct address information 3. Correct data copied to plant B as plant A (a) In Sales and Distribution -> Shipping -> Picking -> Determine Picking Locati on -> Assign Picking Locations (OVL3), delete entry where Shipping Point = plant A and Plant = plant B and press save. (b) In Sales and Distribution -> Shipping -> Basic Shipping Functions -> Shippin g Point Determination -> Assign shipping points wherever plant B is found the sh ipping point is plant A. This must be changed to plant B. (c) In Enterprise Structure -> Maintain Structure -> Assignment -> Sales and Dis tribution -> Assign shipping point to plant delete plant B shipping point from t he plant A assignement. (d) In Enterprise Structure -> Maintain Structure -> Definition -> Sales and Dis tribution -> Define, copy, delete, check shipping point copy shipping point plan t A to shipping point plant B. Correct the description in the define section of this node. (e) In Sales and Distribution -> Shipping -> Picking -> Determine Picking Locati on -> Assign Picking Locations (OVL3), copy plant A entry to plant B entry, chan ging all data to plant B. (f) Check with Reorder buying group to determine MRP controllers for new plant. Remove plant A MRP controllers from plant B, and add controllers received from reorder buying group. IMG is Materials Management -> Consumption Based Planning -> Master Data -> Define MRP controllers (g) Define special procurement. IMG is Materials Management -> Consumption Based Planning -> Master Data -> Define special procurement type. (h) OMGN Assign customer in Set up stock transport order [Plant] .

(i) OMGN in Set up stock transport order [Purchasing Document type] ; an entry was created for source plant B and plant A, this entry should have a UB order type a nd the check box should be off. Each plant needs a plant B UB entry created. (j) OMJ3 Delete incorrect entry in print parameters. Remove entry where plant = plant B & storage location = plant A. Create entry for plant B storage locati on B (k) Verify entry for new plant exists in OVLT picking output (l) Verify entry for new plant is correct in VP01 4. Manual configuration (a) Create plant customer number and assign to plant in OMGN. (b) OMJ3 (c) OPK8 set correct printer for plant B Set printer for plant for list LG01. This is for production orders.

(d) Output determination OVLT (set printer), In addition to above, other changes based on customization in your installation needs to be done as well. KBS Account Assigned Purchase Order Explain the transaction key KBS in OBYC configuration. In which situation will t ransaction key KBS be used? ------------------------------------------------------------------------------------------------------------------------KBS transaction/event key will be only called for account assigned PO. It is no t used for stock PO. Purchase order with account assignment (KBS) You cannot assign this transaction/event key to an account. It means that the ac count assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt. For KBS, A/C assignment is not possible in OBYC. Whatever the G/L has been assig n in Purchase Order, it will take that G/L into account. In Standard SAP, for transaction event key KBS, account determination is not act ive. You can find the same in OBYC t-code. In account assigned PO, G/L account is entered manually or is pick up through co st center and hence account determination will not happen through transaction ev ent key. So This transaction event key is used only to find the posting keys and not the G/L accounts. Whereas other transaction event keys are used for account determination. KBS key doesn t require any additional settings in OBYC. It only looks for account specification in PO (say K / C / P) and GL account and can be assigned in OKB9 t-code. When we do GR for PO with account assign {KBS (consumption)}, it will debit the given GL account (assigned in OKB9 t.code) and credit GR/IR account (w hich is define in OBYC). ----------------------------------------------------------------------------------------------------------------------Release Procedure With And Without Classification Question: What are the differences between release procedure with classification and relea se procedure without classification? When are they used? Is it possible to have a release procedure without classification for a PO? Answer: Two different procedures are available for requisitions: With classification With this procedure, requisitions can be released both at item level (i.e. itemby-item) and in total. The latter approach is also termed "overall release".

Without classification With this procedure, requisitions can only be released at item level. The two procedures are mutually exclusive (that is to say, you must decide in fa vor of one of them only - you cannot use both). External purchasing documents (i.e. purchasing documents other than requisitions ) are released at header level. Item-by-item release is not possible. These docu ments can only be released using the release procedure with classification Requisitions without classification can have Account Assignment category, Materi al Group, Plant and Total Value only as characteristics, whereas in with classif ication you can define your own characteristics. Release procedure without classification is possible for internal purchasing doc s. There you can release at item level. But for PO we have to release at header level. We can't release them at item level. So for External purchasing docs we m ust set release procedure with classification. It is not possible to have releas e procedure without classification for PO. -------------------------------------------------------------------------------------------------------------------------