Skip to main content

(R12.2+) Changes in Business Rules of PO Cancel Action Functionality

This article provides information about New feature in (R12.2+) related to Cancel Action Functionality and its Business Rules' changes -


Oracle Purchasing now provides the following changes in business rules of the Cancel action functionality:
  • When cancelling the PO, Oracle Purchasing will no longer launch the Approval Workflow to make the PO in 'Approved' status after cancellation.
  • Buyers can cancel purchasing documents (at any level: header, line, and shipment) that are at the Requires Reapproval status.
  • When cancelling the Approved PO (at any level), The application creates the document's new revision and maintains archived if archive on is set as 'Approve'. This information is communicated to suppliers.
  • Action history will be recorded with the cancel action (in case of cancel at header level).
  • When a buyer cancels a purchasing document that has changes since its last revision, the application now displays a warning message, which clearly indicates changes, if any, in the Quantity, Amount, Price, Need By, and Promised Date fields. The application does not validate any other fields when performing the cancel action. Buyers can ignore changes in specific fields and continue with the cancel action.  Note: If there is a change in the listed attributes of only one shipment, then the warning indicates the changes done clearly. But, if changes are there to multiple shipments, then the warning is generic indicating that there are some pending changes to the document and buyers can ignore the changes if they want and continue with the transaction.
  • When invoice cancellation happens after the cancellation of a purchase order, the Canceled Quantity on the purchase order line or the purchase order total does not reflect the quantity which was utilized by invoice and is now canceled and no longer in use. To correctly recalculate quantity, buyers must final close the document in Oracle Purchasing.
  • Buyers can recreate a demand for internal requisition if the complex purchase order line is not received or billed.
  • No difference in cancelling the document from PO Summary and PO Entry Form.
  • While cancelling the PO which in Requires Reapproval' / 'Rejected' (if it has not been approved at least one time) status, then changes done in the Quantity, Amount, Price, Need By, and Promised Date fields, if any, will be reverted to old value. But Changes to the other fields will be retained.


Document Status:
Document Status Before Cancel
Document Status after Cancel
 Initial Status
Cancel at Header
Cancel at Line / Shipment
APPROVED
APPROVED
APPROVED
REQUIRES REAPPROVAL
APPROVED
REQUIRES REAPPROVAL
REJECTED (in case if it has not been approved at least one time)
APPROVED
REJECTED



Comments

  1. When 1-coin full homes return 8 and 1-coin flushes return 5 (known as 8-5 Bonus Poker), the sport returns 99.2% with excellent play. Once you understand the code, you can to|you possibly can} inform at a look which is which. Often you’ll find all three versions in the same casino. By checking every machine, it's simple to establish which is the smarter play. There is no single technique that's right for every video poker 바카라 사이트 recreation. It is really helpful that you simply select your favourite poker variant, after which studying about it and enjoying in} it as much as possible.

    ReplyDelete

Post a Comment

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_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  

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 ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table