Liquid UI - Documentation - 4.08 Before Liquid UI and After Liquid UI

4.08 Before Liquid UI and After Liquid UI


Using WS commands, you can group similar features and functions to a single screen, and further, group them in sections on a screen.

  • Screens, Transactions and Tab consolidations
  • Supports global changing of terminologies, e.g. ‘Defects’ to ‘Reason’; in fields, messages, menus, and even graphs
  • Freely manipulate tables and columns, create complex behavior changes – eg. VA01 with Shopping cart
  • Native Automation of OLE Excel directly for WS
  • Scalable 64-bit server engine
  • WS Recorder – easily diagnosis error after it

Scenario

For example, consider the Sales & Distribution module of SAP.

Using Default SAP Process

After Customizing using WS Commands

 

Before Liquid UI
After Liquid UI

 

Navigate to confusing Header and Item level

to enter data.

 

Presented in a simplified logical set of screens.

 

 

Going to another transaction for 4 screens of credit check, redundantly entering data.

Performed inside VA01, with radio buttons and prompts. Data entered here auto populates across subsequent steps.

 

Going into inventory system to perform Availability Check (ATP).

 

Integrated into VA01 and automatically completed.

 

New session of MM03 with 3 or 4 screens to check material.

 

Integrated into VA01 and without opportunity for error.

Pricing Condition requires 3 or 4 screens to handle various discounts and other conditions.

Presented in one screen with optional interactive help. Downstream cost of errors (returns, credits, re-invoicing) avoided.

Using WS commands, users can create better customizations and streamline SAP business processes.  Based on the usage of a command, WS commands are categorized as:

  • Adding Elements 
  • Changing Elements
  • Extensions
  • Functional Automation

Can't find the answers you're looking for?