Ansicht
Dokumentation

CRMV_MKTPL_ATT - Define Field Catalog Attributes for Marketing Project Display

BAL Application Log Documentation   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

In this Customizing activity, you can do the following:

• View the standard calendar attributes delivered by SAP. These attribute entries cannot be changed without modifying the attribute structure.

• Maintain your own attribute entries for custom attributes. for example, fields added via Easy Enhancement Workbench.

Note: Customattributes have to be added in a customer namespace.

The field catalogue of marketing project attributes that you see here can be transferred to the calendar for Group By, Search By Attribute functions and default values in the row context.

Since this is a catalogue containing meta data about attributes, it does not tell you which attributes are actually used in the calendar. It is more of a superset of attributes for you to choose from.

To maintain customer-specific attributes, use the following fields of the customizing view:

Calendar Attr. ID
The technical ID of an attribute.

Category,,
This is the object category. For example, CPfor campaigns or campaign elements and TPfor trade promotions

Attribute ID and Category together form the key of the customizing entry. This means that you can maintain the same attribute ID for different object categories. You do this when the corresponding attribute contains object-specific values such as the Type / Objective / Tactic.

Assgmt Type
This is the technical name of the marketing project assignment which has the attribute structure containing the attribute to be added.
If the assignment type is empty, it means that the attribute is a header attribute and is expected to be part of attribute structure CRMS_MKTPL_OL_ATTRIBUTES_ALL.

Data Field
This can either be:

• The name of a single field, which is part of the corresponding attribute structure depending on the assignment type (see above)

• The name of a structure containing all the fields that combine to form the distinct value of the attribute

Example:
Attribute Person Responsiblehas data field RESPONSIBLE. This is the name of the field in attribute structure CRMS_MKTPL_OL_ATTRIBUTES_ALL. And there is no other attribute you have to consider parallelly, for a consistent person responsible entry.
In contrast, there is the Type / Objective / Tacticattribute. Since a tactic can make sense only if an objective is known and an objective can make sense only in the context of a given type, these individual attributes have to be considered together to make up the logical calendar attribute Type / Objective / Tactic. In such cases, you can specify the name of a structure as the data field which contains fieldnames of the individual attributes that have to be grouped.

Data Field
This is almost the same as the previous Data Field entry, only that this Data Field contains clear textual descriptions of data whereas the previous one contain technical keys.

Cardinality
This indicates if the attributes is a one-is to-one (1:1) or a one-is to-many (1:N) attribute.

Example:
Attribute person responsible is a 1:1 attribute because one marketing project can have exactly one person responsible.
The product in contrast is a 1:N attribute because one marketing project can have multiple products.

Attributes with a cardinality of 1:N cannot be used as row context attributes and will only be available in Group By and Search By Attribute.

Attribute Name
Text that appears on the WebClient UI, to represent this attribute.

Separator
Here you can specify the characters (a maximum of three) that will be used to separate grouped attribute values. For example: Type / Objective / Tactic.

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4524 Date: 20240523 Time: 160336     sap01-206 ( 77 ms )