Refactored validation logic by removing hardcoded validation from application files and implementing GENMST-based validation to support client-specific requirements

Added the condition for the Order Status Update whatsApp Message as per the requirement, Only for PR006 and PR017 process completion the message will be send to the customer

Added transporter validation and RFQ rate calculation using FINPARAM-based pricelist configuration(remove dublicate code)

Added a logic for Live and Client Developer transaction the schema name will be fetch from the curren user

the selected Distribution Route during Sales Order processing.

- Added DB_PILOT handling in schema execution rules
- Restricted DDL execution to DB_MAIN schema only
- Added synonym creation for DB_READ and DB_PILOT on object creation/replacement
- Added object-specific grant handling for TABLE, VIEW, SEQUENCE, PROCEDURE, FUNCTION, PACKAGE, and TYPE
- Granted SELECT, INSERT, UPDATE, DELETE privileges on TABLES to DB_PILOT
- Granted SELECT privilege on TABLES, VIEWS, and SEQUENCES to DB_READ
- Granted EXECUTE privilege on PROCEDURE, FUNCTION, PACKAGE, and TYPE objects to DB_READ and DB_PILOT
- Added logging for schema and grant execution details

Fixed Distribution Route pophelp issue where only one record was displayed despite multiple records being available.

Made changes in the WhatsAppComm component to repalce the function name with the actual result in the message body

Fixed issue where RFQ Wizard detail screen was not loading all items for divisions with a large item count

Updated profile ID validation logic to handle both single and comma-separated multiple profile IDs for logged-in users

Made changes in ManageSqlConf, For confirmation of Client Dev transaction the Pilot transaction should be confirmed

Resolved the issue reported by the QC regarding wrong validation message on click of Release To Pilot button

Updated the package for ManageSql and ManageSqlConf class and On Submit click added the validation through GENMST instead or code level

Added the remarks and enterprise description in the workflow XSL and increased the width of Remarks field in the header form

In Application API added comment and Screen when we directly add API User (third form) after adding header details (first form)
SAXParseException is coming.

In Application API Screen when we directly add API User (third form) after adding header details (first form)
SAXParseException is coming.