Diff between Project version and selection version

Hi All
  what is the functions of the project version and selection version and difference between the same.
Thanks
S.Murali

Hi,
Refer below sap help link for function and use of project version & selection version.
project version
http://help.sap.com/erp2005_ehp_04/helpdata/EN/d8/1fe8344d1d166be10000009b38f83b/frameset.htm
selection version
http://help.sap.com/saphelp_erp60_sp/helpdata/en/ee/41f41846ee11d189470000e829fbbd/content.htm
Regards,
Sandeep
Edited by: Sandeep Theurkar on May 23, 2009 1:29 PM

Similar Messages

  • Diff between Project Landscape and System landscape

    Hai Gurus
    Explain the thread
    Thanks & Regards
    Srikanth

    http://help.sap.com/saphelp_sm32/helpdata/en/62/afcc3a9e8d6526e10000000a11402f/content.htm
    SAP LANDSCAPE:
    Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.
    DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
    QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.
    PROD may have something like a 200 Production.
    These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
    Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage).
    As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
    You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
    But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV).
    The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
    The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
    In summary:
    Landscape : is the arrangement for the servers
    IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
    DEVELOPMENT ---> QUALITY -
    > PRODUCTION
    DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
    QUALITY : is where the core team members and other members test the customization.
    PRODUCTION : is where the live data of the company is recorded.
    A request will flow from Dev->Qual->Prod and not backwards.
    1. Sandbox server:
    In the initial stages of any implementation project, You are given
    a sandbox server where you do all the configuration/customization as per the companies business process.
    2. Development Server:
    Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
    3. Production Server:
    This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.
    These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
    Presentaion Server- Where SAP GUI have.
    Application Server - Where SAP Installed.
    Database Server - Where Database installed.
    What is the meaning of "R" in R/3 systems?
    R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has.
    R/3 means three layers are installed in Different system/server and they are connected with each other.
    1)Presentation
    2)Application.
    3)Data base server.
    Reward if useful

  • What is difference between Oracle version  and DB version.

    What is the difference between Oracle version and DB Version?
    How we came to know about the installed version through SQL query.

    SQL> select * from v$version;
    BANNER
    Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
    PL/SQL Release 8.1.7.0.0 - Production
    CORE 8.1.7.0.0 Production
    TNS for Linux: Version 8.1.7.0.0 - Development
    NLSRTL Version 3.4.1.0.0 - Production
    SQL>
    Joel P�rez

  • Currently running Adobe XI Standard, i have a PDF that i Save As excel however on my computer it converts it differently than my coworkers computer who has the same Adobe version and same version of Excel 2010. Is something different selected on mine than

    Currently running Adobe XI Standard, i have a PDF that i Save As excel however on my computer it converts it differently than my coworkers computer who has the same Adobe version and same version of Excel 2010. Is something different selected on mine than his? How can i troubleshoot?
    Can provide more information if needed...

    Hello nmohamm,
    To examine the conversion settings in Acrobat, do the following:
    1. Select Edit > Preferences
    2. In the preferences dialog, select the "Convert From PDF" category.
    3. In the "Converting From PDF" list, select "Excel workbook".
    4. Click the "Edit Settings" button to view your conversion settings.
    Regards,
    Charlene

  • What difference on ABAP language between 2004 version and before version

    Hi everyone,
    Does there exist difference about ABAP language between 2004 version and before version? If it does, what's that? For example, what's new keywords? Which old key words can't be applied on 2004 platform any more?
    Any suggestion is highly appreciated.
    Best Regards,
    Julian

    hi
    good
    to get all these details plz visit the SAP site where you ll get the release notes related to all the concepts.
    Thanks
    mrutyun^

  • Difference between UCOS restricted version and unrestricted version

    Hi to all,
    somebody knows which is the difference between restricted version and unrestricted version??
    Which are the main differences??
    Thanks
    David

    Hi.
    Basically restricted version has encryption enabled and unrestricted not.
    You may give a look to this thread.
    https://supportforums.cisco.com/discussion/11409366/restricted-version-and-unrestricted-version-ccm-comparison
    HTH
    Regards
    Carlo

  • Difference between Planning Version and Simulation Version

    Hi friends,
    What is the difference between Planning Version and Simulation Version?
    Thanks,
    Debi

    Debi
    There are a lot of threads in this forum that give detailed info about version concept. Also you can refer to help.sap.
    Anyways , planning version is the version against which your live cache data is stored.  The data against this version is the one that the planners and buyers are going to refer to or use to make their planning and buying decisions. Data against the planning version is nothing but data relevant to the business .
    There may be instances where you would like to simulate some scenario. If you want to do trial and error analysis and at the same time if you do not want to impact the actual business data , then you create simulation versions and simulate your scenario.
    For example your actual sales orders received for the month of March may be 100 CS. This is the actual number that will be stored against your planning version. Lets say the demand planner wants to find out what will be the impact if there is a sudden bulk demand from a new customer for 500 CS - that is if he wants to do a what - if analysis then he can create a simulation version and try to check the impact .
    Thanks
    Aparna

  • Screen diff. between 4.7 and Ecc 6.0

    Hi All,
    Can you please provide the list of Transaction Code, where the Screens are diff.between 4.7 and ECC 6.0 in SD.
    Means as per user View, they can find the diff. of the field for the screen. like Suppose in VA01 in ECC 6.0 might be add few more fields or modify the fields...compare to 4.7.
    We need as per the Client requests..
    regards
    Pinal

    There are so many differences between the version in different objects
    I will explain in two or more objects the difference
    1 in the customer master in 4.6 version there is no partner function tab in the customer in xd01 t-code
    and also there is no CIN tab in that version
    but it is there in the 4.7 EE version
    This is the major change from the 4.6cc to 4.7EE
    2. in 4.7EE there is some settings that are related for CIN
    which cannot be done in 4.7EE that means they need some patches for doing the configuration setting for the CIN
    But we can do the same in the 6.0 version
    These are the some of the settings that are differed in the two versions and in that two objects
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prospective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences please refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    For Functionality Differences please refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
    http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
    Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
    Re: SAP version differences 4.5b, 4.6c and ECC6.0
    You can find the difference in release notes of each SAP version.
    Here are the links.
    http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
    http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prospective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences please refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    rewards if it helps
    siva

  • Tool versions and Application versions

    hi,
    i have a doubt in basic concept of peopleosft regarding the realtion between tool versions and application versions
    I have two systems..
    system1 : Application version 8.8 and tool version 8.49
    system 2: Application version 8.9 and tool version 8.46
    Now, the integration broker and webservices are completley different in these two tool versions...
    from whatever i know..when tool version is upgraded..navigations in application remain same but the way the process is done in background differ...
    so if we have webservices in application 8.8 and tools 8.46...the navigations are different and when we upgrade to 8.49 the whole concept of webservices change...so the navigations invariably change..how can it be possible..?
    Can someone explain me this or give a link to a doc for reference..
    Thanks in advance,
    Karthik
    Edited by: karthik tulasi on May 18, 2009 12:14 PM

    Well, you seems confuse, or I was not clear enough.
    Maybe I'm still not getting your question as it should, so you could try to rephrase it again.
    What's your concern exactly ?
    A new try on my side:
    The menu your are talking about is the Peopletools menu, so application does not interact with it.
    The only link between application and Peopletools are some calls. The application does NOT care about the Peopletools menu.
    The application/peopletools capabilities are embeded in the Peopletools which are ready or not ready to receive calls from differents Applications versions.
    Once more, menus are only frontend user GUI, but internally, this is an other stuff I tried to explain above.
    Basically, for the application point of view, Peopletools version are not know. This is the other way around, Peopletools are willing to receive application calls.
    Nicolas.

  • Diff between 4.7e and ecc 6.0

    hi abapers !
    can any tell me the diff, between 4.7e and ecc 6.0 ?
    cheers.
    rajesh.

    Hi.
    First of all I would like to ask you to have a look into our rules of engagement. One of the really important rules for our forums is that you should try to solve your question yourself first. One very usefull tool are search engines. Perhaps you heard about google or some other internet search. And there is a search function in the SDN too. Please use it before asking any question.
    Then I would like to ask you to give as much information as available regarding your question. My first intention was to answer 1.3. As Eric did that before me I refrain from this. But please understand: No one here in the forums knows in which kind of diff are you interested. And don't tell me you want to know all differences. I have seen such questions but then the only correct answer would be a source code diff. And that would be a little bit more than we allow for postings.
    And then: This is an ABAP forum. If you are asking which changes have been done to the programming language ABAP between this versions then you are in the right forum. If not -> ask somewhere else.
    Future postings as unspecific as this one might get locked or deleted without prior notice.
    Best regards,
    Jan Stallkamp

  • Search Example Code inside for Versioned and non-Versioned Documents

    These may be of use to someone...
    File names:
    AttributeSearch.java
    AttributeContentSearch.java
    The AttributeSearch application will search for documents (both versioned and non-versioned) with a file name containing "txt", residing in the user "system"'s home directory.
    The AttributeContentSearch application will search for documents (both versioned and non-versioned) with a file name containing "txt", and document content containing the word "hello", residing in the user "system"'s home directory.

    import oracle.ifs.beans.LibraryService;
    import oracle.ifs.beans.LibrarySession;
    import oracle.ifs.common.CleartextCredential;
    import oracle.ifs.common.ConnectOptions;
    import oracle.ifs.common.IfsException;
    import java.util.Locale;
    import oracle.ifs.beans.DirectoryUser;
    import oracle.ifs.beans.PrimaryUserProfile;
    import oracle.ifs.beans.PublicObject;
    import oracle.ifs.beans.Document;
    import oracle.ifs.beans.Folder;
    import oracle.ifs.beans.ContentObject;
    import oracle.ifs.beans.Search;
    // SEARCH RESULT
    import oracle.ifs.beans.SearchResultObject;
    // CONTENT + ATTRIBUTE SEARCH
    import oracle.ifs.search.ContextSearchSpecification;
    // SELECT, FROM
    import oracle.ifs.search.SearchClassSpecification;
    // ORDER BY
    import oracle.ifs.search.SearchSortSpecification;
    // WHERE
    import oracle.ifs.search.SearchClause;
    import oracle.ifs.search.SearchQualification;
    import oracle.ifs.search.JoinQualification;
    import oracle.ifs.search.FolderRestrictQualification;
    import oracle.ifs.search.AttributeQualification;
    import oracle.ifs.search.ContextQualification;
    public class AttributeContentSearch
    public static void main(String args[])
    try {
    LibraryService ifsService = new LibraryService();
    System.out.println("Oracle iFS Version " + ifsService.getVersionString());
    CleartextCredential credentials = new CleartextCredential("system","manager");
    ConnectOptions options = new ConnectOptions();
    options.setLocale(Locale.getDefault());
    options.setServiceName("ServerManager");
    options.setServicePassword("ifssys");
    LibrarySession ifsSession = ifsService.connect(credentials,options);
    DirectoryUser thisUser = ifsSession.getUser();
    System.out.println("Connected as \"" + thisUser.getDistinguishedName() + (thisUser.isAdminEnabled() ? "\" (admin enabled)" : "\""));
    PrimaryUserProfile userProfile = thisUser.getPrimaryUserProfile();
    SearchResultObject[] sro = runSearch (ifsSession,"hello");
    if (sro != null)
    for (int i = 0; i < sro.length; i++)
    System.out.print (((PublicObject)sro.getLibraryObject()).getName());
    System.out.println (" (" + ((PublicObject)sro[i].getLibraryObject()).getId() + ")");
    } catch (IfsException e)
    public static SearchResultObject [] runSearch( LibrarySession ifsSession, String searchCriteria) throws IfsException
    ContextSearchSpecification ss = null;
    SearchClassSpecification scs = new SearchClassSpecification();
    SearchSortSpecification sss = new SearchSortSpecification();
    SearchQualification sc = null;
    ss = new ContextSearchSpecification();
    ss.setContextClassname(ContentObject.CLASS_NAME);
    scs.addSearchClass( PublicObject.CLASS_NAME );
    scs.addSearchClass( Document.CLASS_NAME );
    scs.addSearchClass( ContentObject.CLASS_NAME );
    scs.addResultClass( Document.CLASS_NAME );
    sss.add( Document.CLASS_NAME, "NAME", true );
    sc = buildSearchClause( ifsSession, searchCriteria);
    ss.setSearchClassSpecification( scs );
    ss.setSearchQualification( sc );
    ss.setSearchSortSpecification( sss );
    Search s = new Search( ifsSession, ss );
    s.open();
    SearchResultObject [] sro = s.getItems();
    s.close();
    return sro;
    public static SearchQualification buildSearchClause( LibrarySession ifsSession, String searchCriteria ) throws IfsException
    Folder f = ifsSession.getUser().getPrimaryUserProfile().getHomeFolder();
    FolderRestrictQualification frq = new FolderRestrictQualification();
    frq.setStartFolder( f );
    frq.setSearchClassname(PublicObject.CLASS_NAME);
    AttributeQualification aq = new AttributeQualification();
    aq.setAttribute(Document.CLASS_NAME, PublicObject.NAME_ATTRIBUTE);
    aq.setOperatorType(AttributeQualification.LIKE);
    aq.setValue("%txt%");
    ContextQualification cq = new ContextQualification();
    cq.setQuery(searchCriteria);
    cq.setName("Test0");
    JoinQualification jq1 = new JoinQualification();
    jq1.setLeftAttribute ( Document.CLASS_NAME, Document.CONTENTOBJECT_ATTRIBUTE );
    jq1.setRightAttribute( ContentObject.CLASS_NAME, null);
    JoinQualification jq = new JoinQualificatio n();
    jq.setLeftAttribute ( PublicObject.CLASS_NAME, PublicObject.RESOLVEDPUBLICOBJECT_ATTRIBUTE );
    jq.setRightAttribute( Document.CLASS_NAME, null);
    SearchClause sc;
    sc = new SearchClause(jq, jq1, SearchClause.AND);
    sc = new SearchClause(sc, cq, SearchClause.AND);
    sc = new SearchClause(sc, frq, SearchClause.AND);
    sc = new SearchClause(sc, aq, SearchClause.AND);
    return sc;
    null

  • Diff between interactive report and interactive alv

    Diff between interactive report and interactive alv? Suppose I have been given certain program then how I will diffrentiate that this prog should be done in interactive alv or interactive report.

    hi
    both are used for same purpose
    interactive report means an output list which displays basic details & allow user to interact, so that a new list is populated based on user-selection. With interactive list, the user can actively control data retrieval and display during the session.
    I suggest to use ALV.by using ALV we can display in Grid as well as list format.
    Output format will be good . Sorting,Filtering facilities are provided by itself.We can have column headings also.
    if helpful reward points

  • What is the exact diff between  At New  and On Chnage

    hello all
    what is the exact diff between  At New  and On Chnage in control breaks statements. and when  shall we go for At new & when shall we go for On change on events.
    Plz tell with with some code.

    Hi ,
    Using at new
    Each time the value of c changes, the lines of code between at new and endat are executed. This block is also executed during the first loop pass or if any fields to the left of c change. Between at and endat, the numeric fields to the right of c are set to zero. The non-numeric fields are filled with asterisks (*). If there are multiple occurrences of at new, they are all executed. at end of behaves in a similar fashion.
    Using the on change of Statement
    Another statement you can use to perform control break processing is on change of. It behaves in a manner similar to at new.
    The following points apply:
    u2022     If the value of any of the variables (v1, v2, and so on) changes from one test to the next, the statements following on change of are executed.
    u2022     If no change is detected and else is specified, the statements following else are executed.
    on change of differs from at new in the following respects:
    u2022     It can be used in any loop construct, not just loop at. For example, it can be used within select and endselect, do and enddo, or while and endwhile, as well as inside get events.
    u2022     A single on change of can be triggered by a change within one or more fields named after of and separated by or. These fields can be elementary fields or field strings. If you are within a loop, these fields do not have to belong to the loop.
    u2022     When used within a loop, a change in a field to the left of the control level does not trigger a control break.
    u2022     When used within a loop, fields to the right still contain their original values; they are not changed to contain zeros or asterisks.
    u2022     You can use else between on change of and endon.
    u2022     You can use it with loop at it where . . ..
    u2022     You can use sum with on change of. It sums all numeric fields except the one(s) named after of.
    u2022     Any values changed within on change of remain changed after endon. The contents of the header line are not restored as they are for at and endat.
    Regards,
    KV

  • Diff between sap query and abap query

    diff between sap query and abap query

    Hi,
    ABAP query is mostly used by functional consultants.
    SAP Query :
    Purpose
    The SAP Query application is used to create lists not already contained in the SAP standard system. 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 reporting programs and create different types of reports such as basic lists, statistics, and ranked lists.
    Features
    SAP Query's range of functions corresponds to the classical reporting functions available in the system. Requirements in this area such as list, statistic, or ranked list creation can be met using queries.
    All the data required by users for their lists can be selected from any SAP table created by the customer.
    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. Then you can edit list display in WYSIWYG mode whenever you want using drag and drop and the other toolbox functions available.
    ABAP Query,:
    As far as I Believe, is the use of select statements in the ABAP Programming. This needs a knowledge of Open SQL commands like Select,UPdtae, Modify etc. This has to be done only by someone who has a little bit of ABAP experience.
    To sum up, SAP queries are readymade programs given by SAP, which the user can use making slight modification like the slection texts, the tables from which the data is to be retrieved and the format in which the data is to be displayed.ABAP queries become imperative when there is no such SAP query existing and also when there is a lot of customizing involved to use a SAP Query directly
    use either SQ02 ans SQ01
    or SQVI tr code
    for more information please go thru this url:
    http://www.thespot4sap.com/Articles/SAP_ABAP_Queries_Create_The_Query.asp
    http://goldenink.com/abap/sap_query.html
    Please check this PDF document (starting page 352) perhaps it will help u.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVQUE/BCSRVQUE.pdf
    check the below link will be helpful for u
    Tutorial on SQVI
    once you create query system generates a report starting with AQZZ/SAPQUERY/ABAGENCY2======= assing this report to tr code for the same
    regards,
    vasavi.
    reward if it is helpful.

  • Diff between ECC5.0 and ECC6.0

    Hi,
    This is Ramakrishna,can any one give proper explanation diff between ECC5.0 and ECC6.0
    Regards
    Ramakrishna

    Hi,
    Refer following link;
    [SAP ERP Solution Browser|http://solutionbrowser.erp.sap.fmpmedia.com/]
    Following are the basic differences as far as MM Module is concerned;
    Pickup list - Batch where-used list display in transaction MB56
    u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
    u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
    u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
    Usability enhancements for transaction MIGO for the posting of goods movements
    u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
    u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
    u2022 User changes the default values in the menu path "Settings -> Default Values."
    u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
    - Goods receipt
    - Goods issue
    - Transfer posting
    - Remove from storage
    u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
    New report : display list of invoice documents (MIR5)
    u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
    u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
    u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
    u2022 In the output list, the report shows both posted and held invoices.
    u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
    Requirement prioritizations in materials management
    u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
    u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
    Mass maintenance of outline agreements
    The following two transactions available:
    u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
    u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
    Commitment plan for purchase contracts
    u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
    u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
    u2022 This commitment plan itself can have any number of items.
    u2022 User can define a value and a validity date for each commitment plan item.
    u2022 This enables user to pre plan different values for different periods of time.
    u2022 The software generates an earmarked fund document for a defined commitment plan item.
    u2022 This earmarked funds document can in turn contain several different items with different account assignments.
    u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
    u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
    u2022 Account assignment to a different account assignment object is then no longer allowed.
    Availability check in "Enjoy purchase order and requisition"
    u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
    u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
    - To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
    - Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
    u2022 Two settings are possible with availability check:
    - Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
    - Delivery proposal - Full confirmation
    External services: putting service items in the purchase order on hold (changed)
    User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
    Customizing transactions OX18 replaced by view
    The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
    Goods receipt: new movement types in inventory management
    The following new movement types are available in inventory management:
    - 107: Goods receipt to valuated goods receipt blocked stock
    - 109: Goods receipt from valuated goods receipt blocked stock
    Prepayment of invoices
    This functionality is characterized as follows:
    u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
    u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
    u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
    u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
    u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
    u2022 When the software posts invoices, it continues to execute the standard checks.
    u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
    u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
    u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
    Purchasing accounting information to the former SAP Business Information Warehouse
    u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
    u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
    Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
    u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
    u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
    u2022 Functionality for report RMMR1MRS is enhanced.
    u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
    u2022 To do so, set the relevant indicator on the initial screen of the report.
    Parking service items
    It is now possible to put service orders without errors or with commitment errors on hold.
    Report MB5B : Stock on Posting Date
    u2022 This Report is available with u201CNon-Hierarchyu201D display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
    u2022 This functionality is not available in Release 4.7.
    Stock Transfer Between Storage Locations
    u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
    u2022 As a result of which user can input issuing storage location with supplying plant.
    u2022 Facility of using different delivery types for different issuing storage locations is available.
    u2022 Shipping Point data can also be determined based on the issuing storage location

Maybe you are looking for