Purchase organizational dataBefore you can perform purchase procedures, you must specify purchase organizational data, such as the purchase order types that define the mandatory steps in the purchase order procedure, purchase offices that you can use to create purchase contracts, orders, and schedules, and user profiles with user-specific default data. If multisite is implemented, you can also specify procurement data and parameters specific for sites. Specifying purchase order types The purchase order type determines the activities that are included in the order procedure, and how and in which sequence the order procedure is carried out. When a purchase order type is linked to a purchase order, the purchase order is processed according to the activities specified for the purchase order type. To specify purchase order types and their activities:
For more information, refer to Flexible purchase order processing. Specifying purchase offices The purchase office determines the location from which purchase orders, contracts, schedules, requisitions, and requests for quotation (RFQs) are processed. A purchase office is required to complete transactions with buy-from business partners. Various purchase offices can be set up for one company. After you set up the purchase office, you can specify user profiles. To specify a purchase office:
Specifying procurement data by site If multisite is implemented, you can specify procurement data and parameters specific for a site. This is data such as settings for back orders and purchase prices. Specifying procurement data by site is required if these data and settings are different from the companywide or global procurement parameters. For more information, refer to Setting up a multisite structure within a company. Specifying user profiles User profiles are used to set up default information for purchasing employees, so documents can be processed faster. In the Purchase User Profiles (tdpur0143m000) session, you can link a user to a purchase office, order type, and warehouse for each login code. If multisite is implemented, you can also link a user to a site. When the user creates a purchase order, call-off, purchase contract, purchase requisition, request for quotation, approval rule, purchase schedule, or purchase release, the user profile determines the defaults. This accelerates the purchase-related transaction entry processes. Specifying approval rules Purchase order approval is a mandatory step in the purchase order procedure. You can validate purchase orders against approval rules before their status becomes Approved. For more information, refer to Approval rules for purchase orders.
| |||