Ultriva User’s Conference 2012Business Unit configuration

Presented by Nandu Gopalun

Business unit configuration

– Business unit Configuration

2

Topics to cover

Business Unit configuration.

• Customization verses Configuration• Standardization• User friendly• Self Explanatory (Mostly)

3

Business Unit Configurations

4

• Where can we set?– Every Business unit level

• Plant level• Work center level• Supplier level

• Who can set?– Administrators at Plant and WC level– Buyers at Supplier level

Business Unit Configuration

5

Plant or Work center level configuration

Business Unit Configuration

6

• Call off is a special Feature where the customer send forecast and make the supplier to keep the parts ready by the date and customer calls for the product when the actually need them

• It is mainly used from LCR suppliers Vs Domestic Suppliers

• Only applicable if you have LFM module

• Only applicable if you have LFM module

• Ultriva can also Track the Blanket Quantity and alert Buyer

General Configuration

Business Unit Configuration

7

• Different Prefix for Temporary Card (Old Feature since some of the customers are still using)

• Seasonal Kanbans can be handled by turning this ON.

• Loop size set up when customer do data load using web

• Do not force Loop size• Minimum 2 cards in the loop• No Adjustment

Card Configuration

• Max Number of cards can be created in a batch

Business Unit Configuration

8

• Inspection Rejection process can be • Classic• Manual

• Managing Decimal factors

Custom Configuration

Business Unit Configuration

9

• Off means customer prefers to fix the issue in ERP and doesn’t want Ultriva to send the record again to ERP

• On means User fix the issue and retry in Ultriva, which in turn send the data back to ERP

• Only for some parts you need integration

• Mainly for Oracle

Integration Configuration

• Mainly for Oracle but can be used in any place

Business Unit Configuration

10

Pick List Configuration

Business Unit Configuration

11

• Ultriva can send Kanban Card in email to supplier.

• Mainly used at 3PL or warehouse

Print Configuration

• Depends on internet connection speed

Business Unit Configuration

12

• Combination > Needs to turn on the flag at Item Level

• Self explanatory

• Mainly used if the data coming from ERP without kanban card ID

Receipt Configuration

• Validation

Business Unit Configuration

13

• Used in SBR Module

• Used in SBR Module

Release Configuration

Business Unit Configuration

14

• Multiple Scan before submit

• If the receiving team missed to receive and part is consumed so quick, the system will auto receive instead of fail

Scan Configuration

• If supplier missed shipping the card in Ultriva and when the receiver scans the card it will automatically Ship the card and receive the card.

Business Unit Configuration

15

• Used in OEE Module

Ship Configuration

• (Mainly used in SBR Module but it can be used in kanban also)

• None• All Items• Selected Items

Business Unit Configuration

• Supplier Business Unit Configuration

16

Business Unit Configuration

17

• Used in LFM Module

Release Configuration

Business Unit Configuration

18

• Supplier can get Release ID electronically using EDI / flat file and print the card ID from their ERP System

• Used mainly in 3PL or LFM Module

Print Configuration

Business Unit Configuration

19

• Used in LFM Module

Receive Configuration

Business Unit Configuration

20

• Depends on Customer this can be enforced at supplier level

• Supplier can send EDI 856 or ASN electronically.

Ship Configuration

• Self explanatory

• Master Lebel

Questions

21

22