Supplier/Price Catalog (P41061/F41061)

parora

Well Known Member
Hi All,

For those of you using the Supplier/Price Catalog in JDE/Peoplesoft/Oracle (having a hard time keeping track), would like to get feedback on the following:

1. How are you performing mass updates on price changes for a specific vendor. Do you export the price list for the vendor, change it in say Excel, and import it back in with new effective dates? Or have you written your own program to accomplish this?

2. Regardless of the Effective From Date in the Supplier Price Catalog, JDE takes the price from the earlier Effective Through Date. For example, if you have item setup with Effective Date From 06/08/03 to Effective Date Through 12/31/10 and then for the same item have the Effective Date From 06/10/03 and Effective Date Through 12/31/11, and enter a PO on 06/11/03, it will take the price from the Effective Date Through 12/31/10. (Note not considering any Quantity Breaks in this Example). Based on this,

a) What's the purpose of the Effective From Date then?

b) In the above example, say I load my prices From 06/08/03 and then a later point in time, say 06/10/03, they change. Do you end up creating a new record in the Supplier Pricing Catalog and changing the Effective End Date on the first record, from 12/31/10 to 06/09/03? Or do you override the exiting price on the first record? If you do the latter, do you feel there is no need to keep history of the prices?

3. Has anyone modified form P41061/W41061A to allow for sequencing (for example by Effective Dates) to allow input/changes easier for the user. What was required?

4. Are you not using the Supplier/Price Catalog, but using Advance pricing as a substitute? For simple pricing scenarios (Buy Item X from Vendor ABC for $10), what benefits does Advance Pricing offer over Supplier/Price Catalog.

Thanks for your feedback in advance.





**************************************************************************************
Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. Thank you.

Information confidentielle: Le présent message, ainsi que tout fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; il est de nature confidentielle et peut constituer une information privilégiée. Nous avertissons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l’expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci.
**************************************************************************************



OneWorld XE, Update 6, SP20, AS/400
 
Hey Parora, I have yet to figure out what the rationale is for using the earlier effective date as a tie breaker for overlapping date ranges. For mass updates, our solution to the problem was to right an SQL script that would create new price records in the catalogue table and change the expiry date of the old price records to the day before the effective date of the new prices.
That way we get new prices and we get to keep a record of the old prices.

HP
 
Back
Top