Ansicht
Dokumentation
RFKKORD02_EXTENDED - Evaluation of Standing Requests
BAL Application Log Documentation Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Purpose
The program lists all standing requests and information from the corresponding FI-CA documents that correspond with the selection conditions.
You can choose between a hierarchical tree structure and a flat table view on the selection screen in the section entitled "output format".
Output as tree structure
In the tree structure the data is grouped according to request and period of execution.
- The search function is supported.
- Other functions such as filtering, aggregation (total, average, maximum etc.) or the export of the data displayed is not supported.
- By simply clicking on a document number, you will be navigated to this document (transaction fpe3).
- By double clicking on another field, you are navigated to the request (transaction fkkord2).
Output in table view
The table view is rather a technical view of the data.
- Search, filter and export functions are supported.
- The "total", "mean value", "minimum", and "maximum" aggregation functions are supported for all amount fields in transaction currency.
- By simply clicking the document number, you will be navigated to this document (transaction fpe3).
- By double clicking on the request number, you are navigated to the request (transaction fkkord2).
The result shows you the most important information about your standing request. In addition to the columns displayed in the standard system, you can add additional columns using the layout. The information displayed contains both the database fields from the tables DFKKORDER, DFKKORDERDUE and DFKKORDERPOS and the additional information derived from them.
Use of selection criteria and authorization check
Maximum number of hits
The number of hits encompass the number of lines in the table view that meet the selection criteria. This is not the number of standing requests or the number of all the lines in the table view. Since an individual standing request can contain several lines (one line for each period of execution, per special date, and per request item), the number of all lines is usually higher than the number of standing requests. Furthermore, missing authorizations and the “all or nothing” principle (see below) may mean that additional lines are removed from or added to the results list.
Authorization check
Requests from locked business partners (locked for the purpose of data protection) are not displayed. Incidentally, the same authorization checks such as in transaction fkkord2 are performed for each request.
"All or nothing" principle
Since the selection criteria does not only contain the header data of the request, a direct application of these criteria can lead to misleading results, since part of the request fulfills the criteria and another however does not. Therefore, either all data is always output for a request or no data at all.
Examples:
- Example 1: Request 25 has two items: one for business partner 100 and the other for business partner 200. The business partner 100 has been selected on the selection screen. In this case, request 25 is completely displayed, both the item for business partner 100 as well as the item for business partner 200.
- Example 2: Business partner 100 is locked for the purpose of data protection. In this case, no data for request 25 is output, it is also not output for business partner 200.
- Example 3: The maximum number of hits is set to 250. The first item from request 25 is at position 250. The second position is at the position 251. In this case, all items of the request are displayed.
Dynamic Selection
You can use the dynamic selection to add selection criteria for all fields (except purely technical fields) in the database tables DFKKORDER, DFKKORDERDUE, and DFKKORDERPOS.
If selection criteria are provided on the dynamic selection screen for fields that are not available on the standard selection screen, this is indicated as “active dynamic selection” and is displayed with the supplement “active” on the pushbutton for dynamic selections.
When you save variants, active dynamic selections are saved on the standard selection screen along with the selection criteria.
Dynamic selections on the standard selection screen are synchronized:
- When you access the dynamic selection, the following occurs:
- The current selection on the standard selection screen is used as a preselection for the dynamic selection.
- Existing, active dynamic selections for fields that are not defined on the standard selection screen are not changed.
When you return to the standard selection screen, all fields in the current dynamic selection overwrite the existing selections for the corresponding fields on the standard selection screen.
If you change selections for fields on the standard selection screen, this only has an effect on the selection criteria for these fields. Active dynamic selections are not changed.
If the program is executed, all active dynamic selections and all criteria defined on the current selection screen take effect.
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 6388 Date: 20240601 Time: 053428 sap01-206 ( 100 ms )
