User status profile: Replication of user status to PS

[Former Member]

Hello all.

The requirement is to be able to set a user status in cProjects and then to have it replicated into PS.

There are OSS notes under PLM-CPR (744586,963404) which mentions this type of functionality.

Note 744586 states for example that

"

...

The logic for transfer user status is as following:

1. The user status profile used in cProjects must have the same name as the user staus profile defaulted in project profile in R/3.

2. The user status set in cProjcts must have the same name as the user statis defined in the corresponding status profile in R/3.

"

The notes are however also tagged with software component BBPCRM.

Am I correct in assuming that this particular function therefore is only available when using project replication in CRM (and not when using software component CPRXRPM) ?

If yes - is there anyone with experience of other ways of achieving something like this?

Regards / Anders

[Former Member]

Hi Zhenbo,

thanks for your answer.

I will talk with the customer at hand of whether to report this in Solution Manager as a functionality gap.

In a scenario where you use manual MLC linkage I think it is OK to set the user status directly in PS:

Here we are however planning to use the automatic MLC WBS-creation (down to level 3). In order to set a user status change in PS you would then each time have to first undo the master data lock and after the user status change set the master data lock back again.

This do not look a good process.

It would have been better to be able to set the status in cProjects (where the concerned people mainly will work) and then to have it replicated to PS.

Are there any other options at hand?

Regards / Anders

[former_member201206]

Hi Anders,

You noticed the components correctly. The both notes are only valid for the cProject 3.1 scenario, which uses the CRM middle ware to replicate the cProject -> R/3 PS.

The replications logic of cProject 4.0 has been changed completely. And only costs relevant fields are transfered to the R/3. Even some system status of cProject is not transfered to the R/3. See note 927960.

If you find this is functionality gap, which can be used in common business scenario. It is welcome to report it to SAP solution manager.

Thanks for your efforts in advance,

Kind regards,

Zhenbo