The following activity codes (sorted by type) may have an impact on the way the function operates :
VII :
International transfers
The following general parameters may change the way the function is working :
AMTVIR1 (defined at level Company) : Threshold 1 payment balance
AMTVIR2 (defined at level Company) : Threshold 2 payment balance
AMTVIR3 (defined at level Company) : Threshold 3 PB countervalue
CTLPAZ (defined at level User) : Pay approval control
DEPMGTMOD (defined at level Company) : Discount management mode
FLGPAZ (defined at level Site) : Payment approval management
DATDEP (defined at level Company) : Date for the calc of discounts
DENCRG (defined at level Company) : Late charge payment attribute
DENDEP (defined at level Company) : Customer early paymt./discount
DENINSRCP (defined at level Company) : Prepayment rec accounting code
DENINSSEN (defined at level Company) : Prepayment iss accounting code
DENPAY (defined at level Company) : Supplier early paymt./discount
DENSPG (defined at level Company) : Payment exp accounting code
DENTAK (defined at level Company) : Payment rec accounting code
DEPDUDDAT (defined at level Company) : Due dates in discount section
PAYUNALL (defined at level Company) : Unalloc. payments considered
PPYCONSCTL (defined at level Company) : Prepayment control
SOICPT (defined at level Company) : Statement posting
The sequence numbers used to number the documents managed by this function are :
PY1 : Payment Receipts
PYL : Payment Lot
The sequence number assignment function defines the sequence number which is used
An authorization can be granted for this function to limit the processes to a company or a site.
The following miscellaneous tables are used by the function. They must be populated if necessary :
Miscellaneous table number 3 : Unpaid reason
Miscellaneous table number 313 : SEPA - Payment nature
The payment transaction is a grouping key of the payments based on the sense of these payments and their payment mode (miscellaneous table no. 3: Checks, Drafts, Transfers, etc.).
For a payment transaction, x linked payment modes are defined. These links are used to match the open items on the invoice posted upon payment transaction (see the documentation Payment conditions ).
The set up of these payment transactions (see the documentation Payment transactions) makes it possible to define:
Whatever the payment transaction, when a payment is automatically generated through the automatic proposal, it is included in an entry batch. This facilitates the transaction tracking and management and also corresponds to a milestone for selection during the management of the next phases.
Depending on the payment transaction setup, the batch number and content can be displayed and adjusted.
It is possible to integrate the user code to the counter using the Complement field.
For each company, and possibly for each site, it is necessary to define the linked bank(s) (refer to the documentation on Bank account and Bank allocations).
The following tables are implemented by the function :
Table |
Table description |
---|---|
BANK [BAN] |
|
BPARTNER [BPR] |
|
BPCUSTOMER [BPC] |
|
BPSUPPLIER [BPS] |
|
CACCEDEF [CDE] |
|
CADSP [DSP] |
|
COMPANY [CPY] |
|
FACILITY [FCY] |
|
GACCDUDATE [DUD] |
Open items |
PAYMENTD [PYD] |
Payment lines |
PAYMENTH [PYH] |
Payment header |
PINVOICE [PIH] |
|
PORDER [POH] |
|
SINVOICE [SIH] |
Sales invoices |
SORDER [SOH] |
|
TABCHANGE [TCH] |
Currency rate table |
TABCUR [TCU] |
|
TABPAYTYP [TPY] |
|
TABUNIT [TUN] |