The master and reference data related to the processes for the commercial department at ArcelorMittal were often stored in an unstructured way (MS Excel, Word,...) in a Lotus Notes database for which a custom approval flow was written. In order to be able to distribute this data to the receiving systems, it was implemented in the ERP system (SAP ECC6, non-unicode).
This solution was not sufficient for the current needs and SAP MDG was choosen. Here you can read why…
Procure to pay is designed to provide organizations with control and visibility over the purchase process. It provides insights in the initial decision to make the purchase, automate and accelerate the process of selecting the goods and the transaction made to pay the goods purchased.
But even in this process it is possible to make mistakes: use faulty vendor, pricing, material data, which is inefficient and can cost a lot. Think on missing discounts because the payment terms were not available in your vendor master data. Or the example of a company merge with similar materials and vendors, which can cause duplicates and corrupt or inaccurate records.
For people who don’t know what a Hackathon is, it is a 48 hour marathon of hacking and solving actual and daily problems. In this case the subject was Mobility of the Future. The subject speaks for itself: fixing the mobility problems of today to get a better future. At the Hackathon there were four challenges to solve. We took the challenge to solve the problem around public transport and co-mobilit
In a world where master data is increasing exponentially, enterprises now more than ever need to keep master data consistent and accurate across the organization to better perform key activities. SAP’s solution that consolidates and centrally governs your master data is called SAP Master Data Governance (MDG).
We at Avelon are specialised in SAP MDG and in this blog we would like to give insight into how SAP Information Steward can increase your master data quality and its relation with SAP MDG.
Many users make use of the ability to link MS Office or PDF files to SAP documents. By default, these files are stored in the SAP database. It's very easy to save attachments to an external system, such as a SAP Content Server. As a result, the SAP database size can be significantly reduced, sometimes by 25%.
When we recently sat together during an after-work drink, we were thinking of the possibilities of IOT (internet of things) from an SAP perspective and how we as a company could get hands-on experience here and possibly create a solution which has a descent commercial viability.
This brought us to visionary ideas and great plans like completely automated drive-in-cinemas with license plate recognition, building access by means of ID readers and SAP HR data, … But that wasn’t really good enough.
On the other side, agriculture is one of the drivers for IOT. And SAP is also offering solutions in this line of business. Why not focus on that ?
For many years, SAP Business Workflow has been the standard tool for automating processes and optimizing business processes within the SAP Business Suite. This also applies to S/4 HANA. The responsible team has made several changes to the workflow runtime and development environment to be able to better respond to the new needs. Innovations have been introduced in the design of processes, the execution of tasks and the workflow engine itself. Everything revolves around simplicity and flexibility.
If parallel change request stages exist during an MDG process, the user can see the different work items by pressing the "Work Items" button. The default pop-up only shows the ID and the description of the work Item but gives no further information. For a customer of ours, we have extended this standard pop-up so that they know who the processor of the work Item is next to the status of the sub workflow.
On Thursday, January 19th, 2017 Avelon organizes together with the VNSG and SAP a workflow afternoon session. This day will be devoted to the future development of workflow and associated business benefits. It will be a varied afternoon, for both developers and business users to work with SAP workflow.
Assigning workflow tasks to more than one person creates a shared processing responsibility. A disadvantage may be that the number of tasks increases rapidly in the workflow inbox, with a lower performance of the SAP Workflow inbox as a result. An example is the often large workflow inbox of the accounts payables.
A recent SAP OSS note improves the performance of retrieving task-specific attributes within Fiori My Inbox app. The methodology described in this note also works for the SAP GUI Workflow Inbox (transaction SBWP) for professional users.
During a recent webinar on the status of the workflow customer connection program (organized by SAP product improvement) SAP reported that the coming years we can still expect many improvements around SAP Business Workflow. It was stated that SAP Business Workflow is and remains the default tool to automate (approval) procedures within the SAP Business Suite. This remains the case for S/4HANA.
Thanks to the "SAP Customer Connection for SAP NetWeaver Workflow 2015" program last year, dozens of improvements have been collected, evaluated and largely accepted by SAP. During the past months, some of these improvements have been made available via OSS notes .
At the last webinar on the status of the program it was reported that more SAP Workflow improvements can be expected. It was stated that SAP Workflow is the standard tool for automating procedures. This remains the case in S/4HANA.