Crop Cost Analysis and Transaction Traceability
When a crop cost is challenged, start with the ledger amount and follow the allocation to its source. Cost Drill-Down shows the destination, allocation basis, intermediate centre and underlying transaction. The key distinction is between the original transaction value and the share charged to the crop.
Before you begin
Agree the period, cost element and amount under review. A single transaction may contribute to several crop or WIP destinations.
Navigation: Top-right screen dropdown → Cost Drill-Down.
Procedure
- Select the ledger cost element. In the example, choose Spares.
- Review the destination totals, then select Farm crop: Potato.
- Check the allocation moves by cycle, basis, intermediate source and logical land.
- Select the relevant move. The worked trace uses Well 34 engine on P075-26.
- Read What caused it and compare the original transaction amount with Share here. Note the asset, job order and vendor bill.
- Use the breadcrumb buttons to return to an earlier level. Refer the source document or driver query to the responsible team.
Responsibilities and follow-up
The explanation should identify both the expense and the allocation basis. This allows finance to check the source document and operations to validate the land or resource assignment.
Worked trace: spare parts to potato
| Level | Example result |
|---|---|
| Ledger | Spares: SAR 500,000 |
| Final object | Farm crop: Potato: SAR 90,782.15 |
| Allocation move | Cycle 3; area basis; Well 34 engine; P075-26; SAR 7,645.17 |
| Source | MA-0096; material issue; Spares; asset ENG-34 |
| Supporting references | Job order JO-0111; vendor bill VB-07011 |
| Source amount / allocated share | SAR 14,016.15 / SAR 7,645.17 |
Important notes
Do not charge the full source amount to each destination when reviewing split allocations. The final grid provides transaction references; direct navigation from those references to native NetSuite records was not verified.
