SAP Project System (PS) DEMO

SAP PS – Q&A

Project Functionality of - SAP-PS (Project System)

The Project System module of SAP (PS) is specifically designed to provide comprehensive and fully integrated project management functionality for SAP customers. When it was originally designed and developed its core functionality was borrowed from and shared with the PP and CO modules.  So most of the PS objects (WBS elements, networks, activities, activity elements) are cost objects similar to cost centers in CO, while networks have scheduling and resource management capabilities that are very similar to PP. Whenever you need flexibility and frequent user interaction for resource loaded scheduling activities, you still feel the remnants of an architecture and user interface that was originally designed for the more static context of PP.    Shortcomings include user-friendliness since SAP did not manage to satisfactorily put the end user in control to easily manipulate the data. In that respect, SAP's unsurpassed enterprise functionality often is perceived as an issue by end-users. Also, and somewhat ironically, PS and PP are not seamlessly integrated. This means that costs or dates do not roll up or cannot be pushed down between PS &PP.

What is SAP PS?

Projects are generally part of the internal processes of a company. To be able to control all tasks in project execution, you need an organizational form that is specific to the project and which is shared by all departments involved. Before you can carry out a project in its entirety, the project goals must be precisely described and the project activities to be carried out must be structured. A clear, unambiguous project structure is the basis for successful project planning, monitoring, and control.

The high degree of integration between the Project System (PS) and other R/3 application components means that you can plan, execute, and account for projects as part of your normal commercial procedures. This means the Project System has constant access to data in all the departments involved in the project.

The R/3 PS guarantees close and constant monitoring of all aspects of your project including both technical and commercial aspects of the project.

Versions in Project Systems

 

Explain the type of version in SAP Project Systems.
Basically, there are different kinds of versions in PS. They are:

1. Project versions - these are basically snapshots of a project at different stages of a project. Based on how the system is set up, a version could be created everytime the system status of a project object is changed, for example. Or, you could manually create a project version in transaction CNS41 or the like. You could create a version with a key and then you could compare the different snapshots of a project against each other or against version 0 (operative project).

2. Simulation versions - these are essentially "play around with" versions. Meaning that you could use them to try "what if" kind of scenario by changing dates, structure, milestones, etc... and compare results with the operative version. For example, you may want to determine what the impact is going to be of a certain change to the project before making the actual change to the operative project. Then, you could create a simulation version, play around with it to make sure it does what you want it to do, then make the actual change to the operative change or you could convert the simulation version to the operative version also. I am not sure if they are hidden issues in doing this, but to make the point here, the simulation version is a "play ground" for "what if" scenarii for the project. The main difference, I believe, between the project and simulation versions is that project versions cannot be changed/modified once they are copied, while simulation versions can be. Also, you cannot copy a project version to an operative version, but you can copy a simulation version to an operative version.

3. Planning/Controlling versions - these are the versions used for storing different kinds of planning details for the project. Essentially, these versions are also "operational" and can be changed as needed. For example, you may want to keep the operative version (version 0) always for actual costs, while you will use planning version P1 to store planned values from ECP, then version P2 for Unit Costing values, etc... Unlike simulation versions however, you cannot copy a planned version to the operational 
project (I don't think). You can however, copy one plan version to the other.

4. Progress Versions - These versions are used for carrying out Earned Value Analysis and other measurements against project progress based on POC, etc.  Progress version is controlling area specific and defines the control data for POC and earned values. It is mandatory to maintain progress version along with method of calculation. The system records progress analysis data in the progress version. That is why you can get the result only if you maintain it in the progress tab of WBS.

SPRO -> Project System -> Progress-> Progress Analysis -> Define Measurement Method as Default.

Here you define the Version, Object Type, Plan/Actual, Default Measurement Method.

After that Version would be defaulted for the object in the hierarchy.

 

 

SAP PS – Basics of Project System- http://www.sap-basis-abap.com/sapps.htm

This course covers basic SAP Project System in 10 lessons, including master data, project planning, acquisitions, network activities and settlements using the new Project Builder. This is an interactive simulation course and includes simulated SAP screens. This allows you to interact with the screens just like a real SAP system, including entering data in fields and clicking on buttons or links.

SAP PS Training Goals- This course will help you become familiar with SAP's PS (Project System) module using the Project Builder. You will learn how to:

• Create a Project with Work Breakdown Structures (WBS) & Network Activities
  
• Create Project Plans with Easy Cost Planning and Project Planning Board
  
• Create Requisitions and Purchase Orders for WBS
  
• Run Settlements
  
• Run Project Reports
  

This SAP PS training uses ECC 6.0 (newest SAP release) and includes 420+ training slides, study guide for each lesson, 60+ pages of additional SAP documentation and email support.

"The training is very clear and easy to understand. The fact that it can be done anytime is a "great" feature as I could do it at home with no interruptions. Also having the capability to back up and repeat a process is extremely helpful. With no set time limits, when I was ready to book an asset, I could review just that section and get pointers right on the spot."
Pat Z., Whirlpool Corporation

Training Content

Lesson 1 Create Project Structure & Work Breakdown Structures
Lesson 2 Create Network Activity
Lesson 3 Create Project Plan (Cost Planning & Project Planning Board)
Lesson 4 Create Requisitions & Purchase Orders for WBS
Lesson 5 Complete Network Activity
Lesson 6 Settle Network Activity to WBS
Lesson 7 Settlement to Asset under Construction
Lesson 8 Run Project Reports
Lesson 9 Create Final Settlement Rules
Lesson 10 Project Closeout and Final Settlement

Transaction Codes

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

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

 

 

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 For PS Module

What are those standard project system tcodes?

No Transaction Code Description

1.   CJ20n                 Creation of Project
2.   CJ20n                 Creation of WBS Elements
3.   CJ20n                 Creation of Activities
4.   CJ20n                  Assigning relationships to activities
5.   CJ20n                  Assigning of milestones to activities/WBS Elements
6.   CJ20n                  Assigning of materials of activities
7.   CJ40                    Planning of costs to project
8.   IMCCP3              Copy Planned cost to budget
9.   CJBV                   Availability Control of budget
10. CJ30                    Assigning Budget to Project
11. CJ20n                   Release of Project/WBS Elements/activities
12. CN25                   Confirmation of activities
13. CJ20n                   Maintain actual dates to milestones of WBS Elements/activities
14. CJ37                     Supplement in project
15. CJ38                     Return in project
16. KB21n                  Direct Activity Allocation
17. CNL1                   Create Delivery Information
18. CNL2                   Change Delivery Information
19. CNS0                   Delivery from project
20. CNL3                   Display Delivery Information
21. CJ2c/CJ20N         Display Project
22. CJ41                     Display cost planning
23. CJ31                     Display Budget
24. CN28                    Display Confirmations
25. CJ3B                     Display Document (BUDGET)
26. CN29                    Cancel/Reverse of Confirmations
27. CN41                    Structure Overview
28. CN42N                 Overview of  Project Definition
29. CN43N                 Overview of WBS Elements
30. CN46N                 Overview of Networks
31. CN47N                 Overview of Activities
32. CN55N                 Overview of Sales Document items
33. CN53N                 Overview of Milestones
34. CN52N                 Components Overview
35. CN42                    Enhanced Overview of Project definition
36. CN43                    Enhanced Overview of WBS Elements
37. CN44                    Enhanced Overview of Planned Orders
38. CN45                    Enhanced Overview of Orders
39. CN46                    Enhanced Overview  of Networks
40. CN47                    Enhanced Overview of Activities
41. CN48                    Enhanced Overview of Confirmations
42. CN52                    Enhanced Overview of Components
43. CN53                    Enhanced Overview of Milestones
44. CNS54                  Enhanced  Overview of  Sales and Distribution Documents
45. CNS55                  Enhanced Overview of Sales Document items
46. ME5J                     Purchase requisitions for Project
47. ME2J                     Purchase Orders for Project
48. CNMM                  Project Oriented Procurement
49. CN60                     Display change documents
50. S_ALR_87013542 Actual/Commitment/Total/Plan in Control Area Currency
51. S_ALR_87013557 Budget/Actual/Variance
52. S_ALR_87013560 Budget Updates
53. S_ALR_87013532 Plan/Actual/Variance
54. S_ALR_87013533 Plan/Actual/Commitment/Rem.Plan/Assigned
55. S_ALR_87013534 Plan1/Plan2/Act/Commitment

SAP Project System SPRO Tcodes List 1

CJ20N is basic Tcode most of the functions can be accessed with this.

Usually it involves:
- Create proj definition -- cj20n
- Create wbs elements (more than one wbs can be defined for a project) -- cj20n
- Create network -- cj20n
- Define activity for network -- cj20n
- Assign component to the activity
- Post a goods issue for the component -- MIGO mvt type 281

T-Codes List Used In SAP-PS For Customization Part 1

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

 

SAP Project System SPRO Tcodes List 2

How to delete PS master data and transaction data?

This is a complex one. SAP usually does not allow you to delete anything. You will have to archive and then delete the objects. If there are "bad" projects without any transactional activity, you can mark the projects with status DLFL. To archive, use transaction code SARA.

You will have to get your entire functional team - MM, SD, FI, CO, PS - and decide on a module-by-module and transaction-by-transaction basis on the best approach to purge this data. You will also have to think about auditing and retrieval if this is production data.

Solution is Archiving. It's a seperate process better consult you basis consultants for this.

Archiving object you should be looking at is PS_PROJECT (T Code SARA)

T-Codes List Used In SAP-PS For Customization Part 2

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

SAP Project System SPRO Tcodes List 3

How to schedule the network within the dates provided in the network header?

The problem is that every time I schedule the network, scheduling happens as per the date given in assigned WBSE & not as per the dates specified in NTW Header.

Go to Project Planning Board. Click on the "Options" icon. 
- Select the "Scheduling" option. 
- On the tab "Scheduling parameters for activities", the "Scheduling method" selected should be "X Network determines dates". In your case I believe it is "WBS determines dates".

You can set this in SPRO-->Project System-->Dates-->Date Planning in WBS-->Define parameters for WBS scheduling--> Select Scheduing method as "X Network determines dates"

 

T-Codes List Used In SAP-PS For Customization Part 3

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

Planned Cost Differs from Actual Cost

Question : I have a problem. I have a standard activity which the price is $1 / hr.   I have created a project in which a activity has a planned hr of qty 1. But my planned cost comes in as '$0.83'.   But when I comfirm my activity, the actual cost comes in as '$1'.

Why is my planned cost differing? What is the cause of the $0.83 instead of $1.  Where can i check and change this.

Answer : I guess that you use different costing (and valuation) variants. so the system might valuate plan and actuals differently.

Question : Where and how do i control it?

Answer : In the network header are two fields: one for the plan costing variant and one for the actual costing variant.

You maintain the costing variants in the customizing: PS -> Costs -> Planned Costs -> Automatic

Costing in Networks -> Costing -> Define Costing Variants. Display the costing variant and jump to the valuation variant. There you find how the determines the costs.

Validations in PS

Question : I am trying to use validation in the Project.   Can any one tell when are the call up points 110 and 120 trigerred ?

I want to validate one of the user defined fields in WBS.

Everything is working fine when I simulate the validation. But when I enter a value in the user defined field and save the project then I do not get the error message as expected.

Does anybody have an idea what could be wrong ??

Answer : Please see if you have checked the check box for Automatic validation in the relevant project profile.

Question : I want to validate the customer number in one of the user fields in WBS.   The formula builder in the validation screen, it seems, does not support table fields other than fields from PRPS.   Can this be done thru some user exits ?? If yes how ?? Can u guide me in this ??

Answer : To use a user exit in validations, you have to perform following steps;

- copy SAP standard program GGBS002 to ZGGBS002
- create a user exit in this program (such as U902, U903 etc)
- the user exit you defined in the above mentioned program will be visible in validations on screen tab 'Exits'
- configure your validation with 'User exit' as option

WBS description doesn´t appear completely in hierarchical

Question : In the hierarchical reports in PS de WBS description is not showed completely. Do you know a way to make this appear completely?

Answer :-

We are on 4.6B and this is what you can do. :-
1) Execute report
2) Expand your results, if necessary
3) Click on any WBS line description
4) Follow the menu path Settings/Characteristic display
5) Choose lead column
6) Move object short description to the value set side of the panel
7) Move object long description to the lead column side of the panel

Save (if you have authorization). Note you can use this procedure for any other object that may show up on the report display. i.e. navigation characteristics change the objects displayed.

Anyway to put checks before setting to TECO?

Question : Can anyone pl let me know about the followings:
Is there any way to put checks (in the form of tick mark etc) before setting the system status to "TECO"- e.g. some documents are received or not etc.

Answer : You can set the system status to Technically completed TECO which can be later on withdrawn. The necessary changes are reflected in the system status on saving the Network

With the setup of user statusses (tr. OIBS), you have the ability to disable the 'TECO' as long as a certain user status 'e.g. waiting for documents' is active

Links to documents stored on the Web

Question : Is there a way to create a document (under a project) which refers to a URL and not to a document stored on a content server?

Answer : Yes you can, but you need define in DMS customizing some points.

1.- Inner "Define Data Carriers" in Define data carrier type external "DMS" a record with this information: TYP = IE, Description = That you want, Check ONLINE and EX, the inside this in Define External DMS create a record with DATACAR = INTERNET, TYP = IE, Description = That you want, Check EX.

2.- Inner "Define Workstation Applications" define an application for web pages without file format, inside this in "Define Workstation applications in network" create records for options 1, 2, 3, the path of location of your navigator in your PC or you can put "%AUTO% iexplore.exe %f".  Then when you create a document in the Original field you can put the URL and in the Data Carrier field put the name that you define in the customizing.

How to settlement auc to asset in PS?

Question : The cost of project have settled to auc(investment asset), but when the project is finished, in AM or in PS i can't settle auc to asset?

Pls give me some suggestion! Any idea is appreciation!

Answer : You must set technically complete for your WBS & NW before settle AUC to Assets.

Updating the current Order cost plan

Question : We are in 46C. Starting a project, we establish an Order cost plan. We plan the amount of work (in hours) and specify the work center for each of the activities. For material components, we enter the forecast material costs in the field "Material planning". We see the total and detailed by activity cost plan in CNS41 (Structure overview) in the column "Order cost plan 000".   At some point in time, the project advancement shows that we have to reconsider the original cost  plan, for instance because the actual costs collected so far are much higher than foreseen at start-up. Management decides to change the cost plan 000 to reflect the new forecasted budget.  Management already told that they would like to be able to specify a new total value for the Order cost plan 000 of the activity rather then to play with the amount of work (hours) in the activity. They say it should be something like this (for labor): (actual cost) + (number of hours to do * cost of work center) = order cost plan 000.

What options do we have to modify the "Order cost plan 000"??

Answer : There is a functionality called cost forecast (transaction CJ9L/CJ9M). I think this is exactly what you require. The forecasted costs are saved in a separate CO version. You could try to display this version in CNS41.

Create network from Sales Order

Question :

We are currently running 4.6C and have implemented SD and PS. The situation is we want to be able to create a network automatically from the sales order during creation.

I've assigned the strategy group 85 to the material master and I've defined the network parameters from sales order (via transaction CN08).

The result...

During creation of the sales order (transaction VA01), the network is created successfully but the components are not transferred to the network. Is it supposed to or not? If so, what additional configuration should I look at?

I'm not very familiar with the standard functionality so I'm hoping someone out there has experience with this topic.

Answer : The components in assembly processing remain on the sales order only.

In case you are working with reasonably complex scenario on BOM and procurement, where material items have their own dependencies schedulewise e.g to design, you should put the materials on the network. The best way to accomplish this is to do the BOM allocation (transfer) to activities and have only the invoicing item at sales order.

IM and FM

Question :
Is that possible to use IM to control investment projects and FM to control general costs?
What is needed to be done in order to avoid conflicts between IM and PS ?

Answer :
Investment Management() IM Module is highly integrated with controlling(CO) , project system(PS), and Asset Management(FI-AA) components.

IF you would like to implement IM & PS you might ask yourself what additional advantages are offered by using IM .

These Include:

1- in PS you can represent the planned and the budgeted values of all projects . using IM you can represent the budgeting process from the organization pointview. IM helps you track of budget amounts that you carry forward for projects that were approved in prior fisical year.

2- Using AR in IM CAN help you decide what budget will be assigned to your organization Unit.

IM Handles Cost Planning & Budget Approval and PS Manages Project Execution with AVAC for the Budget for each project.

Multiple Root WBS

Question : Can any one tell me in detail of advantages and Dis-advantages of Multiples Root WBS in the project.And one more why do you using the same coding Mask for PD and Root WBS.

Answer : Multiple Root WBSEs helps in budgeting scenarios where these WBSEs are funded from different sources say a customer project has part scope of R&D (funded by R&D).

You may also want to fund these root WBSEs from IM programs (linking to position IDs.)

Question : Subject : PS Assets under Construction

I know that I can maintain the Plant for the WBS Element, what I would like to know is if it is also possible to maintain the Location as well? I've heard that it is not possible but I would like to hear other opinions. Any suggestions? We are on version 4.0B.

I would like to know since the Asset Management people here are asking if it's possible to maintain it in PS or if this can only be done in AM.

MM is not included in this implementation, but we did set up the Plants and Locations.

Reply : Subject : PS Assets under Construction

you can maintain a location for a WBS element as well. Select WBS element, follow path Details > Orgainsation. This screen has a field called Functional Location, apart from other orgainsation details such as Controlling Area, Company Code, Business Area, Plant, Calender etc

Question : Subject : PS Network Status's & Confirmations

Is there a status that can be set for a network activity that will stop time confirmations from being processed? TECO stops changes to the basic data, but allows further time confirmations.
 

 

 

Reply : Subject : PS Network Status's & Confirmations

you can lock account assignment for the network/activity in consideration depending on whether the network is header/activity

assigned. This disallows the confirmation of the activities.

Any Variant Capabilities in CM07 Report

I am executing the CM07 report whuich is the Variable Capacity Planning Report.

Out of which, I like the results because I obtain the fields I need by going thru the individual ''choose fields'' button.

However in 4,6c) it does seem to have any variant capabilities ???

I have to reenter the fields selection every item I back out of the report ... Which is a bit anoying !!!

Anyone has any recipes for this so that columns/criterias selected  can be save guarded  for the next time ???

There are Variant list capabilities for CM07 Capacity report.

Mainly via PS-> Information Systems->Resources->Tools->Resources->Selection->General Profile  (OPA6)  and also via PS-> Information Systems->Resources->Tools->Resources->Selection-> Variant List Poifile Details (OPDT).

You create a new ''Z'' Variant Profile list with all the fields that you want to select and show in yopur  CM0?  report .

Be carefull to click correctly on the greenish/yellowish arrow to bring up the field selections pop up window...

Than associate this new Z  Variant Profile to a newly defined ''Z'' General Profile...

Then after you can override with othe Variant Lists  in the profile selection of the CM07 report txn.  itself if needed

Change Documents in SAP Project

In the Customising for Create Project Profile (OPSA) there are 2 fields for "Change Documents".

Where and how is this useful during implemenation?

There are 2 outcomes for change documents and they should both be implemented if it's important that you keep track of changes made to a project:
 
General changes (the one at the top)

- any field content changes made to a project WBS after it was first saved will be recorded in a file. eg. if you changes the WBS description, the old value and the new value will be recorded, or if you changed a person responsible, it would also be recorded etc. This information can be reviewed in Info Systems report CN60 to old/new values and who/when.
 
Status Managment (the one checked in Status Management)

- any changes to System and User Status will be recorded, including the status history and who/when. Changes can be seen in any project maintenance transaction (eg. CJ02, CJ20N) by clicking on the "i" icon for a PD or WBS, then following the internal pull-down menu path: Extras>Change Documents> For Status/All.You can then drill-down on the satus to see its history.

SAP PS Interview Questions

Q1. For raising Client billing, is there any possibility of linking line items in SD module with Activities / WBS in PS module? 

A1. It can be linked through DIP Profile and do Resource Related Billing for raising billing.

Q2. Can Revenues be linked with Activities?

A2. No, it can be done at WBS level with 'Billing' operative indicator.

Q3. Can progress be updated in WBS elements?

A3. Yes, You can use Progress Analysis (EVA) for this.

Q4. We would like to compare the planned cost, actual cost & revenue for line items in SD module. For this as what object should we consider the line item in PS module.

A4. You can use Billing level WBS in PS module. 

Q5. In easy cost planning/ cost models, the resource requirement details (quantity and rate) are given to get the cost of each line item. But to get planned cost of each activity, the consultant is asking us to assign resources separately again in activities. If we consider the line items as activities, should we assign the resources again or the same in easy cost planning / cost models can be linked to get the resources assignment in a simpler method.

A5. Instead of this, you can use costing variant for Easy Cost Planning (not for the activities)  

Is there any way by which we can lock two specific wbs elements say overheads and other expenses, so that the user cannot release PR?

The easiest way would be to define the project release process in the bottom-up fashion. That means, you will only release the activities/WBS elements that you need from time to time during the course of the project. That way, charges won't be accrued on a WBS element until it's released (so, don't release it until it's ready for collecting costs).

Is there any way by which we can stop the network from attaching further materials after it is released?

This is controlled through the change profile, which is assigned to the network profile. In the change profile, under the Component tab, you can define the release status of the activity at which you can create/change/delete material components.

How can we set the options for capacity reports CM01?

This will possible depend on your config, but the options I use are:
    Settings>General>
    Tick, Cumulation of reqmts, Dyn. capacity cumul. and then select the hierarchy you have set up.
I then select the financial year (as we are budget driven) using Entry type A and the start/finish of the financial year.
I select period Month.
Then click tick.
I then select the work centre I require. or arm of the hierarchy.
You can then select standard overview and also select graphs or if you need a detailed list press that button.   *-- Jim Carter

Short Interview Q& As on SAP PS

Project Calculations

When we confirm activities and see it in cns41 report we can see that the POC is aggregated at the Network,WBS and project level.

 

How does the system calculate this.. i.e on what factors and criteria?

PS, like, other Projects Programs used the Pondered advance has a project and structural (WBS) phisical advance.
IF you have a Project with only 1 activitie. The 100% phisical advance of the activitie is passed to the Project.
If you have a Prj. with 2 activities and both had 100% phisical advance.  The project has 200%? NO!, PS calculated this

Percent complete Activity A = 100 = A-POC
Percent complete Activity B =100    B-POC
Weigth or contribution of A = 30%     A-Wgt
Weigth or Contribution of B =70%      B-Wgt
(The sum of the weigth need to be 100%)

The Project Advance will be A-POC*A-wgt + B-POC*B-Wgt 
This implies =  100*30% + 100*70% = 30 + 70 =100

The weigth is a function of Men-Hours, Cost or Special-Weigth.  

User Status Report

In the business scenario used here a status profile containing different User statuses with authorisation controls has been set up in the Project Definition for controlling the process of Project creation & approval. The process flow is as follows - The project is created by the design team, after which it is sent to pre-audit team for approval, the pre-audit team approves it, on approval the project is released and the rest of the process flows on.  Each of the above phases is marked by an user status and on completion of a phase the user sets the next user status for the object. 

Requirement : An ABAP report is required to be developed which shows the date and time at which each of the user staus was set and released. 

Go to transaction SE38, and enter RBSVCDOC in the field "Program". Select the Execute button. Insert your WBS's object number, and select the tick box "SHOW_ALL" Execute the program.

If the results is what you are looking for, then follow these steps to have your required report on User Status Change Log:

1. Ask your ABAP program to copy function RBSVCDOC to a Z-Program, and 2. assign a Z-transaction code this copied Z-program. 3. You can also ask the programmer if he is able to design a user defined input screen to this program.

Creating an Internal Activity at the Network Level

Trying to create an internal activity at the network level and whenever I go to the menu to add an internal activity, the level moves up to the project level instead of remaining at the nework level.  This of course prevents me from creating the internal activity.  Why this is happening?

Work out the following path :
1) Go to "Structure Tree" (Top-left pane of Project Builder), click on Network Header.
2) In "Work Area" (Right pane) click on "Activities Overview" icon. Go to "Int. Processing Tab" and define activity with relevant field details and Confirm.

This will create Int activity in the selected Network only.   *-- Nabada More

Time calculation in work Center 

My requirement is to calculate the time taken for a component which contains 4 Operations.  Using Work Centers in PS Module.

  Details of the Operations:

  1. Chain cutting

  2. Soldering

  3. Lock fitting

  4. Assembly

Time taken for soldering operation = 15 sec/soldering operation

One component contains = 20 soldering operation

Total time taken to finish one component = 300 sec

In one day  we can make = 8 hr(28800sec)/300sec=96 nos.

How we can calculate this in the system Using Work Center.

  You need to do folowing....
  1) Define 4 activity type with these names and give the unit of operation as second - and assign it to a cost center in kp26 
      with cost
  2) Define a work center in CNR1...using usage project management 0006
  3) Assign formulae SAP004 in the other formulae in scheduling tab and SAP008 in capacity Tab.
  4) Assign working hours for your WC in capacity tab header data as 8 hours and put number of available capacity
      (no.of people in Work center)
  5) Assign all the activity types in the Work center costing tab
  6) Give duration for all these activity in your project 
  7) Schedule the project and do costing....    *-- Ritesh Bhushan

FAQ on SAP PS

Workforce Planning and Project Status

When a project status is set back to REL from TECO or CLSD status, the work force planning done is getting deleted completly at the activity. 

Run cmp9(Evaluation again) and you will have workforce planning back. 

 
 

WorkForce Planning

We are using CMP2 for doing workforce planning in our Org, we attach reources to activities, now the issue is we want to put an end date to the resource attached so that the particluar resource does not appear in cmp2 . 

P.S - we have tried by attaching resource to WBS too, it doesn't work. 

In CMP2 - mark the relevant line - press the bottom with the pencil - make a new end date and save. 

Next time you enter CMP2 the start date has to be after the end date you entered. 

Be aware that the end date affect the work list for the person in CATS. 

 

Table for System status (wbs)

I am trying to create one query to find out wbs status assigned Open PO. I have located the relevant file for PO but not able to get table which stores system status. 

The table names are JEST, TJ02T 

Pass the OBJNR to the table JEST you will get System Status Number. 

Once you get System Status Number pass it to table TJO2T you will get System Status text. 

 

WBS and company codes 

 

Is it possible to have two different company code within the same WBS structure?

For a single WBS element - NO 

Within the structure - YES provided company codes belong to same controlling area 

 

ISBD system status

Does anyone know if system status ISBD should be set if a budget tolerance with action "warning" is exceeded, however the total budget is not exceeded. We have the following set up: 

80% Warning 

90% Warning with mail 

100% Error message 

At 80% the system status ISBD (Insufficient budgeting) is set; is this correct. 

You are right. The status ISBD (Insufficient budgeting) is set once the tolerence limit 1 is exceeded. 

 

Project version: Can I go back to a previous version?

Can I go back to a previous version of a project? For instance, a new project version is created automatically on release of the project. Is it possible to go back to the previous version in order to "undo" the release? 

Project versions are used as snapshots of projects at different status or manually triggered points. You would not be able to go back to versions because the version is not the operative project. 

You will not be able to undo a REL status. 

 

Close the Project

How can I close the project, after closing any PRs and PO no Processing?

Open the project in CJ20N. Go to menu bar path: Edit-> status-> Close. Save project. Please note that you must first have gone through the normal progression of status moves from CRTD to REL to TECO before you will be able to close. 

List Of SAP PS Reports

No.Transaction code    Description

1.   CN42N                    Overview of  Project Definition
2.   CN43N                    Overview of WBS Elements
3.   CN41                       Structure Overview
4.   CN53N                    Overview of Milestones
5.   CN52N                    Components Overview
6.   ME5J                        Purchase requisitions for Project
7.   ME2J                        Purchase Orders for Project
8.   CNMM                    Project Oriented Procurement
9.   CN60                       Display change documents
10. S_ALR_87100185   Actual Costs for Each Month (Current Fiscal Year) 
11. S_ALR_87100186   Planned Costs for Each Month (Current Fiscal Year) 
12. S_ALR_87100187   Commitments for Each Month (Current Fiscal Year) 
13. S_ALR_87013532   Plan/Actual/Variance
14. S_ALR_87013533   Plan/Actual/Commitment/Rem.Plan/Assigned
15. S_ALR_87013534   Plan1/Plan2/Act/Commitment
16. S_ALR_87013537   Commitment Detail 
17. S_ALR_87013542   Actual/Commitment/Total/Plan in Control Area Currency
18. S_ALR_87013557   Budget/Actual/Variance
19. S_ALR_87013558   Budget/Actual/Commitment/Rem Plan/Assigned 
20. S_ALR_87013560   Budget Updates

Project Functionality of SAP-PM (Plant Maintenance)

The SAP Plant Maintenance module (PM) is designed to handle the management and execution of integrated maintenance processes. Such processes include preventative, routine and turnaround maintenance, all fully integrated with purchasing, MRP, controlling and financial accounting performed in SAP. The main objects used in PM are work orders, a series of which (often grouped by revisions) are what typically is thought of as a "project". Such maintenance projects are planned by describing the estimated work effort per "operation" (activity) and work center performing that work effort. By linking operations inside work orders or across them a generic project schedule is created.     Unfortunately SAP-PM has only limited scheduling capabilities. Therefore effective enterprise project scheduling for maintenance purposes requires either the use of the SAP PS module, the integration with external scheduling tools like Primavera or MS Project, or for less complex projects the use of external tools like GWOS (for more information about these tools please search this web site).    The basic master records used by Plant Maintenance are:   - Maintenance Notifications; - Maintenance Orders;  - Functional Locations; - Equipments; - Materials; and - Work Centers (Resources).    Functional Locations and Equipments contain fields that allow grouping by units, locations, or plant locations.

 

Project Functionality of SAP-CO (Controlling)

There are several important touchpoints between SAP projects and the SAP Controlling module (CO). All SAP cost planning and budgeting (in SAP terminology: budget = approved cost plan) functions are handled using standard CO functionality. Objects relevant to project management in SAP are cost objects. This means that planned, committed and actual costs can be charged to them like to a cost center or an internal order in CO. Among these cost objects are WBS elements, networks, activities, activity elements, maintenance orders, operations and suboperations.    Costs may be planned on many levels and in many ways, starting as investment management (IM) level or WBS structure level cost planning, through primary cost element planning, and going on to purchase requisitions, planned allocations, planned hourly use of resources with associated standard cost rates, and many more.    Actual costs may be charged to SAP project objects in many ways, typically through goods or service receipts, accounts payable invoices, general ledger (GL) postings, cost allocations or settlements. The SAP system will automatically perform the relevant controlling postings in the background so that CO plan-actual or plan-commitment-actual reports can be run in PS or PM.    Standard costing using standard cost rates associated with work centers (resources) are defined in SAP CO, either internally calculated or manually assigned. This then means that cost center-based controlling transactions have a direct impact on project costing.    The moment you say "costs" in SAP, you say "CO" automatically, even when dealing with projects in PS or PM.    Project Functionality of SAP-PP (Production Planning)  Production planning and project management in SAP have many touchpoints. They intersect particularly in a make-to-order environment involving sales-driven projects. In principle there are a lot of similarities between the production planning module (PP) of SAP and the Project System (PS) or even Plant Maintenance (PM). Production orders are very similar to networks or maintenance orders/work orders.    The main difference is that PP deals with ongoing operational aspects while PS and PM deal with projects. Projects are defined as a series of activities with a start and finish date in order to complete clearly specified deliverables at a high quality standard. From that perspective the main conceptual difference to PP is the limitation in time. PP, PS and PM all define a series of tasks, link them through relationships with each other, assign work centers to them to define where and by whom the tasks are supposed to be completed, and then schedule and cost these tasks out.    Even the tools used in SAP are very similar or often the same (like work centers, definition of relationships, resource leveling). This should not be surprising as particularly the PS module, and also to some degree PM, has been built by combining PP and controlling (CO) functionality. It does indeed seem that one reason why project management in SAP often is perceived as not user-friendly is due to that fact. Many of the "logistics" functions of the dynamically changing PS and PM modules are rooted in the much more static PP module. The result is great functional power but often clumsy screens and transactions.    The assignment of internally produced materials (components) to projects in PS or PM reflects another area where these modules intersect. In that case PP provides input to PS or PM, and the timing of this input is synchronized through scheduling and MRP (materials requirements planning) transactions.    There are a number of limitations in the way PP on the one side and PS and PM on the other side interact. At least in the standard SAP R/3 system costs and dates are not naturally rolling up or synchronizing between these modules.    Project Functionality of SAP-SD (Sales & Distribution)  What does Sales and Distribution (SD) functionality have to do with the management of enterprise projects? It does for more companies than may seem obvious at a first glance. For contractors using their own SAP system to manage and deliver capital investment projects the SD module is where the billable deliverables of their projects are defined. The same is true for everybody who uses the SAP project system (PS) to manage the make-to-order production of complex products, whether they are powerplants, aircraft parts, or the concrete bridges.    SAP has functionality that allows to tie reference (template) project structures to product codes so that at the time of sales order creation the setup of a project structure can automatically be triggered. This does then link SD and PS seamlessly, at least on a high level. As the project progresses, milestone billing set up in SAP-PS can then trigger payments in SD, which again results in revenue postings in the SAP financial accounting module (FI).    There are a number of other reasons where SD can interact with projects managedf in SAP. Mostly, however, it does so only when you take a comprehensive look at the overall process, trying to ensure full integration. Not doing so may lead to inconsistencies between what sales people or customer relationship personnel sees in SD and the actual status of the delivery of products. One may just consider a situation where SD data from a suppliers' system needs to be tied into a project master schedule managed by a general contractor. To overcome the latter it is helpful to mirror and match purchase orders and sales orders between supplier and customer, also in line with the way the general project is managed.    Project Functionality of SAP-IM (Investment Management)  The potential significance of SAP's Investment Management module (IM) is too often overlooked when considering the management of complex enterprise projects. Nevertheless it should in most cases be considered when designing scalable project management solution that center around SAP.    SAP IM is a tool designed to enable program management in SAP. Program management as defined by SAP in that context means the process of defining a hierarchy on top of many projects with the purpose of planning and controlling costs, including project appropriation management and budget authorizations. Its strongest integration points, besides PS, are with the SAP Controlling (CO) and Asset Management (AM) modules.    While IM was originally developed for the budgeting and high-level management of capital investment initiatives, its functionality has been extended to allow its use for similar functions. It simply is a tool that can perform such functions on top of any kind of PS projects.   Preferred Project Management Tool is...   SAP Project System (PS)     Primavera Enterprise/P3e   Microsoft Project     SAP with Primavera       Difference between SAP PS and PM?   The SAP world makes an important distinction between "PS" and "PM". The acronym "PM" is a source of frequent confusion. For many project management professionals it simply stands for "Project Management", while in the SAP community it is the abbreviation for the "Plant Maintenance" module of SAP.  The SAP PM module was not designed as a project management module. It still contains a lot of components very similar to the SAP PS module, which is the project management module called "Project System". SAP define their modules by function more so than by the process they cover. The Process Building Blocks for Projects with SAP Forget about technology and do not pay attention to modules: The key process blocks of Enterprise Projects deal with functional aspects! To set up an effective project management system, these functional aspects need to be clearly defined. If multiple tools are used, responsibilities per functional aspect and project management layer need to be assigned to one tool only, for each layer of the enterprise project (enterprise, project, and contractor).  Key process blocks or functions are:  1. Structures (WBS in SAP-PS) 2. Schedule (Network) 3. Cost Plan (Budgeting) 4. Resources (Work Centers) 5. Actuals / T&E 6. Progress / Completion

Accounting :

Budget Exceeded Even When There is Amount Available

WBS element budget exceeded even when there is amount available. Is there any percentage between the amount available and amount to be paid that the system determines before paying an invoice.  Where is this configuration made?

Check your budget profile in the IMG (trx. OPS9).

Select the F1 help function on the following fields:

1. "Total values" in the Timeframe block
2. "Annual values" in the Timeframe block
3. All five fields in the "Availability Control" block
Verify then if any conflict exist in the logic of your settings.

Secondly, go to your configuration settings in the IMG regarding the Tolerance limits for Availability control. 

Check your SPRO setting under Project System>Costs>Budget>Define Tolerance Limits. 

As per the setting in spro for budget tolerance limit, system gives you the message.   Here you set at what %age of releases budget, system will give you message and the type of message also like warning or error along with the area where you want to put this budget check. 

The column "Activity" stipulates the action to be taken by the system when you reach the percentage of expenditure as stipulated in the column "Usage".

Example:
Activity = 1 (Warning)
Usage = 95 (percentage)

In this example, the system will issue a warning when your total expenditure (actual costs) reach 95% of the budget amount. This is checked by the system, based on the settings in the budget profile as stated above.

 

CLOSING A PROJECT

Subject: CLOSING A PROJECT

I tried to close a project # 2600000089. I am getting an error message " There is still WIP for WBS 2600000089 ". 

The long text suggests that " Calculate the WIP for WBS 2600000089 so that it can be cleared. Then settle WBS 2600000089, including the cleared WIP in the settlement ". 

I am not clear with this information. What should I do for this ?? 

We went from 3.1H to 3.1I about 20 days back. In 3.1H I have never come across like this.. 

-----Reply Message----- 
Subject: RE: CLOSING A PROJECT

Typically this occurs for one of two reasons:
- You have costs on the WBS that need to be settled to a cost center or other WBS
- You have RA that still needs to be run and settled
This can get comlicated if you are not doing full settlement as you will have to open up the past periods to fix it. 

-----Reply Message----- 
Subject: RE: CLOSING A PROJECT

You cannot close the project if you have a WIP value in it. It's because: 

1. No invoice has been generated for that project. (fully invoiced status hasn't been reached). If you generate the invoice, the WIP value will be transferred to cost of sales. 

2. Invoice has been generated but the WIP value is not yet settled fully due to some provision as provided by the difference between your plan values and actual values. Have both values equal and run the RA and settlement again. Once WIP is zero, then change the status to CLOSED. 

Investment Management

Subject: Investment Management - Urgent! Urgent ! 

We wish to incorporate monthly spending plans in IM(Investment Management). Has anybody had any success in
implementing this in conjunction with having Annual and Overall Budget Management.

-----Reply Message-----
Subject: Re: Investment Management - Urgent! Urgent ! 

Have not tried using monthly plans in IM, but have used multiple plan versions in PS (all IM measures in my co. are linked to
projects). PS reporting allows selection of the plan version for comparison to budget. 
Most effective use is for cumulative monthly cost plans. Also suggest that you would want to use a unique identifier for monthly
plans vs. overall project plans in your naming/numbering conventions.

Settlement Rule For a WBS Element

What is meant by WBS element and in what scenario, PM orders settlement rule created with category as WBS?

Budget: Amount of resources allocated under a particular head in a financial year.

Budget Control: Having/ creating a control on the resources allocated in a financial year.

Original Budget: The initial budget that you have allocated to a WBS element.

Supplement of Budget: One time/ discrete increment in the original budget.

Return of Budget: Taking out the unutilized portion of the budget.

Transfer of Budget: Transferring the budget among two or more expense heads.

Project Definition: A framework for a business undertaking with a fixed goal to achieve with given resources.  The project definition contains dates and organizational information that are binding for the entire project.  WBS Element: Individual structural element in a work breakdown structure (WBS) representing the hierarchical organization of an R/3 project. Describes either a concrete task or a partial one that can be further subdivided.

Proposed Business Process : Assume there are seven expense heads in maintenance department. There may be addition of expense head in near future.  Based on the maintenance heads, maintenance department will create a project in project system. This project will be used for statistical purpose only & will not have any financial implication.  

Upon creation of a project, WBS elements will be created as per the expense heads. So for each expense head, there will be one top level WBS element. Again these WBS elements will be divided in twelve WBS elements. These twelve WBS elements represent twelve calendar months. Budget will be allocated to each WBS element & the WBS element will be released from the project.

Maintenance department will create maintenance orders as per their work requirements. These orders will be settled to cost centre, which is maintained in the settlement rule. Also WBS element will have to be mentioned in each order so that the budget control can take place. So as to capture cost from each maintenance order, the WBS element field will be made ?mandatory field? in maintenance order.

So when a maintenance order is released, system will do a budget check against the WBS element mentioned. If the budget check status is OK, order is released or else it will stopped from release. If the order is stopped from release, maintenance department will have to supplement the budget. Upon supplementing, the order is released again & the maintenance cost such as, labour, material costs can be booked on the order. Again the order cost is settled to cost centre & at the same time, budget is consumed from the respective WBS element.

Every year, maintenance department will copy the previous years project so as to save time & efforts to create project & WBS elements. And the maintenance department will assign the budget allocated to each WBS element in a financial year.  It is also possible to return the unutilised budget or, transfer of budget from one WBS element to another.

- Create a project CJ20N
- Create WBS element CJ20N
- Assign Budget to WBS elementsKO22
- Display assigned Budget KO23
- Supplement Budget KO24
- Display Supplement budget KO25
- Return Budget KO26
- Display Return budget KO27
- Transfer of budget CJ34

Settlement From WBS to AUC that was created from other WBS

How can make a settlement from a WBS to an AUC that was created from other WBS ?. The system send me a message AA 311 You cannot posted to the AUC ( Investment Support Measure ). The Help told me that I need flag a WBS like a Capital Investment Measure, I search in all fields of the structure but I dont found nothing.

Go to the WBS element Control data tab and enter the investment profile field. Then it will allow you to create an AUC.

What is the correct procedure for settling the WBS element costs to an AuC & then to as asset? For settlement to AUC settlement rule is not required.  Follow the steps:
 
1) For WBS element where the asset has to be created, AUC willbe created automatically when the WBS element is in release status to get this investment profile should be assigned to WBS element in Control Tab
2) You can see in the syatem status show as AUC to see the AUC number follow the path
    EDIT---> WBS element ----> Investment program----> Asset under Construction where you can see the AUc which is created automatically
3) Once the above two steps are throughfor settlement to AUC goto transaction CJ88 give the WBS element number select the processing type as partial captalization and execute all the costs pertaining to that WBS elements will be automatically settled to the AUC which is created for that WBS element

Project Objects

Subject: Project Objects

We have found that there are more than one WBS for an object. This is
supposed to be a unique relationship i.e. one to one. 
On doing an object find for a Project Characteristic you obtain the 
object numbers (that is WBS elements internal numbers) of the objects 
that contain the characteristics. Using T.code SE16 you can find the WBS 
element number of the object. On doing this search we have found 
multiple WBS elements for the same object number. On investigating the 
situation, we found that in most instances the "other" object another 
WBS element in the same structure or one created shortly after the 
correct WBS element.

We have not yet found out why this happens, what the solution is or if 
we have found all occurrences.

-----Reply Message-----
Subject: RE: Project Objects

In PRPS, there is 4 fields that refer to an SAP object:
POSID is the WBS element identifyer the user see on the screen
PSPNR is the internal SAP project item number (which IS unique)
OBJNR is the SAP object number (made out prefix 'PR' and the internal
project item number. It is also the number that is stored in the Costs tables.
PSPHI is the internal current number of the project the WBS element belongs
to.

All these numbers are absolutely unique. But all WBS elements in the same
project will share the same PSPHI, which indicates the project (from the
PROJ database).

The reason why you have an internal SAP number (PSPNR) and an external
number (POSID) is to allow the user to change the WBS element identifyer
without losing all the history.

Check to make sure you were looking at the right object number.

Various Cost Planning Methods in PS

I have come across various cost Planning methods like:

(1)    Easy Cost Planning

(2)    Unit Costing

(3)    Detailed Cost Planning

(4)    Network Costing

When do we go for each of these methods,  practically. 

In general implementation, which Cost Planning would be used?

Here is a very brief overview for you:
 
Easy Cost Planning(ECP) is really Unit Costing with a pretty face (MysapCom).  It is used in Transaction CJ20N (Project Builder) only.

You can set up 'Cost Models' in ECP using Characteristics which can be used to calculate values and automatically create Cost Plan Line Items - this is useful for companies who have pre-set planning methods (eg. Planning costs for building a bicycle, or a chemical test that requires known materials, labour, services and general costs.). It is a very flexible tool. 

An extention to ECP is Execution Services, which allows you to automatically generate Material Reservations, Purchase Requisitions and Activity Allocations. Its disadvantages (versus Networks) is that the planned costs are all aggregated to one WBS (unless you split your WBS's up to reflect the work you are doing - Labour, Materials, Equipment etc). 

Therefore, actual costs hit the WBS itself, not the line-item to which you planned. Disadvantages of ECP is that it does not distribute planned costs across time (no distribution rule). Also, there is no scheduling (start-finish, dependencies). Configuration for ECP is relatively straight forward. Costs for ECP can be planned against any Plan Version (default is Plan Version 0).
 
Networks allow you to plan costs via objects called Network Activities. They can be maintained not only in CJ20N, but also in CJ2D. They are a little more complex to use, but they allow you to have a networked structure. Each Network Activity can have planned costs for Work Centre/Activity Type, Stock/Non-stock Materials, Services and General Costs by Cost Element. Activities can have a list of Material Components. 

Networks will generate Material Reservations and/or Purchase Requisitions automatically. Configuration can be very complex. All costs for Networks are sent to Plan Version 0. Distribution of costs across time is supported.
Detailed Cost Planning is used when you simply want to plan your costs via Cost Elements. You can plan these costs against any Plan Version.
 
For a quick, easy planning method, ECP cannot be beaten as long as you don't want complex scheduling.
 
It is impossible to list all the feature/advantages/disadvantages to the planning methods in this.

Asset Value Date in Settlement

We are doing line item settlement in our system.  As the settlement is done at the WBS level, all the assets capitalized would have the same asset value date. Is it possible to have different asset value date for different line items? 

Yes, provided you do the settlement run on different dates. Also check the FI settings for settlement strategy.

SAP Standard defaults the following scenario:

An asset can only be capitalized when the asset is in use/productive. This means the deliverable/asset must be completed.

This is the same as the status TECO (technically complete). When you capitalize (settle to asset), then the system takes the date when the WBS status changed to TECO, and defaults this date as the asset value. All the line items in the WBS will therefore assume the TECO date of the WBS and that is why all the line items in the WBS have the same asset value date.

All the individual line items contributes together to one unique asset, and all have the same value date of the unique asset, which was derived, from the TECO date of the WBS.

This can be adjusted and changed in the FI-AA module, but make sure you understand the implications. The asset value date is used to derive the start date for depreciation, and depreciation is normally governed externally by a governmental institution, and your company must adhere to this external requirements. Consult with your company's auditor/financial executive to get the applicable rules and make sure your settings faals within this requirements.

Logistics :

PS Substitutions

We have configured Partner funcitons to used at PD and WBS element level. We want to enter the 'customer number' as partner at the PD level and then want to copy it automatically in all the WBS elements under the project. 

Is it possible to do such a thing? We are unable to use substitutions coz Partner fields do not occur in the substitution fields. 

 

This is reasonably easy to achieve with substitution exit, where you can retrieve data from any logically linked objects and use these as substitution source data. This is described in note 440186, chapter 4. 

However, with this technique you can only maintain the fields of PRPS,  e.g. user fields USR*. 

If your intention is to substitute corresponding Partner role in each level of WBS, I think that will not be possible with this technique directly. 

You should additionally check if there is a user exit at partner maintenance to complete the scenario. 

 

Normally you can use user exit RGGBS00 to insert a user specific into subsititution. 

But in your case, it's a little complex, because the partner is in another table (not in PRPS). however you can try to insert your own field into table GB01 and regenerate with program RGUGBR00 (note 42615). 

Progress Analysis to measure EVA

Q- I am currently working on a Chemical industry  Re-implementation.  My client wants to implement Progress Analysis to measure EVA.  They current use WBS elements (No Networks).  I have been trying to find an instance where progress analysis (EVA) has been implemented for WBS so I can decide what needs to be in place.   Anyone who has some imformation on these should please give me an insight or documentation.  This would be greatly appreciated. 

Tony

A-Unfortunately, from my experience, I can say that Progress analysis/ EVA Earned Value Analysis in PS cannot be done without the activities and of course withouth the networks. We had the same problem, as in our company as we had before only WBS and we needed EVA. For EVA PS has the Transaction CNE5 and in this kind of reports (see also CN41) values of rhe the field "actual work" will be "built up" on basis of activities confirmations. As I can suggest you, if the company does not want to change the current structure of the projects, a soulution would be to i! ntegrate PS with BW, if they have BW there, and to generate the needed reports for analysing the EVA in BW. 
Otherwise I have not heard to be possible to have Progress Analisys without activities in SAP Standard. 

Elena Manole

Thanks for the reply.  It is very helpful.  It confirms what I thought.

Tony

Progress analysis at WBS level is also possible., Use estimation method and put the ACTUAL WORK DONE.

Mukesh

I agree with Mr Mukesh. We are using the EVA method estimation and actual work done for WBS. 
Please create a new "Z" method of EVA which will allow confirmation of WBS in a similar way as being allowed for activities. You can then confirm the WBS for actual progress of work and enter the % completion of actual work to get schedule vs actual curve.

Salim Mohsin Shakir 

Using the Estimation method with WBS means you are not really doing EVM in SAP.  You would need to calculate the percentage using another tool.  Also, since your WBS schedule dates are not dynamic, the forecasts would be very difficult to create.  If the company is re-imiplementing, have them implement Networks Activities, at a minimum of one Activity per WBS.
 
Sequence Of Operations To Get EVA

In my project system I want project progress analysis on the basis of only time proportionality.  Cost will not be consider for progress andtheir are different units used like m, m3, km & hr for work in internal & external activities, so is it possible to do such setting on the basis of confirmation in customisation? 

Yes it is possible do through activity confirmation.  It all depends on EV basis, their you need to set time proportionality.

You need to perform sequence of operations to get EVA. for time prop. you need to maintain scheduling, activity confirmation etc.
 
Define default meas method as Time prop for objects in customising.
 
You need to do customization settings for EVA for progress version, statistical key figures, value catagories, progress cost element etc. 
 
You can go the following customizing steps... this will help you to configure as per your needs. This is not as per your need, as only you can understand what all the customizations you need to do........
 
1. Create Progress Version 101 with exclusive use 'Progress Analysis'. I have selected Plan & Actual check boxes. 
2. Settings for Progress Version- 
a) Plan version - '0' 
b) EV basis - Cost plan (active project, annual values) 
c) POC weighting - Cost plan (active project, annual values)
d) Planning type - Basic dates 
e) Early / Late - earliest possible 
f) Both reference boxes selected 

3. SKFs- I created three SKFs 10 (Non-Aggregated POC), 20 (Aggregated POC) and 30 (POC for RA) with unit of measure '%' and selected the Key value category 'Total values'. 

4. I need to assign these SKFs to different value categories. I created three value category 10, 20 & 30 with selection 'SKF with total values' and unit of measure '%'. Then I assigned SKF 10 to VC 10, SKF 20 to VC 20, SKF 30 to VC 30

5. I assigned measurement method as default value: 
a) WBS (Plan) - Cost Proportional 
b) WBS (Actual) - Cost Proportional 
c) Internal Activity (Plan) - Cost Proportional 
d) Internal Activity (Actual) - Degree of Processing 
c) Exernal activity(Plan) - Cost Proportional 
d) Exernal Activity (Actual) - Degree of Processing 

6. I made progress cost element '6511100' (Secondary cost element) with Cost element category as 61. 

7. I maintain a value catagory 6511100 with Cost radio button selected.
And assigned the progress cost element to the value catagory. i.e Cost element 6511100 to value catagory 6511100.

8. I maintain the assignment of cost element group. ie. I assigned progress cost elemnt to cost element group with default radio button selected. In the cost element group, I have selected certain cost elements which we regularly used (cost elements for project materials, project manhours, project contracts, spares etc)
 
Run CJEN first then CNE1 and CNE5

Milestones

Subject: Milestones

We don't use networks and activities.

The same time we want to use milestones only with WBS-elements for basic POC evaluation.

For instance for WBS we can attach several milestones with different POC, like 10%, 50%, 80%.

What is the tool in the system to confirm that particular milestone is reached? How can I change milestone status?

-----Reply Message-----
Subject: RE: Milestones

each milestone attached to a WBS element will have an actual date field open for entery when u release the WBS element. this will determine if the milestone has been achieved or not.

the %age entered in the milestone for POC will be considered in the progress analysis.

 

 

Project profile

-----Original Message-----
Subject: Project profile

We have decided not to allow creation of projects with certain project profiles.how can we prevent using the project
profiles.
If we delete the project profiles will it affect the existing projects or completed projects made of those profiles.

-----Reply Message-----
Subject: RE: Project profile

Hi there,

Have you ever used validations rules. That may work well in such a situation. You could use a rule like this : "If profile ID is
ABC then error message 333". If you heve not used these rules before tell us about that and we may help you.

-----Reply Message-----
Subject: RE: Project profile

You can delete the profiles but you may encounter problems creating new WBS elements in the old projects. The profile is
only used to provide defualts to these elements, so you will have to enter the values manually (e.g. Project Type).

The other probelm area that comes to mind are any reports that use the profile as part of dynamic selections.

Capacity Planning in PS module; Calendar like in MS Projects

With Pool Capacity we can generally define capacity for a group of expertise in a given Work Center. Meaning that if I have 10 peoples working at 40 hours a week each, my total capacity on a weekly basis is 400 hours.

 

If the demands from activities in my various projects using that Work Center exceeds the 400 hours then I'll be under capacity and Gantt's in Planning Board will show in red !!!!!

 

However if I decide to go for Individual Capacity planning using HR module; then from what I read the individuals already defined in HR as employee number; will be tied to the Work Center and automatically taken and represented in Gantt's chart individually.

 

The link is to tie them as employee number to the Work Center in HR.

My question is; likewise in MS Projects; where we can define availability via the calendar; we can grey out days when an individual is on vacation or not available.

 

And that will reflect in the overall availability...

 

In PS is there a way to get an ''equivalent'' calendar !!!!

 

I did not see anything in PS itself to lock individual's dates !!!!!

 

Would this be in HR ???

 

Mainly when I want to reserve vacation time ahead for indivial labour resources..!!!!

I am not an expert in this area but I know a bit about it (I made it in a customer, but at the end I had to undo it). Actually I cannot work with networks so all I have it is my memory.

The pool capacity works as you say, but it seems that you are using the capacity availabality feature. I understood that if you use that, the system only checks if there is capacity avalibale, but not makes a capacity "commitment", it means, other networks can plan that capacity as own (this is made in the "levelling" section). At last, I only used the first feature so only had a look on the second.

I do not know how to plan people from HR module but:
- In CMP9 you can assign people to networks in basis to its Work Center in individual days (but it is very boring for the user).
- In the activity tag "Personal Assignment" you can assign people to an activity. This uses the HR information (working start time, absences, substitutions...). But this is not a capacity check or plan (at the end, I used that information to make a customer-specific report).
- The function "HR_PERSON_READ_WORK_SCHEDULE" can be used to know the exact avilabilty of a person (it will show you working hours, if that day is holiday, if there is a planned absence or substitution... everything). But you need to report previously that data to the system. (if you use it, take a look to the HR_PERSON_INIT_WORK_SCHEDULE too).
- The working factory calendar of the activity it is used to plan the capacity ==> maybe you would need to make a calendar for each employee (too much work I think).

Note that in MS project when you "gray" days is for all the activities, to make that in PS you should make a factory calendar with those days as no working days. I have talking to "gray" those days for each activity.

Sorry if this is not very clear (it has taken me an hour with several interrupts).

 

I very much agree with Guillermo, and I would suggest to go for his ideea. In my opinion using personal capacity planing in PS-HR is very inflexible and deficitary.
 
However, the link PS-HR you are asking for,
 
1. In work center (Transsaction: change work center) you will have to assign the persons from HR, you will have to be carefull as in the transaction there are 2 methods/buttons to assign persons to a work center. now I cannot tell you by heart which one is effectively linking the HR with PS, as only one works, you will have to try both of them (swich to capacity view and you'll see one button sth. "Link to HR" and then the other option is in the menu bar)
 
2. In HR - you will have to work with your HR colleagues maybe, should be maintained some HR Infotypes: Transaction PA61,
Infotype 0007 - planned working time (e.g. 8 hr. a day)
Infotype 0005 - vacation
Infotype 2001, type pf Infotype 0100 - absences
 
For the infotype 0007 - you will have alreadythe Arbeitszeitplanregel "rule to plan the working time", if I translate correct from german, which will set the calender for you. This is made with another HR transaction for the HR calender ....this calender(e.g. factory calender) has to be then generated/activated for every month (separate transaction). I do not remember all the transactions codes now, but is pretty much intuitiv, as the system will give you the steps while maintaining the Infotypes.
 
3. Then you plan the persons in the Activities for a determined period of time. In CMP9 you'll see the availability with the standard working hours (8Hr/day, as set in HR in calender) and the absences (as planed in HR in infotypes) with empty cells (Nota Bene: these cells have in transactions CMP2 and CMP3 a change modus, are not grey or inactive !!!!!) You can change the planing then with the transactions CMP2 or CMP3, one is from project, the other from workcenter point of view . If you make changes in CMP2 or 3 you will not see the changes in Project builder for example. With CMP9 you can only view the personals planing for a workcenter, a project...
 
I remember there is another transaction to see the personal availability somewhere in the Infosystem> PS>capacity. You'll have to look for it and generate it from Mandant 000.
 
Unfortunately, there are some more constraints, which you will discover while testing.
 
Project Status set to TECO

When I set a project on status TECO.  We can still do confirmations on the project.

Is there a setting or a way in which we can set the project to TECO and not be able to do confirmations on that particular project?

There is no link between TECO and actual confirmation. It might possible that the project is technically completed but non technical activities are still pending..

All WBS elements, networks and activities are set on status TECO in the project. I have set the status over a week ago and yet am still allowed to do confirmations to the activities in the project.

We did not experience this problem before.  It is the first time and it happens for all projects that are set to status TECO.

If you have networks and activities involved your best bet is to use project builder to make a status change at the project definition level which will cascade down to wbs elements, network header and network operations.

You may try setting a DLFG flag and see if it prevents confirmations from occurring on the activities. If you need to undo the deletion flag the sequence is as follows:

Using CJ02 undo DLFG at project definition level then select all wbs elements and perform the same. using CN22 undo DLFG at network header level then select all activities and perform the same.

Project builder allows status set downwards but not undo on all components, therefore requiring CJ02 and CN22 to undo.

List of RA caculated values

In the part of "Result Analysis data" in the result screen after RA operation, there is a field named L(r). 

List of RA caculated values:

R(p) = Planned revenue for valuation
 
C(p) = Planned costs for valuation
 
M(p) = Planned costs for complaints and commissions for valuation
 
S(p) = Planned special costs (cost of sales = actual costs) for valuation
 
L(real) = Realized loss
 
N(p) = Planned values not taken into account
 
R(a) = Actual revenue
 
C(a) = Actual costs
 
M(a) = Actual cost of complaints and commissions
 
S(a) = Actual special costs (cost of sales = actual costs)
 
N(a) = Actual values not taken into account
 
D(a) = Down payt
 
C(c) = Calculated costs
 
R(c) = Calculated revenue
 
C(av) = Valuated actual costs
 
M(av) = Valuated cost of complaints/commissions
 
POC = Percentage of completion
 
C(r) = Reserves for unrealized costs
 
R(r) = Revenue surplus
 
C(z) = Work in process (capitalized costs)
 
R(z) = Revenue in excess of billings
 
M(r) = Reserves for cost of complaints and commissions
 
COS = Cost of sales
 
R(n) = Revenue aff. net income
 
Project System Status -Deletion Flag Active

One problem with the network triggered by a SO with CN08 linkage.  The network appears in display mode with system status -deletion flag active.   How to change the system status and delete the network?

Here is the deletion flag behavior I have observed. 

We are using assembly order processing and also use CN08.

Using CN22 or CJ20N to create DLFG you set the status on the network header Edit>status>deletion flag this rolls the status down to the activity level.

To reverse the deltion flag you must first:

cancel the deletion flag on the network header, then select all activities in the activity overview and cancel deletion flag.

Now some people believe that when the deletion flag is set that it removes all of the activities from the network.

This is false, users who do not see the activities after the deletion flag is set must use the following menu path to "reveal" the activties:

Edit> Object> Display Deleted>On

Which table is the system storing the  Project Def, WBS, NW and NWA system and User status?

Check these tables:

PROJ : Master data for project definition
PRPS: Master data for WBS
PRHI: Master data for project Jerarquie

TJ02 - a list of all System Status'. You can use transaction BS23 to see these, or SE16n via normal enquiry
JEST - current System/ User Status by object number (WBS and Network)
JCDS - history of System/ User Status by object number (WBS and Network)
   
Needless to say, you have to get the object number first by looking at PROJ, PRPS for Projects and AUFK, AFKO, AFVC, AFVU or AFVV for Networks.
   
Use SE16n to see the contents.

PS:  Status "code" contained in JEST for particular object number, after selecting object number of choice from JEST to obtain status text simply join JEST to TJ02T linking JEST-STAT to TJ02T-ISTAT and finally pick language TJ02T-SPRAS .

Stop Commitments Before Release Of Projects

We are creating projects via Appropriation requests. The theory is that no commitments should be created before the project is released. However, we have proven that users can change the Res./Purc. indicator to 'immediate' before the project has been released. If the approver does not pick up that the project is not released yet, they can even create a Purchase order. 

You can not remove authorisation for the "immediate" indicator, because the indicator changes when you release the project from "from release" to "immediate".

    

How can we stop ANY committments from being created until the project has been released?

In OPSC make sure the Release immediately has been unmarked.
 
In transac OPUA (field selection network header) go to influencing choose network profile or controlling area depending on which you want to customize. Set the field "Reservation/Purc.req" CAUFVD-AUDISP make it to only displauy.
 
Go to transac OPUC (field selection network details) go to influencing, choose network profile or contolling area to which you want to customize the setting. Set it to change and in the field "Reservation/Purc.req" - AFVGD-AUDISP make it to only display. 
 
This would prevent the users from changing it to display when they create and assign activities to networks/projects. 

One more customization, in transac OPUU in the network tab make sure the setting is for 2 (from release)

or

A very effective way to handle this is using User status management .go to tcode bs02 and define a status profile which can be defaulted in the project profile, in the status profile define proj definition,WBS,network header and network activity as the infulenced object types.

Create a status "blck" as an initital status and in the business transaction field block PR and PRQ creation.
Next create a status"allw" which will be set after project is released and allow PR and PRQ creation after status is set

What is WBS element?

 1) What is WBS element?

 2) What is the Tcode to get to that screen?

 3) What is the need and pupose of WBS element?

 4) Do we happen to work on Functional module during our implementaion project?

 5) In what scenario/situation we will be working on WBS?

WBS is nothing but Work Breakdown Structure. It is mainly used in Project System (PS) module. Tcode : CJ20N

For any project defined we must have atleast one WBS. Within this WBS we can have networks. Networks are nothing but the series of activities. Material are used to perform the activities.

To explain in detail just consider one example:

Govt of india wants to have Roads to be build through out the india. So Project can be defined in sap as "Connectivity".

WBS can be roads within different states like Roads for Gujarat, Karnataka etc.. i.e. WBS Gujarat, WBS Karnataka etc.

We can define different networks for these WBS  like Road Between Ahmedabad to Surat or Between Bangalore to Belgham.

For this network we can have many activities like Land selection, Land Preparation, Road Building, Final finishing etc etc.
 

Hemal's example was a good example. Project Systems comes into play only when the industry's business is based on projects like... Construction companies, Engineer to Order scenarios. You may not see anyone using PS module for retail business. As Hemal explained in that example, you have a main project which is broken down into WBS elements. You can use the TC CJ20N to create the project and the WBS elements. Each WBS may have mutiple Networks associated and each Network may have multiple Network Activities as explained in the example by Hemal.
   
On the Sales Order, if your client is implementing PS module, you may have to attach the Sales Order to the WBS element it belongs to. WBS element is nothing but a bucket where all the activities belonging to that particular part of the project are captured. In the example, WBS Gujurat will tell you how many Sales Orders were created for the Gujurat sector, howmuch was spent on raw materials, what's the currect stock ([roject stock) available. How many Production Orders have been confirmed and howmany of them are getting confrmed in the future. How many invoices have been generated or how much revenue has been generated for that particular sector. How many deliveries have been made, what deliverables are still not accomplished. 
   
So as you can see, PS is the center stage for all the modules that are being implemented like FI/CO, SD, MM, PP in this example. You can have cost centers and work centers defined. You can also have profit centers assigned at the plant level and get reports on varius selection criteria. 
   
In a complete cycle of PS, like in reality, you initiate a project, you confirm/release the WBS/activities as per requirement, you execute the project and you close it. 
   
One cannot initiate an activity unless it has been released by the project manager. Everything is accountable here and every dime is counted and at the end you know howmuch did you spend or make on each sector (WBS). Dont get confused with the term sector here... I am using it just for the explaination purposes. :)
   
In one typical example, the company I was working with until not too long ago, had Deliveries from the Project (TC: CNS0). We never used VL01N. We used CNS0 to create a delivery and then used VL02N for confirming the picking quantity for the already created delivery document.
   
I hope this should help you at least a bit. I'm not a PS consultant so I may not know a whole lot but trying going to CJ20N and you will see a lot yourself. 
   
PS concultants are one of the highest paid consultants. Their supply is less and so is the demand. They are expected to understand real world business processes very well and they are generally the center stage of a project.

Aggregate POC Calculation

When we confirm activities and see it in cns41 report we can see that the POC is aggregated at the Network,WBS and porject level.  How does the system calculate this.. i.e on what factors and criteria?

Result analysis determines the costs & revenues belong to the period, along with the Work in progress (WIP) or Reserves.

Result analysis calculation is based on the planned / actual Cost & Revenue. 

POC (Percentage of Completion) determines by the valuation method you opt …

The formula for POC :

  POC = R (a) / R (P) Revenue Proportionate

  POC = C (a) / C (p) Cost Proportionate 

Result Analysis Determines:

- Calculated Costs C(c) = POC X C (p) Same for Revenue 
- WIP (If C(a) >C (c) ) WIP = C(z)= C(a) - C(p)
- Reserves for unrealized costs (if C(a) < C(c) )
   C( r ) = C (c ) – C(a) 
- Revenue Surplus (if R (a) > R(c) ) 
   R (r) = R(a) –R(c) 

E.g.

Revenue Proportionate RA: 

In some project you have R(p) =3000$
  C (p) = 2000$
  R (a) = 1200$
  C (a) = 1000$

Then POC = 1200 /3000 = 40 %

C(c) = POC X C(p) = 40 % X 2000 = 800$

WIP = C(z) = C(a) –C(c) = 1000-800 =200$

Dynamic Selection on Report Not Working

I have several reports on which the dynamic selection is not working. For instance, the report CN43N. The report is outputting all data in a year i.e it is disregarding the condition I specified in the dynamic selection fields.

Is there some configuration to make to this report so that the dynamic selection works?

Include field are only possible for fields are realte to PS table:

 1. Execute Transaction SE36. 

 2. Logical Database Builder: PSJ

 3. Choose "Extras -> Selection views".

 4. Copy selection view "SAP" to "CUS".

 5. Change view "CUS".

 6. Go to "Tables", select the correct table, for example table ACT01 for object type "Activity".
 Here, you must ensure that this table is also listed under "Extras -> Dynamic selections" - only these tables can be used.

 7. Double-click on the table name.

 8. In the "Fields of the table", select the fields desired and allocate them to one of the "Functional groups".

 9. Save.               http://www.sap-img.com/sap-ps.htm

The Project System has no organizational structures of its own; you incorporate it into the existing structure by making assignments to the organizational units in Accounting and Logistics. It is this which enables the Project System to present data clearly and in many different ways.

 

 

 

 

Q ; My company is contemplating the implementation of SAP Project Systems (PS)this year. But having already implemented CO (internal orders) and IM, which covers some aspects of the life cycle of capital projects, to what extent will there exists duplicity in the SAP system, and what aspects of the installed modules will be subject to change/modifications to accommodate PS? Also, what kind of implementation time can we expect?

Answer : SAP PS is designed to work well with both CO and IM. The PS module will allow better management of your projects. Allow adequate time in your project to review your requirements and understand the impact this new module will have on your existing setup. Also include time for testing and training so that you can ensure the new features work properly and your clients understand how to achieve the benefits.

What parameter is used to extend the maximum number of GUI sessions in a 4.6C environment?

RESPONSE

The parameter is "rdisp/max_alt_modes" and its default value is 6 sessions. The minimum is 2 and the maximum is 16. Use transaction RZ11 to get additional information about the parameters and use RZ10 to implement the parameters. also, you might want to look into these other parameters:

login/multi_login_users

login/disable_multi_gui_login

 

 

Transactions For PS Module

What are those standard project system tcodes?
No Transaction Code Description

1.   CJ20n                 Creation of Project
2.   CJ20n                 Creation of WBS Elements
3.   CJ20n                 Creation of Activities
4.   CJ20n                  Assigning relationships to activities
5.   CJ20n                  Assigning of milestones to activities/WBS Elements
6.   CJ20n                  Assigning of materials of activities
7.   CJ40                    Planning of costs to project
8.   IMCCP3              Copy Planned cost to budget
9.   CJBV                   Availability Control of budget
10. CJ30                    Assigning Budget to Project
11. CJ20n                   Release of Project/WBS Elements/activities
12. CN25                   Confirmation of activities
13. CJ20n                   Maintain actual dates to milestones of WBS Elements/activities
14. CJ37                     Supplement in project
15. CJ38                     Return in project
16. KB21n                  Direct Activity Allocation
17. CNL1                   Create Delivery Information
18. CNL2                   Change Delivery Information
19. CNS0                   Delivery from project
20. CNL3                   Display Delivery Information
21. CJ2c/CJ20N         Display Project
22. CJ41                     Display cost planning
23. CJ31                     Display Budget
24. CN28                    Display Confirmations
25. CJ3B                     Display Document (BUDGET)
26. CN29                    Cancel/Reverse of Confirmations
27. CN41                    Structure Overview
28. CN42N                 Overview of  Project Definition
29. CN43N                 Overview of WBS Elements
30. CN46N                 Overview of Networks
31. CN47N                 Overview of Activities
32. CN55N                 Overview of Sales Document items
33. CN53N                 Overview of Milestones
34. CN52N                 Components Overview
35. CN42                    Enhanced Overview of Project definition
36. CN43                    Enhanced Overview of WBS Elements
37. CN44                    Enhanced Overview of Planned Orders
38. CN45                    Enhanced Overview of Orders
39. CN46                    Enhanced Overview  of Networks
40. CN47                    Enhanced Overview of Activities
41. CN48                    Enhanced Overview of Confirmations
42. CN52                    Enhanced Overview of Components
43. CN53                    Enhanced Overview of Milestones
44. CNS54                  Enhanced  Overview of  Sales and Distribution Documents
45. CNS55                  Enhanced Overview of Sales Document items
46. ME5J                     Purchase requisitions for Project
47. ME2J                     Purchase Orders for Project
48. CNMM                  Project Oriented Procurement
49. CN60                     Display change documents
50. S_ALR_87013542 Actual/Commitment/Total/Plan in Control Area Currency
51. S_ALR_87013557 Budget/Actual/Variance
52. S_ALR_87013560 Budget Updates
53. S_ALR_87013532 Plan/Actual/Variance
54. S_ALR_87013533 Plan/Actual/Commitment/Rem.Plan/Assigned
55. S_ALR_87013534 Plan1/Plan2/Act/Commitment

Validation in PS - WBS

I want to validate the customer number in one of the user fields in WBS.   The formula builder in the validation screen, it seems, does not support table fields other than fields from PRPS.   Can this be done thru some user exits ?? If yes how ?? Can you guide me in this ??

Answer :

To use a user exit in validations, you have to perform following steps;

- copy SAP standard program GGBS002 to ZGGBS002
- create a user exit in this program (such as U902, U903 etc)
- the user exit you defined in the above mentioned program will be visible in validations on screen tab 'Exits'
- configure your validation with 'User exit' as option

 

How To Create a Multilevel BOM

How To Create a Multilevel BOM and How Does It Work

 
 

{mosbanner:id=23}

Multi level bom is a Bom which it has different components at different level..for example:
- A ( finished material)
- B ( semi finished)
- C ( Raw material)

When you run the MRP, Bom will explode upto last level and it will plan the requirement of each individual material.

What ever may be the kind of BOM to be created transaction codes are as below:
 
- CS01 : BOM create
- CS02: BOM Change
- CS03: BOM display
 
Pre requisites are material master record for the materials.

What you have to keep in mind is:
 
1. BOM creation is through CS01 only.
2. When you have to create multilevel BOM, you have to carry craetion of BOM level by level.
3. First create BOM for assemblies (means materials which are produced inhouse, means materials with procurement type "E" in the material master MRP 2 view).
4. Finally create BOM for the finished product using these assemblies as components.
5. When you see the BOM of finished part after creation through CS03, you can find these assemblies with a tick mark in the field "Assembly".  When you double click you can see the susequent BOM of these  assemblies.
6. Example would be for a vehicle suppose engine, front wheel, back wheel are the "E"parts.  Create BOM first for these engine, front wheel and backwheel with respective material components.
Then create BOM for vehicle with these three "E".
When you see the BOM of vehicle after creation, you can see a tick mark against these E parts which shows that they have BOM furtehr down and you can double click and see the components of these

Validation in PS

am trying to use validation in the Project.   Can any one tell when are the call up points 110 and 120 trigerred ?

I want to validate one of the user defined fields in WBS.

Everything is working fine when I simulate the validation. But when I enter a value in the user defined field and save the project then I do not get the error message as expected.

Does anybody have an idea what could be wrong ??

Answer :

Please see if you have checked the check box for Automatic validation in the relevant project profile.

 

WBS Elements

1. What is WBS element?
   
2. What is the Tcode to get to that screen?
   
3. What is the need and pupose of WBS element?
   
4. Do we happen to work on Functional module during our implementaion project?
   
5. In what scenario/situation we will be working on WBS?
   

WBS is nothing but Work Breakdown Structure. It is mainly used in Project System (PS) module. Tcode : CJ20N

For any project defined we must have atleast one WBS. Within this WBS we can have networks. Networks are nothing but the series of activities. Material are used to perform the activities.

To explain in detail just consider one example:

Govt of india wants to have Roads to be build through out the india. So Project can be defined in sap as "Connectivity".

WBS can be roads within different states like Roads for Gujarat, Karnataka etc.. i.e. WBS Gujarat, WBS Karnataka etc.

We can define different networks for these WBS like Road Between Ahmedabad to Surat or Between Bangalore to Belgham.

For this network we can have many activities like Land selection, Land Preparation, Road Building, Final finishing etc etc.

Hemal's example was a good example. Project Systems comes into play only when the industry's business is based on projects like... Construction companies, Engineer to Order scenarios. You may not see anyone using PS module for retail business. As Hemal explained in that example, you have a main project which is broken down into WBS elements. You can use the TC CJ20N to create the project and the WBS elements. Each WBS may have mutiple Networks associated and each Network may have multiple Network Activities as explained in the example by Hemal.

On the Sales Order, if your client is implementing PS module, you may have to attach the Sales Order to the WBS element it belongs to. WBS element is nothing but a bucket where all the activities belonging to that particular part of the project are captured. In the example, WBS Gujurat will tell you how many Sales Orders were created for the Gujurat sector, howmuch was spent on raw materials, what's the currect stock ([roject stock) available. How many Production Orders have been confirmed and howmany of them are getting confrmed in the future. How many invoices have been generated or how much revenue has been generated for that particular sector. How many deliveries have been made, what deliverables are still not accomplished.

So as you can see, PS is the center stage for all the modules that are being implemented like FI/CO, SD, MM, PP in this example. You can have cost centers and work centers defined. You can also have profit centers assigned at the plant level and get reports on varius selection criteria.

In a complete cycle of PS, like in reality, you initiate a project, you confirm/release the WBS/activities as per requirement, you execute the project and you close it.

One cannot initiate an activity unless it has been released by the project manager. Everything is accountable here and every dime is counted and at the end you know howmuch did you spend or make on each sector (WBS). Dont get confused with the term sector here... I am using it just for the explaination purposes. :)

In one typical example, the company I was working with until not too long ago, had Deliveries from the Project (TC: CNS0). We never used VL01N. We used CNS0 to create a delivery and then used VL02N for confirming the picking quantity for the already created delivery document.

I hope this should help you at least a bit. I'm not a PS consultant so I may not know a whole lot but trying going to CJ20N and you will see a lot yourself.

PS concultants are one of the highest paid consultants. Their supply is less and so is the demand. They are expected to understand real world business processes very well and they are generally the center stage of a project.

1) What is WBS element?
2) What is the Tcode to get to that screen?
3) What is the need and pupose of WBS element?
4) Do we happen to work on Functional module during our implementaion project?
5) In what scenario/situation we will be working on WBS?

WBS is nothing but Work Breakdown Structure. It is mainly used in Project System (PS) module. Tcode : CJ20N

For any project defined we must have atleast one WBS. Within this WBS we can have networks. Networks are nothing but the series of activities. Material are used to perform the activities.

To explain in detail just consider one example:

Govt of india wants to have Roads to be build through out the india. So Project can be defined in sap as "Connectivity".

WBS can be roads within different states like Roads for Gujarat, Karnataka etc.. i.e. WBS Gujarat, WBS Karnataka etc.

We can define different networks for these WBS like Road Between Ahmedabad to Surat or Between Bangalore to Belgham.

For this network we can have many activities like Land selection, Land Preparation, Road Building, Final finishing etc etc.

Hemal's example was a good example. Project Systems comes into play only when the industry's business is based on projects like... Construction companies, Engineer to Order scenarios. You may not see anyone using PS module for retail business. As Hemal explained in that example, you have a main project which is broken down into WBS elements. You can use the TC CJ20N to create the project and the WBS elements. Each WBS may have mutiple Networks associated and each Network may have multiple Network Activities as explained in the example by Hemal.

On the Sales Order, if your client is implementing PS module, you may have to attach the Sales Order to the WBS element it belongs to. WBS element is nothing but a bucket where all the activities belonging to that particular part of the project are captured. In the example, WBS Gujurat will tell you how many Sales Orders were created for the Gujurat sector, howmuch was spent on raw materials, what's the currect stock ([roject stock) available. How many Production Orders have been confirmed and howmany of them are getting confrmed in the future. How many invoices have been generated or how much revenue has been generated for that particular sector. How many deliveries have been made, what deliverables are still not accomplished.

So as you can see, PS is the center stage for all the modules that are being implemented like FI/CO, SD, MM, PP in this example. You can have cost centers and work centers defined. You can also have profit centers assigned at the plant level and get reports on varius selection criteria.

In a complete cycle of PS, like in reality, you initiate a project, you confirm/release the WBS/activities as per requirement, you execute the project and you close it.

One cannot initiate an activity unless it has been released by the project manager. Everything is accountable here and every dime is counted and at the end you know howmuch did you spend or make on each sector (WBS). Dont get confused with the term sector here... I am using it just for the explaination purposes. :)

In one typical example, the company I was working with until not too long ago, had Deliveries from the Project (TC: CNS0). We never used VL01N. We used CNS0 to create a delivery and then used VL02N for confirming the picking quantity for the already created delivery document.

Hierarchical Structure of the Project definition

A few Definitions of the terminologies used in the above diagram:

Project:

The project definition is the binding framework for all organizational elements within a project.

Work Break down Structure:

With a work breakdown structure you can divide the project into useful steps, specify fixed or
"basic" dates, specify the work involved, and determine project costs. The individual levels of
the hierarchy in a work breakdown structure enable you to  organize a project into steps.

Work Break down Structure Element (Sub WBS):

You can further break down these steps into individual elements. Maximum steps supported
are 99.

Network:

It is a special type work order on which cost can be planned, controlled and monitored.

Activities:

These are the actual tasks that are to be executed for the completion of the project

The SAP PS consultant is responsible for the analysis, design, configuration & support of the SAP PS area to meet the business needs of company. Knowledge and min. End-to-End Implementations and at least two Support Projects ,· 2 years Project Management or work scheduling experience. Working closely with our customers to deliver, maintain and troubleshoot and enhance SAP functionality and through knowledge of the FI module and knowledge of its integration with other modules.

 

SAP R/3 is based on a three tier client/server technology. Typically, it is made up of three functionally distinct layers namely: the user interface, business logic and database.
The user interface, which is otherwise known as the presentation server displays the interface for users' communication with the SAP system. It is often referred to as the SAP GUI. As a matter of fact, it is a program called sapgui.exe. The application server is where the business logic and data manipulation takes place. Data processing, SAP administration tasks and client request/feedback management are handled within the business layer. The database layer is synonymous to the database server and it typically acts as a data repository for tables and other database objects and structures

Ideally, an R/3 system is composed of one database server, one or more application servers and one or more presentation servers. SAP Business One on the other hand is composed of a database server and one or more presentation servers.

the difference between SAP Business One and SAP R/3. The non technical answer to this question is that; SAP Business One is SAP's offering for small and mid size companies, while R/3 is SAP's offering for large companies.

Procedure: What to Do in Case of Power Failure in SAP Project.

The procedure to be followed in case of a power failure in the power sources of either the productive or backup server.

1. Check the UPS Make sure the UPS is functioning properly, and check the remaining time. You should have approximately XX minutes to shut down the system.
   
2. Log onto SAP and check for users and processes If any users are still on SAP, send a system message for them to log off immediately. Check for background processes, interrupted user processes, and other processes that may need attention before shutting down, and record them in the Power Failure Log.
   
3. Stop SAP and Shut Down the Database Refer to Starting/Stopping the Database and SAP for detailed instructions on shutting down SAP and the database.
   
4. Shut down the Server Refer to Powering On/Off the Server and the UPS for detailed instructions on powering off the server
   
5. Power Off the UPS Refer to Powering On/Off the Server and the UPS for detailed instructions on powering off the server
   

cProjects ( Capital Projects ) :

cProjects (Collaboration Projects) is the SAP web-based application built on the Web Application Server (WAS). cProjects is a component of the cProjects Suite. cFolders is another component of cProject Suite.

cProjects was designed for organizations that need to manage multi-phase projects with high quality control can benefit from cProjects. cProjects supports flexible project management and team collaboration.

cProjects provides project structuring capabilities (project definition, phases, checklists and tasks), roles-based resource management, flexible authorization control and scheduling functionalities, in conjunction with broad project management and monitoring features.

cProjects requires WAS 6.2 and cProjects Suite prior to deploying cProjects.

SAP Project System - A ready Reference ( Part 1 )

 https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9622

Being a beginner in SAP PS is a challenge. As a techie, When I started my ABAP Program in PS Module, I found a lot of scattered information but there is no article or blog with consolidated information even on basic terminologies of SAP PS. This blog is my attempt to provide an insight of basic techno-functional aspects and terminologies of SAP PS to a novice. 

In my first blog you will find the important terms of the PS module. I have tried to explain them with the help of an example. Following this is the next blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9659 where the technicalities of the same are covered.

The Project System (PS) module of SAP is specifically designed to provide comprehensive and fully integrated project management functionality for SAP customers. A Project is a complex undertaking, bringing with it huge data of different type.

At the beginning of each project, whether it involves developing a new product, make-to-order engineering or internal organization, you need to define and set up the structures necessary to manage your project and incorporate them into your existing organizations and processes. Before you can run a project in its entirety, you must first describe the project goals precisely and create a structure for the project activities to be carried out. A clear project structure provides a basis for successful project planning, monitoring and control.

Organizational Structures in Project System:

"

 You create and manage your project structure in SAP R/3 Project System, by means of work breakdown structures and networks.The WBS describes individual phases and functions of a project. Network contains the individual project tasks and the dependencies between them in the form of activities and relationships 

Some important terms:

 
 

Project Definition

Project Definition is general description of the project that you want to manage. It is a framework laid down for all the objects created within a project. It contains organizational data that is binding for the entire project. 

Work Breakdown Structure (WBS)

WBS is a hierarchical model of the tasks to be performed in the project. It provides overview of the project and forms basis for the project organization and coordination.It shows work, time and money spent on the project. You can use it to plan dates & costs and allocate budget. The Work Breakdown Structure can be displayed according to:

• Phase
  
• Function
  
• Object
  

  Individual tasks required to carry out the project is called WBS elements.
  

  
  

  Network
  

  The network describes project processing. Thus the Network contains instructions on how to carry out activities in a specific way, in a specific order and in a specific time period.Main elements of network are activities and relationships. It forms the basis for planning, analyzing and monitoring time schedules, costs, & resources.
  

  
  

  Activities
  

  Activities are used to plan project staffing, capacity, material, PRTs, and service requirements. When activities are assigned to WBS elements, detailed view of costs, dates, and capacities at WBS element could be obtained. It's a task in a network which has a defined start and finish. An activity can be broken down into activity elements.Three categories of activities in the Project System:·        
  

• Internal Activities        
  
• External Activities        
  
• General Cost Activities 
  

  Activity element
  

  Activity element is an activity which is subordinate to another activity. Activity elements contain the same information as activities.Three categories of activity elements in the Project System:
  

• Work elements
  
• External Elements
  
• General Cost Elements 
  

  Activity Type
  

  It's a physical measure of activity output of a cost center .e.g. hours, number of units produced, machine times, production times. 
  

  Milestones
  

  Milestones are the events in the project to which particular importance is attached Or which trigger predefined functions. In general they indicate transition between different departments or phases. Milestones are assigned to activities and WBS elements:In PS milestones are used to:
  

• Trigger predefined functions in network activities.
  
• Carry out earned value analysis.
  
• Determine dates in billing plan for sales orders. 
  

  Relationships
  

  You use relationships to depict chronological and technical dependencies between activities. The relationship determines the nature of the link between the individual activities. :
  

• FS Relationship : An activity does not start until the preceding activity is completed.
  
• SS Relationship  : An activity can not start unless another activity has started.
  
• FF Relationship  : An activity can not be completed until another activity has been completed.
  
• SF Relationship : An activity can not be completed until another succeeding activity has stared. 
  

  Confirmations
  

  It is a part of network control. It documents the state of processing for the network activities and activity elements. There are two types of confirmations Partial & Final.Confirmations are used to record:
  

• The work center where the activity was carried out.
  
• The person who carried out this activity.
  
• The yield and scrap produced in an activity.
  
• The actual values for the duration and dates. 
  

  
   

  
   

  Settlement
  

  As a rule, projects are used to collect and monitor costs, but are not usually the final cost object. For this reason the costs in atypical project will be settled at the end of the period.To this end, you store settlement rules in the activity / WBS element requiring settlement. They contain information on settlement receivers, cost apportionment and control data. Settlement receivers could be cost centers, G/L accounts. Etc.
  

  Budget
  

  The budget is the approved cost structure for an action or project in a particular period.Budgeting differs from cost plan in that it is binding. In the approval phase you prescribe your project funds in the form of budget. It is possible to allocate overall and annual budget in parallel.
  

  Work Centers
  

  Work center represents the resources responsible for executing an activity. In a work center, you can enter the available capacity and an operating time. You can arrange the work centers in a hierarchy for capacity evaluation purposes.  Internal activities are assigned to work centers (resources) to be completed.A work center is a physical unit within a company where an activity is performed.
  

  Profit Center
  

  It is subdivision of business organization which is set up for internal management control purposes. Profit centers divide business up on a management basis. The basic aim of profit center accounting is to present areas of the business as entities operating independently in the market.   
  

  Lots of jargons ….let me site an instance of the construction project  of a building.. 
  

  Let say there is a construction company that is going to construct a Multi-Storey building. 
  

  The first thing that needs to be created in the system is Project Definition. The entire activity plan for this project will come under this project definition. Overall budget
  needs to be estimated, assigned and get approved for the project. Project timeline needs to be decided.  Project could be then subdivided into separate parts which are actually WBS elements lets say in this e.g. we have 4 main WBS elements:
  

1. Land Acquisition
   
2. Procurement                    
   
3. Construction
   
4. General
   

To every above WBS, budget and time line need to estimated. 

Now to take an example we will drill down two WBS elements namely Land Acquisition and Construction.

- Land Acquisition could be sub divided into activities as in 

• Generation of request document for the land.
  
• Soil testing
  
• Approval for construction
  
• Preparation of purchase order of the land
  

  Above 4 activities should be done in sequence. As in second activity will start only after request document for the land is completed and so on. Hence these activities have FS Relationship between them. 
  

  - Now take WBS element Construction.
  

  It could be sub divided in to floor wise tasks. Let say, we have four story building and each floor has 4 flats. So under WBS element 'Construction' we may create separate sub WBS element for each floor. Each sub WBS element of floor may be divided further into last level of WBS elements one for each flat on the floor. This way we will have hierarchy of the WBS elements.Finally last level of WBS elements i.e. WBS elements of the flats will have activities like
  

1. Plumbing
   
2. Electrical work
   
3. Flooring
   
4. Painting
   
5. Furniture
   

These activities form the Network.

Let say Plumbing and Electricity work are the external activities as they are given to a outside contractor. While the other activities are done by company labor so they are internal activities. Plumbing and Electrical work could be started simultaneously.While flooring needs be done once the plumbing and Electrical work is complete. Hence they have FS relationship and so on…. Now if we talk about milestones:

1. First milestone could be purchasing the land
   
2. Second could construct the base of the building.
   
3. Third could be construct the floors
   
4. Fourth could be completion of plumbing and electrical work for all the flats. And so on….
   

As I have said that Work center represents the resources responsible for executing an activity For the above activities, work centers could be the company labor required for the construction, labor provided by the external service center for plumbing and Electricity work. while Profit Centers could be the finally constructed flats. 

 

 

 

 

Sr NO	Project Elements	Examples
1	Project Def	Constructing the Buiding
2	WBS	Generation of request document for the land Soil testing Approval for construction          Preparation of purchase order of the land
3	Activities (Under  3rd WBS)	Plumbing( external Activities) Electricity work( external Activities) Flooring (internal activities) Painting (internal activities) Furniture
4	Relationship	Flooring needs be done after the plumbing and Electricity work. Hence they have FS relationship
5	Milestones	First milestone could be purchasing the land Second could construct the base of the building.T hird could be construct the floors Fourth could be completion of plumbing and electricity work for all the flats
6	Network	Plumbing and Electricity installation are to be one contractor each. Therefore, there exist a network within on the activities of it under different WBSs.

Referencee : The book : Functions in Detail : R/3 System - Project   Management in Engineering & Construction )

• hi sheetal i am working on a report in PS and need to pull the last posting date with amount spend on the project.... where can i those.
  
  This is a very useful blog for all the techis...Very simple language and a lot of useful content...
  Keep it up.
  

  Both the parts are very much descriptive and can be used as reference for techies.
  Starting point for beginners.
  PS module generally remains behind in implementations for various reasons.
  This would motivate ps-related persons in
  understanding basics & methodology of how
  SAP makes it easier in doing so.
  keep up
  

• PS module generally remains behind in implementations for various reasons.
  This would motivate ps-related persons in
  understanding basics & methodology of how
  SAP makes it easier in doing so.
  
• A good one . Will really help beginners to understand the concepts of SAP PS.
  
• Appreciate ur efforts put in, towards making
  PS-Module,simplified,informative & presentable
  covering conceptual knowledge.
  Hope to see bog no2 as early as possible.
  All the Best in future endeavours also.
  
  
• https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9659
  

  Project System:
  http://help.sap.com/saphelp_47x200/helpdata/en/04/926eae46f311d189470000e829fbbd/frameset.htm
  
  PS transactions:
  http://help.sap.com/erp2005_ehp_03/helpdata/EN/41/4388389f402852e10000009b38f842/frameset.htm
  

  http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
  
  http://www.easymarketplace.de/online-pdfs.php
  

  
   

  SAP Project System - A ready Reference ( Part 1 )
  https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9622
  
  SAP Project System - A ready Reference ( Part 2 )
  https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9659
  

  
   

  
   

  
   

  
   

  
   

  
   

  
   

  SAP Project System - A ready Reference ( Part 2 )

   
   

  In my previous blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9622 , I had explained Basic PS terminologies with the help of a simple example.
  

  Now let me go to some technicalities of the same.
  

  If some body asks me to develop report in PS module what basic information do I need?
  

  Mainly I need to find out three things :
  

• Master tables and there relationship with each other.
  
• Standard transactions in PS module and
  
• BAPIs used to deal with PS data.
  

  Let's start with the master table
  

  PS Master Tables and their relationship:
  

  Object	Master Table
  Project Definition	PROJ
  WBS element	PRPS
  Network	AFKO ,AUFK
  Activity	AFVV , AFVC
  Activity Element	AFVV , AFVC
  Activity Type	CEPC
  Milestone	MLST
  Budget	BPGE , BPJA

  Following diagram depicts the linkage between various master tables in PS module.
  

   
  

    
  

  
   

  Frequently used PS Transactions
  

  Object	Transaction	Description
  Project Definition	CJ06	Create Project Definition
  	CJ07	Change Project Definition
  	CJ08	Display Project Definition
  	CJ20N	Project Builder
  WSB Element	CJ01	Create Work Breakdown Structure
  	CJ02	Change Work Breakdown Structure
  	CJ03	Display Work Breakdown Structure
  	CJ11	Create WBS Element
  	CJ12	Change WBS Element
  	Cj13	Delete WBS Element
  Network	CN21	Create Network
  	CN22	Change Network
  	CN23	Display Network
  	CN24	Overall Network Scheduling
  	CN24N	Overall Network Scheduling
  	CJ20N	Project Builder
  Activity	CJ20n	Project Builder
  Milestone	CN53N	Overview: Milestones
  	CJ20N	Project Builder
  Relationship	CN49	Overview: Relationships
  	CN49N	Overview: Relationships
  	CNS49	Overview: Relationships
  Confirmations	CN25	Confirm Completions in Network
  	CN27	Collective confirmation
  	CN28	Display Network Confirmations
  	CN29	Cancel Network Confirmation
  	CN2X	Confirm Completions in Network
  Settlement	CJ02	Create Settlement Rule
  	CJ88	Settle Projects and Networks
  	CJ8A	Act.-setlmt: Proj. retirmt. from IM
  	CJ8G	Actual Settlement: Projects/Networks
  Budg et	CJ30	Change Project Original Budget
  	CJ31	Display Project Original Budget
  	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

  BAPIs used in PS Transactions
  

  Project Definition:
  

  BAPI to extract details of Project Definition: 
  

  BAPI Name	BAPI Description
  BAPI_PROJECTDEF_EXISTENCECHECK	To check whether a project definition exists
  BAPI_BUS2001_GETD ATA	To get detailed information about a project definition. To do this, you must transfer the external ID of the project definition in the parameter I_PROJECT_DEFINITION. If required, you can also specify in which language the language-dependent fields, such as time units, system status, and so on, are to be returned. If you do not specify a language, the system language is used
  BAPI_PROJECT_GETINFO	To read detailed information about project definitions and the WBS elements of projects from the system.
  BAPI_PROJECTDEF_GETDETAIL	To read detail information about the project definition
  BAPI_BUS2001_GET_STATUS	To get both the active system statuses and the user statuses for a project definition
  BAPI_PROJECTDEF_GETLIST	Provides a list of project definitions
  BAPI_GET_PROJECT_STATISTICS	Display project statistics

  BAPI to create/update Project Definition data: 
  							

  BAPI Name	BAPI Description
  BAPI_BUS2001_CREATE	Create a project definition
  BAPI_PROJECTDEF_CREATE	Create a project definition
  BAPI_BUS2001_CHANGE	Change Project Definition
  BAPI_PROJECTDEF_UPDATE	Change Project Definition
  BAPI_BUS2001_DELETE	Delete Project Definition
  BAPI_BUS2001_SET_STATUS	one system status and one user status  can be revoked each time, and one system status  and one user status  can be set each time for a project definition

   
   

  WBS - Work Breakdown Structure:
  

  BAPI to extract details of WBS element: 
  

  BAPI Name	BAPI Description
  BAPI_BUS2054_GETDATA	To get detailed information about WBS elements.
  BAPI_BUS2054_GET_GUID_FROM_KEY	Read the GUID (Global Unique Identifier) using the external object key.
  BAPI_BUS2054_GET_STATUS	To read the active system statuses and user statuses for a list of PSP elements
  BAPI_BUS2054_GET_KEY_FROM_GUID	Read the externalobject key (WBS Key) using the GUID (Global Unique Identifier).

  BAPI create/update WBS element data: 
  

  BAPI Name	BAPI Description
  BAPI_BUS2054_CREATE_MULTI	Create  WBS Element
  BAPI_BUS2054_CHANGE_MUL TI	Change  WBS Element
  BAPI_BUS2054_DELETE_MULTI	Delete WBS Element

   
   

  Network:
  

  BAPI to extract details of Network: 
  

  BAPI Name	BAPI Description
  BAPI_NETWORK_EXISTENCECHECK	Check whether network exists
  BAPI_NETWORK_GETDETAIL	Read detailed information about a network including all objects from the system.
  BAPI_NETWORK_GETINFO	Read detailed information about a network including all objects from the system
  BAPI_NETWORK_GETLIST	Produces a list of networks with descriptions. Returns a container of network numbers
  BAPI_BUS2002_GETDATA	Returns Detail Data for Network Header.
  BAPI_BUS2002_GET_GUID_FROM_KEY	Read GUIDS Using the Network Keys
  BAPI_BUS2002_GET_KEY_FROM_GUID	Read Network Key Using the GUIDs
  BAPI_BUS2002_GET_STATUS	Get network Status

   BAPI create/update Network data: 
  

  BAPI Name	BAPI Description
  BAPI_NETWORK_MAINTAIN	To edit network headers, activities and relationships
  BAPI_BUS2002_CREATE	Create Network Header. Only one network can be created each time this BAPI is called.
  BAPI_BUS 2002_CHANGE	Change Network Header. Only one network header can be changed each time this BAPI is called.
  BAPI_BUS2002_DELETE	Delete Network Header. Only one network can be processed each time the BAPI is called.
  BAPI_BUS2002_SET_STATUS	Set/Reset Network Status. At the same time, you can revoke one system status and one user status, or set one system status and one user status in a list of activities for the network.

   
   

  Activity: 
  

  BAPI to extract details of Activity: 
  

  BAPI Name	BAPI Description
  BAPI_BUS20 02_ACT_GETDATA	Detail Data for Activities
  BAPI_BUS2002_GET_ACTGUID_4_KEY	Read the GUIDs Using the Network Activity Key. Read the GUID (Global Unique Identifier) using the external object key.
  BAPI_BUS2002_GET_ACTKEY_4_GUID	Read the Network Activity Key Using the GUIDs. Read the external object key using the GUID (Global Unique Identifier).
  BAPI_BUS2002_GET_STATUS	Read active system statuses and user statuses for a network header (NUMBER) as well as its activities

  BAPI create/update Activity data: 
  

  BAPI Name	BAPI Description
  BAPI_BUS2002_ACT_CHANGE_MULTI	Change one or more activities. Activities of one network only can be changed each time this BAPI is called.
  BAPI_BUS2002_ACT_CREATE_MULTI	Create one or more activities. Activities of one network only can be changed each time this BAPI is called.
  BAPI_BUS2002_ACT_DELETE_MULTI	Delete one or more activities. Activities of one network only can be changed each time this BAPI is called.

   
   

  Activity Element: 
  

  BAPI to extract details of Activity Element: 
  

  BAPI Name	BAPI Description
  BAPI_BUS2002_ACTELEM_GETDATA	Get detailed information about activity elements.
  BAPI_BUS2002_GET_ELEGUID_4_KEY	Read the GUIDs Using the Activity Element IDs

  BAPI create/update Activity Element data: 
  

  BAPI Name	BAPI Description
  BAPI_BUS2002_ACTELEM_CHANGE_M	Change one or more activity elements. Each time this BAPI is called, only the activity elements for one network can be changed
  BAPI_BUS2002_ACTELEM_CREATE_M	Create one or more activity elements. Each time this BAPI is called, only the activity elements for one network can be changed
  BAPI_BUS2002_ACTELEM_DELETE_M	Delete one or more activity elements. Each time this BAPI is called, only the activity elements for one network can be changed

   
   

  Activity Type: 
  

  BAPI to extract details of Activity Type: 
  

  BAPI Name	BAPI Description
  BAPI_ACTIVITYTYPE_GETDETAIL	Detailed information on a selected activity type on Key Date.
  BAPI_ACTIVITYTYPE_GETLIST	List of Activity Types Using Selection Criteria
  BAPI_ACTIVITYT YPE_GETPRICES	Determines, for a given day, activity prices for cost center/activity type combinations.

  BAPI create/update Activity Type data: 
  

  BAPI Name	BAPI Description
  BAPI_ACTTYPE_CHANGEMULTIPLE	Change One or More Activity Types
  BAPI_ACTTYPE_CREATEMULTIPLE	Create One or More Activity Types

   
   

  Confirmation:
  

  BAPI to extract details of Confirmations 
  

  BAPI Name	BAPI Description
  BAPI_NETWORK_CONF_GETDETAIL	Using this method you can make the detail data of a confirmation for a network available for the transferred object. You can also make goods movement posted together with the confirmation available.
  BAPI_NETWORK_CONF_GETLIST	All confirmations are determined for the specified network activity or activity element. The transferred capacity category and split are interpreted as additional constraints
  BAPI_NETWORK_CONF_GETPROP	To make default data available for confirming network activities

  BAPI create/update Confirmation data: 
  

  BAPI Name	BAPI Description
  BAPI_NETWORK_CONF_ADD	To enter confirmations for network activities/ activity elements and splits.
  BAPI_NETWORK_CONF_CANCEL	To cancel a network confirmation that has already been booked.

   
   

• Hey, thanks for the blog on Project System. I think you might be interested to know about the Project System ES bundle.
  

  This ES bundle offers enterprise service-based integration with SAP Project System. One simple use would be to have a contractor with a handheld update project status via an enterprise service (telling you, for example, that the wiring on the third floor of the building is 50% complete, for example).
  

• thanks for appreciating my work.
  Give me some time , even i am not aware about this problem ..let me ask sdn team regarding the same.
  
  Hey you can print this blog. Just Scroll the blog to right most corner and u will see PRINT option.
  
  

  SAP PS Consultant

  Job Description

  • Document current and future business processes in consultation with users • Review and edit requirements, specifications, business processes and recommends related to proposed solution • Provides functional process ownership for one or many business process areas • Works with the user client community, designers and Process Management to determine the best solution to help resolve customer problems and satisfy customer requirements • Document all enhancements including comprehensive flowcharts, system configuration and business requirements (Using SAP tools). • Identify organization strengths and weaknesses and suggest areas of improvement • Understand the business issues and data challenges of the organization • Performs configuration work as needed to support new and existing functionality • Prepares functionality specifications and delivers to developers • Collaborates with developers and the quality assurance team to develop and test significant new functionality • Performs integration testing work as necessary, to insure that new functionality does not adversely affect existing functionality • Identify and document customization (and interfaces) requirements and provide specifications of the same. • Provide pro-active support • Identify root cause of issues in systems and provide resolutions • Trains end users on new enhancements or functionality as required • Maintain confidentiality with regard to the information being processed, stored and accessed

  
   

  
   

  Profile

  • 5 Years of System Analysis, Design and Development experience. • Minimum of 2 full life cycle SAP implementation experience. • Should have good experience in following areas in Project Systems: o Project Planning o Time and Resource Management o Project Execution o Strategic Portfolio Management o Projects experience an advantage • Experience in Life-Cycle Data Management (Document Management) would be an advantage • Should have used Solution Manager • Demonstrated ability to proactively identify improvement opportunities and initiate change • Team player – ability to work in teams and cooperate closely with inter-functional representatives. • Fair conduct of English. • Positive attitude – always on the look for solving problems and helping others. • Committed and hard working. • Good project management, communication and organizational skills

  
   

  Job Title : SAP PS CONSULTANT 
  

  Job Description: 1. Understand the Functional requirements of various Planning, budgeting and project management process
  2. To map the end user requirements with standard functionalities available in SAP
  3. Carry out configuration in SAP system to meet the end user requirements
  4. Understanding of the integration with various modules CO, MM, PP, SD, in relation to PS
  5. Write logic (Functional Specifications) for ABAP programming
  6. Test the developments done to ensure smooth running in the organization
  7. Carry out unit testing & end user testing
  8. Plan & conduct training to end users
  9. Manage master and cutover data
  10. Understand the issues faced by end users on day to day basis and provide solution to their satisfaction
  11. Visit remote project sites and impart SAP usage training to end users 
  

  SAP PS CONSULTANT
  

  • Understanding of PS business processes, standards and practices of related applications
    
  • Involvement in implementing at least 3 SAP projects as PS consultant
    
  • Integration expertise with other SAP modules (i.e. CO, MM, CRM) will be highly valued
    
  • Bachelor's or Master's Degree in Computer Science or related fields.
    
  • Experience in business requirement analysis, business process design, SAP configuration, system testing, data migration and user training.
    
  • Excellent command of English.
    
  • Excellent interpersonal, communication and presentation skills
    

  
   

  
   

  Role and Responsibilities:
  

  • The Senior SAP PS IM Consultant will be supporting in the configuration of an ongoing SAP project for a large government division in Queensland.
    
  • Hands on configuration skills in both the Project Systems and Investment Management modules will be required.
    
  • Previous team lead experience not essential although preferred.
    

  Skills Required:
  

  • A minimum of 7 years of SAP PS/IM experience in multiple large scale SAP implementations required.
    
  • Strong knowledge of PS/IM integration with FI, CO, SD, PM and SD.
    
  • Demonstrated understanding of ASAP Methodology and an ability to understand the business process cycle in addition to configuration of the system.
    
  • strong team leadership skills and be able to define creative solutions and demonstrate initiative to lead teams/sub-teams through project challenges
    
  • Experience in Government not necessary but always helpful
    
  • Excellent communication skills both written and spoken in a team environment.
    

    
     

  SAP - Project System (PS) 
  

  The documentation which follows describes the single roles in the Project System (PS) application component.
  

   Worklist for Project Period-End Closing 
  

  Technical name: SAP_PS_PEREND_PROJ_WLM
  

  Tasks
  

  You can use the transaction for this role to generate the worklist for the period and fiscal year to be processed as part of period-end closing.
  

  
   

  
   

  Activities in the Project System
  

  Transaction	Function
  WLMPS	Worklist Monitor

   Archiving 
  

  Technical Name: <SAP_PS_ARCHIVING>
  

  Tasks
  

  You use the transactions for these roles to maintain data for archiving.
  

  Activities in the Project System
  

  Transaction	Function
  KOAA	Archiving: Settlement Documents
  FMRE_ARCH	Archiving: Funds Commitments
  CN80	Archiving: Project Structures
  KBEA	Transfer Price Agreement/Allocation: Set Deletion Indicator
  KBEB	Transfer Price Agreement/Allocation: Generate Archive
  KBEC	Transfer Price Agreement/Allocation: Manage Archive
  CN99	Archiving Standard Networks

   Requirements Grouping 
  

  Technical name: SAP_PS_GROUPING
  

  Tasks
  

  You can use the transactions for this role to group requirements for WBS elements within a project or across projects for planning purposes.
  

  Activities in the Project System
  

  Transaction	Function
  GRM4	Requirements Grouping: Assign WBS Elements Individually
  GRM3	Requirements Grouping: Assign WBS Elements Using List
  GRM1	Requirements Grouping: Display Assigned WBS Elements
  GRM5	Requirements Grouping: Assign Planning Groups
  GRM2	Requirements Grouping: Display Assigned Planning Groups
  GRM7	Requirements Grouping: Display Assigned Planning WBS Elements

   Claim Management 
  

  Technical name: SAP_PS_CLAIM
  

  Tasks
  

  You can use the transactions for this role to create and edit notifications of type "Claim" and to obtain an overview of existing claims.
  

  Activities in the Project System
  

  Transaction	Function
  CLM1	Create Claim
  CLM2	Change Claim
  CLM3	Display Claim
  CLM10	Claim Overview
  CLM11	Claim Hierarchy

   Collaboration 
  

  Technical name: SAP_PS_CEP
  

  Tasks
  

  You can use the transactions for this role to depict business process between your business and external business partners (producers, sub-suppliers) based on the Internet.
  

  The aim is efficient information and knowledge transfer between a person responsible for a project in your business and external partners, within the framework of a joint project. With the help of Collaborative Engineering and Project Management you can make project structures, product structures, and documents from the R/3 System that are relevant to the joint project available over the Internet to selected participants. The change objects or comments are sent back to you for you to check and return to the R/3 System.
  

  Activities in the Project System
  

  Transaction	Function
  CMWO	CEP: Configuration Management
  CEP_R3_MON	CEP: Monitoring
  CEO1	CEP: Display Folder
  CEO2	CEP: Transfer Folder
  CEO3	CEP: Check Folder

   Executing Controlling Reports 
  

  Technical name: SAP_PS_EXECUTE_CO_REPORTS
  

  Task
  

  You can use the transactions for this role to execute hierarchy reports and cost element reports.
  

  Activities in the Project System
  

  Transaction	Function
  CJE0	Execute Report: Hierarchy Report
  CJEB	Execute Report: Hierarchy Report in Background
  GR55	Execute Report: Cost Element Report

   Displaying Documents 
  

  Tasks
  

  You can use the transactions for this role to display texts and documents for a project and its objects.
  

  Activities in the Project System
  

  Transaction	Function
  CN05	Display Project Texts
  CV03N	Document Management: Display Documents

  Integration
  

  See also:
  

  Maintaining and Displaying Documents
  
  

  Maintaining and Displaying Documents 
  

  Technical name: <SAP_PS_DOCUMENTS>
  

  Tasks
  

  You can use the transactions for this role to maintain and display texts and documents for a project and its objects, and to conduct targeted
  document searches using a search engine.
  

  Activities in the Project System
  

  Transaction	Function
  CN04	Edit Project Texts
  CN05	Display Project Texts
  CV01N	Document Management: Create Documents
  CV02N	Document Management: Change Documents
  CV03N	Document Management: Display Documents
  CV04N	Document Management: Find Documents

  Integration
  

  See also:
  

  Displaying Documents
  

  Line Item Reports 
  

  Technical name: SAP_PS_REP_LINE_ITEM
  

  Tasks
  

  You can use the transactions for this role to display line item reports.
  

  Activities in the Project System
  

  Transaction	Function
  CJI3	Actual Costs/Revenues
  CJI5	Commitments
  CJI4	Planned Costs/Revenues
  CJIB	Budget
  CJIA	Actual Payments/Payment Commitments
  CJI9	Hierarchical Cost/Revenue Planning
  CJIC	Display Project Settlement Line Items
  CJID	Display Project Settlement Line Items

  Integration
  

  See also:
  

  Executing Controlling Reports
  
  

  Executing Controlling Reports 
  

  Technical name: SAP_PS_EXECUTE_CO_REPORTS
  

  Task
  

  You can use the transactions for this role to execute hierarchy reports and cost element reports.
  

  Activities in the Project System
  

  Transaction	Function
  CJE0	Execute Report: Hierarchy Report
  CJEB	Execute Report: Hierarchy Report in Background
  GR55	Execute Report: Cost Element Report

  Reports on Revenues and Earnings 
  

  Technical name: SAP_PS_REP_REVENUES
  

  Tasks
  

  You can use the transactions for this role to display reports on revenues and earnings.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87013562	Annual Overview
  S_ALR_87013563	Structure
  S_ALR_87013564	Plan/Actual/Variance
  S_ALR_87013566	Actual Contribution Margin
  S_ALR_87013567	Quotation/Order/Plan/Actual
  S_ALR_87013568	Project Result
  S_ALR_87013569	Incoming Orders/Orders on Hand
  S_ALR_87013570	Actual/Plan/Absolute Variance/% Variance %
  S_ALR_87013571	Actual - Plan- Comparison per Period
  S_ALR_87013572	Project Result

   Progress Determination 
  

  Technical name: SAP_PS_PROGRESS
  

  Tasks
  

  You can use the transactions for this role to determine the progress values for your project(s).
  

  Activities in the Project System
  

  Transaction	Function
  CNE1	Progress Determination: Individual Processing
  CNE2	Progress Determination: Collective Processing

   Overall CO Planning for Projects 
  

  Technical name: SAP_PS_OVERALL_CO_PLAN_PROJ
  

  Tasks
  

  You can use the transactions for this role to manually plan costs and revenues in the work breakdown structure. You can have the system calculate plan values in the network, or you can copy existing planning and use that as a template for fresh planning.
  

  Activities in the Project System
  

  Transaction	Function
  CJ40	Change Overall Costs in the WBS
  CJ41	Display Overall Costs in the WBS
  CJ42	Change Revenues in the WBS
  CJ43	Display Revenues in the WBS
  CJ9K	Network Costing
  CJ9FS	Copy Planning

   Progress Information System 
  

  Technical name: SAP_PS_REP_PROGRESS
  

  Tasks
  

  You can use the transactions for this role to display progress analysis reports.
  

  Activities in the Project System
  

  Transaction	Function
  CNE5	Progress Analysis: Structure Overview
  S_ALR_87015124	Progress Analysis: Project Hierarchy
  S_ALR_87015124	Progress Analysis: Detail
  CNMT	Milestone Trend Analysis

  Integration
  

  See also:
  

  Progress Determination
  

  Materials Information System 
  

  Technical name: SAP_PS_REP_MATERIAL
  

  Tasks
  

  You can use the transactions for this role to display reports about materials
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87015076	Material Components
  MD04	Requirements/Inventory
  CO24	Missing Parts
  MD09	Pegged Requirements
  MD4C	Order Report
  MB25	Reservations
  S_ALR_870156067	Planned Orders
  ME3K	Outline Agreements
  MBBS	Valuated Project Stock
  ME5J	Purchase Requisitions for Project
  ME5K	Purchase Requisitions for Account Assignment
  ME2J	Purchasing Documents for Project
  ME2K	Purchase Orders for Account Assignment

   Structure Information System 
  

  Technical name: SAP_PS_REP_STRUCT
  

  Tasks
  

  You can use the transactions in this role to evaluate your project structure flexibly, per various criteria.
  

  Activities in the Project System
  

  Transaction	Function
  CN41	Structure Overview
  S_ALR_87015065	Individual Overview: Project Definition
  S_ALR_87015066	Individual Overview: WBS Elements
  S_ALR_87015069	Individual Overview: Networks
  S_ALR_87015070	Individual Overview: Activities
  S_ALR_87015068	Individual Overview: Orders
  S_ALR_87015077	Individual Overview: Sales Documents
  S_ALR_87015078	Individual Overview: Sales Document Items
  S_ALR_87015072	Individual Overview: Relationships
  S_ALR_87015073	Individual Overview: Milestones
  CF16	On Materials
  CF17	On Document
  CF15	On PRT Master
  CF18	On Equipment
  CN60	On Project/Network

   Information System Tools 
  

  Technical name: SAP_PS_REP_TOOLS
  

  Tasks
  

  You can use the transactions for this role to create and edit report forms in the Report Painter, and execute inheritance runs, to draw data from the system for, among other things, the Executive Information System (EIS).
  

  Activities in the Project System
  

  Transaction	Function
  CJE4	Hierarchy Reports: Create Form
  CJE5	Hierarchy Reports: Change Form
  CJE6	Hierarchy Reports: Display Form
  CJE1	Hierarchy Reports: Create
  CJE2	Hierarchy Reports: Change
  CJE3	Hierarchy Reports: Display
  CJE0	Hierarchy Reports: Execute
  GRR1	Cost Element Reports: Create Report Painter Report
  GRR2	Cost Element Reports: Change Report Painter Report
  GRR3	Cost Element Reports: Display Report Painter Report
  GRR4	Cost Element Reports: Delete Report Painter Report
  CJH1	Summarization: Inheritance
  CJH2	Summarization: Inheritance Evaluation
  KKRC	Summarization: Summarization
  KKR0	Summarization: Hierarchy
  CJSA	Data Transfer to EIS

   Actual Payments in Projects 
  

  Technical name: SAP_PS_PAYMENTS_PLAN
  

  Tasks
  

  You can use the transactions for this role to transfer actual payments and display the transfers.
  

  Activities in the Project System
  

  Transaction	Function
  FMWA	Create Funds Transfer
  FMWC	Display Funds Transfer

   Project Year-End Closing 
  

  Technical name: SAP_PS_PROJ_YEAREND
  

  Tasks
  

  You can use the transactions for this role as part of the fiscal year-end closing to carry forward commitment values that are still open into the first period of the next fiscal year, and to carry forward unused project budgets to that fiscal year.
  

  Activities in the Project System
  

  Transaction	Function
  CJCF	Carry Forward Commitment
  CJCO	Carry Forward Budget

   Cost Reports 
  

  Technical name: SAP_PS_REP_COSTS
  

  Tasks
  

  You can use the transactions for this role to display all cost reports.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87013532	Plan/Actual/Variance
  S_ALR_87013533	Plan/Actual/Commitment/Remaining Plan/Assigned
  S_ALR_87013538	Project Version Comparison: Actual/Plan
  S_ALR_87100185	Actual Costs per Month, Current Fiscal Year
  S_ALR_87100188	Actual Costs: Aggregated
  S_ALR_87100189	Actual/Planned Time Series
  S_ALR_87100190	Actual/Plan/Variance per Project and Person Responsible
  S_ALR_87013540	Forecast
  S_ALR_87013541	Project Interest: Plan/Actual
  S_ALR_87013542	Actual/Commitment/Total/Plan in Controlling Area Currency
  S_ALR_87013543	Actual/Plan/Absolute Variance/% Variance %
  S_ALR_87013544	Actual - Plan- Comparison per Period
  S_ALR_87013545	Actual: Period Comparison
  S_ALR_87013546	Commitments: Period Comparison
  S_ALR_87013547	Plan: Period Comparison
  S_ALR_87013548	Statistical Key Figures/Periods
  S_ALR_87013549	Actual - Plan- Comparison, with Partner
  S_ALR_87013555	Project Result
  S_ALR_87013556	Funds Overview
  S_ALR_87013558	Plan/Actual/Commitment/Remaining Plan/Assigned

  Integration
  

  See also:
  

  Executing Controlling Reports
  

  Line Item Reports
  

   Mass Changes 
  

  Technical name: SAP_PS_MASS_CHANGE
  

  Tasks
  

  You can use the transactions for this role to execute mass changes for projects and evaluate them in the log.
  

  Activities in the Project System
  

  Transaction	Function
  CNMASS	Execute Mass Changes
  CNMASSPROT	Mass Changes: Log

   Materials in Projects 
  

  Technical name: SAP_PS_MATERIAL
  

  Tasks
  

  You can use the transactions for this role to plan and monitor project material requirements and costs, and to regulate and schedule the flow of materials.
  

  Activities in the Project System
  

  Transaction	Function
  MM01	Create Material
  MM02	Change Material
  MM03	Display Material
  CN33	BOM Transfer
  MD51	Project Material Requirements Planning
  MD50	Sales Order Material Requirements Planning
  MD4C	Order Report
  CO46	Order Progress Report
  CO24	Backlog Processing: Missing Parts Information System
  CO06	Backlog Processing: Materials
  V_RA	Backlog Processing: Sales Orders
  MDUP	Sales Order/Material Assignment: Edit
  MDUS	Sales Order/Material Assignment: Display
  CNL1	Create Delivery Information
  CNL2	Change Delivery Information
  CNL3	Display Delivery Information
  CNSO	Delivery from Project

   Displaying Materials in Projects 
  

  Technical name: SAP_PS_MATERIAL_DISPL
  

  Tasks
  

  You can use the transactions for this role to display project material requirements and costs.
  

  Activities in the Project System
  

  Transaction	Function
  MM03	Display Material Master Data
  MD4C	Order Report
  CO46	Order Progress Report
  S_ALR_87015076	Material Components

   Project Funds Commitments 
  

  Technical name: SAP_PS_FUNDS_COMMITMENT
  

  Tasks
  

  You can use the transactions for this role to enter expected costs or revenues, even at an early stage when you do not know which transaction (purchase order, material reservation, and so on) will actually cause them. This enables you to reserve portions of the budget early.
  

  Activities in the Project System
  

  Transaction	Function
  FMZ1	Create Funds Commitment
  FMZ2	Change Funds Commitment
  FMZ3	Display Funds Commitment
  FMZ6	Reduce Funds Commitment

   Project Period-End Closing: Individual Processing 
  

  Technical name: SAP_PS_PEREND_PROJ_IND
  

  Tasks
  

  You can use the transactions for this role as part of period-end closing to carry out period-related commercial transactions for each project individually. You thus ensure that, on the one hand, all the data belonging to a project can be determined and, on the other, that the data is available to your company's management.
  

  Activities in the Project System
  

  Transaction	Function
  CJB2	Settlement Rule: Individual Processing
  PSW5	Periodic Repostings
  CPTK	Template Allocation: Individual Processing
  CJN1	Revaluation at Actual Prices: Individual Processing
  CJ08	Overhead: Individual Commitment Processing
  CJ44	Actual Overhead Calculation: Individual Processing
  CJZ2	Interest Calculation: Individual Processing
  CJ9L	Cost Forecast: Individual Processing
  CJA2	Incoming Orders: Individual Processing
  CJ88	Settlement: Individual Processing
  CJIC	Settlement: Investment Project Line Items
  KKA0P	Change Cutoff Period for Planned Results Analysis
  KKA2	Execute Results Analysis: Individual Processing
  KKA2P	Execute Planned Results Analysis: Individual Processing

  Integration
  

  See also:
  

  Period-End Closing: Collective Processing
  

   Period-End Closing: Collective Processing 
  

  Technical name: SAP_PS_PEREND_PROJ_COLL
  

  Tasks
  

  You can use the transactions for this role as part of period-end closing to carry out period-related commercial transactions for several projects simultaneously. You thus ensure that, on the one hand, all the data belonging to a project can be determined and, on the other, that the data is available to your company's management.
  

  Activities in the Project System
  

  Transaction	Function
  CJB1	Settlement Rule: Collective Processing
  PSW5	Periodic Reposting
  CPTL	Template Allocation: Collective Processing
  CJN2	Revaluation at Actual Prices: Collective Processing
  CJ09	Commitment Overhead Calculation: Collective Processing
  CJ45	Actual Overhead Calculation: Collective Processing
  CJZ1	Interest Calculation: Collective Processing
  CJ9M	Cost Forecast: Collective Processing
  CJC1	Results Analysis: Check Status Validity Date
  CJA1	Incoming Orders: Collective Processing
  CJ8G	Settlement: Collective Processing
  KKAJ	Execute Results Analysis: Collective Processing
  KKAJP	Execute Results Analysis: Collective Processing

  Integration
  

  See also:
  

  Project Period-End Closing: Individual Processing
  
  

  Project Periodic CO Planning 
  

  Technical name: SAP_PS_PER_CO_PLAN_PROJ
  

  Tasks
  

  You can use these transactions to determine all the plan data to be taken into account for a period, and to compile project plan data for enterprise controlling purposes.
  

  Activities in the Project System
  

  Transaction	Function
  KP04	Set Planner Profile
  CJR2	Change Costs/Activity Inputs
  CJR3	Display Costs/Activity Inputs
  KSWB	Periodic Reposting
  CJ9BS	Copy Project Planning
  CJ9CS	Projects: Copy Actual to Plan
  CPUL	Template Allocation: Collective Processing
  CJ47	Overhead: Collective Processing
  CJZ5	Interest Calculation: Collective Processing
  CJC2	Results Analysis: Plan Status Changes
  CJ9G	Settlement: Collective Processing
  CJS2	Change Statistical Key Figures (WBS Element)
  CJS3	Display Statistical Key Figures (WBS Element)
  CJK2	Change Statistical Key Figures (Network)
  CJK3	Display Statistical Key Figures (Network)

   Evaluating Human Resources 
  

  Technical name: SAP_PS_PERS_RES_EVAL
  

  Tasks
  

  You can use the transaction for this role to evaluate human resources.
  

  Activities in the Project System
  

  Transaction	Function
  CMP9	Workforce Planning - Reporting

   Planning Human Resources 
  

  Technical name: SAP_PS_PERS_RES_PLAN
  

  Tasks
  

  You can use the transactions for this role to display reports on human resources, in a project view and a work center view.
  

  Activities in the Project System
  

  Transaction	Function
  CMP2	Workforce Planning: Selection Project View
  CMP3	Workforce Planning: Work Center View

   Planned Payments 
  

  Technical name: SAP_PS_PAYMENTS_PLAN
  

  Tasks
  

  You can use the transactions for this role to plan revenues and expenditures in one or more WBS elements, and to display the planned payments.
  

  Activities in the Project System
  

  Transaction	Function
  CJ48	Payments in the WBS: Change
  CJ49	Payments in WBS: Display

   Project Budgeting 
  

  Technical name: SAP_PS_BUDGET_PROJ
  

  Tasks
  

  You can use the transactions for this role to execute budgeting and availability control for your project.
  

  Activities in the Project System
  

  Transaction	Function
  CJ30	Create Original Budget
  CJ31	Display Original Budget
  CJ37	Budget Supplement: Within Project
  CJ36	Budget Supplement: To Project
  CJ38	Budget Return: Within Project
  CJ35	Budget Return: From Project
  CJ32	Change Budget Release
  CJ33	Display Budget Release
  CJ3a	Change Budget Document
  CJ3b	Display Budget Document
  CJBV	Budget: Activate Availability Control
  CJBW	Budget: Deactivate Availability Control
  OPSX	Budget: Reset "Budgeted" Status
  CJ34	Budget Transfer

   Maintaining and Displaying Project Structures 
  

  Technical name: SAP_PS_STRUCT
  

  Tasks
  

  You use the transactions for this role to maintain the structures for your project. A clear project structure is the foundation of successful project planning, monitoring, and control.
  

  Activities in the Project System
  

  Transaction	Function
  CJ20N	Project Builder
  CJ27	Project Planning Board: Create Project
  CJ2B	Project Planning Board: Change Project
  CJ2C	Project Planning Board: Display Project
  CJ2D	Structure Planning: Create Project
  CJ20	Structure Planning: Change Project
  CJ2A	Structure Planning: Display Project
  CJV1	Create Simulation
  CJV2	Change Simulation
  CJV3	Display Simulation
  CJV5	Delete Simulation
  CJV7	Simulation: Logs
  CN60	Change Documents: On Project/Network
  CJ01	Work Breakdown Structure: Create
  CJ02	Work Breakdown Structure: Change
  CJ03	Work Breakdown Structure: Display
  CN21	Network: Create
  CN22	Network: Change
  CN23	Network: Display

   Display Project Structures 
  

  Technical name: SAP_PS_STRUCT_DISPL
  

  Tasks
  

  You can use the transactions for this role to display the structures of your project. A clear project structure is the foundation of successful project planning, monitoring, and control.
  

  Activities in the Project System
  

  Transaction	Function
  CJ20N	Project Builder
  CJ2C	Project Planning Board: Display Project
  CJ2A	Structure Planning: Display Project
  CJV3	Display Simulation
  CJ03	Display Work Breakdown Structure
  CN23	Display Network
  CJ13	Display WBS Element
  KJH3	Display WBS Element Group

  PS Input: Line Manager Generic Role 
  

  Technical name: SAP_PS_LINE_MANAGER
  

  Tasks
  

  <required>
  

  Activities in the Project System
  

  Transaction	Function
  CNR3	Work Center: Display Master Record
  CR13	Work Center: Display Capacity
  CMP3	Workforce Planning: Work Center View
  CMP9	Workforce Planning - Reporting
  CM01	Capacity Evaluation, Work Center View

   Confirmations 
  

  Technical name: SAP_PS_CONFIRM
  

  Tasks
  

  Here, you can enter and process confirmations for activities and activity elements.
  

  Activities in the Project System
  

  Transaction	Function
  CN25	Create Network Confirmation (Individual Processing)
  CN28	Display Network Confirmation (Individual Processing)
  CN29	Cancel Network Confirmation (Individual Processing)
  CN27	Collective Confirmation Processing
  CAT2	Timesheet: Enter Times
  CAT3	Timesheet: Display Times

   Maintaining Work Center Master Data 
  

  Technical name: SAP_PS_BASIC_WRKPL
  

  Tasks
  

  You use the transactions for these roles to maintain the master data for work centers.
  

  Activities in the Project System
  

  Transaction	Function
  CNR1	Work Center: Create Master Record
  CNR2	Work Center: Change Master Record
  CR11	Work Center: Create Capacity
  CR12	Work Center: Change Capacity
  CR21	Work Center: Create Hierarchy
  CR22	Work Center: Change Hierarchy

  Displaying Work Center Master Data 
  

  Technical name: SAP_PS_BASIC_WRKPL_DISPL
  

  Tasks
  

  You can use the transactions for this role to display the work center master data.
  

  Activities in the Project System
  

  Transaction	Function
  CNR3	Work Center: Display Master Record
  CR13	Work Center: Display Capacity
  CR23	Work Center: Display Hierarchy
  CR05	Evaluation - Work Center List
  CR06	Evaluation - Cost Center Assignment
  CR07	Evaluation - Work Center Capacity
  CR08	Evaluation - Work Center Hierarchy
  CR10	Evaluation - Change Documents
  CA83	Where-Used - Work Center
  CR15	Where-Used - Capacity
  OP4A	Available Capacity - Shift Program
  OP03	Available Capacity - Factory Calendar

   Displaying Standard Structures 
  

  Technical name: SAP_PS_STD_STRUCT_DISPL
  

  Tasks
  

  You can use the transactions for this role to display the standard structures of your project.
  

  Activities in the Project System
  

  Transaction	Function
  CJ93	Display Standard WBS
  CN03	Display Standard Network
  CN13	Display Standard Milestones

  Integration
  

  See also:
  

  Maintaining and Displaying Project Structures
  

   Maintaining Standard Structures 
  

  Technical name: SAP_PS_STD_STRUCT
  

  Tasks
  

  You use the transactions for these roles to maintain the standard structures for your project.
  

  Activities in the Project System
  

  Transaction	Function
  CJ91	Standard WBS: Create
  CJ92	Standard WBS: Change
  CJ93	Standard WBS: Display
  CN01	Standard Network: Create
  CN02	Standard Network: Change
  CN03	Display Standard Network
  CN98	Delete Standard Network
  CU41	Standard Network Configuration Profile: Create
  CU42	Standard Network Configuration Profile: Change
  CU43	Standard Network Configuration Profile: Create
  CA88	Replace Work Center
  CA78	Replace PRT
  CN11	Standard Milestone: Create
  CN12	Standard Milestone: Change
  CN13	Standard Milestone: Display
  CN08	Network Parameters from Sales Order: Edit
  CN09	Network Parameters from Sales Order: Display
  CA83	Where-Used Lists: Standard Networks for Work Center
  CA73	Where-Used Lists: Standard Networks for PRT
  CJCS	Change Documents: For Standard WBS
  CN61	Change Documents: For Standard Network

  Integration
  

  See also:
  

  Displaying Standard Structures
  

  Maintaining and Displaying Project Structures
  

  Maintaining Dates in Projects 
  

  Technical name: SAP_PS_DATES
  

  Tasks
  

  You use the transactions for these roles to maintain dates in your project.
  

  Activities in the Project System
  

  Transaction	Function
  CJ2B	Project Planning Board: Change Project
  CJ2C	Project Planning Board: Display Project
  CJ21	Change Basic Dates
  CJ22	Display Basic Dates
  CJ25	Change WBS Dates
  CJ26	Display WBS Dates
  CJ23	Change Forecast Dates
  CJ24	Display Forecast Dates
  CN24	Overall Network Scheduling
  CJ29	Project Scheduling

   Displaying Dates in Projects 
  

  Technical name: SAP_PS_DATES_DISPLAY
  

  Tasks
  

  You can use the transactions for this role to display all the dates in the work breakdown structure.
  

  Activities in the Project System
  

  Transaction	Function
  CJ26	Display WBS Dates
  CJ22	Display Basic Dates
  CJ24	Display Forecast Dates
  CJ2C	Project Planning Board: Display Project

   Monitoring Dates for Materials 
  

  Technical name: SAP_PS_MONITOR_MAT_DATES
  

  Tasks
  

  You can use the transaction for this role to monitor dates for materials.
  

  Activities in the Project System
  

  Transaction	Function
  NWTM	Monitoring Dates

   Actual Transfer Prices 
  

  Technical name: SAP_PS_TRANSFER_PRICE_ACTUAL
  

  Tasks
  

  You can use the transactions for this role to allocate a transfer price from a transfer price agreement, so that actual revenues are posted in the sender and actual costs in the receiver. You can also display the transfer price allocation and cancel it.
  

  Activities in the Project System
  

  Transaction	Function
  CJG4	Transfer Price Allocation: Enter Using List
  CJG3	Transfer Price Allocation: Display
  CJG5	Transfer Price Allocation: Cancel

  Integration
  

  See also:
  

  Planned Transfer Prices
  

   Planned Transfer Prices 
  

  Technical name: SAP_PS_TRANSFER_PRICE_PLAN
  

  Tasks
  

  You can use the transactions for this role to agree a transfer price for the rendering of a particular service between two WBS elements, display, and change the agreement.
  

  Activities in the Project System
  

  Transaction	Function
  CJF1	Transfer Price Agreement: Create
  CJF2	Transfer Price Agreement: Change
  CJF3	Transfer Price Agreement: Display
  CJF4	Transfer Price Agreement: Change Using List

  Integration
  

  See also:
  

  Actual Transfer Prices
  

   Summarized Cost Reports 
  

  Einzelpostenberichte
  

  Technical name: SAP_PS_REP_COST_SUMMARIZ
  

  Tasks
  

  You can use the transactions for this role to combine a number of projects with like characteristics, thereby effecting more efficient project control. This enables you to carry out analyses that allow for clearer costs at higher level, such as project manager level.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87013576	Summarization Overview: Project Hierarchies
  S_ALR_87013577	Summarization: Costs/Revenues/Expenditures/Receipts
  S_ALR_87013578	Plan/Actual/Variance
  S_ALR_87013579	Plan/Actual/Commitment
  S_ALR_87013580	Actual/Plan/Variance
  S_ALR_87013581	Actual/Plan/Commitment
  S_ALR_87013582	Current/Cumulative/Total
  S_ALR_87013583	Budget/Actual/Variance
  S_ALR_87013584	Budget/Actual/Commitment
  S_ALR_87013585	Plan/Actual/Variance
  S_ALR_87013587	Actual Contribution Margin
  S_ALR_87013588	Order Result
  S_ALR_87013589	Actual/Plan/Variance
  S_ALR_87013590	Current/Cumulative/Total
  S_ALR_87013591	Payment Summarization: Overview

  Integration
  

  See also:
  

  Executing Controlling Reports
  

  Line Item Reports
  

  Cost Reports
  

   Calculating the Sales Price 
  

  Technical name: SAP_PS_SALES_PRICING
  

  Tasks
  

  You can use the transaction in this role to calculate the sales price for a customer inquiry re a product or service, and save the result in a document. You can carry out as many sales pricings as you want, and compare them.
  

  If required, you can also create a detailed quotation for a project-assigned customer inquiry, based on project planning in the SD application component. You can use a billing plan to record the sales price calculated as planned revenue in the project.
  

  Activities in the Project System
  

  Transaction	Function
  DP81	Sales Pricing

   Allocation Templates 
  

  Technical name: SAP_PS_MODEL_PROJ
  

  Tasks
  

  You can use the transactions for this role to carry out template-allocation to allocate overhead costs. Costs are not simply allocated, but the quantities used by the relevant receiver object are determined. The costs are calculated by the valuing quanti
  ti
  es at a rate.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87004530	Create Selection Variants for Collective Processing
  S_ALR_87005496	Stipulate Reposting Cycles
  S_ALR_87007996	Maintain Templates
  OKG1	Stipulate Capitalization Percentage Rates
  S_ALR_87005128	Copying Costs and Revenues: Create Plan Version
  S_ALR_87004530	Allocation: Create Selection Variants for Collective Processing
  S_ALR_87005459	Allocation: Define Percentage Overhead
  S_ALR_87005456	Allocation: Define Quantity-Based Overhead
  KKE1	Base Object Costing: Create
  KKE2	Base Object Costing: Change
  KKE3	Base Object Costing: Display

   
   

  Template ( CO) --
  

  Controlling (CO)
  

  A dynamic allocation tool that uses functions and formulas to calculate numerical values and the values of Boolean expressions (true or false).
  

  This tool is used for various purposes such as sender-receiver allocations and as an aid for formula planning. Instead of preassigned allocation data, the template uses a generic description for any data (such as the sender object, quantities, and costs). Since this data is not known at the time the template allocation is performed, it is determined dynamically when the values are calculated.
  

  Payment Reports 
  

  Technical name: SAP_PS_REP_PAYMENTS
  

  Tasks
  

  The system uses the transactions in this role to represent the value flow of project-related payment data in a single project, in partial projects, or across projects according to hierarchical points of view.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87100191	Payments: Receipts/Expenditures for a Fiscal Year
  KSB5	Document Display: Actual Costs/Revenues
  CJ3B	Document Display: Budget
  CJIG	Document Display: Payments
  S_ALR_87013573	Payments: Receipts/Expenditures for all Projects
  S_ALR_87013575	Payments: Receipts
  S_ALR_87013574	Payments: Expenditures

   Payment Transfer for Project Period-End Closing 
  

  Technical name: SAP_PS_PEREND_PROJ_PAYMENT
  

  Tasks
  

  The system uses the transaction for this role to record partial payments and payments that reference invoices in Project Cash Management. You use the payment transfer facility to display cleared invoices under the value type "Payment" in Project Cash Management and to record partial payments and remaining items that reference projects in Project Cash Management.
  

  Activities in the Project System
  

  Transaction	Function
  CJFN	Payment Transfer

  Integration
  

  See also:
  

  Payment Reports
  

  Payment Reports 
  

  Technical name: SAP_PS_REP_PAYMENTS
  

  Tasks
  

  The system uses the transactions in this role to represent the value flow of project-related payment data in a single project, in partial projects, or across projects according to hierarchical points of view.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87100191	Payments: Receipts/Expenditures for a Fiscal Year
  KSB5	Document Display: Actual Costs/Revenues
  CJ3B	Document Display: Budget
  CJIG	Document Display: Payments
  S_ALR_87013573	Payments: Receipts/Expenditures for all Projects
  S_ALR_87013575	Payments: Receipts
  S_ALR_87013574	Payments: Expenditures

   Summarized Cost Reports 
  

  Einzelpostenberichte
  

  Technical name: SAP_PS_REP_COST_SUMMARIZ
  

  Tasks
  

  You can use the transactions for this role to combine a number of projects with like characteristics, thereby effecting more efficient project control. This enables you to carry out analyses that allow for clearer costs at higher level, such as project manager level.
  

  Activities in the Project System
  

  Transaction	Function
  S_ALR_87013576	Summarization Overview: Project Hierarchies
  S_ALR_87013577	Summarization: Costs/Revenues/Expenditures/Receipts
  S_ALR_87013578	Plan/Actual/Variance
  S_ALR_87013579	Plan/Actual/Commitment
  S_ALR_87013580	Actual/Plan/Variance
  S_ALR_87013581	Actual/Plan/Commitment
  S_ALR_87013582	Current/Cumulative/Total
  S_ALR_87013583	Budget/Actual/Variance
  S_ALR_87013584	Budget/Actual/Commitment
  S_ALR_87013585	Plan/Actual/Variance
  S_ALR_87013587	Actual Contribution Margin
  S_ALR_87013588	Order Result
  S_ALR_87013589	Actual/Plan/Variance
  S_ALR_87013590	Current/Cumulative/Total
  S_ALR_87013591	Payment Summarization: Overview

  Integration
  

  See also:
  

  Executing Controlling Reports
  

  Line Item Reports
  

  Cost Reports.
  

  
  

  
   

  SAP PS CONFIGURATION SYLLABUS AND DETAILS
  

  
   

  InvestmentManagement configuration
  

   
   

   Define Program Types
  

      DefineUser Fields
  

      SpecifyStatus Profile&Assign to Program type
  

      GenerateInvestment Program from Profit center&Cost centerhierarchy
  

     MaintainingPlanning&Budget Profile&assigning it to Program type
  

      Maintainingappropriation request types
  

      SpecifyingSpecial symbols for appropriation request number
  

      Maintainingcoding masks for appropriation request number
  

      ConfiguringInternal orders as Investment measures
  

      DefiningTolerance limits for availability control
  

      Configuringprojects as Investment measures
  

  
   

  ProjectSystem Configuration
  

   
   

      DefineProject Profile
  

     Define Investment Profile
  

     MaintainBudget Profile
  

     DefiningSpecial Characters for Projects and Project coding mask
  

      Creating Project type for WBSelements
  

      Creating user defined fields for WBSelements
  

  Maintainingsubstitution rule
  

  Maintainingnetwork types and its parameters
  

  Maintainingnetwork profiles
  

  DefiningMilestone usage
  

  DefiningTime profiles for Project planning board
  

  Definingprofiles for the project planning board
  

  DefiningValue categories
  

  Maintainingbudget profile
  

  Creatingsettlement profile&specifying default profile in projectdefinition
  

  
  Definingstrategies for determining settlement rules
  

  
  Assigningstrategies and default rules to network types
  

  Specifydefault settlement profiles for networks
  

  Definingparameters for Availability check
  

  
  Definingconfirmation parameters        
  

  
   

  
   

  
   

  
   

  Investment Management configuration
  

   
   

  Define Program Types
  

  Define User Fields
  

  Specify Status Profile & Assign to Program type
  

  Generate Investment Program from Profit center & Cost center hierarchy
  

  Maintaining Planning & Budget Profile & assigning it to Program type
  

  Maintaining appropriation request types
  

  Specifying Special symbols for appropriation request number
  

  Maintaining coding masks for appropriation request number
  

  Configuring Internal orders as Investment measures
  

  Defining Tolerance limits for availability control
  

  Configuring projects as Investment measures
  

   
   

    Project System Configuration
  

   
   

  Define Project Profile
  

  Define Investment Profile
  

  Maintain Budget Profile
  

  Defining Special Characters for Projects and Project coding mask
  

  Creating Project type for WBS elements
  

  Creating user defined fields for WBS elements
  

  Maintaining substitution rule
  

  Maintaining network types and its parameters
  

  Maintaining network profiles
  

  Defining Milestone usage
  

  Defining Time profiles for Project planning board
  

  Defining profiles for the project planning board
  

  Defining Value categories
  

  Maintaining budget profile
  

  Creating settlement profile & specifying default profile in
  

  Project definition
  

  Defining strategies for determining settlement rules
  

  Assigning strategies and default rules to network types
  

  Specify default settlement profiles for networks
  

  Defining parameters for Availability check
  

  Defining confirmation parameters        
  

  
   

  
   

  
   

  Project Systems (PS)
  

  
   

  End-to-end Project Management-environments developed from SAP WBS-elements and networks. Specialty solutions include – user status settings, project version control, CATS (Cross Application Time Sheet), resource related quote and billing tie in with SD. Provided: BPR, configuration as well as requirements definition for specialty ABAP/4 reports and outputs.
  

  
   

  SAP Project System (PS) - SD integrations:
  

  
   

  The PS SD Integration is mainly for the customer projects.
  

  System will generate projects/network during creation of sales order.
  
  

  Your sales order value will go to PS as planned revenue.
  When you do billing in sales order you will get actual revenue in the project.
  When the milestone is achieved or confirmation of the network activity, billing block will be removed in your sales order for billing.
  

  
   

  
   

  Also the DIP profile is another area to check out in PS-SD. The idea is to use this in Resource Related Billing scenarios. It's a very interesting feature that has been introduced in 4.6C onwards. This enables you to select at various levels (like Cost element etc) how the billing needs to be done.
  

  
   

  Use the following path for DIP profile configuration.
  
  SPRO-Project Systems-Revenues and Earnings-Integration with SD Documents-Create Quotations and Project Billing-Maintain Profiles for Quotations & Billing.
  

  
   

  The order should be project order. (PS1). In the material master strategy group should be 85 (tab MRP 3) also put item category group as 0005 (tab Sales Org.2)
  
  First to create standard wbs and network as per project requirement. Please also attach mile stones for billing plan. attach the material to the network with the tcode cn08.
  
  to create the sales order with the material then project will be created in the back ground, the sales order number and project number will be the same.
  
  The revenue planning will be done automatically, only we need to plan the cost. Any changes in the sales order will effect the project and vise versa.
  

  
   

  Additional:
  

  1. During inquiry you can enter your WBS element, and do your project planning cost and after that become your estimate price send to customer thru quotation.
  2. If you use variant configuration, you determine activity and component for your project from sales order variant.
  3. You can run availability check based on project planning to check you can deliver on time.
  

  If there is down payment request on your project please post the down payment request by tcode F-29. Once the full payment is received please clear the down payment by tcode F-39.
  

  
   

  To find PS1 document type in transaction VOV8?
  

  
   

  If you have IDES, pls. copy the settings of PS1 (which is available in IDES) into development as ZPS1.
  

  
   

  
   

  The details of CO settings for PS - SD integration
  

  
   

  
   

  The CO Setting is: -
  
  Maintain Assignment of SD-Conditions to CO-PA Value Fields
  
  Controlling > Profitability Analysis > Flows of Actual Values > Transfer of Billing Documents > Assign Value Fields (KE4I)
  

  
   

  Assign Sales Orders to Project Account
  
  This section describes which standard settings and values must exist in Customizing for you to be able to assign a sales document (customer quotation or sales order) to a WBS element manually.
  
  The settings you need to line projects and sales documents manually are prescribed by SAP. If you use these standard settings, you do not need to make any additional settings in Customizing.
  
  Strategy Groups
  
  
  SAP has predefined strategy group 21 (with strategy 21) for the link between sales documents and projects.
  
  Notes:
  
  If you do not maintain the strategy group for the material in the sales and distribution document item, you cannot assign that item to a WBS element.
  
  Alternatively, you can assign the strategy group to a material using MRP group 0021 (also predefined).
  
  Requirements Classes
  
  
  SAP has predefined requirements class 80 with account assignment category D (assignment to WBS element) for the link between projects and sales and distribution documents. Requirements class 80 is assigned to strategy 21 using requirements type KP (also predefined).
  
  Recommendation
  
  do not change the standard settings supplied by SAP.
  

  
   

  
   

  You need to set the SD/PS Assignment indicator on the control tab page of the standard project definition, for PS-SD integration, assembly processing.
  

  
   

  During inquiry you can enter your WBS element, and do your project planning cost and after that become your estimate price send to customer thru quotation.
  

  
   

  To ensure a one-to-one match between the project and its related sales document, the number of the standard WBS element should always be longer than ten characters.
  

  
   

  Some more steps related to IDES data...
  

  
   

  
  
  1).Requirement class 80 and requirement type KP.(Tcode OVZH)
  
  2). Maintain the above in strategy 85 in planning strategy in SPRO.
  
  3). Maintain requirement type and class for item category in VV07.
  
  3) Create standard templates thru CJ91 and CN01.
  
  4).Create materials thru MM01 and select material type as KMAT and strategy group 85 as defined above and maintain item category as u have maintained in spro.
  
  5).Assign materials to network and WbS thru CN08.
  

  
   

  
   

  With currency with PS and SD?
  

  
   

  We have ATO process and have some issue with USD and CAD currency with PS andSD
  
  we are using a group currency in the controlling area (type 30 set as USD). In addition we have object currency turned on for the Controlling Area so we have company currency in parallel for each company assigned to the controlling area. Within CO everything is working fine, the issue appears to be when the CO-PS planned amount is passed to the sales order EK01 condition. In this case, CO-PS has both object currency and controlling area currency but it uses the controlling area currency as the amount passed to the sales order.