Wat is the advantage of force view?

hello,
only i know that it is created object in db and after tat we can create the table as per requirement.
please tell me wat is the main advantage of Force View?
Tks
PM

Hello PM,
if you have mutual dependencies, e.g. between a package and a view, then you cannot create the view because of an invalid package and you cannot validate the package because the view does not exist.
A workaround has been to create a dummy view, compile the package and create the actual view. Now you can force Oracle to create the view and then compile the package.
Regards
Marcus

Similar Messages

What is VIEW in Database table what is the advantage

Hi:
I would like to get your opinion on what is the advantage of Table VIEW?
I read a note saying it is all about simplifying Query.
But when you come to XMLTYPE where there is only ONE ROW and NO COLUMN,
How do you create XMLVIEW for a large XML files?
Please help
Ali_02

Overview of Views
Read here...
http://download.oracle.com/docs/cd/E11882_01/server.112/e10713/schemaob.htm#i20690
XMLView or XMLTYPE ?
Overview of XML in Oracle Database
Read here...
http://download.oracle.com/docs/cd/E11882_01/server.112/e10713/cncptdev.htm#CNCPT1535
Edited by: ordba on Mar 4, 2010 9:50 AM

Advantage of Materialized view on prebuilt table

Could someone tell me the advantage of Materialized view on prebuilt table?. I'm unable to understand the concept from the Oracle documentation. I need to know the answers for following questions.
1) Is the data stored in table and MV same?. Does the query retrive data from table or MV?. The query internally uses either table or a view as the names of both are same.
2) Our DSS application is generating complicated queries and executing for long time. Is there any way I can optimize those queries using MV without rewriting the code in the application.

It's a roughly analgous problem to figuring out what set of indexes to create to improve the performance of an application-- you need to understand the various queries, how the application is accessing data, and you need to balance a variety of competing needs in order to come up with a reasonable set of indexes.
Fundamentally, Oracle can only use a materialized view to satisfy a query if a human could use just the data in the materialized view to answer the question. That generally means that the materialized view is going to have to be aggregated at a lower level or at the same level as the query. A materialized view that aggregates sales by day can be used for queries by year but a materialized view that aggregates sales by year cannot be used for queries that get sales by day. A materiailized view that aggregates sales by vendor and product can be used for queries that aggregate by vendor or by product, but a materialized view that aggregates by product cannot be used in a query that aggregates by product for a particular vendor.
You'll have to balance what materialized views are ideal for a particular query, what materialized views are sufficient for a particular set of queries, and how to balance the space, managability, and refresh performance requirements between creating lots of somewhat redundant materialized views that provide optimal query performance at the cost of a lot of disk and a large refresh window vs creating fewer, more general materialized views that consume less disk and can be refreshed faster but that provide less query performance boosts.
Justin

Uses of force view

Hi All,
Can you tell me what are the uses of force view?
Thanks in advance.

It's relatively common to find in install scripts (and/or in import & export). If you're going to create dozens of different views which depend on various other views and/or tables, figuring out the proper order to drop and/or create each view and ensuring that the build script is updated with that information every time can be rather painful and tedious. It's much easier to FORCE the creation of the views in some human-reasonable order (i.e. alphabetically) and compile everything at the end.
Justin

What is the main difference between view and materialize view and advantage of Mview ??

What is the main difference between view and materialize view and advantage of Mview ??

1.A view uses a query to pull data from its associated tables.
2.Views do not have data's physically stored in the Database.
3.Views Get the Data from 2 or more tables and displays as a single block.
4.But a materialized view is a table on disk is a result set of a query done.
5.A Materialized view can have data's in the database.
6.Materialized view are used for Boosting the Performance.
7.And the important one is Materialized views are updated based on the parameters defined when they are created.
8.By using triggers we can update the data in a materialized view.
9.When you call a materialized view it will show the data when it was last updated.
Hope it helps.

What is the advantage of using DataSourceUpdateMode.OnPropertyChanged for databinding winform c#

first see my code
public class Car : INotifyPropertyChanged
private string _make;
private string _model;
private int _year;
public event PropertyChangedEventHandler PropertyChanged;
public Car(string make, string model, int year)
_make = make;
_model = model;
_year = year;
public string Make
get { return _make; }
set
_make = value;
this.NotifyPropertyChanged("Make");
public string Model
get { return _model; }
set
_model = value;
this.NotifyPropertyChanged("Model");
public int Year
get { return _year; }
set
_year = value;
this.NotifyPropertyChanged("Year");
private void NotifyPropertyChanged(string name)
if (PropertyChanged != null)
PropertyChanged(this, new PropertyChangedEventArgs(name));
this way i am binding
public partial class Form1 : Form
public Form1()
InitializeComponent();
BindingList<Car> ol;
private void Form1_Load(object sender, EventArgs e)
Car carTest = new Car("Ford", "Mustang", 1967);
ol = new BindingList<Car>();
ol.Add(carTest);
this.textBox1.DataBindings.Add("Text", ol, "Make", true, DataSourceUpdateMode.OnPropertyChanged);
this.textBox2.DataBindings.Add("Text", ol, "Make", true, DataSourceUpdateMode.OnPropertyChanged);
this.textBox3.DataBindings.Add("Text", ol, "Make");
dataGridView1.DataSource = ol;
private void button1_Click(object sender, EventArgs e)
ol.Where(d => d.Make == "Ford").First().Make = "My Ford000";
i use DataSourceUpdateMode.OnPropertyChanged for one textbox and did not use for other textbox
 this.textBox2.DataBindings.Add("Text", ol, "Make", true, DataSourceUpdateMode.OnPropertyChanged);
 this.textBox3.DataBindings.Add("Text", ol, "Make");
when change value in one textbox the change is reflected in other textbox too without using
DataSourceUpdateMode.OnPropertyChanged so just do not understand the advantage of
DataSourceUpdateMode.OnPropertyChanged
even when change data in data source by the below way then change is also reflected in all textboxes.
ol.Where(d => d.Make == "Ford").First().Make = "My Ford000";
please help me to understand right usage of DataSourceUpdateMode.OnPropertyChanged
like when and where to use.
thanks

Hi Mou_kolkata,
>> please help me to understand right usage of DataSourceUpdateMode.OnPropertyChanged like when and where to use.
In my option, when the binding is first established, the specified property of the data source object is copied to the specified property of the host object. Thereafter, the specified properties of the objects can be updated either automatically or manually.
DataSourceUpdateMode.OnPropertyChanged specifies the data source object is to be updated whenever the host object publishes a property changed event for the bound property. You could use the code below when you want the datasouce object to be updated automatically.
this.textBox1.DataBindings.Add("Text", ol, "Make", true, DataSourceUpdateMode.OnPropertyChanged);
You could refer the link below for more information:
# Hosting Simple Data Binding
http://www.codeproject.com/Articles/114758/Hosting-Simple-Data-Binding
Hope it will help.
Best Regards,
Edward
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

What is the advantage of using IB to create XIBs/Class Objects over coding?

Hi all,
I hoping someone can provide me some pros and cons as to when I should use IB to create XIBs and/or class objects as opposed to directly coding them.
For example, if I choose Apple's Template for creating a Navigation Based Application (cocoa touch), the project creates two NIB files - MainMenu and RootViewController.
However looking at one of demo apps SimpleDrillDown, it does not have a RootViewController XIB and instead creates it via code.
Another example from the same two apps is that the template generates a "Navigation Controller" class object in the Mainmenu.xib. SimpleDrillDown does not bother with this in the XIB, but uses code to generate the controller:
- (void)applicationDidFinishLaunching:(UIApplication *)application {
// Create the navigation and view controllers
RootViewController *rootViewController = [[RootViewController alloc] init];
UINavigationController *aNavigationController = [[UINavigationController alloc] initWithRootViewController:rootViewController];
self.navigationController = aNavigationController;
[aNavigationController release];
[rootViewController release];
// Configure and show the window
[window addSubview:[navigationController view]];
[window makeKeyAndVisible];
as opposed to the template which only needs this:
- (void)applicationDidFinishLaunching:(UIApplication *)application {
// Configure and show the window
// Navigation Controller is defined in MainWindow.xib
[window addSubview:[navigationController view]];
[window makeKeyAndVisible];
So what are the advantages of each approach. Why does apple suggest one approach and yet all its demos use another.
Any thoughts, answers gratefully received.
TIA, Michael.

You can do whatever you're comfortable with, but most of the best Cocoa programmers--the ones on the Mac, I mean--recommend putting everything you can into Interface Builder.
It's a little like the difference between writing a program to do a bunch of financial calculations and using a spreadsheet. Yeah, the program can do everything the spreadsheet can--and more besides--but you'll find it far easier to create, use and modify the spreadsheet.
Interface Builder takes away a lot of completely meaningless choices ("What order should I create the objects in? How should I name the variables? How should I create their frames? What order should I set the attributes in?"), leaving you with an interface optimized for creating and arranging objects, and allowing your code to focus on what you really do need to think about--your application's logic.
(By the way--part of the reason Apple's demos don't all use Interface Builder is that the very first SDK releases didn't have it. Back then, you had to create all your views programatically. Believe me, I have no wish to go back to setting autoresize masks manually. Now get off my lawn, whippersnapper.)

How to subdivide 1 large TABLE based on the output of a VIEW

I am searching for a decent method / example code to subdivide a large table (into a global temp table (GTT) for further processing) based on a list of numeric/alphanumeric which is the resultset from a view.
I am groping with the following strategy in PL/SQL:
1 -- set up cursor, execute the view (so I have the list of identifiers)
2 -- create a second cursor (or loop?) which:
accepts each of the identifiers in turn
executes a query (EXECUTE IMMEDIATE?) on the larger table
INSERTs (or appends?) each resultset into the GTT
3 -- Then the GTT contains just the requires subset of the larger table for further processing and eventual import into iReport for reporting.
Can anyone point me to code that would "spoon feed" me on this? Or suggest the best / better way to go about it?
The scale of the issue here -- GTT is defined and ready to go, the larger table contains approx 40,000 rows and I need to extract a dozen subsets or so which add up to approx 1000 rows.
Thanks,
Rob

Welcome to the forum!
>
I am searching for a decent method / example code to subdivide a large table (into a global temp table (GTT) for further processing) based on a list of numeric/alphanumeric which is the resultset from a view.
Can anyone point me to code that would "spoon feed" me on this? Or suggest the best / better way to go about it?
The scale of the issue here -- GTT is defined and ready to go, the larger table contains approx 40,000 rows and I need to extract a dozen subsets or so which add up to approx 1000 rows.
>
No - there is no code to point you to.
As many of the previous responses indicate part of the concern is that you seem to have already chosen and partially implemented a solution but the information you provided makes us question whether you have adequately analyzed and defined the actual problem and processing that needs to happen. Here's why I have questions about your approach
1. GTT - a red flag issue - these tables are generally not needed in Oracle. So when you, or anyone says they plan to use one it raises a red flag. People want to be sure you really need one rather than not using a table at all, or just using a regular table instead of a GTT.
2. Double nested CURSOR loops - a DOUBLE red flag issue - this is almost always SLOW-BY-SLOW (row-by-row) processing at its worst. It is seldom needed, doesn't perform well and won't scale. People are going to question this choice and rightfully so.
3. EXECUTE IMMEDIATE - a red flag issue or at least a yellow/warning flag. This is definitely a legitimate methodology when it is needed but may times developers resort to it when it isn't needed because it seems easier than doing the hard work of actually defining ALL of the requirements. It seems easier because it appears that it will allow and work for those 'unexpected' things that seem to come up in new development.
Unfortunately most of those unexpected things come up because the developer did not adequately define all of the requirements. The code may execute when those things arise but it likely won't do the right thing.
Seeing all three of those red flag issues in the same question is like waving a red flag at a charging bull. The responses you get are all likely to be of the 'DO NOT DO THAT' variety.
You are correct that a work table is appropriate when there is business logic to be applied to a set of data that cannot be applied using SQL alone. Use a regular table unless
1. you plan to have multiple sessions working with the table simutaneously,
2. each session needs to work with ONLY their own data in that table and not data from other sessions
3. the data does NOT need to be available after the session ends
4. you actually need a GTT to take advantage of the automatic data preservation (ON COMMIT PRESERVE/DELETE) functionality
Remember - when a session ends the data in the GTT is gone. That can makek it very difficult to troubleshoot data related problems since a different session can't see what data is in the table. Even if a GTT is needed for the final product it is very useful to use a regular table so that the data can be examined after test runs to help find and fix problems. Then after development is complete and initial testing is done a GTT would be substituted and final testing performed.
So the main remaining question is why you need to perform multiple dynamic queries to get the data populated into the work table? Especially why is a nested cursor loop needed? My suspicion is that you have the queries stored in a query table and one of your loops extracts the query and executes it dynamically.
How many queries are we talking about? Do these queries change from run to run? Please provide more detail of the process and an example query for the selection filtering as well as a typical dynamic query you plan to use.

What is the advantage in Maintaing the master data if it can be directly ..

Hi,
When looking for possible values in an object, I see that it has 20 possible values that can be selected while in BEx. But when I go to the object itself under the InfoObject tree(in rsa1), with a hope to maintain master data, I do not find "Maintain Master" in the context menu of the object.
1. where could the possible values that I saw in the report be coming from?
2. I understand it is possible that the object was filled as data was being loaded in some data target and that may explain why no master data was being maintained but it had values.
If that is the case, then, what is the advantage in Maintaing the master data (i.e. directly maintaing the master if it can be directly maintain through loaded files)?
Thanks

Thanks,
On 1:
so you are saying that the SID table gets populated during the transactional data load.
In the change mode of the object, I see
SID Table /BI0/Sxxxxxxx.
a)
Is this what you were referring to as the S table? How do I see the values in this SID talbe.
and can it be modified?
b)
Also, how come that the other object without "Maintain Master data" in context menu and the one with this option both have the
SID Table /BI0/S........
c)
Other than the difference I see in their context menu what should be the difference?
2.
You mentioned that the "System just creates a SID for the incoming value. "
a)
Where in the system do I see these system generated SIDs?
You noted that "But loading master data assures the masterdata attributes and texts, which are not generated while loading transactional data except for the SID"
b) If this is so important, is there a way to prevent data loads without master data
i.e. to force the maintenance of master data?
Also, isn't it possible to load the attributes of an infoobject while load data? You seem o be suggesting otherwise.
Thanks

What are the advantages..

Hi friends,
 can you please tell me what are the advantages of using MVC? because i can use ABAP Objects without using MVC.
Thanks in advance,
Regards,
Kannan.

Hi Kanna,
 For Dynamically componentised you need to use controller.In the main page you partition for what you want to present dynamically and then call controller as a response to the user.What the action you have take in case of Page flow logic(Event Handler) need to be placed in controller.
Using the MVC design pattern has the following advantages:
· Structuring BSP applications is simplified, since the view is cleanly separated from the controller and the model. This not only facilitates changing BSP applications, but also considerably improves their maintenance.
· You have the option of generating program-driven layout. The HTML/XML output is therefore created by program code instead of a page with scripting.
· Navigation using the <bsp:goto> element and call using the <bsp:call> element. The advantage of using <bsp:goto> navigation over redirect is that there is no additional network traffic. Furthermore, you remain in the same work process, which can have advantages for creating objects and memory space. The call using <bsp:call> element is more variable than adding them using INCLUDEdirective, since it is triggered at runtime.
With the call option using <bsp:call>, you can also distribute the user interface into components.
· Optimized performance due to fewer redirects.
· Intuitive and east-to-use interface for application development.
Main advantage of MVC is that you can keep these(Model View ,Controller) separately.If you need to change in logic you do not have to worry about presentation(View).
Regards,
Albert

Advantage of FORCE LOGGING over NOLOGGING

Hi,
Can you please help me on the advantages of using force logging mode with a standby database and the effect of it in indexes etc. Also, it may help if you could also share ideas on difference between the two modes?
Thanks,
Jennah

>> Can you help me what factors would be sacrificed
This really depends on your system, in most cases you will not be able to see a difference. However i did a small test:
- drop index, restart db
- create index with logging (measure time/redo size)
- drop index, restart db
- create index with logging (measure time/redo size)
Result:
logging - Elapsed: 00:02:40.68 / Redo size: 800mb
nologging - Elapsed: 00:02:20.29 / Redo size: 1.5mb
Here the full test:
[code]SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME VALUE
redo size 28304
SQL> CREATE UNIQUE INDEX "SAPR3"."CDCLS~0" ON "SAPR3"."CDCLS"
("MANDANT", "OBJECTCLAS", "OBJECTID", "CHANGENR", "PAGENO")
PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PSAPCLUI" LOGGING;
Index created.
Elapsed: 00:02:40.68
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME VALUE
redo size 834714816
SQL> select segment_name, bytes/1024/1024 "Size_MB" from dba_segments where segment_name = 'CDCLS~0'
SEGMENT_NAME Size_MB
CDCLS~0 800
drop index / db restart here
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME VALUE
redo size 28992
SQL> CREATE UNIQUE INDEX "SAPR3"."CDCLS~0" ON "SAPR3"."CDCLS"
("MANDANT", "OBJECTCLAS", "OBJECTID", "CHANGENR", "PAGENO")
PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "PSAPCLUI" NOLOGGING;
Index created.
Elapsed: 00:02:20.29
SQL> select a.name, b.value from v$statname a, v$mystat b where a.statistic# = b.statistic# and a.name = 'redo size';
NAME VALUE
redo size 1520824
SQL> select segment_name, bytes/1024/1024 "Size_MB" from dba_segments where segment_name = 'CDCLS~0';
SEGMENT_NAME Size_MB
CDCLS~0 800[/code]

Create Force View

Hi all,
When I import the dumpfile I get the follwing errors...
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "uni"."V_F_OFS_REQUEST_DETAIL" "
" ("RECID","XMLRECORD","APPLICATION","NAPPLICATION","VERSION","NVERSION","F"
"UNCTION","NFUNCTION","TRANS_REFERENCE","NTRANS_REFERENCE","USER_NAME","NUSE"
"R_NAME","COMPANY","NCOMPANY","DATE_TIME_RECD","NDATE_TIME_RECD","DATE_TIME_"
"QUEUE","NDATE_TIME_QUEUE","DATE_TIME_PROC","NDATE_TIME_PROC","STATUS","NSTA"
"TUS","MSG_IN","NMSG_IN","MSG_OUT","NMSG_OUT","ACTION","NACTION","GTS_CONTRO"
"L","NGTS_CONTROL","NO_OF_AUTH","NNO_OF_AUTH") AS "
"SELECT x.RECID, x.XMLRECORD.getClobVal() "XMLRECORD""
",NVL(extractValue(x.xmlrecord,'/row/c1'),'^A') "APPLICATION",NVL(NUMCAST(ex"
"tractValue(x.xmlrecord,'/row/c1')),0) "nAPPLICATION",NVL(extractValue(x.xml"
"record,'/row/c2'),'^A') "VERSION",NVL(NUMCAST(extractValue(x.xmlrecord,'/ro"
"w/c2')),0) "nVERSION",NVL(extractValue(x.xmlrecord,'/row/c3'),'^A') "FUNCTI"
"ON",NVL(NUMCAST(extractValue(x.xmlrecord,'/row/c3')),0) "nFUNCTION",NVL(ext"
"ractValue(x.xmlrecord,'/row/c4'),'^A') "TRANS_REFERENCE",NVL(NUMCAST(extrac"
"tValue(x.xmlrecord,'/row/c4')),0) "nTRANS_REFERENCE",NVL(extractValue(x.xml"
"record,'/row/c5'),'^A') "USER_NAME",NVL(NUMCAST(extractValue(x.xmlrecord,'/"
"row/c5')),0) "nUSER_NAME",NVL(extractValue(x.xmlrecord,'/row/c6'),'^A') "CO"
"MPANY",NVL(NUMCAST(extractValue(x.xmlrecord,'/row/c6')),0) "nCOMPANY",NVL(e"
How to overcome this? and how to avoid this? Pls suggest me
Thanks in advance..

Yes, force view command never gives an error, its always a warning. And if you are getting this error during import, dont worry, view have been created in your schema by import command. This might happen when view is refers to any table that actually is not present. In your case it might be a case when view in the current schema refers table in another schema. So i think you should just try to query that view in the schema where you have just done the import.
Also to verify that why error came, you can go to the source schema and check for the base table of the view under consideration. From there you can get useful information about the actual base table and why import showing up the warning.

Force view

Hello Guys,
Can you tell me what is the use of view when we create with FORCE option if underliying table is not available ?
CREATE OR REPLACE FORCE VIEW MY_VIEW AS SELECT * FROM EMP;
Now View My_View will be created even if the emp table is not available. But where we can use this view ?. What is the applicatin of My_View when we know that EMP table is not available ?.
Thanking you.

Simple demonstration...
SQL> create or replace view my_view as select * from empdept;
create or replace view my_view as select * from empdept
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> create or replace force view my_view as select * from empdept;
Warning: View created with compilation errors.
SQL> select * from my_view;
select * from my_view
ERROR at line 1:
ORA-04063: view "SCOTT.MY_VIEW" has errors
SQL> create table empdept as select ename, deptno from emp;
Table created.
SQL> select * from my_view;
ENAME          DEPTNO
SMITH              20
ALLEN              30
WARD
JONES              20
MARTIN             30
BLAKE
CLARK              10
SCOTT              20
KING               10
TURNER             30
ADAMS              20
JAMES              30
FORD               20
MILLER             10
14 rows selected.
SQL>

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi ?
I am modifying an existing workspace for a new product, and it seems like more work to add the vi's into a LabVIEW project
does it gain anything in the long run

Hi Rusty,
I wanted to quickly clarify on the integration between TestStand and LabVIEW Projects.
As Jeff mentioned, some of the big benefits of using LabVIEW Projects is to organize code and to namespace them.
For instance if you had a project called "Power Supply" that housed all your power supply code and had a VI in that called "Initialize", and another project called "Temperature Chamber" that also had a VI called "Initialize", both these VIs are namespaced by the project, so there is no longer confusion about which "Initialize" VI is being used.
Now from a TestStand point of view, in prior version of TestStand, we lost some of this benefit because TestStand did not know about TestStand projects and called VIs simply as un-namespaced VIs. However, in TestStand 2010 (released last year, free eval available at ni.com/teststand), we added the ability to (optionally) call VIs within the context of their projects. This means that:
VIs are now namespaced by their project, even when called from TestStand
VIs can use project specific constructs like NI-DAQmx tasks and conditional compilation settings
Note: When creating deployments, the VIs maintain their projects and namespacing, so this benefit holds true for deployments as well.
Additionally, someone had mentioned looking into using lvlibs to namespace your VIs for deployment. Two comments:
With TestStand 2010, this is no longer neccessary since the project itself namespaces the VIs
You might also want to look into LabVIEW Packed Project Libraries, which combined several VIs into a single file. Think of it as a DLL specific to LabVIEW that is as easy to call as normal LabVIEW VIs. TestStand 2010 can call VIs that are exposed by PPLs. In addition, the deployment utility can automatically pack your VIs into PPLs for deployment.
Hope this is helpful!
Jervin Justin
NI TestStand Product Manager

Wat is the use of casting in field symbols

wat is the use of casting in field symbols?

When you assign a data object to a field symbol, you can cast to any data type. This means that any area of memory can be viewed as having assumed a given type. You can then address parts of fields symbolically without having to use offset/length addressing.
A cast is performed using the CASTINGaddition of the ASSIGN statement. The CASTINGaddition allows you to assign a data object to a field symbol where the type of the data object is incompatible with that of the field symbol. There are two types of casting: casting with an implicit type declaration and casting with an explicit type declaration.
For details please have a look at below link:
[Casting|http://help.sap.com/saphelp_nw70/helpdata/en/fc/eb3930358411d1829f0000e829fbfe/frameset.htm]
I hope it helps.
Thanks,
Vibha
Please mark all the useful answers

Wat is the advantage of force view?

Similar Messages

Maybe you are looking for