Configuring SAP for Inbound and Outbound Processing. Event creation must be implemented by you or by SAP. An event is created from specific application programs the event creator and then published systemwide. Any number of receivers can respond to the event with their own response mechanisms. An event is usually defined as a component of an object type. SAP pseudo events are not processed by the SAP Event manager, but are called from an ABAP program or Remote Function Call using the Destination parameter. Related Concepts and Terminology. The following topic lists and defines specific terminology related to SAP and SAP event handling. Client and Server Programs. RFC programs for non SAP systems can function as either the caller or the called program in an RFC communication. There are two types of RFC programs The RFC client is the instance that calls the RFC to run the function that is provided by an RFC server. The functions that can be called remotely are called RFC functions, and the functions provided by the RFC API are called RFC calls. SAP Gateway. The SAP Gateway is a secure application server. No connections are accepted unless they have been preregistered previously from the SAP presentation Client. A server connection presents itself to the Gateway and exposes a Program Identifier. If the Program Identifier is found in the list of registered Program IDs, the Gateway server then offers a connection to the server, which Accepts a connection. This Program. ID is then linked with an RFC Destination within SAP, which enables SAP Function Modules and ALE documents IDocs or BAPI IDocs to be routed to the destination. The RFC Destination functions as a tag to mask the Program ID to SAP users. HTTP compression is a capability that can be built into web servers and web clients to improve transfer speed and bandwidth utilization. HTTP data is compressed. An RFC server program can be registered with the SAP gateway and wait for incoming RFC call requests. An RFC server program registers itself under a Program ID at an SAP gateway and not for a specific SAP system. Complete list of SAP CA tcodes Transaction Codes. CATS CrossApplication Time tcode CATS, Time Sheet Maintain Times tcode CAT2, CATS ObjectRelated. All SAP transactions sorted by Transaction Code Below is some basic tips on the transaction codes. A transaction that ends in the number below usually has the. Register Rfc Program SaptaSAP BW datasource 2LIS17I3HDR Plant maintenance orders. One of the more common challenges related to the SAP NetWeaver BW Accelerator that SAP administrators face is a broken RFC connection between the blades of the BW. ERROR Transaction program not registered Hi, We are connecting our ECC QA system with PI system via registering transaction program. In SAPGUI, the destination must be defined with transaction SM5. T and Register Mode. Moreover, this entry must contain information on the SAP gateway at which the RFC server program is registered. Program IDs and Load Balancing. If the Gateway Server has a connection to a particular server instance and another server instance presents itself to the gateway, then the gateway offers the connection and then begins functioning in Load Balancing mode. Using a proprietary algorithm, the Gateway sends different messages to each server depending on demand and total processing time. This may cause unpredictable results when messages are validated by schema and application. When configuring multiple events in the Oracle Application Server using a single SAP program ID, SAP load balances the event data. For example, if multiple remote function calls or BAPIs use the same program ID for example, ORACLETDS and multiple SAP listeners are configured with this progam. ID, then SAP sends one request to one listener and the next to another listener, and so on. There is a load balancing algorithm present in the SAP Gateway Server. This mechanism is proprietary to SAP application development and might work by comparing total throughput of the connection, the number of times in wait state, and so on. This means one connection might receive nine messages and a second connection might receive one message. If five of the nine messages are rejected for schema validation and the one message on the other connection is rejected for schema validation, you might suspect that you are missing SAP event handling messages. Load balancing in server inbound to adapter from SAP situations is handled by connecting multiple instances of the adapter to the SAP system. The SAP system will then load balance the connections. You cannot tune this performance. Load balancing in client outbound from adapter to SAP situations is handled only by the SAP application design. If your system supports a Message Server, then you can load balance in client situations. If you have only one application server, you cannot load balance except by application server tuning, such as maximum number of connections permitted or time of day limits on connections. The SAP system default limit is 1. RFC communication or adapter users. Each user takes up more than 2 MB of memory on the application server of the SAP system, and more or less on the adapter depending on the workload. Connection Pooling. A connection pool is a set of client connections to a specific destination. The pool may automatically create new connections to the specified remote system or return an already existing connection. It also provides methods to return a connection back to the pool when it is no longer needed. A connection pool can check which connections are no longer in use and can be closed to save system resources. The time period after which the pool checks the connections as well as the time after which a connection will time out can be configured by the calling application. A pool is always bound to one user ID and password, meaning that all connections taken from this pool will also use these credentials. An SAP connection is always bound to an SAP user ID and an SAP Client number. If you log on with a pool size that is set to 1, no connection pool is created 1 userid 1 process thread. If you log on with a pool size that is greater than 1, a pool is created with a size of n, which is the number you specified. For more information about connection pooling, see the SAP JCO API documentation. Registering Your Program ID in SAPGUITo enable your SAP system to issue the following calls or interfaces to the SAP event adapter, you must register your program ID under an RFC destination. Remote Function Calls RFCBusiness Application Programming Interfaces BAPIIntermediate Documents IDocThe RFC destination is a symbolic name for example, ORACLETDS that is used to direct events to a target system, masking the program ID. The Program ID is configured in both SAPGUI and the event adapter. Registering Your Program IDTo register your program ID Launch the SAP GUI and log in to the SAP system. Select Tools, Administration, Network, and then RFC destination. Run the SM5. 9 transaction. The Display and maintain RFC destinations window is displayed. Description of the illustration iwaysaputcpipconnect. Select TCPIP connections and click Create. The RFC Destination window is displayed. Description of the illustration iwaysapurfcddestination. Provide the following information In the RFC destination field, enter a name, for example, ORACLETDS. The value you enter in this field is case sensitive. In the Connection type field, enter T for destination type TCPIP. In the Description field, enter a brief description. Click Save from the tool bar or select Save from the Destination menu. The RFC Destination ORACLETDS window is displayed. Description of the illustration iwaysapuiwaydest. Perform the following steps For the Activation Type, click Registration. In the Program field, enter ORACLETDS. Click Save from the tool bar or select Save from the Destination menu. Ensure your event adapter is running. Verify that the SAP system and Oracle. AS Adapter for SAP are communicating. Click Test. Connection. Testing the SAP Event Adapter. In the SAP Server, the SE3. RFC Remote Function Call or a BAPI Business Application Programming Interface to any RFC destination. For more information on RFC destination, see Registering Your Program ID in SAPGUI.