Ali Raza Zaidi

A practitioner’s musings on Dynamics 365 Finance and Operations

alirazazaidi

Consignment Inventory Handling in D365 Finance and Operations

by

Hi friends, In this post, I am going to share my notes about consignment inventory in D365 Finance and Operations.

So what is consignment inventory? Consignment inventory is stock stored in our warehouse but actually owned by its supplier.

If you remember, there is a tracking dimension called “Owner.” In product configuration, we have set this owner as inventory.

The complete process is as follows:.

While writing this article, I am using Contoso data, the USMF legal entity, and the following version and update of D365.

Installed product version: 10.0.37 (10.0.1725.47)

Installed platform version: Update61 (7.0.7068.67).

The first step is to create a vendor.  I am going to create a new vendor with the ID “Consignment Vendor”

The second step is to set up a consignment owner.

For this, we have to follow the below navigation.

Inventory Management > Setup> Dimension > Inventory Owner

Here we can add a vendor account and set an ID as the owner.

With the vendor account plus its owner.

The third step is to enable the tracking dimension. In the CONSO demo data, we can find already-configured tracking dimensions.

The tracking dimension form can be found at the following location:

Product and Information Management > Setup > Dimension and Variant Groups > Tracking Dimension.

The tracking dimension is active in the case of the Active check box, which is marked.

So we use this tracking dimension in new products.

To make things simple, we are going to create a simple product.

A new product name is “Consignment_0001.”

Consignment inventory works only on the moving average or standard cost method. We are going to use the moving average item model group. I also used the owner as a tracking dimension.

On release, product details form. Or in the purchase order tab, set the primary vendor.

We need to create a trade agreement for $80. This step is required, so when a purchase order is created, the price will be picked from here. Otherwise, it will pick the price set during item creation, whether you enter it or not.

So all steps have been taken. Let’s go to the consignment replenishment order. So vendors deliver stock to your organization.

The navigation for consignment replenishment orders is as follows:.

Procurement and sourcing > Consignment > Consignment replenishment orders

I am placing the 100 quantities in the 1, 11, and 12 warehouses.

On this screen, enter the quantity 100. You can also modify the requested delivery date for product delivery.

From the top menu, we can receive quantities.

Product receipts have no impact on inventory costs. If we see the inventory transaction details for the product, we will find no impact on cost. And the reason for that is that we did not own the quantity.

Inventory Owner Change Journal.

So we got a request from one of our customers for 10 units. For owning and selling this 10 quantity, we have to generate and post our own inventory change journal.

The navigation of Inventory owner journal at following location in D365 finance and operations.

Procurement and sourcing> consignment > inventory ownership change

Here is a very interesting thing. Here, the owner changes from vendor to legal entity. It means that if the consignment is owned by a current legal entity, we can sell it.

Let’s try this. I am going to post 10 quantities and then see what purchase order was created and what product receipt was posted against it.

The system generated a purchased order with a received status.

If we note, the price is coming with a unit price of $80. This price is coming from a trade agreement.

On checking the inventory transaction generated against. The physical date and physical cost amount are updated.

On the vendor invoice and its posting in the system, the financial date and financial cost are also updated.

Inventory ownership changed, and now we can sell or consume this quantity.

Following the screenshot, the sales order quantity is sold and delivered to the customer.

How you like this post, see you in another blog post.

Unregister Purchase Order line register quantity which is received via mobile device OR Remove Stock via PO in D365FO

by

A small tip: I just create a purchase order and register the quantity. Either directly on the purchase order or through the mobile app, advance warehouse in D365 Finance and Operations. Now I want to cancel that line or unregister the quantity for that line.

As compared to Ax 2012, it is relatively easy in D365 Finance and Operations.

For this, open the purchase order and go to a specific line, click on the update line, and click on registration.

From registration form click on ” Add registration line”

On clicking add registration line, you will find negative values.

Click on Confirm Registration. This will reverse the registration process after closing this form you can remove the line from purchase order

Similar way you can unregister the picked quantity in Sales order processing.

Glossary to Business Analysis

by

As business analysts, we deal with people, processes, and technology. We have to listen to user stories and understand their needs. Separate their wants from their needs. What is actually required as compared to their wants? Most importantly, what is actually possible with respect to their budget?

During communication between professionals as well as end users, we use different terms and jurgans. I listed some of them here.

Here is a list of some common terminology that you might come across in a business analysis glossary:

  1. Business Analyst: Consider a specialist who understands the organization’s processes, procedures, existing systems, and goals and provides the solution.
  2. Stakeholders: people or groups of people who have involvement in both ownership and investment and direct efficacy of the success or failure of the system.
  3. Requirements: detailed statements that explain the functions, processes, and pain areas of the end user or group of users.
  4. SWOT Analysis: Decision-making tools that help organizations identify their strengths, weaknesses, and opportunities
  5. Use Case: A use case is a sample event or process, or an example of documenting the interaction of a system or process with actors, users, or systems.
  6. Gap Analysis: difference between the actual system functionality provided by the system and the requirements that come from stakeholders
  7. Agile: A project management approach for requirement gathering, development, testing, and delivery to the end user that focuses on flexibility, collaboration, and customer feedback.
  8. Waterfall: A transition to requirement gathering, software development, and implementation Linear and sequential framework.
  9. Business Process Modeling: The graphical representation of business processes for the purposes of understanding, analyzing, and improving them.
  10. ROI (Return on Investment): measure the profit or value gained from an investment.
  11. KPI (Key Performance Indicator): measurement of key factors for success in implementation or success in requirement gathering. or preformance.
  12. RACI Matrix: A technique for clarifying project or process roles and responsibilities (responsible, accountable, consulted, and informed).
  13. Scope creep: uncontrolled changes and additions to the scope of a project. This leads to delays and overbudgeting for the project.
  14. Change Management: The process of planning, implementing, and managing organizational changes
  15. BRD (Business Needs Document): A document that outlines a project’s high-level business needs.
  16. User Story: Understanding and documentation of presepective end uses; this term is widely used in Agile.
  17. Decision Matrix: requirements and their solutions vs. possibilities based on established criteria
  18. Feasibility Study: Documentation for the proposed solution: is it viable or possible, both in terms of cost and time?
  19. Sprint: what will be delivered, requirement gathering, and development within a 2-4 week period for a defined requirement or set of features.

Product Attribute Data Management D365 Finance and Operations

by

We are senior, or senior citizen. Most of the time, young champs do things. And we as senior, just control the situation or communicate.

We can not do everything. We need to delegate things. Today I got chance to work with a young champ to import the product attribute in a system.

I used following Data Entities

Product attribute enumeration types v3
Product attribute integer enumeration types
Attribute group
Product attributes – Specification of attribute types and attribute name
Product category attributes – combination of category and attribute on a product
Product attribute values – for attribute values assignment per product
Product entity attribute value entity – for attribute values assignment per product
Category hierarchies & product category hierarchy – for Procurement category
Internal organization product attribute values
Product category category attribute group assignments – attribute assignment on category
Product category product attribute group assignments

Corrective or reactive Maintenance

by

Reactive, corrective, or break down maintnenance requires for component that supports the supply chain process in any organization.

In this video, I shared the flow of corrective maintenance and with example you can perform corrective maintenance.

Purchase Order Receiving Dynamics 365 Advanced Warehouse

by

I walk through the setup and procedure for the Dynamics 365 Advanced Warehouse Purchase order receiving in today’s session. I demonstrate two procedures: a one-step procedure for receiving an item from a pallet directly to a shelf, and a two-step procedure for receiving an item from a pallet to a receiving point before moving it to a shelf.

Job types 101 Asset Management in D365 Finance and Operations. Asset Management Part 2

by

Hello, everyone. This is the second post in the Enterprise Asset Management Series.

In my last post, I shared some insider information and my understanding of locations in Asset Management. You can find that post at the link below.

In this post, we will discuss the following things:

  1. Maintenance job categories.
  2. Maintenance job types variants.
  3. Maintenance job types.
  4. Maintenance checklist template.
  5. Setup default checklist on job type.

Maintenance job Categories:

Categories are used to group Job types. We can identify these job types with category types.

Navigation

Asset Management > Setup > Job > Maintenance job type categories

Maintenance Job Types Variants

This is a non-essential setup requirement. Just to provide the extra information and possible need for more care required for maintenance. For example, Condition Assessment at 1000 Km or 2000 km is possible for technicians to verify or diagnose in more detail as compared to 1000 km if Job type variations exist.

Navigation

Asset Management > Setup > Job > Maintenance job type variants

Maintenance job types.

One of the major central points of Asset management is the common template, where we need to define things that are copied to work orders.

In the Details sections, we just have counters; these counters are the result of the below tabs or sections.

In this section, we can define the job category and also mention that this type of job requires downtime activities.

Then comes the description.

In this field, you can define and note anything you want to store as details.

Then come Job variants,

In this section, we defined the Job variants; these variants will be shown when we select job types on a work order. What we define here will reflect on the work order Type. The Job variant will populate based on the job type.

Job skills and Job certificates are unimportant and less used features. They can be defined, but they will never be used. It is just information.

The next critical step is to complete the maintenance job successfully.

Where we define, next job after completing jobs. these were just information, I did not found any benefit to define succeeding maintenance jobs.

Now comes with Asset Types. In this section we defined qualified asset types on this job type are allowed.

When we define a work order against an asset, on the selection of the asset, the drop-down shows only assigned job types in the above-mentioned job type.

This will be one of the most important points in the whole maintenance job type.

Maintenance Job Defaults:

If you click on the action pane, then Maintenance Job Type, a new form will open.

where we can define different check lists, forecasts, descriptions, and resources for the default job type.

We can also add multiple defaults based on variations in the combination of job type and asset type. The same job type can work for different types of assets. We defined the asset type in the above-mentioned step, in Asset Type.

For current example, which mostly from contoso data and usmf legal entity, You can see Hours are 1.00. If I click on forecast button on fast tab

You will find something similar. You can see that the forecast method has already defined an hour.

There are complete details on Item forecast, and in the same way, we can define expense forecast and fee forecast.

Most of the time, we used to set expenses for technician work, food he took during maintenance work, or travel expenses we had to give to the technician for each. In the fee section, most of the time we record the outsourced service charges. It depends on how you plan.

This forecast is important; when we post the actual journal, the comparison between forecast and actual will come from here.

I will probably discuss this in my next blog post.

Here We have to define a maintenance checklist. We can assign these maintenance check lists to job types. When we define a work order for a specific job type, the check list defined for that job type defaults to it.

These check lists will be used for verification of maintenance or to ensure that technicians will perform all necessary maintenance.

Check lists can now be defined as different check lists. These check lists are used to verify what type of test we have to define for each asset type.

We can define, new check list with help of following options.

Text is used for the just-mentioned answer.

The header is used to create a separator between questions; they appear in the same way they are defined as per line number.

Variables are usually Yes, no, or multiple choice answer; most of the time, it will be used for two values: “True” and “False”.

Then comes measurement, which will be used for numeric values. for example, vehicle use counter, and then there is range, which can also be defined here.

Template: here we define the template. I used to prefer this because, in this way, we can define templates Independently and reuse them later.

We can create a new maintenance check list by click on new button.

Or you can define, check lists in following navigation. These reusable check list can be select in above link.

Navigation >setup >Maintenance checklist > Maintenance checklist templates

In this we define Job type, And all things defined here will be reuse in work order.

Hope you like this post,

Locations in Asset Management in D365 Finance and Operations. Asset Management Part 1

by

In this series of blog , I am going to share the functionality of Asset management in D365 Finance and Operations.

In first blog post I described the concept and option of location in D365 Finance and Operations.

So what is functional location.

Functional locations are places where assets can be installed. These locations can be hierarchical. Let’s say we have a head office building that has 10 rooms: 2 conference rooms and 8 halls. Every hall has one printer and four desks, and on each desk, one laptop or computer is placed.

In some cases, locations don’t have assets directly installed on them. For example, the head office did not have assets directly. But every hall inside the head office building can have assets installed. For this reason, we can disable the Create asset on location option in Asset Type.

Followings are points why we need asset maintenance on location.

  • We can define asset maintenance at a specific location.
  • We can get the total cost for a specific location.
  • We can get the total Item consumption for a specific location.
  • Even so, we can get a list of Work orders and maintenance requests for a specific location.
  • List of faults that occur at a specific location.

Location Lifecycle state:

Asset management > Setup > Functional Location > Location Lifecycle state:

No alt text provided for this image

The life cycle state defines the current state of an asset. There are multiple properties defined for the location state.

Functional Location Action toggle button If we enable yes, then this location will be in an active state.

create Asset toggle button: if this button is enabled to yes, it means we can create assets on location.

Allow Rename the location. If this property is true, then we can rename the location. Otherwise, it is not possible to rename the location.

New sublocation toggle button: In the case of property, location will allow new sublocations. When a location is in this state, we can add sublocations to assets.

Install asset at location toggle button: this state ensures that assets can be installed at location. Sometimes we have hierarchical locations and cannot install assets at those locations.

Delete functional location. if the location this state, where this option is true, we can delete the location.

Asset State: Asset state, means when ever asset is installed on this location, it will change to assigned that state.

Based on our need we can make new life cycle state and we can set above mentioned properties to play with these.

Currently I select only three life cycle states for example, New, active and Ended.

No alt text provided for this image

Location life Cycle model:

Life Cycle model helps us to define behavior of states.

Asset management > Setup > Functional Location > Location Lifecycle Model.

No alt text provided for this image

For example, the above screenshot can be explained in the following way:

  • The active state can be converted into an ending state.
  • When Any location is in an end state, that is, a final state, it cannot be converted to another state.
  • A new state can be converted into an active state; we cannot convert it into an ending state.

We can define the life cycle model based on our needs by adding more life cycle states and enabling and disabling different toggle buttons for each state.

Location Type:

Location Type helps us make a template. There is a possibility we have similar types of locations. And these locations can have similar characteristics.

You can find location Type with below navigation path.

Asset management > Setup > Functional Location > Location Type

No alt text provided for this image

Location type:

On location type, we can define the functional location life cycle model. It is automatically copied to the location when we create a location.

The toggle button for allow Multiple assets allows you to install multiple assets.

We can also enable or disable the update asset dimension allowed on assets (this function is not working because of some missing functionality).

Then some fields are just counters for the number of asset types installed on location, the count of permitted location types, etc.

The system will then determine which types of assets are permitted to be located. For example, in the office hall, we can install a printer, laptop, and photocopier. We cannot install a forklift in the office hall.

If we do not define any asset type here, then the location will be open for all types of assets.

Maintenance Plan:

We can also define a maintenance plan based on location. Most of the time, every asset has a different maintenance plan. We usually do not use this feature. But where can we define a maintenance plan? That is applicable to all assets.

No alt text provided for this image

Permitted type Tab.

In the system, we can define hierarchical locations; for example, the head office can have a hall room and a conference room. Head office cannot have another building or factory as a child. Here we can define Allow location types in this tab.

No alt text provided for this image

Asset Attribute requirements

We can also define asset attribute types on functional locations type. For example color of Red. This option did not validate on location as well as asset.

No alt text provided for this image

Conclusion: We can define location types. In some implementations, locations are not important. For these, we can define a default location, and we set this in the Asset Maintenance parameter page. When an asset is created, it automatically picks the default location.

For further Inquiry

email alirazazaidi@live.com

Cell Number+971555128359