This transaction set enables railroads and their trading partners to inquire about or communicate advice regarding problem logs in rail operations. Typically sent by a railroad carrier, freight forwarder, or maintenance facility to a railroad operations center or problem management system, the 452 transaction set may be initiated in response to operational disruptions, equipment failures, or service issues requiring investigation or documentation. The message is structured around three key segments: the BGP (Beginning Segment for Problem Log Inquiry or Advice) segment, which establishes the nature and scope of the inquiry or advisory communication; the N9 (Reference Identification) segment, which links the problem to relevant transaction numbers, work orders, or incident reports; and the NTE (Note/Special Instruction) segment, which accommodates detailed descriptions and contextual information about the problem being logged or investigated.

In practice, Union Pacific Railroad might send a 452 transaction to its maintenance operations center to inquire about or report a known issue affecting a shipment of automotive parts bound for a Detroit assembly plant. The railroad would populate the BGP segment to identify whether the message is an inquiry seeking status on a previously logged problem or advice notifying the operations center of a newly discovered issue. Supporting N9 segments would reference the original problem ticket number and related shipment identifiers, while multiple NTE segments would document the specific symptoms, timeline, and impact—for instance, reporting that a faulty rail switch caused a two-hour delay at a switching yard near Chicago. The receiving operations team would use this information to update their problem management database and coordinate resolution efforts.