consolut - /SAPTRX/EE_MONITOR - Process overdue expected events

/SAPTRX/EE_MONITOR - Process overdue expected events

CL_GUI_FRONTEND_SERVICES - Frontend Services Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.

Purpose

You can use this report to process overdue expected events.

SAP EM processes overdue expected events belonging to the seasonalprocurement process in a different way from other overdue events. In the case of overdue expected eventsbelonging to the seasonal procurement process, SAP EM works onevent handlers and not on individual expected events. SAP EMbundles the expected events. When you select an overdue expected event for an event handler belongingto the seasonal procurement process, SAP EM reads all the expectedevents for this event handler. At the same time, SAP EM determinesinternally with reference to the time index for the report selection and in one step which expectedevents for the event handler will be overdue in this report run. SAP EM determines from these expected events which one is valid and has the highest internal priority.

Integration

Prerequisites

Features

Selection

Selection Parameters Specific to Seasonal Procurement

By default, you have the following selection options specific to seasonal procurement:

Check for Old qRFCs:

The Check for Old qRFCs parameter is set by default. SAPEM uses it to check whether there are terminated queued Remote Function Calls (qRFCs) with specialprefixes. SAP EM has constructed these for event handlers belongingto the seasonal procurement process (business process type ESC_PURORD_FASHION) in a previous run ofthe expected event monitor. If SAP EM finds terminated qRFCs,it means that a program error has occurred or that SAP EM couldnot reach the target system. First try to restart the qRFC using transaction SMQ1. If the error lies in the target system, you must perform one of the following options:

Delete the terminated qRFCs before restarting this report using transaction SMQ1(qRFC Monitor (Outbound Queues)). Note that by doing this you lose allthe activities for purchase orders in the package that come after the purchase order for which the program error occurred.

Restart the terminated qRFCs before restarting this report using transaction SMQ1 (qRFC Monitor (Outbound Queues)).

Before restarting this report, explicitly exclude the check for terminated qRFCs by not settingthe Check for Old qRFCs parameter in this report. SAPEM does not check for old qRFCs, but instead constructs a new qRFC. This new qRFC is based onthe current SAP EM data. Note that the same purchase order item can exist in both qRFCs.

When you restart the terminated qRFC after rectifying the error (transaction SMQ1), SAPEM executes the activities in the terminated qRFC that have not yet been processed. This mightmean that SAP EM executes some activities twice. For example,SAP EM postpones a date/time twice: The first time with the newqRFC that uses data that is not current from the viewpoint of the terminated qRFC, and a second time due to restarting the terminated qRFC.

Lines per Package Without Split: SAPEM only takes into account this parameter if you have not set the Packageper Purchase Order indicator. The parameter specifies the maximum number of lines per package(new queue name). Here SAP EM takes into account the fact thatpurchase order items belong to the same purchase order in the same package. This means that if necessary,SAP EM prevents a purchase order from being split by generatingmore lines for a package than the parameter specifies. The queue name contains EMFSas the prefix. The default value is 1000. You should make sure that you do not choose a value that is too small.

Package per Purchase Order: SAP EMconstructs one package per purchase order. It forms the queue name for current entries from the prefixSCEMFSN + purchase order number and for old entries from the prefix SCEMFSO + purchase order number.

SAP EM can then execute this report. When SAPEM processes qRFCs, it executes automatic activities, as required. Here it can be the case thata direct data backflow takes place from the SAP system to SAP EM.This backflow can result in changes to the expected events for event handlers. These changes have adirect effect on the selection of overdue expected events in this report. The processing of events belongingto the seasonal procurement process is not dependent on the indicator. If there are event handlers inSAP EM that belong to the seasonal procurement process, you should set the indicator.

You can also activate additional selection options specific to seasonal procurement. To do this, you:

Create an entry and set the Seasonal Procurement indicator in Customizingfor SAP EM. You set the indicator in the Implementation Guide(IMG) for SAP EM under GeneralSettings in SAP Event Management -> Activate Seasonal Procurement Process or in transaction /SAPTRX/TSC0FASH.

Set the parameter value X for GET/SET parameter /SAPTRX/EE_MON_SEL (Display Monitor Fields).

You then get the following radio buttons under Old Monitor Entries:

Process Old Monitor Entries:

If you choose this radio button, SAP EM also processes old entriesduring the monitor run, that is, entries that it did not create within this run. SAPEM first processes the current entries. It then processes the old ones and deletes them from the database.

Do Not Process Old Monitor Entries:

If you choose this radio button, SAP EM does notprocess any old entries during the monitor run, that is, entries that it did not create within this run. Moreover, it does not delete the database entry.

Delete Old Monitor Entries:

If you choose this radio button, SAP EM deletes old entries during the monitor run, that is, entries that it did not create within this run, without first processing them.

Fields Not Specific to Seasonal Procurement

If SAP EM is to display the following selection fields that arenot specific to seasonal procurement, you must set the parameter value X for the GET/SET parameter /SAPTRX/EE_MON_SEL (Display Monitor Fields).

Selection Criteria for Monitor Function

From date:

SAP EM uses this date to define the lower limit of the date index that it uses to select overdue expected events.

To date:

SAP EM uses this date to define the upper limit of the date indexthat it uses to select overdue expected events. You cannot, however, make a selection for a date that lies in the future.

Package size - monitor selection:

This field specifies the maximum number of overdue expected events that SAP EM can select in this monitor run.

Location Parameters

Location code set:

This field restricts the selection to a particular location code set. If you fill this field, you must also fill the Location Code ID1 field. If the SAP system has not transferred any internal event codes to SAP EM, it issues a warning message in dialog mode and an information message in background mode.