BDC Processing

I need some help in finding some documentation or getting some information on BDC processing. We have some consultants in France helping us with a project and the developer is using BDC code like
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> NODATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
The above code is in a include module that is called by the main programs. I would to understand how this process works and what are the advantages and disadvantages of this type of coding. I am checking here in the forums, tying to narrow my searches to find any documentation, but so far no luck. If someone could point me in the right direction, that would be very helpful.
thanks in advance for the help.
I am trying to find some documentation in this to

This type of coding could be used to fill in screens in SAP automatically.
If you don't know what to pass of values. Then start transaction SM35 and do a recording of the action you want to automate.
Add is some source to make it clear voor you. It is source used for HR.
refresh BDCDATA.
Global
perform bdc_dynpro      using 'SAPMP50A'         '1000'.
perform bdc_field       using 'BDC_OKCODE'       '=INS'.
perform bdc_field       using 'RP50G-PERNR'      sap_pernr.
perform bdc_field       using 'RP50G-TIMR6'      'X'.
perform bdc_field       using 'RP50G-CHOIC'      '0000'.
Infotype 0000
perform bdc_dynpro      using 'MP000000'         '2000'.
perform bdc_field       using 'BDC_OKCODE'       '=UPD'.
perform bdc_field       using 'P0000-MASSN'      rec_leaving-massn.
perform bdc_field       using 'P0000-MASSG'      rec_leaving-massg.
perform bdc_field       USING 'P0000-BEGDA'      rec_leaving-begda.
Infotype 0001
perform bdc_dynpro      using 'MP000100'         '2000'.
perform bdc_field       using 'BDC_OKCODE'       '=UPD'.
perform bdc_field       USING 'P0001-BEGDA'      rec_leaving-begda.
perform bdc_field       USING 'P0001-ENDDA'      rec_leaving-endda.
perform bdc_field       USING 'P0001-ABKRS'      '99'.
Infotype 0016
perform bdc_dynpro      using 'MP001600'          '2012'.
perform bdc_field       using 'BDC_OKCODE'        '/ENXT'.
Infotype 0008
perform bdc_dynpro      using 'MP000800'          '2000'.
perform bdc_field       using 'BDC_OKCODE'        '/ENXT'.
Infotype 0007
perform bdc_dynpro      using 'MP000700'          '2012'.
perform bdc_field       using 'BDC_OKCODE'        '/ENXT'.
Infotype 9304
perform bdc_dynpro      using 'MP930400'          '2000'.
perform bdc_field       using 'BDC_OKCODE'        '/ENXT'.
perform bdc_transaction using 'PA30'.

Similar Messages

BDC process

Dear Gurus,
I want to know about BDC Process and also i want to know the purpose,use & how to use BDC Process.
Thanks in advance.

hi
Batch Data Communication or BDC is a batch interfacing
technique that SAP developed. It is mainly used for
uploading data into the SAP R/3 system. BDC works by
simulating the user input from transactional screen via an
ABAP program.
The data input data file will come in the form of a flat
file which the user save as file type txt file or prn file
from the Microsoft Excel program. An Abaper will create a
program to read the text file and upload into the SAP system.
Normally, the tcode SHDB will be used to record the
transaction code the user used. After, the simulation, the
Abaper can generate a sample program and modify from there.
It makes the programming easier and faster.
chk this pdf file
http://www.sappoint.com/abap/bdcconcept.pdf
chk this for FAQs on BDC
http://www.sap-img.com/abap/question-about-bdc-program.htm
sample code for call transaction method
http://www.sapdevelopment.co.uk/bdc/bdc_ctcode.htm
chk this for BDC recording with screen shots
http://www.sapdevelopment.co.uk/bdc/bdc_recording.htm
Hi refer the following links,
http://www.sappoint.com/abap/bdcconcept.pdf
http://www.planetsap.com/bdc_main_page.htm
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sappoint.com/abap/files.pdf
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_gci1068429_tax293481,00.html
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/d62292b3-0301-0010-df98-aaac31cd4a41
regards
kunal

Issue with BDC processing of F-65 after upgrade to ECC 6.0

Dear ABAP gurus,
We have upgraded our SAP system from version 4.7 to ECC 6.0.
We are facing issue when processing BDC sessions for transaction code F-65.
The screen which appears for Assignment to a profitability segment creates issue when processing BDC for F-65.
The screen name is SAPLKEAK and the corresponding screen number is 0300.
This screen displays the characteristic and its corrsponding values. The characteristics and its values are pulled in from FICO Config at runtime when you execute F-65 and all relevant Tcodes of business transaction RFBU.
We checked for the characteristics maintained for Characteristic group via std. transaction code KEPA. It shows 4 characteristics listed of which 2 are optional and 2 are mandatory. The same settings are available in older version as well as in ECC 6.0. Also validated the assignment of characteristic group to the actual data i.e to the business transaction RFBU via Tcode KE4G.
When we do recording in SHDB in both the systems, the older version shows it correctly displaying 4 fields(2 optional and 2 mandatory) in the Assignment to a profitability segment screen whereas the new system displays some 12 additional fields. Also none of the fields appear mandatory.
The issue is we are still not able to identify whether this is a technical issue or functional issue.
Searched for relevant OSS notes but couldn't find any.
Anyone of you who have faced this issue, please respond immediately.
We have this issue to be resolved on high priority.
Help will be highly appreciated.
Regards,
Kavita

This issue was also posted with an OSS-message to SAP, and the solution was to run this program SD_PLANVALUE_UPDATE
Berit

Suppress Warning [W] message during BDC process [as batch SM36]

Hi expert,
i had problem where Warning message is force my BDC program to stop during SM36 batch job submit.
if program trigger in ad-hoc process [call program directly using tcode] , program works fine.
let me share briefly about My program, i intend to create VA41 transaction which have contract start date less than today's date. Warning message V5 001 will appear [not as pop-up window] which force my BDC to stop during SM36.
please kindly help.

Hi Rudy..
The problem is with Contract begin date should be greater than the begin date...you cannot create the Contract for past dates.
Even BDC will continue for Warning and Information messages and stops if encounters the error message.
Pass the contran begin date greater or Equal to current date .

BDC Processing Mode Problem

Hi ,
I have problem in BDC recording. i am doing CO02 BDC by Call Transaction when i am Using 'A' and 'E' mode its updating Work center.
and the BDC messagecol fill with following messages.
TCODE DYNAME    DYNUMB   MSGTYP   MSGID           MSGNR       Message
CO02 <SAPLCOKO   0115            |I                |C2                       136         Status of released order is reverted to "Created"
CO02 <SAPLCOKO   0115            |S               |CO                      521         Scheduling carried out (see log)
CO02 <SAPLCOKO   0115            |S               |CO                      521         RS_TESTFRAME_CALL Scheduling carried out (see log)
CO02 <SAPLCOKO   0115            |S                |C2                       002         Release carried out
CO02 <SAPLCOKO   0115            |S                |CO                      100         Order number RS_TESTFRAME_CALL saved
But when i am runing With 'N' Mode its not updating data and giving following messages:
TCODE    DYNAME   DYNUMB   MSGTYP   MSGID    MSGNR                           Message
CO02   <SAPLCOKO <0115             |I                 C2          |136              Status of released order is reverted to "Created"
CO02   <SAPLCOKO <0115             |S                CO         |520              RS_TESTFRAME_CALL scheduling carried out
CO02   <SAPLCOKO <0115             |S                00          |344              No batch input data for screen RS_TESTFRAME_CALL RE
how can i track N mode.

If you look colsly in the LOG of mode N, it clearly says that there is no batch input for screen RS_TESTFRAME_CALL.
When you run in MODE A or MODE E this message comes and you press Enter and system will Skip this step. But when you run with the MODE N, this kine status message "No Batch input ... " will lead to the failure of the BDC. It will not process further steps.
Regards,
Naimesh Patel

BDC processing for background and foreground execution

Hi,
I've come accross a situation where in a BDC for sales order creation, creates one sales order and at the same time creates another sales order with a blank sales order number(but the data of both the sales order is identical), meaning it creates 2 sales orders. This only occurs when the BDC is processed in mode 'N' but it works fine when the BDC runs in mode 'A' and 'E'. Any idea as to why this could be happening?
Any help will be appreciated.
Thanks,
ALAM.

Hi Alam,
No, sorry, I don't know why this is happening.
What update-mode are you using? Asynchronous or Synchronous?
Test both options, maybe it helps.
Why are you not using BAPI_SALESORDER_CREATEFROMDAT2?
Regards, Miranda

Bdc process in tree daigram

hai to all
can any one explain BDC and methods, in brief manner as per interveiw.(most helpful if it is in tree daigram).

Hi Shiv,
There is no such tree diagram for bdc. I am giving some info.just go thru it.
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.
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW.
BDC and LSMW are the two data migration techniques (from legacy to SAP) . BDC technique is usually done by ABAPers. It consists of three methods.
1) Call Dialog Method
2) Session Method
3) Call Transaction Method
In the case of Session Method , a BDC Session is created , which has the data and info to run it in batch mode. When the user runs this session, every transactions are run in batch mode and tables are updated.
WHile in call transaction, no session is created. Instead , a report prog is created , which takes input from the file and calls the transaction in Batch mode.
Call dialog method is similar to call transaction, except that updation is done by the calling program itself.This method is obsolete.
Advantages of Batch Input Method are
1)Can process large data volumes
2) data integrity is maintained
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/backgrou nd 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.
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
What is BDC programming?- Transferring of large/external/legacy data into SAP system using Batch Input programming. Batch input is a automatic procedure referred to as BDC(Batch Data Communications).The central component of the transfer is a queue file which receives the data vie a batch input programs and groups associated data into sessions.
What are the functional modules used in sequence in BDC?- These are the 3 functional modules which are used in a sequence to perform a data transfer successfully using BDC programming: BDC_OPEN_GROUP - Parameters like Name of the client, sessions and user name are specified in this functional modules. BDC_INSERT - It is used to insert the data for one transaction into a session. BDC_CLOSE_GROUP - This is used to close the batch input session.
What should be the approach for writing a BDC program?
ANS:-
STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED CONVERSION.
STEP 2: TRANSFERING THE FLAT FILE INTO SAP SYSTEM CALLED SAP DATA TRANSFER.
STEP 3: DEPENDING UPON THE BDC TYPE i ) call transaction(Write the program explicitly)
ii) create sessions (sessions are created and processed. if success data will transfer).
What is a batch input session?
ANS:-
BATCH INPUT SESSION is an intermediate step between internal table and database table.
Data along with the action is stored in session ie data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.
. What is the alternative to batch input session?
ANS:-
Call transaction.
A situation: An ABAP program creates a batch input session.
We need to submit the program and the batch session in background. How to do it?
ANS :-
go to SM36 and create background job by giving
job name, job class and job steps (JOB SCHEDULING)
. What are the problems in processing batch input sessions?
How is batch input process different from processing online?
ANS:-
PROBLEMS:-
i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually.
ii)if session processing fails data will not be transferred to SAP database table.
. What do you do when the system crashes in the middle of a BDC batch session?
ans:-
we will look into the error log file (SM35).
What do you do with errors in BDC batch sessions?
ANS:-
. Setting up a BDC program where you find information from?
ans:-
. What has to be done to the packed fields before submitting to a BDC session.
ans:-
fields converted into character type.
What is the structure of a BDC sessions.
ans:-
BDCDATA (standard structure).
What are the fields in a BDC_Tab Table.
ans:-
program,dynpro,dynbegin,fnam,fval.
We look into the list of incorrect session and process it again. To correct incorrect session we analyize the session to determine which screen and value produced the error.For small errors in data we correct them interactively otherwise
modify batch input program that has generated the session or many times even the datafile.
How do you set up background jobs in SAP? What are the steps? What are the event driven batch jobs?
ans:-
go to SM36 and create background job by giving job name,job class and job steps(JOB SCHEDULING)
Advantages & Disadvantages of different types of BDCs?
Ans Transaction Method:
1) It is faster than session method.
2) While executing, it starts from starting.
Session Method:
1) It is slower than transaction method.
2) While executing, it does not start from starting.
How to write a BDC - how do u go about it?
Ans Steps for writing BDC
1) /nSE38
2) Declare Tables, Data (for ITAB) and Data (for BDCITAB)
3) Call function Upload.
4) Write code for the First Screen, Radio Button, Filename, Change Button, Second Screen, Utilities (Create Entries), Third Screen and Save.
5) Call transaction SE11 using BDCITAB mode A.
6) Save, Check Errors, Activate and Execute.
What are the function module in BDC?
Ans There are three function module in BDC:
1) BDC_OPEN_GROUP
2) BDC_INSERT
3) BDC_CLOSE_GROUP
for interview base see theese links shiva
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
thanks
karthik
reward me points if usefull

Problems in BDC Processing.

What are the problems in processing batch input sessions?
How is batch input process different from processing on line?

Hi,
CHECK THESE THREADS...
Difference between Call Transaction & Batch Input
Re: difference between "call transaction&batch input"
Re: Difference between the Direct Input Method and Batch Input Method
Regards,
Omkar.

BDC-Process session in back ground

HI to all,
Is there any FM to call session in back ground
i am using RSBDCSUB apart form this if there is any FM please tell me.
regarda
raadha

Hi,
Use this sample code
DATA:    RUNTIME        TYPE I.             "Runtime
DATA:    GROUP          LIKE APQI-GROUPID,     " Mappenname
         BDCIMMED       LIKE RFIPI-BDCIMMED,   " nur BDC: sof. Abspielen
         BDCSTRTDT      LIKE TBTCJOB-SDLSTRTDT, "nur BDC: Startdatum
         BDCSTRTTM      LIKE TBTCJOB-SDLSTRTTM. "nur BDC: Startzeit
form mappe_abspielen_im_batch.
GET RUN TIME FIELD RUNTIME.
JOBNAME    = 'RFEBFD00-FIEB'.
JOBNAME+14 = RUNTIME.
eak-point.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            JOBNAME          = JOBNAME
            JOBGROUP         = 'FIEB'
       IMPORTING
            JOBCOUNT         = JOBCOUNT
       EXCEPTIONS
            CANT_CREATE_JOB = 01
            INVALID_JOB_DATA = 02
            JOBNAME_MISSING = 03.
IF SY-SUBRC NE 0.
    MESSAGE E015 RAISING SESSION_NOT_PROCESSABLE.
ENDIF.
SUBMIT RSBDCSUB AND RETURN
                  USER SY-UNAME
                  VIA JOB JOBNAME NUMBER JOBCOUNT
                with mappe    = group
                  WITH MAPPE    = BI-NAME
                  WITH VON      = SY-DATUM
                  WITH BIS      = SY-DATUM
                  WITH Z_VERARB = 'X'.
    BDCSTRTDT = SY-DATUM.
    BDCSTRTDT = SPACE.
    BDCSTRTTM = SPACE.
    BDCIMMED = 'X'.
bdcstrttm = runtime.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            JOBNAME              = JOBNAME
            JOBCOUNT             = JOBCOUNT
            STRTIMMED            = BDCIMMED
            SDLSTRTDT            = BDCSTRTDT
            SDLSTRTTM            = BDCSTRTTM
       EXCEPTIONS
            CANT_START_IMMEDIATE = 01
            JOBNAME_MISSING      = 02
            JOB_CLOSE_FAILED     = 03
            JOB_NOSTEPS          = 04
            JOB_NOTEX            = 05
            LOCK_FAILED          = 06.
IF SY-SUBRC NE 0.
    MESSAGE E015 RAISING SESSION_NOT_PROCESSABLE.
ENDIF.
CLEAR BDCIMMED.
BDCSTRTDT = SPACE.
BDCSTRTTM = SPACE.
Regards
Krishna

Problem with repititive screen processing in BDC

Hello,
I am trying to post a General Ledger document with multiple line items using transaction FB01. This involves the header screen, and a debit entry screen and a credit entry screen, for each line.
Using SHDB, I recorded the transaction for posting for one set of screens- one header, debit entry, credit entry.
In the program I have seperated the header and put the debit, credit processing logic in a loop, to accommodate the multiple line items via BDC processing.
After the call transaction, I see the resulting document in the system has only one set of documents and no more. Is there any sample code anybody has? Any pointers? that will enable me to put the debit and credit entries in a loop using BDC.
Thank You for your help.
Sumit.

Hey Saquib,
The program is at the link
http://sumit1.googlepages.com/zctbfi109_journal_entry_in
Thank you.
Sumit.

BDC Step by Step Process

Hi Experts,
I'm new to BDC.
If you have any material which shows step by step process of BDC
with screen shots please forwards to the following mail id...
[email protected]
Kindly help me!!!!
I would be very grateful for your help..
thanks & regards,
shilpa

BDC or Batch Input Program Tips and Tricks
Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
Learning BDC Programming
I want to learn how to upload data using BDC. If I have a excel data file how will upload it using BDC. I don't know the full process of doing it, if someone help me in this. I want it using BDC session process and processing that session. I was trying to upload material master other day. But could not follow the process of uploading using BDC though I know LSMW. Please explain me the BDC process in details with examples.
For a BDC upload you need to write a program which created BDC sessions.
Steps:
1. Work out the transaction you would use to create the data manually.
2. Use transaction SHDB to record the creation of one material master data.
Click the New recording button or the Menu - Recording - Create
3. Save the recording, and then go back a screen and go to the overview.
4. Select the recording and click on Edit - Create Program. Give the program a Z name, and select transfer from recording.
5. Edit the program. You will see that all the data you entered is hard-coded into the program. You need to make the following changes:
5.1 After the start-of-selection, Call ws_upload to upload the file (the excel file needs to be saved as TAB separated).
5.2 After the open-group, Loop on the uploaded data. For each line, perform validation checks on the data, then modify the perform bdc_field commands to use the file data.
5.3. After perform bdc_transaction, add the endloop.
Execute the program. It will have options to create a batch session or to process directly.
These are all my finds . Might be it will be useful to you.
Direct call of transactions, session handling:
/nxxxx This terminates the current transaction, and starts transaction xxxx
/n This terminates the transaction. This generally corresponds to pressing F15 to go back.
/nend This termiantes all separate sessions and logs off (corresponds to System - Logoff).
/nex This terminates all separate sessions and logs off immediately (without any warning!).
/oxxxx This opens a new session and starts transaction xxxx in This session.
/o This lists existing sessions and allows deletion or opening of a new session.
/i This terminates the current session (corresponds to System End
/i1, /i2,... This terminates the session with the number given.
.xyzw Fast path: 'xyzw' refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).
Batch
The following commands can be entered in correction mode ('Process in foreground' or 'Display errors only') when processing a batch input session:
/n This terminates the current batch input transaction and characterizes it as
/bdel This deletes the current batch input transaction.
/bend This terminates batch input processing and sets the session to Failed
/bda This switches from Display errors only to Process in foreground
/bde This switches from Process in foreground to Display errors only
ABAP/4
/h This switches into debugging mode.
/hs This switches into debugging mode and activates the debugging of system functions.
Buffer
WARNING: Resetting buffers can significantly change the performance of the entire system for a long time.
It should therefore only be used where there is a good reason tdso. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log.
/$SYNC This resets all buffers of the application server
/$CUA This resets the CUA buffer of the application server
/$TAB This resets the TABLE buffers of the application server
/$NAM This resets the nametab buffer of the application server
/$DYNP This resets the screen buffer of the application server
and also see these following links.
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
Regards.

How to processing of bdc in the middle

i have 30,000 records i have updated some 10,000 records now i want to stop complete bdc process how can i do that? please provide me the answer.

Hi Kudala,
If you are executing in Forground then
->right click on the SAP session ->STOP TRANSACTION
If Executing in background ->
Cancel/ Delete the Session in SM35.
Hope this helps.
Manish

Computer Aided test tool in processing BDC

Hi friends,
I have some doubts regarding the CATT mode in Processing BDC(SHDB transaction).
1) What's the use of this CATT mode in BDC Processing?
2) What is use of"NO CATT, CATT WITHOUT INDIVIDUAL SCREEN CONTROL, CATT WITH INDIVIDUAL SCREEN CONTROL" these three modes in Processing BDC?
3) What is the difference between the three modes?

Hi,
I have searched in the forum regarding this topic. I'am getting only answers like whats is CATT,and what is it used for. Iam unable to find the exact difference between "CATT WITHOUT INDIVIDUAL SCREEN CONTROL" and " CATT WITH INDIVIDUAL SCREEN CONTROL".

Is BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE(manual) creation?

Hi Experts,
Ours is IS-Oil.
If the user do not enters/inputs OIC_MOT (Mode Of Transport) at ITEM level on the External Details popup, SAP will get it from Customar Master-KNA1 and populates on it, because its a mandatory field (OIC_MOT), but, do not throws an Error message and interupts the sales order creation process.
We have a inbound IDOC posting function module for sales order (VA01), which posts the sales oreders by using BDC (CALL TRANSACTION 'VA01') in the system. In this function module, we are not populating the OIC_MOT field contained segment by hoping SAP will populate/default it while it hits CALL TRANSACTION 'VA01' of my BDC of my FM of IB IDOC. But, SAP is not defaulting/populating and throwing error message (saying 'OIC_MOT field is a mandatory input field' data is missing) and IDOC is failing, pls. let me know Wht its so? is the BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE (manual ) creation of sales order?
Thank you

Hi
Several transactions can ba a different behavior between online and bdc process, but if you simulate the trx by SM35 you should find out these gaps
I don't know OIL vertical, but the main transactions have a bapi can be used insted of BDC program (BAPI_SALESORDER_CREATEFROMDAT2, but perhaps there's a particular BAPI for OIL).
Max

BDC session error handling for IW41 transaction

Hi,
When the order confirmation is done by BDC session program, it is executed without any error. But if we do the same process manually, it is showing the error message as 'Posting period is Locked for 001 2012'. My question here is why this is not happening when it is executed through bdc session program.
Anyone can help us?
Thanks,
Guna

It is difficult to believe that you would get good results from background BDC process and error in foreground using same transaction and exactly the same data. Beyond that, why is month 1 of the current year locked? Are you absolutely sure that:
BDC works correctly? maybe does NOT and the errors have been missed or ignored?
Data is precisely the same for both BDC sessions?
Same transaction is called?
Sounds silly perhaps, but I have to believe that something is very different between the two sessions.

BDC Processing

Similar Messages

Maybe you are looking for