topic Re: Commit Problem with BAPI_SHIPMENT_CHANGE in Application Development and Automation Discussions

Commit Problem with BAPI_SHIPMENT_CHANGE

Former Member — Sat, 08 Sep 2007 10:38:35 GMT

Hi, all, thank you very much for your help.

I'm trying with BAPI_SHIPMENT_CHANGE, to change a shipment's Planning_Status. The Planning_Status is successfully updated. But, the LOCK of the shipment is NOT automatically released after the bapi commit.

Following is my detailed processing:

1. Write an ABAP LIST.

2. Press a button on the ABAP LIST's Application tool bar to call the bapi.

      AT USER-COMMAND.
         CASE sy-ucomm.
             WHEN 'CALL_BAPI'.
                  CALL FUNCTION 'BAPI_SHIPMENT_CHANGE'
                  ......
                  CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
                  ......
         ENDCASE.

3. After the bapi, stay at the current ABAP LIST wihout leaving.

Although I commit the bapi explicitly, and the planned update succeeds, the processing shipment stays being locked by me, unless I leave the ABAP LIST. And just when I leave the current screen, the lock is released.

I'm wondering, hasn't the BAPI_TRANSACTION_COMMIT committed successfully? Or, do I miss some steps?

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

chaouki_akir — Sat, 08 Sep 2007 13:54:17 GMT

Hello,

i have questions :

1/ what transaction is telling you that the processing shipment is locked by you ?

2/ In your program do you have any other function with name '%enqueue%' ?

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

Former Member — Sun, 09 Sep 2007 10:20:08 GMT

Hi, chaouki,

Thanks for your reply.

1). Transaction 'VT02N' tells me the shipment is being locked by myself, if I haven't leave the ABAP LIST.

2). There is NO extra 'ENQUE' processing in my program. Only BAPI_SHIPMENT_CHANGE and BAPI_TRANSACTION_COMMIT.

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

chaouki_akir — Sun, 09 Sep 2007 10:56:10 GMT

Hello,

1/Do you know what is the use of ENQUEUE/DEQUEUE function module ?

2/My point of vue is : the VT02N is trying to lock the Shipment entry (created by the BAPI) by calling an ENQUEUE function module. By debbuging the VT02N transaction, you can know the name of the ENQUEUE function module.

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

Former Member — Sun, 09 Sep 2007 12:54:38 GMT

I agree with you on the lock.

I'm wondering, why BAPI_TRANSACTION_COMMIT doesn't release the lock? Why Leaving_Screen releases the lock?

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

Former Member — Mon, 10 Sep 2007 02:44:21 GMT

Could anyone please help?

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

chaouki_akir — Mon, 10 Sep 2007 09:24:50 GMT

Hello,

your problem have already been encountered in this forum.

==> So, what you have done is correct. And to unlock the entry, you just have to call function 'DEQUEUE_ALL' (as explained in thread ).

Re: Commit Problem with BAPI_SHIPMENT_CHANGE

Former Member — Thu, 20 Sep 2007 01:53:47 GMT

chaouki, thank you very much.