| | Purchase Schedule Lines (tdpur3111m000) Use this session to view, enter, maintain, or delete purchase schedule lines. Note - You can only maintain schedule lines of nonreferenced schedules in this session.
- You cannot delete schedule lines with the statuses Partial Receipt, Final Receipt, or Invoiced. Processed schedule lines can only be deleted in the Archive and Delete Purchase Schedules (tdpur3224m000) session.
- Transactions are logged for purchase schedule lines based on
the Transaction Time Fence parameter in the Purchase Contract Line Logistic Data (tdpur3102m000) or Items - Purchase Business Partner (tdipu0110m000) sessions.
- If you click the Show the attachments button, the Objects Links (dmcom8110m000) session starts in which you can link a document
of any format to the purchase schedule line, or view the linked
document(s).
Schedule For pull schedules, the same schedule number can occur two times in the Purchase Schedules (tdpur3110m000) session. The first number represents the Pull Forecast schedule type and the second number represents the Pull Call-off schedule type. Note You can specify the default number group for
purchase schedules in the Number Group for Purchase Orders / Purchase Schedules field of the Purchase Schedule Parameters (tdpur0100m500) session. You can determine the default series for the purchase
schedule number group in the following sessions: - Purchase Offices (tdpur0112m000)
- Purchase User Profiles (tdpur0143m000)
Origin The purchase schedule line's origin. Status The schedule line's status. Note If the Use Confirmation check box is selected in the Buy-from Business Partner (tccom4120s000) session, you cannot approve a purchase
schedule line before the Confirmed Quantity and Confirmation Date fields are filled. Schedule Line The number of the schedule line. This number uniquely
identifies each requirement of an item that a specified business partner must
supply at a specific date and time. Note For purchase schedule lines that are
manually specified, you can determine the default step size in the Step Size for Purchase Schedule Lines field of the Purchase Schedule Parameters (tdpur0100m500) session. For purchase schedules that are
automatically generated, to avoid position numbers getting exhausted too soon,
step size 1 is used. Transactions Logged If this check box is selected, transactions have been
logged for the schedule line. Note Transactions are logged based on the value
of the Transaction Time Fence field of the Purchase Contract Line Logistic Data (tdpur3102m000)/ Items - Purchase Business Partner (tdipu0110m000) session. Schedule Text If this check box is selected, a specific text with,
for example, additional reference information is available. Firm Planned If this check box is selected, during the next run of Enterprise Planning, the
schedule line cannot be changed. Note If you click Undo Firm Planned on the appropriate menu of this session, you can change the schedule line's status to Firm. Peg Distribution If this check box is selected, a peg distribution is linked to this Purchase Schedule Line. Subject to Trade Compliance Note This field is available only if the Import Compliance check box is selected in the Global Trade Compliance Parameters (tcgtc0100m000) session. Reference ID The reference ID can be retrieved from one of the
following supply systems: To generate schedule lines from Assembly Control (ASC) If the supply system is order controlled
supply in line sequencing (SILS), a reference number/ID is generated in the Assembly Control (ASC) module, which represents a combination of Vehicle number (VIN),
Line Station, and Assembly Kit. For this reason, a one-to-one relationship
exists between the schedule line reference and the sequence shipping data, as
stored in the Sequence Shipping data (tdpur3517m000) session. The
reference ID is a unique field, which informs you about all items that must be
packed together or that must be treated as a single entity. If the supply system is order controlled
batch, in the Assembly Control (ASC) module, a reference ID is created for each material
line. To generate schedule lines from Warehousing If pull call-off schedule lines are
generated from Warehousing, the reference ID is generated while creating the purchase
schedule line. The reference ID stored in the current field is used as an
individual reference for the pull call-off schedule line. Note If pull call-off schedule lines are
generated from Warehousing, the generated reference ID is derived from the number
group as entered in the Number Group for Call-offs field of the Purchase Schedule Parameters (tdpur0100m500) session. Buy-from Business Partner Note This field cannot be changed on schedule
line level. Ship-from BP Note This field cannot be changed on schedule
line level. Requirement Type If the requirement type in which the
schedule line falls changes as a result of regeneration, the requirement type is updated according
to the new segment set. The new
requirement type is then stored on the schedule line. Note For pull schedules of the type Call-off, no segment sets are used. The
requirement type is always Firm. Warehouse The code of the warehouse where the
goods must be delivered. You must fill this field in case of standard
items. In case of cost items, service items, project subcontracting, and
equipment items, this field must be left empty. Project and equipment items are
delivered at te project's address. Address The address of the warehouse or place where the goods must be
delivered. Extra Intrastat Info Statistical import/export data that is not available as
standard information in LN, but which is required on the sales listing or the
Intrastat declaration by some of the EU member states. You can add up to 15 data fields to the Intrastat statistical
data by defining them as extra Intrastat information set. You can assign the
extra Intrastat information sets to warehouse order lines. Customs Value The tax that is levied on an export article's
value. The customs value is used during the customs
check. If this field is filled, the customs value need not be calculated when
passing the customs, which saves time and transport costs. Restrictions The customs value only applies: - To deliveries, not to receipts. As a result, this field can
only be filled if goods must be returned.
- If the goods are delivered by Warehousing. If
this field is filled and you release the order to Warehousing, the
customs value is defaulted to the Outbound Order Lines (whinh2120m000) session.
Note If the Payment field is set to No Payment, the item's standard cost is displayed by default. Planned Receipt Date The planned date on which the items on the order/schedule line
are planned to be received. The planned receipt date cannot occur before the
order date/schedule generation date. The planned receipt date is important for
schedules that are Receipt Based, as defaulted from the Shipment/Receipt Based field of the Purchase Schedules (tdpur3110m000) session. The planned receipt date is used to: Note If the schedule is Shipment Based, you can calculate the planned receipt date from the planned
shipment date. Planned Shipment Date The planned date on which the items on the order/schedule line
must be shipped/picked up at the ship from business partner's site. The planned
shipment date cannot fall before the order date. The planned shipment date is important for
schedules that are Shipment Based, as defaulted from the Shipment/Receipt Based field of the Purchase Schedules (tdpur3110m000) session. The planned shipment date is used to
determine in which segment the schedule falls,
and, consequently to cluster schedule lines and calculate a schedule line's requirement type. Note If the schedule is Receipt Based, you can calculate the planned shipment date from the planned
receipt date. Confirmation Date Default value This field is defaulted from the Confirmation Date field of the Purchase Release Line - Details (tdpur3522m000) session. Confirmation Accepted If this check box is selected, the Confirmed Quantity is accepted by the buyer. No
further negociations are possible with the supplier. Note - This field can only be filled if the Use Confirmation (Purchase) check box is selected in the Implemented Software Components (tccom0100s000) session.
- If a confirmed quantity of zero is accepted, the schedule
line is canceled automatically.
Default value This field is defaulted from the Confirmation Accepted field of the Purchase Release Line - Details (tdpur3522m000) session. Release If this field is filled, a purchase release
has already been sent to the supplier for this particular schedule line. Receipt The latest receipt number that identifies a receipt of goods on the schedule line. As soon
as receipts are confirmed in Warehousing, this number is communicated to
the Purchase Control module. Note You can have more than one receipt on a
particular schedule line. To view partial receipt details for a schedule line,
on the appropriate menu,
click Receipts. This command starts the Purchase Schedule - Receipts (tdpur3115m200) session, in which you can view all receipt
quantities and receipt numbers for a particular schedule line. Receipt Date Note As soon as a receipt is confirmed in Warehousing, this
number is communicated to the Purchase Control (PUR) module. Sold-to Business Partner LN can use the items supplied by the current
schedule to fulfill a schedule for the sold-to business partner displayed in
this field. Ship-to Business Partner LN can use the items supplied by the current
schedule to fulfill a schedule for the ship-to business partner displayed in
this field. Business Object Type Note The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Business Object Note The following fields are always used in combination;
together, they identify the relevant order or order line: - Business Object Type
- Business Object
- Business Object Reference
Reference The reference code to which this supply object has been demand pegged. LN can only use the items supplied by the current
schedule to fulfill a demand specified by the reference displayed in this
field. LN can use this field in two ways: - If the Sold-to Business Partner field is filled, LN uses the Reference field to record a reference code defined by
a customer.
- If the Sold-to Business Partner field is empty, LN uses the Reference field to record an internal
reference.
You can use a reference code to keep a
collection of parts linked together, even if they follow different routings,
for example, if some of the parts are transported to a subcontractor to be returned later. Option List ID The identification of the options and features for a configured
item. The ID is used in the item specification to match supply and
demand. Inventory on Order The total quantity of supply orders that is demand pegged and will be received in the warehouse,
expressed in the purchase unit. Inventory on Order The total quantity of supply orders that is demand pegged and will be received in the warehouse,
expressed in the inventory unit. Invoice Date The date on which the invoice is printed. Invoice The identification of an invoice, which consists of the
transaction-type code and the first free number in the series used for invoices
for the order type. Payment Use this field to define the payment between the purchase
office, which issues the purchase schedule, and the supplier. Note This field is set to: - Pay on Use if the Consigned check box is selected for the purchase
schedule.
- Pay on Receipt when delivering to a warehouse with a linked sold-to business
partner.
- Pay on Receipt for items that are not received in a warehouse.
For push schedules with a linked blanket warehouse order, this field is defaulted from the Payment field of the Purchase Schedules (tdpur3110m000) session. For sequence shipping schedules, if the Option List ID is specified for any of the linked
sequence shipping data records in the Sequence Shipping data (tdpur3517m000) session, you cannot select Pay on Use or No Payment. Payment (Internally) Use this field to define the payment between the purchase
office, which issues the purchase schedule, and the warehouse, which receives
the purchase schedule. Note This field: - Is set to Pay on Receipt when delivering to a project (without a warehouse), or a work
center.
- Is set to Not Applicable if the Payment field is set to No Payment.
- Cannot be set to No Payment.
- Is defaulted from the Payment (Internally) field of the Purchase Schedules (tdpur3110m000) session for push schedules with a linked blanket warehouse order.
Payment (Direct Delivery) Use this field to define the payment between the purchase
office, which issues the purchase schedule, and the customer. This field applies if a purchase schedule is
created at the supplier's site for directly delivering goods to a VMI warehouse at the customer's site by a third
party. Note This field: - Must be set to Pay on Use or No Payment if the warehouse has a sold-to business partner
linked to it.
- Is set to Not Applicable if the warehouse has no linked sold-to business
partner.
- Cannot be set to Pay on Receipt, because no sales orders can be generated for purchase
schedules.
- Is defaulted from the Payment (Direct Delivery) field of the Purchase Schedules (tdpur3110m000) session for push schedules with a linked blanket warehouse order.
Purchase Type A purchase order property that enables you to identify the kind
of purchase made and in this way, the kind of payable. This property is used to
post the purchase to the correct Accounts Payable account when the invoice is created. To
post a purchase invoice, LN retrieves the control account from the purchase type linked to the
purchase order line. Note A control account is defined for every purchase type. When
purchase invoices are posted, LN retrieves the purchase type to determine the control account that
must be used for posting. Tax Tax Classification An attribute of order headers and order lines that you can use
to define tax exceptions for the transaction. LN retrieves the default
tax classification from the invoice-from and invoice-to business partners. For example, you can use the tax classification to
indicate: - That payments to an invoice-from business partner are subject
to withholding tax and social contributions
- To group business partners who have the same tax aspects for
your company, for example, subcontractors, or agents
- That the tax must be paid in a country other than the sales
office or service office's home country
Default value This field is defaulted from the purchase
schedule header. Exempt Note If the Tax Exempt Level parameter in the Tax Parameters (tctax0100m000) session is set to: - Limited and you select this check box manually, the Tax Code is defaulted from the Exempt Purchase field of the Tax Handling (tctax0138m000) session. If you clear this check box manually, the tax
code is not changed.
- Extended and you select this check box manually, the Tax Code is not changed. If you clear this check box manually, the Exempt Reason and Exempt Certificate fields are cleared and
disabled.
Own Tax Number A number used to identify legal persons or businesses. The tax
authorities assign the tax numbers to the registered businesses. Your business
partners must provide you with their tax number. Business partners without a
tax number are considered to be private persons. Tax Code The tax code that applies to the purchase schedule line. Note The tax code that can be entered in this
field can only be of the VAT kind. BP Tax Number The business partner's tax ID. Note The business partner's tax ID is date
effective. To determine and display the correct tax ID for the business
partner, LN uses the
planned receipt date. Exempt Reason The reason why your own company is exempt from sales
tax. Note - This field only applies if the Tax Exempt Level parameter is set to Extended in the Tax Parameters (tctax0100m000) session.
- This field is defaulted from the method that is used to
retrieve tax details, as defined in the Search Sequence Tax Libraries group box of the Tax Parameters (tctax0100m000) session.
- The reason code must be of the Tax Exemption type and must be date effective, as valuated by the Planned Receipt Date.
Exempt Certificate Note - LN prints the exempt reasons on the invoices.
- This field only applies if the Tax Exempt Level parameter is set to Extended in the Tax Parameters (tctax0100m000) session.
- This field is defaulted from the method that is used to
retrieve tax details, as defined in the Search Sequence Tax Libraries group box of the Tax Parameters (tctax0100m000) session.
Required Ordered Quantity Note Enterprise Planning uses this field to check whether
the confirmed quantities are enough to meet the planned quantities, or whether
additional supply is required. Required Ordered Quantity Unit The unit in which the Required Ordered Quantity is expressed. Confirmed Quantity Note Enterprise Planning uses this field to check whether
the confirmed quantities are enough to meet the planned quantities, or whether
additional supply is required. Default value This field is defaulted from the Confirmed Quantity field of the Purchase Release Line - Details (tdpur3522m000) session. Confirmed Quantity Unit The unit in which the Confirmed Quantity is expressed. Default value This field is defaulted from the Confirmed Quantity Unit field of the Purchase Release Line - Details (tdpur3522m000) session. Schedule Quantity This field is filled with the value of the: - Confirmed Quantity field if the Confirmation Date is filled.
- Required Ordered Quantity field if the Confirmation Date is not filled.
Purchase Unit The unit in which you purchase an item, also referred to as
the purchase quantity unit. Note The unit set in which the unit is stored must be linked to the item in the Items - Defaults (tcibd0102m000) session. You can define units in the Units (tcmcs0101m000) session, unit sets in the Unit Sets (tcmcs0106m000) session, and units by unit set in the Units by Unit Set (tcmcs0112m000) session. Note - A conversion factor must be linked to the item in the Conversion Factors (tcibd0103m000) session.
- If a contract is linked to the schedule, the unit defined
in the Purchase Contract Lines (tdpur3101m000) session is used by default. If no
contract is linked, LN uses the purchase unit that is specified in the Items - Purchase (tdipu0101m000) session.
Schedule Quantity This field is filled with the value of the: - Confirmed Quantity field if the Confirmation Date is filled.
- Required Schedule Quantity field if the Confirmation Date is not filled.
Invoiced Quantity The invoiced quantity of all approved invoices linked to this schedule line,
expressed in the inventory unit. Note If the Method of Calculating Average Purchase Price field in
the Purchase Order Parameters (tdpur0100m400) session has the value Current Inventory, the current field is also filled when partial invoices are
approved. The reason for this is to make correct calculations for the average
purchase price. Schedule Currency The currency in which the
amounts on the purchase schedule are expressed. Price The price you pay for an item, expressed in the purchase
currency. Note - If the business partner is an external business partner,
prices and discounts are defaulted from the linked Purchase Contract Prices (tdpur3103m000) session.
- If the item is a configurable item and the Option Based Pricing check box is selected in the Purchase Contract Lines (tdpur3101m000) session, the price is retrieved from the generic price list in the Generic Price Lists (tipcf4101m000) session.
- If the Payment field is set to No Payment, the price is zero.
- If the Material Pricing in Procurement check box is selected
in the Material Price Parameters (tcmpr0100m000) session, this price can include material prices.
/ The item unit in which an item's purchase price is expressed.
This unit can differ from the item's inventory unit. Total Discount % The total of all discounts that are applied to the schedule
line, expressed as a percentage. Net Amount The net amount is calculated as follows: Purchase schedule line quantity * price - discount. Note f the purchase schedule is linked to a
contract, prices and discounts are defaulted from the linked Purchase Contract Prices (tdpur3103m000) session. If no contract is linked to the
purchase schedule, prices and discounts are retrieved from the Item Purchase Data module. Landed Cost Amount The total of all costs that are associated with the procurement
of an item until delivery and receipt in a warehouse. Landed costs typically
include freight costs, insurance costs, customs duties, and handling
costs. Inventory Unit The unit of measure in which the inventory of an item is
recorded, such as piece, kilogram, box of 12, or meter. The inventory unit is also used as the base unit in measure
conversions, especially for conversions that concern the order unit and the
price unit on a purchase order or a sales order. These conversions always use
the inventory unit as the base unit. An inventory unit therefore applies to all
item types, also to item types that cannot be kept in stock. Received Quantity The actually delivered quantity of items on the purchase schedule line, expressed in the
inventory unit. Received Amount The received quantity * (price - discount amount per schedule
line). Note If a receipt is confirmed for a configured item that deviates from the ordered configured item, in the Sequence Shipping data (tdpur3517m000) session, LN retrieves the price
and discounts from the last Sent sequence shipping schedule line revision with a
configured item that is equal to the received configured item. Otherwise, the
price and discounts from the current session are used to calculate the
amount. Preferred Manufacturer Part Number Note The MPN must have the status Approved on the requirement date, which is the planned
delivery date. Item The raw materials, subassemblies, finished products, and tools
that can be purchased, stored, manufactured, and sold. An item can also represent a set of items handled as one kit,
or which exist in multiple product variants. You can also define nonphysical items, which are not
retained in inventory but can be used to post costs or to invoice services to
customers. The examples of nonphysical items: - Cost items (for example, electricity)
- Service items
- Subcontracting services
- List items (menus/options)
Buy-from Business Partner Note This field cannot be changed on schedule
line level. Frozen The freezing status of the schedule line. Note For an external business partner, you can determine the
periods for which the requirements on the schedule lines are frozen in the
following fields of the Purchase Contract Line Logistic Data (tdpur3102m000) session: - Freezing Time Increase.
- Frozen Period (-).
For an internal business partner, you can define these
periods in the following fields of the Items - Purchase Business Partner (tdipu0110m000) session: - Frozen Period for Increasing Qty.
- Frozen Period for Decreasing Qty.
LN automatically fills in the field in the current
session. To determine the value of this field, LN compares the dates
on the schedule line with the period that is defined in the previously
mentioned fields. Schedule Amount The cumulative order amount of all lines in a schedule after
discounts are deducted. Note If the Payment field is set to Pay on Receipt, received schedule lines are not taken into account in the
schedule amount calculation. Sched Amnt (Home) The currency in which balances of entities shared by all the
companies of a financial company group are expressed. For example, LN uses the reference
currency for business partner balances. Note - The reference currency is the common base currency of the
companies in a multisite structure.
- For currency systems other than the standard currency system, the reference currency is a
company's base currency for all calculations with currencies.
Item The item that is derived from the schedule header. Status The purchase schedule's status. Open Balance The balance of all unpaid invoices relating to one particular
business partner. Open Balance The currency in which the
open balance is expressed. Project The code of the project for which the item
is required. Note - You can only enter TP projects in this field. PCS projects
are not allowed.
- You can only enter a project code in this field for push schedules.
Element The smallest part of an element structure. An element is used
to define the (structure of the) work of the project, so that you can carry it
out. Activity The unique identification of an activity. 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. Note This field is blank and disabled if the Peg Distribution check box is selected in this session. 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
- General Costs
- Not Applicable
Note If you use Assembly Control (ASC), you cannot use cost components
of the General Costs type. Note This field is blank and disabled if the Peg Distribution check box is selected in this session. 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). | |