Selection of Requests in PSA while loading DTP in Full-Mode

Hi all,
i'm using the DataSource 0uc_sales_stats_01 to load data into BW 7.0.
The InfoPackage is manually scheduled.
In older posts, i did not find any solutions.
Problem description:
i can't delete old requests in PSA, because they are needed by other users.
the DataSource is connected with an DSO via transformation.
in the created DTP, i can only choose full extraction mode (delta mode is not supported for this DataSource).
in my workaround i would like to select only the new requests to avoid duplicate loads into my DSO.
but in the endroutine or startroutine, i can not access the PSA request numbers.
also, there is no possibility to select requests in DTP filter...
does anyone know a solution for my problem?
kind regards,
Philipp

hi Philipp,
Its just a thought, just pretend that the old requests are successfully updated to the dso . Next time dtp will not pick those request. If you can find a way to update tables like (rsodsactreq ) with old request and success status,then you can skip those requests next time.
cheers

Similar Messages

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

  • OLD deleted PSA request is being fetched by DTP in load-Very strange

    Hello Friends,
    One week before one delta request was loaded to PSA which was not updated to Target.
    Because of some reason Later we had to delete the INIT after removing all the requests from PSA .tHEN we did init again (for some reason).Then II loaded first delta to PSA.wHEN NOW I am trying to load data from PSA TO CUBE,it is picking up old delta request also which is currently also not available in PSA.This is really strange.
    request is not there in PSA but being extracted by DTP ??
    Any idea ,why it has happened?
    I have thought of a solution for it ..to make the previous delta request RED in infopackage monitor ...then to load the DTP again...But why it;s happening?
    Is it SAp bug or I am missing anything here??
    Thanks

    Correct Ajeet.
    Infact I had checked PSA and then INIT was refreshed.Still how delta request related to previous delta INIT is coming??clueless???
    I had checked already with changing the date in PSA.....no old request is available.it is empty ...
    And Ajeet,
    It is easily visible in DTP monitor to see the request being extracted in load from PSA.
    Any other Idea...we are at SP-17.
    thanks
    Edited by: Baljinder Singh on Aug 10, 2009 1:50 PM

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

  • How to push a perticular request from PSA to Data target using DTP in BI

    Hello all.
      I have mulitple requests in PSA & wanted to move only perticular requests (Randomly,  say first request & last request ) to data target using DTP in BI 7.0. How can we do this.. ? Is there any option in DTP (BI 7.0)for selective loading of requests from PSA to Data Target..
      Thanks in advance..
    Cheers,
    sami.

    Hi,
      It is possible by using 'zero fetch' in DTP
    If you want only the recent req to be loaded.
    1. In PSA, change the status of the recent request to red
    2. Do a zero fetch
    that is processing mode - No data transfer; delta status in source: fetched
    With this processing mode you execute a delta without transferring data.
    3. change the particular request status back to green
    4. Run a delta load
    Regards,
    Priya.D

  • 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

  • Dump while Executing DTP - PSA To ODS

    While executing DTP, I am getting the following ABAP Dump: "MESSAGE_TYPE_X".
    "MESSAGE_TYPE_X" " "
    "SAPLRSSTATMAN" or "LRSSTATMA
    "RSSTATMAN_GET_PARTTAB_PSA"
    I was facing some selection issue in the Info Package (generic Data source), then I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly.
    Now I am facing the issue while loading data from PSA to ODS through DTP. I already activated all the objects again (Data Source, ODS, & DTP).
    Please guide me.
    Thanks in Advance u2026u2026
    Kiruthika

    I tried with Error DTP, I am getting same Dump. When I click Execute button with debug option directly it's going to Dump.
    I am getting the following Error message
    Runtime Errors         MESSAGE_TYPE_X
      keywords:
      "MESSAGE_TYPE_X" " "
      "SAPLRSSTATMAN" or "LRSSTATMA
      "RSSTATMAN_GET_PARTTAB_PSA"
    Information on where terminated
        Termination occurred in the ABAP program "SAPLRSSTATMAN" - in
         "RSSTATMAN_GET_PARTTAB_PSA".
        The main program was "RSAWBN_START ".
        In the source code you have the termination point in line 1165
        of the (Include) program "LRSSTATMANU10".
    I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly. As per my understanding table u201CRSSELDONEu201D is used for info package selection.
    If there any problem related to this, please guide me.
    Regards,
    Kiruthika
    Edited by: kiruthika marappan on Sep 4, 2009 2:16 PM

  • Error while loading into DTP

    Hi,
    I am loading data to a DSO from 0FI_AP_30. PSA I am able to load successfully but while loading this PSA data to DTP i get the following error message:
    @5D@     Request REQU_D44GG0YIPPH7NBQ5F1VOCB890 not extracted; request is in obsolete version of DataSource     @35@
    and in help this is the respose:
    Diagnosis
    The request REQU_D44GG0YIPPH7NBQ5F1VOCB890 was loaded into the PSA table when the DataSource had a different structure to the current one. Incompatible changes have been made to the DataSource since then and the request cannot be extracted with the DTP anymore.
    System Response
    The request is in PSA /BIC/B0001232, version 001. The current PSA version is 002. An extraction would lead to a short dump because of field incompatibilities.
    Procedure
    If you no longer require the data, you do not need to take any further action.
    If you do still require the data, you can just extract it by creating a generic DataSource in the Myself source system in PSA /BIC/B0001232, version 001. You can find the technical name of the PSA table in the table RSTSODS with the specified PSA name and version.  Convert the data using a separate transformation into the new target format.
    Please let me know what can be done for this? pl give me the solution.
    Thanks & Regards,
    Vijaya

    Hi Vijaya,
    I am also facing the same error for data source 2LIS_03_BF, i am unable to load the same in one DSO, can you elaborate how you solved your issue ASAP?
    I can't run IP because this data source requires downtime in ecc. We have already done that.
    Thanks & Regards
    Manna Das

  • BI 7.0 - Error while loading data from R3 to PSA

    Hi,
    I transported Master Data ATTR/TEXT object from DEV to QA (BI 7.0 NW 2004s); and getting the following error while loading the data from R3 in to PSA using the InfoPackage.
    Any clue to resolve this issue is appreciated.
    Monitor - STATUS tab:
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Service API .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    Monitor - Details Tab:
    Extraction (messages): Errors occurred
    Error occurred in the data selection
    Request IDoc : Application document not posted
    Error Message:
    Diagnosis                                                                               
    In the source system, there is no transfer structure available for    
        InfoSource 0ACTIONTYPE_TEXT .                                                                               
    System Response                                                                               
    The data transfer is terminated.                                                                               
    Procedure                                                                               
    In the Administrator Workbench, regenerate from this source system the
        transfer structure for InfoSource 0COMPANY_TEXT .                                                                               
    Thanks,

    Hi,
    Pl try the below
    The l_dta data target that you want to load is an InfoObject (master data or text
    table).
    You must declare this for the InfoProvider in Transaction RSD1.
    You do this on the 'Master Data/Text' tab by assigning any InfoArea to the InfoObject.
    The InfoProvider (that is, this InfoObject) is then displayed below this InfoArea in
    the InfoProvider tree.
    Rregards,
    Senthil

  • 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 Delta request from one ODS to another

    Hi,
    I have 2 ODS . ODS1 is the source ODS and ODS2 is the target ODS. ODS1 has full loads daily
    I have initialised delta from ODS1 to ODS2 and i was loading delta on a daily basis.
    Today while loading from ODS1 to ODS2 it failed. Then i deleted the data from ODS2 (Target ODS) and tried loading again. But it again said 'No delta possible'. So i deleted the full loads from ODS1. But when i load again it says the previous delta is invalidated since the full loads in the ODS1 are deleted. Can anyone of you please let me know how to handle this situation without re-initialising.
    Regards,
    Pramod

    Hi,
    I am not sure if you can go ahead without initializing again.
    I feel you may not have reset the datamart before pulling the repeat delta. This was a mistake. On top of that you have pulled a Full request. It should have been ideally a full repair.
    If you still have that full request in target try converting that into full repair by using this SE38 > RSSM_SET_REPAIR_FULL_FLAG (Change a full request to full repair request )  .
    If it works you have a chance of continuing with your deltas. But you may have lost the last delta.
    If it doesnt work and you have not pulled any delta after that load you have two options to retrieve the delta.
    1. See if its in PSA. then pull from PSA and once done force request to green , next delta should be fine.
    2. If its not there try reset the datamart in source ODS and pulling the delta again.
    If both doesnt work you may need to perform full repair and then reinit.
    Thanks,
    JituK

  • Error while loading from DTP

    Hi,
    We are facing some issue while loading the data from R/3 to BW using DTP.
    We are getting the error (both for full and delta)as follows:
    Data package 1:Errors during Processing
    *     Extraction datasource*
    *     Filter out new records with same key.*
    *     RSDS material*
    *     Update to datastore object*
    *          Unpack data package*
    *          Exception in substep:write data package*
    *          Processing terminated.*
    *     Set technical status to red*
    *     Set overall status to red*
    *     Set overall status to green*
    *     Further processing started*
    *     Set status to u2018Processed furtheru2019*
    The expansion of the error Exception in substep: write data package:
    Record 0, segment 0001 is not in teh cross-record table
    Error while writing error stack
    Record 0, segment 0001 is not in the cross-record table
    Error in substep update to DataStore Object
    We are using both start routine and end routine in the transformation.
    Any help on this is highly appreciable.
    End routine:
        IF NOT RESULT_PACKAGE IS INITIAL.
          SELECT salesorg comp_code FROM /bi0/psalesorg
          INTO TABLE it_salesorg
          FOR ALL ENTRIES IN RESULT_PACKAGE
          WHERE salesorg = RESULT_PACKAGE-SALESORG
          AND objvers = 'A'.
          SELECT /bic/ZMATRTUGP FROM /bic/pZMATRTUGP
          INTO TABLE it_mat
          FOR ALL ENTRIES IN RESULT_PACKAGE
          WHERE /bic/ZMATRTUGP = RESULT_PACKAGE-/bic/ZMATRTUGP.
          it_data[] = RESULT_PACKAGE[].
        ENDIF.
    get company code from salesorg for all material
        LOOP AT it_data INTO st_data.
          w_tabix = sy-tabix.
          READ TABLE it_salesorg INTO st_salesorg
          WITH TABLE KEY salesorg = st_data-salesorg.
          IF sy-subrc = 0.
            st_data-comp_code = st_salesorg-compcode.
            MODIFY it_data FROM st_data INDEX w_tabix.
          ENDIF.
        ENDLOOP.
        REFRESH RESULT_PACKAGE.
        RESULT_PACKAGE[] = it_data[].
    *Finally check for each material if something has changed since the last
    *loading : if yes compare and update, otherwise no upload
        IF NOT it_mat[] IS INITIAL.
          SELECT * FROM /bic/azalomrtu00
          INTO TABLE it_check
          FOR ALL ENTRIES IN it_mat
          WHERE /bic/ZMATRTUGP = it_mat-zmaterial.
        ENDIF.
        DELETE it_check WHERE salesorg IS INITIAL.
        CLEAR st_result_package.
        LOOP AT RESULT_PACKAGE INTO st_RESULT_PACKAGE.
          READ TABLE it_check INTO st_check
          WITH TABLE KEY
          /bic/ZMATRTUGP = st_result_package-/bic/ZMATRTUGP
          CUST_GRP4 = st_result_package-CUST_GRP4
          SALESORG = st_result_package-SALESORG
          VALIDTO = st_result_package-VALIDTO.
          IF sy-subrc = 0.
    *If one of the characteristic is different, let that entry in the
    *result_package otherwise no use updating it
            IF st_check-/BIC/ZCSBRTUGP = st_result_package-/BIC/ZCSBRTUGP
            AND st_check-/BIC/ZCONDTYPE = st_result_package-/BIC/ZCONDTYPE
            AND st_check-comp_code = st_result_package-comp_code
            AND st_check-/BIC/ZCNT_RTU = st_result_package-/bic/ZCNT_RTU
            AND st_check-VALIDFROM = st_result_package-VALIDFROM.
              DELETE RESULT_PACKAGE.
            ELSE.
    *entry is new : let it updated.
            ENDIF.
            DELETE it_check WHERE
                  /bic/ZMATRTUGP = st_result_package-/bic/ZMATRTUGP
          AND CUST_GRP4 = st_result_package-CUST_GRP4
          AND SALESORG = st_result_package-SALESORG
          AND VALIDTO = st_result_package-VALIDTO.
          ENDIF.
        ENDLOOP.
    *if some entries are in the ODS but not in the datapackage, they have to
    *be deleted in the ODS since they don't exist anymore
        LOOP AT it_check INTO st_check.
          CLEAR st_result_package.
          st_result_package-/bic/ZMATRTUGP = st_check-/bic/ZMATRTUGP.
          st_result_package-CUST_GRP4 = st_check-CUST_GRP4.
          st_result_package-SALESORG = st_check-SALESORG.
          st_result_package-VALIDTO = st_check-VALIDTO.
          st_result_package-recordmode = 'D'.
          APPEND st_result_package TO RESULT_PACKAGE.
        ENDLOOP.
    Thanks in advance.
    Thanks,
    Meghana

    Hi Meghana
    HAve you got an short dump in ST22 transaction ?
    If yes, what is it ?
    In your routine, maybe you should as well add a counter for index in your loop :
    DATA : w_idx like sy-tabix.
    When you loop at result_package, do :      w_idx = sy-tabix.
    And make :     DELETE result_package INDEX w_idex.
    Hope it helps you
    Mickael

  • Error while loading from PSA to Cube. RSM2-704 & RSAR -119

    Dear Gurus,
    I have to extract about 1.13 million records from set up tables to the MM cube 0IC_C03. While doing, the following two errors occured while loading from the psa to the cube:
    Error ID - RSM2 & error no. 704: Data records in the PSA were marked for data package 39 . Here there were 2 errors. The system wrote information or warnings for the remaining data records.
    Error ID- RSAR & No. 119: The update delivered the error code 4 .
    (Data records for package 39 selected in PSA - 2 error(s). Record 5129 :No SID found for value 'EMN ' of characteristic 0BASE_UOM . Record 5132 :No SID found for value 'EMN ' of characteristic 0BASE_UOM )
    I tried to change the defective records in psa by deleting the erraneous field value EMN and tried to load but failed.
    Now, my questions are:
    How can I resolve the issue ?
    (ii) How to rectify the erraneous record ? should we only delete the erraneous field value or delete the entire record from the psa.
    (iii) How to delete a record from psa.
    Thanks & regards,
    Sheeja.

    Hi,
    Data records for package 39 selected in PSA - 2 error(s). Record 5129 :No SID found for value 'EMN ' of characteristic 0BASE_UOM . Record 5132 :No SID found for value 'EMN ' of characteristic 0BASE_UOM
    The issue with record no. 5129 and 5132.
    In PSA check errorneous records and it will display only the error records, you just edit as per the require and try reloading into cube.
    Deleting single record is not possible.
    Let us know if you still have any issues.
    Reg
    Pra

  • Error while loading data on 0LIV_DS01 ODS through DTP

    Hi Expert,
                  I am trying to load data on 0LIV_DS01 ODS through 2LIS_06_INV datasource data is comming correctly in PSA
    while i'm trying to load data on ODS through DTP is runing properly till 9th package but at 10th package it showing me error
    like "Exception condition "CTT_NOT_FOUND" raised"
    Error Analysis
    "A RAISE statement in the program "SAPLRSW0" raised the exception
    condition "CTT_NOT_FOUND".
    Since the exception was not intercepted by a superior
    program, processing was terminated."
    please tell me how i rectify the error....
    Thanks and Regards
    Lalit Kumar

    Hi,
    This error has to do something with Currency Conversion.
    While loading from the DSO to the cube, do you have any currency conversions?
    Please look at the below threads:
    Loading error in 0LIV_DS01
    Raise Exception error: CTT_NOT_FOUND
    Hope this helps.
    Regards
    Vishal

  • TSV_TNEW_PAGE_ALLOC_FAILED error while loading the DATA using DTP

    Hi,
    While loading the data using DTP for 2  DSO's we are gettig the error
    TSV_TNEW_PAGE_ALLOC_FAILED
    can any one kindly help me out regarding the same.
    Thank You,
    Poornima.

    Hi Soundarya,
    Thanks a lot for the reply. But i found that its running fine in development, where as coming to quality its throwing an error. These happened for Two DSO's. In both the transformations i have identified that the Transformation names are different from Development and Quality..
    There are no routines written for them and no select statements have been used
    Can you please suggest me regarding the same.
    Edited by: Poornima Gayatri on Mar 22, 2010 7:00 AM

Maybe you are looking for