Article: Approach for system and business process integration with EDI business partner along with the case study.
Summary: Article includes the case study for EDI integration helping companies to create system-to-system integration and seamless business processes.
Author: Kamal Dial
Created on: 18st September 2014.
Author Bio: Kamal is a Consultant at Infosys and has over 4.5 years of professional work experience as business process and domain consultant. He is engineering graduate from PEC Chandigarh and post graduate in Management from Symbiosis Pune. He would like to thank his team member Amerjit Singh Mann for his valuable contribution and guidance towards this implementation.
Introduction- EDI integration for seamless business process continuity.
Integration between different business processes within an organization and across organizations is very important for a successful SAP implementation. Integration includes interfacing with legacy systems, communicating with third party partners, and integrating business processes across different systems. EDI (Electronic Data Interchange) technology is used for integration which uses IDOC (Intermediate Document) interface for exchanging data between different systems. EDI provides business process integration across companies by exchanging business documents such as sales order, order confirmation, delivery notes, shipment notices, invoices in electronic form using industry standard formats such as ANSI X12 and EDIFACT.
Purpose: Purpose of this integration with EDI partner is to optimize the business process and improve overall efficiency by eradicating manual intervention in the current process.
Case study: This case study is about major agribusiness client having high volume business with third party EDI partner which involves exchanging information related to order management, order acknowledgment, availability, delivery, invoice. It required a B2B system integration using standardized communication process considering high transactional volume and inefficiencies in the current process.
As Is Business process
This B2B scenario involves exchange of various documents and information between business partners at different point of time. Usual steps involved as followed:
Problem statement: This process has various drawbacks as below:
Approach adopted:
Usage of SAP Process Integration which is a platform to provide a single point of integration without changing existing complex network of legacy systems. It’s a powerful middleware by SAP to provide seamless end to end integration between SAP and non-SAP applications inside and outside the corporate boundary.
TO BE Business process:
Automate process of order creation: Orders will be initiated by EDI partner directly which would flow to SAP system (of agribusiness company) via IDOCS.
Interface: Net weaver Process Orchestration provides process integration and business rules management to help companies create system-to-system integration and seamless business processes.
Order responses: The order confirmation will happen in SAP depending upon the availability of material and order response will send the information to EDI partner via IDOC after validation
Delivery, invoice- Other information and documents related to order changes, delivery, invoice will be also exchanged via IDOCS.
Solution implemented:
1. Order creation/ change order: For order creation/change setup partner details in SAP using transaction WE20-
Technical changes involved in include - LVEDAF2U using enhancement spot in program SAPLVEDA to populate values in inbound IDOC using below mapping
By default, order is created with predefined delivery block since it needs to be validated by sales representative before confirming back to EDI business partner. New customized order reason can be used to distinguish a normal order from an EDI order.
2. Order response used for sending order confirmation, outbound parameters are maintained for EDI partner in transaction code WE20.
Prerequisites before configuration outbound parameters are:
Outbound parameter setup require below steps:
Technical changes: Requirement routine created to trigger the output only when delivery block is removed by sales representative executive after order validation. This routine is configured in output procedure itself
3. Delivery and invoice related information is being sent to EDI partner, for that outbound delivery/invoice based parameters needs to be configured in outbound parameters.
4.Notification updates: Customized report is created to provide below information to sales service officers
Process and system Integration after implementation:
Automation and seamless integration of business processes achieved. Orders are triggered by EDI partner directly which would flow to SAP system (of agribusiness client) through IDOCS via SAP PI interface. Once confirmed and checked by sales representative executive, order response is being sent back to EDI business partner automatically. Delivery and invoice related information is also being sent to partner automatically using outbound IDOCS.
Key challenges involved:
Conclusion:
Business Benefits:
Recommendations:
Abbreviations
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |