Skip to main content

S4HANA-Project Systems Operative Indicators in WBS- CJ20N

 

Use and Purpose of Operative Indicators in WBS elements


When a customer Requests for ATO or ETO process where we create a Project with Integration between SD and PS ( project systems)

As a First step we create a Project in CJ20N and under the Project we will Create Multiple WBS elements which has to be set for Operative Indicators

This article deals with Operative Indicators in WBS elements.


WE Use Operative Indicators to define characteristics of WBS and to specify which tasks WBS can perform during Execution

In General, we have three Operative Indicators such as

1. Planning Indicator

2. Account Assignment Indicator

3. Billing Indicator

For Example, While Creating a Project- Manufacturing an Equipment. We will Create different WBS elements for each Level such as Design, Procurement of components, Production, Assembly and Installation. During Each state some cost is incurred and we plan in advance based on the Activities

This level of Planning the Cost will be only enabled and updated at WBS elements where it is Flagged as Planning Element.


Account Assignment Element:

WBS element will be flagged for Account Assignment element if any Actual Cost is posted

For Example, While Creating a Project- Manufacturing an Equipment. We will Create different WBS elements for each Level such as Design, Procurement of components, Production, Assembly and Installation. In each level of WBS elements while Confirming WBS element we will incur the cost and that Cost is called Actual Cost. 

When Posting Actual , WBS should be flagged as Account Assignment element else Actual cost will not be allowed


Billing Element:

WBS element will be flagged for Billing Element if Revenu is Planned and Posted.

For example, When we are created a Customer Project , we obviously expect some Revenue either directly or with Milestones, in such cases we flag WBS as Billing element which ensures Posting of Revenue 






























Comments

  1. This post is very simple to read and appreciate without leaving any details out. Great work ! cloud call center software

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost ...

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Nu...