Shulou(Shulou.com)06/01 Report--

This article introduces SAP MM for MRKO transaction code optimization advice is what, the content is very detailed, interested friends can refer to, hope to be helpful to you.

Several optimization suggestions of SAP MM for MRKO transaction code

SAP has been upgrading SAP software systems for decades, from early R2 to R3, ECC, and now S4HANA and Cloud. In the process of upgrading, the BUG found in the early products has been repaired; some functions have been expanded, and some old functions have been abandoned; the software product family is getting larger and larger, and the functions are more and more complete, so that now the SAP software system has become a leader in enterprise management software, and its market share remains at the top. Many big companies such as the world's top 500 and China's top 500 have launched the software system, and regard the system as a strategic platform or ERP core platform, and become the management master behind the big companies.

However, the author found that in the process of upgrading the SAP system, some areas that are not easy to use in the project practice, or need to be improved, have not been optimized, but have always maintained the mode in the old version. And SAP doesn't seem to plan to optimize these features that seem to need to be optimized and improved in subsequent product upgrades.

Take the transaction code MRKO, which is familiar to the consultant of MM module, as an example. This transaction code is used to regularly create invoices based on our consumed pipeline materials and consignment inventory data in consignment procurement and pipeline procurement scenarios, so as to facilitate subsequent payment and achieve regular settlement with suppliers. The author believes that the following three points are worth doing some optimization in the future upgrading of SAP products.

The DISPLAY and SETTLE functions in 1Magna MRKO should be separated.

There are two main functions in the MRKO transaction code, one is to export the list of consignment inventory of pipeline materials or suppliers that we actually use within a specified period of time, and then talk to the supplier list, that is, the 'Display' function on the initial interface. One is to trigger the purchase invoice based on the quantity of pipeline materials we have used within a specified period of time or the consignment inventory of the supplier to form our payables, that is, the 'Settle' (settlement) function on the initial interface.

In project practice, most of the purchasing department exports the data to reconcile with the supplier, while the financial department performs the settlement function and triggers the invoice voucher. In other words, the display and settlement functions are carried out by different business departments, and the authority needs to be separated, especially the settlement function. Many enterprises stipulate that it can only be implemented by the users of the financial department, and the purchasing department cannot perform this function. However, the permission control of the SAP system can not achieve the effect of using the standard permission object to separate the 'display' from the 'settlement' function. Therefore, in the project practice, it is often necessary to create a new ZMRKO-like transaction code based on the transaction code, which shields the settlement function and opens it to the procurement department users, while the MRKO transaction code is not open to the procurement department users. In this way, the separation and control of permissions can be realized.

Will SAP be able to separate the display and settle functions in MRKO in future product upgrades and optimizations? Either divide the transaction code into two, one with only Display permissions and one with only Settle permissions, or design two different permission objects, one to execute Display and the other to execute Settle. In this way, there will be less custom development in the project practice.

2the MRKO transaction code should allow the user to enter the posting date.

In the settlement option, MRKO cannot generate invoice vouchers according to the posting date specified by the user, but can only use the current date of the server as the 'posting date' of the generated invoice. It makes sense for SAP to design this way, but in business practice, it is often hoped that the posting date is a certain date in the past for a variety of reasons. Especially at the end of the month, users should execute MRKO at the end of the month to trigger invoices to form the month's payables, fail to execute the MRKO transaction code in time, but wait until the beginning of next month to execute the transaction code, only to find that the posting date in the generated invoice can not be the past date, which will naturally bring business confusion.

Can the future upgrade of SAP products consider giving the user a chance to enter a posting date that he thinks is appropriate?

The Invoice generated by 3Magna MRKO should be able to Reverse directly with a simple transaction code.

Once the MRKO transaction code successfully triggers the invoice voucher, if the business staff finds that the data is incorrect or the operation is wrong, they find that the ordinary transaction code MR8M that cancels the invoice cannot write off the invoice voucher, but needs to write off the relevant goods, and then execute MRKO to generate a new invoice according to these sterilized material voucher numbers, which is the opposite of the previous invoice voucher. In other words, if you want to cancel the invoice vouchers triggered by MRKO, it is more complicated and manual work is relatively large.

In the future upgrading of SAP products, can we consider doing a transaction code similar to MR8M sterilization invoices, which can be used to directly write off the invoice vouchers triggered by MRKO? This facilitates the operation of business personnel, simplifies the operation steps of the system, and reduces the workload. Wouldn't it be better?

On the SAP MM for MRKO transaction code optimization advice is shared here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.