You can go directly to the SCM Queue Manager to monitor the CIF queues.
For additional error analysis, you can go directly from the postprocessing record to the relevant entry in the application log.
CIF error handling must be active.
CIF error handling is connected to authorization object C_APO_CFPP. An authorization profile with the relevant settings must be assigned to this authorization object for the user. The following activities authorize specific actions:
· 02 Change
¡ Retransfer objects to SAP R/3 or SAP APO
¡ Set postprocessing records to processing status Obsolete (set manually)
¡ Undo processing status Obsolete (set manually)
· 06 Delete
¡ Delete postprocessing records
· 03 Display
¡ All other actions
The selection screen provides you with the following options:
· Entry of the required SAP R/3 target system
As standard, CIF postprocessing always selects postprocessing records for both transfer directions (that is, transfers both from and to the selected SAP R/3 system).
In the lower screen area, you find the Select Data from R/3 indicator that is set as standard. In this case, the program reads the data both in SAP APO and the SAP R/3 system specified. In certain scenarios, such as the ATP scenario, data is sent only from SAP R/3 to SAP APO. It is not possible to update the data in SAP R/3 from SAP APO. To prevent a transfer from SAP APO to SAP R/3, an RFC destination is often not entered in SAP APO or an invalid one is used. In such scenarios, you should reset the indicator; otherwise, there may be program errors.
· Selection of postprocessing records according to certain selection criteria
· Additional restriction of postprocessing records according to error or processing status
· Different display options and user-specific definition of the layout
· Control of block formation when objects are present and during the selection of postprocessing records
The output screen provides you with the following options:
From the top of the screen, you can go to the SCM queue manager or make a new selection of postprocessing records using the selection criteria from the selection screen. The new selection includes processing records that have been generated in the meantime.
There is a navigation tree to the left of the screen. You can use the navigation tree to select the transfer direction for which postprocessing records are to be displayed. Under each transfer direction, you find the order categories for which postprocessing records were selected and in parentheses afterwards you find the number of postprocessing records with processing status Still for Processing. You use the selection in the navigation tree to filter the display of postprocessing records in the worklist (that is, the worklist only displays the postprocessing records that you have selected in the navigation tree).
The system displays the postprocessing records selected for the target system in list form in the worklist. Postprocessing records that are still to be processed are white, those that have been processed are green, and obsolete ones are gray. In general, you only select the postprocessing records that are still to be processed.
You can mark postprocessing records that are still to be processed individually and then process them in the following way:
· You use the Display Application Log icon to go directly to the application log to analyze the cause of error. You can access the application log by double-clicking on the postprocessing record.
· The History icon displays all postprocessing records that were previously generated for this object and that have not yet been reorganized.
· You use the Set Entry as Obsolete indicator to set the processing status of the postprocessing record to Obsolete (Set Manually); for example, if you do not want an object to be sent again. The object itself is unaffected by this action.
· You use the Remove Obsolescence Indicator to reset the processing status to Still for Processing. As a result, the postprocessing record is displayed in yellow.
· You use the Edit Note icon to create a note for the postprocessing record. First you select the relevant row. The note that has been created appears in the column Note. You can also change or delete an existing note using this icon. Notes are not language dependent, in other words, notes created in languages other than the user’s logon language are also displayed.
· You use the Display Note icon to display the note.
· You use the Send to APO APO and Send to R/3 R/3 icons to resend the object for which the postprocessing record was written to the relevant target system. For more information, see Resending Objects.
Processed postprocessing records are automatically removed from the worklist and appear under Objects Processed in this Session. A session starts each time you enter this screen from the selection screen. Postprocessing records with objects that have just been retransferred are marked in yellow. If a new error occurs when they are transferred again, they are marked in red.
You can process the postprocessing records as follows:
· You use the Add to Worklist icon to move the postprocessing record back to the worklist; for example, when the object is to be retransferred to the target system. The postprocessing record is only displayed in the worklist if the relevant object type is selected in the navigation tree.
· You can use the Display Current Postprocessing Log Current icon to display messages in the lower screen section for processing steps that have just been carried out. A maximum of 100 postprocessing logs are displayed.
· You can use the Display All Postprocessing Logs All icon to display all messages from this session.
· You use the Refresh Display icon to update the display for a postprocessing record when a retransfer is being made (that is, when the postprocessing record has the postprocessing status Currently Being Transferred).
· The times for postprocessing records are given in UTC.
· The following applies for transfers from SAP R/3 to SAP APO: Processing steps such as Set Entry as Obsolete, Remove Obsolescence Indicator, Send to APO, or Send to R/3 that you execute for a postprocessing record are automatically executed for all postprocessing records in this LUW. This retains the original composition of the LUW.