Transaction codes from end user point of view

hi all,
I am expecting end user transaction codes of warehouse management.
I am familiar with materials management but looking to learn WM.
regards,
nitin patil

Hi refer bellow Tcodes,
WM                    
0.LI21  -  Clear the stock from inventory                    
1.LB01 - Create Transfer Requirement                    
2.LB02 - Change transfer requirement                    
3.LB03 - Display Transfer Requirement                    
4.LB10 - TRs for Storage Type                    
5.LB11 - TRs for Material                    
6.LB12 - TRs and Posting Change for MLEat.Doc.                    
7.LB13 - TRs for Requirement                    
8.LD10 - Clear decentralized inventory difference                    
9.LD11 - Clear differences for decentral.sys.                    
10.LI01 - Create System Inventory Record                    
11.LI02 - Change System Inventory Record                    
12.LI03 - Display System Inventory Record                    
13.LI04 - Print System Inventory Record                    
14.LI05 - Inventory History for Storage Bin                    
15.LI06 - Block Storage types for annual invent.                    
16.LI11 - Enter Inventory Count                    
17.LI12 - Change inventory count                    
18.LI13 - Display Inventory Count                    
19.LI14 - Start Inventory Recount                    
20.LI20 - Clear Inventory Differences WM                    
21.LI21 - Clear Inventory Differences in MM-IM                    
22.LL01 - Warehouse Activity Monitor                    
23.LLVS - WM Menu                    
24.LN01 - Number Ranges for Transfer Requirement                    
25.LN02 - Number Ranges for Transfer Orders                    
26.LN03 - Number Ranges for Quants                    
27.LN04 - Number Ranges for Posting Changes                    
28.LN05 - Number Ranges for Inventory                    
29.LN06 - Number Ranges for Reference Number                    
30.LN08 - Number Range Maintenance: LVS_LENUM                    
31.LP10 - Direct picking for PO                    
32.LP11 - WM staging of crate parts WM运                    
33.LP12 - Staging release order parts (WM-PP)                    
34.LP21 - WM replenishment for fixed bins WM                    
35.LP22 - Replenishment Planning for Fixed Bins                    
36.LQ01 - Transfer Posting in Invent. Mgmt                    
37.LQ02 - Transfer Posting in Invent. Mgmt                    
38.LS01 - Create Warehouse Master Record                    
39.LS02 - Change Warehouse Master Record                    
40.LS03 - Display Warehouse Master Record                    
41.LS04 - Display Empty Storage Bins                    
42.LS05 - Generate Storage Bins                    
43.LS06 - Block Storage Bins                    
44.LS07 - Block Quants                    
45.LS08 - Block Storage Bins per Aisle                    
46.LS09 - Display Material Data for Storage Type                    
47.LS11 - Change storage bins (multiple proc.)                    
48.LS12 - Block Storage type                    
49.LS22 - Change Quants                    
50.LS23 - Display Quants                    
51.LS24 - Display Quants for Material                    
52.LS25 - Display Quants per Storage Bin                    
53.LS26 - Stock of Material                    
54.LS27 - Display Quants for storage unit                    
55.LS28 - Display storage units / bin                    
56.LS32 - Change storage unit                    
57.LS33 - Display storage unit                    
58.LS41 - List of control cycles for WIP loc                    
59.LT01 - Create Transfer Order                    
60.LT02 - Create TO for Inventory Difference                    
61.LT03 - Create TO from Delivery Note                    
62.LT04 - Create TO from TR                    
63.LT05 - Process Posting Change Notice                    
64.LT06 - Create TO for Material Document                    
65.LT07 - Create TO for mixed storage unit                    
66.LT08 - Manual addition to storage unit                    
67.LT09 - ID point function for storage units                    
68.LT0A - Pre-plan storage units                    
69.LT0B - Stock Placement of Shipping Units                    
70.LT0C - Stock Removal of Shipping Units                    
71.LT0D - Stock Transfer of Shipping Units                    
72.LT0E - Create Removal TO for 2-Step Picking                    
73.LT10 - Create Transfer Order from List                    
74.LT11 - Confirm Transfer Order Item                    
75.LT12 - Confirm Transfer Order                    
76.LT13 - Confirm TO for storage unit                    
77.LT14 - Confirm preplanned TO item                    
78.LT15 - Canceling transfer order                    
79.LT16 - Canceling TO for storage unit                    
80.LT17 - Single Entry of Actual Data                    
81.LT1A - Change Transfer Order                    
82.LT21 - Display Transfer Order                    
83.LT22 - Display Transfer Order / Storage Type                    
84.LT23 - Display Transfer Orders by Numbers                    
85.LT24 - Display Transfer Order / Material                    
86.LT25 - Display Transfer Order / Reference                    
87.LT26 - Transfer orders for storage bin                    
88.LT27 - Transfer order for storage unit                    
89.LT28 - Display Transfer Order / Reference                    
90.LT31 - Print TO Manually                    
91.LT32 - Print transfer order for storageunit                    
92.LT41 - Prepare TRs for Multiple Processing                    
93.LT42 - Create TOs by Multiple Processing                    
94.LT43 - Forming groups for deliveries                    
95.LT44 - Release for Multiple Processing                    
96.LT45 - Evaluation of reference numbers                    
97.LT51 - Maintain Missing Stock                    
98.LT63 - Control: Single Entry of Actual Data                    
99.LT64 - Single Entry of Actual Data                    
100.LT72 - Determine 2-step relevance                    
101.LT73 - Display 2-step                    
102.LU01 - Create Posting Change Notice                    
103.LU02 - Change Posting Change Notice                    
104.LU03 - Display Posting Change Notice                    
105.LU04 - Selection of Posting Change Notices                    
106.LX01 - List of Empty Storage Bins                    
107.LX02 - Inventory List                    
108.LX03 - Bin Status Report                    
109.LX04 - Capacity Used                    
110.LX05 - Block Bins in Bl.Storage w .Time Limt                    
111.LX06 - Inventory List for Fire Department                    
112.LX07 - Check storage                    
113.LX08 - Accident Regulations List                    
114.LX09 - Overview of All Transfer Requirements                    
115.LX10 - Activities per Storage Type                    
116.LX11 - Overview of Documents                    
117.LX12 - Document Overview: Landscape Format                    
118.LX13 - Analysis of Differences                    
119.LX14 - Analysis of Material Transfers                    
120.LX15 - Selection of Bins for Annual Inventory                    
121.LX16 - Selection of Bins for Continuous Inventory                    
122.LX17 - List of Inventory Differences                    
123.LX18 - Statistics of Inventory Differences                    
124.LX19 - Inventory Data Takeover by Batch Inp.                    
125.LX20 - Generate interim storage bins                    
126.LX21 - Pick List for Several Transfer Order                    
127.LX22 - Process Inventory from Overview                    
128.LX23 - Stock comparison IM - WM                    
129.LX24 - Display of Hazardous Material numbers                    
130.LX25 - Inventory Status                    
131.LX26 - Inventory in WM via cycle counting                    
132.LX27 - Stock levels by shelf life expiry date                    
133.LX28 - Relevant TO item for ext.system                    
134.LX29 - Fixed bin supervision                    
135.LX30 - Overview of WM messages ext.system                    
136.LX31 - Analysis of print control tables                    
137.LX32 - Archived transfer orders                    
138.LX33 - Archived transfer requirements                    
139.LX34 - Archived posting change notices                    
140.LX35 - Archived system inventory records                    
141.LX36 - Archived inventory histories                    
142.LX37 - Linked objects                    
143.LX38 - Check Report Customizing Strategy K                    
144.LX39 - Evaluation Reference No. for 2-S.Pck                    
145.LX40 - Material Situation Prod. Storage Bin                    
146.LX41 - Bin Status Report WM/PP Interface                    
147.LX42 - Evaluation PP Order from WM View                    
148.LX43 - Consistency Check for Control Cycles MCL9                    
WM: Material Plcmt/Removal:Selection                    
149.MCLD - WM: Material flow - Selection                    
150.MCLH - WM: Movement types - selection -                    
151.OL01 - Display / change LDK34 (bins)                    
152.OL02 - Display / change RLPLA (bins)                    
153.OL03 - Display / change LDK33 (stock)                    
154.OL04 - Display / change RLBES (stock)                    
155.OL05 - Display / change LDK30 (mat.whse)                    
156.OL06 - Display / change LDK31 (mat.type)                    
157.OL07 - Data transfer stor.bins LDK34->RLPLA                    
158.OL08 - Data transfer stor.bins RLPLA->B.I.                    
159.OL09 - Data transfer stor.bins LDK34->LAGP                    
160.OL10 - Test storage bin data transfer                    
161.OL11 - Data transfer stock LDK33->RLBES                    
162.OL12 - Data transfer stock RLBES-> B.I.                    
163.OL13 - Data transfer stock LDK33->LQUA                    
164.OL14 - Test stock data transfer                    
165.OL15 - Data transfer material whse no.view                    
166.OL16 - Test mat.master data transfer (MLGN)                    
167.OL17 - Data transfer material storage type                    
168.OL18 - Test mat.master data transfer (MLGT)                    
169.OLVS C SD Menu for Master Data                    
170.VM01 - Create Hazardous Material                    
171.VM02 - Change Hazardous Material                    
172.VM03 - Display Hazardous Material                    
WM-DWM                    
Decentralized Warehouse Management                    
1.DZ00 - Introduction to Decentralized Systems                    
2.LD01 - Repost Communication Document                    
3.LD02 - Reposting multiple comm.records                    
4.LD03 - Display Communication Document                    
5.LD04 - Evaluation of Communication Doc                    
6.LD05 - Check LDK01 Records (internal call)                    
7.LD06 - Check LDK02 Records                    
8.LD07 - Check LDK03 Records                    
9.LD08 - Check LDK04 Records (internal call)                    
10.LD09 - Check LDK05 records                    
11.LN07 - Number Ranges for WM Communic.Rec.

Similar Messages

  • Responce times from end-user point of view

    Hi,
    I am looking for the way how to collect responce times from end-user point of view.
    Logging of function execution via DMS is not enogh thus we need to discover and monitor problems in all components including poor network, users terminals etc.
    Regards,
    Tomasz

    Hi,
    I am looking for the way how to collect responce times from end-user point of view.
    Logging of function execution via DMS is not enogh thus we need to discover and monitor problems in all components including poor network, users terminals etc.
    Regards,
    Tomasz

  • From the End User Point of view

    Hi,
    Suppose i have scenario like file to idoc, the file should run every day night,when any errors occur at idoc side how can end user know whether it is successfully updated at R/3 side or not. In this scenario exactly what is role of end user what will he do.
    Thanks in advance.
    Regards,
    Prem.S

    Hi Prem,
    In this case the end user/basis team/ ie basically who ever is responsible for monitoring has to go to transaction WE02/WE05 to monitor if any error has occured in posting the application document.
    if any error is there in WE02 then he can go to transaction BD87 and repost the idocs.
    Cheers,
    Sumit
    ps : reward points if that helped u.

  • Step by step Funds Management (from a user point of view)

    Hi,
    Kindly provide me the details of the steps (step by step) to be followed to upload the budget (by a user).
    Regards,
    Vikas Malhotra

    Hi Viki,
    Check out this doc
    http://www.copacustomhelp.state.pa.us/infopak/nav/budget/index.htm
    Assign points if useful
    Regards
    Genie

  • Lost message from server's point of view

    Hi All
    Following situation:
    The JMS-Provider sends a JMS-Message. The message is entirely in the wire and is still flying to the consumer. Before the message arrives to the consumer, the network connection fails, so the client does nothing know about the send message.
    From the server’s point of view the message was successfully sent but not acknowledged yet. The server waits for an acknowledge and doesn’t undertake redelivery, because the consumer session on the server is still living.
    From the consumer point of view the message was not sent so the client has nothing to ack, so we have some “deadlock”.
    The question is – how does server recognize such situation (short connection fail, deadlock) and what does it undertake to guarantee the delivery?
    Thank you.

    The JMS-Provider sends a JMS-Message. The message is entirely in the wire and is still flying to the consumer. Before the message arrives to the consumer, the network connection fails, so the client does nothing know about the send message.
    From the server’s point of view the message was successfully sent but not acknowledged yet. The server waits for an acknowledge and doesn’t undertake redelivery, because the consumer session on the server is still living.
    From the consumer point of view the message was not sent so the client has nothing to ack, so we have some “deadlock”.
    The question is – how does server recognize such situation (short connection fail, deadlock) and what does it undertake to guarantee the delivery?If the "network connection fails" whilst sending a message then the server (and probably the client) will almost certainly receive a SocketException. A message is unlikely to simply disappear on the wire without at least one end of the socket getting an exception of some kind, and if the socket is simply hanging for some reason then most JMS providers would have a means to detect this (e.g. by sending periodic packets down the wire to check it is still alive).
    But ultimately, if a persistent message is sent to a consuming client and the message is not acknowledged (or the transaction committed) then the server will eventually redeliver it. JMS doesn't define exactly when an unacknowledged message is redelivered, but it typically wouldn't happen until the consumer in question has closed.
    Nigel

  • Improving audio quality from a subscriber point of view

    Hi,
    I am building an application that requires audio chat. When the chat is happening between an Android user and a PC user, the PC user can hear clearly when the Android user speaks. However, when it is the other way around, the Android user hear distorted sound,with noises. Is there any way to improve audio received from a subscriber point of view?
    Please advice, thanks!
    Regards

    Hi Raff,
    The Android device is a Samsung Galaxy S i9000 and it is running AIR 2.6, attached below is a snippet of the code related to the audio i am using
    <mx:Button x="121" y="700" height="34" width="117" label="Audio" toggle="true" id="audioButt"
       click="(audioButt.selected) ? audioPub.publish(): audioPub.stop()" includeIn="LoggedIn"/>
    <mx:Button x="242" y="700" height="34" width="117" label="Quality" toggle="true" id="audioButt1" includeIn="LoggedIn"
       click="(audioButt.selected) ? audioPub.microphoneManager.encodeQuality = 3 : audioPub.microphoneManager.encodeQuality = 4"/>
    <rtc:AudioPublisher  id="audioPub" codec="{SoundCodec.SPEEX}" useEchoSuppression="true" silenceLevel="0"  />
    <rtc:AudioSubscriber/>
    I think the problem is related to the script I am writing,I created a button  called Quality to reduce the encodeQuality of my PC microphone, will it helps to improve the audio recieved from my Android device?Please advice, thanks!
    Regards

  • Reports User Point of View Question

    I created a report that has two grids and the databases are both essbase cubes and have the same dimension names. I am working with Hyperion Reports 9.3. I wanted to link the User Point of View, so that all the user had to do was click on:
    1. Period (ie-Apr)
    2. Company Code
    3. FiscalYear (ie-FY10)
    What the Preview User Point of View shows is a drop-down box at the top that has the user select each database connection and change the POV for these dimensions. I'd like to not do that. I'd like the User POV to only have to be selected once.
    Note: At a previous job, I am pretty sure I was able to do this without having to change the User POV for each db connection. I know there were two connections but didn't have to change the POV twice. I will provide additional details if needed.
    Thanks, T

    I'm not sure if that will work for me. I already have the 2nd grid hidden from view and there isn't an option to "pull" the POV from another grid that I can see. I even tried merge equivalent prompts in the User Preferences in Workspace but I think that is for prompts only, not user POV.

  • User Point of View

    Hi ,
    Can we give a Descriptive lable for a User point of View ?
    Suppose the name of dimesnion is Version which i have set it as user point of view . Then can i give lable / name to the same someting like " Enter Version ..." like we do for prompts.
    Thanks & Regards
    Vijaya

    Hi Vijaya,
    As far as I know, it is not possible. But if hyperion does do some change in their work space code, then it might be possible.
    It is not possible from your side.
    Regards,
    rahukl

  • Which design is best from a performance point of view?

    Hello
    I'm writing a small system that needs to track changes to certain columns on 4 different tables. I'm using triggers on those columns to write the changes to a single "change register" table, which has 12 columns. Beacuse the majority of tracked data is not shared between the tables, most of the columns will have null values. From a design point of view it is apparent that having 4 separate change register tables (one for each main table that is being tracked), would be better in terms of avoiding lots of null columns for each row, but I was trying to trade this off against having a single table to see all changes that have been made across the tracked tables.
    From a performance point of view though, will there be any real difference whether there are 4 separate tables or 1 single register table? I'm only ever going to be inserting into the register table, and then reading back from it at a later date and there won't be any indexes on it. Someone I work with suggested that there would be more overhead on the redo logs if a single table was used rather than 4 separate tables.
    Any help would be appreciated.
    David

    The volumes of data are going to be pretty small,
    maybe a couple of thousand records each day, it's an
    OLTP environment with 150 concurrent users max.Consider also the growing of data and if you'll put data constantly to an historical db or if the same tables will contain the increasing number of record.
    The point that my colleague raised was that multiple
    inserts into a single table across multiple
    transactions could cause a lot of redo contention,
    but I can't see how inserting into one table from
    multiple triggers would result in more redo
    contention that inserting into multiple tables. The
    updates that will fire the triggers are only ever
    going to be single row updates, and won't normally
    cause more than one trigger to fire within a single
    transaction. Is this a fair assumption to make?
    David
    I agree with you, the only thing I will consider, instead of redo problem, is the locking on the table that could be generated when logs of different tables will have to be put in a single table, i mean if after insert of a log record you could need to update it....
    In this case if 2 or more users have to update the same log you could have problems.

  • JMS - Useful from an international point of view?

    Hi everyone,
    I was wondering if JMS could be useful from a legislative point of view. I mean could it be useful when two companies situated in different countries communicate? Does JMS make this communication easier/better in any way?
    Hope someone is able to help me :)

    JMS is ideal for the loosely coupled communications which the integration of two different companies or governments would require. However, message oriented middleware has typically been a behind-the-firewall technology. So, while most JMS vendors support messaging over the firewall, it is not their primary focus. Web services are better suited to the type of over-the-Internet integration you are describing. The issue with this, however, is that web services lack transactional support. I think they are working on that though.

  • Remove transaction codes from multiple roles at a time

    Hello,
    how to remove transaction codes from multiple roles at at time?
    Thank you in Advance.

    Hi Vanita,
             Why do you want to remove a t-code from all the roles. Are you no longer going to use the t-code. If this is the case then you can lock the transaction code in T-code SM01 so that no one can use it. But this would effect other users as well, it should only be locked if no one should use the particular T-code.
    Another alternative is to write a program to remove the particular T-Code from the table AGR_TCODES where the relation ship between the role and t-code is stored.
    Thanks.

  • HOW TO FIND TRANSACTION CODE BASED ON uSER eXIT.

    HI FRIENDS,
    I WOULD LIKE TO KNOW HOW WE CAN FIND OUT A TRANSACTION CODE OF AN USER EXIT.
    MY USER EXIT IS : EXIT_SAPLV60B_002 .
    PLEASE LET ME KNOW .
    THANS IN ADVANCE,
    REGARDS,
    ROBERTS.K

    FUNCTION EXIT_SAPLV60B_002.
    ""Lokale Schnittstelle:
    *"  IMPORTING
    *"     VALUE(XACCIT) LIKE  ACCIT STRUCTURE  ACCIT
    *"     VALUE(VBRK) LIKE  VBRK STRUCTURE  VBRK
    *"     REFERENCE(DOC_NUMBER) LIKE  VBRK-VBELN OPTIONAL
    *"  EXPORTING
    *"     VALUE(XACCIT) LIKE  ACCIT STRUCTURE  ACCIT
    *"  TABLES
    *"      CVBRP STRUCTURE  VBRPVB OPTIONAL
    *"      CKOMV STRUCTURE  KOMV
      INCLUDE ZXVVFU02.
    ENDFUNCTION.
    Above is the interface of the function module stated by you, create the include zxvvfu02 by double clicking on it,
    put a break point in it and activate and in the debugging mode you can see that the structure XACCIT has EBELN i.e.
    purchase order no. assign it to the reqd field.

  • I want to add transaction code for one user.

    Hi abapers,
    My requirement is;
    I want to add transaction code for one user.
    EX: zsdf to kanne.
    Can any body tell me the procedure step by step.
    With regards,

    If you want to give authorisation to an user for a particular tcode, you need to first include the transaction code in an authorisation Role and then assign the authorisation role to the user id in the transaction code SUIM.
    A Basis guy will be able to help you to do this and anyway this is not the job of an ABAPer.
    Hope this helps you.
    Reward if this helps you

  • Handling Unit Information from sap mm point of view

    Hi all.
    Looking for Handling Unit Information from sap mm point of view.
    Regards.
    Parameshwar
    Note : Please search forum before posting.
    Edited by: Jeyakanthan A on Sep 22, 2011 1:20 PM

    Please refer the below links
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/LOHU/LOHU.pdf
    http://help.sap.com/bp_bblibrary/600/html/G74_BB_EN_US.htm

  • Filter in User point of view

    Hi ,
    I have set a filter Custom ( Just two values) for Version which is set as user point of view .
    I can see only two values in the FR studio for that report .
    But i have following issues.
    1) When other users/developers login with there credentials the custom filter is not getting applied . That is the other developer can see all the values.
    2) When i run the report in workspace the custom filter does not get set . It shows all the values even though in the design the Custom filter is set.
    please let me know how i can resolve the above issue and is critical for me .
    Thanks and Regards
    Vijaya

    I know what you are referring to. What you did was create a filter only for your user id and not for the report. That option in the FR Studio is very misleading, it makes it appear as if the report was limited to those 2 members. It is only for the user id of the person developing the report when you preview the report.
    What you can do is put Version in the Grid POV. There you can limit the members users will see when they run the report. Unfortunately, it's not very pretty and a bit confusing for users.

Maybe you are looking for