| Sales Release Lines (tdsls3508m100) 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)
- Customer contract reference
Revision A number that uniquely identifies the revision of the release.
The release revision number indicates the updates that are sent to the business
partner. Line The number that identifies the sales release line. Sold-to Business Partner The business partner who orders goods or services from your
organization, who owns the configurations you maintain, or for whom you perform
a project. Usually a customer's purchase department. The agreement with the sold-to business partner can include: - Default price and discount agreements
- Sales order defaults
- Delivery terms
- The related ship-to and invoice-to business partner
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)
If an incoming EDI item is unsuccessfully converted during
processing EDI messages, this field is left empty. Note If lines are manually added to releases with the Sales Release Origin set to EDI, you can
leave the Item blank and only fill the Customer Item. Item code conversion will be applied
during sales release processing if the conversion settings are correctly
defined. Customer Item Identification code for an item (product, component, or part).
The item code can consist of multiple fields or segments. This field is automatically filled with the incoming EDI
item code, which must be converted during processing EDI messages. Note If lines are manually added to releases with the Sales Release Origin set to EDI, you can
leave the Item blank and only fill the Customer Item. Item code conversion will be applied
during sales release processing if the conversion settings are correctly
defined. 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. Origin The origin that created the sales release line. Status The status of the sales release line. Creation Date The date and time on which the sales release line was
created. Warnings Present If this check box is selected, a warning message is
linked to the sales release line. Errors Present If this check box is selected, an error message is
linked to the sales release. 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 Releases Overview (tdsls3512m000) session. 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 Releases Overview (tdsls3512m000) session. Customer ReleasePosition The business partner's release line number. This number can be
used for reference purposes. Customer Order The number assigned to the order or contract by the sold-to
business partner (for example, the sold-to business partner's purchase contract
number). The customer order number can be used to identify a sales contract
line. Customer Contract Reference The identifier of the item's model, part, or year with the
sold-to business partner. This reference is used to identify a sales contract
line. Schedule 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. Processing Date The date and time on which the sales release line was processed
into a sales schedule. Item Code System An external, alternate way of coding items. Coding systems can
be general standard systems (such as EAN) or systems that are dependent on a
specific business partner. Note This field is used for conversion of an incoming EDI item
code. Convert Item If this check box is selected, conversion of an EDI item must still be
applied. Note If conversion is needed during processing releases to
schedules, Electronic Data Interchange automatically selects this check box. Ship-to Address The ship-to business partner's address. EDI Business Partner The EDI sold-to business partner, which is used for conversion of an incoming EDI item
code. Item code conversion will be applied during sales release
processing if the conversion settings are correctly defined. Lot Selection Define conditions for the shipment of lot items. Allowed values Any The goods to be shipped are not subject to any special lot
conditions. The items can be shipped in any lot. Same You can select any lot for shipment, but the entire
shipment must have the same lot. Specific You can only ship one specific lot.
Sales Office A department that is identified in the company business model
to manage the business partner's sales relations. The sales office is used to
identify the locations that are responsible for the organization's sales
activities. Currency The currency in which the amounts on the sales schedule are
expressed. Self-Billing If this check box is selected, self-billing is applicable. In this case, the invoice is
created by the sold-to business partner. Default value If the sales release is: - Inserted through electronic data interchange (EDI), the value of this field is defaulted from
EDI.
- Manually entered, this check box is cleared by default. You
can manually select this check box.
Cumulative Shipped Quantity The total cumulated quantity that you shipped for the sales
schedule, expressed in the inventory unit. Note If this field is filled, cumulatives are synchronized with
the cumulative data from an external component. Received CUM The total cumulated quantity that your ship-to business partner
received for the sales schedule, expressed in the inventory unit. Prior Required CUM The required cumulative that you received from your business partner, expressed in
the inventory unit. Last Receipt Quantity The quantity that your business partner received with the last
shipment for the sales schedule, expressed in the inventory unit. Last Receipt Date The last date on which your business partner received a
shipment for the sales schedule. Last ASN The number of the advance shipment notice that you sent in advance of the last shipment for the
sales schedule. Last Shipment The number of the last shipment that your business partner
received for the sales schedule. FAB Authorization Through Date The date until which the fab authorization is valid. Note This date cannot be before the current date. RAW Authorization Through Date The date until which the raw authorization is valid. Note This date cannot be before the FAB Authorization Through Date. FAB Authorization A valid authorization to start the production for a quantity of
items that is required on the sales schedule, expressed in the inventory unit. RAW Authorization A valid authorization to buy raw material that is needed to
produce a quantity of items that is required on the sales schedule, expressed
in the inventory unit. Text If this check box is selected, a text is present. 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). | |