Uploaded image for project: 'PrintTalk'
  1. PrintTalk
  2. PTK-250

Add more information about the Reorder possibility

    XMLWordPrintable

    Details

    • Draft:
      Hide

      Table 6.1 Business Object References

      PurchaseOrder - A PurchaseOrder for a reorder. PurchaseOrder/@ReorderID is specified.
      Note: A PurchaseOrder for a reorder does not specify a BusinessRefID as this would define a change order (see below).

      Table 3.10: PurchaseOrder Element

      ReorderID ? ... Whitespace separated list of unique values that refer to Request/@BusinessID
      values of PrintTalk PurchaseOrder documents that are the basis for this (collected)
      re-order, if the re-order is the starting point. All relevant information for the PurchaseOrder SHALL be present if @ReorderID is present. Note: @ReorderID is provided as a hint for the Print Provider.
      Show
      Table 6.1 Business Object References PurchaseOrder - A PurchaseOrder for a reorder. PurchaseOrder/@ReorderID is specified. Note: A PurchaseOrder for a reorder does not specify a BusinessRefID as this would define a change order (see below). Table 3.10: PurchaseOrder Element ReorderID ? ... Whitespace separated list of unique values that refer to Request/@BusinessID values of PrintTalk PurchaseOrder documents that are the basis for this (collected) re-order , if the re-order is the starting point . All relevant information for the PurchaseOrder SHALL be present if @ReorderID is present. Note: @ReorderID is provided as a hint for the Print Provider.

      Description

      In both RFQ and PurchaseOrder, the @ReorderID attribute can be used to reorder some set of previous PurchaseOrders.  However, this control flow is not mentioned at all in Chapter 6, and additional information on it might be appropriate other places as well.

      For example, in Table 6.1 Business Object References, the appropriate existing row to be updated would be, I suppose:

      PurchaseOrder - The initial PurchaseOrder.
      Note: An initial PurchaseOrder implies known prices from a grid or dynamic website.

      It would make sense if this row mentioned the ReorderID possibility, if in fact this is the appropriate row.  Similarly, is section 6.5.1.1 Fixed Price Procurement the appropriate workflow for this case?  If so, the section should say so.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              denniscarney Dennis Carney
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: