Re:Uploading legacy data

Dear friends:
I am doing uploading for 500 records using LSMW.
After uploading i am unable to edit my Holder with respect of their position.But i checked through PA30,records are updated and having all information.
Again i tried through PP01-Relation ship infotype-1001
Its working fine and updating in OM.
Even i run all the reports like RHINTEE00.01,10,20,30....
So please Someone could raise a better solution for this...
Thanks&Regards:
Kumar Reddy

pleas check T77S0 Table
PLOGI ORGA intergration switch is X means on when you run the RHINTEE00.01,10,20,30 programs.
If not make sure switch is on and run the RHINTEE00.01,10,20,30 these programs again and see
Best Regards

Similar Messages

Upload legacy data into SAP

Hi experts,
I have to upload legacy data into SAP by using eCATT recording Transaction. For doing this I have completed Test script in tcode SECATT. After this what I have to do.. How can I attach my legacy file.. Can anyone help me. ..Its really urgent
Thanks in advance

Hi,
There are a series of weblogs in this area. Check them out, I think there are 8 in a series:
/people/sapna.modi/blog/2006/04/10/ecatt--an-introduction-part-i
cheers
Aveek

Please send detail steps for uploading legacy data

Hi friends,
please send detail steps for uploading legacy data
Thanking u in advance,
Diwa.

HI U CAN USE LSMW TO UPLOAD LEGACY DATA
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which.
LSMW Steps For Data Migration
How to develop a lsmw for data migration for va01 or xk01 transaction?
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
    Execute.
3. Maintain object attributes.
    Execute
    select Batch Input recording
    goto->Recording overview
    create
    recording name.
    enter transaction code.
    start recording
    do recording as per ur choice.
    save + back.
    enter recording name in lsmw screen.
    save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
    Here you have to enter the name of internal table.
    display change
    create
    save + back
3. MAINTAIN SOURCE FIELDS.
    display change
    select structure
    source_fields->copy fields.
    a dialogue window will come .
    select -> from data file
    apply source fields
    enter No. of fields
    length of fields
    attach file
    save + back
4. MAINTAIN STRUCTURE RELATIONS
    display change
    save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
    display change
    click on source field, select exact field from structue and enter
    repeat these steps for all fields.
    save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
    execute
    save + back
7. SPECIFY FILES.
    display change
    click on legacy data
    attah flat file
    give description
    select tabulatore
    enter
    save + back
8. ASSIGN FILE
    execute
    display change
    save + back
9. IMPORT DATA.
    execute
    display change
    save + back
10. DISPLAY IMPORTED DATA
      enter ok, it willl show records only.
      back
11. CONVERT DATA
      execute
      display change
      save + back
12. DISPLAY CONVERTED DATA
      execute
      display change
      save + back
13. CREATE BATCH INPUT SESSION
      tick keep batch input folder
      F8
      back
14. RUN BATCH INPUT SESSION.
      sm35 will come
      Object name will be shown here
      select object & process

Upload legacy data

Hi experts,
I have to upload legacy data into SAP by using eCATT recording Transaction. For doing this I have completed Test script in tcode SECATT. After this what I have to do.. How can I attach my legacy file.. Can anyone help me. ..Its really urgent

hi silviya,
check these threads...
/people/sapna.modi/blog/2006/04/10/ecatt-scripts-creation--sapgui-mode-part-iii
Steps in ECATT
uploading data from external files with multiple entries in ecatt
ecatt upload
Error in executing eCATT GUI Script
hope these help,
do reward if it helps,
priya.

Problem when upload legacy data

Hi all,
I've faced a problem when uploading asset legacy data (AS91) for customer. My customer have started depreciation on May 21, 2009, and I set transfer date is November 30, 2010. So SAP doesn't calculate right planned value for December, 2010. I think that problem related to the first month depreciation. It calculated full month for depreciation (instead of from May 21) and change the planned value for December 2010. So I want SAP just calculate 11 days depreciation for May 2009. How can I config to do this?
Thanks in advance!

Hi,
Check in the asset master Opening Start Date for depreciation.. If it is under open mode change that date and see asset explorer for depreciation values.
Thanks,
Padmaja

Upload 3 year old legacy data into ECC

I need to upload legacy data (purchase orders/FI line items from accounting entries) of 2007/8/9 into ECC today through LSMW. Can i do this?Do I need to open posting periods of 2007/8/9. How to do that?
Does anything have to be done using MMPV or MMRV??

Hi,
No this is not possible/recommended. The recommended practice is to upload trial balance as on the cutover date.
It means...
1) If the cutover date is similar to year end, then only balance sheet items which are open items as on that date
2) If the cutover date is other than year end date, then all open items of balance sheet accounts and year to date balance of profit and loss account.
Best Regards,
Madhu

Steps to prepare and upload legacy master data excel files into SAP?

Hi abap experts,
We have brand new installed ECC system somehow configured but with no master or transaction data loaded .It is new empty system....We also have some legacy data in excel files...We want to start loading some data into the SAP sandbox step by step and to see how they work...test some transactions see if the loaded data are good etc initial tests.
Few questions here are raised:
-Can someone tell me what is the process of loading this data into SAP system?
-Should this excel file must me reworked prepared somehow(fields, columns etc) in order to be ready for upload to SAP??
-Users asked me how to prepared their legacy excel files so they can be ready in SAP format for upload.?Is this an abaper job or it is a functional guy job?
-Or should the excel files be converted to .txt files and then imported to SAP?Does it really make some difference if files are in excel or .txt format?
-Should the Abaper determine the structure of those excel file(to be ready for upload ) and if yes, what are the technical rules here ?
-What tools should be used for this initial data loads? CATT , Lsmw , batch input or something else?
-At which point we should test the data?I guess after the initial load?
-What tools are used in all steps before...
-If someone can provide me with step by step scenario or guide of loading some kind of initial master data - from .xls file alignment to the real upload - this will be great..
You can email me some upload guide or some excel/txt file examples and screenshots documents to excersize....
Your help is appreciated it.!
Jon

hi,
excel sheet uploading:
http://www.sap-img.com/abap/upload-direct-excel.htm
http://www.sap-img.com/abap/excel_upload_alternative-kcd-excel-ole-to-int-convert.htm
http://www.sapdevelopment.co.uk/file/file_upexcel.htm
http://www.sapdevelopment.co.uk/ms/mshome.htm

Legacy data upload for Training & Event Management

As per the requirement, the legacy /history data for training events is to be uploaded in the system. To start the process the data templates were prepared for uploading training objects like D (Business Event Group), L (Business Event Type) and E (Business Event) and these were uploaded. Also the relationships A003 between D & L and A020 between E & D were also maintained. As a part of training history the attendees were also maintained (uploaded) using the relationship A025 between E & P objects. However when we go to PSV2, then the tree structure does not reflect the name of the person who attended the event.
Please suggest and advice.

Hi Nitin,
I have a query regarding the Legacy data. I wanted to ask you that how did you structure the Historical BEG and BET.
Did you create different BEG for the Current and the Legacy data.
But in that case there could be BET's common in both the current and legacy data with different object ids
For e.g. Under Current BEG and Historical BEG I may have a BET Technical Programmes with diffrent Ids say 60000000 and 60987655. This may create a problem when running reports.
Pls tell me strategy that you have used for creating the catalog.
Regards
Yashika Kaka

Upload master data tables from legacy systems with XI on BW

Hi developers,
Can you help me to reconstruct the steps necessary for upload master data, deriving by legacy tables, on BW system using XI?
Thanks in advance

Hi,
see the following link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/52398597-0601-0010-868a-fd95f8061d85
Rgs
Antonino

How to upload the data from legacy system database to SAP data base

Hi.
We are doing analysis of Legacy system and which needs to be converted to SAP system i.e. SAP implementation.
I just want to know , how we migrate the existing whole data( from legacy system) into SAP system.
and which method is the best method to use data migration from legacy to SAP system if data legacy data amount is huge.
Please suggest me.
Thanks.

Hi
We can either use the BDC or BAPI or LSMW or Direct Input techiniques for the data transfers.
The combination of both Session and Call transaction can be used to achieve this that includes the error handling also. This invloves the screen interaction.
These days, BAPIs are used to overvome some upgrade problems. For easy upgradation, we cna go for BAPIs. Here ther is no screen intercation.
LSMW mainly used for master data transfers using some standrad programs.
As per your client or company desicions we can choose any of them.
Please refer to these links for more understanding -
BDC Vs LSMW -
BDC VS LSMW
BDC Vs BAPI -
BDC VS LSMW
Thanks & Regards,
Chandralekha.

What is the Tcodes for Uploading of data using BDC & CATT

PP members:
I was going through the cutover activities , and what I understood is we transfer all the legacy system data into SAP before going live
The data upload follows certain steps (depends on the organizational design load strategies)
First we upload all the master data ( material master, BOM, W/C's & Routings)
Then the transaction data ( Ideally speaking, there should no open orders i.e. WIP as on the day of cutoff )
If the WIP (Work in Process) is unavoidable then the materials consumed shall be treated as materials of the previous stage and necessary adjustments shall be made after cutover day
At this point, I could not able to understand what does the author mean materials of the previous stage
Now comming to the uploading of data into SAP from legacy system, we use tools like LSMW, CATT & BDC
Is it a must to use only LSMW tool to upload master data or any other upload tools are fine
Lastly,. I am not sure about the Tcode of CATT & BDC
Summary of the questions:
1.What does the author mean material of previous stage, for WIP materials during cutover activities
2. Is it mandatory to use only LSMW tool for uploading for master data
3. What are the Tcodes for upload tools CATT & BDC ?
Thanks for your time
Suren R

Dear,
1.What does the author mean material of previous stage, for WIP materials during cutover activities - as i understood, what is the stage of material..like it must have gone through 2 work centers and other 2 is left. i.e. you need to create Production order with only 2 operation as other 2 is already over. - usually it is done in such a way that we will create Production order and confirm till 2 operations and WIp is calculated so thatb FI will tally the books in SAP and lagacy.
2. Is it mandatory to use only LSMW tool for uploading for master data - no you can use any tool as required and suits yr requirement
3. What are the Tcodes for upload tools CATT & BDC- BDC through a prog in SE38. CATT through - SCEM.

How to upload the data to 'abzu' transaction using bapi

Hi Experts ,
I need to upload the data to the (asset write up ) transaction 'abzu' and please help me inthis regard
i found some bapi's like below
BAPI_FIXEDASSET_CHANGE Changes an Asset
BAPI_FIXEDASSET_CREATE Creates an Asset
BAPI_FIXEDASSET_CREATE1 Creates an Asset
BAPI_FIXEDASSET_GETDETAIL Display Detailed Information on a Fixed Asset
BAPI_FIXEDASSET_GETLIST Information on Selected Assets
BAPI_FIXEDASSET_OVRTAKE_CREATE BAPI for Legacy Data Transfer
BAPI_FIXEDASSET_TEST BAPI for Legacy Data Transfer
i tried with this bapies but unable to do the transfer the data ,
please help me ,
which is the exactly suitable bapi for uploading the data to 'abzu' transaction
i apriciate you advanced ,
please give me the exactly solution for this ,
Regards.,

Hi Experts ,
I need to upload the data to the (asset write up ) transaction 'abzu' and please help me inthis regard
i found some bapi's like below
BAPI_FIXEDASSET_CHANGE Changes an Asset
BAPI_FIXEDASSET_CREATE Creates an Asset
BAPI_FIXEDASSET_CREATE1 Creates an Asset
BAPI_FIXEDASSET_GETDETAIL Display Detailed Information on a Fixed Asset
BAPI_FIXEDASSET_GETLIST Information on Selected Assets
BAPI_FIXEDASSET_OVRTAKE_CREATE BAPI for Legacy Data Transfer
BAPI_FIXEDASSET_TEST BAPI for Legacy Data Transfer
i tried with this bapies but unable to do the transfer the data ,
please help me ,
which is the exactly suitable bapi for uploading the data to 'abzu' transaction
i apriciate you advanced ,
please give me the exactly solution for this ,
Regards.,

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
 MATNR LIKE MARA-MATNR,
 MBRSH LIKE MARA-MBRSH, "Industry Sector
 MTART LIKE MARA-MTART, "Matl Type
 WERKS LIKE MARD-WERKS, "Plant
 LGORT LIKE MARD-LGORT, "Storage location
 VKORG LIKE MVKE-VKORG,
 VTWEG LIKE MVKE-VTWEG,
 MAKTX LIKE MAKT-MAKTX, "Matl Desc.
 MEINS LIKE MARA-MEINS, "Base UOM
 MATKL LIKE MARA-MATKL, "Matl.Grp
* BISMT LIKE MARA-BISMT,
 SPART LIKE MARA-SPART, "Division
* BRGEW LIKE MARA-BRGEW, "Gross weight
 GROES LIKE MARA-GROES,
 FERTH LIKE MARA-FERTH,
 ZEINR LIKE MARA-ZEINR,
 TAXKM1 LIKE MLAN-TAXM1,
 TAXKM2 LIKE MLAN-TAXM2,
 TAXKM3 LIKE MLAN-TAXM3,
 TAXKM4 LIKE MLAN-TAXM4,
 KTGRM LIKE MVKE-KTGRM,
* GEWEI LIKE MARA-GEWEI, "Weight unit
* NTGEW LIKE MARA-NTGEW, "Net weight
* KLART LIKE RMCLF-KLART,
 MTVFP LIKE MARC-MTVFP, "Availibility Check
* XGCHP LIKE MARA-XGCHP,
 XCHPF LIKE MARA-XCHPF, "Batch Management
 TRAGR LIKE MARA-TRAGR,
 LADGR TYPE MARC-LADGR,
 VPRSV LIKE MBEW-VPRSV, "Price Control
 VERPR LIKE MBEW-VERPR,
* SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
* $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
* $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
 IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
* $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
 MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
* DYNPRO_NUMBER = SYST-DYNNR
 FIELD_NAME = 'P_FILE'
 IMPORTING
 FILE_NAME = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*& Form data_fetch_to_xls
* text
* --> p1 text
* <-- p2 text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 EXPORTING
 FILENAME = P_FILE
 I_BEGIN_COL = 1
 I_BEGIN_ROW = 2
 I_END_COL = 25
 I_END_ROW = 2
 TABLES
 INTERN = IT_EXCEL
 EXCEPTIONS
 INCONSISTENT_PARAMETERS = 1
 UPLOAD_OLE = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
 /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
 IF NOT IT_EXCEL[] IS INITIAL.
 CLEAR LEGACY_DATA.
 REFRESH LEGACY_DATA[].
 LOOP AT IT_EXCEL.
 IT_EXCEL_DUMMY = IT_EXCEL.
 AT NEW COL.
 CASE IT_EXCEL_DUMMY-COL.
 WHEN 1.
 LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 2.
 LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 3.
 LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 4.
 LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 5.
 LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 6.
 LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 7.
 LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 8.
 LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
 WHEN 9.
 LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
 WHEN 10.
 LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
 WHEN 11.
 LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 12.
 LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
 WHEN 13.
 LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
 WHEN 14.
 LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
 WHEN 15.
 LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 16.
 LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 17.
 LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 18.
 LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 19.
 LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 20.
 LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
 WHEN 21.
 LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 22.
 LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 23.
 LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
 WHEN 24.
 LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
 WHEN 25.
 LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
 APPEND LEGACY_DATA.
 CLEAR LEGACY_DATA.
 ENDCASE.
 ENDAT.
 AT END OF ROW.
 ENDAT.
 ENDLOOP.
 ENDIF.
ENDIF.
ENDFORM. " data_fetch_to_xls
*& Form insertion
* text
* --> p1 text
* <-- p2 text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM. " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

Regarding Upload of data into SAP from Application server using DATA SETS

Hi all,
I have a problem when uploading data that is application server [.txt file] into SAP using OPEN DATA SET,READ DATA SET & CLOSE DATA SET it is now going to dump. The file is actually splits the fields by using Tab Delimiter.
During uploading some junk values are coming with '#' so it going to dump and giving follow type of error.
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Unable to interpret "#0#0#0#0#0#0#0#" as a number.
Can any one solve the above issue as i need it urgently.
Thanks in advance.
Thanks & Regards,
Rayeezuddin.

Hi Hielman,
Thnaks for that reply and for effort you are putting to solve my issue.
I had done the same thing what u have posted prior to your reply but still i am getting dump.
FORM f_get_legacy_data .
DATA: l_tab type xstring,
 l_tab1(1) type c,
 s type x.
move '23' to l_tab.
move l_tab to l_tab1.
OPEN DATASET v_pfile FOR INPUT IN TEXT MODE ENCODING DEFAULT.
OPEN DATASET v_pfile FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc <> 0.
 MESSAGE text-207 TYPE c_e.
ELSE.
DO.
 CLEAR wa_input1.
 READ DATASET v_pfile INTO wa_input1.
 READ DATASET v_pfile INTO wa_read.
 IF sy-subrc EQ 0.
 move wa_read to i_txt-txt.
 append i_txt.
 ELSE.
 EXIT.
 ENDIF.
ENDDO.
s = '09'.
loop at i_txt.
 move i_txt-txt+10(1) to l_tab1.
 move '#' to l_tab1.
 split i_txt-txt at s into wa_input1-vbeln wa_input1-posnr
 split i_txt-txt at '#' into wa_input1-vbeln wa_input1-posnr
 wa_input1-per0bal wa_input1-per1val
 wa_input1-per2val wa_input1-per3val
 wa_input1-per4val wa_input1-per5val
 wa_input1-per6val wa_input1-per7val
 wa_input1-per8val wa_input1-per9val
 wa_input1-per10val wa_input1-per11val
 wa_input1-per12val.
 APPEND wa_input1 TO i_input1.
 CLEAR wa_input1.
endloop.
ENDIF.
CLOSE DATASET v_pfile.
IF i_input1[] IS INITIAL.
If there is no data in the legacy file or if the structure of the
legacy data does not match with that of internal table error message
need to be displayed.
 MESSAGE text-211 TYPE c_e.
*&--begin of change--
ELSE.
 CLEAR: wa_input, wa_input1.
 LOOP AT i_input1 INTO wa_input1.
 MOVE wa_input1 TO wa_input.
 MOVE: wa_input1-vbeln TO wa_input-vbeln,
 wa_input1-posnr TO wa_input-posnr,
 wa_input1-per0bal TO wa_input-per0bal,
 wa_input1-per1val TO wa_input-per1val,
 wa_input1-per2val TO wa_input-per2val,
 wa_input1-per3val TO wa_input-per3val,
 wa_input1-per4val TO wa_input-per4val,
 wa_input1-per5val TO wa_input-per5val,
 wa_input1-per6val TO wa_input-per6val,
 wa_input1-per7val TO wa_input-per7val,
 wa_input1-per8val TO wa_input-per8val,
 wa_input1-per9val TO wa_input-per9val,
 wa_input1-per10val TO wa_input-per10val,
 wa_input1-per11val TO wa_input-per11val,
 wa_input1-per12val TO wa_input-per12val.
 APPEND wa_input TO i_input.
 CLEAR: wa_input, wa_input1.
 ENDLOOP.
ENDIF.
ENDFORM. " GET_LEGACY_DATA
When i am giving input as
Directory /pw/data/erp/D5S/fi/up
Name: Backlog1616_D1S.txt
BKCOPO1 BKSOI1 1000.00 100.00 -200.00 0 0 0 0 0 0 0
BKSOPO2 BKSOI2 2222.22 0 300 0 0 0 0 0 0 0
BKSOPO3 BKSOI3 -3000 400 0 0 0 0 0 0 0 0
BKSOPO4 4000.55 500 600 0 0 0 0 0 0 0
0040000000 000010 -100 -110 -110 0 0 -600 0 0 0 0
0040000001 000010 -110 -110 0 0 0 -610 0 0 0 0
I am getting i_input internal table populated as follows at the end of that subroutine.
After appending [APPEND wa_input TO i_input].
BKCOPO1#BK|000000| 0.00 | 0.00 | 0.00 |
BKSOPO2#BK|000000| 0.00 | 0.00 | 0.00 |
BKCOPO3#BK|000000| 0.00 | 0.00 | 0.00 |
BKCOPO4##4|000000| 0.00 | 0.00 | 0.00 |
0040000000|000000| 0.00 | 0.00 | 0.00 |
0040000001|000000| 0.00 | 0.00 | 0.00 |
And output is showing erronious records: 6
No entries inserted.
Can you solve this issue.

SAP Legacy data Migration Starategy/Process

Hi Friends
I would request you, if anybody let me knwo the process of legacy data migration into sap. What are steps I have to follow while doing legacy data migration. My questions are:
1) How to upload GL balances from legacy to SAP
2) How to upload Vendor and Customer open items into sap
3) Asset balances How to upload
4) what is the use of Migration clearing accounts.
Kindly provide if any documents for legacy data migration into sap.
Thanks in advance
Rao

Dear Rao,
Just check the bwlow link you can understand easly to upload the balances.
http://www.saptechies.com/sap-pdf-books-download/SAP_Go_live_strategy11248141773.pdf
Check the bwlow procedure for the same way do it.
First create 5 Dummy GL codes. These GL code should be zero at the end of uploading balances.
1     GL Offset Account               Dr
          Asset Offset Account          Cr
          AP Offset Account          Cr
          Sales          Cr
          Other GL's          Cr
2     Cash               Dr
     Consumption               Dr
     Asset Offset Account               Dr
     AR Offset Account               Dr
     Material Offset Account               Dr
     Other GL's               Dr
          GL Offset Account     x     Cr
3     AP Offset Account               Dr
          Vendor 1          Cr
          Vendor 2          Cr
          Vendor 3          Cr
4     Customer 1               Dr
     Customer 2               Dr
     Customer 3               Dr
          AR Offset Account          Cr
5     Fixed Asset 1               Dr
     Fixed Asset 2               Dr
          Asset Offset Account          Cr
          Acc. Depreciation Account          Cr
6     Stock Inventory Account               Dr
          Material Offset Account          Cr
Regards,

Re:Uploading legacy data

Similar Messages

Maybe you are looking for