Ansicht
Dokumentation
New Functions for Requests ( RELNPS_461A_REQUESTS )
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Short text
New Functions for Requests
Scope of Functions
Deferrals
Until now, only individual due dates (FI documents) could be deferred in a request. In the local authorities sector, however, several due dates of a sub-ledger account are usually handled in one deferral activity. In order to represent this process, the so-called mass deferral was developed allowing you to process several due dates in one deferral request.
In contrast to the individual deferral, it is now not possible to enter deferral requests in the mass deferral without a request number. This is due to the fact that it is technically no longer possible to make the connection between documents due and deferred documents by means of the invoice reference.
- Calculation of deferral interests
You can now allocate the calculation data for the deferral interests for each revenue type. Interests are then, for example, calculated for each revenue type or the total amount is rounded for each revenue type.
The calculation of the deferral interests begins with the Posting date of the deferral (previously: Due date of the document to be deferred).
You have the option of preassigning the commitment item or revenue type fields using the Set/Get parameters "PSOICI" and "PSOITR" when calculating the deferral interests.
- Reversal of deferral requests
The source documents are not restored when reversing a deferral request that has several due dates (FI documents). Mass processing is now available to help the reversing of deferrals with open items due.
Archiving deferrals
As soon as a deferral request was posted, the field Reason
for reversal in the deferred FI document is set to "01" (deferral request). This is possible
because during the reversal of the deferral request, the source FI documents are not restored. This
means that deferral requests no longer need to be specially prepared for archiving: The program previously used for preparing deferral requests for archiving (RFFMPS05) is no longer required.
Withholding tax
The extended withholding tax is offered for requests with the following restrictions:
- Standing requests with withholding tax are not possible
- Only documents, for which withholding tax information is posted at the time of payment, can be deferred
- The request printout contains no withholding tax information
- If you want to enter a deduction request for a document, for which the withholding tax has already been booked in the invoice, the customizable message FICUSTOM 020 must also have been adjusted, in order to allow an entry despite a difference in amount.
Non-deductible tax
Starting from this release, it is possible to use a tax code for non-deductible input tax in requests. It is possible to distribute the tax amount to the G/L account items and fixed asset items using this tax code.
Processing petty amounts
Starting from this release, a program is available for the automated writing off of petty amounts in customer or vendor accounts.
For further information on this topic, refer to the documentation for Processing petty amounts.
Substitution of fields in requests
Starting from this release, there are two points in time (Business Transaction Events) during requests, at which you can define your own coding so that certain fields in the requests can be filled automatically. These are the processes "00107010" and "00107020".
Authorization check during display of a request
Starting from this release, when requests are displayed, the FM account assignment is checked with activity '11'. The authorization check takes place at the same time as the other authorization checks, that is to say, if it is feasible, the commitment item, funds center and fund are all checked, if not, only a single check takes place.
During the processing of a stored FI document, the activity for posting '10' takes place. This check can be suppressed using user exit EXIT_SAPLFMWR_003, which is called up in the FM update.
Damage caused to data by errors
Software/hardware requirements
Installation information
Effects on System Administration
Effects on Customizing
Deferral
To be able to execute deferrals, you must define a G/L account for deferrals for each company code variant and fiscal year identification in the Customizing of Funds Management Germany in step
"Define account determination for deferrals".
Once
you have defined the general ledger, it is posted in the deferral request and in the relevant inverse postings instead of the general ledger defined in the account determination table.
To ensure that the data remains consistent, you must also adjust the FI field status of this general ledger so that the user can only enter a Funds Management account assignment (FM account assignment). All other account assignments must be hidden. You make these settings in the Customizing of Financial Accounting in step "Maintain field status variants".
Withholding tax
To use extended withholding tax, you must have made the settings in the Customizing of Financial Accounting in step Extended withholding tax.
To correctly adjust the customizable message, choose the step Change message control.
Effect on batch input
Changes to the Interface
Changes in procedure
Procedure for removing dataset errors
Dependent functions
Planning
Further notes
RFUMSV00 - Advance Return for Tax on Sales/Purchases rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 6697 Date: 20240603 Time: 231101 sap01-206 ( 116 ms )
