Recent content by gatsbyinca

TailorPro (and presumanly QAD's ICT) could do this for you. A primative solution would be to use specify ISS-SO as a restricted transaction for the item's status code until the price is setup. HTH.

If the posted entry has come from the SO module (gltr_tr_type = "SO"), the Document field (gltr_doc) should contain the invoice. You can obtain the sales order from a few different places, but the easiest way is probably via the Invoice History table (ih_hist where ih_inv_nbr = gltr_doc).

How is the performance?Performance depends on what your users are used to...if they are coming from a ChUI / GUI system that flys then they will be disappointed. We tried to get all users onto .NET UI after our recent upgrade but there was a near riot on the 1st day...so we reintroduced GUI for...

7.9.15 (Ship) also 7.13.1 (Pending Invoice Maintenance)...plus others ways that I'm not aware of :) 7.13.3 (Invoice Print) 7.13.4 (Invoice Post)

I think if you use quotes around the double quote it will work. We had this once with pt_desc when we were CIM loading into 1.4.1 and the item description had the " symbol for inch e.g. Bearing 3/4" would be formatted as Bearing 3/4""" I think this works but it was a long time ago. I...

You can delete the order in 7.1.1 (F5, CTRL-D, <DELETE> button depending on the UI). This will create "debooking" tr_hist records (ORD-SO) and delete the so_mstr / sod_det records. The standard system deletes sales order records when the order is shipped, invoiced & the invoice is posted if all...

If the item (sod_part) is a configured part, an additional pop-up window appears during order entry. This is where the configuration is specified (e.g. use standard bill or make specific selections). This information can vary from order to order, so it is recorded in the sob_det. The sod_det...

Hi, That's an interesting problem. We've played around a little with simplified screens (same version & service pack as you) and faced a somewhat similar issue with Sales Order Maintenance (7.1.1). Our solution was to do this...keep the standard program "as is" and create a new program that is...

25.3.1.1 Entity Code Maintenance (eB2.1)

I don't know your data...but I assume 440330 is the account (or combined A/C & Sub Acct) and 421 is the Cost Center? (You mentioned that you are on v9.0 ... I don't recall what version of QAD split out the sub-acct into a separate field) In any case...they have to be on the same line...

Your first 2 characters are "." (this is F4 / Esc)...don't you need "-" on separate lines? I assume you don't want to specify the GL Reference (i.e. you allow system to assign) and the Effective Date / Currency.

Although you may not want to specify site in your query if inventory exists in more than one site. In this case, include in_site as a display field. One other thing for eB2.1, you may want to include domain in your query.

Costs are stored in sct_det table. Depends our how your Finance people have defined cost sets...relevant fields are: sct_sim (the cost set) sct_site sct_partDomain is also important in eB2.1

I believe it is prh_rcp_date (prh_hist table)

Hi, We recently upgraded our QAD system to run on Progress 10.1A. We have been struggling with the ODBC part ever since! In our old system (9. something), we had a Progress user ID (_User record ) called “sysprogress”. We used this to connect via ODBC. As I understand it, we manually...