x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 3 replies
  • Subscribers 106 subscribers
  • Views 1598 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
47
topics
95
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
965
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
JoLynn

How to set Adjustment flag when importing duplicate AP invoice

Posted By

I have created a VI job to import AP invoices into Sage 100 Advanced 2014. The import is working with the exception of when an invoice has already been imported, it does not show "Adjust" in the data entry file or on the register. The only place I have found any indication of the duplication is in the VI job log if you click on the header record, it will display a warning next to the invoice number. It is not practical to click on every header record in the import to find this information.

Can someone assist me in configuring the VI job to note that if an invoice exists in history, the invoice will be noted as an adjustment?

Thanks.

  • 0

    When you say "invoice has already been imported"  does this mean it has been posted or not? There is a column for Adjustment so in your source file you would need some type of flag that would signal the import to set Adjustment to Y.

  • 0 in reply to BigLouie

    The invoice has already been posted. They are not trying to adjust an invoice, so there would be nothing in the source file to indicated it is an adjustment. They are wanting some type of notification that the invoice already exists in history so they do not re-import the same invoice twice.

  • 0 in reply to JoLynn

    In that case you would need some type of perform logic to skip if it exist in history.  Perform logic for AP to do this was one of the first perform logics written by Slade.  Not sure if there is a current version floating around out there or if there is a flag in VI now. If this is JoLynn the reseller, ask Scott Brady at Sage, he would know.

*Community Hub is the new name for Sage City