Ansicht
Dokumentation

Logging of Errors in the Initial Data Transfer (New) ( RELNAPO_401_INT_INITPROT )

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Short text

Logging of Errors in the Initial Data Transfer (New)

Use

If an error occurs in SAP R/3 during the selection of the orders to be sent in the initial data transfer, the system previously terminated the initial data transfer with the message "Error occurred in order selection." Since no other log entries were written for this error, it could take a long time to determine the cause of the termination of the initial data transfer.

As of SAP R/3 Plug-In 2003.1, the system generates entries in the CIF application log in SAP R/3 when errors occur in the transfer of planned or manufacturing orders. The orders that are affected are not posted to the target system, but the initial transfer continues without errors and subsequent orders continue to be transferred. Note that the system only generates entries in the CIF application log if X (Normal) or D (Detailed) is set in the Logging column for this user in the Implementation Guide of the APO Core Interface (CIF IMG) under Basic Settings for the Data Transfer -> Set Up User Parameters.

If you want an error in order selection to lead to the termination of the initial data transfer, as was previously the case, you can use customer exit CIFORD002. SAP Note 593413 describes the necessary steps.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

The system issues a message that an error has occurred and that an entry was created in the application log. You should therefore check after each initial data transfer whether entries exist in the application log relating to the transfer of planned and manufacturing orders. You access the application log from the CIF menu under Monitoring or by calling transaction CFG1.

After you have analyzed the error(s), change the order in SAP R/3. This change is then transferred to SAP APO automatically as part of the change transfer. If the order does not yet exist in SAP APO, it is created automatically, otherwise it is changed as needed.

The automatic change transfer to SAP APO requires an active integration model. The integration model is not active if, for example, you have used customer exit CIFORD002 to specify that the initial transfer should terminate at errors.

Effects on Customizing

Further Information

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 2679 Date: 20240427 Time: 042440     sap01-206 ( 65 ms )