David Fielder

Currently, the purchase order line number field is not visible on the invoice lines in the supplier collaboration module. This is required by suppliers so they can validate and update invoice lines in comparision to the purchase order doucment they have received from the customer.

This is especially important in industries where product masters & variants are used such as retail. The display dimensions functionality is not avaiable on the invoice lines in supplier collaboration. This means dimensions such as size can't be added to the invoice lines as identifiers.

In Hunter Boots scenario, this has made it impossible for suppliers to tell the invoice lines apart as the same product master number is listed on multiple lines but the purchase order line number & size code fields are not visible. This issue has made the supplier collaboration invoicing functionality unusable, and will likely have to be descoped from implementation.

Electronic Reporting/Business Document Management is the out of the box tool provided in D365 Finance & Operations, for designing custom reports and documents. Designing a custom document allows the customer to ensure that the report will contain the required data and fit their branding.

One of the documents that can be designed and configured with these tools is the Purchase Order Confirmation document. If print management is configured to print this document using Electronic Reporting/Business Document Management, then the custom Purchase Order Confirmation document will be printed in all applicable modules in D365. This includes Procurement and Sourcing for internal users, and Vendor Collaboration for external users.

However, external users are unable to print the custom document designed in Electronic Reporting/Business Document Management, in Vendor Collaboration. Instead, they are presented with an error message and no document is printed. Microsoft support and the product group have confirmed that this is a gap in the standard product. Only the standard SSRS report for this document is supported for external users in Vendor Collaboration.

It is not possible to configure print management to print the custom document for internal users in Procurement and Sourcing, and the standard SSRS report for external users in Vendor Collaboration. This means however the system is configured, either the internal users or external users are going to lose out. Either external users can't print anything, or the internal users have to print the standard SSRS report that doesn't meet requirements.

When goods are imported through customs, the payable duty amount is typically calculated using purchase price + transport costs. Other costs could also be taken into consideration such as insurance, royalties, brokerage fees etc. The costs that are taken into consideration will be determined by the country/region the goods are being imported to.

In the UK, customs will calculate the payable duty amount using the CIF (cost, insurance, freight) value of the goods and the duty % determined by the exporting country and commodity code for the item. The duty calculation must also be completed in the local currency, therefore exchange rates must be applied if the transactions are in a foreign currency.

The calculation would be as follows:

• Payable duty = (cost of goods + cost of insurance + cost of freight) x duty %.
• For example: (£9000 + £200 + £800) x 2 % = £200

It is not possible to configure auto costs in the landed cost module to perform this calculation. Functionality does exist to link auto costs together, but you can only link auto costs within the same auto cost record. For example, you cannot link the duty cost on the item cost area to the freight cost on the shipping container cost area.

Microsoft has previously suggested a workaround by configuring a duty cost on the item cost area and a second duty cost on the shipping container cost area that is linked to the freight cost. However, this is not realistic as a shipping container could have a mixture of items with different duty % rates. The duty cost estimate on POs/Voyages would be inaccurate.

In addition to duty there will be other costs such as anti-dumping duty that also need to be linked to other costs to accurately calculate the cost estimate. Auto costs must be enhanced with new functionality that can create accurate cost estimates per PO/Voyage for these scenarios. The system has the data to complete the calculations but lacks the functionality/logic to do so.

When a user creates product variants for a product master, they can use the 'Variant suggestions' function to select from the available colour, size, stye dimensions on the product master to create product variants.

The issue with the 'Variant suggestions' form is that it only displays the dimension ID, it does not display the dimension name or description. For example, a colour could be setup as follows:

• Colour ID: MNB
• Colour name: Midnight Blue
• Colour description: Dark Blue

In this example, the 'Variant suggestions' screen would only display "MNB" under the 'Select colours' fast tab.

As it is possible to setup dimension names & descriptions, the system should pull through these values to the relevant screens such as 'Variant suggestions', so it is clear the user which dimension/variant they are selecting.

I have had this requirement from multiple clients who have had to consider customisations or ISVs to plug this gap. This is a simple change to the standard solution, which would allow clients to better spend their budget elsewhere.