Professional Documents
Culture Documents
Order To Cash - CTO Using Complex Model in WMS Mobile r12
Order To Cash - CTO Using Complex Model in WMS Mobile r12
Order To Cash - CTO Using Complex Model in WMS Mobile r12
Complex Model in
WMS/Mobile
Demo Script (Internal)
Page 1
Table of Contents
Page i
Order to Cash - CTO using Complex Model in WMS/Mobile
Document Control
Objective
'ENHANCED - R12' The purpose of this Flow demo script is to illustrate the use of Oracle
products to forecast, plan, price and fulfill a complex high-tech Integrated System (Server,
Storage and Rack) configuration. The demo starts in Oracle Order Management with order
creation and ends at Install Base. The configuration uses functionality that includes connectors,
configurator attributes and extended functionality such as dynamic imaging.
The configuration is priced using configurator attributes and pricing attributes in Advanced
Pricing. The order is scheduled and booked.
Enhancements for R12 include Option Specific Sourcing (OSS) where the Server Model is either
sourced and manufactured from W2 or purchased from Advantage Corp. Advanced Supply
Chain Planning processes (Collections and Plan) are run. We require the use of ASCP due to the
multi-org setup. This allows the creation of requisitions and inter-company orders which are
mostly automated through a request set. We then use mobile WMS to move, complete, pick and
ship from W2 to W1 or receive into W1 from Advantage Corp. We then use mobile WMS to
receive, put away, move, complete, pick and ship from W1.
For 11.5.10 the demo now uses Oracle Demand Planning to create a forecast which is published
to ASCP. The user can perform ATP check and see the items which are late. The user can also
see the consumption from the forecast. The models are now all serialized and visible in the
Install Base after invoicing. The scenario has been extended in 11.5.10r2 where the customer
logs into iSupport as there is a problem with a piece of hardware. She locates the component in
the Install Base and creates a Service Request.
Another R12 enhancement has the dispatch representative complete the service flow (dispatch
technician to customer site, debrief and close). We then see the updates to the structure back in
the Install Base.
Page 1
What's New?
Option Specific Sourcing (Server model sourced from W2 or Advantage Corp based on the
selected server)
Completed Dispatch Center Flow so the changes made in service are now displayed in the Install
Base
Pitfalls
NA
Assumptions
NA
Related Documents
http://globalxchange.oraclecorp.com/demodocs >Reference Materials Folder > Fundamentals
Page 2
Launch Planning Manager
Launch Planning Manager
1. Log into Forms
Field Value
User Name MFG
Password WELCOME
(T) Manufacturing
Applications Navigator > (N) Manufacturing and Distribution Manager > Advanced
Planning > Source Instance Setups > Setup > Planning Manager
(B) OK
Page 3
Optional - Change Processing Lead Times for ATP
Optional - Change Processing Lead Times for ATP
The items below have already been setup with lead times but you can change them if you
need to for your demo.
Select Organization
Field Value
Organizations W2
There are three items set for ATP in W2 for this demo: IS30200, IS30201 and IS30202.
These are the only items we need to change in W2.
(B) Find
(I) Save
These are the only items we set for ATP in W1 at this point.
Select Organization
Field Value
Page 4
Organizations W1
6. This is the same as the last section but it has to be repeated for the following items in W1:
IS40150
IS40151
IS40152
IS50250
IS50202
(B) Find
(I) Save
(I) Save
Page 5
Run ASCP Collections
Run ASCP Collections
You should run ASCP Collections and the Plan on the actual day of the demo to get the
correct ATP dates (with the default setup).
(N) Advanced Planning > Advanced Supply Chain Planning > Other > Change
Instance/Organization
Change Organization
Field Value
Organizations TST:W1
(N) Advanced Planning > Advanced Supply Chain Planning > Collections > Oracle
Systems > Standard Collection
Field Value
Instance TST
(B) OK
This will return you to the Planning Data Collection Request Set form.
(B) Submit
This will launch the data collection processes. The default settings will apply for the
Planning ODS Load.
(B) OK
Page 6
(M) Requests > View Requests > (B) Find
The collection process will launch a series of concurrent processes. When all of these
have completed, the collection process is done and you may proceed with planning.
The processes are:
Planning Data Collection (Report Set), which will launch:
Data Pull (Request Set Stage), which will launch:
Planning Data Pull
Refresh Snapshots
Planning Data Pull Worker (5)
ODS Load (Request Set Stage), which will launch:
Planning ODS Load
Planning ODS Load Worker (3)
Planning Data Collection - Purge Staging Tables
Collaboration ODS Load
All of these processes will complete with a normal status except the following:
The Planning ODS Load which completes with the following message in its log file:
“ORA-00001: unique constraint (MSC.MSC_UNITS_OF_MEASURE_U2) violated.”
The Planning ODS Load (Request Set Stage) which completes with the following
message in its log file: “The stage completed with the outcome Warning. This outcome
was computed by the stage function.”
Planning Data Collection (Request Set Planning Data Collection) which completes with
the following message in its log file: “The set completed normally with outcome
Warning. The outcome was determined by the stage Planning ODS Load.”
If any process completes with an error, identify the error message in the log file. Contact
demohelp with the error message.
Page 7
Run ASCP Plan
Run ASCP Plan
10. Launch Advanced Supply Chain Plan.
(N) Advanced Planning > Advanced Supply Chain Planning > Supply Chain Plan >
Launch
(B) OK
(B) OK
(B) Submit
(B) No
This launches a series of concurrent requests. It is not necessary to wait until all of the
requests have a Completed Normal status. After the Memory Based Planner has
completed successfully, the plan is available in the Planner Workbench.
Page 8
Launch Request Set
Launch Request Set
For 11.5.10 we tried to simplify the demo flow. To help with this we created a new request
set for all the pre-demo concurrent requests and associated parameters.
This script also documents all the requests in the request set (for informational purposes or
in case you wish to launch each concurrent request individually).
If you want to launch the concurrent requests individually, goto task #14. Otherwise, goto
task #11.
(B) OK
All the parameters have been defined in the request set. When Submit is clicked all the
parameters will appear.
(B) Schedule
Page 9
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Common
Run the Job Periodically
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s) You may need to consider a larger
time interval depending on other scheduled
concurrent requests being ran at the same time.
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
NOTE : you may get an error about the Offset Days. We are trying to fix this issue before
deployment. It does not affect the function of the request set or concurrent processes – it is a
problem with the value set. Just click OK to continue
(B) No
Page 10
Launch Transaction Interface Manager
Launch Transaction Interface Manager
14. Open the Interface Manager Form
(N) > Inventory > Setup > Transactions > Interface Managers
The Launch Inventory Managers window appears displaying the transaction manager
you choose as the process to be submitted.
Note: If the transaction manager is already active, Oracle Inventory displays a warning
before displaying the new window.
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) OK
Page 11
19. Close the Interface Manager window
Page 12
Launch Workflow Background Process for Sales Orders
Field Value
Item Type OM Order Line
Process Deferred Yes
Process Timeout No
Process Stuck No
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) No
Page 13
Launch AutoCreate Configuration Process in W1
In the Name field, use the LOV to select: AutoCreate Configuration Items
Accept the default parameters except change the Organization field from blank to W1
(B) OK
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
Page 14
Launch AutoCreate Final Assembly Orders in W1
(B) OK
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
Page 15
Close the Submit Requests Screen.
Page 16
Launch AutoCreate Final Assembly Orders in W2
(B) OK
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
Page 17
Close the Submit Requests Screen.
Page 18
Launch Create Internal Orders
Launch Create Internal Orders
29. Launch the Create Internal Sales Order Program under the Destination Inventory
Organization W1
(N) Other > Requests > Run > Single Request, (B) OK
Use the LOV to choose Create Internal Orders, there are no parameters
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) No
Page 19
Launch Order Import
Launch Order Import
31. Launch the Order Import Request Program
(N) Order Management > Orders, Returns > Import Orders > Order Import Request
Field Value
Order Source Internal
(B) OK
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) No
Page 20
Launch Release Sales Orders
Launch Release Sales Orders
33. Run Release Sales Orders (for W2)
(N) Order Management > Shipping > Release Sales Orders > Release Sales Orders SRS
Field Value
Release Rule Name W2WMS
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) Yes
Field Value
Page 21
Release Rule Name WMS Pick Release
(B) Schedule.
Specify a start time and an end time and specify that it be launched every minute at the
completion of the prior run.
Field Value
Start At Time demo is to begin
End At Time demo is to end
Re-run Every 1 Minute(s)
Apply the Interval... From the Completion of the prior run
(B) OK
(B) Submit
(B) No.
If Pre Demo Steps complete, goto task #37. Otherwise, goto task #1.
Begin Demo
Page 22
Create Sales Order for Integrated Systems
(T) Manufacturing
(N) Manufacturing and Distribution Manager > Order Management > Orders, Returns >
Quick Sales Order
Field Value
Customer Business World
Order Type IB Order – CTO
In past releases of this script we used SmartBuy as the customer. In the 11.5.10r2
version we now use iSupport and this is currently only set up for Amy Miller, an
employee of Business World. If you do not plan to show iSupport or creating a Service
Request then you can still use SmartBuy.
(T) Others
Page 23
Discuss how Defaulting rules were defined to automatically populate the fields in the
order screen such as order type.
Discuss how the defaulted order type on this order, Mixed, supports both order and
return lines. Point out that these can be defined based on customers business needs
This is important to successfully get all the details to the Install Base. You need to
select the correct line type - there are 3 Standard (Line Invoicing) types. It must also
be the one with a line type of ATO Model.
(B) Configurator
Page 24
Configuring a Complex Integrated System
Configuring a Complex Integrated System
For R12 we introduced Option Specific Sourcing in the flow to the Server Model. This now
results in two different flows (which cannot be combined at this point):
(See bug: 5755099)
For 11.5.10r2 the user interface is new now using HTML functionality. The flow is exactly
the same as the older DHTML ui.
This configuration is made up of four ATO models : ISAT000 (Vision Integrated Systems),
ISAT001 (Vision Servers), ISAT002 (Vision Storage Systems) and ISAT003 (Vision Rack
Systems). The model is manufactured in W1 except for the Server (ISAT001) which is
sourced from W2.
Note : the number of models configured (server - ISAT001) will affect some of the
downstream processing. For example, adding two server models to the order, one for a qty
of 1 and one for a qty of 2 will result in two inter-company sales orders. If both were for qty
one then both configurations would appear on one sales order.
The configuration is setup for several different paths and all options are working. All four
steps have to be completed for a valid configuration. The first page details the four steps
and each page has a similar layout to give the model a uniform feel. There is also a "Help"
button on the title bar, which launches an html file that discusses the four steps and the
various configurator icons. The "Help" exists on each page.
(B) F11
This will maximize the browser screen which will make it a little easier
(B) Help
This launches a custom html file into a new browser window. Navigate and discuss
how the configurator can access external hyperlinks. The help link is available on every
screen.
Page 25
42. Configure/Add Servers to the Configuration
You can add multiple instantiations of each model - this is called Solution Based
Modeling. What this means is that each instantiation can have a different configuration
from another. You can also change the quantity of each instantiation, as required.
There is also the ability to delete the instantiation.
We will go back and add a second server to this model in a subsequent step of this
script.
Notice at the top the Step-by-Step navigation. It shows all the steps/screens inside the
Server model.
This model has been designed for two levels of user. Guided Buying allows the sales
rep to ask business orientated questions to the customer and allows the configuration
rules to recommend a solution. Server Configuration allows the sales rep to enter in the
server details directly (CPU speed, memory, etc. etc.). We will use the Server
Configuration in a subsequent step of this script.
Select either Data Center or Web Services from the "Select a solution category"
Field Value
Select a solution category Any
If Data Center
Field Value
Select a solution for data services Any
If Web Services
Field Value
Select a solution for web services Any
Answer Questions
Field Value
What availability level do you need High Availability
Page 26
(Note : selects gold service level later in
model)
Numbered user performance Max 7,000
Response time performance More than 5 seconds
Numbered user performance and Response time performance are used to calculate the best
server configuration.
Field Value
Estimated storage capacity Maximum of 327GB
Used to calculate the disk capacity required for use in the storage configuration
Field Value
Would you like this system racked ? Yes
(B) Next
All the options have been pre-selected from the Guided Buying questions based on the
server requirements. Select any server options
(B) Next
Some of the PCI cards are not available and therefore not shown because of the
different Bus Speeds on each slot. Notice that only two PCI cards are available on this
server. As each slot is chosen the image on the right will update with the PCI card
number (this is standard functionality in 11.5.10 created by customizing the ui layout).
Page 27
PCI Slot 2 From Drop Down – Select Any without a
Red X
(B) Next
The software package options are actual hyperlinks to live Oracle pages with information
about Oracle products. These links are a standard part of the configurator product. Click on
some of these links to show the functionality.
(B) Apply
Notice that the complete box for the server now appears on the right. This gives the
user a guide as to where they are in the model
This will show the multiple instantiation/solution based modeling functionality and the
networking.
Note that the "Pre-Configured Storage Capacity" has already been populated. This
came from a question in Guided Buying.
Page 28
Notice how the first 6 disk arrays update.
Notice now that all 12-disk arrays populate - but with smaller capacity hard drives.
(B) Continue
This is where we use the connector functionality to create a network. The idea here is
to network the storage system to the server(s) within the model and use rules to validate
the connection. At least one connection is required in the model.
A new screen launches showing the configured servers from earlier. These are the
available servers for networking.
Field Value
ISAT001 Connector Vision Servers [1]
The storage system has only 4 ports, which are available for networking. Once a port
has been chosen it cannot be used in any other connections. This is controlled by
configurator the rules.
A new screen launches showing the configured servers from earlier. These are the
available servers for networking.
Field Value
Page 29
ISAT001 Connector 2 Vision Servers [2]
(B) Apply
There are two ways to configure the rack - either a standard rack system or a custom rack
system. The default is the standard rack system (due to answering 'yes' to rack in Guided
Buying)
Page 30
The custom rack description could be passed back to a flexfield via a trigger. This is not
implemented here in the demo.
(B) Apply
All the options have already been chosen as a result of earlier questions in the
configuration. The service features are required and are used to derive the correct price
for the corresponding service items in the Sever and the Storage models. This is
achieved using Advanced Pricing (a pricing package and pricing attributes) and
Configurator Attributes.
Field Value
Select a service level Already selected
Service duration Any
Select a service option Already selected
Select a monitor Any
(B) Apply
From the main screen it is possible to update the quantities of the configured models and
also show other rules. One of the rules is that each rack can only contain four components
(any combination of Servers and Storage Units). To show this we will change the quantity
of the each of the Server Models to two.
Note : the quantity of models configured (server - ISAT001) will affect some of the
downstream processing. For example, adding two server models to the order, one for a qty
of 1 and one for a qty of 2 will result in two inter-company sales orders. If both were for qty
one then both configurations would appear on one sales order.
(B) Enter
(B) Enter
This launches a message at the top of the window explaining the above rule. Rather
than adding a rack we will change the qty of the second server to 1
Page 31
(B) OK
(B) Enter
A new window launches saying that the "Number of Racks in now valid". This is all
controlled by the setup of the configurator rules.
Note : the quantity of models configured (server - ISTA001) will affect some of the
downstream processing. For example, adding two server models to the order, one for a
qty of 1 and one for a qty of 2 will result in two inter-company sales orders. If both
were for qty one then both configurations would appear on one sales order.
This shows all the items that are being passed back to the host application
(B) Finish
Page down the order to locate one of the Vision Servers (item ISAT001)
The item will be in option class ISOC209. The item starts with IS3035n.
Notice the price for the service item. The item shown will depend on what you choose
during the configuration. The attributes of Service Duration and Service Options were
used to derive the final service price - Advanced Pricing applies a specific markup
factor which we will show later in forms. We will now reconfigure the model to show
how the price changes for the same item.
(B) Configure
Page 32
(B) System Options / Service
All the options have already been chosen as a result of earlier questions in the
configuration. The service features are required and are used to derive the correct price
for the corresponding service items in the Sever and the Storage models. This is
achieved using Advanced Pricing (a pricing package and pricing attributes) and
Configurator Attributes.
Field Value
Service duration Make a different selection
(B) Apply
(B) Finish
The same service level is used in the Storage model to calculate the price. You can
show that as well in the same method as above.
Page 33
Check Availability
Check Availability
For 11.5.10 we enabled ATP (for a few items) for this configuration model. In this section
we will perform an ATP check and identify that some items will make the order late
(assuming today is left as the default Request Date).
(B) Availability
The Available Date should be about 30 days in the future (if you did not change the
processing time)
In the ATP Details screen some items will appear in yellow. The exact items will
depend on your configuration. The items in yellow will have a value in the Days Late
column. You may want to consider creating a new folder view and move the Days Late
to the left.
Therefore from this screen you can identify which items are sending the order late. This
screen would also show configuration matching, if it was enabled. We set up the items
to Not match but we plan to enhance this demo later.
The model will expand out to show pegging details enabling the user to identify the
items that are causing the lateness. The items late will depend on the settings you set in
the pre-demo steps for the Processing Lead-Times
Page 34
Schedule and Book Order
Schedule and Book Order
New in 11.5.10 is a change in the time at which the configuration items are created. Pre-
11.5.10 the order had to be booked before the CTO concurrent process created the
configuration items. With 11.5.10, once the order has been scheduled then the CTO process
will pick up the configuration and create the item(s). We have the concurrent request
running in the Request Set launched in the pre-demo steps.
Please note – only the top level ATO configuration item will be visible within the sales
order even though the lower items have also been created. These lower level models can be
viewed in the Supply to Order Workbench which we cover shortly in the script.
The order should schedule to the date shown in the availability screen based on item
availability
(B) Book
Page 35
Review Supply to Order Workbench
Review Supply to Order Workbench
Once the order has been scheduled the request set will process the configuration model and
create the configuration items. Only the top-level item (ISAT000*12345) will be visible
from the sales order. We can see all the configuration items in the Supply to Order
Workbench.
Once the order has booked then the request set will also process the configuration item and
create the top-level job order in a Released status (controlled by a concurrent request
parameter). The CTO process will also create the lower level work orders for ISAT002 and
ISAT003.
(B) OK
Notice that a WIP job has been created for the parent item which is linked to this sales
order. The line status should be Production Open.
You will now see all the configuration items created for this model. Please note these
down as you will use them later:
Page 36
This will give information in a new screen on the WIP Job status. The status should be
Released. Write down the WIP Job Number (Document Number):
WIP Job (Document Number) : _____________
Page 37
Run ASCP Collections
Run ASCP Collections
As we mentioned earlier the ISAT001 model is sourced from W2. As this is a multi-
organization demo with ATP we have to run ASCP Collections and Plan to create the
internal requisitions. Later they are then released from the Planners Workbench and
imported into W2 to created the internal sales orders.
ASCP Collections should complete in about 15 minutes although this will vary based on the
instance loading.
(N) Advanced Planning > Advanced Supply Chain Planning > Collections > Oracle
Systems > Standard Collection
(B) OK
Field Value
Instance TST
(B) OK
This will return you to the Planning Data Collection Request Set form.
(B) Submit
This will launch the data collection processes. The default settings will apply for the
Planning ODS Load.
Page 38
A Submitted Request Set pop-up will be displayed.
(B) OK
The collection process will launch a series of concurrent processes. When all of these
have completed, the collection process is done and you may proceed with planning.
The processes are:
Planning Data Collection (Report Set), which will launch:
Data Pull (Request Set Stage), which will launch:
Planning Data Pull
Refresh Snapshots
Planning Data Pull Worker (5)
ODS Load (Request Set Stage), which will launch:
Planning ODS Load
Planning ODS Load Worker (3)
Planning Data Collection - Purge Staging Tables
Collaboration ODS Load
All of these processes will complete with a normal status except the following:
The Planning ODS Load which completes with the following message in its log file:
“ORA-00001: unique constraint (MSC.MSC_UNITS_OF_MEASURE_U2) violated.”
The Planning ODS Load (Request Set Stage) which completes with the following
message in its log file: “The stage completed with the outcome Warning. This outcome
was computed by the stage function.”
Planning Data Collection (Request Set Planning Data Collection) which completes with
the following message in its log file: “The set completed normally with outcome
Warning. The outcome was determined by the stage Planning ODS Load.”
If any process completes with an error, identify the error message in the log file. Contact
demohelp with the error message.
Page 39
Run ASCP Plan
Run ASCP Plan
The ASCP Plan should complete in about 5 minutes although this can vary based on the
instance loading.
(N) > Advanced Planning > Advanced Supply Chain Planning > Supply Chain Plan >
Launch
(B) OK
(B) OK
(B) Submit
(B) No
This launches a series of concurrent requests. It is not necessary to wait until all of the
requests have a Completed Normal status. After the Memory Based Planner has
completed successfully, the plan is available in the Planner Workbench.
Page 40
Release Requisitions from ASCP Planners Workbench
Release Requisitions from ASCP Planners Workbench
Where are we: The discrete jobs are automatically released into manufacturing. However
we still need to use the PWB to release the purchase requisitions against W2 for the
ISAT001 (servers). Once released the request set will run a series of processes to import
into W2, automatically create the sales orders and automatically release the work order.
(N) Advanced Planning > Advanced Supply Chain Planning > Supply Chain Plan >
Workbench
(B) OK
(T) Plans
Click on Configurbl
This will open the Supply/Demand(TST:W1) form showing all the IS% items. We
create a query to automatically locate the requisitions for release
(I) Folder
Field Value
Open Folder ISAT001 Requisitions
(B) OK
This will show the ISAT001 configuration items. Here you will see the new
configuration items for the order you entered. You should see 2 (ISAT001*nnnnn and
ISAT001*nnnnn).
Page 41
(T) Sourcing
In here you will see how the server configuration is being sourced based on OSS. For
example:
Click on the For Release checkbox for each line (for the items you noted earlier)
(I) Save
Note the Due Date and Quantity of the job so you can verify the job is created correctly.
A release status dialog box will be displayed telling you to what instance it was saved
and what type of supply was sent over.
(B) OK
The request set will now process the releases to create and release the sales order in W2
for the two ISAT001 items. These make a few minutes to run and complete.
- ISAT000*nnnnn (Integrated System) This is not shown in the WIP Mass Load
- ISAT002*nnnnn (Storage)
- ISAT003*nnnnn (Rack)
In W2 :
- ISAT001*nnnnn (Server)
- ISAT001*nnnnn (Server)
Once the order has been created in W2 the request set will also automatically run the
following :
Create the Releases
Order Import into W2 (creates Order Import Child Req1 for each)
Page 42
AutoCreate Final Assembly in W2 (creates and releases the work orders for
each ISAT001 item)
Page 43
Transact Mobile Move and Complete in W2
Transact Mobile Move and Complete in W2
Where are we : the order(s) have been progressed into manufacturing and both
configurations (ISAT001*nnnnn) that are sourced from W2 are now moved and completed
Mobile Apps is accessed from the Direct Access portal, there is no need to logout.
(B) Launch
Field Value
Device List Default
66. Transact Mobile Move and Complete for Each of the ISAT001 Jobs
(N) Manufacturing (4) > Assy and Material Txn (1) > Complete Assy (2) > Move and
Complete (2)
Select Organization
Field Value
Organization W2
Page 44
SN (Serial Number) VIS1100xx* (VIS11000, VIS11001, etc.)
If "No result is found" is displayed when trying to locate the job then you need to wait
for the request set to process (order import, auto-create final assembly in W2)
The serial number is required and used later in Install Base. Write down the serial
numbers:
ISAT001*nnnnnn SN = _____________
ISAT001*nnnnnn SN = _____________
<Save>
The items have been moved and all materials have been backflushed.
(B) F2
Go to Menu > Y
(B) F2
(B) F2
(B) F2
Page 45
Pick from non-LPN Controlled Sub Inventory with Drop
Pick from non-LPN Controlled Sub Inventory with Drop
Where are we : the configurations are now picked as the backflushing was completed in the
last step.
(N) Tasks (5) > Directed Tasks (1) > Interleaved Tasks (1) > Accept Any Task (1)
(N) Done
You will see the pick task for the item entered earlier. If you don’t then ensure that the
request set is still running. The Interface Manager has to run the WIP Move Transaction
Manager and Process Transaction Interface Manager before you see the tasks.
If you have created bar codes you will be able to scan the following information, if not you will
need to confirm each field. Please see the Script WMS - Label Viewer for further information on
viewing and printing labels.
Field Value
Sub (populated) BULK
Confirm BULK
Loc (populated) B1.1.1
Confirm B1.1.1
LPN Null
Item (populated) Assembly Number : ISAT001*nnnnn
Confirm* ISAT001*nnnnn
UOM (populated) Ea (1 Ea)
Confirm 1
Page 46
SN Ctrl L (this will used the SN you entered
earlier)
<Done>
Generate LPN
Field Value
Xfer LPN Ctrl G to Generate Next LPN No.
The system will now direct you to the Staging Lane to drop the product you just picked
Field Value
From LPN Filled in from previous step
To Sub (populated) STA
Confirm STA
To Loc (populated) L1.1.1
Confirm L1.1.1
Drop LPN Null, assumes same as From LPN
<Done>
The configuration (order line) is now staged and ready for loading to the Truck via the
Dock Door
If the first configuration, goto task #69 and repeat the above steps for the second
configuration. Otherwise, goto task #72.
(B) F2
(B) F2
(B) F2
Page 47
Ship LPN Mobile in W2
Ship LPN Mobile in W2
Where are we: the configurations are now ready for shipment to W1.
<Continue/Ship>
<Ship All>
You will receive a message to say the deliveries have been submitted Interface Trip Stop
req >
If the first configuration, goto task #74 and repeat the above steps for the second
configuration. Otherwise, goto task #76.
Page 48
(B) F2
(B) F2
Page 49
Receive Purchase Order in Mobile in W1
Receive Purchase Order in Mobile in W1
Where are we : We are now in the W1 organization and will receive in the purchased server
(VS400X) that is sourced from Advantage Corp.
<Done>
Page 50
Receive Internal Requisition in Mobile in W1
Receive Internal Requisition in Mobile in W1
Where are we : We are now back in the W1 organization. The configurations (the servers)
have now shipped from W2 and now have to be received into W1 ready for shipment with
the rest of the configuration (storage and rack).
The only way to get the Req numbers is to look at the conc request Order Import Child
Req1. One is create foe each ISAT001 item. Click on the View Output button and look to
the bottom. You will see 10/9369// Order has been booked. The 9369 is the req number.
You may want to note those down for use in this section in case there are other requisitions.
(N) Inbound (1) > Receive (2) > Int Req (4)
Field Value
Org Code W1
Req Num Scan, Enter # or Ctrl L. A req number should be
visible
From LPN Ctrl L. Your LPN(s) should be visible
Item Ctrl L
<Done>
Page 51
If the first requisition, goto task #78 and repeat the above steps for the second requisition.
Otherwise, goto task #82.
(B) F2
(B) F2
Page 52
Put Away in Mobile in W1
Put Away in Mobile in W1
Where are we : the two configurations are put away in W1
(N) Tasks (1) > Directed Tasks (1) > Directed Move (5) > Move Any LPN (1)
<Drop>
If the first order, goto task #83 and repeat the above steps for the second requisition.
Otherwise, goto task #85.
(B) F2
Go to Menu > Y
(B) F2
(B) F2
(B) F2
Page 53
Transact Mobile Move and Complete in W1
Transact Mobile Move and Complete in W1
Where are we: The server model(s) have now been manufactured, shipped from W2,
received and put away into W1. The other configuration items (storage, rack) are now
moved, completed, picked and shipped in W1. The whole system (ISAT000) is then
shipped and invoiced.
(N) Manufacturing (4) > Assy and Material Txn (1) > Complete Assy (2) > Move and
Complete (2)
<Save>
The items have been moved and all materials have been backflushed.
<Save>
Page 54
The items have been moved and all materials have been backflushed.
<Components>
The serial number needs entering for each of the sub assemblies (the nested models)
under ISAT000. This is very easy, just use Ctrl L to select the Serial Numbers that
have already been entered
<Next Component>
<Next Component>
<Next Component>
Page 55
Enter Parent/Component Serial Number
Field Value
Component ISAT003*nnnnnn
Parent SN Ctrl L
SN Ctrl L
<Save>
The items have been moved and all materials have been backflushed.
(B) F2
Go to Menu > Y
(B) F2
(B) F2
(B) F2
Page 56
Pick from non-LPN Controlled Sub Inventory with Drop
Pick from Non-LPN Controlled Sub-Inventory with Drop in W1
Where are we : the parent model, ISAT000, is now ready for picking
(N) Tasks(5) > Direct Tasks(1) > Interleaved Tasks(1) > Accept Any Task(1)
You will see the pick task for the item ISAT000*nnnnn
If you have created bar codes you will be able to scan the following information, if not you will
need to confirm each field. Please see the Script WMS - Label Viewer for further information on
viewing and printing labels.
Page 57
Item (populated) ISAT000*nnnnn
Confirm ISAT000*nnnnn
UOM (populated) Ea
SN Ctrl L (to use the same number as earlier)
<Done>
The system will now direct you to the Staging Lane to drop the product you just picked
Field Value
From LPN (populated) Filled in from previous step
To Sub (populated) STA
Confirm STA
To Loc (populated) L1.1.1
Confirm L1.1.1
Drop LPN Null, assumes same as From LPN
<Done>
The Order is now staged and ready for loading to the Truck via the Dock Door.
Page 58
Ship LPN Mobile in W1
Ship LPN Mobile in W1
Where are we : the parent model is now shipped. Once shipped Workflow will process the
order. This will create the invoice and it will become visible in the install base.
(N) Outbound (2) > Shipping (3) > LPN Ship (2)
<Continue/Ship>
<Ship All>
Page 59
You will receive a message to say the deliveries have been submitted Interface Trip
Stop req.
Page 60
View Sales Order Invoice
If you want to view the sales order invoice through AR, then goto task #100. Otherwise goto
task #101.
(I) Find
(B) Find
(N) Order Management > Orders, Returns > Quick Order Organizer
(B) Find
Page 61
Receivables Transaction form is opened.
Logout of Portal
Page 62
View Order in Install Base
102.Login to iSupport
(H) iSupport
This returns all the Vision Integrated Systems models in Install Base
(I) View Configuration against the Instance with the Correct Serial Number
Expand the Vision Storage Systems (with the Configuration Item and Serial Number)
Page 63
NOTE: It is very important you log the service request against the Vision Storage
Systems model with the ISAT002*nnnnn and a serial number.
The failed component is the hard drive in the configuration. For example, 36 GB HD
@ 7200rpm.
‘Create Service Request: Identify Problem’ page will display. The item you launched
the request from is automatically shown in the Product section
Field Value
Problem Type(LOV) HARDWR (Hardware Problem)
(B) Select
Field Value
Urgency(LOV) Immediate
Problem Summary One of the Hard Disks has failed
(B) Next
Page 64
now it has stopped working
(B) Next
Navigates to the Suggested Solutions screen. iSupport will try and bring up a solution.
Currently we have no recommendations.
(B) Next
(B) Next
(B) Submit
A confirmation with Service Request number will be displayed. Write down the
Service Request Number: ________
(B) Email to Me
We now change roles in the flow and move to the Field Service Dispatcher who schedules the
task for the technician
Page 65
Generate Field Service Trips
Generate Field Service Trips
This program creates shifts (arrival and departure tasks) for every technician. This can be
run as a pre-demo step.
107.Login
Field Value
Username/password syuhov/welcome
Responsibility Field Service Manager, Vision Operations
108.Generate Request
Enter Parameters:
Field: Value:
Time Frame Start Today’s date (Default)
Action Add
(B) OK
Parameters window closes and the Generate Shift Tasks window is again the focus
(B) Submit
(B) No
Page 66
Create Task
Create Task
In this scenario, the service agent will create the task for the service request created in the
previous step.
(N) Filed Service Dispatcher > Service Request > Service Requests > Find Service
Requests
(B) Search
(T) Tasks
(I) Save
Task Number will appear in the NUM field and Task record will appear in the spread
table. Write down the Task Number: __________
Close window
Page 67
Assign Field Engineer (Dispatch Center)
Assign Field Engineer (Dispatch Center)
In this scenario, the field service dispatcher assigns and schedules the technician to the task
that was created in the previous step by the service agent.
The field service dispatcher assigns and schedules the service task to appropriate service
technician based on: technician availability, parts availability, skills and contract SLAs.
The newly created tasks not yet assigned are listed in the Inbox on the left of the
dispatch center.
Find the task you just created or would like to schedule and highlight it with the cursor
The Auto Schedule and the Advise buttons are now enabled.
In Intelligent mode, the Scheduler suggests task assignment options based on pre-
defined constraints and costs. The costs should be interpreted as “penalty points” rather
than real costs.
Select the checkbox next to Territory Qualifiers (under the Resources section)
Territory Qualifiers: all are selected by default – you can unselect them if necessary to
further limit a search.
Contracts and Installed Base options can be used when there is a preferred resource
defined in either a customer’s service contract or associated to a product in the
customer’s installed base.
Skills option can be used when a task need resources with specific skills to perform the
task.
Page 68
Select No parts for the Availability Condition (Under Spares section)
(B) Search
The Advice Tab is active. The various assignment options are listed with a relative cost
for each option. The options are listed in ascending sequence of “cost”.
The resource list will show the travel times for each resource to the task location.
Check the first option, which is the resource with lowest cost
The Start and End date fields are populated at the bottom of the tab
(B) Schedule
Overview Tab now shows: The Scheduled Start and End dates for the scheduled task
The task status change can be seen in the Plan Board, to the right of the departure time.
In the Plan Board and the Gantt tab, the task color changes based on the setups to reflect
the new status. The status is also updated in the Resource tab.
Page 69
Debrief Task
Debrief Task
In this scenario, since we are using the same user for the entire flow we can assume that the
field service technician does not have access to the application so he/she may pass the
debrief information to the dispatcher. The field service dispatcher debrief on behalf of the
technician. However, we have setup different technicians in case you need to show the
specific role.
Right click on the task that was previously assigned and select Debrief
(B) Apply
Page 70
This can take a few seconds to come up
(B) Apply
Page 71
A concurrent request (CSF: Update Debrief Lines) is launched in the background to
generate charges, create inventory transactions and update Installed base.
If your request finishes with warnings go to the Debrief form to check the error
Column. Correct the error and submit the request again. You just need to save the
changes.
118.Review Charges
If you highlight your task in the task box the Service Request UI will show up.
Otherwise, you will get the Find Service Request UI and you will need to enter the SR
or task number.
(ST) Action
Verify charge lines have been created for all debrief lines
(ST) Pricing
(B) Submit
Now Order is created in Booked Status. This order contains items that are “Bill Only”
and if you want you can show these back in Order Management.
Page 72
View Changed Install Base
119.Login to iSupport
Field Value
Username/password amiller/welcome
This returns all the Vision Integrated Systems models in Install Base
(I) View Configuration against the Instance with the Correct Serial Number
Expand the Vision Storage Systems (with the Configuration Item and Serial Number)
You will now see the original count has dropped from 12 to 11 and there is now a new
disk with the status “Latest”.
Page 73
End of activity.
Page 74
Flowchart
Start
Run ASCP Launch Request
D
Collections Set
Launch Planning Launch ASCP Launch ADS Request
Mgr Collections (8) Set (12)
Check Collections Schedule request to run
Log into Forms (1) Processes. (9) periodically (13)
Launch Planning Mgr
(2)
A
Run ASCP Plan A
Optional - Change Launch Advanced
Supply Chain Plan. (10) Launch
Processing Lead Transaction
Times for ATP Interface Mgr
Open Organization Item Open Interface Mgr
for W2 (3) Form (14)
Set Processing Lead Select Organization W1
Time (4) You want to
(15)
Open Organization Item launch concurrent
Y Launch Transaction
for W1 (5) requests individually?
Interface Mgr (16)
This is same as last A Schedule request to run
section but it has to be
periodically (17)
repeated for following
Repeat above for
items in W1: (6) N Material Transaction
Set Processing Lead (18)
Time (7)
Launch Request Close Interface Mgr
window (19)
Set
Change Organization B
(11)
Page 75
B
Page 76
C
Page 77
E
Y
First configuration? F
Page 78
F A
Page 79
H
Page 80
I
Login (107)
Generate Request
(108) Debrief Task
Debrief start of task
(114)
Create Task Create Labor Debrief
Line (115)
Create Task from Create Material Debrief
Service Request (109) Lines (116)
Debrief complete,
complete Task (117)
Review Charges (118)
Page 81