Child pages
  • SRM Purchase Order does not trigger message output condition in ECC
Skip to end of metadata
Go to start of metadata

Purpose

Explain how the system works and manage the Purchase Order Output in the Extended Classic Scenario.

Overview

In the section is explained how the system works, SRM and ECC R/3 system concern message output. A workaround also will be provided to BAPI with a example of code.

How system works

When using Extended Classic Scenario, EBP takes on the role as the purchasing system so that the EBP PO (local PO) is the 'controlling' PO The local PO is copied to the backend but only to the extent that this is necessary for the follow-on steps (confirmation and invoice).

No changes can be made to the PO in the backend.  Since EBP is considered the purchasing system in this case, backend release strategies cannot be used on these PO's. R/3 output determination does not work in the extended classic scenario.  The PO must be output using EBP.

Workaround

In order to change this behavior please follow the note 883693. Except for the changing in SRM, field no_messaging = ‘ ‘ should be transferred to BAPI_PO_CREATE1. Then output determination may happen in MM side.

 ************************

* The same change also have to be done at the Include for BAPI_PO_CREATE1

   Include: LBBP_BAPI_POF20..

   <<<<<<<Context Block>>>>>>>

   ....

   ELSE.

CALL FUNCTION 'FUNCTION_EXISTS'

  EXPORTING

    funcname           = 'BAPI_PO_CREATE1'

  EXCEPTIONS

    function_not_exist = 1

    OTHERS             = 2.

IF sy-subrc EQ 0.

<<<<<Insert Block>>>>>>>

no_messaging = ’ ‘.

**************************

Related Content

Related Documents

Related Notes

SAP Note883693 - ECS: PO output determination in R/3

SAP Note564826 - EBP: Customizing for the output of EBP documents