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

Similar Messages

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.

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

Error while loading data from PSA to Infoobject through DTP(URGENT)

Hi-
I am running into an issue while loading the data from PSA to Infoobject.
It says
Data Package 1 : error during processing.
Updating Attributes for Infoobject
Error in substep
Process Terminated
Please let me know ur solution as this is very urgent....

Data Package 1 : error during processing.
This is the error when your flat file is opened at the time of scheduling. Pls close your flat file, will upload correctly.
Let me know if you have any further query.

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.

Error while loading data from 0FI_TX_4 to ODS

Dear Friends,
One of our proccess chain getting error since a week, every day with same error while loading data from R3 data source 0FI_TX_4 to ODS.
Short dump is raised in R3 system.
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLBWFIR" or "LBWFIRU13"
"BWFIR_READ_BSET_CPUDT_DATA"
ORA-01555
The number of records are below 10000 only.
All other chains are OK.
we have already searched SDN and Notes...and applied below solution, but still no use
Increase the size of all the roll back segments
Increase number of REDO logs
Decrease the number of records per data packet
Any more suggessions please ??
Thanks
Tony

How are you telling that no. of records are below 10000 .Have you checked the no.of records in PSA???
Now ,I tell you something which I had done for this error .I increased the Package size such that whole data gets transferred in single data package.Please make the package size as large as possible so that all the data can be processed in single package.
I know you have read so many threads on the same but what I am suggesting is what I have done and successfully rectified this issue.
regards,
rocks

Error while updating data from PSA to ODS

Hi Sap Gurus,
I am facing the error while updating data from PSA to ODS in BI 7.0
The exact error message is:
The argument 'TBD' cannot be interpreted as a number
The error was triggered at the following point in the program:
GP44QSI5RV9ZA5X0NX0YMTP1FRJ 5212
Please suggest how to proceed on this issue.
Points will be awarded.

Hi ,
Try to simulate the process.That can give you exact error location.
It seems like while updating few records may be no in the format of the field in which it is updated.
Regards
Rahul Bindroo

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 a file on application server

Hi all,
Facing an error while loading data from a flat file.
Error 'The argument '##yyyymmdd;@##' cannot be interpreted as a number ' while assigning character.
I changed the format of date fields (tried with number,general,date(International))in the xls. But i still get the same error.Did check all the data types in Data source all the fields are dats.
Can you please tell me what could be the problem?
Thank you all,
Praveen

Hi all,
As far as my first question i got through it but i had one more field in my flat file while actually is a time stamp, but in my flat file i have a data in this format
10/21/2006 5:11:48 AM which i need to change to 10/21/2006
one more note is i have some of the fields as NULL in this field
Last Updated Date
10/21/2006 5:11:48 AM
10/21/2006 5:11:48 AM
NULL
NULL
10/21/2006 5:11:48 AM
NULL
I want to display the values as 10/21/2006 and NULL as it is.
Please let me know if we have a conversion routine in datasource which can solve my problem.
Regards,
Praveen

Error while loading data from DS into cube

Hello All
I am getting the below error while loading data from Data source to the cube.
Record 1 :Time conversion from 0CALDAY to 0FISCPER (fiscal year ) failed with value 20070331
Wht am i suppose to do?
Need ur input in this regard.
Regards
Rohit

Hi
Simply map 0calday to 0fiscper(you already done it)..You might have forgotten to map fiscal year variant in update rules....if it comes from souce,just map it..if it won't comes from source...make it as constant in update rules and give value..
If your business is April to March make it as 'V3'
If your business is January to Decemeber make it as 'K4'..
activate your update rules delete old data and upload again....
Hope it helps
Thanks
Teja

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

Error while loading data from R/3 to PSA

Hi,
While loading data from R/3 to PSA i am getting error 'the argument 0.6 j cannot be interpreted as a number when assing application structure.Actually in R/3 0.6 and JPY are 2 different columns.So when loading J is getting concatenated with 0.6,so i think i am getting this error.
Hope i am clear.
please help me to resolve this issue.
Thanks in Advance,
Girish

Hi,
U have to go thru the note and chk/compare the settings with ur system...i.e packages, levels...
If not take the assistance from BASIS...
Note; And also all the notes may not be the exact note tht matches ur issue always...its jst a comparision within our system...If it doesn't solve our issue we have to search for another alternative...
rgds,

Error while loading data from R/3 into DSO

Hi,
While loading data from 2lis_02_s012 into a DSO the following error occured:
=============================================
Diagnosis
    Updating for the information structure is still activated in client 150
    (and possibly also in other clients).
System Response
    o   It is not possible to upload data in the initial mode.
    o   Generation of the delta update was terminated.
Procedure
    1. Switch off updating in all system clients.
    2. Repeat the relevant activity.
=============================================
Anyone plz help me in solving the issue.
Thanks & Regards,
VN.

Hi VN,
1. Incase you do full update , system will allow you to load without any error.
2. In case you want to do init then
      Lock users
      Stop the update in the system .
      Load init Package
      Start the update
      Unlock users.
      Load delta package.
Hope it helps.
Regards
Mr Kapadia

Error in loading data from PSA to masterdataTables by using ProcessManually

Hello,
While loading Attribute master data to Masterdata tables, the data is loaded successfully to PSA but when I clicked process manually tab in the monitor screen to load the Attribute master data to Masterdata tables it is showing error.
Can anyone pls help me in solving this issue.
Thanks,
Soujanya

Hi Soujanya,
If it is a SAP BI 7 data flow, in order to load data from PSA to the InfoObject master data tables, you have to run the corresponding DTP.
On the other hand, if it is a SAP BW 3.x data flow, the InfoPackage should be configured so as to update data to subsequent targets (that is to say, the InfoObject).
Finally, take into account that if the DataSource provides duplicate records, the DTP or the InfoPackage (depending on the dataflow version) should be configured in order to deal with it. Otherwise, you could receive error messages during data load.
I hope this helps you.
Regards,
Maximiliano

Error while loading data from PSA to DSO using DTP

Similar Messages

Maybe you are looking for