Blanket PO Manual

Download PDF version here.

2.EULA #

Please read our End User License Agreement online at: //willoware.com/install/end-user-license-agreement/

3.Important Limitations #

  • Blanket PO cannot be used with Encumbrance Management.
  • Blanket POs cannot be edited in the Edit Purchase Order Status window.
  • All Items used on a Blanket PO must have the Purchase Tax Option = Nontaxable (on Item Maintenance).  If tax is required, it must be manually calculated and added as a line item on each release.
  • The Non-Inventoried Item Tax Option in Purchase Order Processing Setup must be set to Nontaxable.
  • Trade Discount, Freight, Miscellaneous and Tax are not supported.  These fields will be locked.
  • The PO Line Number field in the PO Lines table (POP10110), limits the maximum number of rows (Control Lines plus all Release Lines) to 32,767.  So a Control Line Increment (line number spacing between Control Lines) of 1000, allows for 32 control lines with 999 releases per control line.  If you decrease the Control Line Increment, it will increase the number of possible control lines while decreases the number of possible releases.

4.Installation #

The installation process for all WilloWare products is identical.  Please review the general installation instructions at www.willoware.com/install.

5.Registration #

All WilloWare software uses the same Registration window.  See the general Registration Window instructions here:

//willoware.com/online/registration-window/

6.Security #

During installation a Security Task will be created called BLANKETPO.  It will have access to all windows in the module.

The installation will also create a Security Role called BLANKETPO, and assign the Security Task to the Role.

To ensure that users have access to the windows required by the Blanket PO Module, you can:

Assign the BLANKETPO Security Task to an existing Role, or

Assign the BLANKETPO Security Role to one or more Users

It is important to not modify the BLANKETPO Security Task.  When updates for BPO are installed they will rebuild the Security Task to ensure it is configured correctly, and any changes will be overwritten.

7.About #

The About Window for all WilloWare products is identical.  Open the About Window by going to Help >> About Microsoft Dynamics GP.  From that window select Additional >> About {WilloWare Product/Customization}.

{WilloWare Product/Customization} = the installed product, such as GP PowerPack or LabelLink.

Please refer to the general About Window guide here: www.willoware.com/online/about-window

8.Setup #

Setup

HelpID: 731922002

Navigation: Tools >> Setup >> Purchasing >> Setup Blanket PO

The Registration Key enables Blanket PO for the System—without the key you cannot access the Setup Blanket PO window. The Blanket PO module can be enabled on a company-by-company basis, so that it can be active in one company and not used in another.

Enable Blanket PO: Mark this box to enabled Blanket PO for the current company. You must restart your GP client for this setting to take effect.

Enable Auditing: The Blanket PO Control Settings can be audited, which will track every change to the control settings and require the user to enter a reason for the change. See the section titled PO Control Settings.

Default Control Option: When a new Blanket PO is created the Default Control Option will be used. The Control Option can be changed on a PO as long as no Control Lines have been entered. Once Control Lines exist, the Control Option for the PO becomes locked.

    • Control Line Quantity: you can specify the quantity of an Item to be purchased per PO Line (each line can have a different control quantity).
    • Control Line Cost: you can specify the total extended cost allowed for the purchases of an Item. The Control Cost is specified per PO Line.
    • PO Control Quantity: a total control quantity can be specified for the entire Blanket PO. The total quantity in base of all releases cannot exceed the PO Control Quantity.
    • PO Control Cost: a total dollar value control can be set for the entire Blanket PO. The total extended cost of all releases cannot exceed the PO Control Cost.

Release Number Label: This is used by the Report Writer function that retrieves the Release Number, by the PO Release Entry and Inquiry windows when displaying the Release Number, and when the Release Number is added to the Item Description (see below). If you provide a label it will automatically be inserted into the calculated field on the reports (see the Report Writer section of this document for more detail). The Example field shows how the Release Number will be displayed.

Default PO Entry View: “Show Detail” is the normal 2-line view. “Show Summary” displays just one line per PO Line.

Control Line Increment: The Control Line Increment is the spacing between Control Lines. The default is 1000, which allows for one Control Line with up to 999 Release Lines. The Control Line Increment must be specified in multiples of 10. The Dynamics GP Purchase Order can have up to 32,767 lines, so a Control Line Increment of 1000 allows for 32 Control Lines with 999 Releases per Control Line. If you need more than 32 Control Lines adjust the Control Line Increment accordingly. Once a Blanket PO is created, the Control Line Increment will be locked and cannot be changed. If you have updated to a new build of BPO from a build which did not have this feature, the Control Line Increment will be automatically set to 1000 and locked.

Add Release Number to PO Line Description: when enabled, Blanket PO will add the Release Number to the beginning of the Item Description and Vendor Item Description, as shown below.

Adding Release Number to the Item Description makes Release Number visible in:

    • PO Entry
    • Receivings Transaction Entry
      • Purchase Order Items Lookup
    • Purchasing Invoice Entry
      • Purchase Order Items Lookup
    • Purchase Order Processing Item Inquiry
    • All POP Reports that display PO Lines, or Receipt/Invoice Lines
    • SmartLists showing PO Lines or Receipt/Invoice Lines.

Update Existing Documents: this button becomes enabled when the “Add Release Number” checkbox is marked. Running this utility will add the Release Number prefix into the Item Description and Vendor Item Description on all Open and Historical Purchase Orders, Receipts and Invoices. It will not affect non-Blanket Purchase Orders, and it will not re-update existing Blanket PO documents which already contain the Release Number prefix.

The warning above will be displayed after clicking the Update Existing Documents button. You can click NO at this point to stop the process without making any changes.

Security: See the PO Security chapter.

9.PO Security #

PO Security

HelpID: 731922023

PO Security is opened by the SECURITY button on the Setup Blanket PO window.

Users must be granted access to the Blanket PO functions.

    • Enter Blanket PO Settings: users with this security can open the PO Control Settings window and set the Blanket PO control values.
    • Enter Control Lines: users with this security can add, remove, and change Control Lines.
    • Create Releases: users with this security can add Release Lines to the Blanket PO.

If a user does not have ANY of the above security, they will not be able to view Blanket POs or work with them in any manner. A user must have at least one of the above three security options for the “Blanket PO On/Off” menu option to appear on the PO Entry window.

Select a Security Type, then enter User IDs that should have that Security Type.

 

10.Blanket PO Entry #

Blanket PO Entry

Navigation: Transactions >> Purchasing >> Purchase Order Entry >> Additional >> Blanket PO On/Off

The Blanket PO module uses the regular Purchase Order Entry, however when you enable Blanket PO the WilloWare Blanket PO functionality takes control of the window. Since a WilloWare Blanket PO is created using the Purchase Order Entry window, the BPOs will appear in GP inquiries, reports, and SmartLists just like regular POs.

Steps for Creating a Blanket PO

  1. Enter the Blanket Control Settings (PO Settings)
  2. Add one or more Control Lines
  3. Add Planned Releases
  4. Select Planned Released to create a Comitted Release
  5. Print the PO with Control Lines, or print a Release

 

11.Blanket Control Settings #

PO Settings

HelpID: 731922020

Begin by entering the “header” fields on the PO (PO Number, Buyer, Vendor, etc). Once the required fields are entered go to Actions >> Blanket Settings.

The PO Settings window is used to enter the Blanket Control Settings.

Close PO: see the section entitled Close PO for more information. This utility is used to force a Blanket PO to be closed. It will prompt you to confirm you are ready, and if auditing in enabled, it will also require entering a reason for closing the PO. The Close PO utility forces the PO, and all of its lines, into a Closed status.

Control PO By: the Default Control Option from Setup will determine which Control PO By option is marked. This can be changed as long as no Control Lines have been added to the PO.

The two Control Line options allow specifying a separate control amount on each Control Line.

The two PO Control options allow specifying a control amount for the entire PO.

PO Control Amount: for the two PO Control options you can enter a PO-level control (in Quantity or Dollar Amount). A quantity control will be based on the Quantity In Base for all release lines on the PO.

Release Total: displays the total for release lines in either Quantity or Cost.

Previous BPO: enter a Previous Blanket PO Number. This is used for reporting purposes and can be added to the GP Purchase Order form.

Contract Number: if you have a contract with the Vendor which governs this PO, it can be entered here and added to the GP reports.

End Date: if you have a contract with an expiration date, or you want the Blanket to only be active for a certain amount of time, enter the End Date here. The End Date is the last day on which the Blanket PO can be used. After that, no more release lines can be added.

Release Min Qty: if each release should have a minimum quantity, enter it here. If left blank (zero), there will be no minimum quantity. If a release is below the minimum, you will not be able to Commit the release.

Release Min Cost: if each release should have a minimum cost, enter it here. If left blank (zero), there will be no minimum cost. If a release is below the minimum, you will not be able to Commit the release.

Approved Items: if the Blanket only covers certain approved items, list them here. You can enter them manually, or automatically add a large number of items from a SmartList.

To import from a SmartList, open and display the SmartList you want to use. It must be a list of Item Numbers with Item Number in the first column. When the SmartList with Item Numbers is display, return to the PO Settings window and click the Add SmartList Items button.

  • Red X button – deletes all items. You will be asked to confirm this action before it proceeds.
  • Remove Line button – deletes a single, selected line.

Auditing: the PO Control settings can be changed as needed, until a Control Line is added. At that point, if Auditing in enabled in Setup, any change to the PO Settings will will require entering a reason for the change, and it will be recorded with the User ID, Date and Time of the change.

The audit also records the before change value, and after change value for the field that was changed.

To view the Audit, select the GoTo button >> View Audit.

After closing the PO Settings window, the Blanket PO Entry window will show the Control Amount:

12.Entering Control Lines #

Entering Control Lines

If the Control Setting is one of the PO Line options, the values entered on the Control Line for Quantity or Cost will determine the total quantity or cost allowed for the releases for the item.

If the Control Setting is one of the PO options, the values entered for Quantity and Cost on the Control Line are less important. In this case they serve more as defaults for release lines. For example, if the Control Line is for a service which has a rate of $150 per hour, you can enter $150 as the Unit Cost and have that default on the release lines.

Control Lines are entered in the Blanket PO Entry window in the same manner Items are normally added to a Purchase Order.

The Subtotal and Total on the Blanket PO Entry window display the total of the Releases. Once Releases have been entered, you can toggle between showing them or hiding them in the scrolling window by selecting Additional >> Show/Hide Releases.

Other important considerations when entering Control Lines in the Blanket PO Entry window:

  • Control Lines are numbered by 1000 (or whatever value was entered in Setup). The first control line is 1000, the second is 2000. That means you can have up to 999 releases per Control Line.
  • All Items used on a Blanket PO must have the Purchase Tax Option = Nontaxable (on Item Maintenance).
  • The Non-Inventoried Item Tax Option in Purchase Order Processing Setup must be set to Nontaxable.
  • Extended Cost and Quantity Canceled are NOT editable. The Control Lines are immediately canceled as soon as they are entered to prevent them from being seen as inventory on order.
  • On Control Lines the Item Number, Quantity Ordered, Unit Cost, Item Description, and Warehouse will be editable. If there are NO Release Lines the U of M will be editable.
  • On Release Lines only the Item Number and Item Description will be editable.
  • On the Purchasing Item Detail Entry window the fields in the lower 2/3 of the window will still be editable (i.e. the dates, Inventory Account, and so on), but the same “header” fields will be editable/not-editable as described above.
  • The Trade Discount, Freight, Miscellaneous and Tax fields (and expansion buttons) will be locked. Blanket PO does not support amounts in these fields.

13.Entering Releases #

Entering Releases

HelpID: 731922006

From the Blanket PO Entry window select Actions >> Blanket Release

There are three sections to the PO Release Entry window:

  • A: the tree view shows an overview of all of the Control Lines on a PO. Each Control Line can be expanded to view the Release Lines below it.
  • B: Planned Releases. Use this section to enter Planned Releases. A Planned Release is later “Released”, which creates a Firmed Release.
  • C: Firmed Releases. When Planned Releases are Firmed they are added to the Firmed Release window. Clicking Commit Release creates a “release event”—which is a group of released lines that can all be printed together on a PO.

Treeview

The following icons will display in the Treeview to indicate different statuses of the PO Line.

PO Line Closed

PO Line Canceled

PO Line Received

Not Released

Released

Clicking on the Control Line will make the Planned Releases window display all releases for the selected Control Line.

Click on a Release Line (Planned or Firmed) will make the Planned Releases window display only the selected release.

When Receipts and/or Invoices have been entered for a Release Line you will be able to expand the Release Line to view those documents. Double-click on a Receipt/Invoice to open the document in an Inquiry window. Also, once a Planned Release line has become a firmed release, the Release Number will display next to each line.

Planned Releases

Depending on the Control By setting (either Quantity or Cost), the Planned Releases section will show either the Quantity or Dollar Amount remaining. Enter the Quantity, Required Date, and Unit Cost for each Planned Release.

Location Code will default to the Site used on the Control Line, but it can be changed for Release.

When you are ready to firm a Planned Release and print a PO, mark the Release checkbox. This will add the line to the Firmed Release window.

Until you click the Commit button, you can remove lines from the Firmed Release window. Either select a line and click the Delete Line button, or unmark the Release checkbox in the Planned Release window.

You can put multiple items on a Release. Select a new item from window A (the treeview), then mark the Release box for a line to Release.

If Releases Minimums are specified, you will not be able to commit the release until the minimums are met.

If the Blanket Settings specify an End Date, and that date has passed, you will not be able to create a new release.

Repeat this process until all of the items you need to release have been added to the Release. The click COMMIT RELEASE.

DOUBLE-CHECK YOUR WORK FIRST! Once you firm a release by clicking the Commit Release button, you cannot “un-firm” the release. In the event such lines do need to be removed, cancel the quantities for the released lines in the Planned Release window.

Firmed Releases

As described in the Planned Releases section, add lines to a Firmed Release by marking the Release checkbox in the Planned Releases window. You can add several lines from the Planned Releases to a Firmed Release. For example, you could mark two Planned Releases for 128 SDRAM on different required dates, then switch to 256 SDRAM and add a couple more lines. Continue in the manner until you have included all Planned Release lines onto the Firmed Release before clicking the COMMIT RELEASE button.

If the Commit Release button has not been clicked, you can select a line in the Firmed Release window and remove it by clicking the Delete Line button.

If Release Minimums are specified in the Blanket Control Settings, you will not be able to commit the release until the minimums are met.

The Release Number increments by 1, automatically, when each new Firmed Release is created.

Use the Release Number dropdown list to select and view earlier releases.

Printing Releases

The procedure for printing a Blanket PO is the same as printing regular Purchase Orders. Click the Print button on Blanket PO Entry.

Before the Print Options window opens, you will have to select which Release Number you want to print. The drop-down box will contain all Releases for the PO, with the most current release already selected. To re-print an earlier release, select the Release Number from the drop-down.

The first option in the dropdown list is “Control Lines”. Select this option to print a Purchase Order showing only the Control Lines.

After selecting an option, click OK.

The Print One Purchase Order Per Address checkbox may be automatically marked, or unmarked, and/or locked depending on whether or not Control Lines are being printed, and whether or not a Release includes multiple Addresses.

Print One PO per Address
Control Lines Multiple Sites or One Site Unmarked, locked.

All Control Lines are always printed on one PO, even if the Control Lines are for different sites.

Release Lines One Site Marked, locked.

If a Release includes only one site, the checkbox will be marked and locked.

Release Lines Multiple Sites Unmarked, editable.

If a Release includes multiple sites, you can choose to include all lines on one PO (the addresses will print below the Item Number), or to one PO per site (the address will print in the Ship To address box).

The printing process will also populate to Blanket PO tables with the PO Number and the PO Lines to be printed. These tables can be used when creating a custom Purchase Order (such as in Crystal Reports or SSRS) so that the report will pull the Release Lines or Control Lines selected by the User.

The BPO report tables are:

  • BPO Report Header (W7319BPORptHdr)
    • User ID
    • PO Number
  • BPO Report Detail (W7319BPORptDtl)
    • User ID
    • PO Number
    • Ord (PO Line Number)

Blanket POs cannot be printed from the Print Purchasing Documents window.

14.Receiving a Blanket #

Receiving a Blanket PO

Receiving a Firmed Release from a Blanket PO is performed exactly like receiving a regular PO Line.

The Select Purchase Order Items window will not show the Blanket Control Lines or the Planned Release Lines—it only shows the Firmed Release Lines. The Item Description field for Blanket Lines will show the Release Number (i.e. “RN: 1”), and the Promised Date from the PO Line.

15.Closing a Blanket #

Closing a BlanketPO

BlanketPOs which use a PO Line control method will close automatically when the Control Lines are complete.

BlanketPOs which use a PO level control must be manually closed. They will remain open even after the Control Amount has been reached. This allows changing the PO Control Quantities, perhaps after making another agreement with the Vendor to extend the Blanket.

A BlanketPO cannot be closed if it has a Firmed Release line which is new or partially received. All Firmed Releases need to either be received or canceled.

Any BlanketPO can be forced closed by using the “Close PO” utility in the PO Settings window.

Steps To Close a Blanket PO

  1. Select the PO in Blanket PO Entry
  2. Select Actions >> PO Settings
  3. Click CLOSE PO.

You will be asked to confirm you are ready to close the PO. Closing the PO cannot be undone because the PO is automatically moved to history after it has been closed.

If auditing is enabled, you will also be required to enter a reason for closing the PO.

16.PO Release Inquiry #

PO Release Inquiry

HelpID: 731922007

From the Purchase Order Inquiry Zoom window, select Additional >> PO Release Inquiry

This window displays the Blanket PO Release information in a view-only window.

17.PO Settings Inquiry #

PO Settings Inquiry

HelpID: 731922024

From the Purchase Order Inquiry Zoom window, select Additional >> PO Settings Inquiry

To view the Audit, select the GoTo button >> View Audit.

 

18.Reporting Integration #

Reporting Integration

Release Number

Release Number can be added to any POP Report Form by using the Report Writer User Defined function called rw_TableLineString. Follow the steps below to add Revision Level to any POP Report.

Step-1: Create a calculated field to change the datatype of ORD (the PO Line) to be currency. The rw_TableLineString function require the input for this field using the currency datatype, but ORD are long integer. The following steps explain how to create the conversion fields.

 

  1. Open the POP Report Form (such as POP Purchase Order Other Form) in Report Writer
  2. Select Calculated Fields from the Toolbox, then click NEW
  3. Name the field: cyORD
  4. Result Type = Currency
  5. Click the FIELDS tab.
  6. In the Resources list, select Purchase Order Line Rollup Temp. Select the ORD field.
  7. Click Add
  8. Click OK to save the Calculated Field.

Step-2: Create a calculated field for Release Number.

  1. Select Calculated Fields from the Toolbox, then click NEW
  2. Name the field: sRelNum
  3. Result Type = String
  4. Click the FUNCTIONS tab, click User-Defined, select Core = System, then Function = rw_TableLineString
  5. Click Add
  6. Add the Product ID
    1. Click the CONSTANTS tab, select Type = Integer, enter 7319, then click ADD.
  7. Add the Report Name
    1. On the Contants Tab, select Type = String, enter POP, then click ADD.
  8. Add the PO Number
    1. On the Fields tab, select Resources = Purchase Order Line Rollup Temp, select Field = PO Number, then click ADD.
  9. Add the Document Type (this is not used)
    1. On the Constants tab, select Type = Integer, enter 1, then click ADD.
  10. Add the ORD
    1. This is where you use the cyLineSeq created above. Click the Fields tab, select Resources = Calculated Fields, select Field = cyORD, then click ADD.
  11. Add the Sequence (this is not used)
    1. On the Constants Tab, select Type = Currency. Enter 0 (zero), then click ADD.
  12. Add the Data Control
    1. This is an integer that tells GP PowerPack which piece of data to return. In this case there is only one, Release Number, so add an Integer Constant of 1. Click the Constants tab, select Type = Integer, enter 1, then click ADD.
  13. Click OK to save the calculated field.

Add sRelNum to the modified POP Form, and format as needed. Release Number should be added somewhere in the Report and Page Header sections, as shown below:

The Release Number Label from Setup (see Setup) will automatically be added to the Release Number returned by the rw_TableLineString function.

 

The sRelNum calculated field output is shown below. Note that “RN” is added automatically because “RN” was entered as the Release Number Label in the Setup window. You can hard-code a prefix onto the report if desired, and leave the Release Number Label field blank on the Setup window.

PO Settings – Numeric

The numeric values from the PO Settings window (Blanket PO control values) can be added to GP reports by using the report writer function: rw_TableLineCurrency.

Values for the Control Number:

1 = Blanket Control. Returned values are:

1 – Control by Line Quantity

2 – Control by Line Cost

3 – Control by PO Quantity

4 – Control by PO Cost

2 = Control Amount. Either the total of Control Lines (for a Line Control method), or the PO Control Amount from PO Settings.

3 = Total Release value (either Total Cost, or Total Quantity in the Base UofM)

4 = Release Minimum Quantity

5 = Release Minimum Cost

Steps to create a calculated field for numeric PO Settings

Open the GP report in Report Writer

In the Toolbox, select Calculated Fields, click NEW

This example will create a field to display Release Minimum Cost.

  1. Name: cReleaseMin
  2. Result Type: Currency
  3. Select Functions >> User Defined. Core = System. Function = rw_TableHeaderCurrency. Click ADD
  4. Click Constants. Type = Integer. Constant = 7319. Click ADD
  5. Click Constants. Type = String. Constant = empty (don’t enter anything). Click ADD
  6. Click Fields. Resources = Purchase Order Work (or other table containing the PO Number). Field = PO Number. Click ADD
  7. Click Constants. Type = Integer. Constant = 0. Click ADD
  8. Click Constants. Type = Integer. Constant = 5. Click ADD. NOTE: see the Control Number values listed above for the values to enter in this field. 5 returns the Release Minimum Cost.
  9. Click OK to save the Calculated Field.
  10. Drag it onto the report
  11. Close the report to save it

PO Settings – Strings

String values from the PO Settings window (Blanket PO Control Values) can be added to GP reports by using the report writer function: rw_TableHeaderString.

Values for the Control Number:

1 = Previous Blanket PO Number

2 = Contract Number

3 = End Date

Steps to create a calculated field for string PO Settings

Open the GP report in Report Writer

In the Toolbox, select Calculated Fields, click NEW

This example will create a field to display Previous Blanket PO Number

  1. Name: sPrevBPO
  2. Result Type: String
  3. Select Functions >> User Defined. Core = System. Function = rw_TableHeaderString. Click ADD
  4. Click Constants. Type = Integer. Constant = 7319. Click ADD
  5. Click Constants. Type = String. Constant = empty (don’t enter anything). Click ADD
  6. Click Fields. Resources = Purchase Order Work (or other table containing the PO Number). Field = PO Number. Click ADD
  7. Click Constants. Type = Integer. Constant = 0. Click ADD
  8. Click Constants. Type = Integer. Constant = 1. Click ADD. NOTE: see the Control Number values listed above for the values to enter in this field. 1 returns the Previous Blanket PO Number.
  9. Click OK to save the Calculated Field.
  10. Drag it onto the report
  11. Close the report to save it

19.Changing Control Line Increment #

Changing Control Line Increment

If you started to use Blanket PO and need to change the Control Line Increment you will need to remove all existing Blanket POs.

Delete, Void, or Cancel all open Blanket Purchase Orders. This is required because after you change the Control Line Increment, the Blanket PO module will no longer recognize Blanket POs created with the previous numbering sequence. If you already have completed receipts against Blanket POs, once those POs are closed and the Control Line Increments is changed, you will not be able to view those POs in the BPO Inquiry window.

Use SQL Management Studio to run the following update. This query will re-enable the Control Line Increment field.

Open Blanket PO Setup and enter the new Control Line Increment.

Control Line Increment will lock again the first time you use the Blanket PO Entry window.

20.Tables #

Tables

The SQL database tables for BlanketPO begin with W7319. For example, W7319Audit is the table which stores the PO Settings audit information.

Table Comment
W7319BPORptHdr This table is provided to support clients who need to write a custom PO report in an external reporting tool, such as SQL Reporting Services.

When a user prints a PO from Purchase Order Entry, one record will be added to this table. The key field is USERID. The PO Report should have a restriction based on User ID so that it pulls to correct PO. PO Number is the other column in this table.

W7319BPORptDtl This is the custom reporting detail table. This table contains the key fields which correspond to the PO Lines table (POP10110). There will be one record in this table for each line that should be printed.

For example, it will contain the keys to retrieve the Control Line records from POP10110, or the keys to retrieve the lines for a specific Release Number.

W7319PO Stores the PO Control Settings.
W7310POAudit Stores the Po Control Settings audit information.
W7310POItems Stores the PO Control Items
POP10100 BlanketPOs are stored in the POP tables just like any other purchase order. For BlanketPOs the two fields below will be set as shown:

POTYPE = REGULAR (1)

CNTRLBLKTBY = 1,2, 3 or 4. This corresponds to:

1 – Control by PO Line Quantity

2 – Control by PO Line Cost

3 – Control by PO Quantity

4 – Control by PO Cost

POP10110 There are several pieces of information which will identify the BlanketPO Lines.

The LineNumber of Control Lines will be in even multiples of the Control Increment. If your Control Increment is 100, LineNumbers 100, 200, 300, etc are control lines.

LineNumber % Control Increment = 0

The formula above can be used in tSql to identify Control Lines.

Also, for Control Lines the CostCatID field will contain the Control Method. This field is blank for Release Lines.

For Release Lines the LineNumber is not an even multiple of the Control Increment.

LineNumber % Control Increment <> 0

The formula above can be used in tSql to identify release lines.

ProjNum = Release Number. Only populated for Firmed Release lines.

RELEASE = 0 for Planned Releases, and 1 for Firmed Releases.

Help Guide Powered by Documentor
Suggest Edit