Ansicht
Dokumentation
RFARR_RAI_PP_PROC_START - Process Revenue Accounting Items
Fill RESBD Structure from EBP Component Structure Vendor Master (General Section)This documentation is copyright by SAP AG.
Purpose
You use this program to transfer revenue accounting items from status processable (2) to processed (4).
Prerequisites
Features
Selection
Standard Variants
Output
Activities
- Specify the selection data
- You may restrict the revenue accounting items to be processed by the following parameters:
- Revenue accounting item class
- Sender component
- Logical system
- Header ID (ID of the original document in the sender component, for example sales order ID or billing document ID)
- Reference type
- Reference ID
- Company code
- You may add additional selection parameters by choosing Further Selections.
- Specify the technical parameters
- Specify the settings for the application log
- Specify the problem class for which the system writes messages to the application log. If you process mass data, choose problem class Importantor Very Important. If you process low volumes, choose problem class Additional Information.
- Optionally, enter an external ID for the log. The external ID can be used to identify the application log created by the mass run in transaction Analyse Application Log (transaction SLG1). If no external ID is entered, the system automatically determines an ID using number range object Mass Run Log No. (BANK_RUNNR).
- Execute the program (F8).
Additional information
Distribution of revenue accounting items to the intervals
Each processable revenue accounting item is assigned to a subarea (technical field name KEYPP,
possible values are 000 - 999). This way, all revenue accounting items are (in the ideal case evenly) distributed into 1.000 subareas.
The subarea of a processable order item is determined based on the reference ID (technical field name
REFERENCE_ID) of the order item. This means that each order item with a specific reference ID is assigned to the same subarea.
The subarea of a fulfillment item is equal to the subarea of the related order item. The subarea of an invoice item is equal to the subarea of the related order item as well.
When starting the processing of revenue accounting items, the number of intervals is specified. The processing program evenly distributes all available subareas to the intervals.
Each interval processes all items belonging to its assigned subareas and corresponding to the specified selection parameters.
Locking mechanism
As long as one interval is processed, ALL processable items of the subareas assigned to this interval and assigned to the company codes specified in the selection data are locked. This means that no other processing run in parallel can process items that belong to the same combinations of subareas and company codes.
If a mass run is started without any restrictions on the company code (nothing entered in selection parameter company code), the subareas of this interval are locked for all company codes used in SAP Revenue Accounting and Reporting (IMG: Revenue Accounting -> Revenue Accounting Contracts -> Assign Company Codes to Accounting Principles).
If a mass run is started for one or several company codes (selection parameter company code is used), the subareas of this interval are only locked for the company codes specified.
Sequence of processing
Within one interval, the order items are processed first.
Note:
The program processes all selected order items with identical reference type and ID in one block, as
these revenue accounting items are likely to refer to the same revenue accounting contract. This way, the number of updates on a revenue accounting contract can be minimized.
It is therefore not recommended to restrict the selection, for example to a single sender component,
if revenue accounting items of different sender components shall become part of the same revenue accounting
contract afterwards. If the selection is restricted, for example to a single sender component, several
processing runs need to update one and the same revenue accounting contract. This has a negative impact on performance.
Then, the fulfillment items are processed.
Finally, the invoice items are processed.
Reprocessing of locked data
Revenue accounting items can't be processed when the revenue accounting contract or the subarea / company code they are assigned to is locked by another process.
To keep the number of items, which could not be processed due to locking errors, as small as possible, mass processing stores the data with locking issues and reprocesses them again at the end of the mass run.
Further selections
You can exclude fields from the field list for further selections by adding them to structure CI_FARR_S_FREE_SEL_PROC_EXCL.
You can determine default fields for further selections by adding them to structure CI_FARR_S_FREE_SEL_PROC_DFLT.
Invoice or fulfillment revenue accounting items (RAIs) aren't selected for processing if they are selected
in the field list under Further Selectionswhen the field belongs only to the order RAI structure, and not to the invoice or fulfillment RAI structure.
You can change this behavior using the user parameter FARR_NEW_LOGIC. After FARR_NEW_LOGICis
activated, a new list box Process FF and Invoice RAIsis added on the user interface of FARR_RAI_PROC under Further Selections.
After selecting All Items Independent of Order Items, the fulfillment and invoice RAIs are selected for processing regardless of the order items.
If Only Items Related to Order Itemsis selected, just the fulfillment and invoice RAIs that belong to the currently processed order items are processed. These fulfillment and invoice RAIs are also processed when a field is selected in Further Selectionsthat does not exist for fulfillment or invoice RAIs.
Integration
Parallel processing runs can be monitored with transaction Monitor for Parallel Processing Runs(FARR_RAI_PP_MON).
RFUMSV00 - Advance Return for Tax on Sales/Purchases CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 7749 Date: 20240520 Time: 131150 sap01-206 ( 128 ms )
