Procurement & Material Management System (MATS) is a custom solution based on J2EE framework implemented for a leading automotive  manufacturing company for at all its plants to
improve the efficiency of its purchasing and material management processes. A rich GUI combined with easy to use functionalities are provided for its users from Production, Warehouse, Accounting and Purchasing departments.

MATS system supports Warehouse with functionality grouped under modules such as Forecast, Procurement, Goods Receipt, Goods Issue, Invoice Verification, Physical Count and Master Data and for Purchasing it supports with Sourcing module and for Accounting/Cost control department, it supports with consolidated Reports on all the transactions. The accounting department creates annual budgets by cost center in SAP and wants to track & control expenses in a real-time manner. As a result, customer wanted a real-time interface between MATS and SAP to support below key business requirements leading to an efficient control of expenses

• Support real-time budget control : Provide a real-time budget control functionality from MATS application with the budget information residing in SAP and budget being shared by multiple systems. Support real-time budget control activities such as Check budget, Reserve budget, Release budget reservation, Update budget and Consume budget.
• Support real-time accounting postings : Provide ability for MATS to do General Ledger(GL) or Accounts Payable(AP) posting on specific expense account codes for all transactions in MATS such as Goods Receipt (GR), Goods Issue (GI), Invoice Confirmation (INV), Credit Note (CN), Debit Note (DN), Retroactive CN(RCN), Retroactive DN(RDN), Cancel Operation for all above objects, Physical stock adjustment
• Support Physical count reconciliation: Provide volume update of records from MATS to SAP for materials that have difference in stock count during annual cycle count process

This whitepaper provides you with the solution for the above requirement. Download the whitepaper here (652).

This study focuses on how RosettaNet can be used to integrate non-SAP partner and an SAP partner. Background information of SAP and RosettaNet is given, possible and mapping is discussed. A prototype of implementation is also constructed, to see how the implementation can be put in practive. It appears that the basis concept of implementation is correct, even if it lacks many qualities commonly associated with the integration of enterprise systems.

The message types of these two types of standards are well documented and understandable. There were no significant differences, at least in the case of purchase order. However, an IDoc lots of internal data that the PIP can not provide for which SAP must generate according to some of the mapping tables when receiving and IDOC transformed from PIP.

Understand about SAP R/3 IDocs and RosettaNet PIPs, Web Services and IBM websphere and Mapping between the message formats.  Read more about this study Here (407).

Internet Transaction Server (ITS) is the transaction processing system that connects the web HTTP server and the standard R/3 system. ITS is available since SAP release 3.1G. All the Internet Application Components (IAC) of SAP will be transacted through ITS.

Using ITS & IAC the standard R/3 transactions can be performed through the World Wide Web. Some of the business components that are pre-web-enabled by SAP are, • HR Employee Self-Service (ESS)

• Components in SAP Retail Store
• SAP B2B Procurement

It is also possible to web-enable the custom transactions and other standard transactions using ITS, using the following tools and components supplied by SAP.

• SAP@Web Studio
• SAP GUI for HTML
• Web RFC
• Web Reporting
• Web Transactions

These components support generation of dynamic HTMLs, HTMLBusiness, JavaScript, Common Gateway Interface (CGI), Microsoft Information Server API (ISAPI), Netscape Server API (NSAPI)
and can interact with Java, C++ or VB programs.

There are a number of connectors supplied by SAP for integrating R/3 with different applications and technologies.

• SAP Business Connectors
• SAP Java Connectors
• SAP .NET Connectors
• SAP DCOM Connectors

The Java, .NET and DCOM connectors are took kits, which are functionally similar, to enable interoperability between SAP and other software. These toolkits typically come with middleware APIs to support RFC (synchronous, transactional & queued), BAPIs, and IDocs. These connectors are ideal for custom interface development for the in-house integration needs. SAP Business Connectors is a step above the technology connectors. Business Connectors allow integration of local and application over the net, with open standards (like XML etc…). The BAPI and IDoc interfaces are made available to partners over the net using secured XML based services. In addition, Business Connectors enable to expose additional Web Services over the internet for the business partners to get information deeply buried into your ERP system.

This guide describes how to analyze the Microsoft Exchange integration with SAP Enterprise Portal 6.0

Checklist:

Check MSX-A component setup

• Check MS Outlook setup
  Is the correct version of Microsoft Outlook installed on the IIS server?
  Is Microsoft Outlook configured to access Microsoft Exchange Server?
  Do I have the correct version of Microsoft Exchange Server?

• Check IIS setup
  Can ASP applications run on the IIS?
  Is the MS Exchange server in the same windows logon domain as the IIS server?
  Do users have sufficient rights to execute the MSX-Acomponent?
  Have the MSX-A components been registered?
  Does the setup work with the test application?
  Is Kerberos SSO enabled?
  Do OWA iViews work with SSO?
  Is the MSX-A component configured on the backend server hosting the Kerberos components?

Check portal setup

• Is the user set up correctly?
• Is the IIS configuration mapped correctly?
• Can the IIS server be reached using the host name from the portal?
• Is the integration functioning?

Download the complete manual from Rapidshare or Mediafire.