Codeunit 37216 "PEPPOL30 Sales Validation"

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

Properties

Procedures

• ValidateDocument(RecordVariant: Variant): Validates a sales document header against PEPPOL 3.0 requirements. Validates mandatory fields, formats, and business rules at the document level.
• ValidateDocumentLines(RecordVariant: Variant): Validates all sales document lines associated with a sales header against PEPPOL 3.0 requirements. Iterates through all lines and performs line-level validation Validates.
• ValidateDocumentLine(RecordVariant: Variant): Validates a single sales document line against PEPPOL 3.0 requirements. Performs validation Validates on individual line fields and business rules.
• ValidatePostedDocument(RecordVariant: Variant): Validates a posted sales document against PEPPOL 3.0 requirements. Validates the posted document for compliance before export or transmission.
• ValidateLineTypeAndDescription(RecordVariant: Variant): Boolean: Validates the sales line
• CheckCurrencyCode(CurrencyCode: Code[10]): Validates that the currency code is a valid 3-character ISO currency code.
• CheckCountryRegionCode(CountryRegionCode: Code[10]): Validates that the country/region code has a valid 2-character ISO code.
• CheckShipToAddress(SalesHeader: Record "Sales Header"): Validates the ship-to address fields on a sales header.
• CheckTaxCategory(SalesLine: Record "Sales Line"): Validates the tax category for a sales line.
• EnsureZeroRate(VatPercent: Decimal; TaxCategoryCode: Code[10]): Ensures the VAT percentage is zero for tax categories that require it.
• EnsurePositiveRate(VatPercent: Decimal; TaxCategoryCode: Code[10]): Ensures the VAT percentage is positive for tax categories that require it.
• EnsureSingleOutsideScopeVATBreakdown(SalesLine: Record "Sales Line"): Ensures only a single outside scope VAT breakdown exists for PEPPOL compliance.

Triggers

OnRun

Relations

• runs on Table 36 “Sales Header”

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 Sales Validation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.