How To Fix FC028 - A dunn.notice for each dunn.area is not defined for comp.code &

SAP Error Message - Details

• Message type: E = Error

• Message class: FC - FI configuration error messages

• Message number: 028

• Message text: A dunn.notice for each dunn.area is not defined for comp.code &

What causes this issue?

You have specified a dunning area for company code &V1&. If you want to
create dunning notices for each dunning area for this company code, you
must also specify this when configuring the dunning program.

How to fix this error?

Select the "Dunning notices per dunning area" field for company code
&V1& when configuring the dunning program. You find this under the menu
option <LS>Environment -> Company code data</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FC028 - A dunn.notice for each dunn.area is not defined for comp.code & ?

  The SAP error message FC028 indicates that a dunning notice for a specific dunning area is not defined for the company code in question. This typically occurs in the context of accounts receivable when the system is trying to generate dunning notices but cannot find the necessary configuration for the specified company code.
  Cause:
  
  Missing Dunning Configuration: The most common cause of this error is that the dunning area has not been defined for the specified company code in the dunning configuration settings.
  Incorrect Dunning Area: The dunning area specified in the dunning run may not be correctly assigned to the company code.
  Dunning Procedure Not Assigned: The dunning procedure may not be assigned to the customer account or the company code.
  
  Solution:
  To resolve the error FC028, follow these steps:
  
  
  Check Dunning Configuration:
  
  Go to the SAP transaction code OBD2 (Dunning Areas).
  Verify that the dunning area is defined for the relevant company code.
  If it is not defined, you will need to create a new entry for the dunning area and assign it to the company code.
  
  
  
  Assign Dunning Procedure:
  
  Use transaction code OBD3 to check if the dunning procedure is assigned to the customer account.
  Ensure that the dunning procedure is correctly assigned to the customer master data.
  
  
  
  Review Dunning Settings:
  
  Go to transaction code FBMP (Dunning Procedure) to review the dunning procedure settings.
  Ensure that all necessary parameters are set up correctly for the dunning area and company code.
  
  
  
  Test Dunning Run:
  
  After making the necessary changes, perform a test dunning run using transaction code F150 to ensure that the dunning notices can be generated without errors.
  
  
  
  Related Information:
  
  Dunning Areas: Dunning areas are used to categorize customers for dunning purposes. Each dunning area can have its own dunning procedure and settings.
  Dunning Procedures: These define how dunning notices are generated, including the frequency, intervals, and content of the notices.
  Transaction Codes:
  
  OBD2: Define Dunning Areas
  OBD3: Assign Dunning Procedures
  FBMP: Dunning Procedure Configuration
  F150: Dunning Run
  
  
  
  By following these steps and ensuring that the necessary configurations are in place, you should be able to resolve the FC028 error and successfully generate dunning notices for the specified company code.