IDOCS OUTBOUND TRIGGER PART TWO

The messages are typically processed byFORM ENTRY in PROGRAM RSNAST00.If we are dealing with printing or faxing andFORM EDI_PROCESSING in PROGRAM RSNASTED.If we are dealing with IDocsFORM ALE_PROCESSING in PROGRAM RSNASTED.

If we are dealing with ALE,The following piece of code does principally the same thing as RSNAST00 does and makes full use of all customizing settings for message handling.

TABLES: NAST.
SELECT * FROM NAST ...
PERFORM einzelnachricht IN PROGRAM RSNAST00

The processing routine for the respective media and message is customized in the table TNAPR. This table records the name of a FORM routine, which processes the message for the chosen media and the name of an ABAP where this FORM is found.The ABAP RSNAST00 is the standard ABAP, which is used to collect unprocessed NAST message and to execute the assigned action.

RSNAST00 can be executed as a collector batch run, that eventually looks for unprocessed IDocs. The usual way of doing that is to define a batch-run job with transaction SM37. This job has to be set for periodic processing and start a program that triggers the IDoc re-sending.

Cave! RSNAST00 will only look for IDocs which are set to NAST-VSZTP = '1' or '2' (Time of processing). VSZPT = '3' or '4' is ignored by RSNAST00.

Start RSNAST00 in the foreground first and find the parameters that match your required selection criteria. Save them as a VARIANT and then define the periodic batch job using the variant.If RSNAST00 does not meet 100% your needs you can create an own program similar to RSNAST00. The only requirement for this program are two steps:

* Read the NAST entry to process into structure NAST tables nast.
data: subrc like sy-subrc.....
select from NAST where .......
* then call FORM einzelnachricht(rsnast00) to process the record PERFORM einzelnachricht(rsnast00) USING subrc.

RELATED POSTS

IDOC OUT BOUND TRIGGERS

IDocs should be sent out at certain events. Therefore you have to define a trigger. A lot of consideration is required to determine the correct moment when to send out the IDoc. The IDoc can be triggered at a certain time or when an event is raised. R/3 uses several completely different methods to determine the trigger point.

There are messages to tell the system that there is an IDoc waiting for dispatching, there are log files which may be evaluated to see if IDocs are due to send and there can be a workflow chain triggered, which includes the sending of the IDoc.

The simplest way to create IDocs, is to write an ABAP. The individual ABAP can either be a triggering ABAP which runs at certain events, e.g. every night, or it can be an ABAP which does the complete IDoc creation from scratch.A triggering ABAP would simply try to determine which IDocs need sending and call the appropriate IDoc creation routines.

You may also imagine the ABAP to do all the job. As this is mostly reinventing the wheel, it is not really recommended and should be reserved to situation, where the other solution do not provide an appropriate mean.You can use the R/3 message concept to trigger IDocs the same way as you trigger SAPscript printing.One of the key tables in R/3 is the table NAST. This table records reminders written by applications. Those reminders are called messages.

Every time when an applications sees the necessity to pass information to a third party. a message is written to NAST. A message handler will eventually check the entries in the table and cause an appropriate action.

The concept of NAST messages has originally been designed for triggering SAPscript printing. The very same mechanism is used for IDocs, where the IDoc processor replaces the print task, as an IDoc is only the paperless form of a printed document.The messages are usually be created using the condition technique, a mechanism available to all major R/3 applications.

The conditions are set up the same way for any output media. So you may define a condition for printing a document and then just change the output media from printer to IDoc/EDI or ALE.

Creating NAST messages is a standard functionality in most of the SAP core applications. Those applications - e.g. VA01, ME21 - perform calls to the central function module MESSAGING of group V61B. The function module uses customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record stores all information that is necessary to create an IDoc. This includes mainly an object key to identify the processed object and application to the message handler and the sender and receiver information.

Creating NAST messages is a standard functionality in most of the SAP core applications. Those applications - e.g. VA01, ME21 - perform calls to the central function module MESSAGING of group V61B. The function module uses customizing entries, mainly those of the tables T681* to T685*.

A NAST output message is stored as a single record in the table NAST. The record stores all information that is necessary to create an IDoc. This includes mainly an object key to identify the processed object and application to the message handler and the sender and receiver information.

RELATED POSTS

ABAP IDOC'S INBOUND BASIC TOOLS 3

The declaration of valid combinations is done to allow validation, if the system can handle a certain combination.

The combination of message type and IDoc type determine the processing algorithm. This is usually a function module with a well defined interface or a SAP business object and is set up in table EDIFCT.The entry made here points to a function module which will be called when the IDoc is to be processed.

The entries for message code and message function are usually left blank. They can be used to derive sub types of messages together with the partner profile used. Figure  Assign a handler function to a message/message type The definition for inbound and outbound IDocs is analogous. Of course, the function module will be different.



uses the method of logical process codes to detach the IDoc processing and the processing function module. They assign a logical name to the function instead of specifying the physical function name.
The IDoc functions are often used for a series of message type/IDoc type combination. It is necessary to replace the processing function by a different one. E.g. when you make a copy of a standard function to avoid modifying the standard. The combination message type/IDoc will determine the logical processing code, which itself points to a function. If the function changes, only the definition of the processing codes will be changed and the new function will be immediately effective for all IDocs associated with the process code.

For inbound processing codes you have to specify the method to use for the determination of the inbound function.


This is the option you would usually choose. It allows processing via the ALE scenarios.

 After defining the processing code you have to assign it to one or several logical message types. This declaration is used to validate, if a message can be handled by the receiving system.The inbound processing code is assigned analogously. The processing code is a pointer to a function module which can handle the inbound request for the specified IDoc and message type.

The definition of the processing code is identifying the handler routine and assigning a serious of processing options.You need to click "Processing with ALE", if your function can be used via the ALE engine. This is the option you would usually choose. It allows processing via the ALE scenarios.



Associate a function module with a process code For inbound processing you need to indicate whether the function will be capable of dialog processing. This is meant for those functions which process the inbound data via call transaction. Those functions can be replayed in visible batch input mode to check why the processing might have failed.




RELATED LINKS

ABAP BDC SESSION METHOD SAMPLE CODE

* pool of form routines
include zmppn001.

* Define BDC Table Structure
data: begin of itab_bdc_tab occurs 0.
include structure bdcdata.
data: end of itab_bdc_tab.

* Input record layout of Leagcy File
data: begin of itab_xcel occurs 0,
matnr(18) type c,
werks(4) type c,
alnag(2) type c,
verid(4) type c,
text1(40) type c,
bstmi like mkal-bstmi,
bstma like mkal-bstma,
adatu(10) type c,
bdatu(10) type c,
stlal(2) type c,
stlan(1) type c,
serkz(1) type c,
mdv01(8) type c,
elpro(4) type c,
alort(4) type c,
end of itab_xcel.

data: begin of lt_pp04_cache occurs 0,
matnr like itab_xcel-matnr,
werks like itab_xcel-werks,
alnag like itab_xcel-alnag,
plnnr like mapl-plnnr,
arbpl like crhd-arbpl,
ktext like crtx-ktext,
end of lt_pp04_cache.

data: v_ssnnr(4) type n,
v_lines_in_xcel like sy-tabix,
v_ssnname like apqi-groupid,
v_trans_in_ssn type i,
* wa_xcel LIKE itab_xcel,
l_tabix like sy-tabix,
v_matnr like rc27m-matnr,
v_plnnr like mapl-plnnr,
v_plnal like mapl-plnal,
v_tcode like sy-tcode value 'C223',
v_plnty like plas-plnty value 'R',
v_objty like crhd-objty value 'A',
v_plpo_steus like plpo-steus value 'PP04',
v_verwe like crhd-verwe value '0007'.


* Parameters
selection-screen: skip 3.
selection-screen: begin of block 1 with frame.
*
parameters: p_name like rlgrap-filename
default 'C:\My Documents\InputFile.txt'
obligatory,
* bdc session name prefix
p_bdcpfx(6) default 'ZPVCRT'
obligatory,
* number for transction per BDC session
p_trnssn type i
default 2000 obligatory,
* retain the BDC session after successfull execution
p_keep like apqi-qerase
default 'X',
* user who will be executing BDC session
p_uname like apqi-userid
default sy-uname
obligatory.
*
selection-screen: end of block 1.
*
********************************************************
********************************************************
*
* possible entry list (F4 dropdown) for input file name
at selection-screen on value-request for p_name.

*-SELECT FILE FROM USERS LOCAL PC
call function 'WS_FILENAME_GET'
exporting
* DEF_FILENAME = ' '
def_path = 'C:\Temp\'
mask = ',*.*,*.*.'
mode = 'O'
title = 'Select File '(007)
importing
filename = p_name
* RC =
exceptions
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
others = 5.

if sy-subrc <> 0.
* MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
* WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*
********************************************************
********************************************************
*
* begin the show :-)
*
start-of-selection.

* read data from input file
perform transfer_xcel_to_itab.
*
*
loop at itab_xcel.

* hang on to xcel line num
l_tabix = sy-tabix.

* each line in the xcel file marks begining of new prod.version defn
* if num-of-trnas-in-session = 0, create new BDC session
if v_trans_in_ssn is initial.
perform bdc_session_open.
endif.

* begin new bdc script for rtg create trans
* fill in bdc-data for prod.version maintenance screens
perform bdc_build_script.

* insert the bdc script as a BDC transaction
perform bdc_submit_transaction.

* keep track of how many BDC transactions were inserted in the BDC
* session
add 1 to v_trans_in_ssn.
* if the user-specified num of trans in BDC session is reached OR
* if end of input file is reached, close the BDC session
if v_trans_in_ssn = p_trnssn or
l_tabix = v_lines_in_xcel.
perform bdc_session_close.
clear v_trans_in_ssn.
endif.

endloop.

top-of-page.
call function 'Z_HEADER'
* EXPORTING
* FLEX_TEXT1 =
* FLEX_TEXT2 =
* FLEX_TEXT3 =
.
*---------------------------------------------------------------------*
* FORM TRANSFER_XCEL_TO_ITAB *
*---------------------------------------------------------------------*
* Transfer Xcel Spreadsheet to SAP Internal Table *
*---------------------------------------------------------------------*
form transfer_xcel_to_itab.
*
* Read the tab-delimited file into itab
call function 'WS_UPLOAD'
exporting
filename = p_name
filetype = 'DAT'
* IMPORTING
* filelength = flength
tables
data_tab = itab_xcel
exceptions
conversion_error = 1
file_open_error = 2
file_read_error = 3
invalid_table_width = 4
invalid_type = 5
no_batch = 6
unknown_error = 7
others = 8.
*
if sy-subrc = 0.
* sort the data
sort itab_xcel by matnr werks.
clear v_lines_in_xcel.
* if no data in the file - error out
describe table itab_xcel lines v_lines_in_xcel.
if v_lines_in_xcel is initial.
write: / 'No data in input file'.
stop.
endif.
else.
* if file upload failed - error out
write: / 'Error reading input file'.
stop.
endif.

endform.

*---------------------------------------------------------------------*
* FORM BDC_SESSION_OPEN *
*---------------------------------------------------------------------*
* Open BDC Session *
*---------------------------------------------------------------------*
form bdc_session_open.

* create bdc session name = prefix-from-selectn-screen + nnnn
add 1 to v_ssnnr.
concatenate p_bdcpfx v_ssnnr into v_ssnname.

* open new bdc session
call function 'BDC_OPEN_GROUP'
exporting
client = sy-mandt
group = v_ssnname
keep = p_keep
user = p_uname
exceptions
client_invalid = 1
destination_invalid = 2
group_invalid = 3
group_is_locked = 4
holddate_invalid = 5
internal_error = 6
queue_error = 7
running = 8
system_lock_error = 9
user_invalid = 10
others = 11.

endform.

*---------------------------------------------------------------------*
* FORM BDC_BUILD_SCRIPT *
*---------------------------------------------------------------------*
* Build BDC *
*---------------------------------------------------------------------*
form bdc_build_script.

data: l_arbpl like crhd-arbpl,
l_text1 like mkal-text1,
l_mdv01 like mkal-mdv01,
l_mapl like mapl.


* clear bdc-data itab - begin of new bdc transaction
clear itab_bdc_tab.
refresh itab_bdc_tab.
*
* read material cross reference tables to determine sap part#
clear : v_matnr, v_plnnr, v_plnal.
perform read_matnr_cross_ref using itab_xcel-matnr
itab_xcel-werks
changing v_matnr.
*
* determine the version description to use
if itab_xcel-text1 is initial.
l_text1 = itab_xcel-verid.
else.
l_text1 = itab_xcel-text1.
endif.

* determine the routing group# and group ctr# to use
perform read_routing .
*
* determine the production line to use
if itab_xcel-mdv01 is initial.
* if not provided in the file then:
* prod line = work ctr on the last PP04 op of the rtg determined above
perform read_wc_on_last_pp04 using v_plnnr v_plnal
changing l_mdv01.
* NOTE: when executing the above form\routine, if v_plnnr is initial
* or v_plnal is initial, THEN l_mdv01 will automatically be
* returned blank (ie initial)
else.
l_mdv01 = itab_xcel-mdv01.
endif.

*
* build bdc script
perform bdc_build_script_record
*
* fill in initial screen
using: 'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=ENTE',
' ' 'MKAL-WERKS' itab_xcel-werks,
' ' 'MKAL-MATNR' v_matnr,
' ' 'MKAL_ADMIN-DISPO' space,
' ' 'MKAL-PLNNR' space,
' ' 'MKAL_ADMIN-STTAG' space,
' ' 'MKAL-PLNNG' space,
' ' 'MKAL-MDV01' space,
' ' 'MKAL-PLNNM' space,
* click create button on initial screen and go to detail screen
'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=CREA',
* fill in the detail screen and go back to initial screen
'X' 'SAPLCMFV' '2000',
' ' 'BDC_OKCODE' '=CLOS',
' ' 'MKAL_EXPAND-MATNR' v_matnr,
' ' 'MKAL_EXPAND-VERID' itab_xcel-verid,
' ' 'MKAL_EXPAND-TEXT1' l_text1,
' ' 'MKAL_EXPAND-BSTMI' itab_xcel-bstmi,
' ' 'MKAL_EXPAND-BSTMA' itab_xcel-bstma,
' ' 'MKAL_EXPAND-ADATU' itab_xcel-adatu,
' ' 'MKAL_EXPAND-BDATU' itab_xcel-bdatu,
' ' 'MKAL_EXPAND-PLTYG' v_plnty,
' ' 'MKAL_EXPAND-PLNNG' v_plnnr,
' ' 'MKAL_EXPAND-ALNAG' v_plnal,
' ' 'MKAL_EXPAND-STLAL' itab_xcel-stlal,
' ' 'MKAL_EXPAND-STLAN' itab_xcel-stlan,
' ' 'MKAL_EXPAND-SERKZ' itab_xcel-serkz,
' ' 'MKAL_EXPAND-MDV01' l_mdv01,
' ' 'MKAL_EXPAND-ELPRO' itab_xcel-elpro,
' ' 'MKAL_EXPAND-ALORT' itab_xcel-alort,
* save the production version from initial screen
'X' 'SAPLCMFV' '1000',
' ' 'BDC_OKCODE' '=SAVE'.

*
endform.

*---------------------------------------------------------------------*
* FORM BDC_SUBMIT_TRANSACTION *
*---------------------------------------------------------------------*
* Submit BDC Session *
*---------------------------------------------------------------------*
form bdc_submit_transaction.

** Load BDC script as a trqansction in BDC session
call function 'BDC_INSERT'
exporting
tcode = v_tcode
tables
dynprotab = itab_bdc_tab
exceptions
internal_error = 01
not_open = 02
queue_error = 03
tcode_invalid = 04.

endform.

*---------------------------------------------------------------------*
* FORM BDC_BUILD_SCRIPT_RECORD *
*---------------------------------------------------------------------*
form bdc_build_script_record using dynbegin name value.

clear itab_bdc_tab.
if dynbegin = 'X'.
move: name to itab_bdc_tab-program,
value to itab_bdc_tab-dynpro,
'X' to itab_bdc_tab-dynbegin.
else.
move: name to itab_bdc_tab-fnam,
value to itab_bdc_tab-fval.
shift itab_bdc_tab-fval left deleting leading space.
endif.

append itab_bdc_tab.

endform.

*---------------------------------------------------------------------*
* FORM BDC_SESSION_CLOSE *
*---------------------------------------------------------------------*
* Close BDC Session *
*---------------------------------------------------------------------*
form bdc_session_close.

* close the session
call function 'BDC_CLOSE_GROUP'
exceptions
not_open = 1
queue_error = 2
others = 3.

skip 2.
if sy-subrc ne 0.
write: / 'Error Closing BDC Session ' , 'RETURN CODE: ', sy-subrc.
else.
write : / 'Session created:', v_ssnname,
50 '# of transactions:', v_trans_in_ssn.
endif.

endform.
*&---------------------------------------------------------------------*
*& Form read_routing_cache
*&---------------------------------------------------------------------*
*FORM read_routing_cache USING pi_matnr
* pi_werks
* pi_alnag
* pi_verid
* pi_mdv01.
*
* DATA: BEGIN OF lt_plpo OCCURS 0,
* vornr LIKE plpo-vornr,
* objty LIKE crhd-objty,
* objid LIKE crhd-objid,
* arbpl LIKE crhd-arbpl,
* END OF lt_plpo,
* l_mapl_plnnr LIKE mapl-plnnr.
*
** determine the routing group#
* CLEAR lt_pp04_cache.
** chk if its in the cache first, if not then get it from MAPL table
** and put it in the cache
* READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr
* werks = pi_werks
* alnag = pi_alnag.
* IF sy-subrc = 0.
** do nothing - lt_pp04_cache header line has rtg#
* ELSE.
** get the routing group # from MAPL
* SELECT plnnr INTO l_mapl_plnnr
* FROM mapl UP TO 1 ROWS
* WHERE matnr = pi_matnr AND
* werks = pi_werks AND
* plnty = 'R' AND
* plnal = pi_alnag AND
* loekz = space.
* ENDSELECT.
** put it in the cache internal table
* IF NOT l_mapl_plnnr IS INITIAL.
* lt_pp04_cache-matnr = pi_matnr.
* lt_pp04_cache-werks = pi_werks.
* lt_pp04_cache-alnag = pi_alnag.
* lt_pp04_cache-plnnr = l_mapl_plnnr.
* APPEND lt_pp04_cache.
* ENDIF.
* ENDIF.
*
** if the rtg# was determined AND
** -- the work center was not determined yet AND
** -- work center was really needed for this line in the input file
** then
** -- read the work center from last PP04 operation on the routing
** -- update the cache accordingly
*
*
* IF NOT lt_pp04_cache-plnnr IS INITIAL AND
* lt_pp04_cache-arbpl IS INITIAL AND
* ( pi_verid IS INITIAL OR
* pi_mdv01 IS INITIAL ).
*
** read the last PP04 operation
* CLEAR lt_plpo.
* REFRESH lt_plpo.
* SELECT vornr e~objty e~objid e~arbpl
* INTO CORRESPONDING FIELDS OF TABLE lt_plpo
* FROM plas AS b
* INNER JOIN plpo AS c
* ON b~plnty = c~plnty AND
* b~plnnr = c~plnnr AND
* b~zaehl = c~zaehl
* INNER JOIN crhd AS e
* ON c~arbid = e~objid
* WHERE b~plnty = v_plnty AND
* b~plnnr = lt_pp04_cache-plnnr AND
* b~plnal = lt_pp04_cache-alnag AND
* c~loekz = space AND
* c~steus = v_plpo_steus AND
* e~objty = v_objty AND
* e~werks = lt_pp04_cache-werks AND
* e~verwe = v_verwe.
* SORT lt_plpo BY vornr DESCENDING.
* READ TABLE lt_plpo INDEX 1.
**
* IF NOT lt_plpo-arbpl IS INITIAL.
* lt_pp04_cache-arbpl = lt_plpo-arbpl.
** read work center description
* SELECT SINGLE ktext INTO lt_pp04_cache-ktext
* FROM crtx WHERE objty = lt_plpo-objty AND
* objid = lt_plpo-objid AND
* spras = sy-langu.
** the following read will get the index of the correct record to be
** updated in the cache
* READ TABLE lt_pp04_cache
* WITH KEY matnr = pi_matnr
* werks = pi_werks
* alnag = pi_alnag.
* MODIFY lt_pp04_cache
* INDEX sy-tabix
* TRANSPORTING arbpl ktext.
* ENDIF.
* ENDIF.
*
*ENDFORM. " read_last_pp04_operation_cache
*&---------------------------------------------------------------------*
*& Form read_routing
*&---------------------------------------------------------------------*
form read_routing.

data: begin of lt_mapl occurs 0,
plnnr like mapl-plnnr,
plnal like mapl-plnal,
end of lt_mapl,
l_arbpl like crhd-arbpl.

* get all the rtg# and grp ctr# from MAPL
select plnnr plnal
into corresponding fields of table lt_mapl
from mapl
where matnr = v_matnr and
werks = itab_xcel-werks and
plnty = v_plnty and "Rate Routing
loekz = space. "with del flag = OFF
sort lt_mapl by plnal.

if not itab_xcel-verid is initial.
* if the verid=0001 then use the 1st good rtg-grp# and grp-ctr#
if itab_xcel-verid = '0001'.
read table lt_mapl index 1.
v_plnnr = lt_mapl-plnnr.
v_plnal = lt_mapl-plnal.
else.
* if the verid<>0001 then use the rtg-grp# and grp-ctr# of the routing
* whose work center on the last PP04 operation matches the given verid
loop at lt_mapl.
clear l_arbpl.
* get the work center from the last PP04 operation
perform read_wc_on_last_pp04 using lt_mapl-plnnr
lt_mapl-plnal
changing l_arbpl.
*
if itab_xcel-verid = l_arbpl.
v_plnnr = lt_mapl-plnnr.
v_plnal = lt_mapl-plnal.
exit.
endif.
endloop.
endif.
else.
* do nothing
endif.

* For version IDs that are other then '0000' or 'ZWIP' :--
if itab_xcel-verid NE '0000' and
itab_xcel-verid NE 'ZWIP'.
* if routing group# or group counter was not determined, make the
* valid-to date 99/99/9999 so that the BDC, on execution, errors out.
if v_plnnr is initial or
v_plnal is initial.
itab_xcel-bdatu = '99/99/9999'.
endif.
endif.

** determine the routing group#
* CLEAR lt_pp04_cache.
** chk if its in the cache first, if not then get it from MAPL table
** and put it in the cache
* READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr
* werks = pi_werks
* alnag = pi_alnag.
* IF sy-subrc = 0.
** do nothing - lt_pp04_cache header line has rtg#
* ELSE.
** get the routing group # from MAPL
** put it in the cache internal table
* IF NOT l_mapl_plnnr IS INITIAL.
* lt_pp04_cache-matnr = pi_matnr.
* lt_pp04_cache-werks = pi_werks.
* lt_pp04_cache-alnag = pi_alnag.
* lt_pp04_cache-plnnr = l_mapl_plnnr.
* APPEND lt_pp04_cache.
* ENDIF.
* ENDIF.
*
** if the rtg# was determined AND
** -- the work center was not determined yet AND
** -- work center was really needed for this line in the input file
** then
** -- read the work center from last PP04 operation on the routing
** -- update the cache accordingly
*
*
* IF NOT lt_pp04_cache-plnnr IS INITIAL AND
* lt_pp04_cache-arbpl IS INITIAL AND
* ( pi_verid IS INITIAL OR
* pi_mdv01 IS INITIAL ).
*
** read the last PP04 operation
* CLEAR lt_plpo.
* REFRESH lt_plpo.
* SELECT vornr e~objty e~objid e~arbpl
* INTO CORRESPONDING FIELDS OF TABLE lt_plpo
* FROM plas AS b
* INNER JOIN plpo AS c
* ON b~plnty = c~plnty AND
* b~plnnr = c~plnnr AND
* b~zaehl = c~zaehl
* INNER JOIN crhd AS e
* ON c~arbid = e~objid
* WHERE b~plnty = v_plnty AND
* b~plnnr = lt_pp04_cache-plnnr AND
* b~plnal = lt_pp04_cache-alnag AND
* c~loekz = space AND
* c~steus = v_plpo_steus AND
* e~objty = v_objty AND
* e~werks = lt_pp04_cache-werks AND
* e~verwe = v_verwe.
* SORT lt_plpo BY vornr DESCENDING.
* READ TABLE lt_plpo INDEX 1.
**
* IF NOT lt_plpo-arbpl IS INITIAL.
* lt_pp04_cache-arbpl = lt_plpo-arbpl.
** read work center description
* SELECT SINGLE ktext INTO lt_pp04_cache-ktext
* FROM crtx WHERE objty = lt_plpo-objty AND
* objid = lt_plpo-objid AND
* spras = sy-langu.
** the following read will get the index of the correct record to be
** updated in the cache
* READ TABLE lt_pp04_cache
* WITH KEY matnr = pi_matnr
* werks = pi_werks
* alnag = pi_alnag.
* MODIFY lt_pp04_cache
* INDEX sy-tabix
* TRANSPORTING arbpl ktext.
* ENDIF.
* ENDIF.

endform. " read_last_pp04_operation_cache
*&---------------------------------------------------------------------*
*& Form read_wc_on_last_pp04
*&---------------------------------------------------------------------*
form read_wc_on_last_pp04 using pi_plnnr
pi_plnal
changing pe_arbpl.

data: begin of lt_plpo occurs 0,
vornr like plpo-vornr,
objty like crhd-objty,
objid like crhd-objid,
arbpl like crhd-arbpl,
end of lt_plpo.

* get all the PP04 operations for the given rtg# & grp-ctr#
select vornr e~objty e~objid e~arbpl
into corresponding fields of table lt_plpo
from plas as b
inner join plpo as c
on b~plnty = c~plnty and
b~plnnr = c~plnnr and
b~zaehl = c~zaehl
inner join crhd as e
on c~arbid = e~objid
where b~plnty = v_plnty and "Rate Routing
b~plnnr = pi_plnnr and
b~plnal = pi_plnal and
c~loekz = space and "Oper Del Flag = OFF
c~steus = v_plpo_steus and "PP04
e~objty = v_objty. "WC Obj Type = 'A'
* read the last operation
sort lt_plpo by vornr descending.
read table lt_plpo index 1.
pe_arbpl = lt_plpo-arbpl.

endform.

RELATED LINKS

BDC 1
BDC 2
BDC 9
BDC SAMPLE CODE XD 01

ABAP BDC SAMPLE CODE XD01

*----------------------------------------------------------------------*
* Table/Structure declarations. *
*----------------------------------------------------------------------*

TABLES : KNA1. "Customer master

*----------------------------------------------------------------------*
* Constants declarations. *
*----------------------------------------------------------------------*

CONSTANTS : C_MODE VALUE 'A',
C_UPDATE VALUE 'S',
C_X VALUE 'X',
C_SESS TYPE APQI-GROUPID VALUE 'ZCUSTOMER', "Session Name
C_XD01 LIKE TSTC-TCODE VALUE 'XD01'.

*----------------------------------------------------------------------*
* Variable declarations. *
*----------------------------------------------------------------------*

DATA : V_FNAME(15) VALUE SPACE, " Name of file to be created
V_FAILREC TYPE I, " No of failed records
V_MSG(255), " Message Text
V_ERRREC TYPE I, " No of failed records
V_LINES TYPE I, " No of records
V_BANKS(15), " Table column BANKS
V_BANKL(15), " Table column BANKL
V_BANKN(15), " Table column BANKN
V_TIDX(2) TYPE N. " Table row index



*----------------------------------------------------------------------*
*-- FLAG DECLARATIONS
*----------------------------------------------------------------------*

DATA : FG_DATA_EXIST VALUE 'X', " Check for data
FG_SESSION_OPEN VALUE ' '. " Check for Session Open

*----------------------------------------------------------------------*
*-- MACRO DEFINITIONS
*----------------------------------------------------------------------*

*-- Macro for BANKS
DEFINE BANKS.
CLEAR V_BANKS.
CONCATENATE 'KNBK-BANKS(' &1 ')' INTO V_BANKS.
CONDENSE V_BANKS.
END-OF-DEFINITION.


*-- Macro for BANKL
DEFINE BANKL.
CLEAR V_BANKL.
CONCATENATE 'KNBK-BANKL(' &1 ')' INTO V_BANKL.
CONDENSE V_BANKL.
END-OF-DEFINITION.


*-- Macro for BANKN
DEFINE BANKN.
CLEAR V_BANKN.
CONCATENATE 'KNBK-BANKN(' &1 ')' INTO V_BANKN.
CONDENSE V_BANKN.
END-OF-DEFINITION.



*----------------------------------------------------------------------*
* Structures / Internal table declarations *
*----------------------------------------------------------------------*

*-- Structure to hold BDC data
TYPES : BEGIN OF T_BDCTABLE.
INCLUDE STRUCTURE BDCDATA.
TYPES END OF T_BDCTABLE.

*-- Structure to trap BDC messages
TYPES : BEGIN OF T_MSG.
INCLUDE STRUCTURE BDCMSGCOLL.
TYPES : END OF T_MSG.

*-- Structure to trap ERROR messages
TYPES : BEGIN OF T_ERR_MSG,
MESSAGE(255),
END OF T_ERR_MSG.


*--Internal table to store flat file data
DATA : BEGIN OF IT_KNA1 OCCURS 0,
KUNNR LIKE KNA1-KUNNR,
KTOKD LIKE T077D-KTOKD,
NAME1 LIKE KNA1-NAME1,
SORTL LIKE KNA1-SORTL,
ORT01 LIKE KNA1-ORT01,
PSTLZ LIKE KNA1-PSTLZ,
LAND1 LIKE KNA1-LAND1,
SPRAS LIKE KNA1-SPRAS,
LZONE LIKE KNA1-LZONE,
END OF IT_KNA1.

*--Internal table to store bank details
DATA : BEGIN OF IT_BANK OCCURS 0,
BANKS LIKE KNBK-BANKS,
BANKL LIKE KNBK-BANKL,
BANKN LIKE KNBK-BANKN,
END OF IT_BANK.

*-- Internal table to hold BDC data
DATA: IT_BDCDATA TYPE STANDARD TABLE OF T_BDCTABLE WITH HEADER LINE,

*-- Internal Table to store ALL messages
IT_MSG TYPE STANDARD TABLE OF T_MSG WITH HEADER LINE,

*-- Internal Table to store error messages
IT_ERR_MSG TYPE STANDARD TABLE OF T_ERR_MSG WITH HEADER LINE.


*----------------------------------------------------------------------*
* Selection Screen. *
*----------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.

PARAMETERS : P_FLNAME(15) OBLIGATORY.

SELECTION-SCREEN END OF BLOCK B1.

SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002.

SELECTION-SCREEN BEGIN OF LINE.

PARAMETERS : R_LIST RADIOBUTTON GROUP GRP1.
SELECTION-SCREEN COMMENT 5(20) TEXT-003.

PARAMETERS : R_SESS RADIOBUTTON GROUP GRP1.
SELECTION-SCREEN COMMENT 30(20) TEXT-004.

SELECTION-SCREEN END OF LINE.

SELECTION-SCREEN END OF BLOCK B2.



*----------------------------------------------------------------------*
* Event:Initialization *
*----------------------------------------------------------------------*
INITIALIZATION.

*----------------------------------------------------------------------*
* AT Selection Screen. *
*----------------------------------------------------------------------*
AT SELECTION-SCREEN.

*----------------------------------------------------------------------*
* Event: Start-of-Selection *
*----------------------------------------------------------------------*
START-OF-SELECTION.

V_FNAME = P_FLNAME.
PERFORM GET_DATA.
PERFORM GET_BANKDATA.
PERFORM GENERATE_DATASET.

*----------------------------------------------------------------------*
* Event: End-of-Selection *
*----------------------------------------------------------------------*
END-OF-SELECTION.

IF FG_DATA_EXIST = ' '.
MESSAGE I010 WITH TEXT-009.
EXIT.
ENDIF.

PERFORM GENERATE_BDCDATA.
PERFORM DISPLAY_ERR_RECS.

*----------------------------------------------------------------------*
* Event: top-of-page
*----------------------------------------------------------------------*
TOP-OF-PAGE.


*//////////////////////////////////////////////////////////////////////*
*
* FORM DEFINITIONS *
*
*//////////////////////////////////////////////////////////////////////
*&---------------------------------------------------------------------*
*& Form get_data
*&---------------------------------------------------------------------*
* Subroutine to get the data from mard
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM GET_DATA.

CALL FUNCTION 'UPLOAD'
EXPORTING
* CODEPAGE = ' '
FILENAME = 'C:\XD01.TXT'
FILETYPE = 'DAT'
* ITEM = ' '
* FILEMASK_MASK = ' '
* FILEMASK_TEXT = ' '
* FILETYPE_NO_CHANGE = ' '
* FILEMASK_ALL = ' '
* FILETYPE_NO_SHOW = ' '
* LINE_EXIT = ' '
* USER_FORM = ' '
* USER_PROG = ' '
* SILENT = 'S'
* IMPORTING
* FILESIZE =
* CANCEL =
* ACT_FILENAME =
* ACT_FILETYPE =
TABLES
DATA_TAB = IT_KNA1
* EXCEPTIONS
* CONVERSION_ERROR = 1
* INVALID_TABLE_WIDTH = 2
* INVALID_TYPE = 3
* NO_BATCH = 4
* UNKNOWN_ERROR = 5
* GUI_REFUSE_FILETRANSFER = 6
* OTHERS = 7
.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.


IF IT_KNA1[] IS INITIAL.
FG_DATA_EXIST = ' '.
ENDIF.

ENDFORM. " get_data
*&---------------------------------------------------------------------*
*& Form GENERATE_DATASET
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM GENERATE_DATASET.

MESSAGE I010 WITH 'OPENING FILE IN APPLICATION SERVER'.

**--Creating a data set in application server

OPEN DATASET V_FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.


**---Transfering data from internal table to dataset

MESSAGE I010 WITH 'TRANSFERING DATA FROM INETERAL TABLE TO THE FILE'.

LOOP AT IT_KNA1.

TRANSFER IT_KNA1 TO V_FNAME.

ENDLOOP.

**--Closing the dataset

MESSAGE I010 WITH 'CLOSING THE FILE'.
CLOSE DATASET V_FNAME.

ENDFORM. " GENERATE_DATASET

*&---------------------------------------------------------------------*
*& Form BDC_DYNPRO
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_0467 text
* -->P_0468 text
*----------------------------------------------------------------------*
FORM BDC_DYNPRO USING PROGRAM DYNPRO.

CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = DYNPRO.
IT_BDCDATA-DYNBEGIN = 'X'.
APPEND IT_BDCDATA.

ENDFORM.

*&---------------------------------------------------------------------*
*& Form BDC_FIELD
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_0472 text
* -->P_0473 text
*----------------------------------------------------------------------*
FORM BDC_FIELD USING FNAM FVAL.

IF NOT FVAL IS INITIAL.

CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.

ENDIF.

ENDFORM.
*&---------------------------------------------------------------------*
*& Form GENERATE_BDCDATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM GENERATE_BDCDATA.


REFRESH IT_KNA1.
* Opening dataset for reading

OPEN DATASET V_FNAME FOR INPUT IN TEXT MODE ENCODING DEFAULT.

**** Reading the file from application server
DO.

CLEAR: IT_KNA1,IT_BDCDATA.
REFRESH IT_BDCDATA.

READ DATASET V_FNAME INTO IT_KNA1.

IF SY-SUBRC <> 0.

EXIT.

ELSE.
* Populate BDC Data for Initial Screen
PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0100',
BDC_FIELD USING 'BDC_CURSOR' 'RF02D-KUNNR',
BDC_FIELD USING 'BDC_OKCODE' '/00',
BDC_FIELD USING 'RF02D-KUNNR' IT_KNA1-KUNNR,
BDC_FIELD USING 'RF02D-KTOKD' IT_KNA1-KTOKD.

* Populate BDC Data for Second Screen
PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0110',
BDC_FIELD USING 'BDC_CURSOR' 'KNA1-NAME1',
BDC_FIELD USING 'BDC_OKCODE' '/00',
BDC_FIELD USING 'KNA1-NAME1' IT_KNA1-NAME1,
BDC_FIELD USING 'KNA1-SORTL' IT_KNA1-SORTL,
BDC_FIELD USING 'KNA1-ORT01' IT_KNA1-ORT01,
BDC_FIELD USING 'KNA1-PSTLZ' IT_KNA1-PSTLZ,
BDC_FIELD USING 'KNA1-LAND1' IT_KNA1-LAND1,
BDC_FIELD USING 'KNA1-SPRAS' IT_KNA1-SPRAS.

* Populate BDC Data for Third Screen
PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0120',
BDC_FIELD USING 'BDC_CURSOR' 'KNA1-LZONE',
BDC_FIELD USING 'BDC_OKCODE' '/00',
BDC_FIELD USING 'KNA1-LZONE' IT_KNA1-LZONE.
* Populate BDC Data for Fourth Screen
PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0125',
BDC_FIELD USING 'BDC_CURSOR' 'KNA1-NIELS',
BDC_FIELD USING 'BDC_OKCODE' '/00'.

* Populate BDC Data for Table control for bank details.
V_TIDX = '01'.
LOOP AT IT_BANK.

BANKS V_TIDX.
BANKL V_TIDX.
BANKN V_TIDX.

PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0130',
BDC_FIELD USING 'BDC_CURSOR' V_BANKN,
BDC_FIELD USING 'BDC_OKCODE' '=ENTR',
BDC_FIELD USING V_BANKS IT_BANK-BANKS,
BDC_FIELD USING V_BANKL IT_BANK-BANKL,
BDC_FIELD USING V_BANKN IT_BANK-BANKN.

V_TIDX = V_TIDX + 1.

ENDLOOP.

PERFORM : BDC_DYNPRO USING 'SAPMF02D' '0130',
BDC_FIELD USING 'BDC_CURSOR' V_BANKS,
BDC_FIELD USING 'BDC_OKCODE' '=UPDA'.

CALL TRANSACTION C_XD01 USING IT_BDCDATA
MODE C_MODE
UPDATE C_UPDATE
MESSAGES INTO IT_MSG.

IF SY-SUBRC <> 0.
*--In case of error list display
IF R_LIST = C_X.

V_ERRREC = V_ERRREC + 1.
PERFORM FORMAT_MESSAGE.

IT_ERR_MSG-MESSAGE = V_MSG.
APPEND IT_ERR_MSG.

CLEAR : V_MSG,IT_ERR_MSG.

ENDIF.
*--In case of session log
IF R_SESS = C_X.
*-- In case of transaction fails.
IF FG_SESSION_OPEN = ' '.

FG_SESSION_OPEN = C_X.
PERFORM BDC_OPEN_GROUP.

ENDIF. " IF FG_SESSION_OPEN = ' '.
*-- Insert BDC Data..
PERFORM BDC_INSERT_DATA.

ENDIF. " IF R_SESS = C_X.

ENDIF. " IF SY-SUBRC <> 0.

ENDIF. " IF SY-SUBRC <> 0.


ENDDO.


* Closing the dataset

CLOSE DATASET V_FNAME.

*-- Close the session if opened
IF FG_SESSION_OPEN = C_X.
PERFORM BDC_CLOSE_GROUP.
CALL TRANSACTION 'SM35'.
ENDIF.

ENDFORM. " GENERATE_BDCDATA
*&---------------------------------------------------------------------*
*& Form BDC_OPEN_GROUP
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM BDC_OPEN_GROUP.


CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
* DEST = FILLER8
GROUP = C_SESS
* HOLDDATE = FILLER8
KEEP = C_X
USER = SY-UNAME
* RECORD = FILLER1
* IMPORTING
* QID =
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11
.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

ENDFORM. " BDC_OPEN_GROUP
*&---------------------------------------------------------------------*
*& Form BDC_INSERT_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM BDC_INSERT_DATA.


CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_XD01
* POST_LOCAL = NOVBLOCAL
* PRINTING = NOPRINT
TABLES
DYNPROTAB = IT_BDCDATA
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7
.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

ENDFORM. " BDC_INSERT_DATA
*&---------------------------------------------------------------------*
*& Form BDC_CLOSE_GROUP
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM BDC_CLOSE_GROUP.

CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 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.

ENDFORM. " BDC_CLOSE_GROUP
*&---------------------------------------------------------------------*
*& Form FORMAT_MESSAGE
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM FORMAT_MESSAGE.


CLEAR V_LINES.
DESCRIBE TABLE IT_MSG LINES V_LINES.

READ TABLE IT_MSG INDEX V_LINES.

CLEAR V_MSG.

CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = IT_MSG-MSGID
LANG = IT_MSG-MSGSPRA
NO = IT_MSG-MSGNR
V1 = IT_MSG-MSGV1
V2 = IT_MSG-MSGV2
V3 = IT_MSG-MSGV3
V4 = IT_MSG-MSGV4
IMPORTING
MSG = V_MSG
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2.

IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.



ENDFORM. " FORMAT_MESSAGE
*&---------------------------------------------------------------------*
*& Form DISPLAY_ERR_RECS
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM DISPLAY_ERR_RECS.

LOOP AT IT_ERR_MSG.

WRITE: / IT_ERR_MSG-MESSAGE.

ENDLOOP.

ENDFORM. " DISPLAY_ERR_RECS
*&---------------------------------------------------------------------*
*& Form GET_BANKDATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- br="br" p2="p2" text="text">*----------------------------------------------------------------------*
FORM GET_BANKDATA.

IT_BANK-BANKS = 'AD'.
IT_BANK-BANKL = '1000'.
IT_BANK-BANKN = 'S.B A/C'.
APPEND IT_BANK.

IT_BANK-BANKS = 'AD'.
IT_BANK-BANKL = 'CITY'.
IT_BANK-BANKN = 'CURR. A/C'.
APPEND IT_BANK.

IT_BANK-BANKS = 'AD'.
IT_BANK-BANKL = 'H001'.
IT_BANK-BANKN = 'S.B A/C'.
APPEND IT_BANK.

RELATED POSTS

BDC SESSION METHOD SAMPLE CODE

BDC PART 4
BDC PART 3
BDC PART 2
BDC PART 1

ABAP BDC TABLE CONTROL

BDC table control is an area on the screen in which you can display data in tabular form. You process it using a loop. Table controls are comparable to step loop tables. While a table control consists of a single definition row, step loop blocks may extend over more than one row. Table controls are more flexible than step loops, and are intended to replace them

When you need to handle a scenario like in sales order,it may contain more than one material,if you have more than one material We have to use table control,it will have number of columns and number of rows.

Table controls allow you to enter, display, and modify tabular data easily on the screen

Check this code,


PARAMETERS: file1 LIKE rlgrap-filename.

************************************************************************
*Internal Table Declarations
************************************************************************

DATA: BEGIN OF itab OCCURS 0,
matnr(18) TYPE c, "MaterialNumber
werks(4) TYPE c, "Plant
vdatu(10) TYPE c, "Valid From Date
bdatu(10) TYPE c, "Valid To Date
lifnr(10) TYPE c, "Vendor Number
ekorg(4) TYPE c, "Purchasing Organization
feskz TYPE c, "Fixed
autet TYPE c, "MRP Indicator
END OF itab.

DATA: bdcdata LIKE TABLE OF bdcdata WITH HEADER LINE.

************************************************************************
*VARIABLES Declarations
************************************************************************
DATA: wa1 LIKE LINE OF itab. "Workarea for ITAB
DATA: n TYPE i, "Check
count TYPE i.
DATA: cnt(2), "Counter
wa(15). "Workarea to hold concatenatedvalue
DATA v_msg(100).
DATA: flag.
DATA: file TYPE string.

************************************************************************
*Initialization event
************************************************************************

INITIALIZATION.

************************************************************************
*At-selection-screen event
************************************************************************

*To provide Input help for file name

AT SELECTION-SCREEN ON VALUE-REQUEST FOR file1.


CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = file1.

***********************************************************************
*START-OF-SELECTION EVENT
***********************************************************************

START-OF-SELECTION.

MOVE file1 TO file.


CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = file
filetype = 'ASC'
has_field_separator = 'X'
TABLES
data_tab = itab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.

*To populate BDCDATA and start data transfer

LOOP AT itab .

* To validate Plant range

IF itab-werks = '1000' OR itab-werks = '2000'
OR itab-werks = '1008'.

AT NEW werks.

CLEAR: n.
cnt = 1.

PERFORM bdc_dynpro USING 'SAPLMEOR' '0200'.
PERFORM bdc_field USING 'BDC_CURSOR'
'EORD-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'EORD-MATNR'
itab-matnr.
PERFORM bdc_field USING 'EORD-WERKS'
itab-werks.
PERFORM bdc_dynpro USING 'SAPLMEOR' '0205'.


CONCATENATE 'EORD-EKORG(' cnt ')' INTO wa.

PERFORM bdc_field USING 'BDC_CURSOR'
wa.

PERFORM bdc_field USING 'BDC_OKCODE'
'=BU'.
ENDAT.

IF n = 12.


READ TABLE bdcdata WITH KEY fval = '=BU'.
bdcdata-fval = '=NS'.
MODIFY bdcdata INDEX sy-tabix TRANSPORTING fval.


PERFORM bdc_dynpro USING 'SAPLMEOR' '0205'.
PERFORM bdc_field USING 'BDC_CURSOR'
'EORD-VDATU(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=BU'.

cnt = 2.
n = 2.
ENDIF.



CONCATENATE 'EORD-VDATU(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-vdatu.

CONCATENATE 'EORD-BDATU(' cnt ')' INTO wa.

PERFORM bdc_field USING wa
itab-bdatu.
CONCATENATE 'EORD-LIFNR(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-lifnr.
CONCATENATE 'EORD-EKORG(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-ekorg.
CONCATENATE 'RM06W-FESKZ(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-feskz.
CONCATENATE 'EORD-AUTET(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-autet.

IF n <> 12.
n = cnt.
ENDIF.
cnt = cnt + 1.


AT END OF werks.

CALL TRANSACTION 'ME01' USING bdcdata
UPDATE 'S'
MODE 'A'.


CLEAR:bdcdata,bdcdata[].


CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
id = sy-msgid
lang = 'EN'
no = sy-msgno
v1 = sy-msgv1
v2 = sy-msgv2
v3 = sy-msgv3
v4 = sy-msgv4
IMPORTING
msg = v_msg.

WRITE:/ v_msg.
CLEAR: bdcdata,bdcdata[],flag.


ENDAT.

ENDIF.
ENDLOOP.


*----------------------------------------------------------------------*
* Start new screen *
*----------------------------------------------------------------------*
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.

ENDFORM.

*----------------------------------------------------------------------*
* Insert field values
*----------------------------------------------------------------------*
FORM bdc_field USING fnam fval.
IF NOT fval IS INITIAL.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDIF.
CLEAR wa.
ENDFORM.


Sample code 2

THis is example to upload the Bank details of the Vendor which has the TC.

REPORT zprataptable2
NO STANDARD PAGE HEADING LINE-SIZE 255.
DATA : BEGIN OF itab OCCURS 0,
i1 TYPE i,
lifnr LIKE rf02k-lifnr,
bukrs LIKE rf02k-bukrs,
ekorg LIKE rf02k-ekorg,
ktokk LIKE rf02k-ktokk,
anred LIKE lfa1-anred,
name1 LIKE lfa1-name1,
sortl LIKE lfa1-sortl,
land1 LIKE lfa1-land1,
akont LIKE lfb1-akont,
fdgrv LIKE lfb1-fdgrv,
waers LIKE lfm1-waers,
END OF itab.

DATA : BEGIN OF jtab OCCURS 0,
j1 TYPE i,
banks LIKE lfbk-banks,
bankl LIKE lfbk-bankl,
bankn LIKE lfbk-bankn,
END OF jtab.

DATA : cnt(4) TYPE n.
DATA : fdt(20) TYPE c.

DATA : c TYPE i.



INCLUDE bdcrecx1.

START-OF-SELECTION.

CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = 'C:\first1.txt'
filetype = 'DAT'
TABLES
data_tab = itab.

CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = 'C:\second.txt'
filetype = 'DAT'
TABLES
data_tab = jtab.



LOOP AT itab.


PERFORM bdc_dynpro USING 'SAPMF02K' '0100'.
PERFORM bdc_field USING 'BDC_CURSOR'
'RF02K-KTOKK'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'RF02K-LIFNR'
itab-lifnr.
PERFORM bdc_field USING 'RF02K-BUKRS'
itab-bukrs.
PERFORM bdc_field USING 'RF02K-EKORG'
itab-ekorg.
PERFORM bdc_field USING 'RF02K-KTOKK'
itab-ktokk.
PERFORM bdc_dynpro USING 'SAPMF02K' '0110'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFA1-LAND1'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFA1-ANRED'
itab-anred.
PERFORM bdc_field USING 'LFA1-NAME1'
itab-name1.
PERFORM bdc_field USING 'LFA1-SORTL'
itab-sortl.
PERFORM bdc_field USING 'LFA1-LAND1'
itab-land1.
PERFORM bdc_dynpro USING 'SAPMF02K' '0120'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFA1-KUNNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKN(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
cnt = 0.
LOOP AT jtab WHERE j1 = itab-i1.
cnt = cnt + 1.
CONCATENATE 'LFBK-BANKS(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-banks.

CONCATENATE 'LFBK-BANKL(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-bankl.

CONCATENATE 'LFBK-BANKN(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-bankn.
IF cnt = 5.
cnt = 0.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKS(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=P+'.


PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKN(02)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
ENDIF.
ENDLOOP.


PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKS(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0210'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB1-FDGRV'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFB1-AKONT'
itab-akont.
PERFORM bdc_field USING 'LFB1-FDGRV'
itab-fdgrv.
PERFORM bdc_dynpro USING 'SAPMF02K' '0215'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB1-ZTERM'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0220'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB5-MAHNA'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0310'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFM1-WAERS'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFM1-WAERS'
itab-waers.
PERFORM bdc_dynpro USING 'SAPMF02K' '0320'.
PERFORM bdc_field USING 'BDC_CURSOR'
'RF02K-LIFNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM bdc_dynpro USING 'SAPLSPO1' '0300'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=YES'.
PERFORM bdc_transaction USING 'XK01'.
ENDLOOP.
PERFORM close_group.



Header file:


1 63190 0001 0001 0001 mr bal188 b in 31000 a1 inr
2 63191 0001 0001 0001 mr bal189 b in 31000 a1 inr

TC file:

1 in sb 11000
1 in sb 12000
1 in sb 13000
1 in sb 14000
1 in sb 15000
1 in sb 16000
1 in sb 17000
1 in sb 18000
1 in sb 19000
1 in sb 20000
1 in sb 21000
1 in sb 22000
2 in sb 21000
2 in sb 22000

RELATED POSTS

ABAP IDOC'S BASIC TOOLS 2

Creating an IDoc Segment WE31:

The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.We will define a structure to send a text from the text database.Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a single segment structure. The thus defined IDoc segment is then created as a data dictionary structure. You can view the created structure with SE11 and use it in an ABAP as any TABLES declaration.

To demonstrate the use of the IDoc segment editor we will set up an example, which allows you to send a single text from the text pool (tables STXH and STXL) as an IDoc. These are the texts that you can see with SO10 or edit from within many applications.

We will show the steps to define an IDoc segment YAXX_THEAD with the DDic structure of THEAD.



To facilitate our work, we will use the "copy-from-template-tool", which reads the definition of a DDIC structure and inserts the field and the matching definitions as rows in the IDoc editor. You could, of course, define the structure completely manually, but using the template makes it easier.

 The tool in release 4.0b lets you use both DDIC structures or another IDoc segmentdefinition as a template.


The thus created structure can be edited any time. When saving, it will create a data dictionary structure based on the definition in WE31. The DDIC structure will retain the same name. You can view the structure as a table definition with SE11 and use it in an ABAP the same way.

Defining the Message Type (EDMSG)

The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.Imagine the situation of sending a purchase order to a supplier. When the IDoc with the purchase order reaches the supplier, it will be interpreted as a sales order received from a customer, namely you.

Simultaneously you want to send the IDoc data to the supplier's warehouse to inform it that a purchase order has been issued and is on the way.Both IDoc receivers will receive the same IDoc format; however, the IDoc will be tagged with a different message type. While the IDoc to the supplier will be flagged as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc sent to the warehouse should be flagged differently, so that the warehouse can recognize the order as a mere informational copy and process it differently than a true purchase order.

The message type together with the IDoc type determine the processing function. The message types are stored in table EDMSG.Defining the message type can be done from the transaction WEDI

EDMSG: Defining the message type (1)

The entry is only a base entry which tells the system that the message type is allowed. Other transactions will use that table as a check table to validate the entry. IT is as shown .



EDMSG: Defining the message type (1):

The entry is only a base entry which tells the system that the message type is allowed. Other transactions will use that table as a check table to validate the entry.


RELATED POSTS

ABAP IDOC'S BASIC TOOLS

There are several common expressions and methods that you need to know, when dealing with IDoc.The message type defines the semantic context of an IDoc. The message type tells the processing routines, how the message has to be interpreted.The same IDoc data can be sent with different message types. E.g. The same IDoc structure which is used for a purchase order can also be used for transmitting a sales order. Imagine the situation that you receive a sales order from your clients and in addition you receive copies of sales orders sent by an subsidiary of your company.

An IDoc type defines the syntax of the IDoc data. It tells which segments are found in an Idoc and what fields the segments are made of.The processing code is a logical name that determines the processing routine. This points usually to a function module, but the processing routine can also be a
workflow or an event.The use of a logical processing code makes it easy to modify the processing routine for a series of partner profiles at once.

Every sender-receiver relationship needs a profile defined. This one determines

• the processing code
• the processing times and conditions
• and in the case of outbound IDocs
• the media port used to send the IDoc and
• the triggers used to send the IDoc

The IDoc partners are classified in logical groups. Up to release 4.5 there were the following standard partner types defined: LS, KU, LI.The logical system is meant to be a different computer and was primarily introduced for use with the ALE functionality. You would use a partner type of LS, when linking with a different computer system, e.g. a legacy or subsystem.The partner type customer is used in classical EDI transmission to designate a partner, that requires a service from your company or is in the role of a debtor with respect to your company, e.g. the payer, sold-to-party, ship-to-party.

The partner type supplier is used in classical EDI transmission to designate a partner, that delivers a service to your company. This is typically the supplier in a purchase order. In SD orders you also find LI type partners, e.g. the shipping agent.

Message Type – How to Know What the Data Means

Data exchanged by an IDoc via EDI is known as message. Messages of the same kind belong to the  same message type.The message type defines the semantic context of an IDoc. The message type tells
the receiver how the message has to be interpreted.The term message is commonly used in communication, be it EDI or telecommunication. Any stream of data sent to a receiver with well-defined information in itis known as a message. EDIFACT, ANSI/X.12, XML and others use message the same way.

Unfortunately, the term message is used in many contexts other than EDI as well. Even R/3 uses the word message for the internal communication between applications. While this is totally OK from the abstract point of view of data modelling, it may sometimes cause confusion if it is unclear whether we are referring to IDoc messages or internal messages.

The specification of the message type along with the sent IDoc package is especially important when the physical IDoc type (the data structure of the IDoc file) is used for different purposes.A classical ambiguity arises in communication with customs via EDI. They usually set up a universal file format for an arbitrary kind of declaration, e.g. Intrastat, Extrastat, Export declarations, monthly reports etc. Depending on the message type, only applicable fields are filled with valid data. The message type tells the receiver which fields are  of interest at all.


Partner Profiles – How to Know the Format of the Partner

Different partners may speak different languages. While the information remains the same, different receivers may require completely different file formats and communication protocols.This information is stored in a partner profile.In a partner profile you will specify the names of the partners which are allowed to exchange IDocs to your system. For each partner you have to list the message types that the partner may send.

For any such message type, the profile tells the IDoc type, which the partner expects for that kind of message.For outbound processing, the partner profile also sets the media to transport the data to its receiver, e.g.

• an operating system file
• automated FTP
• XML or EDIFACT transmission via a broker/converter
• internet
• direct remote function call

The means of transport depends on the receiving partner, the IDoc type and message type (context).Therefore, you may choose to send the same data as a file to your vendor and via FTP to your remote plant.Also you may decide to exchange purchase data with a vendor via FTP but send payment notes to the same vendor in a file.For inbound processing, the partner profile customizsng will also determine a processing code, which can handle the received data.

IDoc Type – The Structure of the IDoc File

The IDoc type is the name of the data structure used to describe the file format of a specific IDoc.An IDoc is a segmented data file. It has typically several segments. The segments are usually structured into fields; however, different segments use different fields.The Idoc type is defined with transaction WE30, the respective segments are defined with transaction WE31.

Processing Codes

The processing code is a pointer to an algorithm to process an IDoc. It is used to allow more flexibility in assigning the processing function to an IDoc message.The processing code is a logical name for the algorithm used to process the IDoc. The processing code points itself to a method or function, which is capable of processing the IDoc data.

A processing code can point to an SAP predefined or a self-written business object or function module as long as they comply with certain interface standards.The processing codes allow you to easily change the processing algorithm. Because the process code can be used for more than one partner profile, the algorithm can be easily changed for every concerned IDoc.The IDoc engine will call a function module or a business object which is expected to perform the application processing for the received IDoc data. The function module must provide exactly the interface parameters which are needed to call it from the IDoc engine.

In addition to the writing of the processing function modules, IDoc development requires the definition of the segment structures and a series of customising settings to control the flow of the  IDoc engine.

Segments define the structure of the records in an IDoc. They are defined with transaction WE31.Check first, whether the client you are working with already has a logical system name assigned.The logical system name is stored in table T000 as T000-LOGSYS. This is the table of installed clients.If there is no name defined, you need to create a logical system name . This means
simply adding a line to table TBDLS. You can edit the table directly or access the table from transaction SALE.

The recommended naming convention is

sysid + "CLNT" + client

If your system is DEV and client is 100, then the logical system name should be:
DEVCLNT100.

System PRO with client 123 would be PROCLNT123 etc.The logical system also needs to be defined as a target within the R/3 network. Those definitions are done with transaction SM59 and are usually part of the work of the R/3 basis team.

RELATED POSTS