How To Fix MM358 - Customer-defined fields for structure &1 have not been transferred

SAP Error Message - Details

• Message type: E = Error

• Message class: MM - Messages for material master maintenance and Customizing

• Message number: 358

• Message text: Customer-defined fields for structure &1 have not been transferred

What causes this issue?

Customer-defined fields have not been written to the database for one
of the following reasons:
The key fields for the table parameters (EXTENSIONIN and EXTENSIONINX)
do not contain entries or do not agree.
The key fields for the table parameters do not agree with the key
fields for the corresponding import parameters (for example, PLANTDATA
and PLANTDATAX or in the case of the material number
HEADDATA-MATERIAL).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Make sure that the key fields are the same for all relevant parameters.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MM358 - Customer-defined fields for structure &1 have not been transferred ?

  The SAP error message MM358 indicates that there are customer-defined fields in a structure that have not been transferred during a specific operation, typically related to material management processes. This error often arises in scenarios involving data transfer, such as during the creation or modification of materials, vendor data, or other related master data.
  Cause:
  
  Missing Custom Fields: The error usually occurs when there are custom fields defined in a structure that are expected to be populated but are not being transferred correctly.
  Inconsistent Data Model: If the data model in the source system does not match the expected structure in the target system, it can lead to this error.
  Configuration Issues: There may be issues in the configuration of the custom fields or the data transfer process itself.
  User Exits or BAdIs: If there are user exits or Business Add-Ins (BAdIs) that are supposed to handle the transfer of these fields but are not implemented or are incorrectly implemented, this can lead to the error.
  
  Solution:
  
  Check Custom Field Configuration: Verify that the custom fields are correctly defined in the system. Ensure that they are included in the relevant structures and that their data types and lengths are correctly set.
  Data Transfer Logic: Review the logic used for data transfer. If you are using a custom program or a standard transaction, ensure that the custom fields are being populated and transferred correctly.
  Implement User Exits/BAdIs: If applicable, implement or adjust the user exits or BAdIs that are responsible for handling the transfer of these custom fields. Ensure that they are correctly coded to populate the fields as needed.
  Debugging: Use debugging tools to trace the data transfer process and identify where the custom fields are being omitted. This can help pinpoint the exact location of the issue.
  Consult Documentation: Review any relevant documentation or notes from SAP regarding the specific transaction or process you are working with. There may be known issues or additional configuration steps required.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues related to the MM358 error. SAP frequently releases notes that address specific error messages and provide guidance on how to resolve them.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in the process, such as MM01 (Create Material), MM02 (Change Material), or others related to material management.
  Custom Development: If your organization has custom developments, ensure that they are aligned with the standard SAP processes and that they handle custom fields appropriately.
  
  By following these steps, you should be able to identify the cause of the MM358 error and implement a solution to resolve it. If the issue persists, consider reaching out to SAP support or consulting with an SAP expert for further assistance.