A one-sided turnover on an account, which represents either a credit or a debit. A payment item can consist of one or more payment item positions with the same item ID, for example, the return of a debit memo with the corresponding return charge.
In Account Management (FS-AM) you use payment items to enter one-sided postings (such as cash deposits and withdrawals). Payment items can reach Account Management from an external payment transaction system by means of BAPI interfaces. However, you can also enter payment items directly in the dialog (see Creating Payment Items and Displaying Payment Items).
Payment items can also be generated by the posting of payment orders. For more information, see Payment Orders and Creating Payment Orders.
You can post payment items with a posting date that is after the current posting date. These payment items are called future items, and are posted on the account, but are not included in the balance.
You can use a Business Application Programming Interface (BAPI) to split the posting amount of a payment item among multiple SubFinPayt dates and/or multiple value dates (item split). In an item split, the posting amount is split among different dates for inclusion in the available amount and/or interest calculation, rather than the whole amount being included.
Payment items can be returned in the dialog, and reversal or return is possible (see Returning Payment Items). Reversals can, however, also be made via BAPI interfaces.
Payment items on special accounts with the Clearing feature can be cleared in the dialog and in a mass run (see Clearing Payment Items).
To improve the performance of the operational system, you can archive payment items and display archived payment items in the dialog (Displaying Archived Payment Items).
You can create prenotes with a transaction currency that differs from the account currency. For more information about the prerequisites and procedure, see Currency Exchange.
Payment items initiated internally or externally at first contain one position only, but it is possible to create an additional position (for example, charges) during posting. This can be the case, for example, with account settlement items.
Every payment item comprises information regarding:
The transaction type describing how the item was updated.
The medium by means of which the item or the payment order belonging to the item came to the bank.
The payment method with which the corresponding item was forwarded. This is only of relevance for payment items from payment orders.
You can differentiate between payment items according to the following criteria:
The item type: Ordering party, recipient, route, turnover
The status For more information, see Payment Item Status.
The account on which the item was posted: CpD (suspense account), other accounts.
The structure definition for the payment item comprises attributes, methods, and customer enhancements.
Attributes
This business object has the following attributes:
Own Attributes
Payment Item GUID
Position Number
Payment Item Status
Item Type
Posting Date
Value Date
Subject to Final Payment Date
Amount in Transaction Currency
Transaction Currency
Amount in Account Currency
Account Currency
Exchange Rate
Relevant to Intraday
Credit Memo
Plus/Minus Sign of Amount (Debit/Credit Indicator)
Reverse Item Indicator
Indicator: Cleared
Indicator: Value Date Calculated/Specified/Corrected
Indicator: Date of SubFinPayt Balance Predefined
Indicator: Recorded
Process
Posting Text
Payment Notes
Transaction Type
Return Reason
Medium
Payment Method
Sending System
Bank Network Affiliation
External and Internal Clearing Reference
Attributes of Other Objects
Account/Card Attributes from Contract Management
Business Partner Attributes
Payment Order Attributes
Account Settlement Attributes
Bank Statement Attributes
Payment Form Attributes
Condition Attributes
Savings Book Attributes
Attributes of Interest Penalty and of Items Relevant to Settlement
Access Limit Attributes
Amount Notice Attributes
Payment Monitoring Attributes
Product Change Attributes
Attributes of Notice on Card
Account Closure Attributes
General Ledger Attributes
Attributes of Posting Control Rules
Prenote
Reconciliation Unit
Bank Statement Agreement
In Account Management, you can use the following channels to process objects:
Dialog
Business Application Programming Interface (BAPI)
Direct Input (DI)
The following shows which methods of a payment item can be called up via which channel:
Method |
Channel |
||
---|---|---|---|
Dialog |
BAPI |
DI |
|
Create/Post |
x |
x |
x |
Return |
x |
x |
|
Transfer Post |
x |
x |
|
Reverse |
x |
x |
|
Post from postprocessing |
x |
||
Reject from postprocessing |
x |
||
Split items |
x |
||
Detail display |
x |
x |
|
Overview display |
x |
x |
|
Total of returnable items |
x |
||
Read posting dates |
x |
||
Read totals records from “item management incomings” |
x |
||
Clearing |
x |
||
Transferring items with external clearing references |
x |
x |
|
Read individual item splits |
x |
||
Read item splits |
x |
||
Adjust turnover item positions |
x |
In the dialog, you can call the following transactions:
Transaction Code |
Short Description |
---|---|
BCA_PAYMITEM_CREATE |
|
BCA_PAYMITEM_MAINTN |
|
BCA_PAYMITEM_RETURN |
|
BCA_PAYMITEM_GRETURN |
|
BCA_SB_ITEMS_02 |
|
BCA_SB_ITEMS_03 |
|
BCA_PAYMITEM_CLRNG |
|
BCA_PAYMITEM_CLRNG_R |
|
BCA_CLEARING_EXT_RUN |
|
BCA_CLEARING_RUN |
|
BCA_CLEARING_LIST |
|
BCA_PAYMITEM_CPD |
Display open items of a suspense (CpD) account |
BCA_AR_PAYMITEM_BVW |
You can call up the following methods using the BAPI Explorer:
Method |
Short Description |
---|---|
PaymentItemControl.Adjust |
Adjust turnover item positions |
PaymentItemControl.Cancel |
Reverse individual payment items |
PaymentItemControl.CreateClearing |
Posting routing items |
PaymentItemControl.CreateItem |
Post turnover items |
PaymentItemControl.CreateItemSplit |
Split items |
PaymentItemControl.CreateReceiver |
Post recipient items |
PaymentItemControl.CreateSender |
Post ordering party items |
PaymentItemControl.GetPostingDates |
Read posting date |
PaymentItemControl.PostFromPostprocessing |
Post payment items from postprocessing |
PaymentItemControl.Reject |
Reject payment Items from postprocessing |
PaymentItemControl.ReturnItems |
Return payment items |
PaymentItemControl.TransferPost |
Transfer post payment items |
PaymentItemAM.GetDetail |
Read individual payment items |
PaymentItemAM.GetDetailItemSplit |
Read individual item splits |
PaymentItemAM.GetList |
Read payment items |
PaymentItemAM.GetListByRefNo |
Read payment items for reference numbers |
PaymentItemAM.GetListItemSplit |
Read item splits |
PaymentItemAM.GetReconciliationSumsIncomings |
Read totals records from “item management incomings” |
PaymentItemAM.GetSumReturnable |
Read total of returnable payment items |
* You can also execute all the write methods in a test run.
You can migrate payment items only before the go-live of the corresponding contract with this method.
Transfer Category |
Receiver Structure |
Sender Structure |
---|---|---|
77 |
BCA_STR_ITEM_DI_IN |
BCA_STR_ITEM_DI_EXT |
71 *) |
BCA_STR_ITEM_DI_IN |
BCA_STR_ITEM_DI_EX |
Transfer category: 71 - Obsolete
You use transfer category 71 only if you can no longer change to the new transfer category 77 at short notice.
You can use Enterprise Services of the business object Bank Account Revenue Expense Entry. For more information, see SAP Help Portal at
.You are provided with the following business transaction events (BTEs) for payment items:
For an overview of the BTEs, see Customizing for Account Management (FS-AM) in the following Customizing activities:
Technical Settings - Business Transaction Events/Event Control (FS-AM)
Display Information System (P/S)
Display Information System (Process)
BTE |
Short Description |
---|---|
0BCA3270 |
Ordering party item: Report result of postprocessing to feeder system |
0BCA3280 |
Posting control check: Read data and run formal checks |
0BCA3282 |
Posting control check: Account |
0BCA3283 |
Posting control check: Value date |
0BCA3284 |
Posting control check: Limit |
00010025 |
Posting control check: Payment form |
00010026 |
Posting control check: Independent check object |
0BCA3260 |
Prepare payment items: Post |
0BCA3261 |
Prepare payment items: Park |
0BCA3262 |
Prepare payment items: Delete |
0BCA3263 |
Prepare payment items: Change |
0BCA3264 |
Prepare payment items: Release |
0BCA3265 |
Prepare payment items: Reverse |
0BCA3266 |
Prepare payment items: Generate a new document position |
0BCA3291 |
Update data |
0BCA3500 |
Currency exchange: Determine exchange rate and individual spread |
0BCA3501 |
Currency exchange: Differentiation characteristic for account derivation |
0BCA3310 |
Posting control check: Account name |
0BCA3030 |
Payment items: Determine returnable items |
0BCA3040 |
Check whether transfer postings are allowed |
0BCA3041 |
Prepare data: Redirect |
0BCA3042 |
Determine of posting text for direct charges |
0BCA3043 |
Payment items: Clear |
0BCA3044 |
Payment items: Reset |
0BCA3045 |
Create express message |
0BCA3046 |
Payment items: Open |
0BCA3047 |
Prepare data: Reversal |
0BCA3048 |
Payment items: Adjust value date |
0BCA3049 |
Limit check in the reversal |
0BCA3055 |
Payment items: Add new positions |
0BCA3060 |
Method memory entered in global memory |
0BCA3061 |
Posting control check: Notice on amount |
0BCA3062 |
Posting control check: Access limits |
0BCA3063 |
Posting control check: Lifecycle control |
0BCA3064 |
Posting control check: Overdraft protection |
0BCA3065 |
Posting control check: Plan monitoring |
0BCA3066 |
Posting control check: Currency swap |
0BCA3067 |
Posting control check: Facilities |
0BCA3070 |
Payment items: Archiving |
0BCA3080 |
Payment items: Authorization check (dialog) |
0BCA3081 |
Payment items: Authorization check (mass run) |
0BCA3085 |
Payment items: Past value dates before Interest Calculation From date |
0BCA3086 |
Posting control check: Prenote |
0BCA3090 |
Payment items: Bank network affiliation and reference fields |
0BCA3091 |
Determine original payment item |
0BCA3092 |
Payment items: Control for payment distribution |
0BCA3095 |
Payment items: Reference fields for the reversal |
0BCAAP30 |
Returned check |
0BCAAP31 |
Returned check |
0BCAAP40 |
Returned debit memo/credit memo |
0BCAAP41 |
Returned debit memo/credit memo |
0BCAAR10 |
Confirmation of non-execution: Debit memo |
0BCAAR20 |
Confirmation of non-execution: Debit memo |
0BCAAR21 |
Express message: Correspondence printing |
0BCAAR11 |
Express message: Correspondence request |
0BCAAR30 |
Confirmation of non-execution: Check |
0BCAAR31 |
Confirmation of non-execution: Check |
The system checks the authorization object F_PIT_TRT when you process payment items in the dialog. If the check finds errors, the system checks the display authorization for the account. When you process a payment item for your own account, the authorization object F_EMP_SELF is checked for the Add and Create activities.
In Customizing for Account Management (FS-AM), you can choose
, to specify that this extended authorization check is also run for the methods entered from the business objects PaymentItemControl and PaymentItemAM. The system runs only a simplified authorization check for methods that have not been entered, by using authorization object F_PIT_ACT.For more information about the authorization checks in Account Management, see Authorization Management in Account Management
Each payment item is checked for formal and material errors, regardless of whether it has been entered manually in the dialog, or has reached Account Management by means of a BAPI.
Creation of Payment Items in the Dialog
If the checks find material or formal errors subject to posting control, where the initial response according to the posting control rules is not Post, then the clerk can force the posting manually, or generate a posting control order using the rule set. Items that have errors that cannot be subjected to posting control are always rejected.
Creation of Payment Items Via BAPI
If the checks found formal errors that can be subjected to posting control or material errors, the system finds the valid initial response in the posting control rules. If the checks find errors that cannot be subjected to posting control, the system rejects the payment item. You can use the PostOrTerminate parameter when you call the BAPI to decide whether incorrect items are to be processed only for the initial response Post.
Payment item processing depends on the posting control rules, which you can specify in Customizing for Account Management (FS-AM), under .
Using Direct Input to Migrate Payment Items
You can migrate payment items only by using Direct Input. It is not possible to use a BAPI or the dialog for migration.
You can migrate payment items only before the go-live date of the account contract. The relevant check and additional checks are run in the formal check of the migrated payment item (in the function module BCA_API_PAYMITEM_CHECK ). The PostOrTerminate indicator evaluates the posting control rules, meaning that incorrect items are only processed if the response is Post. For all other responses, the items are rejected.
Each payment item has one of the following statuses:
01 In Postprocessing
02 In Release
03 Posted
05 Deleted
06 Reversed
07 Returned
For more information, see Payment Item Status.
Customizing for Account Management (FS-AM) also enables you to specify whether postings in the dialog require the agreement of up to three additional persons (the principle of dual, triple, or quadruple control). Choose Release Object PAYMITEM (Payment Item).
. The Framework for the Principle of Dual Control (CA-GTF-TS-PDC) provides these members of staff with a work item in the Business Workplace, where they can release or reject the payment item. If there is a rejection, the release processor must enter a reason for the member of staff who entered the item. In this case the payment item is automatically deleted. After its final release, the payment item is posted automatically. For more information, seeYou can specify that payment items are archived after a particular period of time (residence time) has expired. You define the residence time for each bank posting area in Customizing for Account Management (FS-AM). Choose
. You can specify separate residence times in the bank posting area for transaction types and products.You can archive payment items with the statuses Posted, Deleted, Reversed, and Returned. Additional conditions are:
You can archive payment items on suspense (CpD) accounts only if they have the Reversed status.
You can archive payment items on accounts with the Clear function only if these items have been cleared.
You can clear payment items on accounts with the Savings Book feature only once the update entry indicator has been set.
Only the payment items whose posting date and release time stamp are before the start time of the last bank statement (posting date and release time stamp) may be archived. This condition must be met for bank statement agreements of the account.
Payment items that have a posting control order due to the posting control rules may only be archived once the corresponding posting control order has reached the final status. The payment item must be archived with any posting control order that it might have.
Payment items that were generated during a settlement can only be archived once the settlement has been archived.
You can archive payment items only if there are no more items in the reconciliation totals for the posting day (totals records for item management incomings).
Payment items where the Intraday indicator is set can thus only be archived if the posting day and the value date of the payment item are before the earliest start date of the existing settlement periods for the account.
For more information about archiving, see Data Archiving and Deletion in Account Management (FS-AM).
Changes to payment items are recorded in change documents.
Correspondence requests are created when payment items are returned. Maintain the correspondence type for the confirmation of non-execution in Customizing for Account Management (FS-AM) under
.When you post returns, correspondence requests are generated. In Customizing for Account Management (FS-AM) under
, enter the correspondence type of the item-induced correspondence.Recipient and ordering party items come from the payment order. Payment orders are generated when recipient items are returned and transfer posted.
When you create payment items for payment forms, you need to specify a payment form number. This applies to recipient items and ordering party items. If there is a payment form with this payment form number that has the Created status in Account Management (FS-AM), the payment form is given the Cashed status if the payment item is posted successfully. If there is no matching payment form in Account Management (FS-AM), the system creates a new one with the status Cashed in the payment form inventory. This also applies if the payment item is still in reallocation.