Quantcast
Channel: SCN: Message List - Business Content and Extractors
Viewing all 5631 articles
Browse latest View live
↧

Re: DSO key field and data field design

March 22, 2016, 2:23 am
$
0
0

Hello Manju,

 

First and foremost, in your generic DataSource based on function modules (getting data from tables FEBKO, FEBEP) you have to sit with your "Relevant Functional Module Consultant" say SD or MM and do extraction in ECC or in BW and asked him for a unique records.

 

For example, you are going to extract some data/information from SD module tables and there you need help from your SD Functional Module consultant and he will guide/help you to identify a unique record, for instance he will say to you Document No and Billing Date make a unique record. Then you will put document number and billing date containing InfoObjects in your Key Part and rest of the fieds/InfoObject will be in the data part of your Custom/Standard DSO.

 

Secondly, you have ask him about aggregation behavior for same key records, say you have couple of records with same key, then would you like to aggregate the Key Figures or overwrite them.

 

I do hope this reply would help you!

 

Many thanks!

 

Tariq Ashraf

↧
Search

Re: Web Application Designer: Map-legend

March 22, 2016, 6:21 am
$
0
0

I would be also interested in a solution for that. I'm struggling with the same problem.

↧
↧

Re: DSO key field and data field design

March 22, 2016, 10:53 pm
$
0
0

Hi Manju,

 

It Depends on the Requirement...but as standard...Check the Keys of the Tables FEBKO, FEBEP and keep the same Keys as that of DSO...based on that Key the Overwriting should happen.

 

Say for example...In ECC ..Table VBAK has Sale Order is the Key....so we can have Sale Order as Key in DSO.

 

 

Regards

 

SVU

↧

Policy Management - BI Content

March 23, 2016, 7:51 pm
$
0
0

Hi everyone,

 

In my new project, we are implementing Insurance Industry Solutions, using FS-PM (Policy Management) and FS-RI (Reinsurance).

I'd like to see the BI Content for both products within the BI Content Library.

 

I can see that most of the content for FS-RI is located under Industry Solutions > Financial Services > Insurance,

but I can't find where is the content for FS-PM.

 

Please inform me where can I find the documentation related to the BI Content for FS-PM.

 

 

Thank you.

↧

Re: DSO key field and data field design

March 24, 2016, 5:46 am
$
0
0

Thanks for your reply.

 

Updating the key fields based on the issue and user requirement.

↧
↧

Re: Problems with 0EMPLOYEE_ATTR extractor

March 24, 2016, 7:38 am
↧

Re: Problems with 0EMPLOYEE_ATTR extractor

March 24, 2016, 7:39 am
↧

Re: Problems with 0EMPLOYEE_ATTR extractor

March 24, 2016, 7:39 am
↧
Search

Re: Problems with 0EMPLOYEE_ATTR extractor

March 24, 2016, 7:39 am
↧
↧

Re: Remove "Results in a delivered query

March 24, 2016, 11:12 am
↧

No fields mapping in transfer rule of hierarchy

March 25, 2016, 2:42 am
$
0
0

Hi all,

 

I can not import the request for 3.x Transfer Rules of Hierarchy (0COSTCENTER_0101_HIER)

 

Error message is:

Mapping between data source 0COSTCENTER_0101_HIER and source system Q01CLNT100 is inconsistent.

Field 0COSTCENTER will not be delivered from DataSource 0COSTCENTER_0101_HIER in source system Q01CLNT100

Field 0CO_AREA will not be delivered from DataSource 0COSTCENTER_0101_HIER in source system Q01CLNT100

 

The extraction in RSA3, is sucessfull and datasource status is ok.

When I create the transfer rule (3.x) directly in Q01CLNT100, I can not see any fields in transfer structure.

But in DEV system the fields appear normal.

 

Anyone has idea what is the solution to resolve this error?

↧

Re: Policy Management - BI Content

March 25, 2016, 6:11 am
↧

Re: No fields mapping in transfer rule of hierarchy

March 25, 2016, 6:16 am
↧
↧

Re: No fields mapping in transfer rule of hierarchy

March 27, 2016, 4:51 am
$
0
0

Hi Rita,

 

Did you replicate DataSource 0COSTCENTER_0101_HIER in the BW system?

If not, then replicate the DataSource first and after that reimport the transport request.

 

Best regards,

Sander

↧

Re: Policy Management - BI Content

March 27, 2016, 5:28 am
$
0
0

Hi Donnie,

 

In 2010 I did an Insurance project with Policy Management. Unlike other Insurance modules, there was at that time very limited Business Content available, i.e. only in the SAP Source System (in namespace /PM0/). We did not have any Business Content in BW.

I advise you to double-check with SAP if the availability of FS-PM Business Content has changed in the meantime.

 

Best regards,
Sander

↧
Search

Re: No fields mapping in transfer rule of hierarchy

March 27, 2016, 5:15 pm
$
0
0

Hi Sander,

 

I replicated the DataSource but the error is still occurred after reimport.

 

Best regards,

Rita

↧

Re: No fields mapping in transfer rule of hierarchy

March 27, 2016, 5:38 pm
$
0
0

Hi Bhavin,

 

I read the thread you mentioned but I can not activate the datasource, because this is  Hierarchy Datasource.

I don't have any problem with other datasources, just the error occures in Hierarchy Datasource that I transferred after System Copy (R/3 Q01CLNT100).

Extraction of data for InfoObject, Transaction  even hierarchy that transferred before system copy works well.

 

Do you have any idea how can I check the fields of hierarchy datasource for IDOC method?

I can see fields for PSA method.. but not for IDOC.

Or is there any setting for Hierarchy IDOC extraction?

 

Best regards,

Rita 

↧
↧

Re: Policy Management - BI Content

March 27, 2016, 7:41 pm
$
0
0

Hi Sander,

 

I already look all over the newest BI Content documentation and can't find anything related to the Policy Management. You convinced me that SAP has not make anything available in the BW side during all these 6 years.

 

Thank you.

↧

Enhancing 0PM_C01 infocube.

March 29, 2016, 1:11 am
$
0
0

Dear all,

 

We are working with 0PM_C01 infocube, flawless up to now, loading deltas through 0PM_OM_OPA_2 datasource (Orders’ Actual Costs). We have 30 millions of records. But users are asking for 0material characteristic to be included into that cube.

 

So we have checked the datasource 0PM_OM_OPA_2 and we found that it includes the field MATNR already, although not mapped to anything, as 0PM_C01 infocube does not include this 0MATERIAL object.

So we are thinking about adding a new dimension to this cube, the dimension “material”, and including the characteristic 0MATERIAL on it. After that, we will map the field MATNR of our standard datasource to the new material dimension. It seems to be easy and it is not supposed to hurt future delta loads.

 

But, what about the historical data?? Can we think in a remodeling process that allow us to complete the old records with this new field without thinking of deleting all, neither doing a initialization? Business day-to-day doesn’t want an initialization, unless it doesn’t mean all users block. I’ve checked if it is possible to do an early delta initialization, but it is not possible with this datasource.

 

I read a lot of stuff about remodeling, but related always to a characteristic that won’t modify the granularity of the enhanced dimension, but I am sure that 0material characteristic will modify this granularity and it will affect to the fact table, where is going to be more records from now on. In addition, the sample routines always refer to reading a master data to fill the new field, but in my case we want to use the same datasource that is used already for the rest of the characteristics and key figures, since it is a characteristic included in.

Could you please suggest a good strategy to face that?

Is it possible to use a Repair request load and setup tables? 

Thank you very much and best regards to everybody.

 

Jorge.

↧

Re: Enhancing 0PM_C01 infocube.

March 29, 2016, 1:26 am
$
0
0

Hi Jorge,

 

Please create a copy cub of 0PM_C01 and load the data from original cube to copied cube.

While loading data to copied cube, you need to fill 0material(consider that copied cube have 0material) as well.

 

Later you can delete data from 0pm_c01 and do the remodeling.

 

Once you done remodeling and activation of all changes you can reload historic data from copied to to original cube.

 

After your reload, delta load will continue without any issue.

 

Data reloading twice may be time consuming activity.

Please do this activity where there is no business. other wise year or month end reporting may effect.

 

Thanks

↧
Viewing all 5631 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>