Dynamics Community Forum Thread Details

Landed Cost Auto Cost Configuration in D365 F&O

Hello,

I am currently working on Landed Cost configuration in D365 F&O and would like to confirm my setup for an auto cost.

I configured an auto cost under the cost area "Item" and named it "Insurance." I set the cost value to 10 and selected "Percent" as the category.

To make this applicable to a group of items, I created a voyage cost group (for example, "VG") in the item setup and assigned it to the relevant items. I also applied the same group in the auto cost item relation.

With this configuration, my expectation is that whenever an item belonging to this group is included in a voyage, the system will automatically apply this insurance cost and display it in the Voyage Cost Inquiry screen.

However, I am unable to see it. Instead, I only see the auto costs configured at the cost area Voyage level and shipping container level.

If this auto cost does not appear in the Voyage Cost Inquiry screen, how can I ensure that it still impacts the cost price of the item? If yes, where can I review the related financial transactions?

Could you please confirm if this setup is correct or advise if anything is missing?

Thank you in advance for your support.

Best regards,

Categories:

Dynamics 365 Supply Chain Management

Hi MZ-15041337-0,

1) Issue
- An auto cost is configured under cost area "Item" (e.g., Insurance, 10% as Percent)
- A voyage cost group (e.g., VG) is assigned to items and also used in the auto cost configuration
- Expectation is that the auto cost should automatically appear in the Voyage Cost Inquiry screen when items are included in a voyage
- However, only costs defined at Voyage level and Shipping container level are visible, while Item-level auto costs are not shown
- Requirement is to understand whether setup is correct and how the cost impacts inventory/financials

2) Reason
- In Landed Cost, auto cost behavior depends on cost area and timing of calculation

Cost areas behave differently:
- Voyage level → always visible at voyage header
- Shipping container level → visible at container level
- Item level → applied only during cost estimation/allocation stage, not immediately visible in Voyage Cost Inquiry
- Item-level auto costs:
- Are not directly stored as standalone voyage cost records
- Are calculated dynamically when costs are estimated or allocated
- Therefore:
- They do not appear in Voyage Cost Inquiry until cost allocation logic is executed
- Additionally:
- If cost estimation or costing process is not triggered, item-level auto costs remain unapplied

3) Resolution
Validate setup:
- Item assigned to correct Voyage cost group
- Same group used in auto cost item relation
- Cost category set correctly (Percent / Fixed)

Ensure correct process execution:
- Perform Cost estimation on voyage
- Then run Cost allocation
- Item-level costs will be applied during this stage rather than appearing immediately

Where to verify the cost impact:
- Use Voyage cost estimation / cost allocation views to see calculated values
- After posting:
- Check Inventory transactions (InventTrans) for adjusted cost price
- Review Voucher transactions for financial postings
- Use Inventory value report or Cost explorer to confirm capitalization

Important note:
- Item-level auto costs do not behave like voyage/container costs in UI visibility
- They are primarily calculation-driven, not directly displayed until costing is applied

Conclusion:
- The setup is correct, but behavior is expected
- Item-level auto costs become visible only during cost estimation/allocation and financial posting, not directly in Voyage Cost Inquiry

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References: