RDA DataSource XI

Hi,
I am using a RDA DataSource to capture messages from a XI System.
I am using also a RDA ODS, I mean the data is update
XI -> PSA -> ODS
for some reason I got the situation that PSA is updated but ODS not.
Daemon stops and I anot able to reactivated because :
"Request ### no yet loaded in target <ODS Name>"
There is some possibility to load those request in ODS ?
if I fry to create other DTP I got a conflict with the existing one...
I am not sure if if changeing to a STADARD DTP will help...and if I will be able to change again in a RDA DTP..
I am going to appreciate any help
FedeX

ok . I misunderstood your question. Help me understand this better -
So, when the Daemon is active and running - data comes to PSA but doesn't update the DTP ? If so, do you see the request in ODS in Yellow or Red status ? Does Daemon stop at this point?
Note: We have a similar setup and it is working fine.
BTW, have you tried repairing the DTP ? It changes it to standard DTP and you can always go back to Realtime DTP

Similar Messages

  • RDA datasource

    hi guys:
    dose dotasource 2LIS_11_VAITM support RDA?in my bi7 system it dosen't support RDA.
    can anybody can give me a ds that support RDA?
    thks
    Best regards

    Hi..
    Insert the required process type into the process chain by using drag and drop or by double-clicking.
      In the next dialog box, select a process variant and confirm your entry.
                                a.      To create a new process variant, enter a name for the variant and choose   Create.
                                b.      In the resulting dialog box, enter the description of the process variant and choose Next.
    The maintenance screen for the process variant appears.
                                c.      In the variant maintenance, select the Data Sources for which real-time data acquisition should be started or stopped for one or more Info Packages for real-time data acquisition.
                                d.      Save the variant and go back to the previous screen.
                                e.      In the resulting dialog box, confirm the insertion of the process variant into your process chain.
    Start Real-Time Data Acquisition (RDA) Load Process
    If the InfoPackages selected in the process variant are not yet assigned to a daemon, the system selects one or more suitable daemons and assigns the corresponding DataSources to them. When searching for a suitable daemon, the system proceeds as follows:
                                a.      Assignment based on the InfoProvider (data target)
    Different DataSources (and therefore InfoPackages) that define values for the same InfoProvider must be assigned to the same daemon.
                                b.      Assignment to the daemon that was last assigned to the DataSource (and therefore to the InfoPackage)
    The system stores the information about the assignment of a DataSource to a daemon when the daemon assignment is deleted. This information can therefore be used later for another assignment to a daemon.
                                c.      Assignment to the daemon to which the fewest DataSources are assigned
    If multiple daemons are possible here, the assignment is made to the daemon with the lowest number
    If there is not yet a daemon available, the system creates one and assigns the DataSources to the daemon. If the DataSources are already assigned to a daemon, this daemon is used.
    The data transfer processes assigned to the DataSources are also assigned to the daemon.
    If all the assignments have been made and the daemon or daemons are not running at the time of process execution, the process chain schedules the daemons for immediate use and the process variant ends.
    If an Infopakage selected in the process variant is assigned to a daemon that is already running, the steps described here are not applicable and not performed.
       Stop Real-Time Data Acquisition (RDA) Load Process
    Running data transfers for the Info Packages and corresponding data transfer processes selected in the process variant are terminated.
    The open PSA, DTP and possibly change log requests are closed (if the daemon is running, after ending the data transfer; directly if the daemon is not running).
    The system then deletes the assignments of the corresponding Data Sources to the daemon.
    As mentioned above, the system stores the information about the assignment of the DataSource to the daemon, and this information can be used again later when the daemon is again assigned.
    If an InfoPackage selected in the process variant is not assigned to a daemon, the steps described here are not applicable and not performed.
    Thanks==points
    Regards
    Sudheer

  • RDA Datasource problem

    THis is my first attempt at an RDA Extractor.   THe problem I am getting is that the daemon job is failing with the message in the job log, "Error during extraction: 0 rowa in l_t_tid, 0 rows in l_t_data - Message RSCRT 360.
    Here's how I got to this point:
    1) Wrote an ABAP in ECC to set the REALTIME to 'X' for this CO-PA datasource (<- Not sure this is even possible for a CO-PA extractor)
    2) Replicated the DS into BI 7
    3) Created a transformation and DTP.
    4) Created an infopack to initialize deltas and ran it (Successfully)
    5) Created an RDA enabled infopack and assigned a daemon to it.

    Never could get it to work

  • Records are repeatedly loading for RDA DataSource

    Hi
    Iam trying to load the data for custom datasource into DSO . This datasource is real time enabled one .
    Eventhough there is no new records are created in ECC system , the real time datasource getting the same number of old reocrds dailiy . I mean , the records are repeatedly loading into the DSO object .
    Why the records are repeatedly loading into the DSO object for real time datasource .
    Please let me know
    Regards
    mohammed

    Hi,
    In RSO2 click on a'GENERIC DELTA' and select the Time stamp and give the lower limit and upper limit
    and if you are loading the data into DSO then select the radio button is "New Status of changed record"
    if you are loading the data into CUBE then select the radio button is "Additive Delta".
    Regards,
    Yerrabelli.

  • Realtime Generic Datasource

    Hi,
    1. How to make a generic datasource as a realtime(RDA) datasource for Realtime data Acquisition??
    2. How to change the value of the field 'REALTIME' in the table ROOSOURCE??
    Thanks
    Message was edited by:
            Vaishali SAP

    Hi,
    The monitor is the main tool for controlling the daemon and assigning DTPs and InfoPackages to a certain daemon. There can be more than one daemon in a system and a daemon can process more than one DataSource.
    For the daemon to pick up the data from the source system we must create an InfoPackage for the real-time data acqusition. This is similar to the InfoPackage we create for our regular scheduled data loads. An additional flag is available in the InfoPackage creation screen – only available if the Data Source is enabled to provide real-time data acquisition data. If it is not then this flag is not available. You can only create one InfoPackage for such a DataSource. It is not possible to create multiple InfoPackages with this real-time data acquisition flag. The reason is that we are specifying some settings in this InfoPackage that are particular to this real-time data acquisition
    Other settings in the InfoPackage include the adapter (how the data is provided). The setting is “Extraction from SAP System Using close to Real-time”.
    Under the Procesing tabstrip we have settings for the closure of the request – either a certain time (in hours / days) or a max number of records per request before we close it. Other settings are for the data package size and the maximum number of times the daemon should try to retrieve data from the source system before it before it actually stops processing.
    Under the Update tabstrip we specify where we get the data from. In this case we see only the option for delta update. To initiate the delta queue we must create an “initialisation of delta” package. Under the Schedule tabstrip there is no option to schedule the InfoPackage – instead we have a “Go to” functionality via the Assign pushbutton which brings us to the daemon where we can assign our InfoPackage and the DTPs to a certain daemon. 
    Regards
    CSM Reddy

  • Enable RDA for customized datasource

    Hi
    Please let me know step by step process how to enable RDA for customized datasource ( generic extraction by FM)
    and how tio enable for standard datasource

    Please let me know step by step process how to enable RDA for customized datasource ( generic extraction by FM)
    Re: Real-Time Data Acquisition
    and how to enable for standard datasource
    goto se38 in ECC, and cerate an executable program with the following code
    Tables : ROOSOURCE.
    UPDATE ROOSOURCE set REALTIME = 'X'
    WHERE OLPTSOURCE = "datasource name" and OBJVERS = 'A'.
    when i am creating infopckage check box is disable for real time data?
    U have to create TWO infopackages, one for Initialize Delta Process, and other for Real Time load...
    Tricky thing here is, before creating Real_Time infopackage, u should load data through first infopackage (Initialize Delta Process).... Then only real time check box is enabled

  • RDA Issue for Datasource 0FI_GL_4

    Hello Gurus,
    I want to implement RDA using datasource  0FI_GL_4.
    1. This datasource in R/3 is not R/3 enabled. I checked this in se11 --> ROOSOURCE ->Execute> 0FI_GL_4.
    The field REALTIME is not enabled.
    2. I am trying to create Web service source system. Whenevr I am going to Web service and by right clicking on it, its showing message that this system is already existed.
    3. Please provide me with step by step information.
    I referred  a blog of Kamaljeet Singh too.
    Kindly let me know how to make this datasource as RDA enabled.
    Thanks,
    Sonu

    Hi Sonu,
    please create an infopackage with update option initialisation without data transfer.
    Run this Infopackage  so that delta is initialized without data transfer and then create an infopackage for delta and u can see the real time check box available for input.
    if u have done this and even then u face the same problem please try this
    check whether u have any other realtime inpofackege for the same datasource.
    if u dont have any such, then try this it might work out.
    i did the same when i faced same problem, after creating the DTP and initialising the delta ,just come out of RSA1 and goto modelling workbench again try to create an infopackage. this worked for me.
    this is an unexplainable solution.
    hope i helped u with this issue.
    dont forget to acknowledge all the relevant answers as its for a good cause.
    please reach me again if u need further help.
    were the documents on web service useful and r u trying to load through web service also.
    Regards,
    Ranjith

  • Creation of RDA infopackage is not possible for datasource 0FI_GL_6 ?

    Hallo Experts,
    I tried to implement a RDA process for BC DSO 0FIGL_O06 "FIGL: Transaction Figures" by setting the REALTIME field of table ROOSOURCE in the source system. Everything seemed to be OK, the related DTP is changeable to "Real-Time DTP", all prerequisites of this help <a href="http://help.sap.com/saphelp_nw70/helpdata/en/f6/787e403566c65de10000000a155106/content.htm">Creating InfoPackages for Real-Time Data Acquisition</a> are fulfiled, but in the IP creation dialogue the RDA field is greyed out. What could it be? Did you also experience such a problem and solved it?
    Many regards
    M.L.

    Hello Andreas,
    certainly I had searched the forum before I asked and I read also the thread you sent me. But to my knowledge (please correct me if I'm wrong!) there wasn't a hint anywhere about migrating your 3.x ds to a 7.0 ds as a prerequisite for RDA. That was the reason why I asked.
    I have still another open thread concerning RDA: [How to do this: loading a huge number of records via delta (RDA)?|How to do this: loading a huge number of records via delta (RDA)?] If you have notice of documentation about the Hybrid Provider model (see thread), please don't hesitate to answer, points will be rewarded...
    Best regards
    Martin Lehmann
    Edited by: Martin Lehmann on Feb 29, 2008 1:29 PM

  • Issue in the Delta load using RDA

    Hi All,
    I am facing an issue while trying to load delta using RDA from R/3 source system.
    Following are the steps followed:
    1. Created a realtime Generic Datasource with timestamp as delta specific field and replicated it to BI.
    2. First I have created the Infopackage(Initialization with data transfer) and loaded upto PSA.
    3. Created a standard DTP to load till DSO and activated the data.
    4. Then created a realtime delta infopackage and assigned it to a Daemon.
    5. Converted the standard DTP to realtime DTP and assigned the same to the Daemon.
    6. Started the Daemon, giving an interval of 5 minutes.
    In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records).
    Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
    Can anyone please help me to solve these issues.
    Thanks & Regards,
    Salini.

    Salini S wrote:
    In the first time, Initialization with data transfer is taking the records correctly. But when I run Daemon for taking delta records, its taking all the records again, i.e. both the previously uploaded historical data and the delta records). .
    If I understand you correctly you Initially did a full load. Yes? Well next you need to do intialise & after that delta.
    The reason is that if you will select delta initialisation & initialisation without data transfer- it means delta queue is initialised now & next time when you will do delta load it will pick only changed records
    If you will select delta initialisation & initialisation with data transfer- It means delta queue is initialised & it will pick records in the same load.
    As you know your targets will receive the changed records from the delta queue.
    Salini S wrote:
      Also after the first delta run, the request status in the Daemon monitor, for both Infopackage and DTP changes to red and Daemon stops automatically.
    I take it the infopackage has run successfully? Did you check? If it has and the error is on the DTP then i suggest the following.
    At runtime, erroneous data records are written to an error stack if the error handling for the data transfer process is activated. You use the error stack to update the data to the target destination  once the error is resolved.
    To resolve the error, in the monitor for the data transfer process, you can navigate to the PSA maintenance by choosing Error Stack in the toolbar, and display and edit erroneous records in the
    error stack.
    I suggest you create an error DTP for an active data transfer process  on the Update tab page (If key fields of the error stack for DataStore objects are overwrite On the Extraction tab page under  Semantic Groups, define the key fields for the error stack.)  The error DTP uses the full update mode to extract data from the error stack (in this case, the source of the DTP) and transfer
    it to the target that you have already defined in the data transfer process. Once the data records have been successfully updated, they are deleted from the error stack. If there are any erroneous data records, they are written to the error stack again in a new error DTP request.
    As I'm sure you know when a DTP request is deleted, the corresponding data records are also deleted from the error stack.
    I hope the above helps you.

  • Real time data aquisation(RDA)

    hi
    if i want use datasource for RDA , its support in r/3 side? so its wont support for flat file?
    where can i check  the data source will support for RDA or not?
    once datasource replicated while creating infopackage need to check check box and dtp need to check RDA

    goto SAP system
    goto transaction SE16
    give ROOSOURCE in Table and execute.
    in the next screen give ur DATASOURCE name and execute.
    this will give the datsource settings  check the realtime field if its checked then ur datasource is real time enabled.
    else u can enable it by writing a small program.
    goto se38
    cerate an executable program with the following code
    Tables : ROOSOURCE.
    Parameters :  P_OLTPSR LIKE ROOSOURCE-OLTPSOURCE.
    UPDATE ROOSOURCE set REALTIME = 'X' 
    WHERE  OLPTSOURCE = P_OLTPSR
    and   OBJVERS = 'A'.
    When u execute this program it asks for datasource name , give ur datasource name and execute. it will real time enabled.
    u can again check it in SE16.
    hope this helps.

  • WHAT IS DAEMON CONCEPT IN RDA ?

    HI EXPERTS,
    WHAT IS DAEMON CONCEPT IN RDA ?HOW IT WORKS ?
    I will assign points for ur valuable answers

    HI,
    In the monitor: real-time data acquisition (transaction RSCRT), the daemons that are currently in the system are displayed in a tree structure.
    It also contains the monitor functions for processing the daemons and the InfoPackages. You can create, stop, and delete daemons and you can execute other functions for the functions. For InfoPackages, you can start, stop, or cancel data transfer, among other things, as well as assign a daemon.
    Functions
    Overview of the daemons
    Below a daemon, the InfoPackages are displayed that are assigned to a daemon and that are controlled by it. Below an InfoPackage, the ODS objects are displayed that are supplied by this InfoPackage. Below the ODS objects, the requests for the current and last day are displayed that have supplied the ODS objects with data. The legend provides you with information on the navigation options in the overview of the daemons, and also on the symbols for the various levels of the overview. You can update the overview using Extras ® Refresh.
    Daemon
    The real-time data acquisition daemon is a background process that processes the InfoPackages assigned to it. It receives information from the InfoPackage as to when and how often the data is to be extracted, which data targets are to be supplied, when a request is to be closed and a new one opened. It also receives information on the definition of the data transfer and on the status.
    The daemon works on the basis of the list of the DataSources assigned to it via the InfoPackage, extracts the data from the source systems and transfers it to the PSA table and the ODS objects. It informs the Service API in the source system when the data for the source system has been successfully updated. If the PSA request has completed successfully and a new delta request has been opened, the updated data is deleted from the delta queue of the source system.
    Several daemons that work on disjunctive combinations of DataSources can be used. If several DataSources supply one ODS object, the same daemon has to be used for these DataSources, that is one ODS object can always only be supplied.
    The daemon runs in a permanent background job and only switches to a "sleep" mode after performing a data transfer if there is currently no other data in the delta queue. The RFC connection to the source systems is maintained. This implies that a permanent RFC connection is required between every source system and the SAP BW for real-time data transfer.
    So that not too much main memory is used and the RFC connection does not have to exist for too long, the daemon ends every hour on its own and schedules again, so that the main memory can be released again and a new RFC connection is opened.?? This happens without the real-time requests having to be closed.
    Tarak

  • Datasource Creation for Informatica Source system in NW2004s

    Hi,
    We are upgrading BW 3.5 to SAP NW2004s. In NW2004s Create datasource
    is new feature provided in BW 7.0.
    I tried to create this datasource for Flat file and worked fine. We
    are also using Informatica as source system (External System).
    Whenever I tried to create datasource for External system such as
    Informatica, it gives message
    "Datasource ZTEST(INFPCPD):Object Type RSDS not supported in BAPI
    Source System"
    Is it a bug? or Creation of datasource is not supported incase of
    Informatica or external system?
    Thanks
    Rupesh

    Hi Rupesh,
    The latest BI release in SAP NetWeaver 7.0 (2004s) includes a new type of DataSource for which staging BAPI has not yet been aligned.
    Third party ETL tool vendors can therefore only implement their load processes using the original type of DataSource from BW 3.x. This DataSource is still provided in the new release without any changes. Upgrading to NetWeaver 7.0 (2004s) BI (BI 7.0) does not therefore endanger existing implementations based on BW 3.x and NetWeaver 2004 (BW 3.5).
    It is also possible to migrate third party ETL implementations based on BW 3.x into the new data-flow concept of a NetWeaver 7.0 (2004s) BI environment using new DataSources, transformations (also new), and data transfer processes (DTP) (also new). This is possible because the system provides an emulated view for BW 3.x DataSources, which makes it possible to combine them with NetWeaver 7.0 (2004s) transformations and DTPs for regular batch load processing (this does not include direct access and real-time data acquisition (RDA)).
    This allows the benefits of the new data loading concept to be made available in such third party ETL-based loading scenarios.
    Regards,
    Anil

  • Datasource migration from 3.5 to 7

    Hi Expert,
    BI 7 was installed in the environment with datasource 3.5 actviated in source system. I am not sure do I need to migrate datasources from 3.5 to 7.0? Can experts please share with me on what are the features available in datasource 7.0? Will datasource 7.0 improve on delta loading? Is migration a must from datasources 3.5 to 7.0?
    Your reply is much appreciated.
    Thanks and regards,
    Kang Ring

    Hi,
    As correctly pointed out, the datasource migration is not required unless you plan to achieve the following:
    1. RDA (Real Time data acquisition)
    2. Direct access to master data.
    3. Remote activation of datasource (meaning from BW itself, you can acitvate DS in ECC)
    However the only checkpoint is that if you are using hierarchies, those have to be loaded with 3.5 datasources as 7.0 does not support hierarchies. It is supported in 7.3
    Also check the link for BI 7.0 new features.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm

  • Erroneous no of data updation for RDA

    Hi experts,
             i have created a generic datasource made it RDA enabled  for test purpose, executed successfully init of delta. As per method created RDA package assigned package and
    dtp to daemon, settings were period -1 MIN and autometic closure of request in 1 hr. Now i
    added 4 records in table associated with this datasource these 4 recoeds are being updatd in
    DSO in every one minute adding overall 240 records in an hour. What to do?

    Hi sunil ..
    I feel there is problem with your request closing ..of demon..
    Requests are opened and closed as follows:
    .1.      When a daemon is started, it opens a PSA request in the first load process.
    2.      The system opens a DTP request and change log request when the PSA request contains data.
    3.      The daemon uses the threshold values defined in the InfoPackage to determine when to close a
              request. The data transfer process copies these settings from the InfoPackage.
              When a PSA request is closed, the related DTP and change log requests in the same load       
              process are closed too.
    4.      When the requests are closed, new requests are opened automatically the next time the daemon
             accesses data and the data transfer for real-time data acquisition continues with these new 
             requests.
    5.      Again, the system only opens a DTP request and change log request when the PSA request
             contains data.
    6.      If you are transferring data from an SAP source system, data is automatically deleted from the
             delta queue when the new PSA request is opened.
       The data (and the open requests) are available for analysis and reporting as soon as they have been   successfully updated and activated in the DataStore object.
    With real-time data acquisition, the requests (PSA requests, DTP requests and change log requests) remain open across several load processes. The requests are closed when the threshold values set in the InfoPackage are reached. The system opens new requests and data transfer is continued using the new requests. In the monitor for real-time data acquisition, you can close PSA and DTP requests manually.
    If errors occur, you can close an open request manually, correct the error and then restart data transfer.
    Regards,
    Shikha

  • RDA Requirements

    Dear Gurus,
    I currently have an ECC 5.0 R/3 system connected to BW 3.5 and running perfectly on major business areas like sales, inventory, purchasing, FI/COPA etc.
    I am in the process of implementing BI 7.0 as a separate server connected to the same ECC 5.0 R/3 system and intend to use the same datasources currently linked to the BW 3.5 system.
    The requirement is that we will be expensively using RDA for the BI 7.0 extraction and current PI_BASIS component in R/3 is 2004_1_640 at level 10. I suppose this level does not support RDA and I need to upgrade PI_BASIS to the next version.
    The question is would it affect the existing data sources and delta which are already mapped to the BW 3.5 server if I upgrade the PI_BASIS plugin to a version that supports RDA on the R/3 source swystem?
    Regards
    Suneeth

    )How can we identify what datasources are REAL TIME datasources in R/3?
    ==> field REALTIME in table ROOSOURCE
    2)Can any standard datasources be converted to REAL TIME datasources.
    If yes ,what are the steps in details?
    ==> Yes, if the extractor can provide Real-Time data, i.e. at every point in time delta information. A negative example are FI-GL extractors which are only capable to provide data on a daily basis.
    If you identify such a DataSource and the DataSource is critical to your project success, please contact me directly via EMail.
    Proceeding is as follows (SPS8 is recommended):
    a.) Set field ROOSOURCE-REALTIME for respective DataSource (per customer ABAP report)
    b.) Replicate DataSource
    c.) Create DeltaInit InfoPackage and execute
    d.) Create Transformation and DTP to a DataStore Object (if applicable)
    e.) Create a daemon in Real-Time Monitor (Transaction RSRDA)
    f.) Locate your DataSource in the 'Not assigned' part of the tree structure
    g.) Assign InfoPackage and DTP to daeomon (via context menu on the DataSource)
    h.) Start the daemon
    3)Why only ODS is used to load for REAL TIME datasources and not INFOCUBES.
    ==> Since data is immediately available for reporting and we have an open request we have a specific update processing for the data target (with a special DTP). This has currently only been implemented for DataStore Object.
    4)Can generic datasources be built as REAL TIME datasources.
    Yes
    Real-Time Data Acquisition -BI@2004s
    Hope it Helps
    Chetan
    @CP..

Maybe you are looking for