Stop memorizing SAP transaction codes.

Type the code and the number, like VA03 123456 or MM03 4711. Looking Glass builds SAP's skip-first-screen command, *MM03 RMMG1-MATNR=4711, and opens it in the browser through WebGUI or in SAP GUI on Windows. Some transactions take several values: FB03 1000000123 fills the document, and your default company code and this year fill the other two. You can name them too, FB03 1000000123 2000 2025. The number is one clean value, so it can never add a second field or a command.

Built in: VA02, VA03, VL02N, VL03N, VF03, MM02, MM03, CO03, SU01, SE16N, FB02, FB03, FB08 and MIR4. For any other transaction, you add one line saying which screen field takes the number. SAP shows it under F1, Technical Information. That is how a 100,000-code company list gains number entry, one frequently used transaction at a time. The built-in field names come from SAP's standard first screens and are confirmed on your system in the first week of a pilot.

Not to read or write data. It opens destinations your team has approved. For a transaction with a known number field it opens SAP WebGUI on your launchpad's host, or SAP GUI on Windows through SAP's own sapshcut tool, with the number already in the first screen. It never sends a password and never presses Save. Reading records through authorized interfaces is planned, not built.

Yes. You list your systems once, each with its system ID, client and launchpad address. With two or more listed, nothing opens until you pick one, Production is never the default, and the system shows beside every result and on every confirmation. Switch by typing @. Each system uses its own launchpad address, and the Production block follows the system you chose.

Partly. Each system can state whether it runs ECC or S/4HANA. A transaction that carries a release tag is then marked when it doesn't fit, for example "Replaced: use BP", and ranked below the ones that do. It still appears, so someone typing an old code lands on the answer instead of a dead end. Every result also says whether it runs as a Fiori app or in SAP GUI. The tags it ships with cover only cases SAP documents, such as customer and vendor master moving to the Business Partner. SAP publishes no single complete list, so your own list and your process owner remain the source of truth.

Yes to both. Anyone can add the words their team really uses to any transaction ("stuck shipment", "GRN status"), and those words then find it. They only widen the search and never change a transaction's risk label or what it asks before opening. Anyone can also report a result as wrong, out of date, or missing, with a short note. Reports are saved on that person's computer, and whoever looks after the list can read them in the administrator view and export them as a spreadsheet. A report never changes the results by itself.

Not today. Matching is a rules-based engine that runs offline, so every result can explain itself. An AI layer may be added later to improve ranking. If it is, it will only suggest. Your registry and launch rules would still decide what may run.

On two sets of requests we wrote and never tuned on, the right transaction was in the top three results for about 92 to 94 in 100 requests, and first for about 75 to 77 in 100. We wrote the requests ourselves, so treat them as a guide, and your own list will tell you more. It misses when a request uses an idea nobody wrote down. Importing your list and the learning feature raise it for your team, and the admin view collects the searches that found nothing.

We wrote them for Looking Glass. They are not SAP documentation and are not checked against your system, and the product labels them that way. Your own imported list takes priority over them.

It does not connect to SAP to read or write data. Its number entry, its switching between systems, its release marking, and its optional direct SAP GUI launch are tested against stand-ins, not yet a real SAP system or a real SAP GUI. A Windows installer is built but untested on a real Windows PC, so pilots start on Macs. Installers are not yet signed, so your IT team may need to allow them. Guided processes and knowledge cards exist in the app but are off for the pilot. Search words and reports stay on each person's computer, and sharing them across a team is by exporting and importing files, with no central console yet.

6 to 8 weeks, with up to 10 people on one team. The first week is setup, the next weeks are real use with a weekly check-in, and the last week is a review of the results.

An export of your SAP transaction list, one team of up to 10 people with someone who can confirm the transactions and field names, your SAP launchpad address so WebGUI can fill in numbers, about an hour a week, and your IT team's permission to install the app.

We agree the measures with you first: how long about 10 typical tasks take before and during the pilot, the searches that found nothing, a short survey, and the setup effort. The app does not yet count repeat use, so that is observed in check-ins rather than reported as a number.

You decide. If you continue, your $2,500 is credited toward the first year of a Team or Department plan, as long as you sign within 30 days of the review. If you stop, nothing renews and you keep the written review.

No. Searching, learning and your saved progress all happen on your computer. There is no account and no cloud service in the product.

A paid pilot at $2,500 flat, then an annual plan per team: $4,800 a year for up to 25 seats, or $14,400 a year for up to 100. The first few customers get a design-partner rate. Everything is billed annually in advance by invoice, net 30, and prices exclude tax.

Yes. Plans are sold by signed order form and invoice, so purchase orders and your usual payment process work.

No. Looking Glass is an independent product made by Camden Burke. It is not affiliated with, endorsed by, or sponsored by SAP.