How To Fix FTI_LDB_MESSAGE391 - Default value not found; enter a valid package size

SAP Error Message - Details

• Message type: E = Error

• Message class: FTI_LDB_MESSAGE - Messages for TR OLTP Reporting Using Logical Databases

• Message number: 391

• Message text: Default value not found; enter a valid package size

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTI_LDB_MESSAGE391 - Default value not found; enter a valid package size ?

  The SAP error message FTI_LDB_MESSAGE391 with the description "Default value not found; enter a valid package size" typically occurs in the context of data processing or data extraction, particularly when working with the SAP Financial Transaction Interface (FTI) or similar modules that involve data packages.
  Cause:
  This error usually arises when the system is unable to find a default value for the package size parameter that is required for processing a transaction or data extraction. The package size is a critical parameter that determines how much data is processed in a single transaction or batch. If the system cannot retrieve a default value, it may indicate:
  
  Configuration Issues: The default settings for package size may not be configured correctly in the system.
  Missing Customization: The necessary customization or settings for the specific transaction or data extraction process may not have been set up.
  Data Integrity Issues: There may be issues with the data being processed, such as missing or incorrect entries that prevent the system from determining a valid package size.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration Settings:
  
  Navigate to the relevant configuration settings in SAP (e.g., SPRO) and verify that the default package size is defined for the relevant module or transaction.
  Ensure that the settings align with your organization's data processing requirements.
  
  
  
  Enter a Valid Package Size:
  
  If the system prompts for a package size, manually enter a valid value that is appropriate for the data being processed. This value should be based on your organization's data handling practices.
  
  
  
  Review Customization:
  
  If you are using a custom program or report, check the code to ensure that it correctly retrieves or sets the package size. You may need to consult with a developer or SAP consultant if you are not familiar with the code.
  
  
  
  Data Validation:
  
  Review the data being processed to ensure that it is complete and valid. Look for any anomalies or missing entries that could affect the processing.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific module you are working with. There may be specific guidelines or known issues related to package size settings.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights or patches if this is a known issue.
  
  
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may need to use specific transaction codes to access configuration settings (e.g., SPRO for configuration).
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.