Supported BAdIs

SAP Business Add-Ins (BAdIs) are used to adapt SAP software to specific requirements. They can be inserted into the system to accommodate user requirements that are not included in the standard delivery.

Business Process Flows

  • BADI_UJ_BPF_SETUSER - Provides the performer and reviewer of a BPF activity. This BAdI applies to both Business Process Flows and Work Status.

  • BADI_UJ_BPF_REVIEW_VALIDATION - Overrides the system logic if the current user is able to approve or reject a BPF activity. This BAdI is triggered when the activity list is displayed and the user chooses Approve or Reject as a reviewer.
  • BADI_UJ_BPF_REVIEW_LOGIC - With this BAdI you can implement custom logic. It is triggered when the user chooses Approve or Reject.
  • BADI_UJ_BPF_SUBMIT_LOGIC - With this BAdI you can implement custom logic. It is triggered when the user chooses Submit.

Script Logic

  • BADI_UJ_CUSTOM_LOGIC - With this BAdI you can implement custom calculation logic. It is triggered from script logic.

  • BADI_UJCTRL_RUN_CONTROL (Enhancement spot UJCTRL_RUN_CONTROL) - Allows you to write your own control logic via ABAP.

SQE

BADI_UJ_SQE_POST_PROCESS
  • Method POST_PROCESS - Triggered after data is read from the database. You can implement custom logic to manipulate the data before it is sent to the frontend.
  • Method CUSTOMIZE_PROPERTIES - Triggered by master data properties in the BAdI implementation, before a web report is displayed. You can change the member description and input enablement of Planning and Consolidation web reporting.

Write Back

BADI_UJR_WRITE_BACK - Triggered when the write back module is started. The data sent from other modules is sent to the BAdI interface and you can manipulate that data within the BAdI implementation. The processed data goes through all standard validations and is posted to BW.

Data Manager

  • BADI_UJD_RETRACT - Triggered from Data Manager. You can use this BAdI to export Planning and Consolidation data to an external source, for example, to write planning data back to ECC for budget control.
  • BADI_UJD_ROUTINE - Triggered during transformation when loading data from an external data source. You can use this BAdI to run complex data transformations which are not possible with a transformation file.

Validation

BADI_UJ_VALIDATION_RULE_LOGIC - Triggered by the write back module. You can use this BAdI to validate input data with ABAP code instead of defining validation rules.

Security

  • BADI_UJE_DYNAMIC_DAP - Triggered after a static data access profile (DAP) setting is read from the database. You can use this BAdI to dynamically define data security for a user and reduce the number of static DAPs to be created.
  • UJE_DIM_PROCESSED_BADI - Triggered after dimension master data is processed. Can be used to automatically update DAP settings based on a change in the master data.

Journals

BADI_UJJ_CALCULATED_AMOUNT - Triggered when you save or post a journal. Can be used to generate additional journal entries.

Work Status

  • BADI_UJ_BPF_SETUSER - You can implement customized logic that provides the owner and manager for work status. This BAdI applies to both Business Process Flows and Work Status.

  • UJW_LOCKOUT_SCHEDULE_BADI - Triggered when the work status is checked by internal models. Can be used to provide work status lock information programmatically.

Parameter

BADI_UJ_PARAM_CHANGE - Triggered when a user changes a parameter in IMG. Mainly used by Planning and Consolidation internal logic to apply specific checks.