User Manual

For
ASCP Work-Bench

Version - 04

Page 1 of 136
 DOCUMENT RELEASE NOTICE

Date Made By Checked By Approved By Version Change Reference

27-June-14 Core Team 00 First Version Released
03-SEPT-14 Core Team 01 First Version Released (INSTANCE CHANGE)
14-JAN-15 Core Team 02 Third Version Released
17-MAR-15 Core Team 03 Fourth Version Released
10-DEC-16 Gaurav 04 Fifth Version Released

Change History –

Date Change Details

27-June-14 First Version Released
03-SEPT-14 Second Version Released (INSTANCE CHANGE)
10-DEC-16 a) Business Forecast terms change in Protocol for ASCP.
b) Validation case changes from 75% to 100%.
c) FG special category (FPRD.FPRD.SPL.NA) removed.
d) Steps added for DS/PR release through ASCP to SPO creation and
approval.

Page 2 of 136
 Table of Contents

1. Protocol of ASCP Run ....................................................................................................................................4

2. Steps for Plan Run ........................................................................................................................................5
3. Set Ups for ASCP Run ............................................................................................................................. 6-17
4. Routings… .................................................................................................................................................. 6-9
5. Define Cluster Priority & Harness Priority… ............................................................................................ 9-14
6. Define Club Days & Buffer Days… ......................................................................................................... 14-17
7. Assembly Work Bench & WB Parameter Details .................................................................................. 17-24
8. Color Code Details .......................................................................................................................................24
9. Editing/Modification on Final Assy Plan .....................................................................................................24
10. VALIDATION TEST CASES…………………………………………………………………………………………….………………………25-38

11. Method to check schedule from Standard Workbench & Excel Export of Prod. Plan……..................39-53

12. To see pegging in Supply and Demand……………………………………………………………………………………...........55-63

13. GANTT CHART …………………………………………………………………………………………………..…………..……………………64-68

14. LPC Work Bench…………………………………………………………………………………………………………….…………………..69-72

15. LPC Work Bench Details………………………………………………………………………………………………………………………72-73
16. Editing/Modification on Final LPC Plan ...................................................................................................... 73
17. Work Order Creation & Release through Custom Release Set Request …….…………….………………………..74-86

18. Sub Inventory Transfer (Production Slip) from PF001 to FG001…………………………..…………………………..….87-90

19. IR Release from ASCP & to check DFF……………………………..………………………………..…………………………………91-102

20. DS Release from ASCP for wires and RM Items after Purchase Plan Run………………………………………..….…103-110

21. PR Release from ASCP for MSEW/SMIEL/APD and SPO Creation & Approval………………………………..….…110-136

Page 3 of 136
Protocol of ASCP Run:-

Page 4 of 136
Steps for Plan Run

1. Assembly Plan Run.

a. User can change the assembly plan (If req.) and save. In this saved assembly plan, LPC Plan will
Run.
b. If user doesn’t change the plan within the time limit, then system suggested Assembly plan will be saved &
LPC Plan will be run on the same system suggested plan.
2. LPC Plan Run.
a. User can change the LPC plan (If req.) and save. In this saved assembly plan, Child Part Plan will
Run.
b. If user doesn’t change the plan within the time limit, then system suggested LPC plan will be saved & Child
Part Plan will be run on the same system suggested plan.
3. Child Part Plan Run (Purchase Plan Run)
After LPC Final Plan Run, Child Part Plan will run.
4. Work Order Creation
Work Order(s) is (are) create and release to source instance by Custom Release With Parent Update.
By this program we can create for single FG code or for all FG for that particular ORG. (Unit).
And the job orders are created on date basis for e.g. if we release plan for 10th Sept. then on the basis of
freeze LPC Plan date-wise job order released.

Page 5 of 136
Set Ups for ASCP Run:
Routings of the FG/SUBA.
Step-1:- Go to design Responsibility and Click on Routings.

Step-2:- Below screen will appear, then again click on “Routings”.

Page 6 of 136
Step-3:- Routing Screen will appear.

Enter Item Code and Then as department for the item If FG then Assembly for SUBA it will be LPC

Page 7 of 136
 Step-4:- Click on Operation Resources to define Cluster and Standard time for harness which comes from Interface
Automatically. If we have to change we can change It for example if hourly Output for harness is 4.7 in One Hour
then we have to enter 4.7 in Inverse Column.
Harness qty completed
in 1 Hour
Click here to add
Cluster

Basis Should be
Item

Time taken to complete

1 harness (Hrs)

Step-5:- To define completion Sub inventory click on routing detail.

Enter Deptt. For
Item
Sequence will come
automatically as 10

Page 8 of 136
 Step-6:- In Completion Sub Inventor y Enter the Sub inventory in which after Completion Item Will be Transfer.

For FG PF001; For CKTS/JCKT/CCKT will be WIPCKT

Enter completion
Sub inventory

To define Cluster Priority and Harness Priority:

Step-1:- Go to “MSSL_Custom_Responsibility”.

Page 9 of 136
Step-2:- Then go to “MSSL Cluster Priority” option to change Cluster priority.

Below Window will appear:-

Page 10 of 136
 Step-3:- In the below window press F11 and Ctrl+F11 to get data.

FG Code
Suba Code
Cluster Description Harness
Unit Code Cluster Code
Cluster Priority
Priority

Step-4:- Click on new tab (as per below instruction).

Click here to add new

entry

Page 11 of 136
Step-5:- Fill the details as per below instructions.

Enter Unit Code Enter Cluster Code

here here

Step-6:- Fill the Cluster priority as per below instructions.

Enter Cluster
Priority here

Page 12 of 136
Step-7:- Fill th e FG Code as per instructions.

Enter FG Code
here

Step-8:- Fill the FG Prioirty as per below instruction.

Enter FG priority
here

Page 13 of 136
Step-9:- Now, Save the details.
Click on SAVE
option

Defining Fixed Days Supply (CLUB days) and safety Stock % (Buffer Days):
Step-1:- Select Custom Resp. from resp. menu.

Page 14 of 136
 Step-2:- Select Item Inventory Info from resp. menu.

Click Here

Step-3:- Below screen will be appeared. Find button to To define MRP To Consider pack
get detail planned or Not size of RM Item
Enter FG (Item
Code) here

Description of
Item

As per Login
Org Code will
come

To define To define Club Days

planner for enter here days
the Item

To define Item To Buffer days

is Make or Buy Enter days*100
for Ex. For 2
days enter 200
To define here
Minimum qty to To define To define
buy for item Max. qty to locator for
Buy for item the Item

Page 15 of 136
Step-4:- Fill the FG Code as per below instruction.

To Check To define item is

material bar code enable
Step-5:- Click on find. status or not

Page 16 of 136
Step-6:-Details will be populated automatically.

Assembly Work Bench

Step-1:- Login

Page 17 of 136
Step-2:- Select Workbench option from ASCP module resp. menu.

Click on
“Workbench”

Step-3:- Below screen will appear, and show the Plans. Select Assembly Plan to view or to change and save.

Right click on
“Assembly Plan”

Page 18 of 136
Step-4:- Below window will appears, Go to Custom PWB, and then Custom Planning Workbench.

Custom PWB
Custom Planning Workbench

Step-5:- Below is the Assembly Workbench (Custom Workbench).

Plan Start Date

Excel Export
I.O. Text Box Button

SAVE Button

MSSL_Production (Assembly Plan)

Query Button

Plan Due Date

Page 19 of 136
Step-6:- Fill the req. details (Only I.O. code) & Press Query button to retrieve plan.

Select I.O. and press OK.

Inventory Organizations LOV Window.

Click on I. O. & fill Unit

name. Click on “QUERY”
button to retrieve plan.

Page 20 of 136
Step-7:- Plan will be received in below format.

Demand Row, System Suggested Plan Row, User Editable Plan Row.

System Suggested User editable Plan

Demand Row. Plan row Row

Page 21 of 136
 Assembly Workbench Parameter Details:-

6 8 12
5 9 3 4 13 14
2 7 15
1

16

17

18

11 10 19
20

21

22

23

24

25
26 28
27

Page 22 of 136
S. No. Parameter Details
1 Inventory Organization This shows Inventory Org. for which work bench is opened
2 Plan Type This shows the plan type i.e. Assembly plan or LPC plan
3 Start Date This shows the date on which plan is run
4 Due Date This shows the last date of plan
This will show total demand for the bal. month. (It Works on
5 Bal. Month Demand weekdays from 1st day to last day)
6 Next Month Demand This will show total demand for the next month.
This will show harness buffer days which was defined in
7 Buffer Days source.
This will show Harness Club Days which was defined in
8 Club Days source

9 FG Assy Capacity This will show the harness output in an hour for Assembly.

10 FG LPC Capacity This will show the harness output in an hour for LPC.
11 Alternate Cluster This will show the alternate cluster if defined
12 FG Stock This will show the stock for the particular FG Code.
13 Pre FG Stock This will show the Pre FG stock for the particular FG Code
14 Open Job Order qty. LPC This will show open work order qty. for LPC.
15 Open Job Order qty. Assy This will show open work order qty. for Assembly.
16 Harness Cluster This will show the Harness Cluster
17 Cluster Priority This will show the Cluster Priority
18 FG Priority This will show the Harness (FG) Priority
19 No. of Ckts This will show details of Harness Ckts
20 Total Demand Load (Ckts) This will show total Ckt load as per demand

21 Total Demand Load (C/O) This will show total Change Over (C/O) load as per demand
22 Total Suggested Load (Ckts) This will show total system suggested Ckt load
23 Total Suggested Load (C/O) This will show total system suggested Change Over load
24 Total Actual Plan (Ckts) This will show total actual planned Ckts
25 Total Actual Plan (C/O) This will show total actual planned Change Over
26 FG Code This will show End FG Code (Harness Code)
27 SUBA Code This will show SUBA Code w.r.t. FG Code (Harness Code)
This will show the qty. which is not produced before the
28 Backlog Qty. plan run date.

Page 23 of 136
Color Code Details:-

Color Assembly LPC

Blue Line Demand Demand (Assembly Actual Plan/ User Modified Plan)
Grey Line System Suggested Plan System Suggested Plan
White Line User Modified Plan User Modified Plan
Red Highlighted Cell Capacity Over Loaded Capacity Over Loaded

Editing/Modification on Final Assy Plan

Step-8:- User can edit/modify the system suggested plan if req. User can change the qty., pre pone or
Postpone the system suggested plan in white colored line and then after modification press the
Save button and this plan will be saved as a final actual plan. On the basis of this final actual
Plan LPC Plan will be run next day of Assembly Plan.

User can edit plan here only in white

row.

Page 24 of 136
Validation Test Cases

Page 25 of 136
Page 26 of 136
Case-1: System Suggested plan as per club days.

Page 27 of 136
 Case-2: System Suggested plan as per buffer days.

Case-3: System is suggesting next month’s demand.

Page 28 of 136
Case-4: Harness Cluster, Cluster Priority, FG priority and number of CKT coming as defined in System.

Page 29 of 136
 No. of CKT (Harness)

Standard Time (Sec.)

Item Standard Time

(Sec.)

Case-5: Balance Month demand considering backlog and balance days demand.

Page 30 of 136
 Case-6: System suggested after considering On hand and Backlog.

Case-7: SYSTEM NOT ALLOWED changing less than 100 % of the system suggested plan. (Showing by POP UP window)

Page 31 of 136
Case-8: Validation Cases system not allowed before n days (n=3).

Case-9: System not allowed saving more than system suggested plan.

Page 32 of 136
Case-10:- Steps for checking the over-loading in Workbench during plan run. (Shown by RED Color in WB).

Step-1: - Custom Workbench showing overloading in Cluster no. – CV35

Step-2: - Standard WB for overloaded part as Shown In above Screen.

Page 33 of 136
Step-3: - GANTT Chart For Resource In which FG is Overloaded.
Open the ORACLE Login window & click on “Work-bench”:

Select UNIT form the LOV (Here P02 – for U6A):-

Page 34 of 136
Right Click on Assembly Plan, below window appears then click on “Resources”;

After filling all details (Criteria, Condition, from, etc) & click on FIND button:

Click on “FIND”
button.

Page 35 of 136
Below screen appears, and then click on Gantt chart button to see GANTT Charts:
(Here one thing to remember we have to select particular cluster to see Gantt chart, as Gantt charts used to see
the cluster’s over-loading.)

Click Here

Below is the screen of GANTT CHART: Then click on VIEW button, and select Resource – HOURS:

Page 36 of 136
 In Below Screen Resource Overload on 29 September for Resource CV35.

Step-4: - . FG part’s Whose Demand On 29th September 2014.

Page 37 of 136
Step-5:- To check Exception on FG coming on the 29th September 2014.

For FG YP532603 showing Exception that’s why Overload Red color is coming for FG on 29th September in Custom WB.

Step : 6: As there is no Overloading YP552603 so There is no exception for Part in Std WB and Also there is no Over
load red color in Custom WB.

Page 38 of 136
To See Demand against planned order by Supply & Demand:

Step1:- Click on Workbench.

Click on
“Workbench”.

Right click on
MSSL_Prod (Assembly
Plan)

Page 39 of 136
Step-2:- RIGHT CLICK ON PLAN, BELOW WINDOW WILL COME.

Click on “Supply
and Demand”.

Step-3:- Click on Supply and Demand.

Click on “Supply
and Demand”.

Click on “Supply
and Demand”.

Page 40 of 136
Step-4:- Below window will appear after clicking on supply and Demand.

Step-5:- Fill the yellow fields from LOV. Select “Item”.

Page 41 of 136
Step-6:- Here in second column select “EQUALS” from LOV.

Step-7:- Then in third column fill the Item for which you have to check Supply & Demand.

Page 42 of 136
Step-8:- Below reduction window will appear. Put the item code in reduction window.

Step-9:- Below window will appear.

Page 43 of 136
Step-10:- After filling all details, click on FIND button.

Page 44 of 136
Step-11:- BELOW WINDOW WILL APPEAR (showing all details), we can export schedule to excel also.

Page 45 of 136
Step-12:- To export in excel click on FILE & select EXPORT.

Here click on Continue to End button:

Page 46 of 136
EXCEL Exporting is in progress:

Page 47 of 136
Exporting is done in NOTEPAD, Select all and copy to excel for any editing and working:

EXCEL EXPORT OF PRODUCTION PLAN FROM CUSTOM WORKBENCH IN ASCP through EXPORT button:
Step 1 : In the CWB of PROD Plan shown below click on EXPORT button.

Page 48 of 136
Step-2 : After click on EXPORT radio button, below message appears to save the changes if any.

Step-3 : Then after click on OK in above, a request ID generates for the request done.

Page 49 of 136
Step-4 : Then to see the output, go to VIEW and click requests as shown below.

Click on FIND button to see the request status.

Page 50 of 136
Here in the below screen, the request ID status will appears for all requests done then after request phase –
completed shown here, click on View Output button.

Below screen showing click on View output button.

Page 51 of 136
Step-5 : After clicking on view output, below screen appears showing the output on Notepad.

This output form need to be change in CSV format to export in excel. Below steps to be followed.

Page 52 of 136
After assigning file name followed by “.CSV”, click on SAVE.

Page 53 of 136
Step – 6: Below is the output of Production Plan (ASCP) in excel format.

Page 54 of 136
To see the Supply and Demand Pegging:
Login to the ASCP (8002) Instance and right click on MSSL_PUR (Purchase) Plan from Plans:

Then click on Supply and Demand:

Page 55 of 136
Again click on Supply and Demand:

Below screen will appear, fill the required data in the blanks:

Page 56 of 136
Below screen will appear, fill the Item Code in the reduction criteria window and press OK:

Below screen showing the reduction window for Item Code – HSAB0502, and press OK:

Page 57 of 136
Below screen will appear, Click on FIND button & press OK:

Click on FIND
Button.

Below screen will appear, showing the Supply & Demand for the entered Item – HSAB0502:

User can check “Pegging” for the child

items under the Enter Item code from
here.

Page 58 of 136
To see the pegging for the child items under the entered Item – ZHSAB0502, Click on “Hide Dependent Demands” first.

Click on Hide Dependent Demands

After that click on “Hide Operation Resource”.

Click on Hide Operation Resource

Page 59 of 136
 Then click on “Supply Pegging” button:

Click on Supply Pegging

Then below screen appears:

Click Here
on “+” sign.

After click on “+” child items pegging will display

here it is showing the pegging of Ckt-
PIFQX001744 in SUBA – ZHSAB0502. Total Qty.
7480 of Ckt- PIFQX001744 is pegged in 4 planned
orders. (1790+2010+1950+1730 = 7480)

Page 60 of 136
Let us take another example for checking pegging:
Below report is showing the immediate parent of 12961533 is PIGSR000048; then we check pegging for Assembly –
12961533.

For checking the pegging of 12961533 we have to Check Pegging of Its Immediate Parent i.e PIGSR000048 under
SUBA ZHSAB0502 and then we have to go under pegging of immediate Parent.
In Below Screen pegging of Immediate Parent of 12961533 i.e PIGSR000048 is shown Under Suba Code
ZHSAB0502.

Click here on “+” sign to see the pegging of

12961533 under PIGSR000048.

Page 61 of 136
 Now For Pegging of 12961533 we have to drill down the pegging of immediate Parent i.e PIGSR000048(As shown
in Below Screen).
There are Two Planned Order of 12961533 are pegged under one planned order of immediate Parent i.e.
PIGSR000048 in below Screen.

After Click on “+” sign pegging of 12961533

open under PIGSR000048.

There is one Planned Order of 12961533 are pegged under one planned order of immediate Parent i.e.
PIGSR000048 in below Screen.

After Click on “+” sign pegging of 12961533

open under PIGSR000048.

Page 62 of 136
 There is one Planned Order of 12961533 are pegged under one planned order of immediate Parent i.e.
PIGSR000048 in below Screen.

After Click on “+” sign pegging of 12961533

open under PIGSR000048.

There is one Planned Order of 12961533 are pegged under one planned order of immediate Parent i.e.
PIGSR000048 in below Screen.

After Click on “+” sign pegging of 12961533

open under PIGSR000048.

{Note: - After checking the pegging of 12961533 under immediate parent i.e., PIGDR000048; for all 4 ckts as
shown above; The BOM qty. of 12961533 is 18080.44656 which is equal to the sum of planned order qty. of
12961533 in all 4 ckts. (i.e., 2565.839886+1615.867674+4858.51572+4326.73788+4713.4854= 18080.44656), that
means this is OK.}

Page 63 of 136
GANTT CHART
Open the ORACLE Login window & click on “Work-bench”:

Click Here

Select UNIT (P02 – for U6A):-

Select Unit
from here

Page 64 of 136
Below window will appear, from this window select plans (Assembly / LPC):

Right Click on Assembly Plan, below window appears then click on “Resources”;

Page 65 of 136
Below screen appears, fill the Yellow fields in below window (Yellow fields are mandatory):-

After filling all details (Criteria, Condition, from, etc) & click on FIND button:

Click on “FIND”
button.

Page 66 of 136
 Below screen appears, and then click on Gantt chart button to see GANTT Charts:
(Here one thing to remember we have to select particular cluster to see Gantt chart, as Gantt charts used to see
the cluster’s over-loading.)

Click
Here

Below is the screen of GANTT CHART:

Page 67 of 136
 Then click on VIEW button, and select Resource – HOURS:

Below is the result, here it is showing 3.1 HRS over-loading in Cluster CV00:

Page 68 of 136
LPC Work bench
Option Selection
Step-1:- Select Workbench option from ASCP module resp. menu.

Click here on Work Bench

Step-2:- Below screen will appear, and show the Plans. Select LPC Plan to view or to change and save.

Page 69 of 136
Step-3:- Right Click on LPC Plan (MSSL_MFG), Go to Custom PWB, Custom Planning Workbench.

Step-4:- Below is the LPC workbench.

Page 70 of 136
 Fill the req. details (Only I.O. code) & Press Query button.

Select
I.O.
(Unit)
from
here.

After filling the relevant data in blanks, below window will appear.

Page 71 of 136
Step-5:- Plan will be received in below format.

LPC Work Bench Parameter Details:-

Parameter Details
Inventory Organization This shows Inventory Org. for which work bench is opened
Plan Type This shows the plan type i.e. Assembly plan or LPC plan
Start Date This shows the date on which plan is run
Due Date This shows the last date of plan

Bal. Month Demand This will show total demand for the bal. month. (It Works on weekdays from 1st day
to last day)
Next Month Demand This will show total demand for the next month.
Buffer Days This will show harness buffer days which was defined in source.
Club Days This will show Harness Club Days which was defined in source
FG Assy Capacity This will show the time in which one harness can processed in Assembly
FG LPC Capacity This will show the time in which one harness can processed in LPC
Alternate Cluster This will show the alternate cluster if defined
FG Stock This will show the stock for the particular FG Code.
Pre FG Stock This will show the Pre FG stock for the particular FG Code
Open Job Order qty. LPC This will show open work order qty. for LPC.
Open Job Order qty. Assy This will show open work order qty. for LPC.
Harness Cluster This will show the Harness Cluster

Page 72 of 136
 Cluster Priority This will show the Cluster Priority
FG Priority This will show the Harness (FG) Priority
No. of Ckts This will show details of Harness Ckts
Total Demand Load (Ckts) This will show total Ckt load as per demand
Total Demand Load (C/O) This will show total Change Over (C/O) load as per demand
Total Suggested Load (Ckts) This will show total system suggested Ckt load
Total Suggested Load (C/O) This will show total system suggested Change Over load
Total Actual Plan (Ckts) This will show total actual planned Ckts
Total Actual Plan (C/O) This will show total actual planned Change Over
FG Code This will show End FG Code (Harness Code)
SUBA Code This will show SUBA Code w.r.t. FG Code (Harness Code)
Backlog Qty. This will show the qty. which is not produced before the plan run date.

Editing/Modification on Final LPC Plan

Step-8:- User can edit/modify the system suggested plan if req. User can change the qty., pre pone or
Postpone the system suggested plan in white colored line and then after modification press the
Save button and this plan will be saved as a final actual plan. On the basis of this final actual
Plan Child Part Plan (Purchase Plan) will be run next day of LPC Plan.

Page 73 of 136
WORK ORDER CREATION THROUGH ASCP INSTANCE (Custom Release Set) :-

Step-1:- Login to the ASCP Instance & select workbench from Supply Chain Plan.

Click on workbench.

Step-2:- After selecting Workbench in ASCP Instance, Run a request. Click on “VIEW” and go to Requests.

Page 74 of 136
Click on Submit a New
Request button – to
submit a new request.

Click on “OK”
button

Page 75 of 136
Step-3:- From request select “Custom Release with Parent Update” option and press OK.

Page 76 of 136
Step-4:- After selecting “Custom Release With Parent Update” option from request window; below screen appears
and here fill all details and press OK.

Fill all the entries in this window:--

Page 77 of 136
Zoom view of window, fill all the entries and press OK.
Enter Org. (Unit)

Enter SUBA Code

Enter Date as
per format.

After entering all

blanks and then
press OK.

Page 78 of 136
By this program we can create WO for single FG code OR for all FG for that particular Unit. ORG. Name

Below is the print screen for Creating WO for Single FG:-

SUBA Code

Date Format.

Below is the print screen for Creating WO for All FG for that particular Unit:-

Note: In date Format month should be first three letters and Letters Should be in Capital letters otherwise the
request will not be completed.

ORG. Name
Do not enter
SUBA Code.

Date Format.

Page 79 of 136
Step-4:- After selecting the one from above two options of WO create press OK.

Submit request and see the output.

Details of Parameters entered
are showing here.

Click on Submit button

Step-5 :- After click on Submit button, below window will appear and a request ID Number generated for that
submission in Decision window.

Click on “NO”

Page 80 of 136
After click on “No” in Decision window, we have to press FIND button :-

Click on FIND
Button for seeing
the output.

Below window is showing the Request ID number status.

Below Window is showing that the Output request is running for “Custom Release with Parent Update”.

Page 81 of 136
The output of this request is ZERO and this is because this shows the data has been shifted in Other instance
(Source – SIT), then we have to login in Source Instance (8000) and just after completion of WO Creation program
in ASCP Instance there is another request will RUN in SIT Instance i.e., WIP Mass Load.

Request Status is showing –

Completed.

After completion of request, click on “View Output”.

Click on View Output, to

see the result. Click on View Log, to see
Click on View Details, to the LOG file in case of
see request details. error.

Page 82 of 136
Below screen showing the LOG File for a request through VIEW LOG option.

Page 83 of 136
 Step-6:- LOGIN TO PRODUCTION INSTANCE

Step-7:- After LOGIN to Source (8000) Instance, view the request which is automatically runs after Custom Release
Set request completed in ASCP (8002) Instance.

Click on
Request
in View
option

Page 84 of 136
Step-8:- After click on request, below window will appear.

Click on FIND button to see the

request.

Step-9:- Below is the screen showing WIP Mass Load Completed in Source Instance.

To View Output,
click here.

Page 85 of 136
 Step-10:- Below screen is showing the output of WIP Mass Load. Here it is showing the Job Orders Created
Successfully for FG with SUBA and Childs automatically according to the date selected in Custom Release Set in AS

FG WO
created

SUBA
WO
created

This block is showing that Joint

Ckts, Ckts, Composite Ckts Work
Message showing in output Order (WO) created.
that job successfully
completed.

Page 86 of 136
Sub-Inventory Transfer

Production Slip (Sub-Inventory Transfer) from MM0PF to FG001:

 After completing production cycle or backflush, the stock of FG/Item will come in MM0PF location and
then this stock has to be transfer to FG001 location to Sale/Dispatch.

Below screen showing On-Hand stock for FG Code – JD130200, Qty. = 100 in PF001.

Login to Source Instance for Production Slip (Sub-Inventory transfer):

Page 87 of 136
Select ORG from LOV:

Below window will appear, showing the Sub-Inv.:

Page 88 of 136
Click on Transact Lines:

Below WINDOW WILL APPEAR: showing stock = 100 available in PF001;

From this window we can transfer stock from PF001 to FG001:

Page 89 of 136
After transferring stock from PF001 to FG001 (i.e., Production Slip)
Stock will transferred, we can check the transferred stock from POH (Physical on-hand details option):
As shown in below screens – Before POH details & After POH details.

Before After

Page 90 of 136
IR (Internal Requisition) Steps:-
Step-1:- Select Prod (Assembly Plan) from resp. menu.

Step-2:- Below screen will be appeared, and shows the ASCP IR suggestion. Select the FG Code for which IR need to
be created.

Page 91 of 136
To Check Source Unit Click on Sourcing It will show from Which Unit Item Will be Buy.

Step-3:-Go to Plan tab and select Release option .

Page 92 of 136
Step-4:- Below screen will be appeared, Press ok button.

Step-5:- Below screen will appear.

Page 93 of 136
Check the Release IR from ASCP.
Step-6:- Select Purchasing PR Creator User resp. from resp. menu in source instance.

Step-7:- Select Requisition Summary.

Page 94 of 136
Step-8:- Below screen will be appeared.

Step-9:- Go to import source and open the LOV.

Page 95 of 136
Step-10:- Select MSC from LOV.

Step-11:- Below screen will appear, press Find button.

Page 96 of 136
Step-12:- All Released IR will be appeared in below screen. Click on line for which details need to be checked.

Step-13:- Details will be appeared for selected Line IR.

Page 97 of 136
Create Internal Order:-
Step-14:- Run the new request to create internal orders for any approved IR.

Click on Create Internal

Order from request form.

Step-15:- Press Submit button.

Page 98 of 136
Step-16:- Press Ok button.

Now, Internal Order has been created.

To Check DFF for the Buy Item In Source ORG.
Go to Prod. Responsibility of Source Org.

Production Responsibility

Page 99 of 136
Click on View Discrete Job

Click on “View Discrete Job”

option.

Select Org. from LOV.

Page 100 of 136

Enter FG Code in Assembly.

Click on FIND

Click on Open Button to check particular Job code.

Click on OPEN
button.

Page 101 of 136

Click On DFF (Descriptive Flag Field).
Click on DFF
button.

DFF Detail as shown in below screen.

Parent Job
Code

Parent FG/Suba same

I/O.

GCNC Status for

that Job No.

MRS Qty.
After updating DFF click on OK.

Page 102 of 136

Steps for DS releasing for Group Companies (like MSEW/SMIEL/APD)-- Wire plans through ASCP:

We can release demand for wire through ASCP instance in Oracle after Purchase Plan completed. First login to ASCP
window and then follow the below steps.

Release purchase order for MSEW/SMIL/APD following below steps.

Step – 1: After login in ASCP click on Workbench from Planner User responsibility, then select Purchase Plan from Plans, then
right click then go to supply and demand.

Page 103 of 136

Step – 2: Again right click then go to supply and demand.

Page 104 of 136

Step – 3: After click on Supply and Demand, below screen appears, then fill all details like criteria - Supplier, condition – Equals,
then select Supplier name from the LOV (List of Values).

Page 105 of 136

Zoom view of Supply/Demand window:-

Below screen showing reduction criteria selected to release DS for Group Company(MSEW) recommended by ASCP
Purchase Plan:- Here date range will be selected as per agreed rules.

Page 106 of 136

Step – 4: After Supplier name from the LOV (List of Values) i.e., Motherson Sumi Electric Wires Ltd., then below screen appears
with all the wires demand through purchase plan run in ASCP.

Below screen is showing all information related to wires demand from Supplier Named - MSEW.

Step – 5: If we want to release DS for wire then click on For Release then save. After save that particular planned order we
have released and Action Change to from release to none.

As shown in below screen.

Page 107 of 136

Step – 6: If we want to check where this wire demand come from of against which planned order demand then we can see this
through Pegging.

As shown in below screen.

We can also release DS for RM Items likewise. (After PURCHASE PLAN RUN COMPLETES).

Below are the steps shown, here we select Asian Rubber as Supplier.

Page 108 of 136

All RM Items for supplier – Asian Rubber are shown in below screen. Select an item and save.

Below screen showing SAVE after selecting an item.

Page 109 of 136

After SAVE this row for which DS release will become PINK in color, showing that DS released for this item against
this planned order.

PR Release from ASCP for MSEW/SMIEL/APD and SPO Creation & Approval
Step-1: Below screen showing the selection criterial for MSEW in ASCP Standard Workbench.

Page 110 of 136

Step-2: Then Go To Plan and Select All for Release.

Step-3: Below screen appears showing all selected RM’s with PINK color. Click at OK at pop up note.

Page 111 of 136

Step-4: Below screen appears.

Step-5: Then Go to Plan and Release the selected RM Items.

Page 112 of 136

Step-6: Below screen appears, press OK to save and proceed.

Below screen showing Requisition Number that fire from ASCP to Production Instance.

Here click on OK.

Note: Now ACSP Instance work finish. User has to login in PRODUCTION Instance.

Page 113 of 136

Production Instance

Step-7: Login to Production Instance and Go to Purchase User responsibility.

Then GO TO Oracle Purchasing under Purchase User Responsibility.

Page 114 of 136

Then Go To Requisition under Oracle Purchasing Responsibility.

Below screen appears from “Requisitions” under Oracle Purchasing Resp.

Page 115 of 136

Step-8: Below screen appears, Go to View and select Requests.

Step-9: Below screen appears, showing Requisition Import status came from ASCP to Production Instance in MSC
Table. Here request import showing the same number that showed in ASCP.

Page 116 of 136

Below screen showing ASCP request number.

Note: Above steps are just to check whether request fire from ASCP will Imported to Production Instance.

Step-10: Then select Requisition Summary option under Requisition under Oracle Purchasing in Purchase User
Responsibility.

Page 117 of 136

Click on Requisition under Oracle Purchasing.

Then click on Requisition Summary under Requisition.

Page 118 of 136

Step-11: Below form opens, then press List of Values (LOV) at Import Source.

Click on LOV in
Import Source

Step-12: LOV opens then select MSC and press OK.

Page 119 of 136

Step-13: Then enter Date Range, for which user want to see PO number. And then press FIND (B) button.

Date range to
be enter here

Then Click
Here

Step-14: Below screen appears, showing PR number. PR released from ASCP is always in Approved status.

Page 120 of 136

Below screen appears

PR Number

Step-15: By sliding to the right side, user can get showing PO number against PR number.

PO Number

Page 121 of 136

Standard Purchase Order (SPO) Creation

Step-16: For SPO creations go to “PO Summary (Localized)” option under Purchase User Resp.

Step-17: Below screen appears. Now enter PO Number or select from LOV.

Enter PO number
here.

Page 122 of 136

Step-18: Below screen showing PO number LOV. Select PO number then press OK.

Step-19: Below screen showing, press FIND button.

Click on
FIND

Page 123 of 136

Step-20: Below screen showing, press OPEN button to open PO.

Click on
OPEN

Step-21: After pressing Open button, below screen appears. Here in SPO form all fields filled automatically. No
need to fill any data. Only we need to press Approve button to send this SPO to next level of Approval (i.e. Process
Owner).

Click on
Approve

Page 124 of 136

Step-22: Below screen appears. Click on Forward to select Approval path and send notification mail. Then press OK.

Select
Forward

Step-23: Below screen appears, and then select SPO Hierarchy of your respective Org. from LOV.

Page 125 of 136

Step-24: Below screen appears, showing Approval Path and Forward to (i.e., Process Owner).

Step-25: Then click on OK button to complete the loop.

Click OK

Page 126 of 136

Step-26: Below screen showing - Mail Notification for SPO number – 1004001666.

Notification mail fires as soon as SPO Approve by Unit Buyer, and showing Action required by Process Owner.

LOGIN to Approver

Step-27: Below screen appears, here Worklist is showing SPO submitted by Unit Buyer for PO Approval.

SPO No. – 1004001666 is

showing in Approver’s Work
List.

Page 127 of 136

Step-28: Below screen appears after click in Worklist of SPO by Approver. Here approver will give decision.

`Approver can Approve / Reject.

Step-29: Below screen showing, Approver’s decision.

SPO is Approve by
Approver by
clicking here

Page 128 of 136

Notification mail fires after SPO Approve by the Approver (Process Owner).

Step-30: Mail Notification shows for SPO number – 1004001666 in below screen.

Page 129 of 136

Steps to RUN request

Step 31: After SPO is approved by Process Owner, Unit Buyer has to run a request from Purchase User
Responsibility, Request name as “XXMSSL: PO Communicate to Supplier (Forecast for Weekly Schedule) - CEMLI
17”.

Note: The purpose of this request is to send Data file through system at Supplier’s system. This is mandatory to
RUN this request in case of Manual DS and Auto DS Release (From ASCP_Purchase Plan) for Group Companies
(MSEW/SMIEL/APD), otherwise supplier will not be able to upload SPO information at their end.

Steps to Run “XXMSSL: PO Communicate to Supplier (Forecast for Weekly Schedule) - CEMLI 17” are as follows:

Step A: Click on “View” from Purchase User Responsibility. And then select Request, as shown below.

Click here

Step B: Below screen appears. Click on “Submit a New Request” button.

Click here

Page 130 of 136

Step C: Below screen appears. Click on “OK” button.

Click here

Step D: Below screen appears. Then select report from LOV.

Page 131 of 136

User can also select request name using below reduction criteria.

Step E: Below screen appears. Now enter Input Parameters to run the request.

Select Operating Unit from LOV (List of Values).

Click here to see

LOV

Page 132 of 136

Below screen showing Operating Unit’s LOV. Select Unit from here.

Below screen showing Supplier’s LOV. Select Supplier Name from here.

Page 133 of 136

Below screen showing Supplier Site’s LOV. Select Supplier Site from here.

Below screen showing PO Number’s LOV. Select PO Number from here.

Page 134 of 136

Step F: Below screen appears. After entering all input parameters then “Submit” and then click on “No”.

Then click
“NO”

First click on
“SUBMIT”

Step G: Below screen appears. Then click on “FIND” button to see submit request status.

First click on
“FIND”

Page 135 of 136

Step H: Below screen appears. Showing the request status as “Normal” and Phase as “Completed”, which means
request completed successfully.

Page 136 of 136