|
What are the cutover activities followed for PP module?
I am listing some cut over activities to be followed (for PP - Discrete Manufacturing). Production Planning / Master data:
- Bill of materials
Transaction data:
Since, the production orders are for longer duration and it is not possible to dismantle the product and add it to inventory, following can be the strategy for migrating the data to SAP: - Create a material master for the work in process and
set the standard price as the cost incurred for that product (ie. Work
in process)
Complete the production process after the cut off date of the project. Tips by: K.S.Kulkarni What happens to planned after it has been converted into production order? When you convert Planned order to Production order. the planned order are offset by production order. Reference of planned order can be seen in the production order. How to attach a drawing for a material to BOM? Is it possible? Yes, you can attach a drawing.
Report in Long Term Planning
- You use long term planning for your customers, what they need are very
simple, just to calculate future requirements for 1 or 2 years.
Use MS70 then use MCEC. Scheduling planned order
- How can you get planned orders scheduled so that you can do capacity
leveling?
When running MRP, try selecting "2" in the scheduling box this will bring planned orders into CM01 and CM21 Capacity planning CM01 - When you run capacity planning T-code: CM01, you found the plan orders are not included in the pegged requirement, you checked the profile, the check box for order and plan order are all actived. Guess that planned orders have been created without capacity requirement indicator in MRP ("2" - Lead Time scheduling), if this is the case, then when converted to process orders they will have impact on the Resource. If you want to see them as planned orders, re-run the MRP or change in every planned order, going to the Menu: Edit --> Scheduling Another couple of possibilities are to do with the routing/work centres used and whether it isactually calculates consumption of capacity of the category at the work centre being displayed in CM01 (it might consume a capacity pool or it might not consume the category). MPS in Backgound/Online - You want to run MPS for a plant either online or in the background, but you do not get any results. If you run MPS for a single material/plant, then everything is 100% OK. You need to run a planning file and a consistency check first, transaction OMDO and MDRE respectively you'll need to set up two jobs to do it but it is straight forward, once you've done this set up the background job for MPS to run and do it in NEUPL first time round and then change to NETCH after that. What is the output of MPS run? From MPS run you plan the materials which are of 'A' type
in the abc analysis (80% dollar value) that have to be planned before hand.
Table for production order status - What is the table for finding status (for Ex TECO ed prodn orders). We are not able to find from AFKO and AFRU tables the status of production orders or at least the link tables if known can be mentionned. You are unable to link the structure caufvd and IOHEADER WITH AFKO and AFRU. JEST is the table. Data dictonary table for SOP
planning data - You are using Standard SOP (Info structure S076), in which
table can you see the planning values that you maintained in MC93 transaction?
Use T.Code MC95 to display your entries under the version which maintained the the table S076. Production order operation's component allocation - How does SAP know that an operation has components as indicated by the component allocation indicator? Tcode CO08. Component allocation is done via routing maintenance or BOM maintenance for the assembly. This is master data maintenance. As soon as a PO is created, the master data is read into the PO. How to delete groups of products?
Delete the members in the product group and then archive
the product group in transaction SARA, object=MM_MATNR.
|
|
PP Test Questions
Get help for your SAP PP Problems
SAP PP Tips
Main Index
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|