Message type: E = Error
Message class: 1Q - Messages In-House Banking
Message number: 100
Message text: Payment order &2 in bank area &1 - all items posted
All items in payment order &2 have been posted in bank area &1. If the
transaction currency of the ordering party item or recipient item
differs from the account currency, the system generates an additional
payment order for the currency swap in each case. You can use report
program IHC_BCAREVPO_ALV01 to list the additional payment orders for
currency swaps.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message "1Q100 Payment order &2 in bank area &1 - all items posted" typically indicates that there is an issue with a payment order in the specified bank area. This error usually arises when you are trying to process a payment order that has already been fully processed or posted, meaning that all items associated with that payment order have already been accounted for in the system.
Cause:
- Payment Order Already Processed: The payment order you are trying to work with has already been fully processed, and no further actions can be taken on it.
- Incorrect Status: The payment order may be in a status that does not allow for further processing (e.g., it may be marked as completed or canceled).
- Data Integrity Issues: There may be inconsistencies in the data related to the payment order or bank area.
Solution:
- Check Payment Order Status: Verify the status of the payment order in question. If it has already been processed, you will not be able to make further changes or process it again.
- Review Related Documents: Look at the documents associated with the payment order to ensure that all items have been correctly posted and that there are no outstanding items.
- Consult with Finance Team: If you believe there is an error or if you need to reverse or adjust the payment order, consult with your finance or accounting team for guidance on how to proceed.
- Use Transaction Codes: Utilize relevant transaction codes (like F110 for automatic payment transactions) to check the payment run and see if there are any discrepancies.
- Error Logs: Check the error logs or application logs for more detailed information about the error and any related issues.
Related Information:
If the issue persists after following these steps, it may be necessary to escalate the problem to your SAP support team or consult with SAP directly for further assistance.
1Q062 &1 Due to the error the document cannot be posted completely
Self-Explanatory Message Since SAP believes that this specific error message is ...
1Q050 No entries stored in TBKKIHB4 for account &1/&2
Self-Explanatory Message Since SAP believes that this specific error message is ...
1Q101 Collective bank transfers are not supported for split postings
Self-Explanatory Message Since SAP believes that this specific error message is ...
1Q102 Exch. rate entry not permitted for EMU currencies - rate will be deleted
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.