SQL Server

PEPPOL Document Validation

See more HTTP Misc Examples

Demonstrates how to call a Web service to validate your PEPPOL documents according to the latest PEPPOL rules. The validation service requires UBL files. SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    -- This example assumes the Chilkat HTTP API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- --------------------------------------------------------------------------------
    -- Also see Chilkat's Online WSDL Code Generator
    -- to generate code and SOAP Request and Response XML for each operation in a WSDL.
    -- --------------------------------------------------------------------------------

    DECLARE @http int
    EXEC @hr = sp_OACreate 'Chilkat.Http', @http OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- We are sending the following POST:

    -- POST /wsdvs HTTP/1.1
    -- Host: peppol.helger.com
    -- Content-Type: application/soap+xml; charset=utf-8
    -- Content-Length: <length>
    -- 
    -- <?xml version="1.0"?>
    -- <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    -- <S:Body>
    -- <validateRequestInput xmlns="http://peppol.helger.com/ws/documentvalidationservice/201701/" VESID="eu.peppol.bis2:t10:3.3.0" displayLocale="en">
    -- <XML>...ENTITY_ENCODED_INVOICE_XML_GOES_HERE...</XML>
    -- </validateRequestInput>
    -- </S:Body>
    -- </S:Envelope>

    -- Build the SOAP XML shown above.
    -- First load the PEPPOL invoice that will be the data contained in the <XML>...</XML> SOAP element.
    -- We are using the XML invoice obtained from https://github.com/austriapro/ebinterface-standards/blob/master/schemas/ebInterface5p0/samples/ebinterface_5p0_sample_ecosio.xml
    DECLARE @sbPeppolInvoiceXml int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbPeppolInvoiceXml OUT

    EXEC sp_OAMethod @sbPeppolInvoiceXml, 'LoadFile', @success OUT, 'qa_data/xml/peppol_invoice.xml', 'utf-8'

    DECLARE @xml int
    EXEC @hr = sp_OACreate 'Chilkat.Xml', @xml OUT

    EXEC sp_OASetProperty @xml, 'Tag', 'S:Envelope'
    EXEC sp_OAMethod @xml, 'AddAttribute', @success OUT, 'xmlns:S', 'http://schemas.xmlsoap.org/soap/envelope/'
    EXEC sp_OAMethod @xml, 'UpdateAttrAt', @success OUT, 'S:Body|validateRequestInput', 1, 'xmlns', 'http://peppol.helger.com/ws/documentvalidationservice/201701/'
    EXEC sp_OAMethod @xml, 'UpdateAttrAt', @success OUT, 'S:Body|validateRequestInput', 1, 'VESID', 'at.ebinterface:invoice:5.0'
    EXEC sp_OAMethod @xml, 'UpdateAttrAt', @success OUT, 'S:Body|validateRequestInput', 1, 'displayLocale', 'en'
    EXEC sp_OAMethod @sbPeppolInvoiceXml, 'GetAsString', @sTmp0 OUT
    EXEC sp_OAMethod @xml, 'UpdateChildContent', NULL, 'S:Body|validateRequestInput|XML', @sTmp0

    -- We don't need to specify the Content-Length or Host headers.  Chilkat automatically adds them.

    -- Send the request...
    DECLARE @resp int
    EXEC @hr = sp_OACreate 'Chilkat.HttpResponse', @resp OUT

    EXEC sp_OAMethod @xml, 'GetXml', @sTmp0 OUT
    EXEC sp_OAMethod @http, 'HttpStr', @success OUT, 'POST', 'https://peppol.helger.com/wsdvs', @sTmp0, 'utf-8', 'text/xml', @resp
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @http, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @http
        EXEC @hr = sp_OADestroy @sbPeppolInvoiceXml
        EXEC @hr = sp_OADestroy @xml
        EXEC @hr = sp_OADestroy @resp
        RETURN
      END


    EXEC sp_OAGetProperty @resp, 'StatusCode', @iTmp0 OUT
    PRINT 'Response Status Code = ' + @iTmp0

    DECLARE @respXml int
    EXEC @hr = sp_OACreate 'Chilkat.Xml', @respXml OUT

    EXEC sp_OAGetProperty @resp, 'BodyStr', @sTmp0 OUT
    EXEC sp_OAMethod @respXml, 'LoadXml', @success OUT, @sTmp0


    PRINT 'Response XML:'
    EXEC sp_OAMethod @respXml, 'GetXml', @sTmp0 OUT
    PRINT @sTmp0

    -- A success repsonse looks like this:

    -- <?xml version="1.0" encoding="UTF-8"?>
    -- <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    --     <S:Body>
    --         <validateResponseOutput xmlns="http://peppol.helger.com/ws/documentvalidationservice/201701/" success="true" interrupted="false" mostSevereErrorLevel="SUCCESS">
    --             <Result success="true" artifactType="xsd" artifactPath="/schemas/ebinterface/ebinterface-5.0.xsd"/>
    --         </validateResponseOutput>
    --     </S:Body>
    -- </S:Envelope>

    EXEC @hr = sp_OADestroy @http
    EXEC @hr = sp_OADestroy @sbPeppolInvoiceXml
    EXEC @hr = sp_OADestroy @xml
    EXEC @hr = sp_OADestroy @resp
    EXEC @hr = sp_OADestroy @respXml


END
GO