How To Fix REXCJP343 - Incorrect cons. sharing meth. (&) defined in table for fixed unit prices

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCJP - Localization Flexible Real Estate Japan

• Message number: 343

• Message text: Incorrect cons. sharing meth. (&) defined in table for fixed unit prices

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 REXCJP343 - Incorrect cons. sharing meth. (&) defined in table for fixed unit prices ?

  The SAP error message REXCJP343 indicates that there is an issue with the configuration of the cost sharing method for fixed unit prices in the project management module. This error typically arises when the system encounters an inconsistency or an invalid setting in the configuration tables related to cost sharing methods.
  Cause:
  
  Incorrect Configuration: The cost sharing method defined in the relevant configuration tables does not match the expected values or is not set up correctly.
  Missing Entries: There may be missing entries in the configuration tables that define how costs should be shared among different cost objects or project elements.
  Incompatible Settings: The settings for fixed unit prices may not be compatible with the defined cost sharing method.
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the configuration settings for project management (transaction code SPRO).
  Navigate to the relevant section for defining cost sharing methods and ensure that the settings are correct.
  Verify that the cost sharing method is properly defined and that it corresponds to the expected values.
  
  
  
  Review Table Entries:
  
  Use transaction SE11 to check the relevant tables (e.g., T_REXCJP) for cost sharing methods.
  Ensure that the entries for the cost sharing method are complete and correct.
  
  
  
  Adjust Project Settings:
  
  If the project settings are causing the issue, review the project definition and ensure that the cost sharing method aligns with the project’s requirements.
  
  
  
  Consult Documentation: 
  
  Refer to SAP documentation or help resources for guidance on the specific cost sharing methods and their configurations.
  
  
  
  Testing: 
  
  After making changes, test the configuration by attempting to execute the transaction that previously generated the error to ensure that the issue is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (for configuration), SE11 (for table maintenance), and CJ20N (for project management).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional insights or solutions.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the problem persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.