S/4 HANA Cloud Professional Services/CPD/SC_PROJ_ENGMT_CREATE_UPD - WorkPackageSet

[purnachandrarao_mandadapu]

Hi Experts,

We have the below issue. Can you please help us?

Issue:

The work package data element in S4C is an auto-generated number. This data will be coming from Clarizen and Agilent would prefer if they can prescribe a work package number into S4C.

Question:

Is this truly a hard issue within S4C or is this something which can be updated? With the coding mask or number range?

[Feras_Al-Basha · Accepted solution]

Hello purnachandrarao.mandadapu3 ,

In addition to enda.fennelly 's comments, by leveraging the project ID generator BADi we could come with a sort of workaround.

Essentially this BADI automatically generates a project ID based on the coded design. Then WBS elements inherent the project ID code generated to create the technical IDs of WBS elements. Hence, a pattern could be defined per customer during BADi implementation. That said, the prefix to override the 1.1 , 1.2 , 1.3 etc. appended to the end of work-packages is not something we would have control over as this is used technically in the DIP profile to match cost and revenue with semantic tags.

To illustrate, say for instance we have two customers.

We implement the BADi with the following logic:

When customer 1 is selected during project creation then automatically a project ID is generated as follows CUST1

Then the first work-package created will be CUST1.1.1, the second work-package will be CUST1.2 etc.

And when customer 2 is selected then the project ID generated is as CUST2 hence the first work package created for this customer will be CUST2.1.1, etc.

Attached is a sample example.

Below are more details about the BADI

During runtime, the following components are available in a structure (as a changing parameter) to generate a project ID up to 16 alphanumeric characters:

• engagementprojectname - Project Name

• customer - Customer ID

• customername - Customer Name

• engagementprojectserviceorg - Service Organization ID

• engmtprojectserviceorgname - Service Organization Name

It is recommended that you use only the components with IDs to auto-generate a project ID (due to the allowed length of a project ID).

Please note the following when implementing a custom logic:

• For customer projects, the custom logic is invoked when you select a customer. In addition, if you wish to influence the ID by the project name, then your logic should consider this input before generating a project ID.

• For internal projects, the custom logic is invoked as soon as you launch the app.

Hope this information helps,

Thank you,

Feras

[Enda]

Hi Purna,

I checked the available SSCUI's and Expert Configuration available on the Activate Roadmap ( https://roadmapviewer-supportportal.dispatcher.hana.ondemand.com/#/group//roadmap/IMPS4HANACLDENMGMT... ) and currently there is no customizing available to maintain external number range available for Work Package

Please raise a feature request if you would like for this to be added at the SAP Customer Influence link http://influence.sap.com/saps4hanacloud

Thank you

Enda.