LSMW via IDOC

I need to know how to use LSMW using IDOCS.Preferably in steps.
WAiting for the reply.
Ajit

hi,
check this one
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
steps for LSMW: detail documnets: http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

Similar Messages

Lsmw via idoc method

Hi
Experts can u let me know the settings to be made while updating the data in lsmw via idoc method.....
thanks in advance

hi,
check this one
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
steps for LSMW: detail documnets: http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

Urgent : LSMW using Idocs

Hi Friends...kindly send me step by step procedure on how to do LSMW using Idocs only. I know how to do LSMW using all other methods other than Idocs. So
Kindly send me procedure or any good document on LSMW using Idocs. Thanks in advance.

Hi Satyesh T
Go through the following Steps for LSMW Using IDoc
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.
Thanks & Regards
Sreeni

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

Master data upload via LSMW using IDoc method

Dear all,
I know this has been a topic of many discussions but I would like to ask you is to share your thoughts and possibly experience with the following scenario:
Interface between non-SAP system and SAP system has to be built whereby master data gets created in the non-SAP system and has to be uploaded into SAP. This is a process that needs to be performed on a constant basis and hence my question: is there a way that the MD upload takes place in the background via LSMW with IDoc? Or any other way, for instance, with a flat file, etc.?
Thank you very much for your input!
Regards,
Miro

Miro - It depends upon many factors
1. Number of source systems
2. Volumn of recorsds ( Data to be loaded)
3. Transformation needed or not needed from S to D ( source to destination), We may consider it as
business rules/mapping
Based on above you may segrigate the objects related to data, eventually you can shoose approach of loading in SAP,
As if straigt forward load for some 20k-30K records ( Just a file load on regular basis), one to one mapping then go for LSMW, if some complex transformation logic needed then go SAP data services implementation. best part here is if you multiple sources that can be handeled here.
Accordingly you can proceed ...
Hope it helps.
Best !
Deep

Data transfer thru lsmw via bapi

how to perform data transfer thru lsmw via bapi.
Thanks.
Regards
Rama

HI
BAPI stands for Business API(Application Program Interface).
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
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://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
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
u can check the below the material also
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
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
BAPI - BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.
BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.
LSMW- No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
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.
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.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
Check your procedure using this 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
What are the methods to migrate data from a legacy system to SAP?
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
Execute.
3. Maintain object attributes.
Execute
select Batch Input recording
goto->Recording overview
create
recording name.
enter transaction code.
start recording
do recording as per ur choice.
save + back.
enter recording name in lsmw screen.
save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
Here you have to enter the name of internal table.
display change
create
save + back
3. MAINTAIN SOURCE FIELDS.
display change
select structure
source_fields->copy fields.
a dialogue window will come .
select -> from data file
apply source fields
enter No. of fields
length of fields
attach file
save + back
4. MAINTAIN STRUCTURE RELATIONS
display change
save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
display change
click on source field, select exact field from structue and enter
repeat these steps for all fields.
save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
execute
save + back
7. SPECIFY FILES.
display change
click on legacy data
attah flat file
give description
select tabulatore
enter
save + back
8. ASSIGN FILE
execute
display change
save + back
9. IMPORT DATA.
execute
display change
save + back
10. DISPLAY IMPORTED DATA
enter ok, it willl show records only.
back
11. CONVERT DATA
execute
display change
save + back
12. DISPLAY CONVERTED DATA
execute
display change
save + back
13. CREATE BATCH INPUT SESSION
tick keep batch input folder
F8
back
14. RUN BATCH INPUT SESSION.
sm35 will come
Object name will be shown here
select object & process
Regards
Pavan

Working on LSMW using IDoc method for processing Open Sales Orders

We are currently in middle of creation of a new instance of production for a different Business SBU. We are looking to utilise the LSMW tool using IDocs for uploading / transferring the open orders to the new box. If some one has worked on LSMW using IDocs, please get in touch and if you could share any documents on the process of utilising the LSMW tool using Idocs for any kind of conversions, it would be great. The following is a sample case.
1. Each order will have multiple segments with different qualifiers under various segments.
2. Multiple line items would be available under each order.
Issues we are currently looking to solve :
1. How do you manage to loop through the qualifiers during processing for the same segment.
2. How do you prepare the tool to recognise the multiple line items of the same order.
3. What kind of strategy needs to be used to create the input data file(s). Like, splitting the header and detail level information ?
Note : The volume of data we are looking at is somewhere around 40-60 thousand orders worldwide.
Thanks in Advance.

hI vikram check this link
and reward points if helpful
http://www.****************/Tutorials/LSMW/IDocMethod/IDocMethod1.htm
http://www.jt77.com/system-dynamics/model-01395.html

Creation of sales order via IDoc ORDERS05 - specify a reason of rejectio

Hi,
I want to create a sales order via IDoc (type:ORDERS05), i specify for an E1EDP01 segment a reason of rejection (ABGRU),
The sales order is created succefully by calling the FM IDOC_INPUT_ORDERS but the order quantity of the item where i have specified a reason of rejection is equals to 0.
Is this normal? i want that this will take 3 value either 0?
Could anyone help me?
Thx

Hi,
Thank you for ur answer.
I've followed the procedure that you have explained and the Quantity 3 have been succefully passed to VA01 but is set to zero when i execute the next OK-CODE (=UER2, i think it is llike Enter button ). I simulate the same procedure by creating a sales order on VA01 and i've finally found the problem : at item level, if i enter the Material (MATNR), the order Quantity (KWMENG) and the Reason of rejection (ABGRU), the quantity is set to zero after clicking the enter button ; but if i enter only The material and The quantity followed by enter button, and enter after the Reason of rejection, it works fine, the Quantity doesn't change.
What is the solution that you propose to me?
I've try this one on debugger mode:
The FM which interpret the Idoc create the sales order by CALLING TRANSACTION 'VA01' USING bdcdata....
I've modified the bdcdata to implement the sequence of the steps before (MATNR + QTY <ENTER> ABGRU <ENTER>).
1. Is it possible to code this modification?
2. Is there a way to structure the Idoc for having this sequence in bdcdata?
Thanks in advance!
Narivelo

Credit Memo request with reference to Billing Document number via IDoc

Hi,
I want to create credit memo request with reference to billing document number via IDocs.
I have tried through ORDERS05, but when I process I saw that it is only processing with reference to contract number or quotation.
So is any other way of creating credit memo request creation with reference to Billing document number via IDocs?
Thank you in advance.
Regards,
Santhi

Please Help... it is Urgent... Thank you

PM Notification from ERP 6 to ERP 4.7 via IDOC

Hallo,
can you help me? I'll sent an PM notification from an ERP6 to an ERP 4.7 via IDOC an the same back. Did I've a chance to do this without a lot of programming with standard Function modules for example. I'm interested in all solutions. The ERP 6 side I've configured, with a SAP standard message type INOTIF and process code /ISDFPS/NO01 that works all fine. The IDOC receives in the ERP 4.7, but I can't handle it on this side. Changes in on ERP must sent to the other side.
Thank you for all your help!
Best regards
Martin

Hi Tony
the RFC user-id needs to be a COMMUNICATION user (or CPIC, for older releases).
Martin
IGNORE WHAT I JUST SAID..... Do not use Communication type users at all anymore. Use SYSTEM / SERVICE users only....
The reasoning behind this is well explained in [User Type Communication|User Type Communication]. You can also check the [Best Practice - How to analyze and secure RFC connections |http://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections] wiki entry, however, it doesn't really help on debugging errors.
SAProuter String: /H/xxx.xxxxxx.com/S/<;saprouter_port>/W/<saprouter_pwd>/H/
Target Host: /H/xxx.xxxxxx.com/S/<;saprouter_port>/H/<server_name>.<domain><local>/H/
You don't appear to be specifying the saprouter password in your SM59 router string
Edited by: Martin English on Oct 6, 2010 3:33 PM

Problem in product creation via IDOC CRMXIF_PRODUCT_SAVE

Hello,
For our Product migration, we are trying to use LSMW, by IDOC, using Message Type CRMXIF_PRODUCT_SAVE, and IDOC Type CRMXIF_PRODUCT_SAVE01. However, each IDOC fails with the same errors each time, which are:
- Data cannot be maintained for set type COMM_PR_SHTEXT
- Data cannot be maintained for set type COMM_PR_UNIT
- Assign a base category to the product
- Error status 'A' calling validation service
- Validation error occurred: Module COM_PRODUCT_MAT_VALIDATE , BDoc type P
I searched alot and found no sure solution... the hierachy/category I created is specific, and I see no SAP standard hierachies/categories containing these set types COMM_PR_SHTEXT and COMM_PR_UNIT.
Furthermore, I dont see these set types in the list when I try to add them to my specific category. Are they truely standard SAP set types??
If so, how do I get around these IDOC errors and post successfully the IDOC/product creation??
Thanks,
Tim

Dear Tim,
Please check if the settypes COMM_PR_UNIT and COMM_PR_SHTEXT are
assigned to the mentioned category in transaction COMM_HIERARCHY.
Settype COMM_PR_SHTEXT contains the description of the product.
You want to maintain the UOM and this is stored in settype
COMM_PR_UNIT and the settype will also be recommended.
Additionally, please ensure that you have added a default category
in the customizing: Path: spro > EPB professionel > SRM Server >
Master Data > Content Management > Define Mapping for Product Categories
Hope this information is helpful. Please reward points!
Gerhard

Transfer of data from APO to ERP via IDOC

Hi,
I know we can transfer the of transactional data(Planned orders) from APO to R/3 is done via CIF.
Suppose if I need to transfer the same via IDOC instead of CIF how can I do it?
Let me know the steps to follow and way to find out how the data got transferred by IDOC?
For e.g. When I have transfer a planned order from APO to ERP, the data should be populated in the IDOC LOIPRO01 on the ERP side.
Cheers,
Simha.

Hi,
For a thouht If you want to use that IDOC data to be transfer to an other system from R/3 then let the data flow through CIF and in INBOUND exit wright code to create IDOC.
But Iam not sure whether it works.
Please eloborate requirement.
Regards,
Kishore Reddy.

Error message mes when trying to send PO via IDOCS to another system?

Hi Abap expert,
I am getting wired message what I ma trying to send PO via IDocs to other SAP system.
I went to all partner , port configurations on WE20 and everything there seems to be fine but once I go to ME23N, then GO TO -> MESSAGES , than opens another windows when you key in MESSAGE CONTROL DATA that have been mantained
in the outbound parameters in the PARTNER PROFILE configurations.Then I am getting the message :
'No communication data has been defined for transmission medium 6'-----
The LED on "PO:output screen' is YELLOW and never gets green.
Can someone tell me how to overcome this and send my PO Idocs?Please some more details will be appreciate it!
Thank you much eveyone!
Boby

Hi,
Go and check it in NACE tcode, whether , Condition type, output types are maintained or not? if not maintained, Maintain it for 6 -PO for EDI.
Hope this is the error you are getting.
Thanks
Manju

Credit/Debit Memo Request with reference to Billing document via IDoc

Hello Experts,
It seems SAP doesn't support Credit/Debit Memo Request with reference to Billing document via IDoc. Via IDoc, we can create sales document only with reference to contract or quotation but not with reference to billing/invoice document.
Wanted to check if anybody came across such requirement and what would be the best way to acheive (Other than custom program using BAPI).
Additional Information: Its ECC 6.0 Environment with AFS 6.03
Appreciate your help.
Thanks,
Shekhar.

Please Help... it is Urgent... Thank you

Creating a BP in CRM through LSMW using IDOC

I am trying to create a buss partner in crm through LSMW using IDOC:
Message Type: CRMXIF_PARTNER_SAVE_M
Basic Type: CRMXIF_PARTNER_SAVE_M02
I get an error: "No update is defined for BP role 000000".
I am also filling
IDENTIFICATIONCATEGORY: CRM001
IDENTIFICATIONNUMBER: 12345678
However i get this error only if the external ID does not exist in table BUT0ID.
otherwise if the external ID is present in table BUT0ID and the object task is "U"pdate, the BP is saved.
Has anybody worked on BP creation using IDOCs? If yes please guide me.

Hi,
This Check Box is required for Archiving Business Partners from the System. You can have a full idea about the same from the link below [Archiving Business Partners|http://help.sap.com/saphelp_crm60/helpdata/en/52/cff837a9aae651e10000009b38f8cf/frameset.htm]
Also have a look at the following [Introduction to Data Archiving (CA-ARC)|http://help.sap.com/saphelp_crm60/helpdata/en/8d/3e4c11462a11d189000000e8323d3a/frameset.htm]
Hope this helps.
Thanks,
Samantak.

LSMW via IDOC

Similar Messages

Maybe you are looking for