ESO/ERP Integration for Service Items?

Question

Hello experts,
In an ESO/ERP integrated system, can data from Service master in the ERP also be used to create RFQ's and Auctions in ESO?
Are there any special considerations for Service Items in such an integrated environment or would they be treated as regular material master items inside ESO?
Thanks & Regards,
Reshma

Answer 1

Hi Reshma
You are right, currently Item type D is nto supported for the ERP - ESO implementation for Document types RFQ, PR, PO that are created from the MSA or the RFx award from SAP ES.
However, you can still try to create the interface using some Z programs if you are pushed to the limit
What you can do?
1) Copy the Program for the BBP_ESI package model it to suit methods that call the Service line into the PR with Item category D - if you are successful here, you can check with the available list of API's on the ES side to check where in the XML extract you can actually incorporate the Service lines
2) Create a Proxy using the existing interface delivered for RFQ or PR from ECC to SAP ES RFx, in PI you can define the Service line logic so that the Payloads in PI can enable this transfer
3) The XML that is generated for this interface must be in Sync with what all RFx expects to process it as a service line, since there is no classification on the SAP ES side for addressing service lines separately.
4) You can also extend the XPRess functionality, since SAP ES views Service and print requests service lines, see if you can somehow integrate creation of an XPress draft from a Service PR in ECC, that too should be possible.
5) If all approaches fail, its better to integrate the SRM SoCo to push the Service lines into SAP ES RFx draft, below would be the approach.
u2022 Requirements from SRM, SAP R/3 or SAP ECC to SRM Sourcing cockpit
u2022 Create Bid invitation in SRM : Draft status
u2022 All SRM Bid Invitations to populate in a new screen developed, this screen will have all bid invitations lined up with a check box next to them, the Bid Invitation can be selected and pushed to SAP E-Sourcing
u2022 Proxy created to extract these fields from SRM and put it in XI outbound
u2022MAP / Cross MAP the data structures and pass the data
u2022 Push the Bid Invitation into SAP E-Sourcing as RFx Draft
u2022 Once the Bid Invitation is pushed into the SAP ESO application, it cannot be modified in SRM
Hope this gives you some fair approach