Tata Consultancy Services: Doosan Weekend Job Run Book

TATA CONSULTANCY SERVICES
Doosan Weekend Job Run Book

2 Doosan Weekend Job Run Book
Table of Contents
1. Un scheduling the GWN Orders ................................................................ 3
2.1 Copy Merge Forecast Program for Source-PCT_EMPTY .................................. 5
2. 2 Copy Merge Forecast Program for Source-PCT_LS .................................................... 7
3. Load/Copy/Merge MDS Program for Organization PCT .................... 9
4. Copy/Merge Forecast Programs for Organization GWN ................... 10
4. 1 DICE Empty Gwinner Demand Classes Forecast ..................................................... 10
4. 2 DICE Load Gwinner Demand Classes Forecast ........................................................ 12
5. DICE Populate Forecast Data for Manual ATP (JOB-0092) .................. 14
6. Rescheduling Of the GWN Programs ..................................................... 16
6. 1 Rescheduling Orders for demand class-AP ............................................................... 17
7. DICE OSS Arrival Date Update(JOB-0102): ........................................................ 18
8. 1 MDS Program for Organization: BCA ........................................................................ 19
8. 2 MDS Program for Organization: BIM ......................................................................... 21
8.3 Load/Copy/Merge Programs for Organization GWN ............................................. 22
9. Data Collection .................................................................................................................................... 23
10. Launch and Push Plan Programs.................................................................................................... 27
10. 1 Push Plan Program for LEG:STA .............................................................................. 27
10. 2 Launch Supply Chain Planning Program for LEG: BIM ........................................ 29
10. 3 Push Plan Program for LEG: BIM .............................................................................. 29
10. 4 Launch Supply Chain Planning Program for LEG: PCT ........................................ 30
10. 5 Push Plan Program for LEG: PCT ............................................................................. 31
10. 6 Launch Supply Chain Planning Program for LEG: BCM....................................... 31
10. 7 Push Plan Program for LEG: BCM ............................................................................ 32
11. DICE Release Concurrent Programs ............................................................................................... 33
11. 1 DICE Release Concurrent program on Hold (EXT-0063) ....................................... 33
10. 2 DICE Release Concurrent program on Hold (EXT-0063) ....................................... 34
12. SQL Queries ........................................................................................................................................ 35
13. Issues Faced During Weekend Planning Run ................................................................................ 42
13.1 Push Plan Issues ............................................................................................................ 42
22.2 Refresh Collection Snapshot Failure: ......................................................................... 43
13.3 Data Collection Failure: ............................................................................................... 44
Shift Timings
We should always consider shift timings of ‘Assembly’ and should not consider ‘Welding’
3RD Shift in Assembly will be from 11PM Friday (CST) – 7 AM Saturday (CST)
1st Shift in Assembly is from 7AM Saturday (CST) – 3 PM Saturday (CST)

1. Un scheduling the GWN Orders
nd
2 Shift in Assembly is from 3PM Saturday (CST) – 11 PM Saturday (CST)
For un-scheduling GWN sales order, we need to submit only one ‘DICE Reschedule Ship-From-Org (JOB-
0038)’ program will thread count as 15 (as of now, it can be changed later based on the planning manager
performance):
Instance DNAPROD(P1)
Responsibility SRC Weekend Planning User All (Bobcat)
Path Supply chain planning Others Change

OrganizationSelect GWN
Steps:
1. Click on Submit a New Request.
2. Enter the Job Name - DICE Reschedule Ship-From-Org (JOB-0038)
3. Enter the Parameter as follows (mentioned in the excel sheetScheduling Rules B (tab) )
a. Ship from Org Id-GWN

b. Unschedule only = Yes
c. Item= Null
d. Include Overridden SSD= Yes
e. Resequence Method=FIFO_SEQ_NUM
f. OM Item Type Code=Model
g. Threads = 15
4. Click OK
5. Click Submit
6. Note down the Request Id of the program in the excel sheet against the respective Program name.
PLANNING MANAGER RECORES
select process_status, count(*)

from mrp_so_lines_temp
group by process_status;
Check the number of orders against the Item Model using the below query .
--GWN MODELS -- SCHEDULE STATUS BY MODEL/DEMAND CLASS

SELECT demand_class_code, alloc_model, Schedule_status_code, COUNT(*) FROM
xxom_alc_unsched_orders_v
WHERE organization_id = 106
and demand_class_code = 'AMR1'
--and Schedule_status_code is null
--and Schedule_status_code is not null
GROUP BY demand_class_code, alloc_model, Schedule_status_code
order by alloc_model;
When the GWN un-scheduling is running, we can run the below programs:
Copy Merge Forecast Programs for Organization PCT
2.1 Copy Merge Forecast Program for Source-PCT_EMPTY
Responsibility SRC Weekend Planning User PCT (Bobcat)

OrganizationSelect PCT
Steps:
1. Click Supply chain Planning
2. Click Forecast
3. Click Copy
4. Enter the parameters as mentioned in the excel sheet.
5. Enter the Start date and End date from parameters tab in excel sheet under Forecast Copy section
against PCT_EMPTY.
6. Click Ok
7. Click Submit
8. Note down the Request Id
Verification:
Path:
Supply chain planning->Forecast->View sets
Press F11( Query mode) in Forecast set give PCT_CON_ST and ctrl+F11. Click on forecast items select
second item click on detail. Make sure its empty.
Note: Copy/Merge Forecast programs for PCT should be run sequentially i. e. Only after the
completion of current program, execute the next one.
2. 2 Copy Merge Forecast Program for Source-PCT_LS

Steps:
In the same Responsibility
2. Click Forecast
3. Click Copy
5. Enter the Start date and End date from parameters tab in excel sheet under Forecast Copysection
against PCT_LS
6. Click Ok
7. Click Submit

Verification:
Path:
Supply chain planning->Forecast->View sets
Press F11( Query mode) IN Forecast set give PCT_CON_ST and ctrl+F11. Click on forecast items. Enter
in query mode give M2% in item and ctrl+F11 then click on detail make sure all the dates are within the
end date as given in excel sheet.
--FORECAST VIEWS -- CHANGE ORGANIZATION_ID TO APPROPRIATE ORG

SELECT FD. ORGANIZATION_ID,
FD. FORECAST_DESIGNATOR,
FD. SOURCE_FORECAST_DESIGNATOR,
Sum(FD. CURRENT_FORECAST_QUANTITY) CURRENTQTY,
SUM(FD. ORIGINAL_FORECAST_QUANTITY) ORIGINALQTY,
SUM(FD. ORIGINAL_FORECAST_QUANTITY - FD. CURRENT_FORECAST_QUANTITY)
CONSUMEDQTY
FROM MRP_FORECAST_DATES_V FD
WHERE FD. ORGANIZATION_ID = 446
AND FD. FORECAST_DESIGNATOR not like 'SIOP%'
Group By
FD. ORGANIZATION_ID,
FD. SOURCE_FORECAST_DESIGNATOR
order by FD. ORGANIZATION_ID, FD. FORECAST_DESIGNATOR;
Explanation:
After running the program the Current Quantity and the Original Quantity should be equal (in the
snapshot below)
Note: After the completion of the above program, you can execute Load/Copy/Merge for PCT
organization
3. Load/Copy/Merge MDS Program for Organization PCT

Steps:
In the same responsibility
1. Click on Supply Chain Planning
2. Click on MDS
3. Click on LOAD/COPY/MERGE
4. Enter the Parameters entered in the excel sheet.
5. Enter the start date and end date from the parameters tab in the excel sheet from the MDS
ASCPsection against PCT organization
6. Click Ok
7. Click Submit

9. Click on the View Details tab and note down the start and end time of the program in the excel sheet.
4. Copy/Merge Forecast Programs for Organization GWN
4. 1 DICE Empty Gwinner Demand Classes Forecast

Steps:
1. Go to Toolbar
2. Click on View
3. Select Requests
4. Click on Submit a New Request
5. Select Request Set
6. Enter the Job Name as mentioned in the excel sheet
7. Clicking on every row (Parameters tab), default parameters are populated.
8. Click ok.
9. Click Submit
Validation:
After running above program, please run below query by giving dates as mentioned in parameter tab of
weekend excel for copy forecast.
After running this query, you should not be able to see forecast designator (AMR1_CN_FC / AP_CN_FC
/ EMEA_CN_FC/ OCN_CN_FC/ EXPD_CN_FC /NAGS_CN_FC/ CHN_CN_FC) – if you don’t see
these forecast designators, which means it is fine.

FD. SOURCE_ORGANIZATION_CODE,

CONSUMEDQTY
AND FD. FORECAST_DATE >= '10-jul-2013' ------enter the default dates
AND FD. FORECAST_DATE < '31-JUL-2014' ------enter the default dates
Group By
FD. SOURCE_ORGANIZATION_CODE
4. 2 DICE Load Gwinner Demand Classes Forecast

Steps:
1. Go to Toolbar
2. Click on View
3. Select Requests
6. Enter the Job Name as mentioned in the excel sheet
7. Clicking on every row (Parameters tab), default parameters are populated.
8. Enter the start date and end from the excel sheet in the Parameters tab from the Forecast / Copy
section against GWN for every demand class.
9. Click ok.
10. Click Submit
11. Note down the Request ID.
Validation:
After running above program, please run below query by giving dates as mentioned in parameter tab of
weekend excel for copy forecast.
After running this query, you should be able to see forecast designator (AMR1_CN_FC / AP_CN_FC /
EMEA_CN_FC/ OCN_CN_FC/ EXPD_CN_FC /NAGS_CN_FC/ CHN_CN_FC) and if you don’t see
even anyone of these that means we have an issue with the program parameters or program run.
Also, original quantity and current quantity should match.

FD. SOURCE_ORGANIZATION_CODE,
CONSUMEDQTY
AND FD. FORECAST_DATE >= '10-jul-2013'—--enter the dates from excel sheet
AND FD. FORECAST_DATE < '31-JUL-2014' —--enter the dates from excel sheet
Group By
FD. SOURCE_ORGANIZATION_CODE
5. DICE Populate Forecast Data for Manual ATP (JOB-0092)

Steps:
1. Go to Toolbar
2. Click on View
3. Select Requests
5. Select Single Request
6. Enter the Program Name - DICE Populate Forecast Data for Manual ATP (JOB-0092)
7. Enter the parameter from the excel sheet (Org- GWN)
8. Click Ok
9. Click Submit
10. Note down the Request Id of the program in the excel sheet against the respective Program
name.
Once program “DICE Populate Forecast Data for Manual ATP (JOB-0092)”, gets completed, please run
below query to check quickly whether data is copied to “xxit_fc_item_qty” table. If we see data for all
forecast designators that means program worked the way it is intended to:
Selectorganization_id,forecast_designator,count(*)fromxxit_fc_item_qtygroupbyorganization_id,forecast
_designatororderbyorganization_id,forecast_designator;
--ATP Custom Table Counts by FC Name
selectorganization_id,
forecast_designator,
sum(original_forecast_quantity)Orig,
sum(current_forecast_quantity)Curr
fromxxit_fc_item_qty
groupbyorganization_id,
forecast_designator
orderbyorganization_id,
forecast_designator;
6. Rescheduling Of the GWN Programs

Note: For re-scheduling the GWN sales orders, keep the thread count as 1.
1. When Rescheduling, submit 8-10 programs at a time and check the Process count using the below
mentioned query.
PLANNING MANAGER RECORES

2. You can execute the Rescheduling programs in parallel
3. For Process Status=2, Count should be maintained below 10,000.

Steps:
1. Click on Submit a New Request.
2. Enter the Job Name - DICE Reschedule Ship-From-Org (JOB-0038)
3. Enter the Parameter as follows (mentioned in the excel sheetScheduling Rules B (tab) )
6. 1 Rescheduling Orders for demand class-AP
a. Ship from Org Id-GWN
b. Unschedule Only = No
c. Item= Null
d. Include Overridden SSD= Yes
e. Resequence Method=FIFO_SEQ_NUM
f. OM Item Type Code=Model
g. Demand Class=AP
h. Threads = 1
4. Click OK
5. Click Submit
Run the above program each time for various demand class like EMEA, Oceania, NAGS, EXP, China
and AMR1 orders as below:
Note:
1. Run for all the items (Check scheduling rules tab) provided in excel sheet and make sure all
the orders are properly rescheduled.
2. Check the query GWN Models -- Schedule Status by Model/Demand Class -- use to monitor
AMR1 demand class unschedule/reschedule to make sure all the orders are scheduled
properly.
3. When we start running Unscheduling/Rescheduling programs we have a query planning
manager records keep monitoring it and make sure that process status is not exceeding 10,000.
4. When Rescheduling has completed, check the forecast query for gwn.
If the consumption shown is less than number of rescheduled orders then run
Overconsumption query given below:
select sum(current_forecast_quantity)
from MRP_FORECAST_dates_v
where forecast_designator='GWN_CON_ST'
and last_update_date>= '06-Jul-2013'
and origination_type_desc ='Overconsumption'
The output of the above query should match the difference between scheduled sales order and
the forecast consumption.
7. DICE OSS Arrival Date Update(JOB-0102):

Once GWN re-scheduling is completed, we can run the DICE OSS Arrival Date
Update(JOB-0102), it does not need any input parameter.
8. MDS Programs for Organizations BCA, BIM, BMK, CAR, WHP and GWN
8. 1 MDS Program for Organization: BCA


OrganizationSelect BCA
Steps:
2. Click MDS
3. Click Load/Copy/Merge
5. Enter the Start date and End date from parameters under MDS ASCPsection for BCA organization
6. Click Ok
7. Click Submit
9. Click on the View Details tab and note down the start and end time of the program in the excel sheet
Note: Only after the completion of above program, execute the next program.
8. 2 MDS Program for Organization: BIM

OrganizationSelect BIM
Steps:
2. Click MDS
5. Enter the Start date and End date from parameters under MDS ASCPsection for BIM organization
6. Click Ok
7. Click Submit
Note: Once the above program is completed, execute the next program.
Similarly execute the MDS programs for the orgs and for GWN MDS,
Note:
Before executing Load/Copy/Merge for GWN, make sure
1. Rescheduling of GWN programs should be complete.

2. Check the Gwinner shift timings.
8.3 Load/Copy/Merge Programs for Organization GWN

Note: This Program should be executed after the GWN shift is completed.
For example GWN are working in 3rd shift (Friday 11PM-Saturday 7AM (CST)), then the program
should be executed after Saturday 7AM (CST).

Steps:
2. Click MDS
5. Enter the Start date and End date from parameters under MDS ASCPsection for GWN organization
6. Click Ok
7. Click Submit
9. Data Collection
Instance DNAASCPP(O1)
Responsibility Advanced Supply Chain Planner
Path Click on Supply chain planning->Others->Click on

Change the Organization and select LEG: STA and
click ok.
Steps:
1. Go to Toolbar
2. Click on View
3. Select Requests

6. Enter Program Name-ASCP Port Pwr Daily Request Set
7. Enter Parameters mentioned in the excel sheet (sales order as Yes)
Job 36. 1 Planning Data Pull
a. Enter Number of Workers and Sales Order( Special Parameters in excel sheet)
b. Click Ok.
Job 36. 2 Planning ODS Load
a. Enter Number of Workers (Special Parameters in the excel sheet)
b. Click Ok.
Job 36. 3 Launch Supply Chain Planning Process
a. Enter Plan Name (Dest column in the excel sheet)
b. Click Ok
8. Click Submit
9. Note down the Request id of the programs in the excel sheet.
10. Enter the Start time and the End time of the programs as mentioned below in the excel sheet.
Program Name Start time End Time

ASCP Port Pwr Daily Request Set ASCP Port Pwr Daily Request Set Analyze Plan Partition
Planning Data Pull Planning Data Pull Program before Planning ODS
Load
Planning ODS Load Planning ODS Load Program before Launch Supply
Chain Planning Process
Launch Supply Chain Planning Launch Supply Chain Planning Analyze Plan Partition
Process Process
Note: After Completion of the above data collection
1. You can execute the next Program (Push Plan) in the same instance (O1).
10. Launch and Push Plan Programs

Note: 1. Launch and Push Program of the same organization should not be run in parallel.
2. Two Launch Plans of different organization should not be run in parallel.
3. Two Push Plans of different organization should not be run in parallel.
4. Launch plan and Push Plan of two different organizations should be run in parallel.
5. For the Push Plan programs make sure that the Horizontal Start Date and Horizontal End Dates
should have no value.
6. Run the below query after completion of each Launch supply program and check for the updated
dates in the output
select compile_designator, last_update_date from MSC_PLANS
where compile_designator in
('BCM_WKEND','BCM_ATT','PCTWEKEND','BCM_MIDWK','PP_WKEND')
10. 1 Push Plan Program for LEG:STA

Steps:
In the same responsibility and organization
1. Click on submit a new request
2. Click on single request
3. Enter Program Name-Push Plan Information
4. Enter the Parameter mentioned in the excel sheet

Push Plan (Org- LEG: STA)
a. Enter Plan Type (Special parameters column in the excel sheet)
b. Enter Plan Name (Dest column in the excel sheet)
5. Click Ok.
6. Click Submit
7. Note down the Request id, Start time & End Time in the excel sheet against the respective
program.
You can run the Launch Plan Program of different organization in parallel with the above Push
Plan program.
10. 2 Launch Supply Chain Planning Program for LEG: BIM


Change the Organization and select LEG: BIM and
click ok.
Steps:
1. Click Supply Chain Plan
2. Click Launch
3. Enter the Program Name-Launch Supply Chain Planning Process
4. Enter the parameters mentioned in the excel sheet.
b. Click Ok
5. Click Submit
6. Enter the Request Id in the excel sheet against the respective Program.
7. Enter the Start Time and End time as mentioned below

Process Process
10. 3 Push Plan Program for LEG: BIM
Steps:

5. a. Enter Plan Type (Special parameters column in the excel sheet)
6. Click Ok.
7. Click Submit
8. Note down the Request id, Start time & End Time in the excel sheet against therespective program.
10. 4 Launch Supply Chain Planning Program for LEG: PCT

Change the Organization and select LEG: PCT and
click ok.
Steps:
2. Click Launch
b. Click Ok
5. Click Submit

Process Process
10. 5 Push Plan Program for LEG: PCT
Steps:
6. Click Ok.
7. Click Submit
8. Note down the Request id, Start time & End Time in the excel sheet against the respective program.
Note:
Similarly we need to launch the BCM_WKEND plan and push plan information program after the
BCM_WKEND plan gets completed.
10. 6 Launch Supply Chain Planning Program for LEG: BCM

Change the Organization and select LEG: BCM and
click ok.
Steps:
2. Click Launch
b. Click Ok
5. Click Submit

Process Process
10. 7 Push Plan Program for LEG: BCM
Steps:
6. Click Ok.
7. Click Submit
8. Note down the Request id, Start time & End Time in the excel sheet against the respective program.
11. DICE Release Concurrent Programs
11. 1 DICE Release Concurrent program on Hold (EXT-0063)

Steps:
1. Go to Toolbar
2. Click on View
3. Select Requests
5. Enter the Job Name - DICE Release Concurrent program on Hold (EXT-0063)
6. Enter the Request Id(parameters tab in excel sheet)mentionedunderPlanning Parameterssection

against the Program in the parameters field.
7. Click OK
8. Click Submit
Note: Once the above program completes, execute the next program
10. 2 DICE Release Concurrent program on Hold (EXT-0063)

Steps:

2. Select Single Request
3. Enter the Job Name-DICE Release Concurrent program on Hold (EXT-0063)
4. Enter the Request Id(parameters tab in excel sheet)mentionedunderPlanning Parameterssection

against the Program in the parameters field.
8. Click OK
9. Click Submit
12. SQL Queries

SQL QUERY :
--LIST OF ORG ID AND ORG CODE
SELECT * FROM ORG_ORGANIZATION_DEFINITIONS where organization_id in

(105,106,124,244,284,446,607,631,687,867) order by 1;
--PLANNING MANAGER RECORES

--GWN MODELS -- SCHEDULE STATUS BY DEMAND CLASS
SELECT Demand_class_code, Schedule_status_code, COUNT(*) FROM xxom_alc_unsched_orders_v

WHERE organization_id = 106 GROUP BY demand_class_code, Schedule_status_code order by
demand_class_code;
--GWN MODELS -- SCHEDULE STATUS BY MODEL/DEMAND CLASS
SELECT demand_class_code, alloc_model, Schedule_status_code, COUNT(*) FROM

xxom_alc_unsched_orders_v
and demand_class_code = 'AMR1'
--and Schedule_status_code is null
--and Schedule_status_code is not null
GROUP BY demand_class_code, alloc_model, Schedule_status_code
order by alloc_model;
--GWN MODELS -- ORDERS DETAILED VIEW
SELECT * FROM xxom_alc_unsched_orders_v

--and alloc_model = 'S205'
--and schedule_ship_date is not null
--and schedule_ship_date is null
--and demand_class_code = 'EXPD'
ORDER BY schedule_ship_date, ordered_date;
--GWN STANDARD ITEMS -- SCHEDULE STATUS
select
ola. schedule_status_code, msi. item_Type, ola. item_type_Code, ola. visible_demand_Flag, oha.
attribute14,
msi. atp_flag, ola. override_atp_date_code OVATP, sum(ola. ordered_quantity)
from oe_order_lines_allola,
oe_order_headers_alloha,
mtl_system_items_bmsi
where msi. inventory_item_id = ola. inventory_item_id
and msi. organization_id = ola. ship_from_org_id
and oha. header_id = ola. header_id
and ola. ship_from_org_id = 106
and ola. open_flag = 'Y'
and ola. booked_flag = 'Y'

and ola. cancelled_flag = 'N'
and (ola. visible_demand_flag = 'Y' or ola. visible_demand_flag is null)
and msi. atp_flag in ('Y','R','C')
and ola. link_to_line_id is null
and ola. item_type_code in ('Standard')
and ola. actual_shipment_Date IS NULL
group by
ola. schedule_status_code, msi. item_Type, ola. item_type_Code, ola. visible_demand_Flag,
oha. attribute14, msi. atp_flag, ola. override_atp_date_code
order by
ola. schedule_status_codedesc;
--PCT MODELS -- SCHEDULE STATUS
select
attribute14,
and ola. item_type_code in ('MODEL')
group by
order by
--FAR MODELS -- SCHEDULE STATUS
select
attribute14,
and ola. item_type_code in ('MODEL')
group by
order by
--FORECAST VIEWS -- CHANGE ORGANIZATION_ID TO APPROPRIATE ORG

CONSUMEDQTY
Group By
FD. SOURCE_FORECAST_DESIGNATOR
--Overconsumption----
select sum(current_forecast_quantity)
from MRP_FORECAST_dates_v
where forecast_designator='GWN_CON_ST'
and last_update_date>= '06-Jul-2013' ///current date
and origination_type_desc ='Overconsumption'
---MDS Query---
Select msd.schedule_designator, sum(msd.original_schedule_quantity)

from mrp_schedule_datesmsd
where schedule_designator in
('AMR1_GMDS','AP_GMDS','EMEA_GMDS','EXPD_GMDS','CHN_GMDS',
'NAGS_GMDS','OCN_GMDS')
AND SCHEDULE_DATE >= '22-Jul-2013'
AND SCHEDULE_DATE <= '31-Jul-2014'
and source_code='MRCSAL'
group by
msd.schedule_designator
---DICE Populate Forecast Data for Manual ATP (JOB-0092)---
select organization_id,
forecast_designator,
sum(original_forecast_quantity) Orig,
sum(current_forecast_quantity) Curr
from xxit_fc_item_qty
group by organization_id,
forecast_designator
order by organization_id,
forecast_designator;
----Launch Supply Chain query-----
select compile_designator, last_update_date from MSC_PLANS
where compile_designator in
('BCM_WKEND','BCM_ATT','PCTWEKEND','BCM_MIDWK','PP_WKEND')
ORGANIZATION_ID ORGANIZATION_CODE ORGANIZATION_NAME
105 BCM Bobcat Manufacturing

106 GWN Gwinner
124 FAR Fargo Offsite

244 CAR Carrollton
284 LFD Litchfield
446 PCT Pont-Chateau
607 BCA BCA Inventory Org
631 STA STA Inventory Org
687 BIM Bobcat Imports
867 BMK Bismarck Building 40
13. Issues Faced During Weekend Planning Run
13.1 Push Plan Issues
1, Push Plan completing with following error:
“ORACLE error 2055 in FDPSTP
Cause: FDPSTP failed due to ORA-02055: distributed update operation failed; rollback required
ORA-00001: unique constraint (MRP.MRP_GROSS_REQUIREMENTS_U1) violated
ORA-02063: preceding line from DNAPROD
ORA-06512: at "APPS.MS”
Cause:
Error is caused by pushing a demand from ASCP with the same DEMAND_ID as an existing
MRP_GROSS_REQUIREMENTS entry
The product design generates the DEMAND_ID values used when pushing a demand from the RDBMS
sequence MRP_GROSS_REQUIREMENTS_S. If that sequence reaches its maximum value, the sequence
needs to be reset to a smaller number.
Solution:
After discussing with DBA team, we have learnt that instead of resetting the sequence, we better purge
the plans whose Min/Max demand id is causing the issue.
Run following sql to get nextval value:
select mrp_gross_requirements_s.nextval from dual
Run the below SQL again and compare the values of MIN(DEMAND_ID) and MAX(DEMAND_ID) and
ensure that they are not greater than the LAST_NUM of theSequence MRP_GROSS_REQUIREMENTS_S.
select min(demand_id), max(demand_id), organization_id, compile_designator

from mrp_gross_requirements
group by organization_id, compile_designator
order by min(demand_id)
Output should come like:
Purge the plans using following two responsibilities assigned to Bobcat_jobs_plan user:
SRC MPS and MRP Purge (Bobcat)

SRC MPS and MRP Purge FR (Bobcat)
Please follow Note 944864.1 and 577658.1 inMetalink, whenever you need more info.
2, Push Plan completing with warning and with following error:
ORA-02049: timeout: distributed transaction waiting for lock
ORA-02063: preceding line from DNAPROD
This happens only with BCM_WKEND plan during Sunday Evening and it is not happening every
weekend.
Root Cause of issue is yet to be determined.
22.2 Refresh Collection Snapshot Failure:
We had one failure on it during the weekend after the application of patch # 16772118.
After application of this patch we have issues where materialized views are used. We use materialized
view in Refresh collection Snapshot and hence it is causing the issue.
SR # 3-8113810409, opened with Oracle on it and we get more info on it through note # 1573704.1
We applied the patch # 17230530 provided by Oracle to eliminate the issue we had with materialized
view.
13.3 Data Collection Failure:
'Planning Data Pull Worker' completed with error.
In one of the planning data pull worker log file I see below error (but not in all planning data pull
workers log files).
Procedure LOAD_SALES_ORDER(3) started.

Error pulling data from MRP_AP3_SALES_ORDERS_V to MSC_ST_SALES_ORDERS.
ORA-12801: error signaled in parallel query server P000, instance m221009dbss3004:DNAPROD2 (2)
ORA-08103: object no longer exists
ORA-02063: preceding 2 lines from DNAPROD
ORA-12801: error signaled in parallel query server P000, instance m221009dbss3004:DNAPROD2 (2)
ORA-08103: object no longer exists
ORA-02063: preceding 2 lines from DNAPROD
Solution:
Cause is not known, but Oracle advised to run below 8 steps and it solved the issue:
1. Ask your DBA to compile all invalid objects in both Source and Destination Instances. (please
skip this if already done)
2. Using Adadmin, regenerate All schemas in Source and in Destination instances.

This means:
Go to Adadmin main Menu
Section 2: Maintain Applications Files
Then select:
1. Relink Applications programs
If you cannot do this for All Schemas, run it at least for:

(For Source: INV,BOM,WIP,PO,ONT,MRP,APPS, and APPLSYS schemas.)
(For APS Instance MSC Schema)
3. Run Gather Stat Schemas for All schemas in both Source and in Destination instances.
- If you can, run it for 50% or even more like 80%, if not, just run it at a % level that you can.
- If you cannot do this for All Schemas, run it at least for:

(For Source: Run Gather Schema Statistics for INV,BOM,WIP,PO,ONT,MRP,APPS, and APPLSYS
schemas).
(For APS Instance: Run Gather Schema Statistics for MSC Schema).
4. In APS Instance (Planning Instance):

To clean up the Staging Tables, run program "Planning Data Collection - Purge Staging Tables"
(Run in as STANDALONE PROGRAM as shown below):
Go to Advanced Supply Chain Planner responsibility.
Navigate to: Other / Request
Click on "Submit a New Request" button
Submit program: "Planning Data Collection - Purge Staging Tables"
Parameters:
- Instance: (Select your Instance Code)
- Validation: No
5. In Source instance, please set the profile option:

MSC: Source Setup Required = "Yes"
6. In Source instance:
Run "Refresh Collections Snapshots" program with following parameters:
(run it from Source Instance if using Decentralized setup):
Go to Oracle Manufacturing responsibilities, such as:
Material Planner or Manufacturing and Distribution Manager, or Material Planner (or ASCP)
Navigation:
View / Requests / Submit a New Request.
Submit program: "Refresh Collection Snapshot"
Parameters:
Refresh Mode = Complete
Snapshot Name = ALL SNAPSHOTS
7. In Source instance:
Run "Refresh Collections Snapshots" program with following parameters:
(run it from Source Instance if using Decentralized setup):
Go to Oracle Manufacturing responsibilities, such as:
Material Planner or Manufacturing and Distribution Manager, or Material Planner (or ASCP)
Navigation:
View / Requests / Submit a New Request.
Submit program: "Refresh Collection Snapshot"
Parameters:
Refresh Mode = Automatic
Snapshot Name = ALL SNAPSHOTS
Threshold for Truncating Logs = 0
Degree = 0
8. Run Complete Data Collection from ASCP responsibility (in Destination instance, if
Decentralized):
Go to Advanced Supply Chain Planner responsibility.
Navigation:
Collections / Oracle Systems / Standard Collections
Collections Method = Complete Refresh
Root Cause:
We have found the root cause of the data collection failure we had past weekend. This error was caused
due to the running of a Scheduled “Refresh Collection Snapshot” job in DNAPROD instance in parallel
with “Planning Data Pull” in DNAASCPP instance.
The “Refresh Collection Snapshot” is scheduled to run at 2AM Sunday morning and due to delayed
weekend plan runs we run data collection 2 at same time. Hence, running time of both jobs coincides and
due to which “Refresh Collection Snapshot” in DNAPROD create locks on snapshot tables.

Tata Consultancy Services: Doosan Weekend Job Run Book

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Tata Consultancy Services: Doosan Weekend Job Run Book

Caricato da

Copyright:

Formati disponibili

TATA CONSULTANCY SERVICES

Doosan Weekend Job Run Book

1st Shift in Assembly is from 7AM Saturday (CST) – 3 PM Saturday (CST)

Responsibility SRC Weekend Planning User All (Bobcat)

Path Supply chain planning Others Change

1. Click on Submit a New Request.

2. Enter the Job Name - DICE Reschedule Ship-From-Org (JOB-0038)

a. Ship from Org Id-GWN

b. Unschedule only = Yes

d. Include Overridden SSD= Yes

f. OM Item Type Code=Model

PLANNING MANAGER RECORES

select process_status, count(*)

--GWN MODELS -- SCHEDULE STATUS BY MODEL/DEMAND CLASS

WHERE organization_id = 106

and demand_class_code = 'AMR1'

--and Schedule_status_code is null

--and Schedule_status_code is not null

GROUP BY demand_class_code, alloc_model, Schedule_status_code

Copy Merge Forecast Programs for Organization PCT

2.1 Copy Merge Forecast Program for Source-PCT_EMPTY

Responsibility SRC Weekend Planning User PCT (Bobcat)

Path Supply chain planning Others Change

1. Click Supply chain Planning

4. Enter the parameters as mentioned in the excel sheet.

8. Note down the Request Id

Supply chain planning->Forecast->View sets

2. 2 Copy Merge Forecast Program for Source-PCT_LS

In the same Responsibility

1. Click Supply chain Planning

4. Enter the parameters as mentioned in the excel sheet.

8. Note down the Request Id

Supply chain planning->Forecast->View sets

--FORECAST VIEWS -- CHANGE ORGANIZATION_ID TO APPROPRIATE ORG

3. Load/Copy/Merge MDS Program for Organization PCT

In the same responsibility

1. Click on Supply Chain Planning

4. Enter the Parameters entered in the excel sheet.

8. Note down the Request Id

4. Copy/Merge Forecast Programs for Organization GWN

4. 1 DICE Empty Gwinner Demand Classes Forecast

Responsibility SRC Weekend Planning User All (Bobcat)

Path Supply chain planning Others Change

SELECT FD. ORGANIZATION_ID,

SUM(FD. ORIGINAL_FORECAST_QUANTITY) ORIGINALQTY,

4. 2 DICE Load Gwinner Demand Classes Forecast

Also, original quantity and current quantity should match.

SELECT FD. ORGANIZATION_ID,

5. DICE Populate Forecast Data for Manual ATP (JOB-0092)

Responsibility SRC Weekend Planning User All (Bobcat)

Path Supply chain planning Others Change

--ATP Custom Table Counts by FC Name

6. Rescheduling Of the GWN Programs

PLANNING MANAGER RECORES

select process_status, count(*)

2. You can execute the Rescheduling programs in parallel

3. For Process Status=2, Count should be maintained below 10,000.

Responsibility SRC Weekend Planning User All (Bobcat)

Path Supply chain planning Others Change

1. Click on Submit a New Request.

2. Enter the Job Name - DICE Reschedule Ship-From-Org (JOB-0038)

6. 1 Rescheduling Orders for demand class-AP

a. Ship from Org Id-GWN