LX39 - Evaluation Reference No. for 2-S.Pck

SAP Transaction Code - Details

• Transaction Code: LX39

  Description: Evaluation Reference No. for 2-S.Pck

  Release: S/4HANA and ECC 6

  Menu Path:

  • Logistics > Sales and Distribution > Shipping and Transportation > Picking > Wave Picks > Two-Step Picking > Analysis
  • Logistics > Logistics Execution > Outbound Process > Goods Issue for Outbound Delivery > Picking > Wave Picks > Two-Step Picking > Analysis
  • Logistics > Logistics Execution > Outbound Process > Goods Issue for Other Transactions > Picking > Group of Transfer Requirements > Two-Step Picking > Analysis
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Shipment > Shipment Costs > Environment > Shipping > Picking > Warehouse Management > Transfer Order > 2-step Picking > Analysis > 2-step Procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Shipment > Shipment Costs > Environment > Shipping > Picking > Wave Picks > Subsequent Functions > 2-step Picking > Analysis > 2-step Procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Shipment > Shipment Costs > Environment > Shipping > Environment > Warehouse Management > TransOrder > 2-Step Picking > Analysis > 2-step procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Environment > Shipping > General > Picking > Warehouse Management > Transfer Order > 2-step Picking > Analysis > 2-step Procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Environment > Shipping > General > Picking > Warehouse Management > Environment > Warehouse Management > TransOrder > 2-Step Picking > Analysis > 2-step procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Environment > Shipping > General > Picking > Wave Picks > Subsequent Functions > 2-step Picking > Analysis > 2-step Procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Environment > Shipping > General > Picking > Wave Picks > Environment > Warehouse Management > TransOrder > 2-Step Picking > Analysis > 2-step procedure
  • Logistics > Logistics Execution > JIT Inbound > Environment > Shipment > Environment > Shipping > General > Environment > Warehouse Management > TransOrder > 2-Step Picking > Analysis > 2-step procedure
  • Logistics > Logistics Execution > Information System > Warehouse > Collective Processing > Analysis of 2-Step Procedure
  • Logistics > Production > Kanban > Environment > Warehouse Management > TransOrder > 2-Step Picking > Analysis > 2-step procedure
  • Logistics > Customer Service > Service Processing > Order > Customer Repair > Shipping > Picking > Wave Picks > Two-Step Picking > Analysis

• • Program: RL2STK00

    Screen: 1000

    Authorization Object:

  • Development Package: LVS

    Package Description: Application development Warehouse Management (WM)

    Parent Package: APPL

  • Module/Component: LE-WM

    Description: Warehouse Management

AnswerBot

• SAP Tcode: LX39 - Evaluation Reference No. for 2-S.Pck

  g.
  
  Overview:
  The SAP transaction code LX39 is used to evaluate the reference number for a two-step package. This code is used to assign a reference number to a two-step package, which is then used to track the package throughout its life cycle. 
  
  Functionality: 
  The LX39 transaction code allows users to assign a reference number to a two-step package. This reference number is then used to track the package throughout its life cycle. The reference number can be used to identify the package, as well as to track its progress and status. 
  
  Step-by-Step How to Use 
  To use the LX39 transaction code, users must first enter the two-step package number in the “Package Number” field. Then, they must enter the reference number in the “Reference Number” field. Finally, they must click “Save” to save the reference number and complete the process. 
  
  Other Recommendations: 
  It is important to note that the reference number assigned by LX39 should be unique and should not be reused for other packages. Additionally, users should ensure that they are entering the correct reference number for each package, as this will help ensure that packages are tracked accurately throughout their life cycle.