Hierarchy
⤷ IS-U-IDE (Application Component) Intercompany Data Exchange
⤷ EE_DEREG_INV (Package) Payment Management in a Deregulated Environment
Basic Data
Data Element | E_PAYM_METHOD_CREDIT |
Short Description | Payment Method for Credit (Aggregated) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PYMET_KK | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table | TFK042Z |
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 | PymtMethCr |
Medium | 15 | PymtMethodCred. |
Long | 20 | Pymt Method Credit |
Heading | 20 | Pymt Method Credit |
Documentation
Definition
Specification of a repayment method for credit items from the aggregated bill
Use
In accordance with the agreement with the supplier, you can already specify a repayment method when creating the aggregated bill for the credit items.
Dependencies
As default, the system does not check whether the specified repayment method is also maintained as a valid repayment method in the Aggr. Posting Contract Account Service Provider transaction in the corresponding contract account for the supplier.
If reversal entries from the DFKKTHI database table are aggregated separately, and a credit results from the aggregation, then the specified repayment method is not transferred to the corresponding item. An aggregated billing document consisting only of reversal entries can never be paid out without first performing a check.
For further information, see the documentation for event R205. Event R205 allows you to define customer-specific checks (for example, to check whether the specified repayment method is valid).
Example
History
Last changed by/on | SAP | 20050411 |
SAP Release Created in | 600 |