Kontakt

Ansicht
Dokumentation

FARRIC_OL - Revenue Accounting: Operational Load

FARRIC_OL - Revenue Accounting: Operational Load

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to perform an operational load of existing sales orders in a system, marking customized sales order items as relevant for Revenue Accounting (RAR).

Only customized sales order items relevant for revenue accounting are loaded. Subsequent documents, such as goods issue or billing documents relevant for revenue accounting, are also loaded by default unless they are switched off in expert parameters.

After the sales order item is loaded, the SD Revenue Recognitiontype is removed, and the sales order item is no longer processed by SD Revenue Recognition.

The detail lines for SD Revenue Recognitionused to post revenues are set to Inactive. Otherwise, all SD Revenue Recognition tables remain available for reporting or auditing purposes.

Depending on which contract management version is selected, the system performs the following activities:

  • If Classic Contract Management is selected, you must set the status of the company code to Migration, and the transfer date must also be assigned in Customizing. The legacy data of recognized revenue in SD Revenue Recognition is passed to Revenue Accounting (RAR).
  • If Contract Managementis selected, there is no need to set the status of the company code or to assign the transfer date. Further, you don't need to specify the migration fiscal year and period, as the system always determines the last period from the open period as the migration fiscal year and period.

Integration

Prerequisites

  • You have customized the item categories relevant for Revenue Accounting.
  • The integration component for Revenue Accounting is activated.
  • If you select Classic Contract Managementas the contract management version, then the status of the affected company code needs to be customized for MigrationLoad in Customizing under Revenue Accounting → Revenue Accounting Contracts (Classic)→ Assign Company Code to Accounting Principles.
  • Sales documents and their follow-on documents (like goods issue and invoices) that have previously been loaded into Revenue Accounting and must be loaded again (due to issues) have to be reset first. To do so, select the documents and choose the processing type Reset in the selection screen parameters. In addition, if you use Contract Management, the related revenue contracts must be cleaned by running the transaction FARR_PROD_CLEANUP.

Features

Selection

The following selection criteria are provided on the screen to determine the documents relevant for processing:

  • Company Code
  • Sales Organization
  • Distribution Channel
  • Sales Document Type
  • Sales Document
  • Created on
  • Migration Package:This field is relevant only if Classic Contract Management is selected as the contract management version.

The following selection screen parameters determine the way selected documents are processed:

  • Processing Type The following values are possible:
  • Load: revenue accounting relevance is determined based on the configuration (in Customizing under Sales and Distribution -> Revenue Accounting and Reporting -> Maintain Revenue Accounting Item Settings). If a sales order item is relevant, it is sent to Revenue Accounting together with all follow-on documents related to this item.

  • Reset: If an operational load (or any further processing in Revenue Accounting) was not successful and the operational load has to be repeated, the previously loaded documents must be reset first. Otherwise, the operational load cannot select them again. Reset means that the revenue accounting relevance is removed from the corresponding item and from all follow-on documents. Hence, the program recovers the state before the last operational load if the same selection criteria is applied(this means that the same documents are selected).

  • Contract Management Version:The following values are possible:
  • Classic Contract Management: The revenue contract will be created by Classic Contract Management from the sales order, and it requires you to set the status of the company code to Migration and to specify the transfer date in Customizing under Revenue Accounting → Revenue Accounting Contracts (Classic) → Assign Company Codes to Accounting Principles. You must migrate the sales orders collectively.

  • Contract Management: The revenue contract will be created by Optimized Contract Management from the sales order. You are not required to set the status of the company code to Migration. Further, you migrate each sales order individually. As you are not required to set status of the company code to Migration or maintain the transfer date, you need to specify the migration fiscal year and posting period.

  • Simulation If this checkbox is selected, the run is executed without changing the current data or sending RAIs. Simulation is based on the actual state of the database. This may result in a document being processed or not.
  • Synchronous Online Processing If this checkbox is selected, synchronous online processing is performed.
  • Number of Documents in Package This parameter is used to build packages of sales orders with the number given. Every package is processed in a separate job allowing parallelization.
  • External Run ID For every program execution, there is a unique ID identifying a run. This ID is generated automatically if no ID is entered.
  • Message Problem Class Filter to determine which messages are sent to the application log.

The following parameters are visible only if the operational load is executed in expert mode (with transaction FARRIC_OL_EXPERT). Please use the expert mode (transaction FARRIC_OL_EXPERT) only after contacting SAP.

  • Process Fulfillment Documents If this checkbox is selected, the fulfillment documents of the selected sales orders are also processed. Please deselect this checkbox only if the information needs to come from a legacy (non-SD) system.
  • Process Billing Documents If this checkbox is selected, the billing documents in the document flow of the selected sales orders are also processed. Please deselect this checkbox only if the information needs to come from a legacy (non-SD) system.
  • Create Legacy Data If this checkbox is selected, legacy data is created. For this, the realized revenue is obtained from SD-Revenue Recognition if a sales document item is relevant for SD-Revenue Recognitionand if SAP Sales and Distribution Integration with SAP Revenue Accounting and Reportingis installed. Otherwise, the realized revenue is calculated based on the processed billing documents. Please deselect this checkbox only if the information needs to come from a legacy (non-SD) system.
  • Search for Root Documents.If this checkbox is selected, the documents processed access the source document and its links for the document chain. Setting this parameter forces the chain to start from the source document and its initial selection criteria. This includes predecessor documents as well as successor documents. If you do not set this checkbox, only successor documents are considered.
  • Read from Archive.If this checkbox is selected, SD invoices and FI documents that are archived will be read from the archive. If this checkbox is not selected and a document is archived, an error message is issued.
  • Skip Completed Sales Document:If you set this indicator, the migration will skip the completed documents.

Standard Variants

Output

Processing results are recorded in a log and displayed on the screen for verification. You can find previously created application logs by calling the display log transaction with object FARRICand subobject OL.

Activities

You can accelerate document processing using parallel job execution. Maintain the distribution view for the application type FARRIC_OLto enable faster document processing by a corresponding job distribution.

Example






PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 10919 Date: 20240601 Time: 011517     sap01-206 ( 203 ms )