SAP EDI Implementation Case Study

Project: SAP B2B / EDI Implementation
Industry: Chemical

Business Challenges:
Current B2B/EDI transactions were supported by Webmethods using RFC functionality.  The client has decided to replace Webmethods with Inovis middleware.  Inovis does’t have RFC functionality which limits its EDI mapping capabilities.  Much of the mapping functions that Webmethods handled will have to be handled the by SAP software.

High Level Business Solution:
Design and reconfigure all of the existing EDI transactions, including configuration of new Port and EDI partners.  Implement single EDI partner concept eliminating the need for EDI partner configuration for each new B2B customer or vendor.  Implement triggering concept on the application server at the unix level to process IDOC files to ensure near real time processing of data.  Design and develop architectural overview of the entire B2B process including inter-company transactions outlining multiple systems and processes.

Business/Technical Solution Details:
• Implemented new File type port.
• Reconfigured all existing message types to reflect new port.
• Created single EDI partner at transmission partner for all inbound B2B transactions.
• Created EDI partners for customers and vendors for outbound transactions.
• Designed and implemented SAP enhancements like user-exits and enhancement spots to accommodate mapping in SAP.
• Created ABAP-PI type port for inter-company transactions.
• Designed and developed processing module required for ABAP-PI port which converted outbound IDOC into corresponding inbound IDOC which routs to SAP for posting.
• Implemented message variants for inter-company transaction message types to differentiate B2B transactions from inter-company transactions.
• Created test scripts for each message type as part of QA unit and regression testing.
• Created separate testing strategy for Inovis middleware conducting end-to-end testing.