Ansicht
Dokumentation

EXTRACT_ILM_NOTIF_SAMPLE - Extract ILM Notifications - Sample Report

Fill RESBD Structure from EBP Component Structure   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Purpose

Using this report, you can simulate local and external extraction of ILM notification details. You can run the sample report to understand the exact details that are extracted when the actual extraction process is run using recipient RFC destination or OData service.

Integration

Prerequisites

Features

ILM Object

Name of the object on which the ILM process is run.

Notification Mode

Unique Notification identifier for each of the ILM processes

01: Archiving Write

02: Archiving Delete

03: Data Destruction Run Using Archiving Write Report

04: Data Destruction of Archive Files

05: Destruction Run Using Data Destruction Object

*: All

11: Blocked

12: Unblocked

Recipient ID

Unique identifier of the recipient registered to extract notification data.

From (Date/Time)

Date and time range of ILM notifications to be considered for extraction.

To (Date/Time)

Date and time range of ILM notifications to be considered for extraction.

Complete Extraction

Flag to extract all available notification details. If date and time range is supplied with From (Date/Time)and To (Date/Time), that takes the precedence over Complete Extraction.

Simulate External Extraction

Select this checkbox to simulate external extraction of ILM notification details via RFC request or OData service. The following fields are enabled only when this checkbox is selected:

Recipient RFC Destination, Recipient URL and Extraction Purpose.

Recipient RFC Destination

Requesting RFC destination for extraction of ILM notification details. Caller must supply technical name of RFC destination (RFCDEST). Use Function Module RFC_SYSTEM_INFO to get the technical name of RFC destination of the caller.

Additional information:

The automatic authorization check is made by implicitly calling function module AUTHORITY_CHECK_RFC. If it detects an authorization issue, this function module triggers one of the exceptions defined in its interface, namely USER_DONT_EXIST or RFC_NO_AUTHORITY, thus triggering a runtime error. We recommend that you call this function module explicitly before a remote call, thus enabling you to handle any exceptions that may arise. If authorization exists, the function module does not return an explicit result, instead, like all function modules that are performed successfully, it sets sy-subrc to 0.

If the system profile parameter auth/rfc_authority_check is set (value 1), then the System automatically checks at the CALL FUNCTION keyword whether the authorizations user has the required RFC authorization.

Recipient URL

Requesting host URL for extraction of ILM notification details. Ex: OData service URL for GET request can be provided.

Extraction Purpose

Purpose of extraction for ILM notification via RFC request or via OData service.

Standard Variants

Output

Activities

Execute this report with valid values for the given selection fields to extract ILM notification details.

Example

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4393 Date: 20240531 Time: 145437     sap01-206 ( 63 ms )