Ansicht
Dokumentation
FARR_CHANGE_MODE_DET - BAdI: Determination of Contract Change for Performance Obligations
General Material Data General Data in Customer MasterThis documentation is copyright by SAP AG.
This Business Add-In (BAdI) is used in the Revenue Accounting (FI-RA) component. You can use this BAdI to determine the change type of contract changes for performance obligations (POB). Change types include a change of estimates, contract modification, and an attribute change from the inception date without price reallocation.
Based on price allocation methods, POBs in a contract are sorted into two categories, each using a method to determine the change type:
- DETERMINE_CHANGE_MODE
- This method is for POBs that are included in the allocation of the contractual price (excluding POBs marked as Exclude from Allocation and lower-level POBs under such POBs). All allocation-relevant POBs in the contract must apply the same change type; either a change of estimates, contract modification, or an attribute change from the inception date without price reallocation.
- DETERMINE_CHANGE_MODE_EX_ALLOC
- This method is for POBs that are excluded from the allocation of the contractual price (those marked as Exclude from Allocation and lower-level POBs under such POBs). These POBs do not share in the allocation of the contractual price. Therefore, different change types can be applied.
If this BAdI is not implemented, the system determines the change type as a change of estimates or contract modification by default. The system determination process is explained below:
First, the system determines the change type as a change of estimates when one or more of the following changes occur:
- Update the POB Exclude from Allocation attribute from True to False or from False to True without any allocation difference.
- Change the estimated quantity of the POB.
- Update the residual allocation of the POB.
- Change the standalone selling price (SSP), SSP currency, or SSP tolerance amount without any change to the quantity, duration, or price.
- Change the SSP tolerance percentage.
- Change the contractual price of all allocation-relevant POBs to 0.
Secondly, if a change of estimates is not determined using the criteria from the first step, the system determines that the change type is contract modification when one or more of the following changes occur:
- Change or switch the pricing condition types without total contractual price changing.
- Add a new POB with an SSP greater than 0, an SSP tolerance that is not equal to 0, or with a contractual price that is not equal to 0.
- Delete a POB.
- Change the SSP, SSP currency, or SSP tolerance amount with a quantity, price, or duration change.
- Change the contractual price of a POB (unit-distinct or non-unit-distinct) that is from operational documents, whereby there is at least one open POB in the contract.
- Create an invoice that changes the contractual price and there is at least one open POB in the contract.
Note: If each POB has more than one change, the system determines the POB change type based on the change that appears first in the above change of estimates change list or contract modification change list. For example, if a POB is excluded from price allocation and the SSP is changed, the system determines the POB change type as change of estimates due to the former change.
However, some changes can only be determined outside the BAdI as a change of estimates. For more information, see Contract Change -> Determining the Contract Change Type -> Determining the Change Type outside the BAdI.
When the change type is not determined as a change of estimates or contract modification, it is applied as an attribute change from the inception date without price reallocation. For more information, see Contract Change -> Determining the Contract Change Type -> Default Change Types for a Change from the Inception Date without Reallocation.
Additionally, changes can be determined via the user interface. However, determination via the user interface will be overridden by determination outside the BAdI. For more information, see Contract Change -> Determining the Contract Change Type -> Determining the Change Type via the User Interface.
In the contract level, contract change types are determined according to combinations of POB change types. See the following table for examples:
| POB1 Change Type | POB2 Change Type | Contract Change Type | ||
|---|---|---|---|---|
| Change of Estimates | Change of Estimates | Change of Estimates | ||
| Change of Estimates | Contract Modification | Change of Estimates | ||
| Attributes Change from the | ||||
| Change of Estimates | Inception Date Without Price | Change of Estimates | ||
| Allocation | ||||
| Contract Modification | Change of Estimates | Change of Estimates | ||
| Contract Modification | Contract Modification | Contract Modification | ||
| Attributes Change from the | ||||
| Contract Modification | Inception Date Without Price | Contract Modification | ||
| Allocation | ||||
| Attributes Change from the | ||||
| Inception Date Without Price | Change of Estimates | Change of Estimates | ||
| Allocation | ||||
| Attributes Change from the | ||||
| Inception Date Without Price | Contract Modification | Contract Modification | ||
| Allocation | ||||
| Attributes Change from the | Attributes Change from the | Attributes Change from the | ||
| Inception Date Without Price | Inception Date Without Price | Inception Date Without Price | ||
| Allocation | Allocation | Allocation |
For more information about standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
BAdI method documentation:
For information about implementing BAdIs as part of the Enhancement Framework, see SAP Library for SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View->Application Server->Application Server ABAP->Application Development on AS ABAP->ABAP Customer Development->Enhancement Framework.
ABAP Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 9611 Date: 20240523 Time: 191059 sap01-206 ( 112 ms )
