Data migration from ECC5.0 to ECC6.0

Question

Hi All,
Is there a standard SAP utility to migrate the data from ECC5.0 to ECC6.0? Assumption is that all the standard fields and the transactions are same. Good example for this case is standard material master, Purchase order, purchase info record etc.
Currently I am planning to extract the data from source system (using custom program or table download etc...) and upload the data into target system (using LSMW, eCATT, BDC etc...).
Is there a standard way to load the data into target system without extraction and upload? Please let me know.
Thanks
Nagarajan

Answer 1

ALE Customizing
1)     IMG > Application Link Enabling (ALE) > Sending and Receiving  >  logical systems > Define Logical System:  name it XXXXXX
2)     IMG > Application Link Enabling (ALE) > Sending and Receiving  >  Systems in Network > Asynchronous Processing > Assigning Ports > Define Port: name it XXXXXX   Description:  Files for Migration to YYY
The port need to be defined beneath FILE
The IDOC record types for SAP Release 4.x need to be selected
A physical directory is needed.  One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
3)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
a)     Cross-System Company Codes
b) Assign Cross-System Company Code to Chart of Accounts
c) Assign Company Code to Cross-System Company Code
Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
4)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
Here we need a distribution model
     Structure: model view (call it XXXXXX)
               Sending system (AAAAAA)
                    Receiving system  (XXXXXX)
5)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
(Beside of customers and vendors, we need to add the message type BOMMAT for material bill of materials and MATMAS for material master to to the distribution model, probably manually in step 4. Depending on further requests for automatic migration the one or other message type may need to be added later )
6)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
Partner profile type/Partner type: LS  logical system
Partner profile/Partner number: XXXXXX
Details at Post Processing agent
Typ: US user
Agent: JJJJJ
Lang: EN
Outbound parameters
Message type:     ADDR2MAS
               ADR3MAS
               ADRMAS
               MATMAS
               CREMAS
               DEBMAS
Details per message type like this:
Receiver port: XXXXXXX Output mode: Collect Idocs and Do not start subsystem
IDOC type:      for     ADDR2MAS   use      ADR2MAS02
               ADR3MAS          ADR3MAS02
               ADRMAS          ADRMAS02
               MATMAS          MATMAS03
               CREMAS          CREMAS03
               DEBMAS          DEBMAS05
Activate syntax check
7)     Authorization needed to execute Transactions:
BD12 Send Customers
BD14 Send vendors
BD10 Send material
BD30 Send bill of material
Depending on future migration requests for other objects we may need some more.