Report 99001048 "Planning Availability"
Base Application · Microsoft.Manufacturing.Reports
Across versionsobsolete pending since 27.0
- BC23-24present
- BC251 procedures added, 1 procedures changed
- BC26unchanged
- BC271 procedures added, 1 procedures changed
- BC28unchanged
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Manufacturing.Reports · captioned “Planning Availability (Obsolete)” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Planning Availability (Obsolete) |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Basic, Suite |
| ObsoleteState | Pending |
| ObsoleteTag | 27.0 |
| ObsoleteReason | This report has been deprecated and will be removed in a future release. |
Events published
OnCollectData(var TempPlanningBuffer: Record "Planning Buffer" temporary; Selection: Boolean)+ BC25 (integration)- subscribers: Codeunit 6497 “Serv. Planning Availability” OnCollectData
OnRequisitionLineOnBeforeTempPlanningBufferInsert(var TempPlanningBuffer: Record "Planning Buffer" temporary; RequisitionLine: Record "Requisition Line")+ BC27 (internal)- subscribers: Codeunit 99000875 “Prod. Order Availability Mgt.” OnRequisitionLineOnBeforeTempPlanningBufferInsert
Procedures
NewRecordWithDetails(NewDate: Date; NewItemNo: Code[20]; NewDescription: Text[100])Δ BC25ModifyForecast(ItemNo: Code[20]; Date: Date; DocumentType: Option; Quantity: Decimal)Δ BC27 (protected)
Plus 3 local procedures.
Triggers
OnInitReport, OnPreReport
Extended by
Documented on Microsoft Learn
Deprecations
- object: Pending 27.0 (#if not CLEAN27), “This report has been deprecated and will be removed in a future release.”
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: "report", object_name: "Planning Availability"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.