Customer Portal Export

1. Choose the customer and the four files

Customer

Use exports from the same day, so the dates are current.

The customer's file from the portal Downloaded from the customer's portal (Assia: Delivery Schedule)

AX WIP Status Report Supplier side: production status and confirmed date

AX Sales Order Status Report Customer side: the customer's order lines (Assia: account 2046117)

Salesforce EQ list Open EQ cases, list view EQ_TR_IN1

2. Check and download

0rows filled

0rows left as they were

0rows in the customer's file

Only Qty, Delivery Date, Status and Comment are written. Every other cell stays as the customer sent it.

Run ID: – — quote it when you report a problem

Why a row was left as it was	Rows

Our order status

A list of every order line in the AX report, with status, confirmed date and comment in our own words. It does not need the customer's file. Use the Excel to check the status yourself. The JSON is the same list for another program.

AX WIP Status Report Supplier side: production status and confirmed date

AX Sales Order Status Report The order lines to list

Salesforce EQ list Open EQ cases, list view EQ_TR_IN1

Files chosen in "Fill customer file" are used here too.

How to test

Download the customer's file from their portal (Assia: the Delivery Schedule screen).
On the same day, export two reports from AX as Excel: the WIP Status Report and the Sales Order Status Report for the customer's account (Assia: 2046117).
Export the Salesforce EQ list (list view EQ_TR_IN1) as Excel.
Open "Fill customer file", choose the customer, add the four files and click Fill.
Download the filled file and open it in Excel. Compare five rows with AX: status, confirmed date and comment.

Please check especially

Only Qty, Delivery Date, Status and Comment changed. Every other column is as the customer sent it.
The rows under "Why a row was left as it was" really cannot be filled.
Split lines (the same Line ID on several rows) keep the customer's quantities.
Rows with an open EQ case show the EQ status, not "In Production".

How it works

The tool finds each line of the customer's file in AX by PO number and part number.
An open EQ case sets "waiting for the customer" or "waiting for the vendor". Otherwise an open AX line sets "in production", with the AX confirmed date and the AX production text as comment. Each customer's own words come from that customer's profile (Assia: "EQ waiting for Assia", "In Production").
A date is only written when AX has one. The tool never guesses a date.
Lines it cannot decide are left as they were and listed with the reason.

Feedback

For every problem send the Run ID from the result, the row number in the customer's file, what you expected and what you got.

Known limits of this test version

Lines already invoiced in AX are left as they are. We are still clarifying with the customer how they should look.
Rows without a matching line in the AX Sales Order report stay empty.
Upload a filled file to the customer's portal only after your IBR contact agreed.