Run Time

The design process target is used for run time connectivity. Verify that when you created the target, you specified the correct connection pool and IDoc parameters. For security reasons, target parameters can be overridden for a single session, but the base information can never be changed. You must delete and recreate the target for permanent changes.

Processing Guidelines

In a structural issue, information about the function or its parameters are faulty. This can be connectivity issues, release issues, authorizations or even incorrect document.

What can you do?

If you created your instance document in an external editor or program, verify the document against the iWay created schema for the document. If this is correct, verify the schema against the SAP ERP function parameters to make sure there were no errors or omissions in creating the schema. If all of these pass, note the error message, a reproduction scenario, traces of the error, and contact iWay support.

In a data issue, it is the values you are passing to the function that are incorrect.

What can you do?

Verify that you are sending the data for the release dependent version of the function or IDoc you wish to call. Make sure you are passing data that is valid for the SAP ERP parameter for the function. Check with the functional area specialist for the application to make sure you meet the application requirements.

Service processing occurs when the iWay Application Adapter for SAP ERP calls an SAP ERP system and waits for a response. In this scenario, you typically create a Target, browse to the meta data of the function or IDoc you with to work with, and create a schema and / or a web service. You then create a channel with all valid processing parameters. You then create an XML instance with the data you want to pass to the function, and submit it to the iWay adapter via any standard protocol. The response is delivered to the destination channel you configured when setting up the service.

Event processing occurs when an SAP ERP system calls the iWay Application Adapter for SAP ERP. Verify correct Event registration in SAP ERP using the correct event modality: change pointers / table update / BAPI Event, custom function.

The following event-driven scenarios are possible:

• An SAP ERP system calls the iWay Application Adapter for SAP ERP and the adapter is configured for asynchronos processing.
  • BAPI/RFC interface. In this case, SAP ERP passes the function name and any input parameters to the function. iWay creates an XML document with these parameters and the function name as the root node at the defined destination.
  • IDoc interface. The IDocs are created by the adapter at the defined destination.
• An SAP ERP system calls the iWay Application Adapter for SAP ERP and the adapter is configured for synchronous processing.
  • BAPI/RFC interface. You must define a service that will process the function parameters and return valid data in SAP ERP format back to SAP ERP. Any iWay service or a custom service you program can be used for this type.
  • IDoc interface. The IDoc interface is asynchronous by design. Any attempt to make synchronous events from IDocs can seriously impair the TRFC service on the SAP ERP application server. Do not attempt to define this scenario.

Examine your entire system landscape configuration. Determine if the number of documents received or sent matches processing times and memory requirements. SAP ERP maintains an online optimization help file for you to review all of these parameters. Increase hardware of total number of iWay adapter instances can optimize performance.

Here are some quick tips and suggestions:

• Use transaction ST06 to review the CPU, memory, swap, disk, and LAN response times.
• Use transaction ST02 to review the memory buffers. If any field has a indication (red color), investigate each field's dependant parameters and make the necessary adjustments.
• Determine whether the server has any external processes and/or programs running. In addition, review the shared pool buffers, redo log buffers, and how much is allocated for the SAP ERP buffers.
• Determine whether you will use dialog or communication users and how many work processes have been allocated and make sure there is a sufficient amount available.

  For example, there can be some users who are running inefficient programs that are delaying the dialog work processes. Use transaction SM50 to check all dialog work processes that have a waiting status.

• Use transaction ST04 to review the database response times. Examine the physical reads ratio, logical reads ratio, wait times, and number of user calls.
• Use transaction SE30 to perform an ABAP runtime analysis. Every long running program can be optimized, whether on the ABAP layer or on the selection layer. In general, more attention should be focused toward custom programs. Since these are usually created quickly, performance considerations are often neglected.