Prerequisites for Data Transfer

Since, in most cases, data is transferred asynchronously and in the background, the system cannot issue error messages directly to the user. For this reason, entries are made in the SAP application log under the object CIF and various subobjects in the systems involved.

To make it easier to search any errors that might have occurred, you should therefore activate the CIF application log on both sides, at least during the setup and test phases.

Set the Logging parameter to D in transaction CFC2 in the ERP system.
Set the Logging parameter to Detailed in transaction /SAPAPO/C4 in the SCM system.

Note that you can configure the control parameters for writing the application log in a user-specific way. If you enter * as the user name, the entry has an effect on all users whose identification is not entered explicitly in the transaction.

To connect your ERP system to the SCM system, you may need to make additional settings with regard to defining RFC destinations (transaction SM59) in both systems.

If you want the ATP check to be performed in the SCM system but triggered from the ERP system, make sure when defining the RFC connection for the SCM system in the ERP system that you use a user ID for the SCM system that was created there as a dialog user.
To be able, in special cases, to execute calls in one of the systems within the debugger, the RFC user used must also have debugging authorization.
If connection errors or lock problems occur in a target system, use transaction SM59 in the sending system to configure the settings for the target system in such a way that the system automatically repeats unsuccessful calls after a certain period of time. You can do this in the detailed view of an RFC destination under the menu option tRFC Options . It has proven successful to set the Connection Attempts to 10 and the pause between attempts to 2 . These settings mean that calls that could not be processed successfully due to technical connection errors or locks, in SAP liveCache for example, are executed again after 2 minutes. If the errors occur again, up to 10 more attempts are made to execute the call.
If you want a qRFC to be retained for debugging and not executed immediately by qRFC administration, you can set the parameter Debug to R in transaction CFC2 in the ERP system and to Debugging On/Recording of t/qRFCs (NOSENDS) in transaction /SAPAPO/C4 in the SCM system.

Up to and including SAP APO 3.1, the same RFC destination is used for all calls from SAP R/3 to SAP APO and vice versa. All necessary user authorizations must therefore be effective for this RFC destination. As of SAP APO 4.0, the concept of flexible RFC destinations is in place. This means that special RFC destinations are used for dialog application cases (ATP check, debugging, and so on). This offers a better and more secure way to control the authorizations to be granted. For more information, see the CIF Customizing in the SCM system under Start of the navigation path Basic Settings for Creating the System Landscape Next navigation step Assign RFC Destinations to Various Application Cases. End of the navigation path