SAP ABAP Data Element BDM_XARRANGED_FOR_PAY (Arranged for Payment)
Hierarchy
☛
PI_BASIS (Software Component) Basis Plug-In
⤷
CA (Application Component) Cross-Application Components
⤷
PI_FIN_BDM (Package) Dispute Management - Basis
PI_BASIS (Software Component) Basis Plug-In⤷
CA (Application Component) Cross-Application Components⤷
PI_FIN_BDM (Package) Dispute Management - Basis
Basic Data
| Data Element | BDM_XARRANGED_FOR_PAY |
| Short Description | Arranged for Payment |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BDM_XARRANGED_FOR_PAY | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | XARRANGED_PAY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 6 | Arrngd |
| Medium | 15 | Arranged |
| Long | 0 | |
| Heading | 25 | Arranged for Payment |
Documentation
Definition
Indicator: Arranged for Payment.
This indicator is set if an incoming payment method is entered in an open item or if an open item is in a payment order.
Dependencies
If an incoming payment method and a payment block are entered in the open item, and the payment block prevents the automatic payment transaction, then the item is interpreted as being not arranged for payment.
Example
In the following instances an open item is interpreted as not being arranged for payment:
- An incoming payment method and the payment block '*' have been entered in the item. (This means that the item is ignored in the payment program.)
- An incoming payment method and a payment block are entered in an item that cannot be changed in payment proposal processing.
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in | 2005_1_620 |
