NSEB Inbound Document Conversion to Inbound E-Document

Inbound e-documents are created using NSEB Inbound Document. The NSEB Inbound Converter MR automatically converts every 15 minutes to inbound e-document and displays on the Electronic Documents portlet, under Inbound E-Documents for Conversion.

You can click on the number displayed to go to the Inbound E-Documents for Conversion: Results page, which lists the inbound e-documents for conversion. For more information, see Electronic Documents Dashboard SuiteApp Portlet.

And in the inbound e-document record the E-Document Audit Trail subtab displays information about the inbound e-document record including the date created, entity, event type, owner, and details.

NSEB inbound documents with below field values are picked up for conversion:

• Status with values 'Pending' and 'Failed'

• Document Type with value 'InvoiceDetailRequestUBL'

• Document Subtype with values 'ubl-invoice' and 'ubl-creditnote'

• Raw Document with value in XML format.

The template details for the inbound e-document record can be obtained if you select an XSD file in a template record that is appropriate for this inbound e-document record. That template is automatically selected in the E-Document Template field. If XSD file is not provided in e-document template record, then E-Document Template cannot be selected, and inbound document will not be converted. For more information about setting up inbound templates, see Creating E-Document Templates and Understanding XSD in Inbound E-Document Templates

The inbound e-document record required entity details can be obtained using the Inbound CDS PLUGIN execution where the plugin script id is provided as parameter in NSEB Inbound Converter MR script deployment and the entity internal id is expected in the plugin result. The new plugin implementation can be created of the type ‘Inbound Custom Data Source Plugin Type’. To get the expected path of the entity id check the below example.

In consideration with the below sample plugin the entity id path will be: “customDataSources[0].data.entityId”. The path for entity id should be as mentioned as it is expected by EI script to fetch entity details.

          /**
 * @NApiVersion 2.x
 * @NScriptType plugintypeimpl
 * @NModuleScope Public
 */
define(['N/render'], function (nsrender) {
   
    function inject(params) {
        // the expected structure should be defined same as below,
       // as this path is used by EI script to fetch entity details
            customObj = {
              entityId: 55 // internal id of the entity
            };
        

        return {
            customDataSources: [
                {
                    format: nsrender.DataSource.OBJECT,
                    alias: "entityDetails",
                    data: customObj,
                },
            ],
        };
    }

    return {
        inject: inject,
    };
}); 

        

If plugin id is not provoded as script parameter, then as a default approach entity details will be fetched using the PEPPOL ID matching entity where Peppol id is obtained from the payload at xpath: "//cac:AccountingSupplierParty/cac:Party/cbc:EndpointID"

General Notices