Oakley Support Priority: Medium

AFS2

Re-processing a failed RO in Background Job

Oakley uses a Z program called ZDELIVERY_TO_CREATE_ALT to create Return
deliveries and PGI. A background job is scheduled that executes the above
program at regular intervals. However, at times due to unknown reasons, the
background job fails while processing an RO. In such a case, the RO has to be
processed manually using the same program. The below mentioned steps need to
be performed.

The Steps:
Step 1:

Go to T-Code SM37 and enter inputs as below:

Just change the date to the latest date.

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

If the Status is Cancelled, select the Job and click Job Log. Do it for all the Cancelled Jobs.

Step 2:

Now Scroll down to the bottom to see for which RO the processing has failed. Here it is 1520011445.

Step 3:

Now, go to the next cancelled job and search for this failed RO to see if the same has been processed
here. If not, then scroll down again to the last RO where processing failed and see if it is the same RO

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

from the previous job. Sometimes, it is the same RO while at other times it is a different. If different,
note down the RO number and search for it in the next failed job along with the previous one.

Now, if there are any finished jobs, search for these ROs in them. The program is designed to pick any
failed ROs in the next job. If you find the RO in the finished job, take a screenshot and save it. See the
snapshot below for example. This RO 1520012256 had failed in a previous job but picked up and
processed successfully in the next job.

If you do not find the failed RO in any of the jobs (cancelled as well as finished), go to Step 4.

Step 4:

Go to SE38 and enter program name ZDELIVERY_TO_CREATE_ALT.

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

Click Execute and you will arrive at the below screen.

Step 5:

Enter the RO number and execute again.

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

If the operation is successful, you will get the following message or something similar.

If the operation is not successful, you will get the following message instead. If you get a similar message
as below, go back and execute gain. You may have to execute it up to three times to get the success
message.

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

If you continue to get error message despite processing it up to three times, there may be some master
data issues which you need to investigate and resolve. Inform your Business User about it and
investigate the problem.

Note: Always create an Incident in Remedy with priority Medium when you have to manually reprocess
a failed RO. Then document the processing and save it. The naming convention should be as follows:

Incident Number_Date_Month_Year

The header of the document must contain the Incident Number, Date and Status of the Incident.

The naming convention for saving the screenshot of a failed RO successfully processed in the next job is
the RO number itself.

Jobs: LUX_RETURNS_PROCESSING_EMAIL_01; LUX_RETURNS_PROCESSING_EMAIL_02;

LUX_RETURNS_PROCESSING_EMAIL_03

Prepared by: Pankaj Khatoniar

LE Consultant
Oakley Support Priority: Medium
AFS2

Prepared by: Pankaj Khatoniar

LE Consultant