List of BADIS Used in Collection management:

Difference Between BADI and User Exits

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP
System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries
often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors,
partners, and customers to attach additional software to standard SAP source code without having to modify the
original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if
one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer
solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as
country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created
at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect
enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have
to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once
and enhancements that can be used actively by any number of customers at the same time. In addition, Business AddIns can be defined according to filter values. This allows you to control add-in implementation and make it dependent
on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a
manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all
of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques
behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?What is the
system landscape?
1) Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.

2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.

3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
Ex:- 'Development server'-->'Quality server'---> 'Production server'.

List BADIS in BP collection management

1.CVI_BBPCUSTOM_MAPPER
Mapping for SRM-Specific Enhancements

2.CVI_MAP_BUSINESS_ADDRESS
Implementation: BADI: Data Assignment BP-Customer/Vendor/Contact Person
(You can use this BAdI to change and extend field assignments for Customer/Vendor Integration. You can adjust the
assignments between business partner/customer/vendor and contact person data, and the assignments between
business partner relationship data and contact person data.)

3.IF_EX_CVI_MAP_BANKDETAILS.
( You can use this BAdI to change and extend field assignments for bank data in Customer/Vendor Integration. You can
adjust the assignments between bank details for the business partner and bank details for the customer/vendor).

4.IF_EX_CVI_MAP_CREDIT_CARDS
(You can use this BAdI to change and extend field assignments for customer integration. You can adjust the assignments
between payment cards for the business partner and payment cards for the customer master record)

5.CVI_MAP_TITLE_DIRECT .
( You can use this BAdI to change and extend field assignments for Customer/Vendor Integration. You can adjust the
assignments between the form of address for the business partner and the form of address for the customer/vendor. This
is possible only for the direction customer/vendor to business partner)

6.CVI_MAP_BP_CATEGORY
(Determine Business Partner Category Based on Form of Address)

7.CVI_DEFAULT_VALUES_CLASSIC
(With this BAdI you can set default fields for Customer/Vendor Integration that are relevant for synchronization, such as
general data and company code data for the customer, when creating data in the direction business partner to
customer/vendor.)

8.MAP_PARTNER_2_CUSTOMER:
Mapping of business partner number (Partner-ID) to customer number (KUNNR)

9.MAP_CUSTOMER_2_PARTNER:
Mapping of customer number (KUNNR) to business partner number (Partner-ID)

10.MAP_CONTACTPARTNER_2_CONTACT:
Mapping of business partner number (Partner-ID) to contact person number (PARNR)

11.MAP_CONTACT_2_CONTACTPARTNER:

Mapping of contact person number (PARNR) to business partner number (Partner-ID)

Work list Add in BADI

1.UDM_S_WORKLIST_ITEM_ATTR_C
Example 1: You calculate additional key figures for the business partner and display these in the worklist. You distribute
additional indicators from Accounts Receivable Accounting to Collections Management and display these in the worklist.

2. UDM_COLL_AMT_C
You use it to define the amount to be collected

3. UDM_WL_ITEM_DISP_C
With this BAdI, you can fill customer-specific fields when displaying worklist items

4. UDM_EXT_RATING_C
You use it to determine which external rating of the business partner is to be displayed in the worklist

Data Distribution BADI

1. FDM_COLL_SEND_ITEMS
You use it to provided additional data for the distribution of data in Collections Management</. This data can be prepared
for the collection specialists worklist and displayed there. It can also be used to prioritize the business partners to be
contacted
2. FDM_COLL_DETERMINE_BRANCH
The method DETERMINE_BRANCH is used to determine the relevant customer from an invoice item for Collections
Management, differently from the behavior of the SAP standard system.
3. IF_FDM_COLL_DETERMINE_PAYER
With this Business Add-In (BAdI) you can determine an alternative payer from an invoice item for Collections Management
4. FDM_COLL_DISPLAY_DUNN_HISTORY
You can use this BAdI to implement the display of customer contacts having a contact type other thancall or visit. It is
called if the user in receivables processing wants to display details for a customer contact on the Customer Contacts tab.
The contact type is used a filter value for the BadI implementation.
5. FDM_P2P_JUDGE
With this BAdI you have two options for how you valuate promises to pay:

You can valuate a promise to pay without installment plan and specify whether is was kept, partially kept or
broken.

You specify Tolerance Days for the valuation, and so override the entries that you have made in Customizing.
This is possible for both promises to pay with or without installment plan.
6. FDM_COLL_INSTALLMENT_PLAN
You can use this Business Add-In (BAdI) to propose either an installment plan type or a standard installment plan when
you create an installment plan. You can use the method GET_DEFAULT for this. This method is called in receivables
processing if the user navigates to the user interface that allows the creation or change of an installment plan. However, it
is only called if no installment plan has yet been created for the promise to pay.
7. FDM_INST_DISTRIB_RELATIVELY
You can use this Business Add-In (BAdI) to distribute the installments of an installment plan to the invoices for which
promises to pay have been created
8. UDM_BR00000001 to UDM_ BR00000024
The implementation of all basic rules delivered by SAP is active in the standard system. You should not modify or
deactivate these basic rules. In the definition of rules, you decide which of the rules delivered by SAP and which
additionally implemented rules are to be used in strategies and therefore in SAP Collections Management.

Add ins for B.P

1. UDM_BP_PROFILE_C
By implementing this Business Add-In, you can determine, for each business partner, which collection profile is entered in
the respective master record.
2. UDM_CHNG_SGMT_DATA_C
By implementing this BAdI, you can determine, for each segment of a business partner, which collection group and
collection specialist are entered in the respective master record