Excludes some orders/Order Types from MRP

Dealing with orphaned data from a system conversion can indeed be challenging, especially when it impacts your MRP (Material Requirements Planning) calculations. Fortunately, there are several ways you can exclude this data temporarily or permanently, depending on your needs. Here are some methods and suggestions for how you can approach this issue in Acumatica:

1. Using Data Buckets or Data Segmentation

Although Acumatica doesn’t have an explicit "bucket" feature for isolating old or orphaned data, there are several ways to segment or exclude these records based on their characteristics.

Option 1: Use Financial Periods

• Close the Orphaned Data Period: If the orphaned data is from 2022, ensure that the financial periods related to this data are closed. While this won’t prevent the data from being visible, it may prevent it from being included in certain operational workflows like MRP.
• Segmentation by Date: For any reports, dashboards, or MRP calculations, use date filters or set up specific filters to exclude data from 2022 or any other periods where orphaned data exists. This approach will help you isolate and exclude old or irrelevant data while your reconciliation is still in progress.

Option 2: Custom Attributes or Flags

• Custom Fields: You can create a custom field on relevant entities like sales orders, purchase orders, or inventory transactions to flag orphaned data. For instance, you can create a boolean field called IsOrphaned and mark all affected records. Then, modify your reports and processes to exclude these flagged records.
• This custom field can be used in your MRP and reporting filters, ensuring orphaned data is ignored until it’s fully reconciled.

2. Adjusting MRP Calculation Logic

Acumatica’s MRP system looks at various data sources such as open sales orders, purchase orders, production orders, and inventory quantities to calculate material requirements. If the orphaned data is interfering with your MRP, you can implement the following strategies:

• Ignore Past Orders: Modify your MRP configuration to exclude older sales and purchase orders. Most MRP systems allow you to set a horizon date or filter out orders beyond a certain period (like orders older than a year).
• Custom MRP Filters: Implement custom logic or filters for your MRP runs, so the system ignores data from 2022. For instance, you can modify the queries used for MRP calculations to exclude transactions from 2022 or tagged as "orphaned."

How to Exclude Orphaned Data from MRP:

• Examine MRP Input Tables: Look into which tables are being used for your MRP calculations (e.g., SOOrder, POOrder, INItemPlan). Identify if the orphaned data resides in these tables.
• Apply filters based on date or custom flags (like the IsOrphaned field) to ensure that these entries are ignored in the MRP run.
• Use Open Status Filters: Ensure that only open orders with valid dates and statuses are included in the MRP, further reducing the chance of orphaned data affecting calculations.

3. Data Cleansing Options

Another way to handle orphaned data is through data cleansing. You can either remove or archive the orphaned records so that they no longer interfere with system operations.

Option 1: Archiving the Orphaned Data

• Export & Archive: Export the orphaned 2022 data into an external archive, and then mark it as "archived" within Acumatica. You can create a custom archive status or use existing fields (such as document status) to indicate that these records should no longer be used.
• Once marked or archived, modify your MRP and reporting processes to exclude these archived records.

Option 2: Data Removal

• If the orphaned data is not needed for future reference or auditing purposes, consider removing it altogether. You can use Acumatica’s data purge features to clean out old or incorrect records.
• Be sure to back up the data before performing any deletion and ensure that any removal process does not affect system integrity.

4. Manual Reconciliation and Cleanup

If the orphaned data is causing significant disruption, it may be worthwhile to manually reconcile the data, even though it’s time-consuming.

• Batch Processing: If you need to reconcile large amounts of data, consider using batch processing. Acumatica allows you to update or modify large sets of data using import/export scenarios or automation to streamline the process. This could help reduce the time spent on manual cleanup.
• You can automate certain tasks, such as marking old records as orphaned or updating their statuses to indicate they should be excluded from the MRP and other processes.

5. Leveraging Business Events

• You can set up business events to automatically flag or categorize orphaned data based on specific conditions, such as older transaction dates or incomplete records.
• This helps in catching any orphaned records as they are identified and ensuring they are ignored in future system calculations or processes.

6. Work with Acumatica Partner or Consultant

If the orphaned data is complex or pervasive, you may want to work with an Acumatica consultant to implement more advanced filtering or to adjust the system configuration to better manage the legacy data. A consultant can help create custom scripts or filters to ensure the orphaned data doesn’t affect your MRP numbers while also ensuring data integrity.

Summary of Steps:

1. Use Financial Periods: Close the periods related to orphaned data or exclude old periods in your MRP runs.
2. Create Custom Fields or Flags: Flag the orphaned data using custom fields and exclude it from reports and MRP processes.
3. Exclude from MRP: Adjust MRP calculations to filter out old or orphaned transactions.
4. Archive or Remove Data: Consider archiving or purging orphaned data from the system.
5. Automate Cleanup with Business Events: Automate reconciliation tasks or set up business events to manage orphaned data dynamically.