[Home] [Help]
276: END IF;
277:
278: -- Logic :
279: -- + Fetch all workflow related attributes.
280: -- + In loop fetch next set of approvers. Using AME_API2.getNextApprovers3(..) will provide
281: -- set of production rules (name/value pairs) being applied to currents set of approvers.
282: -- + Check whether returned set of approvers have valid position or not by giving call to
283: -- function position_has_valid_approvers or not.
284: -- + When count of approvers reach to zero, check whether worklfow routing process is completed or
281: -- set of production rules (name/value pairs) being applied to currents set of approvers.
282: -- + Check whether returned set of approvers have valid position or not by giving call to
283: -- function position_has_valid_approvers or not.
284: -- + When count of approvers reach to zero, check whether worklfow routing process is completed or
285: -- not through OUT varaible l_completeYNO in AME_API2.getNextApprovers3(..) */
286:
287: -- Check if there is any AME exception. If yes, then return 'invalid approver'
288: l_ame_exception := po_wf_util_pkg.GetItemAttrText( aname => 'AME_EXCEPTION');
289:
310: PO_WF_DEBUG_PKG.insert_debug(itemtype,itemkey, l_log_head||':'||l_progress||' Calling AME API with transaction id ' || l_transaction_id);
311: END IF;
312:
313: ame_util2.detailedApprovalStatusFlagYN := ame_util.booleanTrue;
314: AME_API2.getNextApprovers3 (
315: applicationIdIn => applicationId,
316: transactionTypeIn => l_transaction_type,
317: transactionIdIn => l_transaction_id,
318: flagApproversAsNotifiedIn => ame_util.booleanTrue,
620: tmpApproverList ame_util.approversTable2;
621: l_process_out VARCHAR2(10);
622:
623: BEGIN
624: ame_api2.getAllApprovers7 ( applicationIdIn => applicationId,
625: transactionIdIn => documentId,
626: transactionTypeIn => documentType,
627: approvalProcessCompleteYNOut => l_process_out,
628: approversOut => tmpApproverList );
668: --Function:
669: -- Workflow activity PL/SQL handler.
670: -- + This procedure is used to send the notification for the approvers.
671: -- + Iterate through the list of approvers got from the API call
672: -- ame_api2.getNextApprovers3.
673: -- + Get the next approver name from the global variable g_next_approvers
674: -- and for each retrieved approver separate workflow process is kicked.
675: -- + They are marked as child of the current approval process (workflow
676: -- master detail co-ordination).
1200: -- APPROVE AND FORWARD on the basis of current_approver_type.
1201: -- Also populate l_forwardee.name value or else AME throws exception
1202: -- Update current approval record attribute approval_status with proper
1203: -- status, so that same can be communicated to AME.
1204: -- Update AME about current status of approver through API ame_api2.updateApprovalStatus.
1205:
1206: l_progress := '010';
1207: IF (g_po_wf_debug = 'Y') THEN
1208: PO_WF_DEBUG_PKG.insert_debug(itemtype,itemkey, l_log_head||':'||l_progress);
1319:
1320: l_progress := '060';
1321: -- Update the Approval status with the response from the approver.
1322: IF p_response IN ('FORWARD', 'APPROVE AND FORWARD') THEN
1323: ame_api2.updateApprovalStatus(
1324: applicationIdIn => applicationId,
1325: transactionIdIn => l_ame_transaction_id,
1326: transactionTypeIn => l_transaction_type,
1327: approverIn => l_current_approver,
1326: transactionTypeIn => l_transaction_type,
1327: approverIn => l_current_approver,
1328: forwardeeIn => l_forwardee);
1329: ELSE
1330: ame_api2.updateApprovalStatus(
1331: applicationIdIn => applicationId,
1332: transactionIdIn => l_ame_transaction_id,
1333: transactionTypeIn => l_transaction_type,
1334: approverIn => l_current_approver);
3799:
3800: fnd_message.set_token('PERSON_NAME', l_approver_disp_name);
3801: l_note := fnd_message.get;
3802:
3803: ame_api2.getAllApprovers7 ( applicationIdIn => applicationId,
3804: transactionIdIn => l_ame_transaction_id,
3805: transactionTypeIn => l_transaction_type,
3806: approvalProcessCompleteYNOut => l_process_out,
3807: approversOut => l_approver_list );
5130: END IF;
5131:
5132: IF(e_signer_flag = 'Y') THEN
5133: g_next_approvers(l_approver_index).approval_status := ame_util.nullStatus;
5134: ame_api2.updateApprovalStatus ( applicationIdIn => applicationId,
5135: transactionIdIn => l_ame_transaction_id,
5136: transactionTypeIn => l_transaction_type,
5137: approverIn => g_next_approvers(l_approver_index),
5138: updateItemIn => TRUE);
5282: -- Get the approver category by checking production indexes - Reviewer,
5283: -- Post approval group - Signer else Approver.
5284: -- Populate the plsql table po_ame_approver_tab.
5285:
5286: ame_api2.getAllApprovers3(applicationIdIn => applicationId,
5287: transactionTypeIn => transactionType,
5288: transactionIdIn => transactionId,
5289: approvalProcessCompleteYNOut => xprocess_out,
5290: approversOut => ApproverList,
6345:
6346: BEGIN
6347: -- Logic :
6348: -- 1. For post-approvers/reviewers/approvers where ameStatus is still NULL or notified, we need to supress them.
6349: -- 2. Here we fetch all approvers through ame_api2.getAllApprovers7. Then check for approvers
6350: -- whose status is NULL, means for them AME routing havent been strated yet.
6351: -- 3. Call ame_api3.suppressApprover to suppress such approvers.
6352: -- We set-reset dynamic profile 'PO_SYS_GENERATED_APPROVERS_SUPPRESS', to override AME mandatory
6353: -- attribute ALLOW_DELETING_RULE_GENERATED_APPROVERS.
6362: l_transaction_type := po_wf_util_pkg.GetItemAttrText( aname => 'AME_TRANSACTION_TYPE');
6363: l_transaction_id := po_wf_util_pkg.GetItemAttrNumber( aname => 'AME_TRANSACTION_ID');
6364:
6365: IF l_transaction_id IS NOT NULL AND l_transaction_type IS NOT NULL THEN
6366: ame_api2.getAllApprovers7(applicationIdIn => applicationId,
6367: transactionTypeIn => l_transaction_type,
6368: transactionIdIn => l_transaction_id,
6369: approvalProcessCompleteYNOut => xprocess_out,
6370: approversOut => l_approver_list);