topic Re: Call transaction and commit work problem in Application Development and Automation Discussions

Call transaction and commit work problem

chaiphon — Thu, 09 Aug 2007 03:50:13 GMT

Hi all,

I have written one program to call FB01 to create a document.

here is the logic (pseudo code)

call transaction 'FB01' mode 'N' using it_bdc message it_message.

read it_message with msgtyp = 'E'.

if sy-subrc = 0.

rollback work.

else.

commit work.

endif.

I tested the file that I upload in development and quality system and it works fine. 1 record create 1 document. However, when it was transported to production, the program creates 2 documents for one record with the same time in document header and the same data in document items. It happened when the server has low memory and it happened only one day.

Could anyone tell me why it happen? because I use call transaction and commit work then LUW has commit twice with the same information?

Rewarded if it is helpful.

Thanks,

Phon

Re: Call transaction and commit work problem

varma_narayana — Thu, 09 Aug 2007 04:03:46 GMT

Hi..

This is your code.

call transaction 'FB01' mode 'N' using it_bdc message it_message.

read it_message with msgtyp = 'E'.

if sy-subrc = 0.

rollback work.

else.

commit work.

endif.

Here you are trying to Rollback the transaction if there is an error message.

This is not Required as the Trasaction will not be commited when there is an Error message. So there is no need of COMMIT or ROLLBACK here.

You can modify like this.

<b>call transaction 'FB01'

mode 'N'

using it_bdc

message it_message.

IF SY-SUBRC NE 0. "Transation unsuccessful

read it_message with msgtyp = 'E'.

if sy-subrc = 0.</b>write:/ it_message-msgty,

it_message-msgnr,

it_message-msgid,

it_message-msgv1,

it_message-msgv2.

endif.

ENDIF.

Hint: you can use the FM FORMAT_MESSAGE to Get the message based on the Message attributes.

<b>Reward if Helpful</b>

Re: Call transaction and commit work problem

Former Member — Thu, 09 Aug 2007 04:04:02 GMT

Hi Chaiphon,

I dont understand why you do a rollback when no data is committed. Just do a Commit work if the read statement returns sy-subrc NE 0.

Regards,

Yogesh

Re: Call transaction and commit work problem

former_member194669 — Thu, 09 Aug 2007 04:08:12 GMT

Hi,

Try to use


call transaction 'FB01' mode 'L' using it_bdc message it_message.

aRs

Re: Call transaction and commit work problem

chaiphon — Thu, 09 Aug 2007 04:19:47 GMT

I will take out commit work and rollback work but I still wonder wht the document was posted twice.

Re: Call transaction and commit work problem

former_member194669 — Thu, 09 Aug 2007 04:27:07 GMT

Hi,

Try to use

CALL FUNCTION 'BAPI_ACC_GL_POSTING_POST'

aRs

Re: Call transaction and commit work problem

chaiphon — Thu, 09 Aug 2007 04:34:22 GMT

Thanks for your suggestion. I want to know the reason because I code the same for many programa and SAP should not post the same document twice even thought I commit work after call transaction. is there any OSS note for this?

Re: Call transaction and commit work problem

former_member194669 — Thu, 09 Aug 2007 04:37:27 GMT

Hi,

As per you query you are saying it is wokring fine in QAS or other systems.

please check your it_bdc table , how records created in that? any duplicates?

I could not find OSS for this

aRs

Re: Call transaction and commit work problem

chaiphon — Thu, 09 Aug 2007 04:46:51 GMT

Thanks aRs, I search from SAP OSS as well but I cannot find any note that is helpful.

when the problem occurs I use the same file that user upload in production and upload it in Quality system. the record is about 1000+ records.

In production the message will be

document 1 has been created

document 3 has been created

document 5 has been created

document 7 has been created

document 8 has been created (Sometimes it created only one document).

document 10 has been created

document 13 has been created

...

However, if you go into the system and look for document 2, the data will be exactly the same as document 1 including the posting time(in the same second).

in quality system the message will be

document 1 has been created

document 2 has been created

document 3 has been created

document 4 has been created

....

now I have to create program to reverse all the duplicate documents and I will post to OSS tomorrow. Any other idea?

Re: Call transaction and commit work problem

former_member194669 — Thu, 09 Aug 2007 04:55:51 GMT

Hi,

After seeing these production records i got doubt to use wait command after commit work.

document 1 has been created

document 3 has been created

document 5 has been created

document 7 has been created

document 8 has been created (Sometimes it created only one document).

document 10 has been created

document 13 has been created

call transaction 'FB01' mode 'N' using it_bdc message it_message.

read it_message with msgtyp = 'E'.

if sy-subrc = 0.

rollback work.

else.

commit work.

<<<<<< use here any below mentioned wait command >>>>>

endif.

This 3 command can be used after an update. Usually after a COMMIT WORK.

Delay for 4 seconds.

1. WAIT UP TO 4 Seconds.

2. call function 'ENQUE_SLEEP'

exporting

seconds = 4.

3. CALL FUNCTION 'FMCT_WAIT_FOR_UPDATE'

EXPORTING

I_SEC = 4.

aRs