Purchase Requisitions (tdpur2501m000)

Use this session to view, enter, and maintain purchase requisition headers.

You can start this session in the details mode by clicking:

  • Details on the appropriate menu of the Purchase Requisitions (tdpur2501m000) overview session.
  • Purchase Requisition Details on the File menu of the Purchase Requisition (tdpur2600m000) session.

When you double-click a record, or click the New button, the Purchase Requisition (tdpur2600m000) session is started.

 

Requisition

The number that identifies the purchase requisition.

Requisition Origin

The origin that created the requisition.

Allowed values

Origin

Requester

The employee code of the user who initiated the purchase requisition.

Requester Department

The department code of the department who initiated the purchase requisition.

Reference A

The first of two user-defined fields that you can use to gather information for purchase reporting, and maintain purchase requisitions grouped by the reference.

Reference B

The second of two user-defined fields that you can use to gather information for purchase reporting, and maintain purchase requisitions grouped by the reference.

Status

The status of the purchase requisition.

Allowed values

Requisition Status

Workflow Status

The status that is applicable if the business object requires authorization approval using ION Workflow.

When you perform a change that requires authorization, a checked-out version is automatically created for the business object. The changes you submit are only effective after approval/check-in. You can also undo your changes, or recall your submitted changes.

  • Checked-out and checked-in objects are displayed in the Checked-out Objects (ttocm9599m000) session.
  • From the appropriate menu of this session, select Workflow and execute the required action for the business object.

Allowed values

If the business object is checked out, this field displays an Object status.

If the business object is checked in, this field displays an Approval status.

If a description is specified for the object type in the Workflow Information Fields (ttocm0106m000) session (which is displayed as a tab in the Object Types (ttocm0102m000) session), regardless if the object is checked in or out, this field always displays the value of the appropriate Description field.

Note

For more information on setting up and using ION Workflow for business objects in LN, refer to the Infor LN Integration Guide for Infor ION Workflows and Monitors.

Last Transaction Date

The last date on which the requisition was modified.

Requisition Date

Initially, this is the date on which the requisition is specified, but this date can be manually changed to a date in the future.

Default value

The current (creation) date.

Requested Date

The date on which the requested item must be received.

Approver Department

The department code of either a department defined as the approver department, or the department to which the approver has been assigned.

Note

The approver department must be a valid department as defined in the Approvers (tdpur2105m000) session.

Default value

For requisitions with the Created status, this field is defaulted from the Purchase User Profiles (tdpur0143m000) session. Otherwise, this field is defaulted from the Purchase Requisition Approval Progress (tdpur2506m000) session.

Approver

The employee code of the person who must approve the purchase requisition.

Note

The employee must be a valid approver as defined in the Approvers (tdpur2105m000) session.

Default value

For requisitions with the Created status, this field is defaulted from the Purchase User Profiles (tdpur0143m000) session. Otherwise, this field is defaulted from the Purchase Requisition Approval Progress (tdpur2506m000) session.

Spend Approved

If this check box is selected, the purchase requisition was approved in the (external) approval process.

Note
  • If the Budget Control check box is selected in the Implemented Software Components (tccom0100s000) session, the requisition obtains the Approved status when the budget check was successful for all requisition lines, and as a result, the Budget Exception check box is cleared on the requisition lines.
  • If the Budget Control check box is cleared, when the requisition receives the Approved status, the Spend Approved check box is also selected.
Reason for Rejection

The reason why the Status is set to Rejected.

Urgent

If this check box is selected, the requisition line is urgent on the Buyer Home page.

Allow Partial Rejection

If this check box is selected, a purchase requisition can receive the Approved status if, besides approved lines, it also contains requisition lines that are rejected. Therefore, the purchase requisition allows rejection of individual lines. Only the lines with the Rejected check box cleared can be converted to a request-for-quotation (RFQ) or a purchase order.

If this check box is cleared, a purchase requisition cannot receive the Approved status if it contains requisition lines with the Rejected check box selected.

Text

If this check box is selected, a text is present.

Conversion Type

Conversion Type

Default value

The value of this field is defaulted to the lines of the purchase requisition, but can be modified for each requisition line using the Purchase Requisition - Prepare Conversion (tdpur2600m100) session.

Buyer

The employee of your company who is the contact to the concerned buy-from business partner. The buyer is also known as the purchasing agent.

Purchase Office

The purchase office associated with the requisition. The purchase office provides the appropriate default office attributes during requisition entry.

Currency

A generally accepted medium of exchange such as coins, treasury notes, and banknotes.

The following currency types are available in LN:

  • Home currency, which is used internally by companies to calculate costs, record budgets, and register tax amounts
  • Transaction currency, which is used in transactions with business partners, such as orders and invoices
Requesting Warehouse

The code of the warehouse where the requested item must be delivered.

Receipt Address

The actual address where goods must be delivered that you recorded for each supplier. In practice, this can be one of your warehouses.

Project

The code of the project for which the item is required.

Default value

The value of this field is defaulted to requisition lines.

Element

The element linked to the project.

Default value

The value of this field is defaulted to requisition lines.

Activity

The activity linked to the project.

Default value

The value of this field is defaulted to requisition lines.

Extension

The parts of projects for which special arrangements are have been made that concern invoicing, such as variations, provisional amounts, quantities to be settled, and fluctuation settlements. An extension can be attached to one or more budget lines.

Default value

The value of this field is defaulted to requisition lines.

Related topics

Cost Component

A cost component is a user-defined category for the classification of costs.

Cost components have the following functions:

  • To break down an item's standard cost, sales price, or valuation price.
  • To create a comparison between the estimated production order costs and the actual production order costs.
  • To calculate production variances.
  • To view the distribution of your costs over the various cost components in the Cost Accounting module.

Cost components can be of the following cost types:

  • Operation Costs
  • Material Costs
  • Surcharge on Material Costs
  • General Costs
  • Not Applicable
Note

If you use Assembly Control (ASC), you cannot use cost components of the General Costs type.

Default value

The value of this field is defaulted to requisition lines.

Additional Information
Additional Field

User-defined fields of various field formats that can be added to various sessions, in which users can edit these fields. No functional logic is linked to the contents of these fields.

Additional information fields can be linked to database tables. When linked to a table, the fields are displayed in the sessions corresponding to the database tables. For example, a field defined for the whinh200 table is displayed as an extra field in the Warehousing Orders (whinh2100m000) session.

The contents of additional fields can be transferred between database tables. For example, the information specified by a user in additional information field A of the Warehousing Orders (whinh2100m000) session is transferred to additional information field A in the Shipments (whinh4130m000) session. For this purpose, additional information fields with identical field formats and field name A must be present for the whinh200 and the whinh430 tables (whinh430 corresponds to the Shipments (whinh4130m000) session).

Click Extended Additional Information to view all additional information fields that are linked to the purchase document in the Extended Additional Information (tcstl2110m000) session.

Note

Because no buy-from business partner is available in this session, the additional information fields defined in the General definition level are used.

 

Details

Starts the current session in the details mode.

Submit

Submits the purchase requisition for approval.

Cancel

Cancels the purchase requisition.

Without Buyer

Only displays purchase requisitions with an empty Buyer field.

Urgent (Lines)

Only displays purchase requisitions with the Urgent check box selected.

Approved

Only displays purchase requisitions with the Status set to Approved.