FSCM Collection and Dispute Management Data Model

[MurlidharKhatri]

To build a foundational understanding of how SAP Collection Management is structured within the data model, it's essential to recognize the key components and their relationships. Here's a high-level overview:

o effectively manage overdue items, a collection specialist relies on data from the FSCM Collection Management system, which is sourced from the Accounts Receivable (AR) system. This data, posted in FI_GL, is periodically replicated between the AR system and FSCM, ensuring up-to-date information through regular delta updates.

Here’s a high-level overview of key aspects:

1. Business Partners (BP):

   • Role: Central to the data model, business partners are created with the Collection Management role (UDM000).
   • Linkages: They are linked to collection profiles and segments.
   • Updates: Collection segments, groups, and specialists must be updated in BP.

2. Collection Profiles (UDMBPPROFILE):

   • Definition: Defined at the header level, these profiles outline the collection strategy for each business partner.
   • Rules: Rules within the profile allocate points to collectible items, which then appear in the collection worklist based on priority.

3. Collection Segments (UDMBPSEGMENTS):

   • Specification: At the item level, segments specify the collection group and specialist responsible for managing receivables.
   • Practical Use: Segments divide collection activities among specialists, ideal for global organizations assigning different specialists by country or region.

4. Receivables Management:

   • Function: Involves evaluating and prioritizing customers using collection strategies to ensure proactive management of accounts receivable.

5. Integration with Other Modules:

   • Comprehensive Approach: Collection Management integrates with other SAP modules like Credit and Dispute Management, providing a holistic approach to managing financial supply chains.

This structured approach ensures that collection specialists have the necessary data and strategies to manage overdue items effectively.

Let's focus on the data model aspect now.

Relation ship of collectible items and Worklist

Filtered Customer AR totals, such as items that are not due, are enriched with valuation scores and risk categories. Additionally, customer events at various points in time are captured with an extra line in the table. These events include:

• Promised
• Disputed
• Dunning
• Highest dunning level
• Amount arranged/paid
• Broken promise
• Resubmission
• Resubmission reason
• Customer-defined disputes

This comprehensive data provides a rich view of historical customer behavior.

Promise to Pay and Attributes

In Table UDM_P2P_ATTR, you can find detailed information such as Promised Amount, Amount Paid, Promised for Date, Promised on Date, Last Payment, P2P Status, and P2P Level, which indicates the number of promises made. Additionally, contact person details are available.

Using the internal key of a dispute case, you can check Table SCMG_T_CASE_ATTR for attributes like Table Type (P2P/Dispute Case info), Created on, Completed on, Status (Active, Confirmed, Voided), and various System Statuses.

Resubmission

For resubmission details, check Table UDM_RSM_ATTR using Customer and Company Code. This table provides information such as Created by, Segment, Resubmission Date/Time, Reason, and links with BSEG.

Customer Contact

Customer contact moments are recorded during customer interactions, dunning, and account statements. Using the Business Partner or technical key of a worklist item (Table UDM_WL_ITEM), you can fetch customer contact details from Table UDM_CCT_ATTR by entering the technical key "WORKITEM_ID". This will provide information on Customer Contact person, contact direction (I/O), Contact Type, Result ID, Reached, Date/Time, etc.

Dispute Case

From Table UDMCASEATTR00, you can obtain details for Customer and Company Code, including original disputed amount, current disputed amount, Amount Paid, Amount Credited, Amount Written Off, Customer Disputed, System Status, and Collector. Using the internal key of the dispute case from UDMCASEATTR00, check Table SCMG_T_CASE_ATTR for attributes like Table Type (Dispute Case info), Created on, Completed on, Status (Active, Confirmed, Voided), and various System Statuses.

Notes

Notes are typically created during the following moments:

• Dispute Case Creation from worklist
• Promise to Pay
• Resubmission

To fetch notes, go to Table UDM_CCT_ATTR where customer contact details are available. Based on the GUID from UDM_CCT_ATTR, retrieve notes from Table STXD.

Disputed Objects

By concatenating Company Code + document number (with leading zeros) + Fiscal Year + Item number (from BSID+BSAD), you can obtain the GUID of disputed objects from Table FDM_DCOBJ. Use the UUID to check Tables SCMG_T_CASE_ATTR or UDMCASEATTR00 for dispute case details.

Depending on the classification, the key varies:

• BUPA/INFOBUPA: Customer number
• INFOBILL: Invoice No
• Classification NTS: Resubmission-related notes

Values can be determined using the function module UDM_RSM_GET_MULTI_RFC.

From the AR side, you can find details such as Open Item, Posting Date, Baseline Date, Due Date, Clearing Date, Disputed status, P2P, Dunned, Maximum Dunning Level, Account Statement, and Dispute Origin (e.g., Price mismatch).

Please do reach out to me for any further questions.