Difference in 4.7 EE & ECC6.0

Question

Hi Experts!!!
Can any body help it out waht are the differences in 4.7EE and ECC 6.0  in table format.  Tommorrow i am going to present it in my company..
S.No      MODULE         PROCESS         DESCRIPTION        Comparision to present version.     T.CODE     Status
Thanks a lot for helping .
regards
suneel

Answer 1

hi
Some of the difference in MM
Archiving
The most frequently used archiving objects have been reworked so that they now correspond to a uniform standard. This has two main advantages: The archiving objects can be used uniformly in archiving projects and accessing archived data across different applications has been improved. The changes concern the following areas:
1. Selection screen
In the selection screen of the write program, you can specify under processing options whether the program should be performed in the test or production mode. If you select the detail log checkbox, a uniform log detailing which objects were processed is delivered in each write program. For certain archiving objects, such detail logs can also be delivered in other program, such as in the deletion or preparatory program. For more information, see the F1 help documentation.
2. Progress confirmation
A progress message appears every 30 minutes in the job log for programs executed in the background. For program executed in dialog mode, the progress message appears in the status line every 10 seconds.
3. Log
With each archiving run, the following information is written to the log (spool list):
•     Number of table entries, processed archiving objects, archiving files, and so on.
•     Processed business objects (such as orders or billing documents)
As described above, you can choose in the selection screen of the write program whether a detail log listing the individual business objects processed is issued instead of the usual compact log.
4. Interrupting the archiving run
To enable you to react appropriately to a given time frame or restricted disk place during archiving, the write phase of an archiving run can be interrupted and then continued at a later point. This function forms part of archive administration (transaction SARA).
5. Customizing specific to archiving objects
The technical settings in customizing specific to archiving objects have been examined for the processed archiving objects and modified where necessary. You can implement the new parameters by activating the corresponding BC set (transaction SCPR20). The BC set is called ARCH_<archiving object>. For example, the BC set for archiving object SD_VBAK is ARCH_SD_VBAK. We recommend that you implement the new parameters.
6. Network graphic
The network graphic for the individual archiving objects has been examined and any necessary adjustments have been made
7. Enhanced access of the archive
Archive access via the archive information system and the document relationship browser have been enhanced and improved. For some archiving objects, read access from certain application transactions to archived data is now available.
The following is true for process and production orders:
•     With the exception of interrupting the archiving run, these archiving objects were not changed for SAP R/3 Enterprise 4.70 software. See SAP Note 713545.
•     No progress confirmation messages are displayed
•     Customizing specific to archiving objects was not changed
•     In general, no other steps are required for the upgrade. In particular, you do not have to create any new variants for write and deletion programs.
For more information on the changes implemented, see SAP note 577847. Special features for upgrade from SAP R/3 Enterprise 4.70
The affected archiving objects were in fact already reworked for SAP R/3 Enterprise 4.70 (see SAP Note 577847). For the implemented changes to take effect, however, they had to be activated explicitly. If you have already activated them for Release 4.70, no further steps are required for this upgrade.
Effects on system administration
As new write and deletion programs have been assigned to the archiving objects, it is generally necessary to check the variants for scheduling the write and deletion programs and to make any necessary adjustments. In particular, it is necessary to enter the new variants for the deletion programs in customizing specific to archiving objects. We recommend using the variants SAP&TEST and SAP&PROD. You can also use the BC sets ARCH_<archiving object> to enter these variants. BC sets are activated using the transaction SCPR20. Note that these actions are not necessary for any archiving objects that have already been upgraded with SAP Note 577847.
BAPI for material Reservation
In the Business object material reservation (object type BUS2093 - material reservation), the following new and enhanced business application programming interfaces (BAPIs) exist. In brackets you will find the names of the corresponding function modules
New BAPIs
•     Get items 1 (BAPI_RESERVATION_GETITEMS1): BAPI to read reservation items add the base unit of measure to the returned item data
•     Change (BAPI_RESERVATION_CHANGE): BAPI to change individual reservations enable the changing of an existing reservation including the appending of new items. An optional ATP check and calendar check corresponding to the functionality provided by the MB21 transaction will be provided as well for this BAPI.
Changed BAPI
•     CreateFromData1 (BAPI_RESERVATION_CREATE1): BAPI to create individual reservations With this BAPI, you can optionally assign an external reservation number. The optional ATP check and calendar check corresponding to the functionality provided by the MB21 transaction will also be provided with this BAPI.
New Report: Display List of Invoice Documents
Logistics invoice verification offers you a new report display list of invoice documents (RMMR1MDI), which you can use to display a list of invoice documents. As an addition to the existing program invoice overview (transaction code MIR6), you have extended selection criteria and display options. For example, on the initial screen you can make selections by one-time customers, invoice gross amount, and entry date. You can also show an expert mode, which enables you to select at plant level by financial accounting document, general ledger account posting, and material posting. In the output list, the report shows both posted and held invoices. It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background, or which the system has already verified as containing errors.
Pick-Up List: Batch Where-Used List Display in MB56
Until now, the top-down and bottom-up analyses in the function pick-up list for batch where-used list (transaction MB5C) where only displayed in the form of simple output lists. As of SAP ERP Central Component 5.00, the function pick-up list for batch where-used list branches to the batch where-used list itself (transaction MB56). In addition, you can define how the data in the batch where-used list is displayed, in the initial screen.
You can use all the settings available in the batch where-used list. For example, 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 pick-up list.
Purchase Orders - Funds Management
*Reference funds reservation from purchase requisitions(PRs)/purchase orders (POs) going into stock
•     You can now reference a funds reservation from a purchase requsition or a purchase order, even if these documents use account assignment category space, meaning that the order is not for direct consumption, but for inventory stock
•     Field Status for PRs/POs Without Account Assignment Categories
•     It is now possible to customize the funds management (FM) account assignment elements (and funds reservations) for POs and PRs with account assignment category space, meaning items that are not ordered for consumption, but which go into stock. This feature is only supported in the new transactions (ME2N and ME5N).
•     Effects on Customizing
•     If you do not carry out this customizing and FM is active, all the available fields are displayed as optional
•     Redesign of FM warehouse concept
The main changes are as follows:
•     Warehouse funds center and any other account assignment can be derived using the derivation tool
•     Statistical indicator must be triggered using a statistical commitment item
Purchase Orders - Order Optimization
To make order optimization available for general use, the following changes were made to the functions that could previously only be used for SAP retail software:
Plants no longer have to be of type store or distribution center. In non-retail solutions, order optimization selects plants of type <BLANK> in the following transactions: Automatic load building (WLB13), manual load building (WLB5) and replenishment workbench (WOD1). The links from these transactions to maintenance transactions for the site master (WB02) were converted to links to the plant master (OX10).
Determining orderable materials – You must determine this list using the user exit EXIT_SAPLWPOPO_001
Removing links to promotion transactions – Because promotions can only be used in SAP retail software, the options to go to promotion transactions from the menu entries have been removed
Enhanced order optimization
The following changes have been made to the order optimization functions:
•     Messages changed
- When errors occur during automatic load building, the system now creates information messages instead of error messages. This means it can process all error-free load builds. You can recognize the load builds that contain errors and process them manually.
- In the flow trace for automatic load building you can see more clearly which messages belong to a load build. The system now indicates the start of processing and the end of processing of a load build with a message.
- The existing messages have been extended to include extra information so that you can make the relevant corrections, for example, in the master data.
•     More detailed control of order optimization possible
•     In Customizing for order optimization, more detailed control of the parameters for load building and Investment Buying is now possible using profiles, for example, maximum range of coverage for order optimization. You can now select a profile from the entries from Customizing for order optimization in the selection screen for order optimization. If no profiles have been entered, the system uses the first entry in table TWBO0. This means that the program behavior remains unchanged following an upgrade and you do not have to adjust anything.
•     Materials without forecast values possible
- Automatic load building now also considers materials without forecast values. Purchase requisitions and purchase orders are processed in the same way as materials with forecast values.
•     Restriction profile check enhanced
- In customizing for order optimization you can now define for restriction profiles whether an order request link is valid for the minimum restrictions check. In this case, the minimum restrictions count as being fulfilled when at least one of the minimum restrictions is fulfilled.
•     Results list for automatic load building extended
- In the results list for automatic load building, you can now select and delete rows in blocks or created follow-on documents. This makes faster subsequent processing possible.
- All functions that show additional details screens or branch to display transactions have been switched to cursor-sensitive logic.
- You can now delete individual rows or several rows from the results list. This reduces the extra manual work required. You can make sure manually that the load builds created by automatic load building fulfil a restriction profile. When you delete rows, the totals of the actual values for a restriction profile are reduced.
•     Purchase requisitions from automatic load building can be excluded
- You can now exclude purchase requisitions with certain document types from processing in automatic load building. The procurement process for these purchase requisitions then takes place outside of automatic load building.
•     New follow-on documents possible
- If you do not start automatic load building in simulation mode, the system now offers purchase requisitions as possible order documents in addition to purchase orders. You can determine whether the load building always creates purchase requisitions or only when all restrictions defined in a restriction profile are fulfilled. If in the latter case, not all the restrictions are fulfilled, the transaction behaves as it would in simulation mode. Purchase requisitions as follow-on documents save you work. You can, for example, delete purchase requisitions or assign them to another vendor.
- You can now have purchase requistions generated for additional quantities from the results list.
•     Validity of the results list dependent on a plant calendar
- In Customizing for order optimization, you can now set the number of calendar days for which the entries in the results list for automatic load building are valid. You can set a short validity period and the validity period of the entries that were created after a weekend or public holiday gives your MRP controllers sufficient time to check and adjust the results.
reward if useul
rb