Recently I have tried to make an adjustment for the Purchase order workflow in Microsoft Dynamics 365 for Supply Chain Management. When I pressed Edit button, nothing has happened, workflow editor has not showed up.
To solve this issue, I had to run the following command:
rundll32 dfshim CleanOnlineAppCache
When you are providing a demo for the potential customers in D365 SCM, typically you use Contoso demo data with the existing the Contoso personas.
In some occasions, you need to create a slide talking about the personas that will be used for the demo, including pictures and their roles.
In this blogpost, I would like to share the list of the links that I used for the recent demo and I found them useful:
This is the site where you can find the names, pictures and the job descriptions for the Contoso personas:
Microsoft Dynamics Customer Model (d365-design.azurewebsites.net)
Here you can find the list of the Contoso personas available out of the box and the security roles assigned:
How do I login to the new AX as a demo user persona? - Microsoft Dynamics 365 Blog
That's it!
Business scenario: Typically when you have multiple approved purchase requisition lines (from different purchase requisitions) that are procured from the same vendor, it is highly unlikely that the requisition lines from the different requisitions have the same accounting date (which can be defaulted from the requested date via Purchasing policies: Use requested date as accounting date parameter in the Purchase requisition control rule policy is set to "Yes"). In this scenario, when you purchase order is created for such requisitions, multiple purchase orders are created based on the accounting date. This lead to the procurement department to do the following:
However, there is a configurations that was introduced to solve this issue and consolidate multiple requisitions into single purchase orders in case if accounting dates are different.
To control the consolidation behavior you need to activate the new feature:
• Feature: "Consolidate multiple purchase requisitions into a single purchase order by accounting date"
• Feature description: This feature allows for the consolidation of multiple purchase requisitions into a single purchase order if the different purchase requisitions have different accounting dates. Purchase order creation and demand consolidation purchasing policy rule can be setup to drive the decision for grouping requisition lines by accounting date on purchase order level automatically. Warning!: Consolidation purchase order by accounting date is not supported if budget control is enabled because the accounting date is used, for budget reservations and encumbrance. Therefore, it should be kept during the transition from purchase requisition to purchase order.
Note: If your organization has budgeting control activated, this parameter will not have any affect. The system will be creating multiple purchase orders in this case.
Let's walk trough the scenario, when approved purchase requisitions are released manually through "Release approved purchase requisitions" page. For this scenario, manual purchase order creation is enabled (Purchasing policy > Purchase order creation and demand consolidation rule > Manual purchase order creation tab > Manually create purchase orders).
Create and approve requisition lines with different requested dates.
When "Consolidate by accounting date" is OFF, releasing multiple PR with different accounting date, will create multiple POs.
In this blog post I would like to provide an overview of intercompany flows and what is the expected process to be performed in Microsoft Dynamics 365 Supply Chain Management.
The following diagram illustrates the idea behind the two-legged intercompany chain and steps that typically performed in Microsoft Dynamics 365 Supply Chain Management to achieve the needed result.
In order, to enable the Maintenance mode - run Command prompt as administrator then execute the following command:
c:\AosService\PackagesLocalDirectory\Bin\Microsoft.Dynamics.AX.Deployment.Setup.exe --metadatadir c:\AosService\PackagesLocalDirectory --bindir c:\AosService\PackagesLocalDirectory\Bin --sqlserver . --sqldatabase axdb --sqluser axdbadmin --sqlpwd AOSWebSite@123 --setupmode maintenancemode --isinmaintenancemode true + Enter
Next – execute the command: IISreset + Enter
Maintenance mode enabled!
c:\AosService\PackagesLocalDirectory\Bin\Microsoft.Dynamics.AX.Deployment.Setup.exe --metadatadir c:\AosService\PackagesLocalDirectory --bindir c:\AosService\PackagesLocalDirectory\Bin --sqlserver . --sqldatabase axdb --sqluser axdbadmin --sqlpwd AOSWebSite@123 --setupmode maintenancemode --isinmaintenancemode false + Enter
Next – execute the command: IISreset + Enter
Maintenance mode disabled!
There is a possibility to configure tiered charges for the purchase orders. For more details, visit this page - https://docs.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/about-tiered-charges-on-sales-orders
In order to activate this feature, navigate to the Feature management workspace, find Charges from and to amounts on Purchase orders feature on the list and click Enable now button. Once you activate it, you can configure tiered charges.
Once you enable this feature, Automatic charges page will be extended with a few fields:
Mode of delivery code will determine when to apply charges:
On the local VM, you might face an issue while trying to download the task recorder: Sorry, something went wrong and the file wasn't downloaded
