Learn Production Planning

Sunday, September 30, 2007

Scheduling-6



What Is Mean By Schedule Lines

What is mean by schedule lines?
Explain the schedule lines in md02?

1. no schedule lines
2. schedule lines in opening period
3. schedule lines

Schedule lines are created against schedule agreements. Say if you have a material which is procured from subcontract. If you want the delivery in particular days with schedule you can maintain schedule agreeement. In source list you will maintain vendor, schedule agreeement with validity dates and which agreement is relevant for mrp.

If you maintain 2 against the sch agreemetn mrp will generate schedule line which you can see in md04. Also this delivery schedules are updated in scheduling agreement (t cod ME33). When running mrp in initial screen delivery schedules--you have to maintain 3 create schedule line

Schedule line in opening period - Opening period is maintained in Configuration of "Schedule Margin Key" which is getting assigned to Material master in MRP2 view.

Your understanding of the result after MRP is needed.

Define Floats (Scheduling 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. Recommendation

The opening period should reflect the processing time the MRP controller needs to convert planned orders into purchase requisitions or production orders. The opening period should be at least as long as the interval between two MRP intervals, so that all planned orders can be taken into account during the conversion.

Scheduling-5



What is Finite and Infinite Scheduling

What is finite and infinite scheduling? How it is carried out? What is to be done for each one? What are their significance?

Differences between planning and scheduling, finite and infinite


Finite Scheduling
Scheduling type within capacity planning that takes account of the capacity loads which already exist. Finite scheduling calculates the start and finish dates for operations in the order. It is a detailed scheduling strategy with which you schedule orders and operations, taking into account the existing resource load. A resource overload cannot occur.

Infinite Scheduling
A detailed scheduling strategy with which you schedule orders and operations, without taking into account the existing resource load. It is therefore possible for resource overloads to occur.

R/3 does planning without consideration for capacity situations. So if MRP says you need 500 parts on 3/1/04, it schedules them all to be built at the same time, even though you can only do 100 at a time. Assume you have a fixed lot size of 100, you'll get 5 planned orders for 100 to start on the same day. This is "Infinite Planning". APO would recognize that constraint, and instead schedule out the 5 orders over time. The important part of that is that it also will schedule out the deliveries of the components for 5 different days. This is "Finite Planning".

Now, assume old fashion MRP. It schedules all 5 orders for the same day, and the buyers go out an get all of the components for the same day. Then the planner realizes he can't do all 5, and manually changes the schedule, and manually spreads out the 5 orders. The buyers will recieve rescheduling notifications, but not until the scheduler does the manual rescheduling.
You could call this "Infinite Scheduling", but that only means the same thing as Infinite Planning.

But, SAP has "Capacity Leveling". What that means is you run another program after MRP (CM27 and CM28), which can be run in batch mode overnight. (There is a ton of configuration and thinking that will be required to do this!). The capacity leveling program will recognize the constrant at the work center level, and fill up the first day, then re-schedule the next
order to the next available capacity, then the next order searches for available capacity, and so on. This is called "Finite Scheduling". The problem with this is the opposite of Infinite Planning, which is it doesn't take Material availablity into consideration! The system will re-schedule a production order without thinking about whether the materials will be available
or not.

Finite Planning does Finite Scheduling at the same time. If there is no capacity available on the desired date, the system looks for when capacity IS available. Then it stops to see if Materials will also be available (usually based on the lead-time for those components). If there is a material problem, then the system figures out when the materials WILL be available, and then
checks to see if capacity is available on THAT day, and if so, it blocks off capacity, and allocates the materials for that day.

Scheduling-4



Scheduling Background Jobs for MRP

Transaction code : MDBT

click Create Variant button (specified a variant name and click continue).


Then fill in the following fields :-

Scope of Planning : Optional (refer to Note if you want to specify a plant grouping)
Plant : Your company Plant
Processing Key : NETCH
Create PUrchase Req. : 1
Schedule lines : 1
Create MRP lists : 1
Planning mode : 1
Scheduling : 1
Planning date : default date

Click the Back button and you will be prompt Save Values.

Type in a Description and click the Save button.

After creating the variant, park your cursor at the variant and click the Schedule job button.

Fill in the Date and Time value.

Click Schedule periodically and you are prompt to choose the period.

Click the Create button and you are done.

To check, you can click the Show Scheduling button.

Note :

Define Scope of Planning for Total Planning in 'OM0E'.

1. Choose New entries.

2. Enter a key and a description for the scope of planning that you would like to define. Save your entries.

3. Select the scope of planning and choose Sequence of plants/MRP areas.

4. Choose new entries and enter the plants or the MRP areas in the sequence in which they are to be planned. The counter determines the sequence.

5. Save your entries.

Scheduling-3



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.


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.

Scheduling-2



Schedule Margin Key in Production Scheduling

I want to know impact of schedule margine key in production scheduling in following changes in mateial master
1) if I have schedule key where all floats are zero but I enter in-house prodution time as e.g. 7 days .
2) if I have key where floats before prodution is 5 days and same values in next floats and in house production time as 1 day.
All above with MTO what is impact of above cases in scheduling.

While "Basic Scheduling" in MRP... Scheduling margin key is not considered. It takes the "In house production" days for fixing up the start date. This is only exact to "days".

Lead Time scheduling is carried out on request from the scope of MRP. Target dates are calculated from routing and Capacity requirement calculations are also done. The calculations are exact to the seconds (time).

SCHEDULING MARGIN KEY takes effect only for Lead Time Scheduling. For this you have to configure for "scheduling horizon" to limit the period for which lead time scheduling and capacity planning should be carried out. scheduling horizon is the period in working days. If a planned order has its basic start date within this period in future, lead time scheduling is carried out using the selected routing. The production times are calculated from the float times of the scheduling margin key in the material master record and the time from the individual operations. If the planned order has its basic start date further in the future than this scheduling horizon, the basic dates are calculated from the in-house production times in the material master and are transferred to the production times.

Could you explain what's function of opening period in Sched Margin key.

Opening period is like a "release window". The length of the opening period is the window of opportunity a planner has to convert the planned order to a purchase req.

For example - Component A has a lead time of 14 days and opening period of 5 days. Requirement on 12-22-03

Opening Date - 12-01-03
Start Date - 12-08-03
Finish Date - 12-22-03

Now the planner can convert the order starting Dec. 1st, instead of Dec. 8. It basically is a buffer in the lead time to get things on order a little sooner than needed.

What's the function for Plan order convert to production order?

As your example,
Requirement on 12-22-03

Opening Date - 12-01-03
Start Date - 12-08-03
Finish Date - 12-22-03

But I can convert plan order to production before 12-01-03 at random, so I wonder what is the opening period real function? it looks useless to restrict when to convert plan order to production order.

CO41 and MD15 are used for the conversion process. Here you enter the opening dates you wish to convert. Of course the opening period will not stop you from converting planned orders - hopefully your planner is not randomly converting orders or you have much bigger issues!!!!

The opening period is basically just to get the planned order to show up on the CO41 or MD15 lists in case you wish to convert it sooner than the lead time suggests.

Your answer make me clear to understand the opening period.

BTW,could you explain the release key ,float after production and float before production parameter in SchedMargin key?

I know the parameter affection in production,but I am not sure why to define how many days in each parameter.

for example, release key defined for 10 workdays,but you can release production order out of the release period randomly.any way to stop release out of the release period?

For example - Component A has a lead time of 14 days and opening period of 5 days. Requirement on 12-22-03
Opening Date - 12-01-03 ???
Start Date - 12-08-03 (from requirement date - lead time ?)
Finish Date - 12-22-03 (from requirement date ?)
Why Openning date = 12/01/2003 how system calculate , Could you please explain to me..

I know that when we run MRP system will check if the opening date is out of open period system will generate Plan order instead of PR .

The times in the sch. margin key are in workdays. That's how it gets the dates. The component I was describing originally would have been a purchased part, where lead time is in calendar days.

The order start date and the order finish date form the framework within which a production order is to be executed. Since malfunctions and disturbances in the production process can never be fully prevented, the system uses particular floats in a production order. The system takes into account so-called "before and after production floats" when scheduling an order.

The float before production is a start float. It has two functions:

It can compensate for delays in the staging of the material components.
If there is a capacity bottleneck at the work centers involved, the production dates can be moved forward in the future. In this way it serves as a float for capacity leveling.
The float after production is a finish float. It is used to compensate for unexpected disturbances in the production process, so that they do not delay the scheduled finish date.

The floats before and after production are defined for each material using a scheduling margin key. This scheduling margin key is automatically transferred from the material master when an order is created. However, you can change the times in the order.

The system calculates the scheduled start of the order by adding the float before production to the order start date. It calculates the scheduled finish of the order by subtracting the float after production from the order finish date.

The system deducts the number of days defined in the release period from the scheduled start of the order and thus determines the scheduled release date of the order. This date can be used for collective release.

Scheduling-1


Rescheduling date does not take into account the GR Processing Time

If you look at MD04, the rescheduling date is based on the Stocks Requirement date.

It does not take into account the parameters in Procurement and Scheduling in the Material Master.

In the net requirements calculation, the system checks whether warehouse stock or firmed receipts are available to cover requirements. If a material shortage exists, the system usually creates a new procurement proposal.

The rescheduling check is used to change the dates of already existing firmed receipts not planned on the same day as the requirement to suit the requirement date.

For this purpose, the system displays the appropriate exception messages with rescheduling proposals for these firmed receipts to be processed by the MRP controller.

You defined the rescheduling parameters in Customizing for MRP.

An important parameters is the rescheduling horizon period to be included.

1. OPPQ per plant to Carry out overall maintenance of plant parameters.

2. OPPR per MRP group to Carry out overall maintenance of MRP groups.

You can also define tolerance values for the creation of exception messages.

These values define a time period in which no exception message is to be created, despite the fact that a rescheduling proposal may exist.

The MRP controller can thus avoid a situation where too many exception messages are created if a certain buffer has already been planned for scheduling basis dates.

Rescheduling Exception Proposal

Bring process forward (reschedule in)

Within this rescheduling horizon, the net requirements calculation checks whether, after a requirement, a firmed receipt exists, which can be used to cover this requirement. Then the system displays a rescheduling date as well as the exception message Bring process forward for this receipt. The net requirements calculation then uses this receipt and the
system will only create another procurement proposal if the receipt quantity is not sufficient to cover the complete requirement. Several firmed receipts can be used to cover one requirement.

The rescheduling horizon is always calculated from the MRP date.

Postpone process (reschedule out), or cancel process

The net requirements calculation checks over the complete time axis whether availability could still be guaranteed without the receipt in question. If this is the case, the system checks whether the receipt planned here could be used to cover a future requirement. If the system can find such a requirement, it then displays a rescheduling date as well as the exception message Postpone process for this receipt.

If the system finds no future requirement, for which the receipt is required, the system displays the exception message Cancel process.

TABLE-3



Table of the Order Production Operation

Which is the table of the order production operation details? I need to get the activities for production order :
Setup, Labor, Machine, Confirmed and to confirm.
I can see look at this in CO02 / Operation Overview (f5) / Operation Detalis / Qty-Activities

That is probably the hardest information to piece together, I used 5 tables with multiple joins to get User Fields for operations in a production order. Maybe you can use something simular.

AFKO - this is for your basic production header info - order number, basic finish date etc

S022 - this is for your operation header details - operation number, Work centre etc if you are only after the header details such as setup time and execution time, you can probably stop here without going to AFVC or AUFV (you definitely need AUFK if you want order status)

AUFK - this is for your order master data - Order released flag, order complete flag, technically complete date, you'll need this to filter out closed orders

AFVC - this is to link to the detail table - however I used the control key field in it so I would know whether it was a MILE stone or GPP1 for confirmation's sake

AUFV - this is the user field table - you may want to replace this with whatever detail you are after

Delete all the automatic joins:

AFKO -> AUFK on:
AUFNR -> AUFNR

AFKO -> S022 on:
AUFNR -> AUFNR
PLNBEZ -> MATNR

AFKO -> AFVC on:
AUFPL -> AUFPL

S022 -> AFVC on:
WERKS -> WERKS
PLNFL -> PLNFL
VORNR -> VORNR

The join below is for user fields in operation detail, you will have to find your own relevant table, but I assume the two key fields will be the same??

AFVC -> AFVU on:
AUFPL -> AUFPL - Routing number of operations in the order APLZL -> APLZL - General Counter for order

TABLE-2




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 Link of PRT data to Material
CRVM_B Link of Material to PRT data
CRVS_A Link of PRT Internal number to PRT External number
CRVS_B Link of PRT External number to PRT Internal number

TABLE-1



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

Wednesday, September 19, 2007

Transaction Codes-3


Commonly Used Tcodes in PP Module Part 3

Material Requirement Planning

Menu Nodes Transaction Activity

Master Data MD25 Create planning calendar
MD26 Change planning calendar
MD27 Display planning calendar
MDSA Display BOM explosion number
MDSP Edit BOM explosion number
MEQ1 Maintain quota file
OPPP Explode BOM by date
MDUS Display project assignment
MDUP Process project assignment
MDL1 Create production lot
MDL2 Change production lot
MDL3 Display production lot
Planning             MD20       Create planning file entry
MD21 Display planning file entry
MDAB Set up planning file entry in background
MDRE Check planning file entry
MD01 Total planning online
MDBT Total planning in background
MD03 Single-item, single-level planning
MD02 Single-item, multi-level planning
MD43 Interactive single-item planning
MD50 Multi-level, make-to-order planning
MD51 Multi-level project planning
MF52 Display planning table
MF50 Change planning table
MF57 Planning table by MRP lists
MF51 Planning table by production list
Evaluations          MD04       Stock/requirements list
MD07 Collective access of stock/requirements lis
MD05 MRP list
MD06 Collective access of MRP lists
MDLD Print MRP list
MD45 Planning result
MD46 Collective access of planning result
MD44 Planning situation for a material
MD47 Planning situation for a product group
MD48 Cross-plant planning situation
MD4C Order report
MD09 Pegged requirements
CO46 Order progress
Planned Order        MD11       Create planned order
MD12 Change planned order
MD13 Individual access of planned order
MD16 Collective access of planned orders
MD14 Individual conversion of planned order into
MD15 Collective conversion of planned orders int
MDUM Convert planned order into purchase requisi
CO40 Convert individual planned order into produ
CO41 Collective conversion of planned orders int
CO48 Partial conversion of planned order into pr
COR7 Individual conversion of planned order into
COR7_PC Collective conversion of planned orders int
COR8 Partial conversion of planned order into pr
MDVP Collective availability check
MDAC Execute action for planned order
LONG TERM PLANNING

PALNNING SCENARIO
MS31 CREATE
MS32 CHANGE
MS33 DISPLAY
PLANNING RUN MS01 ON LINE
MSBT SA BACKGROUND JOB
MS02 SINGLE ITEM - MULTI LEVEL
MS03 SINGLE ITEM - SINGLE LEVEL
MS50 SINGLE ITEM - SALES ORDER
MS51 SINGLE ITEM PLANNING, PROJECT
MFSO PLANNING TABLE
EVALUTIONS           MS05       MRP LIST MATERIAL
MS06 MRP LIST COLLECTIVE DISPLAY
MSLD PRINT MRP LIST
MS04 STOCK/REQUIREMENTS LIST
MS07 STOCK/REQUIREMENT LIST COLLECTIVE DISPLAY
MS44 PLANNING SITUATION MATERIAL
MS47 SITUATION PRODUCT GROUP
MPS-MASTER SCHEDULE ITEMS

TOTAL PLANNING
MD40 ON LINE
MDBS SA BACKGROUND JOB
MD41 SINGLE ITEM - MULTI LEVEL
MD42 SINGLE ITEM - SINGLE LEVEL
MD43 SINGLE ITEM - INTERACTIVE
MD50 SINGLE ITEM - SALES ORDER
MD51 SINGLE ITEM PLANNING, PROJECT
*** EVALUTION IS SIMILAR TO MRP

PRODUCTION CONTROL

ORDER - CREATE CO01 WITH MATERIAL
CO07 WITHOUT MATERIAL
CO40 FROM PLANNED ORDER
CO41 COLLECTIVE CONVERTION OF PLANNED ORDER
CO08 FOR SALES ORDER
CO10 FOR PROJECT
CO02 CHANGE
CO03 DISPLAY
CONTROL              MD04       STOCK/REQUIREMENTS LIST
COHV MASS PROCESSING
COMAC COLLECTIVE AVAILABILITY CHECK
CO05N COLLECTIVE RELEASE
CO04N PRINT
CO09 AVAILABILITY OVER VIEW
GOODS MOVEMENT       MF65       STOCK TRANSFER FOR RESERVATION
MATERIAL STAGING     MF68       LOG
MB1A GOODS ISSUE
MB31 GOODS RECEIPT
COWBPACK PACK MATERIAL
CONFIRMATION         CO1V       TIME TICKET
FOR OPERATION CO14 DISPLAY
CO13 CANCEL
CO1L REQUESTED CONFIRMATIONS
CO1P PREDEFINED PROCESSES
TOOLS-ARCHIVING      CO78       ORDER
KOAA SETTELMENT DOCUMENTS
CAPACITY PLANNING

EVALUTION
CM01 LOAD

WORK CENTER VIEW CM02 ORDERS
CM03 POOL
CM04 BACKLOG
CM05 OVERLOAD
CM07 VARIABLE
EXTENDED EVALUTION CM50 WORK CENTER VIEW
CM51 INDIVIDUAL CAPACITY VIEW
CM52 ORDER VIEW
LEVELLING CM21 PLANNING TABLE (GRAPHICAL)
WORK CENTER VIEW CM22 PLANNING TABLE (TABULAR)
INDIVIDUAL CAPACITY VCM27 PLANNING TABLE (GRAPHICAL)
CM28 PLANNING TABLE (TABULAR)
ORDER VIEW CM31 PLANNING TABLE (GRAPHICAL)
CM32 PLANNING TABLE (TABULAR)
AVAILABLE CAPACITY CR12 CHANGE
CAPACITY CR13 DISPLAY
OP4A SHIFT SEQUENCE
OP43 FACTORY CALENDER

Transaction Codes-2


Commonly Used Tcodes in PP Module Part 2


SALES AND OPERATIONS PLANNING

PRODUCT GROUP MC84 CREATE
MC86 CHANGE
MC85 DISPLAY
GRAPHIC MC91 PRODUCT GROUP
MC92 OVERVIEW
PLANNING MC81 CREATE
FOR PRODUCT GROUP MC82 CHANGE
MC83 DISPLAY
MC75 TRANSFER PG TO PLANNING
FOR MATERIAL MC87 CREATE
MC88 CHANGE
MC89 DISPLAY
MC74 TRANSFER MATERIALS TO DM
MC9K MATERIAL AVAILABILITY
VERSION MANAGEMENT MC78 COPY
MC80 DELETE
FLEXIBLE PLANNING MC93 CREATE
PLANNING MC94 CHANGE
MC95 DISPLAY
MC9K MATERIAL AVAILABILITY
TOOLS/PLANNING TYPE MC8A CREATE
MACRO MC8B CHANGE
MC8C DISPLAY
EVENT MC64 CREATE
MC65 CHANGE
MC66 DISPLAY
ROUGH CUT PLANNING MC35 CREATE
PROFILE MC36 CHANGE
MC37 DISPLAY
ENVIRONMENT MC90 TRANSFER MATERIALS TO DM
ACTIVITY REQT. KSPP TRANSFER TO COST CENTRE
KSBL COST CENTRE OLANNING REPORT
KSOP TRANSFER TO ACTIVITY BASED COSTING
CPBL PLANNING REPORT PROCESSES
MC9C REPORTING
SETTINGS MC96 FORECAST PROFILE
DISSAGGRIGATION MC76 BREAKDOWN PG PLAN
MC77 DISPLAY PG PLAN
MC75 TRANSFER PG TO PLANNING
MC74 TRANSFER MATERIALS TO DM

FORECASTING


INDIVIDUAL FORECAST MP30 EXECUTE
MP31 CHANGE
MP32 DISPLAY
TOTAL FORECAST MP38 EXECUTE
MP33 REPROCESS
MP39 PRINT
MPBT EXECUTE BACKGROUND
MPDR PRINT BACKGROUND

DEMAND MANAGEMENT


PIR MD61 CREATE
MD62 CHANGE
MD63 DISPLAY
MD65 REQTS. FOR SCINARIO
MD66 COPY SIMULATED DEPENDENT REQT.
MD70 COPY TOTAL FORE CAST
EVALUATION MD73 DISPLAY TOTAL REQT.
MD79 EXCELL INTERFACE
MD4C ORDER REPORT
MD72 CHARECTERISTICS PLANNING
CUSTOMER REQT. MD81 CREATE
MD82 CHANGE
MD83 DISPLAY

REPETITIVE MANUFACTURING

MASTER DATA C223 PRODUCTION VERTION
PRODUCT COST PLANNING
COSTING RUN CKMATSEL CREATE
SELECTION LIST CKMATCON Edit
CK40N EDIT COSTING RUN

Transaction Codes-1


Commonly Used Tcodes in PP Module Part 1

MATERIAL


CREATE-GENERAL MM01 IMMEDIETELY
MM11 SCHEDULE
CHANGE MM02 IMMEDIETELY
MM12 SCHEDULE
MM13 ACTIVATE
FLAG FOR DELETION MM06 IMMEDIETELY
MM16 SCHEDULE
DISPLAY MM03 DISPLAY CURRENT
MM19 DISPLAY AT KEY DATE
DISPLAY CHANGES MM04 ACTIVE CHANGES
MM14 SCHEDULE CHANGES
MM17 MASS MAINTENANCE
MMAM CHANGE MATERIAL TYPE
OTHER MMBE STOCK OVERVIEW
MMPV CLOSE PERIOD
MMRV ALLOW POSTING TO
PREVIOUS PERIOD
MM50 INSTANT MATERIAL VIEW
MMSC ENTER STORAGE LOCATIONS
MM60 MATERIAL LIST
ARCHIVING(MATERIAL) MM71 ARCHIVE/DELETE
MM72 DISPLAY ARCHIVE

BILL OF MATERIAL (MATERIAL BOM)

CS01 CREATE
CS02 CHANGE
CS03 DISPLAY
EXTRAS CS28 ARCHIVING
CS20 MASS CHANGES
EVALUATION/BOM CS11 BOM MULTILEVEL
EXPLOSION/MATERIAL CS12 STRUCTURE MULTILEVEL
BOM CS13 SUMMURISED BOM


WORK CENTRES


CR01 CREATE
CR02 CHANGE
CR03 DISPLAY
CA85 REPLACE
CAPACITY CR11 CREATE
CR12 CHANGE
CR13 DISPLAY
HIERARCHY CR21 CREATE
CR22 CHANGE
CR23 DISPLAY
LINE HIERARCHY LDB1 CREATE
LDB2 CHANGE
LDB3 DISPLAY
REPORTING CR60 W/C INFORMATION SYSTEM
CR05 W/C LIST
CR06 COST CENTRE ASSIGNMENT
CR07 W/C CAPACITIES
CR08 W/C HIERARCHY
WHERE USED CA80 WORK CENTRE
CR15 CAPACITY
CR10 CHANGE DOCUMENTS
EXTRAS CR09 STD. TEXTS TASK LIST
CR41 ARCHIVING

ROUTING



STAD. ROUTING CA01 CREATE
CA02 CHANGE
CA03 DISPLAY
REF. OPERATION SETS CA11 CREATE
CA12 CHANGE
CA13 DISPLAY
RATE ROUTING CA21 CREATE
CA22 CHANGE
CA23 DISPLAY
REF. RATE ROUTING CA31 CREATE
CA32 CHANGE
CA33 DISPLAY
EXTRAS CA85 REPLACE W/C
MASS CHANGES CA95 REPLACE REF. OP. SET
CA75 REPLACE PRT
DELETE TASK LIST CA99 WITH ARCHIVING
CA98 W/O ARCHIVING
REPORTING CA80 WORK CENTRE
WHERE USED LIST CA90 REF. OP. SETS
CA70 PRODUCTION RESORCE TOOLS

COST CENTRE


OKKP MAINTAIN CONTROLLING AREA
KS01 CREATE COST CENTRE
KZS2 CREATE COSTING SHEET
KA01 CREATE PRI. COST ELEMENT
KA06 CREATE SEC. COST ELEMENT
KL01 CREATE ACTIVITY TYPE
KP26 ACTIVITY TYPE/PRICE PLANNING