Adding Optional Fields to Purchase Orders that Use Datapipes

You can add optional field information to the purchase order forms that come with the program by:

  • Setting datapipe query parameters in the PORPT.INI file, so that the datapipe will process optional fields. More...

    The purchase orders datapipe allows you to extract fields from the following database tables:

    • APVENO (optional fields for Accounts Payable vendors).
    • POPORHO (optional fields for purchase order headers).
    • ICITEMO (optional fields for inventory items).
    • POPORLO (optional fields for purchase order details).

    The purchase orders datapipe identifies the various types of details that it prints by parameters in PORPT.INI and by different LNTYPE codes.

    LNTYPE is a field in the datapipe record provided to the Crystal report. For more information, see About Detail LNTYPE Codes.

  • All optional fields are initially turned off in PORPT.INI.

  • Using SAP Crystal Reports® for Sage 300 to add the optional fields to a detail section in the report form. More...

    Purchase Orders comes with four standard purchase orders formats:

    • Two formats use datapipes (POPOR01.rpt and POPOR02.rpt).
    • Note: Datapipes are programs that extract and organize data to increase the efficiency of particular reports.

    • Two formats read data directly from the Sage 300 database (POPOR03.rpt and POPOR04.rpt).

To set the datapipe query parameters for printing purchase orders:

  1. In your Sage 300 program folder, locate the PORPT.INI file in the PO folder, and then open it in text editing software.
  2. Search for POPOPRN.DLL for POPOR01.RPT or POPOR02.RPT.
  3. To include optional field information, set the following parameters to 1:
    • Parameter 15 (vendor optional fields)
    • Parameter 16 (header optional fields)
    • Parameter 17 (item optional fields)
    • Parameter 18 (detail optional fields)

    Note: If the information is not required on the forms, set the parameter to 0.

  4. Save, and then close the file.
  5. Restart Sage 300.