|
|
|
|
|
Description: Often times a supplier sends back multiple order responses to the same order. In this scenario, the supplier sends back an order response with a response type code that maps to Accepted As Is and an order status of Processing. Then, later on, the supplier sends back a second order response with a response type code that again maps to Accepted As Is. However, this time the order status is Accepted. So, the supplier used the second order response to essentially inform the buyer of a status change while the order itself (part, quantity, price, etc) was not changed by the supplier.
This scenario could have just as well been a case where the supplier sets the response type code and order status to Accepted for both order responses. In the second order response, the shipping status could have changed from Not Yet Shipped to Delivered.
The point to be made here is that the supplier may keep sending order responses with a response type code that maps to Accepted As Is and Procurement will keep processing these responses with a buyer status of Accepted By Supplier. The order (Supplier) status for the order in Procurement is simply whatever status the supplier provides.
After Procurement process each response with a response type code that maps to Accepted As Is, the same set of available actions will be accessible to the buyer as are in the scenario Accepted By Supplier above.
