How To Fix C/070 - Invalid value for number of IDOCs per LUW (download). Set standard value

SAP Error Message - Details

• Message type: E = Error

• Message class: C/ -

• Message number: 070

• Message text: Invalid value for number of IDOCs per LUW (download). Set standard value

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 C/070 - Invalid value for number of IDOCs per LUW (download). Set standard value ?

  The SAP error message C/070 "Invalid value for number of IDOCs per LUW (download). Set standard value?" typically occurs when there is an issue with the configuration of the IDoc processing parameters in the SAP system. This error is related to the number of IDocs that can be processed in a single Logical Unit of Work (LUW) during the download process.
  Cause:
  
  Invalid Configuration: The error is often caused by an invalid or unsupported value set for the number of IDocs that can be processed in one LUW. This value is usually defined in the configuration settings for IDoc processing.
  System Limitations: The system may have limitations on the number of IDocs that can be processed at once, and the configured value exceeds this limit.
  Custom Settings: If there are custom settings or modifications in the IDoc processing logic, they may lead to this error if not properly configured.
  
  Solution:
  
  
  Check Configuration:
  
  Go to transaction code WE20 (Partner Profiles) and check the settings for the relevant partner profile.
  Look for the parameter that specifies the number of IDocs per LUW. Ensure that it is set to a valid value (typically between 1 and 999).
  
  
  
  Set Standard Value:
  
  If the value is invalid, you can set it to a standard value. A common standard value is 1 or 10, depending on your business requirements.
  After making changes, save the configuration and test the IDoc processing again.
  
  
  
  Review Documentation:
  
  Consult the SAP documentation or help files related to IDoc processing to understand the recommended settings and limitations.
  
  
  
  Check for Custom Code:
  
  If there are any custom developments or enhancements related to IDoc processing, review them to ensure they are not causing the issue.
  
  
  
  System Parameters:
  
  Check system parameters related to IDoc processing in transaction RZ10 or RZ11 to ensure they are set correctly.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test to ensure that the IDocs are processed without errors.
  
  
  
  Related Information:
  
  IDoc Basics: IDocs (Intermediate Documents) are used in SAP for data interchange between systems. Understanding how IDocs work can help in troubleshooting related issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE02 (Display IDoc), WE19 (Test IDoc), and WE21 (Port Definition) for monitoring and testing IDocs.
  SAP Notes: Check for any SAP Notes related to IDoc processing and the specific error message for additional guidance or patches.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or technical team for further assistance.