The Corporate Purchasing Submit Pipeline

The Corporate Purchasing Submit pipeline consists of two stages. These stages run components that validate the purchase order requisition, transfer the purchase order to the vendor, and write the order to database storage. This pipeline is analogous to the Purchase pipeline used in business-to-consumer sites.

The Corporate Purchasing Submit pipeline can be run once you have run an OrderForm successfully through the Corporate Purchasing Plan pipeline, and have confirmed the customer’s desire to finalize a purchase.

Because these pipeline components write to a database, the Corporate Purchasing Submit pipeline is often a transacted pipeline. A transacted pipeline is a pipeline that consists exclusively of components that are designed and configured to support Microsoft Transaction Server (MTS) transactions.

This template for the Corporate Purchasing Submit pipeline is CorpPurchaseSubmit.pct. An example of a pipeline based on this template is the CorpPurchasingSubmit.pcf file in the /Config directory of the Microsoft Market sample site.

The Corporate Purchasing Submit pipeline template consists of the following stages.

Purchase Order Validate Stage

The Purchase Order Validate stage is used to verify that the purchase order is valid.

Commerce Server 3.0 includes no component for this stage (other than Scriptor). However, you can add your own custom component to validate the purchase order.

Purchase Order Submit Stage

This stage handles the completed purchase order and transmits it to the vendor.

The components related to this stage include the following.