Input Help for Payment Details 
Use
By marking/not marking the two fields entitled Payment activity and Payment request in the payment details of the financial transaction with a cross, you choose whether the payment program should be used for payment and if yes, which payment program should be used for the payment. Depending on whether a field is marked with a cross or not, you get the corresponding posting logic.
Number for posting logic |
Payment activity |
Payment Request |
1 |
No |
No |
2 |
No |
Yes |
3 |
Yes |
No |
4 |
Yes |
Yes |
Depending on how you made your choice (Table 1), you must go to input of payment details. You find out from the following table which entries are required or optional and which ones are not considered:
|
Possible entries | ||||
Entry fields |
1 |
2 |
3 |
4 |
Direction |
X |
X |
X |
X |
Currency |
X |
X |
X |
X |
Validity |
O |
O |
O |
O |
Flow type |
O |
O |
O |
O |
Name |
||||
House bank |
O |
O |
O |
O |
Account ID |
O |
O |
O |
O |
Payment activity |
X |
X | ||
Payer/Payee |
O |
O |
O | |
Partner bank |
X |
O |
X | |
Payment method |
O |
|||
Payment method supplement |
O |
O |
O | |
Payment request |
XC |
XC | ||
Single payment |
OC |
OC | ||
Same direction |
O |
O | ||
Determine grouping definition |
O |
O | ||
Payment methods |
X |
X | ||
X X = Input required
O O = Input optional
C C = Input only included if it does not contradict Customizing of flow types.
/: / = Input not considered