How To Fix FMLGD_INFO355 - Cmpny code &1/trnsn type &2; gen. error message for debit memos not def.

SAP Error Message - Details

• Message type: E = Error

• Message class: FMLGD_INFO -

• Message number: 355

• Message text: Cmpny code &1/trnsn type &2; gen. error message for debit memos not def.

What causes this issue?

No general error message (FMLGD/002) is created for debit memos for
company code &V1& and transaction type &V2&.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Create an error message for processing debit memos <ZH>002</> for
company code &V1& and transaction type &V2&.
To do this, use IMG activity <DS:SIMG._ISPSFM_H_MSGNR>Define Error
Handling</>.
Note that you are not allowed to specify a posting rule, business
transaction code, +/- sign and amount for this error message.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FMLGD_INFO355 - Cmpny code &1/trnsn type &2; gen. error message for debit memos not def. ?

  The SAP error message FMLGD_INFO355 typically indicates that there is a configuration issue related to debit memos in the financial module of SAP. This error occurs when the system cannot find the necessary settings for the specified company code and transaction type for debit memos.
  Cause:
  
  Missing Configuration: The most common cause of this error is that the debit memo transaction type has not been properly configured in the system for the specified company code.
  Incorrect Transaction Type: The transaction type being used may not be valid for debit memos.
  Authorization Issues: There may be authorization issues preventing the system from accessing the necessary configuration settings.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that are causing the system to fail in processing the debit memo.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > Accounts Receivable and Accounts Payable > Business Transactions > Incoming Invoices > Define Transaction Types for Incoming Invoices.
  Ensure that the transaction type for debit memos is defined for the relevant company code.
  
  
  
  Define Debit Memo Transaction Type:
  
  If the transaction type is missing, you will need to create it. Make sure to define the necessary parameters and settings for debit memos.
  
  
  
  Review Authorization:
  
  Check if the user has the necessary authorizations to create or process debit memos. This can be done by reviewing the user roles and authorizations in the system.
  
  
  
  Check Master Data:
  
  Ensure that the customer/vendor master data is correctly set up and that there are no inconsistencies that could lead to this error.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, test the configuration by attempting to create a debit memo again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBD2 (for defining transaction types) or OBD3 (for checking existing transaction types).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Refer to SAP documentation for detailed steps on configuring financial transactions, especially for accounts receivable and payable.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP Financials for further assistance.