| Identification FastTab |
|
|
| Identification |
|
|
| EDI number |
EDI Staging table record id |
Change EDI number |
| Company |
Legal entity of the document |
|
| Company GLN |
The company’s global location number is shown here |
Company GLN |
| Template Id |
The EDI template that will be used to create the outbound file |
Trading partner > Template assigned to document type |
| Staging to target status |
The current status of the staging record. Options include: • Not Started – The staging record has been created but no outbound file has yet been generated. • Error – The staging record has been processed, but no outbound file has been created. There are errors with the staging record that needs to be reviewed. • Completed – The staging record has been succesfully processed and added to the outbound file queue. • Canceled – The record has been manually canceled and will be excluded from processing. |
|
| Reset status |
|
|
| Reset status profile |
Reset status profile assigned to the file/document. This will default from EDI shared parameters or can be overridden on Trading partner’s incoming and outgoing documents. The profile can also be changed to another profile which will also reset the Reset status attempts to 0 and reset the Reset status date/time |
|
| Reset status date/time |
Next date/time automatic reset status will run |
|
| Reset status attempts |
Number of reset attempts already processed. The reset attempts will stop once this number reaches the End after as per assigned Reset status profile’s Recurrence |
|
| Recurrence |
Recurrence text. Contains standard details of Recurrence, for example: • Interval (recurrence pattern) • How many times the period will run (End after) • From date/time the recurrence will start |
|
| Overview |
|
|
| Purchase order |
The D365 purchase order number |
|
| Purchase order date |
The original purchase order date from the purchase order is shown here |
Original order date |
| Purchase change date |
The change purchase order date from the PO is shown here |
Change order date |
| EDI order type |
The EDI order type is shown here. Mapped value from Order type group |
Order type |
| EDI order purpose |
The EDI order purpose is shown here. Mapped value from Order purpose group |
Order purpose code |
| Status |
|
|
| Group control number |
Group control number for the outbound document. To be used to match inbound functional acknowledgement, where applicable. |
|
| Received |
Indicates if the Functional acknowledgement inbound has been received from the trading partner for the outbound document record. |
|
| General FastTab |
|
|
| Details |
|
|
| Vendor reference |
Vendor’s order reference |
|
| Vendor account |
Vendor assigned to the purchase order |
|
| Vendor name |
Vendor name |
|
| Trading partner GLN |
The vendor’s global location number is shown here. |
Trading partner GLN |
| Company GLN |
The company’s global location number is shown here. |
|
| Buyer group |
The Purchase Order’s Buyer group is shown here. |
Buyer group |
| Buyer name |
Buyer name |
|
| Buyer email |
Buyer email |
|
| Buyer phone |
Buyer phone |
|
| Company phone |
Company phone |
|
| Company name |
Company name |
|
| Tax registration number |
Company tax registration number |
|
| Vendor invoicing |
|
|
| Vendor name |
Vendor name |
|
| Vendor primary street number |
Vendor primary address - street number |
|
| Vendor primary street |
Vendor primary address - street |
|
| Vendor primary city |
Vendor primary address - city |
|
| Vendor primary county |
Vendor primary address - county |
|
| Vendor primary state |
Vendor primary address - state |
|
| Vendor primary ZIP/postal code |
Vendor primary address - ZIP/postal code |
|
| Vendor primary country/region |
Vendor primary address – country/region |
|
| Tax exempt number |
Vendor tax exempt number |
|
| Customer invoicing |
|
|
| Our account number |
Bill to - Our account number in the vendor’s system. As per ‘Our account number’ loaded on Vendor’s Invoice account |
Bill to |
| Name |
Bill to - Name |
|
| Name or description |
Bill to - Invoice address name |
|
| Street number |
Bill to - Street number |
|
| Street |
Bill to - Street |
|
| City |
Bill to - City |
|
| County |
Bill to - County |
|
| State |
Bill to - State |
|
| ZIP/postal code |
Bill to - ZIP/postal code |
|
| Country/region |
Bill to - Country/region |
|
| Version |
|
|
| PO version number |
The version of the D365 purchase order number |
Change version number |
| Created date and time |
The date and time the selected record was created in the staging table |
|
| Acknowledgement requested |
Indicates if functional acknowledgement has been requested from the trading partner for the outbound document. |
|
| Agreement |
|
|
| Purchase agreement |
The D365 purchase agreement number (applicable for release orders) |
|
| Effective date |
Purchase agreement effective date |
|
| Expiration date |
Purchase agreement expiration date |
|
| Delivery |
|
|
| Delivery name |
Ship to - Name |
|
| Our account number |
Ship to - Our account number in the vendor’s system. As per ‘Our account number’ loaded on Vendor’s Order account Ship to |
|
| Store code |
Ship to - Store code |
|
| Street number |
Ship to - Street number |
|
| Street |
Ship to - Street |
|
| City |
Ship to - City |
|
| County |
Ship to - County |
|
| State |
Ship to - State |
|
| ZIP/postal code |
Ship to - ZIP/postal code |
|
| Country/region |
Ship to - Country/region |
|
| ISO |
Ship to - Country/region ISO |
|
| Latitude |
Ship to - Latitude |
|
| Longitude |
Ship to - Longitude |
|
| Delivery date |
Required receipt date |
Delivery date |
| Confirmed receipt date |
Acknowledged delivery date from the Vendor purchase order acknowledgement. Purchase order’s Confirmed receipt date. |
|
| Site |
Storage dimension - Site |
Site |
| Warehouse |
Storage dimension - Warehouse |
Warehouse |
| Delivery terms |
Delivery terms |
|
| Delivery mode |
Delivery mode |
|
| Text |
Header note to be sent with purchase order |
|
| Requester |
Requester |
Requester |
| Requester email |
Requester’s primary email |
|
| Requester phone |
Requester’s primary phone |
|
| Attention information |
Attention information |
|
| Transportation |
|
|
| Shipping carrier |
Shipping carrier |
|
| Carrier qualifier |
Code designating the system/method of code structure used for shipping carrier |
|
| EDI carrier mode |
Code specifying the method or type of transportation for the shipment. Mapped value from Carrier mode |
|
| Miscellaneous |
|
|
| Misc. indicator |
Code which indicates an allowance or charge for the service specified. Mapped value from Misc. charge/allowance indicator |
|
| EDI charges code |
Code identifying the service, promotion, allowance, or charge. Mapped value from Charges code |
|
| Totals |
|
|
| Subtotal amount |
Subtotal of all purchase order lines |
|
| Line discount |
Discount for all purchase order lines |
|
| Misc. amount |
Purchase order header Misc. charge/allowance amount |
|
| Tax amount |
Tax amount |
|
| Round-off |
Round-off |
|
| Total amount |
Total amount |
|
| Payment |
|
|
| Currency |
Currency |
|
| Terms code |
Payment terms. Mapped value from Payment terms type group |
|
| Terms net days |
Payment terms net due days calculated from delivery date. Example with delivery date 16/04/2019 • Current month + 30 days = 44 • Current month + 2 months + 20 days and payment day = 15th = 90 • Current quarter + 15 days = 90 • Current year + 1 month = 290 • Current week + 7 days = 11 • Net + 1 month + 15 days = 45 • COD = 0 |
|
| Cash discount |
Settlement discount percentage |
|
| Days |
Settlement days |
|
| Discount amount |
Settlement discount amount if paid within settlement days |
|