LRAW data Conversion during Unicode Conversion

Hi,
We have upgraded our 46C MDMP system to Unicode system.
After conversion we found that some of the tables with field of LRAW type are having conversion issue.
In 46C system, Russian data which enetered in the MS Cyrillic (Code page 1504), is converted to code page 1500 after unicode conversion.
We have not found any entries for this table in vocabulary, reprocess log or in SUMG.
For example table STXL. This table contains Purchase order text for the material.
Report HRUU_CONVERT_IN_UNICODE does not shows LRAW data field for conversion.
Can you suggest how LRAW data can be converted from 1500 to 1504 code page.
Thanks and Regards
Rahul

Hi Rahul,
STXL is a language dependent INDX type table. Hence SPUMG will not scan this one with the default settings.
Please have a look at the description of INDX type table handling in the Unicode conversion Guide.
In the Unicode system, you can use UMG_ADJUST_STXL for the conversion.
However please be aware of the restrictions:
Once you have decided about the code page and converted the object, this cannot be reverted !
Therefore it is highly recommended to check the display mode first and in addition test it extensively on a sandbox system !
Best regards,
Nils Buerckel
SAP AG

Similar Messages

  • Error during unicode conversion

    Dear all,
    we are facing one issue during unicode conversion. the code is as follows:
    FIELD-SYMBOLS : <n> TYPE X,
                                 <c> TYPE C.
    DATA : a TYPE i.
    DATA : x TYPE x.
    MOVE <n> TO a.
    a = a + 22.
    MOVE a TO x.
    ASSIGN x TO <c> CASTING TYPE c
    and we are getting the following error:
    ERROR : the length of "X" in bytes must be a multiple of the size of a Unicode character (regardless of the size of the unicode character
    please guide on how this can be resolved in ECC.
    Regards,
    N.Jain

    Hi,
    here is some code to do it:
    FIELD-SYMBOLS : <n> TYPE x,
                    <c> TYPE c.
    DATA : a TYPE i.
    DATA : x TYPE x.
    MOVE <n> TO a.
    a = a + 22.
    MOVE a TO x.
    DATA:
      buffer TYPE xstring,
      conv TYPE REF TO cl_abap_conv_in_ce,
      x_char.
    buffer = x.
    conv = cl_abap_conv_in_ce=>create(
           encoding = 'NON-UNICODE'
           input = buffer
    CALL METHOD conv->read(
      EXPORTING
        n    = 1
      IMPORTING
        data = x_char
    ASSIGN x_char TO <c>.
    Regards
    Walter Habich
    Edited by: Walter Habich on Jun 10, 2008 4:09 PM

  • Usage of Conversion Classes During Unicode Conversion

    Hi,
    I have code
    "TRANSLATE  BBKF-SGTXT FROM CODE PAGE '0100' TO '0120'"  Now During Unicode i need to Use the Conversion classes
    Can any one help to proceede further on this
    Actually I am using  CL_ABAP_CONV_OUT_CE and I am getting the Data in Binary Format But I want that to be in Character format can any one suggest me
    Thanks & Regards,
    Prasad

    Do you have an EBCDIC system with code page 0100? (check it using SNLS transaction)
    In that case, CL_ABAP_CONV_OUT_CE is okay.
    After having converted to code page 0120 (into xstring), here is how to cast xstring variable to character.
    DATA x TYPE x LENGTH 800. " so that to compile, x length
                              " must be a multiple of 4 (don't ask why)
    FIELD-SYMBOLS <c> TYPE c.
    x = xstring. "make sure x is long enough
    ASSIGN x TO <c> CASTING.
    BBKF-SGTXT = <c>.

  • Data conversion for New GL - Going live during fiscal year

    Hi Experts,
    My client is going live on Oct 1 (fiscal year in Jan -Dec). So for data conversion we need to load P&L and BalanceSheet as of Sept 30, 2009.  I need your help to resolve few open issues. (we have activated Doc Splitting with Zero Balance and Segment )
    1) When we load P&L balances - how can I assign Profit Centers to all these P&L iitems .  
    2) What is the procedure (best practices) to assign Profit Centers to all the Balance Sheet items since we are going live during Fiscal Year
    3) When we process open items  (AR, AP) in month of October how the Profit Center assignment will work?
    (My client will be using Profit /Cost center terminology first time, so we need to map all the B&S and PnL items to Profit centers)
    4) What is the best way to map all the Balance Sheet GL accounts to Profit Centers.
    Sorry for asking too many questions. Any help would me very much appreciated.
    Thanks,
    Sam

    1) When we load P&L balances - how can I assign Profit Centers to all these P&L iitems .
    Each P&L account balance has to be upload with cost centre, then automatically PC will be triggered.
    2) What is the procedure (best practices) to assign Profit Centers to all the Balance Sheet items since we are going live during Fiscal Year
    Let client decide the profit centre for balance sheet items, since they knows which balance relates to which pc
    3) When we process open items (AR, AP) in month of October how the Profit Center assignment will work?
    While uploading AR,AP balances, each line item to be uploaded with profit centre, automatically in october PC assignment will work.
    (My client will be using Profit /Cost center terminology first time, so we need to map all the B&S and PnL items to Profit centers)
    4) What is the best way to map all the Balance Sheet GL accounts to Profit Centers
    Try to identify each balance sheet gl balance to each profit centre, this will help in future reports. otherwise put in common pc

  • Error during Unicode Conversion at DDNTF table

    Hello
    We are doing a Unicode Conversion for our CRT systems. This system now
    is a SAP CRM 7.0 SR1 ABAP.
    We have performed preparatory steps (SPUMG, checks, updating R3load,
    R3ldctl, R3szchk, dboralib, ...),
    but when we start Import process we get an error in SAPSDIC package.
    The error looks like:
    *************************+
    (RTF) ########## WARNING ###########
    Without ORDER BY PRIMARY KEY the exported data may be unusable
    for some databases
    (EXP) INFO: table DDNTF will be exported with sorting
    (RSCP) ERROR: 'DDNTF' in UMGCCTL: Guess has illegal value.
    (RSCP) WARN: DDNTF: Missing in UMGSTAT,
    ERROR in nametab conversion
    conversion of nametab table 'DDNTF ':
    rscpMCStartTab: rc = 128
    (CNV) ERROR: data conversion failed. rc = 2
    (DB) INFO: disconnected from DB
    /usr/sap/CRT/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/CRT/SYS/exe/run/R3load: END OF LOG: 20091229193651
    Any idea??
    Thanks in advance
    Regards

    Yes I executed this Report using Menu Tool Bar.
    The first execution gave me some errors regarding some tables existing at database level but  not in DDIC. We ignored this errrors because those tables are not important.
    But the last try, we decided solve this inconsistencies deleteting those tables at database level, repeting report RADUCNT (in this case no errors appeared) and repeting the export with the same error..
    Now, we have seen in Tabscript STATUS of SPUMG there are some errors regarding DDNTF inconsistency found at table control. Reason 4.  But this reason means that faillback codepage missing at table control for this table. But as far I know, I can't fill failbak field for this kind of table...
    So know I'm reseting SPUMG, and reestarting again..
    But I don't understand what is the problem
    In a few minutes I will you inform about results
    Meanwhile is anybody have any suggestion or idea... please let me know
    Thanks!

  • 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

  • Data conversion of open checks

    Hello,
    We are preparing our data conversions for a new implementation of SAP in the US. A question came up as to whether we should enter check masters for checks we have printed and mailed to our vendors but haven't been cashed at the time of go-live. The other option would be to put the balance of these open checks into a GL account and manually enter journal entries when they are cashed.
    Our normal business process will be to use FCHR to process a file we receive from our bank with cashed checks. If we don't create check masters for our open checks, then FCHR will not be able to automatically process cashed checks from before go-live.
    My question: is it best practice to load these open checks during the data conversion into SAP so that FCHR will clear them out, or is this normally handled as an exception using manual journal entries?
    And, if it is best practice to load the check masters in SAP, what transaction code would we use to enter the open checks?
    Thanks,
    JB

    HI
    We have developed an ABAP program to set deletion indicatior in PO in mass. You can do the same by consulting your ABAPER.
    Regards
    Anil

  • FICO Data Conversions clarifications

    Hi,
    I am currently working on data conversion project. We have our FY from April to March and we are going live on June 01. I am trying to analyse the FICO objects. I have seen many conversations here but confused between balances and open items. I am trying to use ABAP programs instead of LSMW as much as possible
    Master Data:
    1) GL Master Data
    2) AP Vendor Master Data
    3) AR Customer Master Data
    4) FA Master Data
    5) Cost Centers
    6) Profit Centers
    Transaction Data:
    Note that client wants to use only one offsetting conversion account instead of one account each for GL, AP, AR, FA etc
    7) GL Balances
         what is the difference between balances and open items here and how do we post them (can i use f-02 for both) and document types?
         lets say i have GL 600100 which has a balance of $5000. If i want to post it during data conversion, should i post it as Dr 600100 Cr 700100 (this is a        offsetting account used only for conversion)
         how do you post an GL Open Items and what would be the accounting entries
    8) Vendor Balances
         what is the difference between Vendor balances and Vendor Open items.
         lets say if i have 10 invoices pending payment for a vendor 10000, is the posting to KR doc type as Cr 10000 (vendor) Dr 700100 (this is a offsetting account used only for conversion) correct?
    9) Customer Balances
         what is the difference between Customer balances and Customer Open items.
         lets say if i have 10 invoices pending payment by a customer 80000, is the posting to DR doc type as Dr 80000 (Customer) Cr 700100 (this is a offsetting account used only for conversion) correct?
    10) Historical Data
         If the client asks us to post data from April 1 until May 31, what is the best approach, also here we are circumventing few things such as
         If there is a GR is done but not Invoiced, then these will be just posted as regular invoices (KR) instead of PO - GR - IV sequence
         If there is Invoice (PO based ones) but not paid, then these will be considered as regular open invoices (KR) as above
         like wise for O2C invoices too
    I am trying to understand if i missing anything and if i have to follow any sequence. Appreciate if you guys can help with an example and if if i am missing any objects here...
    Thanks
    Shriya

    Follow this and use LSMW.
    LSMW for Functional Consultants in simple step-by-step way
    Refer this to understand the basic:
    Data Migration Part - Reg.
    Regarding your questions: It does not matter whether you use single or five or six offsetting account. You should aware that at the end of the transfer your offsetting accounting balance should be zero.
    You take trail balance (forget about the vendors / customers as you load them as open items)
    All debit balances you debit in SAP and Credit the offsetting account. All credits you credit in SAP and debit offsetting account. Usually, GL open items would not be loaded, it is only balances. Open items are only for vendors and customers.
    Note: You should NOT load tax line on the customer / vendor invoices, as they are already accounted for in the GL balances. Otherwise, your Migration account would never be zero.
    For Assets, you need to load asset sub-ledger data separately through AS91 and GL balances separately. Use OAMK to set and reset the reconciliation accounts of assets. Once you loaded asset values, put them as reconciliation accounts and nobody should touch them.
    You only load historical data line items of vendors or customers. You do  not post goods or invoices receipts again from MM. Mostly, what you can upload is open purchase orders.
    Hope this helps.
    Regards,
    Ravi

  • How to master data conversion in ABAP/4 programming

    I only know there is no special syntax to data conversion and put an "=" between destination data object and source object.
    But I don't know whether the conversion is legal or not.
    Who can help me?

    For conversions between structured fields or a structured field and a singlefield , flat structures were previously treated like C fileds, With the implementation of Unicode this approach has become too error prone, since it is not clear if programs can be executed with platform-independent semantics.
    aRs

  • Char to Date conversion problem - again!

    Hi,
    in order to make date selection 'more attractive' for end users I have been tasked with presenting a text field with 'January 2010', 'February 2010' etc to the end users for their prompts.
    So far so easy...
    However, I then need to use the values to derive either dates, or years, or date numbers.
    This all works fine during development when I am testing using a default parameter thus; -
    '@{MYMONTHYEAR}{September 2010}' - which is fed into various very complex functions.
    BUT - when I try to use the report in conjunction with the parameter I get; -
    'The evaluation of the index 6 expression on row count -1 failed. [nQSError: 46046] Datetime value 2010/09/01 does not match the specifiied format'
    However, cast('2010/09/01' as date) works fine... and convoluted as the logic of my functions is, the fundamental char to date conversion is exactly in this format.
    Anyone shed any light on this, give me a guaranteed way to handle char to date conversion?
    thanks,
    Robert.

    Hi,
    I tried your workaround case when 1=2... but I still get the same error....
    Not when I have the format from my default value, but when I get the value from a dashboard prompt in a page.
    The full error is; -
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 46046] Datetime value 2012/09/01 does not match the specified format. (HY000)
    SQL Issued: SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10, s_11, s_12, s_13, s_14, s_15, s_16, s_17, s_18, s_19, s_20, s_21, s_22, s_23, s_24, s_25, s_26, s_27, s_28, s_29, s_30, s_31, s_32, s_33, s_34, s_35, s_36, s_37, s_38, s_39, s_40, s_41, s_42, s_43, s_44, s_45, s_46, s_47, s_48, s_49, s_50, s_51, s_52, s_53, s_54, s_55, s_56, s_57 FROM ( SELECT 0 s_0, "Vivaldi Detail"."Product Global Hierarchy"."Tobacco Category Groups" s_1, "Vivaldi Detail"."Product Global Hierarchy"."Tobacco Category" s_2, "Vivaldi Detail"."Product Global Hierarchy"."Total Tobacco Products" s_3, FILTER("Vivaldi Detail"."Fact Sales Detail"."SOM %" USING ("Vivaldi Detail"."Time"."Year" =cast((cast(right('September 2012',4) as integer)-1) as char(4)))) s_4, FILTER("Vivaldi Detail"."Fact Sales Detail"."SOM %" USING ("Vivaldi Detail"."Time"."Year" =cast((cast(right('September 2012',4) as integer)-2) as char(4)))) s_5, FILTER("Vivaldi Detail"."Fact Sales Detail"."SOM %" USING ("Vivaldi Detail"."Time"."Year" =cast((cast(right('September 2012',4) as integer)-3) as char(4)))) s_6, FILTER(FILTER("Vivaldi Detail"."Fact Sales Detail"."SOM %" USING ("Vivaldi Detail"."Time"."Year" =cast((cast(right('September 2012',4) as integer)-1) as char))) USING "Vivaldi Detail"."Time"."Month Number" <=month(CASE WHEN 1=2 THEN CURRENT_DATE ELSE cast(right('September 2012',4)||'/'||CASE left('September 2012',LOCATE(' ','September 2012')-1) WHEN 'January' THEN '01/01' WHEN 'February' then '02/01' when 'March' then '03/01' when 'April' then '04/01' when 'May' then '05/01' when 'June' then '06/01' when 'July' then '07/01' when 'August' then '08/01' when 'September' then '09/01' when 'October' then '10/01' when 'November' then '11/01' ELSE '12/01' END as date)END)) s_7, FILTER(FILTER("Vivaldi Detail"."Fact Sales Detail"."SOM %" USING ("Vivaldi Detail"."Time"."Year" =right('September 2012',4))) USING "Vivaldi Detail"."Time"."Month Number" <=month(CASE WHEN 1=2 THEN CURRENT_DATE ELSE cast(right('September 2012',4)||'/'||CASE left('September 2012',LOCATE(' ','September 2012')-1) WHEN 'January' THEN '01/01' WHEN 'February' then '02/01' when A brief sample of a typical formula which causes this is; -
    FILTER(FILTER(FILTER("Fact Sales Detail"."SOM %" USING ("Time"."Year" =   right('@{MYEAR}{September 2010}',4))) USING ("Time"."Month Number" = 2)) USING "Time"."Month Number" <= month(CASE WHEN 1=2 THEN CURRENT_DATE ELSE cast(right('@{MYEAR}{September 2010}',4)||'/'||CASE left('@{MYEAR}{September 2010}',  LOCATE(' ','@{MYEAR}{September 2010}') -1) WHEN 'January' THEN '01/01'  WHEN 'February' then '02/01' when 'March' then '03/01' when 'April' then '04/01' when 'May' then '05/01' when 'June' then '06/01' when 'July' then '07/01' when 'August' then '08/01' when 'September' then '09/01' when 'October' then '10/01' when 'November' then '11/01' ELSE '12/01' END as date)  END    ))The September 2010 default being EXACTLY what is selected from the dashboard prompt when testing. It does not error, but returns no data in isolation, but when when from the prompt it errors...
    And the date format, if fed into a cast ('2012/09/01' as date) does not error.
    Anyone help - this is really driving me mad, syntax is good - it should work!!!
    thanks,
    Robert.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Ssis - data conversion

    i am getting error in data flow task as below, how to fix it.
     Error: Column "A12" cannot convert between unicode and non-unicode string data types.

    Hi,
    Did you try using a data conversion task??
    check :
    http://www.mssqltips.com/sqlservertip/1393/import-excel-unicode-data-with-sql-server-integration-services/
    http://www.mssqltips.com/sqlservertip/3046/sql-server-integration-services-data-type-conversion-testing/
    Thanks,
    Jay
    <If the post was helpful mark as 'Helpful' and if the post answered your query, mark as 'Answered'>

  • 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>

  • Data Conversion in SAP E-Recruiting.

    Hi SAP E-Recruiters,
    Our client is using a Legacy application for recruiting candidates where it has 5000 candidates data base (internal and external candidates' applications).
    Now they are asking for movement of this whole data to the newly implementing SAP E-recruiting system. We are exploring various data conversion methods and found that BDC, LSMW will not work for E-recruiting data upload as we have every thing in BSP/Web Dynpro pages here.
    We need your help in finding a solution for moving this data from legacy to SAP E-Recruiting. Pls do the needful.
    Thanks,
    Sudheer

    Sudheer,
    So far there are no SAP delivered migration methods or BAPI's available conversion of candidates/applications, as you have already specified BDC's wouldnot work. Internal candidates always can be brought over in eRecruitment with integration techniques between PA and eRecruit depending upon the landscape.
    However, for external candidates custom conversion programs have to be written by making use of methods/function modules that are used in BSP/WebDynpro.
    regards
    Sridhar

Maybe you are looking for