#ListOpenAccountReceivables

Can anyone give me insight about this? I've seen this used in a few reports, but I haven't been able to figure out where it's populated from.

The report I'm looking at is "Customer - Accounts Receivable (Detailed) Report.qrp". I would like to do some filtering from data we have stored in the customer.customtext1 field, but I'm not sure if it will be possible.

Any information about this would be greatly appreciated. I've looked through the customization guide and haven't seen any mention of this.

Thanks, Michael

Reply to
Michael Behm
Loading thread data ...

See that entry that says: ProcedureCall="ListOpenAccountReceivables"

That is calling an internal procedure in RMS that creates a temporary table named #ListOpenAccountReceivables.

You can't change the structure of this temp table, but that's OK, because the report is joined to the Customer Table anyway...

just add the following to the bottom of the report:

Begin Column FieldName = "Customer.CustomText1" DrillDownFieldName = "" DrillDownReportName = "" Title = "Custom1" VBDataType = vbString Formula = "" ColHidden = False ColNotDisplayable = False FilterDisabled = False ColWidth = 810 GroupMethod = groupmethodNone ColFormat = "" End Column

Glenn Adams Tiber Creek C> Can anyone give me insight about this? I've seen this used in a few reports,

Reply to
Glenn Adams [MVP - Retail Mgmt]

Glenn, thanks for responding to my question. I really appreciate you taking the time to help explain that to me.

So the procedure that's called is a RMS procedure and not a procedure stored in the database? That was part of my mis-understanding. I had looked through the database procedures, but I didn't see any procedures with that name.

Do you happen to know what fields are created in this temporary table? The report I mentioned uses: Balance, AccountNumber, Name, Company, StoreCode, StoreID, StoreName, AccountReceivableType, Date, AccountReceivableID, DueDate, Aging, and OriginalAmount

On a side note, are there other procedures that can be called that exist?

Michael

Reply to
Michael Behm

Yes, that one is an internal procedure, not a stored proc.

It's completely undocumented. My assumption is that all of the columns are used in the report as this report is the only thing in the system that uses the proc as far as I know.

Internal procedures of this type are not documented. The only way that you could find them would be to scan through the .qrp files to see if there is anything that's used in the same way. I don't remember seeing anything else like that though.

In most cases where a temporary object is created for a report, they use PREQUERY1 to run a create statement within the report itself (see the item movement history report for an example). I have no idea why they used an internal procedure in this one case.

Glenn Adams Tiber Creek C> Glenn, thanks for responding to my question. I really appreciate you taking

Reply to
Glenn Adams [MVP - Retail Mgmt]

Glenn,

As always, your input was greatly appreciated. Thanks for taking the time to "document" this part of Microsofts software for me.

Michael

Reply to
Michael Behm

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.