Econnect and SOP bill/sold to customer bill to address

(0) Share

Report

Posted on by dma550x

Hello all,

I have been using what I thought was bill to address on a SOP document via econnect. I am struggling as I don't see full documentation on these, but would the taSopHdrIvcInsert.Address1 be sold to? The docs list it as "ADDRESS1 string 60 Customer address one"

ocHeader is my source data. Thank you!

var salesHdr = new taSopHdrIvcInsert
{
CUSTNMBR = ocHeader.CustomerId,
SLPRSNID = ocHeader.GPSlsprsnID,
ADDRESS1 = ocHeader.OCAddress1,
ADDRESS2 = ocHeader.OCAddress2,
CITY = ocHeader.OCCity,
STATE = ocHeader.OCState,
ZIPCODE = ocHeader.OCZip,
COUNTRY = ocHeader.OCCountry,
};

Categories:

Microsoft Dynamics GP

All responses (2)

Answers (1)

Cole69 40 on at

Like (0)

Report

RE: Econnect and SOP bill/sold to customer bill to address

I am importing SOP Orders using eConnect and sending in a unique 'override' Ship To address with the order Liteblue header.
Verified answer

Joseph Markovich 3,900 on at

Like (1)

Report

RE: Econnect and SOP bill/sold to customer bill to address

The address fields on the SOP header are actually the ship to address fields. It defaults to whatever is the primary Ship To address ID that is showing in the customer card, but can be changed to whatever.

The bill to address is just a reference back to whatever is the primary Bill To address in the customer card. That field is PRBTADCD.

I hope this helps.

Joe