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.
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 The default number group for all sales 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. Number Group Sales Orders / Sales Schedules The number group for 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:
If this check box is cleared, it is not mandatory for a sales schedule to have a linked contract. Consequently:
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 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:
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:
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
Link Consumption Invoice Lines To The method to link consumption invoice lines in the sales schedule
procedure. Note
Allowed values 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. 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:
Important!
Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Log history data. Level of Intake 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. Allowed values 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.
| |||