Skip to main content

Navigation in Scopevisio using procurement as an example

How to navigate in Scopevisio procurement: menu bar, process bar, worklist and forms in the Scopevisio Client.

With the menu bar, process bar and worklist, you move through procurement in the Scopevisio Client and process procurement transactions. You open procurement in the Scopevisio Client in the ribbon under Procurement. This article shows the navigation using procurement as an example. The structure is similar for other areas.

Prerequisites for working in procurement

To navigate in procurement in the Scopevisio Client, you need the following:

  • The Procurement module is included in the license scope

  • You have the necessary access rights to use the procurement functions

  • You have an active Internet connection and a valid Scopevisio user account

Structure of the user interface in Scopevisio procurement

The user interface of procurement in the Scopevisio Client consists of six levels:

  1. Main navigation (horizontal, at the top): The tabs Organization → Documents → Sales → Finance → Procurement → Personal. This is the top level. Here you select the business area.

  2. Ribbon/toolbar (below it): Context-dependent functions such as Teamwork, contacts, calendar, tasks, time tracking, products and more. They change depending on the selected main area.

  3. Tab navigation (workspace): The grey tabs such as Scopevisio Start, Orders, Order control and Goods receipts are your open workspaces, similar to browser tabs.

  4. Process breadcrumb (yellow/orange): The horizontal workflow Aufträge → Order proposals → Orders → Goods receipts → Returns → Incoming invoices → Zahlungen. It shows you where you currently are in the procurement process.

  5. Filter/list area: On the left the filter options (worklist, Lieferstatus, Zeitraum), on the right the data table.

  6. Assistant system: Step-by-step configuration with horizontal tabs: Assistent → Gesellschaft → Benutzer → Betriebsdaten → and more.

In short, you work like this: select the area, select the process step, filter, work.

Use the menu bar and process bar in procurement

After you open procurement, Scopevisio shows a menu bar with buttons. You use it to enter the various sub-areas of procurement.

Below it is the process bar. It is divided into individual segments. When you move the mouse pointer over a segment (mouseover), Scopevisio shows the number of documents contained and the totals of the respective values. This gives you a quick overview of the current processing status of the procurement transactions.

Find requirement request, order enquiries and deliveries in the ribbon

The following paths lead in the Scopevisio Client in the ribbon to these areas of procurement:

  • Requirement request: In the fixed area on the left of the ribbon (next to Zeiterfassung and Reisen/Spesen), select Bedarfsanforderungen → Bedarfsanforderungen

  • Deliveries for a requirement request: Bedarfsanforderungen → Lieferungen (Bedarfsanforderung)

  • Order enquiries: Procurement → Bestellanfragen. The entry is located between Order proposals and Orders

The current names are "requirement request" and "order control". "Bedarfsmeldung" (until April 2025) and "Anforderungssteuerung" (until February 2024) are former names of the same areas.

Operate the worklist in procurement

Via a button in the menu bar, you open a new page with an overview of all forms that correspond to the respective call. This overview is called the worklist in Scopevisio.

The following functions are available in the worklist:

  • Filter options: At header level, you set general filters. You also define filters at column level to narrow down the view further.

  • Column arrangement: You rearrange columns by clicking in the top row. Via the context menu, you hide columns or show additional columns.

  • Customised views: You save the customised display as a worklist. This way you prepare different views for different questions.

Commands at the bottom of the worklist

The central commands are located at the bottom of the worklist (from left to right):

  • Add: Opens a new view for entering a single form

  • Edit: Opens the selected form from the overview in the single view

  • Delete/Remove: Removes the selected form from the overview

Structure of a form in procurement

Each form in procurement has a similar structure:

  • Addressee: Selection from the existing contacts

  • Date fields: Can be pre-filled or adjusted manually

  • Items: With the Add button (bottom left), you add products from product management. With Remove, you delete a product line completely.

  • Save: At the bottom right are the functions Save, Temporary save or Save current entries

  • Process progress: To the left of the save functions is the Transfer to (next step) button. It completes the current process step and transfers all information to the subsequent transaction.

You can also see the relationship between the forms from the predecessor and successor forms shown at the top right or in the middle. This keeps the process flow traceable.

Further support for navigation in Scopevisio

You can find further information on operation and on the modules in the Scopevisio online help. If your question remains open, ask in the chat for a handover to the support team.

Related articles about navigation in procurement

Background: Why a standard ERP system moves your company forward

This section explains why Scopevisio, as a standard ERP system (ERP: Enterprise Resource Planning, software for planning and controlling company resources), is built on uniform processes. It does not describe an operating procedure.

Your success does not lie in individual processes, but in what you achieve with them. A standard ERP system helps you focus on your customers, your products and your innovation instead of self-built administration systems.

Why does a standard ERP bring proven processes?

A standard ERP system is not "off the peg", but maps best practice.

This gives you:

  • Processes that have proven themselves in practice

  • Collected experience in one solution

  • Further development by the manufacturer

This is what you avoid:

  • Reinventing the wheel

  • Mistakes that others have already made

  • Dependence on individual developers or consultants

Your accounting, your purchasing and your warehouse management are generally not your competitive advantage. That is why it is worth not building them yourself.

Why do uniform processes make you fast and flexible?

The more standardised your processes are, the easier they are to expand and hand over.

Scalability:

  • New location: You use the same standard

  • More employees: You train them in familiar processes

  • New markets: The system is prepared for it

Changeover and cover:

  • Employees can take over tasks because processes are clear

  • In case of vacation, illness or change of employees, the process remains traceable

  • Knowledge is in the system, not only in the heads of individual people

Transparency and control:

  • You see what is happening in your company

  • Bottlenecks become visible

  • You decide on the basis of data

Why value creation instead of administration?

The decisive question is: What do you earn your money with? Generally not with individual order processing, special posting procedures or self-maintained Excel lists, but with products, service, innovation and customer relationships.

A standard ERP system helps you reduce administrative effort. The result:

  • Your employees work more on value creation and less on administration

  • Your time belongs to customers and markets, not to internal coordination

  • Your energy flows into innovation, not into IT projects

Background: Why it is worth working on your processes

This section explains why process work is part of introducing a standard ERP system. Process work is not an end in itself, but an investment in your future. If your processes are not efficient, they cost money every day.

What does process optimisation mean?

Eliminate waste:

  • Stop double entries

  • Remove media breaks

  • Abolish unnecessary approval loops

  • Gain time for value creation

Create clarity:

  • Who does what, when and how?

  • No grey areas

  • No "We have always done it this way"

  • Responsibility becomes visible

Establish measurability:

  • What does a process cost?

  • Where are the bottlenecks?

  • What works well, what does not?

  • Continuous improvement becomes possible

Achieve independence:

  • Less dependence on individual people who know their way around

  • Vacation and illness are easier to bridge

  • Growth becomes plannable

How are standard ERP and process work connected?

A standard ERP system makes visible where your processes are inefficient. There are three typical reactions to this insight:

  • Rejection: "The system does not suit us, we need customisations!" Possible consequence: long customisation and high costs.

  • Ignorance: "We will introduce it, but change nothing in our processes!" Possible consequence: The system only documents, the inefficiencies remain.

  • Transformation: "We will use the opportunity to fundamentally rethink our processes!" Possible consequence: a leaner company with a system that holds up.

Which core message suits me?

The core messages address three types of readers:

  • For the quick to decide: "Standard ERP: Proven processes. More time for what matters." Invest less energy in self-built administration and concentrate on your performance in the market.

  • For the reflective: "Process optimisation is not a project, but an attitude." A standard ERP system makes you look honestly at your processes. This is uncomfortable, but can contribute to more efficient work and plannable growth.

  • For pragmatists: "Less administration. More value creation." Inefficient processes cost money every day. A standard ERP system makes them visible so that you can improve them.

Background: Why every movement must be recorded in the system

Scopevisio maps real processes, it does not create them. Every action that changes a stock, a value or a status (a goods withdrawal, a count, a posting) must therefore be consciously recorded in the system. Scopevisio cannot automatically detect a real action, cannot estimate it and cannot reconstruct it afterwards if it was not documented.

This recording is usually a single, clearly defined step, mostly a click on a document or a function. The step itself is not optional. At most, the time or the exact way in which it is done is negotiable (for example automated from a transaction or recorded manually afterwards), but not whether it takes place.

Why can Scopevisio not know by itself what is happening in the warehouse?

A system only knows what it has been told. Software cannot reliably know that someone has taken a product from the shelf, performed a service or carried out a count in the warehouse unless this is entered. The digital status and the real status are two separate things that must be kept in sync by recording. If the recording is omitted, a deviation arises between the two, regardless of how simple or complex the recording step is.

Which examples show the same logic?

  • An invoice is not posted: No payment transaction, no open item and no correct balance arise. The posting was omitted, the system did not fail.

  • A goods withdrawal is not recorded: The posted stock remains unchanged while the actual stock falls. The stock value in the system is then wrong because the withdrawal was not documented.

  • A count is not carried out: A system cannot estimate or derive a stock. It only maps what was counted and entered. If the count is missing, the basis for a correct stock is missing.

Why is the cause of a deviation often overlooked?

The difference between these cases lies in the visibility of the consequence. An omitted invoice is usually noticed immediately: open items, dunning and missing payment receipt make the error visible. An omitted goods withdrawal or count is often noticed much later, usually only at the next count or when a sale fails because of a missing stock.

This time delay does not change the cause. However, it often leads to the deviation being attributed to the system, although the cause, the missing recording, lies far earlier in time.

A system can make every real action recordable. It cannot replace an action that did not take place.

Did this answer your question?