Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

FPA agreement/items loaded agaisnt wrong supplier ID

Status
Not open for further replies.

Calator

Programmer
Feb 12, 2001
262
AU
Hi,
Ref :FPA / MIMS4.1

A number of agreeents & items have been loaded against the wrong supplier ID. Is there a housekeeping/bulk update program that would allow to change the supplier id on existing records, rather than heving to delete and recreate them with the correct supplier id?
 
Have a look at MSB070 - Bulk change program. I think it will let you do what you want.
 
Hi,
Thanks for pointing to MSB070, interesting stuff, however this does not appear to address this particular problem.

I wasn't able to find an option to update the actual FPA files (MSF25*). MSB070/03 Purchasing options includes an option to modify FPA/Agreement, however on the second screen the available fields to be changed appear to belong to MSF170/MSF210.

The notes in the source code and the ref.manuals also indicate that:
"Files nominated for update are MSF100 ; MSF170 ; MSF210 , MSF165 and MSF071"

Please let me know if I'm wrong, or maybe it's a MIMS version issue (we use 4.1)
 
O.K., let's try it another way. I take it the FPA process has not been completed. I'm only guessing here, but, could you complete the process so MSF210 is updated and then run MSB070. It's been a couple of years since I've worked on Supply so I may be mistaken. How about SQL?
 
Hi,

1. FPA agreement has been created (MSF253) and items have been loaded (MSF251). I don't know if MSF210 has been updated or not, would this be relevant anyway, if MSB070 does not appear to update any files in the FPA module (in particular: MSF253)? This hypothesis is based on available documentation, I get you advice though and it's a good idea to try it out.

2. our policies do not allow to bypass the application and update the database using sql unless sql is supplied by Mincom.
 
To all those interested: Mincom have indicated that MSB25A should be used to fix the problem, by using Old Supplier/ New Supplier parameters
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top