I hope you are doing good. In this video, I explained below concepts. I hope it will be definitely helpful for your learning
LT01 is a Transaction code which is used to transfer stock from one storage bin to other storage bin. We can transfer one Material only. This Transaction can also be used to move partial quantity of a Pallet to other Storage Bin
Transfer Order Creation with T Code LT01
Transfer Order Confirmation with T Code LT12
Transfer Order Creation with FM- L_TO_CREATE_SINGLE with sub functionalities like TO Creation by passing Source and Destination Storage Bin details/TO Creation without inputting the Storage Bin details/TO Creation without immediate confirmation/TO Creation with Immediate confirmation
You can click below link and register if you need my whole SAP MM Videos
I hope you are doing good. As part of new strategy of Interview videos, I came up with one more video on SAP WM. In these videos, one interview question will be explained with answer along with respective live screen sharing in SAP. I hope this video will also be helpful for your learning.
Thanks for watching. Provide your valuable feedback and follow my blog for future updates.
Purchase Requisition is an internal purchasing document and Purchase order is an external purchasing document which will be shared with Vendor to get the ordered materials. We can get the Purchase Order details which are created with reference to respective purchase requisition by using below logic. The PO creation date and time details can be taken by following below two steps
Step 1: Pass Purchase Requisition (BANFN) in EBAN table and get Purchase Order (EBELN). Below screenshots are provided to understand the input data and output data. Transaction code which is used for below screenshots is SE16N
Input Screen is provided below where the Table and Purchase Requisition field are highlighted
Output Screen is provided below where the Purchase order field is highlighted
Step 2: Pass above Purchase Order Number (EBAN-EBELN) as OBJECTID , Application object Change id (CHANGE_IND) = I in CDHDR table and get the PO Creation Date (UDATE) and time (UTIME) as shown below
Input data is provided below by highlighting the Table and input fields
Output data is provided below where the required fields Date and Time are highlighted
We can use this logic when you get the requirement to fetch PO creation date and time for any custom report and smart forms. I hope this document is helpful for you. Thanks for viewing the document. Please provide your valuable feedback and share with your network.
Answer: We can block a Storage Bin with Transaction Code LS02N- Change Storage Bin or Transaction Code LS06- Block/Unblock Several Storage Bins simultaneously. We use LS06 when we want to block multiple bins at a time based on business requirement. In this document, I have explained the process of Blocking Storage Bin for Stock Removal along with testing document which will be helpful to understand the requirement.
Generally business use this functionality when they want to block specific Storage Bins due to maintenance activities or repairing work or temporarily no use or blocked the stock for specific business purposes. Based on business requirement, we will create multiple reasons in configuration.
1.Master Data Change:
Updating Stock Removal indicator and Reason for a Storage Bin with LS02N Transaction Code. We can configure multiple Blocking Reasons based on business requirement which will be assigned during the process of blocking.
Once you flag the stock removal check box and input the suitable reason for blocking, you need save.
Once you click on save, system will give below successful message.
You can display the Storage Bin with Transaction Code LS03N where the blocking reason and block indicator can be seen. You can find below screen where I highlighted the key fields
We have completed the blocking of Stock Removal for the Storage Bin A-0-1. Now we will do the testing to understand the use of blocking and how does it help business to stop picking or stock removal from specific Storage Bin
As part of testing, I have taken a Storage Unit which belongs to the Storage Bin A-0-1. Now we will try to transfer the Storage Unit to other storage Bin. You can get the list of Storage units of the bin from standard SAP Reports like LX02/LX03
Display Storage Unit- T Code – LS27
Input Storage Unit and click enter to get the Storage Unit details. You can observe the storage type and bin on the screen.
Now we will test the process of creating Transfer order to move the Storage Unit 1000000036 from A-0-1 to any available storage bin to check the system behavior.
Create Transfer Order with Storage Unit: T Code- LT09
Go to the Transaction Code LT09 and input Storage Unit which needs to be moved along with movement type 999 as shown in below screenshot. After inputting the details, you need to click enter.
Once you click enter, system shows below screen. Check the source details like Plant, Storage Location, Storage Type and Bin etc. Then click on Create Transfer Order. If you want to transfer to specific storage bin, you can input otherwise system will fetch destination storage bin details based on Putaway Strategies.
Once you click on Create Transfer Order, system gives below error message as the source storage bin A-0-1 is blocked for stock removal.
I hope this document is helpful to understand the business requirement and respective solution. Until you unblock the storage bin, system won’t allow to remove/pick any stock from that storage bin.
Thanks for viewing the document. You can share with your network if you like the document and explanation.
Answer: Latest GR date field in Purchase Order item is useful to control the late Goods Receipts. Based on business requirement, this can be used to provide as information to the user who performs Goods Receipt or else to stop GR which happens after the Latest GR date of PO. Generally, business uses this field for information purpose but not to stop GR.
Business can use this field as information or as control to stop GR for the Purchase Orders.
Ex: Delivery date of a PO item is 03.03.2019 and the Latest GR date is maintained as 12.03.2019. And make the message M7163 as E (Error) so system won’t allow any Goods Receipt after 12.03.2019. Similar approach can be used to prompt as information by keeping message M7163 as W (Warning)
Below is the explanation from SAP about the field Latest GR date. I have provided the screenshot from Purchase Order for your reference
Latest Possible Goods Receipt
This is the latest acceptable date for goods receipt (GR).
If goods are received after this date, you will receive either a warning message or an error message, depending on the system setting. If you receive an error message, you will not be able to post the GR.
Below screenshot shows the Warning message which will be prompted by the system during Goods Receipt
I hope this document is useful for you. Provide your valuable feedback.
Requirement: Based on business requirement, system shouldn’t allow users to create Purchase Order with reference to Contract (outline agreement) which is already expired.
Solution: This requirement can be fulfilled by changing the warning message to Error message about contract expiry message number :06041. But, we should clearly inform users about the impact once the message is changed to Error. After the message is changed to Error, purchase order can’t be created with the expired contract.
Before going to the solution of changing the message type, we will see the message during Purchase Order creation
Below is the contract header screen which is expired. This contract will be used to create the Purchase Order. We can see in below screen that the contract validity End is 31.01.2018
Below screen shows the Warning message related to contract expiry but it won’t stop the creation of Purchase Order although it gives warning. So, it will be like an information to the user who is creating Purchase Order. User can ignore the warning message and proceed with PO creation
Message details are provided below
Based on business requirement, the solution is decided to change the message from Warning to Error (E). The configuration path to make these changes is
SPRO-IMG Reference-Material Management-Purchasing-Environment Data-Define Attributes of System Messages-System messages
This configuration setting will be helpful to stop the creation of both Purchase Requisition and Purchase Order with reference to expired Contract document.
I hope this support issue is helpful for your learning. Go through my documents/videos and provide your valuable feedback.