Duplicates from PSA to DSO Load

Hi,
I have 2 key fields in the DSO and there is a status field in data fields. In delta loads, I am getting the records with the same keys (already existing) but the different statuses. Due to this I am getting duplicate issue. But, I need to load this to DSO.
Could you please suggest.
Regards,
Chinna

Hi Chinna,
If it is compounded then it would consider as key hence datawould show two(more) records as per compounding
or
If you pass the same value for compounding then it would overwrite,
else create other DSO with 2 key objects without compounding then upload the data from dso1 to dso2 ,
Other than this i don't see any option (when the data writing to DB it will check the key according to that it will update the data so what ever we do it would update like this )
Hope you got the point...
Regards,
Satya

Similar Messages

How to load a selective request from PSA to DSO using DTP?

Hi Gurus,
The PSA is having 3 requests, how to load the request number 2 from psa to DSO using DTP?
Thanks
SDP
Edited by: SDPSAP on Nov 15, 2011 7:58 PM

Let us say that requests are 1,2 and 3. 1 being the first one and 3 is the last one. Now you need to load request 2 in DSO from PSA.
- create a Delta DTP
- Tick "Only Get Delta Once"
- Tick "Get One Request Only"
- Untick "Reterive Until No More New Data"
- execute the DTP, it will load request 1 to DSO
- delete this request from DTP
- execute DTP again, it will load request 2 to DSO; this is what you need.
If DSO is write optimized, you do not need to untick "Reterive Until no More New Data"; just execute the DTP, it will create 3 requests in DSO, delete first and last and you will get only 2 in DSO.
I hope it helps.
Regards,
Gaurav

Long time to load data from PSA to DSO -Sequential read RSBKDATA_V

Hi ,
It is taking long time to load data from PSA to DSO. It is doing Sequential read on RSBKDATA_V and table contents no data .
we are at - SAPKW70105. It started since yesterday . There is no changes in system parameters.
Please advice.
Thanks
Nilesh

Hi Nilesh,
I guess the following SAP Note will help you in this situation.
[1476842 - Performance: read RSBKDATA only when needed|https://websmp107.sap-ag.de/sap/support/notes/1476842]
Just note that the reference to Support Packages is wrong. It is also included in SAP_BW 701 06.

Error while loading data from PSA to DSO using DTP

Hi,
I have a Unique aplha numeric identifier of type "Char" length "32" . When I am loading the data from PSA to DSO using DTP I get the following error message:
"An error occurred while executing a transformation rule:
The exact error message is
Overflow converting from ' '
The error was triggered at the following point in the program:
GP4JJHUI6HD7NYAK6MVCDY4A01V 425
System response
Processing the data record has been terminated"
Any idea how I can resolve this....
Thanks

Hi,
fist check weather any special characteristics if not
check in data source under this we have fields tab check the format of a particular field format internal/external/check u choose internal format, if any check routine once
use Semantic Groups in the DTP.
Try it
Thanku
lokeeshM
Edited by: lmedaSAP_BI on Oct 20, 2010 6:44 AM

Error while loading data from PSA to DSO

Hi,
How to identify the erroneous records in DSO?
While loading the data from PSA to DSO through Process chains we are facing the error says:
"Value '#' (hex. '0023') of characteristic 0BBP_DELREF contains invalid characters"
"Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0BBP_DELREF"
There is no error records in PSA but it seems some invalid characters exists.
Could you please help us how to find the error records in DSO and how to correct it.

Hi,
These are errors BRAIN290 & RSDRO302.
The problem here most likely is that BW doesn't recognise a character you are trying to load. Generally the character is not "#",
as BW displays all symbols it does not recognise as #. You should decode from the hex string what the actual value is. Note that hex values < 20 are not allowed in BW.
Please review Note 173241 and the document mentioned within.
This shows what characters are not allowed in BW characteristic values.
You should check if the character is allowed, and then you can solve the problem in one of the following ways:
1) add this character to the "permitted character" list in RSKC as described in the note.
2) correct the value in the source system.
3) correct the value in the PSA (to do this, you will need to delete the request from the ODS object and then you can change the disallowed character via the PSA maintenance).
4) follow Note 1075403 so that the characters HEX00 to HEX1F are not checked (this affects only characteristics that do not allow "lower case").
5) if you cannot use any of the above options, then you will need to create a routine in your transfer rules for the affected infoobject, and change the value to a character which is permitted in BW.
These are the usual ways to solve this issue.
Rgds,
Colum

Urgent : Error while loading data from PSA to DSO

Hi,
I am working on 7.0.
When i look for data into PSA then i have 1 date field which is containing data in proper date format. This date field is mapped with 0CALMONTH & 0CALYEAR for which i have written routine and directly assigned to 0DOC_DATE .
I have written a start routine to do some modifications in SOURCE_PACKAGE.
But When i am loading data from PSA to DSO its giving below error:
" Exception wrong_date ; see long text RSTRAN 303
Diagnosis
An exception wrong_date was raised while executing function module
RST_TOBJ_TO_DERIVED_TOBJ .
System Response
Processing the corresponding record has been terminated.
Procedure
To analyze the cause, set a break point in the program of the
transformation at the call point of function module
RST_TOBJ_TO_DERIVED_TOBJ . Simulate the data transfer process to
investigate the cause. "
I am not getting why this error is coming up
pls guide me !!

you can map the code to DOC_DATE .
The code is used to read from any date and convert that into Fiscal year/period.
Try this code.
data: l_fiscyear type t009b-bdatj.
call function 'FISCPER_FROM_CALMONTH_CALC'
exporting
id_date = COMM_STRUCTURE-doc_date
iv_periv = 'V9'
importing
ev_fiscyear = l_fiscyear.
result value of the routine
RESULT = l_fiscyear.

Issue when doing Delta loads from PSA to DSO using DTP - Pls help Urgent

Hi All,
I have done 3 data loads into PSA and from PSA, iam loading the data into DSO - by splitting that load into 3 using 3 DTPs. (Split that by Fiscal Period).
2 of the DTP loads are extracting the data from 3 PSA requests.
But, one of the DTP load is filtering on ONE PSA request.
So, we are not getting the full data into DSO.
Can some one pls help me why the DTP load is beheaving like this ???
Even though i have not given any filters for Request id, still , for one load its picking up the data by filtering on One Req ID.
Cheers,
Nisha

Hi Jr,
Sorry for late reply.
I think i found the solution, the diff between the DTP's is i ahve ticked " Get request one after another " .
I have changed it now and its working fine.
Thanks,
Nisha

Error while transferring Data from PSA to DSO

Hi all,
We had a requirement to load data into the DSO.We are extracting it from R3.
Problem is that while loading in PSA it is showing 1056 records ,But when we are trying to load it in DSO it is showing Transferred records as 1428 and added records as 1073.Please help ASAP!!!!!!!!

Hi,
the difference in records can be due to some changes happening in the transformation.
check your transformation from the DS to your DSO if it contains any start,end or update routines oe any other such thing.
Also check if there is one to one mapping from DS to DSO or if some fields in DS are not mapped to DSO.
Regards,
Dhanya

ERROR DURING LOADING DATA FROM PSA TO DSO IN "PRUEFMBKT"

Respected all
I am trying to load data through an r/3 field( pruefmbkt, char-40length) to infoobject. the data is coming correctly to psa but when i am loading it in to dso or infocube request is turning red giving following error message--
Value '010/12.05-112.15/hold on not operate' (hex.
'3031302F31322E30352D3131322E31352F686F6C64206F6E20') of characteristic
PRU_LSIL contains invalid characters
Message no. BRAIN060
Diagnosis
    Only the following standard characters are valid in characteristic
    values by default:
    !"%&''()*,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.+
    Furthermore, characteristic values that only consist of the character #
    or that begin with ! are not valid.
    You are trying to load the invalid characteristic value 1. (hexidecimal
    representation 3031302F31322E30352D3131322E31352F686F6C64206F6E20).
Procedure for System Administration
    Try to change the invalid characters to valid characters.
    If you want values that contain invalid characters to be admitted into
    the system, make the appropriate setting in BW Customizing. Refer to the
    documentation describing the requirements for special characters and the
    possible consequences.
    For more information on the problems involved with valid and invalid
    characters, click here.
kindly give me the solution how to deal with this problem.
thanks
abhay

HI Abhay,
please check if the infoobject corresponding to field PRU_LSIL in BW system has lower case checkbox enabled in the infoobject properties, as the value '010/12.05-112.15/hold on not operate' coming from R/3 has lower case alphabets.
Hope this helps.
Regards,
Umesh.

Long time to load data from PSA to DSO / CUBE. Sequential read RSBKDATA_V

Hi Gurus
The process stays for several hours on sequential read from RSBKDATA_V - temporary storage for DTPs.
After several hours, the processing finally starts, but even when I assign several BGDs to the DTP it takes hours to load the data.
We have BI7.0 with SP22, so all relevant notes are already implemented.
Does any one had similar problem, please?
Thanks in advance
Martin

Hi Martin,
this issue has cropped up a few times. Please check and implement the following notes:
1338465    P22:DTP:LOG: Performance problem when messages are added +
1331544    P22:HINT:Slow performance when accessing RSMONFACT +
1312701    70SP21: Performance on view RSBKDATA_V selects
1304234    70SP21: Performance on the hashed table p_th_rsbkdata_v **
1168098    70SP19: Performance during DataStore object extraction
1080027    70SP16: Performance during parallel processing
These notes should improve the performance of the DTPs in your system.
After you've added the notes, please check in tables RSBKDATA and RSBKDATAINFO whether they contain any data. If the tables are empty, please reorganise the tables, and restart the dtp.
Hope this helps you.
Rgds,
Colum

Data Load for 20M records from PSA

Hi Team,
We need to reload a huge volume of data (around 20 million records) of Billing data (2LIS_13_VDITM) PSA to the first level DSO and then to the higher level targets.
If we are going to run the entire load with one full request from PSA to DSO for 20M records will it have any performance issue?
Will it be a good approach to split the load based on ‘Billing Document Number’?
In Case, If we the load by 'Billing Document Number'; will it create any performance issue from the reporting perspective (if we receive the data from multiple requests?) Since most of the report would be ran based on Date and not by 'Billing Document Number'.
Thanks
San

Hi,
Better solution put the filter based on the year and fiscal year.
check the how many years of data based on the you can put filter.
Thanks,
Phani.

Data from PSA to ODS taking very very long time and fails

Hi Gurus,
I have been trying to load data from my CRM system to BI with some range in Data Selection.
I was loading to PSA then then Data Target (Package by Package). It failed twice by taking lot of time.
Then I brought the data to the PSA only successfully and tried moving it to ODS and shockingly long waiting hours it took and failed.
Please help me resolve this.
Thanks

Hi,
Search the BI short dump overview for the short dump that belongs to the request.
Pay attention to the correct time and date on the selection screen.
You access a short dump list using the wizard or the menu path
"Environment -> Short dump -> In the Data Warehouse".
And also some TRFC time out error.
We have fixed it by increasing the profile parameter time and also clearing the old errored TRFC which where lying in the Source.
Yet this has been running for about 20 hours to move data from PSA to DSO. and only some of the Data Packages are turning into Green and Some in Red and Some in Yellow.
Please help
Thanks

Delete the data from PSA

Hello!
I had unsuccessful data transfer process.
How can I delete the contents of the PSA and load the file into the PSA again?
(tcode, execute steps)
Thank you very much!
regards
Thom

Hi,
Goto - Rsa1 - Modeling tab - datasource - Application Component - Datasource - right click - manage - Select the request and delete then request is deleted from PSA.
Now load data to PSA throught infopackage.
With Regards,
PCR

Split ''Upload from PSA" to separate Data Targets

Hi,
I have the following situation:
1 ODS as datasource
2 ODS and 1 CUBE as data targets.
I'm updating my data targets with deltas with one infopackage using process chain.
As the CUBE is also a data source for another CUBE I want to speed up the upload process by separating the load to data targets.
So:
data from 1st ODS to CUBE 1 as first step then I can process data to CUBE 2 with different process chain;
2nd step would be upload data again form 1st ODS to two remaining ODSs.
The point is that I'm using one info package and cannot split loads per data targets. I tried to create two infopackages: one with CUBE 1 as data target and second with my ODSs as data targets. But the second infopackage doesn't return delta any more.
Is there any solution for such a case?

Thanks Arun for your input, the problem is that I don't want to create new transfer rules or update rules or any other objects. Only question is, if data from PSA can be loaded to the specified target with use of process chain. I know I can use the specified request to upload data targets separately but it involves manual work and I need to use info package variants.
Message was edited by: A. Pazucha

Doesn't load from source system to PSA and DSO

Hi Gurus,
We have launched a Delta load from Source System (POSDM) to DSO. In the source system there are 5000000 rows but none was loaded into DSO or PSA. The delta load was ok, but any data was loaded.
If the delta load was lunch again, would be loaded those 5000000 rows. Or those 5000000 rows wouldn't be able to load again.
Any idea abut this issue? Any feedback will be really appreciated.
Thanks in advance.

Hi David,
Are you sure this 5 million records are delta records and should be pulled into BW as delta??
did you count the number of records in the underlying tables??
which data source you are using??
Delta loads are suppose to bring the new records or changed records since the last data load and not all the records.
Since the request is green as you said and still it shows 0 records then it is possible that nothing has changed since last delta.try to see the details of the data load... if it failed...may be thats the reason you are not able to see any records.
If you schedule the delta again it will bring the records changed or created after last delta.
If the delta was unsuccessfull then turn the QM status and overall status of request to red manually in the monitor of the request and delete it from PSA and all the targets in which its loaded and schedule the delta again and it should bring the delta.
Thanks
Ajeet
Thanks
Ajeet

Duplicates from PSA to DSO Load

Similar Messages

Maybe you are looking for