Version ECC 6.0 and 4.7

Hi Guru,
In HR Point of view, What is difference between ECC6.0 and 4.7 versions?
Regards
Kadalur

Dear Andy
Can you give 2 more points in HR point of view.
Regards
kadalur

Similar Messages

Users working in version ECC 6.0 and above

hi
I need some help, I am trying to run this code on my system but not able to get the desired result,
i just want to test whether other users working on ECC 6.0 and above can run this code from their system.
Just copy, paste and run this code... I will get an e-mail automatically, I shall reward points in return, please help me with this...
REPORT bcs_example_5.
* This example shows how to send
*   - a simple text provided in an internal table of text lines
*   - and an attached MS word document provided in internal table
*   - to some internet email address.
* All activities done via facade CL_BCS!
DATA: send_request       TYPE REF TO cl_bcs.
DATA: text               TYPE bcsy_text.
data: binary_content     type solix_tab.
DATA: document           TYPE REF TO cl_document_bcs.
DATA: sender             TYPE REF TO cl_sapuser_bcs.
DATA: recipient          TYPE REF TO if_recipient_bcs.
DATA: bcs_exception      type ref to cx_bcs.
data: sent_to_all        type os_boolean.
START-OF-SELECTION.
    PERFORM main.
*       FORM main                                                     *
FORM main.
try.
*     -------- create persistent send request ------------------------
      send_request = cl_bcs=>create_persistent( ).
*     -------- create and set document with attachment ---------------
*     create document from internal table with text
      APPEND 'Hello world!' TO text.
      document = cl_document_bcs=>create_document(
                      i_type    = 'RAW'
                      i_text    = text
                      i_length = '12'
                      i_subject = '' ).
*     add attachment to document
*     BCS expects document content here e.g. from document upload
*     binary_content = ...
      CALL METHOD document->add_attachment
        EXPORTING i_attachment_type = 'DOC'
                   i_attachment_subject = 'My attachment'
                   i_att_content_hex    = binary_content.
*subject line more than 50 chars
      DATA: T_SUB TYPE STRING.
      t_sub = '[ D01 TEST] CCS0000096 NJ 8A7192 21 CONSTITUTION AVE'.
      call method send_request->set_message_subject( t_sub ).
*     add document to send request
      CALL METHOD send_request->set_document( document ).
*     --------- set sender -------------------------------------------
*     note: this is necessary only if you want to set the sender
*           different from actual user (SY-UNAME). Otherwise sender is
*           set automatically with actual user.
      sender = cl_sapuser_bcs=>create( sy-uname ).
      CALL METHOD send_request->set_sender
        EXPORTING i_sender = sender.
*     --------- add recipient (e-mail address) -----------------------
*     create recipient - please replace e-mail address !!!
      recipient = cl_cam_address_bcs=>create_internet_address(
                                        '[email protected]' ).
* To send the mail immediately
      call method send_request->set_send_immediately( 'X' ).
*     add recipient with its respective attributes to send request
      CALL METHOD send_request->add_recipient
        EXPORTING
          i_recipient = recipient
          i_express    = 'X'.
*     ---------- send document ---------------------------------------
      CALL METHOD send_request->send(
        exporting
          i_with_error_screen = 'X'
        receiving
          result              = sent_to_all ).
      if sent_to_all = 'X'.
        write text-003.
      endif.
      COMMIT WORK.
* *                     exception handling
* * replace this very rudimentary exception handling
* * with your own one !!!
catch cx_bcs into bcs_exception.
    write: 'Fehler aufgetreten.'(001).
    write: 'Fehlertyp:'(002), bcs_exception->error_type.
    exit.
endtry.
ENDFORM.

Hi,
The following code is i have done in ECC 6.0 working fine for me. May this one help you in anyway.
data: send_request       type ref to cl_bcs.
data: document           type ref to cl_document_bcs.
data: sender             type ref to cl_sapuser_bcs.
data: recipient          type ref to if_recipient_bcs.
data: exception_info     type ref to if_os_exception_info,
bcs_exception            type ref to cx_document_bcs.
data i_attachment_size type sood-objlen.
data v_status          type bcs_stml.
data v_request_status type bcs_rqst.
send_request = cl_bcs=>create_persistent( ).
try.
      document = cl_document_bcs=>create_document(
                                    i_type    = 'RAW'
                                    i_text = it_content[]
                                    i_subject = subject ).
      if not attach_name1 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext1
            i_attachment_subject = attach_name1
            i_att_content_text   = it_attach1[].
      endif.
      if not attach_name2 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext2
            i_attachment_subject = attach_name2
            i_att_content_text   = it_attach2[].
      endif.
      if not attach_name3 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext3
            i_attachment_subject = attach_name3
            i_att_content_text   = it_attach3[].
      endif.
      if not attach_name4 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext4
            i_attachment_subject = attach_name4
            i_att_content_text   = it_attach4[].
      endif.
      if not attach_name5 is initial.
        call method document->add_attachment
          exporting
            i_attachment_type    = attach_ext5
            i_attachment_subject = attach_name5
            i_att_content_text   = it_attach5[].
      endif.
      call method send_request->set_document( document ).
      sender = cl_sapuser_bcs=>create( sy-uname ).
      call method send_request->set_sender
        exporting
          i_sender = sender.
      loop at it_recipient.
        translate it_recipient-smtp_addr to lower case.
        recipient = cl_cam_address_bcs=>create_internet_address( it_recipient-smtp_addr ).
        call method send_request->add_recipient
          exporting
            i_recipient = recipient
            i_express    = ' '
            i_copy       = ' '
            i_blind_copy = ' '
            i_no_forward = ' '.
      endloop.
      move : 'E' to v_request_status.
      v_status = v_request_status.
      call method send_request->set_status_attributes
        exporting
          i_requested_status = v_request_status
          i_status_mail      = v_status.
      call method send_request->send( ).
      commit work.
    catch cx_document_bcs into bcs_exception.
endtry.
I could not able to check your code in development boxes of mine . sorry.
aRs

Difference between ECC 6.0 and earlier versions

Hi,
one of the difference between ECC 6.0 and earlier versions is that instead 'WS_UPLOAD' and 'WS_DOWNLOAD' in ECC we should use 'GUI_UPLOAD' and 'GUI_DOWNLOAD' respectively.
(of course SPDD and SPRO tcodes is known by everone i suppose)
Similarly can u all put down some differences here, atleast one entry by each, I think we can make a good docu. I have searched the net for the differences but could not get much, so by each of us contributing one each, it would become good docu..for all of us.
Thanx in advance

Unicode Errors Encountered and their Solutions
E1. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified.
     Error:
     OPEN DATASET FILE FOR OUTPUT IN TEXT MODE.
     Solution:
     OPEN DATASET FILE FOR OUTPUT IN LEGACY TEXT MODE.
E2. In Unicode, DESCRIBE DISTANCE can only be used with the IN BYTE MODE or IN
      CHARACTER MODE addition.
     Error:
     DESCRIBE DISTANCE BETWEEN T_KOMK AND T_KOMK-HIEBO01 INTO BPOS.
     Solution:
DESCRIBE DISTANCE BETWEEN T_KOMK AND T_KOMK-HIENR01 INTO BPOS
IN CHARACTER MODE.
E3. u201CUSR02-UFLAGu201D must be a byte-type field (Typ X or XSTRING )
     Error:
     IF USR02-UFLAG O YULOCK.
     Solution: Since the data type of USR02-UFLAG is type INT and is compared with data type
                X u2013 Hence the error. So we define a new variable ZULOCK and assign the
                value of USR02-UFLAG to ZULOCK.
              New variable
              DATA: ZULOCK(1) TYPE X.   "APBRP00
              Assign value
                            ZULOCK = USR02-UFLAG.
        Compare -
               IF ZULOCK = YULOCK.   u201Creplace IF USR02-UFLAG O YULOCK.
E4. HT cannot be converted to a Character type field
Error :
WRITE ht TO t_data+10(2).
Solution : Since the data type of ht is a type u2018Xu2019 and the data is been transfer to
         t_data which has a data type u2018Cu2019. value of one data type cannot be copy to
         another data type where one of them is type string .Hence the error occur,
         so the data type of ht is been change to Type u2018Cu2019
     OR
           A Tab ( value 09 ) is introduced as part of the row. The value 09 is not converted in Unicode environment. Instead we need to use class
     Error:
          DATA: BEGIN OF ht,
               x(1) TYPE x VALUE '09',
          END OF ht.
     Solution:
              Define Class after the Tables definition.
                   CLASS cl_abap_char_utilities DEFINITION LOAD.
              Data Defination : Comment internal table HT and define a variable HT type C.
       *   Insert + APRIA00 05/02/2007 Unicode project
       *   DATA: BEGIN OF ht,
     *         x(1) TYPE x VALUE '09'
       *   END OF ht.
     *   Insert - APRIA00 05/02/2007 Unicode project
       DATA HT type C.
       Before using HT assign Horizontal tab.
                 Ht = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
E5. In Unicode programs the u201C#u201D cannot appear in names, as it is does here in the name    u201C#LINESu201D
     Error :
     #LINES                 TYPE I,
     Solution : Since the # is used in the start of name, it is not allowed. We need to
              remove it.
     Solution for the above
     V_LINES                 TYPE I,
E6. In u201CTEXT MODEu201D the u201CENCODINGu201D addition must be specified as well as the addition was required FOR OUTPUT,FOR INPUT, FOR APPENDING OR FOR UPDATE was expected.
     Error:
     OPEN DATASET PATH_NAME IN TEXT MODE.
     Solution:
     Download =     OPEN DATASET PATH_NAME FOR OUTPUT IN LEGACY TEXT MODE.
     Upload        = OPEN DATASET AUSZUG-FILE IN TEXT MODE FOR INPUT ENCODING DEFAULT.
E7. u201CTABu201D must be a character-type data object( data type C,N, D, T or String). Field string)
     Error:
            data: begin of tab,                   "Excel Parameter Split at TAB
        t type x value '09',          "Tabulator
       end of tab.
            concatenate 'Material' 'Package Status'
                into z_download-line separated by tab.
            ( In the above command the two field are to be separated with a horizontal Tab. The earlier      way of assigning the tab value u201809u2019 will not work in Unicode environment.
     Solution:
     Define a class just after the Table defination.
          CLASS cl_abap_char_utilities DEFINITION LOAD.
            Define variable Tab as shown below :
          Data : TAB           TYPE C.
     Before the concatenate statement assign the value of Tab using pre-defined attributes.
          TAB = CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
E8. Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not Unicode-
      enabled; use the class cl_gui_frontend_services
     Error-1: Function WS_DOWNLOAD is obsolete in Unicode environment.
            call function 'WS_DOWNLOAD'
                 exporting
                      filename = zfilename
                 tables
                      data_tab = z_download.
     Solutions-1: Instead of WS_DOWNLOAD use GUI_DOWNLOAD.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
*   BIN_FILESIZE                  =
    FILENAME                      = zfilename
TABLES
    DATA_TAB                      = z_download.
E9. The "/" character is reserved for identification of namespaces. It must be entered twice.
        The name of a namespace must be at least 3 characters long.
     Error :
                 U/N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
     Solution :
     * Special character can not be used to define a data variable
     *      U/N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
              U_N(3)        TYPE C, "U/N    --> ERSETZT DURCH SPACE
     * Insert - APSUS02 07/02/2007 Unicode Project
E10. "LP_TAB" and "CS_TAB" are not mutually convertible. In Unicode programs,
         "LP_TAB" must have the same structure layout as "CS_TAB", independent of the length
         of a Unicode character.
     Error : This error is encountered when data from one internal table is copied to another
                         internal table which different structure. In this case its LP_TAB & CS_TAB.
                 LP_TAB[] = CS_TAB[].
     Solution :
          * Replace + APSUS02 07/02/2007 Unicode Project
*   LP_TAB[] = CS_TAB[].
              move-corresponding CS_TAB to LP_TAB.
          * Replace + APSUS02 07/02/2007 Unicode Project
E11. Could not specify the access range automatically. This means that you need a RANGE
          addition.
     Error : Range need to be specified as an addition to the command.
            DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1).
           Solution :
            DO 4 TIMES VARYING HELP_CHAR FROM ABCD(1) NEXT ABCD+1(1)
          * Insert + APSUS02 07/02/2007 Unicode Project.
                                                      RANGE ABCD+0(4).
* Insert - APSUS02 07/02/2007 Unicode Project.
E12 . Processing Terminated Error code: Error in opening /
                                          Path not found when downloading to Unix directory.
     Error : PARAMETER: outfile(92) DEFAULT
              '/CP/interface/NPP/data/MX/cbslaprcpts'
                    LOWER CASE,
               kmxmstrd AS CHECKBOX.
            This error is encountered when the path is missing. The above path is related to CCP.
     Solution: For testing purpose comment the original path and replace it with
                                 /CP/interface/CCD/Unicode_test/
E13.    Upload/Ws_Upload and Download/Ws_Download are obsolete, since they are not                                                                       Unicode- enabled; use the class cl_gui_frontend_services
     Error: Function WS_UPLOAD is obsolete in Unicode environment. (During UCCHECK)
               Call function 'WS_UPLOAD'
       Exporting
            Filename                = zfilename
            Filetype                = u2018DATu2019
       Tables
            data_tab                = z_upload
       Exceptions
            Conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_table_width     = 4
            invalid_type            = 5
            no_batch                = 6
            unknown_error           = 7
            gui_refuse_filetransfer = 8
            others                  = 9.
     Solution: Instead of WS_UPLOAD use TEXT_CONVERT_XLS_TO_SAP. Do not use temporary file put the file name as it is.
1) First define a type pool and a variable of type truxs_t_text_data.
TYPE-POOLS: truxs.
DATA: it_raw TYPE truxs_t_text_data.
     2) Use this it_raw in the function module in parameter i_tab_raw_data. Put file name and the internal table in the function module.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
    EXPORTING
*     I_FIELD_SEPERATOR        =
*      i_line_header            = ' '
      i_tab_raw_data           = it_raw       " WORK TABLE
      i_filename               = zfilename
    TABLES
      i_tab_converted_data     = z_upload[]    "ACTUAL DATA
   EXCEPTIONS
      conversion_failed        = 1
      OTHERS                   = 2.
     Comment u201Ci_line headeru201D. It takes the first/ header line of the file which is to be uploaded.
Put square brackets after internal table as shown above.
E14.    CURSORHOLD may not be converted into a number.
     Error: GET CURSOR LINE CURSORHOLD VALUE CURSOR_HOLD.
     Solution: In the declaration part of CURSORHOLD, one field is of u2018Pu2019 type and one field is of u2018Iu2019 type, which is not allowed in Unicode environment.So change the the type of it to NUMC.

What is the difference between version 4.7 EE and ECC 6.0 in SD module.

Hi SAP Gurus,
what are the features in 4.7 EE version in general.
what are the features in ECC 6.0 version in general.
then give me the exact difference between version 4.7 EE and ECC 6.0 in SD module.
if u give the information, then u will get the rewards.
Regards,
somu.

Hi Somu,
These are additional enhancements avialble in ECC6.0 other than that remaining same as 4.7E
1.E-Commerce:- SAP ERP provides powerful e-commerce capabilities that can be expanded in an easy, cost-effective manner in line with business growth. Organizations can run a complete sales process on the Internet, and provide business-to-business (B2B) and business-to-consumer (B2C) customers with personalized and interactive online self-services.
2.Mobile Sales for Handhelds:-SAP ERP enables sales professionals to access front- and back-office business processes and to manage critical sales activities in the field using standard PDAs or other handheld devices (including those with bar code scanners). In this area, SAP ERP provides the following functions:- Customer managementWith SAP ERP, sales professionals may enter, view, and modify detailed customer information, and view sales order history for each customer.- Sales order managementSAP ERP enables sales staff to take sales orders via bar code scanners; search, create, and modify sales orders; and list or sort sales order partners.- Material managementSupport for material management for mobile sales enables staff to view material lists or details for a specific material, search material, and display customer-specific prices.
3.Resource-Related Down Payments and Billing:-- Supports creation of down-payment requests analogous to the functions offered by resource-related billing- Enables organizations to bill the requesting company code for services provided via a resource-related billing document.
4.SAP Beverage Functions Available for the Consumer Products Industry:- As of SAP ERP Central Component (SAP ECC) 5.00, the following functions from the SAP beverage industry solution are available for the consumer products industry:* SAP ECC 5.00, consumer products (EA-CP 500)- Material sorting- Extra charge- Empties management- Part load lift orders- Pendulum list indirect sales- Sales returns- Excise duty* SAP ECC 5.00, supply chain management extension (EA-SCM 500)- Direct store delivery back-end- Master data- Visit control- Transportation planning (including loading units, aggregation categories)- Vehicle space optimization- Output control (including valuated delivery note)- Route accounting (including tour data entry, cash payer, route settlement)* SAP ECC 5.00, industry-specific sales enhancements (EA-ISSE 500)- Extended rebate processing.
5.Credit Management:-Integrating sales and distribution (SD) credit management with SAP Credit Management application:With SAP ERP 6.0 application, you can also use SAP Credit Management in SAP Financial Supply Chain Management set of applications (FIN-FSCM-CR) to perform all credit checks and commitment updates for all areas of sales (SD-BF-CM). In SAP Credit Management, you can update the data from multiple systems. This enables you to execute credit checks with consistent data in distributed systems, too. Furthermore, you can connect to external credit information providers by extensible markup language (XML) interfaces. Alternatively, you can continue to use SD Credit Management (SD-BF-CM).
6.E-Commerce: Catalog Management :-As of SAP ERP 6.0 application, you must carry out product catalog replication from your ERP solution to the Text Retrieval and Information Extraction (TREX) server for use in the Web shop, using the report ISA_CATALOG_REPLICATION.
7.E-Commerce: Quotation and Order Management:- Order creation with reference to a contract that has been displayed* Lock of sales documents to avoid concurrent access during the order change process* Display of bills of material in the shopping basket* Free goods processing* Processing of grid products for the SAP Apparel and Footwear application* One-step business order processing* Selection of multiple transaction types in the shopping basket* Credit card support in business-to-business (B2B) Web shop* Material number format conversion* Maintenance of delivery priority in the shopping basket (B2B)* Document search for all documents across all sales areas* Interprocess communication-characteristic value display in basket and order confirmation
8.E-Commerce: Selling Over eBay:-Creation and management of product listings on eBay leverages the e-commerce order management and fulfillment capabilities of the SAP ERP application by easily tying existing tax, pricing, shipping, and payment configurations to post-auction processing. Enhancements in 2005: * You can use the business-to-consumer (B2C) checkout instead of the eBay checkout. With the B2C checkout, you can maximize cross-selling and up-selling opportunities by leveraging B2C functionality, determine tax and shipping using the elaborate methodologies available through condition techniques in SAP ERP 6.0. * E-mail notification scenario: winner notification to keep the auction winner updated with the status of the auction and of his or her order * Monitoring through features such as single-activity trace (SAT), heartbeat, and logging * Creation and publishing of multiple-item auctions and manual retraction of winners
9.E-Commerce: User Management:-- Web-based user management for business-to-business internet users - Assignment of authorization roles to users in web-based user management - Automatic migration of SU05 to SU01 internet users
10.Enterprise Services in Sales Order Management:-Please check in the Enterprise Services Workplace site which enterprise services are available for sales order management on the SAP Developer Network site (www.sdn.sap.com).
11.Internet Pricing and Configurator (IPC):-The IPC is enhanced and integrated to allow configuration within the sales documents of the SAP ERP application reusing existing model data while leveraging its improved functionality and advanced user interface within SAP ERP.
12.Price Catalog (PRICAT): Inbound Processing (Retail):-Inbound message processing of PRICAT essages:As of SAP ERP Central Component enterprise extension retail 6.0 (EA-RET 600) component, you can create and change article data automatically, or in an interface for mass data handling. The system takes both single and generic articles and bills of material and prices into account.
13.Rebate Condition Records Using Scales:-As of SAP ERP 6.0 application, you can set up rebate agreements so that the scale base value and the rebate scale level is derived from the total sales volume of multiple condition records. You do this by grouping condition records in the rebate agreement.
14.SAP Role: Internal Sales Representative:-SAP role internal sales representativeThis role delivers all the functions to fulfill the requirements of an internal sales representative. This includes tasks such as answering phone calls from customers and prospective customers, processing incoming inquiries and sales orders, and preparing quotations and sales contracts.Target groupThe responsibilities of an internal sales representative (or customer service representative) include the following:- Answering phone calls from customers and prospective customers- Answering product, price, and order status related questions- Processing incoming inquiries and sales orders- Preparing quotations and sales contracts- Taking sales orders and ensuring successful order processing for example, taking care of the completeness of sales documents, releasing delivery-blocked orders, and so on - Support for the outside sales force for example, checking on quotations, updating customer master data, and so on- Preparing reports and sales analyses for the sales manager and the sales teamWork overview This work center gives you an overview of your daily work and gives you easy access to your most important tasks. Sales documents This work center allows you to work on all your sales documents. You can create and maintain inquiries, quotations, sales orders, sales contracts, scheduling agreements, and billing documents. Order fulfillment This work center allows you to monitor order fulfillment. You can display deliveries, backorders, and shipments, and can check product availability.Master data This work center enables you to work on all your master data. You can create and maintain business partners, customer agreements, prices and conditions, and products.
I hope it will help you
Regards,
Murali.

Upgrading from 4.7 to ECC 6.0 And GTS 2.0 to a newer version

Hi everyone,
I am new to SAP SD, I am involved in upgrading from R/3 4.7 to ecc 6.0 and GTS 2.0 to a newer version. Can somebody tell me the major differences in these two vesions and also some link through which I can get some info. It is very urgent.
Thanks.

Dear Paranidharan Gandhi,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
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 pls 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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Documentation on differences between Version ECC 6 and Old version

We are looking for information/documentation on differences between Version ECC 6 and Old version for HCM. Appreciate for your great help.
Best Regards,
Eric

Hai..
Re: differnce b/n 4.7 and ecc 6.0
Re: Difference Between SAP Version ECC 4.6, 4.7, SAP 5.0, 6.0 with SA
https://websmp210.sap-ag.de/releasenotesRelease Notes
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/
http://service.sap.com/instguides
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
http://solutionbrowser.erp.sap.fmpmedia.com/
http://solutionbrowser.erp.sap.fmpmedia.com/

Difference between versions 4.7EE , ECC 5.0 and ECC 6.0.

Hi Guys..Today I attended one interview. There They asked me the difference between the versions of 4.7EE , ECC 5.0 and ECC 6.0?.
So, Could anyone please post the differences and Advantages one over another?
9916596344

Could you please search the forum first? There's a lot of questions asking for the same...
Greetings,
Blag.

Data Consistency when Copying/ Refreshing ECC 6.0 and SRM-SUS 5.0 Systems

Hello,
We are planning a refresh / system copy of an ECC 6.0 and SRM-SUS 5.0 system
The refreshes will be completed from backups taken of production systems refreshed onto the QA Landscape.
I have referenced the following SDN thread that provides some guidelines on how to refresh R/3 and SRM systems and maintain data consistency between the systems using BDLS and changing entries that correspond to backend RFC destinations:
[Is there a process/program to update tables/data after System Refresh?;
This thread is fairly old and relates to earlier versions of R/3 (4.7) and SRM (3.0). We have heard that at higher system versions there may be technical reasons why a refresh canu2019t be performed.
Does anyone have experience of completing successful refreshes of landscape that contain ECC and SRM systems at higher SAP versions (ideally ECC 6.0 and SRM-SUS 5.0) Does anyone know whether it is technically possible?
Are there any additional steps that we need to be aware of at these higher SAP versions in completing the copy to ensure that the data remains consistent between ECC and SRM?
Thanks
Frances

I have seen this somewhere in the forum: See if this helps you
BDLS: Convertion of logical system (SRM).
Check entry in table TWPURLSVR.
Check RFC connections (R/3 and SRM)
SPRO, check or set the following points:
Set up Distribution Model and distribute it
Define backend system
Define backend sytem per product category
Setting for vendor synchronization
Numbe ranges
Define object in backend sytem
Define external services (catalogs)
Check WF customizing: SWU3, settings for tasks
SICF: maintain the service BBPSTART, SAPCONNECT
SE38:
Run SIAC_PUBLISH_ALL_INTERNAL
Run BBP_LOCATIONS_GET_ALL
Update vendor BBPUPDVD
Check Middleware if used.
Run BBP_GET_EXRATE.
Schedule jobs (bbp_get_status2, clean_reqreq_up)
Convert attributes with RHOM_ATTRIBUTE_REPLACE

SAP ECC 6.0 and mySAP ERP

Hello Gurus,
Could somebody tell me the difference between SAP ECC 6.0 and mySAP ERP
Thanks and reward guaranteed

Hi,
These are versions of SAP.
you can findout the differences between these two versions from the following link
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards
Ali

How to populate cheque number in IDOC for ERP version ECC 6.0

Hi
I am using ERP version ECC 6.0. I have created a sequencial cheque lot in FCHI and assign payment method to it. But when i generate a payment run, Idoc is not getting generated. In proposal run log "IDoc type could not be determined for the IDoc" this error occurs.
Could you suggest why this error is coming. Any other configuration should be done in ERP for that payment method.

Hi Rajesh,
I am using PEXR2002 format for Idoc. Problem is i want Cheque number to populate in the Idoc for assigned payment method. For that i have assigned payment method for the cheque lot using t-code FCHI. After this i created proposal and run the payment. Status shows 1 generated, 1 completed. But the Idoc doesn't get created.Whats the problem. Can someone help me in this issue.
Thanks,
Shilpa
Edited by: Shilpa Korad on Jan 20, 2010 9:29 AM
Edited by: Shilpa Korad on Jan 20, 2010 9:48 AM

ECC 5.0 and BO without BW/BI Integration Best Practise

Hi,
I know that SAP can connect with BO system using RapidMart (replacing data warehouse BW/BI). Is this best practise?Because when i see the BI Platform RoadMap,I conclude that BI and BO will be integrate into one product, and i'm afraid to invest right now because in the future it seems we need to implement the BW system to make this BI system optimal.
My company want to use BO without implement BW system right now. SAP system that we use right now is ECC 5.0 and my company only upgrade it to next version when version 5.0 not supported again.Thank you.
Cheers,
Satria

Hi Satria,
the answer depends a little bit on what the requirement is.
RapidMarts are an option to implement a data mart solution on top of an ERP solution. On top of the Rapid Marts you can then use the BusinessObjects tools without hitting the OLTP system directly.
Ingo

ECC 5.0 and CRM 7.0 Integration Questions

Hello,
We are on ECC 5.0 and are part of a global implementation that is putting in CRM 7.0.
We have a couple of issues/questions.
1. We want to integrate ECC Internal Orders with CRM Contracts and Orders. However we don't see the ECC Internal Order type SAPS in ECC 5.0. What release/plugin would give us SAPS Internal order type
2. We currently use CS and PM in ECC, and we have equipment and func. locations. Do we need to be on a certain version/plugin to integrate Equipment and Func. Locations with CRM iBase?
3. Any tips/suggestions on integrating Vertex with CRM for taxes.
Thanks
chris

Hi
Here are the Answers
1. We want to integrate ECC Internal Orders with CRM Contracts and Orders. However we don't see the ECC Internal Order type SAPS in ECC 5.0. What release/plugin would give us SAPS Internal order type
- This is release indepedant- It is been available from R/3 4.7 so you should have it, if you dont have an SAPS order type, you have 2 options
1. Create your own SAPS Order type
2. Define RFC from Client "000" and push the order type. This must be available in "000" as a standard delivery, may be your Basis did not move the order types properly.
2. We currently use CS and PM in ECC, and we have equipment and func. locations. Do we need to be on a certain version/plugin to integrate Equipment and Func. Locations with CRM iBase?
Yes you can have the equipment and Functional Locations, but for FLocs to download to CRM you need ECC6.0 with Sp6 anything below cannot be integrated or downloaded with CRM7.0 .. for Equipments any versions are fine and you do all configuration and customization in CRM
3. Any tips/suggestions on integrating Vertex with CRM for taxes.
Its a broad question, SAP provides standard integration option to vertex, and you integrate as needed..
let me know if you need anything else.

Difference between ecc 5.0 and 4.7 or earlier in MM

Hello masters,
would you briefly explain the diffrence between ecc 5.0 and 4.7. as per MM module is concerened ,any document or link given will be appriciated .
Thanks in Advance,
Suresh.

Please check these links...
Upgrading notes 4.7 Vs ECC6
Solution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
ECC 5.0:
http://help.sap.com/saphelp_erp2004/helpdata/en/c6/feda40ebccb533e10000000a155106/frameset.htm
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
Thanks
Senthil

ECC 5.0 AND ECC 6.0

Hi Guru,
Can anyone tell me the functionality difference between ECC 5 .0 and ecc6.0.
Regards
Ananthi.M

Please explore
http://erp.fmpmedia.com/Default.aspx?alias=erp.fmpmedia.com/english
Source release version: mySAP ERP 2004
Target release version: SAP ERP 6.0
Solution area: Human Capital Management
Source: http://solutionbrowser.erp.sap.fmpmedia.com/

ESS implementation posibility with ECC 6.0 and EP 6.0

Hi ,
To implement ESS with ECC 6.0 and EP 6.0
Any body can suggest for this implementation feasibility and possibility.
What are the Business packages has to down load and where can we get those BPs.?
After importing into EP 6.0 , what are the configurations and settings required to get SAP HR screens/ivews (preview when we create after systems in EP),
What are the prerequisites and hardware and software requirements for 8000 users (apprx) ?
Any version upgradations are required for implementing this or
can we use this ECC 6.0 as backend and EP 6.0
and please help required for all those things.
Thanks
Kumar.

For ESS/MSS based on ECC 6.0 (ERP 2005), you can download the XSS business packages from
service.sap.com/download --> Support patches and packages --> Entry By application Group --> SAP Application Components --> SAP ERP -->
SAP ERP 2005 --> Entry By Component --> SAP XSS --> (SAP ESS 600, SAP MSS 600 and SAP PCUI_GP 600).
You can use JSPM to apply these business packages on to the portal. To use JSPM, you have to login to the portal server using <SID>adm to be able to use the JSPM tool.
Business Packages and components in it: you BP consists of the 2 following parts
1) BP_ERP5ESS / BP_ERP5MSS is Portal Business package which consist of iview, pages and roles.. while SAP_ESS / SAP_MSS. is WebDynpro part of it.
These iviews will direct to some WD application which are part of SAP_ESS / SAP_MSS. and they are deployed on server.
2) you have to simple go to
service.sap.com/downloadSupport patches and packagesEntry By application GroupSAP Application ComponentsSAP ERPSAP ERP 2004/2005--Entry By ComponentSAP XSS
pick the correct version and download. You get full package not incremental. Old ones will be overwritten when you deploy them. try to download them again if it failed first time.
3) Refer note 761266 for package compatibility.

Version ECC 6.0 and 4.7

Similar Messages

Maybe you are looking for