Express document "Update was terminated" received from author

[dubbaka]

Hello Team,

We are using 'BAPI_PO_CHANGE' to modify Delivery date, some times after 'BAPI_TRANSACTION_COMMIT' we are getting error “Express document "Update was terminated" received from author”. If we run same file second time it will get processed successfully.

Can anyone please let me know how to suppress this error.

CALL FUNCTION 'BAPI_PO_CHANGE'
    EXPORTING
      PURCHASEORDER                = T_EKET-EBELN
*     POHEADER                     = T_HEADER
*     POHEADERX                    = T_HEADERX
*     POADDRVENDOR                 =
*     TESTRUN                      =
*     MEMORY_UNCOMPLETE            =
*     MEMORY_COMPLETE              =
*     POEXPIMPHEADER               =
*     POEXPIMPHEADERX              =
*     VERSIONS                     =
*     NO_MESSAGING                 =
*     NO_MESSAGE_REQ               =
*     NO_AUTHORITY                 =
*     NO_PRICE_FROM_PO             =
*   IMPORTING
*     EXPHEADER                    =
*     EXPPOEXPIMPHEADER            =
   TABLES
     RETURN                       = RETURN
*     POITEM                       = T_POITEM
*     POITEMX                      = T_POITEMX
*     POADDRDELIVERY               = T_POADDRDELIVERY
     POSCHEDULE                   = T_POSCHEDULE
     POSCHEDULEX                  = T_POSCHEDULEX
*     POACCOUNT                    =
*     POACCOUNTPROFITSEGMENT       =
*     POACCOUNTX                   =
*     POCONDHEADER                 =
*     POCONDHEADERX                =
*     POCOND                       = T_POCOND
*     POCONDX                      =
*     POLIMITS                     =
*     POCONTRACTLIMITS             =
*     POSERVICES                   =
*     POSRVACCESSVALUES            =
*     POSERVICESTEXT               =
*     EXTENSIONIN                  =
*     EXTENSIONOUT                 = T_EXTENSIONOUT
*     POEXPIMPITEM                 =
*     POEXPIMPITEMX                =
*     POTEXTHEADER                 =
*     POTEXTITEM                   =
*     ALLVERSIONS                  =
*     POPARTNER                    = T_POPPARTNER
*     POCOMPONENTS                 =
*     POCOMPONENTSX                =
*     POSHIPPING                   =
*     POSHIPPINGX                  =
*     POSHIPPINGEXP                =
*     POHISTORY                    =
*     POHISTORY_TOTALS             =
*     POCONFIRMATION               =
            .
  READ TABLE RETURN  WITH KEY TYPE = 'E' .
  IF SY-SUBRC IS INITIAL.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
*     IMPORTING
*       RETURN        =
              .
    DELETE RETURN WHERE TYPE NE 'E'.
    LOOP AT RETURN.
      IT_ERROR-MESS = RETURN-MESSAGE.
      IT_ERROR-PO = T_EKET-EBELN.
      APPEND IT_ERROR.
    ENDLOOP.
  ELSE.
    READ TABLE RETURN  WITH KEY TYPE = 'A' .
    IF SY-SUBRC IS INITIAL.
      CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.             .
      DELETE RETURN WHERE TYPE NE 'A'.                                             
      LOOP AT RETURN.
        IT_ERROR-MESS = RETURN-MESSAGE.
        IT_ERROR-PO = T_EKET-EBELN.
        APPEND IT_ERROR.
      ENDLOOP.
    ELSE.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT          = 'X'.
 
ENDIF.

[Sandra_Rossi]

Check SAP notes. I find a few ones for "j_3avasso" "duplicate".

[DominikTylczyn]

Check the note 2564358 - Dump DBSQL_DUPLICATE_KEY_ERROR while sending confirmations for Purchase Order containing V...

[dubbaka]

Subject: Clarification on SAP Note 2564358 - Impact When VAS Is Not Maintained for AFS Materials

Thank you for your response DominikTylczyn,

I have reviewed SAP Note 2564358, and it appears to be relevant to our system. However, the note mentions as a prerequisite that VAS must be maintained on the purchasing side for AFS materials. In our case, some of our purchase orders do not include VAS. Could you please advise whether the implementation of this note will have any functional or technical impact when VAS is not maintained in certain purchase orders?

[DominikTylczyn]

I have no idea. You can address the issue to SAP support. However, I'm pretty sure they will point to this note first.