How to find the IP address of a SAP system
Scenario – You wish to connect to your SAP system from a remote connection, you require your SAP system IP address and port.
Option 1 – There are a few methods to discover the IP address of a system the easiest being to simply use the menu path:
System–>Status–> then press (SHIFT+F5) –> You will see your current systems IP address under the System Information.
Option 2 – Alternativly you may use SM59 then select R/3 connections and double click on the system (RFC destination), then select the menu path:
System Information–>Target System –> You will see the target systems IP address under the “Network address”.
BD56 and WE20 ALE IDoc Segment Filtering
Problem with ALE IDoc segment filtering?
A common problem related to ALE IDoc segment filtering is a mis-alignment between the partner profile settings in WE20 and the segment filtering settings in BD56. Normally the settings in BD56 are maintained and transported where the values in WE20 are maintained manually in each system. If the settings in WE20 are not maintained with the same expected parameters in BD56 the segment filtering will not work. Specifically one needs to make special note that:
- BD56 – Message Type = WE20 – Message Type
- BD56 – Logical System Type = WE20 – Partner Type
- BD56 – Receiver = WE20 – Partner Number
- BD56 – Receiver Role = WE20 – Partner Role
Specifically if Receiver Role is blank then Partner role must be blank. Alternatively if a value exists such as LS (Logical System) the same value must be in both fields.
So which system is connected?
I work on a large landscape of 110 SAP systems (not clients). Every now and then someone asks if a specific system is connected to another, there is no way I can remember which systems are connected. Depending on what system they are referring to one may be able to execute a system specific transaction. However as a dependable alternative one may simply use SM59 and view the connected systems.
Here you can view the following connections:
- R/3 connections
- HTTP Connections to R/3 System
- Internal connections
- Logical destinations
- TCP/IP connections
- Connections via ABAP/4 driver
Tip – Depending on your settings (If the logon data is saved on the Logon/security tab) you may even be able to login to a connected system remotely from within SM59, simply select the R/3 connection and selecting “Remote logon” button.
ABAP Code Inspector
Do you need to easily check the performance of an ABAP program or do some analysis on its code?
You can use the transaction SCI.
This is a very powerful transaction code, which can do more than a performance check.
However here is an example of one of the more simpler uses:
From transaction SCI.
-Enter Person responsible
-Enter A name and version and select the “Create” Icon.
From the new screen
-Select the “Single” radio button
-From the drop down select “PROG Program”
-Enter the program/report you wish to analyse in the adjacent field.
-Under the check variant section enter “PERFORMANCE_CHECKLIST” (If this value does not work simply select the value from the F4 match-code selection list).
-Select Execute
From the next screen select the “Results” Icon (Shift + F6).
EDI – IDoc Segment Qualifiers Actions Sundry tips
Have you ever looked for documentation on an IDoc type, listing all segments, all fields including descriptions in the segment and all actions/qualifiers or possible selection values for a field?
You can get all this information by generating a report on a specific IDoc type by using the following function module in Se37: IDOCTYPE_READ_COMPLETE
Put the IDoc basic type for example “ORDERS05” in the field “PI_IDOCTYP” then select the Test Icon.
Alternatively Should you wish to see all qualifiers for a specific segment you can use the Function module “SEGMENT_READ_COMPLETE”.
Enter the segment, for example “E1EDK02” in the field “PI_SEGTYP” and select the Test Icon. In this example segment you will find there are 92 possible qualifiers.
Unrelated Sundry EDI OSS notes
A great OSS note regarding EDI with 27 questions and answers is “SAP Note 456127 – FAQ: Electronic Data Interchange (EDI)in purchasing” .
Another OSS note which gives the settings to use in WE20 when you use the Message Control tab – ”SAP Note 389713 – VE 561: Partner nnn is not an EDI partner”.
External Send – email Output and Transaction SCOT
Question: How does the external sending of email for output messages for example standard Order Confirmation occur with SAPconnect?
Answer: The format of the output must be adjusted to be used by the SMTP email server as used in SAPconnect (transaction SCOT). Here is a quick guideline for email outbound processing only:
1) You have to adjust the profile of the SAP Web Application Server if you want to use the SMTP function. The SAPconnect send job can only be scheduled for servers on which SMTP has been activated. For this reason, you must activate SMTP for all of the SAP system’s application servers. – Use transaction RZ10.
2) You maintain the SAPconnect settings for the SMTP node. For more information on SCOT see standard SAP help: Here
3) Next the original format of your standard output,for example order confirmation output could be in SCR (Standard SAPscript). In this case the SD messages are transferred to SAPconnect in SCR format (SAPscript) these are then converted to OTF format and may be converted to PDF format in accordance with the conversion rules in the IMG.
The configuration for the system is done in “SAP Customizing Implementation Guide–> SAPNetWeaver –>SAP Web Application Server -> Basis Services -> Communication Interfaces -> SAPconnect Client-Wide Settings -> General Settings -> Conversion Rules”.
4) Lastly the emails from the SAP spplication are stored in a queue. A background job needs to be created to collect the emails from the queue and process/send them. You can schedul ethe job in SAPconnect with SCOT as follows:
- From the user menu in SCOT select View–>Jobs
- Select Create
- Enter a job name and confirm it.
- Select the variant SAP&CONNECTALL Sending requests
- Schedule the job to run periodically for example every 10 mins.
For more information, refer to the online documentation for SAPconnect (component BC-SRV-COM).
Quick and Easy Tut – EDI – Pricing Condition Records
Introduction
So you know that SAP can send pricing condition records from your SAP system to another system using ALE/EDI. An investigation of transaction WE60 can show you the structure of the Basic Type “COND_A03″.
But what is the easiest method of sending the initial data load from SAP to another system for pricing condition records, or how do you use it? Read more 
How To: Generate a WSDL from a RFC Function Module
WSDL – Web Service Description language – (WSDL, pronounced ‘wiz-del’) is an XML-based language that provides a model for describing Web services. (A web service is typically an application programming interface (API) or Web API that is accessed via Hypertext Transfer Protocol (HTTP) and executed on a remote system, hosting the requested service.)
An example in layman’s terms is, you can have a RFC (Remote Function Call) function module which is used in SAP for example to create a sales document. You then have a company outside of your system which needs to send the input parameters to your system in order to create the sales document. The process to follow below will create the interface WSDL which the external company can use to place the data. Read more
Initial ALE Loads or IDoc Creation
Picture it, you would like to create an IDoc of a specific message type in your system with very little set-up. This is easily done using the following transaction codes:
Understanding the Application Server
ERP/ R/3 system architecture consists of amongst others:
- Presentation Server
- Application Server
- Database Server
- You can display a list of application servers that have registered themselves with the SAP message server by executing Transaction SM51, or by choosing Administration –> System Administration –>Monitor –>System Monitoring –>Servers.
The application server may have the following Message Types: Services provided by the application server This contains the configured SAP Work Process types (Dialog, update (Update and Upd2), Enqueue, Batch and Spool) as well as the following services:
SAP Tips – IDocs – Parallel Processing versus Packet Size
What is best to use for system performance?
It is not a cut and dry answer – both methods are valid and have their strengths and weaknesses. The following will help: Read more
SAP Tips – IDoc Commit and Packet Size
Program – RBDAPP01
Use - Inbound processing of IDocs
Tip - Packet Size – (Field- EDP13-PCKSIZ) Read more
SMQ1 – Outbound Queue Statuses
Outbound Queue
The following statuses may be displayed in transaction
SMQ1:
