Andreas Tangemann

In AX2012 the function of virtual company accounts and table collections made it possible to use the same master data in different companies.

In D365 this function is not available anymore. To overcome this problem we use a master data company and copy the data from this company to all active companies.

While using this functionality we realized that for some master data translations can be ex-/imported with data entities, for others data entities are not available.

For example the target entities TrvBarcodeInstructionsLanguageTxtEntity and TrvPolicyLanguageTxtEntity are available.

We are missing target entities for translations of

- Accounts payable > Setup > Charges setup > Charges code

- Accounts payable > Setup > Delivery terms > Terms of delivery

- Accounts payable > Setup > Payment setup > Terms of payment

- Accounts payable > Setup > Payment setup > Cash discounts

- General ledger > Indirect taxes > Sales tax > Sales tax codes > Tax directives

The data entity "Project ledger posting definition" allows to export data, but can only be used to import data once.

As soon as data has been imported no updates to the existing records are possible. This error is shown:

"Cannot create a record in Ledger posting setup (Projosting), Account type: Cost, The record already exists."

Other data entities like "Ledger posting definition for procurement" allow to update existing records. This should also be possible for the data entity "Project ledger posting definition".

This is the standard process when manually creating an invoice for a purchase order and matching it to product receipts:

• Purchase order
• Product receipt 1 => 4 items
• Product receipt 2 => 3 items
• Product receipt 3 => 5 items
• Post invoice for product receipt 1
• Accounts payable > Invoices > Pending vendor invoices
• Click on “Vendor invoice > New > From product receipt
• Mark “Include” for product receipt 1 and click “Ok”

Using menu item “Vendor invoice > New > From product receipt” will start the process again and you can in- or exclude product receipts.

As soon as you save the invoice and leave the form, you can not use the function “From product receipt” again. The menu item does not appear anymore.

This would be extremely helpful, especially if you create the pending invoice from an external system. In this case you never have the chance to use the function “From product receipt”.

In this example, matching product receipt 1 for this invoice would mean deselecting all items (1 click) and then selecting four items (4 clicks) and matching the receipt (4 clicks).

If the function “From product receipt” would be available this would be reduced to deselecting all items (1 click) and selecting one product receipt (1 click). This means 2 clicks instead of 9.

In AX2012 R2 this was also possible by selecting “Add another product receipt”.

Business Scenario

Companies using standard cost as valuation method need to show a history of prices for the year end audit. If active prices are set up, the form "Product information management > Products > Release products > Manage cost > Setup > Item price" shows this history of prices by item.

Problem

If you calculate item cost (e.g. "Product information management > Products > Release products > Manage cost > Setup > Item price > Calculate item cost"), pending prices are also used. Pending prices can be deleted or changed and there is no history. Companies are not able to explain calculated prices during audit, if the pending price has been deleted or changed.

Proposed Solution

Create a parameter that allows to include or exclude pending prices when calculating item cost.

Benefit

Companies can decide to use both prices or just active prices. If only active prices are used, a clear price history can be shown by item and the standard cost calculation will not include any pending prices.

Business Scenario:

• Ledger allocations rules can be used to distribute cost or make intercompany postings.

Problem:

• Companies heavily using the ledger allocation rules need to start or set up batch jobs separately for each allocation rule. With ledger allocation groups, it would be possible to start several ledger allocation rules at the same time.

Proposed Solution:

• New program to create Ledger allocation groups
• General ledger > Allocations > Ledger allocation group
• New field in ledger allocation rules to specify the linked group
• General ledger > Allocations > Ledger allocation rules
• New field to either specify one ledger allocation rule or one ledger allocation group to be processed
• General ledger > Allocations > Process allocation request

Benefits:

• Save time in the month end process. Make sure to start all necessary ledger allocation rules.