Customer Attributes

[Former Member]

Hi all,

I need some help with the requirement for the below IMG activity. Namely, I need the process for creating the attributes. Data Dictionaries are new to me.

thanks.

Definition of Customer Attributes for Object Types

Use

You can define a user attribute here. Then assign it to an object. The Transactions, Configuration and Development tabs show the object types . The attribute is project and solution-independent, and is shown in an object dialog box in the Other Attributes tab.

Requirements

The attributes of the attribute are specified in the table or structure fields in the Data Dictionary, so they must be maintained there.

For example:

Integer or Character

Field length

Value help

Activities

To create a user attribute:

1. Choose New Entries.

2. Enter a name and description of the attribute.

The name and description are shown later in the object dialog window, and you cannot change the name after you have saved, so use a meaningful name and description.

3. Save.

Specify attribute attributes:

4. Select an attribute and choose Attribute Attributes in the tree.

5. Specify a Data Dictionary table or structure field or choose from the value help.

6. Specify in the field Value Check:

whether the entry is to be checked against a value list. These values are offered as selection help.

whether it is a required field.

7. In the field Multiple Values, whether this attribute can take only one, or several values.

8. In the field Visibility whether the field is visible in the attribute dialog.

[khalil_serrhini]

Hi Jason,

let's say you want to add a date to the attributes of a program in SOLAR02; like for example date of start !

1 - In SPRO -> Definition of Customer Attributes for Object Types

a - you ll first create a customer attribute (name, description) for ex (zstartdate, start dev date)

b - you ll create property for this attribute (table name, fieldname, multiple values, visibility) for ex (CRMD_ORDERADM_H, POSTING_DATE, SINGLE-VALUE-ATTRIBUTE, Attribute is visible)

AT THIS POINT THE TABLE NAME DOES NT REALLY MATTER CAUSE WE RE NOT GONNA CHECK VALUE OF ATTRIBUTE. WE JUST NEED A TABLE THAT CONTAINS A DATE SO WE CAN HAVE THE RIGHT DATA ELEMENT !! AND THIS ONE DOES CONTAIN A DATE !!

2 - In SPRO -> Assign Customer Attributes to Objects

a - Choose Object Type Program (Object Type) ex (Program)

b - Assign attribute created in step 1 to program (Customer Attribute Name, Attribute Order, Value Check) ex (zstartdate, 1, Input Required) with options like mandatory, check of content ...

3 - After this if you go to SOLAR02, in Development Tab and you select attributes of an object type 'Program Name'; you ll see in a new tab names Other Attributes; YOUR NEW ATTRIBUTE ZSTARTDATE

Hope this helps,

Regards,

Khalil

[Former Member]

Hi Khalil,

I understand the two tasks decribed in the IMG notes, what I dont understand is how to do the requirement.

Unfortunately, your description doesn't get me much closer.

b - you ll create property for this attribute (table name, fieldname, multiple values, visibility) for ex (CRMD_ORDERADM_H, POSTING_DATE, SINGLE-VALUE-ATTRIBUTE, Attribute is visible)
AT THIS POINT THE TABLE NAME DOES NT REALLY MATTER CAUSE WE RE NOT GONNA CHECK VALUE OF ATTRIBUTE. WE JUST NEED A TABLE THAT CONTAINS A DATE SO WE CAN HAVE THE RIGHT DATA ELEMENT !! AND THIS ONE DOES CONTAIN A DATE !!

From what I have been able to tell, I go to tcode SE11 - ABAP Dictionary Maintenance, but I am not really sure what exactly I do here. My guess is I enter my Ztable name into the Database Table field, but I wanted to get some advice from the community before I just fumble along in the system.

[jiamin_pan]

It depends the type of object u want to add in the attribute.

What Khalil means is that u dont have to create ur own table in SE11 if u can just use 1 attribute from a standard table.

The exemple he has given means that u can reuse tha date type from a existing table and add it to the custom field in SOLAR02.

[Former Member]

OK, the fuzziness is starting to go away.

My specific examples are:

- I want to use attributes for business areas that can be assigned to the blueprint structure process steps.

- I also want to use them for configuration cycles, to assign them to IMG objects.

These both seem like custom tables to me.