x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 11 replies
  • Subscribers 118 subscribers
  • Views 2089 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
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
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
j-fly

Sage100 Visual Integrator: Where to put ship to informaton?

SOLVED
Posted By

OK. This has me flustered.

I have figured out how to use Temp fields in Vi for Sage 100 2019 to create a single SO that has multiple items on it. The data source I'm using has a separate row for each item purchased, and my current VI job creates one SO with multiple items. No problem.  

However, my script makes the Billing and Shipping Address the same. I I need those to be different and I add the Ship To fields with the operation as REPLACE, mapped to the appropriate columns on my data source, it creates a brand new SO for each items sold, even if one person buys multiple items. And since those items are on different lines of the data source, multiple SO are created instead of the single SO I had going before. Make sense?

I'm sure this is an order thing, but I cannot figure out the order. I have two scree shots below: the first is the VI job that works, and the second is the same VI job with the Ship To Fields that break the job.

Again, the first will create 1 SO for multiple items but makes the billing and shipping addresses the same. The second makes the billing and shipping addresses different when needed, but splits the order into 2 SO for the same order number. 

What am I doing wrong?

Thanks a bunch!

Jamie

Parents
  • 0

    The "NEXT" SO# function is triggered when any values for "H" fields change.  Check your source data to ensure the ShipTo data is repeated exactly on each line.

  • 0 in reply to Kevin M

    Hey Kevin M,

    Thanks for always being a beacon! Can you explain what you mean by exactly? What I'm doing is using the REPLACE operation and then just changing the column number to the one in my data source.

  • 0 in reply to j-fly

    You can't have the ShipTo values only on one line of the source data.  They need to be repeated exactly on each and every line for the SO (in your source data), or the NEXT function will think it's a new transaction.

    There is a flag to have header data separate from line data, but you need to specify (tab 4) criteria for the designation.

  • 0 in reply to Kevin M

    Kevin,

    The data source only has the billing and shipping info on the first item, unfortunately. And if we have hundreds of orders, it would be time consuming to copy and paste that data.

    The separate header trick doesn't work either. Bummer. I am stuck on this one.

    I tried adding a temp field for just one shipping field-the Shipping Address 1 field, where the temp field makes the replacement. But Then the shipping address field in Sage was skipped. Is there a way to use Temp fields like you can with populating fiedls with numbers or calculations, but use string instead?

  • 0 in reply to j-fly

    Try temp fields marked as Key Assigns Only to the fields.  I don't know if it will work for this, but worth a try.

  • 0 in reply to Kevin M

    Well, I can't seem to figure it out. Is there something other than REPLACE I can use to populate the Ship To fields from the data source? If REPLACE in any header field triggers a new SO to be created, that makes the additional work on our sales team pretty hefty. We have just moved from Mas90 to Sage100-BIG jump and Mas didn't care about the REPLACE operation. You could use it 100 times and it would honor the request. 

  • 0 in reply to j-fly

    Key Assign temp fields using Replace.  Ship To fields as calculated (pulling in the temp fields, when not blank).

    That is the only idea I have.

  • 0 in reply to Kevin M

    Ok. I think that might habve gotten me somewhere. What is the operator for not blank. Here is what I have:

    Temp003 is referencing column 36 which has the street number. I'm starting with just 1 field to see if I can get it to work and then add the other Ship To fields.

    The this is my Shipping Address 1 field referencing Temp003. What should I do differently? This scenario does not populate the Shipping Address 1 field and makes multiple orders for the same SO#.

Reply
  • 0 in reply to Kevin M

    Ok. I think that might habve gotten me somewhere. What is the operator for not blank. Here is what I have:

    Temp003 is referencing column 36 which has the street number. I'm starting with just 1 field to see if I can get it to work and then add the other Ship To fields.

    The this is my Shipping Address 1 field referencing Temp003. What should I do differently? This scenario does not populate the Shipping Address 1 field and makes multiple orders for the same SO#.

Children

*Community Hub is the new name for Sage City