Best Of
Re: Procurement Spend Analysis and Payment Spend Analysis tile configuration
Response to my SR:
In the research done, it cannot find references of questions addressed with respect of Purchasing Operations Dashboard. Changing the delivered configuration cannot be done without customization. Attached SR3-41722417131 -SCM9.2-2.docx file with suggestion of changing the (1) ‘From Date and To Date’ and (2) ‘add additional facets to search by’. In my test the last one did not work, possible there are some limitations to avoid performance issues. And I’ve found out some PeopleTools KMs that indicate this is PT specific rather than Purchasing application.
Steps:
1. Check PO Spend Analysis from Portal PT
Navigation PeopleTools > Portal > Structure Fluid Structure Content > Fluid Pages > Procurement Operations >
Notice the grid name under PO Spend Analysis
2. Open Pivot Grid Wizard
Navigation Reporting Tools > Pivot Grid > Pivot Grid Wizard
Search for PO_SPEND_TYPE_MP_FL_PVG pivot.
3. Press Next until ‘Specify Data Model Values’
4. Go to Select Query Prompt Values at the bottom of the page
Here you may change the parameters From Date = 01/01/2006 and To Date = 12/31/2015, but this is consider customization.
5. Query Manger
Press Ok to message < Query is being used as datasource by other definition(s). (139,356) >
Notice Prompts
I’ve run a trace and the Procurement Spend Analysis (Navigation Fluid Pages > Procurement Operations > PO Spend Analysis) is build based on the query PO_SPEND_TYPE_MP_FL_PVG that is using prompts from PSPGQRYPROMPT record.
6. Add new facet to Pivot
At step 3 of PO_SPEND_TYPE_MP_FL_PVG pivot, Data Model, go to specify Axes and Filters: Rows, Columns, and Filters.
Press yes to message
<Confirm Column Type change. (268,153)
Changing the Column Type selection for a saved entry will make all the Views associated with the model invalid and these views will be removed. It will also remove any user customizations previously made for this model. Are you sure you wish to proceed?>
Here, the system does not recommend more than 12 axis:
< More than 12 axis type of columns are not recommended in a Pivot Grid Model.
It is not recommended to have more than 12 axis type of columns in the Pivot Grid Model for two reasons -
1. This model will fail on the Microsoft SQL Server due to database platform limitations.
2. More than 12 axis type of columns can lead to a slower performance of the Pivot Grid.>
Then add a Facet (Filter) under the data columns section, locate the field you want to use as a facet/filter.
Save and Finish the Wizard.
The Supplier ID is available, the requestor ID not because is not included from the query manger.
So in both case you need to customize the pivot and query that is not either recommended or supported.
Also more details are in the PeopleBooks > Configuring Procurement Analysis Inquiries
https://docs.oracle.com/cd/F88359_01/fscm92pbr49/eng/fscm/spog/ConfiguringProcurementAnalysisInquiries-9f3eee.html?pli=ul_d4592e544_spog
Understanding PeopleSoft Fluid User Interface with Procurement Operations Pages
https://docs.oracle.com/cd/F88359_01/fscm92pbr49/eng/fscm/spog/UnderstandingPeopleSoftFluidUserInterfaceWithProcurementOperationsPages.html?pli=ul_d4592e544_spog
KM Docs:
E-PG: Pivot Grids Missing Saved Filters If More Than 10 Facets ( Doc ID 2533932.1 )
E-PG: Pivot Grid Incremental Facet Count ( Doc ID 2525700.1 )
Re: Is there a way to calculate a percent discount on a purchase order?
Hi Lauren,
I've not found a way to add an adjustment based on the PO total dollars.
This is the existing KM where it suggests adding a discount line.
How To Record Discounts Or Service Charges In A Purchase Order? (Doc ID 2554131.1)
I think one other option is to add a header negative misc charge. It looks like you need to allocate on the lines though. The misc charge should be visible though and it's based on user entering the discount amount rather than a calculation being done for you.
Recommending adding this in idea spaces for this PO order total price adjustments.
Thank you,
Nick
Re: Difference between Closed & Closed for Receiving Status for PO
Close :
Purchasing automatically closes shipments for receiving and invoicing based on controls that you specify in the Purchasing Options window. Once all shipments for a given line are closed, Purchasing automatically closes the line. When all lines for a given header are closed, Purchasing
automatically closes the document. PO with 'Closed' status is soft closed po. you can open the po using option : PO Summary > Tools > Control > Open .
Close for Receiving :
The Receipt Close Tolerance lets you specify a quantity percentage within which Purchasing closes a partially received shipment.
For example, if your Receipt Close Tolerance is 5% and you receive 96% of an expected shipment, Purchasing automatically closes this shipment for receiving. The Receipt Close Point lets you choose
which receiving action (Received, Accepted, or Delivered) you want to use as the point when Purchasing closes a shipment for receiving based on the Receipt Close Tolerance. For example, if you set a Receipt Close Tolerance of 5% and choose Delivered as your Receipt Close Point, Purchasing closes
shipments for receiving when you have delivered 95% or more of the ordered quantity.
Re: ODACLI configure-dataguard fails around step 7 Restore missing archivelog (Primary Site)
Hi,
You should not open the standby database in open mode by default unless you have Active Data Guard license.
Otherwise, you would violate your license agreement.
Br,
krisz
Re: 19.29 oneoff patch missing? 37690446
Ideally at some point next week. Please keep checking on the available patch back ports.
Re: How are you integrating multiple P6 schedules in OPC and importing updates without losing logic?
so one of the issues you may have with the update settings is the chance the relationships get updated and therefore the external ties get lost because the new file does not contain the externals.
Best practice is to
- Receive baseline files from subs
- Conduct external relationship meetings/agree on Program Baseline
- Perform exports of each subprojects and return them to the subcontractors ( these versions will contain the external relationships)
- Each sub is to use the provided file to update their schedules.
- Receive the updated files from the subs with the update setting. (files will all still have the external relationships)
- Conduct meeting/manage external relationships and agree on program progress.
- Repeat export of projects
- Repeat process
The key is on both parties to adhere to
- Always use the current file provided by master
- Never adjust external relationships while the individual projects are being updated outside the master
It’s a method… but to be honest given that we live in a world of shared environments, just pull out your credit card, bring your subs into OPC, and give them their project access with limited permissions and stop doing all this import/export stuff. And don’t say they don’t know how to use it. They can be trained. Companies have to learn Aconex let’s say if the project documents are stored there even if the only have ever used Procore. This is the same.
Re: Oracle 12 Spatial – How to Set Up NTv2 Grid for GDA94 to GDA2020 Transformation
To enable NTv2 grid-based transformations (such as from GDA94 to GDA2020) in Oracle Spatial (Oracle Database 12c),
you need to ensure that Oracle Spatial can locate and access your NTv2 grid files (*.gsb). Here’s how you can do this:
Oracle Spatial looks for datum shift (grid) files in the directory specified by the SDO_COORD_ATR_PATH initialization parameter.
If this parameter is not set, Oracle will use its default directory ($ORACLE_HOME/md/demo/coordinate/), but setting the parameter is best practice.
Place your .gsb files in a directory accessible to the Oracle server, e.g.:
/u01/app/oracle/product/12.2.0/dbhome_1/md/demo/coordinate/
or a custom directory (preferred for custom files), e.g.:
/u01/app/oracle/ntv2_grids/
Set the SDO_COORD_ATR_PATH database initialization parameter to point to this directory.
You can set this system parameter (as SYSDBA):
ALTER SYSTEM SET SDO_COORD_ATR_PATH = '/u01/app/oracle/ntv2_grids/' SCOPE=SPFILE;
Restart the database if you set the parameter using SPFILE or pfile.The Oracle RDBMS user must have read access to the grid files and the directory.
Oracle Spatial transformations must refer to the NTv2 transformation by name, referencing your grid file in the transformation definition.
Check the table SDO_DATUM_TRANSFORMS to see if your transformation is already defined, or create a custom transform referencing the grid file.
Thanks
Swati A