Source system in PSA deletion variant

Dear Experts
In process chain PSA deletion variant,in source system column I will give the Development source system name(C6D),and after transport to the Quality styem(C6Q) Should I change this source system manually in qualtiy or system automatically will pick up the corresponding source system name?If not,what is the possible solution since we dont have any access in quality system.
Cheers
Rajesh

Thanks for the reply.I got doubt because in DEV we have to enter manually both DS  and SOURCE SYSTEM manually...after importing to Quality will it change the source system name?...Can i take for grant...Pls confirm....
Rajesh

Similar Messages

  • DataSource extraction very slow ( from Source System to PSA it takes 23 hrs

    Friends,
    We have enhanced the datasource 0CRM_SALES_ORDER_I with the user exit....after the enhancement i.e (adding the new fields and wrote some coding to enhance ...) the data extraction takes place for around 23 hours. there is approximately 2,50,000 records.
    Can you please suggest any steps to tune up the performance of the datasource.
    NOTE: Data Extraction from source system to PSA alone takes 23 hrs.once the data is arrived in PSA then the loading of data to cube is fast.
    PLZ help me to solve this issue.
    BASKAR

    Hi Friends,
    This is the code used for the datasource enhancement.(EXIT_SAPLRSAP_001)
    DATA : IS_CRMT_BW_SALES_ORDER_I LIKE CRMT_BW_SALES_ORDER_I.
    DATA:  MKT_ATTR TYPE STANDARD TABLE OF  CRMT_BW_SALES_ORDER_I.
    DATA: L_TABIX TYPE I.
    DATA: LT_LINK TYPE STANDARD TABLE OF CRMD_LINK,
          LS_LINK TYPE CRMD_LINK.
    DATA: LT_PARTNER TYPE STANDARD TABLE OF CRMD_PARTNER,
          LS_PARTNER TYPE CRMD_PARTNER.
    DATA: LT_BUT000 TYPE STANDARD TABLE OF BUT000,
          LS_BUT000 TYPE BUT000.
    DATA: GUID TYPE CRMT_OBJECT_GUID.
    DATA: GUID1 TYPE CRMT_OBJECT_GUID_TAB.
    DATA: ET_PARTNER TYPE CRMT_PARTNER_EXTERNAL_WRKT,
          ES_PARTNER TYPE CRMT_PARTNER_EXTERNAL_WRK.
    TYPES: BEGIN OF M_BINARY,
           OBJGUID_A_SEL TYPE CRMT_OBJECT_GUID,
            END OF M_BINARY.
    DATA: IT_BINARY TYPE STANDARD TABLE OF M_BINARY,
          WA_BINARY TYPE M_BINARY.
    TYPES : BEGIN OF M_COUPON,
             OFRCODE TYPE CRM_MKTPL_OFRCODE,
             END OF M_COUPON.
    DATA: IT_COUPON TYPE STANDARD TABLE OF M_COUPON,
          WA_COUPON TYPE M_COUPON.
    DATA: CAMPAIGN_ID TYPE CGPL_EXTID.
    TYPES : BEGIN OF M_ITEM,
             GUID TYPE CRMT_OBJECT_GUID,
            END OF M_ITEM.
    DATA: IT_ITEM TYPE STANDARD TABLE OF M_ITEM,
          WA_ITEM TYPE M_ITEM.
    TYPES : BEGIN OF M_PRICE,
                  KSCHL TYPE PRCT_COND_TYPE,
                  KWERT  TYPE PRCT_COND_VALUE,
                  KBETR   TYPE PRCT_COND_RATE,
            END OF M_PRICE.
    DATA: IT_PRICE TYPE STANDARD TABLE OF M_PRICE,
          WA_PRICE TYPE M_PRICE.
    DATA: PRODUCT_GUID TYPE COMT_PRODUCT_GUID.
    TYPES : BEGIN OF M_FRAGMENT,
             PRODUCT_GUID TYPE COMT_PRODUCT_GUID,
             FRAGMENT_GUID TYPE COMT_FRG_GUID,
             FRAGMENT_TYPE TYPE COMT_FRGTYPE_GUID,
           END OF M_FRAGMENT.
    DATA: IT_FRAGMENT TYPE STANDARD TABLE OF M_FRAGMENT,
          WA_FRAGMENT TYPE M_FRAGMENT.
    TYPES : BEGIN OF M_UCORD,
          PRODUCT_GUID TYPE     COMT_PRODUCT_GUID,
          FRAGMENT_TYPE     TYPE COMT_FRGTYPE_GUID,
          ZZ0010 TYPE     Z1YEARPLAN,
            ZZ0011 TYPE Z6YAERPLAN_1,
            ZZ0012 TYPE Z11YEARPLAN,
            ZZ0013 TYPE Z16YEARPLAN,
            ZZ0014 TYPE Z21YEARPLAN,
         END OF M_UCORD.
    DATA: IT_UCORD TYPE STANDARD TABLE OF M_UCORD,
          WA_UCORD TYPE M_UCORD.
    DATA: IT_CATEGORY TYPE STANDARD TABLE OF COMM_PRPRDCATR,
          WA_CATEGORY TYPE COMM_PRPRDCATR.
    DATA: IT_CATEGORY_MASTER TYPE STANDARD TABLE OF ZPROD_CATEGORY ,
          WA_CATEGORY_MASTER TYPE ZPROD_CATEGORY .
    types : begin of st_final,
               OBJGUID_B_SEL  TYPE CRMT_OBJECT_GUID,
               OFRCODE TYPE CRM_MKTPL_OFRCODE,
               PRODJ_ID TYPE CGPL_GUID16,
               OBJGUID_A_SEL type     CRMT_OBJECT_GUID,
              end of st_final.
    data : t_final1 type  standard table of st_final.
    data : w_final1 type  st_final.
    SELECT  bOBJGUID_B_SEL aOFRCODE  aPROJECT_GUID bOBJGUID_A_SEL  INTO table t_final1 FROM
       CRMD_MKTPL_COUP as a  inner join CRMD_BRELVONAE as b on  bOBJGUID_A_SEL = aPROJECT_GUID .

  • /BIC/ namespace not modifiable, can't create PSA delete variant in process

    Hello,
    When I attempt to create a PSA delete process in a process chain, I get an error message as such:
    Namespace '/BIC/' must be set to 'changeable' (transaction SE06)
    Message no. R7063
    I have had Basis dot his for me before and it worked, but it takes a lot of change menagement to do this.  I have asked Basis to leave it modifiable in SE06, but they will not.  Is that the only way to be able to create PSA process variants is to have Basis use SE06?  I looked in Object Changeability, but nothing stuck out.  I should not have to have Basis do this task every time.  Please let me know if there is a better way.
    Thank you.
    Brent

    Hi Brent
    I believe /BIC/ namespace should remain modifiable where you are creating PSA deletion process.
    You can check if that is the case in your system.
    Check in TRNSPACE table with namespace /BIC/  .. changagle flag should be X. I think it should be in your production also
    Regards
    Anindya
    Edited by: Anindya Bose on Mar 8, 2012 4:52 AM

  • Doesn't load from source system to PSA and DSO

    Hi Gurus,
    We have launched a Delta load from Source System (POSDM) to DSO. In the source system there are 5000000 rows but none was loaded into DSO or PSA. The delta load was ok, but any data was loaded.
    If the delta  load was lunch again, would be loaded those 5000000 rows. Or those 5000000 rows wouldn't be able to load again.
    Any idea abut this issue? Any feedback will be really appreciated.
    Thanks in advance.

    Hi David,
    Are you sure this 5 million records are delta records and should be pulled into BW as delta??
    did you count the number of records in the underlying tables??
    which data source you are using??
    Delta loads are suppose to bring the new records or changed records since the last data load and not all the records.
    Since the request is green as you said and still it shows 0 records then it is possible that nothing has changed since last delta.try to see the details of the data load... if it failed...may be thats the reason you are not able to see any records.
    If you schedule the delta again it will bring the records changed or created after last delta.
    If the delta was unsuccessfull then turn the QM status and overall status of request to red manually in the monitor of the request and delete it from PSA and all the targets in which its loaded and schedule the delta again and it should bring the delta.
    Thanks
    Ajeet
    Thanks
    Ajeet

  • Error in the source system for fiscal year variant K4 Period 00

    We are experiencing the following issue when loading data from module Flexible real estate RE-FX CASHFLOW CUBE OREFX_C06 Error in source system Fiscal year variant K4 is not defined for the period 00.

    Hi,
    You need to check in your source whether you have maintained Fiscal Yr Variant or not? Talk to you Functional person before you do the BI Extraction.
    In Table T009B
    You can check Fields
    MANDAT - client
    PERIV - Fiscal Year Variant
    BDATJ - Posting date YYYY
    BUMON - Posting date calendar month
    Check Table T009B and see if you fiscal variant is maintained for all periods of Years (as per error its not). maintain the same in Source system and transfer Global settings in BW to copy the same into BW system.
    @AK

  • PSA deletion variant - Syntax error in program "SAPLRS_PSA_DEL_GUI

    Hi.
    Recently, we have implemented the note 1357168 to overcome the error "Object name &1 after the prefix has to start with ABC...XYZ".
    But after that if we maintain any PSA/Change log variant we are getting the below error Syntax error in program "SAPLRS_PSA_DEL_GUI.
    We have identified the class CL_RS_PSA_DEL_MASS_DELETION for that. but not able to figure it out what is the issue.
    please help.

    check this
    Note 1388321 - 7.01SP6:Short dump in maintaining PSA deletion variant

  • PSA Deletion variant in Process chain

    When I add more than one PSA tables in one process step of Process chain would the deletion happen sequentially or parallelly?
    In other words, if I have some 20 PSA tables to be deleted, can I put all of them in one step or should I put them in different steps - some 4 or 5 steps - to reduce load on system? (I need to keep only 2 days data in each table).

    Hi,
    it will happen sequentially. You can put them in one process step.
    However, I recommend to include the PSA deletion systematically in each corresponding chain since you can control it and monitor it better.
    hope this helps...
    Olivier.
    Message was edited by:
            Olivier Cora

  • Understanding the data transfer from source system to PSA

    hi experts,
    i an new to BI. i have created a transactional data source for VBAK table and replicated that to BI. Created transformations and info package for uploading the data into PSA. i just want to know the sequence of steps that the system executes when we run the infopackage. i know that it makes a rfc call to source and brings the data back to BI. i want to where that RFC call happens and what is the RFC FM name etc.,. I tried to debug the process using /h, but as you know, it is very difficult to debug the whole standard code. it is very complex. i got lost some where in the middle. if anybody has any idea / or done any research on this ,please share your findings.
    thanks

    Hi,
    Once you click on Start buton in Infopackage,
    1. BW system wil send on erequest to ECC along with DataSource details.
    2. Based on BW request ECC will respond and it will send message OK and starts extraction.
    3. Based on InfoPackage selection the Data will executes in ECC and picks the data in Packets.
    4. And ECC will send the data in teh form of Datapackets to BW (Idocs)
    5. Once the selection creatiro is over the Job will finish.
    6. You can see the data in BW
    Thanks
    Reddy

  • Delete source system fails

    I've got a flat file source system definition which I deleted via rsa1 --> source system --> right-click --> delete.  it deleted all the dependant objects (transfer rules, psa, EDI config, etc), but the system still shows up in RSA1.  There's an entry in table RSBASIDOC referencing this source system (field SLOGSYS), because we manually tried creating a basic idoc type for it (which we now can't delete with tcode WE20 since it's been generated).
    Does anyone know off hand how to get rid of the source system in the RSA1 list?
    Thanks!
    Rich

    Hi Rich -
       I guess the SAP Note (967999) applies in your case. I've pasted it below for your reference.
    Symptom
    In the source system tree of the Administrator Workbench (AWB), you use the 'Delete' function in the context menu (right mouse button) for a connected source system.
    Even though the system displays success message RSAR 262:
    Source system & deleted
    at the end in the status line, the source system connection is visible again after the AWB has been updated and the source system connection has not been deleted.
    Other terms
    Context menu, source system tree, right mouse button, delete source system, RSAR, 262, 620, SLG1, RSAR262, RSAR620, AdminWorkbench
    Reason and Prerequisites
    This problem is caused by a program error.
    An error occurs during the deletion, however the system does not inform you correctly of this at the end, after the deletion process has terminated.
    Solution
    BW 3.0B
    Import Support Package 33 for 3.0B (BW 3.0B Patch 33 or SAPKW30B33) into your BW system. The Support Package is available onceNote 914950 "SAPBWNews BW 3.0B Support Package 33", which describes this Support Package in more detail, has been released for customers.
    BW 3.10 Content
    Import Support Package 27 for 3.10 (BW 3.10 Patch 27 or SAPKW31027) into your BW system. The Support Package is available onceNote 935963 "SAPBWNews BW 3.1 Content Support Package 27", which describes this Support Package in more detail, has been released for customers.
    BW 3.50
    Import Support Package 19 for 3.5 (BW3.50 Patch 19 or SAPKW35019) into your BW system. The Support Package is available once Note 928662 "SAPBWNews BW Support Package19 NetWeaver'04 Stack 19", which describes this Support Package in more detail, has been released for customers.
    BW 7.0
    Import Support Package 10 for 7.0 (BW7.0 Patch10 or SAPKW70010) into your BW system. The Support Package is available once Note 914304 "SAPBWNews BW 7.0 Support Package 10", which describes this Support Package in more detail, has been released for customers.
    To provide information in advance, the note(s) mentioned above may already be available before the Support Package(s) is/are released. In this case, the short text of the note still contains the words "Preliminary version".
    Pls assign points if helpful.

  • PSA deleition variant issue for the BW data source 80CUST_SALEST

    Hi all,
    I am trying to create a PSA deletion variant for the datasource 80CUST_SALEST, It is a BW Export Datasource,
    We are in BI EHP1 7.01 SP3,  I am getting a error like "Object name 0CUST_SALEST after the prefix
    start with ABC...XYZ". it is not allowing me to save the PSA variant.
    I also had a similar type of issue when creation for 1_COPA Datasources which was resolved by the OSS 1309619.
    Can you please suggest me or advice me of any OSS notes/remedies for this issue.

    can't you create the variant referring to the infopackage instead of the psa table?
    M.

  • Deletion of Source system

    Hello,
    I need help in deleting any links that exist for an old R3 system. We have migrated our source R3 system which was called SP1 to another system called SP2. Now we have datasources, DTP and update rules pertaining to the old system that we would like to delete. I tested out an option to delete the source system in the workbench by clicking under  the Source system , choosing the one I wished to delete and right clicking on that and choosing Delete. I got a warning saying that its not possible to delete because the RFC connections are no longer available, which is true. I chose Ignore in the message window that popped up and that led to all the datasources, DTP and infopackages getting deleted. This seems too good to be true that we got rid of all links to the old system . What I am wondering is whether this method causes some other important data to vanish as well. Is there also a better way to delete all links to the old system.
    Regards,
    Jaya

    Hi Jaya
    As you said there is no connectivity with the source system, then you are no more using the Datasources from that source system.
    Ensure that you are not using the datasources in your regulary used Infosources.
    If you are using then they me be set to inactive.
    As you said youa re not at all using that source system you can delete that.
    Regards
    PBI

  • Source system deletion

    Hi ,
    We have two R/3 systems as Source systems for our BW.
    Right now,both are in a postion to give data for lot of Data targets.
    And now, we are planing to drop one source system.
    So, kindly give me an idea about the steps to be followed
    to make sure that there will be no problems after dropping
    (like Metadata inconsistency...etc) .
    Kindly provide few notes on this issuse also.
    With rgds,
    Anil Kumar Sharma .P

    Hi Anil!
      i think first you got to remove all the source system assignments for all the InfoSources with this particular source system by deleting transfer rules.  one more thing is about logical system dependency of your data, i mean if there is any data which has 0logsys compounded and the data is loaded from this source system. then determine what you are going to do with this data and how you are going to refer it in future.
    and once you are sure there is no link between this source system and BW. you can then delete this source system by justselecting delete in the context menu of this source system.

  • DELETE SOURCE SYSTEM FORCEFULLY

    Hi Experts,
               I am working on BW 3.5 had a r/3 source system which has been formatted recently now when i am trying to delete this source system (while going traough RSA1->source system right click delete) it says "deleting source system failed".i ckecked through t.code sm21 "source system BIWDEV not known.i have also tried to delete it through FM RSAP_BIW_DISCONNECT and RSAR_LOGICAL_SYSTEM_DELTE but nothing is working.There is entry of this source system in RSBASIDOC table.Please help.
    Sanjeev

    Hi,
    try deleting first this pertner profiles with tcode WE20 and then delete the source system....
    if this system is not up anymore then delete the part profiles, and the RFC connection
    caution; you'll loose all TRules connected to this source system...
    hope this helps...
    Olivier.

  • Problem with PSA deletion

    Hi All,
    My requirement is to delete all PSA requests everyday before daily loads. For this i have created a PC with PSA deletion variant with the followng settings - data-source = 0CO_PC_02, source system = *, older than = 0 days, all requests (red and green). When the variant is run no requests are deleted, even if there are requests meeting the above conditions. Logs of the variant do not show any requests.  When i delete the requests manually from the Data-Source overview screen the requests are deleted but i can still see the request in the PSA table (se16). What could be the reason. The scenario works fine for other data-sources and variants with identical settings. Thanks.
    Regards,
    Saurabh Diwakar

    Hi,
    Please specify only these three things nothing else . This should do the job for you .
    Data Source name
    exact Name of the Source System with client Name
    In older than put 0.
    -Vikram

  • Disconnet a Source system from RSA1

    Hi!
    I changed all the neccessary BW objects from one SAP ECC system to another one in my SAP BW system via tcode BDLS (e.g. EC1CLNT500 --> EC2CLNT500).
    Now I would like to delete the old entry of EC1CLNT500 in RSA1 --> source systems.
    When I do so I get the following error:
    Source system cannot be deleted in Content system
    Message no. RSAR670
    Diagnosis
    If a source system is deleted in the Content system, the shadow tables
    for all source system-dependent objects for this source system release are also deleted. You can configure a user as a non-Content user by using a SET-GET parameter. You can then use this user to delete the system, and then the above-named objects are not changed duringdeletion.
    System Response
    The function is completed.
    Procedure
    Logon as user ACTIVATE, and repeat your actions.
    Can some one tell me how to proceed here?
    regards
    Jürgen

    Hi!
    The table RSBASIDOC does not have the entry for new SAP BW system that I would like to disconnect.
    Only the value of the old SAP BW system is there...
    How to proceed?
    Thank you!

Maybe you are looking for