PM Document On Hold

(0) Share

Report

Posted on by Community Member

We have a process in our GP10 environment that was a customised piece of work from a previous provider, This customisation allows an Open RMdocument to be placed on hold (using a custom table) and updated the HOLD field in the PM Open Table. We have now configured GP13 (we are not migrating but starting fresh) and have built a process in CRM2013 that will allow most of the work to be done one the customer record.

What we are struggling with is passing something to GP to set the HOLD status of the PM document. We have used Scribe to do most of the work but it doesn't reference the HOLD field.

Anyone automated the update of this field in their processes?

*This post is locked for comments

All responses (4)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

RE: PM Document On Hold

Thx for the reply. We run a Central Billing platform which means we get 1 invoice in from a supplier and we issue it directly out to a retail store. The store pays us, we consolidate and pay once to supplier. If a store disputes an Invoice we want to put it on hold for them to pay us (so it isn't classed as overdue) but at the same time put it on hold so we don't pay supplier (once paid there is lower incentive to sort the dispute.)

I figured we would use a a table with a voucher and hold field then trigger it in the PM20000. Thx for a great reply.
Community Member on at

Like (0)

Report

RE: PM Document On Hold

You can't use econnect but could do it in the back end.
Tim W 2,925 on at

Like (0)

Report

RE: PM Document On Hold

Question on your statement" "allows an Open RMdocument to be placed on hold (using a custom table) and updated the HOLD field in the PM Open Table", did you mean Open PM Document and setting the hold field on PM or are you doing some Pay on Pay AR-AP cross function where you want to get paid ahead of releasing and paying some type of Revenue share payment?  Mostly just for my curiosity.

Regardless without testing it I'd say you need a secondary process similar to what you had at the old version. Scribe wraps eConnect and so both work within the same logic flow it that they integrate un-posted records, those then get reviewed (perhaps) and then posted by a user.

The AP hold logic is applied through the UI after the voucher has posted. As such, the work table (PM10000, the table Scribe and eConnect write to) will not have the HOLD field as that is logic applied only after the document is posted and then it would be the PM20000.

If I had to write this logic into a scribe integration I'd extend the integration to write to a custom table the Voucher to 'Hold', then have a table trigger on PM20000 to read the pending hold table and update the record while listening for a PM20000 insert.

Best

Tim
Suggested answer

soma 24,410 on at

Like (0)

Report

RE: PM Document On Hold

I think you can use eConnect procedure or backend update to achieve this.

Hope this helps