How To Fix FI_E059 - Document type &1 for BL does not exist. See long text

SAP Error Message - Details

• Message type: E = Error

• Message class: FI_E - Message Class for FM English Developers

• Message number: 059

• Message text: Document type &1 for BL does not exist. See long text

What causes this issue?

You are using the funds management system integrated with the budgetary
ledger (BL). For postings in the BL, an FI-GL document type is
required.
The default document type for the budgetary ledger is &V1&. If desired,
customers can use this default document type. However, this document
type has not been created for this company code through customizing.

System Response

The budgetary ledger processor cannot post this document.

How to fix this error?

You have the following options>
If you want to use the default document type for the budgetary ledger,
use transaction OBA7 to create the document type &V1&. You can access
it using the link defined below.

<DS:TRAN.OBA7>Execute maintain "Document Types"</>
ENDIF
If you need to use a document type other than &V1& for the budgetary
ledger postings, follow the procedure described below.

Procedure for System Administrators

Create a function module similar to FM_LEDGER_DOCUMENT_TYPE_ASSIGN.
Then replace this default function module name with your own one in the
business transaction events (BTE) table TPS31, PROCS = '00108012', APPL
= 'IS-PS'.
You have to program all validations regarding the consistency of the
derived document types, such as the existing document type, existing
ranges in company code, and so on.
For additional information check the source code from the standard
function module FM_LEDGER_DOCUMENT_TYPE_ASSIGN but do not modify this
code.
Since the budgetary ledger interface table is passed as a parameter,
more complex document type determination can be programmed, based, for
example, on the company code, value type, fund, or funds center.

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FI_E059 - Document type &1 for BL does not exist. See long text ?

  The SAP error message FI_E059 indicates that a specific document type for a business transaction (in this case, a "BL" or "Billing Document") does not exist in the system. This error typically arises when trying to post a financial document or perform a transaction that requires a specific document type that has not been defined or configured in the system.
  Cause:
  
  Missing Document Type: The document type specified in the transaction does not exist in the system configuration.
  Incorrect Configuration: The document type may have been incorrectly configured or deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the document type.
  Custom Development: If there are custom developments or enhancements, they may not be correctly referencing the document type.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > Financial Accounting Global Settings (New) > Document Types > Define Document Types.
  Verify if the document type for "BL" exists. If it does not, you may need to create it.
  
  
  
  Create Document Type:
  
  If the document type is missing, you can create a new document type by following the steps in the configuration menu.
  Ensure that you assign the correct number range and other relevant settings.
  
  
  
  Check User Authorizations:
  
  Ensure that the user has the necessary authorizations to use the document type. This can be checked in the user roles and profiles.
  
  
  
  Review Custom Code:
  
  If there are any custom programs or enhancements, review the code to ensure that it is correctly referencing the document type.
  
  
  
  Consult Documentation:
  
  Check the long text of the error message for additional details or specific instructions related to the error.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like OBY6 (for document types) or SPRO (to access the configuration menu) to navigate to the relevant settings.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.