Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

LSMW

Former Member

‎08-02-2006 5:17 PM

0 Kudos

Has anybody created LSMW using IDOC and BAPI.

Can anybody tell me the procedure to create

an LSMW using these two.

5 REPLIES 5

Former Member

‎08-02-2006 5:29 PM

0 Kudos

Hi Kevin,

Please check this..

http://help.sap.com/saphelp_nw2004s/helpdata/en/ad/2d54a41d7011d2b42e006094b944c8/frameset.htm

cheers,

Prashanth

P.S Please mark helpful answers

Former Member

‎08-02-2006 5:32 PM

0 Kudos

check this thread

Regards,

Santosh

Former Member

‎08-02-2006 5:39 PM

0 Kudos

hi kevin,

check it out

3.9 Preparations for Using IDoc Inbound Processing

IDocs (Intermediate Documents) were developed for exchanging messages between different systems (R/3 ó R/3; R/3 ó R/2; R/3 ó non-SAP system).

Since it is a standard interface to the R/3 applications, this technique can also be used for transferring data.

To do this, however, some presettings and preparations are required (settings have to be done for eache project). For a summary of these requirements see Settings ® IDoc inbound processing in the LSM Workbench.

· The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:

Port: LSMW

Name: Legacy System Migration Workbench

Version: 3 (IDoc record types SAP Release 4.x)

Outbound file Please enter a (dummy) physical directory and a file name, i.e. ‘filelsmw’

· As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous. SAP recommends:

Port: assigned by the system

Version: 3 (IDoc record types SAP Release 4.x)

RFC destination: Name of R/3 System

Name of port: Legacy System Migration Workbench

· Then the partner type should be defined or selected. SAP recommends:

Partner type: "US" (User)

As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:

Partner type: Create US

Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES

Form routine: READ_USER

Short description: any

· Finally a partner number should be defined or selected. SAP recommends:

Partner number: LSMW

Partner type: US

Partner status: A (active)

Type: US

Language: DE or EN

Person in charge: Your user ID

· Activate IDoc inbound processing

¾ Confirm with "Yes" (to be done once for each system)

· Verify workflow customizing (to be done once for each system)

¾ The following entries of the workflow runtime system should be marked with a green check mark:

· Workflow Administrator maintained

· Workflow RFC destination completely configured

· Generic decision task classified completely

· Sending to objects and to HR objects is active

¾ To do this, you can start automatic customizing. After this you should set item "Monitoring job for work items with errors" to "not scheduled". (This means that you unmark the ID "Monitoring of WIs with temporary errors".) If you do not do this, the R/3 system tries over and over again to post incorrect IDocs created during data migration.

¾ Check the function with Test RFC destination. The following message should be displayed:

'Ping' executed successfully. The RFC destination for the SAP Business Workflow is fully configured.

If u find it useful mark the points

if u need more info shoot me a mail to callnaveen@gmail.com

i will send it to you

Regards,

Naveen