* Error from PSA **RSAODS

I am facing the issue in 0HRPOSITION_TEXT Master Data Load that "**** Error from PSA ****(RSAODS) " again and again and
the PSA is also not present for this specific load .
What to do for this.?

Also,
Check sm58 in sorce system and if any entries with your BW source system then select it and Goto Execute LUw and execute it. This happens when some datapackets does not reach PSA.
Another solution might be the one described in note 968504: running the program 'RS_TRANSTRU_ACTIVATE_ALL'.
Thanks
Neetha

Similar Messages

"****Error from PSA****" error message when loading InfoCube

Hi all,
I am getting the following error message when loading transaction data to an InfoCube.
***Error from PSA***
This is not MD or Hierarchies (like previous messages in the forum)
Please advise.
Thanks,
Miki

Hi Miki,
Before just loading data into the infocube. Catchup PSA table and see the data into it.
Then u may find the solution.
But as ronald said this shouldnot be the complete error statement.
bye.

**** Error from PSA **** while loading 0comp_code (processing- info obejct)

Hi,
I am getting error **** Error from PSA **** while loading info object attributes for company code (0comp_code). I am not using oly info obejct in processing.
below is the error message.
Error from PSA ****
Error message when processing in the Business Warehouse
Diagnosis
An error occurred in the SAP BW when processing the data. The error is documented in an error message.
System response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Scheduler
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
I checked in SM37 in both source system and BW. I do not see any matches. I have tried loading other master data (for eg. customer) and all were successful. That clearly indicates that connection between ECC and BW systems correct (RFC connection, logical systems etc).
please advise.

Thank you for your answers and points assigned.
I am not using PSA in my data transfers i am using info object only option. I am also getting same error even if I use PSA . no change in error message.
when i click on psa in monitor. i am getting below error message.
-No data packet numbers could be determined for request.
detailed error message: (all are in red color)
Requests (messages): Errors occurred (RED)
      -Data request arranged (GREEN)
     - Error in the data request (RED)
Extraction (messages): Missing messages (RED)
        -Missing message: Request received (YELLOW)
       -Missing message: Number of sent records (YELLOW)
      -Missing message: Selection completed (YELLOW)
Transfer (IDocs and TRFC): Missing messages (RED)
Processing (data packet): No data (RED)
please advise and points will assigned. thanks for your help.

Removal of error from psa

hi friends
can any one tell me how can we remove an error from psa
thanks in advance
with regards
kalyan

Hi,
   Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control the behavior of the BI system if data records with errors occur in the data flow with 3.x objects (use of transfer and update rules) when you are loading data using the PSA.
The system checks for data records with errors:
      in the transfer rules
      in the update rules
      when data is updated to the master data tables, text tables, or hierarchy tables
      when data is updated to the InfoCube
      when checking for referential integrity within an InfoObject against the master data tables or DataStore objects on the communication structure level.
Features
Incorrect records arising in transfer rules, update rules, when updating to a data target, or when checking for referential integrity, are highlighted and returned to the error handler. The error handler locates the original PSA records and writes the corresponding log. This function is not yet available for updating to DataStore objects.
Using the Error Handling function on the Update Parameters tab page in the scheduler, you can control how the system responds to incorrect data records.
Activities
       1.      Define how the system should react to incorrect data records
a.       No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
b.       Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request (using a QM action, that is, by setting the Overall status on the Status tab page in the monitor).
c.       Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
With option a), the incorrect records are marked in red in the PSA maintenance. You can display the relevant error messages amodally, edit the records, and update the request manually. If it was not possible to write to the PSA (hierarchy or transfer method IDoc), an application log is written instead.
With options b) and c), a new request that is only updated to the PSA is formed from the incorrect records. Here you can edit the records of the new request in the PSA and start the update manually.
If errors arise when an InfoCube is updated, new requests are generated for incorrect records for each InfoCube combination. Among these requests, the incorrect records are updated to the PSA. These new requests have entered as data targets the InfoCubes for which there were incorrect records. If, for example, a record was updated to two InfoCubes by mistake, a request is generated for this record that contains both InfoCubes as data targets. In the PSA tree, the requests appear as successfully updated in the PSA. These new requests can then be triggered again for updating to the InfoCubes.
       2.      Specify the maximum number of incorrect data records that are allowed before the system terminates the load process. In the PSA, you can display the errors that have arisen up to that point. If you do not specify the maximum number of incorrect records after which termination should occur, the handling of incorrect data records is inactive and the update terminates after the first error.
       3.      Define how the BI system should react if the number of data records received by the BI system is not the same as the number of data records updated in BI.
A difference between the number of received and updated records can occur:
         in the transfer rules
         in the update rules
         when updating
Records are sorted, aggregated, or added.
If you set the No Aggregation Permitted indicator, the request is deemed incorrect if the number of received records is not the same as the number of updated records.
Regardless of this indicator, an error occurs if the number of selected records is not the same as the number of records received in the BI system.
Result
The monitor directs the user to the relevant error case and enables a direct navigation into the PSA or the respective error request.
If you want to continue processing the incorrect data records in a program that you have written yourself, you can use the method GET_ERRORS of class CL_RSSM_ERROR_HANDLER. The use of this method is documented in the RS_ERRORLOG_EXAMPLE.
To perform complex checks on data records, or to carry out specific changes to data records regularly, you can use delivered function modules (PSA-APIs) to program against a PSA table.
If you want to execute data validation with program support, select Tools ® ABAP Workbench ® Development ® ABAP Editor and create a program.
If you use transfer routines or update routines it may be necessary to read data in the PSA table afterwards.
Employee bonuses are loaded into an InfoCube and sales figures for employees are loaded into a PSA table. If an employees bonus is to be calculated in a routine in the transformation, in accordance with his/her sales, the sales must be read from the PSA table.
       1.      Call up the function module RSSM_API_REQUEST_GET to get a list of requests with request ID for a particular InfoSource of a particular type. You have the option of restricting request output using a time restriction and/or the transfer method.
You must know the request ID, as the request ID is the key that makes managing data records in the PSA possible.
       2.      With the request information received so far, and with the help of the function module, you can
         read RSAR_ODS_API_GET data records from the PSA table
         write RSAR_ODS_API_PUT changed data records in the PSA table.
RSAR_ODS_API_GET
You can call up the function module RSAR_ODS_API_GET with the list of request IDs given by the function module RSSM_API_REQUEST_GET. The function module RSAR_ODS_API_GET no longer recognizes InfoSources on the interface, rather it recognizes the request IDs instead. With the parameter I_T_SELECTIONS, you can restrict reading data records in the PSA table with reference to the fields of the transfer structure. In your program, the selections are filled and transferred to the parameter I_T_SELECTIONS.
The import parameter causes the function module to output the data records in the parameter E_T_DATA. Data output is unstructured, since the function module RSAR_ODS_API_GET works generically, and therefore does not recognize the specific structure of the PSA. You can find information on the field in the PSA table using the parameter E_T_RSFIELDTXT.
RSAR_ODS_API_PUT
After merging or checking and subsequently changing the data, you can write the altered data records into the PSA table with the function module RSAR_ODS_API_PUT. To be able to write request data into the table with the help of this function module, you have to enter the corresponding request ID. The parameter E_T_DATA contains the changed data records.

While loading master data into PSA, the eorror is 'Error from PSA"

Hi All,
While loading master data into PSA, the eorror is 'Error from PSA"
Could you anybody please help in this reagard.
Thanx,
Sridhar.

Hi rakesh,
May be IDOCs not processed completely,
Idoc Problem, Either wait till time out & process Idoc from detail monitor screen, or go to BD87 & process Idoc with status = YELLOW ( be careful while processing IDOCS from BD87, choose only relevant Idocs
Cheers
Raj

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

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

Error while loading the data from PSA to Data Target

Hi to all,
     I'm spacing some error while loading the data to data target.
Error : Record 1 :Value 'Kuldeep Puri Milan Joshi ' (hex. '004B0075006C0064006500650070002000500075007200690
Details:
Requests (messages): Everything OK
Extraction (messages): Everything OK
Transfer (IDocs and TRFC): Errors occurred
      Request IDoc : Application document posted
      Info IDoc 2 : Application document posted
      Info IDoc 1 : Application document posted
      Info IDoc 4 : Application document posted
      Info IDoc 3 : Application document posted
      Data Package 1 : arrived in BW ; Processing : Data records for package 1 selected in PSA - 1 er
Processing (data packet): Errors occurred
      Update PSA ( 2462 Records posted ) : No errors
      Transfer Rules ( 2462 -> 2462 Records ) : No errors
      Update rules ( 2462 -> 2462 Records ) : No errors
      Update ( 0 new / 0 changed ) : Errors occurred
      Processing end : Errors occurred
I'm totally new to this issue. please help to solve this error.
Regards,
Saran

Hi,
I think you are facing an invalid character issue.
This issue can be resolved by correcting the error records in PSA and updating it into the target. For that the first step should be to identify if all the records are there in PSA. You can find out this from checking the Details tab in RSMO, Job log , PSA > sorting records based on status,etc. Once its confirmed force the request to red and delete the particular request from the target cube. Then go to PSA and edit the incorrect records (correcting or blanking out the invalid entries for particular field InfoObject for the incorrect record) and save it. Once all the incorrect records are edited go to RSA1>PSA find the particular request and update to target manually (right click on PSA request > Start update immediately).
I will add the step by step procedure to edit PSA data and update into target (request based).
In your case the error message says Error : Record 1 :Value 'Kuldeep Puri Milan Joshi '. You just need to conver this to Capital letter in PSA and reload.
Edit the field to KULDEEP PURI MILAN JOSHI in PSA and push it to target.
Identifying incorrect records.
System wont show all the incorrect records at the first time itself. You need to search the PSA table manually to find all the incorrect records.
1. First see RSMO > Details > Expand upate rules / processing tabs and you will find some of the error records.
2. Then you can go to PSA and filter using the status of records. Filter all the red requests. This may also wont show the entire incorrect records.
3. Then you can go to PSA and filter using the incorrect records based on the particular field.
4. If this also doesnt work out go to PSA and sort (not filter) the records based on the particular field with incorrect values and it will show all the records. Note down the record numbers and then edit them one by one.
If you want to confirm find the PSA table and search manually."
Also Run the report RS_ERRORLOG_EXAMPLE,By this report you can display all incorrected records of the data & you can also find whether the error occured in PSA or in TRANSFER RULES.
Steps to resolve this
1. Force the request to red in RSMO > Status tab.
2. Delete the request from target.
3. Come to RSMO > top right you can see PSA maintenace button > click and go to PSA .
4.Edit the record
5. Save PSA data.
6. Got to RSA15 > Search by request name > Right click > update the request from PSA to target.
Refer how to Modify PSA Data
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40890eda-1b99-2a10-2d8b-a18b9108fc38
This should solve your problem for now.
As a long term you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW.
RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
Refer
/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
/people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
/people/aaron.wang3/blog/2007/09/03/steps-of-including-one-special-characters-into-permitted-ones-in-bi
http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
For adding Other characters
OSS note #173241 Allowed characters in the BW System
Thanks,
JituK
Edited by: Jitu Krishna on Mar 22, 2008 1:52 PM

Error while re-loading from PSA..!

Hi All,
I have deleted request from Infocube which was aggregated.
I was trying to reload the same request from PSA, i am getting the following error:
SID 163.687 is smaller than Rollup SID of Cube
0PCA_C01; No request posting
Please help me in this..
Regards,
Kiran

Hi Kiran,
You are trying to load a request into the cube, but the aggregates are already rolled up with a request higher/newer than this request. To solve this I think that you need to deactivate the aggregates and afterwards reactivate and roll up new data.
Hope it helps.
BR
Stefan

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 when i am loading data from PSA to ODS

hai Gurus
Very good morning
Actually i am loading data from PSA to ODS.
But when i am loading data i am getting the error InfoObject/BIC/0REFER_DOC does not contain ALPHA -CONFORMING VALUE 0.
Can anybody help me to solve the problem and reload the data
Thanks & Regards
Jayavardhan

Hi,
Lacs of postings are there in this forum on this topic. Searching teh forum is the best option for u now.
With rgds,
Anil Kumar Sharma .P

Error when loading the data from PSA to ODS......

Hi BW guru's,
i am facing one problem while loading the data from PSA to ODS.so please help me in this regard.
Please give a step by step guidelines for me...
the error while loading the data from PSA to ODS is "There are no PSA tables for these selection criteria","An error occurred when reading PSA data".
thanks in advance,
ashok.

hi ashok,
u can push data from psa to ods, for this goto the psa in rsa1>psa>goto that request>rightclick>select " schedule update Immediately ", then data will moved from psa to ods.
or
In ods > delete the failed request>goto the processing tab-->select 3rd option " psa and then subsequentially to data targets ", --> schedule the infopackage.
bye
sunil

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 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 from PSA ****RSAODS

Similar Messages

Maybe you are looking for

* Error from PSA **RSAODS