Map CAM data to ERP fields
Map one lease, site, and statement year. That is the safest starting grain.
Then keep every source row below that key. Do not replace source labels with clean names.
OSCRE joins real estate data with enterprise records. Its model includes lease abstraction schemas.
Use that model as an ID guide. It does not supply a full CAM taxonomy.
Set the record grain
Start with one review record per lease year. Add the site and legal entity.
Use this canonical key:
entity + site + lease + statement year
Keep landlord and property as governed fields. Do not use names as the only keys.
Names can change or repeat. Stable IDs keep history joined.
The record grain should answer one question. Which lease-year record does this row support?
Map the core dimensions
Write one shared rule for each field. Give every field a data owner.
| Canonical field | Source example | Rule | Owner |
|---|---|---|---|
| Entity ID | Company code | Match legal entity | Finance data owner |
| Site ID | Location code | Match occupied site | Real estate owner |
| Property ID | Property record | Keep landlord property key | Real estate owner |
| Landlord ID | Vendor record | Match approved landlord | AP data owner |
| Lease ID | Lease record | Match signed lease | Lease data owner |
| Statement year | CAM statement | Use covered year | Firm reviewer |
| Charge label | Statement row | Keep source text | Firm reviewer |
| Charge type | Governed map | Use approved type | Data owner |
| Evidence ID | Review case | Keep stable ID | System owner |
Do not map a field from memory. Use a source record or approved rule.
Keep two charge fields
Preserve the landlord's exact charge label. Add a separate standard charge type.
For example:
| Source label | Normalized type | Mapping state |
|---|---|---|
| Snow service | Exterior maintenance | Approved |
| Admin charge | Management fee | Review needed |
| Prior year true up | True-up | Approved |
| Other expense | Unmapped | Blocked |
These examples show a mapping pattern. They do not decide lease treatment.
The source label supports trace work. The standard type supports reports and rules.
Do not erase the source label after mapping.
Do not force Other expense into a guessed type.
Use named error states
Reject rows that lack a safe key. Do not send them into a report.
| Error state | Meaning | Next action |
|---|---|---|
entity_unmatched |
No approved entity match | Route to finance owner |
site_unmatched |
No approved site match | Route to site owner |
lease_missing |
No signed lease link | Request the lease |
year_missing |
Statement year is absent | Request source proof |
charge_unmapped |
No approved charge type | Route to map owner |
key_collision |
Two records share one key | Stop and resolve |
source_missing |
Source row cannot be traced | Reject the row |
An error is not a CAM finding. It is a data control result.
Keep the original row with the error. Also keep the person assigned to resolve it.
Preserve source lineage
Each mapped row needs a source trail. Store more than a file name.
Keep these fields:
- Source file ID
- Source file name
- Source page
- Source row label
- Source row amount
- Import time
- Mapping version
- Approval record
Do not claim the ERP can show each field. The consultant chooses supported storage options.
Oracle custom segments can sort some records. They can affect GL reports and filters. Oracle lists those options here.
Use features enabled for that client. A custom segment is not a CAM audit.
Version every mapping
Mappings change as new labels arrive. Give each approved map a version.
Store:
- Version ID
- Effective date
- Approved owner
- Changed source label
- Old type
- New type
- Reason
- Backfill choice
Do not rewrite old reports without approval. Record any backfill as a separate action.
A new map should pass sample tests. It should also reject unknown labels.
Stop many-to-one mistakes
One clean dimension can hide several sources. That can break lease-year trace work.
Reject these cases:
- Two leases share one lease ID
- Two sites share one location code
- Two years share one statement record
- Two landlords share one vendor alias
- Several rows lose their source IDs
Some many-to-one maps may be valid. The data owner must approve them in writing.
Keep the reason beside the map. Do not treat an exception as a default.
Test ten source rows
Start with a small data profile. Ten rows can expose basic map gaps.
Choose rows with different source labels. Include one missing or unclear label.
For each row, test:
- Does the entity match?
- Does the site match?
- Does the lease match?
- Does the statement year exist?
- Does the source row stay linked?
- Does the charge type have approval?
- Does an error stop the row?
This test does not prove full coverage. It shows whether the map can reject gaps.
Walk one sample map
River Bend Foods is a made-up example. Its names and records are made up.
River Bend Foods has one leased site.
Its entity code is RBF-01.
The site code is DAL-07.
The lease ID is L-441.
A 2025 statement has three charge rows. Two labels have approved maps.
The third label says Other expense.
It enters the unmapped-charge state.
The data owner reviews that source row. No report gets a guessed charge type.
The approved rows keep their source pages.
They also keep mapping version CAM-3.
Copy the mapping sheet
Use this table before data build work.
| Field | Source | Rule | Error | Owner |
|---|---|---|---|---|
| Entity ID | ||||
| Site ID | ||||
| Property ID | ||||
| Landlord ID | ||||
| Lease ID | ||||
| Statement year | ||||
| Charge label | ||||
| Charge type | ||||
| Evidence ID |
The system guide maps system bounds. The NetSuite guide maps case states. The advisory guide defines the firm service.
The resource hub holds more data controls.
See the ERP consultant pillar for service scope.
Map other firm paths in the Practice Growth hub.
Where CAMAudit fits
ERP consultants can add this review to the source map.
The mapping sheet needs a reviewed source record. CAMAudit can provide that CAM review record.
It reads the lease and CAM files supplied. Fixed math checks may flag a source row.
That row can keep its source line. Your data owner maps only approved work.
First, your firm reviews and signs the branded CAM audit. The data owner then starts the system handoff.
A dispute letter draft stays with the firm reviewer. The ERP map does not approve that draft.
It is not legal advice. Have counsel review before sending.
CAMAudit does not own your ERP data rules. Your ERP map has no native CAMAudit connector.
Name the data owner in the service line guide.
Ready to add this work to your firm? Get started.
Sources
- OSCRE Industry Data Model, current page
- Oracle custom segments, current help
- Oracle flow issue help, current page
- Oracle vendor bill exception criteria, current help