Data conversion ECC 6.0 Upgrade

Hi SAP Guru's.
My Client is intend to do a ECC6.0 Upgrade from 4.6. My goal is find out is there any data conversion requirement is needed for the project. My Client is doing a technical upgrade and then a full upgrade. Can anybody guide me what are the possible data conversions we can expect for the upgrade.
Thanks
SN

Dear Sankara,
When it is a technical upgrade from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.
We will encounter short dumps while executing certain programs. This may be due to the usage of obsolete function modules or Unicode errors.
The BDCs in the upgraded version will become defective as many of its screen field names will be changed during version change.
Program texts of many programs will be lost. They have to be restored.
In case of tables, enhancement category has to be provided.
There is a possibility of losing the variants during upgradation. So care should be taken to retain them before upgradation.
ECC6.0 is case sensitive, so many of the interface programs will fail to transfer (FTP) files between systems. These objects have to be changed so that the commands passed to the external system be UPPERCASE.
So a developer should be aware of the following:
Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.
You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.
Check the below link to find more details on usage of SPAU & SPDD transactions
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.For eg.:
--> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7
-->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.
In case of tables, we need to specify the Enhancement category.
Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.
In case of BDC programs, some field names will be changed. So they have to be named appropriately.
Please check with the below links for more details:
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
From ABAP's perspective, the following link helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
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

Similar Messages

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

Hi
We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
3 ETN256 You want to install the following add-on components:
3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
level: "0" (component type "A")
3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
level: "0" (component type "A")
2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
(type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
3 ETN245 The following import prerequisites of OCS Package "SAPK-
523EXINVIRSAHR" have not been met:
3 ETN264 In the (alternatively) Requirement set "01":
3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
software component vector
1 ETN214X."**************************************************"
We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
Any ideas?
Regards
Chandu

Hi
This is what the solution provided by SAP Support:
Quote:
we have finally found the problem, it's a bug in the package upload
functionality used by the upgrade. The consequence of this bug is that
Support Packages whose EPS files (.PAT files) have a certain string in
the name, namely the string 0000000 after the _ and before .PAT
extension, are not properly uploaded to the ABAP system and hence are
not visible or known to the upgrade.
This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
Check your EPS/in directory after the CAR/SAR Archives of the SPs are
extracted and rename all .PAT and .ATT files, which have a name like
*_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
Afterwards, the upgrade will upload the informations about the SP
properly and the SP can be included into the upgrade.
Files:
31/01/2007 07:32 329 VS30020106486_0000000.ATT
31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
If these two files are renamed to e.g.
VS30020106486_9000000.ATT
VS30020106486_9000000.PAT
the affected VIRSANH SP2 is uploaded correctly by the upgrade
functionality and the SP inclusion of the VIRSANH SPs works.
Sorry, as of now I cannot promise you a date when the tool fix will be
available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
Afterwards, I will know more...
Unquote:
Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
Regards
Chandu
Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

Dear all,
We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
I shall modity the same to our customer and submit
Thanks & Regards
Senthil
[email protected]

Preparation Phase* 6 days
Kick Off Meeting 1 day
Upgrade Project Procedures Preparation 1 day
Prepare Upgrade Project Plan 1 day
Technical Requirements Assessment 3 days
Assess Training needs of Key-users & End-users 1 day
Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
Business Blueprint Phase 6 days
Develop System Landscape Upgrade Plan 1 day
Functional Requirement Checklist 1 day
ABAP Development check list 1 day
Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
Identify Testing Scope & Scenarios 1 day
Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
Develop Documents as per Basis Activity List 1 day
Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
Prepare Upgrade Deliverables Checklist 1 day
Realization Phase 28 days
Installation of Solution Manager 3.2 System 1 day
Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
Upgrade Frontend Software 4 days
Perform SPAU & SPDD Corrections 5 days
Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
Perform Upgrade Testing for each Application Module 7 days
Perform Unit & Integration Testing 6 days
Perform Training to Key Users & End Users (Generic & Specific) 3 days
Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
Testing by end users on Quality System 1 day
Production Realization & Go-Live Phase 6 days
Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
User Acceptance Testing 1 day
Production System Go-Live 1 day
Post Go-Live Support 14 days
Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

Hardware requariment for ECC 6.0 upgrade from ECC 5.0

Hello
I am on ECC 5.0 with oracle 9.2.0.7.I need to upgrade this to ECC 6.0.
I have already implemented MM,PP,FICO,QM and HCM.My current data base size is 900GB.This has 30GB monthly growth.
With this ECC 6.0 upgrade i am planing to implement PM,EP.
I know converting none Unicode system to unicode system is required some more hardware resources than the none Unicode.
Some document says 40-60% more disk space and 35% more processing speed from current system.
Can any one give me the correct information about the hardware requirement for ECC 5.0 to ECC 6.0 upgrade.
Thanks
Roshantha

Check with the Links
https://websmp102.sap-ag.de/sizing
https://websmp208.sap-ag.de/quicksizer
http://www.4soi.de/
http://www.easymarketplace.de/
Kanagaraja L

Pulling of Exchange Rate data from ECC to BI

Hi All,
we are having an requirement to pull TCURR Table Exchange Rate data from ECC to BI.
If anybody worked on this scenario could you please share valuable inputs regarding this.
I gone through this SDN forum link: Re: Automated Exchange Rate Loading in BPC NW ( please share some more details regarding this )
Regards
Amit

Hi All,
I hope this will help you to pull Exchange rate data from ECC Table : TCURR to SAP BI System.
ECC Steps : Creation of generic datasource
1) Create generic Transaction Data source Using TCode : RSO2 with name ZTCURR and then press create Button.
2) Input Applic. Component: FI-GL and give description.
3) Input View/Table: TCURR and Press save Button.
4) This will take you to extract structure of data source ZTCURR. In this structure select respective field from the selection field option (In future we will use it in BI info package) and then press save button.
5) Use Tcode: RSA3 to check the data by giving custom data source ZTCURR name.
Note:In this case we are extracting full data from TCURR table. If your project demands you can use delta specific field.
SAP BI 7 Steps
1) Go to BI system, TCode: RSA1--> Source System-> Replicate metadata, then you can see generic data source "ZTCURR" in your BI data source tree.
2) Maintain Info cube Structure same like table : TCURR,
ECC Field      ECC DATA TYPE                               BI Field     BI Data Type
KURST     CHAR                          -
>                 ZKURST     CHAR (Length 4)
FCURR     CUKY                          -
>          ZFCURR     CHAR (Length 5)
TCURR     CUKY                          -
>          ZTCURR     CHAR (Length 5)
GDATU     CHAR                          -
>          ZGDAT      CHAR (Length 8)
UKURS     DEC                             -
>          ZUKURS     NUMBER ( Key Figure )
FFACT     DEC                             -
>          ZFFACT     NUMBER ( Key Figure )
TFACT     DEC                             -
>          ZTFACT     NUMBER ( Key Figure )
=========================================================================================
3) Conversion of default format "YYYY/MM/DD" to "YYYYMMDD".
In Transformation: "GDATU" is number format, not date format, so we need to write start routine in transformation.
With the Help of below code you can convert default format
"YYYY/MM/DD" to "YYYYMMDD".
DATA: DATE      TYPE CHAR10,
          L_INDEX   TYPE SY-INDEX.
LOOP AT SOURCE_PACKAGE ASSIGNING <SOURCE_FIELDS>.
    L_INDEX = SY-TABIX.
    CALL FUNCTION 'CONVERSION_EXIT_INVDT_OUTPUT'
      EXPORTING
        INPUT = <SOURCE_FIELDS>-GDATU
      IMPORTING
        OUTPUT = DATE.
    CONCATENATE DATE+6(4)
                DATE+3(2)
                DATE+0(2)
    INTO <SOURCE_FIELDS>-GDATU.
    MODIFY SOURCE_PACKAGE FROM <SOURCE_FIELDS> INDEX L_INDEX TRANSPORTING GDATU.
ENDLOOP.
Note : Customize above ABAP code according to your client requirement.
==============================================================================================
4) Calculation of Month End Rate----> Means last working day of month
Please refer below solution ( sent on 3rd June 2011 ) to calculate Month Rate
Go to BI transformation and write formula in ZGDAT field. In this case add GDATU as source field of rule and write below formula.
*Last working day of month Formula *    :             LAST_WORKINGDAY_MONTH( GDATU, '' )
Last working day is calculated based on the data maintained in the ECC TCODE : SCAL ( SAP Calendar )
==============================================================================================
5) CALMONTH calculation: conversion of YYYYDDMM format   to YYYYMM format.
This below given ABAP code helps you to convert GADTU: YYYYDDMM format   to CALMONTH : YYYYMM format.
In BI transformation write field routine in CALMONTH field to display date in this YYYYMM format.
DATA : L_GDATU TYPE tys_SC_1-GDATU.
CLEAR L_GDATU.
CONCATENATE SOURCE_FIELDS-GDATU0(4) SOURCE_FIELDS-GDATU4(2)
            INTO L_GDATU.
RESULT = L_GDATU.
Regards
Amit
Edited by: amit_sap_n on Jul 20, 2011 1:54 PM

Unsupported data conversion

I just upgrade my jdbc driver to "BEA's MS SQL Server Driver(Type 4)" in WLS 8.1. I got the following errors when executing rs.getTimestamp(1) with a NULL value fetched. Any idea?????
java.sql.SQLException: [BEA][SQLServer JDBC Driver]Unsupported data conversion.
at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.base.BaseData.unsupportedConversion(Unknown Source)
at weblogic.jdbc.base.BaseData.getTimestamp(Unknown Source)
at weblogic.jdbc.base.BaseResultSet.getTimestamp(Unknown Source)
at weblogic.jdbc.base.BaseResultSet.getTimestamp(Unknown Source)
at weblogic.jdbc.wrapper.ResultSet_weblogic_jdbc_base_BaseResultSet.getT
imestamp(Unknown Source)

Steven Yip wrote:
I tried to run the application under WLS8.1sp4 and shown that its version
is 3.40.19 (012727.007216.008716); however, the problem persists.Hi Steven. I think something else must be wrong. I can't duplicate it.
Here's a small program. Change it to your user, password, dbms etc,
and see if you can alter it to get it to show the problem.
What is your table definition?
thanks,
Joe
import java.io.*;
import java.util.*;
import java.net.*;
import java.sql.*;
import weblogic.common.*;
public class ddora
public static void main(String argv[])
throws Exception
Connection c = null;
try
java.util.Properties props = new java.util.Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("SID", "JOE");
Driver d = (Driver)Class.forName("weblogic.jdbc.oracle.OracleDriver").newInstance();
c = d.connect("jdbc:bea:oracle://JOE:1521", props);
System.out.println("Driver version is " + c.getMetaData().getDriverVersion());
Statement s = c.createStatement();
try{s.executeUpdate("drop table joe");} catch (Exception ignore){}
s.executeUpdate("create table joe "
+ " ( DATEOBJ DATE NULL)"
s.executeUpdate("insert into joe values(NULL)");
ResultSet rs = s.executeQuery("SELECT * FROM JOE");
rs.next();
rs.getTimestamp(1);
catch (Exception e)
{ e.printStackTrace(); }
finally
{ try {c.close();}catch (Exception e){} }

ECC 6.0 upgrade BDC, LSMW, IDOC checking stratergy

Hi Experts,
We have developed lot of LSMW involving BDC recordings, programs, IDOC and BAPI to load the data. We are now upgrading to ECC 6.0 and hence like to know the approach or check list whcih will help to check these objects and find out the differences or corrections to be done before moving to ECC 6.0 box.
can u please let me know a check list or any utility program that will help to identify the difference or issues? thx for response.
Ganesh

The best way to find out if everything works is to upgrade a test system and check your process. There's no tool available. LSMW itself didn't change but there may be changes in function modules you use.
Markus

Issue in transfer of data from ECC to APO

Hi All,
I have a requirement of transferring data from ECC to APO. I am using EXIT_SAPLCMAT_001 fro this purpose. The problem is, I need to transfer the data of a field that is not present in cif_matloc but present in /sapapo/matloc.
How should I proceed...Please help....this is an urgent requirement
Thanks & Regards,
SriLalitha

Hi,
you may want to go to the transaction /SAPAPO/SNP_SFT_PROF
Determine Forecast of Replenishment Lead Time
Use
In this field, you specify how the extended safety stock planning determines
the forecast of the replenishment
lead time (RLT). The following values are available:
Supply Chain
The system determines the RLT forecast using the supply chain structure by
adding the corresponding production, transportation, goods receipt, and goods
issue times. If there are alternative procurement options, the system always
takes the
longest
option into account.
Master Data
The system determines the RLT forecast from the location product master
data.
Master Data/ Supply Chain
First, the system determines the RLT forecast from the location product
master data. If no RLT forecast can be determined, the system determines the
forecast using the supply chain structure (as described under
Supply
Chain
Dependencies
You can retrieve the replenishment lead time forecast yourself by using the
GET_LEADTIME
method of the Business Add-In (BAdI) /SAPAPO/SNP_ADV_SFT.
Replenishment Lead Time in Calendar Days
Number of calendar days needed to obtain the product, including its
components, through in-house
production or external
procurement.
Use
The replenishment lead time (RLT) is used in the enhanced methods of safety
stock planning in Supply Network Planning (SNP). The goal of safety
stock planning is to comply with the specified service level, in order
to be prepared for unforeseen demand that may arise during the replenishment
lead time. The longer the RLT, the higher the planned safety stock level.
Dependencies
The field is taken into account by the system only if you have specified
master data or master data/supply chain in the RLT: Determine
Forecast field of the safety stock planning profile used.
Hope this helps.
The RLT from ECC is in MARC-WZEIT which is transferred to APO in structure /SAPAPO/MATIO field CHKHOR.
May be if you maintain the setting in the profile, you may get the value in RELDT.
Thanks.

Unable to extract the data from ECC 6.0 to PSA

Hello,
I'm trying to extract the data from ECC 6.0 data source name as 2LIS_11_VAHDR into BI 7.0
When i try to load Full Load into PSA , I'm getting following error message
Error Message: "DataSource 2LIS_11_VAHDR must be activated"
Actually the data source already active , I look at the datasource using T-code LBWE it is active.
In BI on datasource(2LIS_11_VAHDR) when i right click selected "Manage" system is giving throughing below error message
"Invalid DataStore object name /BIC/B0000043: Reason: No valid entry in table RSTS"
If anybody faced this error message please advise what i'm doing wrong?
Advance thanks

ECC 6.0 side
Delete the setup tables
Fill the data into setup tables
Schedule the job
I can see the data using RSA3 (2LIS_11_VAHDR) 1000 records
BI7.0(Service Pack 15)
Replicate the datasource in Production in Backgroud
Migrate Datasource 3.5 to 7.0 in Development
I did't migrate 3.5 to 7.0 in Production it's not allowing
When i try to schedule the InfoPakage it's giving error message "Data Source is not active"
I'm sure this problem relate to Data Source 3.5 to 7.0 convertion problem in production. In Development there is no problem because manually i convert the datasource 3.5 to 7.0
Thanks

GL Data Conversion from Legacy to Oracle EBS

Hi All,
I am tasked with converting legacy data into GL. I have worked on other conversions like supplier, AR and AP conversions but never worked on GL conversion, so I don't know how and where to start, what are the pre-requisites for entering data into gl_interface table how to ensure that data is correct in the .csv file etc.
Kindly request you all to guide me in right direction. Hope to hear from you all very soon!!! :)
Regards

Hi,
When you talk about GL-Data it is the trial balance to be loaded from legacy to oracle applications.
You can use Web-ADI to upload it ,the check list are
The balance for each account comibnation in the legacy system to be mapped to GL-Oracle code combination balance
With respect to open AR, AP Invoices if the invoices are converted using a control account for migration in GL then
the the balance transfered from AP,AR need not be reversed in GL from the source receivables and payables.
In case if the same account combination are for migrating the balances from AP,AR to GL ..Then the balances transferred from AP,AR should be reversed ..so that it does not affect the TB-GL-Balance
Finally ensure that the balance for the TB-tallys with your legacy system and upload it using Web-ADI ,import and
review and post it.
Hope this points helps your GL-Data conversion.
Regards,
Ramaa

Data conversion strategy for new SOB

Dear Viewers
on 11.5.10
We are creating a new SOB with a change in currency from Feb-11 as this is the requirement
For the same, we need to do data conversion.
I have a confusion for Purchase Orders and Sales Orders
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done?
What if a return has to be made moving forward in FEB-11 under new SOB
Sales Orders:
Open sales orders will be converted, that is the ones that have been entered and not yet booked.
Users have been requested to clear off the Sales order lines which are already pick confirmed but not yet shipped, hence they will be shipped and interfaced to AR
For the Sales orders that have been booked, those lines that are not yet processed further will also be converted.
Now what if a receipt comes after feb 11, how to handle this as the sales order wiould not have been converted?
Please give your advise on the data migration strategy for PO`s and SO's.
Please do add any point that may have been missed by me
Appreciate your help
Thanks
Emm

Hi David,
for master data conversion you can use LSMW and the RE-FX BAPIs. (please refer to SAP note [782947|https://service.sap.com/sap/support/notes/782947] ).
Regards, Franz

Data conversion for new sob

Dear Viewers
on 11.5.10
We are creating a new SOB with a change in currency from Feb-11 as this is the requirement
For the same, we need to do data conversion.
I have a confusion for Purchase Orders and Sales Orders
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done?
What if a return has to be made moving forward in FEB-11 under new SOB
Sales Orders:
Open sales orders will be converted, that is the ones that have been entered and not yet booked.
Users have been requested to clear off the Sales order lines which are already pick confirmed but not yet shipped, hence they will be shipped and interfaced to AR
For the Sales orders that have been booked, those lines that are not yet processed further will also be converted.
Now what if a receipt comes after feb 11, how to handle this as the sales order wiould not have been converted?
Please give your advise on the data migration strategy for PO`s and SO's.
Please do add any point that may have been missed by me
Appreciate your help
Thanks
Emm

emm wrote:
Purchase Orders:
Open purchase orders will be converted, means the unfulfilled PO`s i.e the ones not received and are fully open.
The PO`s which have been recieved but not delivered, Requested the users to clear the intransit receipts.
The PO's which are partially received, what to be done for them?
If a PO is fully received and Delivered will not me converted to the new SOB as its not an open PO
but If invoice comes after Feb-11, than how the matching will be done? <br>Business needs to take a decision whether they are fine with matching the POs manually (i.e. referring the documents and verify), in this case you may capture the PO information in a DFF in the Invoice distribution. Otherwise if it has to be converted identifying the POs under this scenario, you may consider converting those maintaining receipt close tolerance as 100% and matching type as 2 -way (again business approval needed to handle audit issues) in order to avoid the receipts/delivery conversion etc.<br>
What if a return has to be made moving forward in FEB-11 under new SOB<br>Ideally returns can be done using Miscellaneous/Account Alias Issues specifying the appropriate transaction reasons to clarify the scenario.<br>

Screens not working in ECC 6 after upgradation from 4.6c.

Hi,
The custom developed screens which where developed in 4.6c version is not working properly in ECC 6 after upgradation.Do i have to make any more changes for this .? If anyone have an idea please help me in this issue.The custom developed things are an extended functionality we have done to r/3.
Regards,
jinesh kumar c.

Hi,
Check the Transportatation Logs in STMS for the programs/screens and check whether they are successfully tranported or not?
Because some times we get Dynpro errors for transportation of the screens.
Reward if useful.
regards,
Anji

Data conversion ECC 6.0 Upgrade

Similar Messages

Maybe you are looking for