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.CZ_SECURITY_PVT dependencies on STANDARD

Line 503: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

499: * @param p_unlock_references A value of FND_API.G_TRUE indicates that the child models if any should be
500: * force unlocked. A value of FND_API.G_FALSE indicates that only the root model
501: * will be unlocked
502: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
503: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
504: * @param x_msg_count number of messages on the stack.
505: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
506: * @rep:scope public
507: * @rep:product CZ

Line 505: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

501: * will be unlocked
502: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
503: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
504: * @param x_msg_count number of messages on the stack.
505: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
506: * @rep:scope public
507: * @rep:product CZ
508: * @rep:displayname API for working with force unlock operations on a model
509: * @rep:lifecycle active

Line 536: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

532: * This when passed as an input parameter to unlock_model
533: * API would ensure that only those models that have been locked by the lock API are unlocked. Models
534: * that were previously locked would not be unlocked (by the same user). The retaining of the lock state
535: * is done only during implicit locks and not when an unlock is done from developer.
536: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
537: * @param x_msg_count number of messages on the stack.
538: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
539: * @rep:scope public
540: * @rep:product CZ

Line 538: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

534: * that were previously locked would not be unlocked (by the same user). The retaining of the lock state
535: * is done only during implicit locks and not when an unlock is done from developer.
536: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
537: * @param x_msg_count number of messages on the stack.
538: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
539: * @rep:scope public
540: * @rep:product CZ
541: * @rep:displayname API for working with lock operations on a model
542: * @rep:lifecycle active

Line 602: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

598: * @param p_models_to_unlock would contain an array of model id(s) that have been populated with
599: * locked models during the execution of the lock model API. The unlock_model API will unlock the models
600: * in this array only.
601: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
602: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
603: * @param x_msg_count number of messages on the stack.
604: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
605: * @rep:scope public
606: * @rep:product CZ

Line 604: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

600: * in this array only.
601: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
602: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
603: * @param x_msg_count number of messages on the stack.
604: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
605: * @rep:scope public
606: * @rep:product CZ
607: * @rep:displayname API for working with unlock operations on a model
608: * @rep:lifecycle active

Line 703: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

699: * This is the public interface for force unlock operations on a UI content template in Oracle Configurator
700: * @param p_api_version number. Current version of the API is 1.0
701: * @param p_template_id number. Template_id of the template from cz_ui_templates table
702: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
703: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
704: * @param x_msg_count number of messages on the stack.
705: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
706: * @rep:scope public
707: * @rep:product CZ

Line 705: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

701: * @param p_template_id number. Template_id of the template from cz_ui_templates table
702: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
703: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
704: * @param x_msg_count number of messages on the stack.
705: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
706: * @rep:scope public
707: * @rep:product CZ
708: * @rep:displayname API for working with force unlock operations on a UI content template
709: * @rep:lifecycle active

Line 728: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

724: * @param p_template_id number. Template_id of the template from cz_ui_templates table
725: * @param p_commit_flag A value of FND_API.G_TRUE indicates that the a commit be issued at the end of the
726: * the procedure. A value of FND_API.G_FALSE indicates that no COMMIT is done.
727: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
728: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
729: * @param x_msg_count number of messages on the stack.
730: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
731: * @rep:scope public
732: * @rep:product CZ

Line 730: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

726: * the procedure. A value of FND_API.G_FALSE indicates that no COMMIT is done.
727: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
728: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
729: * @param x_msg_count number of messages on the stack.
730: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
731: * @rep:scope public
732: * @rep:product CZ
733: * @rep:displayname API for working with force lock operations on a UI content template
734: * @rep:lifecycle active

Line 755: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

751: * @param p_commit_flag A value of FND_API.G_TRUE indicates that the a commit be issued at the end of the
752: * the procedure. A value of FND_API.G_FALSE indicates that no COMMIT is done.
753: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
754: * @param x_locked_templates templates locked by this procedure
755: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
756: * @param x_msg_count number of messages on the stack.
757: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
758: * @rep:scope public
759: * @rep:product CZ

Line 757: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

753: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
754: * @param x_locked_templates templates locked by this procedure
755: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
756: * @param x_msg_count number of messages on the stack.
757: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
758: * @rep:scope public
759: * @rep:product CZ
760: * @rep:displayname API for working with force lock operations on a UI content template
761: * @rep:lifecycle active

Line 779: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

775: /*
776: * This is the public interface for unlock operations on a UI content template in Oracle Configurator
777: * @param p_template_id number. Template_id of the template from cz_ui_templates table
778: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
779: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
780: * @param x_msg_count number of messages on the stack.
781: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
782: * @rep:scope public
783: * @rep:product CZ

Line 781: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

777: * @param p_template_id number. Template_id of the template from cz_ui_templates table
778: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
779: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
780: * @param x_msg_count number of messages on the stack.
781: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
782: * @rep:scope public
783: * @rep:product CZ
784: * @rep:displayname API for working with unlock operations on a UI content template
785: * @rep:lifecycle active

Line 801: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )

797: /*
798: * This is the public interface for unlock operations on a UI content template in Oracle Configurator
799: * @param p_templates_to_unlock array of Template_ids from cz_ui_templates table to unlock
800: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
801: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
802: * @param x_msg_count number of messages on the stack.
803: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
804: * @rep:scope public
805: * @rep:product CZ

Line 803: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack

799: * @param p_templates_to_unlock array of Template_ids from cz_ui_templates table to unlock
800: * @param p_init_msg_list FND_API.G_TRUE if the API should initialize the FND stack, FND_API.G_FALSE if not.
801: * @param x_return_status standard FND status. (ex:FND_API.G_RET_STS_SUCCESS )
802: * @param x_msg_count number of messages on the stack.
803: * @param x_msg_data standard FND OUT parameter for message. Messages are written to the FND error stack
804: * @rep:scope public
805: * @rep:product CZ
806: * @rep:displayname API for working with unlock operations on a UI content template
807: * @rep:lifecycle active