LAS4 - Change Sequence Sched. Interactively

SAP Transaction Code - Details

• Transaction Code: LAS4

  Description: Change Sequence Sched. Interactively

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Logistics Execution > JIT Inbound > Environment > Repetitive Manufacturing > Planning > Change Sequence Schedule Interactively
  • Logistics > Production > Repetitive Manufacturing > Planning > Change Sequence Schedule Interactively
  • Logistics > Production > Kanban > Environment > Repetitive Manufacturing > Planning > Change Sequence Schedule Interactively

• • Program: SAPLSP00

    Screen: 100

    Authorization Object:

  • Development Package: LASP

    Package Description: Application Development R/3 Logistics Automotive Sequencing

    Parent Package: APPL

  • Module/Component: PP-FLW-SEQ

    Description: Sequencing

AnswerBot

• SAP Tcode: LAS4 - Change Sequence Sched. Interactively

  
  Overview:
  The SAP transaction code LAS4 is used to change the sequence scheduling interactively. This transaction code is used to change the sequence scheduling of a particular job in the SAP system. It allows users to modify the sequence scheduling of a job without having to go through the entire process of creating a new job. 
  
  Functionality: 
  The LAS4 transaction code allows users to modify the sequence scheduling of a job in the SAP system. This includes changing the start time, end time, and other parameters associated with the job. The transaction code also allows users to view and edit existing sequence schedules. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code LAS4 in the command field. 
  2. Select the job you want to modify from the list of jobs displayed. 
  3. Select the “Change Sequence Scheduling” option from the menu. 
  4. Enter the new start time, end time, and other parameters associated with the job. 
  5. Click “Save” to save your changes. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the options available in this transaction code before making any changes to a job’s sequence scheduling. Additionally, it is important to ensure that all changes are properly tested before they are implemented in production environments.