Create an internal order with OG

Oct 13, 2025 by talynt.org 82 views

Introduction

In this article, we will delve into the issue of target MOS being slightly different after migration from one system to another. This problem can be particularly frustrating, especially when it affects the accuracy of your data. We will explore the root cause of this issue, provide a step-by-step guide on how to reproduce it, and suggest a fix to resolve the problem.

What Went Wrong?

The target MOS (Minimum Order Quantity) is not matching exactly after migration from the original system (OG) to the new system (omSupply). This discrepancy can be attributed to the way dates are being converted between the two systems.

Expected Behaviour

The expected behaviour is that the target MOS should match exactly after migration from OG to omSupply. This means that the conversion of dates between the two systems should be accurate, and the target MOS should be calculated correctly.

How to Reproduce

To reproduce this issue, follow these steps:

Create an internal order with OG: Create an internal order using the original system (OG).
Migrate to omSupply: Migrate the internal order from OG to the new system (omSupply).
Compare the target MOS: Compare the target MOS in OG with the target MOS in omSupply. You should notice that the target MOS is slightly different.

Suggested Fix

The suggested fix is to use 30 (the number of days in a month) instead of NUMBER_OF_DAYS_IN_A_MONTH when converting between daysToSupply. This change will ensure that the conversion of dates between the two systems is accurate, and the target MOS is calculated correctly.

Your Environment

To help us better understand the issue, please provide the following information about your environment:

Open mSupply Version: What version of mSupply are you using?
Legacy mSupply Central Server Version: What version of the legacy mSupply Central Server are you using?
Platform: What platform are you using (e.g., Android, browser, desktop, server)?
Database type: What type of database are you using (e.g., PostgreSQL, SQLite3)?

Understanding the Issue

The issue of target MOS being slightly different after migration can be attributed to the way dates are being converted between the two systems. When migrating from OG to omSupply, the conversion of dates is not accurate, resulting in a discrepancy in the target MOS.

Why is this Happening?

The reason for this discrepancy is that NUMBER_OF_DAYS_IN_A_MONTH is not being used correctly when converting between daysToSupply. This is causing the conversion of dates to be inaccurate, resulting in a discrepancy in the target MOS.

How to Resolve the Issue

To resolve this issue, you can follow these steps:

Update the conversion code: Update the conversion code to use 30 (the number of days in a month) instead of NUMBER_OF_DAYS_IN_A_MONTH.
Re-migrate the data: Re-migrate the data from OG to omSupply using the updated conversion code.
Verify the target MOS: Verify that the target MOS is accurate and matches exactly after migration.

Conclusion

Introduction

In our previous article, we explored the issue of target MOS being slightly different after migration from one system to another. We discussed the root cause of this issue, provided a step-by-step guide on how to reproduce it, and suggested a fix to resolve the problem. In this article, we will answer some frequently asked questions (FAQs) related to this issue.

Q: What is the target MOS, and why is it important?

A: The target MOS (Minimum Order Quantity) is a critical parameter in inventory management systems. It represents the minimum quantity of a product that should be ordered to meet the demand. The target MOS is important because it helps to ensure that the inventory levels are adequate to meet the demand, while also minimizing the costs associated with overstocking or understocking.

Q: Why is the target MOS different after migration?

A: The target MOS is different after migration because of the way dates are being converted between the two systems. When migrating from OG to omSupply, the conversion of dates is not accurate, resulting in a discrepancy in the target MOS.

Q: What is the root cause of this issue?

A: The root cause of this issue is the use of NUMBER_OF_DAYS_IN_A_MONTH instead of 30 (the number of days in a month) when converting between daysToSupply.

Q: How can I reproduce this issue?

A: To reproduce this issue, follow these steps:

Create an internal order with OG: Create an internal order using the original system (OG).
Migrate to omSupply: Migrate the internal order from OG to the new system (omSupply).
Compare the target MOS: Compare the target MOS in OG with the target MOS in omSupply. You should notice that the target MOS is slightly different.

Q: What is the suggested fix for this issue?

A: The suggested fix is to use 30 (the number of days in a month) instead of NUMBER_OF_DAYS_IN_A_MONTH when converting between daysToSupply.

Q: How can I update the conversion code to use 30 instead of `NUMBER_OF_DAYS_IN_A_MONTH`?

A: To update the conversion code, follow these steps:

Identify the conversion code: Identify the code that is responsible for converting dates between the two systems.
Update the code: Update the code to use 30 (the number of days in a month) instead of NUMBER_OF_DAYS_IN_A_MONTH.
Test the code: Test the code to ensure that it is working correctly.

Q: What are the benefits of using 30 instead of `NUMBER_OF_DAYS_IN_A_MONTH`?

A: The benefits of using 30 instead of NUMBER_OF_DAYS_IN_A_MONTH include:

Improved accuracy: Using 30 instead of NUMBER_OF_DAYS_IN_A_MONTH ensures that the conversion of dates is accurate, resulting in a more accurate target MOS.
Reduced errors: Using 30 instead of NUMBER_OF_DAYS_IN_A_MONTH reduces the likelihood of errors in the target MOS, which can have significant consequences in inventory management systems.

Q: Can I use `NUMBER_OF_DAYS_IN_A_MONTH` in other contexts?

A: While NUMBER_OF_DAYS_IN_A_MONTH may be used in other contexts, it is not recommended to use it when converting between daysToSupply. This is because NUMBER_OF_DAYS_IN_A_MONTH is not a reliable value, and using it can result in inaccurate conversions.

Conclusion

In conclusion, the issue of target MOS being slightly different after migration can be attributed to the way dates are being converted between the two systems. By using 30 (the number of days in a month) instead of NUMBER_OF_DAYS_IN_A_MONTH when converting between daysToSupply, we can ensure that the conversion of dates is accurate, and the target MOS is calculated correctly.