Kontakt

Ansicht
Dokumentation

FARR_BADI_CHANGE_TYP - BAdI: Change Type Determination

FARR_BADI_CHANGE_TYP - BAdI: Change Type Determination

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the Revenue Accounting (FI-RA) component. You can use this BAdI to determine a performance obligation change type when a contract is changed.

This BAdI is called when the revenue accounting contract management performs a contract change.

When a change is made to a contract that involves a price change, you can use this BAdI to determine whether a prospective change or a retrospective change should be made to each performance obligation (POB) when accommodating this change.

The system passes pre-defined POB change types to the BAdI in the changing parameter RESULT. These POB change types are determined because the contract management can perform certain changes only using a specific POB change type. Do not overwrite, redetermine or delete these pre-defined POB change types.

The POB change type determination BAdI must always return a change type for all POBs which are passed to the BAdI through the importing parameter POBNEWDATA. The POB change type must be either ‘R’ (Retrospective Change) or ‘P’ (Prospective Change) but never empty.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

The system pre-defines a retrospective POB change type for the following changes

  • A new POB is created
  • A POB is deleted
  • A POB structure (such as a compound structure) is changed
  • The start date of a time-based POB is changed
  • The start date of a time-based POB is empty
  • The deferral method of a time-based POB is changed
  • The effective date of the change is earlier than the start date of a time-based POB
  • The end date of a time-based POB is changed to a date earlier than the last contract change
  • The end date of a time-based POB is changed, and a prospective change was performed before the old end date
  • The POB is a billing element
  • The process is in Operational Migration mode
  • A new POB is added. A change is made to this POB which is then performed on the effective date of the POB creation

The system pre-defines a prospective POB change type for the following changes

  • The contract is terminated early
  • CL_FARR_CHANGE_TYPE_DETN_BADI

The fallback class implementation determines a retrospective change type for the following changes

  • The transaction price of a POB is changed to 0
  • The transaction price, original transaction price, start date, end date, deferral method, and quantity of a POB are not changed, but any of the following fields of the POB are changed: SSP, SSP range percentage, SSP range amount, residual flag, or prevent allocation flag.

The fallback class implementation determines a prospective change type for all other POBs except for those with a pre-defined change type.

BAdI method documentation:

  • IF_FARR_CHANGE_TYPE_DETN=> DETERMINE_CHANGE_TYPE

For information about implementing BAdIs as part of the Enhancement Framework, go to the SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then select Product Assistance. On the SAP Help Portal, choose the SAP NetWeaver Library: Function-Oriented View->Application Server->Application Server ABAP->Application Development on AS ABAP->ABAP Customer Development->Enhancement Framework.






Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 4039 Date: 20240523 Time: 192300     sap01-206 ( 65 ms )