Skip to main content

Customization of Requisition Approval Workflow

Sometimes the organization's business requirement may not be met by the standard requisition approval workflow. Customizations have to be done to meet these business requirements.

Below are some of the scenarios where the approval path will have to be routed differently when compared to the standard path.
1. Requisitions created on certain items.
2. When a base line is set on Approval limit.
3. Information displayed in Notifications.

Steps to create the custom workflow:

1. In the workflow builder, copy and paste the standard workflow Requisition (REQAPPRV) (File Name :  $PO_TOP/patch/115/import/US/poxwfrqa.wft) to the DB. It will ask for a new ITEM_TYPE. Provide a name for the custom workflow.
2. Add the required attributes, functions and nodes to the Process. Make necessary changes to the Process.
3. For Notifications, messages need to be provided appropriately. PL/SQL messages may not work properly in 11.5.10 version. For those cases, JRAD notification messages can be used.
4. Save the workflow in the database.
5. In Oracle Applications system, navigate to
SETUP->PURCHASING->DOCUMENT TYPES and select 'Purchase Requisition'.
6. Select the custom approval workflow and the starting process in the Requisition approval LOV.
7. Save the record.
8. Schedule a periodic concurrent request 'Workflow Background Process' for this new custom item type.

Comments

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line...

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,               ...

How To Enable / Disable Forms Personalization Option

Forms Personalization gives great flexibility to execute custom business logic without performing so much of technical work. To start forms personalization navigate to Help -> Diagnostics -> Custom Code -> Personalize But many time when we click on personalize it give below error  " Function is not available for this respnosibility. Change responsibilities or contact your System Administrator " To Enable access to forms personalization function we need to set below profile option.  -  Utilities:Diagnostics -> Yes / No It determines the diagnostics option is enabled for a user / responsibility or site, depending on the level profile option is set. Navigate to System Administrator -> Profile -> System Query for your user / responsibility for which you want to provide access. Set the value to 'Yes' , If you want allow access to forms personalization Since we change the profile option please change the respons...