Best Of
Re: How to force sipd to check local-policy additionally to reg-cache
Hi Antonio.
Thanks for the idea. I always wait for your alternative point of view to any issue. Although in my case numbers in RURI and TO are the same, I can intentionally modify the user-uri with HMR on ingress from Core (and store original called number in some custom header, to be able to restore it on egress towards SA), to cause rec-cache lookup fail and force sipd to check the local-policy.
Regards.
Daureen
Re: Web ADI for OPM Formula
Hello
There is an interface API - GMD_FORMULA_DETAIL_PUB which is used to create, update and delete Formula details. Update Formula Details procedure is used to update Formula Detail information. You can try this API for updating the scrap factors on the formula details.
Thank you.
Re: RMAN duplicate a PDB in a database of WE8MSWIN1252 character set to a CDB of AL32UTF8
Yes , This is supported starting from Oracle Database 18c. Target CDB should be AL32UTF8 , We can clone different character set PDB
Re: Significance of AVCO and VARC fields in F43121
Hi,
VARC (Cost Variance) represents the dollar variance between the amount on the received purchase order and the amount entered during voucher match.
AVCO (Average Cost Difference) represents the change in average cost caused by an overpayment or underpayment during voucher match.
If the amount at voucher match differs from the received PO amount, the system creates a VARC value. If the voucher match quantity is greater than the on-hand quantity, AVCO may differ from VARC.
The Item Ledger/Cardex table (F4111) is updated only with the variance related to the on-hand quantity.
Calculation used:
VARC / Voucher Match Quantity × On-Hand Quantity = AVCO
Regards,
Mahesh
Re: E-mail notifications for ECO Approvers
Hi,
To enable e-mail notifications for ECO approvers, the approver must exist in the Address Book (P01012).
In Work Center (P012503):
- Use the form exit to access Email Preferences
- Enter the Electronic Address type as E-mail Address
- Enter the approver’s e-mail address
- Set Messaging Indicator = 1
In User Profile Revisions (P0092):
- Enter the Address Book Number in the Address Number field
Also, verify that the approver is included in ECO Approval Routing Master (P4808).
When the Notification UBE (R48181) is run:
- E-mail is sent to approvers in the first approval group
- E-mail is sent to the next approval group only after the first group approves the ECO and the notification process is run again
Regards,
Mahesh
Re: ECO approval notifications for changes or rejections
Hi,
Approvers should monitor their approval queues in ECO Approvals (P4818).
A notification message is created only the first time an approver is notified. No additional messages are created for later updates or changes to the ECO.
The notification can be reviewed in:
- Employee Work Center (P012503)
- Employee Queue Manager (P012501)
- Tool Exit from any application
The notification includes an icon that allows the approver to directly access ECO Approval Audit/Review (P48185). From there, the approver can open the Approval form (P4818) to approve or reject the ECO.
Regards,
Mahesh
Re: Permission Denied Error
Hello,
The Administrator referred here is the person who has admin rights on the Usergroup that you belong to and will a person within your Organization.
Regards, Pramod
Re: How to prevent sales order line splitting through R42118
Hi,
The R42118 processing option #3 (Commitments) controls how inventory commitments are handled:
- Blank = Soft Commit
- 1 = Hard Commit
To avoid splitting sales order lines, this processing option should ideally be set to Blank.
However, line splitting can still happen depending on the Customer Master setup. If the Partial Shipments Allowed flag is enabled for the customer, the system can split the line by shipping available quantity and moving the remaining quantity to backorder.
To completely prevent line splitting:
- Disable Partial Shipments Allowed for the customer
- In Customer Master, uncheck the Partial Shipments Allowed option in Billing Instructions
For additional details, refer Oracle Note: E1: 42: Inventory Commitments in Backorder Release Process (R42118/P42117) (KB203856)
Regards,
Mahesh
Re: Backordered sales order line last status set to 900
Hi,
Yes, this is standard system behavior.
The last status of a backordered sales order line is set to 900 to differentiate lines that were shippable from lines that were backordered. This helps with tracking purposes and allows reports to be generated based on the last status code.
This system behavior is documented in Oracle Note: E1: 42: Why Is the Last Status on a Sales Order (P4210) Line That Was Backordered Always Set to 900? (KB357774)
Regards,
Mahesh