Sage 100

Working on a PO receipt of goods (with the invoice) and all is going well except for one little stickler. It's adding the items to the PO, not receiving/invoicing the existing lines. Funny but the PO says complete after the update but the items still show as on PO (see below). The receipt import doesn't populate the quantity ordered either. Not sure that would solve it however. The customer is exporting the PO then sending it to the vendor who then sends the product and exports an invoice. I gave them the format for the receipt and it is working except for this little bug-a-boo. I looked to see if there was a line index I could include in the export but I don't see one. What am I missing?? TIA.

You need to import back in with the PO line key, too, and will have to manually set the backorder (as part of the VI), otherwise existing lines will backorder = 0

I don't see a line key in the export job maintenance. Where is it???

How are you doing the export?

Through VI and I don't see a line key.

On the export header, there is a button for Options. Select the one to allow export read only fields and it should be available then

Will give it a try - thanks @RobertWhite.

After you find the PO_PurchaseOrderDetail.LineKey field to export, populate the PO_ReceiptDetail.OrderLineKey field on the import. (in the file layouts it is field 19, not field 3).

I have a client that does that on a regular basis, I created a crystal report that allows them to enter the PO they are receiving against and it gives them back the OrderLineKeys, they then add that to their Receipt Import csv file and process the VI import.

I think @RobertWhite's hint will work to export it then I will have the vendor include it in their invoice export (hopefully!).

My lesson learned on this is that if the PO has 5 lines, you need 5 lines imported back (whether received or not) otherwise the missing lines won't be received and they will backorder = 0

They don't allow backorders but I am excluding PO lines with zero qty ordered (customer auto-generates from SO's then picks from the whse and changes the PO accordingly). Complicated, I know...

My memory of what @RobertWhite references is a bug (err... ""undocumented feature""). If you don't import all lines from the parent PO, the PO data after posting the receipt will not be what you would expect. I believe we solved the issue by importing to a UDT, with a SQL view to fill in the gaps (Premium), then an ODBC import from the UDT to create the receipt. If the vendor misses a line, or splits the shipment into two invoices, bad things can happen.

Requiring all the original PO lines to be imported, even if there is no receipt qty, and assigning the OrderLineKey has been the design by Sage since PO went to Framework. It wasn't designed with V/I in mind. So not doing these steps can result in Qty on PO, Qty on BO and such being off after ROG Update and then having to rebuild PO Sorts frequently. For that reason, we created a custom import program for PO ROG Entry that runs off the menu to replace V/I imports. It also deals with situation of applying partial and over-received qtys when the same item on the original PO repeats.

Hey @AlnoorCassim do you have any info on your product?

@AlnoorCassim, me too, me too! I would also like info on your custom import.