Hence if issues creep up relating to performance, configuration, connection etc., along with the investigation from the JAVA end (using java administration tools like visual admin, config tool, telnet etc), it is also useful to check the backend R/3 servers for important leads that may result in faster resolution of the issue.

This guide provides main TCodes for the same and has been segregated into three parts and shows a brief overview about the main Tcode in each area.

Download: Abap T-Code Related to Java Administration

SAP has a very strong middleware tool when compared to other applications like Oracle where it is pretty easy for SAP CRM application to connect with and exchange data with other SAP Applications like SAP BW, SAP R/3 system etc. This connection and data transfer is established through middleware.

From an ERP application perspective this is an extremely important aspect the data exchange among the systems is kind of back-bone and the crux of very existence of the application. This data exchange can be of following types between other systems and CRM:

1. Initial data transfer which is also called as Initial Load in SAP terminology
2. Intermediate synchronization of data among the applications also called as Delta Load in SAP terminology
3. Synchronization

Just to throw some light on the kinds of data exchange mentioned above, it can be better understood if we look at the frequency of the data exchange. Initial load is primarily a one time activity wherein when the connectivity is established between the systems, the data is transferred from one system to another. This data can range from configuration data (like pricing conditions) to master data (like Business Partners and Products) to transactional data (like Sales Quotations, Contracts and Sales Orders).

Delta load is an activity of intermediate data transfer among the systems. This activity takes place more often than not to keep the data in various systems in sync and also take care of the changes to details of the data in various systems. It also takes care of newly created data in the system and distributes the same to other connected applications. Primarily this takes place in real-time and is primarily done automatically.

Synchronization activity is to take care of any out of sync data. This may be a cause of connectivity failure or might as well be an outcome of maintenance activity. This is primarily done manually as and when needed.

Download: SAP CRM Middleware Configuration

• Scope of check in the product availability check
• Check against forecast
• Rules-based ATP check (product substitution and location determination at component level)

This white paper ebook explains the process of Multilevel ATP and component substitution in MLATP.

Download: Multilevel ATP With Ruled-Based Component Subtitutions

In some cases where information needs to be “pushed” from SAP rather than “pulled”, it is necessary to configure the SAP system to send IDocs to the external system. The external system in this case needs to have a Listener, which is triggered when information is sent to it. The systems involved in this scenario are SAP ECC and SAP MII. In SAP MII 12.1, there have been some substantial changes in how the IDoc Listeners are configured. Instead of configuring the IDoc Listener in MII, there are 10 preconfigured IDoc Listeners which are available in MII. The specific connection parameters to the ERP system are applied in NetWeaver.

Download: How to Send IDocs from SAP to MII

Here some outline:

Extended Flexibility for Data Modeling and Complex Objects

Support for multi-object repositories

• Multiple business objects (=main tables) can reside in one and the same repository. E.g. supplier and product data can be stored in one repository
• Records of different main tables can reference each other (new field type “Lookup [Main]”). E.g. a supplier can be related to several products
• Main tables can share the same customizing/lookup tables. E.g. the main tables “customers” and “suppliers” can be connected to the table “countries” in order to ensure consistent information about the country of origin of both business partners

Support for nested structures

• New composite data type tuple allows modeling of nested structures. E.g. product capacity information depending on plant and location or multiple addresses of a business partner can hold multiple phone numbers

Inbound processing

• Redesign of XML Import (enhanced usability and performance)
• Support for parallel import processes for multiple repositories
• Improved responsiveness during concurrent read and write actions (Write lock optimization)

Outbound processing

• Syndication performance enhancements e.g. in regards to parallel syndication
• Functional enhancements such as
• Syndication of multilingual attribute values (i.e. value and region)

Download: Overview of SAP NetWeaver MDM 7.1

Download: procedures to integrate SAP BI queries into Crystal Reports

If your company is subject to regulations that are conditionally based on the contents of the goods you import or export this new feature can be leveraged to analyze BOMs for license determination and assign the right license to the BOM component in the customs document.

This guide explains the major steps of how to use this new feature.

Download: How to Use BOM Dependent Licence Determination in SAP Global Trade Services – GTS

You can configure to use The SSL based HTTPS protocol, in which the data exchange is encrypted and requiring a certificate. In this ebook, HTTPS connection configurations are explained.

Download: How To Configure SSL for SAP NetWeaver Mobile 7.1

Download: Abap Object Basic Tutorial