Exact difference between VOimpl and VORowimpl and EO.

Can anybody tell me whats the exact difference between
VOimpl and VORowimpl and EO.
Thanks

Entity Object :BC4J entity objects encapsulate the business rules (validations, actions and so on) associated with a row in a database table, view, synonym or snapshot.
View Object : (ViewImpl)
In the simplest terms, a BC4J view object encapsulates a database query and provides iteration over and access to the view rows in its result set.
View Row : ViewRowImpl :
Represents a single row in a view object.
For more Details see OA Developer Guide.
Thanks

Similar Messages

  • Whatz the exact difference between the glossy display and the ratina display??

    whatz the exact difference between the glossy display and the ratina display??

    Oops I means half billion (5.1 million pixels)

  • Exact Difference between Non Stock NLAG and Non Valuated  UNBW Materia type

    Dear All
    What is the Exact Difference between Non Stock NLAG and Non Valuated  UNBW Materia type?
    I tried creating Purchase Order and found that accouting doc got created at both times and stock was not updated in MMBE for both material types.
    Regards

    Hi,
    non-valuated material (Material Type UNBW):
    This type of material is managed on a quantity basis, but not on a value basis. This makes sense for materials of low value, stocks of which nevertheless have to be monitored (for example, operating manuals).
    Non-stock material (NLAG) (Material Type NLAG):
    Inventory management is not possible for these materials either on a quantity or value basis. For frequently required consumables, the use of this material type nevertheless enables you to store the information required to create
    purchasing documents (such as texts and units of measure).
    When a material is procured directly for consumption, no material master record is necessary. In connection with consumable materials, you can distinguish between the following cases:
    • Consumable material without material master record
    • Consumable material with material master record that is not subject to
    inventory management (on either a quantity or value basis)
    • Consumable material with material master record that is subject to inventory management on a quantity, but not a value, basis
    Regards,
    Pardeep malik

  • Exact difference between tolerance key AN and AP

    HI,
    Can any one tell me exact difference between the tolerance keys AN & AP with examples?
    Thanks& Regards,
    Pushparaj S.

    Hi Swetha,
    So, do you mean that AN & AP are the same as per the functionality wise. but only AP can allow further filter of the items as per the additional setting for item category?
    For example:
    Custo:
    AN: upper limit 100 EUR
    MIRO:
    IR: Item 1: Item category: "L" exceeds 100 EUR
    IR: Item 2: Item category: "Standard" exceeds 100 EUR
    Result:
    In this case system will block both items...
    Custo:
    AP: upper limit 100 EUR
    Item category: "standard"
    MIRO:
    IR: Item 1: Item category: "L" exceeds 100 EUR
    IR: Item 2: Item category: "Standard" exceeds 100 EUR
    Result:
    In this case system will block only item 2...
    Please confirm this...
    Thanks & Regards,
    Pushparaj S.

  • Exact difference between Item category and Account assignment category

    Can anyone plz give the exact difference between account assignment category and Item category
    Thanks inadvance

    Hi,
    Account Assignment Category: Key indicating whether an item is to be assigned to an auxiliary account (such as a cost center). The account assignment category determines which account assignment data (e.g. cost center, account number, etc.) is required for the item.
    Item category: Identifier indicating the characteristics of an item. The item category determines whether the following are necessary or allowed with regard to an item:
    Material number, Additional account assignment, Inventory management in the R/3 System, Goods receipt, Invoice receipt.
    Prase

  • Difference between rew level triggers and statement level triggers

    Hi All
    I would like to know the exact difference between rew level triggers and statement level triggers.Please provide me with an example.
    Thanks
    Anand

    What is difference between row & statement?
    One statement can change many rows.
    Difference determines how many times the trigger fires or under what conditions.

  • Difference between on change of and at end of :

    Hi Can any one explain me what is the exact difference between on change of and at end of .
    I know the basic differences.
    But i would like to know in which case we can use the above two statemetns.
    Suppose :
    Matnr   plant       sloc       movementype      date                          qty
    12       001          002           261                12/11/08                    10
    12      001          002            261               12/11/08                      11
    12      002          003            261               12/11/08                      12
    Here i need to add the quantity based up on the material,
    If the materials is maintained in different plants then it should give the total for for that particular plant.
    Please help me how to build logic to this :
    Regards,
    Vinay.

    ok sure i will give it to u.
    MATNR       PLANT          SLOC            BWART           BUDAT         QTY1           QTY2           QTY3             QTY4            QTY5
    127874     2501     3025     200906     201     0.000     0.000     0.000     0.000     0.000
                         QTY6           QTY7             QTY8             QTY9           QTY10         QTY11            QTY12
         0.000     0.000     0.000     0.000     0.000     0.364     0.000
    127874     2501     3025     200905     201     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     7.000     0.000     0.000
    127874     2501     3025     200905     202     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     1.000     0.000     0.000
    127874     2501     3025     200905     261     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     35.000     0.000     0.000
    127874     2501     3025     200905     551     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     0.000     5.000     0.000     0.000
    Here i need to write the logic for that material usage :
    This material usage will be caliculated based upon the movement types in that particular month :
    The formula is :
    AT END OF BUDAT.
         FINAL_VALUE_WA-KWMENG12 =   ( W_QTY261 -   W_QTY262 ) + ( W_QTY201 - W_QTY202 ) + ( W_QTY551 - W_QTY552 ).
          CLEAR : W_QTY261,W_QTY262,W_QTY201,W_QTY202,W_QTY551,W_QTY552.
        ENDAT.
    Here iam writting the logic as at end of the month iam caliculating.
    But what my question is if we have same material in different plant and the usage is in the same month
    then i think this query is going to fail.
    Edited by: vinay raj on Jul 6, 2009 2:02 PM
    Edited by: vinay raj on Jul 6, 2009 2:03 PM

  • Difference between 4.7 EE and 4.6 C

    hi to all
    Me ravi kumar. pl explain my doubts
    what is exact difference between 4.7 EE and 4.6C?
    What is cut over activities?
    thank u
    with regards
    ravi kumar

    Hi,
    Pl. follow the link,
    http://www.thespot4sap.com/articles/SAP_4point7_Features_Benefits.asp
    Regards,
    Senthilkumar SD

  • What is the exact difference between Purchse order and purchase requisition

    Hi all,
    What is the exact difference between Purchse order and purchase requisition.
    Thx

    Hi,
    <b>Purchase Requisition</b>-> Staff in an orgn places Pur requisition for want of some goods/products - ME51
    Related Table EBAN
    Request for Quotation(RFQ)-> The Purchase dept in the orgn calls/requests for the quotation for the products against which PR was raised. - ME41
    Vendor Evaluation->After receving the RFQ's, after comparison a Vendor is finalised based on the terms and conditions.
    <b>Purchase Order(PO)</b>-> Pur order was issued to that vendor asking him to supply the goods/products -ME21N
    Tables:EKKO,EKPO
    Goods Receipt Note(GRN)->Vendor supplies the material/Products to the orgn-
    MB01
    Goods Issue (GI) -> People receives their respective itesm for which they have placed the Requisitions
    Vendor, Material ,Qty are mandatory for PO.
    Regards,
    Padmam.

  • Exact difference between function and procedure

    exact difference between function and procedure(real time diff.....not like return value, dml....) and function do some work at the same time that work also do procedure..why function

    ranitB wrote:
    1. Function is called Inline a query. A return value is must.
    But, procedure may/may not contain a return value.Not true.
    A function may be called in a query providing it meets certain limitations (no DDL, or transactional statements such as commit/rollback etc.).
    A function does not have to be called from a query, it can be called from other PL/SQL code or from other external applications.
    Regular functions must return a value, though pipelined functions do not...
    SQL> CREATE OR REPLACE TYPE split_tbl IS TABLE OF VARCHAR2(32767);
      2  /
    Type created.
    SQL> CREATE OR REPLACE FUNCTION split (p_list VARCHAR2, p_delim VARCHAR2:=' ') RETURN SPLIT_TBL PIPELINED IS
      2      l_idx    PLS_INTEGER;
      3      l_list   VARCHAR2(32767) := p_list;
      4      l_value  VARCHAR2(32767);
      5    BEGIN
      6      LOOP
      7        l_idx := INSTR(l_list, p_delim);
      8        IF l_idx > 0 THEN
      9          PIPE ROW(SUBSTR(l_list, 1, l_idx-1));
    10          l_list := SUBSTR(l_list, l_idx+LENGTH(p_delim));
    11        ELSE
    12          PIPE ROW(l_list);
    13          EXIT;
    14        END IF;
    15      END LOOP;
    16      RETURN;
    17    END SPLIT;
    18  /
    Function created.
    SQL> SELECT column_value
      2  FROM TABLE(split('FRED,JIM,BOB,TED,MARK',','));
    COLUMN_VALUE
    FRED
    JIM
    BOB
    TED
    MARK... whilst the definition of the function shows a return type, the return statement inside the function simply returns, without a value. That's because the data is passed back through a special "pipeline", and you can write code to show that the data is available to a query as soon as it's piped, and before the function has completed (reached the return statement) if you like.
    A procedure does not return a value (And no an OUT parameter is not a "returned" value, it's a writeable parameter, there's a difference)
    2. There are some limitations in functions which is possbl through procedures.
    Like - Oracle doesn't support DML in functions called in Select queries (using PRAGMA AUTONOMOUS_TRANSACTION will help).Not strictly true. and SQL query is considered to be DML, so a function could perform a query and then be used inside another query...
    SQL> ed
    Wrote file afiedt.buf
      1  create or replace function f_dname(p_deptno in number) return varchar2 is
      2    v_dname varchar2(10);
      3  begin
      4    select dname into v_dname
      5    from   dept
      6    where  deptno = p_deptno;
      7    return v_dname;
      8* end;
    SQL> /
    Function created.
    SQL> ed
    Wrote file afiedt.buf
      1* select empno, ename, f_dname(deptno) as dname from emp
    SQL> /
         EMPNO ENAME      DNAME
          7369 SMITH      RESEARCH
          7499 ALLEN      SALES
          7521 WARD       SALES
          7566 JONES      RESEARCH
          7654 MARTIN     SALES
          7698 BLAKE      SALES
          7782 CLARK      ACCOUNTING
          7788 SCOTT      RESEARCH
          7839 KING       ACCOUNTING
          7844 TURNER     SALES
          7876 ADAMS      RESEARCH
          7900 JAMES      SALES
          7902 FORD       RESEARCH
          7934 MILLER     ACCOUNTING
    14 rows selected.It's been discussed many times on the forum... my favourite here...
    {message:id=1668675}
    Edited by: BluShadow on 17-Sep-2012 09:22

  • Exact  difference between se09 and se10

    Hi all,
    i want to know the exact difference  between se09 and se10  .
    i know
    SE09 is the workbench transport requests transaction - here the developers can track changes to all ABAP workbench objects (dictionary, reports, module pools, etc). This is a developer-specific transaction and mostly all developers have access to this transaction.
    SE10 is the customizing request display transaction - this displays all the customizing requests in the system. Again, this could be restricted to Business analysts if required, since they would be doing most of the customizing changes in the system.
    but i think this is not the correct answer which is  already appear in the thread list
    recently sombady has answer like the one which i have mentioned above but the interviwer said that this is wrong.
    CAN ANYONE TELL ME THE EXACT ANSWER AND HELP ME OUT.
    Regards
    fareed

    Hi Fareed,
      First of all, i would say its a nice obsevation. As soon as i saw your post i started checking both transactions in seperate window and i found something interesting.
    My Observation is as follows:-
    <b>When we create a Transaction, apart from the Transaction Name, Program Name, Screen Number etc., we also can give someting called "AUTHORIZATION FOR CALLED TRANSACTIONS", under the menu: UTILITIES of the window.
    Also we can use TRANSACTION:SE97, Maintain Transaction call Authorization in CALL TRANSACTION. Here we maintain the list of TRANSACTION CALLED for our Calling Transaction.
    Now if you see, this list for Transaction SE09 and SE10, The Authorization for Called Transaction Differs a lot. Hence the difference bettween SE09 and SE10 is mainly the AUTHORIZATION Objects.</b>
    <b>NOTE:</b> This is my own observation, so there are chances of misinterpretation from my side, accounting to the human err. But this is something new to me too.
    Thanks and regards,
    RAVI :).
    PLEASE AWARD POINTS IF YOU FEEL MY SOLUTION TO YOUR QUESTION IS RIGHT $-).

  • 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

  • Exact Difference between Total  Status And QM Status

    Hello All,
    I want to know Exact Difference between Total Status in Monitor And QM Status in Data Target.when these two are going to be changed manually. i am facing a Problem.
    daily delta upload is going on from R3 to BW.Today it has given a problem while loading data. please give me u r ideas on this. how this delta should be Success.By changing which status ( Total, QM status) i need to chage for deleting the failure Request , to load delta again.
    thanks in advance.
    Eswar

    The global monitor queue time can be set in transaction RSCUSTV2. This is the time that the system allows to elapse before it sets a request to 'Terminated'. If the time of the last received message that logged a processing step on the monitor for this request has taken longer than the monitor queue time, the traffic light in the monitor is set to red. 
    If the monitor traffic light was set to red due to the queue time, this does not necessarily mean that the request can no longer be successful. 
    If the data is very delayed by the time it reaches BW (because the source system needs a long time for the extraction or because the link between the source system and BW was interrupted) or if the processing in BW needs a very long time in which the processing step does not log any messages on the monitor, the monitor traffic light becomes red and jumps back to yellow as soon as a new log for this request reaches the monitor. If you manually set the QM status in the monitor, this also does NOT prevent the updating of data for this request in BW! However, then the request can no longer turn green, since the manually set QM status always overrides the technical status of the monitor.
    Bye,
    Roberto

  • Exact difference between System status and the user status

    Hi,
    Please tell me the exact difference between System status and the user status .
    how we customize the both in the system
    Thanks & Regards
    Prajith P
    Moderation: Locked. Please, try to find an answer first. See rules of engagement
    Edited by: Joaquin Fornas on Feb 23, 2012 11:14 AM

    Hi,
    As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
    In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
    System statuses will be updated automatically based on business transactions which will be done on SAP.
    For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
    If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
    These user status as per the name, should be updated by the user manually.
    Regards,
    Maheswaran.

  • What's the exact difference between "Query Def. Filter Value Selection" and

    Hi Gurus,
    what's the exact difference between "Query Def. Filter Value Selection" and "Query Execution Filter Val. Selectn" in info-object's "Business explorer" tab?
    I found out that if my info-object A has a input-ready variable in a query,after the query running,in  the selection screen,my info-object A's F4 value is follow the setting of "Query Execution Filter Val. Selectn",as the setting of "Query Def. Filter Value Selection" I tried every diff setting, it won't effect my query anyway.
    so:
    1.what's the exact difference between "Query Def. Filter Value Selection" and "Query Execution Filter Val. Selectn" in info-object's "Business explorer" tab?
    2.how they effect query's presentation?
    I searched forum,didn't find the answer what I want.
    Thanks everyone.

    Hi Denny,
    I will try to explain it again.
    Query Def. Filter Value Selection : Let say the value is set to "Only Values in Infoprovider"
    Lets take an example infoobject - 0MATERIAL (Material)
    Total material records in material Master = 1000 (master Data table /BI0/PMATERIAL)
    You create a query on top of an Infoprovider using Material.
    Total unique materials in Infoprovider= 500.
    Now when you are in design mode in Query Designer, and you try to restrict Material by few materials (for e.g. 1, 2, and 3), for this you right click on material and select Restrict, the pop-up opens with list of materials, this list is all those 500 materials which are in the infoprovider, because the setting is  "Only Values in Infoprovider". Which means then when you are trying to restrict a characterstic in query definition the list of values displayed for restricition is derived from Infoprovider.
    Query Execution Filter Value Selection  - I think you already know what it is , its the read mode for F4 help selection.
    I hope this helps.
    Thanks
    CK

Maybe you are looking for