simplified order entry and validation - winshuttle time saving in sd and mm module simplification of...

Simplified Order Entry and Validation Božidar Runje | ABB

Winshuttle EMEA User Group Conference | Brussels 2014

Agenda

Who is ABB ?

ABB case for Winshuttle

Key challenges

Key benefits

Lessons learned

ABB’s next phase


Who is ABB?

~150,000 employees

Present

in

countries +100

Formed

in

1988 merger of Swiss (BBC, 1891)

and Swedish (ASEA, 1883)

engineering companies

In revenue

(2013)

billion 42 $


How ABB is organized…


Power and automation are all around us You will find ABB technology…

crossing oceans and on the sea bed,

orbiting the earth and working beneath it,

on the trains we ride and in the facilities

that process our water,

in the fields that grow our crops and

packing the food we eat,

in the plants that generate our power and

in our homes, offices and factories


ABB functional area environment

Controlling

Financial accounting

Treasury

Project System

Sales & distribution 70 Sales Engineers create sales orders in SAP 10 in Low voltage products division In 2013:

2400 sales orders was created by LP, with around

480 000 items and condition types inserted

Material management

Asset management


Business processes in ABB


ABB case for Winshuttle (I)

Issue raised:

• Negative margin in the Orders received report for LP division.

Cause:

• Sales Engineers used wrong item category for discounts

User justification:

• Manual capture of factory discounted price for each item is time consuming for Sales Engineer.

Why Winshuttle?

• Initiative overlapped with Country Manager request to unload Sales Engineers work in SAP.


ABB case for Winshuttle (II)

3 possible scenarios to cover: • Internal (Inter-company) sales orders creation

For every item Sales Engineer had to modify 2 fields in „Shipping” tab: • Set Part.dlv./item to „Only complete deliveries allowed” • Set Max.Part.Deliv to „0”,

Sales order possible to save when for all items those fields where updated.

• External (standard) sales orders creation Header and item level data with lots of possible selections

• Updating existing sales orders • Multiple items and condition types to cover.


Manual Sales Order creation

Generally, Sales Engineers:

• needed to spend more time on higher value tasks

• used MS Excel before creating sales orders – data was ready for use with Winshuttle

Also:

• Standard copy & paste method from excel files to SAP has a limited functionality

• Organizational change required to improve business process and speed up data entrance in SAP


Creation of Standard Sales Orders


Winshuttle & ABB

• One person nominated for creation of Sales Orders for division (previously done by 10 persons)

• Sales engineers use customized Excel template to prepare data for administrator

• Administrator creates Sales Orders with Winshuttle script based on excel template

• Second script used to additionally add items with multiple condition types and condition rates in existing Sales Order

• Process of Sales Order creation is significantly reduced for one division with potential to be extended to other division.


Winshuttle script for creating Sales order

Sales order header:

Items and item details:


Key challenges


Key Benefits for ABB

Rapid response to daily business needs

Tremendous time saving in SD and MM module

Simplification of existing processes

Healthy master data records

Extensive support to on-going projects

Reduced support from ERP hosting center

Specific data extraction without customization

No need for LSMW: avoided error prone user files

SAP users work on higher value tasks


ABB scripts

• Additional scripts created and in everyday use:

Master data Vendors Customers Material Master data records Purchasing info records

Transactional scripts Purchase requisitions Sales Orders Foreign trade: Declarations to the Authorities Customer credit limit management


Script versioning

ABB use Winshuttle „Connect” solution.

IS department already used SharePoint portal: Winshuttle scripts are stored with versioning possibility. Administrators are automatically notified when new version of script is created.


Lessons learned

Learn Winshuttle capabilities and features!


Lessons learned

Key user should be involved in writing T-code specification for script development


Lessons learned

If lookup values should be used as a list from script, wait for script to become mature.


Lessons learned

Use parameter IDs in user profile to reduce mapping fields in excel files

When doing massive changes, activate option to create backup sheet.

Centralize location for Winshuttle Scripts: think about script distribution to Runners.

Deploy Transaction module on server environment (massive updates, scripts backup, scheduling scripts).


ABB’s next phase

Promote current scripts across divisions to avoid as much as possible manual processing in SAP

Analyze transactions with high volume in order to help in data entrance: Winshuttle Value Assessment

Focus on FI department and reduce huge manual workload; cut down overtime hours in closing periods and reporting to ABB Group.

Identify new opportunities for ABB in use of Winshuttle to simplify and optimize work in SAP.


Questions

Let’s connect: [email protected]

simplified order entry and validation - winshuttle time saving in sd and mm module simplification of...

Documents