Skip to main content

Parts Delivered to Customer

When the supplier has informed you that the parts are delivered to your customer and you have entered the direct delivery in your system, the purchase order is automatically closed. The status on the purchase order is changed from Released or Confirmed to Closed. The customer order receives the status Delivered, and the customer can be invoiced. This assumes that no partial deliveries remain on either order. If the supplier has partially delivered an order and for any reason is not able to fully deliver the order, it is possible to manually close the purchase order.

 

We are trying to use the above process, but when the parts are received the PO is closed, but the customer order is NOT being updated, thus we are unable to invoice the customer.  Is there a setting or configuration needed to make this work?

 

Supply Chain personnel get a Warning message when they register the Direct Delivery.  Message says that the customer order has been cancelled or unpegged from the purchase order line.  A check of the customer order line shows it is Released and only has an option to Unpeg.  

hi @dkjensen ,

  There is no such a setting. The flow should work as you clearly explained. According to the your attached message, CO update process after delivery got struck due to pegged CO line cancelled or unpegged. Can you check the Order Line history records? 

regards,

Piyal

Hi Piyal, 

The only thing showing on the order line is the release and requisition creation.

Hi, @dkjensen,

   I just checked IFS Cloud 23R2. It works as expected.

May I know which version you are working with.

regards,

Piyal

IFS Aurena framework version: 10.18.26.0

IFS Aurena client version: 10.18.138.0

IFS OData provider version: 10.18.1.0

Is there a difference in the process if the customer is Inter-Company?

you are using IFS APP10 Aurena client. So, I checked in that environment with internal customer’s CO and working as expected.

So, if you have a test environmnt, please try to recreate the issue. if possible publish the test steps.

 

All of this is being done in our test environment.

 

Customer order created with lines containing parts with Supply Code of Purch Order Dir,

  • order type is INT which has a stops on Release Order, Print Order Confirmation, Reserve Order, Print Pick List, Report Picking, Deliver Order events
  • shipment type is NE which has Stops on Reserve, Print Pick List, Report Picking, Complete and Close Shipment events, there are no stops on the Customer order events

Requisition is automatically created for the part.

Purchase order is created from the Requisition.

Parts are received using the Register Direct Delivery screen

Purchase order lines are automatically closed

 

Ok. I checked any clue from the code as well. Are you using “Direct Delivery from Internal Order Transit” option? With the usage of  that command I can see there are possibility to pop up this error message.

Would the Stops on the order type be preventing the completion?  

No. Order type won’t matter here because we are just updating information about already delivered items. My view is that in your flow you might have included settings related to inter-company/ Inter-site(maybe 2 or more connected supplies)/mixups with the internal supplier. Please have a close look at your functional flow setup.

Where would I find the “functional flow setup” to review?  

First, please test using a basic functional flow setup related to this direct delivery functionality.

Steps:

  • Create an external customer order line with supply code - Purch Ord Dir. make sure your customer is external

  • Release the CO and Create the Purchase order subsequently. Make sure you use an external supplier for this. Release the PO.

  • Register direct delivery and your CO must be in the delivered state.

Thank you for the steps.  I was able to complete the process successfully in our test environment.

Is the Requisition conversion to PO a required step?  We currently are creating the Purchase order manually and not updating the Requisition at all.

Yes. CO initiated PR then PR converted to PO. So, this is a connected flow.

Reply


Terms & ConditionsCookie settings