/SAPTRX/EE_MONITOR - Process overdue expected eventsrdisp/max_wprun_time - Maximum work process run time rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
You can use this report to process overdue expected events.
SAP EM processes overdue expected events belonging to the seasonal procurement process in a different way from other overdue events. In the case of overdue expected events belonging to the seasonal procurement process, SAP EM works on event handlers and not on individual expected events. SAP EM bundles the expected events. When you select an overdue expected event for an event handler belonging to the seasonal procurement process, SAP EM reads all the expected events for this event handler. At the same time, SAP EM determines internally with reference to the time index for the report selection and in one step which expected events 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.
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. SAP EM uses it to check whether there are terminated queued Remote Function Calls (qRFCs) with special prefixes. SAP EM has constructed these for event handlers belonging to the seasonal procurement process (business process type ESC_PURORD_FASHION) in a previous run of the expected event monitor. If SAP EM finds terminated qRFCs, it means that a program error has occurred or that SAP EM could not 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 all the 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 setting the Check for Old qRFCs parameter in this report. SAP EM does not check for old qRFCs, but instead constructs a new qRFC. This new qRFC is based on the 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), SAP EM executes the activities in the terminated qRFC that have not yet been processed. This might mean that SAP EM executes some activities twice. For example, SAP EM postpones a date/time twice: The first time with the new qRFC 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: SAP EM only takes into account this parameter if you have not set the Package per Purchase Order indicator. The parameter specifies the maximum number of lines per package (new queue name). Here SAP EM takes into account the fact that purchase 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 generating more lines for a package than the parameter specifies. The queue name contains EMFS as 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 EM constructs one package per purchase order. It forms the queue name for current entries from the prefix SCEMFSN + purchase order number and for old entries from the prefix SCEMFSO + purchase order number.
SAP EM can then execute this report. When SAP EM processes qRFCs, it executes automatic activities, as required. Here it can be the case that a 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 a direct effect on the selection of overdue expected events in this report. The processing of events belonging to the seasonal procurement process is not dependent on the indicator. If there are event handlers in SAP 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 Customizing for SAP EM. You set the indicator in the Implementation Guide (IMG) for SAP EM under General Settings 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 entries during the monitor run, that is, entries that it did not create within this run. SAP EM 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 not process 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 are not 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 index that 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 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 ID 1 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.
- Location ID 1:
- This is the parameter dependent on the Location Code Setparameter.
- Location ID 2:
- This is the optional parameter the Location ID 1 parameter.
- Internal event code:
- This parameter is a range table with internal event codes. SAP EM uses this table to restrict the selection to certain internal event codes.
CL_GUI_FRONTEND_SERVICES - Frontend Services BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 10879 Date: 20191023 Time: 100926 sap01-206 ( 52 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.