PTP job monitoring procedure has been categorized as follows in accordance with the criticality of the job schedule and its impact on the depending PTP processes.
The list of scheduled jobs is present in the Monitoring Catalog on sharepoint.
Monitoring Process | Module | System | Automatic Jobs | Manual jobs |
|---|---|---|---|---|
SAP background jobs | SAP MM | PF1-020 PF1-050 WP1-400 | In case of job failure, automatic freshdesk ticket will be created
| MMPV jobs for MM period opening and closing, PRS System (PF1-050)
|
SAP SRM | BP2 | Jobs to be monitored manually
| ||
| AP | PF1-020 WP1-400 | In case of job failure, automatic freshdesk ticket will be created
| Readsoft jobs should be handled manually
| |
Readsoft Vendor Loading | AP | Readsoft WP1-400 | Vendor Loading on Readsoft Platform
| |
B-Process Variant IDocs | AP | WP1-400 | IDOCS status
| |
Xerox Variant IDocs | AP | WP1-400 | IDOCS status
|
The monitoring catalog shall be imperatively updated whenever there is a change in the schedule of the job run.
The background jobs for the systems PF1-020 and WP1-400 are regularly checked by the automator.
Below are the specific list of jobs that are monitored by the automator.
Note : In case of a job failure, an automatic fresh desk ticket shall be created under the category Service Monitoring .This ticket has to be checked by the L1 member whether it falls under the L1 scope of resolution. If not, it has to be transferred to L2 immediately for further analysis.
The basic procedure for checking the job status in SAP system is given in the following article.
Systems : PF1-020 and WP1-400
The list of period opening/closing jobs is present in the monitoring catalogue.
If the jobs fail, the MM period have to be closed manually in order not to block the business activities.
Systems : BP2, PRS (PF1-050)
The jobs listed for BP2 system and PRS system in the monitoring catalogue have to be manually monitored daily. In case of any job failure (missing), it has be to escalated to the L2 team via mail.
Systems : WP1-400
The readsoft jobs has to be monitored on a daily basis. The list is given in the monitoring catalog.
Check if the job is in error or missing with the job list file. Missing indiactes that when it is executed, the following error is shown.
| No job matches the selection criteria |
|---|
→ In case of job missing : Send a mail to IBM - solvoper@in.ibm.com with the name of files to be processed in the graph XX and application YY copying the following people.,
→ In case of job failure : Display the job log to see the error, L1 team will try to resolve the issue as per their knowledge. Else, create a Fresh desk ticket with job error details and assign it to L2 PTP-AP team and inform them about the ticket via email.
Twice a week vendors are loaded on READSOFT platform. This process starts in RCS and finishes in READSOFT platform.
Time | Application and Job name/Description |
| Saturday, 08:00 AM French time | RCS : Job FI_ZWFAO04400_S |
| Sunday, 02:20 AM French time | READSOFT : Loading vendors |
| Thursday, 03:00 AM French time | RCS : Job FI_ZWFAO04400 |
| Thursday, 03:30 AM French time | READSOFT : Loading vendors |
NOTE: This checking must be done only on the Monday and Thursday morning French time.
The detailed procedure for checking Readsoft Vendor Loading is given in the following confluence article.
The objective is to check that there is no IDOC in error. The detailed procedure for checking B-Process Variant Idocs is given in the following confluence article.
The objective is to check that there is no IDOC in error. The detailed procedure for checking B-Process Variant Idocs is given in the following confluence article.
| You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
|