Document Security Levels can be set for each document type. Security Levels options include like below screen.
Private: Only the document owner and subsequent approvers can access the document.
Purchasing: Only the document owner, subsequent approvers,
and individuals defined as buyers can access the document.
Hierarchy: Only the document owner, subsequent approvers, and
individuals above the the document owner in the security hierarchy can access
the document.
Note:
Subordinates can’t see the superiors requisitions.
Public: All system users can access the document.Whenever we select security level as Hierarchy at Purchase Requisition Document Type
We will get a new Security Hierarchy option at Document
Control in Purchase Options.
Navigation: MCR PO > Purchasing > Document Types > Requisition Purchase Click on
Update Icon Once select the Security Level as Hierarchy and Apply the changes and go to Purchase Options to see the new Security Hierarchy Option in Document Control. Here we need to specify our hierarchy (MCR PO Hierarchy) and save the changes.
Navigation: MCR PO > Setup > Organizations > Purchasing Options
We can specify the Document Access Level to control what
modification and control actions you take on a perticular document once you
gain the access. Document owners always have full access to their documents.
Document Access Levels includes like below screen.View Only: Accessing employees can only view the document.Only the document owner may modify or control the document (Purchase Requisition).
Modify: Accessing employees can view, modify, freeze and
close the document.
Full: Accessing employees can view, modify, freeze, close,
cancel and finally cancel the documentNavigation: MCR PO > Purchasing > Document Types > Requisition Purchase Click on Update Icon
Document Type – Approval Settings
Navigation: MCR PO > Purchasing > Document Types > Requisition Purchase Click on Update Icon
Approval Settings:
Owner Can Approve: We can enable if the owner can approve his
or her own document. The document is still subject to the approval rules
assigned to the owner’s job or position and document type.
Note:
This Option is not applicable when the document type is RFQ and Quotation.
Approver Can Modify: We can enable/check if the document
approvers are required to modify the
document. If not enable this check box then approver must either simply approve
or reject the document. Approver should include the reason for the
rejected document along with changes
that need to made that will allow them to approve when resubmitted.
Note:
This Option is not applicable when the document type is RFQ and Quotation.
Approval Workflow: We can accept the default workflow or
customized workflow of your own and want to associate it with a specific
document type, we can choose that instead.
Workflow Start Process: We can accept the defaults already
set up in Oracle Workflow, or if we created a workflow process of our own and
want to associate it with a specific document type, we can choose that workflow
process instead.
Approval Transaction Type (Requisitions Only): If we have
implemented Oracle Approvals Management, this selection associates the
transaction type with the requisition document type. Routing Settings:
Can Change Forward-To: If enable, user can change the person
the document is forwarded to. Note: This field is not
applicable when the document type is RFQ and Quotation.
Can Change Forward-From: Allows preparers to forward the document to one of the requestors on the
requisition. This field is only applicable for requisition document types.
Can Change Approval Hierarchy: If enabled, preparers and
approvers can chage the approval hierarchy defaulted into the Approve Document
window
Note:
This field is not applicable when the document type is RFQ and Quotation.
Forward Method: This option applies regardless of whether you
are using position approval hierarchies or the employee/supervisor hierarchies
to determine your approval paths. This field is not applicable when the
document type is RFQ and Quotation.
Valid values are
Direct: The default for the approver is the first person in
the preparer’s approval path with sufficient approval authority.
Hierarchy: The default for the approver is the next person in
the preparer’s approval path regardless of whether he or she has sufficient
approval authority.
Default Hierarchy: The name of the position approval hierarchy
which defines the standard approval path for the particular document type.
Note: This field is not applicable when the document type is RFQ
and Quotation.
Document Type – Controls:
Navigation: MCR PO > Purchasing > Document Types > Requisition PurchaseSecurity Level: Lets you control which groups of employees have access to each document type.
Access Level: Lets you control what modification/control
actions employees can take once they gain access to the document.
Auto create Workflow (Requisitions only): We can accept the default workflow or customized workflow of your own we can choose that instead.
Use Contract Agreement for Auto-Sourcing (Requisitions only):
Requires the requisition creation auto sourcing logic to include approved
contract purchase agreement.Auto create Workflow (Requisitions only): We can accept the default workflow or customized workflow of your own we can choose that instead.
Thanks for this amazing Posts i really like your blog you are doing good work. Keep sharing good blogs and new ideas, features & latest trends in this technology.
ReplyDeleteDocument Management Software
Electronic Document Management System
Document Management System
Cloud Document Management Software
This is an awesome post.Really very informative and creative contents. These concept is a good way to enhance the knowledge.I like it and help me to development very well.Thank you for this brief explanation and very nice information.Well, got a good knowledge.
ReplyDeleteCONTRACTS