Skip to main content

IDoc Whisperer | Bridging the Gap Between System A and B with Magical Data Exchanges [Part 1]

Once upon a time in a company named Ashish Enterprise, they had two SAP systems - System A and System B. The business processes in Ashish Enterprise required seamless integration between these systems to exchange data in real-time. To accomplish this, they decided to implement IDocs (Intermediate Documents).

In their SAP landscape, System A was responsible for managing the sales process, while System B handled the production and manufacturing activities. The company needed to ensure that sales orders created in System A were immediately transmitted to System B for timely production planning and execution.

To set up the IDoc integration between System A and System B, the following steps were taken:

  • Partner Profile Configuration:

            Partner profile configuration is a crucial step in setting up the IDoc integration between systems.             It involves defining the communication settings and parameters for each partner involved in the             IDoc exchange. In this case, we'll focus on configuring the partner profiles for System A and                System B.

            Here are the steps involved in partner profile configuration:

                a. Accessing Partner Profile Configuration:

                        In System A, go to transaction code WE20 (Partner Profile) to access the partner profile                         configuration.

                        In System B, also use transaction code WE20 to access the partner profile configuration.

                b. Creating a Partner Profile:

                        In System A:

                            Click on "Create" to create a new partner profile for System B.

                            Enter the partner number for System B. This number uniquely identifies System B in                             the partner profile configuration.

                            Set the partner type based on the role of System B (e.g., "LS" for Logical System).

                            Enter the logical system name for System B (e.g., "SAP02") in the "Partner Number"                             field.

                           Configure other relevant fields based on the specific requirements of the integration,                                such as message type, port settings, and process code.

                           Save the partner profile.

                        In System B:

                            Follow the same steps as above but create a partner profile for System A.

                            Specify the partner number for System A, logical system name (e.g., "SAP01"), and                                other relevant details.

                c. Configuring Communication Parameters:

                           In both System A and System B:

                           Access the partner profile created for the respective system.

                           Configure the communication parameters to establish the connection between the                                   systems.

                           Specify the communication method, such as RFC (Remote Function Call) or other                                   supported methods.

                           Provide the RFC destination, which represents the connection details of the target                                   system.

                           Set the host name and port number of the target system.

                           Define the communication protocol (e.g., TCP/IP, HTTP, or HTTPS).

                           Additional parameters such as encryption or compression settings may also be                                       configured based on the specific requirements.

               d. Defining Message Types and Settings:

                       In both System A and System B:

                       Access the partner profile for the respective system.

                       Define the message type(s) associated with the integration scenario. For example, in                               System A, specify the message type for sales orders, and in System B, specify the                                   message type for production orders.

                       Configure the specific settings for each message type, including the IDoc structure,                                segments, fields, and any additional parameters required for the integration.

                        Configuring IDOCS with screenshots

  • Communication Channels:

            The SAP Basis administrator defined the communication channels for IDoc exchange. They set             up communication methods, such as RFC (Remote Function Call), to establish the connection                between the two systems. They configured the communication parameters, including the RFC                destination, host name, port number, and other necessary details.

  • Message Type Definition:

            In both System A and System B, the SAP functional consultants defined the IDoc message types             required for the integration. They specified the structure and content of the IDocs, including the             segments and fields to be included. For example, they created a message type for sales orders in             System A and a corresponding message type in System B to receive the sales orders.

  • Mapping and Transformation:

            The functional consultants designed mappings and transformations between the source and                    target IDoc structures. They ensured that the data from System A's sales order IDoc was                        correctly mapped to System B's IDoc structure for production planning and execution. They                    configured field mappings, conversions, and validations to ensure data integrity and                                compatibility.

  • Testing and Validation:

            Once the setup was complete, the SAP Basis administrator and functional consultants performed             extensive testing and validation. They created test sales orders in System A and monitored the                IDoc flow to System B. They verified that the IDocs were transmitted successfully and that the             sales orders were accurately processed in System B.

The IDoc integration between System A and System B was crucial for Ashish Enterprise because it facilitated real-time data exchange and streamlined their sales and production processes. With IDocs, they could ensure that sales orders were promptly transmitted to the production department for immediate planning and execution, reducing lead times and enhancing customer satisfaction.

IDocs provided a reliable and standardized method for exchanging data between SAP systems, improving efficiency, data consistency, and process automation. By automating the data flow using IDocs, Ashish Enterprise could enhance their overall business operations, reduce manual effort, and achieve better integration between their systems.

And so, with the successful implementation of IDocs, Ashish Enterprise enjoyed seamless data exchange and efficient business processes between System A and System B, bringing harmony to their SAP landscape.

Liked the story ? Stay tuned to know all about IDOCs.


You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c