Powered By

Free XML Skins for Blogger

Powered by Blogger

Wednesday, April 8, 2009

Tcodes in SAP Project System Part I

Here is a list of PS transactions. (Excluding the S_ALR** series(reports)
CJ** are mainly Project Definition and WBS related,
CN** are mainly Network and activity related and the
OP** are mainly PS Configuration / Customization related.

There are other which is not on the list, but this is a good platform to start and build up your own list of PS transactions as per your requirements:

CJ01    Create Work Breakdown Structure
CJ02 Change Work Breakdown Structure
CJ03 Display Work Breakdown Structure
CJ06 Create Project Definition
CJ07 Change Project Definition
CJ08 Display Project Definition
CJ11 Create WBS Element
CJ12 Change WBS Element
CJ13 Display WBS Element
CJ14 Display WBS Element (From DMS)
CJ20 Structure planning
CJ20N Project Builder
CJ21 Change Basic Dates
CJ22 Display Basic Dates
CJ23 Change Forecast Dates
CJ24 Display Forecast Dates
CJ25 Change Actual Dates
CJ26 Display Actual Dates
CJ27 Project planning board
CJ29 Update WBS (Forecast)
CJ2A Display structure planning
CJ2B Change project planning board
CJ2C Display project planning board
CJ2D Structure planning
CJ30 Change Project Original Budget
CJ31 Display Project Original Budget
CJ32 Change Project Release
CJ33 Display Project Release
CJ34 Project Budget Transfer
CJ35 Budget Return from Project
CJ36 Budget Supplement to Project
CJ37 Budget Supplement in Project
CJ38 Budget Return in Project
CJ3A Change Budget Document
CJ3B Display Budget Document
CJ40 Change Project Plan
CJ41 Display Project Plan
CJ42 Change Project Revenues
CJ43 Display Project Revenues
CJ44 Act. overhd: Projects, ind. process.
CJ45 Act. ovhd: Projects, coll. process.
CJ46 Plnd ovrhd: Projects, ind. process.
CJ47 Pld Overhead: Projects, Coll.Procssg
CJ48 Change Payment Planning: Init.Screen
CJ49 Display Payment Planning: Init.Scrn
CJ70 Maintain Project Settlement LIs
CJ72 Project: Act. amt. line item settlmt
CJ74 Project Actual Cost Line Items
CJ76 Project Commitment Line Items
CJ7E Plan Data Transfer: Projects
CJ7G Plan Data Transfer: Projects
CJ7M Project Plan Cost Line Items
CJ7N Maint. DRG inv.projects for retmt.
CJ80 Availability Control - Overview
CJ81 Update Report List
CJ88 Settle Projects and Networks
CJ8A Act.-setlmt: Proj. retirmt. from IM
CJ8G Actual Settlement: Projects/Networks
CJ8V Period Close for Project Selection
CJ91 Create Standard WBS
CJ92 Change Standard WBS
CJ93 Display Standard WBS
CJ9B Copy WBS Plan to Plan (Collective)
CJ9B_OLD Copy Project Cost Planning (old)
CJ9BS Copy WBS Plan to Plan (Indiv.)
CJ9C Copy WBS Actual to Plan (Collective)
CJ9C_OLD Copy Project Revenue Planning (old)
CJ9CS Copy WBS Actual to Plan (Indiv.)
CJ9D Copy Plan Versions
CJ9E Plan Settlement: Projects
CJ9ECP Project System: Easy Cost Planning
CJ9F Copy Project Costing (Collective)
CJ9FS Copy Project Costing (Indiv.)
CJ9G Plan Settlement: Projects
CJ9K Network Costing
CJ9L Forecast Costs: Individual Projects
CJ9M Forecast Costs: Coll.Project Proc.
CJ9Q Integrated Planning for Ntwks(Coll.)
CJ9QS Integrated Planning for Ntwks (Ind.)
CJA1 Proj.Rel.Order Receipts: Coll.Proc.
CJA2 Proj.Rel. Order Receipts: Ind.Proc.
CJAL Send project
CJB1 Generate Settmt Rule: Coll.Proc.
CJB2 Generate Settmt Rule: Indiv.Proc.
CJBBS1 Planning Board Report Assignment
CJBBS2 Structure Overview Report Asst
CJBN Reconstruct Availability Control
CJBV Activate Project Availabilty Control
CJBW Deactivate Project Availabilty Cntrl
CJC1 Maintenance Dialog for Stat.by Per.
CJC2 Maintain Planned Status Changes
CJCD Change documents: WBS
CJCF Carry Forward Project Commitments
CJCO Carry Forward Project Budget
CJCS Standard WBS
CJE0 Run Hierarchy Report
CJE1 Create Hierarchy Report
CJE2 Change Hierarchy Report
CJE3 Display Hierarchy Report
CJE4 Create Project Report Layout
CJE5 Change Project Report Layout
CJE6 Display Project Report Layout
CJEA Call Hierarchy Report
CJEB Background Processing, Hier.Reports
CJEC Maintain Project Crcy Trans.Type
CJEK Copy Interfaces/Reports
CJEM Project Reports: Test Monitor
CJEN Reconstruct: Summarized Proj.Data
CJEO Transport Reports
CJEP Transport Forms
CJEQ Import Reports from Client
CJET Translation Tool - Drilldown
CJEV Maintain Global Variable
CJEX Reorganize Drilldown Reports
CJEY Reorganize Report Data
CJEZ Reorganize Forms
CJF1 Create Transfer Price Agreement
CJF2 Change Transfer Price Agreement
CJF3 Display Transfer Price Agreement
CJF4 Transfer Price Agreement List
CJFA Analysis of Data Trans. into PS Cash
CJFN CBM Payment Converter
CJG1 Enter Transfer Price Allocation
CJG3 Display Transfer Price Allocation
CJG4 Enter Trsfr Price Allocation: List
CJG5 Cancel Transfer Price Allocation
CJH1 Reconstruct Project Inheritance
CJH2 Project Inheritance Log
CJI1 Project Budget Line Items
CJI2 Budget Line Items: Document Chain
CJI3 Project Actual Cost Line Items
CJI4 Project Plan Cost Line Items
CJI5 Project Commitment Line Items
CJI8 Project Budget Line Items
CJI9 Project Struct.Pld Costs Line Items
CJIA Project Actual and Commt Paymt LIs
CJIB Project Plan Payment Line Items
CJIC Maintain Project Settlement LIs
CJID Display Project Settlement Line Itms
CJIE Projects: Retirement LI Settlement
CJIF Projects: Profitability Analysis LI
CJIG Display PS Cash Documents
CJJ2 Change Statistical Key Figures
CJJ3 Display Statistical Key Figures
CJK2 Change Statistical Key Figures
CJK3 Display Statistical Key Figures
CJL2 Collective Agreement
CJN1 Reval. ACT: Projects Ind.Pro.
CJN2 Reval. ACT: Projects Col.Pro.
CJNO Number range maintenance: FMCJ_BELNR
CJO8 Overhead COMM: Projects Ind.Pro.
CJO9 Overhead COMM: Projects Col.Pro.
CJP1 Create Project Plan Adjustment
CJP2 Change Project Plan Adjustment
CJP3 Display Project Plan Adjustment
CJP4 Delete Project Plan Adjustment
CJPN Number Range Maintenance: Proj.Items
CJPU Execute Project Plan Adjustment
CJR2 PS: Change plan CElem/Activ. input
CJR3 PS: Display plan CElem/Activ. input
CJR4 PS: Change plan primary cost element
CJR5 PS: Display plan primary cost elem.
CJR6 PS: Change activity input planning
CJR7 PS: Display activity input planning
CJR8 PS: Change revenue type planning
CJR9 PS: Display Revenue Element Planning
CJS2 PS: Change stat. key figure planning
CJS3 PS: Display stat. key fig. planning
CJS4 PS: Change stat. key figure planning
CJS5 PS: Display stat. key fig. planning
CJSA Data Transfer to SAP-EIS
CJSB Select Key Figure and Characteristic
CJSG Generate WBS Element Group
CJSN Number Range Maintenance: Projects
CJT2 Project Actual Payment Line Items
CJV1 Create project version (simulation)
CJV2 Change project version (simulation)
CJV3 Display project version (simulation)
CJV4 Transfer project
CJV5 Delete simulation version
CJV6 Maintenance: Version administration
CJV7 Display transfer log
CJVC Value Category Checking Program
CJW1 EURO: Adjust Project Budget
CJZ1 Act. Int Calc.: Projects Coll. Proc.
CJZ2 Actual Int.Calc.: Project Indiv.Prc.
CJZ3 Plan Int.Calc.: Project Indiv.Prc.
CJZ5 Plan Int.Calc.: Project Coll.Prc.
CJZ6 Actual Int.Calc.: Indiv.CO Order Prc
CJZ7 Planned Int.Calc: Indiv.CO Ord.Proc.
CJZ8 Actual Int.Calc.: Coll.CO Order Prc.
CJZ9 Plan Int.Calc.: Coll.CO Order Prc.

Tcodes in SAP Project System Part II

Network and activity related transaction codes:

CN01    Create Standard Network
CN02 Change Standard Network
CN03 Display Standard Network
CN04 Edit PS Text Catalog
CN05 Display PS Text Catalog
CN06 MPX Download: Standard Network
CN07 MPX Upload: Standard Network
CN08 Allocate material -> stand. network
CN09 Allocate material -> stand. network
CN11 Create standard milestone
CN12 Change standard milestone
CN13 Display standard milestone
CN19 Display Activity (From DMS)
CN20 Dsply network/act.bsc data init.scrn
CN21 Create Network
CN22 Change Network
CN23 Display Network
CN24 Overall Network Scheduling
CN24N Overall Network Scheduling
CN25 Confirm Completions in Network
CN26 Display Mat.Comp/Init: Ntwk,Acty,Itm
CN26N Display Mat. Components (From DMS)
CN27 Collective confirm.
CN28 Display Network Confirmations
CN29 Cancel Network Confirmation
CN2X Confirm Completions in Network
CN30 Processing PDC error records
CN33 PDM-PS interface
CN34 Maintain release table TCNRL
CN35 Control stock / account assignment
CN36 BOM Transfer Profile
CN37 BOM Allocation Field Selection
CN38 Maintain Flexible Reference Point
CN40 Project Overview
CN41 Structure Overview
CN42 Overview: Project Definitions
CN42N Overview: Project Definitions
CN43 Overview: WBS Elements
CN43N Overview: WBS Elements
CN44 Overview: Planned Orders
CN44N Overview: Planned Orders
CN45 Overview: Orders
CN45N Overview: Orders
CN46 Overview: Networks
CN46N Overview: Networks
CN47 Overview: Activities/Elements
CN47N Overview: Activities/Elements
CN48 Overview: Confirmations
CN48N Overview: Confirmations
CN49 Overview: Relationships
CN49N Overview: Relationships
CN50 Overview: Capacity Requirements
CN50N Overview: Capacity Requirements
CN51 Overview: PRTs
CN51N Overview: PRTs
CN52 Overview: Components
CN52N Overview: Components
CN53 Overview: Milestones

CN53N Overview: Milestones
CN54N Overview: Sales Document
CN55N Overview: Sales and Dist. Doc. Items
CN60 Change Documents for Projects/Netw.
CN61 Standard network
CN65 Change documents order /network
CN70 Overview: Batch variants
CN71 Create versions
CN72 Create Project Version
CN80 Archiving project structures
CN81 PS: Archiving project - preliminary
CN82 PS: Archiving project structures
CN83 PS: Archiving project - Info System
CN84 PS: Archiving project - admin.
CN85 PS: Delete operative structures
CN98 Delete Standard Networks
CN99 Archiving Standard Networks
CNB1 Purchase requisitions for project
CNB2 Purchase orders for project
CNC4 Consistency checks for WBS
CNC5 Consistency checks sales order/proj.
CNE1 Project Progress (Individual Proc.)
CNE2 Project Progress (Collective Proc.)
CNE5 Progress Analysis
CNG1 Netw./Hier.: Maintain frame types
CNG2 Netw./Hier.: Maintain form def.
CNG3 Netw./hier.: maintain color definit.
CNG4 Netw./Hier.: Maintain graph. profile
CNG5 Netw./Hier: Maintain options profile
CNG6 Netw./hier.: Maintain node type
CNG7 Netw./Hier.: Maintain link types
CNG8 Netw./Hier.: Maintain field def.
CNG9 Graph. Cust. Netw./Hierarchy Graph.
CNL1 Create delivery information
CNL2 Change delivery information
CNL3 Display delivery information
CNMASS Mass Changes in Project System
CNMASSPROT Display log f. mass changes PS
CNMM Project-Oriented Procurement
CNMT Milestone Trend Analysis
CNN0 Number Range for Library Network
CNN1 Number range maint.: ROUTING_0
CNPAR Partner Overview
CNPRG Network Progress
CNR1 Create Work Center
CNR2 Change Work Center
CNR3 Display Work Center
CNS0 Create deleivry from project
CNS40 Project Overview
CNS41 Structure Overview
CNS42 Overview: Project Definitions
CNS43 Overview: WBS Elements
CNS44 Overview: Planned Orders
CNS45 Overview: Orders
CNS46 Overview: Networks
CNS47 Overview: Activities/Elements
CNS48 Overview: Confirmations
CNS49 Overview: Relationships
CNS50 Overview: Capacity Requirements
CNS51 Overview: PRTs
CNS52 Overview: Components
CNS53 Overview: Milestones
CNS54 Overview: Sales Document
CNS55 Overview: Sales and Dist. Doc. Items
CNS60 Change Documents for Projects/Netw.
CNS71 Create versions
CNS83 PS: Archiving project - Info System
CNSE5 Progress Analysis
CNVL Variable Overviews
CNW1 WWW: Confirmation
CNW4 Project Documents

Tcodes in SAP Project System Part III

PS Configuration / Customization related Transactions codes:

OP00    Maintain Operation Control Key
OP01 Customizing Routing/Work Center
OP03 Factory Calendar C
OP04 Word Processing
OP07 Standard Text
OP08 Standard Text
OP09 Maintain Alternative Activity Desc.
OP10 Maintain Person Responsible
OP11 Maintain Period Pattern Key
OP12 Maintain Location
OP13 Maintain Screen Sequence
OP14 Maintain Type of Std. Value Determin
OP15 Production User Profile
OP16 Maintain Period Pattern
OP17 Formula Parameters
OP18 Maintain Setup Group/Setup Group Cat
OP19 Standard Value Key
OP20 Maintain Setup Type Key
OP21 Define Formula
OP22 Maintain Wage Groups
OP23 Maintain Location
OP24 Maintain period dependent oper. val.
OP26 Maintain suitability
OP28 Maintain Perf. Efficiency Rate Key
OP30 Maintain Move Time Matrix
OP31 Maintain Time Segment (Per. Pattern)
OP32 Maintain Capacity Category
OP34 Maintain Work Center Planner Group
OP35 Maintain Perf. Efficiency Rate Key
OP36 Maintain Capacity Default Values
OP37 Maintain Available Capacity Version
OP38 Maintain Setup Type Key
OP39 Maintain Graphics Profile
OP40 Maintain Work Center Category
OP41 Matchcode for work center
OP42 Default work center
OP43 Maintain Setup Group Categories
OP44 Maintain Task List Usage
OP45 Maintain Usage
OP46 Maintain Task List Status
OP47 Maintain PRT Usage
OP48 Maintain Planner Group
OP49 Matchcode for Routings/Ref. Op. Sets
OP4A Maintain Shift Sequences
OP4B Overview variant: Routing
OP4C Overview variant: Ref. oper. set
OP4D Overview variant: Rate routing
OP4E Overview variant: Ref. rate routing
OP4F Overview var.:Scheduling of routings
OP4G Overview var.:Scheduling ref.op.set
OP4H Overview var.:Scheduling of rate rtg
OP4I Overview var.:Scheduling RefRateRtgs
OP50 Assign Material Types
OP51 Formula Parameters
OP52 Formula Parameters
OP53 Formula Parameters
OP54 Define Formula
OP55 Define Formula
OP56 Define Formula
OP57 Define Formula
OP58 Maintain Default Value Profiles
OP59 Formula Parameters
OP5A Field Selection: Task List Overview
OP5B Field Selection: Task List Header
OP5C Field Selection: Task List Sequence
OP5D Field Selection: Task List Details
OP5E Field selection task list overview
OP5F Field selection std network -> PRT
OP5H Field sel. insp.plan characteristics
OP61 Number range maintenance: ROUTING_3
OP62 Number ranges for routings
OP63 Number Ranges for Ref.Operation Sets
OP64 Maintain Setup Group Key
OP65 Formula Parameters
OP66 Maintain Location Group
OP67 Maintain Operation Control Key
OP68 Maintain Move Time Matrix
OP69 Maintain wage type
OP70 Maintain PRT Control Key
OP71 Maintain Wage Group
OP72 PRT Control Key
OP73 PRT Authorization Group
OP74 Maintain PRT Group Key
OP76 Define suitability
OP77 Engineering Workbench for Task Lists
OP78 Maintain Type of Std. Value Determin
OP7A Customizing matchcode for PRTs
OP7B Define Parameters
OP80 Maintain PRT Status
OP82 Define Formula
OP84 Profiles: Default Values for Rtgs.
OP85 Profiles: Default Values for QM
OP87 Maintain Routing/Ref.Op.Set Usage
OP88 Maintain Assignmt. of Task List Type
OP8A Maintain operation value description
OP8B Maintain standard value texts
OP8C Record layout for background (APL)
OP8D Data transfer APL
OP8E Command file task lists Rel. 2.2A
OP8F Maintain production scheduler
OP8H Profiles: Default Values for Rtgs.
OP91 Maintain Object Overview Version
OP95 Assign Work Center Cat. to Applicatn
OP96 Maintain Work Center Category
OP97 Maintain Performance Efficiency Rate
OP98 Maintain Validity of Perf.Effic.Rate
OPA0 Status selection profiles
OPA1 Maintain combination definitions
OPA2 Define selection profile
OPA3 Define option profile
OPA4 Define list profile
OPA5 Define graphics profile
OPA6 Define overall profile
OPA7 Define columns
OPA9 Maintain selection profiles
OPB1 Define list versions
OPB2 Define distribution function
OPB3 Specify distribution functions
OPB4 Specify distribution strategies
OPB5 Specify distribution key
OPC0 Axis representation selection
OPC1 Maintain axis representation
OPC2 Curve representation selection
OPC3 Maintain curve representation
OPC5 Max. no. of data records
OPCD Capacity category
OPCE Capacity planner
OPCF Time units
OPCG Maintain Operation Control Key
OPCH Maintain production scheduler
OPCI Setup group key/category
OPCL Scheduling type
OPCM Standard value key
OPCN Maintain move time matrix
OPCQ Efficiency rate
OPCR Formula parameters
OPCS Define formula
OPCT Strategies
OPCU Strategy levels
OPCW Planned order parameters
OPCX Formula parameters
OPCY Define formula
OPD0 Resource planning overall profile
OPD1 Resource planning selection profile
OPD2 Capacity leveling - time profile
OPD3 Resource planning evaluation profile
OPD4 Resource planning period profile
OPD5 Flow control definition
OPD6 Flow control control table
OPD7 Flow control statuses
OPD8 Flow Control Actions
OPD9 Flow Control Messages
OPDA Transition matrix (setup matrix)
OPDB Capacity Leveling Strategy Profile
OPDD Factory calendar
OPDE Resource planning control profile
OPDF Define requirements grouping
OPDH Capacity leveling - list profile
OPDJ Define layout
OPDK Define standard overview
OPDL Cap. plan. detailed cap.list maint.
OPDM Define detail list (leveling)
OPDQ Profile for planning table (tab.)
OPDR Define layout key
OPDT Define detail list
OPDU Maintain perf. efficiency rate key
OPDV Com-file (Rel-Info/OLPK) KOP. Set´s
OPDW Com-file (Rel-Info/OLPK) KOP. Set´s
OPE0 Maintain Sort String
OPE1 Maintain Value Type
OPE2 Maintain Machine Type
OPE3 Maintain Planner Group
OPE4 Maintain Control Parameters
OPE5 Maintain rounding categories
OPE6 Maintain Rounding Category
OPE7 Maintain overhead key
OPE8 Maint. Roundg. and Add.Val.Key (Def)
OPE9 Maintain User Profile
OPEA User selection
OPEB Automatic selection
OPEC PP user fields
OPENPS Download Activities to Palm Pilot
OPF0 Maintain User
OPF1 Authorizations for CAPP
OPFA Field selection: Work center
OPFP Configuring the Fixed Price Version
OPFR01 RPUCORF0PBS : IMG Link
OPG0 Profile for planning table
OPG1 Chart sequence - selection
OPG2 Line representation
OPG3 Scale time axis
OPG4 Time scale profile
OPG5 Graphic obj.type sel./repr.profile
OPG6 Transition matrix setup fam.key
OPG7 Line display selection
OPG9 Graphical object type/obj.represent.
OPGD Ref. Oper. Set-All Task Lists (PP)
OPGE Ref. Oper. Set - Rate Routings (PP)
OPGF Work Center - All Task Lists (PP)
OPGG Work Center - Rate Routings (PP)
OPGH Document PRT - All Task Lists
OPGI Equipment PRT - All Task Lists
OPGJ Material PRT - All Task Lists
OPGK Misc. PRT - All Task Lists
OPGL Resource - Master Recipes (PI)
OPGM Process Instr. Cat. - Master Recipe
OPGN Document PRT - Maintenance Task List
OPGO Equipment PRT-Maintenance Task Lists
OPGP Material PRT - Maintenance Task List
OPGQ Misc. PRT - Maintenance Task Lists
OPGR Work Center - Standard Network (PS)
OPGS Document PRT - Standard Network (PS)
OPGT Equipment PRT - Standard Network(PS)
OPGU Material PRT - Standard Network (PS)
OPGV Misc. PRT - Standard Network (PS)
OPH1 CO Cash Bgt Mgmt: Delete Actual Data
OPH2 PS Cash Management: Delete Plan Data
OPH3 CO Cash Bgt Mgmt: Delete Master Data
OPH4 CO Cash Bgt Mgmt: MM Data Transfer
OPH5 CO CBM: Successive FI Data Transfer
OPH6 CO CBM: Take Over FI Completely
OPH7 CO-CBM: Take Over All Data
OPI1 Maintain Value Categories
OPI2 Value Categories for Cost Elements
OPI3 Update Control: File RPSCO
OPI4 Commitment Item Value Categories
OPI5 Value Categories for Stag.Key Figs
OPI6 Activate CO Cash Budget Management
OPI8 Display Value Category
OPIA Interest Profile for Projects
OPIB Maintain Interest Profile
OPIC Intrst Relevance: Cost Els/Cmmt Itms
OPID Proj.Int Calc: Account Determination
OPIE Interest Indicator
OPIF View Maintenance:Compound Int.Cont.
OPIG View Maint.: Compound Int. Periods
OPIH Interest Scale, General Conditions
OPIN Number range maintnce: VHU_PINST
OPJ2 Production order stock determination
OPJ4 Schedule batch function request
OPJ6 Maintain Status Profiles
OPJ7 Maintain Routing Usage
OPJ8 Maintain Operation Control Key
OPJ9 Maintain prod. scheduler group
OPJA Maintain setup group/group category
OPJB Specify system messages
OPJC Maintain Wage Groups
OPJD Item Categories
OPJE User Selection
OPJF Automatic Selection
OPJG Maintain Default Values
OPJH Order types production order
OPJI BOM Usage Priorities
OPJJ Maintain Scope of Check
OPJK Maintain Control
OPJL Maintain Checking Rule
OPJM Application-Specific Criteria
OPJN Maintain Scheduling Type
OPJO C MM-BD units of measurement
OPJP Maint. acct.assgnm.types for orders
OPJQ Standard Value Key
OPJR Maintain move time matrix
OPJS PP: Maintain reduction strategies
OPJT Maintain Strategy Levels
OPJU Production order control parameters
OPJV Maintain Capacity Category
OPJW Maintain Capa.Planr.Grp for WrkCentr
OPJX Factory Calendar C
OPJY Maintain perf. efficiency rate key
OPJZ Maintain Release Periods
OPK0 Confirmation Parameters PP
OPK0T Confirmation Parameters
OPK1 Confirmation Parameters PP-PI
OPK1T Confirmation Parameters
OPK2 Formula Parameters
OPK3 Define Formula
OPK4 Confirmation Parameters
OPK5 Maintain variances
OPK6 List Layout
OPK7 Accessing Customizing PDC transfer
OPK8 Maintain print control prod. orders
OPK9 Maintain Goods Receipt Valuation
OPKA Maintain Movement Types
OPKB Control parallel confirmation
OPKC Control confirmation process chain
OPKD Control confirmation process chain
OPKE Screen Sequence for Components
OPKF Control parallel confirmation
OPKG Maintain Messages
OPKH Maintain Breakpoints
OPKI Maintain Collective Confirmation
OPKJ Maintain PRT Control Key
OPKK Standard Text
OPKL Formula Parameters
OPKM Define Formula
OPKN Overview variant production control
OPKO Command File for Production Orders
OPKP Shop floor control profile
OPKQ Customizing: Matchcode for Proc.Ord.
OPKR Print flag
OPKS Maintain Origins for CO Object
OPKT Initial Screen: Settlement Structure
OPKU Maintain Collective Confirmation
OPKV Print Flag
OPKW Print shop papers
OPKX Deletion Flag/Indicator
OPKZ Customizing Matchcode for ProdOrder
OPL1 Costing Variants: PP Prod. Order
OPL2 Maintain trigger point group
OPL3 Trigger point usage
OPL4 Profile for missing parts list
OPL5 Order type LIS parameters
OPL6 Profile for documented goods mvmts
OPL7 Order change management profile
OPL8 Order type parameters: Overview
OPL9 Parameters for order change mgmt
OPLA Conditions: V_T682F for H CO
OPLB CondTab: Create (batch, prod.)
OPLC CondTab: Change (batchs, prod.)
OPLD CondTab: Display (batches, prod.)
OPLE Strategy types: Batch determ. (prod)
OPLF Access: Maintain batch determ.(prod)
OPLG Batch determ.: Procedure for prod.
OPLH Overview variant - production orders
OPLI Background job for goods movements
OPLJ Job "Fast entry confirmation"
OPLK Overall profile for order prog. rep.
OPLL Order progress: Displayed fields
OPLM Order progress: Displayed fields
OPLO maintain selection profile
OPLP Job "Convert planned order"
OPLQ maintain filter for control keys
OPLR Maintain filter for capacity version
OPLS Parallel processing control
OPLT Target System for Data Transfer
OPLV Maintain Filter for Task List Usage
OPLW Maintain Filter for Task List Status
OPLX Maintain Filter for BOM Usage
OPLY Maintain Filter for BOM Status
OPLZ Maintain POI Planned Order Selection
OPM0 Maintain profile - field selection
OPM1 Costing Variants - Production Order
OPM2 Maintain Detail Screen Control Oper.
OPM3 Maintain Detail Scrn Control Header
OPMF Field Selection - BOM Transfer
OPMI Import models activities
OPMJ Determine progress values
OPN0 Master Recipe Profile
OPN1 Maintain Profiles for Master Recipes
OPN2 Valuation Variants - Prod. Order
OPN3 Overv.Var.: Master Recipe Scheduling
OPN5 Field Seln: Std Network Overview
OPN6 Field Selection Standard Network Hdr
OPN7 Field Sel.:Std Ntwk Activity Detail
OPN8 Field Sel.:Std.Ntwk Comp.Overview
OPN9 Field Sel. Std Ntwk Comp.Detail
OPO1 Create Cost Element Planning Layout
OPO2 Change Cost Element Planning Layout
OPO3 Display Cost Element Planning Layout
OPO4 Create Stat. KF Planning Layout
OPO5 Change Stat. KF Planning Layout
OPO6 Display Stat. KF Planning Layout
OPO7 View Maintenance V_TCJ41_7
OPO8 View Maintenance V_TCJ41_8
OPO9 View Maintenance V_TCJ41_9
OPOA View Maintenance V_T003O_N0
OPOB View Maintenance V_T003O_N1
OPOC View Maintenance V_T399X_N0
OPOD View Maintenance V_T399X_N1
OPOE View Maintenance T_T399X_N2
OPP1 Customizing MRP
OPP2 MPS
OPP3 Customizing Repetitive Manufacturing
OPP5 List Profile Component List
OPPA PP/MRP Customizing Explosion
OPPB Direct Procurement
OPPC Period Grouping
OPPD Customizing Planning Time Fence
OPPE Conversion Plnnd Order -> Prod.Order
OPPE01 General iPPE Customizing
OPPE02 Define iPPE Node Type
OPPE03 Define iPPE Variant Types
OPPE04 Define iPPE Alternative Types
OPPE05 Define iPPE Relationship Types
OPPE06 Customer-Spec. Model Assgts (iPPE)
OPPE07 Time Analysis: Partner Products iPPE
OPPE11 Profiles: iPPE WB Professional
OPPE12 Tabs: iPPE Workbench Professional
OPPE13 User Assgmt: iPPE WB Professional
OPPE14 Define Reports for iPPE WB Prof.
OPPE15 Define Interface for iPPE Workbench
OPPE20 Profile Maintenance iPPE PS
OPPEACT01 Define Std Val. Determin. Type
OPPEACT02 Object Dependency in Process Struct.
OPPECHK01 Customizing: Consistency Check
OPPEDOK Documentation
OPPELUI01 Profile Definition: iPPE WB Express
OPPELUI02 User Assignment: iPPE WB Express
OPPERES01 Customizing for Production Resources
OPPESCMPV Object Dependent Status Management
OPPESTATUS Cross-Application Status Management
OPPF Customizing for Order Report
OPPH Customizing Purchase Req. Conversion
OPPI Available Stock
OPPJ MRP Checking Rule
OPPK Hierarchy Element
OPPL MRP
OPPM Evaluation Profiles
OPPN Layout
OPPO Hierarchy Element
OPPP Customizing Direct Procurement
OPPQ C M MRP Plant Parameters for MRP
OPPR C M MRP MRP Group
OPPS Strategy
OPPT Strategy Group
OPPU Strategy Group for MRP Group
OPPZ MRP Group
OPR1 Area of Responsibility <-> Message
OPR3 Definition of Breakpoints
OPR4_ACT Multilevel Actual Settlement
OPR4_CK Material Cost Estimate
OPR4_CKMC Mass Costing - Sales Documents
OPR4_CKML Closing and Calc. of Periodic Price
OPR4_CKPF Price Update
OPR4_FCO Collective Processing: Variances
OPR4_KKA WIP Calculation
OPR4_KKP Repetitive Mfg and Process Mfg
OPR4_KKS Collective Processing: Variances
OPR4_KKS1 Individual Processing: Variances
OPR4_PPCO Production Order: Cost Calculation
OPR5 Definition of Error Mgmt IDs (SAP)
OPR6 Definition of Object IDs (SAP)
OPR7 Def. of Areas of Responsibility
OPR8 Def. of Minimum Message Types (SAP)
OPR9 Def. of Reference Objects (SAP)
OPRCMFE User-Defined Messages
OPRF Maintain Quotation Prefixes
OPS Customizing for Project System
OPS0 Maintain print control for networks
OPS1 Maintain User Fields
OPS2 Maintain Relationship Texts
OPS3 Maintain PS Text Types
OPS4 maintain simulation profile
OPS5 Maintain Standard Network Profile
OPS6 Maintain Project Manager
OPS7 Maintain Applicant
OPS8 Materialflow network
OPS9 Budget Management Profile
OPSA Maintain Project Profile
OPSB Cost Planning Profile
OPSC Create network types
OPSCAS Command File Payments (PS)
OPSCOS Command File Costs (PS)
OPSD Maintain Profile for Report Lines
OPSE Maintain Report Groups
OPSF Maintain Report Variations
OPSG Order change management profile
OPSH Maintain ctrl. key for activity (PS)
OPSI Edit PS validation rules
OPSINS Command File Info System (PS-F)
OPSJ Maintain Project Coding
OPSK Maintain Special Characters
OPSL Project Info System Overview Maint.
OPSM Maintain Overall Profile PS InfoSys
OPSN Edit PS substitution rules
OPSO Maintain Project Types
OPSP Capacity availability check
OPSPAR1 Maintain Partner Functions
OPSPAR2 Define Lang.-Dep.Partner Functions
OPSPAR3 WBS Partner Profile
OPSQ Intervals for Cost/Revenue Types
OPSR Maintain milestones
OPSREV Command File Revenues (PS)
OPSS Maintain milestones
OPST Network Confirmation Parameters
OPSU Maintain Activity Control Key
OPSV Cost object ind.
OPSW Info System Profile
OPSX PS: Reset "Budgeted" Status
OPT1 Maintain PS Transaction Types
OPT2 Matchcode for project definition
OPT3 Matchcode for WBS elements
OPT4 Matchcode for standard network
OPT5 Customizing matchcode for network
OPT6 Maintain std. milestone group
OPT7 Project planning board profile
OPT8 Maintain hierarchy graphic / dates
OPT9 Network parameters for PS-SD
OPTA Command file for PS -> FI area
OPTB Command file for WBS
OPTC Command file for network
OPTD Command file for standard network
OPTE Command file for PS info system
OPTF Command file for PS graphic
OPTG Maintain PS Info Summztn Criteria
OPTH PS info system maintenance
OPTI Maintain Progrss Analysis Overview
OPTJ Maintain PS Info Unit Conversion
OPTK Exclude Cost Elems from Avlbty Cntrl
OPTL Maintain PS Info Comparison Criteria
OPTM Fincl Budgeting Profile for Projects
OPTN Maintain priorities
OPTO Change costing variants
OPTP Sub-network parameters
OPTQ Maintain WBS scheduling parameters
OPTR Strategies for settlement rules
OPTS Maintain project version profile
OPTT Maint. acct.assgnm.types for orders
OPTU Maint. PS Info System field settings
OPTV Maint. PS Info System sort criteria
OPTW Maint.PS Info System group. criteria
OPTX Maint. PS Info System database set.
OPTY Capacity leveling - Time profile/PS
OPTZ Matchcode for standard WBS elements
OPU0 Matchcode for standard project def.
OPU3 Production order control parameters
OPU4 Maintain Capacity Planning (SOP)
OPU5 Parameter long term planning PlndOrd
OPU6 Production order control parameters
OPU7 Control parameters plant maintenance
OPU8 Overview Var.: Header Line Info Sys.
OPU9 Overview Variant: Item Line
OPUA Field selection: Network: Header
OPUB Field selection: Network: Overview
OPUC Field selection: Network: Details
OPUD Field selection:Network confirmation
OPUH Field sel: Std. project definition
OPUI Field selection: Std. WBS elements
OPUJ Field selection: Project definition
OPUK Field selection: WBS element
OPUL PS: Maintain reduction strategies
OPUM Maintain Subprojects
OPUN Capacity overviews
OPUO Project schedule overviews
OPUP Subnetwork schedule overview
OPUQ Overall network scheduling overview
OPUR Info System: Structure overview
OPUS Maintain Version Number Entry Mask
OPUT Maintain overview variants
OPUU Maintain Network Profile
OPUV Network Type Parameters
OPUW Standard Network Status
OPUX Maintain overview variants std netwk
OPUY Overview var.:Std.ntwrk scheduling
OPUZ Control parameters plant maintenance
OPVC Convert Avlability Cntrl Tol.Limits
OPVP Collective availibility checkProfile

Transaction Code To View All SAP Tables

What is the transaction code to view all SAP (PP) table,or there is some other way to view?

By: Riki Paramita

To browse tables which specified for PP module only, you can use SE16 with a specified application component & sub-component. First, go to SE16, browse the application component (ex : PP), then select the sub-component (ex : PP-SFC, for Production Orders related tables); and all tables within the specified area will be displayed.

In tcode SE16, click the Down Arrow next to the Table Name field:

Then it will pop-up a screen, look at the bottom of the screen:

SE16 - SAP Application Modules

Then select components by clicking the + sign to open up the sub-compenent you want. For e.g.:

SE16 - SAP PP Module Tables

Some important tables within the PP area :

MAST - Material BOM
STKO - BOM Header
STPO - BOM Positions (detail)
MAPL - Assignment for Task Lists to Materials
PLKO - Routing Group Header
PLSO - Routing Group Sequence
PLPO - Routing Group Operations
AFKO - Production Order Header
AFPO -Production Order Position (details)

Related tables in MM area :

MAKT - Material Descriptions
MARA - General Material Data
MARC - Plant Data for Material
MARD - Storage Location Data for Material
MAST - Material to BOM Link

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
What is the T-Code for trigger point?

CO30 MENUCO30 Standard trigger points
CO31 SAPMCNSM Create standard trigger point
CO32 SAPMCNSM Change standard trigger point
CO33 SAPMCNSM Display standard trigger point

What the tcodes to archieve/delete a material BOM? - by Jia

Look at this option to delete a material BOM

There are two ways of deleting BOMs:
- Using the Delete function.
- Using the Deletion indicator.

If you select the deletion indicator, the BOM is archived in the next reorganization run, and can be deleted if required. In the BOM header, you set the indicator that controls physical deletion after the archiving run. You can still process the BOM within its validity period.This also applies if the deletion indicator is entered with reference to a change number with a valid-from date that is after the date of the next reorganization run

You can use the below mentioned tcodes:
CS25/CS28 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs

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

Commonly Used Tcodes in PP Module Part 3

Material Requirement Planning
Menu Nodes TransactionActivity
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
Where shall we maintain number range for planned orders?

To maintain number range for planned order. Go to:
MM-->CBP-->NUMBER RANGE-->DEFINE NUMBER RANGE FOR PLANNING RUN.
Don't allow External Number Assignment.

What is t.code for planning calendar and factory calendar?

Planning Calendar--MD25
Factory Calender--SCAL

Menu Path
SPRO-->Materials Management-->Master Data-->Maintain Planning
SPRO-->Calendar--md25

SPRO-->General Settings-->Currencies-->Expiring Currencies-->Maintain
SPRO-->Calendar-->SCAL

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

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 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

Wednesday, April 1, 2009

PP Scheduling 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.

PP Scheduling 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.

PP Scheduling 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.

PP Scheduling 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.

PP Scheduling 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.

PP Scheduling 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.

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.

PP Production Order Production Setup Time

My client has a production setup where there is a particular activity which has a setup time of 8 hrs when it is executed for the first time, but if another production order is taken up for the same material then the set up rime is zero. That is if I produce a material x at a particular work center the for the first time the set up time is 8 hrs, but if another production order of same material x is executed right after this order then the setup time is zero. Now, if we give the setup time as 8 hrs in routing then the system will calculate total time taking 8 hrs as setup time each time. Is there any way in which the system takes the setup time as zero when a production order for a particular material as repeated.

Soumyadipta

Take a look at the functionality associated with the set up group and transition matrix, if I remember rightly though the setup times are only adjusted after production orders have been despatched in the planning table as this is the first time SAP is aware of the sequence of manufacture

Paul

If I am not wrong, setup matrix and transition matrix can be made use of when you go from one operation to the other in a particular routing. But, here there is only 1 operation in the routing and that operation is being repeated for different production orders of the same material. Can this different setup times be given for this same operation.

Soumyadipta

If I remember if setup group key is defined in the operation in the routing and then the transition times between setup keys is maintained in configuration.

So it's possible to create something like the following:

From Key 1 To Key 1 30 mins
From Key 1 To Key 2 8 hours

So different the operations in orders for the same material should both have the same key and should have a setup time on 30 mins between them.

Then when a different material with a different setup key comes along in the manufacturing sequence it will pick up an 8 hour setup time

Paul

I am facing a much similar problem. We have 15 work stations and daily 50 - 60 production orders are printed. I am maintaining production time as well as set up time in the routings ( There exists a separate routing for all the part no's ). When a production order is printed it copies the setup time from routings. Suppose in one work station there happens has to be 2 production orders processed one by one then the setup is only once. but due to the fact that setup is present in the routings the production order shows a non-conformity of setup time for the 2nd production order. How to solve this problem.

Narendra S

We have a similar situation in the company I work for, we don't actually maintain routings at material level but use reference operation sets at an aggregate level to represent the different production footprints (the link to each material is then made through the production version in the material master).

We measure the actual setup time confirmed in each order belonging to each footprint / family over a rolling three month period and maintain an average setup time in the reference operation set. This gets copied to each production order, but is only to make sure that a time allowance is left in each production week for set up to create meaningful capacity planning data.

When the planners develop the manufacturing schedule using the graphical planning table they then update the setup time in each order automatically with the setup times maintained in the transition matrix so it's more accurate, as it takes account of the order being made on the workcentre previously. So in our case two orders sharing the same footprint will have different setup times.

PP Production Order Material Stock in Production Order

I have the problem in stock against production order:

Our scenario is we don’t want to create a sales order. I create a production order that has 5 operations. The first operation is sub contracting. Through control key (External operation) I create the purchase requisition and convert purchase order in that operation. Through the PO I can issue the ROH and received HALB. When I received the HALB the stock of ROH is automatically reduced. But HALB stock doesn’t increase. In this case where is my HALB material for second operation?

In this case how to proceed?

Do you have a material code for HALB? if you have material code than you can have stock increased. I think there's some mistake with the process. the subcontracting in operation is only for the operation, not the material.

In your configuration, you subcontract the first operation of the FERT production. and there's no stock increase of FERT or HALB when the first operation is completed (confirmation by purchase order...)

And what you want could be possible like this:

You create the HALB material code, and you make it external procurement (F in standard) and with special procurement key subcontracting (30 in standard) (enter these fields in material master mrp2 view). Then you can create purchase order for the HALB material when needed, and send ROH material to the subcontractor for the purchase order and post goods receipt for HALB material and stock increases. And accordingly, since the production of HALB is a different process, not a sub process of FERT material, you should change the routing of FERT material to 4 operations, omitting the first operation, which is subcontracted production of HALB. And you should also change the BOM of the FERT material, and remove the ROH (which is used for producing HALB) and put the HALB material itself.

PP Production Order Automatic Conversion to Production Orders

Is there anyone out there who knows if it is possible to make an automatic change of planned orders to production orders right away - or perhaps even to skip the planned orders and create pp - orders instead?
I have a customer who want to do this (skip the manual conversion).
Perhaps it is impossible?

To create production orders in MRP run without checking first the order proposals (planned orders) is not a recommended process at all. It is against the accepted norms in production/inventory management and its MRP-2 logic on which SAP software is also based on.

If you have complex production - you'd have a nightmare closing all the production orders with the errors not resolved at the prior to conversion stage. On the other hand, if it is too simple production with only a handful of operations and no strict requirement of production control (which seems to be your case, for me), then please do away with production orders, and use the repetitive manufacturing where planned orders are the final.

I am confident that a consultant who can see the need and benefit for the wisdom of planned order conversion as a separate manual process, should ALWAYS be able to convince customer.

As always, the question is, whether you want the right shoe to fit the foot, or cut the foot to fit the shoe.

PP Production Order Regarding Production Order Confirmation

Production order confirmation with future date is not allowed

Future dates can be configured in the confirmation configuration.

In configuration OPK4, define confirmation parameters.

When this configuration comes up, in the "Checks" Sections, the last parameter says

"Date in the future."

Check this box if you want your dates in the future.

It determines whether dates in the future can be used in a confirmation.

If the indicator is not set, you cannot make any confirmations using dates in the future.

If you try to do so, the system will issues an error message.

What is the importance of Production Order confirmation? Is there any specification to use type of confirmation ie., CO11 or CO15 or CO11N ?

A confirmation documents the processing status of orders, operations, suboperations and individual capacities.
You can enter a confirmation
- For an Opeartion (co11/co11n)
You have the following options:
- To confirm quantities, durations, activities or personnel data.
- To make a confirmation at a particular point in time (for example, at the start of setup or the finish of processing) enter a
confirmation.
- When you confirm time events, the system calculates the required duration. For example, the setup duration is the time between setup start and setup finish.
- For an Order : CO15
If you enter a confirmation at order header level, the system confirms all the operations that have a control key in which
confirmation is optional or necessary. The quantitiesconfirmed in the operations are proportional to the quantities confirmed in the order header. *-- Rajesh

I want to stop the confirmation of production order whenever there is no goods issue to the production order so that I can get the correct material accounting report. I can't set backfliush indicator to the material at Routing level because we are handling the raw material in batches, so I have to assign the batches to issue the raw material.( tcode CO27 ).
We have set the criteria to release the production order is only availability of raw material in plant, so system checks only the availability of raw material & releases the order. Is it possible after issuing the raw material the release of order took place?

Goods issues before release of order is not possible in SAP.
You can think of following things.
1) In opj4,you can block release of order if it has missing parts.
2) By using 'user exit' it is possible to disallow confirmation if goods issues are not posted against each component.