Delta control Mechanism

Hi Experts,
Can any one give full Information about Delta Control Mechanism:
1.How it works?
2.When Deltas are loaded from ODS to Cube,If I want to delete Delta Either from a Cube or from an ODS how it can be done.
Thanx in Advance.

Hi Dinesh,
Plz go through the scenerio:
1 I am Loading data to an ODS from R/3 this is further updated to a cube.
2.First I loaded Full upload from R/3 to ODS and to cube also.
3.Next I initialized the Delta .
4.Now I am Extracting the deltas from R/3 to an ODS and finally to cube.
5.Now my ODS and Cube both contain one full update initialization and D1,D2, and D3 Deltas.
6.Now Delta D2 has gone wrong I need to Delete that from both ODS and Cube.---->Now My question is
6.1 If I Delete the D2 from an ODS whether all the deltas will be deleted..?
6.2If all the Deltas are deleting then How can I take care of this scenerio.
In ODS manage Option the tab by name Data Mart Status of the request is availablel.After Deltas are loaded to cube this tab will get a tick mark.If I click on the tick mark it will take me to a screen Delta control Mechanism.
How this will help in this respect.
Pradeep
I

Similar Messages

How to use 2 date field as delta control in generic extractor.

Hi colleagues:
I have developed a generic extractor to extract logistic data: Purchase Orders and Invoice. In order to do that, I have defined a view joining EKBE, EKKO, EKPO, EKET tables on R/3. By this approach, the delta mechanism is supposed to be controlled by the EKBE-BUDAT field and also by the EKPO-AEDAT field. Both fields are available on the view used to create the Datasource. However, the Datasource creation allows us to define just one field as delta control.
I have a few questions regarding to this scenario:
<b>1 - Is it possible to define 2 fields as delta control field on Generic Datasource?</b>
<b>2 - How about creating two similar Datasouces, one having AEDAT as delta control, the other having BUDAT as delta control, and then connect those Datasources to an unique Infosource on the bw side?</b>
Best regards
Waldemar

hi,
1 - as far as I know it is not possible to define 2 fields
2 - this workaround is used often in cases like yours.
Just remember about order of extracting: first you extract new documents then changed
Regards,
Andrzej

Access Control Mechanism in JSF

Hi all ,
I am working on a project (still in analysis phase) and have decided to go for JSF over struts. As i have found that JSF has good advantages over struts. I am searching for a good model (with code) to implement a robust access control mechanism that is in place with JSF. I hope that JSF has developed a good access control mechanism in its current version.
If any one has an example they can send it to me at
[email protected] thanks.

What exactly do you expect of an Access Control Mechanism? There is no such thing in JSF RI (Mojarra).
Aren't you just talking about login/logout and checking for logged in user? Just a Filter and a database is sufficient for that. If you want to display/hide specific JSF components depending on the logged in user, you can use the 'rendered' attribute for that.

Version Control Mechanism for MDM

Hi All,
Can anybody please tell me how version control mechanism is used in SAP NW MDM.
Thanks in advance
Chandan

Hi Chandan,
If you are looking out for maintaining the history of all the Master records, then to the best of my knowledge its not available in MDM. MDM only deals with the latest version of records, however, you can still get back to the old values of records( in data base) , using the change tracking functionlity in MDM.
However, MDM GUI's will show you only the latest updated values.
To know about the change tracking and how it can be integrated with a UI, refer to the link below:
How to Configure SAP MDM Change Tracker for Any Repository:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807861ac-f941-2c10-8f8d-c57f9d421b99
Now, in case you are asking about the ALL VERSIONs feature of MDM, which we use in relation with Check out, then refer to the link below:
How to Control Versioning in SAP MDM
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0b392b8-d4b7-2b10-a189-b3b61df3d9c4
Hope it helps.
Thanks and Regards
Nitin jain

ODI Control Mechanism

I need to design a control mechanism for ODI(Sunopsis) if Any one design it for their client such document is highly appreciated.
I need following steps to include in the control mechanism
1.Organize Workflow
2.Restart strategy for Scenario
3.Log management for insert rows, start and end time.(Client is not interested in using operator for logs)
Thanks
Saif

Hi ,
The username you are connecting to from backend and fireing the query and its a success,
Is the same username being used for connection through the topology manager?
Reshma

License Control Mechanism Implementation

Hi,
I am now trying to implement a license control mechanism for a web based application.
I've studied several websites about this topic, but they did not provide much about the
implementation details. So...could somebody please clarify for me
where(websites, paper, books,API...) should I find the information.
Thanx.

Hi,
Chapter 5: Software Piracy and Code Licensing Schemes of ISBN: 0072225653 has a nice and simple introductory chapter on this topic with full code examples.
Regards,
Duncan Eley.

Idoc control mechanism

Hi,
I have a situation.
In processing the Idocs in background.
can anyone give me some info how to control this processing.
I am talking about PO to SO automation between to SAP systems.
lets assume,
The background job which triggers to send idocs from sender system is At 12.00 noon.
At 10 am , PO is created and Idoc created for this PO and sent to port.
at 11 am the same po has got some changes and the idoc also sent to port(FYI - I am not using Orderchange message type ) .
At port i want to have the sequence of getting processed which is created at 11 am first than the one at 10 am.(the latest).
i mean LIFO(last in first Out),in sending the idocs.
any kind of input is greatly appreciated.
Regards
Message was edited by: Satheesh Mothukuri

Hi Neela,
Please expalin your problem in detail, If following is not useful:
Master IDOC contains all the recods (control record, data record & status record).
After that it will consult Distribution Model for the Sender and Receivers (Tcode -BD64) . Then Communication Idocs are generated for the identified receivers. After that a function module will distribute that Communication Idocs. Communication idocs are generated befor getting into ALE layer.
Ashven

Access Control Mechanism (data level security) not working properly

Hi Experts,
I have done datalevel security for groups by help of a database table. This table contains UserId, Dept. code, GroupName column. UserID are verified by LDAP server during logging into Dashboard. I have made two init blocks for GroupName and Dept.Code .
Query is :
SELECT 'Group', GroupName from TABLE
Where
UserId = ':USER'
Similiar query is for Dept Code.
There are two groups ; 1. CC_User 2. Full_User. I have applied filter in PERMISSIONS for CC_User on Fact table on Dept Code. So, user in this group may see data for Dept Code aligned to him in the table. All_User may see whole data for All Dept Codes as NO filter is applied on this group.
Dept Code , UserId and GroupName are Varchar.
Now problem is this when a user have membership of one group , it works fine. For CC_user it shows data for its Dept Code and All_user may see whole data.
But When A user have permission of both the groups , only data related to CC_User group is visible. But, in my view , maximum permmision out of the both groups must be applied to the user if he belongs to more than one group.
So , here , he must see whole data, as All_user group can see full data.
Does least restrictive permmission happens in case of membership of more than one group in OBIEE.

848839 wrote:
Does least restrictive permmission happens in case of membership of more than one group in OBIEE.Indeed it does. The most restrictive filters get applied if a user belongs to multiple groups that have filters at various levels of data because its always an AND clause in the where condition. This is the sort of behavior in various tools I have seen apart from OBIEE.
Hope this helps.
Regards,
-Amith.

HT203171 Track pad is erratic, sometimes scrolling without touching the pad. Also highlighting chunks of my Thesis with the touch of a finger. Frustrating because I have accidentally deleted during this out of control mechanism with the track pad.

My Mac Book Air has developed an erratic process with the track pad. Sometimes the page scrolls without touching the pad, great chunks of my Thesis can be highlighted and sometimes I delete without realising. Does anyone else have this problem. The Tech wants to replace my track pad today, not sure what to do?

See if any of these items apply:
http://support.apple.com/kb/TS1449
Regards,
Captfred

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Routine,delta upload

Hi experts,
i am new to bw and sdn .
can u answer for my questions ,i was asked in my interview.
1)what is the scenario of start routine?
2)how to generate a report for present year and previous three years?
3)what is the mechanism behind delta upload?
thanks in advance
regards
krisna

Hi Krishna,
1) Start Routine - Start routine is executed prior to executing of transfer rules, so if there is any global variable to be used in all transfer rules then it is better to declare that in start routine.
After start routine execution is over then transfer rules r executed.
Start routine are at two levels
1. update roule
2. transfer rules
start routine is processed once per data package load .For ex : you want to eliminate a set of records based on dome criteria you can do that with start routine . But update rules or transfer rules are processed once per data record where you can manipulate each single record .
There is an internal table called data_package which will have all the data available for processing you can later store all the data in another internal table (you can declare) which can later be used in update rules .
3) Delta Upload Mechanism - Regarding the Delta upload mechanism, it's simply the mechanism that helps updating only the changed data, and not the full update. The field 0RECORDMODE determines whether the records are added to or overwritten. It determines how a record is updated in the delta process: A blank character signifies an after image, X a before image, D deletes the record and R means a reverse image.
You can check following link for details.
http://help.sap.com/saphelp_erp2004/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
Regards,
Ashish.

Is it possible to use the message control in R/3 to trigger a Proxy?

Is it possible to use the message control in R/3 to trigger a Proxy? The message control mechanism has some advantages that I want to use E.g. repeat messages with RSNAST00, configuration instead of coding etc.. Does anyone uses SD Invoice message control mechanisms together with XI Proxies?
Best regards,
Matthias

Hi,
>>>configuration instead of coding etc
currenly it is not possible to achive it without any coding
>>>repeat messages with RSNAST00
RSNAST00 is not used to repeat messages (idocs) but to send them
try using standard IDOC in your sd invoice scenario
if you don't want to do any coding
Regards,
michal

Security mechanism

Hi Jhs team:
We are planning using "oracle single sign-on" with "programmatic Dynamic Role Based Authorization" as our security control mechanism,
The example in jhs_tutorial_3.pdf using Struts-Uix architecture and through ValidateLoginUser Action to wrapped Jhsuser objct,
so, corresponding to our architecture , if we using SSO what is the best practice to put these code about wrapped Jhsuser object ?

Ting Rung,
See my reply on your other post about getting the username in an entity object.
Steven Davelaar.
JHeadstart Team.

Delta data load for huge table in Data Services XI R3

Hi,
We have a project requirement of pulling delta data once in a week from table which has around 44 million records but it doesn't have any last modified column.
In such case we have to use table comparison transform, but it will be very time consuming.
Please provide some suggestions to meet this requirement.
The source of DS job is a snapshot(the source table is in a remote database).
Thanks!

Because SAP Business Objects Data Services XI 3.x doesn't have any built-in delta-enablement mechanism with R3/ECC, the only possibility right now is to do a table compare. Given that this is only a weekly activity, while maybe time-consuming, it may be sufficient.
In the future, you may want to consider activating the related SAP BW standard content DataSource(s) to extract into Data Services prior to loading to the target repositories. This may provide delta-enablement for the data that you're extracting.

Delta update in Info package

Hai all
what is the us of delta update in info package
I had intially loaded data from R/3 to psa using
(INFO PACKAGE->UPDATE-->Initilize delta process)
Then I had created to more records in r/3 side .
this time I scheduled using DELTA UPDATE I am getting 0 records
then what is the use of delta update
How can I get only delta records with out use of selection condition in DATA SELECTION of INFO PACKAGE
thanks
chaithanya

Hi,
You must specify "1" (day) in the lower limit of the delta maintenance.
I could not post my previous reply so here a new try :
Hi Chaithanya,
Let me explain how the generic delta mechanism with "date"-field works on the R/3 side:
When doing a delta extraction, the current date is stored in table ROOSGENDLT or ROOSGENDLM (anyway not so important).
This date will serve as a "from" date for the next delta extraction, though excluding the current value.
This in order to prevent duplicate records to be extracted during a second delta run on the same day.
Without extra settings, it will thus not be possible to extract two different delta's on date the same day.
Solution :
1. If you do not care about duplicate data (e.g. only field assignments with overwrite functionality in the transformation) goto RSO2 in change mode for your extractor and go into the generic delta maintenance screen. In the settings, enter "1" as safety interval lower limit. Like this, the delta processing mechanism will always subtract 1 day from the day stored as 'low-value'.
In your example this means that the initialisation will transfer 4 records, the delta will transfer 6 (although only 2 were added).
2. Use timestamps to determine delta (timestamp should be updated on savetime of record)
I hope this helps.
regards,
Olav

Delta control Mechanism

Similar Messages

Maybe you are looking for