Hierarchy
⤷ IS-U-CA (Application Component) Contract Accounts Receivable and Payable
⤷ EE30 (Package) IS-U: Contract Accounts Receivable and Payable
Basic Data
Data Element | ETHPPM |
Short Description | Payment Process for Billing on Behalf of Third Parties |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | THPPM_KK | |
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 | Paymt Proc |
Medium | 15 | Paymnt Process |
Long | 20 | Bank payment method |
Heading | 8 | PayProc. |
Documentation
Use
In deregulated markets, it can be the case that a service provider receives a bill for customer services from another service provider, or a service provider takes over the bill creation for another service provider.
In these cases, the service provider responsible for the customer bill (for example, the supplier), must make payments to the other service providers (for example, distributors).
There are the following payment methods for this:
- Customer payment
- Advance payment
- Sole provider
Payment after bill receipt, directly by FI. In this case the payment is not processed by FI-CA. The billing party declares all its customer receivables as revenues.
In IS-U, different processes are implemented depending upon the payment method. The payment method is determined for each contract indirectly by the payment class.
The sole provider payment method is typically mapped by a one-contract model, whilst a two-contract model is proposed for advance payment and customer payment. The reason for this is the necessity to divide payments to third parties in the G/L by different company codes.
Dependencies
Example
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 462 |