bdc

Former Member — Tue, 04 Mar 2008 09:22:03 GMT

hai sir

how can we use 2 or more trasactions in session method.

Re: bdc

Former Member — Tue, 04 Mar 2008 09:24:00 GMT

hai sir

in real time ,,which is more useful for uploading. r they useing lsmw(bapi,idoc) methods.

plz they use give meterial , thank u

Re: bdc

Former Member — Tue, 04 Mar 2008 09:29:02 GMT

u can use call transaction twice with two different transaction code.

in case of session method :

Have one BDC_OPEN_GROUP, multiple BDC_INSERT s and one BDC_CLOSE_GROUP.

You should have multiple BDC_INSERT s for multiple transactions.

call function BDC_OPENGROUP.

Build BDC data and cal lBDC_INSERT for transaction 1

Build BDC data and cal lBDC_INSERT for transaction 2

Build BDC data and cal lBDC_INSERT for transaction 3

paas the tcodes to bdc_insert.

call function BDC_CLOSE_GROUP.

Re: bdc

Former Member — Tue, 04 Mar 2008 09:30:55 GMT

Step-By-Step Guide for LSMW using ALE/IDOC Method

Part One: To create IDOC structure

Step One: Run transaction WE31.Create Segment with name ‘ZEMP_SEG’.

Step Two: Input the fields for the segment structure, which would be required in LSMW for mapping purpose.

Step Three: Now, Go to Edit -> Set Release, so that you can use this segment in the R/3 system further.

Step Four: Run transaction ‘we30’ and enter IDOC structure name we want to create.

Here, IDOC structure name is ‘ZEMP_IDC’.

Step Five:

(A)Add segment created earlier to this IDOC type ‘ZEMP_IDC’.

The maximum and minimum repetitions can be from 000000000000 to 99999999999.

Choose any number rang as per requirement.

Now, Go back to earlier page and Click Edit-> Set Release.

(B)Create new Message type in transaction ‘WE81’.

Step Six: Go to transaction ‘SALE’. Click as marked in red color.

Now add two logical system names for sender and receiver ex. IDC64 and IDC87.

Step Seven: Now assign clients to the logical systems created.

Select the client of your current system as per decision to make that system sender or receiver.

After clicking on to Goto->Details , you come to following screen. Input receiver system ‘IDC87’ to client 800.

Here in our LSMW using IDOC method, no need to assign client to sender as we are doing Inbound IDOC Processing (i.e. Receiver side).

Step Eight: Run transaction ‘WE21’ to create File port. Give directory name as the location of your file to be read. Give dummy name for ‘Outbound file’ field. Step Nine: Run ‘SM59’ transaction to create RFC connection. Please make sure here connection type is ‘T’ for TCP/IP .

Step Ten: Run transaction ‘WE20’ to create partner profile for partner of receiver system (IDC87) i.e. sender system (IDC64).

Step Eleven: Create process code using ‘WE42’.

After saving this data, you go screen as below to attach function module to the process code. The process code is the representation of the function module for inbound idoc processing.

Step Twelve: Now you can use this process code in the inbound parameters of the partner’s profile.

Part Two:

Following are the steps to be performed on LSMW side.

Step One:

Enter the project, sub-project and Object name for our scenario.

Step Two:

Click the first radio button ‘Maintain Object Attributes’ , execute and enter the message name and IDOC name into the screen as follows.

Step Three:

Click radio button ‘Maintain Source Structures’ and execute to create new source structure as follows.

Step Four:

Click radio button ‘Maintain Source Fields’ and execute to enter the fields in the source structure. Here these fields are same as the fields in segment of the IDOC created earlier.

Step Five:

Click radio button ‘Maintain Structure Relations’ and execute to create relationship between source and target structure. Here target structure is Message type ‘ZEMP_MSG’.

Step Six:

Click radio button ‘Maintain Field Mapping and Conversion Rules’ and execute to create field mapping and a conversion rules between source structure and target structure.

Step Seven:

Click radio button ‘Maintain Fixed Values, Translations, User-Defined Routines’ and execute to assign fixed values to any field, to call user defined routines etc. These activities are not required in our scenario.

Step Eight:

Click radio button ‘Specify Files’ and execute to assign file on the local workstation to the LSMW to read. The file has contents as shown below.

And now we specify the location of file here.

Step Nine:

Click radio button ‘Specify Files’ and execute to specify file to source structure as follows.

Step Ten:

Click radio button ‘Read Data’ and execute to read file from local workstation as per path specified.

Step Eleven:

Click radio button ‘Display Read Data’ and execute to display data just read.

Step Twelve:

Click radio button ‘Convert Data’ and execute to create a file with extension ‘.conv ’.

Step Thirteen:

Click radio button ‘Display Converted Data’ and execute to display the converted data.

Step Fourteen:

Click radio button ‘Start IDoc Generation’ and execute to generate the IDOC from the data provided and structure mapping done earlier in this document. For this purpose, we cam use the converted file in step twelve. After successful generation of IDOC, below shown message is displayed.

Step Fifteen:

Click radio button ‘Start IDoc Processing’ and execute to process the IDOC by inputting necessary selection parameters.

Step Sixteen:

Click radio button ‘Create IDoc Overview’ and execute to show status and details of IDOC generated. This screen is similar to ‘WE02’ or ‘WE05’ transaction.

Here , as you can see , the status of IDOC is OK (Green color Bubble) and hence confirms successful processing of IDOC.

Step Seventeen:

Click radio button ‘Start IDoc Follow-Up’ and execute to reprocess the IDOC if not posted or generated properly initially.

Go through following links.

Direct Input

http://saptechnical.com/Tutorials/LSMW/VendorDirectInput/page1.htm

Recording

http://saptechnical.com/Tutorials/LSMW/VendorRecording/page1.htm

IDoc Method

http://saptechnical.com/Tutorials/LSMW/IDocMethod/IDocMethod1.htm

BAPI

http://saptechnical.com/Tutorials/LSMW/MMBAPI/Page1.htm