eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.AK_ON_OBJECTS_PVT dependencies on STANDARD

Line 108: -- Results The procedure returns the standard p_return_status parameter

104: --
105: -- Desc Appends all elements in the from_table to the end of the
106: -- to_table. Both tables must be of type Buffer_Tbl_Type.
107: --
108: -- Results The procedure returns the standard p_return_status parameter
109: -- indicating one of the standard return statuses :
110: -- * Unexpected error
111: -- * Error
112: -- * Success

Line 109: -- indicating one of the standard return statuses :

105: -- Desc Appends all elements in the from_table to the end of the
106: -- to_table. Both tables must be of type Buffer_Tbl_Type.
107: --
108: -- Results The procedure returns the standard p_return_status parameter
109: -- indicating one of the standard return statuses :
110: -- * Unexpected error
111: -- * Error
112: -- * Success
113: -- Parameters p_from_table : IN required

Line 160: -- Usage Private procedure for writing standard header information

156:
157: --==============================================
158: -- Procedure DOWNLOAD_HEADER
159: --
160: -- Usage Private procedure for writing standard header information
161: -- to a loader file.
162: -- This procedure is intended to be called only by other APIs
163: -- that are owned by the Core Modules Team (AK)
164: --

Line 165: -- Desc This procedure writes all the standard header information

161: -- to a loader file.
162: -- This procedure is intended to be called only by other APIs
163: -- that are owned by the Core Modules Team (AK)
164: --
165: -- Desc This procedure writes all the standard header information
166: -- including the DEFINE section to the loader file.
167: --
168: -- Results The API returns the standard p_return_status parameter
169: -- indicating one of the standard return statuses :

Line 168: -- Results The API returns the standard p_return_status parameter

164: --
165: -- Desc This procedure writes all the standard header information
166: -- including the DEFINE section to the loader file.
167: --
168: -- Results The API returns the standard p_return_status parameter
169: -- indicating one of the standard return statuses :
170: -- * Unexpected error
171: -- * Error
172: -- * Success

Line 169: -- indicating one of the standard return statuses :

165: -- Desc This procedure writes all the standard header information
166: -- including the DEFINE section to the loader file.
167: --
168: -- Results The API returns the standard p_return_status parameter
169: -- indicating one of the standard return statuses :
170: -- * Unexpected error
171: -- * Error
172: -- * Success
173: -- Parameters p_nls_language : IN optional

Line 2053: -- Results The API returns the standard p_return_status parameter

2049: -- and query object data
2050: -- (including all the tables in these business objects)
2051: -- from the loader file, and update them to the database.
2052: --
2053: -- Results The API returns the standard p_return_status parameter
2054: -- indicating one of the standard return statuses :
2055: -- * Unexpected error
2056: -- * Error
2057: -- * Success

Line 2054: -- indicating one of the standard return statuses :

2050: -- (including all the tables in these business objects)
2051: -- from the loader file, and update them to the database.
2052: --
2053: -- Results The API returns the standard p_return_status parameter
2054: -- indicating one of the standard return statuses :
2055: -- * Unexpected error
2056: -- * Error
2057: -- * Success
2058: -- Parameters

Line 2871: -- Results The API returns the standard p_return_status parameter

2867: -- Desc This procedure parses the input string and returns the first
2868: -- token in the string. It then removes that token from the
2869: -- input string.
2870: --
2871: -- Results The API returns the standard p_return_status parameter
2872: -- indicating one of the standard return statuses :
2873: -- * Unexpected error
2874: -- * Error (including parse error, such as empty input string)
2875: -- * Success

Line 2872: -- indicating one of the standard return statuses :

2868: -- token in the string. It then removes that token from the
2869: -- input string.
2870: --
2871: -- Results The API returns the standard p_return_status parameter
2872: -- indicating one of the standard return statuses :
2873: -- * Unexpected error
2874: -- * Error (including parse error, such as empty input string)
2875: -- * Success
2876: -- The procedure returns the first token in the input string

Line 2992: -- Results The API returns the standard p_return_status parameter

2988: -- A logical line may contain many physical lines in the
2989: -- file, each except the last physical line has a trailing
2990: -- character indicating that the line is to be continued.
2991: --
2992: -- Results The API returns the standard p_return_status parameter
2993: -- indicating one of the standard return statuses :
2994: -- * Unexpected error
2995: -- * Error
2996: -- * Success

Line 2993: -- indicating one of the standard return statuses :

2989: -- file, each except the last physical line has a trailing
2990: -- character indicating that the line is to be continued.
2991: --
2992: -- Results The API returns the standard p_return_status parameter
2993: -- indicating one of the standard return statuses :
2994: -- * Unexpected error
2995: -- * Error
2996: -- * Success
2997: -- The procedure returns the data read from the file into

Line 3135: -- Results The API returns the standard p_return_status parameter

3131: -- who columns for updating or creating a record. It returns
3132: -- a different set of values depending on whether the update
3133: -- is initiated by a user or by the loader.
3134: --
3135: -- Results The API returns the standard p_return_status parameter
3136: -- indicating one of the standard return statuses :
3137: -- * Unexpected error
3138: -- * Error
3139: -- * Success

Line 3136: -- indicating one of the standard return statuses :

3132: -- a different set of values depending on whether the update
3133: -- is initiated by a user or by the loader.
3134: --
3135: -- Results The API returns the standard p_return_status parameter
3136: -- indicating one of the standard return statuses :
3137: -- * Unexpected error
3138: -- * Error
3139: -- * Success
3140: -- Parameters p_loader_timestamp : IN optional

Line 3252: -- Results The API returns the standard p_return_status parameter

3248: -- determining updateablity, or for jlt files with
3249: -- G_FORMAT_FILE_VER of 120.1 or greater uses
3250: -- FND_LOAD_UTIL.UPLOAD_TEST.
3251: --
3252: -- Results The API returns the standard p_return_status parameter
3253: -- indicating one of the standard return statuses :
3254: -- * Unexpected error
3255: -- * Error
3256: -- * Success

Line 3253: -- indicating one of the standard return statuses :

3249: -- G_FORMAT_FILE_VER of 120.1 or greater uses
3250: -- FND_LOAD_UTIL.UPLOAD_TEST.
3251: --
3252: -- Results The API returns the standard p_return_status parameter
3253: -- indicating one of the standard return statuses :
3254: -- * Unexpected error
3255: -- * Error
3256: -- * Success
3257: -- Parameters p_loader_timestamp : IN optional

Line 3402: -- Results The API returns the standard p_return_status parameter

3398: -- into the specified file. The file could be overwritten
3399: -- or appended depending on the value of the parameter
3400: -- p_write_mode.
3401: --
3402: -- Results The API returns the standard p_return_status parameter
3403: -- indicating one of the standard return statuses :
3404: -- * Unexpected error
3405: -- * Error
3406: -- * Success

Line 3403: -- indicating one of the standard return statuses :

3399: -- or appended depending on the value of the parameter
3400: -- p_write_mode.
3401: --
3402: -- Results The API returns the standard p_return_status parameter
3403: -- indicating one of the standard return statuses :
3404: -- * Unexpected error
3405: -- * Error
3406: -- * Success
3407: -- Parameters

Line 3529: -- Results The API returns the standard p_return_status parameter

3525: -- into the specified file. The file could be overwritten
3526: -- or appended depending on the value of the parameter
3527: -- p_write_mode.
3528: --
3529: -- Results The API returns the standard p_return_status parameter
3530: -- indicating one of the standard return statuses :
3531: -- * Unexpected error
3532: -- * Error
3533: -- * Success

Line 3530: -- indicating one of the standard return statuses :

3526: -- or appended depending on the value of the parameter
3527: -- p_write_mode.
3528: --
3529: -- Results The API returns the standard p_return_status parameter
3530: -- indicating one of the standard return statuses :
3531: -- * Unexpected error
3532: -- * Error
3533: -- * Success
3534: -- Parameters

Line 3692: -- Results This function returns the standard p_return_status parameter

3688: --
3689: -- Desc This function checks to see if the given application ID is
3690: -- a valid application ID in the FND_APPLICATION table.
3691: --
3692: -- Results This function returns the standard p_return_status parameter
3693: -- indicating one of the standard return statuses :
3694: -- * Unexpected error
3695: -- * Error
3696: -- * Success

Line 3693: -- indicating one of the standard return statuses :

3689: -- Desc This function checks to see if the given application ID is
3690: -- a valid application ID in the FND_APPLICATION table.
3691: --
3692: -- Results This function returns the standard p_return_status parameter
3693: -- indicating one of the standard return statuses :
3694: -- * Unexpected error
3695: -- * Error
3696: -- * Success
3697: -- Parameters p_application_id : IN required

Line 3759: -- Results This function returns the standard p_return_status parameter

3755: --
3756: -- Desc This function checks to see if the given lookup type and
3757: -- lookup code exists in the AK_LOOKUP_CODES table.
3758: --
3759: -- Results This function returns the standard p_return_status parameter
3760: -- indicating one of the standard return statuses :
3761: -- * Unexpected error
3762: -- * Error
3763: -- * Success

Line 3760: -- indicating one of the standard return statuses :

3756: -- Desc This function checks to see if the given lookup type and
3757: -- lookup code exists in the AK_LOOKUP_CODES table.
3758: --
3759: -- Results This function returns the standard p_return_status parameter
3760: -- indicating one of the standard return statuses :
3761: -- * Unexpected error
3762: -- * Error
3763: -- * Success
3764: -- Parameters p_lookup_type : IN required

Line 3833: -- Results This function returns the standard p_return_status parameter

3829: -- either 'Y' or 'N'. It is used for checking for valid
3830: -- data in columns that accepts only 'Y' or 'N' as valid
3831: -- values.
3832: --
3833: -- Results This function returns the standard p_return_status parameter
3834: -- indicating one of the standard return statuses :
3835: -- * Unexpected error
3836: -- * Error
3837: -- * Success

Line 3834: -- indicating one of the standard return statuses :

3830: -- data in columns that accepts only 'Y' or 'N' as valid
3831: -- values.
3832: --
3833: -- Results This function returns the standard p_return_status parameter
3834: -- indicating one of the standard return statuses :
3835: -- * Unexpected error
3836: -- * Error
3837: -- * Success
3838: -- Parameters p_value : IN required