Ansicht
Dokumentation
RFARR_RAI_PP_PROC_NEWACP_START - Reprocess Revenue Accounting Items for New Accounting Principle
Fill RESBD Structure from EBP Component Structure SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Purpose
You introduced a new accounting principle for a company code in customizing. The data for the new (target) accounting principle shall be created based on the revenue accounting information that is already available in the system for a specified source accounting principle.
You execute this program before starting the transition phase for the new accounting principle.
The program selects all already processed revenue accounting items of the given company code. Archived data is not taken into account.
Revenue accounting items before the transfer date are immediately reprocessed for the target accounting principle. Revenue accounting items after the transfer date are copied back from status Processed (4) to status Processable(2). The latter ones can be processed in the monitor for revenue accounting items (transaction FARR_RAI_MON) or with transaction FARR_RAI_PROC once the target accounting principle is set to status Adoption Preparation.
The date that is relevant for comparison with the transfer date differs for the different RAI class types:
- Order items: inception date (If the inception date is initial, the start date is taken into account. If also the start date is initial, the creation date of the performance obligation of the source accounting principle is taken into account. The start date or the creation date of the performance obligation are stored in the field Inception Date in the revenue accounting item if this field was initial before.)
- Fulfillment items: event date
- Invoice items: posting date
Reprocessing of revenue accounting items with this report for the target accounting principle will lead to an update of the processing timestamp of the selected items. This way, these RAIs are again taken into account for reconciliation between Inbound Processing and Revenue Accounting Contract Management.
Integration
Prerequisites
- Before introducing the new accounting principle in customizing, make sure that all RAIs of the company code, or at least those before transfer date, are succesfully processed. Otherwise reprocessing with this report cannot be executed since this would lead to incorrect postings later on.
- The target accounting principle has to be in status Migration (IMG Activity:Assign Company Codes to Accounting Principles)
- THe source accounting principle needs to be maintained and has to be in status Productive for all migration packages.
Features
Selection
Standard Variants
Output
Activities
- Specify the selection data
- Enter the mandatory input parameters for company code and target accounting principle.
-
You may restrict the revenue accounting items to be reprocessed by ranges of contract IDs.
Remark:Only contracts that belong to the source accounting principle and are specified in the customizing of the target accounting principle will be taken into account!
- 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 Important or 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 and processed 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 and processed 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 code 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 code.
Sequence of processing
Within one interval the order items are processed first.
Then, the fulfillment items are processed.
Finally, the invoice items are processed.
Further Selections
You can exclude fields from the field list for further selections by adding them to structure CI_FARR_S_FREE_SEL_NEWACP_EXCL.
You can determine default fields for further selections by adding them to structure CI_FARR_S_FREE_SEL_NEWACP_DFLT.
Integration
Parallel processing runs can be monitored with transaction Monitor for Parallel Processing Runs (FARR_RAI_PP_MON).
Example
TXBHW - Original Tax Base Amount in Local Currency CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 7316 Date: 20240520 Time: 115716 sap01-206 ( 118 ms )
