Ansicht
Dokumentation

R_EHFND_PCEP_EVT_QUEUE_WORKER - Event Queue Worker for asynchronous processing

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Purpose

The program is part of Product Compliance Event Processing (PCEP) and processes product compliance events and product compliance tasks.

Integration

The program integrates PCEP with background processing and needs no user interaction.

The program runs in the context of an event-based technical job that is triggered by the background event SAP_EHFND_PCEP_EVT_CRTED.

Prerequisites

Features

The idea of PCEP is to decouple the event creation from the event processing. Product compliance-relevant changes to objects create corresponding product compliance events in the system. The processing time of these events can vary based on the type of the event and the amount of impacted data. Therefore, these events are processed in the background.

Example: The user releases a substance-based composition in the relevant SAP Fiori app. The system produces a corresponding product compliance event. Additionally, the system starts the background event SAP_EHFND_PCEP_EVT_CRTED. This event triggers the event-based technical job to start and run the given program that processes the product compliance event in the background.

PCEP event producers can generate events. The counterparts of the event producers are event consumers. Event consumers are the classes that ultimately receive the events and typically act on them. An event consumer may derive product compliance tasks out of the given events, which are then processed separately. Such tasks represent separate and atomic operations that can be processed independently. During task processing, follow-on events may be raised again. This process allows a chain of events and tasks to be built during runtime.

The PCEP scheduler determines the product compliance events and product compliance tasks for processing and decides which item is to be scheduled next based on a defined prioritization. In the case of an event, the defined event consumers are determined and executed. As mentioned, the execution of the event consumers may then create follow-on tasks, which the scheduler then considers. In the case of a task, the defined task implementation is executed.

The PCEP background job runs as long as there are product compliance events and product compliance tasks in the system that are ready for processing.

Consequence: The runtime of the job depends on the number and type of events, the number of event consumers, the number of tasks that are derived from these events, and the runtime of the tasks that may depend on the structure of the underlying data.

Example: Changes to the compliance status of a substance may lead to long recalculations if this substance is used in many products. These long recalculations have a direct impact on the runtime of this job.

Selection

The program considers all product compliance events and product compliance tasks in the processing statuses New and Error.

Standard Variants

The program has a set of clean-up features implemented.

Example: The program deletes product compliance events and product compliance tasks in the processing status Done that are more than two days old.

Output

The program has processed the product compliance events and product compliance tasks.

The activities of the program have been logged in the job log and the application log.

Activities

Example

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 3694 Date: 20240520 Time: 120328     sap01-206 ( 84 ms )