| Purchase organizational data |  |
| Before you can carry out purchase procedures, you must define purchase organizational data, such as order types that define the steps that are mandatory in a purchase order procedure, purchase offices that you can use to create purchase contracts, purchase orders, and purchase schedules, user profiles with user-specific default data, and so on. To define 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 and the type of order defined for the purchase order type. To define purchase order types and their activities, take the following steps: Enter a purchase order type in the Purchase Order Types (tdpur0194m000) or the Purchase Order Type - Activities (tdpur0694m000) session. In addition to the normal purchase order type, several special order types exist. By selecting one or more of the check boxes ( Cost Order, Collect Order, Return Order, and so on), the creation and processing of these orders can differ from normal purchase orders. On the Activities tab of the Purchase Order Type - Activities (tdpur0694m000) session, you must specify for the purchase order type: The activities (tasks) to be carried out. The sequence in which these activities must be carried out. Whether the activity must be carried out automatically or manually. As a result, you can automate the processing of purchase orders. For details, refer to Flexible purchase order processing. Tip You must make sure that the list of activities that is linked to an order type is extensive in order to cover all processes that can apply during execution of the order procedure. If an activity is not applicable to the order type, ERP LN automatically skips this activity. You can view the actual activities that are linked to the purchase order (detail) line and the status of the activities in the Purchase Order Activities (tdpur4113m000) session. To define purchase offices The purchase office determines the location from which purchase orders, contracts, schedules, requisitions, and requests for quotations are processed. A purchase office is needed to complete transactions with buy-from business partners. Various purchase offices can be set up for one company. Once you set up the purchase office, you can define user profiles. To define a purchase office, you must complete the following steps: Define the purchase office as a department in the Departments (tcmcs0565m000) session. Specify purchase-office-specific data in the Purchase Offices (tdpur0112m000) session. The enterprise unit to which the department is linked informs you about the financial company to which financial transactions for the purchase office are posted. If you want to use purchase offices in combination with purchase orders, purchase schedules, purchase contracts, schedule releases, call-offs, requests for quotations, or requisitions, you must fill the concerned series fields. To define 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. 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. To define 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 on defining approval rules, refer to Purchase order approval. Related topics Flexible purchase order processing Purchase order approval Purchase item data General purchase data |