In order to print fields from the CI_Item table on a Purchase Order (either a UDF or a standard field not currently found in the PO Work table) you must either add the CI_Item table to the PO form and link it to the PO Work table, create a sub-report to pull the information in or add UDFs to the Purchase Order Detail table and then pass these fields to the PO Work table.
Adding the CI_Item table to the PO Form will not only defeat the purpose of using a single customizable table to streamline form printing, it could potentially slow down PO form printing considerably if the CI_Item table contains a large number of records.
Creating sub-reports to pull the information into the form can become unwieldy if there are several fields needed across multiple PO forms.
Adding UDFs to the PO Detail table and then to the PO Work table in order to print fields from CI_Item (UDFs, as well as, several inventory fields not currently found on the PO Work table, such as Volume, StandardUnitCost or SalesUMConvFctr) or use them in a calculation will not only create duplicate data in the system, but it will not work for existing Purchase Orders as these UDFs will not have been populated.
Adding the CI_Item table as a data source for the PO_PurchaseOrderPrinting business object like it is available for the SO_SalesOrderPrinting business object would be very beneficial.
by: Wesly G. | over a year ago | General Enhancements
Comments
I see what you mean; the two modules are not consistent with each other.
We just added CI_Item as a data source. It was reported as a defect.
Added in Sage ERP MAS 90 and 200 version 4.5