Skip to Content
author's profile photo Former Member
Former Member

BC with SRM 4.0 or 5.0

Hi,

I need a help because one of my clients would like to use BC with SRM 5.0 and I've found a note 856351 which says "As of SRM 5.0 (SRM SERVER 5.5), the Business Connector is no longer supported in connection with Supplier Relationship Management.

For SRM 4.0 (SRM SERVER 5.0), SAP does not recommend that you use the Business Connectors in connection with Supplier Relationship Management."

I wonder what does it mean that BC is no longer supported for SRM 5.0?

Does it mean that it is not working at all or that SAP is not supporting the solution which is using BC with SRM 5.0?

Regards,

Krzysiek

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2005 at 01:46 PM

    Hello,

    It means that SAP does not provide any mapping content anymore for BC (as BC package).

    But you can still use BC and develop all the mapping.

    You have different XML flows in SRM using BC:

    - Catalog: the one for OCI XML. Newest versions do not need BC or XI. The XML content is directly parsed in SRM.

    - Order collaboration: PO/POR/ASN/GR/IV.

    Take the PO output in XML. During the XML edition, SRM will determine the receiving system type.

    You have 3 different types:

    XISAPXML1 SAP XML Version 1.0 using XI

    XIEBPXML1 EBP proprietary XML Version 1.0 using XI

    BCEBPXML1 EBP proprietary XML Version 1.0 using Business Connector

    In SRM 5.0 if you are using XI for this vendor, XISAPXML1 is used, otherwise BCEBPXML1 is used.

    Then look at Function BBP_PO_SEND.

    In META_PO_SEND, there is a BADI call (BBP_EBPXML_OUT_BADI) to change system type if required.

    Depending on the system type, following functions will be called:

    BUS2201 Send BCEBPXML1 BBP_BAPI_PO_SEND

    BUS2201 Send XIEBPXML1 BBP_XI_PO_SEND

    BUS2201 Send XISAPXML1 BBP_SAPXML1_PO_SEND

    In case of BC, the old BAPI_POEC_XML_SEND is still finally used.

    Inbound POR are handled by BBP_BC_POACKNOWLEDGMENT_ADD

    (BAPI_POEC_ADD_CONFIRMATION).

    Inbound ASN by BBP_BC_SHIPMNTNOTIFICATION_ADD (BAPI_POEC_ADD_CONFIRMATION).

    Inbound GR by BBP_BC_CONF_CREATE (BAPI_CONFEC_CREATE).

    Inbound IV by BBP_BC_INVOICE_CREATE2

    (BAPI_INVOICEEC_CREATE).

    Rgds

    Christophe

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 27, 2005 at 01:14 PM

    Hi Krzysiek,

    I did explore this a little bit. I had an XML based OCI connection and could not get the oci to work. What they mean is (as far as i can understand) BC is not needed for the newer versions atleast for XML support.

    If you want i can send the doc i have on this. Let me know.

    Greetings

    John C

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.