SAP How to solve error Tables TCURM and T001W inconsistent



When facing the SAP error M3820 Tables TCURM and T001W inconsistent; contact your systems administrator, most likely during material creation in MM01, the issue is most likely that the plant hasn't been assigned to the company code.

As described in the Performance Assistant, first step is to check the assignment of plants to company code.

In SPRO, find Enterprise Structure > Assignment > Logistics General > Assign plant to company code

Once in the transaction, create a new entry :

Add the values necessary namely, the plant and the company code :

A customizing request will be necessary to proceed :

And that's it ! The material creation can now proceed.

Tables TCURM and T001W inconsistent

When getting the error Tables TCURM and T001W inconsistent; notify your systems administrator, simply solve it by going to customization transaction SPRO > Enterprise Structure > Assignment > Logistics General > Assign plant to company code, and add an entry for the plant and company code that are facing the issue Tables TCURM and T001W inconsistent; notify your systems administrator.

Tables TCURM and T001W inconsistent; notify your system administrator

T001W table in SAP

The T001W table in SAP is the plant table in SAP, it contains all the plants defined on the current client.

Company code table in SAP

The table T001 is the company code table in SAP, it contains all the company codes defined on the current client, and belongs to FI  Financial Accounting ‌  module.

What is the SAP table TCURM?

The table TCURM is stored in the  SAP system ‌  in version 4.6C or higher. This table contains the current status of the dependent documents for a material master, i.e. if there were already changes to this material since it was last checked out in transaction CU50/CA10 TEMPLOY .

What is the SAP table T001W?

The table T001W is a master data location which was introduced in 4.7A and higher with the standard package RSUPPORT. In this article it's only used to store the current status of materials for a specific plant. The material master record can be found via segment TEMPLO and plant KSTAD.

What happens if the status of a material in table TCURM and T001W is inconsistent?

When you open transaction code CU50/CA10 TEMPLOY or CU51/CA11 TUPLAN, an error occurs on outstanding dependent documents. Because, when entering one of these transactions, the material master record will be read from table T001W. The dependent documents are then checked using TCURM. If there are any changes to these materials since they were last checked out or SAP has no information in TCURM about the material, an error occurs when entering CU50/CA10 TEMPLOY or CU51/CA11 TUPLAN, respectively.

What causes the inconsistency between TCURM and T001W?

The extension of document type DI01 within the period since the materials were last checked out leads to this inconsistency, i.e. if changes are entered for this document type during this time (PKDI01), which is the case with standard document types. For example, if a purchase order is created during this time and approved, the status of this material changes from checked out to completed or confirmed. In transaction CU50/CA10 TEMPLOY, it is then no longer possible to enter new dependent documents since an error will occur when posting.

S/4HANA SAP Materials Management Introduction video training





assignment,  ⏧ code,  ⏧ combination,  ⏧ company,  ⏧ creation,  ⏧ customization,  ⏧ error,  ⏧ issue,  ⏧ material,  ⏧ MM01

Comments (3)

 2021-11-05 -  jorge ir
Perfect boss, fixed
 2021-11-10 -  Ph.D. Tanatsugu
Regarding the contradiction between TCURM and T001W, does it mean that there is a contradiction (missing) in the original instance (Instance of ISO 13584-32) for table data generation? »  More information on this link
 2021-11-12 -  admin
Not necessarily, but it does mean that the two tables are not always updated in sync.

Leave a comment