Ansicht
Dokumentation
RFFMFG_TROR - Treasury Report on Receivables and Debt Collection Activities (TROR)
BAL_S_LOG - Application Log: Log header data CL_GUI_FRONTEND_SERVICES - Frontend ServicesThis documentation is copyright by SAP AG.
Purpose
The Treasury Report on Receivables and Debt Collection Activities (TROR) is designed to extract, manipulate, and display data about accounts receivable and related activity. Treasury requires agencies to submit this report every quarter for the fiscal year-to-date. The report format and line definitions are specified by the Treasury's Financial Management Service (FMS). FMS uses this report to monitor accounts receivable and collections from the public.
In addition to supporting the Treasury requirements, the report program provides additional flexibility to support agency management. For example, agencies can run the report on a monthly basis, include federal customers and public customers, define additional report lines, and change the report processing logic
Integration
Prerequisites
The TROR requires the classification of customers into customer types. The initial delivery of the TROR
uses trading partners to determine customer types using configuration maintained in the Implementation
Guide (IMG). Choose Public Sector Management → Functions for US Federal Government → General Settings →
FI reason codes must be maintained in the IMG. They are used to classify individual documents in accordance
with Treasury regulations, so they appear on the correct report lines. Choose Public
Sector Management → Functions for US Federal Government → Reporting →Treasury Report on Receivables→
Group definitions for reason codes, document types, and G/L accounts are defined in the IMG. Choose
Public Sector Management → Functions for US Federal Government → Reporting →Treasury Report on Receivables→
The report layout and line definitions must be defined in the IMG. Choose Public
Sector Management → Functions for US Federal Government → Reporting →Treasury Report on Receivables →
Features
Selection
The TROR report can be executed for one fiscal year extending up to and including a given posting period.
The selection screen contains options for controlling data to be included in the overall population of the report. The Report Configuration Version is used to select the report layout and line definitions. The Reporting Entity Code is displayed on the header of the report; there is no specific logic associated with it. The Key Date is used for aging calculations. It is compared with the net due date for the original receivable.
Treasury mandates that the report include only receivables from public entities, but receivables from Federal customers can be included by selecting the Include Federal Customers.
When you click Select Account Assignments, additional selection fields appear. However, selection from Ledger 95 is resource-intensive and increases the report’s runtime. By default, the report does not select data from Ledger 95. Use this option if you need to select customer data based on account assignments.
Default logic for document selection, line calculations, and customer type determination is defined
in the Business Add-In (BAdI) implementation. Choose Public Sector Management
→ Functions for US Federal Government → Reporting → Treasury Report on Receivables → Business Add-Ins for TROR →
Note: This BAdI is delivered with default implementation FMFG_TROR_CALC_IMP. To make changes to the default logic, you can create a custom implementation for FMFG_TROR_CALC.
Using the BAdI, the report selects accounting document lines for customers based on the criteria specified on the selection screen. After the initial selection, the report filters the documents for each report line definition based on configuration settings and groups documents that pass through the line filter.
Note: If the report preselects a set of documents, the report output is empty if none of these documents corresponds to the line configuration settings.
For some lines, additional logic specific to that line is in the default BAdI implementation, which can be modified. For example, the beginning balance line includes balances from the beginning of the fiscal year and the new receivables line contains receivables created during the current fiscal year.
The default logic for determining customer types for the TROR uses the trading partner value in the customer master (KNA1-VBUND) and the configuration settings for Trading Partner Exceptions. This determination logic can be modified by creating a custom implementation of BAdI_FMFG_TROR_CALC. If the system cannot determine a valid TROR customer type, the customer is listed in the TROR’s application log and is not included in the report results.
Customers with a trading partner (TP) value not in the TP exceptions table are classified as federal for general ledger posting and the TROR.
Customers with a blank TP in the customer master are considered nonfederal for general ledger posting purposes. Unless there is an entry in the TP exception table for a blank TP with a TROR customer type, documents associated with these customers are excluded from the TROR results. If an entry with a blank TP value is added to the table, the corresponding configuration setting determines the customer type.
Standard Variants
Output
The report output contains lines defined in VC_FMFG_TROR_CONFIG. Numbering and indentation of sections (1, 2, 3,...) and subsections (A, B, C,…) are determined dynamically based on the line order and level specified in the documentation. Total line amounts and counts are based on total configuration values, which provide the list of lines and corresponding signs for totaling contributing lines.
The document list selected for each nontotal amount line can be displayed by double-clicking the line or by selecting the line and clicking Line details.
If errors or warnings occur during the execution, the Application Log button becomes visible and warning message, Errors occurred during processing. Check application log. is displayed in the status bar on the bottom of the screen. For example, messages that appear in the application log include FMFG851 and FMFG855.
Activities
Example
Fill RESBD Structure from EBP Component Structure Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 8530 Date: 20240520 Time: 115502 sap01-206 ( 166 ms )
