Page 982 "Payment Registration Setup"
Base Application · Microsoft.Bank.Payment
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Bank.Payment · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Payment Registration Setup |
| SourceTable | Payment Registration Setup |
| PageType | StandardDialog |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| General | Journal Template Name | Journal Template Name | Specifies the name of the journal template that the Payment Registration window is based on. from the table field |
| Journal Batch Name | Journal Batch Name | Specifies the name of the journal batch that the Payment Registration window is based on. from the table field | |
| Balancing Account Type | Bal. Account Type | Specifies the type of account that is used as the balancing account for payments. The field is filled according to the selection in the Journal Batch Name field. from the table field | |
| Balancing Account | Bal. Account No. | Specifies the account number that is used as the balancing account for payments. from the table field | |
| Use this Account as Default | Use this Account as Def. | Specifies if the account in the Bal. Account No. field is used for all payments. | |
| Automatically Fill Date Received | Auto Fill Date Received | Specifies if the Date Received and the Amount Received fields are automatically filled when you select the Payment Made check box. from the table field |
Triggers
OnOpenPage, OnQueryClosePage
Relations
- source table Table 980 “Payment Registration Setup”
Called by
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 1070 “MS - PayPal Standard Mgt.” (1 call:
RunPaymentRegistrationSetupForce → (object)) - Codeunit 980 “Payment Registration Mgt.” (1 call:
RunSetup → (object))
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Payment Registration Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.