ABAP CODE TO POPULATE LOGICAL SOURCE SYSTEM

Hi Friends please help me with the below
1. Requirement : to Populate The system Date , Source System
in BI for Each load request.
1 Solution: I thought of writing the Start Routine for this but it is giving me error
syntax Error: END METHOD MISSING?????
2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
Thanks
Poonam Roy
ABAP Code.
I have the End Method. what more to do.
METHOD start_routine.
*=== Segments ===
FIELD-SYMBOLS:
<SOURCE_FIELDS> TYPE tys_SC_1.
DATA:
MONITOR_REC TYPE rstmonitor.
$$ begin of routine - insert your code only below this line -
... "insert your code here
FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TRANSTRU
ABORT LIKE SY-SUBRC.
DATA: ZLOAD_DAT LIKE SY-DATUM
ZZSOURSYS TYPE RSLOGSYS
IF G_S_MINFO-DATAPAKID=1
SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
ENDIF.
ABORT = 0.
ENDFORM.
ENDMETHOD.
ENDCLASS.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD.

You have to write the code (<b>in BI/BW</b>) in the transfer rule (<b>between Datasource transfer structure and infosource/info object</b>)
There the FORM begin with
[code]USING RECORD_NO LIKE SY-TABIX
    TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
    G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OIPERSON
    G_T_ERRORLOG TYPE rssm_t_errorlog_int
    RETURNCODE LIKE SY-SUBRC
    ABORT LIKE SY-SUBRC. “set ABORT <> 0 to cancel datapackag[/code]
GS_MIN_INFO structure RSSM_S_MINFO contains information on the request being processed.
<i>G_S_MINFO. This passes technical information about the data load request,
such as requesting user, request date and time, update mode, the handling of
duplicate records, error handling flags, parallel processing flags, and what data
targets to update.</i>
If tou want to use start-routine for optimization reasons and fill an empty field in transfer structure, the structure G_S_MINFO is available too.
[code]USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TAB_TRANSTRU
    G_T_ERRORLOG TYPE rssm_t_errorlog_int
    ABORT LIKE SY-SUBRC. “set ABORT <> 0 to cancel datapackage[/code]
And stay in FORM between limits :
[code]$$ begin of routine
$$ end of routine[/code]
Update RESULT in first case, and field(s) of DATAPAK in second case.
[code]RESULT = G_S_MINFO-LOGSYS.[/code] or
[code]LOOP AT DATAPAK INTO l_s_datapak_line.
  l_s_datapak_line-zzsourcsys = G_S_MINFO-LOGSYS.
  MODIFY DATAPAK FROM l_s_datapak_line.
ENDLOOP.[/code]
Regards

Similar Messages

  • Start Routine to populate the Logical Source System

    Hi Friends please help me with the below
    1. <b>Requirement</b> : to Populate The system Date , Source System
    in BI for Each load request.
    <b>
    1 Solution:</b> I thought of writing the Start Routine for this but it is giving me error
    syntax Error: END METHOD MISSING?????
    2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
    Thanks
    Poonam Roy
    <b>ABAP Code.</b>
    I have the End Method. what more to do.
      METHOD start_routine.
    *=== Segments ===
        FIELD-SYMBOLS:
          <SOURCE_FIELDS>    TYPE tys_SC_1.
        DATA:
          MONITOR_REC     TYPE rstmonitor.
    <b>
    $$ begin of routine - insert your code only below this line        -</b>
    ... "insert your code here
    <b>
    FORM STARTROUTINE
    USING G_S_MINFO TYPE RSSM_S_MINFO
    CHANGING DATAPAK type TRANSTRU
    ABORT LIKE SY-SUBRC.
    DATA: ZLOAD_DAT LIKE SY-DATUM
    ZZSOURSYS TYPE RSLOGSYS
    IF G_S_MINFO-DATAPAKID=1
    SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
    SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
    ENDIF.
    ABORT = 0.
    ENDFORM.
    ENDMETHOD.
    ENDCLASS</b>.
    *--  fill table "MONITOR" with values of structure "MONITOR_REC"
    *-   to make monitor entries
    ... "to cancel the update process
       raise exception type CX_RSROUT_ABORT.
    $$ end of routine - insert your code only before this line         -
      ENDMETHOD.

    Hi,
    Check whether the formula is useful here than Routine. Because you can see the Sy-datum , source system( I Guess) fields as avaialable formula elements .
    With rgds,
    Anil Kumar Sharma .P

  • ABAP logical source system

    dear all,
    how can i get the logical source system using abap into my update rule?

    Hello,
    I believe is SY-SYSID.
    Diogo.

  • Configuration Wizard-NW:BI-AS ABAP(Connectivity of BI and Source System): M

    Hi friends,
    I´m configuring the (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain) in NWA using Configuration Wizard.
    But there is the error in step (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain > Scenario UI: NW_BI_ABAP_DEFAULT > Scenario Process: Abap Server Integration to BI > Configuration Process > Configuration Unit: Initialize > Config Unit BI System: Initialize > Customizing: Assign Logical System to Client > Write Customizing data to Table T000)
    Below error log:
    *Write Customizing data to Table T000*
    Description:
    Exception in step "WriteProfile_1223390220410"
    Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Exception during the import of the profile!
    State
    Step finished with error
    Support Information
    Type of Action
    WriteProfile
    Debug Events
    WriteProfile:Write Customizing data to Table T000
    Library: sap.com/tclmconfig~bs
    SourcePath ./com_sap_nw_bi_abap_default_maintain/ext_12064772269223/ext_1206447991146/Process_1207123636083/proc_1196064316796/Process_1204300420808/proc_1204300371034/WriteProfile_1223390220410
    Time 2011/11/03 at 15:36:57
    Schema content/NetWeaver/Common/Customizing/Clients/T000.xsd
    Type : View Maintenance
    Input
    <TABLE_T000 xmlns:expr="http:/sap.com/ctc/expressions"><T000><MANDT>100</MANDT><LOGSYS>SOLCLNT100</LOGSYS></T000></TABLE_T000>
    Schema
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:vma="http://www.sap.com/ctc/vma"
    elementFormDefault="qualified"> <xsd:element name="TABLE_T000" type="TABLE_T000"></xsd:element> <xsd:complexType name="TABLE_T000"> <xsd:sequence> <xsd:element name="T000" type="T000"> <xsd:annotation> <xsd:appinfo
    source="http://www.sap.com/ctc"> <vma:vmacontext table="T000" isupdate="false"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="T000"> <xsd:sequence> <xsd:element name="MANDT" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="MANDT"/> </xsd:appinfo>
    </xsd:annotation> </xsd:element> <xsd:element name="LOGSYS" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="LOGSYS"></vma:vmaproperty> </xsd:appinfo> </xsd:annotation> </xsd:element
    </xsd:sequence> </xsd:complexType> </xsd:schema>  
    Destination parameters
    user : SOLMAN_ADMIN
    password : % secure content %
    host : cdsolman
    sysnr : 01
    client : 100
    language : en
    Stack Trace
    Caused by: com.sap.tc.lm.ctc.cul.api.CULServiceException: Exception during the import of the profile!
         at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:98)
         at com.sap.tc.lm.ctc.cul.serviceimpl.process.WriteProfileControllerImpl.execute(WriteProfileControllerImpl.java:160)
         ... 16 more
    Caused by: com.sap.tc.lm.ctc.cul.cpi.context.ConfigurationBrokerException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='xml_parsing_exception', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key xml_parsing_exception
         at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:79)
         at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:95)
         ... 17 more
    Caused by: com.sap.tc.lm.ctc.provider.vmaprovider.exceptions.VMAProviderBaseException: Incorrect XML
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:349)
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.setXmlValue(VMAUtil.java:250)
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeContext(JCOProfileExecutorImpl.java:310)
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeChildNode(JCOProfileExecutorImpl.java:183)
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeProfile(JCOProfileExecutorImpl.java:129)
         at com.sap.tc.lm.ctc.provider.vmaprovider.VMAWriteProfile.writeProfile(VMAWriteProfile.java:59)
         at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:144)
         at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:73)
    Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)(:main:, row=1, col=637) -> com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
         at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:341)
    Caused by: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
         at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:209)
         at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
         at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
    All the others steps were finished successfully
    Only this step is with error. I don´t know that to do.
    Regards,
    Ricardo Arriado
    Edited by: Ricardo Arriado on Nov 4, 2011 6:24 PM

    Hi,
    Please double check the JCO user and the authorization.
    Or
    Apply these two notes, it should resolve ur issue
    1493124 CTC: Check table existence before table whitelist
    1471762 CTC: Automated Configuration:
    Hope this helps u.
    Best Regards
    Vijay K

  • Error in code page mapping for Source system whil loading the data from ECC

    HI Gurus,
    I am working in a implementation project, Recently our BI sand box is up, when i am doing my load from 0comp_code_attr it is throwing an error "Error in code page mapping for source system"(This is my first load from ECC).
    In details tab it is showing as the data is sent from the source system but the data is not reaching to the PSA.
    Please let me know if there are any settings needs to be made.
    Many thanks in Advance
    Jagadeesh

    HI V,
    Thanks for your quick response. I did it but it didn't resolve the issue. since the system id which i am having is 3 digits(LEC) but there it is taking only 2 digits, so i clicked on the button called Propose system ids, it has praposed LE, but the issue is stil there.
    Do we need to do any settings in LBWE??
    Thanks and Regards
    Jagadeesh

  • Error in code page mapping for Source System

    Hi All,
    We are Loading data into BI system from MDM System.
    It was loading fine but Yesterday we got an error " Error in code page mapping for Source System"
    Message Class: RSDS_ACCESS 13.
    We alreday tried to Search any IDOCs with error/unprocessed , but there isn't any.
    Any pointers for this error will be Helpful.
    Regards,
    Mayank

    Our SP currently SAPKW70019 , the SAP note mentioned above required to apply SP for 13, which we already beyond that...unfortunately we still face the same problem .. almost every day ..
    any advice.. ?
    Edited by: Edi Erwan  Abu Talib on Jun 22, 2009 8:22 AM

  • Abap Code to populate source system id

    Hi , so kind of All of you,
    please help me, i have written the code in one to one mapping in transformation routine in BI 7,0 right click on zzsourcsys and go tp rule details. No syntax errors in the code but when i load there is no value populating to zzsourcsys . i have defined zzsourcsys as 12 char. can u suggest where it is going wrong, i checked in tools assignment of sourcesystem id is there in my system.
    Abap Code
    TYPE-POOLS: RSSM.
    Data: G_S_MINFO TYPE RSSM_S_MINFO.
    RESULT = G_S_MINFO-LOGSYS.
    Thanks
    Poonam Roy

    You have to write the code (<b>in BI/BW</b>) in the transfer rule (<b>between Datasource transfer structure and infosource/info object</b>)
    There the FORM begin with
    [code]USING RECORD_NO LIKE SY-TABIX
        TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
        G_S_MINFO TYPE RSSM_S_MINFO
    CHANGING RESULT TYPE /BI0/OIPERSON
        G_T_ERRORLOG TYPE rssm_t_errorlog_int
        RETURNCODE LIKE SY-SUBRC
        ABORT LIKE SY-SUBRC. “set ABORT <> 0 to cancel datapackag[/code]
    GS_MIN_INFO structure RSSM_S_MINFO contains information on the request being processed.
    <i>G_S_MINFO. This passes technical information about the data load request,
    such as requesting user, request date and time, update mode, the handling of
    duplicate records, error handling flags, parallel processing flags, and what data
    targets to update.</i>
    If tou want to use start-routine for optimization reasons and fill an empty field in transfer structure, the structure G_S_MINFO is available too.
    [code]USING G_S_MINFO TYPE RSSM_S_MINFO
    CHANGING DATAPAK type TAB_TRANSTRU
        G_T_ERRORLOG TYPE rssm_t_errorlog_int
        ABORT LIKE SY-SUBRC. “set ABORT <> 0 to cancel datapackage[/code]
    And stay in FORM between limits :
    [code]$$ begin of routine
    $$ end of routine[/code]
    Update RESULT in first case, and field(s) of DATAPAK in second case.
    [code]RESULT = G_S_MINFO-LOGSYS.[/code] or
    [code]LOOP AT DATAPAK INTO l_s_datapak_line.
      l_s_datapak_line-zzsourcsys = G_S_MINFO-LOGSYS.
      MODIFY DATAPAK FROM l_s_datapak_line.
    ENDLOOP.[/code]
    Regards

  • BDLS for conversion of logical source system name

    Hello All,
    I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
    But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
    How do I make sure that the reassignment happens correctly?
    And what precautions should be taken to avoid further consequences?
    Regards,
    NIKEKAB

    BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
    Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
    You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
    Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
    Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
    Good luck...

  • ABAP code are cut by the system

    Hello
    I created ABAP code in start of update rules. After saving and re-opening, 10-12 right symbols of the code are cut by the system (see example) :
    ABAP mmmmmmmmmmmmmmmmmmmm        (before saving)
    ABAP mmmmmm                      (after saving)
    Can somebody knows how I can correct it?
    Thanks

    In alternative write code like this:
    mmmmmm mmmmm mmmmm mmmmm
    mmmmm mmmm.
    Hope it helps.
    Regards

  • Transport of Infopackages didn't change logical source system

    Hi
    I have transported a good number of process chains to test. However the infopackages are not visible in out test system. I looked in table RSLDPIO using options 'Active' and logical system  'testERP111' and they wern't there.
    However, when i try the selection 'Active' and 'devERP111' they are there.
    SO this means that the logical system name conversion hasn't worked. EVen though we have have the conversion devERP111 > testERP111 set up in the conversion of logical system names.
    We have many clients (111, 112 113) on our system so the conversion is something wheich is always checked as part of transporting.
    Any ideas why and how to solve it??

    Along with that process chains, U should also transport infopackages / DTPs existing in that process chains.
    In test system, u can check table RSPAKPOS for the infopackages. If the infopackage is does not exist in that table, u should transport the same to test system.

  • Convert the logic source system

    Hi all,
    I have a question related to the transportation.
    We have 3 client for DEV(001) QA(002) & PRD(003).
    I have packaged a transport request for my cube and related transformation. I also mantained the Conversion(DEV001 -> QA002). I released the transport request and import it into QA. It works fine because the source was changed from DEV001 to QA002.
    My question is what the system behavior is if I want to import the same transport request into PRD. can the system automaticly change the source from DEV001 to PRD003? If can't, what should I do?

    Hi,
    Conversion of system has to be maintained in production system as well .
    Once conversion of QA to PRD is maintained , same requests can be transported to PRoduction and system will change ref. of transfer rule from Qa system to PRD system.
    Hope that helps.
    Regards
    Mr Kapadia

  • To refer logical source in update rules

    Hi,
    I wanted to find the logical source system using abap into my update rule, is it possible.
    Help would be appreciated.
    Thanks,
    SD

    Hi,
    you have only to write something like this:
    case sy-sysid.
    * development system
        when 'dev1'.
            result = 'r3_dev'.
    * test system
        when 'test1'
            result = 'r3_test'.
    endcase.
    dev1 and test 1 are your bi systems. When data comming from one source system you can use this code in each transformation.
    Regards
    Andreas

  • Creating Source System in BW

    Hi Friends,
    We are using BI, i have to create a source system(R3) in BW.
    Both sides we have users with enough profiles.
    In RSA1 --> Source System --> Create is using to create the sourse system.
    I am using automatic function at the time of defining the source system.
    It is asking some dialog user from source side, i am giving some dialog user
    then i am getting the error user cannot create in source system.
    Could you please help me out.. how to create R3 source system in BI.
    Thanks in advance
    Srinivas

    Hi Srini,
                    Check u'r partner profiles.if u din't get....
    plz follow this....
    2.1     SAP R/3
    2.1.1     Define Client Administration (SAP R/3)
    Use
    This activity allows you to change Customizing settings.
    Prerequisites
    You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
    Procedure
    Run the following activity:
    SAP R/3 Role Menu     Define Client Administration (SAP R/3)
    Transaction Code     SCC4
    SAP R/3 Menu     Tools &#61664; Administration &#61664; Administration &#61664; Client Administration &#61664; Client Maintenance
    Then carry out the following steps:
    1.     Choose Display &#61614; Change.
    2.     Confirm the warning message Caution: The table is cross client.
    3.     Select your SAP R/3 client and choose Details.
    4.     In the Change View Clients: Details screen, activate the following settings:
    •     Automatic recording of changes
    •     Changes to Repository and cross-client Customizing allowed
    •     eCATT and CATT allowed.
    5.     Save.
    6.     Go back to the SAP Easy Access menu.
    2.1.2     Defining a Logical System for SAP R/3 (SAP R/3)
    Use
    The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
    1.     Define the systems as logical systems.
    2.     Assign the logical system for the SAP R/3 System to a client.
    This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
    Logical systems are defined cross-client.
    Procedure
    Carry out the following steps:
    1.     Access the transaction using:
    SAP R/3 Role Menu     Defining a Logical System for SAP R/3 (SAP R/3)
    Transaction Code     SPRO
    SAP R/3
    IMG Menu     Basis Components (for R/3 Enterprisse: SAP Web Application Server) &#61614; Application Link Enabling (ALE) &#61614; Sending and Receiving Systems &#61614; Logical systems &#61614; Define Logical System
    2.     Choose New entries.
    3.     In the column Log System, enter a name for the logical system that you want to create.
    4.     In the column Name, enter a description of the logical system.
    Log. System     Name
    where      XXX is the system name
    and      NNN is the client.
    5.     Save your entries.
    A transport request for Workbench appears.
    6.     Select an existing request or create a new request, if necessary.
    A transport request for Customizing appears.
    7.     Select an existing request or create a new request, if necessary.
    2.1.3     Assigning Logical System to Client
    Use
    The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
    Procedure
    Carry out the following steps:
    1.     Access the transaction using:
    SAP R/3 Role Menu     Assign Logical System to Client
    Transaction Code     SCC4
    SAP R/3 Menu     Tools &#61664; Administration &#61664; Administration &#61664; Client Administration &#61664; Client Maintenance
    2.     Choose Display ® Change.
    3.     Confirm the warning message The table is cross client.
    4.     Select your R/3 client and choose Details.
    5.     Enter the name of the logical system of your SAP R/3 client.
    6.     Save and confirm the warning message Be careful when changing the logical system.
    7.     Choose Back twice.
    2.1.4     Creating an RFC User (SAP R/3)
    Use
    To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
    The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
    Procedure
    Carry out the following steps:
    1.     Access the transaction using:
    SAP R/3 Role Menu     Creating an RFC User (SAP R/3)
    Transaction Code     SU01
    SAP R/3 Menu     Tools &#61664; Administration &#61664; User Maintenance &#61664; Users
    2.     In the User field, enter RFCUSER.
    3.     Choose Create.
    4.     On the Maintain User screen, enter the following data on the Tab entry screens:
    Address     
    Last Name     
    Function     
    Logon data
    User type     System
    Password     LOGIN
    Profile
    Profiles     SAP_ALL
    SAP_NEW
    S_BI-WX_RFC
    Defaults
    Logon Language     EN
    5.     Save your entries.
    2.3     SAP BW
    2.3.1     Define Client Administration
    Use
    This activity defines changes and transports of the client-dependent and client-independent objects.
    Procedure
    1.     To perform this activity, choose one of the following navigation options:
    SAP BW Role Menu     Local Settings ® Define Client Administration
    Transaction Code     SCC4
    SAP BW Menu     Tools &#61664; Administration &#61664; Administration &#61664; Client Administration &#61664; Client Maintenance
    2.     Switch to change mode.
    3.     Select your client.
    4.     Choose details.
    5.     In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
    6.     In field Client Role enter Customizing
    7.     Check the settings for changes and transport of client-specific objects and client-independent object changes
    If you want to use the settings made by BC-Sets or manually in other systems (other than BW), “Automatic recording of changes” and “Changes to Repository object and cross-client Customizing allowed” is required.
    Result
    Client administration has been defined to support the installation using Best Practices.
    2.3.2     Defining a Logical System for SAP BW (SAP BW)
    Use
    In this step, you define the logical systems in your distributed system.
    Prerequisites
    Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client  (this can be checked in transaction SCC4).
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu     Defining a Logical System for SAP BW (SAP BW)
    Transaction Code     SPRO
    IMG Menu     SAP Reference IMG &#61664; SAP Customizing Implementation Guide &#61664; SAP NetWeaver &#61664; Business Information Warehouse &#61664; Links to other Systems &#61664; General Connection Settings &#61664; Define Logical System
    1.     A dialog box informs you that the table is cross-client. Choose Continue.
    2.     On the Change View “Logical Systems”: Overview screen, choose New entries.
    3.     On the New Entries: Overview of Added Entries screen enter the following data:
    Field name     Description     R/O/C     User action and values     Note
    Log. System     Technical Name of the Logical System          Enter a name for the logical BW system that you want to create     
    Name     Textual Description of the Logical System          Enter a clear description for the logical BW system     
    4.     Choose Save.
    If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
    If you want to continue with the next activity, do not leave the transaction.
    Result
    You have created a Logical System Name for your SAP BW client.
    2.3.3     Assigning Logical System to Client (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW
    Role Menu     Assigning Logical System to Client (SAP BW)
    Transaction Code     SCC4
    SAP BW Menu     Tools &#61664; Administration &#61664; Administration &#61664; Client Administration &#61664; Client Maintenance
    1.     In the view Display View "Clients": Overview, choose Display. &#61614; Change
    2.     Confirm the message.
    3.     Select your BW client.
    4.     Choose Details.
    5.     In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
    6.     Save the entries and go back.
    2.3.4     Opening Administrator Workbench
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW     Modeling &#61664; Administrator Workbench: Modeling
    Transaction Code     RSA1
    1.     In the Replicate Metadata dialog box, choose Only Activate.
    2.     If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
    2.3.5     Creating an RFC-User (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options:
    SAP BW Role Menu     Creating RFC User
    Transaction Code     SU01
    SAP BW Menu     Tools &#61664; Administration &#61664; User Maintenance &#61664; Users
    Then carry out the following steps:
    1.     On the User Maintenance: Initial Screen screen:
    a.     Enter the following data:
    Field      Entry
    User     RFCUSER
    b.     Choose Create.
    2.     On the Maintain User screen:
    a.     Choose the Address tab.
    b.     Enter the following data:
    Field     Entry
    Last Name     RFCUSER
    Function     Default-User for RFC connection
    c.     Choose the Logon data tab.
    d.     Enter the following data:
    Field     Entry
    Password     LOGIN
    User type     System
    e.     Choose the Profiles tab.
    f.     Enter the following data:
    Field     Entry
    Profiles     SAP_ALL , SAP_NEW and S_BI-WHM_RFC
    g.     Choose Save.
    Do not change the password of this user as it is used in RFC connections.
    2.3.6     Define RFC-USER as default (SAP BW)
    Procedure
    To carry out the activity, choose one of the following navigation options
    SAP BW Role Menu     Define RFC-USER as default (SAP BW)
    Transaction Code     RSA1
    SAP BW Menu     Modeling &#61664; Administrator Workbench: Modeling
    1.     On the Administrator Workbench: Modeling screen choose Settings &#61664; Global Settings.
    2.     In the Global Settings/Customizing dialog box choose Glob. Settings.
    3.     On the Display View “RSADMINA Maintenance View”: Details screen:
    a.     Choose Display &#61664; Change.
    b.     Enter RFCUSER in the BW User ALE field.
    c.     Choose Save.
    Leave the transaction in order to activate the entries you have made.
    3.3.2     Creating the Source System in the Administrator Workbench
    Procedure
    1.     From the SAP Menu in the BW system, choose:
    SAP BW Role Menu     Creating the Source System in the Administrator Workbench
    Transaction code     RSA1
    SAP BW Menu     Modeling &#61664; Administrator Workbench: Modeling
    2.     Choose Modeling.
    3.     Choose Source Systems.
    4.     In the right-hand window mark Source Systems.
    5.     Choose the context menu (right mouse click).
    6.     Choose Create.
    Field name     User action and values
    File System, Manual Meta Data, Data Using File...     X
    7.     Choose Enter.
    Field name     User action and values
    Logical source system      FILE 
    Source system name     File system
    8.     Choose Enter.
    9.     Choose Back.

  • Source System in Transformation

    Hi Experts,
    Here is my scenario. We have number of BW  Systems (RBW1 to RBW5 ) for each continental regions. All these should load data to one Global BW System ( GBW ). RBWs have ODSR1 to ODSR5  and all of it will be connected to DSOG1 in global system.
    Now the question is how do i make namespace value unique in GBW. I use Source System as an identifier. In the transformation how do i populate Source System Infoobject??
    Please help.
    Thanks,
    DV

    no need to enhance the DS.... you can write a filed level routine on it.
    create an infosource in between the IO and the transformations and include the filed... and write the filed level routine to that filed.
    You can use the below code to call the source system id .use the below FM...
    CALL FUNCTION 'RSDG_ID_GET_FROM_LOGSYS'
        EXPORTING
          i_source_system = l_sourcesystem
        IMPORTING
          e_soursysid     = RESULT
        EXCEPTIONS
          id_not_found    = 1.
      IF sy-subrc <> 0.
        RETURNCODE = 4.
        MESSAGE e087(r7) WITH l_sourcesystem INTO l_text.
        MOVE-CORRESPONDING syst TO l_s_errorlog.
       l_s_errorlog-record = RECORD_NO.
        APPEND l_s_errorlog TO g_t_errorlog.
      ABORT = 1.
      ENDIF.
    Edited by: prashanthk on Feb 24, 2011 10:59 AM

  • Problem Activating Source system RSAR 374, RSAR 375

    Hi all,
    Hoping you can help me with this issue. I have two
    systems,one R/3 4.7 system and another BW 3.0B system.Both are recently installed. created user in client 800 on R/3. created user in client 100 on BW. i established RFC destination between both, Logical source system assignments and definitions of logical source systems on both. They are working correctly, But i couldnot succeed in creation of the source system. it gets created but it is not activated and ends with the following errors.
    Message and the id next to it
    1) The following errors occured in the source system. RSAR   374.
    2) Result of the destination check: timeout         .      RSAR   375 .
    when i try to activate it by right clicking on it , it does give these errors and activation gets terminated.
    Can anyone pleaseeeeeeeeeeee with this. Thanks a lottttttt........
    kishore karnati

    Hi Kishore and Edwin,
    I have exactly the same problem described here, except I am creating an ECC 6 source system in BI 7.
    Therefore, I am wondering if you guys can elaborate on your experience.
    I get the same error message RSAR 374 and RSAR 375.
    I did both connection and authorization tests for the RFC in SM59 and it's OK.
    What do you mean by the "basic concept of BWREMOTE AND ALEREMOTE background users."???
    Please advise.
    Cheers,
    SJ

Maybe you are looking for

  • Unable To Print or Access Page Setup in Crystal Reports 2008

    I have Win 7 32 bit, and installed Crystal Reports 2008 last week (v12.0.0.683 from the Help window). Every time I open a report, and from the Preview tab clicking File -> Print, or File - > Page Setup, I immediately receive a Windows message that "C

  • How can I get photos to show up in PSE 10 from LR3?

    I've installed PSE10 and linked it to LR3 so I can edit photos in both. When I choose "Edit In" in LR3 it opens up PSE10 but no photo shows up. Any ideas?

  • I am looking to buy a new iMac....help please.

    I am looking to buy a new iMac, and I started a search on Craigslist for fun, and it seems as if some people have some really good deals on the model mb325ll/a. It is the 2.8 ghz version with 2 gigs of ram and a 320gb hard drive. This is not a model

  • Using iCloud - why don't my iPhone and iPad calendar appointments match?

    I use iPhone 5C and iPad Air. I recently decided to ditch using Outlook 2010 Calendar on my PC (Windows 8) and switch to iCloud - a drastic decision after using Outlook for 15 years. I created a new iCloud account and turned on Contacts and Calendar

  • Linking tracks (REWARD!)

    Ok, so the reward might be lame - but I'd appreciate any clear help with this puzzle. I have created a DVD that plays beautifully. It contains 30 music videos that have each been compressed (via Compressor). I have pulled them into a DVDSP template "