Resolve Data Inconsistencies with the Collections Worklist

  • by Kim Ciesla, Senior Financial Consultant and Instructor, SAP America
  • December 18, 2013
Learn how to delete company codes that aren’t necessary for the collections process in an SAP system. By deleting unnecessary company codes and their associated receivables data, you are able to run the collections programs more efficiently and keep only relevant data within the collections worklist.
Learning Objectives

After reading this article, you’ll know how to:

  • Delete company codes that no longer pertain to the collections process
  • Maintain data integrity throughout the process
Key Concept

The cornerstone of Collections Management is the collections worklist, the listing of all past-due customers ranked based on a specific formula. SAP Collections Management is a component of SAP Receivables Management (formerly SAP Financial Supply Chain Management).

Collectors in a company call past-due customers based on the results of a collection worklist that is generated each day. If the list is inaccurate, customers whose accounts are past due may not get a call or customers whose accounts are not past due, may get a call in error. When working accurately, the collection worklist reconciles with the values in the Customer Line Item Display (transaction code FBL5N). There are several reasons why this could get out of sync, including bad program runs or incorrect configuration.

Consider a scenario in which the collection worklist was not updated properly, causing data inconsistencies. An analysis of the values on the collections worklist (transaction codes UDM_SUPERVISOR / UDM_SPECIALIST) compared with the values in Process Receivables and the customer line-item display (transaction FBL5N) shows discrepancies in the values. The log in Distribution of Data to Collections Management (program FDM_COLL_SEND_ITEMS) returns messages that company codes do not exist in the logical system and that processing was terminated.

Kim Ciesla

Kim Ciesla is a senior financial consultant and instructor with SAP America, supporting and implementing SAP R/3 Financials. Kim has worked at SAP America for 19 years and has developed expertise in the areas of Collections and Dispute Management, lockbox, Accounts Receivable, Accounts Payable, and General Ledger, with an extensive background in cross-application functionality. In her free time, she is a world traveler, visiting 41 countries to date.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.