Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Supply Chain Management
Lawson S3 Supply Chain
Vendor ship to account number
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
chaoticist
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5185
People Online:
Visitors:
338
Members:
0
Total:
338
Online Now:
New Topics
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
Infor ION
ION vs IPA
2/29/2024 1:24 AM
We had a person new to Lawson and Infor go to Info
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson S3 Supply Chain
Vendor ship to account number
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Sheri
Veteran Member
Posts: 163
2/27/2013 7:22 PM
Currently we only have one account number listed in AP10 for a vendor. Is there a way to have different account/ship to numbers per vendor, based on what ship to location we are using on PO20 header?
David Williams
Veteran Member
Posts: 1127
2/27/2013 7:44 PM
No, the work around is to use vendor contacts to store your different account numbers but then you have to select the contact on the PO.
Michelle Wetzel
Veteran Member
Posts: 183
2/27/2013 7:46 PM
I wish there was a better way. We have 27 internal companies and each of those could in theory have a different account number and ship to. We use AP10.2 to store the account number and don't store anything in AP10. AP10 is basically a shell for the pfroms and remit tos that are created for the different account/ship to combinations.
Then, on PO20, you choose the pfrom that corresponds to AP10.2 and the correct account feeds in.
My problem comes with the 27 companies - I have to have 27 pfroms created for each vendor just in case we might need to use it.
Michelle
Red
Veteran Member
Posts: 87
2/27/2013 7:49 PM
Sheri,
Are you looking to have this value populate on a purchase order?
For fax and printed orders, we use the vendor locations (AP10.2, tied to PO10.2). Based on our build hierarchy, we assign one or more vendor locations to a particular IC Location. It certainly increases the complexity of the maintenance (exponentially), but it does work. For EDI order, the ED40 translation table takes care of the issue.
I can exand on this if you think it would help,
Red
JonA
Veteran Member
Posts: 1162
2/27/2013 7:55 PM
This is the primary function of AP10.2/PO10.2. For instance, we have our primary medical supplier, vendor 6025 and a vendor location code built for each of our medical centers with the different account numbers tied to each.
Vendor 6025, Location MID1 = Midland account
Vendor 6025, Location CLR1 = Clare account
Vendor 6025, Location GLA1 = Gladwin account
Vendor 6025, Location ALM1 = Alma account
You can go further with this if you have a vendor with multiple divisions that require a different account with each division.
Vendor 310, Location MID1 = Midland account for J&J Healthcare
Vendor 310, Location MID2 = Midland account for J&J Clinical Diagnostics
Vendor 310, Location CLR1 = Clare account for J&J Healthcare
Vendor 310, Location CLR2 = Clare account for J&J Clinical Diagnostics
David Williams
Veteran Member
Posts: 1127
2/27/2013 8:03 PM
Please don't use Purchase From Locations for this - it's a nightmare to maintain, especially if you have EDI
Red
Veteran Member
Posts: 87
2/27/2013 8:04 PM
We have the additional requirement of bringing in the transmission method into the mix. So for a particular location/account, we might have one location that is used for fax, one for printing it out locally, and one when the requester/buyer doesn't want to print it out at all. We are also starting to investigate e-mail transmissions, so that may add another order of maintenance. So, yeah, it gets really ugly really quickly.
Have fun,
Red
Sheri
Veteran Member
Posts: 163
2/28/2013 12:07 PM
Thank you for the information/replies, I appreciate it.
(We currently are using the ED40.1 substitution tables for our EDI vendors and that works well)
I will try adding a P-from for the vendor(AP10.2), we have never used that option but I see your point on how it could become very messy, and does not look to be 'automatic' (having to enter the P-from for ea PO needing the alternate ship to account number?).
I will give this a try today, thank you
JonA
Veteran Member
Posts: 1162
2/28/2013 1:08 PM
I guess if you have a lot of ship-to locations/accounts to maintain it could be a problem. We only have 4 medical centers and then a few minor affiliates that may or may not get a PF location code assigned. Most of our supplies come through the medical centers and are delivered via our courier service. So it's not that difficult for us to maintain.
You are not authorized to post a reply.