Inbound PO Portal · APAC
Not loaded yet Signed in as … ·

Inbound PO Tracking

How the priority works: the AI Priority is decided by AI from Available Qty to Reserve, the SharePoint forecast (this month and the next two months), remaining quantity, delivery timing and Cargo Ready Date slips, with a one-line remark (hover the label under the badge, or open the line). It also checks the forecast file for mistakes. Only these numbers and the item code are sent to the AI. Not in forecast = the item is not in the SharePoint forecast file, so it is set to Low (hover for the remark). None = remaining qty is 0, nothing left to receive. Rule-based = the AI could not answer, so a simple backup rule was used. Where the AI is unavailable the line shows Rules instead: High when Available Qty to Reserve is below this month's forecast, Medium when it is covered, Low when slow moving. Ops Override always wins.
to
0 selected
Cargo Ready Date changes:
red = pushed later than the previous version, teal = pulled earlier. The previous date is shown underneath; expand a row for the full history.
Retrieving Cargo Ready Date changes…0s
PO / Item Supplier / Requisition BU Transit / Shipping Cargo Ready Date Requested Delivery Date Promised Delivery Date (ETD) Expected Receipt Date PO Line Qty Receipt Qty Delivered Qty Remaining Qty Avail. Qty to Reserve Status PO Priority AI Priority Ops Override
Loading PO data…
0s elapsed
Still running the script against Oracle Fusion. Please keep this tab open.