Difference between Batch input and Direct Input

Question

Hi please tell me the difference between Batch Input and Direct Input in BDC?

Answer 1

hi aparna,
<b>DIRECT INPUT</b>
TO ENTER THE DATA INTO THE CORRESPONDING DATABASE TABLES DIRECTLY, THE SYSTEM CALLS A NUMBER OF FUNCTION MODULES THAT EXECUTE ANY NECESSARY CHECKS. IN CASE OF ERRORS, THE DIRECT INPUT TECHNIQUE PROVIDES A RESTART MECHANISM. HOWEVER, TO BE ABLE TO ACTIVATE THE RESTART MECHANISM, DIRECT INPUT PROGRAMS MUST BE EXECUTED IN THE BACKGROUND ONLY. DIRECT INPUT CHECKS THE DATA THOROUGHLY AND THEN UPDATES THE DATABASE DIRECTLY.
TO MAINTAIN AND STRAT THESE PROGRAMS, USE PGM RBMVSHOW OR THE TRANSACTION BMVO.
<b>BATCH INPUT</b>
TYPES – SESSION METHOD, CALL TRANSACTION, DIRECT INPUT.
TO SAVE DATA IN THE BDCTAB, USE THE FIELDNAME ‘BDC_OKCODE’ AND FIELD VALUE OF ‘/11’.
BDCDATA
THIS IS A STRUCTURE WHICH CONTAINS THE FOLLOWING FIELDS.
PROGRAM – NAME OF TH MOD PROG ASSOCIATED WITH THE SCREEN. SET ONLY FOR THE FIRST RECORD OF THE SCREEN.
DYNPRO – SCREEN NUMBER. ALSO SET ONLY FOR FIRST RECORD.
DYNBEGIN – INDICATES THE FIRST RECORD OF THE SCREEN. SET ‘X’ FOR FIRST RECORD OTHERWISE ‘ ‘.
FNAM – FIELD NAME.
FVAL – VALUE FOR THE FIELD NAMED IN FNAM.
THE FIRST STEP IN BDC IS TO UPLOAD DATA FROM THE FLAT FILE OR SEQUENTIAL FILE TO THIS BDCTABLE.
SESSION METHOD
WE USE 3 FUNCTION MODULES IN THIS SESSION METHOD.
1) BDC_OPEN_GROUP
     USER NAME:     USER NAME
     GROUP:          NAME OF THE SESSION
     LOCK DATE:     THE DATE ON WHICH YOU WANT TO PROCESS THE                              SESSION.
     KEEP:          THIS PARAMETER IS PASSED AS ‘X’ WHEN YOU WANT TO RETAIN SESSION AFTER     PROCESSING IT OR ‘ ‘ TO DELETE IT AFTER PROCESSING.
THIS CREATES A SESSION
2) BDC_INSERT
     TCODE:          TRANSACTION NAME
     DYNPROTAB:     BDC DATA
THIS CREATES A SEESION AND DATA IS TRANSFERRED O SESSION.
3) BDC_CLOSE_GROUP – THIS CLOSES THE BDC GROUP.
ONLY ONE SESSION CAN BE CREATED USING BDC_OPEN_GROUP. BUT MULTIPLE TRANSACTIONS CAN BE PROCESSED USING BDC_INSERT.
CALL TRANSACTION
CALL TRANSACTION     <TCODE> USING <BDCTAB>
                                        MODE <A/N/E>
                                        UPDATE <S/A>
                    MESSAGES INTO <MSGTAB>.
A – ALL SCREEN MODE. ALL THE SCREEN OF THE TRANSACTION ARE DISPLAYED.
N – NO SCREEN MODE. NO SCREEN IS DISPLAYED WHEN YOU EXECUTE THE TRANSACTION.
E – ERROR SCREEN. IF THE SCREEN HAS ERROR RECORD, THEN THAT SCREEN WILL BE DISPLAYED.
S - IF YOU CHANGE DATA OF ONE TABLE THEN ALL THE RELATED TABLES GETS UPDATED. AND SY-SUBRC IS RETURNED I.E., SY-SUBRC IS RETURNED FOR ONCE AND ALL.
A - WHEN YOU CHANGE DATA OF ONE TABLE, THE SY-SUBRC IS RETURNED. AND THEN UPDATING OF OTHER AFFECTED TABLES TAKES PLACE.  SO IF SYSTEM FAILS TO UPDATE OTHER TABLES, STILL SY-SUBRC RETURNED IS 0 (I.E., WHEN FIRST TABLE GETS UPDATED
WHEN YOU UPDATE DATABASE TABLE, OPERATION IS EITHER SUCCESSFUL OR UNSUCCESSFUL OR OPERATION IS SUCCESSFUL WITH SOME WARNING. THESE MESSAGES ARE STORED IN INTERNAL TABLE, WHICH YOU SPECIFY ALONG WITH MESSAGE STATEMENT. THIS INTERNAL TABLE SHOULD BE DECLARED LIKE BDCMSGCOLL, A STRUCTURE AVAILABLE IN ABAP/4. IT CONTAINS THE FOLLOWING FIELDS: TCODE, DYNAME, DYNUMB, MSGTYP, MSGID.
DIFFERENCE BETWEEN SESSION AND CALL TRANSACTION
          SESSION METHOD               CALL TRANSACTION
1.          DATA IS NOT UPDATED IN DATABASE TABLE UNLESS SESSION IS PROCESSED.               IMMEDIATE UPDATION IN DATABASE TABLE.
2.          NO SY-SUBRC IS RETURNED.               SY-SUBRC IS RETURNED.
3.          ERROR LOG IS CREATED FOR ERROR RECORDS.               ERRORS NEED TO BE HANDLED EXPLICITLY
4.          UPDATION IN DATABASE TABLE IS ALWAYS SYNCHRONOUS
               UPDATION IN DATABASE TABLE CAN BE SYNCHRONOUS OR ASYNCHRONOUS.
5.          ASYNCHRONOUS PROCESSING               SYNCHRONOUS PROCESSING
6.           TRANSFERS DATA FOR SINGLE TRANSACTIONS               TRANSFERS DATA FOR MULTIPLE TRANSACTIONS
ERROR HANDLING IN CALL TRANSACTION
1)     CREATE AN INTERNAL TABLE SIMILAR TO THE STRUCTURE OF YOUR LOCAL FILE.
2)     CREATE BDCTAB LIKE BDCDATA.
3)     CREATE BDCMSG LIKE BDCMSGCOLL.
4)     CREATE AN INTERNAL TABLE SIMILAR TO THE 1ST INTERNAL TABLE.
5)     UPLOAD FN UPLOADS DATA FROM THE LOCAL FILE TO THE ITAB.
6)     LOOP AT ITAB.
POPULATE BDCTAB TABLE.
CALL TRANSACTION STATEMENT.
PERFORM CHECK.
REFRESH BDCTAB.
ENDLOOP.
7)     FORM CHECK.
IF SY_SUBRC <> 0.
CALL FUNCTION FORMAT_MESSAGE.
APPEND ITAB2.
ENDFORM.
TRANSACTION FOR RECORDING – SHDB.
MAX TIME ALLOWED FOR ONLINE EXECUTION – 300 SECONDS.
<b>
Pls reward if helpful.</b>