Source system- customizing extractors

http://help.sap.com/saphelp_nw04/helpdata/en/7a/27bcf087c7464db8b95eaa717b6e6a/content.htm
In the above link when I go to Maintaining control Parameters for Data Transfer I saw a procedure for the same.
My doubt is I want to go to <b>Client Maintenance</b>, How should I go.
Where is this <b>Source System</b> on which I can go to the<b> tools</b> on the menubar. Is it on the Administrative Workbench?
Please help me.
Sudha.

I think what you want is in SCC4 as Roberto mentions:
http://help.sap.com/saphelp_nw04/helpdata/en/93/eb4b3c45b90b76e10000000a11402f/content.htm
Setting Up the New Client
You set up the new client with client copy tools and a template client: Use the functions of the client copy tool to do this. To call these functions, choose Tools > Administration > Administration > Client Administration > Client Copy.
To prevent client settings from making changes to Repository objects and cross-client Customizing data, use the client maintenance functions. To call these functions, choose Tools > Administration > Administration > Client Administration > Client Maintenance (or call Transaction SCC4).

Similar Messages

  • Finding Source System in Extractors

    Friends,
    I am looking to populate the LOGSYS field in a number of datasources coming from a number of systems.  I realize that it is possible to enhance all the extractors to supply this data from the source system, but I am looking for a method for determining the system on the BW side as the data is processed through the transformation. 
    When I look at the definition of the data source, it occurs to me that the source system assignment should supply the needed information.  This is unique to the data source/system assignment and will also update correctly as the transfer rule is promoted up the landscape. 
    Can anyone give me some advice on how to determine the source system assignment during processing of the inbound data package?
    Regards,
    Kevin

    Hi,
    You can write a routine at the transfer rules level for the logsys.
    Since you have the datasource specific to a particular system and it will bring data from that system only.Just make sure that routine has a hardcoded system name.
    Thanks
    Message was edited by:
            Ajeet Singh

  • SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

    Dear All,
    I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
    1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
    2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
    Please let me know if you have any ideas on the above questions.
    Thanks & Regards
    Ravikiran

    Hi,
    I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
    Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
    Thanks
    Sunny

  • Source System BW - what is "Customizing for extractors" etc.

    Hi,
    Can somebody explain IN DETAIL what is the purpose of
    1)Customizing for the extractors
    2)Transfer Global settings
    3)Transfer exchange rates
    I could not find any documentation in help.sap.com. Is there any documentation?
    thanks a lot

    Jay,
    1)Customizing for the extractors
    This is to modify/control the data transfer settings of the particular source system. It takes you to the SBIW screen (Implementation Guide) directly in the source system. Here you can control your datapacket size, number of datapackets for each IDoc etc. From this screen, you cal also maintain the datasources. All the activities realting to 'maintenance of datasources' can be accessed from here.
    2)Transfer Global settings
    Global tabls such as Fiscal Period tables, Fiscal variant values are transferred to BW from the R/3 system where they are maintained. Do a lookup on tables T00* in SE11 and you can see a bunch of tables.
    3)Transfer exchange rates
    Similar to the above tables, different exchange rates are maintained in the R/3 system. These gets transferred to BW. tables such as TCURR, TCURC, TCURV etc. These are called Global settings.
    Hope it helps
    Gova

  • Plug-Ins and Extractors - Related to Upgrade of Source system

    Hi,
    We are upgrading from R3 to ECC.
    Can I say that, if the Plug-in in current R3 system and the new system(post upgrade)(ECC) are same then, the extractors will also remain same ? hence, nothing will be affected in BW ?
    For example, if the current system(R3) has the Plug-in as PI 2004.1 and the upgraded ECC also has the same Plug-in PI 2004.1 , Can I say that the extractors will also be the same ?
    Regards,
    Rekha .

    You have to take care of all your deltas are picked into the bw before upgradation.
    Some times you may required to replicate the data sources after upgradation.
    You may lose the connection between your R3 and you BW.
    Please do a souce system check after the upgradation.
    You have to take care of all deltas :
    As a standard practice we drain the delta queues by running the IP/ chain multiple times.
    As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
    The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
    V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
    See SAP Notes 506694 and 658992 for more details.
    Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    The SAP BW Service SAPI, which is used for internal and ‘BW to BW’ data mart extraction, is
    upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
    upgrade to avoid any possibility of data loss.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    /message/3221895#3221895 [original link is broken]
    OSS notes 328181 and 762951 as a prerequisites.
    http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B

  • Transformation: Need for calling a custom function module on source system

    Hi Gurus,
    I need to use a custom FM residing on source system within the transformation to determine the type (e.g. posting type) of a document item. The logic is quite complex with many exceptions (many if statements) and 2 customizing & few transparent tables are in use as well in the FM.
    From my point of view, there are few options for achieving the outcome:
    1. Copy the FM logic 1:1 in transformation
    2. Transport the FM from ERP to BW system
    3. Source system delivers the info (e.g. with an extra field "posting_type")
    4. Access the FM directly via RFC/BAPI
    However, there are pros and cons for each of the alternatives:
    *Option 1*
    pros:
    cons: consistency problem, need for importing customizing tables & source tables, high maintenance effort
    *Option 2*
    pros: better consistency compared to Option 1
    cons: need for importing tables, administrative efforts
    *Option 3*
    pros: no logic is needed at BW side, no transformations means no impact on performance, high consistency, no administrative effort
    cons: structure in source system has to be changed, impact on historical records
    *Option 4*
    pros: best consistency (better than Option 3 as FM might change), no administrative effort
    cons: impact on performance during transformation
    Could you please verify my assumptions and give suggestions on solving the problem?
    Thanks a lot!
    Regards,
    Meng

    Hi Joon,
    According to me.
    If Historical data amount is so high, historical data is available in BW(at PSA level or acquisition layer or corporate memory layer) and headache to load history data(because of overload on ECC due to huge amount of data) from ECC then I will suggest combination of 3 and 4 steps.
    If fetching history data from ECC is not headache for you then go for step 3.
    Step 3 is most common approach in BW, which is easy for implementation and support.
    Regards,
    Ashish

  • BW Extractors Problem - Source System Is Incorrect

    Hello,
    I performed a homogeneous system copy of our BW system from our Production BW system to the Development BW system!
    But now I´m with a problem regarding the extractors... when I go to transaction RSA1, I was trying to replicate data in a BWD extractor but it gives me an error. The problem is the Source Client that is not correct, it points to our ERP Production system (P70 client 100) but it should be points to the ERP Test/Quality system (T70).
    When I try to perform a "Replicate Metada" it show me the following error:
    Error during the retrieval of the logon data stored in secure storage
    Can you help me please, how can I correct this situation?! How can I Change the Source System?
    Thank you,
    samid raif

    HI Samid,
    Please have a look at SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW. I think that Scenario B3 is relevant in your situation. Apparently some of the actions are not executed, e.g. Step 6.7 (rename of logical system using t/code BDLS).
    Also note that nowadays there is Post-Copy Automation (PCA). Please refer to 1707321 - BW System Copy: Post Copy Automation (BW-PCA).
    Best regards,
    Sander

  • 0HR_PA_EC_01 Extractor error converting from currency in source system

    Hi all,
    when I run the standard extractor 0HR_PA_EC_01 , I get the following error message in the source system (application log):
    Error converting currency from USD to  on 09/03/2008
    Message no. HRECM00SERVICE006
    Thus, the requst in the PSA  in BI / BW is Red.
    Any recommendations?
    Points will be assigned.
    Thanks

    Rajan,
    You can try this function module for converting currency from one format to another format...
    CONVERT_TO_FOREIGN_CURRENCY...
    other wise... you can try with this function module..
    RSW_CURRENCY_TRANSLATION............ this one i'm not sure abt that will convert ur data into required format..

  • The error occurred in source system Extractor .

    Dear Mates,
    We are getting this error in the process chain, this is a master data load and not showing any clear description of the error and short dump as well.
    Message incomplete (seriousness, area, number, or exception missing)
    Message no. BL203
    Diagnosis
    An incomplete message was sent to the application log.
    A message comprises at least:
    Error seriousness (MSGTY field)
    Work area (MSGID field)
    Error number (MSGNO field)
    At least one of these values is missing.
    At least the exception class (I_S_EXC exception) must be transferred for exceptions.
    Kindly throw any lighton this issue if you have come across of this kind.
    Regards
    Arun S

    Hi Arun,
    In the Sourcesystem, go to transaction RSA3 and give your DS as input.
    Run the extraction and see if you are getting any error messages there.
    It might happen sometimes that due to data error, it might happen.
    some times the records are not transferred to Deltaqueue properly.
    Check the extractor and if you get any error messsage there, there is aproblem in the DS or source system data.
    If you are not getting any error message, try repeating the load again.
    Hope this helps,
    Sri...

  • Customized delta data source for deleting data record in the source system.

    Hello Gurus,
           there is a customized delta data source,  how to implement delta function for deleting data record in the source system?
    I mean if there is record deleted in the source sytem, how to notify SAP BW system for this deleting change by this customized delta
    data source?
    Many thanks.

    Hi,
    when ever record deleted we need to write the code to insert the record in  Z table load this records into BW in a cube with similar structure.while loading into this cube multiply the Keyfigure by -1.
    add this cube in the Multi Provider.The union of the records in the orginal cube and the cube having deleted records will result in zero vale and will not be displayed in report .
    Regards,

  • Error occured in source system - in the extractor

    Hi Experts,
    I started an INIT load from ODS1 to ODS2 and Infocube.
    It is expected to contain 21 million records.
    After loading 17 million records the loading stops with an error message "an error occured in the source system"
    Caller 09 contains an error message.
    Can you please explain the reasons for this error and how to fix it so that i do not face this eror in the next init load.
    Regards,
    Suraj S Nair

    Due to the high volume of records, this error may error.
    Reduce the package size and check the loading once again.
    Hope this helps.

  • Problems Delta Extractor after Homogeneous Source System Copy

    Hi,
    We have R/3 system landscape HUD, HUQ, HUP. And we have BW system landscape BWD and BWP.
    We connect BWD to HUQ and BWP to HUP.
    We made a homogeneous system copy from HUP to HUQ.
    We haven´t made any homogeneous system copy from BWP to BWD.
    We have applied the next OSS note after source system copy:
    325525 Copying and renaming systems in a BW environment
    184322 Procedure after DB copy of BW source system
    184754 Procedure after BW database copy.
    But we have problems in our BW Development (BWD), and we have the next Dump "MESSAGE_TYPE_X" when we can change any delta infopacket, the next text are from Dump:
    "MESSAGE_TYPE_X" C        
    "SAPLRSS1 " or "LRSS1F11 "
    "RSM1_CHECK_FOR_DELTAUPD" 
    I think that the problem is about inconsistencies between RSSDLINIT/SEL tables in BW side and ROOSPRMSC/F tables in R/3 side.
    Please could you tell how can i solve this Dump, because i can restrart and initial and delta packet for different Datasource and i can´t do anything.
    Thanks in advanced,

    Hi,
    We are upgrading our R/3 system from 4.7 to Ecc 6.
    While copying database tables we are using Clinet Carrier tool which is considering only clinet dependent tables. Hence we are loosing our BW delta queue entries in RSA7 of ugraded system.
    We found ROOSPRMSC and ROOSPRMSF tables and copying these 2 tables may resolve the issue and We copied and delta went fine.But we are not sure of only these are the tables to be considered.
    Please let us know what are the relevent tables to be considered to make the Delta to work while copying Data base tables from one system to another.
    Thanks in Advance
    Regards,
    R@ngzz

  • New source system for HR extractors - easy way to change source system?

    Hi
    Our HR module is going to be seperated from the ECC module and thereby placed on a new server and have its own source system.
    In BI we have to handle this as well so that all 7.0 transformations and 3.5 transferrules etc. have to be mapped to the new HR source system. It there a smart way to do that and how would you do it?
    Thanks and kind regards,
    Torben

    Hi Dhanjayan
    Thanks for your reply.
    That would be an option to collect all source system dependent objects in a transport, however by doing that we will also collect objects for all the other areas than HR and it will therefore be a huge task to remove non HR related objects.

  • Background job is running for long tome in source system (ECC)

    Hi All,
    Background job is running for long tome in source system (ECC) while extracting data to PSA.
    I checked in ECC system SM66,SM50 the job is still running
    in SM37 the job is Active
    There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
    I had checked enhancements every thing is correct.
    Please help me on this how can I solve this issue.
    Regards
    Supraja K

    Hi sudhi,
    The difference between Call customer enhancement...  and  Result of customer enhancement:... is very less we can say this as a second.
    The difference is between LUWs confirmed and 1 LUWs -
       and Call customer enhancement -
    Please find the job log details below, and give me the solution to ressolve this
    01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                     R8           048
    01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
    06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
    06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
    06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
    06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
    06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
    06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
    06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
    06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
    06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
    06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
    06:56:32 Job finished                                                                               00           517
    Regards
    Supraja

  • FM CRM_PRIDOC_READ_OW works in source system but not when executed from BW

    Hello All,
    I have extended an extractor in the source system by adding additional fields.
    One of the FM I've used is CRM_PRIDOC_READ_OW. When I run an extraction test in the source system eveything works and data does populates into the new fields.But when I run the infopackage from the BW side, I get an error message which saids the transaction has been terminated. I've been able to trace and pinpoint the possible cause of the error. When I do not call this FM, the infopackage finishes but I do not get data for the new fields and when I do call this FM, I get the error.
    Has anyone experiance this issue before?
    Your assistance will be much appreciated. Here is a portion of the code I wrote:
      loop at I_TABLE into l_s_ZASCRM_OPPT_I.
        lv_guid = l_s_ZASCRM_OPPT_I-GUID.
        lv_item_guid = l_s_ZASCRM_OPPT_I-ITEM_GUID.
        call function 'CRM_PRIDOC_READ_OW'
          exporting
          iv_header_guid = lv_guid
          importing
          ES_PRIDOC = ls_pridoc.
        loop at ls_pridoc-PRIC_COND into ls_pric_cond.
          if ls_pric_cond-kposn = lv_item_guid.
            case ls_pric_cond-STUNR.
              when '40'.
                l_s_ZASCRM_OPPT_I-zz_gpm_ttl_i = ls_pric_cond-kwert.
              when '55'.
                l_s_ZASCRM_OPPT_I-zz_gpd_ttl_i = ls_pric_cond-kwert.
              when '60'.
                l_s_ZASCRM_OPPT_I-zzfy_sp_i = ls_pric_cond-kwert.
              when '70'.
                l_s_ZASCRM_OPPT_I-zzfy_gpm_i = ls_pric_cond-kwert.
              when '80'.
                l_s_ZASCRM_OPPT_I-zzfy_gpd_i = ls_pric_cond-kwert.
            endcase.
          endif.
        endloop.
        append l_s_ZASCRM_OPPT_I to l_s_ZASCRM_OPPT_Itab.
        clear l_s_ZASCRM_OPPT_I.
      endloop
    Thanks,
    Jeff

    Hello Geo!
    Thank you for your question. I think we mapped all the systems you show. Always the same error. Concerning your systems my transport log would say:
    Source system R3DEV does not exist
    We mapped this.
    Any ideas? Is there maybe something in customizing to do what could be forgetten? The system is newly connected and there have never been a transport compounded to this source system before.
    Best regards,
    Peter

Maybe you are looking for