web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AP Vendor Inactivation or SQL to make vendors inactive in BULK

(0) ShareShare
ReportReport
Posted on by

Hi All,

We are looking at options of cleaning our AP Master Data for Vendors.

A consultant has advised us to use the Vendor Inactivation in Procurement and Sourcing >Periodic>Vendors>Vendor inactivation, however, it still allows newly created vendors to be inactive.

I was thinking running an SQL script to find all vendors that are active, and has not been used for 18 months  to be updated to inactive.

Does any one have any options to clean vendors in bulk ?

Cheers,

Phung Huynh

*This post is locked for comments

I have the same question (0)
  • Mea_ Profile Picture
    60,286 on at

    Hi Mhuynh11,

    Can you please explain what is wrong with "Vendor inactivation" periodic operations and what your SQL script should do that Vendor inactivation does not ?

  • Community Member Profile Picture
    on at

    Hi ievgen,

    The vendor inactivation still makes new vendors that I recently created to be "ON HOLD".

    The inactivity period (indays) 568

    Grace time before next hold (in days) 1 day

    Includes employees : NO

    Is my set up done incorrectly?

    so the script I want to do is that it can get me a list of all active vendors that hasn't been used since 2016 and then update to make it "ON HOLD" / inactive .

  • Suggested answer
    nmaenpaa Profile Picture
    101,172 Moderator on at

    I would not suggest changing AX database data with direct SQL queries. This can cause issues because of application caches, RecVersion fields and so on.

    Instead write a x++ class or job to make your changes through the application.

  • Douglas Noel Profile Picture
    3,907 on at

    Hi,

    I think the real problem is the missing exact definition of: What is a vendor, which isn't used since xyz.

    If a vendor hasn't any transactions after xyz it is not used after xyz. Even a new one.

    Maybe it makes sense to check the number of transactions (if any exist) for a given vendor and skip vendors without transactions (or make an additional check in that case, which, for example checks the creation date of the vendor, to distinguish between new vendors without transactions and really old one)

    Regards Douglas

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 21

#2
dserp Profile Picture

dserp 4

#2
dekion Profile Picture

dekion 4

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans