Handling Descriptions 
The following rule of thumb applies to InfoObjects that are modeled with text:
InfoObjects extracted from Customizing have language-dependent texts. Examples:
Data origin, data provider, data delivery agreement
Type of sales data, stock type
InfoObjects that receive descriptions from outside SAP Demand Signal Management have language-independent texts. These description texts are uploaded in the language they are delivered. Examples:
Product, location
Local attributes of product like product category or brand
Using Contexts to Identify Attributes
Retailers often provide descriptions only and no identifiers (IDs)for their attributes. To ensure that the attributes are unique, they are compounded with a context. If a data origin provides only texts for a local attribute, the system generates a unique ID using the internal number range objects. In the given context, the attributes can then be clearly identified.
The following attributes are compounded with the context:
Product group (/DDF/MATL_GRPL)
Manufacturer (/DDF/MANUFACTL)
Brand (/DDF/BRANDL)
Product category (/DDF/PRODCATL)
Product subcategory (/DDF/PRODSCATL)
Dealing with Descriptions Over 60 Characters
The descriptions of InfoObjects are restricted to the length of 60 characters. However, master data delivered by market research companies quite often contains longer descriptions for products and locations. To enable the handling of long descriptions, products and locations have two additional text attributes. Using /DDF/TXTLG1 and /DDF/TXTLG2, you can split up long descriptions into two fields of 60 characters each. This is implemented in the transformation of the master data flow for market research data.
Note
In market research data, locations are often referred to as “markets”.