What is WBS element?

本文详细介绍了工作分解结构(WBS)的概念、用途及其在项目管理系统(PS)模块中的作用。通过政府修建道路项目的例子,解释了如何将大项目细分为多个WBS元素,并分配不同的活动和网络。进一步阐述了如何使用TCode CJ20N创建项目和WBS元素,以及如何在销售订单中关联WBS元素。最后,说明了PS模块在企业项目实施中的关键角色及成本追踪功能。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

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.

Tips by : Hemal, Kunal 
### WBS元素在项目管理和软件开发中的概念 WBS(Work Breakdown Structure,工作分解结构)是一种用于定义和分组项目交付成果及其相关工作的层次化框架。每一个WBS元素代表了一个特定的工作包或任务集合,在整个项目的生命周期内具有明确的责任分配和进度安排。 #### 定义与特性 WBS元素是指构成WBS的具体组成部分,可以是一个单独的任务或是多个子任务的组合。这些元素通常按照一定的逻辑顺序排列,并且彼此之间存在依赖关系[^3]。通过这种方式,项目经理能够更清晰地理解每个阶段所需完成的内容以及如何合理规划资源来实现目标。 #### 创建过程 创建有效的WBS需要遵循一些基本原则: - **自顶向下**:从整体出发逐步细化到具体的活动; - **互斥性**:各分支下的工作项不应重叠交叉; - **完整性**:确保所有必要的工作任务都被覆盖无遗漏; 对于软件开发而言,这可能涉及到需求分析、设计文档编写、编码测试等多个方面的工作流划分[^1]。 ```python def create_wbs_element(task_name, subtasks=None): """ Create a new Work Breakdown Structure Element. :param task_name: Name of the main task represented by this element :param subtasks: List of names representing immediate child tasks/sub-elements :return: A dictionary containing information about the created WBS element """ wbs_element = { "task": task_name, "subtasks": [] if not subtasks else list(subtasks), "status": "Not Started" } return wbs_element ``` 此函数展示了如何构建一个简单的Python对象表示单个工作单元——即WBS的一个节点。它接受两个参数:`task_name` 和 `subtasks` ,其中后者是用来指定该元素下辖的所有直接下属任务列表。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值