Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TPM_TRDT - Legacy Data Transfer Messages
Message number: 112
Message text: Liability position: Quantity info. and value info. are not consistent
The valuation area-independent data record for the liability position:
company code &V1&, ID number &V2&, securities account &V3& in table
TRDTT_DATA_SEC is inconsistent.
For liability positions, the quantities (units and nominals) must be
positive and the purchase value must be negative. For ID numbers
redeemed in installments, the accumulated repayments must be positive.
The legacy data transfer cannot be carried out.
Correct the data record in table TRDTT_DATA_SEC.
Error message extract from SAP system. Copyright SAP SE.
TPM_TRDT112
- Liability position: Quantity info. and value info. are not consistent ?The SAP error message TPM_TRDT112, which states "Liability position: Quantity info. and value info. are not consistent," typically occurs in the context of Treasury and Risk Management (TRM) when there is a mismatch between the quantity and value information of a liability position. This inconsistency can arise from various reasons, and addressing it requires a systematic approach.
Causes:
- Data Entry Errors: Incorrect manual entries during transaction processing can lead to discrepancies between quantity and value.
- Incomplete Transactions: If a transaction is not fully processed or is in a pending state, it may not reflect accurate quantity and value.
- Currency Conversion Issues: If there are issues with currency conversion rates or if the rates have changed after the transaction was recorded, this can lead to inconsistencies.
- System Configuration Issues: Incorrect configuration in the system settings related to Treasury management can lead to mismatches.
- Posting Errors: Errors during the posting of transactions can result in inconsistent data being recorded in the system.
Solutions:
- Review Transaction Data: Check the specific transaction that triggered the error. Ensure that the quantity and value are correctly entered and consistent.
- Reprocess Transactions: If the transaction is incomplete or in a pending state, try to complete or reprocess it to ensure that all data is correctly updated.
- Check Currency Settings: Verify the currency settings and conversion rates used in the transaction. Ensure that they are correct and consistent.
- Run Consistency Checks: Use SAP tools to run consistency checks on the relevant data. This can help identify and rectify discrepancies.
- Adjust Configuration: If the issue is due to system configuration, consult with your SAP Basis or configuration team to ensure that the settings are correct.
- Consult Documentation: Refer to SAP documentation or notes related to TPM_TRDT112 for any specific guidance or patches that may address the issue.
- Contact SAP Support: If the issue persists and cannot be resolved internally, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to identify the root cause of the TPM_TRDT112 error and implement a solution to resolve it.
Get instant SAP help. Sign up for our Free Essentials Plan.
TPM_TRDT111
Entry in table: TRDTT_DATA_SEC/TRDT_VADATA_SEC has no liab.pos. indicator
Trados Memory = TRWhat causes this issue? In table TRDTT_DATA_SEC or TRDTT_VADATA_SEC the entries for company code &V1& and securities accou...
TPM_TRDT110
Entry in table TRDTT_POS_SEC is not indicated as a liability position
Trados Memory = TRWhat causes this issue? The entry in database table TRDTT_POS_SEC for company code &V1& and securities account &V2&...
TPM_TRDT113
Original nominal amount and nominal amount with plus/minus signs
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
TPM_TRDT114
Nominal amount and orig. nominal amount are not consistent (see long txt)
Trados Memory = TRWhat causes this issue? A nominal amount of &V2& &V1& is entered in the data record. According to the original nom...
Click on this link to search all SAP messages.