ABAP-Damodhier-Deepak - 2016-04-13 - 26515 - Spec - Chainlink Job Error Messages (Dan by 2016-04-29) #Delivery #SDSupportShipping

SPECIFICATIONS

26515-Spec-Chainlink Job Error Messages

Purpose


Chainlink Job Error Messages

Admin Info


Purpose
Chainlink Job Error Messages
Requested By
Daniel Brennan
Spec Created By
Damodhier
Spec Created Date
04/18/2016
Spec QA by
Damodhier
Objects
ZSD_CHAINLINK_JOB
Document Status
Completed


Estimates



Sl.No
Activity
Estimation in Hours
1
Research
06
2
Documentation
02
3
Development/ Config
08
4
Unit test in DEV
04
5
Unit test in QUA
00
6
Other activity
00

TOTAL
20

References


Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]


Documents
[Attach any document(s) received for the requirement(s)]

Job Fail.JPG
Job Fail.JPG


Job Fail Reason.png
Job Fail Reason.png


Spec Changes


[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]

Sl.
Change Details
Requested By
Requested On
Notes if any

























Functional Requirement


Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]
If no file is available for the Chainlink job to process, the job is ending with cancelled status. This shouldn't occur when there is no file in the directory.

In Scope:

[List the activities to be included in scope]
Only the ZCHAINLINK_DEL_UPD job is involved.
Chainlink Job will trigger only if the input file is available in the directory.

Out of Scope:

[Out of scope activities]
No other job is in scope.

Solution Summary


[Discuss this section with Requester and get approval prior to beginning work]
A custom program should be created to check the availability of the input file.
1.If the file exists, then the custom program will raise an event to trigger the chain link job.
2.If the file doesn't exist, custom program will not raise an event, hence chain link job will not be triggered.

To achieve this:
1. A daily job is scheduled for the custom program
2. The chainlink job start condition needs to be modified from daily to after event.

Test Plan

[List test scenarios/cases to be executed here]
Test ID
Test Scenario
Expected Results
SD-001
Schedule job for the custom program without a file in the directory.
The ZCHAINLINK_DEL_UPD job shouldn't be triggered.
SD-002
Schedule job for the custom program with a file in the directory.
The ZCHAINLINK_DEL_UPD job should be triggered.

Solution Details

[Provide complete technical details for configuration or programming here]
1. Created an Event 'ZSD_TRIGGER_CHAINLINK_JOB'
2. Chain Link job schedule to be changed to Event Periodic
3. Created a program 'ZSD_CHAINLINK_JOB', which checks the existence of the input file to process the chain link job. If input file exists then custom program will raise event '
'ZSD_TRIGGER_CHAINLINK_JOB' - which will trigger the Chain Link Job.

4.Attached document has the steps for the new custom job set up.(For reference)

Steps to create Chainlink job using Event.docx

Issues


[List Issues / Bugs identified in configuration or development]