APPS.HXC_TIMESTORE_DEPOSIT_UTIL dependencies on HXC_TIMECARD_VALIDATION

Line 620: hxc_timecard_validation.deposit_validation

616:
617: -- Validate blocks, attributes
618: IF (p_mode <> hxc_timestore_deposit.c_migration)
619: THEN
620: hxc_timecard_validation.deposit_validation
621: (p_blocks => p_blocks,
622: p_attributes => p_attributes,
623: p_messages => p_messages,
624: p_props => l_timecard_props,

Line 631: hxc_timecard_validation.data_set_validation

627: p_resubmit => l_resubmit,
628: p_can_deposit => l_can_deposit
629: );
630: ELSE -- minimal validation for migration
631: hxc_timecard_validation.data_set_validation
632: (p_blocks => p_blocks,
633: p_messages => p_messages
634: );
635: END IF;

Line 662: -- hxc_timecard_validation.deposit_validation called above, raises

658: -- Get the messages to perform the audit check
659: p_messages := hxc_timecard_message_helper.getmessages;
660: -- Perform Audit Checks
661: -- Mental Note on how this works:)
662: -- hxc_timecard_validation.deposit_validation called above, raises
663: -- proper errors if something is really wrong, e.g. during the
664: -- project or payroll validation. However for Change and Late Audit
665: -- (CLA), it stores special messages in message table p_messages.
666: -- These messages have a message_level of REASON, are not considered