BAPI LSMW

Why is BAPI method of LSMW considered the most reliable & fast of all methods . I would think the IDOC is most reliable because of the tracing features and Direct Input would be the fastest method

BAPI is faster than any other method as they are integrated properly with the SAP tables and designed specially to fill them.
In LSMW we create BDC to execute.
Refer the links -
scenarios of using direct input,batch input,,bapi,idoc methods in lsmw
/message/3407272#3407272 [original link is broken]
Regards,
Amit
Reward all helpful replies.

Similar Messages

Difference between lsmw using BAPI & lsmw using IDOC?

HI everybody
can anybody tell me difference between lsmw using BAPI & lsmw using IDOC?

IDocs and BAPI are very different, so it should be easy to choose between them depending on your requirements.
IDOCS
Advantages
System can work even if target system not always online. The IDoc will be created and sending will just continue once you get connected to the other system.
No additional programming required. You just need to set up the configuration.
Disadvantages
Receipt/processing on the target system may not be immediate.
The sending system has no way to know whether the target system actually received what you sent (unless you use ALE).
If there is no SAP standard IDoc available for your requirement, it's harder to create a customized IDoc than a customized BAPI.
BAPIS
Advantages
You can tell if your sending was successful or not
Sending to/processing on the other side is immediate
Easier to create your own BAPI than your own IDoc
Disadvantages
Will only work if you have an active online connection.
Some programming required to call the BAPI.
Others interface methods you might also want to consider are ALE and RFCs.

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

Data tranfer using bapi(lsmw)

please explain the steps that are used to upload legacy data into sap using lsmw (bapi method)
Message was edited by:
neela renganathan

Hi,
is step by step process .
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 as prompted.
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:
Please Go through these Links ,
BAPI with LSMW
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
For document on using BAPI with LSMW, I suggest you to visit:
http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
Regards

Query on BAPI -LSMW

Hi All,
I have a requirement on LSMW, Can any body send me step-by-step procedure
to create SD-pricing conditions by using BAPI in LSMW.
Thanks,
Naga

hi naga,
FOR BAPI/IDOC METHOD, WE NEED TO MAINTAIN IDOC INBOUND PROCESSING EXPLICITLY. IN THE INITIAL TRANSACTION OF LSMW, GO TO SETTINGS AND CLICK IDOC INBOUND PROCESSING. WE NEED TO PERFORM THE FOLLOWING STEPS.
     DEFINE OR SELECT A FILE PORT FOR TRANSPORTING THE FILE. OPTIONALLY, YOU CAN ALSO CREATE A TRFC PORT.
     THE PARTNER TYPE HAS TO BE DEFINED OR SELECTED.
     THE PARTNER NUMBER HAS TO BE DEFINED OR SELECTED.
     IDOC INBOUND PROCESSING MUST BE ACTIVATED AND THE WORKFLOW CUSTOMIZING MUST BE CHECKED. BOTH OF THESE TASKS ARE PERFORMED ONCE IN EACH SYSTEM.
EXPORTING AND IMPORTING
EXPORTING - IT IS A GOOD IDEA TO PERFORM THE MIGRATION FROM A LEGACY SYSTEM TO THE SAP SYSTEM IN A TEST SYSTEM FIRST. THIS FUNCTION IS USED TO TRANSFER THE FIELD ASSIGNMENTS DEVELOPED TO THE PRODUCTION SYSTEM.
IMPORTING - IMPORT THE MAPPING AND FIELD ASSIGNMENTS INTO A DIFFERENT SAP SYSTEM.
1) MAINTAINING OBJECT ATTRIBUTES
SPECIFY WHETHER THE DATA IS TO BE TRANSFERRED ONCE OR PERIODICALLY. AND THEN SPECIFY WHICH METHOD YOU GONNA USE FOR THE DATA TRANSFER.
2) MAINTAING SOURCE STRUCTURE
WE CAN CREATE SOURCE STRUCTURES EITHER AT THE SAME LEVEL OR AT THE LOWER LEVEL.
3) MAINTAINING SOURCE FIELDS
WE CAN DIRECTLY CREATE THE SOURCE FIELDS. OR WE CAN COPY THE FIELDS USING THE FOLLOWING METHODS.
     UPLOAD TAB DELIMITED TEXT
     COPY FROM OTHER OBJECT
     COPY FROM DATA REPOSITORY FROM A STRUCTURE OF ABAP DICTIONARY.
     FROM DATA FILE.
4) MAINTAING STRUCTURE RELATIONS
HERE WE ARE ESTABLISHING THE STRUCTURE RELATIONSHIPS BETWEEN THE PROJECT AND THE SAP SYSTEM.
5) MAINTAIN FIELD MAPPING AND CONVERSION RULES
HERE WE ARE MAINTAINING THE FILED RELATIONSHIP BETWEEN THE SOURCE AND TARGET STRUCTURE.
AUTO FIELD MAPPING
AUTO FIELD MAPPING IS USEFUL IN CASE IF FIELDS WITH IDENTICAL OR SIMILAR NAMES/DESCRIPTIONS EXIST IN THE SOURCE AND TARGET STRUCTURES. THIS IS PARTICULARLY THE CASE IF DATA IS TRANSFERRED FROM ONE SAP SYSTEM TO ANOTHER SAP SYSTEM.
CONVERSION RULES
THE DEFAULE CONVERSION RULE IS TRANSFER (MOVE).
INITIAL, CONSTANT, TRANSFER (MOVE), PREFIX, SUFFIX, CONCATENATION, TRANSFER LEFT- ALIGNED, ABAP CODE, X FIELD, MOVE WITH LEADING ZEROS, [(R) FIXED VALUE, TRANSLATION AND USER-DEFINED ROUTINE].
THERE IS A CHECKBOX ONLY IF SOURCE FIELD NOT INITIAL.
GLOBAL VARIABLES
WE CAN USE THESE GLOBAL VARIABLES IN ABAP CODE.
G_PROJECT     CURRENT PROJECT
G_SUBPROJ     CURRENT SUBPROJECT
G_OBJECT     CURRENT OBJECT
G_RECORD     CURRENT TARGET STRUCTURE
PROCESSING TIMES
__BEGIN_OF_PROCESSING__     BEFORE PROCESSING OF DATA IS STARTED.
__BEGIN_OF_RECORD__     BEFORE THE CONVERSION RULE FOR A SOURCE STRUCTURE IS APPLIED.
__END_OF_RECORD     AFTER THE CONVERSION RULE FOR A SOURCE STRUCTURE HAS BEEN APPLIED.
__END_OF_TRANSACTION__     AFTER PROCESSING OF THE TRANSACTION HAS BEEN COMPLETED.
__END_OF_PROCESSING__     AFTER PROCESSING OF DATA HAS BEEN COMPLETED.
__BEGIN_OF_TRANSACTION__     BEFORE PROCESSING OF DATA FOR A TRANSACTION IS STARTED
GLOBAL FUNCTIONS
TRANSFER_RECORD.     THE CURRENT RECORD (THAT IS, THE RECORD FOR THE CURRENT TARGET STRUCTURE) IS TRANSFERRED TO THE OUTPUT BUFFER.
TRANSFER_THIS_RECORD '...'.     A RECORD OF A DIFFERENT TARGET STRUCTURE IS TRANSFERRED TO THE OUTPUT BUFFER. THE NAME OF THE TARGET STRUCTURE HAS TO BE SPECIFIED AS ARGUMENT BETWEEN QUOTATION MARKS.
AT_FIRST_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT IS THE FIRST TRANSACTION INVOLVED.
ON_CHANGE_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT HAS CHANGED AS COMPARED TO THE LAST RECORD.
TRANSFER_TRANSACTION.     THE CURRENT TRANSACTION IS WRITTEN TO THE OUTPUT FILE. THIS TRANSFERS ALL THE RECORDS OF THE OUTPUT BUFFER TO THE OUTPUT FILE.
SKIP_RECORD.     THE CURRENT RECORD IS NOT TRANSFERRED TO THE OUTPUT BUFFER.
SKIP_TRANSACTION.     THE CURRENT TRANSACTION IS NOT WRITTEN TO THE OUTPUT FILE.
6) MAINTAIN FIXED VALUES, TRANSALTIONS, USER-DEFINED ROUTINES
REUSABLE RULES ALLOW YOU TO DEFINE CONVERSION RULES THAT CAN BE USED SEVERAL TIMES.
7) SPECIFY FILES
WE CAN SPECIFY FILES IN PC OR IN APPLICATION SERVER. IN CASE YOUR DATA IS STORED IN MULTIPLE SETS OF FILES, YOU CAN SPECIFY A WILDCARD (*) FOR THE NAME OF YOUR FILE. A WILDCARD CAN BE USED EVERY TIME THE FILES FOR SEVERAL IMPORT RUNS COME FROM DIFFERENT FILES; WITH THE FILE NAME BEING DIFFERENT IS SOME CHARACTERS ONLY.
FOR READ DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.READ
FOR CONVERTED DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.CONV
8) ASSIGN FILES
ASSIGNS THE FILES ALREADY DEFINED TO THE SOURCE STRUCTURES.
CONVERSION PROGRAM - /1CADMC/SAP_LSMW_CONV_OBJN.
9) READ DATA
THE FILES MUST HAVE BEEN SPECIFIED BEFORE AND MADE KNOWN TO THE LSMW. IN THIS STEP, THE DATA IS READ INTO THE APPLICATION SERVER.
WE CAN READ THE SELECTED DATA BY GIVING TRANSACTION NUMBER.
10) CONVERT DATA
THE FILE OF READ DATA IS TRANSFERRED TO THE FILE OF CONVERTED DATA DURING MIGRATION.
WHEN THE LSMW OBJECT IS BASED ON A BAPI OR AN IDOC, ADDITIONAL SELECTION PARAMETERS ARE AVAILABLE ON THE SELECTION SCREEN OF THE DATA CONVERSION PROGRAM:
CREATE IDOCS DIRECTLY:     IDOCS ARE COLLECTED AND THEN PASSED FOR IDOC GENERATION PACKAGE BY PACKAGE.
NO. OF IDOCS PER PACKAGE:     THE DEFAULT IS 50 (THIS VALUE CAN BE CHANGED).
THE ABOVE MENTIONED STEPS ARE COMMON FOR ALL THE TYPES OF IMPORTING METHODS IN LSMW.
IN THE CASE OF STANDARD BATCH INPUT/ BATCH INPUT RECORDING, CREATING BATCH INPUT SESSION AND PROCESSING THAT.
IN THE CASE OF STANDARD DIRECT INPUT, START A DIRECT INPUT SESSION.
IN THE CASE OF BAPI/ IDOC,
     STARTING IDOC GENERATION
     STARTING IDOC PROCESSING
     CREATING AN IDOC OVERVIEW
     STARTING IDOC POSTPROCESSING
FOR DIRECT INPUT METHOD, WE CAN USE EITHER THE PROGRAM RMDATIND OR THE TRANSACTION BMV0.
STARTING IDOC GENERATION FIRST, THE FILE WITH THE CONVERTED DATA IS READ. THE PACKETS OF INFORMATION IN THIS FILE ARE THEN SAVED TO THE SAP DATABASE IN IDOC FORMAT, BUT NOT TO THE DATABASE OF THE CORRESPONDING APPLICATION. THE SYSTEM ASSIGNS A NUMBER TO EACH IDOC. THE FILE WITH THE CONVERTED DATA IS THEN DELETED.
STARTING IDOC PROCESSING THE IDOCS CREATED IN THE FIRST STEP ARE SENT TO THE ASSOCIATED APPLICATION PROGRAM. THIS APPLICATION PROGRAM CHECKS THE DATA AND UPDATES IT IN THE APPLICATION DATABASE, IF NECESSARY.
Pls reward if helpful.

Assign file creating problem in BAPI LSMW

Hello Experts!
Iu2019m trying to upload PO (Header/Item data) though BAPI Method. Iu2019ve one file having Header and Item data. At Assign Files Step when I try to assign file to PO Item Data. System gives me a message
(File 'C:\MySAP\ABAP Programing\LSMW\PORec.txt'
only be assigned to one source structure.)
Looks like system is not letting me give the same file which Iu2019ve given to PO Header data. Can anybody please tell me how I can assign the same file for Header and Item data.
Thanks.

check this weblog by niamesh how to handle header and item in lsmw.
LSMW with RFBIBL00

BAPI LSMW - Partner Profile - VCHARVAL

Hi,
I´m trying to use a LSMW to load data to vendor characteristic, I´m using BAPI method with message type: VCHARVAL, but when I´m going to configure "Maintain Partner Numbers", I need to fit in the Inbound Parameters the field "Process Code", I already tried some values but it doesn´t work.
Can someone tell me what the "process code" is necessary to put in that configuration?

I created a LSMW project, using Business Object Method(BAPI), with Business Object: LFA1, Method: SAVECHARVALUEREPLICAS, Message Type: VCHARVAL and Basic Type: VCHARVAL01, to load data into vendor characteristic values.
When I try to Start IDoc Processing I receive an error: "Function module not allowed: IDOC_INPUT_CHRMAS", I know that error is about the configuration of IDoc Inbound Processing, but I don´t know how configurate in the partner profiles, the Inbound parameters to the message type VCHARVAL.

BAPI/LSMW/BDC/ALE-Idoc-Best One

Hi Folks,
What would be the best method to migrate master and transactional data.(One time upload).
I am suggesting BAPI as we have internal thirdparty RFC calls while creating masterdata.(I guess we wouldnot get this RFC calls in recording).
I gone through the forum but i didnot get convincing answer.
Please help me in deciding.........
Thanks,
Krishna.

Hi
I am suggesting BAPI as we have internal thirdparty RFC calls while creating masterdata.(I guess we wouldnot get this RFC calls in recording).
As BAPI's are Remote Enabled Function Module. I think in your scenario BAPI's should work well for you.
Regards,
Vishwa.

Issue in using BAPI object in LSMW.

Hi Friends,
we are using BUS1506 business object(BAPI) to change settlement data(RESCSU) in LSMW.
We have done the ALE configuration for this object, which is needed to create Inbound idoc.
Here we are getting the error message as "Create a partner profile for message
'BUS1506_CHANGE'
Infact we have created the partner profile for "BUS1506_CHANGE" , But still this error is coming.
Please lemme know if anybody has got experience in such scenarios.
Regards.
Santosh.
00-45-50108553.

Hi, I don't clear when the error message occur, but as I know in the BAPI-LSMW mode, the LSMW can only handle the IDOC send to local, not partner server.
As the IDOC port of LSMW is a file port, so all the IDOC only can send to local.

Sales order details uploading using BAPI method in LSMW

Hi Guys,
Sales order details uploading using BAPI in LSMW, could you please suggest me, is any standard method or programs is available for this.
I have some queries about this.
1) One header line having multiple line items, in this case we able to upload use the LSMW method,
if possible please tell me the steps.
2) Do we need to do any config changes while uploading data?
3) Flat file should be which format.
4) Steps to process each step wise if possible.
Please help me
Thanks,
Gourisanakar.

Hi Gouri Sankar,
would you be able to upload the sales orders with multiple line items using BAPI LSMW?
if so could you plz suggest?
Thanks in advance.
Suresh/

NOTES ON ALE, IDOC, BAPI, BADI, LSMW

HI,
     CAN ANYBODY GIVE ME NOTES OR ANY TYPE OF DOCUMENTATION ON ALE, IDOC, BADI, BAPI, LSMW. I AM NEW TO THIS CONCEPTS. SO PLEASE HELP ME.
                   THANKS IN ADVANCED.

Hi
Creation of Custom IDOc type and message Type
First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.
take the Basis help to create them.
1.First create segments in WE31 Tcode with the required dataelements
2.Create the Basic Idoc Type in WE30
   release the Segments and IDOC type.
3.Create Message type in We81
4.Assign the message type to IDOC type in WE82 T code
5.Create the process code in We41 (for Outbound) WE42 (for Inbound)
6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for    Inbound) Outbound Fun module
7.Create Workflow setting if needed ..
8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0
9.Define setting for fun module in BD51
10.In BD51 Define the settings for Fun module..
10.Assign the Processs Code to Fun mod`ule
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
DEFINING THE BADI
1) execute Tcode SE18.
2) Specify a definition Name : ZBADI_SPFLI
3) Press create
4) Choose the attribute tab. Specify short desc for badi.. and specify the type :
multiple use.
5) Choose the interface tab
6) Specify interface name: ZIF_EX_BADI_SPFLI and save.
7) Dbl clk on interface name to start class builder . specify a method name (name,
level, desc).
Method level desc
Linese;ection instance methos some desc
8) place the cursor on the method name desc its parameters to define the interface.
Parameter type refe field desc
I_carrid import spfli-carrid some
I_connid import spefi-connid some
9) save , check and activateadapter class proposed by system is
ZCL_IM_IM_LINESEL is genereated.
IMPLEMENTATION OF BADI DEFINITION
1) EXECUTE tcode se18.choose menuitem create from the implementation menubar.
2) Specify aname for implementation ZIM_LINESEL
3) Specify short desc.
4) Choose interface tab. System proposes a name fo the implementation class.
ZCL_IM_IMLINESEL which is already generarted.
5) Specify short desc for method
6) Dbl clk on method to insert code..(check the code in AAA).
7) Save , check and activate the code.
Some useful URL
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
www.sapgenie.com/publications/saptips/022006%20-%20Zaidi%20BADI.pdf
http://www.sapdevelopment.co.uk/enhance/enhance_badi.htm
http://help.sap.com/saphelp_nw04/helpdata/en/04/f3683c05ea4464e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/e6/d54d3c596f0b26e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/eab541c5b63031e10000000a155106/frameset.htm
Now write a sample program to use this badi method..
Look for BBB sample program.
AAA
data : wa_flights type sflight,
it_flights type table of sflight.
format color col_heading.
write:/ 'Flight info of:', i_carrid, i_connid.
format color col_normal.
select * from sflight
into corresponding fields of table it_flights
where carrid = i_carrid
and connid = i_connid.
loop at it_flights into wa_flights.
write:/ wa_flights-fldate,
wa_flights-planetype,
wa_flights-price currency wa_flights-currency,
wa_flights-seatsmax,
wa_flights-seatsocc.
endloop.
BBB
*& Report ZBADI_TEST *
REPORT ZBADI_TEST .
tables: spfli.
data: wa_spfli type spfli,
it_spfli type table of spfli with key carrid connid.
*Initialise the object of the interface.
data: exit_ref type ref to ZCL_IM_IM_LINESEL,
exit_ref1 type ref to ZIF_EX_BADISPFLI1.
selection-screen begin of block b1.
select-options: s_carr for spfli-carrid.
selection-screen end of block b1.
start-of-selection.
select * from spfli into corresponding fields of table it_spfli
where carrid in s_carr.
end-of-selection.
loop at it_spfli into wa_spfli.
write:/ wa_spfli-carrid,
wa_spfli-connid,
wa_spfli-cityfrom,
wa_spfli-deptime,
wa_spfli-arrtime.
hide: wa_spfli-carrid, wa_spfli-connid.
endloop.
at line-selection.
check not wa_spfli-carrid is initial.
create object exit_ref.
exit_ref1 = exit_ref.
call method exit_ref1->lineselection
EXPORTING
i_carrid = wa_spfli-carrid
i_connid = wa_spfli-connid.
clear wa_spfli.
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm
and
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf7940e11d295df0000e82de14a/frameset.htm
BAPI
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
ALE
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
LSMW
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
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
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward points if useful
Regards
Anji

LSMW - BAPI - BUS1112 - needed 2 LSMW

Hello all,
I followed the blog post below in attempting to use legacy system migration workbench to load cost center hierarchy data. My input file has 19 records. The first record is a comment line defining the file. The second record contains the controlling area. Records 3 through 19 contain cost center hierarchy data.
When the Idocs are created, the first Idoc has segment one populated, but not segment two. All of the following Idocs have nothing in segment one, but segment two is populated correctly. The data file is attached.
I would've expected that when the Idoc is created it would have a segment one record and 17 segment two records.
I'm sure this must be some configuration that I set up incorrectly. But I'm not quite sure what to look at what or what needs to be changed.
Any insight would be greatly appreciated.
Bruce
scn.sap.com/community/erp/financials/blog/2012/08/10/loading-cost-center-hierarchy-cch-into-sap-using-bapi-lsmw
The solution I used was to create 2 LSMW objects.
1. ceate all cost center groups at level 0. Use the following BAPI settings:
BUS1112
Cost center group
ADDNODE
COSTCENTERGROUP_ADDNODE
COSTCENTERGROUP_ADDNODE01
2. set the parent child relationships using the following BAPI settings:
BUS1112
Cost center group
CREATE
COSTCENTERGROUP_CREATE
COSTCENTERGROUP_CREATE01

In your lsmw mapping, set the value of 'context' as 0001.
This will solve your problem.
Bijay

Mass Change ERS in PO + BAPI

Hi All,
I need to make mass change in lot of PO at itme detail level. I need to uncheck ERS and GR based IV check box in invoice tab.
I dont want to make use of Mass change tcode for this as it cause lot of work and chances of manual error are lot.
I have never used BAPI in LSMW but I have come accross BAPI for PO Change......I am pretty good at recording method in LSMW but I think that wont help me in this case due to the table control in PO. I have also found a tutorial on BAPI + LSMW for PO creation so I got some rough idea for it.
Can someone tell me the sturucture I should use for the BAPI in LSMW for my requirement and the points which I need to take care of. also tell me do I have to actiavte the inbound idoc processing for it.
Please guide....
Also suggest if i need to create 2 flat files for this ....like 1 for header and antoher 1 for item level.
Edited by: Sap: IN on Apr 30, 2011 2:36 PM

I am able to map my flat file with the structure sucessfully
But I am facing problem
1. IDOC segment E1BPNEPOITEM does not have the field GR based IV and ERS.
requirement : as I want to remove these 2 check boxes from couple of PO for different line item I have mapped the fields with the segement mentioned above but I am passing blank value from my flat file...so in the display imported data I am getting PO number and line item number and for those 2 field blank value.
due to this in the step display converted data those 2 fields along with all the fields of the segement itme data are blank and so the IDOC gets created with out any field in the item segment.
question: how to over come this problem ...I need thoes 2 field in the segment but with balnk value. as the check box need to be unchecked in the po.
Edited by: Sap: IN on May 1, 2011 11:56 AM

Upload Property Master Data through LSMW

I am using the following BAPI to upload the Property Data through LSMW.
Business Object: BUS1502
Method: CREATE
Message Type: BUS1502_CREATE
Basic Type: BUS1502_CREATE03
There are two issues which needs to be addressed and hope that this forum can help me out.
1. In this BAPI, i dont see the field mapping for Company Code and Business Entity, both mandatory fields for creating a Property record.
2. Skipping the first step, i reached the step "Start IDoc Generation" in LSMW and get the following error.
EDI: Table passed to EDI_SEGMENTS_ADD_BLOCK is empty.
Anyone encountered these issues? Suggestions to resolve these issues?
Hamdan

Hello Hamdan,
First of all, good decision to use BAPI + LSMW it is the best way to load DATA specifically in REFX. Here's answer to your questions.
1. Pass Company code, BE, other header level fields in E1BUS1502_CREATE structure. This is the main Header structure of the Baisc type you are using. Create source structure with these fields and mapp it to the BAPI fields and you are all set.
2. Check the EDI_DC40 element, or other structures if you are passing values. SAP/System will fill/populate these values on its own, do not pass any values example in fields DOCNUM, CREDAT, etc.
Good luck,
Jag

Cremas in LSMW(problem it is showing

hi friends,
i am going to get IDOC-LSMW, this sort of work on LSMW.i am doing this one first time. i have taken MESSAGE type : CREMAS, AND BASIC TYPE: CREMAS01, because i want to populate file data,(vendor details )which is equivalent of XK01 into to idocs.
In step 13.start idoc generation,
"no partner exist with the name.",type"<b></b>
i think problem with partner profile. Will you suggest me regarding this.
suppose if you have any document FOR lsmw-idoc with a example ,please send to my id:
[email protected]
Thanks in advance.
T.Balaji.

Thank you John for your Advice.To download this one we need to have login and password which cannot be created by us.
http://service.sap.com/lsmw.
understand problem.
if you have any material particularly IDOC-BAPI-LSMW.
PLEASE SEND THAT MY ID.
[email protected]
balaji.

BAPI LSMW

Similar Messages

Maybe you are looking for