Ansicht
Dokumentation

EHFND_PC_JOB_SCOPE - Activation of Scope-Dependent Background Job Definitions

TXBHW - Original Tax Base Amount in Local Currency   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

In Product Compliance, the Technical Job Repository is integrated with the background processing in combination with Product Compliance Event Processing (PCEP).

You can choose whether to use the Technical Job Repository or to create jobs manually using the transaction SM36. If you want to create jobs manually, please skip this Customizing activity and proceed to the Customizing activity Schedule Jobs for Product Compliance Background Processing.

In the Technical Job Repository, the developer defines a technical job. This definition contains the name, the user ("default"), and the settings for event-based scheduling.

The SAP kernel starts a job generation every 60 minutes, which then starts the job R_JR_BTCJOBS_GENERATOR on each client in the system. This job then carries out the following steps:

1. Collect all existing active technical job definitions.
2. For each job definition, check whether the job is relevant in the current client. The relevance check includes the following:

• Should the job run in the business and/or administration client?

• Scope-dependent job definitions: Is a scoping table entry present for the job definition?

Status Scope State	Scope Callback Class State	Scope State of Job Definition	Comment
OFF	No need to check	OFF	Static scope state remains OFF
OFF	No need to check	OFF	Static scope state remains OFF
ON	ON	ON	Static scope state remains ON. Scope callback class state is checked by SJOBREPO runtime.
ON	OFF	OFF	Static scope state remains ON. Scope callback class state is checked by SJOBREPO runtime.

• For each job definition: If not relevant in current client, unschedule any existing technical job.

• For each job definition: If relevant in the current client, calculate start condition for technical job. This job appears as a new job in status Released.

• For each job definition: Check if a technical job already exists with the correct start condition.

• If yes: No action

• If no: Unschedule any existing technical job and schedule a new technical job with the correct start condition.

The event producer (such as a UI via BOPF BO) creates a new PCEP event. The event is added to the database and an SWE2 event is raised and processed in the update task. This ensures that the upcoming background processing is started after the commit has been executed and the BOPF buffer has been flushed to the database. The PCEP SWE2 integration is notified after the commit and raises the background event SAP_EHFND_PCEP_EVT_CRTED. The event-based scheduler is started when a background event occurs. The scheduler scans the table BTCEVTJOB to select all jobs waiting for the specified event and starts a new batch worker process, which then processes the job. The report linked to the job then executes the PCEP consumer API and processes all PCEP events for asynchronous processing.

OFF

OFF

OFF

Carry out the following jobs:

• SAP_EHFND_PCEP

• SAP_EHFND_PC_CONTENT_LOAD

• SAP_EHFND_PC_SRVREQ_REFRESH

• SAP_EHPMA_SVT

For more information, see the Customizing activity Activation of Scope-Dependent Application Job Catalog Entries.

OFF

BAL_S_LOG - Application Log: Log header data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4846 Date: 20240523 Time: 163353     sap01-206 ( 66 ms )