BDC or LSMW for open PO

Dear Friends,
We are suppose to go likve soon, but we have @ 500 open Purchase orders and we would like to ipload same in sap as retail can any 1 guide me how to do it?
Regrads,
Vishal
[email protected]

Hi Vishal,
Please make a note that,
LSMW is used to transfer Master Data.
BDC is used for transactional Data.
LSMW can import data from legacy systems (e.g. in the form of Excel sheets or CSV files). For this, I guess, LSMW converts your data into batch input files automatically. If you use BDC, on the other hand, you have to write your batch input file yourself, line per line.
So, Open Purchase Order are the Transactional Data for you can use BDC for this Purpose
Please take your ABAPER's help to will write a Code to Migrate the Data.
Hope this Solve your Purpose and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Similar Messages

Standard LSMW for open vendor items with Withholding tax

Hi All,
I am searching the direct input LSMW which is having the Withholdig tax. There is a direct input program in LSMW ( RFBIBL00) but it is not uploaded the withholding tax for open vendor and open customer items.
If anybody know which LSMW is recammanded or anthing related to BAPI or IDOC for this requirements.
Dhiraj.

Hi
If you need to upload the WT tax you have to fill the structure BWITH of std BI RFBIBL00, so your LSMW project should create a file like this:
---> Session data
BGR00
---> Document data
BBKPF (Header data
BBSEG (Vendor or customer item)
BWITH (Withholding tax data)
BBSEG (G/L item)
Max

LSMW for open notifications,open sales order & open service order

Hi Gurus,
Can anyone please tell me how to go about writing LSMW's for open notifications,open sales order & open service order.
This is for service processing in CS ,where has the scenario is
Create Notification (IW51) --> create Sales Order(Multiple Line Items) ( VA02) --> Create Service Order ( IW32)
Service order is automatically (Item Proposal) generated w.r.t Sales Order (multiple line items)
How to I do the recording for transactions in such a scenario.
Please suggest!
Thanks!
Vinod

you can use the below LSMW IDOC method
SALESORDER_CREATEFROMDAT2       Sales order: Create Sales Order
SERVICENOTIFICATION_CREATEFROM Create service notification
SERVICE_CREATE                  Creation of a Service Master Record
CARNOT                          Delivery: Shipping notification
DESADT                          Shipping notification
DESADV                          Delivery: Shipping notification
INOTIF                          Notifications
INTUPD                          Notification Status Update
ISU_ADVICE                      IS-U Deregulation: Notification
ISU_CHANGE_REQUEST              IS-U: Notification of Change to
ISU_MAINT_SO                    IS-U Dereg.: Notification of Dev
ISU_REMITTANCE_ADVICE           Transfer Notification

LSMW for Open Deliveries in Sales & Distribution Module

Hi
I am stuck in building LSMW on
Open Deliveries in SD module.
The required fields are
shipping point-VSTEL
ship to party -KUNNR
Document date -BLDAT
Planned GI date-WADAT
Article no-MATNR
Qty -LFIMG
Kindly let me know the TCode and also the process for the same, as i am new to ABAP and there is no
functional people in my project.
Regards
Madhumita

Hi...
U go to LSMW and give Project name and subproject name..
After u selact Batchinput recoeding method a.d give ur tcode for ur recording..
Once finished ur recording u save and come nack.
After u can follow LSMW step.
(if u want more info u go throuh ****************.There how 2 do LSMW step by step s there..U can easily understand)
Regards:
Prabu

BDC or LSMW for MR21

Hi,
Can anyone help me in creating a BDC for MR21:
Create a batch input recording and generate a program that can be modified. A transaction code should be created to run the program, and users must have the transaction included in their profiles. The program must allow BDC sessions to be created (rather than only offering a call transaction option). In the case of large files, the BDC session may be scheduled to run in background. Whereas a program running a call transaction can only run in foreground, if the file is being uploaded from the PC / network.
or an LSMW for MR21.
Create a batch input recording through LSMW, and create the dataload using that. Since the data will be provided in SAP format, it is not strictly necessary to have an LSMW, but the developer may decide this is the simplest development method anyway.
Please help me in this regard.
Thanks,
Sai

hie
for a BDC program for MR21 go to transaction SM35. Recording --> New Recording -->enter the a suitable name for the recording name and transaction MR21 and start to carry out the recording with the help of a functional guy. After you the process has gone through press save and back. Highlight your recordings name and press program. fill in the required name and on the filed contents radio button select Transfer form recording. After this you will have your BDC program ready.
Create another program with type Executable. Copy and paste your BDC program into that one. We do this so that you can assign a transaction code to your program. For the transaction code go to transaction SE93 and fill in a relevant transaction code for your program. Press Create and fill in a relevant description for your transaction code. On the start Object radio button select option Transaction with parameters (parameter transaction) since we will have a parameter for picking the logical destination for the file to be uploaded.
Make adjustments to your program according to your requirements.
I would be happy to assist further.
Regards
PrinceIsaac

BDC or lsmw for ABT1N Transaction

Hi gurus,
last day i got some problem when i do a lSMW for ABT1n Tran.i am thankful to u if u please help me that how can i do it.please give me a complete document for that trans and also a text file so that i properly update it.
                if u do any BDC program for that transaction please give me that program .it's very urgent for me....
Thanks in advance....

Hi Steve,
BAPI_HU_CREATE itself creates HU. You can refer the HU number genrated by this BAPI itself. I hope you are calling bapi as below:
CALL FUNCTION 'BAPI_HU_CREATE'
            EXPORTING
              HEADERPROPOSAL = L_WA_HU_HEAD
            IMPORTING
              HUHEADER       = L_WA_HU_HEADER
              HUKEY          = L_V_HU_NUMBER
            TABLES
              ITEMSPROPOSAL = L_I_HU_ITEM
              RETURN         = I_HU_RETURN
              HUITEM         = L_I_CREATE_HU.
Here, L_V_HU_NUMBER is the HU generated.
Thanks,
Archana
Edited by: Archana Pawar on Sep 29, 2010 7:47 AM

LSMW for Open Production Order Creation

Hi all,
I want to migrate open production orders from legacy system to the other SAP system. Please let me know how should I do it?
I tried using the idoc method with Message type LOIPRO and the Basic Type LOIPRO01 but the it gives a error that No process code for message type LOIPRO. I guess this is a Outbound Idoc.
Next I tried searching for a BAPI for prodcution orders. I found the BAPI, BAPI_PRODORD_CREATE. But it does not contain all the fields I need. Also this BAPI cannot be used in LSMW as it ALE message type does not exist for it.
So please let me know how can I use the idoc method to create the production order as I have all the fields required in the idoc basic type. Also please share if any other method is there to upload the data.
Regards,
Mozila

We had to use BAPIs to upload the production orders.
It was not possible with LSMW.

BDC or LSMW program for AS91 transaction

HI gurus,
i need a BDC or lsmw program for tran:AS91 ie.create legacy data for two inter company data transfer.can anyone please help me bkz it's very urgent for me...
i promise that if i get the ans i reward u.

Hi,
Use Function Module:MAINTENANCE_PLAN_POST

BAPI / LSMW for Accounts Receivable open items and G/L Accounts balance

I want to transport legacy data to SAP.
Please provide me with a BAPI or LSMW for creating entries for
Accounts Receivable open items
General Ledger Accounts balances

Thomas,
Program RFBIBL00 is traditionally used for converting FI transactions. In LSMW, it's object 0100, sub object 0000.
-nathan

BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...

Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AM

Hi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac.

LSMW For Converting Open Sales Orders (not working for more than 1 item)

Hi,
I am using following standard object for Open sales orders .
Object               0090   Sales documents
Method               0000
Program Name         RVINVB10
Program Type         D   Direct Input
Its not working for more than 1 line item.
For more than 1 line item its giving Error saying that
'102122                         V1                   845
Print parameter SAPML2 1 is not defined
Can anybody help me out in this regard.
Thanks in advance.
Nitin.

hello, friend.
i will still research the subject. but the first thing that comes into my mind is t-code VA05. with this, you have the option to change the Plant en masse. so a possible workaround is for you to list a number of sales orders using VA05. you then sort the line items by Plant. choose all items with the same plant, change the plant via mass change... then change back to the original plant. hopefully, the new settings should apply.
do test a few sales orders by doing this for a larger scope.
regards.

'Create' Push button is not working in BDC and LSMW while uploading G/L master data

Hello Experts:
I am facing the following problem:
While uploading G/L master data with the BDC program, 'create' push button is not working even after executing following lines.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
Create G/L account screen is not coming in BDC. Please suggest me what to do.
Thanks !!

Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Hi Glen Anthony
Thank you for the reply Glen Anthony please take a look at the following code.
REPORT ZFI_BDC_FS00
        NO STANDARD PAGE HEADING LINE-SIZE 255.
*INCLUDE BDCRECX1.
TYPES : BEGIN OF STR,
   BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS,        "Company Code
   SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR,        "G/L Account Number
   KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS,        "G/L Account Group
   XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT,    "P&L statement account
   XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK,        "Indicator: Account is a balance sheet account?
   TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML, "G/L account short text
   TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML, "G/L account short text
   WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS,      "Account currency
   XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH,      "Indicator: Only Manage Balances in Local Currency
   MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ,      "Tax Category in Account Master Record
   XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO,      "Indicator: Tax code is not a required field
   MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ,      "Account is reconciliation account
   XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW,      "Indicator: Open item management?
   XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES,      "Indicator: Can Line Items Be Displayed by Account?
   ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA,      "Key for sorting according to assignment numbers
   FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG,      "Field status group
   XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB,      "Indicator: Is account only posted to automatically?
   END OF STR.
DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
        IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
        TXT(4096) TYPE C OCCURS 0,
        MSG TYPE STRING,
        COUNT(5) TYPE N.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
   PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
    PROGRAM_NAME        = SYST-CPROG
    DYNPRO_NUMBER       = SYST-DYNNR
*   FIELD_NAME          = ' '
IMPORTING
    FILE_NAME           = MY_FILE
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
   EXPORTING
*   I_FIELD_SEPERATOR          =
*   I_LINE_HEADER              =
     I_TAB_RAW_DATA             = TXT
     I_FILENAME                 = MY_FILE
   TABLES
     I_TAB_CONVERTED_DATA       = ITAB[]
EXCEPTIONS
    CONVERSION_FAILED          = 1
    OTHERS                     = 2
IF SY-SUBRC <> 0.
* IMPLEMENT SUITABLE ERROR HANDLING HERE
ENDIF.
START-OF-SELECTION.
COUNT = 0.
LOOP AT ITAB.
*PERFORM OPEN_GROUP.
REFRESH IT_BDCDATA.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
*PERFORM BDC_FIELD       USING 'BDC_CURSOR'
*                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                               ITAB-SAKNR. "'5'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
                               ITAB-BUKRS. "'TATA'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_GROUP'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-KTOKS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_BS_PL'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-XBILK'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "''.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB02'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-TXT50_ML'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                               ITAB-TXT20_ML. "'G/L ACCOUNT'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                               ITAB-TXT50_ML. "'G/L ACCOUNT'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB03'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                               ITAB-WAERS. "'INR'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
                               ITAB-XSALH. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                               ITAB-MWSKZ. "'*'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                               ITAB-XMWNO. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                               ITAB-MITKZ. "''.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                               ITAB-XOPVW. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                               ITAB-XKRES. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                               ITAB-ZUAWA. "'1'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=SAVE'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-XINTB'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                               ITAB-FSTAG. "'G019'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                               ITAB-XINTB. "'X'.
*PERFORM BDC_TRANSACTION USING 'FS00'.
CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
COUNT = COUNT + 1.
*PERFORM CLOSE_GROUP.
ENDLOOP.
CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
MESSAGE MSG TYPE 'I'.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
   CLEAR IT_BDCDATA.
   IT_BDCDATA-PROGRAM = PROGRAM.
   IT_BDCDATA-DYNPRO   = DYNPRO.
   IT_BDCDATA-DYNBEGIN = 'X'.
   APPEND IT_BDCDATA.
ENDFORM.
*        INSERT FIELD                                                  *
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
     CLEAR IT_BDCDATA.
     IT_BDCDATA-FNAM = FNAM.
     IT_BDCDATA-FVAL = FVAL.
     APPEND IT_BDCDATA.
* ENDIF.
ENDFORM.

LSMW for master data & transaction data

Hello Experts,
We have master data :
1)Material
2)Vendor
and
Transaction data
3)Open PR
4)Open PO
5)Stock Posting
Can we use LSMW for all these?
Or which one is recommended for each one of them...
Whether BDC or LSMW recommended ?
Kindly suggest...
Regards
Mahesh

alternativ you can use standard reports:
RFBIKR00 fpr vendors
RMDATIND for material
RM06BBI0 FOR PR
RM06EEI0
RM06EEI1
RSTXLITF
for PO
and RM07MMBL for material (transaction data)
hope that helps
Andreas

What is BDC and LSMW? Difference

Dear experts!
Explore the concept of BDC and LSMW and their difference.
Merits/Demerits.
Transactions used for executing and viewing the same.
Rishi.

Rishi,
Hope these links help you:
http://sap-img.com/bdc.htm
http://sap-img.com/sap-data-migration.htm
http://sap-img.com/sap-data-migration.htm
https://websmp206.sap-ag.de/lsmw
<b>LSMW</b>
Data Migration from Non-SAP Systems to SAP systems* Made Easy
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Detailed Information
Objectives
High Flexibility to Ensure the Optimal Solution
The Data Transfer Workbench gives you control of the SAP data transfer interfaces: from proven batch input, through very fast direct input, to Business APIs (BAPIs), which are also suitable for permanent interfaces. This solution is sufficient if certified partner products are available for the transfer of open interfaces, or if you explicitly want to do interface programming in ABAP or the language of the legacy system. SAP provides its customers with the Legacy System Migration (LSM) Workbench, which dramatically reduces the considerable expenditure involved in individual programming. This tool makes it possible to transfer data without any programming. You define the rules for the changeover. The LSM Workbench then uses this definition to generate an ABAP program and thus gives you considerable support during the migration.
Description
Data Migration Controlled by your SAP System
In contrast to many conventional approaches, the solution described here is a component of your SAP system. As a result it is no longer necessary to program in a number of different systems. All you need are basic unloading programs in the legacy system, or, alternatively, existing data interfaces can be used. Everything else takes place in the SAP system. With SAP R/3 Release 4.6C the LSM Workbench is also integrated into the Data Transfer Workbench, and can be called up there.
Maximum Quality
Data migration with the Data Transfer Workbench and the LSM Workbench guarantees maximum quality and consistency of your data in the SAP system. When data is imported, the system performs the same checks as it does during online entry. The update in your database is performed through the Standard Batch Input Program, the Standard Direct Input Program, IDOC interfaces, and R/3 System BAPIs.
Proven Concepts
SAP has already gathered over seven years of migration experience with its own products. The LSM Workbench has been developed on the basis of experience gained with the R/2-R/3 Migration Workbench. In the meantime, the LSM Workbench has also been successfully used over 500 times in the migration of legacy systems to R/3.Concepts and techniques that have proven their worth form the backbone of the LSM Workbench:
Transfer of business data objects (such as material master data) instead of individual tables
Definition of flexible conversion rules that are adapted as part of migration customizing
Automatic generation of a conversion program
Synergy Effects through Uniform Procedures
SAP's experience shows that certain algorithms and techniques appear over and over again during data conversion projects. These techniques have been standardized in the LSM Workbench and can be called at the touch of a button. With this concept of central rules you can ensure, for example, that your vendor numbers are converted in the same way in both your vendor master data and in your purchase orders. This uniform procedure guarantees the consistency of your data and captures synergy effects in cases where you need to migrate data from disparate legacy systems.
Importing Data from PCs
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
Data Verification before Update in the Database
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
Substantial Reduction of Effort
SAP's experiences show that using the Data Transfer Workbench in conjunction with the LSM Workbench can reduce the effort required for data migration by 30% and more.
Project Library - A Knowledge Database
The LSM Workbench is a learning tool: The experience gained in other implementation projects is continually fed into the LSM Workbench, where it directly benefits your project.

Data Migration for Open Purchase Order

Hi, All,
Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
Thank you very much

JC,
Sounds a bit early to be making decisions about the realization phase. It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc). Depending on the complexity and volume of data, it may be necessary to write custom programs to load the data. You will find this out during your requirements gathering.
It is uncommon but possible to load all of these data manually. I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry. I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load. I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment. Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system. You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N. If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
It sounds like you are implying that the client wants YOU to extract the legacy data. For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system). Most of us do not understand the workings of the myriad legacy systems. The client is usually expected to produce one or more legacy system technical experts for you to liase with. You normally negotiate with the technical expert about every facet of of the data migration. In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
Finally, you mentioned how do you track the mapping of master data between legacy and SAP. There are many ways to do this. I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file. If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC. If your data package is small, you can probably get by using MS Excel or similar.
Good Luck,
DB49

BDC or LSMW for open PO

Similar Messages

Maybe you are looking for