Delta in BI7

HI,
Can anyone please tell me the difference between various options for doing delta init in BI7.
What I want to know specifically is we have the option to choose "delta init. extraction from..." and below we have four options
Active Table (Wih Archive)
Active Table (Without Archive)
Archive (Full Extraction Only)
Change Log
what is the difference between these four options ?.
Once we do a delta init using any of the above options, the following deltas would be from Change Log only....so what would be the impact if i chose the delta init from Active table and then normal deltas from Change Log.
Please let me know ur thoughts.
Thanks,
KR

Hi,
BW Data Manager: Extract from Database and Archive?
The settings in the group frame Extraction From... or Delta Extraction From... of the Data Transfer Process maintenance specify the source from which the data of the DTP is extracted. For a full DTP, these settings apply to all requests started by the DTP. For a delta DTP, the settings only apply to the first request (delta initialization), since because of the delta logic, the following requests must all be extracted from the change log.
For Extraction from the DataStore Object, you have the following options:
Active Table (with Archive)
The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
Active Table (Without Archive)
The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
Archive (Only Full Extraction)
The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
Change Log
The data is read from the change log of the DataStore object.
For Extraction from the InfoCube, you have the following options:
InfoCube Tables
Data is only extracted from the database (E table and F table and aggregates).
Archive (Only Full Extraction)
The data is only read from the archive or from a near-line storage.
hope it helps...
regards,
Raju

Similar Messages

DETA IN BI7

hi all,
Can any one send the screen shots ,how set up delta in BI7.is it in infopackeg level or in DTP level.if i is in infopack level shall i need create 2 infopcks.(one for full & secon for delta) r 2 Dtps?

hi,
In BI 7 data will come upto PSA using infopackage and to load further u need DTP.
U can have Delta in both infopackage and DTP.
first u have to bring the data to PSA using inti update and from PSA to data target using DTP delta. Then u can change the infopackge to delta update. and let the DTP in delta itself.
If u doing a full update then in infopackge choose full and also choose full in DTP.
regards
md zubair sha

Int delta

hi experts,
I cannot find the path to delete the int delta in bi7.0
can any one help me.
give me steps how to delete int delta.
thanks
vijay.

Hi,
take a look:
Multiple Init Requests
Delete delta init in delta channel?
Regards
Andreas

Delta not working after upgrade from 3.5 to BI7.0

Hello All,
We have recently upgraded from BW3.5 to BI7.0 and the standard delta is not working now after the upgade. The name of the Extractor is 0CRM_SALES_ACT_1.
Did anyone come across this problem before or can anyone suggest the solution.
Thanks
Madhu

Hi Madhu,
I've experienced a similar problem with this extractor. I attempted to Initialize Delta with Data Transfer to no avail. The job ran for 12+ hours and stayed in "yellow" status (0 records extracted). The following steps worked for me:
1. Initialize Delta without Data Transfer
2. Run Delta Update
3. Run Full Update and Indicate Request as Repair Request
Worked like a champ, data load finished in less than 2 minutes.
Hopefully this will help.
Regards.
Jason

Delta Timestamps in ECC when upgrading BW3 to BI7

Hi,
We are about to do a technical upgrade of our BW 3.1 system to BI 7.0. BW currently contains a large volume of CO-PA Sales and HR Payroll data that are managed through Delta extractions from ECC6.
When BW has upgraded to BI, can we realistically expect that Deltas will continue without any problems.
I understand that the CO-PA time/datestamp for deltas is stored in Table TKEBWTSN and that the HR Payroll time/datestamp for deltas is stored in Table hrms_bw.
Should we backup these tables before the upgrade, so that if the first delta extracts fails, it would be possible to rerun them after updating these tables.
Are there any other precautions that we could take? Unfortunately our development BI system is not set up for Deltas from an ECC source, so we are unable to properly test.
Any suggestions or feedback on managing Deltas during and postupgrade to BI7 would be greatly appreciated.
Regards
Leanne

Hello Leanne,
See this [Best Practice for Upgrade NetWeaver 7.0BI |https://websmp110.sap-ag.de/~sapidb/011000358700000982302007E]
[SAP NetWeaver 7.0 Business Intelligence Upgrade Specifics|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742]
SAP Note 424848 P18SDLInit sels in source sys lost after upgrade 1.2-2.0 (Applies to BI 7.x)
Note 955990 - BI in SAP NetWeaver 7.0: Incompatibilities with SAP BW 3.x
Note 853507 - Release Restr.: Usage Type BI of SAP NetWeaver 2004s
Please see this link for all [BI7.0 Related upgrade info|https://websmp110.sap-ag.de/upgrade-bi]
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/]

Delta options over 3.5 to bi7

hi guru
can u plz let me know what are the new delta option avialable bi 7 when compare to 3.5
regards
ashwin

Hi,
Please go through following links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
bw 7.0
BI 7.0
Difference in Delta between BW 3.5 and BI 7.0
Regards,
Habeeb
Assign points if helpful..:)

BI7 : Change full load to delta load - things to do?

http://wiki.sdn.sap.com/wiki/display/profile/2007/04/30/Differencebetweenfull,intialanddeltaupdatemodes
Difference: Full load, Delta Load & INIT load in BW
Hi.
Since am not familiar with BW request clarity as to how to achieve the following :
We are on BI 7.
On our BW server, One of the Existing process chain loads data as full load daily Till date.
This schedule runs for about 4 to 6 hours during the nights. And the data seems to be growing.
And doing full load, now seems, not that meaningful for data analysis.
So we now feel we need not do a full load every day. But do only the incremental load.
How to make this effective in our existing process chains.
I went thro the 2 links above, but a few things am not clear.
What exactly needs to be done to change a full load into a delta load.
Also do not wish to have any data loss happening.
We run the schedules on a particular process chain for BW around 1 am.
Say from tomorrow I want to have the data loading as delta.
What exactly are the steps to be followed.
Precautions to be taken
So that we have the correct data load and no data is lost - while doing this.
Things to do am not clear :
do initialization with data transfer / or without data tranfer ?
The make it delta?
So that from tomorrow all data loading becomes delta ?
Or
since in our scenario,
daily basis it is full load.
Just make it delta load,
so that whatever changes will run in the next days schedule.
What all things are to be done stepwise.
if anyone could advise.
That would be very helpful.
Also any documentation which explains all these if someone could share the link please ?
Many thanks
indu
Edited by: Indumathy Narayanan on Aug 26, 2011 5:50 PM

Hi,
Kindly look at following links as well
http://help.sap.com/saphelp_nw04s/helpdata/en/44/9821620553053de10000000a1553f6/content.htm
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Thanks and regards

Delta between DSO and Cube

Hi All,
I have been working on a scenario where in we have to realign org structure information of some sales orders , now we have existing sales orders data in DSO , which feeds to a cube . As part of the realignment some master data attributes, more specifically Customer Master attributes, will be changed in R3 for those Sales Orders.
These attributes are part of the transaction data load which is happening to the DSO from the source, now since this transaction load is taking time, to speed up the process of realignment in BW I have used a routine to lookup the masterdata attributes from 0CUSTOMER in BW.
so before BW pulls the realigned data ( Sales Orders ) from R3, I will run a self loop in the DSO where in it will do a lookup in the 0CUSTOMER master data in BW to get the updated customer attributes (ofcourse the 0CUSTOMER load will happen before we do any realignment of the source data) .
Once the self loop transformation is completed and the sales orders are updated with the updated customer attributes, I will load the data to the cubes. (delta load)
Now once the sales order realignment is finished in R3 , I will pull the same set of data in the DSO .
Now the question is, is it necessary that I do a reinit of the cube before I load the second set of data to the cube?
I guess it is not necessary.
Please share your thoughts.

Hello Partho
I understand your KF are overwrite in DSO. But in BI7 flow delta from DSO to cube is request based.
When you will do a self-loop, same records ( I guess you have already loaded them to cube) will have different request id.
As a result your Change Log table will get different id after activation. So same record will get loaded to cube and which will make all your KF in cube doubled.
I believe to make correction in historical records in cube either you have to delete cube content and then run delta from DSO to cube. As first time delta will read Active table of DSO you will get all KF correct in cube..
Else, you have to delete all those previously loaded record from cube selectively.
Regards
Anindya

PM Delta problem. Notifications coming into lbwq but Orders are not coming.

Hi,
I'm talking about 2 datasources of PM modules. I've problem with one of them only.
1. 2LIS_17_I3HDR(I've problem here)
2. 2LIS_17_I0NOTIF(I've no problem here)
When I create or modify some notification I get the information immediately in lbwq and then I take it to bi system. But when I create some orders or modify some I don't get them in lbwq.
My analysis:
The difference between these two datasources in our server is
1. I've converted 2LIS_17_I3HDR data flow to bi7 i.e. transformations and dtps. I've deleted the update rules and infosources and transfer rules i.e. 3.x objects.
2. I've enhanced 2LIS_17_I3HDR and written some code in cmod or exit to fill the enhanced fields.
I've searched the sdn thoroughly and couldn't find any solution. Please help.
Regards,
Sujit.

Hi All,
I've found solution to my problem. After trying so many methods I found one which solved my problem. The function module PMEX_UPDATE_17_1_QRFC was not active. I activated that and delta records started coming into lbwq.
Now one more question is do I need to activate this function module in Production server also when we go live? What is the exact procedure?
Another doubt is : is there any way to recover the delta records which didn't come to lbwq before the activation of function module. I know I need to delete the setup tables and fill it again. But is there any other way?
Thanks,
Sujit.

What is BI7.0?what is new in BI7.0?

Hi,
What is BI7.0?what is new in BI7.0?
Can any body have goodmeterial about BI7.0?Please send to this mail id
[email protected]
immediate reply is highly appriciable.
Regards,
Chow.

hi,
chk these out..
See this very nice presentation prepared by Dr Berg on new features of BI 7.0 (these are the differences between BI 7.0 and BW 3.5):
http://csc-studentweb.lrc.edu/swp/Berg/Articles/NW2004s_what_is_new.ppt
Check the release notes:
http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
This presentation:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
Web Blog:
/people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
You can also refer below posts:
Re: BW 7.0 Release
/message/1383908#1383908 [original link is broken]
Upgrade from BW 3.5 to BW 7.0 (BI 7.0)
Hi,
Some features of BI 7 are
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
this is a good PDF on Upgrade from BW 3.5 to BW 7.0
latest on upgrade tp BI7.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Planning/Master_Guide_NW2004s.pdf
You can seek more information on BI 7.0 in the SAP NetWeaver2004s Ramp-Up.
/community [original link is broken]
Re: BW 7.0 Release
Re: BW 7.0 Release
Re: BW 7.0
take a look presentation
overview
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
detail
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e [original link is broken]
may useful .....
https://www.sdn.sap.com/irj/sdn/developerareas/bi
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Check these presentaions:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
http://csc-studentweb.lrc.edu/swp/Berg/BB_index_main.htm
http://csc-studentweb.lrc.edu/swp/Berg/articles/NW2004s_what_is_new.ppt
Also check out these links...
http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
/message/502929#502929 [original link is broken]
Hope this helps.

BW Upgrade - Down time - Delta queue

Hello Experts,
We are in the process of upgrading the BW system from 3.1 to BI7 but not the R3.
Do we need to drain the delta queue from R3 before the upgrade or we can only go ahead about the BW Delta queue only?
As per the note: 506694, its talks about the BW alone when we are performing the BW upgrade but not R3.
Also let me know whether we need to take R3 down time when we do the BW upgrade alone?
Thanks
Raman

Dear Kedar,
Can we perform the left out steps directly in production? As per my understanding there wont be any issues if we perform the left over steps in production.as this will checks for the consistency check alone.
Interestingly I tried checkcing this program(RSUPGRCHECK).. for the infoobjects in my dev system. its trying to activate some of the infoobjects as well.
It showed a message like this: Activate all Dictionary objects ( 1422 )
I tried checking the number of objects in the system using RSDIOBJ.. where I can see that there are 2600 objects are in A version.!!
Does this message tells that this program has activated this many number of the infoobjects out of 2600? I tried this after the upgrade in the D.
Can you please clarify me on this.?
Final Question: How much period that we need to maintain the Down time in R3. Is it till the Upgrade starting from the PREPARE and till the end of the Post Upgrade activities and the Unicode? I will close this thread after this.
Many thanks again..
Raman
Edited by: Raman R on Aug 28, 2008 3:16 PM

Open Hub, Delta Transformation

Hi All,
Thanks in advance for your help. I am extracting data from a DSO to a flat file using an Open hub and a delta DTP. The problem I have is that if there is no delta (i.e. zero new/changed records) since the last time the open hub ran, my file is not cleared.
For example, If I ran the DTP in the morning and received 100 records, the open hub creates a file in the UNIX directory with a 100 records. However if in the evening I run the DTP again and there are no new records, the file is cleared, and remains with the 100 records. This is causing a problem down the line because the data is sent twice.
Is there anyway that the DTP can output blank files? or can the file be cleared out in a different step in the process chain?
your help is very appreciated.
Thanks

Hi,
This note should correct your problem: 1111259
Summary
Symptom
You extract data using a Delta data transfer process (DTP) to an open hub destination of type 'File on application server'. If the source does not contain any new data, the existing file is not deleted.
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.
In urgent cases, you can implement the correction instructions as an advance correction.
Hope this helps.
Regards,
Diego

Delta and logycal system name

Hi!
I have two identical BW systems: one is a copy another system.
BW1 - original system.
BW2 - copy.
We need 10 days to convert BW2 to UNICODE. During these 10 days datas are loaded from SAP ERP to original system, BW1.
After we convert BW2 to UNICODE we need to load delta-data(which we loaded to BW1 during 10 days) from BW1 to BW2.
How can we do it? We can't stop to load data during 10 days.
I want to create RFC-connection between BW1 and BW2, then replicate data sources, create transformations and DTPs between the same objects (cube or DSO). But how I can find out this delta?
For example, I have two cubes, one cube1 is from BW1, cube1 is from BW2. There are 5 requests in cube1, and 3 requests in cube2. I know that two last requests from cube1 I need to load to cube2, but in DTP I can't choose request filter.
Any idea?
I have another problem: these BW systems have identical logical system name. In future I would delete BW1 and use BW2.
If I rename logical system name of BW2 then I will destroy delta loadings from SAP ERP, because delta is depended on BW logical name.

Hello KEU,
I understand your issue like below:
1. BW1 & BW2 is non-unicode at present. BW2 is a copy of BW1 and hence BW2 objects also non-unicode and you want to migrate all the data and objects into Unicode at present.
2. BW1 is connected to the ECC and you need to dump all the Delta data for the 10 days of period to be posted into BW2 so that you can connect BW2 to ECC once BW1 is retired after the Unicode migration.
You have the below possibilities..
1. Connect BW1 and BW2 thru RFC and create a BW1 source system in BW2. Now you need to replicate all data sources from BW1 source system in BW2. Create required transformations which are necessary to connect to the required targets.
2. To load the Delta data you need a right strategy so that dont miss any of the information from BW1 to BW2. I can say as you are in BI7.0 you have the PSA to store all the data in all the trasactional targets where you are looking to move the data.
- For me you have to take care of this once after the copy is done -
Maintain the connection as stated earlier, create the neceaary transformation, and then you need to maintain the init without data transfer in BW2 for the required data sources (8**) so that the Delta data can be pusched from there onwards. So this is required for all the data flows with respect to the individual targets where are getting oprated with DELTA loads...
-- If you have missed then the other option is that, make sure that in BW1 the data is updated in the targets as per the data flow like target 1 to final targets (considering there is no compression), as you have the PSA's for all the data flows, you need to delete the entries which are made after the system copy is done, so that BW1 and BW2 are at the same level, once after this initi without data transfer needs to be done in BW2. Once this is done you need to reconstruct all the deleted entries in the total flow so that there will not be any data mart symbol exisits so that it can be pushed in the Delta load in BW2. (This operation needs to be handled carefully. If not clear then its not suggestable). Also once the Delta loads are moved to BW2, then you need to work in BW1 to maintain the proper Init status.
3. The final option is to get the 10 days of Data in a flat file from different targets in BW1 and then maintain a right strategy to load the same in the respective targets in BW2. Needs proper attention.
So handle the points carefully as its a complex situation.
Hope this helps..
Murali
Edited by: Murali M on Aug 29, 2010 9:10 AM

DTP Full/Delta loads

I am loading data from one DSO to another. The change log of the source DSO has been deleted for any request before 20 days.
I want to do a full load from active table and then start the delta loads from change log. But the problem is the load is picking up all the previous deltas from change log again, instead of picking deltas after the full load.
Is there a way to do a "init without data transfer", like the option we had before - where it resets the delats so that only the deltas after the full load are picked.
Thanks. Points will be awarded.

Hello Sachin,
In BI7, there's no longer the notion of delta initialization. Just do a delta from your DSO.
Just load the full data in our DSO and launch the delta, then run the deltas for populating your DSO and the corresponding deltas from it.
Hope it helps,

Process Chain in BI7.0

Hi,
What are the steps to create Process Chain in BI
What are the difference between BW 3.5 and BI7.0 PC?
Regards,
Jackie.

Hi Jackie,
Major difference between BW3.5 and BI 7.0 versions
1. In Info sets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for Infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accelerator is a separate box and would cost more.
4. The monitoring has been improved with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal.
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passé! Yes, you can always revert to the old Tcodes.
7. The *Data Warehousing Workbench *replaces the Administrator Workbench.
8. Functional enhancements have been made for the Data Store object:
New type of Data Store object, Enhanced settings for performance optimization of Data Store objects.
9. The transformation replaces the transfer and update rules.
10. New authorization objects have been added
11.*Remodeling *of Info Providers supports you in Information Lifecycle Management.
12 the DataSource: There is a new object concept for the DataSource .
Options for direct access to data have been enhanced.
From BI, remote activation of Data Sources is possible in SAP source systems.
13. There are functional changes to the Persistent Staging Area (PSA).
14. BI supports real-time data acquisition.
15. SAP BW is now known formally as BI (part of NetWeaver 2004s). It implements the Enterprise Data Warehousing (EDW). The new features/ Major differences include:
a) Renamed ODS as Data Store.
b) Inclusion of Write-optimized Data Store which does not have any change log and the requests need no activation
c) Unification of Transfer and Update rules
d) Introduction of "end routine" and "Expert Routine"
e) Push of XML data into BI system (into PSA) without Service API or Delta Queue
f) Introduction of BI accelerator that significantly improves the performance.
g) Load through PSA has become a must. Info Packages are used to load data upto PSA only.
You need to create DTP to update data from PSA to Data Target.
Pls check the following linka also ,it might help u
http://csc-studentweb.lrc.edu/swp/Berg/Articles/NW2004s_what_is_new.ppt
http://help.sap.com/saphelp_nw04s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/52/a21f407b402402e10000000a1550b0/conten
Steps to create Prcocess chains in BI:
Check in the following links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30664504-40dd-2a10-3794-db7b4190bef3
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/bi-70-process-chain-and-psa-deletions-1098154
or tcode rspc is for process chains
1.select new from there
2. enter the variant of the process chain
(for start process i.e first one it is immediate always)
3. from lfet hand side of ur processes select the process u want to do,after the start process for eg: load info package.
(give the name of ip and give the variant i.e at wat time u wannt to execute it).
4.likewise drag and drop the processes u wanted to link, one after the other.
5 activate the pc and then schedule it
Pls assign points if it helps u,
Thanks & Regards,
Madhu

Delta in BI7

Similar Messages

Maybe you are looking for