You are on page 1of 48

Print only till Page 45 Strategy Group Consumption Mode Combined Production Orders QAC1 - AFS in Raymond how

- We take acess Key from SAP and then add coding for Line item/size/grid le vel Production Versions Schedule Margin Key MRP Group MRP Type Lot Size Authoriz ation Group in QM View - QA32 validation -Strategy 50 in Mill 200/400 + Single f irst level of BOM explosion only. ASAP implementation methodology - Project Prep aration, Blue Printing, Realization, Final Preparation, Go Live and Support PP: Production Planning, MRP, Shop Floor control & Capacity Planning. Experience in SOP & DRP, Planning Planning File Entry, MPS/MRP, FICO & PP integration, NETUPL etc., lead time scheduling and basic finish dates, Difference between MD04 & MD0 5 What steps to implement PP Module in Company which alreadyn have all other mod ule. What need to be done if PP not to be implemented and how costing will be do ne? - strategy 20 for sales order based costing Long Term Planning, Sale Operati on Planning, Batch Management, Variant configuration, Product Costing, Engineeri ng Change Management, KANBAN, Classification, Work Scheduling - importance Indiv idual/collective or consolidated Order type config Difference b/w MD04 - supply/ demand Difference b/w Stock requirement List & MRP List MD61 - PIR in R/3 FERT & Raw Material Accounting views - v or s Config setting for ATP, issue alternativ e BOM component against Production Order Planning Horizon BOM Universal+ 2 Produ ction BOMs, MRP Run will work on which and how - maintained in CT22 CO11N Partia l & then CO50 Learn Movement types Sales Order assigned stock transferred to oth er Sales Order, only qty will transfer or value also? Settings for Subcon throug h Production Order Route, account assignment Production Schedule Profile, CO24, CO40, MB31, MBST, MB5T, Version Management, MB52, MC.9, CO46, VA05, MBLB, IQ01, IQ04, IQ03 - Serial Number (In CO02 - Header) Consume from other Plant & product ion Order in other plant etc. Partial Plan Order to Production Order Bulk Plan o rder to production Order Bulk PR to PO Material master, work center, routing, BOM and production version * Knowledge ab out SAP REM (Repetitive Manufacturing)

* Knowledge of Handling Unit Management * Understanding about material Planning and scheduling process. * Knowledge about PP-CO integration. * Knowledge about S cheduling Agreement, Inbound/Outbound deliveries and delivery schedules. * Knowl edge about Long Term Planning * LSMW, BDC, Background jobs, Workflow, Query, Fac tory Calender. QM: QM setings from zero level - Quality Planning, Quality Notification, Quality Inspection and Quality Certificates, Characteristics, Knowledge of Integration with MM, FI & CO (Product Costing) 5. What is MRP group and what is the use of it? The MRP group contains all the materials from the point of view of MRP for assig ning special control parameters for the total planning run. These control parame ters include, for example, the strategy group, the consumption mode, and the pla nning horizon. NOTE: If this field has not been maintained, the system uses the material type instead of the MRP group. In this case, the material type has to b e maintained as the MRP group in Customizing. MRP Groups In this step, you can carry out the total maintenance of the MRP grou ps and you can allocate a material type to an MRP group. The MRP group is an org anizational object that can be used to allocate special control parameters for p lanning to a group of materials. You can maintain MRP groups if planning control per plant is not precise enough for your requirements and you want to allocate certain material groups different control parameters from the plant parameters. For this purpose, MRP groups are defined with these specific control parameters and are assigned to the material in the material master record (MRP 1 screen). F or example, the following control parameters can be set for the total planning r un: the creation indicator for the plarequisitions, MRP lists, and so on) the pl anning horizon the consumption mode The following is valid for total planning an d single-item planning: for all materials without an MRP group, the system uses the plant parameters, or the entries in the initial screen of the planning run f or all materials with an MRP group, the system uses the parameters recorded in t he MRP groupnning run (creation of purchase

1. If you have released Prdn order today and it had gone to shop floor. Next day it was found that there is shortage of material. What will you? 2. How you defi ne Standard Cost and Variable cost in PP? 3. Where can you find Read PP Master i n SAP(PP)? 4. What are all the settings done for configuring integration of PP w ith FICO? 1. Do availability check. You will get missing parts list. Procure tho se missing parts. Then confirm the production order. One more thing you can do, change customize setting so that user cannot release if parts are missing during order release. 2. Standard cost is the cost which is fixed for a period, variab le cost is varying with period. As for example cost of semi finished, finished m aterials are fixed & cost of raw materials are varied. 3. You will find in maste r data tab page of production header data overview, CO02 - Read PP Master Data. Also from Functions menu you will get Read PP Master Data. This means that you w ant the system to re-update the production order with the latest BOM structure. 4. Assigning of Cost center to work center. Assigning Activity type to work cent er, Standard Cost estimate, Costing Run, Order settlement, Product costing. --1. Can MRP be carried out for one particular level of a bom ( Level code : 0001/00 02 etc). Yes it can be done by running for specific materials (Single Material S ingle Level) 2 How Requiements( PIR,Sles Order, Customer Requirement) are reduce d after they are produced? Reqmts are reduced automatically after Delivery is ma de to the Particular Order

(In case of Strategy 11, the PIRs are consumed after the GR for Production Order ) 3. Can't one material be assigned to more than one operation in a routing? One material from a BOM CANNOT be assigned to different Operations. It can be done by defining the material for so many times as required in the BOM 4. How to inse rt an inspection checkpoint at the end of an operation? If in process sample is to be defined, assign inspection type 03 in the Material Master. Then create MIC s and assign them in the Routings. System automatically generates the Inspection Lots 5. Where we have to specify the teardown time in one operation? Teardown t ime can be defined as one of the Standard Parameters... 6. How the process time is calculated in a WC when both labour, Machine categories exist? Scheduling is done based on the Capacity Category we define in the Workcenter 7. How to create opbject dependencies in a BOM FOR A CONFIGURABLE MATERIAL? Go to Extras -> Obje ct Dependency -> Assign For this U need to create Characteristics and Class (of Class Type 300) earlier 8. Can any body explain me why work scheduling view is r equired for semi finished and finished products? (Because we'll mention all deta ils in MRP views) A) We need to maintain working scheduling view in order to mak e that finished or semi finished goods available for production as we assign pro duction scheduler and production scheduler profile in this view, if not maintain ed conversion of planned order to production will not be possible. 1. What are Traffic Lights in MRP? red = the stock is not available yellow - the stock is in average level stock green = the stock is available 2. What is MRP L ist and what is the use of it?

Definition of the MRP List The system creates MRP lists during the planning run according to how you set the creation indicator. These lists contain the plannin g result for the material. The MRP list always displays the stock/requirements s ituation at the time of the last planning run and it also provides a work basis for the MRP controller. Changes that are made after the planning date are not ta ken into consideration, so the list is static. MRP lists are stored in the syste m until they are either deleted manually or replaced by new lists from a subsequ ent planning run. 3. What is the use of Stock Requirement List? In the stock/req uirements list, the most up-to-date stock and requirements situation is displaye d. The main difference between the MRP list and the stock/requirements list is t hat each time the stock/requirements list is called up, the system selects the v arious MRP elements and displays the most up-to-date situation. You thus always see the current availability situation of the material in the stock/requirements list. Changes that are made after the planning date are displayed directly, so the list is therefore dynamic. Stock/requirements lists are not saved in a fixed state in the system, but are subject to change and only exist in the working me mory. Comparison The screen layout of both lists is basically the same. The syst em automatically runs the rescheduling check directly when both lists are create d and puts forward rescheduling proposals. The number of exception messages disp layed in each list is roughly the same. The only difference lies in the fact tha t, due to the nature of the list, no exception messages can occur for newly plan ned MRP elements in the stock/requirements list. Directly after the planning run , both lists contain the same information. As soon as a change relevant to MRP i s made, the system updates the information in the stock/requirements list. As st ock/requirements lists are subject to change, they cannot be set with a processi ng indicator. 4. What is MRP controller Means? The MRP controller is a person or a group of persons responsible for monitoring material availability. You can us e the number entered here, for example, to select the planning results per MRP c onroller. Every material that is relevant to the planning run must be assigned a n MRP controller number in the material master record.

You can also determine a special person for backorder processing who receives a mail if a goods receipt was posted for a missing part. You must enter the mail n ame of this person in the field entitled, recipient name. In addition, you can d efine a person or a group of persons, who are to informed if you send a mail fro m the MRP list or stock/requirements list to the MRP controller for the material displayed. Actions 6. What is Purpose of Schedule Margin Key? In this step, you specify the floats for determining the basic dates of the planned orders. The floats are allocated to the material via the release period key in the material master record. Openin g period The opening period represents the number of workdays that are subtracte d from the order start date in order to determine the order creation date. This time is used by the MRP controller as a float for converting planned orders into purchase requisitions or into production orders. Float before production The fl oat before production represents the number of workdays that are planned as a fl oat between the order start date (planned start date) and the production start d ate (target start date). On the one hand, this float is intended to guarantee th at delays in staging a material do not delay the production start. On the other hand, the production dates can be brought forward by means of the float to cope with capacity bottlenecks. Float after production The float after production sho uld provide a float for the production process to cope with any disruptions so t hat there is no danger that the planned finish date will be exceeded. You plan t he float after production between order finish date (planned finish date) and sc heduled end (target finish date). Release period The release period represents t he number of workdays that are subtracted from the order start date in order to determine the production order release. The release period is only relevant for production order management. 7. What is opening period? Opening period

The opening period represents the number of workdays that are subtracted from th e order start date in order to determine the order creation date. This time is u sed by the MRP controller as a float for converting planned orders into purchase requisitions or into production orders. 8. What is SLA ? Service Level Agreemen ts Service Level Agreements (SLA) define the attributes for service products (fo r example, maintenance, Hotline) that have been agreed upon with the customer in service contracts. The SLA confirms different parameters, such as response time , availability time and system availability. 9. What are Basic Dates? Earliest d ate for the execution of the production order. This date takes into account the float before production. If, on order creation, a planned order exists for the p roduction order or process order, then the order dates are taken from the planne d order. When scheduling the production order the system tries to adhere to the order dates (if necessary, with reduction measures). If it is not possible to ad here to the basic dates and if the control parameter in Customizing allows the b asic dates to be adjusted, the system adjusts the basic dates of the order durin g the scheduling run. If the control parameter in Customizing does not allow the basic dates to be adjusted, the order keeps the basic dates of the planned orde r. If the production order is created manually, you must enter at least one orde r date manually. The scheduling type determines, which order dates you must ente r. 10. What is planning time fence? The planning time fence specifies a period w ithin which no automatic changes are to be made to the master plan. The planning time fence is maintained in workdays. 11. What is Planning Horizon? In this ste p, you define the planning horizon. This planning horizon specifies the period f or the "Net change planning in the planning horizon". In this kind of net change planning, only those materials that have undergone a change that is relevant to MRP within the planning horizon are included in the planning run. Such material s receive a net change planning indicator in the planning file. You make this sp ecification for a plant. You can define an alternative planning horizon for MRP groups

12. What is Group BOM? Alphanumeric character string used to uniquely identify a BOM. Use If you assign a "meaningful" number to a BOM group, this gives you an additional way of accessing the BOM. The system stores the following under a BOM group: all the alternatives in a multiple BOM all the BOMs entered for a varian t BOM 13. What is costing? How it is affected the PP? Determining the material c osts of a product. When you calculate production costs using a quantity structur e, the system automatically determines the BOM and all the BOM items that are re levant to costing, in order to calculate manufacturing costs. 14. What is Meanin g of Customized Reports? The report which is not using SAP standard reports. 15. In Project the Customization is comes under Which Phase? Realization. 16. How y ou get the Ticket? After release order,the reservation will provide the ticke to pick production material. 17. What are GAPS? Some Examples? The GAPS are some i ssue in blue print that SAP cannot capture or prividing the client bussiness pro cess. 18. What is LSMW? The LSM Workbench is an SAP System tool that supports yo u when copying data from non-SAP. systems. 19. After Doing Realization How we will check whether it is working or not? Doin g Final preparation to check using the test case from user. 20. What do we do in Realization Phase?

Provide ARICEF, Configuration Documents, integration test, BPP, UAT, Unit Test a nd implements some SAP notes. 21. How to Move to the Realization Phase? You must have some blueprints to go in next phase. 22. In LSMW which is most important S tep? Maintain Object Attributes Maintain Source Structures Maintain Source Field s Maintain Structure Relations Maintain Field Mapping and Conversion Rules Maint ain Fixed Values, Translations, User-Defined Routines. Difference between MD04 and MD05 MD04 is a dynamic one. After MRP run if any user created sales order or demand b y MD61, it will get update in MD04. But in MD05 , demand created after MRP run w ill not get update. So If you want to see result of MRP run after some time or d ays, you can see in MD05..MD05 shows the planning status when the MRP was run la st time. Suppose if you want to check the stock history when last MRP run taken then it is available only in MD05. For clear meaning... If we do the GI or GR the stock value in MD04 gets updated but it will remains unchanged in MD05 until the next MRP run individual access : you need to enter a material and check the stock of that.. collective access: y ou need not enter a single material.. you can check the stock of more than a mat erial by giving the plant and MRP controller.. > MD04 - Dynamic in nature ie. It shows current situation for stock. > MD05- Sta tic in nature, only shows result of last MRP run, but in between if any procurem ent is raised is not considered/updated in it. > MD05 is MRP list, which also sh ows the error messages generated at the time of MRP run and inturn allows you ta ke the further actions based on this list... > MRP list is optional ie. if you w ant then MRP can be activated / deactivated as per your requirement from SPRO se ttings. > for Both above list individual and collective access is given...Indivi dual is given to access the results for indivual material...while collective is given to access the collective material... MD04: Stock requirement list: which gets updates and changes in stocks & require ments instantly. MD05: MRP list which will get updates during MRP run. In a sens e soon after MRP Run both MD04 & MD05 are same. MD04 : Dynamic instant updation.

MD05: static list . In a sense, it get updated only during MRP RUN. Hope it is c lear. Difference between Engineering BOM, Costing and Production BOM? The Engineering/design BOM includes all the components of the product and their technical data from the design point of view. This BOM is generally not linked t o any order.If you use Engineering as usage, then you can not use in production order, only for planning you can use i.e. MRP The impact of different usage is i f you create a BOM with costing, then you can use it in production costing only. The production BOM contains all the items required from the production and asse mbly point of view. Only items relevant to production, for which production data (such as the issue storage location) can be entered, are required. which get co pied to order. While creating the BOM you need to define th BOM usage which defi nes the area (such as engineering/design or production or sales or costing) wher e a BOM can be used. with usage 1 it is for manufacturing with usage 2 it is for engg/design If you us BOM usage 3, universal it can be used for manufacturing a nd engg /desig Production Scheduling Profile Profile that you can use to specify that certain business transactions are carried out in parallel in a prod uction order / process order (you can, for example, create and release an order at the same time, or release an order and print the shop papers) trigger an auto matic goods receipt specify an overall profile for capacity leveling Use The production scheduling profile is copied into the order during order creation . Dependencies You can assign a production scheduling profile to a material production schedule r The assignment to a material has a higher priority. PSP--- Production Schedulng Profile are set of controls asigned to a Material.

What are the controls Order Release with the Creation of production order . Sche duling with the Order Release Auto Goods Receipt Capacity Profile Automatic Batc h creation with the Production order for the header material Order type for the system to select When we convert the PLanned order to Prd order. In this step yo u can create production scheduling profiles for specific plants. In a production scheduling profile, you can specify that in a production order or process order particular business transactions are carried out in parallel order release on o rder creation generation of document link from material master on order creation generation of document link from BOM on order creation printing on order releas e scheduling on order release generation of document link from material master o n order release generation of document link from BOM on order release specify th at only partial quantities are to be confirmed in an availability check specify that automatic goods receipt should take place enter an overall profile for capa city leveling specify how the capacity requirements of operations should go into the basic load specify when finite scheduling is carried out in the capacity av ailability check specify that for the confirmation no deficit quantities are upd ated no surplus quantities are updated neither deficit nor surplus quantities ar e updated an adjustment of the operation and component quantities to the actual values takes place make various specifications in the area of batch management: automatic batch creation on order creation branch to batch classification on cha nging a batch extended batch classification via Customer Function Call specify t hat only transport requirements are created if transport requirements can be gen erated for all components in the operation specify that when transport requireme nts are generated either the committed quantity or the required quantity are tak en into account specify that the creation of transport requirements takes place automatically specify which order type is proposed depending on the business pro cess (make-to-stock, make-toorder, engineer-to-order, order without material) Yo u can assign a production scheduling profile to a material (work scheduling scre en in material master) production scheduler (Customizing) The assignment to the material has a higher priority. The production scheduling profile is copied to the production order or process o rder on order creation. Activities

1. Create the necessary production scheduling profiles. 2. Assign the profiles t o the appropriate materials or production schedulers. Production Scheduler Defin e production scheduler In this step, you define the production schedulers for yo ur plants. In addition to this, you can assign a control profile to each product ion scheduler. By assigning production schedulers to materials within the applic ation, you can define responsibilities for a materials within production activit y control. Actions 1. Create your production schedulers. 2. If necessary, assign profiles to your production schedulers. Safety Time Time buffer for covering product requirements. The safety time requires that a r equirement should be covered not by the requirements date/time but by a correspo ndingly earlier date/time. Therefore, early receipts should be used or created a ccordingly during planning to cover a requirement. In Production Planning and Detailed Scheduling (PP/DS), only product heuristics use the safety time. A product heuristic takes the safety time into consideratio n by subtracting the safety time from each requirements date/time at the start o f a planning process; in other words, it shifts each requirements date/time to a corresponding earlier date/time. The net requirements calculation takes place o n the basis of the earlier requirements dates/times. When new receipt elements a re created for an uncovered requirement, the early requirements date/time is reg arded as the desired availability date/time. The safety time is location product specific. You enter it in the location produ ct master on the Lot size tab page under Determination of quantities and dates i n the safety days supply field. The safety time entered is only working time. Dur ing planning, the system determines the working and nonworking times from the lo cations production calendar. Functions of Production Version Can somebody enlighten me on the functions of production version and some tips o n its configuration? Production Versions are used to describe the production pro cess to be used for planned / production order. You can use the production versi ons based on: 1. Lot size qty 2. Bom explosion dates 3. Based on MRP Group

Why is it required? Suppose you have 2/3 production lines and 2/3 alternative BO Ms to produce one FG. How system will come to know which BOM and Routing to be u sed. This is done thru Prod.Version. In production version we maintain the combi nation of BOM and routing. Also it can be designed with lot size or validity per iod. Go to MM02--->MRP4 / Work scheduling view ----> Prod.Version. Enter the val idity period and lot size. After entering the reqd. routing no. and BOM alternat ive , carry a check. After getting the Green signals ,Continue. Thus you have sa ved the prod. version. Mass processing TCode- C223. Does this mean that I have t o activate all the BOMs if in case I have 3 alternative BOMs? if yes, then, will i t these 3 BOMs be exploded in MRP? Im just worried coz I might bloat our inventory if there are three active BOMs. No.First of all need not worry about the BOM expl osion. As I told you earlier which BOM and which Routing is decided by Prod.Vers ion. So in MRP the active prod.version only will be considered. Thus active BOM and active Routing will be used for MRP. The question comes: How to deactivate the alternative BOMs and Routing? Two Ways : 1. You lock all other non-relevant Prod.Versions in MM02 of the FG/SFG materia l.(Every alternative BOM and routing forms a Prod.Version) Thus even if there ar e 2/3 prod.versions System will go and check for Unlocked prod. version and use it. 2. If you don't want to do this business of "Lock & Unlock" just place the r equired version at the first place in list of prod.versions in MRP4 view of the material.

Once system finds the first prod.version it will not spend energy in searching o ther alternatives. Also please.don't forget to maintain the selection value of " 2" in MRP 4 view for BOM selection. This will enable you to start the use of pro d. version functionality in SAPPP.(very good tool for practical purposes, costin g and MRP). KANBAN ameset.htm The KANBAN method for controlling production and material flow is based on the a ctual stock quantity in production. Material that is required on a regular basis is continually provided in small quantities in production. Replenishment or the production of a material is only triggered when a higher production level actua lly requires the material. This replenishment is triggered directly in productio n using previously maintained master data. The entries you have to make in the s ystem have been reduced to a minimum, for example, the scanning of a bar code. A ll other actions in the system are carried out automatically in the background. With KANBAN, the production process controls itself and manual posting is reduce d as far as possible. The effect of this is a reduction in lead time and in stoc k. In KANBAN, the signal for material replenishment can be triggered, for exampl e, by the work center that requires the material (demand source) by sending a ca rd to the work center that is responsible for manufacturing the material (supply source). This card describes which material is required, the quantity of the ma terial required and where the material is to be delivered. The name KANBAN origi nally stems from these cards, which are called "kanban" in Japanese. When receiv ing the material, you can automatically post the goods receipt at the demand sou rce by a further kanban signal by bar code, for example. The following graphic i llustrates the KANBAN process:

Implementation Considerations If you want to make full use of the KANBAN technique, your production must fulfi ll a number of preconditions: The consumption of the kanban parts should be rela tively constant within an interval which is longer than the replenishment lead t ime of a kanban. If large quantities of a material are required for a certain pe riod, and then the material is not required at all for a certain period, a large number of kanbans are required to guarantee material availability. This means t hat relatively high inventory levels exist when the material is not required. The supply source has to be able to produce a large number of lots within a shor t interval. To this end, the setup times in production have to be reduced to a m inimum and the reliability of production has to be increased. Waiting until seve ral kanbans for one material have been sent to the supply source before starting production defeats the whole point of the KANBAN method of production. Difference between MD04, MD05, MD06 and MD07 MD04 - MRP Display Stock Requirements List MD04 provides a display of the existi ng, immediate availability of a single material within a plant. The display will show on hand inventory, open requisitions, open purchase orders, open stock tra nsport orders and reservations made against a material. Every time the list is d isplayed or refreshed, it will update with the most current information. MD05 Individual Display of MRP List MD05 provides a snap shot of the condition of a s ingle material within a plant as of the last time MRP was run. The display will show on hand inventory, open requisitions, open purchase orders, open stock tran sport orders and reservations made against a material. MD06 - Collective Display of MRP list MD06 provides a collective list of all mat erials run during the MRP process. Parameters may be set to view certain criteri a across all materials. The same detailed information detailed in MD05 may also be obtained by using the drill-down features. MD07 - Stock Requirements Collective Display MD07 provides a collective list of all materials within a plant. Parameters may be set to view certain criteria acr oss all materials. The same detailed information provided in MD04 may also be ob tained by using the drill-down features. REWORK Separate Order Type is created for Rework and to capture the cost in Order Heade r>Settlement Rule>Parent Order is provided in input. Phantom Items Definition

A phantom item is a sub-assembly in the BOM that does not actually exist in inve ntory. It is used to simplify the BOM. Although the phantom item appears in the BOM, the Production Order will show the components needed to make the phantom it em rather than the phantom item itself. An item can be defined as a phantom item in the Item Master Data. Furthermore a Production Order cannot be created for a phantom Item/Bill of Mate rial as it is not a stock item. Labels parameters MRP The MRP will explode the phantom items and create recommendations for its co mponents. The phantom item will be displayed in the MRP result window without re commendations for information only. Production Order The Production order will e xplode the phantom BOM and display its components in the required order. In the example below, in the production order, the Components 1 to 6 will appear, but n ot Phantom 1 and 2. The BOM requirements of different departments in the same co mpany can be different. The engineering department could create a multi level BO M to define an engine .The manufacturing department could then include this BOM as single phantom item. Phantom items are typically used in multilevel 'Bill of Materials' (BOM), where a single row of a phantom item serves the purpose of an entire sub-tree. These i tems do not exist in the inventory. They are designed to be used in situations w here several BOMs would have the same basic components. Instead of having to ent er the same multiple rows into the BOM, 1 row with the phantom item can be used. A practical application of a phantom item would be, for example, a basic cake m ix for a bakery. This basic recipe plus additional items is used for a variety o f different cakes. A phantom item is a sublevel in the BOM that does not actually exist in inventor y. It is used to simplify the BOM. Although the phantom item appears in the BOM, the components that comprise it appear in the Production Order. Work Scheduling View in Material Master

What is the importance of work scheduling view in material master and the standa rd values in Routing? If I am maintaining Lot size dependent information such as set time, Interoperat ion time, Processing time in work scheduling view in material master and also To tal in-house production time in MRP view under scheduling tab, what will effect on the system? Means how will the system behave in this scenario? In house produ ction time in MRP2 view, specifies the time in workdays needed to produce the ma terial in-house. In-house production time is independent of the order quantity. The system requires the in-house production time to determine the planned dates for planned orders in materials planning. You can define work scheduling times i n the material master record in one of two ways: -Either you enter the in-house production time. If required, you can get the system to update this value from t he routing. -Or you enter the setup, teardown, processing, and interoperation ti mes. If you maintain these values, the system determines the in-house production time on the basis of lot size. SAP PP Tips by : Brajesh What is the basic funda mental of "Independent lot size" and "Dependent lot size" in work scheduling vie w of a material master. I am jumbling a lot between this two to understand the b asic requirement of my client. Second thing is that you are saying that - You ca n define work scheduling times in the material master record in one of two ways: -Either you enter the in-house production time. If required, you can get the sy stem to update this value from the routing. -Or you enter the setup, teardown, p rocessing, and interoperation times. But how the system update this first option . I mean to say , is there any setting in configuration so that the system will update workscheduling time values from the routings? You need scheduling data fo r 2 types of orders, planned orders and production orders. And you can have the scheduling data in 3 ways: 1. Lot size independent in-house production time, in material master, MRP2 view. ex: if in house production time is 2 days, it will s chedule the order for 2 days, and it doesn't matter if the order size is 1 or 10 00, they are both produced in 2 days. (I never met any case that fits this situa tion)

2. Lot size dependent in-house production time, in material master, Workscheduli ng view. ex: if you have 5 day setup time, and 1 day production time for lot siz e of 10, then your order will be scheduled according to the order size. if your order is for 10, then your total production time will be 5 day + 1 day x 10 / 10 , which is 6 days. If your order is for 100, then your total production time wil l be 5 day + 1 day x 100 / 10, which is 15 days. 5 day setup time will not chang e when the order quantity changes, because you make the setup once at the beginn ing of the production, and use the same setup during whole production. 3. Lot si ze dependent in-house production time, in routing. The same calculation of above will be used for this. So, which of these data is used for the 2 order types? F or the planned orders, for default, system uses the times in number 2 above. If that data is not entered, system will use the time in number 1 above. If you wan t the system to use the routing data, then you should use lead-time scheduling p arameter in MRP run, then system will use data in number 3 above. (The idea behind this is, MRP run always takes long time, and if you want it to use routing data, that will also increase this run time. Therefore, you can use routing but take results after long MRP run time, or you can use approximate tim es but take the results after short MRP run. This was very crucial before, becau se at those times hardware technology was not enough to process too much data in short time, when MRP run was taking days and days. But now is not that crucial, that's my personal opinion. As I said before, you can use routing data but take results after long MRP run time, or you can use approximate times but take the results after short MRP run, however, there's one other way which is a combinati on of these two: You can use the system to update the data in number 2 using the data in number 3, which is called the update of material master from routing. I n that case, the approximate production times in material master will be as clos e as possible to the actual production times. In that case, not only MRP run wil l not take long time, but also we will get much better results.) For the product ion orders, always the routing data is used for scheduling. Now, I am cleared that what is independent and dependent lot size. but still the re is one confusion in my mind that where did we mentioned this lot size i.e 10, 100 as per your example in case 2. Secondly, I didnt understand your second last sentence (i.e.the approximate production times in material master will be as cl ose as possible to the actual production times). Can you please clear me this se ntence with suitable example. You enter the lot size on the Work scheduling view of material master, for the lot size dependent times, for my example you enter 10 as lot size. And the approximation is like this: In the material master, you enter the production times as DAYS, but in the routing you can use MINUTES, even seconds. Therefore the most detailed and accurate production times can be enter ed in routing, in material master you can enter only days, which will be the app roximate value.

If your routing is, for lot size of 10, setup time is 3 hours and production tim e is 50 minutes, when you update the material master from routing, system will w rite 3/24 days for the setup time, and 50/1440 minutes for the production time, because it has to convert it to days. But still I dont understand that where I h ave to mentioned that lot size 10 or 100? And second thing is that, If I have to use routing data for planned order what should I have to do? Shall I have to me ntioned lead time scheduling in MD02? You enter lot size in material master, on workscheduling view. and yes, you have to mention on md02 screen that you want l ead-time scheduling. You mean to say I have to enter that 10 or 100 in base quan tity of work scheduling view of material master? Yes. MRP Area in MD02 and MD03 Number of the MRP area for which material requirements planning should be carrie d out separately. An MRP area represents an organizational unit for which you can perform material requirements planning separately. An MRP area can include one or several storag e locations of a plant or a subcontractor. You can define MRP areas in a plant. By defining MRP areas, you can perform MRP for each area. This means the right q uantity of materials can be provided on time for each area, such as a production line, a storage location for spare parts, or subcontractor stock. Definition The MRP area represents an organizational unit for which material requirements p lanning is carried out independently. Basically, there are three types of MRP ar ea: Plant MRP Area The plant MRP area initially contains the plant together with all its storage locations and stock with subcontractors. When you have defined MRP areas for storage locations and for subcontractors and you have assigned the materials, the plant MRP area is reduced by exactly this number of subcontracto rs and storage locations. This is because they are now to be planned separately. MRP Areas for Storage Locations

You can define an MRP area that consists of a particular storage location, by cr eating an MRP area and assigning the storage location to it. Material requiremen ts for this storage location are then planned separately from the rest of the pl ant. You can also group several storage locations into one MRP area, by creating an MRP area and assigning the storage locations to it. These storage locations are then planned together. A storage location of a plant may be assigned to only one MRP area. MRP Areas fo r Subcontractors You can also define an MRP area for each subcontractor. A subcontractor may be assigned to only one MRP area. An MRP area of the subcont ractor type may also only contain one subcontractor. The following graphic shows an example of how a plant can be divided after the implementation of MRP areas: Use You can carry out MRP specifically for the determined MRP areas. This enables yo u to carry out differentiated material requirements planning. The requester can be, for example, the production on a particular assembly line or a subcontract o rder. The MRP area allows you to have specific control over the staging and proc urement of important parts produced in-house and purchased parts for each shop f loor area. You can, however, also plan the provision of components for the indiv idual subcontractors. MRP areas of the storage location or subcontractor type ar e only suitable for: components that are planned and produced for stock finished products that are planned and produced for stock. By assigning a storage locati on in a sales order or by entering an MRP area when creating the planned indepen dent requirements, you can define whether a material is planned in the plant MRP area or in the MRP area of the storage location. Finished products and importan t assemblies intended for make-to-order or engineer-to-order production are alwa ys planned in the plant MRP area. The planning run takes into account the planni ng with MRP areas as follows:

If you do not enter a separate scope of planning, the system plans the whole pla nt, that is, all MRP areas in the plant, during the total planning run. If you w ant to carry out a total planning run for a particular MRP area only, you must s pecify the required MRP area in the scope of planning. During single-item, multi -level planning, the system plans the selected material in the MRP area entered. In addition, the system takes into account planning file entries from other MRP areas, for example, if the material is to be procured using stock transfer. Dur ing single-item, single-level planning, the system plans the selected material i n the MRP area entered only. Structure You define the MRP areas in Customizing for MRP. You can thereby assign the foll owing to an MRP area: one or more storage locations (example: you want to carry out planning for a particular assembly line and therefore assign a production st orage location to the MRP area) a subcontractor. You assign the various MRP areas to the materials in the material master. For th is, you create an MRP area segment for a material for every MRP area, in which i t is used. In this MRP area segment, you can define MRP parameters such as, for example, the lot size or MRP type. This allows you to plan the material differen tly in the MRP area from how you plan it in the plant MRP area. MRP with MRP areas for the material is not activated until the material has been assigned to an MRP area. If you have not assigned a material to an MRP area, th at is, you have not created an MRP area segment in the material master, the mate rial will continue to be planned in the plant MRP area only. If you have assigne d an MRP area to it, the system can plan it in the plant MRP area and in the ass igned MRP area. Integration You can carry out material requirements planning for MRP areas using all MRP pro cedures and all lotsizing procedures. You can also carry out an independent mate rial forecast for MRP areas using your own parameters. The material consumption values are updated separately for each MRP area. A separate ATP check is carried out for each MRP area. If several storage locations belong to an MRP area, the system can also carry out a check at two levels, that is, at storage location le vel and at MRP area level. Stock Transfer from Plant to MRP Area Use If you want to plan material requirements for a storage location separately, you can create an MRP area for this storage location. You can then procure material s that are planned for this MRP area using Stock transfer from plant to MRP area .

If you plan components to be provided for a subcontractor using an MRP area of t he subcontractor type, you can also procure the components to be provided using Stock transfer from plant to MRP area . Integration The process is the same as for Storage Location MRP. In contrast to the storage location MRP, you can use all MRP procedures and are not limited to the reorder point planning procedure. Prerequisites In Customizing for MRP, you have created the special procurement key for Stock t ransfer from plant to MRP area for the plant in which the MRP area is located. Y ou have defined the following parameters: Procurement type : F for External proc urement Special procurement : U for Stock transfer Plant : Number of plant, to w hich the MRP area belongs. In the material master, you have created the MRP area segment and assigned the special procurement key Stock transfer from plant to M RP area. Features During MRP, the system generates a stock transfer reservation for the material i n the MRP area and a material reservation in the plant MRP area. The external procurement storage location that you have entered in the MRP area segment of the material master is used as the receiving storage location. If you have not maintained this field, the system uses the receiving storage location that you entered for the MRP area in Customizing. The actual procurement is proc essed by the plant. With stock transfer to the MRP area, you carry out the trans fer posting for the material with reference to the reservation.

MMD1 - Create MRP Profile - MRP profile is a useful entry aid and makes it easie r to manage MRP data. You define which fields are filled with values when MRP da ta is entered in the material master record, which of these values can be overwr itten and which not. You use the information stored in a profile is standard inf ormation that is needed again and again in similar constellations when material master records are maintained. SAP MRP Profile - How To Used It I do know what a mrp profile is, how to create it, change it etc. but what I don t know is where and how do we use it. I have not seen any key or tab indicating mrp profile. Then what is it? What are tcodes mmd1, mmd2 all about? MMD1 is the transaction code for creating MRP profile. In MRP profile you can create your own record or file, when you use the transact ion. Give the name and description to your own profile and you can select the fi xed values and/or default values from the option given of the MRP fields. For eg . if you select or tick the check box against procurement type in the fixed valu es column then click on screen 1 to fix the value. You get the option of differe nt procurement types, if you select from these option and save , your profile is created . Now, go to material master in the MRP2 screen and go to main menu -->edit-->MRP profile. In this, you can assign your profile which has been created by you. So now you will see that the procurement type has become fixed value for your mater ial and which cannot be changed in the material master .

You can only do the changes if you change your profile again (MMD2) or do not as sign any profile. Similarly, you can store the default values if you require in MRP profile. What is Production Order Settlement? Settlement is nothing but offsetting the costs to the FI portion. CO objects car ry costs, which needs to be re-assignd to the G/L accounts where it comes from. CO never generates any data, it only tracks the same onto some objects which are analysed for definite purpose of tracking the resources which are debits in FI as costs in G/L). In simple words, the flow is like following 1. Direct Costs ar e incurred ( like material consuption ) in form of issues to prod orders. These are captured in G/L. Whenever you issue, consumption account is debited. But are also debited to prod order as Consumption...Dr Inventory.......Cr 2. Indirect c osts are incurred in form of debits to Cost centers in G/Ls. These are actually to be allocated & absorbed in Products via Prod Orders. So it is allocated to pr od orders via diff media like costing sheet or Indirect activity allocations. He re again Prod order is debited with some amount. When the costs are incurred the se should be transffered futher when the order is closed or deliverd to stock. S o whenever you deliver the order, the follwing entry is generatedInventory....Dr Cost of Prod /Mfg Variance.....Cr If your Fin Goods' predetermined cost are sam e as that of actual costs incurred, there will no price difference account affec ted. But when your plan cost ( target cost ) & actual costs are differnet, the d ifference is OFFSET or SETTELLED to price diff accout asCost of Prod / Mfg Var.. ..Dr Price diff acc..........Cr Note that Price diff accont is not created as CO ST ELEMENT. If actual cost is less than target cost, entry would be reverse. Checking the Production Order Settlement 1. Call up the transaction as follows: Menu Path - From the Production Control n ode, choose Order Display. Transaction Code CO03 2. Enter the following data: Fi eld Data

Order Display overview 3. Choose 4. To analyze the current settlement rule, choo se Header Settlement rule . The system displays the settlement rule and the dist ribution rules it contains. In this case, the sales order is the receiver. 5. Ch oose The Display Production Order: Header screen appears. 6. Choose Goto Costs A nalysis . The plan/actual comparison for the order is displayed. The differences between the planned and actual costs correspond to the overhead costs and will be calculated in a separate run. 7. Choose until the overview tree appears. In t he dialog box, choose Yes . 8. Call up the transaction as follows: Menu Path Number of your production order Select Transaction Code 9. Enter the following data: Field Order Period Fiscal year Tes t run Dialog display 10. Choose 11. Choose until the overview tree appears. 12. Call up the transaction as follows: Menu Path From the Production Control node, choose PeriodEnd Closing Overhead Calculation Individual Processing KGI2 Data Number of your production order Current period C urrent year Deselect Select Transaction Code 13. Enter the following data: Field Order Settlement period Pos ting period Fiscal year Processing type Test run From the PeriodEnd Closing node, choose Settlement Individual Processing KO88 Da ta Number of your production order Current period Current period Current year Au tomatic Deselect

14. Choose 15. Choose until the overview tree appears. 16. Call up the transacti on as follows: Menu Path Transaction Code 17. Enter the following data: Field Order Display overview 18. Choose 19. Choose Goto Costs Analysis . The settled order is displayed. 20. Choo se until the overview tree appears. In the dialog box, choose Yes . From the Production Control node, choose Order Display. CO03 Data Number of your production order Select Discrete Manufacturing Vs Repetitive Manufacturing Below picture clearly depicts the differences between Discrete Manufacturing and Repetitive Manufacturing Typical of order-based production is the frequent swit ching from one product to another. Each product is manufactured in individually defined lots. Costs are calculated per order. Inrepetitive manufacturing, the sa me product is produced on a certain production line over a longer period of time . In production, a total quantity is produced according to a certain production rate over a certain period of time. Costs are collected periodically at a produc t cost collector. In order-based production, you usually have a changing sequenc e of work centers where the products are processed. The order of work centers is determined in routings, which can often be very complex. Semi-finished products are frequently placed in interim storage prior to further processing. Repetitiv e manufacturing usually involves a relatively constant flow through production l ines. The routings of the individual products are very similar. With production orders, component materials are staged with specific reference to the individual production orders. Confirmations for the various steps and orders document the work progress and can be used for fine control. In repetitive manufacturing, com ponents are often staged at the production lines without reference to a particul ar order. The confirmations (backflushes) are usually executed periodically with no reference to an order (for example, all the quantities produced in one shift ).

Discrete This scenario describes the manufacture of a product based on productio n orders. Discrete manufacturing is characterized by requirements that occur on an irregular basis and a workshoporiented process. The Discrete Manufacturing sc enario can be used in different variants, production by lot size, make-toorder p roduction and assembly processing. The variants differ mainly in the type of pla nning conducted before-hand and in the relation to the sales order. Repetitive M anufacturing This scenario describes production planning and control within a re petitive manufacturing environment. In repetitive manufacturing, master plans ar e typically created on a period and quantity basis (reduction in individual lot and order-specific processing). A quantity of one product is manufactured over a certain period. The product is processed in a constant flow and interim product s are generally not stocked. In repetitive manufacturing, you usually find that the effort required for production control is significantly less than is require d for single lot and order-based production control and the recording of actual data is kept simpler. Repetitive manufacturing can be used for various industrie s, such as the consumer packaged goods industry, the electronic industry, packag ing industry, for example. You can use Repetitive Manufacturing purely for maketo-stock production, or in a sales orderoriented environment, such as found in t he automotive industry. Discrete Manufacturing : - Order-based production using production order - Produ ction in order lot sizes - Status maintenance (created, released...) per order Availability check for material, capacity, PRTs per order - Material provision controlled per order using material reservations - Order backflush, operation ba ckflush - Cost monitoring per order or per product Repetitive Manufacturing : - Quantity- and period-based planning (planning perio ds) and production - Planned orders (run schedule quantities) authorize producti on; production orders not needed (no conversion). - Repetitive production: The s ame/similar products produces over a longer period of time The aims of using Rep etitive Manufacturing are the following: - Creating and processing production pl ans based on periods (rather than individual lots and orders) - Reducing the adm inistration costs for production control and simplification of completion confir mation via backflushing, while at the same time still being able to use the full range of PPC functions. - Reducing controlling costs. Repetitive Manufacturing - Basic Cycle

Master data: ************ * Material Master: * In this you need to have the REM indicator activated. * A Rem Profile attached * Production version with BOM, rou ting, production line( it is nothing but a work centre) REM indicator activated. * BOM * Routing( Routing or rate routing both will work fine for the rem) * Pro duction version. Configuration: ************* 1. REM Profile Process Flow: *********** 1. First Create all the required material master as in dicated above. 2. Once this is done now you have to create a product cost collec tor * REM- works on the Product cost by period. * So the Product cost collector is a CO order which helps to collect all the cost at a material / production ver sion combination to an internal order * Which later settles the variance against a material * You can create the Product cost collector with KKF6N 3. during the creation of the Product cost collector it will prompt you to do the Preliminary cost collector- for rem you need to run this one also. 4. Once the above is done , now you have to run the Cost estimate Mark and relea se the same with CK11N AND CK21(you can reach the help of FICO consultant to com plete this process) 5. Once the above is done now the master data and prerequisi tes are complete and ready for the PLANNING AND CONFIRMATION of the product/mate rial. 6. Now you can maintain the demand in the md61 for the required quantity. 7. Once the demand is maintained and the MRP is run you will be able to work wit h the REM PLANNING TABLE. 8. One of the best features in the REM is the Rem Plan ning table 9. This can be accessed with the T.CODE MF50. 10. Here when you try t o access the MF50 you have multiple choices to make selections and also restrict ions.

11. Inside the planning table you can see 2 major things a. In the upper section of the planning table you can see the available/ actual capacity b. In the lowe r section of the planning table you can see the demand and few other attributes like stock, ROC, Production version etc. 12. This MF50 helps you to make the Planning- the Creation / modification of the planned order are very dynamic in this screen and is well integrated with all t he functionalities. 13. Once all the planning is done with the MF50 then comes t he EXECUTION ie) our confirmation. 14. In REM production confirmation is called as MATERIAL BACK FLUSH. 15. you can access the Material back flush with MFBF / M F42N 16. HERE in MFBF you can have some mandatory parameters like Quantity, mate rial, production version, date etc which has to be given as input , and the syst em will in turn perform the back flush. 17. the MFBF is single screen which allo w you to perform the below function * Material back flush * Excess consumption * scrap posting * Only activity posting and few more. 18 Once the back flush is d one the stock gets posting 19. You also have cogi/mf47 FOR clearing the post goo ds movement errors for automatic posting. Planning Horizon Planning period in which planned transportation activities are to be executed. Y ou define the planning horizon in the planning profile (see Planning Profile). T he planning horizon defines the possible period of time in which the system can schedule planned transportation activities. Structure You do not define the planning horizon with precise dates and times, but enter i nstead a duration starting from the current date. The system then automatically determines the start and end date and the start and end time. If the planning ho rizon is not to start on the current date, but instead at a later time, you can define an offset. Here you can specify whether the system is to round the planni ng horizon to complete days. The planning horizon must not lie in the past. For the planning horizon, you can specify the time zone in which the system is to ca lculate the horizon. According to this, the planning horizon is defined as follo ws:

Start of planning horizon = current date + defined offset Here, the offset is made up of the offset in days and the additional offset (in hours and minutes). End of planning horizon = start of planning horizon + defined duration of planni ng horizon Here, the duration of the planning horizon is made up of the duration in days and the additional duration (in hours and minutes). If you s when always zon is specify a factory calendar, the system takes into account non-working day calculating the start of the horizon. In this case, the planning horizon begins on a working day. The following figure shows how the planning hori defined:

Difference between MRP vs MPS MD40 - MPS Explain the difference between MRP & MPS. Though both components give s you the requirement list, what we gain out of MPS run rather than running MRP. What is the main idea behind this? The following might help in explaining the difference between MPS and its counte r part MRP. MD40 - MPS - Master Production Scheduling (A MRP type) Master Produc tion Schedule (MPS) : MPS operates within only one level of the BOM, While MRP c an be utilized throughout all levels of a materials BOM. If a MPS is run on a mat erial, the necessary orders are planned at that level. Dependent requirements (i f any) are placed on the next BOM level down, and then the process stops.

Main Idea : Master production scheduling (MPS) is a form of MRP that concentrate s planning on the parts or products that have the great influence on company pro fits or which dominate the entire production process by taking critical resource s. These items are marked as A parts (MPS items) and are planned with extra attent ion. These items are selected for a separate MPS run that takes place before the MRP run. The MPS run is conducted without a BOM explosion so that the MRP contr oller can ensure that the Master schedule items (MSI) are correctly planned befo re the detailed MRP run takes place. The master production schedule is a line on the master schedule grid that reflec ts the anticipated build schedule for those items assigned to the master schedul er. The master scheduler maintains this schedule, and in turn, it becomes a set of planning numbers that drives material requirements planning. It represents wh at the company plans to produce expressed in specific configurations, quantities , and dates. The master production schedule is not a sales item forecast that re presents a statement of demand. The master production schedule must take into ac count the forecast, the production plan, and other important considerations such as backlog, availability of material, availability of capacity, and management policies and goals. Syn: master schedule. Material Requirements Planning (MRP) : A set of techniques that uses bill of material data, inventory data, and the ma ster production schedule to calculate requirements for materials. It makes recom mendations to release replenishment orders for material. Further, because it is time-phased, it makes recommendations to reschedule open orders when due dates a nd need dates are not in phase. Time-phased MRP begins with the items listed on the MPS and determines (1) the quantity of all components and materials required to fabricate those items and (2) the date that the components and material are required. Time-phased MRP is accomplished by exploding the bill of material, adj usting for inventory quantities on hand or on order, and offsetting the net requ irements by the appropriate lead times. MRP Interview Questions: What is the nee d of mrp list if stock requirement list is already there? The MRP list displays the result of the last planning run. Changes that urred between planning runs are ignored in the MRP list. In contrast to e system displays all changes in stock, receipts and issues, which have y occurred, in the stock/requirements list. Which tcode are used to run have occ this, th currentl MRP?

- MD01 is generally used to run the MRP for all the materials in a plant normall y just before go-live. - MD02 is used to run MRP for materials which have a BOM i.e multi-level. - MD03 is used to run MRP for materials which do not have a BOM i.e single level. MRP Configuration / PP Configuration 1. Plant Parameters for MRP (SPRO)

2. MRP type (MM) 3. MRP controller (MM) 4. Procurement Type(MM) 5. Special Procu rement Type if applicable (MM) 6. Lot Sizing Procedure (MM) 7. Scheduling Margin Key(MM) 8. Scheduling Parameters for planned orders through (SPRO) Detail: 1. A ctivate Plant Parameters for MRP(in SPRO) 2. MRP Type Customization(E.g, PD, M1, M2,, -in SPRO - But need not suposed to do without client's permission) 3. MRP C ontroller (in SPRO) 4. Production Scheduler Profile (in SPRO) 5. Order type Depe ndent Paremeters(in SPRO) 6. Plant Parematers(in SPRO) 7. Scheduling Parameters( in SPRO) Important T-Codes - OS23,OPL8,OPJH,OPKP, OPPQ REM - OPU5, Maintain Distribution for Planning Table, Define Distributin Keys SPRO->Production->Shop floor control->Integration->Define Valuation of Goods Rec eived MD04 -Stock requirement list: It displays current stock, all requirements and all receipts. All (-) quantities indicate demand and (+) quantities indicate what is available in stock, being p roduced/procured or planned for production /procurement. After MRP run, the avai lable quantity column is usually zero. If it has a positive value it means you a re trying to produce / procure more than what is required. Stock Requirement lis t is dynamic and it will list the Current status of the Material (Issue/Receipt/ demand). MD05 MRP list This is the Last result of the MRP run and it is very sta tic. Using this Individual material MRP result can be evaluated MD06 Collective access of MRP list This is the collective MRP list analysis. Input can be Plant code along with MRP controller. Further this can be restricted to Material data wise input or Exception groups. This can be viewed daily to view the results of the MRP run. SAP PP Master Data Tables MASTER DATA

Engineering Change Management AENR Customer and priority AEOI Revision Numbers W ork Center CRHD Workcenter Header Data CRCA Workcenter Capacity Allocation CRCO Workcenter Cost Center Assignment CRHH Hierarchy Header CRHS Hierarchy Structure CRTX Workcenter Text KAKO Capacity Header KAZY Intervals of Capacity Routing PL PO Routing Operation Details PLKO Routing Header Details MAPL Routing Link to Ma terial PLAB Relationships - Standard Network PLAS Task List - Selection of Opera tions PLMZ Component Allocation PLPH CAPP Sub-operations PLFH PRT Allocation PLW P Maintenance Package Allocation PLMK Inspection Characteristics Bill of Materia l STPO BOM Item Details STPU BOM Sub Items (designators) STKO BOM Header Details MAST BOM Group to Material STZU BOM History Records STAS BOM Item Selection STP F BOM Explosion Structure Line Design LDLH Line Hierarchy Header LDLP Line Hiera rchy Items LDLT Line Hierarchy Takt Times LDLBC Takts/No. Individual Capacities per Line LDLBH Line Balance Header LDLBP Line Balance Items LDLBT Line Hierarchy Entry and Exit Takts PRT's CRFH PRT Master Data CRVD_A Link of PRT to Document CRVD_B Link of Document to PRT CRVE_A Assignment of PRT data to Equipment CRVE_B Assignment of equipment to PRT data

CRVM_A CRVM_B CRVS_A CRVS_B Link of PRT data to Material Link of Material to PRT data Link of PRT Internal n umber to PRT External number Link of PRT External number to PRT Internal number How to create a query that is very similar to CA03? What tables contain those in formation and what are the relationships? See below routing table relationships: Table MAPL, pass input material number, plant, routing group counter. Table PLK O, field PLNNR, PLNAL eq mapl-plnnr, mapl-plnal Table PLAS, field PLNNR, PLNAL e q mapl-plnnr, mapl-plnal and LOEKZ ne ' ', take field PLNKN Table PLPO, field PL NNR, PLNKN eq plas-plnnr, plas-plnkn You will get correct result same as CA03 li st. Difference Between BADI and User Exits Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specif ic to be included in the standard delivery. Since specific industries often requ ire special functions, SAP allows you to predefine these points in your software . As with customer exits two different views are available: In the definition vi ew, an application programmer predefines exit points in a source that allow spec ific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object. In the im plementation view, the users of Business Add-Ins can customize the logic they ne ed or use a standard logic if one is available. In contrast to customer exits, Business Add-Ins no longer assume a two-level inf rastructure (SAP and customer solutions), but instead allow for a multi-level sy stem landscape (SAP, partner, and customer solutions, as well as country version s, industry solutions, and the like). Definitions and implementations of Busines s Add-Ins can be created at each level within such a system infrastructure. SAP guarantees the upward compatibility of all Business Add-In interfaces. Release u pgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Busine ss Add-Ins in SSCR.

The Business Add-In enhancement technique differentiates between enhancements th at can only be implemented once and enhancements that can be used actively by an y number of customers at the same time. In addition, Business Add-Ins can be def ined according to filter values. This allows you to control add-in implementatio n and make it dependent on specific criteria (on a specific Country value, for e xample). All ABAP sources, screens, GUIs, and table interfaces created using this enhance ment technique are defined in a manner that allows customers to include their ow n enhancements in the standard. A single Business Add-In contains all of the int erfaces necessary to implement a specific task. The actual program code is enhan ced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the sect ion on ABAP Objects. What is difference between badi and user-exists? What is di fference between enhancements and user-exists? and what is the full form of BADI ? I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure. What is the system landscape? 1) Difference between BADI and USER-EXIT. i) BADI 's can be used any number of times, where as USER-EXITS can be used only one tim e. Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not a ssign the same to other project. ii) BADI's are oops based. 2) About 'BDCMSGCOLL ' it is a structure. Used for finding error records. 3) Full form of BADI 'Busin ess addins'. 3) System land scape will be depends on your project Ex:- 'Developm ent server'-->'Quality server'---> 'Production server'...... BAPIs Definition A Business Application Programming Interface (BAPI) is a precisely defined inter face providing access to processes and data in business application systems such as R/3. BAPIs of SAP Business Object Types BAPIs are defined as API methods of SAP business object types. These business ob ject types and their BAPIs are described and stored in the Business Object Repos itory (BOR). A BAPI is implemented as a function module, that is stored and desc ribed in the Function Builder.

BAPIs of SAP Interface Types As of Release 4.5A BAPIs can also describe interfaces, implemented outside the R /3 System that can be called in external systems by R/3 Systems. These BAPIs are known as BAPIs used for outbound processing. The target system is determined fo r the BAPI call in the distribution model of Application Link Enabling (ALE). BAPIs used for outbound processing are defined in the Business Object Repository (BOR) as API methods of SAP Interface Types. Functions implemented outside the R/3 System can be standardized and made available as BAPIs. For further informat ion see BAPIs Used For Outbound Processing. Integration BAPIs can be called within the R/3 System from external application systems and other programs. BAPIs are the communication standard for business applications. BAPI interface technology forms the basis for the following developments: Connec ting: New R/3 components, for example, Advanced Planner and Optimizer (APO) and Business Information Warehouse (BW). Non-SAP software Legacy systems Isolating c omponents within the R/3 System in the context of Business Framework Distributed R/3 scenarios with asynchronous connections using Application Link Enabling (AL E) Connecting R/3 Systems to the Internet using Internet Application Components (IACs) PC programs as frontends to the R/3 System, for example, Visual Basic (Mi crosoft) or Visual Age for Java (IBM). Workflow applications that extend beyond system boundaries Customers' and partners' own developments The graphic below sh ows how BAPI interfaces enable different types of applications to be linked toge ther. BAPIs - Interfaces to the R/3 System For further background information on BAPIs refer to the document


Factory Calender - SCAL is assigned to each plant while defining plant - Enterpr ise Structure, also while creating Work Center we can assign Facory Calender, Pl anning Calender-MD25 is normally not used/required which is maintained in MRP 2 view MRP EXIT - not much use *&---------------------------------------------------------------------* *& Incl ude ZXM61U01 *&--------------------------------------------------------------------* *----------------------------------------------------------------------* * INCLUDE LXM61F01 * *---------------------------------------------------------------------* *---------------------------------------------------------------------* * example coding for User-Exit MRP *---------------------------------------------------------------------* CLEAR: NO_PLANNING, STOP_PLANNING. CASE USER_K EY. *----------------------------------------------------------------------* * m aterials of material type 'FERT' only *---------------------------------------------------------------------* WHEN '001'. IF MT61D-MTART <> 'FERT'. NO_PLANNING = 'X'. ENDIF. *---------------------------------------------------------------------* * materials with MRP type 'PD' only *---------------------------------------------------------------------* WHEN '002'. IF MT61D-DISMM <> 'PD'. NO_PLAN NING = 'X'. ENDIF. *---------------------------------------------------------------------* * reorder-point materials * (any MRP type with MRP procedure 'reorde r-point planning') *---------------------------------------------------------------------*

WHEN '003'. IF T438A-DISVF <> 'B'. NO_PLANNING = 'X'. ENDIF. *---------------------------------------------------------------------* * stop planning after lowlevel code 03 *---------------------------------------------------------------------* WHEN '004'. IF MT61D-DISST > '003'. STOP_PLANNING = 'X'. ENDIF. *---------------------------------------------------------------------* * select materia ls for one MRP controller (specified in user_par) *---------------------------------------------------------------------* WHEN '005'. UXPAR = USER_PAR. CONDENS E UXPAR. WRITE UXPAR+0(3) TO DISPO. IF DISPO IS INITIAL. EXIT. ENDIF. IF MT61D-D ISPO <> DISPO. NO_PLANNING = 'X'. ENDIF. *---------------------------------------------------------------------* * select materials of one material class (spec ified in user_par) *---------------------------------------------------------------------* WHEN '006'. UXPAR = USER_PAR. CONDENSE UXPAR. WRITE UXPAR+0(9) TO MA TKL. IF MATKL IS INITIAL. EXIT. ENDIF. IF MT61D-MATKL <> MATKL. NO_PLANNING = 'X '. ENDIF. ENDCASE. Material Management Tables EINA purchasing Info record. EINE Purchasing Info Rec ord Purchasing Data. MAKT Material description. MARA General Material Data. MARC Plant data for material MARD Storage location Data for material. MAST Material to BOM Link.

MBEW Material valuation MKPF Header Material Document MSEG Document segment mate rial. MVER Material consumption. MVKE Sales data for material. PKPF document hea der Reservation TO23 Material Groups . TO24 Purchasing groups . T156 Movement Ty pe Purchasing Tables EBAN Purchasing requisition. EBKN Purchase requisition acco unt assignment. EKBE History per purchasing document. EKET Scheduling agreement schedule lines. EKKN Account assignment in purchasing document. EKKO Purchasing document header. EKPO Purchasing document Item. IKPF Header Physical inventory d ocument. ISEG Physical inventory document items. LFA1 Vendor master general data . LFB1 Vendor Master (company Code) RESB Reservation/Dependent requirement SAP Production Planning Table Demand Management PBED Independent Requirements Data PBIM Independent Requiremen ts by Material Repetitive Manufacturing SAFK RS Header Master Data S025 LIS -- R un Schedule Quantities S026 LIS -- Material Usage S028 LIS -- Reporting Point St atistics CEZP Reporting Point Document Logs CPZP Reporting Points - Periodic Tot als MRP Records MDKP MRP Document Header Data MDTB MRP Table Structure (no data) PLSC Planning Scenario (Long-term Planning) MDFD MRP Firming Dates MDVM Plannin g File Entries S094 LIS -- Stock/Requirements Analysis Reservations RESB Reserva tions/Dependent Requirements

Planned Orders PLAF Planned Orders Discrete Production AFKO Order Header AFPO Or der Item Detail AFVC Order Operations Detail AFFL Order Sequence Details AFFH Or der PRT Assignment AFBP Order Batch Print Requests AFRU Order Completion Confirm ations AFFW Confirmations -- Goods Movements with Errors AFRC Confirmations -- I ncorrect Cost Calculations AFRD Confirmations -- Defaults for Collective Confirm ation AFRH Confirmations -- Header Info for Confirmation Pool AFRV Confirmation Pool AFWI Confirmations -- Subsequently Posted Goods Movements Classification KL AH Class Detail CABN Characteristic Detail AUSP Characteristic Values CAWN Chara cteristic Values CAWNT Characteristic Value Texts KSML Characteristic Allocation to Class KSSK Material Allocation to Class