The attached file takes you to the in depths of the BDC concepts. The concepts ranges from Concepts, Recording (SHDB), Content of Data, Influencing the execution, Troubleshooting the execution, Special Development, and Miscellaneous questions.

Download Link: BDC_concepts.

*source = Sandra Rossi

You might also be interested in these posts:

1. eCATT – Frequently Asked Questions (FAQs)
2. eCATT Tutorial
3. Step by Step LSMW Tutorial

To overcome of this dynamics we need to get to know where exactly our required view will appear e.g. line 6 or line 10 or line 15. We will use the FM SELECTION_VIEWS_FIND to find out which view will come at which position.

In our BDC, we will follow these steps:
1. Always select the Basic Data 1
2. Get the respective user command for the tab by Executing the FM SELECTION_VIEWS_FIND.

Status (MARA-VPSTA) contains the combination of the View indicator. You can find the relation of the status indicator and view name in the documentation of the data element PSTAT_D or follow this table:

 User department    Maintenance status 

 Work scheduling                A
Accounting                     B
Classification                 C
MRP                            D
Purchasing                     E
Production resources/tools     F
Costing                        G
Basic data                     K
Storage                        L
Forecasting                    P
Quality management             Q
Warehouse management           S
Sales                          V
Plant stocks                   X
Storage location stocks        Z

In this my test BDC, I want to update the MRP type. MRP type comes under the “MRP 1″ view of the material master. So, I will first select the Basic Data and than move to MRP 1 view and update the MRP type.

BDC Code:

REPORT ztest_np_mm02
       NO STANDARD PAGE HEADING LINE-SIZE 255.
*
* Local data
DATA:   messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
DATA:   bdcdata LIKE bdcdata    OCCURS 0 WITH HEADER LINE.
*
* Selection Screen
PARAMETERS: p_matnr TYPE mara-matnr OBLIGATORY,
            p_werks TYPE marc-werks OBLIGATORY,
            p_lgort TYPE rmmg1-lgort OBLIGATORY,
            p_dismm TYPE marc-dismm OBLIGATORY.
*
*
START-OF-SELECTION.
*
* Material views …………………………………………….
  DATA:  l_vpsta LIKE t130m-pstat.
*
  SELECT SINGLE vpsta
         INTO   l_vpsta
         FROM   mara
         WHERE  matnr = p_matnr.
*
* Get View sequence ………………………………………….
  DATA: l_bild  LIKE t133a-bilds,
        lt_bild LIKE mbildtab OCCURS 0 WITH HEADER LINE.
*
* Screen Sequence for Standard Industry tab pages in material master
  l_bild = ’21′.
*
* Get screen sequence
  CALL FUNCTION ‘SELECTION_VIEWS_FIND’
    EXPORTING
      bildsequenz     = l_bild
      pflegestatus    = l_vpsta
    TABLES
      bildtab         = lt_bild
    EXCEPTIONS
      call_wrong      = 1
      empty_selection = 2
      OTHERS          = 3.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
*
* Get the Tab page for MRP1 …………………………………..
  DATA: l_tab_mrp1 TYPE sy-ucomm.
*
* reading table with MRP view
  READ TABLE lt_bild WITH KEY pstat = ‘D’.
  IF sy-subrc = 0.
    l_tab_mrp1 = lt_bild-guifu.
  ENDIF.
*
* make ok code for the MRP1
  CONCATENATE ‘=’ l_tab_mrp1 INTO l_tab_mrp1.
*
* BDC ………………………………………………………
  PERFORM bdc_dynpro      USING ‘SAPLMGMM’ ’0060′.
  PERFORM bdc_field       USING ‘RMMG1-MATNR’
                                 p_matnr.
  PERFORM bdc_field       USING ‘BDC_OKCODE’
                                ‘=ENTR’.
*
  PERFORM bdc_dynpro      USING ‘SAPLMGMM’ ’0070′.
  PERFORM bdc_field       USING ‘MSICHTAUSW-KZSEL(01)’
                                ‘X’.
  PERFORM bdc_field       USING ‘BDC_OKCODE’
                                ‘=ENTR’.
*
  PERFORM bdc_dynpro      USING ‘SAPLMGMM’ ’4004′.
  PERFORM bdc_field       USING ‘BDC_OKCODE’
                                l_tab_mrp1.
*
  PERFORM bdc_dynpro      USING ‘SAPLMGMM’ ’0081′.
  PERFORM bdc_field       USING ‘RMMG1-WERKS’
                                p_werks.
  PERFORM bdc_field       USING ‘RMMG1-LGORT’
                                p_lgort.
  PERFORM bdc_field       USING ‘BDC_OKCODE’
                                ‘=ENTR’.
*
  PERFORM bdc_dynpro      USING ‘SAPLMGMM’ ’4000′.
  PERFORM bdc_field       USING ‘MARC-DISMM’
                                p_dismm.
  PERFORM bdc_field       USING ‘BDC_OKCODE’
                                ‘=BU’.
*
  PERFORM bdc_transaction USING ‘MM02′.
*
*&———————————————————————*
*&      Form  BDC_DYNPRO
*&———————————————————————*
FORM bdc_dynpro USING p_program
                      p_screen.
*
  MOVE: p_program TO bdcdata-program,
        p_screen  TO bdcdata-dynpro,
        ‘X’       TO bdcdata-dynbegin.
*
  APPEND bdcdata.
  CLEAR  bdcdata.
*
ENDFORM.                    ” BDC_DYNPRO
*
*&———————————————————————*
*&      Form  BDC_FIELD
*&———————————————————————*
FORM bdc_field USING p_field_name
                     p_field_value.
*
  MOVE: p_field_name  TO bdcdata-fnam,
        p_field_value TO bdcdata-fval.
*
  APPEND bdcdata.
  CLEAR  bdcdata.
*
ENDFORM.                    ” BDC_FIELD
*
*
*&———————————————————————*
*&      Form  BDC_TRANSACTION
*&———————————————————————*
FORM bdc_transaction USING tcode.
  DATA: l_mstring(480).
  DATA: l_subrc LIKE sy-subrc.
* batch input session
  REFRESH messtab.
  CALL TRANSACTION tcode USING bdcdata
                   MODE   ‘A’
                   “A: show all dynpros
                   “E: show dynpro on error only
                   “N: do not display dynpro
*
                   UPDATE ‘L’
                   MESSAGES INTO messtab.
  REFRESH bdcdata.
ENDFORM.                    “BDC_TRANSACTION

Download Code:

MM02 BDC

*source=nimesh

You might also be interested in these posts:

1. BDC to insert Wage Type in Infotype 0008 (Basic Pay)
2. Embed SAP View in an ABAP Program
3. Assign a T-code to Maintenance View in SAP

Upload programs where you use BDC session method to create Sessions, which should later be executed using transaction SM35.

Requirements before you start:

You need to know the BDC Session name, which is usually an input parameter or is generated by the report programs.

Steps to execute BDC Session from the program:

Step 1: Get BDC Queue ID

CALL FUNCTION ‘BDC_OBJECT_SELECT’

EXPORTING

name                  = session name

session_creator    = sy-uname

datatype             = ‘BDC’

client                  = sy-mandt

qstate                = ‘ ‘

date_from           = sy-datum

date_to              = sy-datum

TABLES

apqitab               = itab_apqi

EXCEPTIONS

OTHERS              = 1.

Queue ID (QID) = itab_apqi-qid

Step 2: Get Session Info

Get Session info for the queue ID from table APQI.

SELECT SINGLE * FROM apqi INTO session WHERE qid = QID (from Step 1).

Step3: Lock BDC Queue

CALL FUNCTION ‘ENQUEUE_BDC_QID’

EXPORTING

datatyp        = session-datatyp

groupid        = session-groupid

qid            = session-qid

EXCEPTIONS

foreign_lock   = 1

system_failure = 99.

Step4: OPEN JOB

DATA:  jobname   LIKE tbtco-jobname,

jobnumb   LIKE rsjobinfo-jobnumb,

Jobname = wa_session-groupid.

CALL FUNCTION ‘JOB_OPEN’

EXPORTING

jobgroup         = ‘BATCH-INPUT’

jobname          = jobname

sdlstrtdt        = sy-datum

sdlstrttm        = sy-uzeit

IMPORTING

jobcount         = jobnumb

EXCEPTIONS

cant_create_job  = 1

invalid_job_data = 2

jobname_missing  = 3

OTHERS           = 99.

Step5: Execute the Queue

Execute the QUEUE using Submit to Report RSBDCBTC.

SUBMIT rsbdcbtc

TO SAP-SPOOL

DESTINATION   space

IMMEDIATELY   space

KEEP IN SPOOL space

WITHOUT SPOOL DYNPRO

USER session-userid

VIA JOB       jobname

NUMBER        jobnumb

WITH queue_id  EQ  wa_session-qid

WITH mappe     EQ  jobname

WITH modus     EQ  ‘N’

WITH logall    EQ  ‘X’  ” Extended Log

AND RETURN.

If Sy-subrc = 0

Step6: Close Job

CALL FUNCTION ‘JOB_CLOSE’

EXPORTING

jobcount                   = jobnumb

jobname                    = jobname

strtimmed                  = ‘X’

targetsystem               = ”   ” Target Host

EXCEPTIONS

cant_start_immediate       = 1

invalid_startdate          = 2

jobname_missing            = 3

job_close_failed           = 4

job_nosteps                = 5

job_notex                  = 6

lock_failed                = 7

OTHERS                     = 99.

IF sy-subrc = 0

Step 7: Update Session info

UPDATE apqi SET   qstate  = ‘S’

WHERE destsys = wa_session-destsys

AND   destapp = wa_session-destapp

AND   datatyp = wa_session-datatyp

AND   groupid = wa_session-groupid

AND   progid  = wa_session-progid

AND   formid  = wa_session-formid

AND   qattrib = wa_session-qattrib

AND   qid     = wa_session-qid.

COMMIT WORK.

Step 8: Delete Job

If Job Not closed (Sy-subrc <> 0 for step 5 or 6), delete Job.

CALL FUNCTION ‘BP_JOB_DELETE’

EXPORTING

jobname    = jobname

jobcount   = jobnumb

forcedmode = ‘X’

EXCEPTIONS

OTHERS     = 99.

Step 9: Unlock BDC queue

CALL FUNCTION ‘DEQUEUE_BDC_QID’

EXPORTING

datatyp = wa_session-datatyp

groupid = wa_session-groupid

qid     = wa_session-qid.

So you are all done. Hope that was simple. 

You might also be interested in these posts:

1. Pretty Report Vs Pretty Printer in ABAP
2. Display a Popup and Get Values from User
3. Convert Spool Request to PDF in SAP

• BDC (Batch Data Communication)
• LSMW (Legacy System Migration Workbench)

This document presents Overview of LSMW and to provides you information about how to use this functionality.

Following are the highlights from this presentation:

• Difference between BDC & LSMW
• What is LSMW ? Principles, Features and Pre-Requisities for LSMW
• Import methods defined: IDOC’ s,BAPI’s, Standart/Direct Input, Batch Input
• Steps for using conversion tool LSMW
• Procedures for Direct Input Method, Batch Input Method, BAPI in LSMW and so on..

Download Link: Step by Step LSMW Tutorial

You might also be interested in these posts:

1. Difference Between LSMW and BDC
2. eCATT Tutorial
3. Complete Reference to ABAP Basics

The differences between LSMW and BDC are as follows:

LSMW is generally for normal SAP applications, while BDC is mainly for any customized applications.

LSMW is a Non-SAP to SAP communication TOOL, whereas BDC is a SAP to SAP communication UTILITY.

LSMW(Legacy System Migration Workbench) is a more user-friendly tool, through which one can do the same work as the BDC. One just has to follow the 14 steps. LSMW offers four ways to import data into SAP, and they are:

BDC, Direct Input, BAPI(BO) and IDOC.

BDC(Batch Data Communication) is basically a program which is either generated by SAP after a recording or programmed by a abaper. It’s like running the transaction manually but all the data is populated in the screens automatically. It is a bit complex when the screen contains Table Controls.

LSMW provides various methods for migration of data, namely those of Direct Input, Batch Input recording and IDOC. BDC however simply makes use of recording. There are two ways of implementing BDC, the Call transaction metod and the Session method.

In LSMW, mapping is taken care of with the help of SAP, whereas in BDC one has to provide explicit mapping directions.

In BDC, we can schedule the job, so the uploading can be done at the same time or later periodically while in LSMW it has to be done at once only. So through LSMW, one cannot upload huge amount of data. Hence we use LSMW for updating or inserting below 5000 records and we use BDC to upload records more than 5000.

Coding is not very flexible in LSMW, whereas in BDC coding is very flexible and applications can be easily customized. this is mainly because LSMW is devised specially for functional consultants who do not perform coding, while BDC is mainly used by technical consultants, who perform coding.

You might also be interested in these posts:

1. Step by Step LSMW Tutorial
2. Difference Between BAPI and RFC
3. Batch Input – Frequently Asked Questions(FAQs)