How To Fix REXCJP160 - Customizing Table for Contract type has not been filled (CN Type: &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCJP - Localization Flexible Real Estate Japan

• Message number: 160

• Message text: Customizing Table for Contract type has not been filled (CN Type: &1)

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 REXCJP160 - Customizing Table for Contract type has not been filled (CN Type: &1) ?

  The SAP error message REXCJP160 indicates that the customizing table for the contract type has not been filled for a specific contract type (denoted by &1). This error typically occurs in the context of SAP Project System (PS) or Contract Management when trying to create or process contracts.
  Cause:
  The error is caused by the absence of necessary configuration in the customizing tables for the specified contract type. This means that the system does not have the required settings to process the contract type you are trying to use. The contract type might not be defined in the relevant customizing tables, or it may not be properly linked to the necessary settings.
  Solution:
  To resolve this error, you need to ensure that the customizing settings for the contract type are correctly defined. Here are the steps to do this:
  
  
  Access Customizing Settings:
  
  Go to the SAP Easy Access screen and enter the transaction code SPRO to access the SAP Reference IMG (Implementation Guide).
  
  
  
  Navigate to the Relevant Path:
  
  Follow the path: Project System -> Structures -> Contracts -> Define Contract Types.
  Alternatively, you may need to check under Project System -> Project Planning -> Define Contract Types depending on your specific configuration.
  
  
  
  Check Contract Type Configuration:
  
  Look for the contract type that corresponds to the one indicated in the error message (&1).
  Ensure that all required fields are filled out correctly. This includes settings related to the contract type, such as the status, allowed transactions, and any other relevant parameters.
  
  
  
  Save Changes:
  
  If you make any changes or add the missing configuration, be sure to save your changes.
  
  
  
  Test the Process Again:
  
  After making the necessary adjustments, try to execute the process that triggered the error again to see if the issue is resolved.
  
  
  
  Related Information:
  
  Authorization: Ensure that you have the necessary authorization to make changes in the customizing settings.
  Transport Requests: If you are working in a development environment, remember to transport your changes to the quality and production environments as needed.
  Documentation: Refer to SAP documentation or help files for more detailed information on contract types and their configuration.
  Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who specializes in Project System or Contract Management.
  
  By following these steps, you should be able to resolve the REXCJP160 error and ensure that your contract type is properly configured in the system.