I came with a concept which will be helpful for all SAP Functional consultants. I hope you will like the video. I am also providing the the document link with this video. Watch and share with your friends.
You can download the document which is used in Video with below link.
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.
I made video to check the roles details and basic usage of SUIM during authorization related queries. I hope it will be helpful for a functional consultant to get basic knowledge to use SUIM Transaction Code.
Watch and learn. Share the video if you like
If you need my whole SAP MM Videos, you can register in below link
Above error is occurred when the service entry sheet is released for a Service Purchase Order. The reason is the Service Purchase Order contains Planned Delivery Costs. Below are the reasons from SAP Standard to stop Service Entry Sheet.
planned delivery costs are generally not supported in
External Services Management and for blanket purchase orders, item category D
In the business function “LOG_MM_MAA_1”, it is possible to process service purchase order items with multiple account assignment and valuated goods receipts only without planned delivery costs. The design of this business function does not allow planned delivery costs for MAA service purchase order items. When posting the goods receipt for MAA purchase order items, the system checks the data to be posted for consistency. If this data is not consistent, the posting of the goods receipt terminates with error message M7 599. This message should prevent data inconsistencies.
For all movement types (e.g. 101), for which label printing is desired, you must maintain movement-type-dependent field selection. You will find this Customizing under: Materials Management –> Inventory Management and Physical Inventory –> Settings for Enjoy Transactions –> Settings for Goods Movements (MIGO) –> Field Selection per Movement Type
Include the field WEANZ as an optional or mandatory entry field for the desired movement types. You can add with New Entries
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.
Generally the requirement to convert the status of IDoc would come in our regular work. Mainly we get the requirement from business to change the status to 68- Error-No further process. Generally IDocs which are not useful and which doesn’t need to be reprocessed will be changed to the status 68.
In this document, I am providing you to convert the status of IDoc with screen shots.
IDoc Status before running the program
The status of IDoc is 51 and it is shown in below screen
2.The program RC1_IDOC_SET_STATUS is used to convert the status. Program can be executed with T Code SA38 or SE38
Once you execute the program, below screen will be appeared. Input the IDoc numbers which need to be converted and also the current status and new status.
Test run option is also available before the actual run
After clicking on execute button, below successful message will be observed. It will indicate the successful conversion
Now you can see the new status 68 for the IDoc.
I hope the document is helpful for you.
Follow the blog for new updates and share with your friends to make it useful to many people. Use Online shopping links in my blog whenever you shop in Flipkart, Amazon etc.
Requirement: Business has the requirement to get the list of Accounting documents against respective Material document(s). As we aware that whenever a Goods movement happens, a material document and accounting document will be generated automatically.
In this document, I have explained the process of getting Accounting documents from Material documents with screen shots.
Important Table and Fields which are used in this document
Table – BKPF – Accounting Document Header
Input Fields – AWTYP– Reference Transaction. As we are giving Material document as input, reference transaction has to be given as MKPF (This field is an optional. You can pass only AWKEY to get the output because AWTYP will vary among the transactions)
AWKEY – Reference Key. Reference key has to be given the combination of Material document+Material document Year ( MBLNR+MJAHR). While givin the material document, you have to give the total number length (here it is 10)
Important Output field: BELNR- Accounting Document Number
Thanks for reading. I hope this document is helpful for you. Share the Blog with your friends in social network.