Updating UOM value on Cost Projections

Yes, bulk updating UOM on Cost Projections is possible in principle, but NOT through GI Mass Update or Import Scenario directly in most standard setups unless the screen is explicitly designed for editing. What you are seeing is expected behavior.

🔎 Why your approaches are failing

1. Generic Inquiry + Mass Update (not working)

Cost Projections (PM Cost Projections) are typically:

• System-generated / calculated records
• Backed by read-only DAC logic or restricted update views
• Often not designed for direct mass update via GI

👉 Even if you expose the field, Acumatica blocks updates because:

• The underlying view is not updateable
• Or the record requires workflow/state validation

2. Import Scenario (errors like “View Document” / “Add button disabled”)

This happens because:

• The screen is likely a processing or inquiry screen, not a true data-entry screen
• Import scenario is trying to use:
  • AddNew (Insert) or Edit (Update) actions that are disabled in UI
• Cost Projection records often require:
  • A parent document context (Project / Budget / Transaction source)

👉 So Import Scenario cannot “attach” to a valid insert/update action

⚠️ Key Design Point (important)

Cost Projections are usually:

• Derived data (calculated from project transactions / planning engine)
• Not meant to be manually mass-maintained

So UOM being blank means:

• It was not populated from source transaction or item setup
• Or projection logic did not enforce it

✅ What actually works (supported approaches)

✔ Option 1 — Fix at source (BEST / recommended)

Instead of updating Cost Projections:

Fix where UOM originates from:

• Stock Items (IN202500)
• Project Cost Budget setup
• Billing rules / project transaction source

Then:
👉 Regenerate projections

This ensures consistency across:

• Projects (PM)
• Inventory (IN)
• Cost Projection engine

✔ Option 2 — Use SQL update (ONLY if allowed in your environment)

If this is a one-time correction and you are on-prem:

You may update directly in:

• PMCostProjection table (or equivalent DAC table)

But:
⚠️ This is NOT recommended unless:

• You fully understand projection recalculation impact
• You will rebuild projections afterward

✔ Option 3 — Custom DAC / Custom screen (proper technical fix)

If business requirement is ongoing:

• Create a custom screen over Cost Projection DAC
• Enable:
  • AllowUpdate = true
  • Proper selectors for UOM validation
• Add processing screen for mass update

✔ Option 4 — Force recalculation/regeneration

If projections are derived:

1. Clear projections (if allowed)
2. Re-run:
   • Project billing / planning / projection process
3. Ensure UOM is populated from source master data

❌ What will NOT work (as you already saw)

• GI Mass Update on projection table
• Import Scenario using Add/Edit screen actions
• UI-based updates on projection inquiry screens
• Updating without valid document context

💡 Practical recommendation for your case

Since your goal is simply:

“Set empty UOM to EA in bulk”

The safest path is:

✔ Check where UOM should come from:

• Item master (IN202500)
• Project Cost Code setup
• Project budget line defaults

✔ Fix that source

✔ Re-run projection generation

If you want, I can help you pinpoint exact source

If you tell me:

• Screen name of Cost Projection (PMxxxxxxx?)
• Whether it is Project Cost Projection or something custom
• How records were generated (planning, billing, import, etc.)

I can tell you the exact field that controls UOM and the clean fix path (no guessing, no SQL).