cancel
Showing results for 
Search instead for 
Did you mean: 

Storing Custom Data in SAP PS

Former Member
0 Kudos

Dear PS Experts,

If we need to store lot of custom data such as 1. Text Fields (5-10 Such fields) 2. Dates (10-12 Dates) 3. Comments 4. Numbers, etc perticular to one Project OR Network, please suggest how can we achieve this.

Thanks & Regards

Shailesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

I would like to add to Ahmed's reply.

You can also check the User fields in WBS. Maybe you can even make use of these fields.

Best Regards,

Gokul

Answers (3)

Answers (3)

Former Member
0 Kudos

Thanks for the elaborative answers

Former Member
0 Kudos

Customer exit should be the best option.

Look at the below link to use classification charateristics to capture the same which is standard but declared not to be used by SAP.

http://wiki.sdn.sap.com/wiki/display/PLM/ClassificationinPS

Regards

Sreenivas

Former Member
0 Kudos

Any particular reason why we should not use classification?

What could be the alternate solution for classification?

Regards

Shailesh

virendra_pal
Active Contributor
0 Kudos

Usually classification was used in previous versions to provide attributes for a project, obviously the requirement for these ws driven by reporting and hence it was possible to summarise project data based on charateristics for controlling reporting.

In future versions I think from 4.5b onwards, SAP have suggested that summarisation should be done using master data (hecne the option in projet profile).

The question then was that if classification is not to be used for attributes or master data then what to do if a customer needs more master data than the standard fields.

For this SAP provides two options

1) User Defined fields - configurable for WBS and network activity

2) Use of exits CNEX* (you can get the detailed numbers from txn SMOD) for customer defined field on project defintion, WBS network activity etc.

In the new world for reporting, the summarisation hierarchy is built on this master data and not on characteristics.

Further suggestion - if you are implementing a new project go straight for exits, try to keep the user defined field for future. I fyou use all the user defined fields every time you need to add an attribute you have no option but to develop.

former_member203108
Active Contributor
0 Kudos

You can use this exit CNEX0006, to define your own fields in project definition.