This is a one-sided turnover on a current account, which represents either a credit or a debit memo. A payment item can consist of one or more payment item positions with the same item identification (item ID), for example, the return of a debit memo with the corresponding return charges.
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 via 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 Orderand 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.
Payment items can be returned in online processing; both reversals and returns are 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 reduce the amount of work of the feeder system, you can archive payment items and display archived payment items online (Displaying Archived Payment Items).
Payment items initiated internally or externally at first contain one position only, but it is possible to create an additional position (e.g. charges) during posting. which can be the case, for example, with account balancing items.
All payment items contain the following information:
· The transaction type describing how the item was updated.
· The medium via which the item or the payment order belonging to the item was brought to the bank.
· The payment method by 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:
· By the item type: ordering party, recipient, route, turnover; and by the
· status.
· The account to which the item was posted: CpD (suspense) account, clearing account, other accounts.
The structure definition for the payment item is divided into attributes, methods and customer enhancements.
This business object has the following attributes:
Own attributes
· Payment item ID
· Position number
· Status of payment item (posted, in release, in postprocessing, reversed)
· Item type
· Posting date
· Value date
· Date subject to final payment
· Amount in transaction currency (*)
· Transaction currency (*)
· Amount in account currency
· Account currency
· Exchange rate (*)
· Indicator: Relevant to intraday
· Plus/minus sign of amount (debit/credit indicator)
· Indicator: Reverse item
· Indicator: Cleared
· Indicator: Recorded
· Process
· Posting text
· Payment notes
· Transaction type
· Return reason
· Medium
· Payment method
· Channel
· Network affiliation
· External and internal clearing reference
* FS-AM does not support the conversion of different currencies.
Reference attributes
· 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 the interest penalty and items relevant to settlement
· Access limit attributes
· Amount notice attributes
· Payment monitoring attributes
· Product change attributes
· Notice on card attributes
· Account closure attributes
· General ledger attributes
· Posting control rules attributes
· Prenote
· Reconciliation unit
· Bank statement agreement
Objects can generally be processed via the following three channels in Account Management:
· 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 |
|
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 |
|
|
Transfer items with external clearing references |
|
x |
x |
The following transactions can be called up in dialog processing mode:
Transaction Code |
Short Description |
F9I4 |
|
F9I7 |
|
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 |
Displaying Open Items of a Clearing Account |
BCA_PAYMITEM_CPD |
Displaying 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.Cancel |
Reversing Individual Payment Items |
PaymentItemControl.CreateClearing |
Posting Routing Items |
PaymentItemControl.CreateItem |
Posting Turnover Items |
PaymentItemControl.CreateReceiver |
Posting Recipient Items |
PaymentItemControl.CreateSender |
Posting Ordering Party Items |
PaymentItemControl.GetPostingDates |
Reading Posting Dates |
PaymentItemControl.PostFromPostprocessing |
Posting payment items from postprocessing |
PaymentItemControl.Reject |
Rejecting payment Items from postprocessing |
PaymentItemControl.ReturnItems |
Returning Payment Items |
PaymentItemControl.TransferPost |
Transfer Posting Payment Items |
PaymentItemAM.GetDetail |
Reading Individual Payment Items |
PaymentItemAM.GetList |
Reading payment items |
PaymentItemAM.GetListByRefNo |
Reading Payment Items for Reference Numbers |
PaymentItemAM.GetSumReturnable |
Reading Total of Returnable Payment Items |
PaymentItemAM.Get ReconciliationSumsIncomings |
Reading Totals Records from Item Management Incomings |
* You can also execute all methods as 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 are provided with the following business transaction events (BTEs) for payment items.
For an overview of the BTEs, see the Customizing settings in the following IMG activities:
Technical Settings ® Business Transaction Events/Event Control (FS-AM)
· ®Display Information System (P/S)
· ® Display Information System (Process)
BTE |
Short Description |
00010010 |
Ordering party item: Report result of postprocessing to previous/feeder system |
00010020 |
Posting control check: Formal check |
00010021 |
Posting control check: Business partner |
00010022 |
Posting control check: Account |
00010023 |
Posting control check: Value date |
00010024 |
Posting control check: Limit |
00010025 |
Posting control check: Payment forms |
00010026 |
Posting control check: Independent check object |
00010030 |
Prepare payment item: Post |
00010031 |
Prepare payment item: Park |
00010032 |
Prepare payment item: Delete |
00010033 |
Prepare payment item: Change |
00010034 |
Prepare payment item: Release |
00010035 |
Prepare payment item: Reverse |
00010036 |
Prepare payment item: Generate new document item |
00010041 |
Data update: Execute |
00010110 |
Posting control check: Account name |
00010210 |
Payment item: Authorization check (online) |
0BCA3030 |
Payment item: Determine returnable items |
0BCA3040 |
Check whether transfer postings are permitted |
0BCA3041 |
Preparing data: Redirection |
0BCA3042 |
Determination of posting text for direct charges |
0BCA3043 |
Payment items: Clearing |
0BCA3044 |
Payment items: Resetting |
0BCA3045 |
Create express message |
0BCA3046 |
Payment items: Open |
0BCA3047 |
Preparing data: Reversal |
0BCA3055 |
Payment items: Adding new positions |
0BCA3060 |
Method memory entered in global memory |
0BCA3061 |
Posting control check: Amount notice |
0BCA3062 |
Posting control check: Access limits |
0BCA3063 |
Posting control check: Life cycle control |
0BCA3070 |
Payment item: Archiving |
0BCA3080 |
Payment item: Authorization check (online) |
0BCA3081 |
Payment item: Authorization check (mass run) |
0BCA3085 |
Payment item: Past value dates before ‘interest calculation from’ date |
0BCA3086 |
Posting control check: Prenote |
0BCA3090 |
Payment item: Bank network affiliation and reference fields |
0BCA3095 |
Payment items: Reference fields for 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 print job |
0BCAAR11 |
Express message: Correspondence request |
0BCAAR30 |
Confirmation of non-execution: Check (payment form) |
0BCAAR31 |
Confirmation of non-execution: Check (payment form) |
The system checks the authorization object F_PIT_TRT when you process payment items in dialog mode. 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 the Customizing for Account Management (FS-AM), you can choose Basic Settings ® Authorizations ® Specify Authorization Check in BAPIs, 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 on the authorization checks in Account Management (FS-AM), see Authorization Management in Account Management
Every payment item is first subjected to a series of formal and material checks, regardless of whether it has been entered manually in dialog processing, or has reached Account Management via BAPI.
Creation of Payment Items in Dialog Processing
If the checks find material errorsor 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 first response Post.
Payment item processing depends on the posting control rules, which you can specify in the Customizing for Account Management (FS-AM) under Item Management ® Posting Control Rules.
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: Explanation of the Status of Payment Items.
The Customizing for Account Management (FS-AM) also enables you to specify whether postings (dialog processing) can be entered only after the agreement of up to another three additional persons (the principle of dual, triple, or quadruple control). Choose Item Management ® Basic Functions ® Release. The Framework for the Principle of Dual Control provides these people with a work item in the Business Workplace, where they can opt to 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, see Release Object PAYMITEM (Payment Item).
You 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 the Customizing for Account Management (FS-AM) under Item Management ® Basic Functions ® Archiving ® Define Residence Time for Payment Items (Object PAYMITEM). 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 Reversed. 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 end 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 may 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 on 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 the Customizing for Account Management (FS-AM) under Item Management ® Returns ® Define Returnable Transaction Types.
When you post returns, correspondence requests are generated. You maintain the correspondence type for the item-triggered correspondence in the Customizing for Account Management (FS-AM). Choose Item Management ® Basic Functions ® Transaction Types and Transaction Type Groups ® Maintain and Assign Transaction Types for Payment Items.
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.