Errors on insert of PO Header records (6 replies)
On a related note, I just built a similar job to insert Order Headers, with the same types of data from the same db, and they inserted just fine into 300.
I'd be happy to discover that I just mis-mapped the vendor code field but I am not seeing it if so...
And another update. Beginning to suspect a bug in Realisable or the 300 API might be behind this; the third mapping field returned in the PO Header view is "Allocate from Serial" ... of note, the third field returned on the Sales Order Header view is Customer Number.
There is no option for Vendor Number or Code or ID. There is only "Vendor", which is consistent with the title in the object model, but it's almost to the bottom of the view list in Iman.
So I attempted to map the Vendor ID to this Allocate field and received this list of errors:
| 1 | Cannot access a disposed object. Object name: 'System.ServiceModel.Channels.ServiceChannel'. |
| 2 | IMan DataService session incurred an error.The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state. |
| 3 | IMan DataService session incurred an error.The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state. |
| 4 | The request channel timed out while waiting for a reply after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. |
| 5 | The communication object, System.ServiceModel.Channels.ReliableRequestSessionChannel, cannot be used for communication because it is in the Faulted state. |
Rebooted and came back after a while; the mapping to "Vendor" is showing as "Tax Amount 4" in the Preview. Gotta be something with one of the apps.
Unfortunately, all of my jobs are erroring out now - even those that were working just fine roughly 24 hours ago - with these errors. I'm dead in the water with many jobs to refine and to build so if anyone has any experience with these errors, I'd be grateful.
I did find one forum post with one of these errors listed but it didn't contain anything actionable for me. Googling didn't seem to provide much for me that was actionable either.
This sounds very much like a known problem with one particular update of sage 300. A way to check is to go into Sage 300 and use the finder on the PO screen. Look at or add columns. If you see the ones you mentioned with different data to the field descriptions then you have the bad version. There are fixes you can find on Sage 300 support.
Steve - I forgot to respond a ways back to say THANK YOU. After updating to PU 5, the Vendor field magically appeared 🙂
I am now inserting PO headers and details though my detail lines are duplicating on each run - see the separate post I entered in the forum last night - if you have any solutions for that one as well. Thanks again!
Building a job to insert POs; at this point, I am only working on Inserting PO headers - no details yet.
I am receiving the following errors when trying to insert the PO with as few data-points as possible (Vendor ID, PO #, PO Date):
I am not specifying terms, acct set, or tax group in the PO data-set as they should be picked up - I ASSUME - when I insert the Vendor Code into the PO header which would be consistent with my experience of other jobs I've built this week to insert master records for Nat Accts, Customers, Vendors, and Items.
Therefore, I assume the actual problem is with the insert of the Vendor Code. I have a column from my source db called "VENDNO" that I have mapped to "Vendor". This should be a slam dunk - so I am pretty confused here.
Of note, I also tried to use the same data to insert a PO Receipt header and also mapped my vendor code data to the "Vendor" field on the receipt header. I received an error along the lines of either a Vendor or PO number was required to insert the header. So, again, something seems amiss with the mapping of the Vendor Code.
Anyone experienced any hinkyness like this or see that I am making some n00b mistake?