Start of Content Area

Function documentationBAdIs for Dispute Case Processing  Locate the document in its SAP Library structure

Use

SAP Dispute Management provides several Business Add-Ins (BAdIs) that you can use to implement customer-specific requirements that do not require modifications (see also Customer Enhancements for SAP Dispute Management).

Features

The Dispute Case Processing of SAP Dispute Management provides you with the following BAdIs:

Business Add-In

Description

SCMG_INITIALIZE_C

Change cases during initialization

This BAdI is called up when you create a case. Here you can implement a customer-specific initialization of the case.

The BAdI is only called when you create a case in Dispute Case Processing, and not when you create a case from Accounts Receivable Accounting.

SCMG_BEFORE_VALID_C

Change cases before validation

This BAdI is always called before the system checks whether case data is correct. Here you can change case attributes according to your requirements.

This BAdI is called when you create or change a case in Dispute Case Processing and also when you create or change a case through process integration with Accounts Receivable Accounting.

SCMG_VALIDATE_C

Customer-defined validation of cases

This BAdI is always called when the system checks the case data. You can carry out customer-defined checks in this BAdI.

This BAdI is called when you create or change a case in Dispute Case Processing and also when you create or change a case through process integration with Accounts Receivable Accounting.

SCMG_CHNG_BFR_STR_C

Change cases before saving

This BAdI is called before the case data is saved to the database. Here you can change case attributes according to your requirements.

This BAdI is called when you create or change a case in Dispute Case Processing and also when you create or change a case through process integration with Accounts Receivable Accounting.

SCMG_VLDT_BFR_STR_C

Customer-defined validation before saving

This BAdI is called before the case data is saved to the database. Here you can carry out customer-specific checks.

This BAdI is called when you create or change a case in Dispute Case Processing and also when you create or change a case through process integration with Accounts Receivable Accounting.

SCMG_STORE_S

Save customer-defined data when saving cases

This BAdI is called when the case data is saved to the database. Here you can save customer-specific data in other tables on the database if you want to save this data with the case.

This BAdI is called when you create or change a case in Dispute Case Processing and also when you create or change a case through process integration with Accounts Receivable Accounting.

SCMG_AUTHORITY_C

Customer-specific authorization checks in the case

In this BAdI you can implement customer-specific authorization checks in the case if you have requirements over and above the standard authorization checks of the case.

This BAdI is called when creating, changing, and displaying a case in Dispute Case Processing and also when creating, changing, and displaying a case from Accounts Receivable Accounting.

SCMG_CASE_FCODE_S

Customer-defined functions

This BAdI is called if a function code that is not implemented in the standard system is called in Dispute Case Processing. To implement customer-defined functions for case processing, you have to define your own function key in the IMG activity Define Functions, and also implement a customer-defined function for the corresponding function code in this BAdI.

UDM_LOC_MASSACT_C

Mass activities on dispute cases

In this BAdI you can define mass activities for dispute cases. These mass activities are then available as function keys in the dispute case search and you can use them on a number of dispute cases in the results list for the search.

For more information, see the documentation for the individual BAdIs.

In addition to the BAdIs listed here, the correspondence function and the workflow integration of SAP Dispute Management provide BAdIs for customer-specific adjustments. For information on these BAdIs, see the IMG of Dispute Case Processing under:

     Correspondence ® Customer Enhancements

     Workflow ® BAdI: Trigger Events

Examples for Using BAdIs

Example

You want to make sure that when you close the case, the root cause code is entered in the case. In the BAdI SCMG_VLDT_BFR_STR_C (Customer-Defined Validation of Cases), you can check whether the case attribute root cause code has been incorrectly set to initial when the case is closed.

Example

In the dispute case, you want to offer a function key that enables the user to set the payment lock in the customer master record. To implement this, you define your own function key and implement the corresponding function in the BAdI SCMG_CASE_FCODE_S (Customer-Defined Functions).

Activities

To implement the customer enhancements, call up the corresponding BAdIs in the Customizing for Dispute Case Processing:

Subject

System

Menu Path

Customer Enhancements

System for Dispute Case Processing

Customer Enhancements

Function Profile ® Customer-Defined Functions

Correspondence ® Customer Enhancements

Correspondence ® Define and Configure Actions

Workflow ® BAdI: Trigger Events

 

 

End of Content Area