Help with custom attributes in PPOMA_BBP

[dean_hinson2]

Hello,

I have added a custom cost center attribute in PPOMA_BBP. I basically a copied existing attribute CNT (cost center). I created a data element and added it to BBP_ATTR_F1. I used OOATTRCUST to add the attribute and made an entry in BBP_ATTR_PROP using SE16. Also, I copied function module BBP_ATTR_F4_ACC and revised for created a custom help module.

The search help works fine in PPOMA_BBP but the selected value is brought back, the value is initally placed the field next to the source system field. However, after a second or two the source system is placed in the custom attribute field and the source system field is blanked out. The same thing happens when maintaining the value manually without using search help.

Is there something I missed?

Regards, Dean.

[dean_hinson2]

Thanks Atul.. for some reason, cannot assign any points. However, Next time, I'll add addtional to make it up to you.

Regards, Dean.

[Former Member]

Hi

Which SRM version are you using ?

<b>Please see the SAP OSS Note -></b>

Note 791465 - PPOMA_BBP:Incorrect search help in back-end for WBS elements

Note 614875 EBP 3.5/4.0: Alpha conversion of the System ID (PPOMA_BBP)

Note 387012 Maintainance of customer attributes

Note 217574 Maintain attribute material group (WGR, RESP_WGR)

<u>Other SAP Notes / related links -></u>

Note 879030 Missing attribute BUK in report BBP_ATTR_TEXT_REFRESH

Note 580769 EBP 3.+: Database error when saving attributes

Note 511365 EBP 3.5: Incorrect default values for PRCAT

Note 544159 EBP 3.+: Backend attributes - no synchronization of texts

Note 545365 EBP 3.+: Refresh of the attribute texts in BBP_ATTR_VALUE_T

Note 508710 EBP 3.5: Default backend-specific attributes are not read

Note 379139 Performance when reading attributes

Note 445401 BBPOR01: Attributes are read incorrectly (PM_VAWRK)

Note 393290 BBPOR01: Attributes are read incorrectly

Hope this will answer all your queries.

Do let me know.

Regards

- Atul

[dean_hinson2]

Atul,

Thanks for the input. These were helpful, but I found out that for some reason (bug maybe) since I did not have the 'default values' checked in OOATTRCUST that caused it not to work. There are standard attributes with the same settings that work but maybe because this is a back-end related attribute, it didn't like not having that set.

Don't know, but it seems to work. Helpful points will be awarded.

Regards, Dean.