Solved

Non-Inventory Part Register Direct Delivery - Error

  • 27 April 2023
  • 6 replies
  • 180 views
A
Rank
Userlevel 1
Badge +1

Hello,

 

I am working with a client on an issue where they converted from Apps 7.5 to Apps 10. They ship non-inventory material from one location to another. The shipping location is set as an internal supplier. The customer is an internal customer. The Customer site enters orders using sourcing code (Int Pur Dir). When the CO is released, a PO is created. The PO shows source (Int Cust Dir). Everything so far functions properly. I have not seen any issues with the setup of the internal customer or internal supplier. Both have the proper flags. But somewhere the initial setup missed something.

 

Proof of concept. In Apps 7.5 system, they can still run the process listed above and everything works. Several CO’s were migrated into Apps 10. Those can be processed correctly as well. However, new CO’s in Apps10 will not complete properly. It gets stuck in Register Direct Delivery.

 

In Apps 7.5, the Register Direct Delivery screen shows the Purch Qty to Deliver and the Inv Qty to Deliver. 

 

In the migrated Apps 10 Register Direct Delivery screen shows the Purch Qty to Deliver and the Inv Qty to Deliver. 

 

 

When created in Apps 10 directly, no quantities show up in Register Direct Delivery.

There are qty’s listed “Due on Dock” which match the PO qty’s

There are quantities listed on the PO:

If qty’s are entered on the Register Direct Delivery page, we receive the following error. The PO is from Supplier 45.

 

Would anyone know why the Purch Qty to Deliver and the Inv Qty to Deliver do not populate in the Register Direct Delivery page?

 

Thank you.

icon

Best answer by Vimukthi Mahakumbura 3 May 2023, 14:31

View original

6 replies

A
Rank
Userlevel 6
Badge +11

Hi,

Do you know if the customer order (Which the internal supply site users to deliver the items) is ‘Delivered’?

You will be able to locate this order by RMB on purchase order line and selecting Supply Chain Order Analysis. 

 

 

If this last customer order was not delivered, I will not see Purch Qty to Deliver in the Register Direct Delivery, and will get the same error as you.

 

When you deliver the internal customer order to send the items to internal demand site, you will see the Purch QTY to Deliver and will be able to process the direct delivery.

 

Thanks

Asanka Garusinghe - https://www.linkedin.com/in/asanka-garusinghe-61634a64/
W
Rank
Userlevel 2
Badge +7

Hi 

Direct Delivery doesn’t work with the Inter-Site/Inter-Company functionality. 

It is because the Direct Delivery functionality doesn’t consider the Internal Transit to clear it down. 

 

Central Orders may be an option where you  can specify a purchasing site then at line level define different delivery sites. 

 

Cheers 

Lee

Vimukthi Mahakumbura
Rank
Userlevel 7
Badge +18

@aconsult Asanka’s response should resolve your issue. The functionality here has been changed when it comes to APP10 comparing to APP75, and the internal CO needs to be delivered. 

To get to the supply chain order analysis above shown, you need to RMB on the CO or PO lines and from their you may direct to the internal CO. 

If you are not seeing this internal CO created at the supplier, it usually means the data setup is incomplete or there is a connectivity issue. See the attached conversation if your problem is that. 

 

 

https://www.linkedin.com/in/vimukthi-mahakumbura-9b2296aa/
A
Rank
Userlevel 1
Badge +1

Thank you. The inter-site messaging was not set up properly. Once we set this up, the messaging for the orders went through properly and we were able to complete the process.

 

J
Rank
Badge +3

@aconsult   What inter-site messaging changes did you make to get it setup properly?  Did the Register Direct Delivery Purchase qty to deliver and inventory qty to deliver fields populate after the changes were made?

A
Rank
Userlevel 1
Badge +1

There is a lot to it. See attached screenshots of Message Media, Message Receiver, and Message Class setups.

3 Attachments

Reply


Terms & ConditionsCookie settings