Transformation of 0SD_C03

[Former Member]

Hi Experts,

I am confused about how to create the transformation for Cube 0SD_C03.

What i have done so far:

1. Activated the Datasources in R/3 and dragged some fields required from communication structure.

2. Replicated it in BI system.

3. Migrated the Datasource in BI System.

Now when i try to create the transformation between the datasource 2LIS_13_VDITM (for billing item), many of the fields like document number, item number, customer gropu, material group etc that are available in my Datasource are not there in the cube.

Another thing that its taking data from multiple DataSources like 2LIS_13_VDHADR, 2LIS_13_VDITM, 2LIS_11_VDHADR & 2LIS_11_VDITM.

I need data from all of them how should i perform mapping, not getting it.

Please suggest me how to perform the mapping, its very urgent.

Thanks !

[Former Member · Accepted solution]

If you dont find the exact Business Content fit for your Business Requirements, most probably, either you need to enhance 0SD_C03 cube to accommodate the extra fields or create a ZSD_C03 with all the information you require.

Also check is there any BC cube which is closely matching your requirements.

[Former Member · Accepted solution]

Praveen for billing related requirements there is only 0SD_C03 available.

That has few fields meeting my requirement, but i am confused about for all the SD requirements is it not necessary to have the fields like Document number, billing number or item number in the standard cubes ?

Then do i enhance it for Document number and other fields ?

[Former Member]

Donot migrate the datasource before you migrate TR/UR.

Saving TR/UR to a word doc may help in mapping as the system would hardly generate any proposals for mapping.

If you have the same Cube & DS up and running in Sandbox - Validate the transformations.

Routines may be migrated manually accordingly to OO ABAP.

[Former Member]

Roberto can u tell me why the fields like document no. or other are not there in the standard one.

[Former Member]

It is not mandatory that all fields in the datasource be mapped to the target fields.

Here may be the fields in question are important, can you please check Transfer Rules if available in your sandbox for the same.

[Former Member]

Looking at your scenario you may need to enhance standard SD_03 cube to accommodate all the required fields. Recntly we build a similar cube that is an enhanced version of SD_C03 which will extract data from Application components 11(Sales Orders), 12(Deliveries) , 13(Billing Documents) & also a Generic Extractor.

As Roberto said it is not mandatory to have all the fields in R/3 LO structure must be extracted to the cube and present in design.

[Former Member]

<i>1. Activated the Datasources in R/3 and dragged some fields required from communication structure.</i>

This means that you have enhanced the standatd LO structure by enhancing couple of new feids from R/3 comm structure. So to store the data for those new fields in BW you have to enhance Info Cube.

[Former Member]

Praveen this is what i have to also do exactly the scenario that u have done, taking data for Sales Orders, billing and 1 generic Datasource.

I do agree that not all fields are mandatory to be mapped. But i am talking about the very common one's Document number, billing number etc. and they are important too.

If we do not have mapping for them, then how we will differentiate each record at reporting level or at some calculation level......Very confusing as i am doing it for first time.

[Former Member]

I think you are looking at more detailed level information storage in BW.Most of the cases the requirement is to display only the sales information in a summarized form.

If your requirement is to extract the sales info at Document Number level, you need to stage the information at ODS first and then update the the cube.look at 0SD_O03.

Using RRI you can drilldown in reports upto Document Number level.