CIF and Batch Job Monitoring Guidelines

CIF – Transfer of master and transactional data from SAP R3 to APO and vice versa

Monitoring Tool / Problem / Action / Follow Up
Transaction SMQ1 in R3 and APO / Number of displayed entries greater than 25000 / Execute Generic Queue Activation as per document
Transaction SMQ1 in R3 and APO / Number of displayed entries greater than 40000 – After activating generic queue a few times / Contact FUNCTIONAL AFTER HOURS SUPPORT. / Monitor queue and activate queue generically every 15 mins
Transaction SMQ1 in R3 and APO / Number of displayed entries remain greater than 30000 – After activating generic queue and 7:00pm batch schedule is due to commence shortly / STOP the running of the CIF_** jobs in the 7:00pm batch schedule. START the schedule at job JC_D_RE030. / Monitor Queueand activate queue generically every 15 mins

Running of Compare and Reconcile report – Check before running

Monitoring Tool / Problem / Action / Follow Up
Transaction SMQ1 in R3 / Number of displayed entries greater than 25000 / DO NOT EXECUTE Compare & Reconcile report. Follow action from above.
Transaction SM37 in R3 / CIF jobs from the 7:00pm batch run have not been completed / DO NOT EXECUTE Compare & Reconcile report.
Check CIF queue and follow actions from CIF instructions.
General / Compare & reconcile report has not been completed by the time the 12:00am batch schedule starts in APO. / STOP running the compare & reconcile report. / Resume running of the report after the batch schedule has been completed – job PP_D_HEU_RPM

Monitoring of batch schedule – Critical Jobs

Monitoring Tool / Critical Jobs / Action
Transaction SM37 in R3 and APO / The CIF_** daily jobs from 7:00pm should run for approximately 1.5 hours in total.
If any CIF_** jobs apart from CIF_D_MD_10 runs longer than 20mins , check the CIF queue … and action as appropriate. / Check the CIF queue and action appropriately
Transaction SM37 in R3 and APO / If any of the CIF_** jobs fail. / Retry once then skip.
Transaction SM37 in R3 and APO / If the following jobs fail , SNP_W_ESSCOP2D, SNP_W_ESSCOP2M, SNP_W_ESSCOP2C, SNP_W_ESSCOP3D, SNP_W_ESSCOP3M, SNP_W_ESSCOP3C, SNP_W_ESSCOP1, SNP_D_DSS, SNP_D_ESSCOPY. / Retry once then skip.
Transaction SM37 in R3 and APO / If the following jobs fail , PP_D_HEU , SNP_D_DEP_MANUF and SNP_D_DEP_DC / Contact FUNCTIONAL AFTER HOURS SUPPORT.
Transaction SM37 in R3 and APO / If PP_D_HEU runs for longer than 2 hours.
If PP_D_HEU_RPM runs for longer than 1 hour. / Contact FUNCTIONAL AFTER HOURS SUPPORT.

Monitoring of batch schedule – Critical Jobs – Demand Planning

Monitoring Tool / Critical Jobs for Action / Action / Follow Up
Transaction SM37 in APO / If any run longer than indicated, take action -
Sunday night schedule
DP_W_FCST010M (3hours)
DP_W_FCST010D (3 hours)
DP_W_FCST010C (3 hours)
DP_W_LOAD010M (40 mins)
DP_W_LOAD010D (40 mins)
DP_W_LOAD010C (40 mins)
Wednesday night schedule
DP_W_CONS020C (2.5hours)
DP_W_CONS020D (2.5hours)
DP_W_CONS020M (2.5hours)
DP_W_LOAD010PR (1.5 hours)
DP_W_TRFR030PR_R3 (1.5 hours)
DP_W_TRFR010PR (1.5 hours) / If any of these jobs FAIL, or DO NOT RUN within parameters (refer flowchart), Call After Hours FUNCTIONAL Support.

Prepared by Naeem Hanif – Dairy Farmers Business Solutions

Page 1 of 3