Customizing LCT File: Concurrent Program download LCT File(afcpprog.lct)

Usually we do not require ALL the Concurrent Programs for a Custom schema to be downloaded to an LCT File unless it’s an initial CUSTOM Object migration (or) Data reconciliation (or) Mass update of some fields.

The FNDLOAD Command SYNTAX to download the Program is as below
FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXXYY_TEST_CP.ldt PROGRAM APPLICATION_SHORT_NAME="XXXYY" CONCURRENT_PROGRAM_NAME="XXXYY_TEST_PRG"


This would download a specific concurrent program and does the job, and I believe an human error can cause a misery to the case if any of the parameters say for ex:CONCURRENT_PROGRAM_NAME is misspell or an underscore missing. Let’s assume the same command as below replacing CONCURRENT_PROGRAM_NAME with CONCURRENT_PROGRAM_NAME1. The FNDLOAD command ignores the second parameter and fetches the complete Application level Programs to an LDT File.

FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXXYY_TEST_CP.ldt PROGRAM APPLICATION_SHORT_NAME="XXXYY" CONCURRENT_PROGRAM_NAME="XXXYY_TEST_PRG"

Sometimes this discrepancy can be identified/caught by opening the file, File size, doing tests in the test environment and these can still be missed at a crucial time causing haywire

And also Suppose there are only 2-5 Concurrent Programs then those 2-5 Concurrent Programs will be downloaded instead of a particular program causing you to believe the size of the file.

To avoid this, the customized the LCT File to download the Program only if CONCURTRENT_PROGRAM_NAME parameter is provided. This goes to the underlying Logic in the LCT File where it considers NULL Application names and NULL Concurrent Program names. Deleting the respective Clauses in the SQL Statements should do the trick for you.

CUSTOM LCT File Upload

Print This Post