Real time infopackage

Hello
Could you please let me know RDA is used for which DSO ?
Real time infopackage support to which DSO and why ?
Regards

Hi........
We use Standard DSO in RDA..........Real-time data acquisition supports tactical decision making. In terms of data acquisition, it supports operational reporting by allowing you to send data to the delta queue or PSA table in real time. You use a daemon to transfer DataStore objects that have been released for reporting to the DSO layer at frequent regular intervals. The data is stored persistently in BI.
You use real-time data acquisition if you want to transfer data to BI at frequent intervals (every hour or minute) and access this data in reporting frequently or regularly (several times a day, at least). The DataSource has to support real-time data acquisition. The option to support real-time data acquisition is a property of a DataSource.............
Real-time data acquisition can be used in two primary scenarios:
via the Service API (SAPI). It incorporates usage of InfoPackage for
Real-time Data Acquisition (source to PSA). It then leverages Data Transfer
Process for Real-time Data Acquisition (PSA to DataStore Object).
via a Web Service Incorporates usage of Web Services to populate the PSA
which then leverages the Real-time DTP to transfer data to the DataStore
Object
Regards,
Debjani........

Similar Messages

Problem in REAL TIME loading

Hi Expert !
The problem is that the REAL TIME infopackage load 0 records.
I build a real time extractor in R3 based on a view (Fi table) .
In BW i created a dso DTP (DTP FOR REAL TIME) infopackage(Adapter: REAL TIME) .
the dtp and the infopackage are assign to DEAMON.
the problem is that 0 records load.
Whats the problem ?
Thanks in advance
Miki

Hi Miki,
I don't think you have any problem.
The data is being loaded into the infocube. When the number of records exceeds the threshhold value (normally 50000) the package will be closed and a new package will be available.
You could go to the infocube and right click -> Change real-time Load Behavior. Then select the first option. The system will then close the request and you can see that there is data in there. Don't forget to put back the option otherwise you can't get new data in.
regards,
Raymond Baggen
Uphantis bv

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 DTPs

Hi all,
I feed SAP BI/BW by a number of Webservices (WS). More or less everthing works fine. Each Web Service has his own Real Time Infopackage which works absolutly fine. In addition most of the Web Services have a real time DTP that is also working fine.
But for one of the WS I am not able to create a realtime DTP.
Does somebody know what the requirments are that you can setup a realtime DTP?

Hi.
Please check the documentation on SAP Help, in the following link:
http://help.sap.com/saphelp_nw70/helpdata/en/42/f80a3f6a983ee4e10000000a1553f7/frameset.htm
Thanks,
Walter Oliveira

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

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.

About DTP with real-time access.

Hello Gurus,
       setting for error handling only has an impact while repairing a DTP request (repair) and during the conversion of the DTP to standard DTP (for example, to correct an error during extraction).
      will you please give a simpel scenario to explain above words?
thank you very much.
Fran

Hi,
Use :
With SAP NetWeaver 7.0, SPS 14, the following changes and enhancements are available for real-time data acquisition:
●      Changes to the menu and the context menu of the monitor for real-time data acquisition
The menu and the context menus for the individual objects in the monitor for real-time data acquisition have been standardized and enhanced. In particular, it is now possible to assign daemons and data transfer processes on various levels using context menu entries. For a complete overview of the functions in the menu and in the context menus, see Monitor for Real-Time Data Acquisition.
●      Assignment of daemons for InfoPackages and data transfer processes (DTP)
To assign InfoPackages and data transfer processes to a daemon, you can call the monitor for real-time data acquisition in the following ways:
○       In the Data Warehousing Workbench using the respective context menu entry Assign RDA Daemon.
○       In InfoPackage maintenance using the Schedule tab page, and in data transfer process maintenance using the Execute tab page.
The button names for jumping to the monitor for real-time data acquisition have changed here. To jump to the monitor, choose Assign Daemon.
●      Repair process chains for repairing a broken data transfer or a missing delta in the DataStore object
In certain situations, a gap in the delta of the DataStore object can occur if there is a closed request in the PSA but there is no corresponding request in the DataStore object. For example, this is the case if a DTP request has terminated due to an error in the transformation. Here, you can create a repair process chain to repair a missing or broken update from the PSA. The repair process chain contains a standard DTP as well as any further processes required for subsequent processing (such as activating the data in the DataStore object or subsequent process chains). When the repair process chain is executed, the complete delta is loaded from the source into the DataStore object and processes for activation and further processing are executed if required.
●      Process types for starting and stopping real-time data acquisition
You can use process chains to control real-time data acquisition using process types Start Real-Time Data Acquisition (RDA) Load Process and Stop Real-Time Data Acquisition (RDA) Load Process.
More Info :
http://help.sap.com/saphelp_nw70/helpdata/en/47/2731751c2a2dede10000000a1553f7/frameset.htm
Regards
Ram.

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?

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 DAEMON Stops and gets inactivated.

Hi,
We have real time DAEMON loading the data from delta queue to the ODS.
It becomes inactive after some time with lots of error messages. Don't understand what they mean . How to get documation to understand what the problem is and how to activate them again ?.
Also, I have another DAEMON, which gets to STOP condition. It doesn't start again even if I try to "Start" it in RSCRT transaction. How to start it again ?. It also gives error messages.
Thanks.

Hi,
Daemon is inactive when no batch job runs for this daemon and no upload via the assigned InfoPackages.
Daemon starts after it has a free batch job and currently no upload with the assigned InfoPackages.
Daemon is stopped when the started data transfers are completed and all related requests are closed.
hope it helps....

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

Real Time on FI-GL

Hi Friends
We have fi-gl and ec-pca data loads currently with period selection full loads .
Business wanted the real time data for their reporting. Our businessdont close the posting periods. They still do postings for 2008 periods and postings happens around the clock over the month end.
We have checked direct access but didn't work.
Is RDA (real time acquicition) works with FI-GL models? I know RDA doesn't work for 0FI_GL_4 datasource.
Is it possible with generic delta method by conatenating cpudt and cputm from bkpf table and use timestamp as a delta enable field?
Please your quick response will be appreciated..
Regards,
Chandu.

The answer for your question on how to find if a data source is RDA
enabled is given below .
Use SE16 to browse the details of your datasources in ROOSOURCE table
If the 'Real-Time Enabl' shows an 'X'it means your datasources are real-
time compatible
See this link .
http://help.sap.com/saphelp_nw2004s/helpdata/
en/52/777e403566c65de10000000a155106/frameset.htm
But if the data source is not real time enabled then you cannot see
that option in the DTP .
SAP has not released the FI-GL datasources with RDA feature, if you
check the delievered version of the FI-GL datasources you will see
that the flag 'Realtime-enabled' is missing. No date has been set yet
for when these datasources will be RDA enabled.
2:
If you really need to use the RDA functionality with the FL-GL
datasources you can use the following workaround:
A: In the table ROOSOURCE set the Flag 'Realtime' to 'X' for
the datasource you want to RDA enable.
To set the RDA flag for the datasource you can use a program like
the following:
REPORT Z_RDA_FLAG.
DATA: ROOSOURCE.
Update ROOSOURCE set REALTIME = 'X'
where OLTPSOURCE = 'put the name of the datasource here'
and OBJVERS = 'A'.
B. Replicate the DataSource into BW
C. Create a DSO Object
D. Migrate the DataSource (right mouse on DataSource in RSA1 DataSource
   overview)
E. Create transformation.
F. Create DTP of type 'Realtime'
G. Create InfoPackage for Init-Simulation (Delta-init load without data
transfer) and trigger the Request for the data load
H. Create another InfoPackage for Realtime data acquisition
I. Create a demon directly from InfoPackage maintenance or via
   transaction RSRDA. Assign DataSource and Realtime DTP to demon. Start
   demon; upload period is 1 minute.
3: The steps in point 2 above is a workaround so we do not support it as
   it is not part of SAP standard functionality.However if you test this
   carefully in your DEV and QA environments you should find that the
   Process works.
PLEASE PAY ATTENTION TO THE FOLLOWING INFORMATION REGARDING RDA:
1. RDA can only be used for completely new scenarios! The reason is that
you need a DataSource of the 7.0 type, not of 3.x type. Since you
migrate a 3.x DataSource into a 7.0 DataSources, the existing transfer
rules and mapping between DataSources and InfoSources are lost (deleted)
or archived. It can destroy your existing scenario. Please be very
cautious and use the Realtime Data Acquisition functionality on a
complete new scenario. Make sure that the DataSource in question you
would like to migrate or to replicate as a 7.0 DataSource, is not
used for other Data targets in your BW system!
2. Be aware of the fact that as soon as you decide to use RDA method,
you cannot load delta via the 'usual' delta upload for the same
scenario anymore. It is not possible to switch between RDA demon usage
and a non-RDA delta loads in the same data flow.
At the moment, no Content-delivered DataSources can be used for RDA
in Standard because the flag 'Realtime-enabled' is missing in the
delivered version. You'd better to wait for 'Realtime' Flag delivering
in DataSource standard done by the corresponding application.
regards,
Colin Moloney

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

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

Real time infopackage

Similar Messages

Maybe you are looking for