Reason field is not visible at the time of Purchase Requisition Cancellation in iProcurement

Reason fields appears only if any of the requisition lines are already on a PO. If there are no lines, then the reason field will not appear. (Doc 388115.1)

How to add approval at the time of award without using Award approval AME

1. Navigate to Responsibility : Approvals Management Administrator 
2 In Administrator Dashboard , search for 'Sourcing Award' and click Go. 
3. Once the record is found then click the pencil icon to update it. 
4. Navigate to 'Step 3 of 4' ie: Mandatory Attributes. 
5. Change the attribute value for : AT_LEAST_ONE_RULE_MUST_APPLY from True to False . 
6. Then navigate to Finish page and save the changes

How to hide the reassign button in the requisition approval notification?

To hide the requisition information button in the requisition approval notification, do the following:

- Open the workflow builder
- Get connected to the database
- Search "PO Requisition Approval" workflow and open it
- Expand: REQAPPRV (PO Requisition Approval)
- Expand: Messages
- Look for: PO_REQ_APPROVE (Approve Requisition)
- Do right click and select 'New Attribute'
- Enter the following data:

1. Internal Name: #HIDE_REASSIGN

2. Display Name: Request Information
3. Description: Request Information
4. Value: Y
- Click APPLY
- Save the workflow process definition into the database.

How to see Purchasing DFF 'PO Line Locations' from PBWC for a GBPA

Flex definition is enabled in GBPA line details page and it is enabled only for "Details" region. "Price Break" region do not have DFF enabled, and that is the reason why "Flex" field is not visible in the personalization page of "Price Break".
If there are any DFF need to be added for GBPA Line details, They sholuld be added in the "Details" Region Only.

Steps need to perform are:
1. Personalize the table PriceBreaksTable in AgreementLineDetailsPG.
2. Add a new column and column header to the table.
3. In the new column add a component of type flex, and provide required details like DFF name, entity name, etc.

Note that DFF in an advanced table has some limitations. Check the framework guide for details.

Canceling or Deleting a Negotiation i.e. RFQ or Auction

RFQ / RFI / Auction can be cancelled only if they are in Open status. User cann't cancel or delete draft RFQ / RFI / Auction. 

After cancellation, user can delete these RFQ / RFI / Auction.

RFQ / RFI / Auction can be deleted once that have been cancelled / closed.

Workaround to cancel and close the Draft RFQ / RFI / Auction:

- Publish the RFQ / RFI / Auction without adding any supplier

- Cancel

- Delete

Negotiation deletion option is available only in Administration Tab of Sourcing Super User Responsibility.

Where to see the amount in functional currency in PO if using foreign currency

Current functionality does not allow for functional amount to show on Purchase Order form or Orders page in BWC.
This issue is being tracked as an ER bug DISPLAY FUNCTIONAL AMOUNTS ON ENTER PO FORM bug 2963920

Workaround in PO Form:
==================

1. Create a DFF on PO Headers - Attribute1 (say), Call it Functional Currency Amount and don't assign a value set.

 2. Create a Forms Personalization on the PO Entry form as below: 

==

 Seq: 30

 Desc: Set Functional Amount DFF att1

 Level:  Function

 ==

 Condition

 Triggering Event:  WHEN-VALIDATE-RECORD

 Triggering Object:  PO_HEADERS

 Condition:  :PO_HEADERS.RATE is not null

 Processing Mode:  Both

 ==

 Action

 Seq:  10

 Type:  Property

 Object Type:  Item

 Target Object:  PO_HEADERS.ATTRIBUTE1

 Property Name:  VALUE

 Value:  ${item.PO_HEADERS.PO_TOTAL_DSP.value}*${item.PO_HEADERS.RATE.value}

 ===

What is 2-way, 3-way, 4-way matching? How is this set-up?

2-way matching verifies that Purchase order and invoice information match within your tolerances as follows: 
Quantity billed <= Quantity Ordered 
Invoice price <= Purchase order price 
(<= sign is used because of tolerances) 

3-way matching verifies that the receipt and invoice information match with the quantity tolerances defined: 
Quantity billed <= Quantity received 

4-way matching verifies that acceptance documents and invoice information match within the quantity tolerances defined: 
Quantity billed <= Quantity accepted. 
(Acceptance is done at the time of Inspecting goods). 

Whether a PO shipment has 2-way, 3-way or 4-way matching can be setup in the Shipment Details zone of the Enter PO form (character) 
Receipt required Inspection required Matching 
YesYes4-way 
YesNo 3-way 
No No 2-way 

What are the documents not supported in PBWC?

Following document types are not supported in PBWC : 
Planned PO 
Local Blanket Agreement 
Local Contract Agreement 
Scheduled Releases 
BPA Releases 
Quotations 
RFQs 

Are Preferences supported in PBWC?

Preferences are not supported in PBWC

Way to define the dependent valueset so that at the time of defining the values for dependent value set value against a independent value set, default values should not appear

1.First create independent valueset,enter the values for the same.
2.Then create dependent valueset,add the indenpendent valuset to this.
3.Enter the default value from the one which you had defined in step1.

GBPA/BPA/SPO which are outcome of a Sourcing RFQ doesn't get defaulted the default contract template

GBPA / BPA / Standard PO which are outcome of a Sourcing RFQ doesn't get defaulted the default contract template even if the profile option 'PO: Auto Apply Default Contract Template' is set to Yes.

PO's autocreated from Requisition don't have contract template attached automatically

When a PO is created from Purchase Requisition via 'CreatePO' workflow, the contract template is not assigned to the PO even profile option 'PO: Auto Apply Default Contract Templates' is set to yes.

This is Bug in R12 onward  and ER is already raised with Oracle development. Bug Reference: 7521651

Express Receiving does not support entering DFF

Express Receiving does not support entering DFF

How to remove 'Retroactive Price' check box from the BPA / GBPA approval form or GBPA control page in PBWC

Change the value of 'PO: Allow Retroactive Pricing of POs' profile option to NEVER

Master Org is appearing in change organization even if the org access is given only for child org for a responsibility

The Organization Access works as follows:

1) If you assign an organization to one responsibility, you will need to assign it to EVERY responsibility that will have access to it.
2) Any organization that is NOT assigned to at least one responsibility is available to ALL RESPONSIBILITIES.

So, if the Master organization is NOT assigned to ANY responsibility , it will be available to ALL RESPONSIBILITIES.

'Release Generation Method' ASL Attribute Is Null If GBPA Is Created From PWBC

Requisiton lines sourced to GBPA are automatically created into POs by CREATEPO workflow, regardless of the value of the Release Generation Method. Thus, specifying Release Generation Method for GBPA is not needed. And, in PWBC only Global Blankets can be created . Thus, this field is not included in PWBC.

Match Approval Level and Invoice Match Option

The Invoice Match Option and Match Approval Level are independent options. You can perform whichever Invoice Match Option you want regardless of the Match Approval Level.

Invoice Match Option:
-----------------------
Purchase Order: Payable must match the invoice to the purchase order

Receipt: Payable must match the invoice to the receipt.

Match Approval Level:
-----------------------
Two-way: Purchase Order and Invoice quantities must match within tolerance before the corresponding invoice can be paid.

Three-way: Purchase Order, Receipt and Invoice quantities must match within tolerance before the corresponding invoice can be paid.

Four-way: Purchase Order, Receipt, Accepted and Invoice quantities must match within tolerance before the corresponding invoice can be paid.

Purchase Order Approval Notification

Purchase Order approval notification always go to Preparer. If the Preparer and  Buyer are two different person, then by default Purchase Order Approval Notification will go to Preparer.
Node 20 of Purchase Order Approval Workflow send this notification. For sending the notification to the Buyer, customization need to be done at this node to add Buyer also in the notification list.
Same place customization need to be done for sending the approval notification to the Original Requester.

Purchase Requisition Approval Notification

Purchase Requisition approval notification always go to Preparer. If the Preparer and Requester are two different person, then by default Purchase Requisition Approval Notification will go to Preparer.
Node 24 of Requisition Approval Workflow send this notification. For sending the notification to the Requester, customization need to be done at this node to add Requester also in the notification list.

Charge Account is not getting defaulted on PO as per Expense Accounts Rule Defined

If you are creating a PO directly (without having Requisition) for indirect purchases, then charge account will not get auto populated in the Distribution as per Expense Accounts Rule. For getting it defaulted as per rule, you need to enter the Requester Name in the Requester field at Distribution level.