Report 300 "Carry Out Reservation"
Base Application · Microsoft.Inventory.Tracking
Across versions
- BC23present
- BC241 procedures added
- BC251 events added, 1 events removed
- BC26-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Inventory.Tracking · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| ApplicationArea | Reservation |
Events published
OnCarryOutReservationOtherDemandType(var ReservationWkshLine: Record "Reservation Wksh. Line"; DemandType: Enum "Reservation Demand Type")+ BC25 − BC25 (integration)- subscribers: Codeunit 935 “Asm. Item Tracking Mgt.” OnCarryOutReservationOtherDemandType, Codeunit 99000842 “Service Line-Reserve” OnCarryOutReservationOtherDemandType, Codeunit 99000891 “Mfg. Item Tracking Mgt.” OnCarryOutReservationOtherDemandType
Procedures
Initialize(NewDemandType: Enum "Reservation Demand Type")+ BC24
Plus 2 local procedures.
Calls
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 300 “Reservation Worksheet Mgt.” (2 calls:
Reserve → GetSourceDocumentLine,Reserve → LogChanges) - Codeunit 99000845 “Reservation Management” (2 calls:
Reserve → AutoReserveOneLine,Reserve → SetReservSource)
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: "report", object_name: "Carry Out Reservation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.