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

Similar Messages

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

Differences between CLEARUPDATESTATUS ONLY and AFTER

As we load data on a monthly basis (time is a sparse dimension), we would like to take advantage of Intelligent Calculation.We use a calcscript with several FIX - CALC DIM(several dimensions, not all) - ENDFIX.We are not sure if we should use:a) the command SET CLEARUPDATESTATUS AFTER at the beginning of the calc script. However, the administrator guide says that with sparse dimensions level 0 blocks are not marked as clean, and as a result, next month Essbase recalculates again upper-level blocks for previous months (it is not neccesary, as previous months were already calculated)or b) at the end of the calcscript add two sentences: SET CLEARUPDATESTATUS AFTER; CALC ALL; (These commands only marks all blocks as clean including level 0, so it does not recalculate previous months).Should we use option b) instead of a)?Thank you very much for your help

We can't do a registry key change no. We don't have any control over the end-user's setup. But perhaps there is a line we can add to the XML source to do it on a per form basis? In the same way I forced legacy rendering using
<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.4/ LegacyRendering:1?>
Failing that, are you aware of any methods that can be used to clear out some of the memory used by the form? We're also exploring other methods for 'hiding' subforms, we're currently investigating dynamically moving objects in the hierachy at runtime so we can shift the nested subforms off screen temporarily.
Thanks for your thoughts on this Paul.
David

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

What is difference between report programming and dialog programming?

hi,
what is difference between report programming and dialog programming? plz provide some example code
bye

ABAP programming
Basically reports are used to read database and represent the results in lists.
Reports are collections of processing blocks that the system calls depending on events.
We can use reports to evaluate data from database tables.
Reports are stand alone programs and controlled by events.
A report itself never creates events
steps in report:
Processing the selection screen
Reading the database
Evaluating the data and creating lists
Outputting a list.
1st u write simple logics, after that u can enhance the code as step by step.
http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
http://www.sapdev.co.uk/reporting/reportinghome.htm
Dialog Programming
Structure of a Dialog Program
A dialog program consists of the following basic components:
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Check this link for basics.
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Check this link for Dialog Programming/Table Control
http://www.planetsap.com/Tips_and_Tricks.htm#dialog
Check this SAP Help for Dialog Program doc.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
Check this SAP Help link for Subscreens.
http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
Check this link for subscreen demo program.
http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
Also check this link too.
http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
http://abapprogramming.blogspot.com/

What is difference between local variable and property node ?

What is difference between local variable and property node ?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview

To make things clear, here are two small examples that show how nasty locals and value properties can be to the naive programmer.
- Open the diagram of the race condition.vi before running it and try to predict what will be the values of the two counters after the third run.
- Use the Compare Locals Properties and Wires.vi to find out how slow locals and value properties can be (times 1000+).
This being demonstrated, I must add that I use globals and value properties quite often, because they are often very convenient
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Race condition.vi ‏9 KB
Compare Locals Properties and Wires.vi ‏18 KB

Difference between implicit enhancement and explicit enhancement

What is the difference between implicit enhancement and explicit enhancement .

Hi Peters,
Implicit enhancement option
Throughout the ABAP system, enhancement options are automatically available at certain pre-defined places. Some of the implicit options are:
u2022 At the end of all the programs (Includes, Reports, Function pool, Module pool, etc.), after the last statement
u2022 At the beginning and end of all FORM subroutines
u2022 At the end of all Function Modules
u2022 At the end of all visibility areas (public, protected and private) of local class
To view all the implicit options available in a source code, choose u2018Edit -> Enhancement Operations -> Show Implicit Enhancement Optionsu2019 from the editor.
Befor that you click on the spiral icon button in the application toolbar
Explicit enhancement option
The Implicit enhancement options are provided at specific source code places explicitly by SAP (Note that these enhancement definitions can also be created by partners and customers in their code).
There are two types of Explicit Enhancement options available. One which can be provided at a specific place - called Enhancement Point, and another which can be used to replace a set of statements u2013 called Enhancement Section. For this, we now have two new ABAP statements, viz.
u2022 ENHANCEMENT-POINT
u2022 ENHANCEMENT-SECTION
When the Enhancement-Section is implemented, only the implementation gets executed and the original code doesnu2019t get executed. This is a new technique, which didnu2019t exist previously in any of the old ways of enhancing, to exclude any standard SAP code from execution. Because of this, there can be only one active implementation of an Enhancement-Section. On the other hand, there can be multiple active implementations of an Enhancement-Point, in which case all the implementations will be executed with no guarantee in the order of execution.
For more information check the following link
[http://help.sap.com/saphelp_nw70/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm]
Thanks,
Surya

Difference between Scheduling lines and Delivery schedule

Hi SD Experts
can u say me the clear difference between Scheduling lines and Delivery schedule.
where we will maintain deliver schedule. whether delivery schedule is automatically created along scheduling agreements..
with regards
James

Hi James,
Schedule Lines: Has basically information realted to delivery scheduling in Sales Order level.
Delivery Scheduling: Is a process using which system will determine what are the different activities which need to be performed and time taken for each activitiy only after which the material can be delivered to the customer.
Delievry scheduling will be started only from the material availability date i.e., system will first determine the material avail date and then do scheduling. By default Standard SAP system does Backward Scheduling in case material availability falls beyond the required delivery date system will do forward schedluing
Delivery Scheduling consists of the following Basic activities:
We give deatils while creating order:
Order Creation Date
Required Delivery Date
Order date - Material availability date - Transportation Planning Date - Loading date - Goods Issue Date - Required Delivery Date
Time Between GI Date and required Delivery Date is called Transit Time
Time Between LoadingDate and GI Date is called Loading time
Time Between Material Availability Date and Loading Date consists of 2 components - Pick / PackTime and Transportation Planning Time
System has to calculate all this before it determines the confirmed delivery date.
Give your mail Id I have some Presentation I will send you across.
REWARD POINTS IF IT HELPS
Regards
Srini

Any basic differences between AT&T and Verizon, & other questions

I am thinking of buying an iPad mini with retina display (32gb). This would most likely be the only iPad I would ever own. I would use it mostly at the house with wifi, but would like to have one with cellular for when we travel in the US and Canada, and for when the electricity goes out. We currently live in a location where both AT&T and Verizon are viable options, but sometime in the next year we hope to move. The state is rural and mountainous, so as we drive around, my spouse's iPhone (with an AT&T plan) often loses service, but so does my Jitterbug phone, which is not tied to any one carrier (as far as I know). A phone can get a signal in one locaton, but then lose it a few feet down the road. So, there is no way I can choose between AT&T or Verizon based on coverage because both are options right now and there is no way to predict which one(s), if any, might provide service to wherever we end up moving to. Therefore, I'm wondering if there are any basic differences between AT&T and Verizon (or any other of the possible carriers) in what they offer or how they work or what they charge and so on that can help me decide which one to choose since it is my understanding that once I pick one of them for an iPad, that decision can never be changed without purchasing a new device. (e.g., I had read somewhere that Verizon does not allow for voice and data at the same time, but since an iPad is not a phone, is that even an issue?) Also, will the iPad work if there is only regular 4G or 3G service? And will a cellular iPad work without signing up for a data plan since I expect to start with only wifi and then add a data plan later? Thank you.

Alfred DeRose, Thank you for answering the second and third questions. Judging by what you wrote, I am assuming there are no differences between what AT&T and Verizon offer that affects iPads, other than looking at coverage area and the cost of "pay as you go" plans. And, as noted, coverage is not something I can base a decision on at this time. So, I either flip a coin to choose between AT&T and Verizon and hope the result is the right one after we move to wherever we end up finding a place to live, or I continue to wait for another year or more until we actually find a new house before I buy an iPad (or maybe a Kindle Fire HDX 8.9"to save money, but I think I've probably settled on an iPad mini retina 7.9" despite its smaller screen). That does not move me along the decision-making process at all, but it is what it is.
Greatcall has not answered my question about what carrier(s) the Jitterbug Plus phone uses. If, in fact, it uses just the Verizon network, I will try to pay better attention to any possible differences in service areas between that phone and my spouse's iPhone as we travel around the state to see if that helps at all. But coverage is so location specific here that I don't think it will.

Difference between Field symbols and field group

Hi experts,
Can you please advice me what is the difference between field symbols and field groups.
Thanks in advance,
Logu.

Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
A field group combines several existing fields together under one name
like
FIELD-GROUPS: fg.
then you can use one insert statement to insert values in fields of field-group.
INSERT f1 f2 ... INTO fg.
Field symbols
If u have experience with 'C', then understand this to be similar to a pointer.
It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
FIELD-SYMBOLS <FS>.
DATA FIELD VALUE 'X'.
ASSIGN FIELD TO <FS>.
WRITE <FS>.
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
example :
DATA: BEGIN OF SPTAB OCCURS 0,
line(1000), " or type string
END OF SPTAB.
DATA: IDX LIKE SY-INDEX.
field-symbols <FS1>.
split tb_sip AT ';' INTO table sptab.
LOOP AT SPTAB.
IDX = IDX + 1.
ASSIGN COMPONENT IDX OF STRUCTURE tb_detsip TO <FS1>.
If sy-subrc = 0.
<FS1> = SPTAB-line.
Endif.
Endloop.
append tb_detsip.
clear idx.
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
Reward points if useful.

Difference between Field symbols and Field groups

<b>Hi Friends,
can you tell me the differences between Field symbols and Field groups? with any examples preferably?
Regards
Dinesh</b>

Hi Dinesh,
A field group combines several existing fields together under one name
like
FIELD-GROUPS: fg.
then you can use one insert statement to insert values in fields of field-group.
INSERT f1 f2 ... INTO fg.
<b>Field symbols</b>
If u have experience with 'C', then understand this to be similar to a pointer.
It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
FIELD-SYMBOLS <FS>.
DATA FIELD VALUE 'X'.
ASSIGN FIELD TO <FS>.
WRITE <FS>.
Field symbols: are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field Groups:
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
Field Groups / Extracts
http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
Field Symbols
http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
Reward points if helpful.
Regards,
Hemant

Difference between class report and interactive report

please give me the differences between classical report and interactive report

Hi,read the following :
In ABAP, there are a total of 7 types of reports. They are:
Classical Reports
Interactive Reports
Logical Database Reports
ABAP query
ALV Reports (ALV stands for ABAP List Viewer)
Report Writer/Report Painter
Views (There are different types of views also)
Classical Reports
These are the most simple reports. It is just an output of data using the Write statement inside a loop.
Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT
Interactive Reports
As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.
And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.
We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).
Logical Database Reports
Logical database is another tool for ABAP reports. Using LDB we can provide extra features for ABAP reports.
While using LDB there is no need for us to declare Parameters.
Selection-screen as they will be generated automatically.
We have to use the statement NODES in ABAP report.
ABAP Query Reports
ABAP query is another tool for ABAP. It provides efficency for ABAP reports. These reports are very accurate.
Transaction Code : SQ01
Report Writer / Report painter
Super users and end users can use Report Painter/Report Writer tools to write their own reports.
Giving them the ability to report on additional fields at their discretion shifts the report maintenance burden to them, saving SAP support groups time and effort normally spent creating and maintaining the reports.
ALV reports
Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length.
In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output.
The report output can contain up to 90 columns in the display with the wide array of display options.
There is no difference between drill down and interactive report, they are the same.
With drilldown reporting, SAP provides you with an interactive information system to let you evaluate the data collected in your application. This information system is capable of analyzing all the data according to any of the characteristics that describe the data. You can also use any key figures you wish to categorize your data. You can display a number of objects for a given key figure, or a number of key figures for a given object. In addition, the system lets you carry out any number of variance analyses (such as plan/actual comparisons, fiscal year comparisons, comparisons of different objects, and so on).
*More on Classical Vs Interactive*
Classical Reports
These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop.
Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.
Events In Classical Reports.
INTIALIZATION: This event triggers before selection screen display.
AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode.
START OF SELECTION: Start of selection screen triggers after proceesing selection screen.
END-OF-SELECTION : It is for Logical Database Reporting.
Interactive Reports
As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.
And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.
We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).
Events associated with Interactive Reports are:
1. AT LINE-SELECTION
2. AT USER-COMMAND
3. AT PF<key>
4. TOP-OF-PAGE DURING LINE-SELECTION.
HIDE statement holds the data to be displayed in the secondary list.
sy-lisel : contains data of the selected line.
sy-lsind : contains the level of report (from 0 to 21)
Interactive Report Events:
AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist.
AT PFn: For predefined function keys...
AT USER-COMMAND : It provides user functions keys.
TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list.
Reward if found helpful

DIFFERENCES between BASIC SCHEDULING and LEAD-TIME SCHEDULING.

Hello SAP Gurus,
Kindly let me know the differences between BASIC SCHEDULING and LEAD-TIME SCHEDULING.
Looking for your early feedback.
Warm regards,
Kaushik.

Hi,
Basic scheduling :
1.Basic dates are calculated.
2.Exact to day.
3.No cap reqmts are generated.
4.uses the inhouse production time from material master.
5.carried out automatically during planning run.
In basic date calculation ( order start date/ order finish date ) the system always
calculates backward scheduling.
1. From the reqmts date the system subtracts the GR processing time to
calculate the order fininsh date.
2. From the order finish date the system subtracts the inhouse production time to calculate the order start date.
3. From the order start date the system subtracts the opening period given in scheduling margin key to calculate the order opening date.
Lead time scheduling :
1.Exact to second
2.ie production start date /time and finish date and time are calculated.
3. cap reqmts are generated.
4. uses times from routing.
5. carried out only if the scheduling mode in MD02 screen is kept with indicator 2.
From the order finish date the system subtracts the float after production to calculate the production finish date.
From the production finish date the individual operations in the routing are scheduled backwards to calculate production start date.
From the production start date the system subtracts the float before production
to calculate order start date.
Regards,
nandha

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

Difference between Before aggregation and After aggregation

Similar Messages

Maybe you are looking for