Skip to Content

Use / Overview: From SAP Library (Status Combination Code – Structures – SAP Library)


Project managers and members must be able to access information about project elements with certain status combinations. By using status combination codes, the system can quickly find project elements with specific status combinations. The system stores the current status combination codes in the master data table of the respective PS object.



There are predefined combination codes available: from SAP Library: Status Combination Code – Structures – SAP Library

Table 1

Combination Code

Combined Status

1

Released and Budget Insufficient

2

Released and Asset Under Construction

3

Released and Budgeting

4

Budget Insufficient

5

Pre Released

6

Technically Completed

7

Locked

8

Master Data Locked

9

Account Assignment Locked

10

Completed

11

Deleted

12

Deletion Flag

13

Created

14

Released

For WBS elements, these codes can be viewed in table PRPS, in field PRPS_STATUS.  If no values are displayed in PRPS, execute program STATUS_COMB_UPDATE to update the values.  Once this program has been executed, values should automatically update.  However, if there are configuration changes on the status combination code settings, run this program again to update the existing data.


FIGURE 1: PRPS

PRPS1.png

I – Configuration Settings:

1. User Status. This must be configured based on desired/applicable scenarios of the company.  The sample status profile shown, shows three user statuses (BLUE, RED and YELLOW).

FIGURE 2: User Status Profile

STATProf.png

2. Status Priority (Standard Status Combination Codes).  These are the default settings.  The Combination Priority may be changed to suit the requirements. 


FIGURE 3: Status Priority

StatPrior.png

3. Leading User Status Profile.  This is where the additional/user-defined status combination codes are to be defined.  The following settings are to be maintained:

Status Combination: must be from 26 onwards (0-25 are reserved for system).

Description: name to describe the combination code

Combination Priority: this will be used to determine which combination code will be used by the system.

Status Profile: the user status profile which contains the relevant statuses of the combination code

FIGURE 4: Leading User Status Profile

/wp-content/uploads/2014/05/leadusrstprof3_456957.png

4. Leading User Status.  In this step, maintain the user status(es) which must be present in the WBS element in order for the status combination code to be applicable.

Note: display the (internal) User Statuses first in table TJ30

FIGURE 5: TJ30

/wp-content/uploads/2014/05/tj30_456958.png

Leading User Status for Status Combination Code 26. (Notes: E0002 is from table TJ30 corresponding to RED Status.  If Error “Not in Namespace” is encountered, save the Leading User Status Profile first before adding the leading user statuses)

FIGURE 6: Leading User Status (1)

/wp-content/uploads/2014/05/leadusrstat1_456966.png

Leading User Status for combination codes 27, 28 and 29.  Note that for combination code 29, there are 2 user statuses assigned.

FIGURE 7: Leading User Status (2)

/wp-content/uploads/2014/05/leadusrstat2_456967.png

5. Save the settings made.  Execute program STATUS_COMB_UPDATE for all projects involved to update the values.

II – Testing

WBS Active Statuses Expected Status Combination Code Explanation
WBS A – CRTD and RED 13

The following status combination codes apply:

13 (since the syst status of the WBS is CREATED, see figure 3)

26 (since this status RED is active, based on figures 4, 5, 6)

Priority of combination code 13 is 1 (maintained in figure 3)

Priority of combination code is 26 is 2 (maintained in figure 4)

since priority 1 is higher, the resulting combination code will be 13

WBS B – REL (only) 14 (only) status combination code 14 will apply (see figure 3)
WBS C – REL and RED 26

The following status combination codes apply:

14 (since the syst status of the WBS is RELEASED, see figure 3)

26 (since this status RED is active, based on figures 4, 5, 6)

Priority of combination code 14 is 14 (maintained in figure 3)

Priority of combination code is 26 is 2 (maintained in figure 4)

since priority 2 is higher than 14, the resulting combination code will be 26

WBS D – REL and BLUE 27

The following status combination codes apply:

14 (since the syst status of the WBS is RELEASED, see figure 3)

27 (since this status BLUE is active, based on figures 4, 5, 7)

Priority of combination code 14 is 14 (maintained in figure 3)

Priority of combination code is 27 is 3 (maintained in figure 4)

since priority 3 is higher than 14, the resulting combination code will be 27

WBS E – REL and YELLOW 28

The following status combination codes apply:

14 (since the syst status of the WBS is RELEASED, see figure 3)

28 (since this status YELLOW is active, based on figures 4, 5, 7)

Priority of combination code 14 is 14 (maintained in figure 3)

Priority of combination code is 28 is 4 (maintained in figure 4)

since priority 4 is higher than 14, the resulting combination code will be 28

WBS F – REL and RED and BLUE 29

The following status combination codes apply:

14 (since the syst status of the WBS is RELEASED, see figure 3)

26 (since the status RED is active, based on figures 4, 5, 6)

27 (since the status BLUE is active, based on figures 4, 5, 7)

29 (since the status RED and BLUE are active, based on figures 4, 5, 7)

Priority of combination code 14 is 14 (maintained in figure 3)

Priority of combination code is 26 is 2 (maintained in figure 4)

Priority of combination code is 27 is 3 (maintained in figure 4)

Priority of combination code is 29 is 1 (maintained in figure 4)

since priority 1 is the highest, the resulting combination code will be 29

WBS G – REL and RED, BLUE and YELLOW 29

same as above.

Note: a status combination code will apply if the WBS element contains ALL the statuses defined in the Leading User Status assignment (Figure 6, 7).  However it is alright if the WBS element has more statuses active than the statuses maintained in the Leading user status.

Additional Reference – SOME Relevant SAP Notes:

2006147 – Status combination code can’t work correctly in validations or substitutions of project objects.  Consider this note if you intend to use the status combination codes in validations/substitutions.

1374337 – Status Combination Code:Update Performance and General Info

1376873 – Status Combination Code Override

1327621 – Status Combination Code Customizing:F4 help

1623507 – Status combination code corrections

Note: This document is based on my basic testing and conclusions drawn based on observation.  Feel free to point out and correct any errors.

This feature is available under Business Function OPS_PS_CI_1, SAP Enhancement Package 3 for SAP ERP 6.0

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Sudhakar Pappu

    Hi,

    Let me congrat for your efforts and time to publish the document.

    However, while reading I felt some disconnect from point no 2 to further points. Though you have mentioned step by step process but seeing some disconnect between them and not able to connect logically in sequential way. You would have added proper navigation and transaction codes appropiately for each step to connect from step 1 to last step. for example status priority figure 3. Also add what are the reports where we can use status combination to extract the data instead of accessing at table level.

    Indeed its good effort and keep it up.

    Thanks,

    Sudhakar

    (0) 

Leave a Reply