LX26 SAP TCode - Inventory in WM via cycle counting









Carry Out Inventory Using the Cycle Counting Method SAP screen

What is LX26 (Inventory in WM via cycle counting) and how is it used? Within an SAP system there are numerous transaction codes (TCode) that each serve different purposes and provide easy access to a variety of different functionality. One such TCode is LX26, which provides access to Inventory in WM via cycle counting / Carry Out Inventory Using the Cycle Counting Method SAP screen functionality within R/3 SAP (Or S/4HANA) systems, depending on your version and release level.

Below for your convenience is a few details about this tcode including any standard documentation. In-order to use this transaction within your SAP system simply enter it into the command input box located in the top left hand corner of the SAP GUI, and press enter. You can also add additional command options such /o to trigger in new window..See full list of command options available.

execute LX26 tcode

Program Name: RLINV050
Screen Number: 0000

LX26 Authorisation objects

In-order to be able to use a SAP transaction code you need to have the correct authorisations setup for your user ID. To check if you have the required level of authorisation to run this use tcode SU53 via a new session (i.e. /N). Simply execute LX26 and then execute /NSU53 immediately afterwards. A report of all authorisations checked will then be displayed...See check tcode authorisation for full details and screenshots of how to check what authorisations you are missing to use a tcode.

Object Field Value
L_TCODE TCD LX26



SAP GUI Support for tcode LX26

When a tcode is created you can select which SAP GUI it has support for from HTML, Java and the main Windows GUI you are probably most familiar with.
GUI for HTML is selected
GUI for Java is not selected
GUI for Windows is not selected

SAPGUI for HTML
LX26 includes support for the HTML web based GUI. The SAP GUI for HTML generates HTML pages for each screen of the SAP transaction so that it can be executed within a standard web browser. Please note there are technical restrictions and possible incompatibility issues with certain browsers which means some transaction functionality may not function correctly.

SAPGUI for Java
LX26 does not support the Java based GUI. The SAP GUI for Java support provides more controls than the SAP GUI for HTML, but requires a plug-in to be downloaded and installed on the users PC so is less popular than the SAP GUI for HTML.

SAPGUI for windows
LX26 does not support the Windows based GUI. Windows(WinGUI) support is the most popular option and transactions can be run under SAP GUI for Windows.



SAP Program associated with transaction LX26

For further details and documentation see program RLINV050

LX26 SPRO IMG Menu Path

Logistics->Production->KANBAN->Environment->Warehouse Management->Physical Inventory->Inventory Document->Create->Cycle counting(LX26)

Logistics->Logistics Execution->JIT Inbound->Environment->Shipment->Environment->Shipping->General->Environment->Warehouse Management->Physical Inventory->Inventory Document->Create->Cycle counting(LX26)

Logistics->Logistics Execution->JIT Inbound->Environment->Shipment->Environment->Shipping->General->Picking->Wave Picks->Environment->Warehouse Management->Physical Inventory->Inventory Document->Create->Cycle counting(LX26)

Logistics->Logistics Execution->JIT Inbound->Environment->Shipment->Environment->Shipping->General->Picking->Warehouse Management->Environment->Warehouse Management->Physical Inventory->Inventory Document->Create->Cycle counting(LX26)

Logistics->Logistics Execution->JIT Inbound->Environment->Shipment->Shipment->Shipment Costs->Environment->Shipping->Environment->Warehouse Management->Physical Inventory->Inventory Document->Create->Cycle counting(LX26)

Logistics->Logistics Execution->Internal Whse Processes->Physical Inventory->In Warehouse Management->Physical Inventory Document->Create->Cycle Counting(LX26)



Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!