Sales Schedule Parameters (tdsls0100s500)

Use this session to maintain sales schedule parameters that determine how the sales schedules and sales schedule history operate.

Click Print to print and compare the parameter settings in the Print SLS Parameters (tdsls0400m000) session.

Note

You can only maintain the parameters for sales schedules in this session. Use the Initialize Parameters (tcmcs0295m000) session to set the default values of the parameters for the whole package.

 

Effective Date

The first day on which a record or a setting is valid. The effective date often includes the effective time.

The parameters are valid up to the effective date of a more recent parameter setting.

Description

A user-defined name that identifies the parameter setting.

Number Group for Releases
Series for Releases

The default series for sales releases that are manually specified or received by a Business Object Document (BOD).

Step Size for Sales Release lines

The interval between successive sales release lines in a sales release.

Related topics

Number Group Sales Orders / Sales Schedules
Step Size for Sales Schedule Lines

The interval between successive sales schedule lines in a sales schedule.

For example, if you enter the value 10, the numbers assigned to successive schedule lines are 10, 20, 30, and so on.

Use Contracts for Schedules

If this check box is selected, a sales schedule must have a linked sales contract. If no contract is found for the sales schedule, the schedule cannot be created.

Consequently:

  • Logistic agreements, which are required for schedules, are retrieved from the Sales Contract Line Logistic Data (tdsls3102m000) session.
  • Contracts are linked at sales schedule header level.
  • Prices and discounts, which are always retrieved from the contract, are stored at schedule line level. You can only update prices and discounts on the contract and not on the schedule line.
  • The Redetermine Price and Discounts at Shipment check box is enabled in the Sales Contract Lines (tdsls3501m000) session.
  • For approved sales schedules, planned warehouse orders are automatically generated or updated.

If this check box is cleared, it is not mandatory for a sales schedule to have a linked contract.

Consequently:

  • Logistic agreements for schedules are retrieved from the Items - Sales Business Partner (tdisa0510m000) session.
  • If contracts are linked to schedules, they are linked at sales schedule line level. These linked contracts are only used to retrieve prices and discounts.
  • Prices and discounts can be manually changed at schedule line level. If the schedule has a linked contract, it is unlinked.

Performance aspects

The setting of this field could affect system performance and database growth. For more information, refer to Planned warehouse orders for sales schedules.

Use Customer Item Code in Contract Search for Schedules

If this check box is selected, Infor LN considers the Customer Item Code to identify a contract for a sales schedule.

Note
  • This field is enabled only if the Use Contracts for Schedules check box is selected.
  • You can clear this check box only if:
    • This check box is cleared for all the sales offices in the Sales Offices (tdsls0512m000) session.
    • Duplicate contract lines are not created.
Use Terms and Conditions for Schedules

If this check box is selected, a sales schedule must have a linked terms and conditions agreement. If no (active) terms and conditions agreement is found for the sales schedule, the schedule cannot be created.

Note

You can select this check box only if the Use Contracts for Schedules check box is also selected in this session.

Use the Schedule Terms and Conditions (tctrm1131m000) session to specify schedule terms and conditions for a terms and conditions agreement.

Use Customer Order for Schedules

If this check box is selected, customer order numbers of incoming sales releases are compared with customer order numbers of sales contract lines and sales schedules.

If this check box is selected, the following are applicable:

  • You must define the process to manage deviating customer order numbers.

    Therefore, in the Sales Contract Lines (tdsls3501m000) session, specify the required information for the following fields:

  • If the Action on Deviating Customer Order is set to Block in the Sales Contract Lines (tdsls3501m000) session, each sales schedule has a unique Customer Order. Therefore, sales schedule revisions are sent and cumulatives are registered for the same customer order number.
  • If the Action on Deviating Customer Order is set to Continue with Sales Release or Continue with Sales Contract, the revisions for a specific sales schedule can have different customer order numbers. Consequently, the cumulatives are not registered by customer order number, but by schedule.
Note

You can select this check box only if the Use Contracts for Schedules check box is selected.

Use Customer Contract Reference for Schedules

If this check box is selected, the customer contract reference is used to identify a sales contract line and sales schedule.

Consequently:

  • The Customer Contract Reference field is available in various sales release-, sales contract-, and sales schedule-sessions.
  • Each customer contract reference requires a contract line, schedule, and CUMs. Consequently, sales schedule revisions are sent and cumulatives are registered for the same customer contract reference.

Regardless of this parameter setting, the customer contract reference must be identical for the sales release, sales contract line, and sales schedule. This can also mean a blank customer contract reference for all documents.

Note
  • You can select this check box, only if the Use Contracts for Schedules check box is also selected.
  • To use customer contract references for information purposes only, specify the reference in an additional information field on the sales release line and not in the Customer Contract Reference field. Consequently, LN searches for sales contract lines and sales schedules with a blank customer contract reference. The reference is not used to identify a sales contract line and sales schedule.
Link Consumption Invoice Lines To

The method to link consumption invoice lines in the sales schedule procedure.

Note

Performance aspects

This parameter affects the number of invoice lines that are sent to a customer.

Delete Sales Release when Sales Schedule is Deleted

If this check box is selected, and if a sales schedule is deleted, the related sales release is also deleted.

Note

You can also delete sales releases in the Archive and Delete Sales Releases (tdsls3209m000) session.

Related topics

Sales Release Archiving Implemented

If this check box is selected, sales releases can be archived to an archive company.

You can archive sales releases in the Archive and Delete Sales Releases (tdsls3209m000) session.

Sales Schedule Archiving Implemented

If this check box is selected, sales schedules can be archived to an archive company.

You can archive sales schedules in the Archive and Delete Sales Schedules (tdsls3224m000) session.

Log Schedule History

If this check box is selected, history must be logged for sales schedules.

If this check box is selected, schedule history is logged in various sessions, such as:

  • Sales Schedule History (tdsls3560m000)
  • Sales Schedule Line History (tdsls3561m000)
  • Sales Schedule Actual Delivery Line History (tdsls3557m000)
Important!
  • In the Sales Schedule Actual Delivery Line History (tdsls3557m000) session, turnover history is logged for processed delivery lines. If the Log Actual Schedule Delivery History check box is also selected in the current session, history for unprocessed delivery lines is also logged in the Sales Schedule Actual Delivery Line History (tdsls3557m000) session.
  • Schedule history is not only used for future analysis, but also for reconciliation, retrobilling, and statistics. These processes require both (un)processed sales schedule actual delivery line history from the Sales Schedule Actual Delivery Line History (tdsls3557m000) session and sales schedule line history from the Sales Schedule Line History (tdsls3561m000) session.
  • To always use the same parameter history setting for a specific sales schedule, the current parameter setting is defaulted to the Log Schedule History field in the Sales Schedules (tdsls3111m000) session at the moment the sales schedule is created. During the life cycle of the sales schedule, this field cannot be changed.

Performance aspects

The setting of this field could affect system performance and database growth. For more information, refer to Log history data.

Level of Order Intake History Logging

Specify which sales schedule history must be logged for intake transactions.

Note

If this parameter is set to Last and you want to update the statistics, you need information to reverse the previous statistics. Therefore, after the Processed in Statistics check box is selected in the Sales Order Line History (tdsls4551m000) session, all intake transactions will be logged as history records.

Performance aspects

The setting of this field could affect system performance and database growth. For more information, refer to Log history data.

Log Actual Schedule Delivery History

If this check box is selected, in addition to the schedule turnover history, history for unprocessed delivery lines is also logged in the Sales Schedule Actual Delivery Line History (tdsls3557m000) session.

If this check box is cleared, only (turnover) history for processed delivery lines is logged in the Sales Schedule Actual Delivery Line History (tdsls3557m000) session.

Note
Important!

Schedule history is not only used for future analysis, but also for reconciliation, retrobilling, and statistics. These processes require both (un)processed sales schedule actual delivery line history from the Sales Schedule Actual Delivery Line History (tdsls3557m000) session and sales schedule line history from the Sales Schedule Line History (tdsls3561m000) session.

Performance aspects

The setting of this field could affect system performance and database growth. For more information, refer to Log history data.