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.
Wednesday, 6 March 2013
Monday, 28 January 2013
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.
Friday, 18 January 2013
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:
==================
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}
===
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.
==
Thursday, 18 October 2012
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
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
Planned PO
Local Blanket Agreement
Local Contract Agreement
Scheduled Releases
BPA Releases
Quotations
RFQs
Wednesday, 15 August 2012
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.
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.
Subscribe to:
Posts (Atom)
