Same WBS name for different projects

[Former Member]

Hi all,

It looks like it is not possible to have several wbs which have the same id, even if they are linked to different project..

Any solution?

Best regards,

Julien

[Former Member · Accepted solution]

The solution is to have unique WBS code. Normally you use the project code as a prefix for WBS code.

[Former Member]

Hi

I want to know for exactly waht purpose you need this?

Second thing you try to identify wbs by short id filed so it is possible that different wbs can have same short ID .

Example

You have two project s T-123456 aND T-123457 AND YOU USE MASK AS + + + THEN you get short id for two wbs as T13 .

SO MORE THAN ONE WBS can have same ID but with referance to project .

Waiting for reply

[Former Member]

Nitin, We are unfortunately not masters of project/wbs definition. They are created in an other system. The idea was to have only one referential.

shashank22 , the new system change structure of projects/wbs.

at the moment projects and wbs use 6 digits. In wbs we concateante project and wbs.

tomorrow, projects and wbs will be in 15 digits each one..impossible to concatenate anymore (only 24 char available)

our problem is that a wbs id (for example X) can be associated to two differents projects (for example Y and Z)

[Former Member]

It look like that coding mask in wbs could be a good idea.

We have an interface using BAPI to create/updrate WBS but that field is not available...Any way to automate this?

[nitin_patoliya]

Yes It is not possible to have same WBS E code in diff. project. The logical reason is that WBS Element is cost object itself and in real time posting transaction same is used alone not with project definition. As suggested by PS User it is advisable to use Project definition as prefix to WBS.

With Regards

Nitin P

[Former Member]

Actually we are already using project in WBS name.

It was working because project were on 6 char and wbs on 12. But now, our projects are on 15 char and wbs too..

in PRPS, wbs field is on 24 char so, impossible to use project name in wbs...

[nitin_patoliya]

In that case you should take logical call so you can identify project name from WBS and vice verse.

With Regards

Nitin P.

[Former Member]

What do you mean by logical call? Does SAP handle such things?

Thanks a lot,

Julien

[nitin_patoliya]

We should customized project structure based on some logical convenience.

As you told you project no is too much long that's why you are not able to prefix project no with WBS no.

- Use of mix of Alphabetic and numerical in project coding mask say in TE- 0910000000 say here TE is your department of line of business 09 is you financial year1000 is you company code and 0000 is open no. range for you . This is just an example for the project definition.

Buy minimizing use of Alphabet, you can optimized project doing mask and give logical representation in the mind of business user.

You can use of validation to avid any user errors. while creating project in any of the departments. So, you will not face 24 character long project mask.

-

---

In particulate to your question logical call i mean, if your project definition is too long than drop few character from it ,so you can accommodate WBS no with prefix of project definition.

With Regards

Nitin P.