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 level Production Versions Schedule Margin Key MRP Group MRP Type Lot Size Authorization Group in QM View - QA32 validation -Strategy 50 in Mill 200/400 + Single first level of BOM explosion only. ASAP implementation methodology - Project Preparation, 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 & MD05 What steps to implement PP Module in Company which alreadyn have all other module. What need to be done if PP not to be implemented and how costing will be done? - strategy 20 for sales order based costing Long Term Planning, Sale Operation Planning, Batch Management, Variant configuration, Product Costing, Engineering Change Management, KANBAN, Classification, Work Scheduling - importance Individual/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 alternative BOM component against Production Order Planning Horizon BOM Universal+ 2 Production BOMs, MRP Run will work on which and how - maintained in CT22 CO11N Partial & then CO50 Learn Movement types Sales Order assigned stock transferred to other Sales Order, only qty will transfer or value also? Settings for Subcon through 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 & production Order in other plant etc. Partial Plan Order to Production Order Bulk Plan order to production Order Bulk PR to PO

Material master, work center, routing, BOM and production version * Knowledge about SAP REM (Repetitive Manufacturing)

* Knowledge of Handling Unit Management * Understanding about material Planning and scheduling process. * Knowledge about PP-CO integration. * Knowledge about Scheduling Agreement, Inbound/Outbound deliveries and delivery schedules. * Knowledge about Long Term Planning * LSMW, BDC, Background jobs, Workflow, Query, Factory 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 assigning special control parameters for the total planning run. These control parameters include, for example, the strategy group, the consumption mode, and the planning 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 be maintained as the MRP group in Customizing.

MRP Groups In this step, you can carry out the total maintenance of the MRP groups and you can allocate a material type to an MRP group. The MRP group is an organizational object that can be used to allocate special control parameters for planning 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). For example, the following control parameters can be set for the total planning run: the creation indicator for the plarequisitions, MRP lists, and so on) the planning horizon the consumption mode The following is valid for total planning and 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 for all materials with an MRP group, the system uses the parameters recorded in the 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 define Standard Cost and Variable cost in PP? 3. Where can you find Read PP Master in SAP(PP)? 4. What are all the settings done for configuring integration of PP with FICO? 1. Do availability check. You will get missing parts list. Procure those 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, variable cost is varying with period. As for example cost of semi finished, finished materials are fixed & cost of raw materials are varied. 3. You will find in master 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 want 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 center, 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/0002 etc). Yes it can be done by running for specific materials (Single Material Single Level) 2 How Requiements( PIR,Sles Order, Customer Requirement) are reduced after they are produced? Reqmts are reduced automatically after Delivery is made 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 insert 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 MICs 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 time 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 -> Object 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 required for semi finished and finished products? (Because we'll mention all details in MRP views) A) We need to maintain working scheduling view in order to make that finished or semi finished goods available for production as we assign production scheduler and production scheduler profile in this view, if not maintained 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 List 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 planning result for the material. The MRP list always displays the stock/requirements situation 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 taken into consideration, so the list is static. MRP lists are stored in the system until they are either deleted manually or replaced by new lists from a subsequent planning run. 3. What is the use of Stock Requirement List? In the stock/requirements list, the most up-to-date stock and requirements situation is displayed. The main difference between the MRP list and the stock/requirements list is that each time the stock/requirements list is called up, the system selects the various 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 memory. Comparison The screen layout of both lists is basically the same. The system automatically runs the rescheduling check directly when both lists are created and puts forward rescheduling proposals. The number of exception messages displayed in each list is roughly the same. The only difference lies in the fact that, due to the nature of the list, no exception messages can occur for newly planned 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 is made, the system updates the information in the stock/requirements list. As stock/requirements lists are subject to change, they cannot be set with a processing 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 use the number entered here, for example, to select the planning results per MRP conroller. Every material that is relevant to the planning run must be assigned an 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 name of this person in the field entitled, recipient name. In addition, you can define a person or a group of persons, who are to informed if you send a mail from 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. Opening period The opening period represents the number of workdays that are subtracted 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 float before production represents the number of workdays that are planned as a float between the order start date (planned start date) and the production start date (target start date). On the one hand, this float is intended to guarantee that 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 should provide a float for the production process to cope with any disruptions so that there is no danger that the planned finish date will be exceeded. You plan the float after production between order finish date (planned finish date) and scheduled end (target finish date). Release period The release period represents the 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 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. 8. What is SLA ? Service Level Agreements Service Level Agreements (SLA) define the attributes for service products (for 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 date 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 production order or process order, then the order dates are taken from the planned 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 adhere to the basic dates and if the control parameter in Customizing allows the basic dates to be adjusted, the system adjusts the basic dates of the order during 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 order. If the production order is created manually, you must enter at least one order date manually. The scheduling type determines, which order dates you must enter. 10. What is planning time fence? The planning time fence specifies a period within 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 step, you define the planning horizon. This planning horizon specifies the period for 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 materials receive a net change planning indicator in the planning file. You make this specification 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 variant BOM 13. What is costing? How it is affected the PP? Determining the material costs of a product. When you calculate production costs using a quantity structure, the system automatically determines the BOM and all the BOM items that are relevant to costing, in order to calculate manufacturing costs. 14. What is Meaning 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 you 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 issue in blue print that SAP cannot capture or prividing the client bussiness process. 18. What is LSMW? The LSM Workbench is an SAP System tool that supports you when copying data from non-SAP. systems.

19. After Doing Realization How we will check whether it is working or not? Doing 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 and 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 Step? Maintain Object Attributes Maintain Source Structures Maintain Source Fields Maintain Structure Relations Maintain Field Mapping and Conversion Rules Maintain 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 by MD61, it will get update in MD04. But in MD05 , demand created after MRP run will not get update. So If you want to see result of MRP run after some time or days, you can see in MD05..MD05 shows the planning status when the MRP was run last 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: you need not enter a single material.. you can check the stock of more than a material by giving the plant and MRP controller..

> MD04 - Dynamic in nature ie. It shows current situation for stock. > MD05- Static in nature, only shows result of last MRP run, but in between if any procurement is raised is not considered/updated in it. > MD05 is MRP list, which also shows the error messages generated at the time of MRP run and inturn allows you take the further actions based on this list... > MRP list is optional ie. if you want then MRP can be activated / deactivated as per your requirement from SPRO settings. > for Both above list individual and collective access is given...Individual 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 & requirements instantly. MD05: MRP list which will get updates during MRP run. In a sense 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 clear.

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 to 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 if 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 assembly 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 copied to order. While creating the BOM you need to define th BOM usage which defines the area (such as engineering/design or production or sales or costing) where 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 and engg /desig

Production Scheduling Profile

Profile that you can use to

specify that certain business transactions are carried out in parallel in a production 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 automatic 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 scheduler 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 . Scheduling with the Order Release Auto Goods Receipt Capacity Profile Automatic Batch 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 you 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 order creation generation of document link from material master on order creation generation of document link from BOM on order creation printing on order release scheduling on order release generation of document link from material master on order release generation of document link from BOM on order release specify that only partial quantities are to be confirmed in an availability check specify that automatic goods receipt should take place enter an overall profile for capacity leveling specify how the capacity requirements of operations should go into the basic load specify when finite scheduling is carried out in the capacity availability check specify that for the confirmation no deficit quantities are updated no surplus quantities are updated neither deficit nor surplus quantities are 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 changing a batch extended batch classification via Customer Function Call specify that only transport requirements are created if transport requirements can be generated for all components in the operation specify that when transport requirements are generated either the committed quantity or the required quantity are taken into account specify that the creation of transport requirements takes place automatically specify which order type is proposed depending on the business process (make-to-stock, make-toorder, engineer-to-order, order without material) You can assign a production scheduling profile to a material (work scheduling screen 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 order on order creation. Activities

1. Create the necessary production scheduling profiles. 2. Assign the profiles to the appropriate materials or production schedulers. Production Scheduler Define production scheduler In this step, you define the production schedulers for your plants. In addition to this, you can assign a control profile to each production scheduler. By assigning production schedulers to materials within the application, you can define responsibilities for a materials within production activity 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 requirement should be covered not by the requirements date/time but by a correspondingly earlier date/time. Therefore, early receipts should be used or created accordingly 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 consideration by subtracting the safety time from each requirements date/time at the start of a planning process; in other words, it shifts each requirements date/time to a corresponding earlier date/time. The net requirements calculation takes place on the basis of the earlier requirements dates/times. When new receipt elements are created for an uncovered requirement, the early requirements date/time is regarded as the desired availability date/time.

The safety time is location product specific. You enter it in the location product master on the Lot size tab page under Determination of quantities and dates in the safety days supply field. The safety time entered is only working time. During planning, the system determines the working and nonworking times from the locations production calendar.

Functions of Production Version

Can somebody enlighten me on the functions of production version and some tips on its configuration? Production Versions are used to describe the production process to be used for planned / production order. You can use the production versions 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 BOMs to produce one FG. How system will come to know which BOM and Routing to be used. This is done thru Prod.Version. In production version we maintain the combination of BOM and routing. Also it can be designed with lot size or validity period. Go to MM02--->MRP4 / Work scheduling view ----> Prod.Version. Enter the validity period and lot size. After entering the reqd. routing no. and BOM alternative , carry a check. After getting the Green signals ,Continue. Thus you have saved the prod. version. Mass processing TCode- C223. Does this mean that I have to activate all the BOMs if in case I have 3 alternative BOMs? if yes, then, will it 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 explosion. As I told you earlier which BOM and which Routing is decided by Prod.Version. 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 material.(Every alternative BOM and routing forms a Prod.Version) Thus even if there are 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 required 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 other 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 prod. version functionality in SAPPP.(very good tool for practical purposes, costing and MRP).

KANBAN
http://help.sap.com/saphelp_470/helpdata/en/90/ba63da446711d189420000e829fbbd/frameset.htm

The KANBAN method for controlling production and material flow is based on the actual 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 actually requires the material. This replenishment is triggered directly in production using previously maintained master data. The entries you have to make in the system have been reduced to a minimum, for example, the scanning of a bar code. All other actions in the system are carried out automatically in the background. With KANBAN, the production process controls itself and manual posting is reduced as far as possible. The effect of this is a reduction in lead time and in stock. In KANBAN, the signal for material replenishment can be triggered, for example, by the work center that requires the material (demand source) by sending a card to the work center that is responsible for manufacturing the material (supply source). This card describes which material is required, the quantity of the material required and where the material is to be delivered. The name KANBAN originally stems from these cards, which are called "kanban" in Japanese. When receiving the material, you can automatically post the goods receipt at the demand source by a further kanban signal by bar code, for example. The following graphic illustrates the KANBAN process:

Implementation Considerations
If you want to make full use of the KANBAN technique, your production must fulfill a number of preconditions: The consumption of the kanban parts should be relatively constant within an interval which is longer than the replenishment lead time of a kanban. If large quantities of a material are required for a certain period, 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 that 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 short interval. To this end, the setup times in production have to be reduced to a minimum and the reliability of production has to be increased. Waiting until several 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 existing, immediate availability of a single material within a plant. The display will show on hand inventory, open requisitions, open purchase orders, open stock transport orders and reservations made against a material. Every time the list is displayed 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 single 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 transport orders and reservations made against a material.

MD06 - Collective Display of MRP list MD06 provides a collective list of all materials run during the MRP process. Parameters may be set to view certain criteria 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 across all materials. The same detailed information provided in MD04 may also be obtained by using the drill-down features.

REWORK
Separate Order Type is created for Rework and to capture the cost in Order Header>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 inventory. 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 item 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 Material as it is not a stock item.

Labels parameters
MRP The MRP will explode the phantom items and create recommendations for its components. The phantom item will be displayed in the MRP result window without recommendations for information only. Production Order The Production order will explode 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 not Phantom 1 and 2. The BOM requirements of different departments in the same company can be different. The engineering department could create a multi level BOM 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 items do not exist in the inventory. They are designed to be used in situations where several BOMs would have the same basic components. Instead of having to enter 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 mix for a bakery. This basic recipe plus additional items is used for a variety of different cakes.

A phantom item is a sublevel in the BOM that does not actually exist in inventory. 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 standard values in Routing?

If I am maintaining Lot size dependent information such as set time, Interoperation time, Processing time in work scheduling view in material master and also Total 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 production time in MRP2 view, specifies the time in workdays needed to produce the material 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 in 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 the routing. -Or you enter the setup, teardown, processing, and interoperation times. 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 fundamental of "Independent lot size" and "Dependent lot size" in work scheduling view of a material master. I am jumbling a lot between this two to understand the basic requirement of my client. Second thing is that you are saying that - You can 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 system to update this value from the routing. -Or you enter the setup, teardown, processing, 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 for 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 schedule the order for 2 days, and it doesn't matter if the order size is 1 or 1000, they are both produced in 2 days. (I never met any case that fits this situation)

2. Lot size dependent in-house production time, in material master, Workscheduling view. ex: if you have 5 day setup time, and 1 day production time for lot size 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 will be 5 day + 1 day x 100 / 10, which is 15 days. 5 day setup time will not change when the order quantity changes, because you make the setup once at the beginning of the production, and use the same setup during whole production. 3. Lot size 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? For 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 want the system to use the routing data, then you should use lead-time scheduling parameter 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 times but take the results after short MRP run. This was very crucial before, because 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 combination 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. In that case, the approximate production times in material master will be as close as possible to the actual production times. In that case, not only MRP run will not take long time, but also we will get much better results.) For the production orders, always the routing data is used for scheduling.

Now, I am cleared that what is independent and dependent lot size. but still there 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 close as possible to the actual production times). Can you please clear me this sentence 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 entered in routing, in material master you can enter only days, which will be the approximate value.

If your routing is, for lot size of 10, setup time is 3 hours and production time is 50 minutes, when you update the material master from routing, system will write 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 have 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 mentioned 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 lead-time scheduling. You mean to say I have to enter that 10 or 100 in base quantity 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 carried 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 storage 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 quantity 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 planning is carried out independently. Basically, there are three types of MRP area: 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 subcontractors 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 creating an MRP area and assigning the storage location to it. Material requirements for this storage location are then planned separately from the rest of the plant. 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 for 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 subcontractor 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 you to carry out differentiated material requirements planning. The requester can be, for example, the production on a particular assembly line or a subcontract order. The MRP area allows you to have specific control over the staging and procurement of important parts produced in-house and purchased parts for each shop floor area. You can, however, also plan the provision of components for the individual subcontractors. MRP areas of the storage location or subcontractor type are only suitable for: components that are planned and produced for stock finished products that are planned and produced for stock. By assigning a storage location in a sales order or by entering an MRP area when creating the planned independent 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 important assemblies intended for make-to-order or engineer-to-order production are always planned in the plant MRP area. The planning run takes into account the planning with MRP areas as follows:

If you do not enter a separate scope of planning, the system plans the whole plant, that is, all MRP areas in the plant, during the total planning run. If you want to carry out a total planning run for a particular MRP area only, you must specify 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. During single-item, single-level planning, the system plans the selected material in the MRP area entered only.

Structure
You define the MRP areas in Customizing for MRP. You can thereby assign the following 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 storage location to the MRP area) a subcontractor.

You assign the various MRP areas to the materials in the material master. For this, you create an MRP area segment for a material for every MRP area, in which it 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 differently 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, that is, you have not created an MRP area segment in the material master, the material will continue to be planned in the plant MRP area only. If you have assigned an MRP area to it, the system can plan it in the plant MRP area and in the assigned MRP area.

Integration
You can carry out material requirements planning for MRP areas using all MRP procedures and all lotsizing procedures. You can also carry out an independent material 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 level 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 materials 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 the 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 transfer from plant to MRP area for the plant in which the MRP area is located. You have defined the following parameters: Procurement type : F for External procurement Special procurement : U for Stock transfer Plant : Number of plant, to which 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 MRP area.

Features
During MRP, the system generates a stock transfer reservation for the material in 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 processed by the plant. With stock transfer to the MRP area, you carry out the transfer posting for the material with reference to the reservation.

MMD1 - Create MRP Profile - MRP profile is a useful entry aid and makes it easier to manage MRP data. You define which fields are filled with values when MRP data is entered in the material master record, which of these values can be overwritten and which not. You use the information stored in a profile is standard information 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 dont 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 transaction. Give the name and description to your own profile and you can select the fixed 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 values column then click on screen 1 to fix the value. You get the option of different 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 material 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 assign 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 carry 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 are 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 costs 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 prod orders via diff media like costing sheet or Indirect activity allocations. Here again Prod order is debited with some amount. When the costs are incurred these should be transffered futher when the order is closed or deliverd to stock. So whenever you deliver the order, the follwing entry is generatedInventory....Dr Cost of Prod /Mfg Variance.....Cr If your Fin Goods' predetermined cost are same as that of actual costs incurred, there will no price difference account affected. But when your plan cost ( target cost ) & actual costs are differnet, the difference 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 COST 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 node, choose Order Display. Transaction Code CO03 2. Enter the following data: Field

Data

Order Display overview 3. Choose 4. To analyze the current settlement rule, choose Header Settlement rule . The system displays the settlement rule and the distribution rules it contains. In this case, the sales order is the receiver. 5. Choose The Display Production Order: Header screen appears. 6. Choose Goto Costs Analysis . 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 the 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 Test 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 Current year Deselect Select

Transaction Code 13. Enter the following data: Field Order Settlement period Posting period Fiscal year Processing type Test run

From the PeriodEnd Closing node, choose Settlement Individual Processing KO88 Data Number of your production order Current period Current period Current year Automatic Deselect

14. Choose 15. Choose until the overview tree appears. 16. Call up the transaction 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. Choose 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 switching from one product to another. Each product is manufactured in individually defined lots. Costs are calculated per order. Inrepetitive manufacturing, the same 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 product cost collector. In order-based production, you usually have a changing sequence 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. Repetitive manufacturing usually involves a relatively constant flow through production lines. 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, components are often staged at the production lines without reference to a particular 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 production orders. Discrete manufacturing is characterized by requirements that occur on an irregular basis and a workshoporiented process. The Discrete Manufacturing scenario can be used in different variants, production by lot size, make-toorder production and assembly processing. The variants differ mainly in the type of planning conducted before-hand and in the relation to the sales order. Repetitive Manufacturing This scenario describes production planning and control within a repetitive manufacturing environment. In repetitive manufacturing, master plans are 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 products are generally not stocked. In repetitive manufacturing, you usually find that the effort required for production control is significantly less than is required for single lot and order-based production control and the recording of actual data is kept simpler. Repetitive manufacturing can be used for various industries, such as the consumer packaged goods industry, the electronic industry, packaging industry, for example. You can use Repetitive Manufacturing purely for make-to-stock production, or in a sales orderoriented environment, such as found in the automotive industry.

Discrete Manufacturing : - Order-based production using production order - Production 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 backflush - Cost monitoring per order or per product

Repetitive Manufacturing : - Quantity- and period-based planning (planning periods) and production - Planned orders (run schedule quantities) authorize production; production orders not needed (no conversion). - Repetitive production: The same/similar products produces over a longer period of time The aims of using Repetitive Manufacturing are the following: - Creating and processing production plans based on periods (rather than individual lots and orders) - Reducing the administration costs for production control and simplification of completion confirmation 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, routing, 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) * Production version. Configuration: ************* 1. REM Profile

Process Flow: *********** 1. First Create all the required material master as indicated above. 2. Once this is done now you have to create a product cost collector * 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 version 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 release the same with CK11N AND CK21(you can reach the help of FICO consultant to complete this process) 5. Once the above is done now the master data and prerequisites are complete and ready for the PLANNING AND CONFIRMATION of the product/material. 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 with the REM PLANNING TABLE. 8. One of the best features in the REM is the Rem Planning table 9. This can be accessed with the T.CODE MF50. 10. Here when you try to access the MF50 you have multiple choices to make selections and also restrictions.

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 lower 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 the functionalities. 13. Once all the planning is done with the MF50 then comes the 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 / MF42N 16. HERE in MFBF you can have some mandatory parameters like Quantity, material, production version, date etc which has to be given as input , and the system will in turn perform the back flush. 17. the MFBF is single screen which allow 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 done the stock gets posting 19. You also have cogi/mf47 FOR clearing the post goods movement errors for automatic posting.

Planning Horizon
Planning period in which planned transportation activities are to be executed. You define the planning horizon in the planning profile (see Planning Profile). The 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 instead 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 horizon 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 planning 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 calculate the horizon. According to this, the planning horizon is defined as follows:

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 planning 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 specify a factory calendar, the system takes into account non-working days when calculating the start of the horizon. In this case, the planning horizon always begins on a working day. The following figure shows how the planning horizon is defined:

Difference between MRP vs MPS

MD40 - MPS Explain the difference between MRP & MPS. Though both components gives 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 counter part MRP. MD40 - MPS - Master Production Scheduling (A MRP type) Master Production Schedule (MPS) : MPS operates within only one level of the BOM, While MRP can be utilized throughout all levels of a materials BOM. If a MPS is run on a material, the necessary orders are planned at that level. Dependent requirements (if 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 concentrates planning on the parts or products that have the great influence on company profits or which dominate the entire production process by taking critical resources. These items are marked as A parts (MPS items) and are planned with extra attention. 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 controller can ensure that the Master schedule items (MSI) are correctly planned before the detailed MRP run takes place.

The master production schedule is a line on the master schedule grid that reflects the anticipated build schedule for those items assigned to the master scheduler. The master scheduler maintains this schedule, and in turn, it becomes a set of planning numbers that drives material requirements planning. It represents what the company plans to produce expressed in specific configurations, quantities, and dates. The master production schedule is not a sales item forecast that represents a statement of demand. The master production schedule must take into account 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 master production schedule to calculate requirements for materials. It makes recommendations to release replenishment orders for material. Further, because it is time-phased, it makes recommendations to reschedule open orders when due dates and 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, adjusting for inventory quantities on hand or on order, and offsetting the net requirements by the appropriate lead times. MRP Interview Questions: What is the need of mrp list if stock requirement list is already there?

The MRP list displays the result of the last planning run. Changes that have occurred between planning runs are ignored in the MRP list. In contrast to this, the system displays all changes in stock, receipts and issues, which have currently occurred, in the stock/requirements list. Which tcode are used to run MRP?

- MD01 is generally used to run the MRP for all the materials in a plant normally 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 Procurement Type if applicable (MM) 6. Lot Sizing Procedure (MM) 7. Scheduling Margin Key(MM) 8. Scheduling Parameters for planned orders through (SPRO) Detail: 1. Activate 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 Controller (in SPRO) 4. Production Scheduler Profile (in SPRO) 5. Order type Dependent 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 Received

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 produced/procured or planned for production /procurement. After MRP run, the available quantity column is usually zero. If it has a positive value it means you are trying to produce / procure more than what is required. Stock Requirement list 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 static. 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 Work 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 PLPO Routing Operation Details PLKO Routing Header Details MAPL Routing Link to Material PLAB Relationships - Standard Network PLAS Task List - Selection of Operations PLMZ Component Allocation PLPH CAPP Sub-operations PLFH PRT Allocation PLWP Maintenance Package Allocation PLMK Inspection Characteristics Bill of Material 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 STPF BOM Explosion Structure Line Design LDLH Line Hierarchy Header LDLP Line Hierarchy 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 number 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 information and what are the relationships? See below routing table relationships: Table MAPL, pass input material number, plant, routing group counter. Table PLKO, field PLNNR, PLNAL eq mapl-plnnr, mapl-plnal Table PLAS, field PLNNR, PLNAL eq mapl-plnnr, mapl-plnal and LOEKZ ne ' ', take field PLNKN Table PLPO, field PLNNR, PLNKN eq plas-plnnr, plas-plnkn You will get correct result same as CA03 list.

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 specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software. As with customer exits two different views are available: In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object. In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.

In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business 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 upgrades 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 Business Add-Ins in SSCR.

The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).

All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task. The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects. What is difference between badi and user-exists? What is difference 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 time. Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign 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 'Business addins'. 3) System land scape will be depends on your project Ex:- 'Development server'-->'Quality server'---> 'Production server'......

BAPIs
Definition
A Business Application Programming Interface (BAPI) is a precisely defined interface 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 object types and their BAPIs are described and stored in the Business Object Repository (BOR). A BAPI is implemented as a function module, that is stored and described 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 for 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 information 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: Connecting: New R/3 components, for example, Advanced Planner and Optimizer (APO) and Business Information Warehouse (BW). Non-SAP software Legacy systems Isolating components within the R/3 System in the context of Business Framework Distributed R/3 scenarios with asynchronous connections using Application Link Enabling (ALE) 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 (Microsoft) or Visual Age for Java (IBM). Workflow applications that extend beyond system boundaries Customers' and partners' own developments The graphic below shows how BAPI interfaces enable different types of applications to be linked together.

BAPIs - Interfaces to the R/3 System

For further background information on BAPIs refer to the document

FUNCTION MODULES FOR PRODUCTION VERSION

Function modules for C223 CM_FV_PROD_VERS_MAINTAIN CM_FV_PROD_VERS_SAVE CM_FV_PROD_VERS_SAVE_ALL CY01_ORDER_MODIFY_PROD_VERSION CM_FV_PROD_VERS_DB_UPDAT MATERIAL_UPDATE_ALL MDIA_UPDATE_MKAL_INTERN

Change Activity - KP26

Shift Definition - OP4A

Factory Calender - SCAL is assigned to each plant while defining plant - Enterprise Structure, also while creating Work Center we can assign Facory Calender, Planning Calender-MD25 is normally not used/required which is maintained in MRP 2 view

MRP EXIT - not much use

*&---------------------------------------------------------------------* *& Include ZXM61U01 *&---------------------------------------------------------------------* *----------------------------------------------------------------------* * INCLUDE LXM61F01 * *----------------------------------------------------------------------* *----------------------------------------------------------------------* * example coding for User-Exit MRP *----------------------------------------------------------------------* CLEAR: NO_PLANNING, STOP_PLANNING. CASE USER_KEY. *----------------------------------------------------------------------* * materials 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_PLANNING = 'X'. ENDIF. *----------------------------------------------------------------------* * reorder-point materials * (any MRP type with MRP procedure 'reorder-point planning') *----------------------------------------------------------------------*

WHEN '003'. IF T438A-DISVF <> 'B'. NO_PLANNING = 'X'. ENDIF. *----------------------------------------------------------------------* * stop planning after low-level code 03 *----------------------------------------------------------------------* WHEN '004'. IF MT61D-DISST > '003'. STOP_PLANNING = 'X'. ENDIF. *----------------------------------------------------------------------* * select materials for one MRP controller (specified in user_par) *----------------------------------------------------------------------* WHEN '005'. UXPAR = USER_PAR. CONDENSE UXPAR. WRITE UXPAR+0(3) TO DISPO. IF DISPO IS INITIAL. EXIT. ENDIF. IF MT61D-DISPO <> DISPO. NO_PLANNING = 'X'. ENDIF. *----------------------------------------------------------------------* * select materials of one material class (specified in user_par) *----------------------------------------------------------------------* WHEN '006'. UXPAR = USER_PAR. CONDENSE UXPAR. WRITE UXPAR+0(9) TO MATKL. 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 Record 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 material. MVER Material consumption. MVKE Sales data for material. PKPF document header Reservation TO23 Material Groups . TO24 Purchasing groups . T156 Movement Type Purchasing Tables EBAN Purchasing requisition. EBKN Purchase requisition account 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 document. 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 Requirements by Material Repetitive Manufacturing SAFK RS Header Master Data S025 LIS -- Run Schedule Quantities S026 LIS -- Material Usage S028 LIS -- Reporting Point Statistics CEZP Reporting Point Document Logs CPZP Reporting Points - Periodic Totals MRP Records MDKP MRP Document Header Data MDTB MRP Table Structure (no data) PLSC Planning Scenario (Long-term Planning) MDFD MRP Firming Dates MDVM Planning File Entries S094 LIS -- Stock/Requirements Analysis Reservations RESB Reservations/Dependent Requirements

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