Init delta package by package

Is it posible a init delta running package by package( from ods to ods update rule) like in the datasource (Load in ods package by package)
Thanks

Hi,
I'm not sure if I understand your question correctly. You want to do the delta init with several InfoPackages with non-overlapping selections, correct?
You cannot do this directly with ODS objects as DataSource, but you can do full loads and after these full loads you do a delta init without data transfer.
You have to ensure that you load all data with your full loads and that no ODS activation is going on until the whole process has finished.
Regards,
Ralf

Similar Messages

In a update rule, run two data packages ; package by package not secuencial

HI, my data source is an ods i want to fill other ods.
If i have two data packages, with 7000 and 5000 registers
i want to run the two datapackages in a secuencial way not parallel.
But the init delta doesn´t give me the option of run package by package.
The options show me is initialization with transfer data (parallel) i want package by package.
How i can do that??
Reward points

a

COPA Init Delta

Hello,
In loading our COPA cube from R/3 to BW, when we run two init delta infopackages in parallel, we get the following error "An init or delta request is already running for this DataSource".
We believe this has to do with the timestamp functionality. According to the documentation we have found, it appears as though we should not split our init delta load into multiple infopackages, but rather limit it to one singe infopackage that loads everything. Can anyone confirm this?
Our COPA datasource is costing based and set up as a generic delta. We are on R/3 PI 2004.1 and BW 3.5.
Thanks,
Kelley

Hi,
That is right, and it will have to do with the timestamp functionality as you said.
Following is from the HOW-TO document which is not exactly for this scenarion but implies the same reason.
"There can only ever be one valid initial package for a DataSource. If, for the same DataSource, a separate initialization is scheduled for different selections, for example, and data is posted to the operating concern between the individual initializations, data inconsistencies could occur between SAP BW and OLTP. The reason for this is that, with each initialization, the time stamp of the DataSource in the OLTP system is set to the current value. Consequently, records from a previous selection are no longer selected with the next delta upload if they were posted with a different selection prior to the last initial run."
hope this helps..
cheers,
Ajay

Init Delta Transfer

Hello Experts
I am facing a small issue. I have a landing ODS (ZVAITM).
From which my data is going to Domestic cube(ZCDOM). Now i got a requirement to load the data from the landing ods (ZVAITM) to other cube export (ZCEXP). Now my problem is if i use the same infopackage, which is "init Delta transfer" which i used to load the first cube (ZCDOM), its not allowing me to do tat "2 inits not possible". how can i get the data to new cube using the same info package...is that the right way or we need to create seperate info package?i am confused...any kind of help is really appreciated..thanks
Regards
Sri

Hi,
If u havnt loaded any data after the init to the first data terget then delete that Init first.
for this goto the info pack, from the menu Scheduler-> init for the source system. from here u can delete the INIT.
Then create an update rule based on the same data source to the 2nd data target. and then take Init with delta. Now it will work..
Hope it helps-
MM

Variable declaration in Package and package body

Hi
Kindly reply the difference in declaring a cursor inside a package vs package body
eg:
create or replace package shapak is
cursor shacur is select * from sha;
function shafun return number;
end;
i can declare the above cursor inside the package body withoout declaring in package specification. but what is the difference?
reply appreciated
thanks
shajan

In general..Items declared in the package spec are visible outside the package..so you can say public.where as items declared in the body are restricted to use within the package..such items are called private.

Unable to create Init Delta InfoPackage.

Hi Experts,
I am working on BI 7.0 within Solution Manager (GSB 100).
Since I am extracting data from only 2 tables into 2 different InfoCubes, we did not require to create any Master Data loads.
In order to load these 2 InfoCubes, I have created 2 Transactional Generic DataSources in RSO2. When I try to create an InfoPackage from the context menu of these DataSources, Only Full Update is coming up in the Update Tab.
I'll create 2 Process Chains eventually for each InfoCubes. How can I create one Init Delta with / without Data Transfer and another Delta InfoPackage?
Any help is very much appreciated. Points will be assigned.
Thanks,
Chandu

Hi Naveen,
You were right. I changed it to Generic Delta and it's working fine now.
Thanks a lot for that. Points assigned.
Quick one... If I wanted to do a Delta Load each time except for the very first time (i.e. Init Delta), it better to have 2 InfoPackages. But should they be as below:
1. Init Delta (should this be With Data or Without Data Transfer...?)
2. Delta Update
Cheers,
Chandu

Packages and packages

Hi
I was rereading Martin's principles of package architecture and was wondering how the concept of package in this context relates to the concept of a Java package
after thinking a bit, I got the feeling these two concepts have nothing to do with each other
I feel that Java packages deal with namespace and access control, while OO packages (the components of your program's binaries) would be, in the Java world, jar files containing classes from different packages (and not especially all classes from these (Java) packages), and constructed as much as possible in order to follow these supposedly good OO principles
Am I right ? partially ? totally ? totally not ? I need some insight on this

Kind of. But what would stop me to define the
namespace on a per-component base? I used structures
like com.mycompany.myapp.database (data tier),
com.mycompany.myapp.web (presentation tier) and the
likes. You could put classes (or packages) belonging
to a certain subsystem into a package dedicated to it.I did it for a long time too, traditionaly with webapps :
be.mycompany.myapp
dataaccess
business
web
and that worked fine... but that's not my concern
actually, what concerns me is the business package itself... I'm writing a very simple peer2peer file sharing tool for both fun & education, and the packaging becomes trickier, since the app is naturally distributed :
* file sharing client package
* user manager client package
* server package (handles login requests & user management requests)
thing is, I reuse many classes among these three "kinds of endpoint", which makes me think about properly dividing my app into small reusable, well-organised components... when java packages come into play, things are getting less clear as of how I should do...
how do you people do when it comes to structuring (packages AND deliverables of) your business layer ?

"Error occurred in the data selection" on init delta load ODS- InfoCube

Hi, gurus and experts!
I'm trying to do Init delta load from 0FIAR_O03 ODS into 0FIAR_C03 InfoCube in PRD env. by InfoPackage "Initialize with delta transfer (with data transfer)". Immediately after the load was started I got error
"Error occurred in the data selection"
with details
"Job terminated in source system --> Request set to red".
Where are no any short dumps. There are 1 activated init load in ODS - nearly 6 500 000 records.
Any ideas about error? And the way I can load data?

Hi Gediminas Berzanskis,
I faced the similar error when I tried to load data from an ODS which contained huge amount of data to a Cube. Even in your case the volume of data is more (around 6.5 million records). The error could be due to the table space issue, please contact your Basis team to check if enough table space exist for both the data targets.
Meanwhile you may also check the RFC connection of the Myself source system.
You can replicate the DSO datasource once and then reactivate the transfer rules using the program RS_TRANSTRU_ACTIVATE_ALL.
Try load with a small amount of data with a Full load option and then with a delta option..
Hope this Helps,
Prajeevan (XLNC)

ORA-04042: procedure, function, package, or package body does not exist

getting following error
I have logged on as sys
GRANT EXECUTE ON CTXSYS.CTX_DDL TO public
ERROR at line 1:
ORA-04042: procedure, function, package, or package body does not exist
does it need Oracle text installed
comp_name
Oracle Database Catalog Views
Oracle Database Packages and Types
Oracle Workspace Manager
JServer JAVA Virtual Machine
Oracle XDK
Oracle Database Java Packages
Oracle Expression Filter
Oracle XML Database
Oracle Rules Manager
Oracle Multimedia
Oracle Real Application Clusters

912919 wrote:
getting following error
I have logged on as sys
GRANT EXECUTE ON CTXSYS.CTX_DDL TO public
ERROR at line 1:
ORA-04042: procedure, function, package, or package body does not exist
does it need Oracle text installed
comp_name
Oracle Database Catalog Views
Oracle Database Packages and Types
Oracle Workspace Manager
JServer JAVA Virtual Machine
Oracle XDK
Oracle Database Java Packages
Oracle Expression Filter
Oracle XML Database
Oracle Rules Manager
Oracle Multimedia
Oracle Real Application Clustersit worked for me.
09:10:19 SQL> GRANT EXECUTE ON CTXSYS.CTX_DDL TO public;
Grant succeeded.
09:10:23 SQL>

INIT Delta

Hi
can anybody tell me how to delete init delta? Is it like full delta..delete a request in mange of the cube?
Hyma.

Hi Hyma,
Go to R3 rsa7 transaction and also idelete the r3 queue. In BW delete all the data from the Infocube and all the Init.
Now redo all from the start.
Look at this post...
Automatic deletion of previous init loads in process chains
If you are sure that no one has put another data in the source system then you can use the existing set up table and do a fresh init.
But the data you have deleted from the delta queue will get lost beacuse they are niether in the set up table nor in the delta queue and it will not get picked at any cost.even if you do a full repair.
If you would have pulled delta then you could have used the set up table.
SO you will have to again fill the set up table so that you have deleted delta records now in set up table and then load from it.
Just do a fresh init without data transfer.
Fill the set up table.
then run a full repair request
and then schedule a daily delta load
every thing will work fine
Hope This Helps.
****Assign Points If Helpful****
Regards,
Ravikanth

How to prevent downgrading of the app in meta package using package versioning feature of package maker tool?

Hi,
Created an installer i.e, meta package using package maker tool. I want to prevent downgrading of the application or package on the target/installed volume.
Problem is, if there is a newer version of app and when I try to install any older version, then it does not throw any error message to the end user and replaces the existing newer version with the older version of app, which should not happen. But, if I check the package version using version comparison of Package maker tool, that works fine with flat packages i.e, with the .pkg files. So, I need the solution for metapackages(.mpkg) and want to prevent downgrading of app for metapackages. I am not getting any solutions for this. Can someone guide me on this?
Thanks for the help provided.

Hi,
Created an installer i.e, meta package using package maker tool. I want to prevent downgrading of the application or package on the target/installed volume.
Problem is, if there is a newer version of app and when I try to install any older version, then it does not throw any error message to the end user and replaces the existing newer version with the older version of app, which should not happen. But, if I check the package version using version comparison of Package maker tool, that works fine with flat packages i.e, with the .pkg files. So, I need the solution for metapackages(.mpkg) and want to prevent downgrading of app for metapackages. I am not getting any solutions for this. Can someone guide me on this?
Thanks for the help provided.

Problem when running Init Delta

Hi Friends,
I'm trying to run Init delta , There is already a Full update run on this ODS , Now since I'm running an Init Delta on this , I'm getting an error that Full Update is already been run on this.
What is the solution for this?? From now I want to do Init delta and Delta on this , Since the number of records are increasing.
Please advice,

Hi !
In the scheduler , select repair full request.
Give a try
I am not sure , about this
Regards
Durai

Including packages in package hierarchy

Hi,
What is the purpose of including packages in package hierarchy?
How can I define use access for them? what is the use?
Please help me out in this.
Thanks and regards,
Lakshmi Reghuvaran

Hello Lakshmi
The <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fd/f39de8ae6f11d596c000a0c94260a5/content.htm">SAP Online Help</a> says the following to this topic:
Goals of the Package Concept
When SAP created the package architecture in R/3 Enterprise, its goals were:
To improve the structure of the software
To encapsulate software functions more strictly
To make well-defined interfaces available to all applications
To clarify responsibilities
The very same goals can be applied to your own packages, either if you are a professional software supplier for SAP or a customer.
Regards
Uwe

Package in package?

Hi,
is there any workaround to implement this?:
CREATE OR REPLACE PACKAGE main_package AS
PACKAGE package_a;
PACKAGE package_b;
PACKAGE package_c;
END main_package;
Thanks

I cannot understand your requirement.
But...
Is this?
 
create or replace
packeg aaa
is
procedure main; /* Public procedure */
end;
create or replace
package body aaa
is
procedure aaa1 /* Private procedure */
is
begin
null; -- any real procedual routine
/* cannot refer aaa2 */
end;
procedure aaa2 /* Private procedure */
is
begin
null; -- any real procedual routine
/* can refer aaa1 */
end;
procedure main
is
begin
aaa1;
aaa2;
end;
-- initial package
begin
null;
end;
 
 
Or this
create or replace
procedure main
is
-- declare type,cursor,variable for main at here
procedure sub1
is
begin
null;
end;
procedure sub2
is
begin
null;
end;
begin -- this is main
sub1;
sub2;
end;
/

Update ST/PI Plugin - Init delta queue

Hi guys,
Yesterday, our basis team, asked me to clean all extraction queue in BW. They will update a plugin (ST/PI) that control the connection between the enviroment BWP and ECP.
I have to delete all the queues in transactions SMQ1, RSA7 and empty the setup table using LBWG. The note 1081287 will give a better explanation about this.
My question is:
Will I have to restart all the LIS extraction again with full update?
For example, to start the datasource 2LIS_08TRTLP, I have to execute the transaction VTBW and after execute an init delta in BW with all data.
Is there a way to start this delta without carry all the data again?
I wanna carry only the new data to BW to update the cubes
thanks
Paulo

Hello Ralf,
They asked me to do these steps:
1 - Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in transaction SMQ1.
2 - Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.
If I delete the contents of the setup tables using LBWG transaction, Will I have to restart all the queues again? Will I lost data?
Thank you
Paulo

Init delta package by package

Similar Messages

Maybe you are looking for