Purchasing

Ability to Receive All for Catchweight Items

Ability to Receive All for Catchweight Items

Program/business class/process affected:

• POReceiptLineTemplate
• PurchaseOrderLine
• PurchaseOrderReceipt
• POReceiptLineTemplate

Use these steps to test the enhancement:

1. Create a PurchaseOrder with multiple lines. One must be a catchweight item. Then release.
2. Do Create Receive All on the purchase order.
3. Optionally, create a receipt on the purchase order and do Receive All action.
4. All non-catchweight items must be created into receipt lines. For catchweight items, lines should remain in PurchaseOrderLines tab, for user to be able to enter both Received and Catchweight quantity.

JT-1526416

Add ability to define Manual Purchase Order Number Range

Since purchase order numbers are sequentially assigned, this enhancement adds the ability to define a range for manual PO numbers and allows creation of purchase orders within the manual range.

Program/business class/process affected:

• Purchasing Company
• PO creation

Use these steps to test the enhancement:

1. Define the manual PO range on Purchasing Company.
2. Manually create a PO and enter the PO number within the manual range.
3. Sequential numbering will skip over the Manual PO number range.

JT-1182541

Include the substitution details on PO Line Acknowledgment Message for Item Substitutions

Include the substitution details on PO Line Acknowledgment Message for Item Substitutions

Program/business class/process affected:

• EDI 855 processing

Use these steps to test the enhancement:

1. Process an EDI 855 record going to CSF, where there is a Record Type 75, Line Status IS record.
2. Run the Purchase Order EDI Acknowledgment action.
3. Check the Purchase Order Acknowledgment Results menu item

Expected Results: On the Acknowledgment Messages tab, there should be a message that says "Status is accepted, substitution made; item xxxx substituted for item yyyyy", where yyyy is the item currently on the PO line.

JT-1357966

Provide link on email to Buyers for PO Details during the PO Acknowledgment process

Provide link on email to Buyers for PO Details during the PO Acknowledgment process

Program/business class/process affected:

• Vendor acknowledgments

Use these steps to test the enhancement:

1. Create a PO EDI Acknowledgment record.
2. Set up the Buyer associated with the PO to have an email address that matches your own.
3. Run the Process Purchase Order EDI Acknowledgment action.
4. You should receive an Email indicating there are acknowledgments to view.

Expected Results: There should be a link on the Email, that when clicked opens the My Acknowledgments list, which shows PO revisions and acknowledgment messages for your buyer record, with the PO that just received acknowledgment messages at the top. You may need to log in.

Note: There is also a new tab on the Purchase Order Acknowledgments menu item to show My Acknowledgments

JT-1536537

Ariba PO cXML file: Need to include INCOTERMS at PO header level

This change was requested by the customer in order to communicate the location where ownership of the shipment is transferred from the seller to the buyer (referred to as “named place”). This field will be transmitted in the cXML OrderRequest that is dispatched and housed within the Terms of Delivery element

Program/business class/process affected:

• PurchaseOrder
• PurchaseFromLocation
• PurchasingVendor
• PurchaseOrderEDIOutput
• StandardCommentCode

Use these steps to test the enhancement:

1. Verify the default handling of data:
   • If Purchase From Location – Named Place data exists, auto-populate.
   • Otherwise, if Purchasing Vendor – Named Place data exists, auto-populate.
   • Otherwise, this field will be blank.
2. Verify the cXML records for OrderRequest document contains the mapped field changes (ShippingPaymentTerms and Comments in TermsOfDelivery element)

cXML Changes for Incoterms Named Place mapping

Need to send terms of the delivery element in cXML for Incoterms

Program/business class/process affected:

• Purchase Order Dispatch process

Use these steps to test the enhancement:

1. Add a purchase order for a vendor or vendor purchasing location that has an issue method set as XML.
2. If the vendor or purchase from location have Incoterms entered, then Incoterms will default on to the purchase order header as Incoterm comment.
3. Incoterms can be updated by accessing them via purchase order header comments.
4. Verify that only one Incoterms comment can be added per purchase order.
5. Release and issue the purchase order.
6. Dispatch the purchase order.
7. Verify that the cXML dispatched has the Incoterms added as a comment in the TermsOfDelivery element.

JT-1514511

Ariba PO cXML file: Need to include INCOTERMS at PO header level

This change was requested by a customer to communicate the location where ownership of the shipment is transferred from the seller to the buyer (referred to as “named place”). This field is transmitted in the cXML OrderRequest that is dispatched and housed within the Terms of Delivery element

Program/business class/process affected:

PurchaseOrder

PurchaseFromLocation

PurchasingVendor

PurchaseOrderEDIOutput

StandardCommentCode

Use these steps to test the enhancement:

JT-1431506