In this video, I have explained the process of fetching delivery texts with Function Module READ_TEXT. As we know that the text details can’t be fetched from Table so we need to use Function Module to get the data. This logic will be helpful when you work on any custom reports or Forms or any other developments where you supposed to get this information and display on screen.
I hope it will be helpful for you. Please watch and provide your valuable feedback.
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.
You can check below link for my SAP WM Videos on YouTube. I hope it will be helpful
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: Business wants to have control in system to give error if any user tries to cancel GR document without cancelling the IR document. This will be helpful to avoid any inconsistencies between GR and IR.
Solution: We should suggest to use GR Based Invoice verification process to the business if they are not using. If they are already using GR Based IV, it will be fine. As per SAP standard system, there is a configuration where we can setup which movements can be allowed after posting Invoice Receipt for a purchase order.
For example: 122- Return to Vendor should be allowed and 102- Cancel of GR Document should not be allowed
Below configuration needs to be used to put this control. The path for configuration : SPRO- SAP Reference IMG-Materials Management-Inventory Management and Physical Inventory-Goods Receipt-For GR-Based IV, Reversal of GR Despite Invoice
Once you click on the node – For GR-Based IV, Reversal of GR Despite Invoice , below screen will be appeared. Movement types need to be maintained along with check box.
Indicates that in the case of GR Based IV, you can enter a reversal in respect of the purchase order, or a return delivery, even though the corresponding invoice for the goods receipt document has already been posted.
If RevGR desp.IR = X, it means GR cancellation/Return to Vendor can be done without cancelling IR document
If RevGR desp.IR = Blank, it means GR cancellation/Return to Vendor can’t be done without cancelling IR document
As the requirement is to test the cancellation of GR Document after posting both GR and IR for purchase order, we can consider that the GR and IR are completed for the Purchase Order. Below is the transaction to cancel the GR document without performing IR cancellation. You can observe the error message based on above configuration.
Transaction Code is MIGO. You can perform the cancellation of Material Document with Transaction Code MBST also. You can observe the error message once you click on Check or Post button
Error details are provided below for the information.
The error message will be given by the system when user tries to cancel the material document without cancelling the IR document when GR Based IV is activated in PO. Below screenshot is provided from the Purchase Order where GR Based IV flag will be available
This error can be resolved if you follow below steps
Cancel IR document with MR8M Transaction Code
Cancel GR document with MIGO-Cancellation or MBST Transaction Code
I hope this support issue document will be helpful for you. Keep learning and sharing. All the Best
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.
We can identify the list of message types which are entered manually for a Purchase order by inputting Purchase Order number in object key field along with input of X to field MANUE. It will give the details of output types which are maintained manually.
Same approach can be used for other documents like Outbound delivery, Shipment etc. If MANUE=Blank, it comes under automatically updated with output condition records
In this video, I covered few important interview questions for SAP MM freshers. I hope it will be helpful for beginners who try for opportunity as SAP MM Trained or Certified freshers. Please give your valuable comments and share if you like.