Best Of
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
Re: Cascading of existing Style Supplier onto a new SKU is a base functionality?
Hi User_B13BC,
Yes, this is standard out-of-the-box MFCS behavior.
The parameter CORESVC_ITEM_CONFIG.CASCADE_IUD_ITEM_SUPPLIER determines whether inserts, updates, or deletes on item/supplier details should cascade to child items. When this parameter is set to 'N', propagation is disabled, meaning each SKU will only have the suppliers explicitly assigned to it.
Thanks,
Atanu
Re: Concurrent request completes without error but cannot view output or log file in the browser.
We are having the exact same problem, and it also started today Jan 31 2023. No configuration changes, nothing we did that might have triggered the problem. A bounce of services didn't help. We are running AutoConfig now, as you found, to see if that helps us.
PhatDBA
Re: Ability to Push New Cost Code Rows from Template to Existing Project Shells
Thanks Jeff! This is useful. I used Create Code but wasn't aware of the Sort Cost Sheet APIs.
Nasim N