Message type: E = Error
Message class: PM - Extended Payment Functions
Message number: 260
Message text: First amount column already reached
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Cash deconcentration always starts from the current date and goes up to
five days after the start date. The optimized account balances are
displayed in a maximum of 6 columns. The balances on the current date
are always on the far left so it is not possible to scroll any further
to the left.
Error message extract from SAP system. Copyright SAP SE.
PM260
- First amount column already reached ?The SAP error message PM260, which states "First amount column already reached," typically occurs in the context of the SAP Plant Maintenance (PM) module when you are trying to enter or modify data in a transaction that involves amounts, such as in maintenance orders or service notifications.
Cause: The error usually arises when: Data Entry Issues: You are attempting to enter an amount in a column that is not allowed or has already been filled. Configuration Settings: The system configuration may restrict the number of amount columns that can be used in a particular transaction. User Authorization: The user may not have the necessary permissions to enter or modify amounts in the specified fields.
Solution: To resolve the PM260 error, you can try the following steps: Check Data Entry: Ensure that you are entering the amount in the correct field. Review the layout of the transaction screen to confirm that you are not trying to enter data in a
Get instant SAP help. Sign up for our Free Essentials Plan.
PM259
Clearing account &1 for company code &2 not maintained in G/L acct master
What causes this issue? The G/L account entered does not exist for the respective company code in the G/L account master record (table SKB1).System R...
PM258
G/L account &1 for company code &2 not maintained in G/L account master
What causes this issue? The G/L account entered does not exist for the respective company code in the G/L account master record (table SKB1).System R...
PM261
Last amount column already reached
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
PM262
Loops in the hierarchy structure not allowed
What causes this issue? Cash deconcentration occurs within one of the tables corresponding to one of the header trees: One or more bank accounts have...
Click on this link to search all SAP messages.