Vendor purchase order acknowledgement

Companies may require a vendor to send a purchase order acknowledgement (POA) for an order and can be one of the reasons a purchase order status is ‘In external review’.
Where the Vendor purchase order document setting profile Acknowledgement required is set to Yes, the purchase order status will be set to In external review upon confirmation.

The following subsections will describe how to view, process the acknowledgement and send a Vendor purchase order confirmation (if required).
The Acknowledgement can be viewed from the Purchase order and confirmation values will be populated with default values per Trading partner.
The Confirmation can be either manually processed or automatically.
Viewing the Staging table records will also be discussed. The processed purchase order acknowledgement and sent confirmation record(s) can be viewed for a purchase order, by selecting the History button on the EDI tab on the Action Pane of the Purchase order page.

Prerequisites

The following setup is prerequisites for the vendor purchase order acknowledgement

1. Create POA response code groups to map the vendor’s values to EDI POA responses code groups.
2. Create Template for the document.
3. Create Setting profile for the document.
4. Create Validation profile for the document.
5. If the vendor trading partner doesn’t exist, create the new trading partner.
6. Assign the applicable POA response code group to the vendor trading partner.
7. Add and enable the vendor purchase order acknowledgement document to the Vendor trading partner and select the applicable:
   • Template
   • Setting profile
   • Validation profile
   • Search mask

Processing

Inbound files have the following three steps:

1. Import - Imported file can be viewed in EDI > Files > Inbound files
2. Import to staging - Imported file is processed to staging record/s. The staging record/s can be viewed at EDI > Documents > Vendor documents > Vendor purchase order acknowledgement
3. Staging to target - The staging record/s is processed to target. If the acknowledgement is succefully processed the corresponding D365 purchase can be updated as per the received vendor values

Create document

Header checks for Vendor purchase order acknowledgement

Header checks are performed when:

1. Importing Vendor purchase order acknowledgement file
2. Processing from import to staging
3. Processing from staging to target

Step 1 - Import

When a purchase order acknowledgement file is imported, the file name is key to identifying the vendor and therefore the document template. See Trading partners for further details. It is based on this document template that the data within the file is identified and a record created in the EDI staging table in the next step.

Note: The file mask is used to identify the trading partner and therefore template

Step 2 - Import to staging - Inbound file validation

When the purchase order acknowledgement file is retrieved and imported, there are various validations that are completed before the staging record is created in the EDI staging table. If the processing of Import to staging errors, the Inbound file’s Status will be set to Error and no staging record created.

Rule Id	Details
Check Template	Identify a template for the Vendor/Document type. This will be used to identify the whereabouts of data within the file

Possible issues and fixes

Import to staging errors for Vendor purchase order acknowledgements can be viewed in:

• EDI > Files > Inbound files filtered to Status set to Error
• EDI > Document maintenance, tab Vendor documents, tile File import errors

At this step the issues are usually around the file not matching the template.

• Does the file have the correct template assigned (General tab, field Template):
  • No: Use Reset template to assign a different template. If this should apply to future documents for the Trading partner, also update in Trading partners.
  • Yes: Review Log and fix the applicable template in EDI > Setup > Document types. Examples issues are date format, new field.

Example error for file not matching template: ‘Segment ‘<xml’ not found in EDI template mapping’

Step 3 - Staging to target

If the processing of Staging to target errors, the staging record’s Staging to target status will be set to Error and the acknowledgement won’t be created on the target D365 purchase order.

Staging line validation - Purchase order acknowledgement

Rule Id	Details	Error
PO line number	Find the D365 purchase order line number to which the POA line belongs	Error at Staging table. No target POA created
No Valid Item	No valid item based on the different options available	Error at Staging table. No target POA created

Possible issues and fixes

Staging to target errors for Vendor purchase order acknowledgements can be viewed in:

• EDI > Documents > Vendor documents > Vendor purchase order acknowledgement filtered to Staging to target tatus set to Error
• EDI > Document maintenance, tab Vendor documents, tile Purchase order acknowledgement errors
• EDI > Document maintenance, tab Vendor documents, Documents page, tab POA

At this step the issues are usually around mapping/business logic issues.
Review the Log or Version log for the applicable record to find the issue. Example errors and method to fix are discussed in below table.
Example errors and possible fixes are discussed in FAQ

Validation

Validation profiles can be specified and linked to the template along with a rule error tolerance which is used to determine how D365 will react. Options are:

• Info - An infolog is displayed with information only, it is not identified as a warning
• Warning - An infolog is displayed with a warning. It is possible to carry on processing
• Error - An infolog is displayed with an error. It is not possible to carry on processing until the error has been corrected. EDI Status = Error

The following table describes each validation option for the Vendor purchase order akcnowledgement document. It also describes if the validation rule is not met, but only has an info or warning error tolerance, how the target D365 purchase order will be updated.

Rule Id	Details	Info/Warning tolerance updates
Purchase order header
Reject	Vendor POA response: Header – not accepted. Vendor rejects the complete purchase order. This validation can be used to manually manage Vendor rejections by adding this validation with an error tolerance.	Cancel purchase order
Version	Validates that the vendor is responding to the current purchase order version	No update to D365 PO, only used for comparison
Delivery date	Vendor POA response: Header – change. The Vendor’s POA delivery date doesn’t match the D365 PO’s delivery date	Update PO header’s Confirmed delivery date
Vendor reference	Vendor POA’s Vendor reference doesn’t match the PO’s Vendor reference	Update PO header’s Vendor reference
Purchase order line
Short pick	Vendor POA response: Line shipment - partial. Acknowledgement qty is less than purchase order line qty. If the vendor’s unit differs, unit conversion is used to convert.	Update PO line’s deliver remainder qty (use unit conversion if POA different unit).
Batch Id update	Where the batch id received is different to the batch id on the purchase order.	If batch doesn’t exist for item, the batch is created and assigned to the purchase order line
Purchase price	Vendor POA response: Line price advise. The vendor’s POA unit price should be checked using the purchase order unit price. If the prices are slightly different it should check both the tolerance and ‘Use Vendor Price’ flag before giving an error/warning. Example: Item X purchase order unit price 10.25 Item Y purchase order unit price 8.88 Vendor has a min and max tolerance setting of 0.05 Purchase order prices are not including tax Vendor sends their EDI POA including tax The setting use vendor pricing is given Item X EDI file price (before converting) 11.26 (after conversion) 10.24 Item Y EDI file price (before converting) 9.70 (after conversion) 8.82. Template setting against this field is warning. A warning is only given for Item Y because it is outside of the tolerance.	Update PO line’s purchase price (if within allowed variance): else error
Delivery date	The Vendor’s POA line delivery date doesn’t match the PO delivery date	Update PO line confirmed delivery date
Reject	Vendor POA response: Line item – out of stock Vendor POA response: Line item – withdrawn Vendor rejects the purchase order line	Cancel purchase order line’s deliver remainder
Minimum/maximum quantity	The POA quantity should be devisable by the multiple specified on the Default/Site order settings table. Use unit conversion if POA unit of measurement differs. Need to set to Error if not allowed to increase deliver remainder over purchase order line over-delivery%	Update PO line deliver remainder.
Line item added	The POA contains a new line for the purchase order. Example: another line is cancelled and replaced with this new line.	Add new line to D365 PO

Override error validation

Where a Vendor purchase order acknowledgement staging record has errored because of Error tolerance validation, button Override error validation can be used to override and process to target.

The button is available on:

• EDI > Vendor workspaces > EDI purchase order processing. Select the Validation tab and select POA Errors under Processing or the tile under Summary.
• EDI > Documents > Vendor documents > Vendor purchase order acknowledgement. Button is enabled when status is not completed or canceled.

Purchase order

Users can access All purchase orders page by navigating to Accounts payable > Purchase orders > All purchase orders and manage the EDI POA’s Confirmation details by using the below buttons that have been added to the EDI tab on the Action Pane.

Field	Description
Confirmation	Select the Confirmation button to review vendor’s POA for the D365 PO. The details of this page will be discussed in below.
Send to EDI	Select the Send to EDI button to create Purchase Order Confirmation (POC) staging table record. The button will only be available if a POA has been received from the Vendor.
Reset flag	Select the Reset flag button to reset the EDI status to allow for re-sending of the POC to the staging table. Note: The POC record on the staging table should be deleted manually before the sales order flag is reset.

Processing Purchase order confirmation (POC)

The POC can be sent manually or automatically to the vendor. Both of these options will be discussed in the following subsections.

Manually processing Purchase order confirmation

The Confirmation page is accessed by navigating to Accounts payable > Purchase orders > All purchase orders, and selecting Confirmation on the EDI tab on the Action Pane. A list of outstanding confirmations can also be accessed by navigating to EDI > Vendor workspaces > EDI purchase order processing and either selecting the tile or tab called Pending POA confirm.

The Confirmation page is split into five tabs:

1. Header - Manage the POC header’s response for ship and receipt dates.
2. Line price - Manage the POC line’ price response, example vendor’s POA purchase price vs. D365 PO line system price.
3. Line quantity - Manage the POC line quantity response, example vendor’s POA purchase quantity vs. D365 PO line quantity.
4. Line date - Manage the POC line date response, example vendor’s POA acknowledged delivery date vs. D365 PO line’s requested delivery date. Used to update PO line’s confirmed delivery date.
5. Line pack - Manage the POC line pack response, example Vendor pack vs. System pack
6. Line inner - Manage the POC line inner response, example Vendor inner vs. System inner

Vendor mapped values for POA response codes are setup in POA response code group and assigned to the Vendor trading partner’s POA response code group.

Header

The following tables describe the fields and buttons that are available on the Header tab of the Confirmation page.
The Header POC response codes are managed on this tab.

Fields

Field	Description
Response code	Vendor’s purchase order acknowledgement header response
Vendor delivery date	Vendor’s acknowledged delivery date (updates D365 PO header confirmed delivery date)
System delivery date	D365 purchase order requested receipt date
Confirmed delivery date	Confirmed delivery date (to be sent on Purchase order confirmation)
Confirmation auto triggered	Indicates if the Confirmed delivery date is an auto triggered value

Buttons

It is possible to update the POC’s confirmed values by using the available buttons:

Button	Description
Confirmation response	Manually select Purchase order confirmation response: • Accept acknowledgement – Update PO Header and Lines with POA’s Header and Lines data • Accept delivery date – Updates only delivery date • Auto set confirmation – Auto trigger all confirmed values for all tabs

Line price

The following tables describe the fields and buttons that are available on the Line price tab of the Confirmation page.

Fields

Field	Description
Log	This will show a warning if Validation failed with error tolerance set to warning
Item number	Item number from the purchase order
Barcode	Barcode for the item number from the purchase order
Product Name	Item name for the item number from the purchase order
Unit	Unit from the purchase line
Vendor price	Price received in the purchase order acknowledgement, converted to purchase unit where POA unit different to PO unit
System price	Unit price from D365 purchase order
Confirmed price	Confirmed price to be sent on the purchase order confirmation (POC) to the vendor. Note: The confirmed price will be set as either the vendor or system values dependant on the parameter set on the POA setting profile: • Use vendor price (Y/N), and if Y falls within variance range: • Maximum negative price variance • Maximum positive price variance
Confirmation auto triggered	Indicates if the Confirmed price is an auto triggered value

Buttons

It is possible to update the Purchase order and Confirmed values by using the available buttons for a particular or multiple lines:

Button	Description
Display dimensions	Update the dimensions displayed on the Confirmation page
Use system price	No update to Purchase order. Updates the Confirmed price field to the system price
Use vendor price	Update the Purchase order line’s unit price and Confirmed price field to the vendor price

Line quantity

The following tables describe the fields and buttons that are available on the Line quantity tab of the Confirmation page.

Fields

Field	Description
Log	This will show a warning if Validation failed with error tolerance set to warning
Item number	Item number from the purchase order
Barcode	Barcode for the item number from the purchase order
Product Name	Item name for the item number from the purchase order
Unit	Unit from the purchase line
Vendor quantity	Quantity received in the purchase order acknowledgement, converted to purchase unit where POA unit different to PO unit
System quantity	Purchase quantity for each purchase line (deliver remainder).
Confirmed quantity	Confirmed quantity to be sent on the purchase order confirmation (POC) to the vendor. Note: The confirmed quantity will be set as the vendor quantity if min/max validation allows update of deliver remainder, else system quantity
Confirmation auto triggered	Indicates if the Confirmed quantity is an auto triggered value

Buttons

It is possible to update the Purchase order and Confirmed values by using the available buttons for a particular or multiple lines:

Button	Description
Display dimensions	Update the dimensions displayed on the Confirmation page
Use system quantity	No update to purchase order. Update the Confirmed quantity field to the system’s deliver remainder quantity
Use vendor quantity	Update the Purchase order line’s deliver remainder quantity and Confirmed quantity field to the vendor quantity
Clear confirmed quantity	No update to purchase order. Clears Confirmed quantity on the Confirmation page.

Line date

The following tables describe the fields and buttons that are available on the Line tab tab of the Confirmation page.

Fields

Field	Description
Log	This will show a warning if Validation failed with error tolerance set to warning
Item number	Item number from the purchase order
Barcode	Barcode for the item number from the purchase order
Product Name	Item name for the item number from the purchase order
Unit	Unit from the purchase line
Vendor delivery date	Acknowledged delivery date received in the purchase order acknowledgement. This value is used in the Purchase order’s Confirmed receipt date.
System delivery date	Delivery date for each purchase line (requested receipt date). This could be the same as vendor’s delivery date, but could also have been overridden to a new value after the purchase order acknowledgement has been received.
Requested delivery date	Requested delivery date to be sent on the purchase order confirmation (POC) to the vendor. Default is System delivery date
Confirmation auto triggered	Indicates if the Confirmed delivery date is an auto triggered value

Buttons

It is possible to update the Purchase order and Confirmed values by using the available buttons for a particular or multiple lines:

Button	Description
Display dimensions	Update the dimensions displayed on the Confirmation page
Use system date	Update Requested receipt date to purchase order line’s Requested receipt date
Use vendor date	Update Requested receipt date to vendor’s Acknowledged delivery date received in the purchase order acknowledgement

Line pack

The following tables describe the fields and buttons that are available on the Line pack tab of the Confirmation page.

Fields

Field	Description
Log	This will show a warning if Validation failed with error tolerance set to warning
Item number	Item number from the purchase order
Barcode	Barcode for the item number from the purchase order
Product Name	Item name for the item number from the purchase order
Unit	Unit from the purchase line
Vendor pack	Pack quantity received from the Vendor in the POA
System pack	Valid system pack for the inner or outer as specified on Package size - inner/outer on the settings profile for the Vendor purchase order acknowledgement
Confirmed pack	Confirmed pack quantity to be sent on the purchase order confirmation (POC) to the vendor. Note: The automatically acknowledged pack (Vendor or System) is set on Confirmed pack on the settings profile for the Vendor purchase order acknowledgement.
Confirmation auto triggered	Indicates if the Confirmed pack is an auto triggered value

Buttons

It is possible to update the Purchase order and Confirmed values by using the available buttons for a particular or multiple lines:

Button	Description
Display dimensions	Update the dimensions displayed on the Confirmation page
Use vendor pack	No updates to purchase order. Update the Confirmed pack field to the Vendor pack
Use system pack	Update the Confirmed pack field to the System pack. Calculated by using unit conversion and rounding setup on the item.
Clear confirmed pack	No update to purchase order. Clears Confirmed pack on the Confirmation page.

Line inner

The following tables describe the fields and buttons that are available on the Line inner tab of the Confirmation page.

Fields

Field	Description
Log	This will show a warning if Validation failed with error tolerance set to warning
Item number	Item number from the purchase order
Barcode	Barcode for the item number from the purchase order
Product Name	Item name for the item number from the purchase order
Unit	Unit from the purchase line
Vendor inners	Vendor # of inners received in the purchase order acknowledgement
System inners	Valid system # of inners. Note: The number of inners is calculated based on the quantity within an outer and inner. Unit conversion, example 12 ea (inner) in a box (outer).
Confirmed inners	Confirmed # of inners to be sent on the purchase order confirmation (POC) to the vendor. Note: The automatically acknowledged inner (Vendor or System) is set on Confirmed inner on the settings profile for the Vendor purchase order acknowledgement.
Confirmation auto triggered	Indicates if the Confirmed inner is an auto triggered value

Buttons

It is possible to update the Purchase order and Confirmed values by using the available buttons for a particular or multiple lines:

Button	Description
Display dimensions	Update the dimensions displayed on the Confirmation page
Use system inner	No updates to purchase order. Update the Confirmed inners field to the System inner.
Use vendor inner	No updates to purchase order. Update the Confirmed inners field to the Vendor inner.
Clear confirmed inners	No update to purchase order. Clears Confirmed inners on the Confirmation page.

Automatically processing Purchase order confirmation

Vendor EDI module includes the ability to automatically send vendor purchase confirmations by setting Purchase order confirmation required to Yes (PO is auto-confirmed) on the Vendor purchase order acknowledgement document setting and assigning it to the Vendor trading partner on the incoming document Vendor purchase order acknowledgement (POA). Once a POA is received from the Vendor, EDI will use document settings and validation to automatically send a confirmation to the vendor.
The confirmations can be viewed in:

• History tab on the D365 Purchase order Action Pane, EDI tab. If Reference is set to Confirmation, the Confirmation matched the Vendor’s POA. If set to Change, the Confirmation didn’t match and sent a change to the vendor.
• EDI > Documents > Vendor purchase order change. If EDI order purpose is set to mapped value for Confirmation, the Confirmation matched the Vendor’s POA. If set to mapped value for Change, the Confirmation didn’t match and sent a change to the vendor.

View staging table records

To view the Vendor purchase order acknowledgement staging records, go to EDI > Documents > Vendor documents > Vendor purchase order acknowledgement. Use this page to review staging and process EDI Vendor purchase order acknowledgement documents, update the D366 purchase order and send the purchase order confirmation (where set to automatic).

List page

The following EDI fields are available on the list page.

Field	Description
EDI number	EDI Staging table record id. Select EDI number or the Details button on the Action Pane, to view the details for the selected record. The number sequence is determined by EDI number on the EDI parameters.
Company account	Legal entity of the document.
Company GLN	The company’s global location number is shown here.
Staging to target status	The current status of the staging record. Options include: • Not Started – The staging record has been successfully processed from the inbound file to the staging table but not processed to target. • Error – The staging record has been processed from the staging table but no target has yet been created/updated. There are errors with the staging record that needs to be reviewed. • Completed – The staging record has been succesfully processed and updated the D365 purchase order and sent a purchase order confirmation (where set to automatic). • Canceled – The record has been manually canceled and will be excluded from processing.
Trading partner account	Vendor account assigned to the staging record.
Trading partner GLN	The Vendor’s global location number is shown here.
Purchase order	Purchase order number for the POA record.
PO version number	The version of the purchase order number being acknowledged.
Purchase order date	The purchase order date from the PO that is being acknowledged is shown here.
Acknowledged status date	The purchase order acknowledgement date from the EDI POA is shown here.
POA code	POA Header code group as mapped in POA response code group.
EDI order purpose	The EDI order purpose is shown here.
Created date and time	The date and time the selected record was created in the staging table.
Sent	Indicates if the Functional acknowledgement outbound has been sent to the trading partner for the inbound document record.

Buttons

The following buttons are available on the Vendor purchase order acknowledgement’s Action Pane, tab Purchase order acknowledgement.

Button	Description
Process purchase order acknowledgment	Process purchase order acknowledgement for the selected record in the staging table.
Process all purchase order acknowledgment	Process purchase order acknowledgement for the staging records that have a Staging to target status set to Not started.
Inbound files	View the inbound file record the selected staging record.
Trading partner	View the trading partner details in the Trading partners page.
Purchase order	If the EDI POA has been completed it is possible to inquire on the linked Purchase order the POA was created for.
Vendor	Inquire on the Vendor for the selected record.
Show log	If there are Errors within the document, it is possible to review them at any time using this button. Shows only the current version.
Version log	View all log versions. When a document’s status is reset and reprocessed, a new log version is created. Can view all log versions.
Reset Status	You can reset the Staging to target status to Not started. This can be used to reprocess the selected record/s. Documents can only be processed if Staging to target status is set to Not started.
Edit reset status recurrence	If the underlying issue was resolved after all the reset attempts have been completed the user can use this button to edit the recurrence field/s. This will: • Update Reset status profile to blank • Update the Reset status date/time to next time reset will run • Reset status attempts set to Zero and • Recurrence text updated with changed recurrence details
Cancel	Select Cancel to update the Staging to target status to Canceled. Button is enabled when the Staging to target status is not set to Completed.
Override error validation	Enabled when Staging to target status is set to Error or Not started. Ability to override error validation and process to target.

The following buttons are available on the Vendor purchase order acknowledgement’s Action Pane, tab Acknowledgement. The Acknowledgement tab is available on all incoming documents staging pages and enables the user to process or view the Functional acknowledgement outbound that has been created for the inbound document.

Button	Description
Send to EDI	If the Sent field for the staging record is set to No, use this button to create the Functional acknowledgement outbound record and also update the Sent field to Yes.
Reset flag	If the Sent field for the staging record has been set to Yes, use this button to reset Sent to No.
Functional acknowledgement	Use this button to view the Functional acknowledgement outbound record created for the inbound document.

Header fields

The following EDI Header staging fields are available on the header page.

Field	Description	D365 PO update
Identification FastTab
Identification
EDI number	EDI Staging table record id	History page on D365 PO
Company account	Legal entity of the document
Company GLN	The company’s global location number is shown here.
Staging to target status	The current status of the staging record. Options include: • Not Started – The staging record has been successfully processed from the inbound file to the staging table but not processed to target. • Error – The staging record has been processed from the staging table but no target has yet been created/updated. There are errors with the staging record that needs to be reviewed. • Completed – The staging record has been succesfully processed and updated the D365 purchase order and sent a purchase order confirmation (where set to automatic). • 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	Purchase order number for the POA record
Purchase order date	The purchase order date from the PO that is being acknowledged is shown here
Acknowledged status date	The purchase order acknowledgement date from the EDI POA is shown here	Acknowledgement status date
POA code	POA Header response code	Acknowledgement status
EDI order purpose	The EDI order purpose is shown here
Status
Group control number	Group control number for outbound document. To be used to match inbound functional acknowledgement, where applicable.
Sent	Indicates if functional acknowledgement outbound has been sent to the trading partner for the inbound document.
General FastTab
Purchase order acknowledgement
POA code	POA Header response code	Acknowledgement status
Details
Vendor reference	Vendor’s order reference	Vendor reference
Vendor account	Vendor account for the POA record
Vendor name	Vendor name
Trading partner GLN	The vendor’s global location number is shown here
Company GLN	The company’s global location number is shown here
Buyer group	The Purchase Order’s Buyer group is shown here
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
Customer invoicing
Bill to	Our account number as loaded on Vendor’s Invoice account
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
Created date and time	The date and time the selected record was created in the staging table.
Delivery
Delivery name	Ship to - Name
Ship to	Our account number as loaded on Vendor’s Order account
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
Delivery date	Required delivery date
Acknowledged delivery date	Acknowledged delivery date	Confirmed delivery date
Site	Storage dimension - Site
Warehouse	Storage dimension - Warehouse
Delivery terms	Delivery terms
Delivery mode	Delivery mode
Form note	Header note to be sent with purchase order
Requester	Requester
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 setup in Carrier mode.
Miscellaneous
Misc. indicator	Code which indicates an allowance or charge for the service specified. Mapped value setup in Misc charge/allowance indicator.
EDI charges code	Code identifying the service, promotion, allowance, or charge. Mapped value setup in 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 setup in Payment terms type group.
Terms net days	Payment terms net due days
Cash discount	Settlement discount percentage
Days	Settlement days
Discount amount	Settlement discount amount if paid within settlement days

Line fields

The following EDI Line fields are available on the lines page.
If update to purchase order line is allowed, column D365 PO line update indicates what field could be updated by the POA.

Field	Description	D365 PO line update
Line number	The line within the EDI table/file. Refers to original purchase order EDI line number and used in matching
Item number	The item identifier as sent by the trading partner
POA code item	Purchase order acknowledgement code for the item, for example line price - advise.
POA code shipment	Purchase order acknowledgement code for shipment of the item, for example partial/full shipment.
Description	Purchase order line text
Purchase quantity	Acknowledged purchase quantity	Deliver remainder quantity. Will be converted if POA unit doesn’t match PO unit. EDI acknowledgement tab > Acknowledged quantity
Unit	Unit of measure of purchase quantity	Used in unit conversion (if applicable) for quantity and unit price
Price unit	The quantity of the product that is covered by the purchase price. Usually 1.	Used in unit price calculation
Price multiplier	Value to be used to obtain a new value. NetUnitPrice/UnitPrice. Example price before discount $100 and after discount $90 has a price multiplier of 0.9
Includes GST	Unit prices and unit discounts includes GST
Unit price	Unit price for the item	POA unit price/POA price unit = D365 PO line unit price. Will be converted if POA unit doesn’t match PO unit. EDI acknowledgement tab > Acknowledged price
Unit discount	The amount of the line discount per price unit
Unit discount percentage	Discount percentage
Net unit price	Unit price net of all discounts
Charges on purchases	The purchase charge that is calculated as a charge that is independent of the quantity on the purchase order line
Misc charges	Miscellaneous charge/allowance allocated to purchase order line
Line amount excluding tax	Net line amount excluding tax
Line amount tax	Line amount tax
Line amount including tax	Net line amount including tax
Currency	Currency
Inners quantity	Unit conversion quantity of inners to outers. Example qty 12 ea (inner) per box (outer)	EDI acknowledgement tab > Acknowledged inner
Inners unit	Inners unit of measure as setup on item’s pack size
Pack quantity	Package quantity	EDI acknowledgement tab > Acknowledged pack
Pack unit	Package unit of measure
Configuration	Product dimension - Configuration
Color	Product dimension - Colour
Size	Product dimension - Size
Style	Product dimension - Style
Version	Product dimension - Version
Site	Storage dimension - Site. ‘Line item added’ - if this staging field is blank, the purchase order header’s Site will be used when creating the new purchase order line.	Line item added: Purchase order line’s Site
Warehouse	Storage dimension - Warehouse. ‘Line item added’ - if this staging field is blank, the purchase order header’s Warehouse will be used when creating the new purchase order line.	Line item added: Purchase order line’s Warehouse
Requested receipt date	The requested receipt date
Acknowledged delivery date	Vendors accepted delivery date	EDI acknowledgement tab > Acknowledged date
Requester	Requester
Attention information	Attention information
Delivery name	Address for Delivery – Delivery name
Name or description	Ship to – Name or description
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
Store code	Ship to - Store code
Batch number	Batch number for the item	Batch
Manufacturing date	Vendor’s manufacturing date for the batch	If D365 batch doesn’t exist, used to create new batch
Expiration date	Vendor’s expiration date for the batch	If D365 batch doesn’t exist, used to create new batch