mh,

I suggest you delete all the data in your existing dictionary (codes, WBS or whatever) and start from scratch. I believe it will only give you a headache reading those codes I presumed you don’t understand as well.

Dieter and Alex are right, WBS is easy in P6 (you can write whatever you want), the same thru with activity codes.

Hi
I don’t know of a way to copy codes into a wbs, sorry. How much in detail the wbs must be, for project management or internal regulations? For reporting purpose it’s better with a big code dictionary.
Regards
Dieter

Hi
As project data has to be represented in accounting, financial controlling, strategic planning ... and has to use data from the erp software (Enterprise Resource Planning) especially master data you have to consider a common key that both systems can understand each other. For projects in general data will be accumulated, because financial controlling has an interest for the status of e.g. engineering in total not for a certain document. To make live easier only cumulated data is transferred - by wbs.
Reporting requirements: All stakeholders have a need for information, but grouped in a different way, only specific parts of the project, ... After you gathered these requirements you’ll assign codes to activities to fulfil all those requirements.
If you’ll need more specific information, just ask for them.
Regards
Dieter

Hi
WBS:
- According to standards
- Interfaces with erp-software and other scheduling in general by wbs
- Not each report group is able to group or to filter by wbs
- Access rights by wbs
- Budget by wbs
- Earned Value parameters by wbs
- Combination of parts of different projects to one project easier

Codes:
- Accessible from (almost) each report group
- Security code

We use both: wbs is standard, related to needs of financial controlling; all other reporting requirements by codes.

Regards
Dieter