--- title: Schedule jobs source: https://docs.newrelic.com/docs/sap-solutions/install-and-configure/schedule-jobs --- Schedule these three programs using transaction `SM36`: | ABAP program | Functionality | Recommended frequency | | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ | --------------------- | | [`/NEWR/REGISTRY_RFC_CHECK`](#rfc-check) | Check RFC connections to the Monitored Systems and NR API endpoints | Every 3 minutes | | [`/NEWR/ABAP_COLLECTION_MANAGERN`](#abap-collection-manager) | Data Collection, Multiple jobs should be scheduled based on connected systems and data providers | Every 5 minutes | | [`/NEWR/RESEND_FAILED_API_TRANS`](#resubmit-program) | Re-submit failed transmissions | Every 15 minutes | ## Schedule RFC check program [#rfc-check] Schedule `/NEWR/REGISTRY_RFC_CHECK` every 1 to 3 minutes using the job name `NR_RFC_CHECK`. Make sure it runs more frequently than the **data collection job**. ## Schedule ABAP data collection manager [#abap-collection-manager] Schedule three data collection jobs with variants focused on the following data provider groups. For instructions on scheduling collection manager jobs before `SP03`, see [Variants and Jobs before SP03](https://docs.newrelic.com/docs/sap-solutions/reference/variants-and-jobs-before-sp03). Separate data providers into three groups for scheduling. For a complete list of all data providers, see the [Data Providers Reference](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference). - **TRACE group** includes performance database (STAD) related data providers: - [`NR.SAP.TRANSACTION`](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference/#sap-appl-metrics): Trace data provider - [`NR.SAP.TRANSACTION.COMPLETE`](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference/#sap-appl-metrics): Complete performance database collection with parallel background RFC process - `NR.SAP.SYSTEM.PROCESS` and `NR_SAP_PROGRAM`: Suspended after SP02 - `NR_SAP_WORKLOAD_COMPLETE` and `NR.SAP.WORKLOAD.COMPLETE` - **IDOC group** includes IDOC-related providers (may take significant time in production): - [`NR_SAP_IDOC`](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference/#idoc-all): Main IDOC status event data provider - [`NR_SAP_IDOC_COMPLETE`](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference/#idoc-all): Complete IDOC retrieval with background RFC collection - `NR_SAP_IDOC_Configuration`: Download IDOC master data to improve performance - **SYSTEM group** includes all remaining data providers. See the [complete list by monitoring group](https://docs.newrelic.com/docs/sap-solutions/monitor/data-providers-reference). ### Create variants for /NEWR/ONE_COLLECTION Starting from **SP03**, `/NEWR/ABAP_COLLECTION_MANAGERN` and `RSBTONEJOB2` are combined into `/NEWR/ONE_COLLECTION`. This program includes all parameters from `/NEWR/ABAP_COLLECTION_MANAGERN` and job names from `RSBTONEJOB2`. It functions similarly. To schedule jobs, create variants for `/NEWR/ONE_COLLECTION` using the following values: | Variant name | TRACE | IDOC | SYSTEM | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Job Name** | `NR_COLLECTION_TRACE` | `NR_COLLECTION_IDOC` | `NR_COLLECTION_SYSTEM` | | **New Relic Account ID** | SAP Account used to receive data | SAP Account used to receive data | SAP Account used to receive data | | **Records per Trans** | Default to 10000 | Default to 10000 | Default to 10000 | | **Data Transmission to New Relic** | Default to Direct | Default to Direct | Default to Direct | | **Data Provider Name** | Select Single Values: - `NR.SAP.TRANSACTION` - `NR.SAP.TRANSACTION.COMPLETE` - `NR.SAP.SYSTEM.PROCESS` - `NR_SAP_PROGRAM` - `NR_SAP_WORKLOAD_COMPLETE` - `NR.SAP.WORKLOAD.COMPLETE` | Select Single Values: - `NR_SAP_IDOC` - `NR_SAP_IDOC_COMPLETE` - `NR_SAP_IDOC_Configuration` | Exclude Single Values: - `NR.SAP.TRANSACTION` - `NR.SAP.TRANSACTION.COMPLETE` - `NR.SAP.SYSTEM.PROCESS` - `NR_SAP_PROGRAM` - `NR_SAP_WORKLOAD_COMPLETE` - `NR.SAP.WORKLOAD.COMPLETE` - `NR_SAP_IDOC` - `NR_SAP_IDOC_COMPLETE` - `NR_SAP_IDOC_Configuration` | | **Execution Mode** | Sequential Processing | Sequential Processing | Parallel Processing | | **Min WP Required** | If system DIA WP >= 30, set to 6; otherwise set to 3. | N/A | If system DIA WP >= 30, set to 6; otherwise set to 3. | ### Schedule collection jobs Use transaction `SM36` to schedule three collection jobs with the following configuration: | Job name | `NR_COLLECTION_TRACE` | `NR_COLLECTION_IDOC` | `NR_COLLECTION_SYSTEM` | | ---------------- | ---------------------- | ---------------------- | ---------------------- | | **Program** | `/NEWR/ONE_COLLECTION` | `/NEWR/ONE_COLLECTION` | `/NEWR/ONE_COLLECTION` | | **Variant** | TRACE | IDOC | SYSTEM | | **Running Freq** | Every 5 minutes | Every 5 minutes | Every 5 minutes | ![A screenshot displaying the SAP ABAP Collection Manager variant configuration screen](https://docs.newrelic.com/images/abap-collection-manager.webp "SAP ABAP Collection Manager variant configuration") #### Schedule each job 1. Start transaction `SM36`. 2. Enter the **Job Name** for each job and set the **Job Class** to **C**. 3. Click **Step**, enter the **Program Name** `/NEWR/ONE_COLLECTION`, and select the **Variant**. 4. Click **Start Condition**, set the **Start Date** and **Time**, and check the **Periodic Job** box. 5. Go to **Period Values**, click **Other Period**, and enter **5** for minutes. ## Schedule resubmit program [#resubmit-program] 1. Create a **variant** named **DEFAULT** for the program `/NEWR/RESEND_FAILED_API_TRANS`. Use it to resubmit failed transmissions for the **New Relic account** in case of a transmission error. 2. Specify the following values: - [**New Relic Account ID**](https://docs.newrelic.com/docs/accounts/accounts-billing/account-structure/account-id) - **HTTP Response Codes**: Exclude `000` and `413`, and the range `200` to `299`. ![A screenshot displaying the resend failed API transactions](https://docs.newrelic.com/images/resend-failed-api-transaction.webp "Resend failed API transactions") 3. Schedule this job to run every 15 minutes to resubmit failed transmissions, such as those with **HTTP response code** `500`, and periodically purge **transmission log entries**.