Concurrent request output files

Concurrent request output files

When you work with EBS software you are bound to come across concurrent programs and concurrent requests.

Concurrent requests are administered in the table "FND_CONCURRENT_REQUESTS". This table contains columns named "OFILE_SIZE" and "OUTFILE_NAME". Digging deeper into these entries, you will soon realise that "OUTFILE_NAME" not always references the requests end result. This has to do with the OPP for which I may some day do an other post.

Bottom line is that the actual end result is stored in a different table: "FND_CONC_REQ_OUTPUTS".

APPS@EBS>desc FND_CONC_REQ_OUTPUTS
Name                  Null?    Type
--------------------- -------- -------------
CONCURRENT_REQUEST_ID NOT NULL NUMBER
OUTPUT_ID             NOT NULL NUMBER
FILE_TYPE             NOT NULL VARCHAR2(30)
FILE_NAME             NOT NULL VARCHAR2(255)
FILE_NODE_NAME        NOT NULL VARCHAR2(255)
FILE_SIZE                      NUMBER
ACTION_TYPE                    NUMBER
FILE_CREATION_DATE    NOT NULL DATE

Ofcourse the CONCURRENT_REQUEST_ID is a reference to the base table. Bonus loot; you get the "FILE_TYPE" too!