| Sales Release Line Details (tdsls3515m000) Use this session to view, enter, and maintain sales release line details. A sales release line detail mainly contains
quantity data. Note - Only release line details for which the Release Type is set to Material Release and Shipping Schedule are displayed in this session.
- A sales release line detail refers to a sales schedule line.
- This session is updated when the release line detail is
processed into a sales schedule line.
- If the Status is Processed, you can no longer update the sales release line
detail.
Release Identifies, by one release number, those sales schedules that
share the following common characteristics: - Sold-to business partner.
- Ship-to business partner.
- Ship-to address.
- Release type (material release/ shipping schedule/ sequence
shipping schedule/ pick-up sheet).
- Shipment based schedule/ receipt based schedule.
- Schedule quantity qualifier.
- Forecast horizon start and end.
- Sales release origin.
- Customer release.
- (Customer order).
Release Revision A number that identifies the revision of the sales release. The
sales release revision identifies the update that was sent to the business
partner. Release Position The number that identifies the sales release line. Sequence The number that identifies the sales release line
detail. Note A fixed step size of one is
applied. Release Type A classification used to specify the type of the release based
on which schedule requirements are grouped and EDI messages can be generated.
These messages are indicated by the used schedule. Item In LN,
the raw materials, subassemblies, finished products, and tools that can be
purchased, stored, manufactured, sold, and so on. An item can also represent a set of items handled as one kit,
or exist in multiple product variants. You can also define nonphysical items, which are not held
in inventory but can be used to post costs or to invoice services to customers.
The following are examples of nonphysical items: - Cost items (for example, electricity)
- Service items
- Subcontracting services
- List items (menus/options)
Quantity The quantity of the item that is required for the sales
schedule line. Sales Unit The unit in which an item is sold. Lot The lot ID that applies for the specific requirement. Engineering Item Revision Length If the physical quantity of the sales unit is Length, Area (m2), or Volume,
which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, this field displays the length of the item. Width If the physical quantity of the sales unit is Length, Area (m2), or Volume,
which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, this field displays the width of the item. Height If the physical quantity of the sales unit is Length, Area (m2), or Volume,
which you can define in the Physical Quantity field of the Units (tcmcs0101m000) session, this field displays the height of the item. Planned Receipt Date The date on which the goods are expected to arrive in the
destination warehouse. If the sales schedule is: - Shipment Based, your business partner must pick up the items at your warehouse.
As a result, the Planned Receipt Date is equal to the Start Date.
- Receipt Based, you must deliver the items at your business partner's
warehouse. Based on the Planned Receipt Date, LN calculates the
default Start Date and End Date as follows:
- Retrieves the address of the Warehouse.
- Retrieves the Address from the Sales Releases (tdsls3512m000) session.
- Calculates the transportation time between these two
addresses.
- Determines the Start Date by planning backwards from the Planned Receipt Date with the transportation time.
- Determines the End Date by planning forward from the Start Date with the Time Unit.
Start Date The start date and time of the sales schedule line. The start
date is the first date of the period for which the sales schedule line applies. The following restrictions apply for the sales schedule
line's start date: - The start date cannot be before the sales schedule's Generation Date.
- The start date cannot be before the end date of the
previous sales schedule line of the same sales schedule, except if the sales
schedule line concerns an Immediate requirement.
- If the sales schedule is linked to a sales contract, the
sales schedule line's start date cannot be before the sales contract's Effective Date.
- The sold-to business partner and the ship-to business
partner must be active on the start date.
The sales schedule line's start date is also the date on
which the required items must be ready for shipment. If the sales schedule is: - Shipment Based, your business partner must pick up the items at your warehouse.
As a result, the Planned Receipt Date is equal to the Start Date.
- Receipt Based, you must deliver the items at your business partner's
warehouse. In this case, LN calculates the default Start Date based on the Planned Receipt Date.
Time Unit The amount of time the End Date is later than the Start Date. Time Unit Hours The end date is one hour later than the start date. Days The end date is one day later than the start date. Weeks The end date is one week later than the start date. Months The end date is one month later than the start date. Four Weeks The end date is four weeks later than the start date. Not Applicable The end date is equal to the start date.
End Date The end date and time of the sales schedule line. The end date
is the last date of the period to which the sales schedule line applies. If the End Date differs from the Start Date field, the requirement is aggregated. Last Delivery Date The last date on which you shipped goods for the sales schedule
line. Text If this check box is selected, a text is present. Address The ship-to business partner's address. Warehouse The warehouse from which the goods must be shipped. Dock Location The business partner's line station to which the items must be delivered. Delivery Point The business partner's delivery point to which the items must be delivered. Reference The reference that you received from your business partner. Note The reference is only specified if the sales
schedule is referenced. Shipment Reference A reference communicated by the customer to identify the
shipment, such as a transport ID or a customer shipment number. If you use pick-up sheets, this number is used to identify the pick-up sheet to which the
sales schedule line is linked. This reference is used as a general reference in this
session. Packaging Reference A A package building criterion, which refers to the distribution
zone or routing code. Packaging Reference B A package building criterion, which refers to the consumption
point or point of destination. Customer Release The business partner's release number. This number can be used
for reference purposes. Default value This field is defaulted from the Sales Release Lines (tdsls3508m000) session. Customer Release Revision The business partner's release revision number. This number can
be used for reference purposes. Default value This field is defaulted from the Sales Release Lines (tdsls3508m000) session. Customer Release Position The business partner's release line number. This number can be
used for reference purposes. Default value This field is defaulted from the Sales Release Lines (tdsls3508m000) session. Customer Release Position Detail The business partner's release line detail number. This number
can be used for reference purposes. Customer Schedule Number The business partner's schedule number. This field is only used
as a reference. Customer Schedule Position The business partner's schedule line number. This field is only
used as a reference. Customer Requirement Type The requirement type for the sales schedule line. Status The status of the sales release line detail. Revision A number that uniquely identifies the revision of the sales
schedule. The sales schedule revision number indicates the sales schedule
updates that are sent by your business partner. Schedule Position The sales schedule line to which the sales release line detail
refers. A sales schedule line identifies each requirement for an item to be
supplied to a specific business partner on a specific date and time. Price The sales price of the item expressed in the currency that is
displayed in the Currency field. Currency The currency in which the amounts on the sales schedule are
expressed. Sales Price Unit The unit to which the (sales/purchase) price applies. Exempt Note If the Tax Exempt Level parameter in the Tax Parameters (tctax0100m000) session is set to: - Limited and you manually select this check box, the Tax Code is defaulted from the Exempt Sales 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 manually clear this check box, the Exempt Reason and Exempt Certificate fields are cleared and
disabled.
Tax Code The tax code that applies to the sales schedule line. Note The tax code that can be entered in this
field can only be of the VAT kind. Exempt Certificate 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.
Exempt Reason The reason code that indicates why a business partner can be
exempt from tax for a certain transaction and jurisdiction. Note - LN prints the exempt reasons on the sales 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.
- The reason code must be of the Tax Exemption type and must be date effective, as valuated by the Planned Receipt Date.
Additional Information User-defined fields that can be linked to LN tables. The contents of additional fields can be transferred between LN tables. Additional
information fields are meaningless to LN as no functional logic is linked to the contents
of these fields. | |