Data Mapping & Migration for Pricing Records.

[Former Member]

Hi,

We are upgrading from 4.6c to ECC 5.O and in Migration stage of Master Records.

Can anybody throw some light of mapping fields and migrating the pricing records(condition records) from 4.6c to ECC 5.O.

Thanks,

Kalyan

[Former Member]

HI

Refer below

[url=http://sap.ittoolbox.com/groups/technical-functional/sap-dev/adding-condition-records-via-lsmw-1632841]Adding Condition Records Via LSMW[/url]

[Former Member]

HI Kalyan

Data migration is the process of transferring data between storage types, formats, or computer systems. Data migration is usually performed programmatically to achieve an automated migration, freeing up human resources from tedious tasks. It is required when organizations or individuals change computer systems or upgrade to new systems.

To achieve an effective data migration procedure, data on the old system is mapped to the new system providing a design for data extraction and data loading. The design relates old data formats to the new system's formats and requirements. Programmatic data migration may involve many phases but it minimally includes data extraction where data is read from the old system and data loading where data is written to the new system.

After loading into the new system, results are subjected to data verification to determine that data was accurately translated, is complete, and supports processes in the new system. During verification, there may be a need for a parallel run of both systems to identify areas of disparity and forestall erroneous data loss.

Automated and manual data cleansing is commonly performed in migration to improve data quality, eliminate redundant or obsolete information, and match the requirements of the new system.

Data migration phases (design, extraction, cleansing, load, verification) for applications of moderate to high complexity are commonly repeated several times before the new system is activated.

Upgradation to SAP R/3 version 4.6c for a leading global manufacturer

The customer is a world leader in the manufacture of energy and telecom cables.

Scope of Work

Upgrade from SAP R/3 version 3.1i with add-on industry specific cable solution to SAP R/3 version 4.6c cable solution.

Benefits to the Customer

With the upgrade, the organization became an integral part of the worldwide ERP network.

New functionalities were added in all the modules in which the upgrade was implemented.

The customer can now upgrade to SAP R/3 4.7 (enterprise) as a single step. Upgrade from SAP R/3 3.1i to SAP R/3 4.7 is not possible. Also, going for a twostep upgrade at one go is full of risks and the two-stage migration mitigates this risk.

Reward if useful to u

[Former Member]

Hi Kalyan Ram,

When you are upgrading from 4.6C to ECC6

Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).

To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).

Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.

For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.

For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.

ECC6.0 supports UNCODE.

For installing 4.6 you don't require solution manager key. It only having ABAP stack.

4.6C supports NONUNICODE.

Major difference is ECC6 is netwear product having WASJAVA+ABAP

secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.

Please go through the link that is shown here and if there is any doubts then feel free to ask.

A3. Major difference is ECC6 is net weaver product having WASJAVA+ABAP

secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides

For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.

For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.

ECC6.0 supports UNCODE.

For installing 4.6 you don't required solution manager key. It only having ABAP stack.

4.6C supports NONUNICODE.

A4. Refer sdn thread and make a small search where u can find lot of information Reg this

olution 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

Refer below and search for posts on this topic on sdn

There are so many differences between the version in different objects

I

These are the some of the settings that are differed in the two versions and in that two objects

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/

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula