Sie sind auf Seite 1von 81

Running the BW

Production Network:
A
Beginners Guide

PART 2 Daily Transactional Data Loads

Table of Contents:
Contents
A.

Transactions Required for BW Production Support

Page 4

B.

Preparation for 10:00 PM Transactional Data Loads

Page 5 13

1.

Setting up your Server

Page 5

2.

5 Required Sessions in GWP ..

Page 5 9

3.

Required Sessions in Source Systems (GP1, CP1, & TP1).

Page 10 11

4.

Documentation (on the shared drive) that youll need

Page 12 - 13

C.

Timeline of Transactional Data Control M Jobs

Page 14

D.

Monitoring Transactional Data Loads & Manual Intervention

Page 15 27

1.

Daily CCA Loads and daily deletion of CCA Plan Versions

Page 15 21

2.

Special End-of-Month Maintenance of CCA Aggregates

Page 22 27

Handling failed Transactional Data Loads by Type

Page 28 - 53

1.

Matrix Failed Transactional Load Types

Page 28

2.

Case 1 DataMart (ODS) to Cube(s) Delta Load

Page 29 41

3.

Case 1 DataMart (ODS) to Cube(s) Delta Load

Page 42 - 53

Special Jobs Calendar and Descriptions

Page 54 - 72

1.

Special Jobs - Calendar

Page 54

2.

4th CWD (Calendar Work Day) - EOM (End of Month) Special Jobs

Page 55

3.

Special Jobs - Descriptions

Page 56 72

1. Daily Network

Page 56

2. Product Cost

Page 56

3. Monthly Master Data Info Group

Page 57

4. Purchasing Bus Planning Special

Page 58 59

5. Product Costing Plan Special

Page 60

6. Finance Monthly

Page 61

7. Finance Monthly 2

Page 62

8. EP Service Delivery Metrics - Monthly

Page 63

9. CCA Actuals Monthly Final

Page 64

E.

F.

Table of Contents:
Contents (cont)
Table of Contents (cont)
10. ZMM_C01 Change

Page 65

11. Reschedule Trans Data

Page 66 69

12. S958 V130 Prelim

Page 70

13. S957 V100 Prelim

Page 71

14. S957 V100 Final

Page 72

Revisions

Page 73

Appendix 1 Answering Pages from the Data Center

Page 74 75

Appendix 2 System Messages

Page 76

Appendix 3 System Architecture

Page 77

Appendix 4 Instant Messenger

Page 78 79

Appendix 5 Dupont Control-M Holiday Calendar

Page 80

Appendix 6 Contact / Phone List

Page 81

Transactional Data Processing

A.

Transactions Required for Production Support

This is a list of transactions and the associated systems that you must have authority to execute
in order to run the Master Data and Transactional Data Loads on the production Network

Item
#

Trans
action

Transaction
Description

Associated
System

Comments

SM37

Job Overview

GWP, CP1,
GP1, TP1

Monitor Control M Jobs


Kill Background jobs

SM50

Process Overview

GWP, CP1,
GP1, TP1

Monitor ALEREMOTE
activity on the system

SM58

Transactional RFC (monitor)

GWP, CP1,
GP1, TP1

Monitor ALEREMORE
trans RFCs between systems

AL08

Current Active Users

GWP, CP1,
GP1, TP1

View active users on all


systems

SM04

User List

GWP, CP1,
GP1, TP1

SM66

Systemwide Work Process Overview

GWP, CP1,
GP1, TP1

View activity on all active


systems

SM51

SAP Servers

GWP, CP1,
GP1, TP1

Display list of active SAP


Servers

ST22

ABAP Dump Analysis

GWP, CP1,
GP1, TP1

List of dumps on the current


system

SM64

Release of an Event

GWP

Trigger an event in the Prod


Event Chain

10

SM02

System Messages

GWP

To create and maintain


system-wide messages

11

DB20

Maintain Statistics

GWP

To maintain statistics

12

ST04

Database Snapshot

GWP

To review Deadlocks and


Lock Waits on programs

* NOTE: If any of these transactions are unavailable to you submit a PQR to modify your profile to
Include these Authorizations.

Transactional Data Processing

B.

Preparation for the 10:00 PM Trans Data Load portion of the Production Network
1.

Setting up your Server

* Ensure that you have a GWP session on Server: gsdux85 System #: 00


. To check this go into your Logon Screen and set up a GWP Production Session (I have called it BW / GWP
Network Support with the following parameters:

2.

5 Required sessions in GWP


You will need to open 5 sessions in GWP Network Support with the
following screens for Production Support:

Session #1: Infosources Monitor Screen


1)
2)
3)
4)

In GWP Enter xaction /nRSA1 (Administrator Workbench),


Select the Infosources Tab
Click on the highest level of the Infosources screen
Click on the Monitor Icon
1.
4.

3.
2.

5
*This will take you to the Infosources Monitor Screen See next Page

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)

Session #1: Infosources Monitor Screen

*Make a note of the


number of successful,
warning, and unsuccessful
jobs 15 minutes prior to
running the network so that you
can keep an accurate count of the
production loads that are completing.

Click the funnel on the menu and


Set the Time Selection to: Today
And the Request Overview to:
Overview Tree
And click Execute

Session #2: Infopackage Groups Display Screen


1)
2)
3)

In a second GWP Session Enter xaction /nRSA1 (Administrator Workbench),


Select the Infosources Tab
Click the Show InfoPackage Groups Icon (see below)

Show InfoPackage Groups

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)

Session #3: Job Overview Screen


1)
2)

In GWP Enter xaction /nSM37


This will take you to the Simple Job Selection Screen.
Enter the following parameters:
a)
Job name : z *
b)
User name: *
c)
Check the Sched. And Finished Boxes
(you can select more checkboxes depending on desired status)
d)
Select todays date in the Fr. & To boxes.

a.
b.

c.
d.

*Click the Execute Button to go to the Job Overview Screen

Job Overview Screen

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)

Session #4: Process Overview Screen


In GWP Enter xaction /nSM50 to go to the Process Overview Screen.
1)

This screen displays all the jobs that are running (or will be running) for the current server
only, gsdux85.

2)

Wherever you see the User ALEREMOTE these are jobs that are related to the Production
Network. this screen will show you all current jobs that are running in the Production Network.

3)

Press F8 to refresh this screen.

4)

This screen allows you to identify jobs by the PID (Parameter ID). If it becomes necessary to
cancel a job from this Screen, follow the instructions below this window.

5)

To cancel a job on this screen: a) Select the job (checkmark), b) Click Process (from the menu),
and c) Click on Cancel without core

b)
c)

a)

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)

Session #5: Systemwide Work Process Overview


In GWP Enter xaction /nSM66 to go to the Systemwide Work Process Overview Screen
1.

This screen will display all active servers associated with the Production Network.

2.

Jobs can be identified on this screen by the PID (Parameter ID).

3.

If you are in GP1 or CP1 - Do not use the Refresh button on this screen this generates a lot of
dumps instead, when you want to refresh this screen - enter the /nSM66 transaction in the blank
text box at the top of the screen, and hit enter. In GWP you CAN use the refresh button.

Notes: These are the 5 sessions in GWP - that you will need to get started with, before the Transactional Data
Loads run at 10:00 pm. The last 2 sessions you may want to switch to a couple other transactions
to view the Prod Network thru the course of the evening. We will review these other transactions later,
but they include:
/nAL08 Current Active Users - Shows all users (including ALEREMOTE) logged onto
all servers at the current time. (reviewed later)
/nSM04 User List - Displays the same server information as the previous xaction, but only for
the current server at the current time. (reviewed later)
/nSM58 Transactional RFC (display) This transaction displays the Remote Function calls
between the Source (R/3) System and the BW (GWP) System. This xaction will have to be
opened in 2 separate sessions in both GP1 and CP1. This xaction will be reviewed next

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)
3.

1.

Required Sessions in Source Systems (GP1, CP1, & TP1)

Besides the previously mentioned 5 sessions in GWP, in the Source System(s) GP1, CP1, and TP1
you will have to monitor the transactional RFC (remote function calls) being performed between the
source system (GP1,CP1, or TP1) and our Production System (GWP). [simplified diagram follows]

GP1
Remote Function Call

TP1

Data &
IDOCs

GWP

Remote Function Call

CP1
The user : ALEREMOTE is responsible during
the network to pass data & IDOCs back and forth
from the source systems to GWP.
This is tracked by transaction /n
nSM58
SM58 in all
source systems.

2.
3.

4.

This monitoring will be done thru the transaction /nSM58.


In GP1, CP1, & TP1 open two sessions both with transaction /nSM58. The reason that you open 2 (or more)
SM58 sessions is that frequently you will be performing a transaction called Execute LUW. This action will
cause your session to clock, so you will want to jump to a second session in the source system to refresh the
SM58 screen.
See the screens on the next page.

10

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)

Normal Monitoring View SM58 in CP1 or GP1

During the Production Network Run this is what the normal


SM58 screen will look like. This is showing the RFCs being executed
between the source system (CP1) and GWP by user ALEREMOTE.
while this screen is up you can click the Refresh button to see new
transactions as they are executed.

SM58 with an ERROR action is required to be taken

Execute LUW

Frequently, you will see a red-highlighted message such as the one in the screen above:
Object requested is currently locked by user ALER. take the following steps
To clear this message:
a) Make sure that you have a second session open in this same source system (CP1)
because once you clear this error message the process will clock (hourglass) for
several minutes. You can jump to the 2nd session (SM58) and refresh that screen
and it will not be clocking.
b) Click on the Function Module field of the highlighted entry (blue field above) once
this is selected,
c) Click on Edit (on the Taskbar).
d) From the drop-down box click on Execute LUW (F6) this will clear the error
message.
e) Go to your other SM58 session and click refresh you should see that the red
highlighted line should be gone.

11

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)
4.

Documentation (on the shared drive) that youll need


* All of this documentation is on the Shared Drive, you will need to print pages from the first
document, the others are for reference:

1.

Task Schedule -Transactional Data for Daily Network (vx) mmddyy.doc


a.

This is the key document for monitoring the Transactional Data Loads, print a copy of it.
This document is in the shared drive, in the following location: E:\T03\BW
Technical\Production Run\.

b.

Select the latest (most recent) version of this document.

c.

This document will automatically print out the current date on the front page.

d.

This document lists the location of other key documents like the Abend list and the Network
schedule.This document also lists the InfoPackage Groups for the Daily Master Data Loads.

e.

This document lists the schedule of events for the Transactional Data Loads

NOTE: A very important part of this document is the Check Counts table (see below excerpt). This is where
you will check the number of Infopackages that execute from each Infopackage Group, and the
sequence that the Infopackages Run.
f.

There is another document similar to this for the Master Data Loads ensure that you copy the
correct one.

g.

This document is modified frequently to try to keep up with changes to the Transactional Data
Load Daily Schedule.

h.

Occasionally, packages are deselected from Groups, or Groups are de-scheduled. It is the
responsibility of the On-call Monitor to note these changes and inform their supervisor so that the
document can be modified.

i.

The screen print below gives an example of how the document is used to record (check the counts)
of the finished Infopackage Groups.

After the whole Infopackage


Group runs (to completion) you
annotate the number of successful
packages in this column, then you
check that this number agrees with
the number of Infopackages column.

This tells you that the Sales - Daily


Transactional Data Group contains
7 active Infopackages (to be run)

Infopackages in Red and with N/A


In the Check Count column are not
Scheduled to run you can disregard
These.

12

Transactional Data Processing


B.

Preparation for the 10:00 PM Trans Data Load portion of the Prod Network (cont)
4.

Documentation (on the shared drive) that youll need (cont)


1.

j.

The way to check that the Infopackage Groups have fully completed and all the Infopackages (within that
group) have run is to go to the Infopackage Groups Display Screen (Session #2) of your GWP
screens. The Master Data Guide (page 13) describes how to check the number of InfoPackages that have
successfully run. Please refer to that section for details.

2.
a.

Task Schedule -Transactional Data for Daily Network (vx) mmddyy.doc (cont)

Special Month-End Documentation

End of Month Processing occurs mainly on the 4th CWD of each month. With several other Special Jobs
occuring in the first week of the month. The calendar for these events is shown on Page 41 of this document.

b.

The document required to record the completions of these events is called ** Task Schedule for February
Month-End (4th Workday): 3/6/03
** - Note: the Month and date values will vary by month. This example was for Februarys Month-End and it was
generated on March 6, 2003.
c.
This is an exerpt of the document (page 2) which shows a Checklist for the Month-End Loads.
d.
It also lists the Packages that are in each Package Group that is run for Month-End processing.
e.
This document is located in the following directory/folder:
E:\T03\BW - Technical\Production Run

13

Transactional Data Processing


C.

Timeline of Transactional Data Control M Jobs


Control-M
Jobs

TIME
19:00 GWT
02:00 PM EST

Events
.Resets all Event Chain processing
For master & all transactional data loads

Z_RESET
_EVENTS
(automatic)

Transactional Data
Groups
DAILY_TRANSACTIONAL_
DATA_INFO_GROUP
IFC00099 Purchases by Document R05 - Daily
IFC00095 Goods Mvmt R05 - Daily

Z_START_
ISCTEMP

3:00 GWT
10:00 PM EST

.This job kicks off the nightly


Daily Transactional Data Loads

(automatic)
3:00 GWT
Appx 10:00 PM EST

START_TRANS_DATA_EC

Z_DEACT
_CCA

. Deactivates CCA cube

Inventory Daily
Purchasing Daily
Cost Center Acct Plan - Daily
Manufacturing Daily
IFC00105 CCA R05 - Daily
Product Cost Unit Price - Daily
IFC00047 Demand Planning R05 - Daily

(automatic)

IFC00073 Business Planning AP0 R05 - Daily

Appx 3:08 GWT


10:08 PM EST

BI_BTCH_COST_
CENTER_ACCT_PLAN

. Begins loading process of


CCA Cube

(automatic)

Sales - Daily
Statistics Loads - Daily
COPA - Daily

BI_DELR_138013
_CCA_V1
BI_DELR_138014
_CCA_V2
.After CCA Loads
BI_DELR_138016
Have begun
_CCA_V3
BI_DELR_138015
_CCA_V4
(manual)

IFC00092 Material Master Daily R05


AR Transactional Data Daily R05

.Operator manually Deletes


4 PLAN VERSION LOADS
from CCA Cube
PROJECT 1 TRANSACTIONAL DATA
GROUP DAILY (CP1)
BP Demand Supply - Daily

Appx 07:00 GWT


2:00 AM EST

Z_ACT
_CCA

. Reactivates CCA Aggregates


After CCA Daily Plan Loads are complete

IFC 20021 CCA Detail Infopackages


IFC20010 COPA Daily Infopackages
IFC20027 CCA Full Costs Infopackages

(automatic)

IFC20004 Notification Causes Infocube

After previous
Job (appx 2:00 AM)

Z_FILL
_CCA

. Begins CCA Aggregate Fill jobs


After CCA Aggregates are activated

IFC20006 Notifications Activities Infocube


IFC20007 Notifications Tasks Infocube

(automatic)

After previous
Job (appx 2:00 AM)

IFC20005 Notifications Infocube

IFC20008 Notifications Items Infocube

. Runs/fills the CCA


Z_AGGREGATE_
FILL_0CCA_C01
performance Aggregates
Z_AGGREGATE_
FILL_0CCA_C01
Z_AGGREGATE_
FILL_0CCA_C01
Z_AGGREGATE_
FILL_0CCA_C01
(automatic)

IFC20030 Maint orders costs & allocations Infocube


IFC20035 - Inventory
IFC20037 Inspection Check/Usage Decision Infocube
IFC20039 Plan/Act Comparison Ord/Mtrl View Info
IFC20040 Plan/Act Comparison Opn/Wrkctr Info
IFC20041 Plan/Act Comparison Mtrl Consump Info
IFC20042 Inspection Result General Data Infocube
IFC20043 Inspection Result Quantitve Data Infocube

9:00 AM GWT
4:00 AM EST

Z_START_TRANS
ACTIONAL_TP1

(automatic)

. Kicks off the T-Cluster Transactional


Data Loads

C: Sales Daily

14

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions

Note: This Procedure is very similar to the loading, monitoring, and deletion of COPA loads. There are some
specific differences. Also, currently, the COPA daily deletions are automatically performed whereas
the CCA daily deletions are still performed manually by the individual monitoring the network.
a)
b)
c)

CCA stands for Cost Center Accounting. The InfoObject that we are interested in is: 0CCA_C01 CCA: Costs & Allocations (Full Cost). This is an InfoCube.
The InfoCube is loaded from the G Cluster and has Aggregates that are also loaded and activated
like the COPA Cube.
Below is a screen print of the Cube with its Aggregate Symbol (activated). If you open the Data
Targets tab and open the Cost Center Accounting folder, you will see the 0CCA_CO1 Cube
(highlighted below). To the right you can see the Symbol for the active Aggregate.

CCA
Cube
(0CCA_C01)

Active Aggregates
symbol

d)

If you right click on the Cube name, from the drop-down box, select Manage.

Select Manage
from the dropdown box

15

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)
e)

Select the Requests tab (if it is not automatically selected).

f)

On this screen, you will see all the successful loads of the CCA Cube. The last 5 loads are from
the previous day. These loads are:

g)

1)

FULL/0CO_OM_CCA_1/0CCA_C01 - PLAN FISCPER V3

2)

FULL/0CO_OM_CCA_1/0CCA_C01 - PLAN FISCPER V4

3)

FULL/0CO_OM_CCA_1/0CCA_C01 - PLAN FISCPER V1

4)

FULL/0CO_OM_CCA_1/0CCA_C01 - PLAN FISCPER V2

5)

FULL/0CO_OM_CCA_1/0CCA_C01-FISCPER

If you move your mouse over the Infopackage names you will see the full name of each
successfully loaded Infopackage. Also notice that all these loads have:
1)

A Request ID (1st Column)

2)

A reportable icon symbol (2nd Column)

3)

A green check mark in the Rollup available (4th Column)

4)

And green lights (indicators) in the next 2 columns.

h)

Notice also, the request and update dates for each load. In this example, these dates range from
03/03/2003 to 03/04/2003. The reason for this is the 1st three loads were started before
midnight, (03/03) the last 2 loads were started after midnight (03/04).

i)

Also, notice from this screen, that below these 5 loads, there are multiple loads from the
previous run (on 02/28/2003). Normally, you would only see one load from the previous run
(because you would have deleted the Plan Fiscper Versions from the previous run) and only the
FISCPER load would be on the Cube..But because this is the 1st load of the new Fiscal
Period (month) the 4 Plan Versions from the last day of the previous month are retained.

16

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)

Note: We will go into more detail on when to delete the previous Plan Fiscper Versions (1 thru 4) this is the
norm. and when to retain the previous Plan Fiscper Versions (on the 1st day of the new Fiscal
period.
A.

Daily CCA Loads


1)

Within the Event Chains for the Daily_Transactional_Data_Info_Group (which start


at 10:00 PM EST), there is an InfoPackage Group called: Cost Center Acct Plan
Daily.

2)

Within this Package Group are the 5 Full Loads which start automatically within the
transactional data event chain. See screen print below.

Daily_Transactional_Data_
Info_Group

CCA Plan Daily


Infopackage Group

5 daily loads (one FISCPER and four PLAN FISCPER VERSIONS (V1 thru V4))
3)

If you double-click on the Cost Center Acct Plan Daily Infopackage Group this
will open the Scheduler screen for this infopackage group. See the next page.

17

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)
A.

Daily CCA Loads (cont)


4)

Within the Scheduler screen for the Cost Center Acct Plan Daily InfoPackage Group
you will notice the 5 Full loads, also notice:
a)

All 5 loads are selected to be run (check marks in the 1st column Execute
InfoPackage.

b)

Also notice that they are listed in order of their start sequence (column 2).

c)

The 3rd Column (with the green checkmark) indicates that all packages are
selected to be run as part of this Group.

d)

The last thing to notice about this screen is the checkmark in the column to the
right of the Infopackage name. This column C is for check whether the
previous request was updated before starting the next request. This description
can be very confusing depending on how you look at it. A check on an
InfoPackage line (as is the case with the FISCPER load) indicates that this
package must complete successfully before the next 2 packages start, so in
effect the 2nd package (and the 3rd package) wait for the 1st Package to
complete. Along these lines the 3rd Package has a checkmark consequently, it
must complete successfully before the 4th (and 5th) packages start simultaneously.

e)

Click on the Schedule Tab. See next page for description.

18

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)
A.

Daily CCA Loads (cont)


5)

The Schedule Tab (below) allows you to view the following information:
a)

The Job Name (in this example BI_BTCH_COST_CENTER_ACCT_PLAN)

b)

A small clock to the right of the Job Name indicates that this batch job is currently
scheduled.

c)

The Selection options button lets you view the Start Time window shown
below. This window displays the event ZFINISHED_PROCESSING and its
specific parameter START_TRANS_DATA_EC that will trigger this
InfoPackage Group to start..

Selection options button (green check indicates


that there are current selections. Click on this button
to open the Start window (below)

Jobname
Clock indicates job is scheduled

d)

e)

The SubseqProcessing button has


nothing selected indicating that after
this group completes it will not
trigger any subsequent events.
In order to change anything about this
job, you must first click the Stop
button to unschedule the job (the
small clock will disappear.

The CCA Plan daily


Group will start after
This event / parameter

19

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)
B.

Daily CCA Manually deleting previous days FISCER Plan Versions


1)

Every Calendar Work Day, the Event Chain Event START_TRANS_DATA_EC will
automatically trigger the CCA Plan Daily group to run automatically. As these loads are
occurring the Network monitor (you) are responsible for manually deleting the previous
days FISCPER Plan Versions (V1 thru V4). This is very similar to the COPA deletes as
outlined in the Master Data Processing Manual.
a)

The first step in doing the daily CCA Deletes, is to identify the correct loads to
delete. They will be the PLAN FISCPER V1, V2, V3, & V4 load.

DO NOT DELETE ANY LOAD NAMED FULL/0CO_OM_CCA_1/0CCA_C01FISCPER THESE LOADS WILL BE AUTOMATICALLY HANDLED BY
THE SYSTEM.
b)

After you have identified the 4 Version Loads to be deleted write the Request
IDs down on a piece of paper. If possible confirm this with other Support
personnel who may be available on-line.

c)

Do a Cntrl-C on the Request ID (in this case 138372). Put your cursor on the blank
JobName field (following BI_DELR) precede the Request ID with an underscore.
Then after the ID put and underscore and then CCA_V#. So that the JobName will
appears as BI_DELR_138372_CCA_V3.
BI_DELR_138372_CCA_V3 In our example, the Version to be
deleted is Version 3. With this specific jobname you can track the progress of the
delete in the Job monitor screen: SM37.

d)

Select the Request ID to be deleted (as in the example below) then press the Delete
Button. This will put a Trashcan Icon on the line.

Click the button


at beginning of
row to select this
Request ID

With Request ID
selected, click the
Delete Button

20

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


1.

Daily CCA Loads and daily deletion of CCA Plan Versions (cont)
B.

Daily CCA Manually deleting previous days FISCER Plan Versions (cont)

2)

e)

Before you refresh the screen, make sure to click on Environment


Complete check of request ID (from the main menu).

f)

From the pop-up window, select Complete Check of all request


IDs for existence in the InfoCube. (as shown above). And click
the green checkmark (Enter).

g)

Following this step, refresh the screen with the Refresh button at
the bottom.

Repeat these steps to delete the remaining 3 Plan Fiscper Versions from
the Cube. If any more detail about doing these deletes is required see
the COPA deletes in the Master Data Manual.

Important Note:
Note: When the 1st Load of CCA data is performed in
a new month DO NOT delete the last 4 Plan Fiscper
Versions from the previous month. These requests will be
retained in the Cube. This is only effective for the First
CCA Load performed in a new month.

21

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates


a)

Following the 1st Successful Load of the CCA Plan Fiscper Version for a new month the following
maintenance process must be performed on the 0CCA_C01 (CCA Cube) Aggregates. Follow
these steps on the workday immediately following the 1st successful load of CCA for the new
month.
1)

Go to the Maintaining Aggregates screen of the 0CCA_C01 Cube by double-clicking on


the Aggregate (Sigma) symbol beside the InfoCube (see the symbol on page 6 of this
document). When you double-click on the symbol this will open the Maintaining
Aggregates screen, shown below.

2)

If you expand the Aggregates window to the right you can see the full name of the
Aggregates. In the case of the CCA Cube the Aggregate names (in our example below)
are as follows:

3)

PLAN/MONTH 001/2003

PLAN/MONTH 002/2003

PLAN FY PostP vt10 2/6/2

PLAN FY PostP vt10 fy2002 2/6/

PLAN FY PostP vt20 PM- 001/200

PLAN FY PostP vt20 PM- 002/200

Expand the tree under the first Aggregate - PLAN MONTH (in the example above the
first Aggregate is PLAN MONTH 001/2003).

22

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates (cont)


4)

With the CCA Maintain Aggregates screen up, right click on the Plan Month Aggregate that you
are going to change. This will not be the same every month. If this is the first workday of March
(Plan Month 003/2003), we will modify the Aggregate for Plan Month 001/2003. There will only
ever be 2 Plan Month Aggregates the one for the current month (003) and the one for the
previous month (002). So, next month April (004) as far as the Plan Month Aggregate we
will only change the (002) [February] Aggregate to the 004 Plan Month (and, next month we will
retain the 003 Plan Month.

5)

With this in mind, we will right click on the PLAN MONTH 001/2003 Aggregate. From the dropdown box (seen below) we will click on Change description text.

6)

Change the Short and Long descriptions in accordance with the example below to your new Plan
Month.
Previous Description

New Description

7)

Click the green checkmark to save your changes.

23

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates (cont)


8)

After you have revised the PLAN MONTH description to 003/2003 you need to modify the Fixed
Value of the Plan Month as follows:
a)

Click on the arrow beside the Plan Month Dimension (Tech Name: 0CCA_C016).

b)

Right click on the Plan Month forcast issued characteristic.

c)

From the drop-down box select Fixed value. A selection table with all valid Plan
Months, will appear along the left-hand side of the monitor screen. (See the screen print on
the next page).

Plan Month
dimension

The current Fixed Value before


being modified

Plan Month forcast issued


characteristic

24

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates (cont)


d)

From the Plan Month selection table (in the below screen print) select the new Plan
Month (in this example the new Plan Month is 003/2003). Then click the green
checkmark below the table (Enter).

Plan Month
selection table

new Plan Month

9)

After you have revised the PLAN MONTH Aggregate, you will repeat the above process for the PLAN
FY PostP vt20 PM- 001/200 Aggregate. See screen prints on next page.

25

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates (cont)


10)

The steps for changing the Plan Month value on this next Aggregate are the same as for the
last. We will review the steps here.

1.

Select Plan FY PostP vt20 PM- 001/200

2.

Right click the above Plan and click and select Change description text

3.

4)

Change the 001/2003 to 003/2003 in the Long Description.

After youve revised the name: go into the Plan Month forcast issued characteristic right click
and again select the Fixed Value from the drop-down box and then select the new Plan Month from
the table.

26

Transactional Data Processing


D.

Monitoring Transactional Data Loads & Manual Intervention


2.

Special End-of-Month Maintenance of CCA Aggregates (cont)

5. Select Fixed Value

6. Select the new Plan Month from the table (003/2002) and click green checkmark.

11)

After the Descriptions and Fixed Values have been updated to the new Plan Month, then you
can exit the Maintain Aggregate Screen.

27

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type


1.

Matrix of Failed Transactional Data Loads


a)

Transactional Data Load vary by type depending on


1)
Data Source (InfoSource, DataMart, ODS, APO, etc)
2)
Data Target (Infocube, ODS, PSA/cube)
3)
Transaction Type (Delta, Full, Full/Delete)
The following table helps to categorize different failed loads so that the Network Monitor
can more easily determine How to address/resolve certain Transactional Data Load
Failures.
The specific steps to resolve/rerun these failed loads will be documented on the pages
following this matrix.

b)
c)

FAILED TRANSACTIONAL DATA LOAD MATRIX

Source

Delta

Datamart

CASE 1

Infosource

CASE 2

Infosource

CASE 3

Datamart

Full/Delete

Target

N/A

N/A

Cube

CASE 4

CASE 5

Cube

Full

ODS
ODS

Notes from Matrix:


Case 3 : Delta Load from an InfoSource to an ODS These failed loads will
be handled the same as the Infosource to the cube, with one exception:
* Prior to re-running the Failed Load you will force the failed
load on the ODS (Data Target), to a QM Status of green, then,
following a successful repeat delta of the load, delete the previous green
load from the cube.
Case 4:
4: Full Load from an InfoSource to a Cube(s) Full load failures will
be handled very similarly to Delta Loads. After the load has failed you can rerun the package then delete the failed load from the InfoCube.
Case 5:
5: Full-Delete Loads from an InfoSource to a Cube(s) Full-Delete
loads will be handled similarly to Case 4 with the exception being that the
successful completion of the newest load, the previous failed load will
automatically be deleted.

28

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load


a)

These notes were provided by Lisa Goodwin to address failed Delta Loads that are being
loaded from a DataMart (ODS) to a cube (or multiple cubes).

Source of failed load:


8ZCO_SD05

b)
c)
d)

The above failed package for 8ZCO_SD05 indicates that the load is from the ODS object
on the BW Production System.
There are 2 ways to tell that this is a Datamart object. If you look at the source system of
the load, it says:
this indicates that the source of this Data is from GWP.
The other distinguishing feature of these loads, is that the object is named:
the 8 (before the ODS name indicates that it is a DataMart. To view this source, go to the
Infosources Tab. All the way at the bottom of the infosources groups, there is a group called
Data Marts. Expand this group.

InfoSources tab

Data Marts:
Infosources group
(at bottom of screen)

29

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


e)

Under the Data Marts Infosource Group you will see 8ZCO_SD05. If you expand this with the
arrows at the left of the name, you will see the source system (in this case: GWPCLNT590). If you
further expand this selection, you will see 3 InfoPackages; the Delta, Full, and Init packages for this
load.

Datasource:
8ZCO_SD05

Source system:
GWPCLNT590

3 Infopackages

f)

When we are ready to re-run this package this is where you will open up the Delta Package to
re-run.BUT NOT YET!

g)

Another note about this failed package In this case (8ZCO_SD05) there aree 2 data targets
-InfoCubes ZCC_SD05 and ZCC_SD10. This can be confirmed by opening the Delta InfoPackage
and reviewing the Data Targets tab.

Additional failed
Load: 8ZCO_SD08

h)

In addition, the above failed package for 8ZCO_SD08 indicates that the load from the ODS
object called ZCO_SD08 to the data targets failed. In this case there is 1 data target
InfoCube ZCC_SD05. However, please note that the ZCC_SD05 target is a target of both
failed loads.

30

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


i)

Since these failures share a data target, the strategy to handle them will be as follows:
1)

Run repeat deltas for both failed Infopackages.

2)

After the repeat deltas complete successfully, delete the failed packages from all of the
data targets.

NOTE: Please note that it is very important to complete the repeat delta loads before you delete any of the
failed packages from the InfoCubes. If you delete the failed load before the repeat delta completes
successfully, you will not be able to do a repeat delta and will have to do an init load of the data target
from the ODS.
j)

The following steps will be taken to resolve this situation:


1)

Force the failed infopackage for 8ZCO_SD05 red in the monitor by;
i.

On the Status tab of the Failed Load, double-click on the top red button across
from the Total line.

Double-click on this button to force


Load red.

Note: You might ask why you have to force the load red, if it is already red. On occasion, a load may change
its status, so that it may appear as red, but after several minutes it may turn yellow again. This step of
forcing the load red will ensure that this anomaly will not occur.

Click on Yes

ii.

The above message box will appear click on Yes on the message box.

31

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


iii.
iv.

Another message box will appear entitled Set Overall Status. When this window
appears the button selected will be for Delete status, back to request status.
Click on the radio button beside Status NOT OK to select this.

select Status
Not O.K.

Enter text here


save icon

v.
vi.

After youve selected Status NOT OK, enter a note in the Quick info text field: the
standard for this note will just be NOT_OK_ZZ (where ZZ is your initials), but you can
put any comments in this field.
Click on the Save Icon (small diskette). This will bring up another confirmation window
see the next page.

32

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


viii.

This message box will ask you if you want to Set all updated requests in the Ics to this QM status?
Click on the Yes button (default).

click on yes
button

ix.

After you click yes this will return you to the Monitor Screen with the Status tab - up. You will see
your text comments next to the red button on the Total line.

Your revised comments


will appear here.

33

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


2)

Repeat the previous steps to force the failed infopackage for 8ZCO_SD08 to red in the
monitor.

3)

The next step is to find the failed InfoPackage for 8ZCO_SD05. It should be in the Data
Marts section, under the 8ZCO_SD05 export data source. In most cases, the failed
infopackage will the DELTA Go to InfoSources. To find this infopackage go back up to the
notes starting at the bottom of Page 20 of this document. Double-click on the Delta package.

Double-click to
open the Delta
package

4)

After the Scheduler Screen for the Infopackage opens. Check each tab:
i.

Select data tab in this case there are no selection criteria.

34

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


ii.

Processing tab in this case Data targets only is selected.

iii.

Data targes tab in this case it shows the 2 (two) cubes selected for the update.

35

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


iv.

iv.

Update parameters tab in this case Delta update and Always update data .. are
selected.

Schedule tab On this tab, you can see that it there are Selection options (green
checkmark beside the Selection options button and there is Subsequent processing. The
radio button Start later is bckgrnd proc. Is selected but if you click on the Selection
options button(see screen print on next page) you will notice that the job is
scheduled to run Immediately.

36

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


5)

This is the window that opens from the Selection options button on the previous screen. This
allows you to set the start time, either Immediately, or After another event is triggered. In the case
of this job, it is selected to run Immediately.

Immediate start
is selected

6)

7)
8)

When you run a job manually as in this case, you will normally want to run it immediately as in
this case. If there was no selection (no green check mark on the Selection option button) then the
alternative radio button on the Schedule tab. Start data load immediately should be selected.
Basically, two different ways to accomplish the same thing Immediate start of the job.
Close this window and return to the Schedule tab.
Click on the Start button to re-run this package.

Start button

37

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


9)

You will be prompted with the following message box No delta update possible. This box is
basically asking you if you want to perform a Repeat Delta you do!

10)

Click on the Request again (default) button. This will run a repeat delta on the last failed load.

Click
Repeat again

11)

The infopackage should start. Check the Monitor screen to ensure this load has started and is in a
yellow status. Monitor the load until it completes successfully and has a green status.

12)

Repeat steps 3 through 10 to re-run the failed infopackage for 8ZCO_SD08.

13)

After both Repeat Deltas have completed successfully, go to Data Targets.

38

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load


14)

Find InfoCube ZCC_SD05.


i.

Right click and choose manage. You should see the 2 failed loads and the 2 successful loads.
The failed loads will show as deltas and the successful loads will show as repeat deltas.

Two successful
Repeat Deltas

Two original
failed Delta
loads

15)

Move the slider (above) to the right to verify the type of data update. From the screen below you
can see that the red (failed) loads are deltas, and the successful (green) loads are Repeat of the last
Deltas.

Notice the type of


Delta update

39

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load


16)

17)

Delete the two failed loads.

i.

Select one of the two failed loads by clicking on the beginning of the line.

ii.

After the load is highlighted, click the Delete (trashcan) button.

iii.

Go to the Environment button on the Main Menu, select Check of Request IDs

iv.

After the Check is complete, Click the Refresh button to remove the failed load
request ID from the Cube.

v.

Repeat the deletion process for the other failed (red) load.

After the deletion of the failed loads are complete, and the delete jobs have finished, and the
failed loads have disappeared from the cube, the remaining Repeat Deltas should have the
Reportable Icon
displayed.

40

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


2.

Case 1 DataMart (ODS) to Cube(s) Delta Load (cont)


18)

After the deletes are completed and the 2 Repeat Deltas have the reportable icon, the loads (on
the Requests tab should appear like the screen print, below.

19)

Repeat steps 14 through 18 for InfoCube ZCC_SD10.

41

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load


a.

This second case involves a Delta Load from and Infosource (2LIS_01_S260) going to 2
different InfoCubes (0SD_C03 & ZSD_Z01). All this information is provided in the name of
the InfoPackage, below DELTA/2LIS_01/S260/0SD_C03&ZSD_Z01.
Another key point about this load, as you can see..it has not failed yet.it is still in a
yellow status. This example also illustrates that some loads, which are relatively small in
amount of data records should finish within minutes. If you observe the detail line with the
yellow triangle under the InfoPackage name you will see that the load started at 23:06:20. If
you look at the system clock at the bottom right corner of the screen, you will notice that the
current time is..01:43 AM. In other words about 2hrs and 37 minutes have expired and this
load has still not finished.
In this case, because the load has not completed, but it has not turned red, we will take the
action of Forcing the Load Red or Failing the Load, so that we can re-run the load more
successfully next time.

b.

c.

d)
e)

The first step is forcing this load red and re-running the load, will be to double click on the
lowest level of the load (i.e. the highlighted line from the Monitor Screen above).
Occasionally, when you double-click on the lowest detail line (as in the above case), a window
will pop up asking if you want to trigger follow-on events see an example of this window
on the next page.

42

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


f.

This is an example of the Trigger follow-on events window. Generally, if this window pops up
select No everytime. This will prevent any subsequent processing from occurring and thus reduce
the possibility of you re-triggering an event after fixing and re-running this failed load so click
on NO.

Always select No you do


Not want to Trigger follow-on
events

g.

After this window closes, you will be returned to the Status screen of the details (see Screen, below).
Double-click on the Yellow indicator (that is in the box) across from the word Total.

Double-click on this indicator


to change the Load status to red

43

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


h.

This is the standard warning message that pops up following an attempt to change the QM Status.
This is a warning not to set a status to green status. If this is done, then attempting a repeat delta
may yield zero records. Since we are changing the status to red, we can disregard this particular
warning. Click Yes to change the QM Status.

h.

When the Set Overall Status window pops up (as below), select the Status NOT OK (red) button,
and put in a brief description in the Quick info text box. Click on the Save Icon (diskette).

44

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


i.

i.

After you save the new QM Status for the load, this window pops up asking you if you want to
update all the requests (in the InfoCubes) to this QM status. Here you will select the default option
of Yes. This will change the requests on the cubes to a red status.

Next, you will get a message about Start automatism this is related to Rolling up data for
Aggregates if the cube has them. Always click Start (the default) on this window.

45

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.
j.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


After you start the automatism process, if the cube does not have any Aggregates, you will get
another pop-up window (see screen, below). This is just a notice that the cube has no Aggregates
and Roll-up is not possible. Click on the green checkmark to accept this message.

k.

Finally, you will be returned to the Status Tab of the Details window (shown below). You will notice
that the status indicator (across from the Total line) is now Red, and your text message has also been
applied.

46

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.
l.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


Click on the Header Tab, (see screen below). If you double click on the InfoCube (in this case
0SD_C03). This will take you to the request tab of the Cube.

Double-click on the
1st Data target to view
the Requests tab of the
Data target

m.

On the Requests tab, verify the QM status of the load is red.

47

Transactional Data Processing


E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


n.

Click on the other Data target ZSD_Z01 to open that Cubes Requests tab, verify the QM status of
the load is red.

o.

Go back to the Header Tab of the Failed Loads detail screen (below). Select the InfoPackage name
from the InfoPackage line (as shown below). Make sure that you get the entire name of the
InfoPackage. Do a CNTL-C to copy the name to the clipboard.

48

E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


p.
q.

r.
s.

Open an Infosources Monitoring Screen. Click on the Binoculars icon to open the Search window.
In the Search text box, CNTL-V (paste) the Infosource name. For the Search in directory field,
click the dropdown symbol and select, Infosources. Then, click the Search button.
On the table, below, the Infosource name will appear on the first line. Click on the Display symbol
to the left of the Datasource.

This will take you to the Infosource (See screen below)


Double-click on the Infosource selected, below this will open up the Infosource Scheduler Screen
see next page.

49

E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


t)

u)

On the Scheduler Screen (below) go to the Data Targets Tab to check the Cubes that this load
will fill. Ensure that both data targets are selected.

Go to the Schedule Tab. In some cases, the radio button Start data load immediately will be
selected. If this is not selected, click on the Selection options button and select Immediate Start.
Then save the Selection Options. On the Schedule tab, click the Start button (with the clock).

50

E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


u)

v)

After you click the Start button you will receive the warning message below. This message
warns you that you cannot do a new Delta update since the last Delta was incorrect. But you
can Attempt to load the data of the last delta update again. Click on the Repeat again button
(the default).

After the Repeat Delta completes successfully open the first of the 2 data targets check to
ensure that there is a green, successful Repeat of the last delta load above the failed load in
the cube. Select the Red, failed load and click the Delete button.

51

E.

Handling Failed Transactional Data Loads by Type (cont)


3.

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


v)

w)

After you click the Delete button, go up to the main menu bar a trashcan icon will appear on the
failed delta load line.

Click on Environment, then click on Complete check of request ID. When the small window opens
up, select the radio button labeled Complete check of all request IDs for existence in the Infocube.
Then click the green checkmark. After this job finishes, click the refresh button.

52

E.

Handling Failed Transactional Data Loads by Type (cont)


3.
x)

Case 2 Infosource (2LIS structure) to Cube(s) - Delta Load (cont)


After the delte job finishes, check the requests tab of the cube, to make sure that the last load was in
fact a Repeat Delta. Check that all loads are green. And finally, check that there is a Reportable
icon on all loads in the Requests tab.

53

Transactional Data Processing


F.

Special Jobs - Calendar & Descriptions


1.

Calendar

BW Production Network Support Schedule


Special Jobs Calendar

SUNDAY

MONDAY

CWD = 1

Daily Network

TUESDAY

CWD = 2

Daily Network

CWD = 3

ZMM_C01 Change

S958 V130 Prelim


S957 V100 Prelim

CWD = 6

Daily Network

10

CWD = 7

Daily Network

Daily Network

Product Costing Special Product Costing Special Product Costing Special

* Retain last Plan Version


loads from last mos of
CCA & COPA

THURSDAY

WEDNESDAY

11

CWD = 8

Daily Network

6
CWD = 4

See next
Page for
Breakdown
Of EOM Jobs
12

CWD = 9

Daily Network

16

17

Daily Network

23

Daily Network

Daily Network

Product Costing Special

29

30

Daily Network
Reschedule Trans Data
S957 V100 Final

13

CWD = 10

14

Daily Network

19

Daily Network

Daily Network

21

Daily Network
Reschedule Trans Data

24

Daily Network

Product Costing Special

20

18

Product Costing Special

22

CWD = 5

SATURDAY

Reschedule Trans Data

Product Costing Special

15

FRIDAY

27

25

26

Daily Network

Daily Network

CWD = -4

CWD = -3

28

Daily Network
Reschedule Trans Data

31
CWD = -2

Daily Network

CWD = -1
Daily Network

Product Costing Special Product Costing Special

* This calendar displays the Special jobs that are required


to be run on the Calendar Work Day (CWD) indicated
above. Brief descriptions of each special job is outlined
on the following pages.

54

Transactional Data Processing


F.

Special Jobs - Calendar & Descriptions


2.

4th CWD (Calendar Work Day) - EOM (End of Month) Special Jobs
a)

The 4th CWD of every month has a number of special jobs that are required to be manually
run, by the BW Production Network personnel. Generally, these jobs are to modify the
Fiscal Period values so that loads point to the new current month.

b)

The Documentation titled: Task Schedule for Month End 4th Workday yyyy-mm-dd, in
BW\T03\BW - Technical\Production Run\ will also serve as a good guide to document
all the required changes.

Appx Run time


CWD = 4

.These 6 Special Jobs are in


The InfoGroup :
Monthly_Transactional_
Data_Info_Group - 1

a)

Daily Network

2:00 PM EST

Product Costing Special

Monthly_Mstr_Data_Info_Grp

Daytime (anytime)
Before 2:00 PM

Purchasing Bus Planning-Special

Before 2:00 PM

Product Costing Plan - Special

Before 2:00 PM

Finance - Monthly

Before 2:00 PM

Finance Monthly 2

Before 2:00 PM

EP Service Dlvry Metrics - Monthly

Before 2:00 PM

CCA Actuals Monthly Final

After normal CCA Run

The procedures for performing all of these Special EOM Jobs are outlined in the following
pages.

55

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


3.

Descriptions

1.

Daily Network
a)

The daily network consists of Master Data Load (daytime) and Transactional Data Loads
(evening)
These loads occur every Calendar Work Day (CWD) with the following exception:
1)
There is no Transactional Data Loads on Friday evenings these loads will be
manually rescheduled each Friday afternoon to be run on the following Sunday
evening.
The following table outlines the Automatic jobs and times that the Master Data and
Transactional Data Loads begin:

b)

c)

Network

Start Job

Start
Time
(EST) /
DLST

Start Time
(GMT)

Ending Event

Appx End
Time
(EST) /
DLST

Appx
End Time
(GMT) /
DLST

MSTR DATA

Z_RESET_EVENTS

1400
2:00 PM

1900
7:00 PM

COPA Aggregs
Complete

2300
11:00 PM

0400
4:00 AM
(next day)

TRANS
DATA

Z_START_ISCTEMP

2200
10:00 PM

0300
3:00 AM
(next day)

CCA Aggregs
Complete

0300
3:00 AM
(next day)

0800
8:00 AM
(next day)

2.

Product Costing Special


a)

b)
c)
d)
e)
f)
g)

The Product Costing Special job occurs on the following dates:


1)
Every Monday of every week
2)
On the following Calendar Work Days (CWD) as shown on the calendar:
1, 2, 3, 4, 5, -2, -1
This job will be run approximately after the Master Data finishes and before the
Transactional Data Loads start.
This job consists of running the InfoPackage Group: Product Costing Special
see below:
Double-click on the Group Name: Product Costing Special.
Select the Schedule Tab.
Click the Start button to execute the InfoPackage Group.
Check that the jobs are running in the monitor.

56

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions

3.

Monthly_Mstr_Data_Info_Grp
a)
b)
c)
d)
e)
f)
g)

The Monthly_Master_Data_Info_Grp Special job occurs on the 4 th CWD of each month.


This job will be run approximately before Master Data starts.
This job consists of running two InfoPackage Groups: Master Data (Text) Monthly and
Master Data (Mdata) - Monthly
see below:
These packages are located in an InfoPackage Group named: Monthly_Master_Data_
Info_Group,
Info_Group withing the InfoPackage Group: Monthly_Transactional_Data_Info_Group 1
see the Screen print, below.
Select and run these 2 individual Infopackage Groups by:
1)
Double-click on the InfoPackage Group name.
2)
Open the Schedule Tab.
Click the Start button to execute the InfoPackage Group.
Check that the jobs are running in the monitor.

57

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions

4.

Purchasing Bus Planning - Special


a)
b)
c)
d)
e)

f)
g)
h)
i)
j)

This job will be done on the 4th CWD of each month.


Search on the InfoPackage FULLDLT/2LIS_02_S805/ZBPPURZ02-ACT
FULLDLT/2LIS_02_S805/ZBPPURZ02-ACT
This will take you to the Purchasing Business Planning Special Infopackage Group (shown
below). This package group is within the Monthly_Transactional_Data_Info_Group 1
Infopackage Group.
Select the ACT FULLDLT Load (highlighted, below).
Double-click on the ACT (Actual) InfoPackage to open the Scheduler.

When the Scheduler opens, select the Select data Tab.


Check the Value type (ZVALTYPE) field has a From value of 010 (as in the screen below).
Because this Package is a FULLDLT,
FULLDLT it will delete the previous load when you run the
infopackage.
After verifying the value of the ZVALTYPE field, Click on the Schedule Tab.
Click the Start button to start the data load immediately.

Verify ZVALTYPE = 010

58

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


4.

Purchasing Bus Planning Special (cont)


a)
b)
c)
d)
e)

f)
g)
h)
i)
j)

This is the 2nd half of the Purchasing Business Planning Special job that will also be
done on the 4th CWD of each month.
Search on the InfoPackage FULLDLT/2LIS_02_S805/ZBPPURZ02-PLAN
FULLDLT/2LIS_02_S805/ZBPPURZ02-PLAN
This will take you to the Purchasing Business Planning Special Infopackage Group
(shown below) within the Monthly_Transactional_Data_Info_Group 1 Infopackage
Group.
Select the PLAN FULLDLT Load (highlighted, below).
Double-click on the PLAN InfoPackage to open the Scheduler.

When the Scheduler opens, select the Select data Tab.


Check the Value type (ZVALTYPE) field has a From value of 020 (as in the screen
below).
Because this Package is a FULLDLT,
FULLDLT it will delete the previous load when you run the
infopackage.
After verifying the value of the ZVALTYPE field, Click on the Schedule Tab.
Click the Start button to start the data load immediately.

Verify the ZVALTYPE field it


should be 020

59

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


5.

Product Costing Plan - Special


a)
b)
c)
d)
e)

f)
g)
h)
i)

This job will be done on the 4th CWD of each month.


This job will change the Planning Period on 2 Data Source Loads to the Current Fiscal
Period.
On the InfoPackage Group Screen do a search on FULL/2LIS_41_S907/ZBPPCZ01FULL/2LIS_41_S907/ZBPPCZ01ZPLANMON
ZPLANMON
This will take you to the InfoPackage Group Product
Product Costing Plan Special
Special (shown
below).
Double-Click on the first InfoPackage ..S907 (highlighted below).

On the Scheduler Screen, select the Select data tab. Scroll down to the bottom of the
table and find Planning
Planning Period ZPLANMON.
ZPLANMON
Change the From value to the current month. Using the screen below as an example:
If this was the 4th CWD of March, 2003. You would change the value below from 200302
to 200303.
Click the Check button and the save icon then go to the Schedule tab and run the
package.
Repeat these steps for the other InfoPackage in this group:
FULL/2LIS_41_S908/ZBPPCZ01 ZPLANMON.
ZPLANMON

Change Planning Period to


Current YYYYMM

60

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


6.

Finance - Monthly
a)
b)
c)
d)
e)

f)
g)
h)
i)
j)

This job will be done on the 4th CWD of each month before 2:00 PM.
This job will change the Planning Period on 2 Data Source Loads to the Current Fiscal
Period.
On the InfoPackage Group Screen do a search on FULL/0FI_AR_1/0FIAR_C02 FISCPER
This will take you to the InfoPackage Group Finance
Finance - Monthly
Monthly (shown below), within
the Monthly_Transactional_Data_Info_Group - 1.
1
Double-Click on the 1st FISCPER Infopackage: FULL/0FI_AP_1/0FIAP_C02FISCPER.
FISCPER

On the Scheduler Screen, select the Select data tab.


Change the FISCPER to the current month. Using the screen below as an example:
If this was the 4th CWD of March, 2003. You would change the value below from 200302
to 200303.
Click the Check button and the save icon.
Repeat these steps for the other FISCPER InfoPackage in this group:
FULL/0FI_AR_1/0FIAR_C02-FISCPER.
FULL/0FI_AR_1/0FIAR_C02-FISCPER
Double-click on the Entire Group Finance
Finance Monthly,
Monthly go to the Schedule Tab and
run the entire Group.

Change this value to the current


Fiscal year/period

61

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


7.

Finance Monthly 2
a)
b)
c)

d)

This job will be done on the 4th CWD of each month before 2:00 PM.
This job will consist of running 3 InfoPackages (shown below) within the InfoPackage
Group: Finance
Finance Monthly - 2
2 (shown below), within the
Monthly_Transactional_Data_Info_Group - 1.
1
Double-Click on the InfoPackage Group that is highlighted.

On the Scheduler Screen, go to the Schedule Tab and click on the Start button to run all
three Packages within the Group.

62

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


8.

EP Service Delivery Metrics - Monthly


a)
b)
c)

d)

This job will be done on the 4th CWD of each month before 2:00 PM.
This job will consist of running 1 InfoPackage (shown below) within the InfoPackage
Group: EP
EP Service Delivery Metrics - Monthly
Monthly (shown below), within the
Monthly_Transactional_Data_Info_Group - 1.
1
Double-Click on the InfoPackage FULLDLT/ZEMETRICS/ZSD_Z10
FULLDLT/ZEMETRICS/ZSD_Z10.

On the Scheduler Screen, go to the Schedule Tab and click on the Start button to run the
InfoPackage.

63

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


9.

CCA Actuals Monthly Final


a)
b)
c)
d)
e)

The CCA Actuals Monthly Final Special Job will be run on the 4th CWD of each month.
This job will be performed immediately after the normal daily network run of the CCA
FISCPER Load at appx. 10:30 PM.
The purpose of this job is to change the selection criteria for the Fiscal Period (FISCPER)
on the selected CCA Load.
On the InfoPackage Screen, open the Cost Center Acct Plan Daily Group ( highlighted
below).
Double-click (open) the InfoPackage FULL/0CO_OM_CCA_1/0CCA_C01-FISCPER

NOTE: This precedure will also be performed for the C and T Cluster InfoPackages:
C: FULL/0CO_OM_CCA_1/ZCC_CCA1 FISCPER and
T: FULL/0CO_OM_CCA_1/ZTC_CCA1 - FISCPER
f)
g)
h)

i)

Once in the InfoPackage, click on the Select data tab.


Verify that 0VTYPE = 010 and 0VERSION = 0
Change the FISCPER from the previous period (in this example it is 2003002) read as
year 2003, month 002 February, to 2003003. Note: The change on the 4th CWD will be
made to the previous month. So in this example, this change would not occur until the 4 th
CWD of April (so that the Fiscal Period displays the previous months data).
Save your changes then go to the schedule tab and click the start button to run the
infopackage.

64

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


10.

ZMM_C01 Change
a)
b)
c)
d)
e)

This job occurs monthly, on the 1st CWD of each month (see calendar).
This job changes the date in the ZBW_ZPCF/ZMM_C01 Current Plan Period to the
current Fiscal Period.
From the InfoPackage Group Screen do a search on FULL/ZBW_ZPCF/ZMM_CO1
FULL/ZBW_ZPCF/ZMM_CO1
Current Plan Period.
Period
This will take you to the InfoPackage Group shown below: IFC00092 Material Master
Daily R05
Double-click on the FULL/ZBW_ZPCF/ZMM_C01 Current Plan Period
Infopackage (highlighted, below).

Open this InfoPackage

f)
g)
h)
i)
j)

When the Scheduler Screen opens, select the Select data tab (as shown below).
Change the Planning Period (ZPLANNING) From Value,
Value to the current month.
From the example, below: On the 1st CWD of March, 2003 you would change the value
below to: 200303.
200303
Click the Check button, then click the save icon.
Go to the Schedule Tab and run the job.

Change Planning
Period select
data to current
fiscal period

65

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


11.

Reschedule Trans Data


a)
b)
c)
d)
e)

The purpose of this Special Job is to revise the scheduled start of the Transactional Data
Loads from Friday to Sunday night at 10:00 PM EST.
This procedure must be executed every Friday Afternoon, prior to the previously
scheduled kick-off of the Transactional Data Loads (at 10:00 PM EST)
The procedure below outlines how to make the necessary changes to the Scheduling of
Batch Job: Z_START_ISCTEMP. which starts the daily transactional data loads.
In GWP execute transaction /Nsm37
On the Simple Job Selection Screen select the options outlined on the screen below and
press the Execute Button..

Set jobname to Z*

Set User name to *


Select Sched. & Released for the
Job status

Blank out From & To (date) fields

Check Z_START_ISCTEMP

66

When the Job Overview Screen comes up select the Z_START_ISCTEMP job by checking the box to its left.

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions

11.

Reschedule Trans Data

(cont)

f)
g)
h)

With the Job name Z_START_ISCTEMP checked;


From the main menu tool bar, select Job.
From the Drop-down box, click on Change.

i)
j)

The Change Job screen will come up. On this screen notice the Start Date and Time.
Click on the Start Conditions button. This will bring up

g)

h)

j) Start Conditions

67

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


11.

Reschedule Trans Data


k)
l)
m)

(cont)

After clicking the Start Conditions button from the previous screen, this Start Time
window will appear. You will change the Scheduled Start date to run 2 days later.
The window below shows the Start Date as 02/24/2003 at 3:00 (am). If you look on a
calendar, this coincides with Monday, February 24th at 3:00 am (GMT).
Because of the system clock setting, and the fact that EST is 5 hours behind GMT this is
the sameas Sunday, February 23rd at 10:00 pm (EST).

Note: Be very careful of recognizing the time zone differences and the Schedules Start Time.

Change Scheduled start date by


2 days to run Sunday evening
Instead of Friday evening.

n)

n)
o)

Make sure Periodic job is checked

After youve made changes to this window, click the Check and the Save buttons.
Then close this window.

68

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


11.

Reschedule Trans Data


p)

(cont)

If you want to check that you rescheduled the job correctly, click on the Job details button
to bring up the detailed information on the Job Z_START_ISCTEMP as shown, below.

p) Job details button

Verify scheduled Start Date and time

q)

This Special Job Reschedule Trans Data - that is performed for the Job
Z_START_ISCTEMP (for C and G Clusters) will be duplicated for Job
Z_START_TRANSACTIONAL_TP1 (for the T Cluster).

Note: Repeat this procedure for the T Cluster Transactional Data Start Job
Z_START_TRANSACTIONAL_TP1.
a)
b)
c)

The Z_START_TRANSACTIONAL_TP1 Job will be changed in the same manner as the


Z_START_ISCTEMP Job.
You will change the Scheduled Start date to run 2 days later.
This will be the ONLY change made to this job.

69

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


12.

S958 V130 Prelim


a)

This Special Job is scheduled to be run on the 2nd CWD of each month.

Note: This job will ONLY be run per APO Notification. In other words, if APO does not
contact you and inform you that this needs to be run, then it will not be run.
b)
c)

d)

On the Infosources tab of the Administrator Workbench, do a search on datasource:


FULL/Z2LIS_41_S958/ZBPDSIZ01-VER. 130 DT. 2
It is located in the APO LIS SALES / USAGE COLLECTOR Infosource Group as seen
on the screen print below.

Double-click on the Infosource Package, go to the Schedule tab and click on the Start
button to run this package.

70

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


13.

S957 V100 Prelim


a)

This Special Job is scheduled to be run on the 2nd CWD of each month.

Note: This job will ONLY be run per APO Notification. In other words, if APO does not
contact you and inform you that this needs to be run, then it will not be run.
b)
c)

d)

On the Infosources tab of the Administrator Workbench, do a search on datasource:


FULL/2LIS_41_S957/ZBPDSIZ01 V.100
It is located in the Non R/3 Planned Demand, Supply, Inventory Infosource Group as
seen on the screen print below.

Double-click on the Infosource Package, go to the Schedule tab and click on the Start
button to run this package.

71

Transactional Data Processing


F.

Special Jobs Calendar & Descriptions


14.

S957 V100 Final


a)

This Special Job is scheduled to be run on the 5th CWD of each month.

Note: This job will ONLY be run per APO Notification. In other words, if APO does not
contact you and inform you that this needs to be run, then it will not be run.
b)
c)
d)

e)
f)

This job will do a refresh of the data on the Demand, Supply, Inventory cube
(ZBPDSIZ01).
On the Infosources tab of the Administrator Workbench, do a search on datasource:
FULL/2LIS_41_S957/ZBPDSIZ01 V.100
It is located in the Non R/3 Planned Demand, Supply, Inventory Infosource Group as
seen on the screen print below.

Double-click on the Infosource Package, go to the Schedule tab and click on the Start
button to run this package.
After the new load successfully completes, go to the Infocube, ZBPDSIZ01 and delete the
previous load.

72

Transactional Data Processing


Revisions

Revision
Number
001

Name
Alan Raichle

Date
03/07/2003

Description of Change
Original Version

73

Appendix 1 Answering Pages from the Data Center


1.
2.

While you are on call to monitor the BW Production Network you will be required to respond to pages
on the BW Production Support Beeper.
To respond to the pages call the T03 Production Network Support Call Center the phone # is:

(302) 292 9922 - when you hear the automated answering system - select Option 1 on your
phone.
Note: This number and an additional Support Center # are listed on the Pager.
3.
4.

Tell the Support personnel your name and that you are from the BW Support Team.
Generally, you will have to respond to 1 (one) of several different messages:
a)
The first type of reported failure (and the most common) is a BW_COMP job failure this page
will typically occur as a result of a failed BW Load that you can see on the GWP Monitor Screen.
In order to prevent this failure from holding up the network tell the support personnel to:
Consider the job

complete

Note: Since you will be continuously monitoring the network, most likely, you will be aware of this failure
and you will have already taken corrective action such as re-running a failed load.
b)

Another type of reported failure will be one of several Jobs (see descriptions on table below).
These are failures/delays on the Source System (GP1, CP1, or TP1) that are delaying BW
loads from occuring. BW loads depend on the successful completion of the R3 Jobs.
If you recognize the job name that the Support person gives you from the table below - instruct the
Support personnel to do the following:

Contact the responsible R/3 Support Personnel from the On-call rotation
for that job and inform them that their job is delayed..

74

Appendix 1 Answering Pages from the Data Center (cont)


R3 CONTROL-M JOB TABLE
DAILY JOBS
R3 Control-M
Job Name

R3 System

BW Job Name
Waiting

Normal BW
Start Time

Triggered Event
Scheduled

FICDPG00

C Cluster

BWBPDSID

7:00 AM

sap_bw_start_bp_p1_dsi_daily

FIGBPGAA

G Cluster

BWBPDALY

8:00 AM

sap_bw_start_bp_daily

FICSDG09

C Cluster

BWP1STC

8:00 AM

ZSTART_DAILY_C_STC

FIGARU43

G Cluster

BWFIAR

8:00 AM

sap_bw_start_fiar

FIGARU47
FIGBPG16

G Cluster
G Cluster

BWFIAREU
BWBPMNTH

8:00 AM
8:00 AM

GWP
GWP

BWMDATA
BWTRDATA

InfoPackage Grp/Cube Name


BP Demand Supply Daily
;ZCCBPDS1
IFC00047 -Demand Planning R05 - Daily ;ZBPDP_Z01-VER.100
DT.1 CUS. E ; IFC00073 Business Planning - APO - R05 Daily ;ZBPDSIZ01-VER. 100 DT.
2
C: Sales Daily ; ZCO_SD05,
ZCO_SD06, ZCO_SD07,
ZCO_SD08, ZCC_SD09
AR Transactional Data - Daily R05 ;ZFIAR_C01 & ZFIAR_C02

On Request - not scheduled


sap_bw_start_fiar_eu
sap_bw_start_bp_monthly

No Dependency on R/3 Control-M Jobs


14:00 EST sap_bw_start_daily_master_data
22:00 EST sap_bw_start_daily_network_isc

Responsible Team &


Phone #

R3 On-call Rotation

R3 On-call Rotation

R3 On-call Rotation
R3 On-call Rotation

R3 On-call Rotation
R3 On-call Rotation

Starts Master Data Loads


Starts Transactional Data Loads

MONTHLY JOBS
R3 Job #/
Name

R3 System

BW Job Name
Waiting

Normal BW
Start Time

BW Load Waiting

InfoPackage/Cube Name

Responsible Team &


Phone #

75

Appendix 2 System Messages


1.
2.
3.

At certain key times during the Production Network, you will be required to change / or
create a new system message in GWP that will be viewable by all subscribers of GWP.
There are currently 6 System Messages that are designed to alert BW Users of th current statuss
of 2 InfoObjects; the G-Cluster COPA Cube (ZCOPA_Z01) and the G-Cluster CCA (Cost Center
Analysis) Cube (0CCA_C01).
Below are the current 6 standard System Messages and their object status:

System Messages
1) ZCOPA_Z01 loads in progress; reporting not available.
2) ZCOPA_Z01 data loads complete; performance aggregates
in progress.
3) ZCOPA_Z01 available for reporting.
4) 0CCA_C01 loads in progress; reporting not available.
5) 0CCA_C01 data loads complete; performance aggregates in
progress.
6) 0CCA_C01 available for reporting.

3.

To apply these messages, enter transaction /nSM02 in GWP

This system message screen (/nSM02) has buttons that allow you to create or
change the current system message for either of the two objects (ZCOPA_Z01 or
0CCA_C01).

76

Appendix 3 System Architecture

77

Appendix 4 Instant Messenger

1.
2.

AOL (America On Line) Instant Messenger is a very popular and accepted method of communicating
with other members of Accenture or Dupont, when you are On-Line.
This service is free and can be downloaded at the following web site:

http://www.aim.com/
3.
4.

After you download the program from the Internet, you will be required to set up your AOL Instant
Messenger, depending on your location and whether you are connected to a LAN or to a Dupont
Server. Your technical support team should be able to assist you with this set-up.
To get to the Connection Preferences screen, once AIM is installed:
a.
Click on the Preferences button (wrench) at the bottom of the Sign-on window.
b.
That will bring up the preferences window (large window in the upper right).
c.
Click on the Sign On/Off Category.
d.
Click on the Connection button. This will bring up the;
e.
Connection Preferences window (bottom right window on the screen print below).
f.
The connection window is expanded on the next page to give you a little more detail.
Sign On/Off Category

Connection button

a. Preferences
Button

78

Appendix 4 Instant Messenger (cont)

5.

The Connection Preferences will allow you to set up the server name and Port. The active settings
below, are what we currently use to connect to AIM at our Delivery Centre. If we are using our dial-in
Modem on our laptops (connecting directly to the Dupont Network) we check the box Connect using
proxy. So, the Proxy Server settings are used to connect to the Dupont Network, and the Server
settings are used to connect to our Accenture Site. And to switch between the two settings, we would
just click on the Connect using proxy selection box.

This is currently set up


To connect to AIM thru the
Accenture Server at our
Delivery Center

Putting a checkmark in this


box will revise the server
settings so that we can connect
to the Dupont Network and still
access AIM

6.

These are additional AIM Servers that can be used in lieu of the cdgate.lvs.dupont.com server, if this
does not work:
a.
improxy-ae.dupont.com
b.
gunther.lvs.dupont.com

7.

Refer to the Contact Sheet for US Wilm BW Support Personnel AIM contact list.

79

Appendix 5 Dupont Control-M Holiday Calendar

2003
S M
5
12
19
26

6
13
20
27

S M
6
13
20
27

7
14
21
28

January
T W T
1 2
7 8 9
14 15 16
21 22 23
28 29 30
April
T W T
1 2 3
8 9 10
15 16 17
22 23 24
29 30

F
3
10
17
24
31

F
4
11
18
25

S
4
11
18
25

February
S M T W T F S S M
1
2 3 4 5 6 7 8 2 3
9 10 11 12 13 14 15 9 10
16 17 18 19 20 21 22 16 17
23 24 25 26 27 28
23 24
30 31

S S M
5
12 4 5
19 11 12
26 18 19
25 26

July
S M T
1
6 7 8
13 14 15
20 21 22
27 28 29

S M
5
12
19
26

6
13
20
27

W
2
9
16
23
30

T
3
10
17
24
31

October
T W T
1 2
7 8 9
14 15 16
21 22 23
28 29 30

F
4
11
18
25

F
3
10
17
24
31

S S
5
12 3
19 10
26 17
24
31
S
4
11
18
25

May
T W T
1
6 7 8
13 14 15
20 21 22
27 28 29

F
2
9
16
23
30

August
M T W T F
1
4 5 6 7 8
11 12 13 14 15
18 19 20 21 22
25 26 27 28 29

S S M
3 1 2
10 8 9
17 15 16
24 22 23
31 29 30

S S M
2
1
9 7 8
16 14 15
23 21 22
30 28 29

March
T W T F
4
11
18
25

S
1
5 6 7 8
12 13 14 15
19 20 21 22
26 27 28 29

June
T W T
3 4 5
10 11 12
17 18 19
24 25 26

F S
6 7
13 14
20 21
27 28

September
T W T F S
2 3 4 5 6
9 10 11 12 13
16 17 18 19 20
23 24 25 26 27
30

November
December
S M T W T F S S M T W T F S
1
1 2 3 4 5 6
2 3 4 5 6 7 8 7 8 9 10 11 12 13
9 10 11 12 13 14 15 14 15 16 17 18 19 20
16 17 18 19 20 21 22 21 22 23 24 25 26 27
23 24 25 26 27 28 29 28 29 30 31
30

= Dupont observed Holidays - for Control-M


* This is from the NDC_Scheduling CW Calendar for 2003. Blue (Holidays), are
treated as non-Calendar Work Days unless jobs are specified to run on these days they
will not.

80

Appendix 6 Contact / Phone List

Name

Position

Location

Vijay
Rajagopal_Nerur

Prod Spt
Lead

Wilmington, DE,
USA

Iliana Robeva

Prod Spt
Tech

Alan Raichle

Phone

E-Mail

EST
GMT-5

DUCOM
830-6166

Vijayaraghavan.R
ajagopal_Nerur@u
sa.dupont.com

VJNerur

Wilmington, DE,
USA

EST
GMT-5

DUCOM
830-5963

Iliana.Robeva
@usa.dupont.com

ilianabw

Prod Spt
Tech

Wilmington, DE,
USA

EST
GMT-5

DUCOM
830-6394

Alan.Raichle
@usa.dupont.com

AlanSRaich

T03 Prod Network


Data Center

Option 1

Newark, DE,
USA

EST
GMT-5

DUCOM
292-9922

NDC_Scheduling@
csc.com

Robert Ketterer

BW
Architect

Wilmington, DE,
USA

EST
GMT-5

DUCOM
830-5888

Robert.m.ketterer
@usa.dupont.com

Ketterrm

Lisa Goodwin

BW
Architect

Wilmington, DE,
USA

EST
GMT-5

DUCOM
830-6090

Lisa.K.Goodwin@u
sa.dupont.com

lisakgoodwin

Angie Gehrum

BWBasis

Cinncinati, OH,
USA

CST
GMT-6

DUCOM
683-6324

angie.gehrum
@usa.dupont.com

Angiegehrum

Brent Nawroth

BWBasis

Cinncinati, OH,
USA

CST
GMT-6

DUCOM

brent.nawroth
@usa.dupont.com

brentnawroth

Dharshan Kapadia

BWBasis
(Off Hrs
Support)

Dharshan.Kapadia
@usa.dupont.com

dkapadia22

BW Beeper (Page)
Dupont Dial-in
Number

Wilmington, DE,
USA

Time
Zone

EST
GMT-5

AIM

DUCOM

Modem
connect
to
Dupont

1-800215 6957

Modem
connect
to
Dupont

1 800
870 4940

81