Real Time datasources

Few questions regarding REAL TIME datasources -
1)How can we identify what datasources are REAL TIME datasources in R/3?
2)Can any standard datasources be converted to REAL TIME datasources.
If yes ,what are the steps in details?
3)Why only ODS is used to load for REAL TIME datasources and not INFOCUBES.
4)Can generic datasources be built as REAL TIME datasources.

Hi,
please see my answers underneath the respective question.
1)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
Cheers
SAP NetWeaver BI Organisation

Similar Messages

Has anyone implemented real time datasource for COPA ?

Hello,
Has anyone implemented a real time data source for COPA ? Please share details of the process for how this can be set up. Thanks.

Hi,
Please follow the following steps...
COPA Extraction
The below are the command steps and explanation. COPA Extraction -steps
R/3 System
1. KEB0
2. Select Datasource 1_CO_PA_CCA
3. Select Field Name for Partitioning (Eg, Ccode)
4. Initialise
5. Select characteristics & Value Fields & Key Figures
6. Select Development Class/Local Object
7. Workbench Request
8. Edit your Data Source to Select/Hide Fields
9. Extract Checker at RSA3 & Extract
BW
1. Replicate Data Source
2. Assign Info Source
3. Transfer all Data Source elements to Info Source
4. Activate Info Source
5. Create Cube on Infoprovider (Copy str from Infosource)
6. Go to Dimensions and create dimensions, Define & Assign
7. Check & Activate
8. Create Update Rules
9. Insert/Modify KF and write routines (const, formula, abap)
10. Activate
11. Create InfoPackage for Initialization
12. Maintain Infopackage
13. Under Update Tab Select Initialize delta on Infopackage
14. Schedule/Monitor
15. Create Another InfoPackage for Delta
16. Check on DELTA OptionPls r
17. Ready for Delta Load
LIS, CO/PA, and FI/SL are Customer Generated Generic Extractors, and LO is BW Content Extractors.
LIS is a cross application component LIS of SAP R/3 , which includes, Sales Information System, Purchasing Information System, Inventory Controlling....
Similarly CO/PA and FI/SL are used for specific Application Component of SAP R/3.
CO/PA collects all the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs). FI/SL collects all the OLTP data for financial accounting, special ledger
1) Add the fields to the operating concern. So that the required field is visible in CE1XXXX table and other concerned tables CE2XXXX, CE3XXXX etc.
2) After you have enhanced the operating concern then you are ready to add it to the CO-PA data source. Since CO-PA is a regenerating application you can't add the field directly to the CO-PA data source. You need to delete the data source and then need to re-create using KEB2 transaction.
3) While re-creating the data source use the same old name so that there won't be any changes in the BW side when you need to assign the data source to info-source. Just replicate the new data source in BW side and map the new field in info-source. If you re-create using a different name then you will be needing extra build efforts to take the data into BW through IS all the way top to IC. I would personally suggest keep the same old data source name as before.
If you are adding the fields from the same "Operating concern" then goto KE24 and edit the dataaource and add your fields. However if you are adding fields outside the "Operating concern" then you need to append the extract structure and populate the fields in user exit using ABAP code. Reference OSS note: 852443
1. Check RSA7 on your R3 to see if there is any delta queue for COPA. (just to see, sometimes there is nothing here for the datasource, sometimes there is)
2. On BW go to SE16 and open the table RSSDLINIT
3. Find the line(s) corresponding to the problem datasource.
4. You can check the load status in RSRQ using the RNR from the table
5. Delete the line(s) in question from RSSDLINIT table
6. Now you will be able to open the infopackage. So now you can ReInit. But before you try to ReInit ....
7. In the infopackage go to the 'Scheduler' menu > 'Initialization options for the source system' and delete the existing INIT (if one is listed)
Regards,
Tapan

Cannot check real time access while creating infopackge

Hi all,
I am getting an error while trying to create a real time infopackage. I have made my datasource real time by changing the real time flag in ROOSOURCE but while creating the infopackage the real time check is greyed out.
I had read in some other message in SDN that you can make non-real time DS into real time by changing the flag in ROOSOURCE any ideas.
Also we are in content 7.0.3 and I dont see any business content either in ECC or BI in ROOSOURCE table with real-time flag marked X. Does SAP delivery any content which are real time or am I missing something here?
thanks for your input

Hi Raj,
You can create the Real-Time infopackage only after creating the info-package for Init Load. The check box for Real-Time is not enabled if Initialization load is not run. Though this check has to be made only after creating the Real-Time Datasource correctly.
Go to RSO2, enter the datasource name, and open it in edit mode. Then choose the option 'generic delta'. Give the field on which you want the Delta pointer to be set (The field you want to enter here should NOT be hidden from SAP BW). Importantly, check the option 'Real-Time Enabl'. save the datasource. It becomes Realtime. Replicate the datasource.
Hope this helps.
Thanks,
Praneeth.

Real-time data acquisition for HR datasources

Dear Experts,
I have a couple of questions on real-time data acquisition...
a) Can you tell me if any standard HR datasources support real-time data acquisition?
b) Can we apply real-time data acquisition for generic datasources? If yes, is there any difference in the process compared to working with business content datasources when using real-time data acquisition?
Hope you can provide some answers...as always, points will be awarded for answers that effectively address the questions.
Thanks a bunch.
K

Hi Karthik,
a)The decision to go for SAP remote cube depends on the volume of data and the frequency of queries. It is advicible not to use the SAP remote cube if the data volume is high and also, the query frequency is high. Which module in HR are yuo implementing? In HR, the data volume is generally high. So, if you go for loading the data from R/3 every 3 hours, you are asfe as long as the loading volumes are less. For example, for implementing Time management, I would not advice frequent loads as it is time consuming process. So, make a decision based on the above mentioned lines. If the data volume is not high, I would prefer the SAP ermote cube as it will reduce managing the loads.
b)I mentioned FM extractor just for the sake of control of data selection. You can even go for view/table extractor.
Hope this helps.
Thanks and Regards
Subray Hegde

Datasource:Real time enabled

Hello everybody,
Hope to have your valuable suggestions on this
1:Is it possible for me to copy a standard FI datasource .I need to have 0FI_AR_4 ,which is currently active and in use ,datasource real time enabled
2:I do not want to go to roosource table and modify the table to make this real time enabled.Is it possible for me to create a new datasource(not generic since i would have to create view/query etc) copying this 0fi_ar_4 and have it real time enabled
3:I tried RSDS transaction.however its not helping me to copy or create
regards
savi

Andreas/Michael,
I would like to add a different dimension to this topic mentioned by you.
Please do correct if wrong.
Problem -
The FI line item delta DataSources can identify new and changed data only to the day because the source tables only contain the CPU date and not the time as time characteristic for the change.
This results in a safety interval of at least one day.
and thats why we cannot enable this datasource as Real Time;however please refer this note below and help me understand how would this fit the aforementioned bill.
Note 485958 - BCT-FI: Extracting FI line items up to the current date
Solution
Due to a customized setting, it is now possible for the FI line item extractors to read the data up to the current date during the delta runs.
During the next delta run, the data is then read again from the day when the previous extraction was called, up to the current day of the call for the new extraction.This means that the delta extraction of the data always occurs with time intervals overlapping by one day.
The delta calculation by the ODS objects ensures that the repeatedly extracted data does not cause duplicate values in the InfoCube.
Hope it Helps
Chetan
@CP...

Problems with real-time extraction from generic datasource.

Hello,
I have a real-time extraction from generic datasoruce with numeric field as a delta pointer. I have created an initilization infopackage, delta IP and real-time IP, real-time data transfer process, real-time deamon. The problem is that real-time extraction does not see delta updates. Deamon creates requests in PSA every minute, but there are all empty. When i delete the deamon and shedule not real-time delta infopackage, it loads delta records correctly. Version of BI - 7.0 SP 18.
The second question: a cannot stop real-time deamon. I stop it in RSRDA, but when i try to shedule standart IP, i get an error, that deamon is still running. So i have to delete it and recreate.
And the 3rd question, theoretical. What real-time extraction is necessary for? As i understand, i can create a process chain that will be sheduled every 1 (5, 10, ...) minute. What are advantages of real-time extraction rather such variant?
Thanks.

Hi,
1.Note 1113610 - P17:SDL:PC:RDA:Daemon runs: Do not start delta/init IPackage
Summary
Symptom
When a daemon runs or is scheduled, you may not start a 'normal' delta/init InfoPackage.
Other terms
RDA, real-time data acquisition, daemon, InfoPackage, scheduler
Reason and Prerequisites
This problem is caused by a program error.
Solution
SAP NetWeaver 7.0 BI
Import Support Package 17 for SAP NetWeaver 7.0 BI (BI Patch 17 or SAPKW70017) into your BI system. The Support Package is available when Note 1106569 "SAPBINews BI7.0 Support Package 17", which describes this Support Package in more detail, is released for customers.
**********you can apply the correction instructions provided in the note
2.i refered closing of the request in the target i.e DSO not psa.
3. Note 1000157 - RDA daemon does not get data from delta queue
Summary
Symptom
You use Real-time Data Acquisition (RDA) to load data from an SAP source system. After several hours or days, the system no longer reads the data from the delta queue. In the RDA monitor, you can see that the InfoPackage has been executed, however the data transfer process (DTP) has not been executed for a long time. In transaction RSA7 in the source system, you can see that there is already data in the delta queue.
Cheers,
swapna.G

Process Chain for Real Time Demon

Please help I am stuck I followed the step by sdn but this is missing in step. how to create now process chain.
I created the below
DSO CONNECTED TO dATASOURCE via Trans,
Real Time IP
Real Time DTP
assigned to Datasource and assigned the DS, IP, DTP to Deamon in RSRDA. NOW I started also manually via start all IP. but How to set the process chains now.
PLEASE HELP ME STEP BY STEP TO PROCESS CHAIN SINCE i am new to this daemon in process chains
Thanks
Soniya
null

Hi
refer to this
CREATION OF PROCESS CHAINS
Process chains are used to automated the loading process.
Will be used in all applications as you cannot schedule hundreds of infopackages manually and daily.
Metachain
Steps for Metachain :
1. Start ( In this variant set ur schedule times for this metachain )
2.Local Process Chain 1 ( Say its a master data process chain - Get into the start variant of this chain ( Sub chain - like any other chain ) and check the second radio button " Start using metachain or API " )
3.Local Process Chain 2 ( Say its a transaction data process chain do the same as in step 2 )
Steps for Process Chains in BI 7.0 for a Cube.
1. Start
2. Execute Infopackage
3. Delete Indexes for Cube
4.Execute DTP
5. Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Execute DTP
5. Activate DSO
For an IO
1. Start
2.Execute infopackage
3.Execute DTP
4.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage ( loads till psa )
3.Execute DTP ( to load DSO frm PSA )
4.Activate DSO
5.Further Processing
6.Delete Indexes for Cube
7.Execute DTP ( to load Cube frm DSO )
8.Create Indexes for Cube
3.X
Master loading ( Attr, Text, Hierarchies )
Steps :
1.Start
2. Execute Infopackage ( say if you are loading 2 IO's just have them all parallel )
3.You might want to load in seq - Attributes - Texts - Hierarchies
4.And ( Connecting all Infopackages )
5.Attribute Change Run ( add all relevant IO's ).
Start
Infopackge1A(Attr)|Infopackge2A(Attr)
Infopackge1B(Txts)|Infopackge2B(Txts)
/_____________________|
Infopackge1C(Txts)______|
\_____________________|
\___________________|
__\___________________|
___\__________________|
______ And Processer_ ( Connect Infopackge1C & Infopackge2B )
__________|__________
Attribute Change Run ( Add Infobject 1 & Infoobject 2 to this variant )
1. Start
2. Delete Indexes for Cube
3. Execute Infopackage
4.Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Activate DSO
For an IO
1.Start
2.Execute infopackage
3.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage
3.Activate DSO
5.Further Processing
6.Delete Indexes for Cube
7.Execute Infopackage
8.Create Indexes for Cube

Error when activating Real Time Data Source

Hi..
I created a generic datasource in R/3 system via RSO2, with the Real-time check box enabled in the settings for Generic Delta. I saved the datasource. Replicated it into BW System.
I tried to activate this Real time Data Source in BW, it says "Error when activating Data Source".
I am on BI 7.0, with PI_BASIS: 2005_1_700.
Please let me know if you need any further information.
Thanks,
Sai.

Hi sai,
Can you specify from where you have created your geneic data source like by using DB tabl/view/infoset query.
am

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.

The problem with Real-Time Data Acqusutuin

Hi , all
I created ds with Generic Delta : Delta-Specific Fields pointed time stamp and in settings checked Real-time Enabl . After that created modeling in BW , made initial update like discribed in SAP Documentation , created one more infopackage with adapter :Real-time extraction from sap , assigned infopackage and dtp to daemon and started job of daemon .
Request stay yellow all of time and dosn't bring no one records of changes in R3 . Anybody know what is the couse for that? Maby I forgot to check something anywhere or star trigger anyone!?

The following setup working fine for me
In R/3 for Generic Delta ---
        Filed Name - AEDTM
        0Calday -- Radio Button - 'ON'
        Upper Limit - 0
        Lower Limit - 2
        Real_Time enabl - Check Box - 'ON'
        New Status for changed records - Radio Button - 'ON'
In BI
    Create infopackage (init) for replicated datasource
    Execute the DTP to load this init data to DSO.
    Do NOT activate DSO
    Now create another Infopack (real_time Enable & ) and create real-time DTP.
In RSRDA
    Create a Daemon
    Assign InfoPack & DTP to Daemon.
    Now start daemon...Here the message says something like 'one of the request is not activated'.
    Now, select DTP under Daemon --> use menu Edit --> Repair Chain --> Execute
    (If repair chain is not yet there then Daemon --> use menu Edit --> Repair Chain --> Generate and
     once this is done execute the using the above path). Once the chain finishs
    Now start Daemon and refresh.
    Now u can see, an open request (yellow) under infopackage.
    As soon as the new records gets load into PSA, then an open request starts under DTP.
    (Note: If no new data available in PSA, no open request starts under DTP)
Also note that, RDA requests (in PSA & DSO Manage) should always be in yellow, that means Real-Time Aquisition is working.

Problem with Real Time Data Acquisition

Hello,
I tried to built a RDA data flow according to the SAP-Help and this blog (/people/kamaljeet.kharbanda/blog/2006/11/13/real-time-data-acquisition-bi2004s), but I ran into a problem. Everything seems to be fine, but even though the daemon is running no new data is added to the DSO. I'll explain in detail what steps I took and hope someone can pinpoint my error(s).
System is BW4 on SPS 17. My datasource as well as my DSObject are in the same system
1.) Created a transparent table with a timestamp-field for generic delta as a local object.
2.) Created a generic datasource from view/table (used the above table), marked it as realtime-enabled and used timestamp as delta-specific field.
3.) Replicated the metadata for my datasource and activated it.
4.) Created a Data Storage Object with infoobjects corresponding to the table fields
5.) Created a transformation between DataSource and DSO
6.) Created a DTP from Data Source to DSO. The type is realtime-DTP.
7.) Created an InfoPackage for Delta-Initial Load. Update mode: Initialize Delta Process -> Initialization with Data Transfer.
8.) Then I changed my DTP (step 6) to "normal DTP" and executed it. Then activated the data in the DSO. The datasets from the table (which i filled with an ABAP-program) were successfully loaded and activated. So now my DSO contains 5 datasets.
9.) Changed the DTP back to "realtime DTP"
10.) Created an InfoPackage for RDA. Adapter is set to "Realtime extraction from SAP System"
11.) Created a daemon, assigned the IP for RDA and the DTP to the daemon and started it up.
12.) Executed my ABAP program to added 3 datasets to the table which is used as a datasource.
So now in my source table there are 8 datasets, but the daemon won't load them. In my RDA-Monitor (trx rsrda) it shows my daemon, the assigned IP and the assigned DTP (status green). Under the IP there's one yellow request (that should be right according to the help), but unlike the picture in the blog (link see above) there's no request under the DTP.
Job overview (sm37) shows an active batch job and some jobs that are ready (every 10minutes a new batch starts and the old one is closed). the job log shows, that the daemon runs, but loads no data...
i think it might be a problem with the delta extraction somewhere, because the intial load works fine and there are no errors anywhere.
Edit: perhaps my settings in the data source unter tab: extraction are wrong?
Delta process: AIE After Images By Extractor (can't change that)
Direct Access: Allowd
real Time: Real-Time DA Supported
Adapter: realtime data extraction (also tried Access to SAP Data through Service API which seems senseless)
Data Format: Fixed Lenght
Anyone can explain what those fileds mean and which one i should use?
Edited by: Christoph Jender on Apr 10, 2008 2:48 PM
Edited by: Christoph Jender on Apr 10, 2008 3:33 PM

Hi again, another thing i'd like to try is to just active a business content datasource which is realtime-enabled and has the ability to dynamically add some values so that i can test if it works. but i have no idea what business content would be applicable here, any ideas on that perhaps?

Real-Time Enabled field and Generic extarctor

Hey,
We are using PI 2004_1_470 on our R/3 system, and I just noticed that there is a field called Real-Time Enabled on the generic delta screen. This maps to ROOSOURCE-REALTIME.
What is the field being used is? Is this some early release of the near real time function that will be part of BW 7.0, or can I use this with BW 3.5?
Thanks Bill!

Hi Mickey,
in general:
1.) you need a 7.0 DataSource (3.X DataSources cannot deliver Real-Time information)
2.) you can only run a DataSource in one mode, either "Real-Time Data Acquistion" or "Standard", i.e. the same DataSource cannot be incorporated in the data flow in different modes.
3.) Business Content DataSources are not delivered with the option "Real-Time Data Acquistion" at the current point in time. We are currently discussing which DataSources should be made available to start off with.
If you have specific scenario in mind, please contact your Ramp-Up Coach in order to direct support by us.
Cheers
SAP NetWeaver2004s Ramp-Up BI Back Office

Regarding PSA real time scenarios and things

Hai
I knew abour PSA therotically . But i want in detail real time scenarios concering about PSA . Like , if data laoding is failed then how to look at PSA and after identifying how to update to corresponding datatarget like this ......
So please tell in detail some real time scenarios about PSA and also send some documents or weblogd or old forums to [email protected] now
I ll assign the points for thanks
bye
mohammed

hi chakri, go through this.
1.The Persistent Staging Area (PSA) is the inbound storage area for data from the source systems in the SAP Business Information Warehouse. The requested data is saved, unchanged from the source system. Request data is stored in the transfer structure format in transparent, relational database tables in the Business Information Warehouse. The data format remains unchanged, meaning that no summarization or transformations take place, as is the case with Info Cubes.
2. The data records in BW are transferred to the transfer structure when you load data with the transfer method PSA. One TRFC is carried out per data package. Data is written to the PSA table from the transfer structure, and stored there. A transparent PSA table is created for every transfer structure that is activated. The PSA tables each have the same structure as their respective transfer structures.
3. The number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length of the data record is limited to 1962 bytes when you use TRFCs.
4. Four types of updates a) psa and data targets parallel b)psa and data targets serially c) only psa with subsequent updates to data targets d) only data targets
5.Since the data is stored in transparent tables in database we can edit the data in psa using ABAP routines using PSA-APIs.
6. u can delete the requests from the PSA for the incorrect data provided that the concerned request data is not populated into data targets.
7. table for PSA:There is only one table for all psa requests.One way to know the psa table name is by right click the psa node and 'maintain export datasource', you will see the table name is /BIC/B0000xxxx (System generated psa table name ) ('ExtractStru.') with se16 you can see the contents, each request no. displayed in field REQUEST.
8. reporting: We can not report directly on psa as the same data is coming form the source system we can see a report from the source sytem. How ever technically speaking we can have a report on that. You are creating an export datasource on it and report using a Remotecube. you could even create an ODS with the same structure of the PSA and push the PSA data into it with no data transformation and then report. When u create an export data soruce on psa it will start with 7 followed by ur PSA name. The below link gives the reporting on psa document.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
Re: Reporting on PSA
Reporting on PSA
9.Changelog and PSA: If we delete data in changelog the data in psa will not be deleted. You have to delete the data in the PSA exclusively.The change log acts as the PSA for the data target if the ODS acts as a datasource. What I mean is if the ODS supplies to another cube/ODS then the source ODS's Changelog is the PSA for the target ODS/Cube.
10.PSA as a data source: create an export data source. The export data source starts with 7 followed by psa name. Go to data marts in the info sources tab and replicate that data source. Create an info source and assign this data source. Activate transfer rules and communication structure Then create a data package and schedule the load to the data target.
11.PSA deletion:
Re: PSA Deletion
12. PSA data in EP:
Re: urgent: PSA Data in EP?
13.Deleting PSA data source:
To delete the export data source
Just go to RSA6 and find the your datasource in the node 'DM', click once (highlight it) and there is a delete icon on the standard icon bar, click on that you should be able to delete the datasource.
Delete PSA datasource
14.Debug load inpsa:
Re: How to Debug a Load into PSA
to load data manually from psa to the data targets.
1. go to rsal .ie administrator work bench
2. under modelling tab choose psa option
3.select your application component
4. choose ur info soruce and expand the tree to see the requests
5. double click on the psa icon
6. a new screen will appear which asks for the no of records to enter give the number and press enter u can see the data in the psa
7. to update psa data manually go to the context menu of that request and select the optio "update date immeditatley" it will be loaded to the data target/
cheers
ravi
dont forget to assign points that is the way of saying thanks in sdn

Real time Implementation scenarios

Hi Gurus,
Can any body send me some real time scenarios on modeling i.e which DataSource used, any enhancements, which cube used ,is that BC on custom cube
Plz
Regards & thanks in advance,
Shiv

This is a Crystal Reports forum. Please close the existing thread an post your question here:
SAP ERP Human Capital Management (SAP ERP HCM)
I would recommend to explain in more detail the business need behind your quesiton in the new posting.
Regards,
Stratos

DTP Born with Incorrect Real-Time Status

Hi Gurus,
What am I doing wrong? When I create a DTP for Real-Time Acquisition, I am getting "Real-Time Status" as "Incorrect" even with a DTP Type correctly set for Real-Time. I have no option to change it for following status:
- New, Without Data Package
- Ready
- Transport Package Read
- Transport Package
- New Transport Package to be Deleted
- Stopped
- Active
- DTP/Infopackage to be closed
I am having quiet few problems to set up DTP with Real-Time Data Acquisition.
Kind Regards,
Gilson

Hi
Not a Guru ,but wanna give it a shot..
Prerequisites for creating Infopackages -
Check
1)The DataSource for which you want to create an InfoPackage supports real-time data acquisition.
2)If you are transferring data into BI using the service API, you have already created an InfoPackage for initializing the delta process for this DataSource, and have completed the initialization.

Closing Requests in the Monitor for Real-Time Data Acquisition
Prerequisites
The daemon is inactive or has errors.
Procedure
In the context menu of the PSA or DTP request, choose Close Request
Barring all those steps mentioned above if I copy you properly ,I put 2 cents on the authorization issue related to RDA.
Check OSS note- 943898
IF at all the note applies to you ,since the patch is not released ,have to go ahead with correction instruction.
Hope it Helps
Chetan
@CP..

Real Time datasources

Similar Messages

Maybe you are looking for