Random JobNum Change

Yahoo Archive
1
FINALLY I think I have traced this down. This seems to be happening randomly on an updateable dashboard. I messed w/ this thing for an hour trying to get it to pull correct data (A whole other issue) and then the notification I set triggered the change. I am not even sure how I did it. I was just refreshing & may have hit save. It is a pretty busy dashboard and the only thing that is "suppose" to update is the Close & Complete checkboxes. I have no formal training on this, so can someone tell me what caused that ? And how to program / setup the dashboard to prevent it. The dashboard seems to be random at times w/ its refresh (which is what I was working on). I would also like to know why that is as well.

Brenda

From: brenda mohr
Sent: Friday, April 05, 2013 9:32 AM
To: 'vantage@yahoogroups.com'
Subject: Random JobNum Change


Recently We have noticed an anomaly with some of our jobs. The jobs have "wrong" PartNums attached to them. Or as it was explained to me, the JobNums have been changed. This is the code that has been tagged as suspect, but I dont see how... Is it possible and if so how? All this is "suppose" to do is trigger the job to schedule. It is part of a BPM attached to Post-Process OrderJobWiz.CreateJobs.

Brenda (9.05.607B)

{Bpm/Bpm.i &OBJECT_NAME="OrderJobWiz" &BPM_BO_SOURCE_BO=1 &CUSTCODE=1 &CUR-COMP=""}
{Bpm/MiscCallContext.i}
{core/UserDefinedData.i "new global"}

{bo/ScheduleEngine/ScheduleEngine_ds.i}

procedure CreateJobsAfter:
define input-output parameter dataset for OrderJobWizDataSet.
define input-output parameter pErrorMessages as character.
{&TRY_PRIVATE}
DEF VAR vh-Schedule AS HANDLE NO-UNDO.
DEF VAR l_finished AS LOGICAL.
DEF VAR c_warnlogtxt AS CHAR.

DEF VAR jobNum AS CHAR.

FOR EACH ttJWJobHead:
jobNum = ttJWJobHead.JobNum.

/*Start running the Customer persistent object*/
RUN bo\ScheduleEngine\ScheduleEngine.p PERSISTENT SET vh-Schedule.

IF VALID-HANDLE (vh-Schedule) THEN DO:

RUN GETScheduleRecord IN vh-Schedule ({&INPUT-OUTPUT_dataset_ScheduleEngineDataSet}).
FIND FIRST ttScheduleEngine.
ASSIGN
ttScheduleEngine.JobNum = jobNum
ttScheduleEngine.Finite = TRUE.

RUN MoveJobItem IN vh-Schedule ({&INPUT_dataset_ScheduleEngineDataSet}, OUTPUT l_finished, OUTPUT c_warnlogtxt).

END.
END.

{&CATCH_PRIVATE}
end procedure.

Brenda (9.05.607B)


[Non-text portions of this message have been removed]
2
Recently We have noticed an anomaly with some of our jobs. The jobs have "wrong" PartNums attached to them. Or as it was explained to me, the JobNums have been changed. This is the code that has been tagged as suspect, but I dont see how... Is it possible and if so how? All this is "suppose" to do is trigger the job to schedule. It is part of a BPM attached to Post-Process OrderJobWiz.CreateJobs.

Brenda (9.05.607B)

{Bpm/Bpm.i &OBJECT_NAME="OrderJobWiz" &BPM_BO_SOURCE_BO=1 &CUSTCODE=1 &CUR-COMP=""}
{Bpm/MiscCallContext.i}
{core/UserDefinedData.i "new global"}

{bo/ScheduleEngine/ScheduleEngine_ds.i}

procedure CreateJobsAfter:
define input-output parameter dataset for OrderJobWizDataSet.
define input-output parameter pErrorMessages as character.
{&TRY_PRIVATE}
DEF VAR vh-Schedule AS HANDLE NO-UNDO.
DEF VAR l_finished AS LOGICAL.
DEF VAR c_warnlogtxt AS CHAR.

DEF VAR jobNum AS CHAR.

FOR EACH ttJWJobHead:
jobNum = ttJWJobHead.JobNum.

/*Start running the Customer persistent object*/
RUN bo\ScheduleEngine\ScheduleEngine.p PERSISTENT SET vh-Schedule.

IF VALID-HANDLE (vh-Schedule) THEN DO:

RUN GETScheduleRecord IN vh-Schedule ({&INPUT-OUTPUT_dataset_ScheduleEngineDataSet}).
FIND FIRST ttScheduleEngine.
ASSIGN
ttScheduleEngine.JobNum = jobNum
ttScheduleEngine.Finite = TRUE.

RUN MoveJobItem IN vh-Schedule ({&INPUT_dataset_ScheduleEngineDataSet}, OUTPUT l_finished, OUTPUT c_warnlogtxt).

END.
END.

{&CATCH_PRIVATE}
end procedure.

Brenda (9.05.607B)


[Non-text portions of this message have been removed]
3
Brenda,

I highly doubt your code is changing the job number, but I'm sure one of our resident programmers will verify! I would bet that someone is changing the part number on the job, which is more likely.

One way to see what is happening is to turn on change logs. Have the system check on job number and part number and see what is happening for sure.

You can turn on change logs under Business Activity Management, which is under Executive Analysis. Pick the jobHead table and track changes on these two fields. This way you could catch the "person" making changes, if it is truly someone doing this and forgetting they did it.

Manasa












From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of brenda mohr
Sent: Friday, April 05, 2013 8:31 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Random JobNum Change



Recently We have noticed an anomaly with some of our jobs. The jobs have "wrong" PartNums attached to them. Or as it was explained to me, the JobNums have been changed. This is the code that has been tagged as suspect, but I dont see how... Is it possible and if so how? All this is "suppose" to do is trigger the job to schedule. It is part of a BPM attached to Post-Process OrderJobWiz.CreateJobs.

Brenda (9.05.607B)

{Bpm/Bpm.i &OBJECT_NAME="OrderJobWiz" &BPM_BO_SOURCE_BO=1 &CUSTCODE=1 &CUR-COMP=""}
{Bpm/MiscCallContext.i}
{core/UserDefinedData.i "new global"}

{bo/ScheduleEngine/ScheduleEngine_ds.i}

procedure CreateJobsAfter:
define input-output parameter dataset for OrderJobWizDataSet.
define input-output parameter pErrorMessages as character.
{&TRY_PRIVATE}
DEF VAR vh-Schedule AS HANDLE NO-UNDO.
DEF VAR l_finished AS LOGICAL.
DEF VAR c_warnlogtxt AS CHAR.

DEF VAR jobNum AS CHAR.

FOR EACH ttJWJobHead:
jobNum = ttJWJobHead.JobNum.

/*Start running the Customer persistent object*/
RUN bo\ScheduleEngine\ScheduleEngine.p PERSISTENT SET vh-Schedule.

IF VALID-HANDLE (vh-Schedule) THEN DO:

RUN GETScheduleRecord IN vh-Schedule ({&INPUT-OUTPUT_dataset_ScheduleEngineDataSet}).
FIND FIRST ttScheduleEngine.
ASSIGN
ttScheduleEngine.JobNum = jobNum
ttScheduleEngine.Finite = TRUE.

RUN MoveJobItem IN vh-Schedule ({&INPUT_dataset_ScheduleEngineDataSet}, OUTPUT l_finished, OUTPUT c_warnlogtxt).

END.
END.

{&CATCH_PRIVATE}
end procedure.

Brenda (9.05.607B)

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]