Hierarchy
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
| Data Element | XFINI_INDPAY |
| Short Description | Processing Status for Payment Specification |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFINI_IP | |
| 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 | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Status |
| Medium | 15 | Proc. Status |
| Long | 20 | Processing Status |
| Heading | 10 | Status |
Documentation
Definition
A payment specification is only interpreted by the payment run or can only be used as selection in the payment lot if the processing status Can Be Used for Payment is set.
The approval workflow can, for example, be defined such that all changes to a payment specification that does not yet have this status are not to be approved and the approval procedure only starts once this status has been set. This would enable sequential further processing of the payment specification by different clerks without every single step having to be approved.
The check for the completeness of the data is only performed once this status has been set. This means that incomplete payment specifications (for example, missing payer, missing payment method) can be entered and completed over time.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20050428 |
| SAP Release Created in | 473 |
