Sap MM Tickets
Sap MM Tickets
Sap MM Tickets
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.
Configuration:
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.
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
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
This configuration setting will be helpful to stop the creation of both Purchase Requisition and
Purchase Order with reference to expired Contract document.
ISSUES IS ABOUT ERS, WHEN I WANT AUTOMATICALLY CREATE ERS IN MRRL, THE
ERROR IS SHOWING THAT “BASELINE DATE FOR PAYMENT DOES NOT EXIST “.