Purchase Release Line - Details by Schedule (tdpur3522m100)
Use this session to view purchase release line details by schedule number.
If the purchase schedule is a non-referenced schedule, a purchase release line detail can contain clustered purchase schedule lines.
If the purchase schedule is a referenced schedule, schedule lines are not clustered. As a result, a one-to-one relationship exists between the purchase release line detail in the current session and the purchase schedule line in the Purchase Schedule Lines (tdpur3111m000) session.
If the referenced schedule is a sequence shipping schedule, no purchase release line details are stored in the current session. The reason for this is that items in a sequence shipping schedule are required for a combination of vehicle number (VIN), line station, and assembly kit. For this reason, a link exists between the release header in the Purchase Releases (tdpur3120m000) session and the release lines in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session. For more information, refer to Sequence shipping schedules.
On the appropriate menu, you can choose:
- Material Release release type. , to show the purchase release's
- Shipping Schedule release type. , to show the purchase release's
- , to show all release types of the purchase release.
- FAB/RAW Authorizations (tdpur3534m000) session. , to start the
Field Information
- Release
-
The number of the purchase release.
- Schedule Type
-
The type of the purchase schedule.
Allowed values
- Pull Call-off
-
A list of time-phased specific requirements of purchased items, triggered from the Assembly Control module, or from Warehousing by means of Kanban, or Time-phased order point.
- Pull Forecast
-
A list of time-phased planned production requirements, generated by Enterprise Planning , which are sent to the supplier. Pull forecast schedules are only used for forecasting purposes. To actually order the items, a pull call-off schedule must be generated.
- Push
-
A list of time-phased requirements, generated by a central planning system such as Enterprise Planning or Project , which are sent to the supplier. Push schedules contain both a forecast for the longer term and actual orders for the short term.
- Issue Date
-
For non-referenced schedules, the issue date is the next schedule issue date.
For referenced schedules, the issue date is the date on which the purchase release is created for the first time.
- Rel. Pos. Detail
-
A number used to identify the position of a purchase release line detail in a purchase release. Each release line detail receives a separate release position number.
Note: For non-referenced schedules, several schedule lines can be clustered into one release line detail. For referenced schedules, a one to one relationship exists between a purchase release line detail and a purchase schedule line. - Item
- Engineering Item Revision
-
The revision of the engineering item.
- Release Status
-
The purchase release line detail's status.
A purchase release line detail can have the following statuses:
- Preview
- Scheduled
- Sent
Note: A purchase release line detail always has the same status as the purchase release line to which the line detail is linked in the Purchase Release Line (tdpur3121m000) session. - Schedule Position
-
Default value
In case of referenced schedules, this field is defaulted from the Line field in the Purchase Schedule Lines (tdpur3111m000) session.
Note: The schedule position number is only filled if the purchase release contains referenced schedules. Because these schedules are not clustered, a one to one relationship exists between a purchase release line detail and a purchase schedule line. - Quantity
-
The quantity of the item required for the purchase release line detail.
- Purchase Unit
-
The order quantity expressed in the purchase unit.
- Start Date
-
For non-referenced schedules, this field represents the schedule issue date.
Dependent on whether the purchase release is receipt based or shipment based, the start date is the first planned delivery date or planned shipment date from which purchase schedule lines are clustered into a specific release line detail.
Note: Purchase schedule lines with a planned delivery date/ planned shipment date falling within the time period determined by the current field and the End Date field, can be clustered into one release line detail.For referenced schedules, this field represents a schedule line's planned delivery date or planned shipment date, and is defaulted directly from the Planned Receipt Date field or the Planned Shipment Date field of the Purchase Schedule Lines (tdpur3111m000) session.
- End Date
-
For non-referenced schedules, dependent on whether the purchase release is receipt based or shipment based, the end date is the last planned delivery date or planned shipment date until which purchase schedule lines are clustered into a specific release line detail.
Note: Purchase schedule lines with a planned delivery date/ planned shipment date falling within the time period determined by the Start Date field and the current field, can be clustered into one release line detail.For referenced schedules, this field represents a schedule line's planned delivery date or planned shipment date, and is defaulted directly from the Planned Receipt Date field or the Planned Shipment Date field of the Purchase Schedule Lines (tdpur3111m000) session.
- Requirement Type
-
The requirement type of the release line detail.
Note: For referenced schedules, the requirement type is always Firm.Allowed values
- Firm
- Immediate
- Planned
- Prior Required CUM
-
The prior required CUM expressed in the inventory unit.
Note: The value of the current field can be equal to, higher than, or lower than the amount in the Required CUM field of the Required Cumulatives (tdpur3130m000) session. - Address
- Calendar Code
-
- Warehouse
-
The code of the warehouse where the goods must be delivered.
- Ship-from Address
-
The address of the ship-from business partner.
- Time Unit
-
The segment time unit of the segment within which the purchase release line-detail falls.
A segment can be expressed in the following time units:
-
Hours
Hourly time bucket. -
Days
Daily time bucket. -
Week
Weekly time bucket. This time bucket runs from Monday through Sunday. -
Month
Monthly time bucket. This time bucket runs from the first Monday of the month through the first Monday of the following month. -
Four Weeks
Four weekly time bucket. 13 of these time buckets occur per year.
-
- Release Type
-
The purchase release's release type.
- Purchase Price
-
Note: If the business partner is an external business partner, prices and discounts are defaulted from the Purchase Contract Prices (tdpur3103m000) session.
- Currency
-
The currency in which the amounts on the purchase schedule are expressed.
- Purchase Price Unit
-
purchase-price unit
- Reference ID
-
The unique identification of the call-off that is linked to a referenced schedule, retrieved from a supply system.
The reference ID can be retrieved from the following supply systems:
- Order controlled/batch
- Kanban
- Time-phased order point
Kanban/ Time-phased order point
If pull call-off schedule lines are generated from Warehousing , the Reference ID is generated while creating the purchase schedule line. The reference ID is used as an individual reference for the pull call-off schedule line/ release line detail.
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.Order controlled/batch
If the supply system is order controlled batch, in Assembly Control , a reference ID is created for each material line.
Note: If schedule lines are generated by Assembly Control , the supply system can also be order controlled/SILS. In this case, the reference number/ID is generated in Assembly Control and represents a combination of Vehicle number (VIN), Line Station, and Assembly Kit. 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. For this supply system, no release lines are displayed in the Purchase Release Line (tdpur3121m000) session and no release line details are displayed in the current session. A link exists between the release header in the Purchase Releases (tdpur3120m000) session and the releases per vehicle number in the Purchase Release Lines - Sequence Shipping Data (tdpur3523m000) session. - Option List ID
-
option list ID
Note: Click to view the configured item 's options and features in the Option List (tcibd4522m000) session. - Confirmed Ordered Quantity
-
The schedule quantity that is confirmed by the supplier.
The confirmed quantities are divided over the (clustered) purchase schedule lines when you save the purchase release line detail.
Note:- You can only define this field if the Release Status is Sent.
- This field can only be filled if the Use Confirmation (Purchase) check box is selected in the Implemented Software Components (tccom0100s000) session.
- Confirmed Quantity Unit
-
The unit in which the Confirmed Ordered Quantity is expressed.
- Confirmed Ordered Quantity
-
The schedule quantity that is confirmed by the supplier, converted to the inventory unit.
The confirmed quantities are divided over the (clustered) purchase schedule lines when you save the purchase release line detail.
- Confirmation Date
-
The date on which the supplier confirmed the schedule quantity.
Note:- You can only define this field if the Release Status is Sent.
- This field can only be filled if the Use Confirmation (Purchase) check box is selected in the Implemented Software Components (tccom0100s000) session.
- Tax Classification
-
- Exempt
-
If this check box is selected, tax exemption applies.
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 Exemption Reason and Exemption Certificate fields are cleared and disabled.
- Tax Country
-
The country used for tax purposes.
- Own Tax Number
-
tax ID
- Tax Code
-
The tax code that applies to the items on the purchase schedule line/ purchase release line detail. The tax code indicates the tax percentage to be charged over the order amount.
- BP Tax Country
-
The country in which the business partner has the tax ID.
- 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. - Exemption Certificate
-
Your own exemption 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.
- Exemption 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.
- Last Receipt Date
-
The receipt date of the most recent receipt number that identifies a receipt of goods on the purchase schedule.
- Release Revision
-
The release revision number of the first schedule release is always 0. LN provides every revised schedule release a new release revision number, which is one number higher than the previous revision number.
Note: If the status of the purchase release is Sent, every change in a released schedule or schedule line results in a new revision number. - Length
-
If the physical quantity of the Purchase Unit, which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, is Area or Volume, this field displays the length of the item.
Default value
This field is derived from the Purchase Unit field of the Purchase Schedule Lines (tdpur3111m000) session.
- Width
-
If the physical quantity of the Purchase Unit, which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, is Area, Volume, or Length, this field displays the width of the item.
Default value
This field is derived from the Purchase Unit field of the Purchase Schedule Lines (tdpur3111m000) session.
- Height
-
If the physical quantity of the Purchase Unit, which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, is Area or Volume, this field displays the thickness of the item.
Default value
This field is derived from the Purchase Unit field of the Purchase Schedule Lines (tdpur3111m000) session.
- Received CUM
-
The received cumulative expressed in the inventory unit.
Default value
The latest value of the Received CUM field in the Received Cumulatives (tdpur3132m000) session is defaulted to the current field.
- Release Position
- Schedule
-
The number of the purchase schedule.
- CUM Reset Date
-
CUM reset date
- Additional Information
-
- Additional Field
-
additional information
Click Extended Additional Information (tcstl2110m000) session.
to view all additional information fields that are linked to the purchase document in the