Overview
Occasionally, data entered or updated in your ERP system may not appear as expected in AGR.
In this article, we’ll explore potential reasons for this issue and outline steps you can take to resolve it.
User Error
Did you verify if there aren't any filters active or that you're looking in the right place?
Example - Missing item
Check if the item is Blocked/Blocked for purchasing (the names of these fields will depend on your ERP's data mapping).
Items marked as such will not be visible at all or appear as Closed at AGR.
AGR filters out items marked as "Closed" through a default filter in View Settings.
Change it from "No" to "Yes" to see all closed items.
Data Management Settings
Did you filter out a particular item group/vendor/replenishment system in Data Management?
Have you configured your location setup to merge locations?
Is the ERP stock considering the same location(s) as AGR? You can see which locations AGR is considering in Settings > Location setup.
Data Mapping
Remember to check your Data Mapping document for any ERP conditions. Only the items that fulfill those conditions will be brought into AGR.
Populate any missing fields or update existing ones to the expected values
Watch out for if customizations have been implemented
Example - Items with variants
When an item has at least one variant assigned to it, standard AGR mapping is that the original item will not appear in AGR.
It's possible to define multiple variants for the same item, but each Item + Variant combination should be mapped into AGR as a separate item.
Refer to our ERP-specific data mapping documents to identify the criteria that apply to your items:
If you don't see your ERP here, contact your CSM/Integration Engineer.
Data Sync Failed or Late Updates
Is it possible that the data on your ERP side has been updated since the last successful data sync with AGR?
Also, the data sync may have failed during the night. Check the Data Management > Data Refresh tab to verify its status and contact your CSM if needed.
Example - AGR stock doesn't match ERP stock
A stock transaction has been posted to the Item Ledger (BC) or equivalent transaction table in your ERP after AGR's daily job (around midnight):
AGR takes a snapshot of the data at that point, so if a purchase order was received after the snapshot was taken, it will show in the stock the next time AGR updates data (tomorrow). In this case, the quantity will show as Undelivered in AGR.
Unbooked transfer order from another location
For BC/NAV users: If an Item number is changed, it can cause discrepancies in the Item Ledger Entry table and incorrect stock quantities to be presented in AGR.
Higher-Level Updates Don’t Reflect at Item Level
AGR manages records on an item-per-location basis as its lowest level, so if you filled in or altered data on a vendor card, for example, the item card will have priority over it.