|
|
 |
|
|
|
|
|
| |
| Al Batha Group of companies |
| |
| Diversified |
| |
| Application Integration with SAP R/3 |
| |
Al Batha Group of companies is a multi-faceted corporation engaged
in a diverse range of activities including manufacturing, engineering, distribution, printing and
construction.
Al Batha has completed implementation of SAP R/3 across all 28 group companies and is now extending
the automating to cover its distribution channels and business partners.
As part of this effort, starting with six of the group companies engaged in distribution of Food
products, Meat, Juices, Detergents, Pharmaceuticals and other FMCG products Al Batha is implementing
a Route Accounting solution to provide visibility of the sales and distribution channels.
Full integration of all new systems is a prerequisite and Al Batha needed to pick the right integration
solution that would scale up to the diverse requirements of its 28 group companies. This choice would
not only effect the current deployment of the Route Accounting solution but also all future applications
and business partner integration.
Security, Scaling, ease of customization and flexibility to adapt to changing business process were the
considerations in selecting the right integration solution.
Al Batha needed a technology that was flexible, based on industry standards, and provided an
enterprise-class level of performance and reliability
|
| |
Al Batha chose Microsoft BizTalk 2002 as the platform for
integration of all future applications to the enterprise ERP System SAP.
The Microsoft BizTalk SAP Adaptor is used for this deployment and it provides a straightforward
yet powerful connectivity solution integrating applications with SAP. The SAP Adaptor reduced
implementation time by use of its features to generated the XML document speciation from the
SAP BOR this was especially significant since Al Batha uses Positional Text IDOCS as their
IDOC format and manually writing XML specifications for a positional IDOC is a formidable and
time consuming task.
For complex transformations and database interaction with the Route Accounting software custom
AIC's were written using Visual Studio .Net
17 outbound IDOC's and 10 inbound IDOC's were handled including,
SD: Sales, Sales returns, damaged returns, exchange returns, warehouse sales.
MM: Stock Transfer, Stock adjustment
FI: AR receipts, open items
Out-Bound Flow
Documents created in SAP are sent via a TRFC port, COM for ABAP is used to pick up the document
and deliver it to the MS BizTalk SAP adaptor. The documents are processed and delivered to the
Route Accounting application.
In-Bound Flow
Documents created by the Route Accounting software flow via the MS BizTalk SAP adaptor to the SAP
DCOM connector which then posts the document to SAP.
Complete loop of document reconciliation for both Out-bound and In-Bound documents is maintained by
use of acknowledgement IDOCS sent and the end of each successful out-bound posting and in-bound updates.
These acknowledgements allow for reconciliation at the document as well as transaction level.
|
| |
- Put in place an infrastructure can handle the RFC between SAP, BizTalk and Route Accounting and at
the same time can also be used to handle trading partner documents (XML) for B2B integration.
- The BizTalk three tier design allows for custom AIC's to be written to handle complex transformations
and is not just limited to GUI based XSLT mapping.
- · Browser-based system management tools that allow for easy management and monitoring a large number
of physically distributed sites.
- Using the MS BizTalk Adaptor for SAP allowed for reduced risk and short development time.
|
|
|
|
|
|
Consulting
Integration
