Some basic om the attached. But basic goal is is illustrate how using SAP Hana a

Some basic om the attached. But basic goal is is illustrate how using SAP Hana and VIm at Phillips 66 we could reduce invoice issues. pay suppliers faster, and get better visibility of our transactions. But should be based on info on what i did below and expanded on to meet criteria of paper. During my time at Phillips 66 as a data analyst, many errors within the newly implemented S/4 HANA would be occurring. Some include Muli-freight PO error, LIV price discrepancies, duplicate invoices, and many more. Although these errors were the biggest issues of them all.
Why the company decided to make the switch to S/4
This paper can cover any issue or topic related to information systems, data communications, telecommunications or any topic related to the course material. The paper will:
Select a business problem or goal related to a topic covered in this course. You are free to choose a business or organization, existing or imaginary, that you find interesting, have worked for or might want to work for.
Further limit your subject to a manageable topic (e.g., don’t try to solve all of the organization’s problems, just work on a small one).
Describe or present the problem/goal in succinct specific terms. Aim for a one or two sentence statement of what you plan to accomplish.
Explain how you plan to deal with the problem/goal (your solution) using concepts discussed in this class. This is where you provide a discussion of how your topic solves the problem. The following bullet points and percentages are intended as a guideline. Different topics will require different subtopics and percentages. You will not be graded with how closely you meet these guidelines, nor is meeting the guidelines a guarantee of a good grade.
Abstract
An abstract, no more than 1 page in length – 2-3 paragraphs, covering the topic and planned paper must be submitted according to the Current Schedule. The abstract will be submitted early to help validate the topic of your paper before you write the entire thing.
Format
Any information presented about the topic should be over and above the information presented about the topic in class. The student is expected to go beyond the basic information and look deeper into any topic than it was discussed in class.
The paper should be between 1700 and 2000 words in length. This would usually be 5-6 pages in length. Excessive length will count against you, as will being too short. Appropriate drawings, pictures, maps, etc. will be expected and will not count against the excessive length limit.
There should be at least five (5) different references. Databases on the Internet can be used to locate other sources. Journals, newspapers, magazines, books, textbooks, or other appropriate materials are to be used.
guidelines for uploaded homework mpeters.pdf
apa-template-03-07-20.docx
Grading
The body of the paper should cover the following:
Percentage (estimate)
Discussion
10%
Discuss the background of the problem/goal so that the reader will understand the basic points. Include a descriiption of the industry and competitors.
10%
Present an analysis of the problem/goal.
40%
Propose a solution using your topic.
15%
Review the strengths of this solution.
10%
Make a final recommendation, note how you overcome the limitations and utilize the strengths of your solution. Include a sequenced implementation if this helps.

The paper will be grading according to the following:
Area
Descriiption
Possible Points
Abstract
Topic idea
25
Content
Topic presentation, extent of coverage, relevance to information systems, data communications and/or networking.
Length of paper (word count), format of paper.
35
References
Citation methods, number of citations and sources,
Correct citations within body of paper (plagiarism will result in a 0 or “F” on this paper)
20
Style
Grammar and spelling within paper
Punctuation and sentence structure
See “Structure” at the end of this document for more information
25
Format
Review of topic, past, present and future states, and recommendations/implications (both positive and negative)
20
SAP s/4 HANA utilizes “in memory computing architecture, which allows the ability to access real time business statistics and analytics”. This means that it converges transactional and analytical systems into one which SAP R/3 did not. S/4 is more user friendly than R/3 with the inclusion of SAP Fiori(Carter, 2023).
Multi-Freight PO Error
The Multi-freight PO error usually occurs when there are multiple transporter companies and a different vendor. This causes the automated system to list many different pricing codes within the GR/IR account instead of the vendors specific code. The way to fix this error is by replacing the multiple PO’s with a single PO from the invoice receipt, test the invoice, and then approve.
LIV Price Discrepency or, “logistics invoice verification price discrepancy” is an error which is caused by a difference in price or quantity in the document posting in comparison to the purchase order. This causes the invoice to get blocked by the system. The invoice will then go into the buyers inbox. In many instances at Phillips 66 there error was in the system but nothing was wrong with the invoice itself. But if there was an issue with the invoice, checking the invoice receipt and purchase order to verify they’re the same would fix it. As long as they match when approving the invoice.
Duplicate Invoice Errors are cause by either the system reading the excel spreadsheet wrong or human error when inputting the invoice into the spreadsheet that S/4 HANA pulls from. In the case of Philip 66, this error was almost always a glitch within the system. The way to solve this error would be to check the documents like the PO, The spreadsheet it was pulled from, as well as the invoice receipt. The invoice can also be check through S/4 itself. By copying the invoice number into the buyer inbox to see if the reference number as multiple invoices attached.