codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 37219 "PEPPOL30 Service Validation"

PEPPOL · Microsoft.Peppol

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Table 5900 "Service Header" (relates to)Service Header

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

PEPPOL · Microsoft.Peppol · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Service Header

Procedures

  • ValidateDocument(RecordVariant: Variant): Validates a service credit memo header against PEPPOL 3.0 requirements. Checks mandatory fields, formats, and business rules at the document level.
  • ValidateDocumentLines(RecordVariant: Variant): Validates all service credit memo lines associated with a service header against PEPPOL 3.0 requirements. Iterates through all lines and performs line-level validation checks.
  • ValidateDocumentLine(RecordVariant: Variant): Validates a single service credit memo line against PEPPOL 3.0 requirements. Performs validation checks on individual line fields and business rules.
  • ValidatePostedDocument(RecordVariant: Variant): Validates a posted service document against PEPPOL 3.0 requirements. Validates the posted document for compliance before export or transmission.
  • ValidateLineTypeAndDescription(RecordVariant: Variant): Boolean: Validates the service line

Triggers

OnRun

Relations

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: "codeunit", object_name: "PEPPOL30 Service Validation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources