Erroneous Records reporting from PSA in 3.5

Dear All
I need to build a report which pulls in only the erroneous records from the PSA in 3.5. I have created an export datasource on the PSA but the status field is not in the extract structure. Is this field able to be included as a field in the extract structure as it is does not contain numbers or characters.
if anyone has a different approach to this methodology then please feel free to comment
Any help will do
Regards
Grant

Hi,
this is a very traditional approach.
try to activate an SQL trace before all this.
You can try to select the data from PSA and when you give the filter on errorneuos records and see the values.
Once trace is stopped you can check which tables it hits and then based on that you can create a function moudule which automatically populates the data in the active table of the DSO based on the selections from the PSA table and status field.
I think its feasible with help of a good ABAP.
Thanks
Ajeet

Similar Messages

How to find erroneous records in PSA in BI 7.0

In BW 3.5 if load fails for some reason like lower case or unidentified character data is edited in PSA n loaded from there.
We have an option to check for only erroneous records in PSA separately.
How can that be possible in BI 7,0 because loading will be done till PSA using an infopackage n it will not fail for such reasons.
I cant go check for each record in PSA which is to be edited after DTP failed .
Please explain

HI,
Below link exactly answers you Q
WHAT IS ERROR HANDLING OPTIONS IN dtp? FOR DSO
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fbd598481e1a61e10000000a422035/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/42/fa50e40f501a77e10000000a422035/frameset.htm
Cheers,
Swapna.G

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.

Is there a way to notify/alert users about records from PSA

Hi All,
During transaction data load in BW 3.5 I am using the option" No update of transaction data if Master data does not exist" in the Infopackage.
If any records don't meet this criteria they will show in different Request in PSA.
My question: Is there a way to notify/alert users about these records from PSA?.
Through process chain we can't send any alerts in this case as loads will not fail.
Please help.
Thank you.
Sree

Brian, Accepeted. We can not create Infoset on PSA.
To create report on PSA, follow this.
https://websmp104.sap-ag.de/~sapidb/011000358700008145112002
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
/message/5239445#5239445 [original link is broken]
Thanks...
Shambhu

Full update not getting all records from PSA to ODS

Dear BW Masters,
I am working with MM module. Iam using standard extract structure 2LIS_02_ACC
Iam doing full update. Getting full data 1300 records in to PSA. But getting only 298 in to my ODS. I tried changing fields in to KEY FIELDS AND IN TO DATA FIELDS in my ODS
But could not get data.
Pls help me..i have dead line before that i need to complete report on the same.
Its happening with the other HDR and ITM extractors.
PLs help me..

Hello,
Look at this example:
R/3 Record:
CustNo | Name | Order | Amount
1234 | Customer1 | Order 1 | 100
1235 | Customer2 | Order 2 | 200
1234 | Customer1 | Order 3 | 300
If Cust.No is Keyfield, In BW you will get 2 records
1234
1235
If Order No is Key field, you will get 3 records.
It is not necessary to get the same no of records as they are in R/3.

Erroneous records in PSA

Hi All,
How to handle erroneous records in PSA. Should I consult R/3 consultants to correct them...

Hi,
this depends on the type of error.
Conversion errors and similar things can be corrected in the transfer rules, real data errors needs to be corrected in the source system itself and so normally by the responsible r/3 guy.
regards
Siggi

Removed Records: PivotTable report from /xl/pivotTables/pivotTable1.xml part (PivotTable view)

I keep getting an error in Excel 2013 when using PowerPivot. Can someone please explain to me what this error means? I can't see that there is anything wrong with the underlying data, and the list of "removed data" is empty too...
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"><logFileName>error085600_01.xml</logFileName><summary>Errors were detected in file 'E:\SkyDrive\Documents\Forex\Greenzone_Stats\Greenzone_2013_v2.xlsx'</summary><removedRecords summary="Following is a list of removed records:"><removedRecord>Removed Records: PivotTable report from /xl/pivotTables/pivotTable1.xml part (PivotTable view)</removedRecord></removedRecords></recoveryLog>
TIA!
Dennis

Turns out it's a resource limitation in Excels chart rendering engine. If I filter the data model so that less rows are included in the PivotChart, the error goes away.
Re
Dennis

Deleting records from PSA

Hi,
Can anyone tell me how to delete the errorneous records from psa table. i have abt 24 data packets each have abt 23000 records.
the error is the dta package 23 and 24.
regards,
nithesh
Edited by: nithesh prakash on Sep 16, 2008 7:56 AM

Hi.,
Another thing........why your data oacket failed.......is your extraction got completed...........
If your data packets failed due to SID issue...........then you load the master data....delete the request without making it red from the target ............go to RSA1 >> click on PSA >> find the request and reconstruct it.........
Otherwise if you extraction is completed............do manual update.......ie right click on data packet >> do manual update.........before that make the settings background.........otherwise in foreground it will take long time..................
Hope this helps you...........
Regards,
Debjani.......

How to pass record Group from Forms with DATA_PARAMETER to Reports Server

How to pass record Group from Forms with DATA_PARAMETER to Reports Server using RUN_REPORT_OBJECT?
When we use products on run time we are using data_parameter for passing record Groups to reports via run_product but now we have to use application server and reports server for same reports.
We met with <FRM-41214 Unable to run reports> for passing DATA_PARAMETER to reports server when used RUN_REPORTS_OBJECT.
How can we pass record Group from Forms with DATA_PARAMETER to Reports Server using RUN_REPORT_OBJECT?
Thanks,
Arif

Hi Mandeep,
Could you please tell me how can i pass data parameter from forms to report through run_product.

Can we delete error records from PSA

Hi,
I am loading data from Myself source system to Infocube. I have 10 Laks records. Out of these 10 Lakhs records, only 2 error records were there. Due to this load failed. suppose I have 100 data packets, these two records is there in 98 data packet Now only 98th Data packet is showing RED in Details tab. So Now I want to use the data which is loaded into cube except the Data packet 98. Now my question is , If I change this request in INFOCUBE as GREEN , Can I see the data for records except 2 error records (Data Packet 98). Bcz, I dont have time to load this again. This is Quality system.
Or Can I modify those 2 records without deleting the request from the Infocube.
Please suggest me how to proceed.
Thanks in Advance,
Shivaram

Hi,
You cannot delete records from the PSA but you can edit the records in the PSA but for that you have to delete the request from the Cube. Then after editing the records in the PSA you have to load the records into the Cube by running the infopackage.
Otherwise you have to create a Error Stack from the Update mode and then you can load the records into the Cube without that records. The Error Stack will hold the incorrect records which you can edit later
But overall you have to delete the failed request from the Cube and then load it again for moving it to next target or for reporting

Data in cube is different from psa in the production system

hi friends
this is very urjent ,the data is fine and same as r/3 in psa.for example i have sales for one article ie billing
2lis_13_vditm . which picked the data from r/3 when i see the records in the psa they r good when tried to see the same record in cube record is not avalible in the cube . only few records are filtered out inbetween psa to cube which is leading to lot of data inconsistency . they r no routines which can filter out the data . only standard sap routines .which updates the data to cube . what could be the problem . any help is apperciated and helpful and will be rewarded. thanks in advance for kind replays.

veda,
In a cube the data gets added up for similar records -
Do you have the same number of records in PSA and Cube ?
if yes - then maybe there exist similar records and the KF is getting summed up in the result.
Also how did you search for the same record in the cube ? since the characteristics go into the dim tables and all that is in the fact table is only dim ids and KFs ...
Do one thing - can you try a report on the cube and check if the data is getting summed up.
Or another workaround - put the PSA Data into an Excel file ( flat file ) and then upload it into an ODS with the same records in Production - you will know if multiple records exits and thereby find out what the problem is due to. ( Bad workaround - but cannot do it in Production)
Arun

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

Duplicate records in BW / PSA

Hello all,
I want to load information about equipment from R/3 into BW. The equipments were migrated from another system into R/3.
Now, the load fails because there are some records which are duplicated (I can see all the records in the PSA table for the equipment).
The key in BW for the records is composed of EQUNR and DATETO - so, there is a equipment twice but with the same DATETO.
So, now I want to write a report which shows only those equipments that are duplicated in the PSA table.
I coded the following:
data : itab type standard table of /BIC/B0000333000 with header line,
itab1 type standard table of /BIC/B0000333000 with header line.
select * from /BIC/B0000333000 into table itab1.
SELECT EQUNR DATETO
INTO corresponding fields of table itab
FROM /BIC/B0000333000
GROUP BY EQUNR DATETO
HAVING COUNT( * ) > 1.
loop at itab.
loop at itab1 where EQUNR = itab-EQUNR
and DATETO = itab-DATETO.
WRITE: / itab-equnr.
endloop.
endloop.
The report executes but doesn't show anything.
Am I missing something or what am I doing wrong?
Kind regards,
Tudor

Hi Anjali,
If you removed Alpha conversion then probably your problem may be solved by implementing OSS Note 486888 "Termination when data is loaded (RSAR196)".
Look at the similiar topic and try to implement proposed solution:
Alpha Conversion
Best regards,
Eugene

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.

Erroneous Records reporting from PSA in 3.5

Similar Messages

Maybe you are looking for