Table 3307 "PA Billing Task Setup"
PayablesAgent · Microsoft.Agent.PayablesAgent
Across versionsobsolete pending since 28.0
- BC23-28not present
- BC29-30present
PayablesAgent · Microsoft.Agent.PayablesAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| DataClassification | SystemMetadata |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | Monetization tracking is moved to platform. |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Code | Code[10] | Specifies the code for the billing task. This is a setup table, the field should be blank. | |
| 10 | Billing Task ID | Guid | Specifies the ID of the billing task. | |
| 11 | Billing Task Start DateTime | DateTime | Specifies the date and time the billing task will start. | |
| 12 | Last Billing Update At | DateTime | Specifies the date and time the last billing task was run. |
Keys
- Key1: Code (clustered)
Deprecations
- object: Pending 28.0 (#if not CLEANSCHEMA28), “Monetization tracking is moved to platform.”
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). 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: "table", object_name: "PA Billing Task Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.