Error in PSA

Hi
While loading the Attributes, I get the following error:
CostcentX: Data record XXX (1000EI300E) :Duplicate data record.
Everything looks apparently alright. I am unable to understand the error and also how to correct the same. Any lead would be appreciated.

You should not load duplicate records when loading master data. You have two options -
1) Work with your process teams and understand why there are two records for a given master data object value and eliminate it in the source system.
2) In the infopackage, you have the option, LOAD TO PSA -> UPDATE FURTHER DATATARGETS and IGNORE DUPLICATE RECORDS. Check these two options and this will eliminate the error.
Hope this helps.

Similar Messages

  • Error in PSA with special characters

    Hello,
    I'm having a problem with sprecial characters in PRD system.
    This happen with standard extractor for Confirmations in SRM module, 0BBP_TD_CONF_1.
    I have 5 records with error in PSA. The field that have the error is 0bbp_delref and it has the text: “GUIA ENTREGA Nº2”.
    The error message says that field OBBP_DELREF has special characters that are not supported by BW.
    The field is char 16 and in spro I have the characters:
    QWERTYUIOPASDFGHJKLǪNºZXCVBM/~^´`* '()"#$%&!?.-0123456789«»<>
    In QUA, I created confirmations with this text and it worked fine and the characters in SPRO are the same.
    Any idea?
    Thanks and best regards,
    Maria

    Hi Maria,
    There will be no issue with update rules as the issue is with Data..
    ALL_CAPITAL should resolve your issue, .otherwise try individually executing those spl characters in RSKC..
    have you tried in SPRO...
    Check in this table RSALLOWEDCHAR in SE11 and find what all characters allowed(permitted)  in PRD system...
    please go through the above mentioned blog once
    Thanks,
    Sudhakar.

  • "****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.

  • Error in PSA Update

    Hi,
    I have this error in PSA Udate:
    msg: "Time conversion from 0CALDAY to 0FISCPER (fiscal year ) failed with value 20070530"
    I have 10 records in PSA . 9 are ok. 1 record shows this error. 3 other records also have 0CALDAY = 20070530 as value. But, they did not return errors.
    Why this particular record error ?
    Thanks in advance

    Hi Raj,
    check this links:
    Time conversion from u0085.Any help on this error in the PSA?
    Re: Inventory Management extraction.
    hope this helps
    cheers
    Sunil

  • Errors In PSA

    Hi All
    I am getting errors in PSA when Loading Master data
    The errors are
    1.ZACTPAR : Data record 77 ('000300000089 '): 
      Version 'Rebserve FM ' is not valid     RSDMD     194
    2.Value 'Rebserve FM ' for characteristic ZACTPAR 
      contains invalid characters     RRSV     7
    Can some body tell me what the prob is and how to solve it
    Regards
    Vasu

    Hi Vasu
    You can see this erroraneous value in PSA maintenance RSA1-> PSA and here select your requst and edit PSA.
    Please check if the value 'Rebserve FM' is not valid value for your characteristic ZACTPAR. You can get change this value in PSA and then re-load. Prior to this discuss this with R/3 people and get confirmation of this value.
    If this issue is with invalid characters (hash like wired characters) then refer to this thread
    Re: Regarding Special Characters
    Hope this helps
    Regards
    Pradip

  • 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 employee’s 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.

  • Unknown error in PSA

    Hi All,
    can anyone tell me reason for this error to occur while loading from ODS to cube and the way to correct the below mentioned error in PSA...
    "Record 0 :Error in a formula function (routine ROUTINE_0002 ), record 0 "?
    Thanks for your quick reply.
    NAV

    Hi NAV,
    It seems the error is in the routine you have written in the transfer rules or update rules. Check the Routines u have written first.
    It may solve the problem..
    Thanks,
    Phani

  • *** 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

  • 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

  • Getting  error in PSA while trying to load data in cube

    Dear Friends,
    I am trying to load data in cube I am getting error in PISA i.e.
         Value 'Boroplus Anticream 19Gm Regular Plain ' (hex. '426F726F706C757320416E7469637265616D203139476D2052') of characteristic .
    please guide me.
    Thanks in Advance.
    Best Regards
    Rafeeq

    <i>Value 'Boroplus Anticream 19Gm Regular Plain ' (hex. '426F726F706C757320416E7469637265616D203139476D2052') of characteristic .</i>
    Your data is in lowercase.. either change the data to UPPERCASE from source..
    or delete the request in cube and edit PSA data from lowecase to UPPER CASE if they are few records only.
    or make the infoobject setting lowecase checked,
    Regards
    Manga(Assign points if it helps!!)

  • ERROR IN PSA LEVEL

    *Hi Experts,*
    *This is kalyan and i am facing a issue in BI 7.20 VER from past 1 week am not able to solve.*
    *this issue is process chain scheduled daily basis and process chain getting failed failed from 01-01-2011 to till date*
    *but records available in psa level but not reached target then when i try to do schedule manullay but*
    *in data target tab it is not showing target.i have tried with process manually this option available ipsa under header tab*
    *when i choose that option it is showing this error SID 1334 is smaller than /equal to update SID of DTA ZSD_BLCO3/47287;Canceled please help me in this issue if one knows and what will be solution.*
    *Thanks In Advance,*
    *Kalyan*

    Hi
    As you told this is running in Process chain. Do you have "Update from PSA" step after this IP is completed.
    check the job log of IP load in SM37, check the error log in Job.
    If you don't have Update from PSA step in PC, include it in your PC or make the changes to IP ( change the option to  PSA and then data target in series in update tab)
    Regards,
    Venkatesh

  • Conversion error in PSA

    Hi
    I am trying to load data from R/3 and i get some erroreneous records in the PSA. The error message says: Error: Conversion foreign curr. -> local curr.: 0020000072 20071218 EUR -> INR
    I checked the records in PSA and the only currency values that i have in PSA is Local Currency an d Stat. Curr. and both of them are INR and there are no other currency values there. I tried this for the cube 0SD_C03 and the datasource is 2lis_11_vaitm and 2lis_11_v_itm. I tried simulating the update but couldnt find anything.
    The requests have turned red because of this. I am unable to find what the problem is. Please help.
    Regards
    Sujai

    Hi Sujai
    In BI7.0 Enviroment, you can also correct your error records in Error stack and SAVE those records
    Now in the DTP Update tab, you have another option called "Create Error DTP", While creating & executing the error DTP,it will load the corrected records in the previous request.
    Hope now you will be clear
    Regards
    Saravanan.ar

  • Error In PSA cleanup

    Hi,
    Data inconsistency; Partition /BIC/B0000940000 not deleted
    Regards,
    Narasa.

    Hi,
    Go to RSRV - All elementary test - PSA table- double click over there and enter the /BIC/B00004240000 name and execute it.. It will show the error message and then correct it by executing the icon called 'correct error'
    Or u can do the other alternative:
    Goto SE38 -> RSAR_PSA_CLEANUP_DIRECTORY and execute. It will repair the PSA Directory if there is any inconsistency and corrects it.
    Some times the SAP system will lock the entries which will give the issues when u do the clean up... so u can wait for some time and then try deleting it if the bove solutions didnt work fine for u..
    Thanks
    Assign points if this helps

  • Error in psa  quality system

    hi all,
    i am getting the problem with psa. 2 records i am getting worng. loading the data from r/3 system.
    Record 181 :0IOBJSV : Data record 181 ('0CorD '): Version '0Cor ' is not valid
    Record 182 :0IOBJSV : Data record 182 ('0CorE '): Version '0Cor ' is not valid
    regards
    kk

    We had this problem in a test. I found SAP Note: 1075643. It doesn't read as though it is going to help, but if you go to the table, you will see that Cor is being changed to CRO.
    At the time of writing, I am waiting for this note to be applied to the source system by the basis team. However rather than go to the trouble of changing the psa data (every time a full load is done) you can change the root cause of the problem.
    It is real estate related so not everyone gets this.
    Here is the note content:
    Symptom
    The three figure value for the object type 'J2' (correction object) will be renamed for the language key 'EN' as 'CRO', as the old value leads to problems (duplicate records) with the DataSource 0IOBJSV_TEXT.
    Reason and Prerequisites
    This problem is caused by a design error.
    Solution
    The correction is delivered by Support Package.
    To implement the correction in advance use the table view maintenance (SM30) in the table TBO01 to change the value OBART_LD to "CRO" for the key SPRAS = "EN", OBART = "J2".

Maybe you are looking for