[Lewis Rosenberg]

Up

0

Down

::

This was a process issue. I needed to use //ASP (add selected packages) at to pack a group of packages into a new package. Doing this twice on one order will create two “P” levels.

[Lewis Rosenberg]

Up

0

Down

::

…and thank you to @gregalford for lining up so many of our great presenters!

[Lewis Rosenberg]

Up

0

Down

::

Please try again. That field was not meant to be required.

[Lewis Rosenberg]

Up

0

Down

::

BTW, Based on current registrations, we’re expecting our largest number of attendees tomorrow since we kicked off the 2023 webinar series!

[Lewis Rosenberg]

Up

0

Down

::

<< need the sequencing of items on 856 to match the sequencing on the 850. How is this best done?>>

Map the EDI 850 PO1 element 01 and the EDI 856 LIN element 01 to and “EDI In” field called “Assigned ID”

[Lewis Rosenberg]

Up

0

Down

::

If the G/L lines were received, they cannot be reversed. You’ll need to invoice them and then you can credit those entries.

[Lewis Rosenberg]

Up

0

Down

::

Thanks for the reply.

I edited my original note because there was no DELETE option, but I guess EDIT did not work either because my update is not on on the original post.

The request I received is actually different than what I posted. The user actually wants a custom value (customer’s shipment number) entered on the Sales Order carried through to and printed on the BOL. The best option for this will be a modification.

[Lewis Rosenberg]

Up

0

Down

::

I am not familiar with Line Status codes on the ASN/EDI 856 What segment is that?

If you are referring to the EDI855 (Purchase Order Acknowledgment), then you need to code it as E_SLSASN to use the status codes. I think that there is also an additional license requirement for the E_SLSASN. It may be the E_SLSPOA that is an export only document with no advanced functionality.

There are some Lanham team members that read this board, so if I am incorrect on any of this, hopefully, they’ll correct me.

[Lewis Rosenberg]

Up

0

Down

::

<<If you are referring to the EDI855 (Purchase Order Acknowledgment), then you need to code it as E_SLSASN to use the status codes>>

CORRECTION:
If you are referring to the EDI855 (Purchase Order Acknowledgment), then you need to code it as E_ADVPOA to use the status codes

[Lewis Rosenberg]

Up

0

Down

::

Bravo! I enjoyed every second!

[Lewis Rosenberg]

Up

0

Down

::

We are using SQL Server Authentication so a SQL account is used on the Authenticate tab of the Data Source Settings.

[Lewis Rosenberg]

Up

0

Down

::

Charlotte is the expert, but I would have expected CTT*3*6.

CTT01 = Number of Line items (3 LIN segments)

CTT02 = Sum of all SN102 segments (3+2+1)

I checked all of my EDI 856 maps and I never had to map the CTT02.

[Lewis Rosenberg]

Up

0

Down

::

Just as a follow up, I have confirmed that table 10044 – Sales Comment Line Detail does not exist in my database, although it is a mapping option. Mapping it does not yield any results for the MSG element on the item line loop.

[Lewis Rosenberg]

Up

0

Down

::

Thanks, Margaret.

I tried that and then could not even find the table in the Dev. Environment, but I will take a second look and try again.

[BC 14 on premise; EDI SE0.61.01 – Version (US Business Central 14.10)(E-Ship 3.17 (SE0.61.01 (SE0.61.01))) ]

[Lewis Rosenberg]

Up

0

Down

::

BTW, you can run multiple BC/NAV versions on your local machine (even if you are still using the Role Tailored Client). I currently have BC14, NAV 2017, and BC20 running on my laptop. BC14 and NAV2017 are on premise and for every day business (2 different companies in our organization) and BC20 is a Cronus database running locally for testing, demonstrations, and learning.