web
You’re offline. This is a read only version of the page.
close
  • Order properties on cXML PO for WMSADDRESSID should use the same address details

    The External catalogue order properties for WMSADDRESSID are set to TRUE (as below description for this field) which is taking the warehouse number from the PO header as the addressID but then taking the ShipTo address details from the Delivery address name on the order. This is inconsistent. The ShipTo address should be taken from or be consistent with the WMSADDRESSID if the parameter is set to TRUE. The default delivery address on the purchase requisition from punchout catalogue should also default from the WMSADDRESSID (warehouse address ID) and not require a manual update. It works this way for items and on purchase orders. Order default from docs.microsoft. WMSADDRESSID Set this property to TRUE to use the warehouse number on the purchase order header as the addressID value in the ShipTo address for the purchase order request that is sent to the vendor. If you set a value for the FIXEDSHIPADDRESSID property, that value takes precedence over this value. Therefore, you should use one property or the other to set the addressID value in the ShipTo address for the document. Current code: //Header ShipTo orderHeader.appendText(''); orderHeader.appendText('
    '); orderHeader.appendText(vendPurchOrderJour.DeliveryName +''); orderHeader.appendText(''); orderHeader.appendText(this.processDeliverTo());
  • Summary order update by customer reference

    Many clients I have worked with would like the ability to produce a customer invoice by customer reference. We did customise this in one project to allow Summary update for 'Customer reference'. This is extremely useful for customers that only make payment against their reference number/PO.
  • Fixed asset indexed revaluation

    This feature is already available as an ESP localisation Fixed asset revaluation groups - Finance | Dynamics 365 | Microsoft Docs


    I am currently working on a public sector project and they have indicated that this is a standard public sector requirement in the United Kingdom to be able to revalue fixed assets based on indexation values year on year.


    Is it possible to extend this functionality to either public sector and/or GBR localisation (or have as standard config)

  • Update to AP parameters to allow for touchless invoice processing

    Many businesses struggle with product receipting discipline, that is, goods are receipted late causing delays in 3-way matching and invoice processing.

     

    This means:

     

    1. With the current functionality in both invoice capture and D365, unless you have the AP parameters set to 'Automatically create invoice lines' from 'Ordered quantity' the PO number is not transferred with the header only invoices from Invoice capture.

     

    2. If the AP params for 'Automatically create invoices lines' are set to 'Product receipt quantity' then the PO number is not transferred if there is no existing product receipt, and the invoice requires manual intervention to progress.

     

    In scenario 2 above, it would be great if the 'Automatically create invoice lines' from 'Product receipt quantity' could run as a process automation task, rather than (or in addition to) the immediate call to D365 on invoice transfer. This would allow for late receipting to also be able to create the invoice lines, and in conjunction with the other process automations (Match vendor invoice lines with product receipts), allow for touchless invoice processing.

     

    Having the PO visible in the pending vendor invoices form helps the AP clerk determine who is responsible for receipting or query management.