topic Re: SAP-BDC in Application Development and Automation Discussions

SAP-BDC

Former Member — Mon, 22 May 2006 01:56:53 GMT

In Session or Calltransaction method while processing data some errors occures how can we rectify the errors?

What kind of errors is possible to come while processing data?

Re: SAP-BDC

RichHeilman — Mon, 22 May 2006 02:08:12 GMT

It all depends on what transaction you are dealing with. Any errors that can happen in the transaction itself can and will happen during BDC. In session, you must fixed the "defect" and re-run the session.

Regards,

Rich Heilman

Re: SAP-BDC

Former Member — Mon, 22 May 2006 02:53:14 GMT

Hi Srinivas,

If the error is in your BDC program, then you have to change the error and run the session again.

IF the error is in the input data, then you can process the session in SM35 in error mode/foreground mode, changing the data which causes the error.

Thanks,

Susmitha

Note : Dont forget to award points for helpful answers.

Re: SAP-BDC

Former Member — Mon, 22 May 2006 03:27:56 GMT

Hi,

If you are talking about session, please process your session in SM35 in mode process/foreground. If you are dealing with call transaction, use mode 'A'.

Both the above will bring you screen to screen and you can actually see your error and from there, you will know how to rectify.

Any kind of errors will be possible- wrong screen sequence, missing screens, data currently being processed by other users.. etc

Rgds,

Re: SAP-BDC

Former Member — Mon, 22 May 2006 03:31:12 GMT

GOOD

BDC SESSION

Messages

If you execute the MESSAGE statement, the following system fields are set. If you execute the MESSAGE … RAISING statement in function modules and methods, these fields are also set in the calling program, if it handles the exception.

SY-MSGID

SY-MSGID contains the message ID.

SY-MSGNO

SY-MSGNO contains the message number.

SY-MSGTY

SY-MSGTY contains the message type.

SY-MSGV1,…,SY-MSGV4

SY-MSGV1 to SY-MSGV4 contain the field contents that are used for the message’s placeholders.

Special Actions that Fill Message Fields

· If you request database locks using the ENQUEUE function module, the field SY-MSGV1 contains the name of the user who holds the lock, in the case of the FOREIGN_LOCK exception.

· IN the case of CALL TRANSACTION or CALL DIALOG with the USING addition, a message displayed during the called screen sequence is returned in the fields SY-MSGID, SY-MSGTY, SY-MSGNO, SY-MSGV1, ... , SY-MSGV4.

· During Remote Function Call (RFC), error messages are transferred from the remote system to the calling system and SY-MSGID, SY-MSGTY, SY-MSGNO,SY-MSGV1, SY-MSGV2, SY-MSGV3, SY-MSGV4 are set. If short dumps or type X messages occur, the system also sets the fields.

CALL TRANSACTION

One solution for capturing error is to decalre a table

data : ERRORTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER

LINE.

and Call Transaction should be like this

call transaction 'MM01' using bdcdata mode 'A'

messages into ERRORTAB.

IF you have error it will stored in errortab in msgv1,

msgv2.. fields. Hope this will help.

GO THROUGH THIS LINK

http://www.sappro.com/downloads/Settings&SystemAreas.pdf

http://www.planetsap.com/thesap_abap_keywords.htm

THANKS

MRUTYUN

Re: SAP-BDC

Former Member — Mon, 22 May 2006 04:33:32 GMT

Hai Srinivas

Go through the following Code

report Z_SRINU_CALLTRANS_VENDOR_01

no standard page heading line-size 255.

Generated data section with specific formatting - DO NOT CHANGE ***

data: begin of it_lfa1 occurs 0,

KTOKK like lfa1-ktokk,

NAME1 like lfa1-name1,

SORTL like lfa1-sortl,

LAND1 like lfa1-land1,

end of it_lfa1.

End generated data section ***

data : it_bdc like bdcdata occurs 0 with header line.

*DATA: IT_MESSAGES TYPE TABLE OF BDCMSGCOLL WITH HEADER LINE.

*DATA: LV_MESSAGE(255).

data : it_messages like bdcmsgcoll occurs 0 with header line.

data : V_message(255).

data : V_flag.

data : V_datum1 type sy-datum.

data : begin of it_mesg occurs 0,

message(100),

end of it_mesg.

*V_datum1 = sy-datum-1.

parameters : P_Sess like APQI-GROUPID.

start-of-selection.

perform Get_data.

*perform open_group.

loop at it_lfa1.

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-KTOKK'

it_lfa1-KTOKK.

perform bdc_dynpro using 'SAPMF02K' '0110'.

perform bdc_field using 'BDC_CURSOR'

'LFA1-LAND1'.

perform bdc_field using 'BDC_OKCODE'

'=UPDA'.

perform bdc_field using 'LFA1-NAME1'

it_lfa1-name1.

perform bdc_field using 'LFA1-SORTL'

it_lfa1-sortl.

perform bdc_field using 'LFA1-LAND1'

it_lfa1-land1.

call transaction 'XK01' using it_bdc

mode 'N'

update 'S'

messages into it_messages.

if sy-subrc <> 0.

if V_flag <> 'X'.

perform open_group.

V_flag = 'X'.

endif.

perform bdc_transaction. "using 'XK01'.

endif.

perform format_messages.

refresh : it_bdc,it_messages.

endloop.

if V_flag = 'X'.

perform close_group.

endif.

&----

*& Form Get_data

&----

text

----

--> p1 text
<-- p2 text

----

FORM Get_data .

CALL FUNCTION 'UPLOAD'

EXPORTING

FILENAME = 'C:\srinu_vendor.txt'

FILETYPE = 'DAT'

TABLES

DATA_TAB = it_lfa1

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.

ENDFORM. " Get_data

&----

*& Form bdc_dynpro

&----

text

----

-->P_0061 text
-->P_0062 text

----

FORM BDC_DYNPRO USING PROGRAM DYNPRO.

CLEAR it_BDC.

it_BDC-PROGRAM = PROGRAM.

it_BDC-DYNPRO = DYNPRO.

it_BDC-DYNBEGIN = 'X'.

APPEND it_BDC.

ENDFORM.

----

Insert field *

----

FORM BDC_FIELD USING FNAM FVAL.

CLEAR it_BDC.

it_BDC-FNAM = FNAM.

it_BDC-FVAL = FVAL.

APPEND it_BDC.

ENDFORM.

&----

*& Form format_messages

&----

text

----

--> p1 text
<-- p2 text

----

FORM format_messages .

loop at it_messages.

CALL FUNCTION 'FORMAT_MESSAGE'

EXPORTING

ID = it_messages-MSGID

LANG = 'EN'

NO = it_messages-MSGNR

V1 = it_messages-MSGV1

V2 = it_messages-MSGV2

V3 = it_messages-MSGV3

V4 = it_messages-MSGV4

IMPORTING

MSG = V_message

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.

write : / V_message.

clear : V_message.

endloop.

ENDFORM. " format_messages

&----

*& Form open_group

&----

text

----

--> p1 text
<-- p2 text

----

FORM open_group .

CALL FUNCTION 'BDC_OPEN_GROUP'

EXPORTING

CLIENT = SY-MANDT

GROUP = P_Sess

HOLDDATE = V_datum1

KEEP = 'X'

USER = SY-UNAME

IF SY-SUBRC = 0.

write : / 'Session Creating wit Name : ',P_Sess.

ENDIF.

ENDFORM. " open_group

&----

*& Form close_group

&----

text

----

--> p1 text
<-- p2 text

----

FORM close_group .

CALL FUNCTION 'BDC_CLOSE_GROUP'.

ENDFORM. " close_group

&----

*& Form bdc_transaction

&----

text

----

-->P_0132 text

----

FORM bdc_transaction. "USING VALUE(P_0132).

CALL FUNCTION 'BDC_INSERT'

EXPORTING

TCODE = 'XK01'

POST_LOCAL = NOVBLOCAL
PRINTING = NOPRINT
SIMUBATCH = ' '
CTUPARAMS = ' '

TABLES

DYNPROTAB = it_bdc

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_transaction

Thanks & regards

Sreenivasulu P