Skip to Content
avatar image
Former Member

Change Status/Message from BE to SRM

Hello,

I have the following situation: A SC is transfered to the BE. For some special products an additional item (limit item) is added in the BE to the PO. This results in the following situation:

SRM BE

1SC 1PO

- P1 - P1

- P2 (limit item, cat=B)

Currently the status 'Fehler im Ablauf' is set obviously of this additional line item in BE.

My question: Is it possible to change the messages/status (CLEAN_REQREQ_UP, BBP_GET_STATUS_2) which is set while a SC is transfered from SRM to BE in this special situation? Is there a BADI in place which can be used?

Kind regards,

Thomas

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Jan 04, 2012 at 11:50 AM

    Hi Thomas,

    Why can the limt item not be added in SRM and flow to ERP in this manner?

    Regards,

    Jason

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello,

      in SRM7.0 this seems to be a standard behaviour although you can add items to the follow-on document via BADI.

      The relevant coding can be found here:

      Class: CL_BBP_BS_SPOOL_SC_CRT_CLASSIC

      Method: UPDATE_BE_FIELDS

      IF lv_srm_items NE lv_be_items. " The backend document exists but does not match SC! Should never happen!

      IF 1 = 0. MESSAGE e178(bbp_pu). ENDIF. " error in backend system, inform sysadmin

      ls_message-msgty = 'E'.

      ls_message-msgid = 'BBP_PU'.

      ls_message-msgno = '178'.

      MESSAGE ID ls_message-msgid TYPE ls_message-msgty NUMBER ls_message-msgno INTO ls_message-message.

      APPEND ls_message TO lt_messages.

      CREATE OBJECT lx_sc_transfer.

      lx_sc_transfer->put_bbp_messages( EXPORTING it_message = lt_messages ).

      RAISE EXCEPTION lx_sc_transfer.

      ENDIF.

      Kind regards,

      Thomas