Ansicht
Dokumentation

/IBS/RB_FPERIOD - Define Settlement Period Change

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

In this Customizing activity, you can define a fiscal year that varies from the calendar year and a corresponding RBS settlement period. If you do not make a setting, then the fiscal year is assumed to be the same as the calendar year, or RBD interprets the settlement period as being the same as the calendar year.

Note that these settings are relevant for the FS-RBD component only. If you want to use a fiscal year that is different to the calendar year, you must also make corresponding settings in the connected financial accounting component (such as SAP FI-GL).

You make the settings at RBD area and evaluation method level.

• In the start of fiscal year field, you define when the RBD settlement period is to start. The system derives the start of the fiscal year from the day and month defined here. Note that this date must be in the past or the system will ignore it.

• In the settlement period field, you must define the length of the settlement period. You can choose between year, half year, quarter, month, and days.

The section below describes the effects of the possible settings in this Customizing activity based on three different sample Customizing settings.

The three sample Customizing settings are described first, followed by a description of RBD processing based on the "position reduction" and "loss on receivables" business operations.

• Variants of Sample Customizing

• Sample Customizing (A): A new RBD settlement period is to start on April 1st and October 1st of a year.

RBD Area:	Flow method	FY Start	Settlement period
0001	02	01.04.2009	Half year

• Sample Customizing (B): A new RBD settlement period is to start on April 1st of a year.

RBD Area:	Flow method	FY Start	Settlement period
0001	02	01.04.2009	Year

• Sample Customizing (C): A new RBD settlement period is to start on January 1st like the calendar year.

No settings are required in this Customizing activity!

• Business operation 1: Reduction of risk provision position (reset or write-off)

On December 31st of the previous calendar year, an appropriation posting was made to set up a risk provision position of EUR 100 for the first time for a source system contract.

During a subsequent evaluation on January 31st of the current calendar year, the system determined a risk provision requirement of EUR 80, which means that the risk provision position must be reduced by EUR 20.

• RBD processing based on sample customizing (A): Reset

Because both the appropriation (12/31) and the reduction of the risk provision requirement (01/31) are in the same settlement period (10/01 of previous calendar year - 03/31 of current calendar year), the reduction of the risk provision position is made using a reset posting.

• RBD processing based on sample customizing (B): Reset

Because both the appropriation (12/31) and the reduction of the risk provision requirement (01/31) are in the same settlement period (04/01 of previous calendar year - 03/31 of current calendar year), the reduction of the risk provision position is made using a reset posting.

• RBD processing based on sample customizing (C): Write-off

Because the reduction of the risk provision requirement (01/31) is in a new RBD settlement period to the original appropriation (12/31), the reduction of the risk provision position is made using a write-off posting.

• Business operation 2: Handling of loss on receivables (reset and direct write-off or usage)

On December 31st of the previous calendar year, an appropriation posting was made to set up a risk provision position of EUR 100 for the first time for a source system contract.

During subsequent evaluation on January 31st of the current calendar year, the system determined a loss on receivables of EUR 40, the risk provision requirement had been reduced to EUR 60 and must now be reduced to EUR 40.

• RBD processing based on sample customizing (A): Reset and direct write-off

Because both the appropriation (12/31) and the inclusion of the risk provision requirement (01/31) are in the same settlement period (10/01 of previous calendar year - 03/31 of current calendar year), the loss on receivables cannot be achieved using usage of the risk provision position. A direct write-off is posted for the loss amount. Because a direct write-off does not affect risk provision position, then the reduction of the risk provision position must be made using an (additional) reset posting.

• RBD processing based on sample customizing (B): Reset and direct write-off

Because both the appropriation (12/31) and the inclusion of the risk provision requirement (01/31) are in the same settlement period (04/01 of previous calendar year - 03/31 of current calendar year), the loss on receivables cannot be achieved using usage of the risk provision position. A direct write-off is posted for the loss amount. Because a direct write-off does not affect risk provision position, then the reduction of the risk provision position must be made using an (additional) reset posting.

• RBD processing based on sample customizing (C): Usage

Because the inclusion of the losson receivables (01/31) is in a new RBD settlement period to the original appropriation (12/31), the system sets up a usage posting for the loss on receivables amount. This means that the risk provision position built up in previous RBD settlement periods is used for the loss on receivables; the usage posting reduces the risk provision position atthe same time.

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 7561 Date: 20240416 Time: 224829     sap01-206 ( 122 ms )