How To Fix FTR_TEX1336 - Invalid split maintenance for commodity &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_TEX1 - Messages for raw exposures

• Message number: 336

• Message text: Invalid split maintenance for commodity &1

What causes this issue?

Invalid split maintenance for the commodity.

System Response

If the units of measure for the component commodity and the master
commodity are the same or if both the units of measure are in the same
dimension, you need to enter the split percentage.
If the units of measure for the component commodity and master commodity
are different or in different dimensions, a split ratio needs to be
entered.
<ZH>Example</>
If a line item commodity ID has a unit of measure KG and if a sub item
commodity has a unit of measure KG or G or TO or LB, the split
percentage needs to be filled. KG, G, TO, LB units all belong to the
same dimension. In cases where the units of measure belong to different
dimensions, the split quantity needs to be filled.

How to fix this error?

You can use transaction
<DS:TRAN.FTREX7>FTREX7</> to correct the split maintenance.

Procedure for System Administrators

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 FTR_TEX1336 - Invalid split maintenance for commodity &1 ?

  The SAP error message FTR_TEX1336 ("Invalid split maintenance for commodity &1") typically occurs in the context of financial transactions involving commodities in SAP's Treasury and Risk Management module. This error indicates that there is an issue with the split maintenance settings for a specific commodity.
  Cause:
  
  Invalid Split Configuration: The error often arises when the split maintenance settings for the commodity in question are not properly configured. This could be due to missing or incorrect entries in the configuration tables.
  Commodity Type Issues: The commodity type may not be set up correctly in the system, leading to inconsistencies in how splits are handled.
  Data Inconsistencies: There may be inconsistencies in the data related to the commodity, such as incorrect master data or transaction data.
  Missing Authorizations: Sometimes, the user may not have the necessary authorizations to perform the split maintenance for the specified commodity.
  
  Solution:
  
  
  Check Split Maintenance Configuration:
  
  Navigate to the configuration settings for the commodity in question. Ensure that the split maintenance settings are correctly defined.
  Verify that the commodity type is correctly set up and that all necessary parameters are filled in.
  
  
  
  Review Master Data:
  
  Check the master data for the commodity to ensure that all required fields are populated correctly.
  Look for any inconsistencies or missing information that could lead to this error.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to perform split maintenance for the commodity. If not, contact your SAP security administrator to grant the required permissions.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific error message for additional troubleshooting steps or patches that may address the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with the error message details and any relevant transaction data.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FTR_EDIT for editing financial transactions or FTR_COMMODITY for managing commodities.
  SAP Notes: Search for SAP Notes related to FTR_TEX1336 in the SAP Support Portal for any known issues or fixes.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.