Difference between queries 0PUR_C01_Q0022 and 0BBP_C01_Q020

Hi Experts,
Can anyone help me in bringing out the difference between the query 0PUR_C01_Q0022 and 0BBP_C01_Q020.The description of both says that the query is meant for purchase order without contract,but fetches data from different cubes.so what is the difference between them.
Please dont give me any links in help.sap,I have read enough.
Regards,
Meera

Which data refers to the purchase order an organisation receives
That tends to be for sales - so CRM and R3 SD
and the one which the orgn raises for procurement
thats SRM and R3 MM

Similar Messages

  • What is difference between bex analyser and bex browser

    what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

    hi
    Bex Browser
    The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
    Document types that you can work with in the BEx Browser are:
    · BW workbooks
    · Documents that are stored in the Business Document Service (BDS)
    · Links (references to file system, shortcuts)
    · Links to internet sites (URLs)
    · SAP transaction calls.
    · Web applications and Web templates
    · Crystal Reports
    Bex Analyser
    The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
    Features
    You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
    Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
    You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
    Overview of the Functional Area of the BEx Analyzer:
    ·        BEx toolbar
    You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
    ·        Evaluating Query Data
    The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
    Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
    ·        Queries in Workbooks
    Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
    When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
    You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
    ·        Precalculating workbooks
    You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
    Activities
    To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
    You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
    Hope this will solve your issu
    nagarjuna

  • Difference between ISU ABAP and normal ABAP

    Hi ,
    Can anyone tell me what is the difference between ISU ABAP and normal ABAP..Is there any difference..if So..what is the difference...also it will be veryuseful if any one has document regarding ISU ABAP..
    Thanks & Regards.
    Srini.

    Hi,
    From technical point of view, there is no difference, Instead of using R/3 tables you will be using IS-U tables in you select queries etc...
    Functionally there are differnce in ISU and R/3 (SD/MM/PM/FI etc..)
    Regards
    Shiva

  • Difference between capacity formulae and scheduling formulae in workcenter

    Hi experts please give me the solution for my queries
    1. What are  the  capacity formulae and scheduling formulae in workcenter, give me examples, What is the difference between capacity formulae and scheduling formulae in workcenter , how these  are used  in workcenter.
    2. what is group and group counter in routing  , how these are used in routing , please explain.
    3. what is the difference between PRTs created with MM01 AND CF01
    4. what is alternative group and order catagery
    5. what is system status , user status and authorisation matrix

    >
    hemamaheswararao wrote:
    > Hi experts please give me the solution for my queries
    > 1. What are  the  capacity formulae and scheduling formulae in workcenter, give me examples, What is the difference between capacity formulae and scheduling formulae in workcenter , how these  are used  in workcenter.
    > 2. what is group and group counter in routing  , how these are used in routing , please explain.
    > 3. what is the difference between PRTs created with MM01 AND CF01
    > 4. what is alternative group and order catagery
    > 5. what is system status , user status and authorisation matrix
    Dear Hemamashewararao,
    Welcome to SDN !
    As per rules you need to raise only one query as per one thread
    Coming to your first query
    As per business requirement formula will be defined
    The most important difference between Capacity formula and scheduling formula
    In SPRO
    for scheduling formula tick mark will be marked for scheduling where as for capacity option  tick mark will not ticked
    For capacity formula tick mark will be marked for option capacity where as for scheduling option tick mark will not ticked
    Currently i am not in front of SAP so i couldn't give you path
    Good Luck !!!
    Regards
    Madhu

  • Difference Between Auto Lockbox and Auto Receipts......

    Hello All,
    Please expain me, What is the Difference Between Auto Lockbox and Auto Receipts?
    Regards,
    Muthu

    We would appreciate if you can add apps version ? and module name before posting in forum.
    Please check below links for you queries:
    Auto lockbox
    http://docs.oracle.com/cd/A60725_05/html/comnls/us/ar/lokbox.htm
    automatic receipts
    http://docs.oracle.com/cd/A60725_05/html/comnls/us/ar/autorc04.htm
    thanks

  • Difference Between SDM Deployment and JSPM

    Hello All,
    Can anybody tell me the difference between SDM Deployment and JSPM.
    please guide me in brief or guide any URL
    Thanks & Regards
    Shishir

    Shishir,
    Do refer the following links
    Java Support Package Manager (JSPM) - http://help.sap.com/saphelp_nw04s/helpdata/EN/87/4797422930c56ae10000000a155106/frameset.htm
    Software Deployment Manager (SDM) - http://help.sap.com/saphelp_nw04/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
    The first page of the links itself describes the purpose of the tools. Also, do use the search features of the forum and search on help.sap.com. Most of the queries are already asked or present in the help documentation.
    Thanks,
    GLM

  • Difference between sap query and sap ad hoc query

    Hello Experts-
    Is there any difference between sap query and sap ad hoc query. If yes, I will appreciate if you can provide some input.
    Thanks,

    Hi,
    SAP Query
    Purpose
    The SAP Query application is used to create reports not already contained in the default. It has been designed for users with little or no knowledge of the SAP programming language ABAP.
    SAP Query offers users a broad range of ways to define reports and create different types of reports such as basic lists, statistics, and ranked lists.
    Features
    The SAP Query comprises five components: Queries, InfoSet Query, InfoSets, User Groups and Translation/Query.
    Classic reporting- the creation of lists, statistics and ranked lists- are covered by the InfoSet Query and Queries components. Other components’ range of functions cover the maintenance of InfoSets, the administration of user groups and also the translation of texts created in the SAP Query.
    All data required by a user for a report can be read from various tables.
    To define a report, you first have to enter individual texts, such as titles, and select the fields and options which determine the report layout. In the WYSIWYG mode, you can edit the lists using Drag & Drop and various toolbars.
    AD Hoc Query
    Definition
    A Web item that enables you to create and change queries in a Web application on an ad-hoc basis.
    Use
    You can use the  Ad-hoc Query Designer Web item in the Web Application Designer to structure Web applications in which you create or change queries. The Web item is as a tool for designing ad-hoc queries in a Web environment.
    In particular it enables you to:
    ·        Create queries by assigning characteristics from an InfoProvider to rows, columns, filters, and free characteristics, and including key figures from the InfoProvider in the key figure structure of the query.
    ·        Restrict or filter key figures and characteristics
    ·        Use predefined key figure structures and restricted or calculated key figures in the query
    ·        Set or change query properties and key figure/characteristic properties in the query
    ·        Create or change conditions and exceptions
    When compared with the BEx Query Designer, the Ad-hoc Query Designer Web item has the following restrictions when creating or changing queries:
    ·        You cannot integrate variables into the query directly.
    However, you can use variables in reusable structures, or restricted or calculate key figures, which are used in the Ad-hoc Query Designer
    ·        The query can contain only one structure. This structure has to be the key figure structure and be in the rows or columns of the query.
    -        You cannot use key figures or key figure structures in the filter.
    -        You cannot define exception cells, since this requires two structures.
    You cannot create the following objects using the Ad-hoc Query Designer Web item:
    -         Reusable structures
    -         Reusable restricted key figures
    -         Reusable calculated key figures
    -        Local calculated key figures
    You can create local, restricted key figures using the Ad-hoc Query Designer Web item.
    You can edit existing queries in the Ad-hoc Query Designer Web item, if the queries adhere to the restrictions laid out above The Ad-hoc Query Designer checks these requirements when loading a query. If the query is too complex, the query can be loaded into the Ad-hoc Query Designer but you cannot change it there. You then receive the appropriate message. You can still check and execute the query.
    "Ad Hoc" is a Latin phrase which means "for this purpose" and in today's parlance generally means "on the fly," or "spontaneously."
    An ad hoc query is a query that is run at the spur of the moment, and generally is never saved to run again. These queries are run using a SQL statement created by a tool or an administrator. So therefore, such a query is one that might suit a situation which is only there for the moment and later on will become irrelevant.
    As queries become more complex, it can be difficult to write them correctly ad-hoc. To help with this, one can instead write the knowledge needed for queries as business rules in English, and then use a system called "Internet Business Logic" to automatically generate and run the SQL queries. One can then get explanations of the results, in English, at the business level.
    Check these links....
    http://help.sap.com/saphelp_nw04/helpdata/en/1f/03223c5f00612be10000000a11402f/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bf2f79-021d-2a10-5082-dadc79aaa92c
    http://www50.sap.com/businessmaps/27FEEF3A12444F89A8524CCACAF4F5BF.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/15/00a042b443c56ae10000000a155106/content.htm
    Reward points if useful....
    Regards
    AK

  • Difference between 'Always Refresh' and 'Disable Cache Hits'

    We are using clustered application servers with its own cache. We are not doing any cache synchronization. So, for selective objects we should ensure that cache is not returning stale objects.
    I see two options in MWB for refreshing and disabling the cache. Can somebody explain the difference between these two and recommend what I should do to address my problem.
    Thanks in advance.

    These are similar and often used together settings:
    'Disable Cache Hits'
    Is used by TopLink when a ReadObjectQuery is executed with only the PK fields. By default TopLink will short-circuit going to the database and try to find the object in the cache first. This includes 1:1 mapping queries. Turning this on will cause TopLink to go to the database instead of the cache in these cases.
    'Always Refresh'
    Is used to tell TopLink how to handle the results returned from a query against the database. By default TopLink will trust the cached version of any instances already cached. When this is enabled, or the refreshIdentityMapResult is turned on for a specific query the results of the query are used to refresh the values of the cached version.
    The trick with always-refresh is that it does not force all queries to go to the database. It simply forces all returned rows to refresh cached instances.
    These are often selected by customers who never want to trust a cached instance. They are typically used together to get that effect. This configuration will get minimal performance gain from the cache but still require the cache for object-identity (avoid duplicate instances).
    Be careful though because these will have the effect for EVERY query and mapping traversal. I typically prefer to manually turn this on for my specific queries where I need to get the latest version from the database versus turning it on for all queries.
    On the query the methods you will be interested in are:
    query.refreshIdentityMapResult()
    This will force the query to the database and have the results refresh the cached instance if it already exists.
    One setting that is of definite interest is
    descriptor.onlyRefreshIfNewerVersion();
    This must be used in conjunction with the above query refresh and optimistic locking but it will avoid additional unecessary steps if the row has not changed since the cached version was read.
    Doug

  • Difference Between data target and infoprovider

    Hi Experts,
    I am new to BW
    What is the difference between data target and  infoprovider
    Thanks and Regards,
    saveen

    Hi Saveen,
    InfoProvider is an object on which BEx queries are created. It provides information (data) to the queries when they are executed. InfoProviders may contain data (like cube) or may not contain data (like multiproivder and InfoSet).
    Data Target is an object to which you will load the data, like cube, ODS or InfoObject. But it is not necessary that each data target is an InfoProvider...like you may have ODS objects that are not enabled for reporting, but you are loading data to them for staging purpose.
    Hope this helps...

  • Difference between personal folder and personal category

    Hi All,
    I am new to this site, I want to post my query. Is this a right place to post my queries? If it is wrong please guide me, where to post my query related to CMC. 
    My question is, What is the difference between personal folder and personal category in central management console (CMC)?
    Thanks and regards,

    HI
    Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.
    Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.
    Item category determination enables, the system proposes the corresponding item category for sales document type through item category group. t-code: VOV4
    Fields in the item category determination:
    Sales document type, item category group, item usage, and higher-level item category
    Default item category, manual item category
    http://help.sap.com/saphelp_47x200/helpdata/en/43/3bcfea0bff11d2956700a0c9306667/frameset.htm
    refer below for further details
    Item category is for a particu;lar sales order item and it has integration with sales document type and material master.
    In material master ,you must have seen the item category grp in basic data and sales area data.
    That means your item category is assigned to the combination of sales document type and item category grp in the configuration.
    Whenever you will create an order for a particular type and you will put your material then your item category will be determined automatically.
    Configuration is done by spro---sd -sales-sales document item----assign item category
    Message was edited by:
            SHESAGIRI GEDILA

  • Difference between SPML1.0 and SPML2.0

    Can anyone tell the difference between SPML1.0 and SPML2.0?
    regards
    ashok

    SPML 1.0
    - not very interoperable between vendors
    - the spec was not very comprehensive, which led to a lot of ExtendedRequests
    - each vendor implemented their own "operational attributes" for each request
    SPML 2.0
    - capabilities below
    - targets
    - profiles as "open content"
    SPML 2.0 Capabilities
    Core - add,lookup,modify,delete,listTargets (SPML 1.0)
    Async - send request to process asynchronously
    Batch - combine individual requests into one Batch
    Bulk - modify or delete object matching a search
    Password - set,reset,validate,expire
    Reference - reference for other Provisioning Service Objets
    Search - queries with Iterators
    Suspend - enable,disable,Provisioning Service Objects(Users)
    Updates - find the objects that have been updated
    Go to http://www.openspml.org for more info

  • Cumulative values: difference between 3.5 and 7.0

    Hi everybody,
    I use queries which display an Amount on month.
    JAN FEB MAR APR
    A1  A2  A3  A4
    I modify the Key Figure property to have cumulated values
    JAN FEB   MAR      APR
    A1  A1A2 A1A2A3 A1A2A3A4
    In Bex 7.0, all is right i have my cumulated values
    In Bex 3.5, it doesn't work ...
    i have the following result:
    JAN FEB MAR APR
    1   3   6   10   ...
    as if i had:
    JAN=>Amount=1   JAN-> 1
    FEB=>Amount=2   FEB-> 1+2 =3
    MAR=>Amount=3   MAR-> 123 = 6
    Why this difference between 3.5 and 7 ?
    I  would like the right result in 3.5,
    How do i proceed ?
    Thanks for your help!
    Rodolphe.

    Appararently,
    On Bex 3.5 ...
    I remplace for my KeyFigure:
    Calculate Single Values As ...
    "Counting All values" by "Nothing"
    and option cumulated activated.
    and it does work !!
    Rodolphe.

  • Differences between (response.sendRedirect and Requestdispatcher.forward)

    Hi All,
    I have 3 queries
    *1> I wanted to know the "Differences" between*
    response.sendRedirect and Requestdispatcher.forward
    *2> when do we Opt for response.sendRedirect?*
    *3> when do we Opt for Requestdispatcher.forward?*
    Thanks,
    Deepak AL

    The fundamental difference is that sendRedirect is a client based direction, while forward is a server based one.
    SendRedirect forces the client to make a new request. In effect you are telling the client browser "What you are looking for is over there"
    RequestDispatcher forward, is purely an internal server transition. The client knows nothing about the forward happening.
    Example
    Lets say you request the page www.myserver.com/myPage.jsp
    Example A: Redirect
    We send a redirect to www.myserver.com/thatPageOverThere.jsp
    The browser receives this message, and its address url changes to www.myserver.com/thatPageOverThere.jsp, and it sends a new request over there.
    Note that it is a completely new request, so any parameters that were sent with the old request are irrelevant. If you want to send them again you have to put them into the sendRedirect url.
    You can also send a redirect to www.myOtherServer.com/thatPageOnACompletelyDifferentServer.jsp
    Example B: Forward to thatPageOverThere.jsp
    We obtain a request dispatcher to "thatPageOverThere.jsp" and forward to that resource.
    The server instead of running myPage.jsp now executes and returns thatPageOverThere.jsp
    The client browser knows nothing of this. As far as it knows it asked for myPage.jsp, and it is getting that response back.
    So if you forward to something like "my/page/inASubFolder.jsp" you have to be very careful with relative links on the page.
    The browser requested myPage.jsp, so it will resolve relative links from that Url.
    When to use one or the other?
    Redirect would need to be used when the resource is on another server.
    Another common usage is the "Post-Redirect-Get" pattern. (you might want to look that up)
    Hope this helps you understand a little.
    cheers,
    evnafets

  • What is difference between sy-tabix and sy-index.

    SAP Seniors,
    Can you please let me know what is difference between sy-index and sy-tabix.
    I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
    Thank you
    Anitha.

    HI,
        Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
    SY-TABIX
    Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
    APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
    COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
    LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
    READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
    SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
    SY-INDEX
    In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
    Hope this helps.
    Thank you,
    Pavan.

  • Difference between sy-tabix and sy-index?

    tell me about sy-tabix and sy-index?what is the difference between sy-tabix and sy-index?
    Moderator Message: Please search before posting. Read the [Forum Rules Of Engagement |https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further details.
    Edited by: Suhas Saha on Jun 18, 2011 5:33 PM

    HI,
        Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
    SY-TABIX
    Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
    APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
    COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
    LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
    READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
    SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
    SY-INDEX
    In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
    Hope this helps.
    Thank you,
    Pavan.

Maybe you are looking for