Supplier Relationship Management
Child pages
  • Error Backend checks could not be performed
Skip to end of metadata
Go to start of metadata

Purpose

This article is to help you to find the cause , or fix the documents with the error BBP_ADMIN 143 “Backend checks could not be performed. Inform system admin”  

Overview

When check a change version (Saved or Held Status) of the PO in Extended Classic Scenario. An error BBP_ADMIN 143 “Backend checks could not be performed. Inform system admin” is issued.

Cause:

The error is issued in the code below :

LBBP_PD_POF16

LBBP_PD_POF16
 
 FORM get_erpmessages USING name.
  DATA: lv_dest       TYPE rfcdisplay-rfcdest,
 ls_messages TYPE bbp_pds_messages.
  RECEIVE RESULTS FROM FUNCTION 'META_DPO_TRANSFER'
       TABLES
        e_messages        = eg_messages_erp
        control_record    = tg_control_record
        EXCEPTIONS
          system_failure = 1
          communication_failure =  2
           OTHERS = 3.

IF sy-subrc <> 0 AND
   eg_messages_erp[] IS INITIAL.
     CLEAR ls_messages.
      ls_messages-msgty = 'E'.
      ls_messages-msgid = 'BBP_ADMIN'.
      ls_messages-msgno = '143'. "Backend checks could not be performed. Inform system admin"
      APPEND ls_messages TO eg_messages_erp.

ENDIF.

 

Similar issues are because by error "RFC destination not found", or z-error found because of the BBP_ECS_PO_OUT_BADI or BBP_DOC_CHECK_BADI

 

Suggestion:

  • Compare the good and bad PO examples o versions to see if the RFC destination are identical /correct.
  • Check if there are Z-errors triggerred in the badi code the when checking the PO.
  • To clarify the root cause ,deactivate the badi BBP_ECS_PO_OUT_BADI or BBP_DOC_CHECK_BADI and retest.
  • Debug the code above.
  • If the issue does not occur in the newly created change version, please delete the incorrect change version (in saved or held status) and create a new one..