Error While Loading Master Data - Generic Extraction

[Former Member]

Hi Experts,

I've encountered an error while loading Master data. Below is the Complete scenario. Please any one answer my question?

SCENARIO:

1. We are required to Create a Master Data in EBI from the generic table maintained at ECC.

The table at ECC has following structure:

Customer | Sales org | Material Division | Segmentation

where Customer, Sales org and Material Division are primary keys. Segmentation is maintained at the level of customer/salesorg/matdiv.

2. We need to maintain the below data flow at EBI.

ECC --> PSA --> Staging DSO --> Transformation --> Master Data

3. The Master Data should have below structure:

Customer | Sales org | Material Division | Crop Year | Segmentation.

where Sales Org and Material Division are compound attributes

4. Create TVARC variable for maintaining CROP YEAR at DSO level. Crop year data won't be coming from ECC.

5. We need to show SEGMENTATION infoobject as Free char at existing Queries.

QUESTIONS:

1. I've Created a master data for Customer by adding Sales org , Mat div, Crop year, segmentation as navigational attributes.

and created Write Optimized DSO with Customer, Sales org, Mat div and Crop year as key fields and Segmentation as Data fields.

I've loaded the data till DSO but when i am loading master data , I am getting error with duplicate values.

I understand the error because of duplicate customer values are being loaded to Master data. but

How to load data from DSO to Master data with 4 primary keys (Customer, Sales org, Mat div and Crop year) in master data?

Let me know if you need any information. This is URGENT. Please help me out to understand the concept and in rectifying the error.

Thanks,

Rohit 

[former_member209202 · Accepted solution]

Hi Rohit,
Please se my suggestion inline.

3.1.  Its understood that we need to create master data in EBI according to the structure given above.

Given that the primary keys are Customer,Sales org, Mat div and Calyear, How do i need to create master data?

I thought this is the solution but need inputs. As you both said i need to compound Sales org, Mat div and Calyear to Customer.

Suman - I can go for standard DSO and add that in multi provider. But my requirement say that i need to create a master data with 4 primary keys.

[Sourav]--- Create Master Data by compounding of Sales Org, Mat Div and Calyear to Customer as you said, But don't add any one of them to attribute. Now, if you have show to Sales Org. Mat Div and Calyear as separate column in the report.. this approach would be challenging. I am assuming as you are already conveyed to create master data, this is the only way of having four primary key.

3.2.  If we can answer 3.1 then we know that how to create master data. Now coming to data flow. they said Staging DSO. Is it Write optimized DSO? or Standard DSO?

If Write optimized DSO, will below data flow work?

ECC ----(Full) ----> PSA----(Delta)----> WRT DSO------(Delta/Full) because its same?---> Master Data

OR

if Standard DSO

ECC ----(Full) ----> PSA----(Delta)----> Std DSO------(Delta) ---> Master Data.

Please let us know what DSO i need to use and what would be the ideal flow?

[Sourav] --- Use Standard DSO and here you may keep 0Calyear as Data field as you are saying 0CALYEAR will be derived based on TVARVC. I hope combination of Customer, Sales Org, Mat Dive will uniquely identify a record.

Flow would be ECC ----(Full) ----> PSA----(Delta)----> Std DSO------(Delta) ---> Master Data.

3.3.  Let me know how to get entries of ocalyear in DSO by creating variable TVARC.

What is TVARC? Any idea? Please note that we are not getting year entries from ECC.

[Sourav] TVARVC is a table where you maintain entries. Go to SM30 put a entry as per the structure there. Once you put the entry you have to write look-up from TVARVC to DSO in the PSA---> DSO transformation to populate the 0CALYEAR values. If Calyear is going to be always current year alternative approach could be reading the calyear from sy-datum.

Hope This Helps.

Sourav

[Former Member · Accepted solution]

Thanks Sourav for your answers/suggestions. Please see my comments/Questions on your points. Point 3.2 If we can answer 3.1 then we know that how to create master data. Now coming to data flow. they said Staging DSO. Is it Write optimized DSO? or Standard DSO? If Write optimized DSO, will below data flow work? ECC ----(Full) ----> PSA----(Delta)----> WRT DSO------(Delta/Full) because its same?---> Master Data OR if Standard DSO ECC ----(Full) ----> PSA----(Delta)----> Std DSO------(Delta) ---> Master Data. Please let us know what DSO i need to use and what would be the ideal flow? [Sourav] --- Use Standard DSO and here you may keep 0Calyear as Data field as you are saying 0CALYEAR will be derived based on TVARVC. I hope combination of Customer, Sales Org, Mat Dive will uniquely identify a record. Flow would be ECC ----(Full) ----> PSA----(Delta)----> Std DSO------(Delta) ---> Master Data. [Rohit] - No, I cannot keep ocalyear in data fields since I need segmentation of customers for both years 2015 and 2016. if I consider only 3 infoobjects "Customer, Sales Org, Mat Dive" as primary key, it will supress 2015 entries when i load 2016 entries with same primary key combination. Thanks for suggesting data flow. but what if i use Write optimized DSO here? what diff it might take when compared to Standard DSO. What i might loose if i use write optimized dso? Thanks, Rohit

[Former Member · Accepted solution]

Hi Sourav,

Sorry, my previous reply was completely congested. Could you please answer my below doubts. Thanks a ton for your answers

Its re: point 3.2

[Rohit] - No, I cannot keep ocalyear in data fields since I need segmentation of customers for both years 2015 and 2016. if I consider only 3 infoobjects "Customer, Sales Org, Mat Dive" as primary key, it will supress 2015 entries when i load 2016 entries with same primary key combination.

Thanks for suggesting data flow.

but

What if i use Write optimized DSO here?

What diff it might take when compared to Standard DSO?

What i might loose if i use write optimized dso?

Thanks,

Rohit

[former_member209202 · Accepted solution]

Hi Rohit,
If you cannot keep 0CALYEAR as Data field keep it as Key Field.

On Coming to your question, what if write optimized DSO is used .. your load performance will definitely be good considering huge number of records. In this case you have to define semantic key as you want to keep the four characteristics as key. But in case of duplicate records you might face issues.

One approach could be you do not define any semantic key and let the duplicate records be handled at master data level.

Write Optimized DSO - SAP NetWeaver Business Warehouse - SCN Wiki

Sourav