Shulou(Shulou.com)06/01 Report--

In EBS concurrent requests, you can set up a schedule to run regularly, which is stored in the fnd_conc_release_classes table and associated with the request table fnd_concurrent_requests through release_class_id.

The details are as follows:

RELEASE_CLASS_ID: primary key, associated with fnd_concurrent_requests.

CLASS_TYPE: contains value 'P'for "Periodic" schedules, 'S'for "on Specific Days" schedules and' X 'for "advanced schedules". P: regular, S: on a specific date, X: advanced

DATE1: start date of the schedule ("Start at" field in the form) start date

DATE2: end date of the schedule ("End at" field in the form), as fnd_concurrent_requests.resubmit_end_date termination date

CLASS_INFO: this is the most interesting field as it contains all the information needed for rescheduling. The format of the field depends on the type of schedule. Data formats vary depending on the type of plan.

"PERIODIC" schedule: periodically

In case of Periodic schedule fnd_conc_release_classes.CLASS_INFO field contains values like "2:D:S" or X:Y:Z where:

X-number of months/weeks/days/hours/minutes the request has to be rescheduled from prior run.

Y-contains a single letter representing units

"M"-months

"D"-days

"H"-hours

"N"-minutes

(there is no representation of "weeks" option. If you specify interval in weeks, it's automatically calculated and stored in "days").

Z-contains a single letter to represent if the rescheduling has to be done from start or from completion of the prior run

S-from the start of the prior run

C-from the completion of the prior run.

Some samples:

30:N:S-Repeat every 30 minutes from the start of the prior run

5:N:C-Repeat every 5 minutes from the completion of the prior run

12:H:S-Repeat every 12 hours from the start of the prior run

It's interesting that information about intervals of periodic schedules is duplicated infnd_concurrent_requests table fields RESUBMIT_INTERVAL, RESUBMIT_INTERVAL_TYPE_CODE and RESUBMIT_INTERVAL_UNIT_CODE.

"ON SPECIFIC DAY" schedule: on a specific date

In case of on Specific Day schedule fnd_conc_release_classes.CLASS_INFO field contains values like "000010000000000000000000000000010000000"-a 39 character value consisting of 0 and 1. The idea ist hat the placement of 1 Murs represent the options selected through form:

1murs at places 1 to 31-represent dates, when request has to be run, eg, if the 10th character is "1"-the request is scheduled to run on 10th day of each month

Character "1" at the 32nd position-specifies that the request has to be run at the last day of each month

1Murs at places 33 to 39-specifies days of week (Sunday-Saturday) the request has to be run. If the 33rd character is "1"-the request is scheduled to run each Sunday, if 34th-on Monday and so on.

Some samples:

0000000000000000000000000000000000000000000000000000001-Days of week: Sa

1111111110000000000000000000000111110-Dates: 1 2 3 4 5 6 7 8 9. Days of week: Mo Tu We Th Fr

00000000000000000000000000000000010000000-Last day of month

Finally, I enclose a paragraph of SQL:

SELECT r.Request_Id P.User_Concurrent_Program_Name | | CASE WHEN p.User_Concurrent_Program_Name = 'Report Set' THEN (SELECT' -'| | s.User_Request_Set_Name FROM Fnd_Request_Sets_Tl s WHERE s.Application_Id = r.Argument1 AND s.Request_Set_Id = r.Argument2 AND LANGUAGE =' US') WHEN p.User_Concurrent_Program_Name = 'Check Periodic Alert' THEN (SELECT' -'| | a.Alert_Name FROM Alr_Alerts a WHERE a.Application_Id = r.Argument1 AND a.Alert_Id = r.Argument2 AND LANGUAGE = 'US') END Concurrent_Program_Name CASE WHEN p.User_Concurrent_Program_Name! = 'Report Set' AND p.User_Concurrent_Program_Name! =' Check Periodic Alert' THEN r.Argument_Text END Argument_Text, r.Requested_Start_Date Next_Run, r.Hold_Flag On_Hold, Decode (c.Class_Type, 'playing,' Periodic' Schedule_Type, CASE WHEN c.Class_Type ='P 'THEN' Repeat every'| Substr (c.Class_Info, 1, Instr (c.Class_Info) ':)-1) | | Decode (Substr (c.Class_Info, Instr (c.Class_Info,':', 1, 1) + 1, 1), 'minutes',' months' 'hacks,' hours', 'Downs,' days') | | Decode (Substr (c.Class_Info, Instr (c.Class_Info,':', 1,2) + 1,1) WHEN c.Class_Type = 'S'THEN Nvl2 (Dates.Dates,' Dates:'| | Dates.Dates | | from the completion of the prior run') WHEN c.Class_Type. ', NULL) | | Decode (Substr (c.Class_Info, 32,1),' 1percent, 'Last day of month) | | Decode (Sign (To_Number (Substr (c.Class_Info, 33),' 1percent, 'Days of week:' | Decode (Substr (c.Class_Info, 33,1),'1' 'Su') | | Decode (Substr (c.Class_Info, 34,1), '1percent,' Mo) | | Decode (Substr (c.Class_Info, 35,1), '1percent,' Tu) | | Decode (Substr (c.Class_Info, 36,1), '1percent,' We') | Decode (Substr (c.Class_Info, 37) 1), '1percent,' Th') | | Decode (Substr (c.Class_Info, 38,1), '1percent,' Fr) | | Decode (Substr (c.Class_Info, 39,1), '1percent,' Sa)) END Schedule, c.Date1 Start_Date, c.Date2 End_Date, c.Class_Info FROM Fnd_Concurrent_Requests r Fnd_Conc_Release_Classes c, Fnd_Concurrent_Programs_Tl p, (SELECT Release_Class_Id, Substr (MAX (Sys_Connect_By_Path (s,')), 2) Dates FROM (SELECT Release_Class_Id, Rank () Over (PARTITION BY Release_Class_Id ORDER BY s) a S FROM (SELECT c.Class_Info, l, c.Release_Class_Id, Decode (Substr (c.Class_Info, l, 1),'1' To_Char (l)) s FROM (SELECT LEVEL l FROM Dual CONNECT BY LEVEL SYSDATE AND c.Class_Type IS NOT NULL AND p.Concurrent_Program_Id = r.Concurrent_Program_Id AND p.Application_Id = r.Program_Application_Id AND p.Language = 'US' AND Dates.Release_Class_Id (+) = r.Release_Class_Id ORDER BY On_Hold, Next_Run

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.