Technical Name: 0CMCP_POS_DATA

As several versions of a CDT can be updated to SAP BW within a project for Category Management CP, a CP-specific extraction logic enhancement is required for POS data. The following example illustrates the problem:

The responsible individual in CP maintains two project-specific versions (Retail Project R1 and Retail Project R2) in BW. Each of these CDTs represents a segment (for example, a category) of the corresponding hierarchy of the project partner (retailer), in which the CP individual’s products are found. The retail data (POS) that is relevant for analysis and planning must be uploaded by flat file from the Retail BW Info Cube or the POS data mart to the CP individual’s BW. So that the POS data is updated to the correct CDT version, a specific InfoSource is needed, which, in addition to the POS-relevant fields, contains a field which includes the hierarchy ID from the CDT version maintained in BW by the individual in CP. The ID of the CDT version (for example, R1) must be defined in this field as a constant in the transfer rules of the InfoSources, independent of the retail data (for example, R1) that is updated to the CP individual’s BW. If several CDT versions with internal data are updated, the corresponding ID of the CDT version must be entered as a fixed value in the additional field in the InfoSource. The constant is assigned on a source system, flat file-specific basis.

In addition to the update rules, the levels of the CDT are derived as follows: If the hierarchy ID field of the InfoSource contains the ID when internal data is updated to BW, the function module RS_BCT_CMCP_READ_CDT in the basic characteristic 0CMCP_SKU determines the CDT record of the ID and updates it to the Cubes. When using the CDT version creation, the hierarchy ID field of the InfoSource must always contain a constant. If this is not the case, no CDT will be found and accordingly no record updated to the Cubes.