Retail Site and LSMW(BAPI or IDOC)

Hello,
I'm trying to upload retail site through LSMW but I can't find a method to do so. Online we use TCode WB01 to create a retail site and I don't want to create a BDC for it since it uses multiple screens. Does anyone know a method to do so? Thanks in advance!
Arash

if you know lsmw mwthod then you can upload site data.
but the question is why do u want upload site with lsmw.
site is a very imp master data in retail. so it will be good if you enter all these by using t-code wb01 manually.
regards
santosh jaiswal

Similar Messages

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

LSMW : BAPI vs IDOC

hi xperts
In LSMW, given the choices between Idoc and BAPI,which processing method is good and why? And when to opt one of the methods?
thkx
Prabhu

Hi
See the links
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
Regards,
Padmam.

Sales Order Creation using LSMW-BAPI.

Hai,
While executing a 14th step in LSMW-BAPI,the IDOC is generated.While Testing the IDoc the values for the Header segment alone is displayed.The Segment sfor Item is not Displayed.Should there be any link between Header & the ITem.
Regards,
Padmam.

Hi,
Can u tell me the steps to create a sales order using idoc, i've created a bapi but thats a temprory use. I wanted to created a sales order automatically when a purchase order is saved.
Please let me know if u can help me, i wanted to do it using idoc
Regards
Sanju

In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

hello all
In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

Hi Swamy,
The differences between IDoc and BAPI are as follows:
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
Idocs are processed asynchronously and no information whatsoever is returned to the client.
The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later.
The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
IDOCs may be more changeable from release to release.
IDOCs are poorly documented.
BAPI
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
BAPIs are called synchronously and (usually) return information.
For BAPIs the client code needs to do the appropriate error handling.
Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
BAPIs are not totally immune to upgrades.
BAPIs are reasonably well documented.
Reward points if useful.
Best Regards,
Sekhar

How to use LSMW using the IDOC to upload and maintain cost center group

Hi Everyone,
Is there anyone who knows how to use LSMW using the IDOC functions instead of the recording. I wanted to upload the alternative cost center group I created in the system.
reply would be greatly appreciated
Warm Regards

Hi Praveen,
There is a risk trying to migrate data directly into standard tables because this can generate database inconsistences or wrong inserted data according to what is customized in the target system. I do not recommend migrate like this.
With LSMW you use objects like direct input programs, idocs, bapis and recorded batch input. Try to create a project and use an standard object for your data. Also, check in SXDA transaction (Goto-->DX programs) if there is a standard program for your data.
Anyway, if you want to upload data directly to tables, read below thread:
["UPLOAD CSV FILE";
[how to upload .csv file into a custom table;
Regards,
Roger

LSMW bapi idocs

Hello evryone,
I am trying to make a lsmw using BAPI with IDoc inbound processing,
But at the time of step Start IDoc Processing
status is 51---- Application Document is not posted
and reason is---- No Master Record Exist for Vendor 10001
could anyone please explain me the reasons for this
Thanx in advance
Jeet Chauhan
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on May 3, 2011 2:44 PM

Hello evryone,
I am trying to make a lsmw using BAPI with IDoc inbound processing,
But at the time of step Start IDoc Processing
status is 51---- Application Document is not posted
and reason is---- No Master Record Exist for Vendor 10001
could anyone please explain me the reasons for this
Thanx in advance
Jeet Chauhan
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on May 3, 2011 2:44 PM

LSMW - BAPi(Idoc settings)

Hi ,
i want to call BAPi in LSMW so in the intial screen iam goin go to settings - idoc inbound processing.
there it is asking for fileport nad partner number: what details should i give.
step by step pls
Thanks,
Donald

Hi Donald,
Go through the following Steps
check this link for step by step procedure on how to do LSMW using Idocs with screen shots
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
Inbound Processing of LSMW Via IDOC's
Step1) Create the Partner Profiles & Port for Inbound Process and Ctivate the Inbound Process for LSMW.
     a) Goto Tcode SALE
                1) Create Logical System for Receiver Save & Come Back
                2) assign Logical to Client for LSMW inbound Process
     b) Goto Tcode SM59
                1) Create RFC Destinations for ALE
     c) Goto Tcode WE21
                1) Create a file port which can read the data from the specified path.
                Here select "FILE" Node --> Click on Create Button(F5)
                Give the following Information
                Port : FILE
                Desc : File Port for Inbound Processing of LSMW Via IDOC's
          Goto Outbound File Tab.
          Select Logical Directory Radio Button.
          Give LOCAL_TEMPORARY_FILES as Logical Path.
          If it is Physical Pthat : C:\TEMP\Filename.
Goto Tcode LSMW
===============
Give      Project          : ZPROJECT
     SubProject        : ZPROJECT
     Object            : ZPROJECT
Click on Create Button
then goto Settings Mwnu
          Click on IDoc Inbound Process.
Here you need to Pass File Port : File
                   Partner Type : LS
                   Partner No. : Port Name (Just Created from WE21 Tcode)
Save And Click on ACTIVATE IDOC INBOUND PROCESS
Save and Come Back.
1) Click on Execute(F8)    1 Maintain Object Attributes
Select IDoc(Intermediate Document)
Message Type : MATMAS
Basic Type   : MATMAS05
Save & Come Back
Then Your Getting the following Steps need to Do
2 Maintain Source Structures
3 Maintain Source Fields
4 Maintain Structure Relations
5 Maintain Field Mapping and Conversion Rules
6 Maintain Fixed Values, Translations, User-Defi
7 Specify Files
8 Assign Files
9 Read Data
10 Display Read Data
11 Convert Data
12 Display Converted Data
13 Start IDoc Generation
14 Start IDoc Processing
15 Create IDoc Overview
16 Start IDoc Follow-Up
2) Select the 2nd Radio Button & Execute.
Click on Create Button.
     Source Structure : ZE1MARAM
        Description      : XXXXXXXXXX
Click on Continu Button
Select Just Created "Source Structure : ZE1MARAM"
Again Click on Create Button this is your Second Source Structure.
     Source Structure : ZE1MAKTM
        Description      : XXXXXXXXXX
It Asks the Same Level or Lowerlavel of Source Structure : ZE1MARAM
select Lower Level Radio Button.
Click on Continue Button
Save & Come Back.
3) Select the 3rd Radio Button and click on Execute Button
Select the first Source Structure
   Click on Copy Button
Select the Third Radio Button
   Click on Copy Button
     Give the Tab Name is E1MARAM
Click on Continue Button.
Save this
Go bottom
Select the 2nd Source Structure " ZE1MAKTM"
   Click on Copy Button
Select the Third Radio Button
   Click on Copy Button
     Give the Tab Name is E1MAKTM
Click on Continue Button.
Save & Come Back.
4) Select the 4TH Radio Button and click on Execute Button
Select E1MARAM -->Click on Relationship Button
     Here A Small window comes then Select ZE1MARAM
     Click on Continue Button.
Select E1MAKTM -->Click on Relationship Button
     Here A Small window comes then Select ZE1MAKTM
     Click on Continue Button.
The Above two Structure are appears in Blue Color
Save & Come Back.
5) Select the 5TH Radio Button and click on Execute Button
First Structure : EDI_DC40 this is Control Record of your IDoc.
after this you will find a Structure "E1MARAM" this is in Orange Color Remember
Select MSGFN Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MSGFN field and double Click on it.
Select MATNR Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MATNR field and double Click on it.
Select MTART Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MTART field and double Click on it.
Select MBRSH Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MBRSH field and double Click on it.
Select MATKL Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MATKL field and double Click on it.
Select MEINS Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->MEINS field and double Click on it.
Select GEWEI Field and Click on Source Field
         a New window will comes here select the ZE1MARAM-->GEWEI field and double Click on it.
Save This.
Go Bottom.
you will find a Structure "E1MAKTM" this is in Orange Color Remember
Select MSGFN Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->MSGFN field and double Click on it.
Select SPRAS Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->SPARS field and double Click on it.
Select MAKTX Field and Click on Source Field
         a New window will comes here select the ZE1MAKTM-->MAKTX field and double Click on it.
Save and Comeback.
Create Your Flat Files Like he following Format. and save it in C:\TEMP folder Only
1st File : MARA.TXT
001     MAT001                                   COUP     C     15          KG                                                                                          01
2nd File : MAKT.TXT
001     EN     New Material For Inbound Processing of LSMW Via IDOC's
6) Select the 6TH Radio Button and click on Execute Button
     We don't do any process here Just Come Back.
7) Select the 7TH Radio Button and click on Execute Button
     Click on Legacy data : Click on F5 Button.
              Add Two Files 1) C:\TEMP\MARA.TXT
                   2) C:\TEMP\MAKT.TXT
     Select Tablator Radio Button as Delimiter
     Save & Come Back.
8) Select the 8TH Radio Button and click on Execute Button
     Select ZE1MARAM Structure and Click on Assignment Button
     Save this
     Select ZE1maktm Structure and Click on Assignment Button
     Save and Come Back.
9) Select the 9TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Read Dada
10) Select the 10TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Display Read Data.
11) Select the 11TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Convert Data.
12) Select the 12TH Radio Button and click on Execute Button
     Click F8 Button.
     Check the Display Convert Data.
13) Select the 13TH Radio Button and click on Execute Button
     Click F8 Button.
14) Select the 14TH Radio Button and click on Execute Button
     This is WE05 Tcode Screen Start IDoc Process.
15) Select the 15TH Radio Button and click on Execute Button
     This is WE05 Tcode Screen Creating IDoc Here
16) Select the 16TH Radio Button and click on Execute Button
     Select Posting Radio Button(that is 5th Button)
     then Click on F8 or Execute Button.
After this your will check your Material exist in receving Side or Not.
Regards
Sreeni

I have lost track of the number of websites that do not work properly on the iPad without Adobe Flash player which is unsupported. I cannot use retail sites, billing sites and most important of all job application sites. All are missing tabs, links, info

I have lost track of the number of websites which do not work properly on my iPad. They include retail sites, billing sites and most important of all job application sites. They all seem to require Adobe Flash Player which cannot be downloaded onto an iPad. Skyfire does not solve the problem. They all load without vital parts of the site such as tabs, links and correct formatting. Any suggestions?

Most such brower/service combinations have a difficult time working with Flash-based apps and often fail completely. Flash videos are usually the most successful content these browers can handle. You can try the others apps - Puffin, iSwifter, etc - but you may find that none of them work, in which case you will not be able to use your iPad with these sites other than by using one of the various remote control solutions to take over a computer running the full Flash Player.
IMHO, any developer that built a Flash application for a billing or job application site was an idiot, but I know that's out of the control of anyone but the relevant company.
Regards.

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

How ca we create an INVOICE using a BAPI and triggring the same IDoc

Hi Gurus,
I have a senario where in I need to create an Invoice from a remote using BAPI and then the INVOICE IDOC has to be triggered for external purpose.
How can be this achived??
Help me as early as possible.
Thanks in Advance...
Suma

Hi,
Are you looking for BAPI <b>BAPI_ACC_INVOICE_RECEIPT_POST</b>?
Hope this helps (please reward me if it does).
Regards, Joerg

Std Idocs and Std BAPI

Hello,
Could you tell me please what are the availabel standard Idocs and Standard Bapis available.
If possible could you tell me why do we use those standard Idocs and Bapis.
Thank you

Hello Jyotsna,
BAPI:
http://help.sap.com/saphelp_nw04/helpdata/en/3e/ecf226942511d2ad4b080009b0fb56/frameset.htm
or
Standard BAPI:
Look at the Transaction BAPI.
T-code: BAPI
Go to the T-Code se37 -
Type BAP* then click F4.
You can find the Standard IDOC's on T- Code in : WE60
check the below link for the list of idocs
http://www.erpgenie.com/sapedi/idoc_interface.htm
Thanks,
Satya
Reward points if it is useful

Bdc and lsmw

Hi All,
I am presuming that both bdc's and lsmw are being used for data migration. if this is right then when would someone prefer bdc over lsmw or vice versa. if my assumption is wrong then tell me for what specifications we use lsmw and for what specs we use a bdc.

Hi,
"The Data Transfer Workbench (or DX Workbench, transaction SXDA) is an integrated SAP tool that supports data transfer and analysis. It
does not have the built-in features for mapping for source structures to target structures, but it will allow you to integrate Legacy System Migration Workbench (LSMW) objects as processing tasks within a run definition. The DX workbench has many features for creating
test data and performing data migrations - for example, logging of data migration runs.
However, if you need to map or convert data, you should use the LSMW. Or, you can integrate
your LSMW objects as task within a more user-friendly data migration run, in which the LSMW
project steps "Read data", "Convert data," and "Start IDoc processing" are automated
and use the features of both tools. If you donot need logging and automated data migration
runs, you can perform your data migration without the DX Workbench."
The following was taken at this site :
http://www.info-sun.com/docs/wp_sapinter.pdf
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form
of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The
transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using
Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Remote Function Call (RFC) in SAP R/3 is based on UNIXs Remote Procedure Call (RPC). RFC enables the real-time link between different R/3 instances and can connect SAP to Non-SAP systems. With Remote Function Call, both inbound (RFCServer) and outbound (RFCClient) interfaces are possible.
SAP also provides a toolkit called RFC API for non-SAP systems to interact with SAPs Function modules remotely.
RFC is a very powerful tool for interfacing with SAP system in real time. Most other interfacing techniques like ALE, EDI, BAPI etc are
inherently based on the RFC technology.
Electronic Data Interchange (EDI) is the industry standard format for exchanging Business data. SAP uses a neutral format called Intermediate Document
(IDoc) for communicating EDI & ALE messages.
The IDoc interface contains data structures and processing logic for each of the business transaction. These are grouped as Message
Types. The external EDI Server is responsible for receiving the EDI messages sent by the trading partners. These EDI messages are then
mapped onto the IDoc structure fields and stored in the IDoc interface layer by SAP.
EDI/IDoc supports both inbound and outbound interfaces. The IDocs received through the EDI Server can be configured to automatically get
processed, or can be stored in the IDoc interface layer for a future manual or scheduled processing. The IDoc interface layer also has a powerful error
handling, reporting, monitoring and reprocessingmechanism built into it (Transaction WEDI). IDoc is also tightly integrated with the WorkFlow system
of SAP for initiating other business tasks upon receiving/sending EDI messages.
The IDoc interface can be employed for non-SAP applications to load or extract data from SAP system. But typically, EDI / IDoc is engaged when
SAP system is to be integrated with any of its business partners (Customers, Suppliers and other partners) for carrying out standard business
transactions (like Create Sales orders, Sending Purchase orders to Suppliers, etc).
Application Link Enabling (ALE) is a middleware tool, which is part of SAPs Business framework Architecture (BFA). ALE can effectively be used
for loosely coupled Asynchronous communication between SAP systems and with non-SAP systems. ALE is based on the distributed processing
architecture and hence integrates applications with the local database rather than centralized one. ALE messages are based on the Intermediate
Document (IDoc) format, similar to the EDI counterpart. Though ALE can be used to interface with non-SAP systems, usually it is used to
distribute Master & Transactional data between SAP R/3 instances.
The ALE distribution can be based on,
Business APIs
IDoc Message Types"
Business API (BAPI) is the most important component of SAP Business Framework. BAPI enables SAP and third party applications to interact and integrate
with each other at the Business Object / Process level.

Diff b/w BDC and LSMW

hi
i want know what is the difference between BDC and LSMW and which is best also tell me BDC and LSMW using for which type data (like master or transactional data)
thanka in advance
deepak

Hi deepak,
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
http://www.sap-img.com/sap-data-migration.htm
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://allsaplinks.com/lsmw.html
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm

Unable to create PO with multiple line items through LSMW-BAPI method

Hi All,
I have a requirement of creating PO through LSMW. I can't use LSMW standard batch input program since there are some fileds not available and also it has many limitations. I'm using LSMW-BAPI method ( Business object BUS2012) which create IDOC and uses BAPI_PO_CREATE1 to ultimately post the PO in the system. I am trying to create PO from a single file which contains both Header and Item data.
Now my problem is that everytime PO is being created with Single line item only. Everytime I am giving multiple item data in the source file LSMW is preparing multiple IDOCs for multiple line items. As per my understanding this is happenng since header and item is in the same hierarchy level of IDOC type PORDCR102 and the control record is inserted for every line item in the source file.
It seems that through LSMW-BAPI it is not possible to create PO with multiple line items. Can anybody provide some input regarding this? Thanks in advance.
BR,
Atanu Mukherjee

Solved by myself.
Earlier the problem was that LSMW was not being able to recognize items under same header. It was creating new IDOCs every time it gets a new item. To enable this we need to create two structure HEADERDATA and ITEMDATA. Two additional identifier fields with identifier value 'H' and 'I' should be added in these two structures respectively. Then we need one sequential file with the identifiers field followed by the header and Item data. Example:
H~header data
I~item data
I~item data
This would help the standard program to understand what are the items under same header and ultimately create PO with multiple line items.
BR,
Atanu Mukherjee

Retail Site and LSMW(BAPI or IDOC)

Similar Messages

Maybe you are looking for