Doubt in bdc and ale reg

using we can transfer the data from one system and another system. in ale also we can do same thing. what is the need of using ale

BDC is used in scenarios where a company decides to do away with an existing ERP system and choses to use a SAP R/3 system in its place(Like from Oracle to SAP, or from any legacy system to SAP).
In the process, the company wil store all the legacy data in flat files before discarding the original system.
The flat file data, will have to be uploaded into the R/3 System again. It such cases BDCs/ Batch Iput programs are used.
ALEs are used in a totally different scenario.
If the company is using two loosely coupled sap systems, and the same data is to be maintained in both the systems, then you will use ALE concept.
It is like latching them together and changes made to one system are automatically refelected in the other system as well.
Regards,
Ravi

Similar Messages

Is BDC and ALE taking a back seat after the introduction of Netweaver

Hello guys
I have heard lot of people saying that after Netweaver XI's introduction to the market, BDC and ALE are taking back seat in the market. Is this true?
Are there any links where I can read some good articles on this comparison in terms of both sales pitch as well as from a technical point of view.
Thanks
Ram

Hi,
I dont think so, Though ALE will be used between SAP to Non SAP, in most of the real time scenarios we can see ALE have been using in between SAP to SAP only. In this case we no need to use XI instead of ALE.
Coming to the BDC, since there are lot of middle ware already existed in the market, i dont think customer can switch to XI immediately. may be it will take some time. In some cases we need to use only BDC.
Thanks
Jaya

Doubt in BDC

I have a doubt in BDC,
They used a standard SAP program (RSBDCBTC_SUB and RFBIBL00) for upload the data for the transaction FBB1. they dont want the particular record .
They used a session method for upload the data.
I know only the session name. how I can delete the particular record.
Once processed the session.
Is it possible to delete the delete the record.
Help me regard this.

Priya,
here i can suggest u one thing
if u want to know the program r report related to that session
just go to sm35
select the session then go with analysis
then in the screen u will get the screens used in that particular program
when u double click on those screens control leads to that respected screen
in that if u go with system - > status u will get all the details of the program
when u double click on the program control leads into that program
then there u can find all the details related to tables and everything
i think it helps for u
Regards,
naveen

Beginner ABAPer asking Doubts in BDC

Hi Guyz,
I am a beginner in ABAP. Here i am sending some doubts on BDC . Any Kind of help will be highly Appreciated.
Thanks,
SAM
1>How do we handle all the scrolling funcions(page ups, page downs atc), and values entered into table controls in BDC ?
2> How do you take care of screen resolution in BDC?

1) page up and page down ... i donno the actual procedure but this is one of the method...
i hope this answers both of ur questions...
After encountering the screen, say u need to select a field in a table. One of the methods is to press Control F on that screen then enter the field name which u want.. and press enter.. then that field will be the first field in the screen resolution ....
just try this for a normal table like spfli... after going to the table display in SE11 press control F or the Binoculars icon.. then u will get a small window u just type in the name of the field u want.. and press enter .. see what happens,
suppose ..
have opened this spfli in se11 transaction and in display mode..
Now 'PERIOD' is the field which is not there in the resolution..
so i have opened the find option ,provided the field name PERIOD in the field of search window.
then pressed enter. Now i will get the same screen( spfli display screen ) with period as the first field in that resolution .. Now i can do whatever is i want with this field.. here i have double clicked on the domain of the field PERIOD.
so u analyse this code....
*spfli display screen..
perform bdc_dynpro using 'SAPLSD41' '2200'. ( * spfli display screen , u can use ur screen number here )
perform bdc_field using 'BDC_OKCODE'
'=FIND'. (* To open the find window )
perform bdc_dynpro using 'SAPLSD41' '0114'. ( * This is the find window )
perform bdc_field using 'BDC_CURSOR'
'RSDXX-FINDSTR'.
perform bdc_field using 'BDC_OKCODE'
'=CANC'. (* OK_CODE for enter )
perform bdc_field using 'RSDXX-FINDSTR'
'PERIOD'. ( * Here i am giving the field name which i want to search or which is not there in the resolution or u can give a vaiable name which contains the value <FIELD NAME> ).
( Now i got the spfli display screen with period as the first field in the screen resolution )
perform bdc_dynpro using 'SAPLSD41' '2200'. (*The previous spfli display screen )
perform bdc_field using 'BDC_OKCODE'
'=WB_SELECT_OBJECT'. (* OK_CODE to double click on the domain of the field PERIOD )
perform bdc_field using 'BDC_CURSOR'
'DD03D-ROLLNAME(01)'.
reward helpful answers...
sai ramesh

Variant Configurator and ALE

Has anyone had any experience with using ALE to transport all aspects of the Variant Configurator set-up to another SAP instance? We had planned to go this route, but have had people tell us that they wrote custom programs to download data from one instance and then use BDC's to load them in the new system. Is there a problem with using ALE for VC set-up data or anything we should be aware off?
Regards.

Hi Cynthia,
I have done this in the past. Definitely ALE is the way to go over BDC's etc.
The only thing you have to watch is the sequence that you send the data in. For example you must send dependency function module definitions before you can send any dependencies that call those functions. Otherwise you get an Idoc failure.
Where you get circular references (for example you have a characteristic which has a dependcy attached to it, and the dependency actually refers to the characteristic by name) then the best thing is to set the status of the dependency to deactivated, ALE it to the target system (syntax check will pass because its deactivated), ALE the characteristic, set the status back on the dependency, and then ALE it again.
Apart from occasional circular references, however, it works really well.
Another thing to watch is that when you set up your ALE distribution model, that you consider the possibility of concurrent development and ALEing between systems. For ease of administration, we set up our DEV system as the source for both QA and for PROD (rather than having DEV as source for QA and QA as source for prod) but this means that you shouldn't do any development on objects currently in QA as the latest changes will be ALE'd from DEV to PROD.
I think the general sequence of ALEing that worked the best was:
1. Characteristics
2. Function module definitions
3. Dependencies
4. Configuration profiles
I feel I have forgotten something there, but I guess you get the idea.
Last thing, you can't ALE the configuration profile user interface. So if you have designed your own layout for the characteristics (with tabs, and userexit buttons etc.) you have to recreate these manually in each environment. Not much fun when you have 10+ clients in your landscape. I kept meaning to write a program to handle it but, time got away from me.
Finally, you have to ask yourself why SAP didn't treat all this stuff as configuration though, and allow you to migrate using change requests. Wouldn't that be nice!!!
Hope that helps.
Cheers,
Brad

BDC and RFC

dear all, may I know what is the different between BDC and RFC?

Hi,

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.sap-img.com/abap/learning-bdc-
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

RFC
Remote Function Call:
RFCs are requests that an SAP component sends to invoke functions on remote systems, or calls that remote systems initiate to invoke functions on an SAP component.A process that can accept RFCs from SAP components. This allows SAP components to access functions in external systems. In SAP BC terminology, the process is called a Listener. Listeners are one or more threads on SAP Business Connector that wait for incoming requests from SAP components. Listeners are named and register with an SAP gateway to indicate that they are ready to accept requests. Listeners can accept RFC or tRFC requests.
Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously.
RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
RFCs manage the communication process, parameter transfer and error handling.
Have a look at this link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Please go through the following link. You will get good info on RFC & its types.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards,
Priyanka.

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

Doubt in concepts and scenarios where used

doubt in differentiating and scenarios for below.
statistics Vs document update      - i already know the definitions of V1 V2 V3 updates, pls dont give defn links
conditions Vs global filters in QD     and scenarios
btree/bitmap index         and scenarios
reconstruction Vs repair   and scenarios
already searched forums, didnt get satisfactory answer.
pls suggest.
Edited by: Swetha N on Jan 20, 2012 10:10 AM

Conditions - You want to get the top 10 customers, you can use condition to get the same. done during the execution, before displayign the data. last step in the report execution.
Filters - You can filter only particular plant, customer etc. will be done before query execution, kind of starting point for qery execution.
Btree / Bit map - in addition to Venkatesh said - Bit Map is read optimized and B Tree is write optimized.
Reconstruction - used in 3.x flow. if a request got deleted by request you can retriev it. Go to reconstruction tab and select the request and do reconstruction.
Repair - I guess you are asking repair full request, if it so, it is a way to pull the data from R3. with some selection that can be defined at the info package for example you found one purchase order with some incorrect data, what you do is delete selectively the purchase order from the system and do full repail request. You can define the same at info provider level.
Document update - you change a Purchase order from Me22n, the document will get update in the r/3 backend table EKKO EKPO etc. Statistical update is from the R/3 reporting table perspective, these are LIS tables.

How can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.

how can we use TABLE CONTROL in BDC and WORK FLOW of ABAP.?
please explain the important questions.

How to deal with table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen? Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
Now with the help of Poonam on sapfans.com developement forum, I find a method with which we can determine the number of visible lines on Transaction Screen from our Calling BDC program. Maybe it is useless to you, but I think it will give your some idea.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference in Static ASSIGN and Dynamic ASSIGN.
Now I begin to describe the step to implement my method:
(I use transaction 'ME21', screen 121 for sample,
the method using is Call Transation Using..)
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop. Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
 LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
 or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data: FixedLine type i, " number of fixed line on a certain screen
 LoopLine type i, " the number of lines occupied by one steploop item
 FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new " scrolling screen is empty, otherwise is 1
 Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
 pageno type i, " you need to scroll screen how many times.
 line type i, " number of lines appears on the screen.
 index(2) type N, " the screen index for certain item
 begin type i, " from parameter of loop
 end type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
 LoopLine type i (see step 1)
 FirstLine type i (see step 2)
 DataLine type i ( this is the item number you will enter in transaction)
 changing pageno type i (return the number of page, depends on run-time visible line in table control/ Step Loop)
 changing line type i.(visible lines one the screen)
data: midd type i,
 vline type i, "visible lines
if DataLine eq 0.
 Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
 pageno = DataLine div vline.
 if pageno eq 0.
 pageno = pageno + 1.
 endif.
elseif FirstLine eq 1.
 pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
 midd = ( DataLine - 1 ) mod ( vline - 1).
 if midd = 0 and DataLine gt 1.
 pageno = pageno - 1.
 endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
 FirstLine type i(see step 2)
 LineIndex type i(item index)
 changing Index type n. (index on the screen)
if FirstLine = 0.
 index = LineIndex mod Line.
 if index = '00'.
 index = Line.
 endif.
elseif FirstLine = 1.
 index = LineIndex mod ( Line - 1 ).
 if ( index between 1 and 0 ) and LineIndex gt 1.
 index = index + Line - 1.
 endif.
 if Line = 2.
 index = index + Line - 1.
 endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
 DataLine type i
 FirstLine type i
 loopindex like sy-index
 changing begin type i
 end type i.
If FirstLine = 0.
 if loopindex = 1.
 begin = 1.
 if DataLine <= Line.
 end = DataLine.
 else.
 end = Line.
 endif.
 elseif loopindex gt 1.
 begin = Line * ( loopindex - 1 ) + 1.
 end = Line * loopindex.
 if end gt DataLine.
 end = DataLine.
 endif.
 endif.
elseif FirstLine = 1.
if loopindex = 1.
 begin = 1.
 if DataLine <= Line.
 end = DataLine.
 else.
 end = Line.
 endif.
elseif loop index gt 1.
 begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
 end = ( Line - 1 ) * ( loopindex - 1 ) + Line.
 if end gt DataLine.
 end = DataLine.
 endif.
endif.
endif.
endform.
Step6 using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: <material>, <quan>, <indicator>.
data: name1(14) value 'EKPO-EMATN(XX)',
 name2(14) value 'EKPO-MENGE(XX)',
 name3(15) value 'RM06E-SELKZ(XX)'.
assign: name1 to <material>,
 name2 to <quan>,
 name3 to <indicator>.
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
 perform calrange using Line DataLine FirstLine sy-index
 changing begin end.
loop at DataTable from begin to end.
 perform calindex using Line FirstLine DataTable-LineIndex changing Index.
 name1+11(2) = Index.
 name2+11(2) = Index.
 name3+12(2) = Index.
 perform bdcfield using <material> DataTable-matnr.
 perform bdcfield using <quan> DataTable-menge.
 perform bdcfield using <indicator> DataTable-indicator.
endloop.
enddo.
An example abap program of handling Table Control during bdc programming.
REPORT zmm_bdcp_purchaseorderkb02
 NO STANDARD PAGE HEADING LINE-SIZE 255.
 Declaring internal tables *
*-----Declaring line structure
DATA : BEGIN OF it_dummy OCCURS 0,
 dummy(255) TYPE c,
 END OF it_dummy.
*-----Internal table for line items
DATA : BEGIN OF it_idata OCCURS 0,
 ematn(18), "Material Number.
 menge(13), "Qyantity.
 netpr(11), "Net Price.
 werks(4), "Plant.
 ebelp(5), "Item Number.
 END OF it_idata.
*-----Deep structure for header data and line items
DATA : BEGIN OF it_me21 OCCURS 0,
 lifnr(10), "Vendor A/c No.
 bsart(4), "A/c Type.
 bedat(8), "Date of creation of PO.
 ekorg(4), "Purchasing Organisation.
 ekgrp(3), "Purchasing Group.
 x_data LIKE TABLE OF it_idata,
 END OF it_me21.
DATA : x_idata LIKE LINE OF it_idata.
DATA : v_delimit VALUE ','.
DATA : v_indx(3) TYPE n.
DATA : v_fnam(30) TYPE c.
DATA : v_count TYPE n.
DATA : v_ne TYPE i.
DATA : v_ns TYPE i.
*include bdcrecx1.
INCLUDE zmm_incl_purchaseorderkb01.
 Search help for file *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 IMPORTING
 file_name = p_file.
START-OF-SELECTION.
 To upload the data into line structure *
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = p_file
 filetype = 'DAT'
 TABLES
 data_tab = it_dummy.
 Processing the data from line structure to internal tables *
REFRESH:it_me21.
CLEAR :it_me21.
LOOP AT it_dummy.
 IF it_dummy-dummy+0(01) = 'H'.
 v_indx = v_indx + 1.
 CLEAR it_idata.
 REFRESH it_idata.
 CLEAR it_me21-x_data.
 REFRESH it_me21-x_data.
 SHIFT it_dummy.
 SPLIT it_dummy AT v_delimit INTO it_me21-lifnr
 it_me21-bsart
 it_me21-bedat
 it_me21-ekorg
 it_me21-ekgrp.
 APPEND it_me21.
 ELSEIF it_dummy-dummy+0(01) = 'L'.
 SHIFT it_dummy.
 SPLIT it_dummy AT v_delimit INTO it_idata-ematn
 it_idata-menge
 it_idata-netpr
 it_idata-werks
 it_idata-ebelp.
 APPEND it_idata TO it_me21-x_data.
 MODIFY it_me21 INDEX v_indx.
 ENDIF.
ENDLOOP.
 To open the group *
PERFORM open_group.
 To populate the bdcdata table for header data *
LOOP AT it_me21.
 v_count = v_count + 1.
 REFRESH it_bdcdata.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0100',
 ' ' 'BDC_CURSOR' 'EKKO-LIFNR',
 ' ' 'BDC_OKCODE' '/00',
 ' ' 'EKKO-LIFNR' it_me21-lifnr,
 ' ' 'RM06E-BSART' it_me21-bsart,
 ' ' 'RM06E-BEDAT' it_me21-bedat,
 ' ' 'EKKO-EKORG' it_me21-ekorg,
 ' ' 'EKKO-EKGRP' it_me21-ekgrp,
 ' ' 'RM06E-LPEIN' 'T'.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '/00'.
 MOVE 1 TO v_indx.
*-----To populate the bdcdata table for line item data
 LOOP AT it_me21-x_data INTO x_idata.
 CONCATENATE 'EKPO-EMATN(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-ematn.
 CONCATENATE 'EKPO-MENGE(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-menge.
 CONCATENATE 'EKPO-NETPR(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-netpr.
 CONCATENATE 'EKPO-WERKS(' v_indx ')' INTO v_fnam.
 PERFORM subr_bdc_table USING ' ' v_fnam x_idata-werks.
 v_indx = v_indx + 1.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '/00'.
 ENDLOOP.
 PERFORM subr_bdc_table USING: 'X' 'SAPMM06E' '0120',
 ' ' 'BDC_CURSOR' 'RM06E-EBELP',
 ' ' 'BDC_OKCODE' '=BU'.
 PERFORM bdc_transaction USING 'ME21'.
ENDLOOP.
PERFORM close_group.
 End of selection event *
END-OF-SELECTION.
IF session NE 'X'.
*-----To display the successful records
 WRITE :/10 text-001. "Sucess records
 WRITE :/10 SY-ULINE(20).
 SKIP.
 IF it_sucess IS INITIAL.
 WRITE :/ text-002.
 ELSE.
 WRITE :/ text-008, "Total number of Succesful records
 35 v_ns.
 SKIP.
 WRITE:/ text-003, "Vendor Number
 17 text-004, "Record number
 30 text-005. "Message
 ENDIF.
 LOOP AT it_sucess.
 WRITE:/4 it_sucess-lifnr,
 17 it_sucess-tabix CENTERED,
 30 it_sucess-sucess_rec.
 ENDLOOP.
 SKIP.
*-----To display the erroneous records
 WRITE:/10 text-006. "Error Records
 WRITE:/10 SY-ULINE(17).
 SKIP.
 IF it_error IS INITIAL.
 WRITE:/ text-007. "No error records
 ELSE.
 WRITE:/ text-009, "Total number of erroneous records
 35 v_ne.
 SKIP.
 WRITE:/ text-003, "Vendor Number
 17 text-004, "Record number
 30 text-005. "Message
 ENDIF.
 LOOP AT it_error.
 WRITE:/4 it_error-lifnr,
 17 it_error-tabix CENTERED,
 30 it_error-error_rec.
 ENDLOOP.
 REFRESH it_sucess.
 REFRESH it_error.
ENDIF.
CODE IN INCLUDE.
Include ZMM_INCL_PURCHASEORDERKB01
DATA: it_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
DATA: it_MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA: E_GROUP_OPENED.
*-----Internal table to store sucess records
DATA:BEGIN OF it_sucess OCCURS 0,
 msgtyp(1) TYPE c,
 lifnr LIKE ekko-lifnr,
 tabix LIKE sy-tabix,
 sucess_rec(125),
 END OF it_sucess.
DATA: g_mess(125) type c.
*-----Internal table to store error records
DATA:BEGIN OF it_error OCCURS 0,
 msgtyp(1) TYPE c,
 lifnr LIKE ekko-lifnr,
 tabix LIKE sy-tabix,
 error_rec(125),
 END OF it_error.
 Selection screen
SELECTION-SCREEN BEGIN OF LINE.
PARAMETERS session RADIOBUTTON GROUP ctu. "create session
SELECTION-SCREEN COMMENT 3(20) text-s07 FOR FIELD session.
SELECTION-SCREEN POSITION 45.
PARAMETERS ctu RADIOBUTTON GROUP ctu. "call transaction
SELECTION-SCREEN COMMENT 48(20) text-s08 FOR FIELD ctu.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s01 FOR FIELD group.
SELECTION-SCREEN POSITION 25.
PARAMETERS group(12). "group name of session
SELECTION-SCREEN COMMENT 48(20) text-s05 FOR FIELD ctumode.
SELECTION-SCREEN POSITION 70.
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'N'.
"A: show all dynpros
"E: show dynpro on error only
"N: do not display dynpro
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 48(20) text-s06 FOR FIELD cupdate.
SELECTION-SCREEN POSITION 70.
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L'.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(20) text-s03 FOR FIELD keep.
SELECTION-SCREEN POSITION 25.
PARAMETERS: keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN COMMENT 48(20) text-s09 FOR FIELD e_group.
SELECTION-SCREEN POSITION 70.
PARAMETERS e_group(12). "group name of error-session
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 51(17) text-s03 FOR FIELD e_keep.
SELECTION-SCREEN POSITION 70.
PARAMETERS: e_keep AS CHECKBOX. "' ' = delete session if finished
"'X' = keep session if finished
SELECTION-SCREEN END OF LINE.
PARAMETERS:p_file LIKE rlgrap-filename.
at selection screen *
AT SELECTION-SCREEN.
group and user must be filled for create session
IF SESSION = 'X' AND
 GROUP = SPACE. "OR USER = SPACE.
 MESSAGE E613(MS).
ENDIF.
create batchinput session *
FORM OPEN_GROUP.
IF SESSION = 'X'.
 SKIP.
 WRITE: /(20) 'Create group'(I01), GROUP.
 SKIP.
*----open batchinput group
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = GROUP
 USER = sy-uname.
 WRITE:/(30) 'BDC_OPEN_GROUP'(I02),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ENDIF.
ENDFORM. "OPEN_GROUP
end batchinput session *
FORM CLOSE_GROUP.
IF SESSION = 'X'.
*------close batchinput group
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /(30) 'BDC_CLOSE_GROUP'(I04),
 (12) 'returncode:'(I05),
 SY-SUBRC.
ELSE.
 IF E_GROUP_OPENED = 'X'.
 CALL FUNCTION 'BDC_CLOSE_GROUP'.
 WRITE: /.
 WRITE: /(30) 'Fehlermappe wurde erzeugt'(I06).
 ENDIF.
ENDIF.
ENDFORM. "CLOSE_GROUP
 Start new transaction according to parameters *
FORM BDC_TRANSACTION USING TCODE TYPE ANY.
DATA: L_SUBRC LIKE SY-SUBRC.
*------batch input session
IF SESSION = 'X'.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = TCODE
 TABLES
 DYNPROTAB = it_BDCDATA.
 WRITE: / 'BDC_INSERT'(I03),
 TCODE,
 'returncode:'(I05),
 SY-SUBRC,
 'RECORD:',
 SY-INDEX.
ELSE.
 REFRESH it_MESSTAB.
 CALL TRANSACTION TCODE USING it_BDCDATA
 MODE CTUMODE
 UPDATE CUPDATE
 MESSAGES INTO it_MESSTAB.
 L_SUBRC = SY-SUBRC.
 WRITE: / 'CALL_TRANSACTION',
 TCODE,
 'returncode:'(I05),
 L_SUBRC,
 'RECORD:',
 SY-INDEX.
ENDIF.
Message handling for Call Transaction *
perform subr_mess_hand using g_mess.
*-----Erzeugen fehlermappe
IF L_SUBRC <> 0 AND E_GROUP <> SPACE.
 IF E_GROUP_OPENED = ' '.
 CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING
 CLIENT = SY-MANDT
 GROUP = E_GROUP
 USER = sy-uname
 KEEP = E_KEEP.
 E_GROUP_OPENED = 'X'.
 ENDIF.
 CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = TCODE
 TABLES
 DYNPROTAB = it_BDCDATA.
ENDIF.
REFRESH it_BDCDATA.
ENDFORM. "BDC_TRANSACTION
 Form subr_bdc_table *
 text
 -->P_0220 text *
 -->P_0221 text *
 -->P_0222 text *
FORM subr_bdc_table USING VALUE(P_0220) TYPE ANY
 VALUE(P_0221) TYPE ANY
 VALUE(P_0222) TYPE ANY.
CLEAR it_bdcdata.
IF P_0220 = ' '.
 CLEAR it_bdcdata.
 it_bdcdata-fnam = P_0221.
 it_bdcdata-fval = P_0222.
 APPEND it_bdcdata.
ELSE.
 it_bdcdata-dynbegin = P_0220.
 it_bdcdata-program = P_0221.
 it_bdcdata-dynpro = P_0222.
 APPEND it_bdcdata.
ENDIF.
ENDFORM. " subr_bdc_table
 Form subr_mess_hand *
 text *
 -->P_G_MESS text *
FORM subr_mess_hand USING P_G_MESS TYPE ANY.
LOOP AT IT_MESSTAB.
 CALL FUNCTION 'FORMAT_MESSAGE'
 EXPORTING
 ID = it_messtab-msgid
 LANG = it_messtab-msgspra
 NO = it_messtab-msgnr
 v1 = it_messtab-msgv1
 v2 = it_messtab-msgv2
 IMPORTING
 MSG = P_G_MESS
 EXCEPTIONS
 OTHERS = 0.
 CASE it_messtab-msgtyp.
 when 'E'.
 it_error-error_rec = P_G_MESS.
 it_error-lifnr = it_me21-lifnr.
 it_error-tabix = v_count.
 APPEND IT_ERROR.
 when 'S'.
 it_sucess-sucess_rec = P_G_MESS.
 it_sucess-lifnr = it_me21-lifnr.
 it_sucess-tabix = v_count.
 APPEND IT_SUCESS.
 endcase.
ENDLOOP.
Describe table it_sucess lines v_ns.
Describe table it_error lines v_ne.
ENDFORM. " subr_mess_hand
Also refer
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/bdc-table-control-668404
and
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
Regards,
srinivas
*reward for useful answers*

'Create' Push button is not working in BDC and LSMW while uploading G/L master data

Hello Experts:
I am facing the following problem:
While uploading G/L master data with the BDC program, 'create' push button is not working even after executing following lines.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ACC_CRE'.
Create G/L account screen is not coming in BDC. Please suggest me what to do.
Thanks !!

Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Hi Glen Anthony
Thank you for the reply Glen Anthony please take a look at the following code.
REPORT ZFI_BDC_FS00
 NO STANDARD PAGE HEADING LINE-SIZE 255.
*INCLUDE BDCRECX1.
TYPES : BEGIN OF STR,
 BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS, "Company Code
 SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR, "G/L Account Number
 KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS, "G/L Account Group
 XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT, "P&L statement account
 XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK, "Indicator: Account is a balance sheet account?
 TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML, "G/L account short text
 TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML, "G/L account short text
 WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS, "Account currency
 XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH, "Indicator: Only Manage Balances in Local Currency
 MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ, "Tax Category in Account Master Record
 XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO, "Indicator: Tax code is not a required field
 MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ, "Account is reconciliation account
 XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW, "Indicator: Open item management?
 XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES, "Indicator: Can Line Items Be Displayed by Account?
 ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA, "Key for sorting according to assignment numbers
 FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG, "Field status group
 XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB, "Indicator: Is account only posted to automatically?
 END OF STR.
DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
 IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
 TXT(4096) TYPE C OCCURS 0,
 MSG TYPE STRING,
 COUNT(5) TYPE N.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
 PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
* FIELD_NAME = ' '
IMPORTING
 FILE_NAME = MY_FILE
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
 EXPORTING
* I_FIELD_SEPERATOR =
* I_LINE_HEADER =
 I_TAB_RAW_DATA = TXT
 I_FILENAME = MY_FILE
 TABLES
 I_TAB_CONVERTED_DATA = ITAB[]
EXCEPTIONS
 CONVERSION_FAILED = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
* IMPLEMENT SUITABLE ERROR HANDLING HERE
ENDIF.
START-OF-SELECTION.
COUNT = 0.
LOOP AT ITAB.
*PERFORM OPEN_GROUP.
REFRESH IT_BDCDATA.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ACC_CRE'.
*PERFORM BDC_FIELD USING 'BDC_CURSOR'
* 'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
 ITAB-SAKNR. "'5'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
 ITAB-BUKRS. "'TATA'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=2102_GROUP'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-KTOKS'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
 ITAB-XPLACCT. "'X'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=2102_BS_PL'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-XBILK'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
 ITAB-XPLACCT. "''.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XBILK'
 ITAB-XBILK. "'X'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=TAB02'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-KTOKS'
 ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-XBILK'
 ITAB-XBILK. "'X'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_COA-TXT50_ML'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
 ITAB-TXT20_ML. "'G/L ACCOUNT'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
 ITAB-TXT50_ML. "'G/L ACCOUNT'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=TAB03'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
 ITAB-WAERS. "'INR'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
 ITAB-XSALH. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
 ITAB-MWSKZ. "'*'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
 ITAB-XMWNO. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
 ITAB-MITKZ. "''.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
 ITAB-XOPVW. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
 ITAB-XKRES. "'X'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
 ITAB-ZUAWA. "'1'.
PERFORM BDC_DYNPRO USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=SAVE'.
PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'GLACCOUNT_SCREEN_CCODE-XINTB'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
 ITAB-FSTAG. "'G019'.
PERFORM BDC_FIELD USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
 ITAB-XINTB. "'X'.
*PERFORM BDC_TRANSACTION USING 'FS00'.
CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
COUNT = COUNT + 1.
*PERFORM CLOSE_GROUP.
ENDLOOP.
CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
MESSAGE MSG TYPE 'I'.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
 CLEAR IT_BDCDATA.
 IT_BDCDATA-PROGRAM = PROGRAM.
 IT_BDCDATA-DYNPRO = DYNPRO.
 IT_BDCDATA-DYNBEGIN = 'X'.
 APPEND IT_BDCDATA.
ENDFORM.
* INSERT FIELD *
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
 CLEAR IT_BDCDATA.
 IT_BDCDATA-FNAM = FNAM.
 IT_BDCDATA-FVAL = FVAL.
 APPEND IT_BDCDATA.
* ENDIF.
ENDFORM.

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

Differences between BDC and LSMW

Hello SAP Gurus,
Kindly let me know the various differences between BDC and LSMW.
Also, please tell me the STEPS of the CUT-OVER PLANNING (Shifting of Data from the Legacy System to the SAP System). Here, the "Data" means which data? Please explain in details.
Looking for your early feedback.
Regards,
Kaushik.

Hi,
BDC- It is Batch data communication. Its used for data conversion from legacy system to SAP system. Only technical people can do it. Tcode is SHDB.
LSMW- It is legacy system migration workbench. Its also used for data conversion from legacy system to SAP system. But it is role of functional consultant.
There are 14 steps in LSMW. As soon as you complete the one step, automatically it will go to next step.
In general you can use LSMW. But if you want to transfer more than 40,000 data, then it is not possible in LSMW. That time you can take help of BDC.
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
Please refer this link,
[PP Cut over activity|http://www.sap-img.com/production/pp-questions-answers.htm]
Regards,
R.Brahmankar

Can any one explain me the relation between BDC and reports events?

hi experts.....
can any one explain me the relation between BDC and reports events? we are using report events in BDC programmes why?\
Is reports events occurs in each and every concept in ABAP i.e creating custom idocs, smart forms, sap scripts, dialog programmes, module pool technics?
thanks in advance

The forums are expert forums. So the first thing I would do is change your name.
It's like entering a grand prix in a car with a "Student Driver" sign.
Rob

Study material - IDOC and ALE systems ( MM integration ).

Dear All,
Can anyone provide me study material on MM integration with IDOC and ALE systems .
Rohan .

Please check these answered links:
ALE , EDI and IDOC with MM??
What is necessary for MM in IDOC and ALE??
idoc configuration in IDES??
Edited by: Afshad Irani on Jul 6, 2010 9:39 AM

Basic of IDOC and ALE

Hi All,
I am beginner of ALE IDOC.
Please tell me in details whats is Control Records, Data Records and Status Records in details.
Thnks in Advance,
awards will be given.
Ulhas

Hi,
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message u201CThe table is cross-client (see Help for further info)u201D. Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
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
go trough 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://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
u2022 Create a Customer Distribution Model (CDM);
u2022 Add appropriate message types and filters to the CDM;
u2022 Generate outbound partner profiles;
u2022 Distribute the CDM to the receiving systems; and
u2022 Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC u2013 Creating IDoc Type from Change Pointers
RSEOUT00 u2013 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Regards,
Shiva Kumar

Doubt in bdc and ale reg

Similar Messages

Maybe you are looking for