Before image and after image concept of ODS

Hi Gurus,
Could anybody help me in understanding the concept of " Before image and after image in ODS"
Kindly forward me if any good docs are available on my email ID: [email protected]
With regards,
wrushali

check this link for after image.
Re: regarding ODS
and before image is snapshot of the data before a change took place
after image is snapshot of the data after change.
these are used for delta update.
Hope it helps.
Regards

Similar Messages

Difference between Before aggregation and After aggregation

Hello ,
Can any one tell me what is d difference between Before and after aggregation of calculated key figure?
Thanks,
Aparna

Before aggregation calculates the data before summarizing the final results while after aggregation, it will summarize the result first before it calculates.
Assume:
Customer#----
Orders
10000----
10
10001----
20
10000----
30
if you want to count the number of customers before aggregates and after aggregates gives you different result.
Before aggregates will give you
Customer#----
Count
10000----
2
10001----
1
After Aggregates will give you
Customer#----
Count
100000----
1
100001----
1
Customer might not be a good example but the concept remains the same for others.
thanks.
Wond

Order printout before realse and after relase

hi
all
order printout before realse and after relase
is this possibile
it gives message teco not done
my client wants in preparation and after relerase
though iknow no logic is there but they stick to this
thanks
manoj

hi
i think you can print the order after the releasing of order or at the time of put in process.
kindly refer the following [link|http://help.sap.com/saphelp_erp60_sp/helpdata/en/5b/ae36044b8611d182ba0000e829fbfe/content.htm]
regards
thyagarajan

Size of SQL query before execution and after execution

hi all
I need help on how can i find out the size of SQL query before execution and after execution in java
The query can be any query select / insert / update
Can anyone help me if any system tables help to find out the required size i mentioned
Urgent help is required
Thanking in advance

I need the size in terms of bytes
like the rquirement is stated as below
select ................: 10 B , return 250 B
so i need size before and after execution in terms of bytes

Difference between Before INSERT and After INSERT trigger?

What is difference between Before INSERT and After INSERT triggers? Can anyone give me a simple example from SCOTT schema for both of these triggers.

The documentation gives a good explanation have you looked at....
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_triggers.htm#sthref1175

Before update and after Update trigger

Hi,
I am following the below approach to overcome ORA-04091: table XXXX is mutating error.
1. In the after update row level trigger i am capturing rowids of changed rows into a table type (of type rowid) defined in a package.
2. In the after update statement level trigger i am using the data from the table type ( that got populated in the first step) to do my work.
3. In the before update statement level trigger i am resetting the table type defined in the package.
Now, can the below situation occur causing the system to fail
1. A Update to the table occurred causing the before update statement level trigger to fire and reset the table type.
2. After that row level after update trigger gets executed and captures the required data.
3. Now before the after update statement level trigger gets executed a new update to the table happened ( to some other row as multiple users are using the application) causing the
before update statement level to fire and erase the data from the table type?
I want to know if above situation can occur or is the execution or before and after update triggers atomic?
Thanks for helping.
TIA
Harsha

A collection in a package is local to the session. And a given session can be processing one SQL statement at a time. So any concurrent updates would be happening in a different session with a different logical collection.
You may encounter problems if your session is trying to update the same rows that other sessions are trying to update (whether via the original update statement or via the updates issued by the trigger). You could encounter performance problems because of row level locks or you could encounter deadlocks. But your session's collection won't be initialized by some other session's actions (other than DDL that replaced the package itself).
Justin

How to compare the value of a cell before changing and after changing.

Hey there,
Now I want to implement a JTable. And the requirement is that users can edit a cell in the Table only once. I think there are two possible ways. One is that after user edited a cell, I will set this cell read only. Another way is to compare the vaule before and after the changing. If it is different, then write back the previous value.
But I did not know how to implement in Java. Can anybody help me?
Thanks alot!
Shelly

inevitably, you will have to save a before copy of
the data, what this many times amounts to is that you
will need to have 2 identical data structures before
you start or some type of locking mechanism for each
piece of data.Why is this inevitable? I don't see it as inevitable at all. In fact, it's quite simple to implement a TableModel that returns false when isEditable(int, int) is invoked for any cell that has already had setValueAt(Object, int, int) inovked on it, for example. Depending on the requirements and implementation a different methodology may be needed for determining when the edit has taken place, such as a custom editor that notifies the TableModel when stopCellEditing() is invoked. Heck, overriding editingStopped() in JTable to do it might even work.
So, create a TableModel that returns isEditabe(int, int) as true only if the cell hasn't been edited yet. The only problem to solve from there is how you know when it's been edited. I've already given you a few leads on that, it's not particularly hard but depending on your exact implementation it may require different solutions.

Modification in data before commit and after function call

Hi,
I am creating a Transfer order (TO) from Transfer requirement using function module L_TO_CREATE_TR.
For one of my requirement I am
Passing I_UPDATE_TASK = X and I_COMMIT_WORK = <blank> so that the actual creation happens on the next screen. Next screen will show some details which can only be fetched if L_TO_CREATE_TR is issued.
Now, on second screen user may change one field called quanity. How can i acheive this.
I can think of two options here :
1) Call rollback and then call the FM again this time with commin flag ON
2) Do we have second option here.
Let there be a light

thanks . i have an idea.
first ,create a row ,and then insert this row.

Display Dims before boot and after shutdown are complete

This is probably a stupid question but a while back I clicked on an option to have my display dim during the shutdown process and stay dim until it was completely booted.
I would like to turn this off but I can't find where the option was. I've checked the device manager, BIOS, standard and advanced display settings the Windows and lenovo power settings with no luck.
I have a thinkpad W500 running Windows 7 Pro 4gb of ram with a recent upgrade in hard drive to a 750 gb WD black series drive. I am also running IE9 which I see has some compatibility issues so I hope I can post this.
Thanks
Lou
Saint James, NY
Solved!
Go to Solution.

Thanks. I found it under Global Power Settings.
Lou
IE 9 left a blank post. I an using compatibality mode now.

How to covert before and after image details from logdump to SQL

Hi,
Through logdump,i am able to retrieve below before and after image details for an update statement.
Instead of below ascii format output, i need to know the complete sql statement before update and after update.
Is there any command to covert below output to readable SQL sentence?
2012/09/26 02:30:16.999.659 FieldComp Len 300 RBA 2528
Name: TEST.TESTTABLE
Before Image: Partition 4 GU m
5e50 86f5 af70 9660 b6fa 785c e34f 8881 0497 9507 | ^P...p.`..x\.O......
799f 2ee2 6399 d539 ea92 90de 828b 83d9 adc9 c8c4 | y...c..9............
ca87 9632 7136 a5fc 826f 8cc7 6ddd 7f8a e02e 816a | ...2q6...o..m......j
6ac4 739a 8011 5068 068a 4553 4937 93e7 cc5a d3d3 | j.s...Ph..ESI7...Z..
6a2b 2540 3be9 1df7 6d0c 0f17 d795 efd4 e0c5 dae9 | j+%@;...m...........
a488 a757 7c07 78a4 5f2a 1330 d2bb 5a05 7075 6b95 | ...W|.x._*.0..Z.puk.
529c f681 97d8 df6f 58d5 37dc e36d 8bc0 19d5 c7f0 | R......oX.7..m......
Bad compressed block, found length of 34549 (x86f5), RBA 2528
Logdump 2335 >n
Hdr-Ind : E (x45) Partition : . (x04)
UndoFlag : . (x00) BeforeAfter: A (x41)
RecLength : 300 (x012c) IO Time : 2012/09/26 02:30:16.999.659
IOType : 15 (x0f) OrigNode : 255 (xff)
TransInd : . (x01) FormatType : R (x52)
SyskeyLen : 0 (x00) Incomplete : . (x00)
AuditRBA : 24567 AuditPos : 4268948
Continued : N (x00) RecCount : 1 (x01)
2012/09/26 02:30:16.999.659 FieldComp Len 300 RBA 2947
Name: TEST.TESTTABLE
After Image: Partition 4 GU m
5e50 86f5 af70 9660 b6fa 785c e34f 8881 0497 9507 | ^P...p.`..x\.O......
799f 2ee2 6399 d539 ea92 90de 828b 83d9 adc9 c8c4 | y...c..9............
ca87 9632 7136 a5fc 826f 8cc7 6ddd 7f8a e02e 816a | ...2q6...o..m......j
6ac4 739a 8011 5068 068a 4553 4937 93e7 cc5a d3d3 | j.s...Ph..ESI7...Z..
6a2b 2540 3be9 1df7 6d0c 0f17 d795 efd4 e0c5 dae9 | j+%@;...m...........
a488 a757 7c07 78a4 5f2a 1330 d2bd 5a05 7075 6b95 | ...W|.x._*.0..Z.puk.
529c f681 97d8 df6f 58d5 37dc e36d e8b8 19d5 1af0 | R......oX.7..m......
Bad compressed block, found length of 34549 (x86f5), RBA 2947

From the reference guide:
*FORMATSQL*
Valid for Extract
Use the FORMATSQLparameter to output data in external SQL format, instead of the default
Oracle GoldenGate canonical format. FORMATSQLgenerates SQLstatements (INSERT, UPDATE,
DELETE) that can be applied to both SQLand Enscribe tables by utilities other than Oracle
GoldenGate Replicat.
NOTE Do not use FORMATSQL if the data will be processed by the Replicat process.
Replicat expects the default canonical format. Do not use FORMATSQLif
FORMATASCIIor FORMATXMLis being used.
A FORMATSQL statement affects all extract files or trails defined after it.
Default output
Without options, FORMATSQLtransactions are output as follows, in comma-delimited format:
● The begin-transaction indicator, B.
● The timestamp at which the transaction was committed.
● The sequence number of the transaction log in which the commit was found.
● The relative byte address (RBA) of the commit record within the transaction log.
● The SQL statements.
● The commit indicator, C.
● A newline indicator.
Every record in a transaction is contained between the begin and commit indicators. Each
combination of commit timestamp and RBA isunique. You can customize the output
format with optional arguments.
Default See “Default output”
Syntax FORMATSQL [<option>] [, ...]

Test scripts for queries before and after upgrade (bi7.0)

HI,
i need to create a documnet for testing the over all functionality of the queries and wad before upgradation and after upgradation(bi 7.0) like structure, rkf , ckf variables, etc , please guide me and send me if any sample template available on this scenario
Thanks in advance
narasim

You can spool (or put in a database table) in your 10G database the sql statements and their performance metadata (this should be done when the system is really used). After the upgrade you can do the same select as used to spool. the statements in the 10G database and compare them (again in a really used system). A sql statement to use could be:
select inst_id, sql_id, hash_value, executions
,(cpu_time/executions)/1000000 cpu_time
,(elapsed_time/executions)/1000000 elapsed_time
,(disk_reads/executions) disk_reads
,(buffer_gets/executions) buffer_gets
,(rows_processed/executions) rows_processed
from gv$sqlarea
where executions>0
order by inst_id, sql_id, hash_value
Regards, Gerwin

Oracle Alert: Access before and after update values of a table column

We have a requirement where a notification needs to be sent when 'END_DATE' attribute (column in a table X) is set, in an Oracle Applications form.
I have defined an Event based Oracle Alert which fires 'On Update' of the table X.
Could anyone please let me know as how to access the value of 'END_DATE' before and after update (i.e :new.END_DATE and :old.END_DATE) in the sql query of the alert.
The need to use the before update and after update values of the attribute 'END_DATE' is that if we add the condition END_DATE is not null, the alert is sent even if any other attrbutes are updated in the Oracle form which is not the intended behavior.
Appreciate any help.
Thanks

Hi
use selectionlistener for your first table then add clientlistener and serverlistener so that you will get the rows on click in back bean.
then get second table vo and and create and add row for that view object. add partial target to refresh your second table from back bean.
on click of save call commit operation.

HT3281 One podcast I'm subscribed to wont download one podcast but others before and after will download what can I do?

I'm subscribed to a podcast group and I've never had trouble with it before just one podcast didnt download and now it wont download at all, ones before it and after it will but this one wont, It plays on itunes but thats it. I tried deleting it and re subscribing but it just is downloading I dunno what to do beucase i only get chance to listen to them on mu ipod when I'm out and about I dont have time to listen to them otherwise.
Thanks, Carrie.

Windows 64bit download: http://support.apple.com/kb/DL1615

Before and After Aggregation

Hi Gurus'
Where can we find the options "Before Aggregation" and "After Aggregation"?What is the basic use of these aggregations?Why we should not use the option called Before Aggregation in a Multiprovider?
Could any one please let me know the above..
Thanks!
James

Hi James,
Aggregation
This function is only available for formulas and calculated key figures.
You can make settings for aggregation and calculation time (for the detail level of the calculated key figure or formula) here. By default, the data is first aggregated to the display level; the formula is then calculated (= standard aggregation). The exception aggregation setting allows the formula to be calculated before aggregation using a reference characteristic, and to be then aggregated with the exception aggregation.
You can select the following settings in the Exception Aggregation field.
●      Use Standard Aggregation: You use this setting to specify that aggregation is to take place before calculating the formula. Therefore, you do not use exception aggregation.
●      Sum
●      Maximum
●      Minimum
●      Exception If More Than One Record Occurs
●      Exception If More Than One Value Occurs
●      Exception If More Than One Value <> 0 Occurs
●      Average of All Values
●      Average of All Values <> 0
●      Average Weighted with Calendar Days
●      Average Weighted with Working Days
You can specify the ID of the factory calendar in Customizing. For more information see the SAP Reference IMG ® SAP Customizing Implementation Guide ® SAP NetWeaver ® Business Intelligence ® Settings for Reporting and Analysis ® General Settings for Reporting and Analysis Set F4 Help and Hierarchies for Time Characteristics/OLAP Settings.
●      Counter for All Detailed Values
●      Counter for All Detailed Values That Are Not Zero, Null, or Error
●      First Value
●      Last Value
●      Standard Deviation
●      Variance
If you use exception aggregation, you must select a characteristic from the Reference Characteristic field, using which the system can calculate the formula before aggregation. In the Reference Characteristic field, you can select from all characteristics that are available in the InfoProvider.
For more information about the setting for exception aggregation, see the documentation for InfoObject maintenance under Tab Page: Aggregation.
Calculate After Aggregation: This field is only displayed for calculated key figures; it is not displayed for formulas. It is used for display and stipulates that the formula of the calculated key figure is calculated after aggregation. If you use calculated key figures that you defined in SAP BW 3.5, you can use this field to specify whether the formula is to be calculated before or after aggregation.
Calculating before aggregation results in poor performance because the database reads the data at the most detailed level and the formula is calculated for every record. In formula calculations, often the single record information for just one or two specific characteristics is required; the remaining data from the InfoProvider can be aggregated.
We recommend that you control the calculation level using an exception aggregation with the corresponding reference characteristic. If you require multiple exception aggregations or reference characteristics, you can nest formulas and calculated key figures in one another and specify an exception aggregation for each formula or calculated key figure.
For more information,
Examples of Exception Aggregation Last Value (LAS) and Average (AV0)
Tab Page: Aggregation
Hope it Helps
Srini

Difference between before and after trigger

    Is there any difference between these two trigger .
    If its there , then please tell when we should use before trigger and after trigger
   thanx
   young bro


BEFORE Triggers
BEFORE triggers run the trigger action before the triggering statement is run. This type of trigger is commonly used in the following situations:
When the trigger action determines whether the triggering statement should be allowed to complete. Using a BEFORE trigger for this purpose, you can eliminate unnecessary processing of the triggering statement and its eventual rollback in cases where an exception is raised in the trigger action.
To derive specific column values before completing a triggering INSERT or UPDATE statement.
AFTER Triggers
AFTER triggers run the trigger action after the triggering statement is run.
Trigger Type Combinations
Using the options listed previously, you can create four types of row and statement triggers:
BEFORE statement trigger
Before executing the triggering statement, the trigger action is run.
BEFORE row trigger
Before modifying each row affected by the triggering statement and before checking appropriate integrity constraints, the trigger action is run, if the trigger restriction was not violated.
AFTER statement trigger
After executing the triggering statement and applying any deferred integrity constraints, the trigger action is run.
AFTER row trigger
After modifying each row affected by the triggering statement and possibly applying appropriate integrity constraints, the trigger action is run for the current row provided the trigger restriction was not violated. Unlike BEFORE row triggers, AFTER row triggers lock rows.
You can have multiple triggers of the same type for the same statement for any given table. For example, you can have two BEFORE statement triggers for UPDATE statements on the employees table. Multiple triggers of the same type permit modular installation of applications that have triggers on the same tables. Also, Oracle materialized view logs use AFTER row triggers, so you can design your own AFTER row trigger in addition to the Oracle-defined AFTER row trigger.
You can create as many triggers of the preceding different types as you need for each type of DML statement, (INSERT, UPDATE, or DELETE).
S

Before image and after image concept of ODS

Similar Messages

Maybe you are looking for