Regarding ENTER in BDC's

hi guru's,
i have done a bdc rec prog.
here is the code:
perform open_group.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MATNR'.
*perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.*
perform bdc_field       using 'RMMG1-MATNR'
                              wa_final-matnr.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(02)'.
perform bdc_field       using 'BDC_OKCODE'
                              'P+'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(02)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                             'MSICHTAUSW-DYTXT(17)'.
*perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.*
perform bdc_field       using 'MSICHTAUSW-KZSEL(04)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(14)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '0080'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-WERKS'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-WERKS'
                               plant.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BABA'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MATNR'.
perform bdc_transaction using 'MM03'.
{color}
Now my problem is, after pressing enter only iam able to select the views.
How to avoid this pressing of ENTER in the above program
*perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.*
so i need a key to replace this   " '=ENTR'. " , which directly processes without me pressing enter key in my output.
regards,
chaitu

hi chaitanya,
use '/00' instead of '=enter'.
check this coading
*& Report ZMM_IMP
report zmm_imp
 no standard page heading line-size 255.
*include bdcrecx1.
include zfin1_include.
selection-screen begin of block blk3 with frame title text-019.
parameters : pa_fname type localfile.
selection-screen end of block blk3.
data : lv_fname type string.
data: begin of record occurs 2,
 matnr_001(018), " MATERIAL NUMBER
 maktx_019(040), " MATERIAL DESCRIPTION
 meins_020(003), " BUM
 matkl_021(009), " MATERIAL NUMBER
 check_820(001),
 aennr_821(003),
 revlv_822(003),
 extwg_850(018), " added for prod. server
 spart_023(002),
 kosch_851(018), " added for prod serv
 normt_900(018), " added 600
 wrkst_901(048), " added 600
 bstme_023(003),
 ekgrp_025(003), " PURCHASING GROUP
 ekwsl_027(004), " PURCHASING VALUE KEY
 usequ_028(001), " QUOTA ARRAY USAGE
 kordb_029(001), " SOURCE LIST
 umren_030(006),
 umrez_031(006),
 stawn_036(017), " IMPORT CODE NUMBER
 steuc_037(016), " CONTROL CODE
 j_1ichid_038(012),
 j_1isubind_039(001),
 j_1icapind_040(001),
 j_1igrxref_041(001),
 j_1imoom_042(018),
 j_1iwaers_043(005),
 j_1ivalass_044(018),
 maabc_049(001), " ABC INDICATOR
 minbe_051(017), " REORDER POINT
 dispo_052(003), " MRP CONTROLLER
 disls_053(002), " LOT SIZE
 bstmi_054(017), " MIN LOT SIZE
 mabst_055(017), " MAX STOCK LVL
 sobsl_068(002), " SPL PROCUREMENT
 plifz_071(003), " PLD DEL TIME
 webaz_072(003), " GR PROCESS TIME
 eisbe_074(017), " SAFETY STOCK
 rwpro_075(003), " COV PROFILE
 strgr_076(002),
 miskz_078(001), " MIXED MRP MRP-3 VIEW START
 mtvfp_079(002), " AVAILABILITY CHK
 sbdkz_081(001), " COLL MRP-4 VIEW
 lgpbe_089(010), " STORAGE BIN
 xmcng_092(001), " NEG STOCKS
 loggr_093(004), "LOG HANDLING GROUP
 qmpur_097(001), " QM IN PROC
 ssqss_098(008), " QM CTRL KEY
 art_01_800(008), " INSP TYPE
 art_02_801(008),
 art_03_802(008),
 art_04_803(008),
 art_05_804(008),
 aktiv_01_805(001), " ACTIVATION
 aktiv_02_806(001),
 aktiv_03_807(001),
 aktiv_04_808(001),
 aktiv_05_809(001),
 art_01_810(008),
 art_02_811(008),
 art_03_812(008),
 aktiv_01_813(001),
 aktiv_02_814(001),
 aktiv_03_815(001),
 bklas_123(004), " VALUATION CLASS
 vprsv_124(001), " PRICE CONTROL
 peinh_125(006), " PRICE UNIT
 verpr_126(015), " MVG AVG PRICE
 stprs_127(011), "MBEW -- STD PRICE
 losgr_130(017), " COST LOT SIZE
 end of record.
End generated data section ***
at selection-screen on value-request for pa_fname.
call function 'F4_FILENAME'
 exporting
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 field_name = 'PA_FNAME'
 importing
 file_name = pa_fname.
start-of-selection.
lv_fname = pa_fname.
perform open_group.
call function 'GUI_UPLOAD'
exporting
 filename = lv_fname
 filetype = 'ASC'
has_field_separator = 'X'
tables
 data_tab = record
if sy-subrc <> 0.
endif.
loop at record.
if sy-subrc <> 0. exit. endif.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
 'RMMG1-MATNR'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'RMMG1-MATNR'
 record-matnr_001.
perform bdc_field using 'RMMG1-MBRSH'
'M'.
perform bdc_field using 'RMMG1-MTART'
'I'.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(17)'.
perform bdc_field using 'BDC_OKCODE'
 'P+'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(02)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(04)'
'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(05)'
'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(06)'
'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(08)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(09)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(10)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(11)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(12)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(13)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(14)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(15)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(17)'
 'X'.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(01)'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(04)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(05)'
 'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(07)'
 'X'.
perform bdc_dynpro using 'SAPLMGMM' '0080'.
perform bdc_field using 'BDC_CURSOR'
 'RMMG1-LGORT'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTR'.
perform bdc_field using 'RMMG1-WERKS'
'PMT1'.
perform bdc_field using 'RMMG1-LGORT'
'RMST'.
perform bdc_field using 'RMMG1-VKORG'
'PMSO'.
perform bdc_field using 'RMMG1-VTWEG'
'DC'.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
 '=RLVP'.
perform bdc_field using 'MAKT-MAKTX'
 record-maktx_019.
perform bdc_field using 'BDC_CURSOR'
 'MARA-MATKL'.
perform bdc_field using 'MARA-MEINS'
 record-meins_020.
perform bdc_field using 'MARA-MATKL'
 record-matkl_021.
if record-check_820 = 'X'.
perform bdc_dynpro using 'SAPLCCRL' '0600'.
perform bdc_field using 'BDC_CURSOR'
 'RC29A-REVLV'.
perform bdc_field using 'BDC_OKCODE'
 '=WEIT'.
perform bdc_field using 'RC29A-AENNR'
 record-aennr_821.
perform bdc_field using 'RC29A-REVLV'
 record-revlv_822.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
endif.
perform bdc_field using 'BDC_OKCODE'
 '=SP02'.
perform bdc_field using 'MARA-EXTWG'
record-extwg_850.
perform bdc_field using 'MARA-SPART'
 record-spart_023.
perform bdc_field using 'MARA-kosch'
record-kosch_851.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'BDC_CURSOR'
 'MARA-NORMT'.
perform bdc_field using 'MARa-NORMT'
 record-normt_900.
perform bdc_field using 'MARa-WRKST'
 record-wrkst_901.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'BDC_CURSOR'
 'MVKE-DWERK'.
perform bdc_field using 'MVKE-DWERK'
'PMT1'.
perform bdc_field using 'MG03STEUER-TAXKM(01)'
'1'.
perform bdc_dynpro using 'SAPLMGMM' '4200'.
perform bdc_field using 'BDC_OKCODE'
 '=MAIN'.
perform bdc_field using 'BDC_CURSOR'
 'MAKT-MAKTX'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP05'.
perform bdc_field using 'BDC_CURSOR'
 'MAKT-MAKTX'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP06'.
perform bdc_field using 'BDC_CURSOR'
 'MVKE-KTGRM'.
perform bdc_field using 'MVKE-VERSG'
'1'.
perform bdc_field using 'MVKE-KTGRM'
'01'.
perform bdc_field using 'MARA-MTPOS_MARA'
'NORM'.
perform bdc_field using 'MVKE-MTPOS'
'NORM'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP09'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-LADGR'.
perform bdc_field using 'MARC-MTVFP'
'01'.
perform bdc_field using 'MARA-TRAGR'
'0001'.
perform bdc_field using 'MARC-LADGR'
'0001'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'MARa-bstme'
 record-bstme_023.
perform bdc_field using 'MARC-EKGRP'
 record-ekgrp_025.
perform bdc_field using 'BDC_CURSOR'
 'MARA-EKWSL'.
perform bdc_field using 'MARA-EKWSL'
 record-ekwsl_027.
perform bdc_field using 'MARC-USEQU'
 record-usequ_028.
perform bdc_field using 'MARC-KORDB'
 record-kordb_029.
if record-bstme_023 <> ' '.
perform bdc_dynpro using 'SAPLMGMM' '0510'.
perform bdc_field using 'BDC_CURSOR'
 'RMMZU-UMREZ'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTR'.
perform bdc_field using 'RMMZU-UMREN'
 record-umren_030.
perform bdc_field using 'RMMZU-UMREZ'
 record-umrez_031.
endif.
*perform bdc_dynpro using 'SAPLMGMM' '4000'.
*perform bdc_field using 'BDC_OKCODE'
 '=SP10'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 'SP12'.
perform bdc_field using 'MARC-STAWN'
 record-stawn_036.
perform bdc_field using 'MARC-STEUC'
 record-steuc_037.
perform bdc_field using 'J_1IMTCHID-J_1ICHID'
 record-j_1ichid_038.
perform bdc_field using 'J_1IMTCHID-J_1ISUBIND'
 record-j_1isubind_039.
perform bdc_field using 'J_1IMTCHID-J_1ICAPIND'
 record-j_1icapind_040.
perform bdc_field using 'J_1IMTCHID-J_1IGRXREF'
 record-j_1igrxref_041.
perform bdc_field using 'J_1IMODDET-J_1IMOOM'
 record-j_1imoom_042.
perform bdc_field using 'J_1IASSVAL-J_1IWAERS'
 record-j_1iwaers_043.
perform bdc_field using 'J_1IASSVAL-J_1IVALASS'
 record-j_1ivalass_044.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP13'.
perform bdc_field using 'MARC-DISGR'
'0000'.
perform bdc_field using 'MARC-MAABC'
 record-maabc_049.
perform bdc_field using 'BDC_CURSOR'
 'MARC-DISPO'.
perform bdc_field using 'MARC-DISMM'
'PD'.
perform bdc_field using 'MARC-MINBE'
 record-minbe_051.
perform bdc_field using 'MARC-DISPO'
 record-dispo_052.
perform bdc_field using 'MARC-DISLS'
 record-disls_053.
perform bdc_field using 'MARC-BSTMI'
 record-bstmi_054.
perform bdc_field using 'MARC-MABST'
 record-mabst_055.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP14'.
perform bdc_field using 'MARC-SOBSL'
 record-sobsl_068.
perform bdc_field using 'MARC-LGPRO'
'RMST'.
perform bdc_field using 'MARC-LGFSB'
'RMST'.
perform bdc_field using 'MARC-PLIFZ'
 record-plifz_071.
perform bdc_field using 'MARC-WEBAZ'
 record-webaz_072.
perform bdc_field using 'MARC-FHORI'
'000'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-RWPRO'.
perform bdc_field using 'MARC-EISBE'
 record-eisbe_074.
perform bdc_field using 'MARC-RWPRO'
 record-rwpro_075.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP15'.
perform bdc_field using 'MARC-strgr'
record-strgr_076.
perform bdc_field using 'MARC-MISKZ'
 record-miskz_078.
perform bdc_field using 'BDC_CURSOR'
 'MARC-MTVFP'.
perform bdc_field using 'MARC-MTVFP'
 record-mtvfp_079.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-SBDKZ'.
perform bdc_field using 'MARC-SBDKZ'
 record-sbdkz_081.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP19'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP20'.
perform bdc_field using 'BDC_CURSOR'
 'MARD-LGPBE'.
perform bdc_field using 'MARD-LGPBE'
 record-lgpbe_089.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 'SP23'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-LOGGR'.
perform bdc_field using 'MARC-XMCNG'
 record-xmcng_092.
perform bdc_field using 'MARC-LOGGR'
 record-loggr_093.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=PB01'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-SSQSS'.
perform bdc_field using 'MARA-QMPUR'
 record-qmpur_097.
perform bdc_field using 'MARC-SSQSS'
 record-ssqss_098.
perform bdc_dynpro using 'SAPLQPLS' '0100'.
perform bdc_field using 'BDC_CURSOR'
 'RMQAM-ARGUMENT'.
perform bdc_field using 'BDC_OKCODE'
 '=NEU'.
perform bdc_dynpro using 'SAPLQPLS' '0100'.
perform bdc_field using 'BDC_CURSOR'
 'RMQAM-AKTIV(05)'.
perform bdc_field using 'BDC_OKCODE'
 'P+'.
perform bdc_field using 'RMQAM-ART(01)'
 record-art_01_800.
perform bdc_field using 'RMQAM-ART(02)'
 record-art_02_801.
perform bdc_field using 'RMQAM-ART(03)'
 record-art_03_802.
perform bdc_field using 'RMQAM-ART(04)'
 record-art_04_803.
perform bdc_field using 'RMQAM-ART(05)'
 record-art_05_804.
perform bdc_field using 'RMQAM-AKTIV(01)'
 record-aktiv_01_805.
perform bdc_field using 'RMQAM-AKTIV(02)'
 record-aktiv_02_806.
perform bdc_field using 'RMQAM-AKTIV(03)'
 record-aktiv_03_807.
perform bdc_field using 'RMQAM-AKTIV(04)'
 record-aktiv_04_808.
perform bdc_field using 'RMQAM-AKTIV(05)'
 record-aktiv_05_809.
perform bdc_dynpro using 'SAPLQPLS' '0100'.
perform bdc_field using 'BDC_CURSOR'
 'RMQAM-ARGUMENT'.
perform bdc_field using 'BDC_OKCODE'
 '=NEU'.
perform bdc_dynpro using 'SAPLQPLS' '0100'.
perform bdc_field using 'BDC_CURSOR'
 'RMQAM-AKTIV(03)'.
perform bdc_field using 'BDC_OKCODE'
 '=WEIT'.
perform bdc_field using 'RMQAM-ART(01)'
 record-art_01_810.
perform bdc_field using 'RMQAM-ART(02)'
 record-art_02_811.
perform bdc_field using 'RMQAM-ART(03)'
 record-art_03_812.
perform bdc_field using 'RMQAM-AKTIV(01)'
 record-aktiv_01_813.
perform bdc_field using 'RMQAM-AKTIV(02)'
 record-aktiv_02_814.
perform bdc_field using 'RMQAM-AKTIV(03)'
 record-aktiv_03_815.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP24'.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '=SP26'.
perform bdc_field using 'BDC_CURSOR'
 'MBEW-VERPR'.
perform bdc_field using 'MBEW-BKLAS'
 record-bklas_123.
perform bdc_field using 'MBEW-VPRSV'
 record-vprsv_124.
perform bdc_field using 'MBEW-PEINH'
 record-peinh_125.
perform bdc_field using 'MBEW-VERPR'
 record-verpr_126.
perform bdc_field using 'MBEW-STPRS'
 record-stprs_127.
perform bdc_dynpro using 'SAPLMGMM' '4000'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'BDC_CURSOR'
 'MARC-PRCTR'.
perform bdc_field using 'MARC-LOSGR'
 record-losgr_130.
perform bdc_dynpro using 'SAPLSPO1' '0300'.
perform bdc_field using 'BDC_OKCODE'
 '=YES'.
perform bdc_transaction using 'MM01'.
endloop.
perform close_group.

Similar Messages

Regarding entering data in Table J_2IRG1BAL

Hi SAP Gurus,
While I tried to enter data into table J_2IRG1BAL through Menu->Utilities->Table->contents->Create Entries
The following Error is displayed .
error : Create data processing function module
Message no. SV023
Diagnosis
You have called the function for editing view contents. The function modules needed for the maintenance functionality of this view are not available in the system.
Procedure
The data processing function module must be re-generated.
Contact the system administration.
Plz Help!
Reagrds Pavan.

Hi Pavan,
Have a look at this OSS Notes
I thnk u need to regenrate the function module using SAP Note .Chk the following whether it will be useful or not.
Note 316683 - V_T778Q: Create data processing function module
Note 849858 - OT: Create data processing function module error -T558E.
Try a search for OSS Notes in Service market place with messages which u have got.
Regards,
Lakshman.

Regarding recording for BDC

Hi,
    If we add a screen exit, will it come in recording ?
For eg:In XD01 tcode if i add a screen through
screen exit ,will it come in recording
Thanks IN Advance

First you must add a screen than when you do recording it will automatically come.
See these badi available for XD01 for screen changes:
Business Add-in
CUSTOMER_ADDRSCR_CHG                    Change Address Screen in the Master Data Maintenance
CUSTOMER_ADD_DATA                       Additional Data at Customers
CUSTOMER_ADD_DATA_BI                    Additional Data at Customers (Batch Input and ALE)
CUSTOMER_ADD_DATA_CS                    Additional Data at Customers (Subscreen Container 4000)
Amit.

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

Changing date in BDC

Hi ALL
I wanna to change the date in the flat file when I am entering into BDC, please give me the code for this one.
Regards
Praveen

Hi,
Try this...
Local variables to set date
DATA:lv_dd(2),
         lv_mm(2),
         lv_yyyy(4),lv_date1(10).
*pass the date field from file into a variable
SPLIT x_data_tab-str1 AT ',' INTO lv_date1.
Set Date into DDMMYYYY format or according to ur *requirement
    lv_dd = lv_date1+0(2).
    lv_mm = lv_date1+3(2).
    lv_yyyy = lv_date1+6(4).
    CONCATENATE lv_dd lv_mm lv_yyyy INTO x_final-bldat.
or if this does not work then use write to field statement
Regards,
Sridhar Reddy k
Message was edited by: sridhar reddy kondam

Regarding data transfers

hi,
can anybody tell me when we use SESSION METHOD,CALL TRANSACTION and LSMW.
urgent plz,
some say that for small amout of data we use CALL TRANSATION and for large volume of data we use SESSION METHOD .but i don't understand how many records is small and how many records is large. and for what type we use LSMW.
full points will be rewarded.
regards,
kiran

BDC
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
ABAP Tips by : Nagaraj Muniyappa
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is
not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program.
Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in
Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.
Differences between bdc session method and call transaction method.
The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel
The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.
Explain in detail with example what is batch input session?
Batch Input Session:
- It is a sequence of transactions, which is generated when user run a particular program.
- It contains the accounting documents that are to be created. The SAP system stores these transactions until you decide to process them online.
- It does not update transaction figures until the session has been processed. Using this technique, you can transfer large amounts of data to the SAP system in a short time.
Three processing modes of executing Batch Input Session :-
(1) Run Visibly : You can correct faulty transactions online & work step-by-step through the transactions not yet executed.
(2) Display Errors only : You can correct faulty transactions online. Transactions not yet executed, but without error, run in the background.
(3) Run in Background : Recommended by SAP.
also refer
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
LSMW
SAP Data Migration with 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.
For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.
If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)
Converts the data from the source format into the target format
Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working online.
regards
srinivas
*reward for useful answers*

BDC code for MB01 Application(Multiple Line Items)

Hi,
Can anybody please send me the BDC CODE for MB01 Application(for Multiple Line items).
Very urgent.
Thanks And Regards,
Ajay

Instead of BDC you can use following BAPI.
see the following ex:
BAPI TO Upload Inventory Data
GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
                     02 - MB31 - Goods Receipts for Prod Order
                     03 - MB1A - Goods Issue
                     04 - MB1B - Transfer Posting
                     05 - MB1C - Enter Other Goods Receipt
                     06 - MB11
Domain: KZBEW - Movement Indicator
     Goods movement w/o reference
B - Goods movement for purchase order
F - Goods movement for production order
L - Goods movement for delivery note
K - Goods movement for kanban requirement (WM - internal only)
O - Subsequent adjustment of "material-provided" consumption
W - Subsequent adjustment of proportion/product unit material
LOOP AT I_TAB.
      count = sy-tabix.
      SELECT SINGLE * FROM ZMM_GI_WIP
                                WHERE GI_NO = I_TAB-DOCNO AND
                                GI_DATE = I_TAB-DOCDT.
      IF SY-SUBRC = 0.
        I_TAB-FLAG = 'C'.
        modify i_tab index count.
        CONCATENATE 'ERROR GI : ' I_TAB-DOCNO
        ' WAS ALREADY UPLOADED' INTO I_MSG1.
        APPEND I_MSG1.
        CLEAR I_TAB-FLAG.
        CONTINUE.
      ELSE.
        CONCATENATE I_TAB-DOCDT+4(2)
                    I_TAB-DOCDT+6(2)
                    I_TAB-DOCDT+2(2)
                    I_TAB-DOCDT+0(2)
                    INTO G_DATE.
        gmhead-pstng_date = G_DATE.
        gmhead-doc_date = sy-datum.
        gmhead-pr_uname = sy-uname.
"01 - MB01 - Goods Receipts for Purchase Order
        gmcode-gm_code = '03'.
        refresh itab.
        clear itab.
        SORT I_MAIN BY SOL_DOCNO.
        LOOP AT I_MAIN WHERE DOCNO = I_TAB-DOCNO.
          IF I_MAIN-GI_TXN_TYPE = 'MGI'.
            itab-move_type = '291'.
          ENDIF.
          itab-mvt_ind    = ' '.
          itab-plant      = I_MAIN-WERKS.
          itab-material   = I_MAIN-MATNR.
          itab-entry_qnt = I_MAIN-ERFMG.
          itab-stge_loc   = I_MAIN-LGOBE.
          itab-ENTRY_UOM = I_MAIN-ERFME.
          IF I_MAIN-WERKS = 'MR'.
            itab-TR_PART_BA = '11'.
          ELSEIF I_MAIN-WERKS = 'MR'.
            itab-TR_PART_BA = '12'.
          ENDIF.
          append itab.
        ENDLOOP.
        if not itab[] is initial.
          call function 'BAPI_GOODSMVT_CREATE'
           exporting
               goodsmvt_header             = gmhead
               goodsmvt_code               = gmcode
             *   TESTRUN                     = ' '
          IMPORTING
              goodsmvt_headret            = mthead
         *   MATERIALDOCUMENT            =
MATDOCUMENTYEAR             =
           tables
             goodsmvt_item               = itab
GOODSMVT_SERIALNUMBER       =
            return                      = errmsg.
          clear errflag.
          loop at errmsg.
            if errmsg-type eq 'E'.
              write:/'Error in function', errmsg-message.
              errflag = 'X'.
            else.
              write:/ errmsg-message.
            endif.
            move errmsg-message to i_msg1.
            append i_msg1.
          endloop.
          if errflag is initial.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            WAIT          =
          IMPORTING
            RETURN        =
           commit work and wait.
            if sy-subrc ne 0.
              write:/ 'Error in updating'.
              exit.
             endif.
        endif.
      ENDIF.
       wait up to 20 seconds.
    ENDLOOP.

In Bdc I have huge volume of data to upload for the given transaction

Hi gurus,
In Bdc I have huge volume of data to upload for the given transaction, here am using session method, it takes lots of exection time to complete the whole transaction, Is there any other method to process the huge volume with minimum time,
reward awaiting
with regards
Thambe

Selection of BDC Method depends on the type of the requirement you have. But you can decide which one will suite requirement basing the difference between the two methods. The following are the differences between Session & Call Transaction.
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is
not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program.
Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in
Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.
synchronous & Asynchronous updating:
http://www.icesoft.com/developer_guides/icefaces/htmlguide/devguide/keyConcepts4.html
synchronous & Asynchronous processings
Asynchronous refers to processes that do not depend on each other's outcome, and can therefore occur on different threads simultaneously. The opposite is synchronous. Synchronous processes wait for one to complete before the next begins. For those Group Policy settings for which both types of processes are available as options, you choose between the faster asynchronous or the safer, more predictable synchronous processing.
By default, the processing of Group Policy is synchronous. Computer policy is completed before the CTRLALTDEL dialog box is presented, and user policy is completed before the shell is active and available for the user to interact with it.
Note
You can change this default behavior by using a policy setting for each so that processing is asynchronous. This is not recommended unless there are compelling performance reasons. To provide the most reliable operation, leave the processing as synchronous.

LSMW And BDC's

Can you send me the Documents and Links regarding LSMW and BDC's my id is [email protected]

hi,
check below sites
LSMW
http://www.sap-img.com/bdc.htm.
LSMW:
steps for LSMW: detail documnets: http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap-img.com/sap-data-migration.htm
https://websmp207.sap-ag.de/lsmw
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
BDC
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d62292b3-0301-0010-df98-aaac31cd4a41
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d4c5e890-0201-0010-bd9a-c3fd8683fc97
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
excel sheet uploading:
http://www.sap-img.com/abap/upload-direct-excel.htm
http://www.sap-img.com/abap/excel_upload_alternative-kcd-excel-ole-to-int-convert.htm
http://www.sapdevelopment.co.uk/file/file_upexcel.htm
http://www.sapdevelopment.co.uk/file/file_upexcel.htm
http://www.sapdevelopment.co.uk/ms/mshome.htm
if useful don't forgot to give points.

Is it possible to enter multiple records in Infotype.

Hi,
    I am having doubt regarding entering multiple values in infotypes for HR-ABAP.
Is there any way to enter multiple records in a infotype, As compared to ABAP, By using table maintence generator we can enter mutiple records in the form of table. In the same way, do we have any way to do multiple entry in HR-ABAP.
Please Explain.......
Thanks & Regards,
Kumar Madduru

Hi pavan,
    I am also having the same doubt regarding multiple entries in an infotype,
Actually my requirement was to make multiple entries into one infotype,
let us take an example as to feed employee project detailes..
i.e.. -
      ! Start date     ! End date      ! Client          ! Role in Project !
      ! 10-02-2004    ! 27-11-2004    ! Nestle        ! Team member   !
      ! 28-11-2004    ! 05-06-2005    ! HP             ! Team member   !
      ! 06-05-2005    ! 18-03-2006    ! Relience     ! Team member   !
      ! 19-03-2006    ! 04-11-2007    ! lenovo        ! Team Lead        !
      ! 05-11-2007    ! 31-12-9999    ! Bajaj          ! Team Lead        !    (current project)
Now, My intension is to enter these data without always clicking create icon,
do we have any possiblity to do this. As we can insert multiple entries using T.code SM30.
i.e to insert or delete multiple data into transp table.
Please reply as soon as possible.
Thanks in advance.
Surender.

Steps to upload vendor invoice(tcode fb60) in bdc

hi, iam srinivas can any one plz send me the steps to upload veneor invoice tcode is (fb60).i dont want the code but i want the steps to create .
thanks and regards.
Srinivas.

refer this site.
FI_AP_FBR2_Post_With_Reference (FBR2)
Business Process Description Overview
Use this procedure to copy a previously posted non-PO invoice document that uses many of the same values.
This may help reduce data entry time if used correctly. For example, the library invoice vouchers that have the same vendor but many invoices on them might be a good example of when to use this transaction code.
Trigger
Perform this procedure when there is an invoice that needs to have data entered where most of the fields are the same as a prior invoice document already entered in the system.
Prerequisites
·         Security Role: AP_DIR_INV_ENTRY
·         An FB60 invoice has already been data entered.
Menu Path
None
Transaction Code
FBR2
Tips and Tricks
·         If you would like to save this transaction under your "Favorites" folder, right-click on the "Favorites" folder, select "Insert Transaction" and type in this t-code when the box appears.
·         You may use the transaction code: search_sap_menu to search for a transaction codes menu path.
Procedure
Enter Vendor Invoice: Company Code PUR
Typically the FBR2 - Post With Reference transaction is accessed from the Financial transaction code that you just used. For Accounts Payable, typically we would use the FB60 transaction code to enter invoices that are not PO-related. After you have entered an invoice, you can now post a second invoice. Feel free to post an invoice in DEV to the Vendor ID number: 31. Choose today's date as the Invoice Date. Enter a Vendor Invoice in the Reference Field. Enter $1000 as the Amount. Enter a Text that you want to show on the remittance advice to the vendor. Choose your own GL Account and Cost Center. Enter 21010000 as the Fund. Make sure to also enter $1000 in the Amount in doc. curr. field.
    Please be aware that the FB60 screenshot above is using the ZPurdue Variant so unless you are also using that same variant the order of your columns may differ.
    Refer to FB60 documentation for more information regarding entering a non-PO related invoice.
    After an invoice has been entered, you may proceed to step 1. If you prefer not to enter an FB60 invoice then after you open FB60, immediately do step 1, but enter "1900001354" in the Document Number field.
1.       Select Goto Post with reference           Shift+F9 to go to the FBR2 transaction.
Post Document: Header Data
The document number you just entered in FB60 should now display. If you did not first enter your own FB60 invoice, please enter 1900001354 in the Document Number field. Make sure Company Code is PUR and Fiscal Year is 2007.
    If you did enter your own FB60 invoice to reference to, please be aware that the data entry fields will have different content in the screen shots than what you are seeing on your screen.
2.       Click or the "Enter" key to proceed.
Post Document: Header Data
Because we want to avoid paying the same invoice twice, we must change the reference field to another Vendor Invoice text.
3.       As required, complete/review the following fields:
Field Name
R/O/C
Description
Reference
R
Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.
Example:          VENDORINVOICE#2
    Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.
Post Document: Header Data
4.       Click or the "Enter" key to proceed.
Post Document Display Overview
You are now viewing the document overview screen.
5.       Double-click to open that line item.
Post Document Correct Vendor item
When you open the Vendor line item, you may change the Text field here to change what appears on the remittance advice.
6.       As required, complete/review the following fields:
Field Name
R/O/C
Description
Text
O
Description field for an entry.
Example:          prints on remittance advice - for second invoice
Post Document Correct Vendor item
7.       Click to return to the document overview screen.
Post Document Display Overview
The document overview screen.
8.       Click to post this second invoice which has the same fields as the original except a different vendor invoice number and a different remittance advice text.
Information
Pending upon your user settings, you may not get this pop up box, but just a message in the bottom left hand corner of the screen.
9.       Click to close the box.
Enter Vendor Invoice: Company Code PUR
Because you used the menu (Goto Post with reference) from FB60 to access the FBR2 transaction code, you are then returned to the FB60 transaction after you have posted the invoice.
10.     Another way to access FBR2 is to just type the t-code in the field at the top of the screen. As required, complete/review the following fields:
Field Name
R/O/C
Description
Transaction Code
R
A unique four-character (in most cases) identification assigned to each SAP transaction based on its purpose.
Example:          /nfbr2
11.     Click or the "Enter" key to proceed.
Post Document: Header Data
The FBR2 transaction code opens with the last document number entered as the default.
12.     Click or the "Enter" key to proceed.
Post Document: Header Data
This time we will change the vendor number
13.     Change the Reference field. As required, complete/review the following fields:
Field Name
R/O/C
Description
Reference
R
Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP. Any SAP-posted document number can be used as a "reference" when entering a new document.
Example:          VENDORINVOICE
    Your reference number should be different than the one above. Otherwise, the system will think you are entering a duplicate invoice. Please change your text slightly.
Post Document: Header Data
14.     As required, complete/review the following fields:
Field Name
R/O/C
Description
Account
R
Unique identification number. SAP uses several kinds of accounts. SAP's general ledger accounts are similar to standard in most accounting systems. SAP also uses sub-ledger accounts for customers (accounts receivable), vendors (accounts payable), and assets (asset accounts). These sub-ledger accounts roll-up to a general ledger account.
Example:          5000129
    Vendor 5000129 in DEV has withholding tax applied to it in the vendor master.
Post Document: Header Data
15.     Click or the "Enter" key to proceed.
Post Document Add Vendor item
If the vendor invoice date was a date in the past, the due date for pay immediately will be in the past. You may get the above informational message to alert you of the date. If you do, just hit the "Enter" key to acknowledge it.
Enter Withholding Tax Information
Because this vendor has withholding tax information in its vendor master, you will receive this popup up box.
16.     Click to accept it.
    Refer to the Tax Department for more information regarding withholding tax.
Post Document Display Overview
You should now see the document overview screen. If you do not, then click on .
17.     Double-click OR click to open it.
Post Document Correct Vendor item
18.     As required, complete/review the following fields:
Field Name
R/O/C
Description
Text
O
Description field for an entry.
Example:          change remittance advice text
Post Document Correct Vendor item
19.     Click to view that Vendor's Withholding tax information again.
Enter Withholding Tax Information
    If for some reason, for this invoice the vendor should not have any withholdings, you would enter a 0.00 in both the W/Tax Base and W/Tax Amt fields.
    When using the FBR2 to change withholding tax amounts, you need to be very careful if using this new invoice as the "reference" invoice for the next one. For example, if you put 0.00 in both W/Tax Base and W/Tax Amt fields then if this is the reference invoice, those 0.00 amounts will automatically be applied to the next; however, you won't see the 0.00 displayed. The 0.00 will be assumed.
20.     Click to close the box.
Post Document Correct Vendor item
21.     Click to post the invoice.
Post Document: Header Data
Your new document number will display in the bottom left hand corner. Pending upon your user settings, you may also get a pop up box to acknowledge.
You have posted another invoice, but this time you changed the vendor ID used, the vendor invoice, and the text on the remittance advice.
    Notice that the "Document Number" field now defaults to the newly posted invoice number.
    Because you entered FBR2 in the transaction code field to access this screen, when you post an invoice you are returned to the beginning of the FBR2 screen. Remember, when you accessed it from the menu line of FB60? If you access it that way, you are then returned to FB60 after the Post with Reference document is posted.
22.     Because you are returned to the start of FBR2 again, you may just click or the "Enter" key to proceed.
Post Document: Header Data
Now you are at the start of entering a new invoice again.
23.     Click to return to the main menu without finishing the process of entering another invoice.
24.     You have completed this transaction.
Result
You have posted two documents by using a reference document. This reduced the data entry required since it defaults the fields from the reference document.
Comments
Be very careful using this transaction if you change withholding tax amounts.
To see the results/calculations of discounts and withholdings, you must run F110, the Payment Program.
http://www.purdue.edu/onepurduehelp/content/fi_ap_fbr2_post_with_reference/wi/html/index.htm
Message was edited by:
        Karthikeyan Pandurangan
Message was edited by:
        Karthikeyan Pandurangan

BDC for Hiring a Employee through hiring action

Hi Experts,
We have done BDC for hiring action.
We do have PA & OM integrated. T77S0 PLOGI ORGA "X".
After hiring is compelted through BDC holder relationship is not appearing for position.
But when we are individually hiring an employee, position is assigned to a holder.
Please advice.
Regards,
IFF

Hi,
During BDC, the integration PA-OM is not processed... you have to run RHINTE00 report.
Kr,
m.

Hi experts bdc

hi all
i am using bdc call transaction to upload data from park vendor invoice transaction in fico.
there are 1000 and 2000 company codes data i have to update.
the transaction ask for first CC and then it takes remaining data.
my bdc work for both the company code, but
issue: when i switch over from one company code i.e. from 2000 to 1000 or from 1000 to 2000, the bdc zprogram throws me out.
fv60.
what could be the problem.
awaiting reply
rocky

Hi,
The problem might be, while switching over the company code, the FV60 transaction gets reset. so check whether you have enter proper BDC data by running the BDC transaction in mode 'A'.
<removed_by-moderator>
Thanks,
Muthu
Edited by: Julius Bussche on Jul 15, 2008 6:50 AM

Calling of MR11 by a report program

Hello All,
I have a requirement where in I have a selection screen on which I would enter an account number and based on that I need to clear the GRIR difference for all PO's based on certain conditions and post the difference into the account on the selection screen. Is there any Function module which can be used having a similar functionality as MR11 transaction, where in the interface of the function module I can send in the account number to be posted in ? If not what could be an alternative to call the transaction other than BDC. I need it to perform the functionality with out displaying the screens of MR11.
Before MR11 call I need to call FB65 and post a vendor credit memo if IR amount is greater then GR amount also.
Any inputs on this ?
Regards,
Sachin

Hello,
Used BDC as there is no other way that I could find out.
Regards,
Sachin
Edited by: Sachin Dargan on Mar 29, 2010 9:58 AM

VA01 DBC for One-time Ship to party

Hi All,
I am creating a BDC program for Sale Order (VA01), only for those customers which have one-time account ship to party. When I creates sale order manually for these types for customer, a Customer address from master data for ship party screen pop-up where user enters ship to party address . But while I am doing DBC recording for the same, than this address from master data for ship party pop-up screen not showing in BDC recording. Is there any way to do this
With Regards
Jitendra Singh

Hi,
BDC is not recommended at all when there is an existing BAPI, that is the case here I guess. Is there a reason why you use BDC? With a BAPI, you'll avoid this kind of issue (workarounds are usually to make sure of the issue by testing with the A display mode, else force the NO batch input option (NOBINPT)).
Sandra

Regarding ENTER in BDC's

Similar Messages

Maybe you are looking for