03/06/2016

Document1114515.1

HowReapprovalRulesCanCausePurchasingDocumentsToRequireReapproval?
(DocID1114515.1)
InthisDocument
Abstract
History
Details

1.1.Predefinedreapprovalrules

1.1.1HeaderChanges

1.1.2.LineChanges

1.1.3.PriceBreakChanges

1.1.4.ShipmentChanges

1.1.5.DistributionChanges

1.2.Userspecificuserrules

1.3.Specificeventswhichcausedocumentstorequirereapproval

2.TheChangeOrderWorkflow

3.Howtomodifythereapprovalrules?

3.1.Howtosetormodifypredefinedreapprovalrules

3.2.Howtosetormodifyuserspecificreapprovalrules

3.2.1.Settinguptoleranceattributesthroughtheform

3.2.2.SettinguptoleranceattributesthroughWorkflowbuilder

3.2.3.SettinguptoleranceattributesthroughSQL*Plus

4.KnownIssues

4.1.IncreasesinPOtotaldonotrequirereapprovalofdocument.

4.2.DecreasesinPOtotaldonotrequirereapprovalofdocument.

4.3.EventsthatwillNOTchangethedocumentstatustoRequiresReapproval

4.3.1.ReschedulingaPurchaseOrderfromtheASCPWorkbench

4.3.2.ChangingapprovedDropShipment

StillHaveQuestions?

Summary
References

APPLIESTO:
OraclePurchasingVersion11.5.10to12.3[Release11.5to12.3]
Informationinthisdocumentappliestoanyplatform.
Form:POXPOEPO.FMBEnterPurchaseOrdersGUI
Form:POXPOVPO.FMBPurchaseOrderSummaryGUI

ABSTRACT
ThisdocumentisdesignedtogiveacompleteoverviewoftheRequiresReapprovalRulesandtheChangeOrderworkflow
withinPurchasing.Thepaperisdesignedtoassistinunderstandingwhichchangescancauseadocumenttorequire
reapprovalandhowtoallowcertainchangestobypassfull(manual)reapproval.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

1/13

03/06/2016

Document1114515.1

HISTORY
12jun2010:Notecreated

DETAILS
1.Whatarereapprovalrules?
Tounderstandreapprovalrulesitisimportanttomakeadistinctionbetweennewdocumentsandalreadyapproved
documents,whicharemodifiedafterapproval:
Ifanewdocumentiscreatedthepurchaseorder,releaseorrequisitionwillalwaysgothroughtheapprovalprocess.
However,addingorchangingspecificinformationforanalreadyapproveddocument,maycausethedocumenttounapprove,
regardlessofwhethertherevisionisincremented.Almostallchangesthatcausetherevisiontobeincrementedalso
unapprovethedocument,asdoesplacingthedocumentonhold,reservingitorcancelingit.
Thereapprovalruleshelpyoucontrolwhetherorhowmuchofarevision(forexample,toQuantity)requiresthedocumentto
undergotheentireapprovalprocessortobeinstantlyapproved.Soinotherwordsthereapprovalrulesdetermineifamodified
purchasingdocumentrequiresreapprovalornot.
Forexample,ifthebusinessrulesatacompanyarethatifapurchaseorderhasatotalchangethatiswithin5%oftheoriginal
amount,theywouldnotrequirecompletereapprovalofthepurchaseorderthenaftersubmissionthedocumentisimmediately
approved.Ifthetotalchangehoweverwouldbeoutside5%thedocumentwouldrequirereapproval.
Note:AprerequisiteforusingreapprovalrulesisthattheArchivemethodmustbesettoArchiveonApprove.Thisissetupvia
theDocumentTypespageandcanbedoneasfollows:
1.StartupaPurchasingresponsibility
2.NavigateSetup>Purchasing>DocumentTypes
TheArchiveonApproveoptioncopiesthepurchaseorderinformationintothearchivetablesinPurchasingeverytimeyou
approveorreapproveapurchaseorder.IftheoptionissettoArchiveonPrint(orArchiveonCommunicate)thenthe
documentalwaysgoesthroughthefullapprovalprocess.
WithinPurchasingtherearethreekindofreapprovalrules/eventsthattriggerthedocumenttorequirereapproval:
1.PredefinedreapprovalrulesinPurchasing
2.Userspecificuserrules
3.Specificevents

1.1.Predefinedreapprovalrules
WithinPurchasingthereexistanumberofpredefinedreapprovalrules.Basedonthesereapprovalrulesthefollowingchanges
canresultinunapprovingadocument:
1.HeaderChanges
2.LineChanges
3.PriceBreakChanges
4.ShipmentChanges
5.DistributionChanges
ThefollowingtablesdescribetheadditionsandchangesyoucanmakethatcausePurchasingtounapproveadocument:

1.1.1HeaderChanges
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

2/13

03/06/2016

Header
Information

Document1114515.1

Standard

Planned

Blanket

Contract

Release

Buyer

Contact

Confirm

ShipTo

BillTo

PaymentTerms

Shipvia

FOB

FreightTerms

BriefNoteto
Supplier

Acceptance
Required

AcceptanceDue
Date

AmountLimit

EffectiveDate

ExpirationDate

AmountAgreed

ReleaseNumber

ReleaseDate

Oracle
Procurement
ContractsContract
Terms

LineInformation Standard

Planned

1.1.2.LineChanges
Blanket

Contract

Release

UnitPrice

LineNumber

Item

ItemRevision

ItemDescription

ItemCategory

Quantity

UnitofMeasure

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

3/13

03/06/2016

Document1114515.1

SourceQuotation
Header

SourceQuotation
Line

HazardClass

ContractNumber

SupplierItem
Number

UNNumber

PriceType

PriceLimit

QuantityAgreed

AmountAgreed

BriefNoteto
Supplier

PromisedDate

NeedByDate

ExpirationDate

CapitalExpense

1.1.3.PriceBreakChanges
PriceBreak

Standard

Planned

Blanket

Contract

Release

ShipToLocation

Quantity

BreakPrice

Discount

Standard

Planned

1.1.4.ShipmentChanges
Shipment

Blanket

Contract

Release

ShipmentNumber

ShipTo

Quantity

PromiseDate

NeedByDate

LastAcceptance

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

4/13

03/06/2016

Document1114515.1

Date
Taxable(Header
only)

ShipmentPrice

SalesOrder
UpdateDate(Drop
Ship)

Standard

Planned

1.1.5.DistributionChanges
Distribution

Blanket

Contract

Release

Distribution
Number(Header
only)

Quantity

Requestor(Header
only)

ChargeAccount

Subinventory

1.2.Userspecificuserrules
Userspecificreapprovalrulesaresetupthroughtheworkflow(POAPPRV)toleranceattributes,whichholdpercentage(%)
tolerances.Youcanmodifypercentagetolerancesusedbythechangeorderworkflowtodeterminewhatpercentageincrease
toaunitprice,quantity,ordocumenttotalrequiresreapproval.Thechangeorderworkflowrepresentsthesepercentage
tolerancesasitemattributesthatyoucanchangeusingtheWorkflowBuilder.AsofRelease12,theseitemattributescanbe
changedthroughtheform'ChangeOrder'aswell(seesection3.2.1).
Bydefaultthesetoleranceattributesaresettozero.Thismeansthatanyincreasewillputthedocumentthroughthecomplete
approvalprocessagain.However,bychangingforexampletheChangeOrderLineUnitPriceTolerancefromzeroto20the
documentwillbereapprovedautomaticallyiftheunitpriceisincreasedbylessthan20percent.
ThefollowingtablewilldisplaythemodifiableItemTypeAttributesforwhichyoucanchangethepercentagetolerances:
ModifiableItemDisplayName

InternalAttributeName

Description

ChangeOrderDistributionQuantity
OrderedTolerance

CO_D_QUANTITY_ORDERED_T

Ifthechangeinthedistribution
Quantityorderedislessthanthis
percentage,thedocumentis
reapprovedautomatically

ChangeOrderHeaderAmountLimit
Tolerance

CO_H_AMOUNT_LIMIT_T

IfthechangetotheAmountLimitis
lessthanthispercentage,the
documentisreapprovedautomatically

ChangeOrderHeaderBlanketTotal
Tolerance

CO_H_BLANKET_TOTAL_T

IfthechangetotheblanketTotalis
lessthanthispercentage,the
documentisreapprovedautomatically

ChangeOrderHeaderPurchaseOrder
TotalTolerance

CO_H_PO_TOTAL_T

Ifthechangetothepurchaseorder
Totalislessthanthispercentage,the

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

5/13

03/06/2016

Document1114515.1

documentisreapprovedautomatically
ChangeOrderLineAgreedAmount
Tolerance

CO_L_COMMITTED_AMT_T

IfthechangeinAmountAgreedisless
thanthispercentage,thedocumentis
reapprovedautomatically

ChangeOrderLinePriceLimit
Tolerance

CO_L_NOT_TO_EXCEED_PRICE_T

IfthechangeinPriceLimitislessthan
thispercentage,thedocumentis
reapprovedautomatically

ChangeOrderLineQuantity
CommittedTolerance

CO_L_QTY_COMMITTED_T

IfthechangeinPriceLimitislessthan
thispercentage,thedocumentis
reapprovedautomatically

ChangeOrderLineQuantityTolerance

CO_L_QUANTITY_T

IfthechangeinQuantityorderedis
lessthanthispercentage,the
documentisreapprovedautomatically

ChangeOrderLineUnitPrice
Tolerance

CO_L_UNIT_PRICE_T

IfthechangeinunitPriceislessthan
thispercentage,thedocumentis
reapprovedautomatically

ChangeOrderShipmentPriceOverride CO_S_PRICE_OVERRIDE_T
Tolerance

Ifthechangeinpriceoverrideisless
thanthispercentage,thedocumentis
reapprovedautomatically

ChangeOrderShipmentQuantity
Tolerance

IfthechangeintheshipmentQuantity
orderedislessthanthispercentage,
thedocumentisreapproved
automatically

CO_S_QUANTITY_T

Note:SometimesthedocumentswillstillfollowtheApprovalhierarchyevenwhenthechangesseemtofallwithinthe
tolerancepercentage.Thismightbecausedbythefactthatthechangeononelevel,iscausingchangesatotherlevelsas
wellforwhichthetolerancesarenotset.
Forinstancethe"ChangeOrderLineUnitPriceTolerance"hasbeendefined,butafterchangingtheunitpricewithinthe
tolerancethepurchaseorderstillrequiresreapproval.
Thismightbecausedbythefactthatthechangeoftheunitpricealsocausethepurchasedocumenttotaltochange,while
the"ChangeOrderHeaderPurchaseOrderTotalTolerance"hasnotbeendefined.

1.3.Specificeventswhichcausedocumentstorequirereapproval
AdditionallypleasefindbelowalistwitheventsthatwillalsochangethedocumentstatustoRequiresReapproval.
1.Unreservingencumbereddocument
2.CancelingaPurchaseOrderthroughtheEnterPurchaseOrdersform(POXPOEPO)
WhenaPOlineiscanceledusingthePurchaseOrdersSummaryform(POXPOVPO)theauthorizationstatusremains
unchanged(i.e.inapprovedstatus).Thisistheexpectedbehavior.Soifyoudonotwantthedocumenttogothroughthe
reapprovalprocess,usethePOSummaryforminstead.Thisbehaviorisexplainedinthefollowingbug:
BUG:4186080POXPOEPO:CANCELPOLINEFORWARDSPOTONEXTAPPROVER
IfyoustillwantthedocumenttogothroughthereapprovalprocesswhenthedocumentiscanceledthroughthePO
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

6/13

03/06/2016

Document1114515.1

Summaryformaworkaroundistosete.g.theToleranceattributeCO_H_PO_TOTAL_Tto10.Ifthedocumentis
canceledthetotalischangedto0.00whichisoutsidethetolerancelimit.Howthiscanbedoneisdescribedinsection3.
SplittingaPOLinetomultipleshipmentswillalsorequirereapprovaleventhoughchangesarewithintheapprovaltolerances.
SeeNote1991253.1formoreinformation.

2.TheChangeOrderWorkflow
WheneveryoumakeachangetoadocumentthatcausesitsstatustochangetoRequiresReapproval,thatdocumentisrouted
throughthechangeorderworkflow.TheChangeOrderworkflowusesthesamereapprovalrulesalreadydefinedin
Purchasing.
Withthechangeorderworkflow,Purchasingletsyoudefinewhatchangestopurchaseordersorreleasesforexample,to
amounts,suppliers,ordatesrequiremanualreapprovalandwhichareautomaticallyreapproved.Ifyoumodifythechange
orderworkflowasdescribedinthenextsection,youcanallowcertainchangestobypassfull(manual)reapproval.All
reapproveddocuments,eitherfullyorautomaticallyreapproved,resultinthedocumentrevisionnumber'sbeingincremented.
TheChangeOrderworkflowisnotactuallyanitemtype,liketheotherPurchasingworkflows,butisagroupofprocesses
containedinthePurchaseOrderApprovalworkflow(POAPPRV).
Thechangeorderworkflowbeginswhenallofthefollowingistrue:
Changestoapurchaseordercauseitsstatustochangeto'RequiresReapproval.'
Thedocumentrevisionnumberofthepurchaseorderincreases.
YouselectSubmitforApproval(andthenchooseOK)intheApproveDocumentwindoworotherwisesubmitthe
documentforapproval.

3.Howtomodifythereapprovalrules?
PurchasingintegrateswithOracleWorkflowtechnologytoletyoudefinewhatchangestopurchaseordersorreleasesfor
example,toamounts,suppliers,ordatesrequirefullreapproval.Alloftheworkflowprocessesandfunctionsrelatingtochange
orderscanbefoundwithinthePOApprovalworkflow.Thechangeorderworkflowprocessusesthesamereapprovalrules
alreadydefinedinPurchasingtodeterminewhetheradocument,dependingonitsdocumenttype,requiresreapproval.
Ifyouwanttochangethereapprovalrulesthatthechangeorderworkflowuses,youcanchangethosereapprovalrulesthat
determinewhatpercentagechangetoaunitprice,quantity,ordocumenttotalrequiresreapproval.
YoucanoptionallychangetheserulesbymodifyingtheirattributesintheOracleWorkflowBuilderorthroughanewformif
usingRelease12.

3.1.Howtosetormodifypredefinedreapprovalrules
InRelease11.5orearlieritisnotpossibletomodifythepredefinedrules.HoweverinRelease12anewformhasbeen
introducedthatmakesitpossibletomodifysomepredefinedrules.Inordertoaccessthisform,pleasetakethefollowing
steps:
1.StartupaPurchasingresponsibility
2.NavigatetoSetup>TolerancesandRoutings>ChangeOrder.Thispageisoperatingunitspecific.
Note:Itisnotpossibletoenternegativevaluesinthetolerancesfields.

Forexample,NeedByDatetoleranceissetto365.IftheNeedByDateatthePOlinelevelisnowchangedtoafuturedate
thatislessthan365daysthedocumentdoesnotneedfullreapproval.
AlthoughthedocumentwillmovetoastatusofRequiresReapprovalitshouldautomaticallyapproveonceyouclickonthe
approvebutton,becausetheworkflowisnotcalledagain.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

7/13

03/06/2016

Document1114515.1

3.2.Howtosetormodifyuserspecificreapprovalrules
UserspecificreapprovalrulesaresetupthroughthePOworkflow(POAPPRV)Toleranceattributes.TheseToleranceattributes
holdpercentage%valuesandareexplainedinthetablewithModifiableItemTypeAttributesinsection1.2.Userspecificuser
rules.
ForadocumenttogothroughtheApprovalprocessagainyouhavetomakesurethatthechangedoesnotfallwithinthe
tolerancepercentage,e.g.whentheunitpricetoleranceissetto10(%),thePOwouldrequirereapprovalifthepriceis
increasedfrom100to110ormore.
Basicallythereare3availableoptionstosettheToleranceattributes:
1.Throughaform
2.ThroughWorkflowBuilder
3.ThroughSQL*Plus

3.2.1.Settinguptoleranceattributesthroughtheform
InRelease11.5orearlieritisnotpossibletomodifythepredefinedrules.Asmentionedearlierinrelease12anewformhas
beenintroduced,thatmakesitpossibletomodifysomepredefinedrules.Inordertoaccessthisform,pleasetakethe
followingsteps:
1.StartupaPurchasingresponsibility
2.NavigatetoSetup>TolerancesandRoutings>ChangeOrder
Note:Itisnotpossibletoenternegativevaluesinthesefields.

3.2.2.SettinguptoleranceattributesthroughWorkflowbuilder
YoucanalsosettheToleranceattributesthroughtheOracleWorkflowBuilderapplication.Inordertodoso,pleasetakethe
followingsteps:
1.Opentheclientapplication'OracleWorkflowBuilder'andconnecttothedatabase.
Loadtheitemtype'POApproval'.

2.IntheWorkflowNavigatorgotoHelp>AboutOracleWorkflowBuilder
Forthepurposeofchangingtheattributevaluetemporarilychangethecustomization'AccessLevel'from'100'to'0'.
(Foradditionalinformationonthe'AccessLevel'seeNote187735.1:32.WhatAccessLevelshouldIbeusinginOracle
WorkflowBuilder)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

8/13

03/06/2016

Document1114515.1

3.Nowclickonthe(+)signnextto'Attributes'toexpandthelist

4.SelectoneofthemodifiableChangeOrdertoleranceitemattributeslisted.Inthisexampletheattribute
'CO_H_PO_TOTAL_CHANGE'willbechanged.
a.DoubleclickontheattributetoopenthePropertiescontrolform.
b.Changethedefaultvaluefrom0toyourowntolerancevalueandpressbutton[Apply]andthen[OK]

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

9/13

03/06/2016

Document1114515.1

5.Savethechangestothedatabase.
6.Changethecustomization'AccessLevel'backfrom'0'to'100'(seestep#2)

3.2.3.SettinguptoleranceattributesthroughSQL*Plus
InRelease11.5theToleranceattributesettingsarestoredintableWF_ITEM_ATTRIBUTES.Pleasefindbelowanexampleon
howtosetthevalueoftheattributetoe.g.anegativevalueforthePOApprovalworkflowitemtype(POAPPRV)andthe
attributeChangeOrderHeaderAmountLimitTolerance:(pleasenotethechangeofanitemattributedefaultvaluewillapplyto
alldocumenttypes)
SQL*Plus>
UPDATEwf_item_attributes
SETnumber_default=10

wherename='CO_H_AMOUNT_LIMIT_T'

InRelease12theTolerancesettingsarestoredintablePO_CHANGE_ORDER_TOLERANCES_ALL.Pleasefindbelowan
exampleonhowtosetthesametoleranceattributeforStandardPurchaseOrdersinRelease12:
SQL*Plus>
UPDATEpo_change_order_tolerances_all

setmaximum_increment=10

wherechange_order_type='CO_ORDERS'

ANDtolerance_name='HEADER_AMOUNT_LIMIT'

ANDorg_id=&Operating_Unit

SoifablanketpurchaseagreementshouldrequirereapprovalondecreasingBPAamountthefollowingupdatecanbeused:
UPDATEpo_change_order_tolerances_all

setmaximum_increment=100

wherechange_order_type='CO_AGREEMENTS'

ANDtolerance_name='HEADER_AMOUNT_AGREED'

ANDorg_id=&Operation_id

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

10/13

03/06/2016

Document1114515.1

PleasenotethistableisstripedwiththeORG_IDcolumnastheseareoperatingunitspecificsettingsforthechangeorder
reapprovalrules.

IntheaboveexampletheupdateisforaStandardPurchaseOrder.Wedistinguishthefollowingvaluesinthecolumn
change_order_type:
BlanketPurchaseAgreement=CO_AGREEMENTS
BlanketReleases=CO_RELEASES
StandardPurchaseOrders=CO_ORDERS

4.KnownIssues
Thischapterprovidesanoverviewofsomeknownissuesandthesolutionstoresolvetheseissues.

4.1.IncreasesinPOtotaldonotrequirereapprovalofdocument.
On11.5.10itisobservedthatalthoughtheChangeOrderHeaderPurchaseOrderTotalTolerance(CO_H_PO_TOTAL_T)isset
to0increaseinpurchaseordertotaldonotcausethePOtorequirereapproval.
ThisissueiscausedbythefactthewrongattributeischeckedtomakeadecisiononReapproval.
ThePOApprovalworkflowprocedurePO_CHORD_WF6.get_default_toleranceshouldgetthetotalchangetolerancefrom
CO_H_PO_TOTAL_Tasthatattributeisdesignedtolerancesothatifthepurchaseordertotalischangedlessthanthe
tolerancepercentage,thedocumentwillbeautomaticallyreapproved.
Currently,thisattribute,whichisthePOApprovalworkflowprocedurePO_CHORD_WF6.get_default_tolerance,iscallingthe
attribute'CO_H_PO_TOTAL_CHANGE'insteadoftheattribute'CO_H_PO_TOTAL_T'.

FormoreinformationseeBug4278227.
ThisissuehasbeenfixedinPOXWCO6B.pls115.14.11510.2orhigher.Todeterminewhichversionofthefileyouhavethe
followingquerycanbeexecuted:
selecttext

fromdba_source
whereline=2

andname='PO_CHORD_WF6'

IflowerthanPOXWCO6B.pls115.14.11510.2pleasedownloadandapplypatchPatch4487674,whichwillinstall
POXWCO6B.pls115.14.11510.3.

4.2.DecreasesinPOtotaldonotrequirereapprovalofdocument.
Itcanbeobservedthatdecreasingunitprice,quantityortotalamountdoesnotrequirereapprovalofdocument.
ItisstandardfunctionalitythatwhenreapprovingaPOwhosedocumenttotalislessthanoriginallyapprovedthatthePOdoes
notpassthroughtheApprovalHierarchy.Andincaseofdecreasingtheunitpriceorquantitythedocumenttotalislowered.
ToachievethefunctionalitywherePO'swhoseDocumentTotalhasdecreasedafterbeingapprovedwouldthenpassthrough
theApprovalHierarchyuponreapproval,theWFattributementionedshouldbesettoanegativevalue.
Mostcommonly,thebusinessrequirementwouldthatallPOspassthroughtheApprovalHierarchyregardlessofthereduction
oftheDocumentTotal.Inthesecasesthevaluefortheattributewouldbe'100'
ThefollowingSQLcanbeusedon11.5.10toupdatetheWFAttribute...
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

11/13

03/06/2016

Document1114515.1

updateWF_ITEM_ATTRIBUTES
setNUMBER_DEFAULT=100

whereitem_type='POAPPRV'

andname='CO_H_PO_TOTAL_T'

AdditionallyperDevelopmentinBug:13836409POWORKFLOWATTRIBUTESNOTCHANGEDSHOULDBE0:
AfteraPOlinequantityisdecreased,thefollowingattributesmayshowas'0':
ChangeOrderDistributionQuantityOrderedChange0
ChangeOrderLinesQuantityChange0
ChangeOrderShipmentsQuantityChange0
Thesearetheworkflowattributesatthedocumentlevel.Theirvaluesarestoredareasbelow:
SELECTmax(po_chord_wf0.percentage_change(

PODA.quantity_ordered,POD.quantity_ordered))

fromPO_DISTRIBUTIONS_ALLPOD,PO_DISTRIBUTIONS_ARCHIVE_ALLPODA

WHEREPOD.po_release_id=x_po_release_id

ANDPOD.po_distribution_id=PODA.po_distribution_id(+)

ANDPODA.latest_external_flag(+)='Y'

Sothemaxchangepercentagevalueisalwaysretainedintheseattributes.
IfonePOlinehasnoquantitychangeandanotherPOlinehasanegativequantitychange,thentheattributevalueissetto
Zero.

4.3.EventsthatwillNOTchangethedocumentstatustoRequiresReapproval
AlsotwoeventshavebeenidentifiedwhichdonotcausethedocumentstatustochangetoRequiresReapproval:
1.ReschedulingaPurchaseOrderfromtheASCPWorkbench
2.ChangingapprovedDropShipment

4.3.1.ReschedulingaPurchaseOrderfromtheASCPWorkbench
ReschedulingaPurchaseOrderfromtheASCPWorkbenchwillnotcausethedocumenttorequirereapproval.Thestatusofthe
PurchaseOrderwillremainunchanged.

4.3.2.ChangingapprovedDropShipment
WhenanexternallysourcedSalesOrderlineisupdated,automaticallytherelatedPurchaseOrderline/shipmentisupdatedas
well.IfthePurchaseOrderisinapprovedstatethePOapprovalworkflowislaunched.IftheBuyerhasenoughauthoritythe
PurchaseOrderisautomaticallyapproved.IftheBuyerdoesnothaveenoughauthoritythestatusofthePurchaseOrder
changesto'InProcess'.

StillHaveQuestions?
TodiscussthisinformationfurtherwithOracleExpertsandindustrypeers,weencourageyoutoreview,joinorstarta
discussionintheMyOracleSupportProcurementCommunity.

SUMMARY

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

12/13

03/06/2016

Document1114515.1

ThisdocumentisdesignedtogiveacompleteoverviewoftheRepapprovalRulesandtheChangeOrderworkflowwithin
Purchasing.Thepaperisdesignedtoassistinunderstandingwhichchangescancauseadocumenttorequirereapprovaland
howtoallowcertainchangestobypassfull(manual)reapproval.ForfurtherreferenceseetheOraclePurchasingUser's
Guide,section'DocumentReapprovalRules'.

REFERENCES
NOTE:728789.1HowtoforceaPOThroughTheApprovalHierarchyWhenReapprovingWithaLowerDocumentTotal
Didn'tfindwhatyouarelookingfor?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrlstate=1d97cnfjsz_238&id=1114515.1

13/13