EDI Outbound 850 and Purch. Comment Lines

KimDynKimDyn Member Posts: 35
edited 2008-07-21 in Navision Attain
Does anyone have experience mapping Purch. Comment Lines into an Outbound 850 from Lanham's Gen2 EDI system? We have also created a customized table that stores Purch. Line Comments and we would like to map those also.

Any suggestions???

Thanks!
Kimberly Weir

Comments

  • SavatageSavatage Member Posts: 7,142
    What kind of comments are you referring to? Unlimited using loops? or something like a 250 character MSG line?

    do you have any working 850's now? any MSG segment?
    or are looking to do Like a line item with
    Command: Line Begin
    Segment MSG: comment line message
    Command: Line End

    I think Alex is the EDI king. Howefully he's not vacation O:)
  • KimDynKimDyn Member Posts: 35
    Savatage wrote:
    What kind of comments are you referring to? Unlimited using loops? or something like a 250 character MSG line?

    do you have any working 850's now? any MSG segment?
    or are looking to do Like a line item with
    Command: Line Begin
    Segment MSG: comment line message
    Command: Line End

    I think Alex is the EDI king. Howefully he's not vacation O:)

    I have ran the MSG segment in the loop and everything ran fine, Thanks! =D>

    I have not been successful in getting the custom Purch. Line Comment Lines to loop in.

    Does the EDI system allow for nested loops?

    Command: Line Begin
    Segment PO1: PO Line Details
    Command: Line Begin
    Segment REF: Purch. Line Comment Line
    Command: Line End
    Command: Line End

    That is the one I really struggle with. ](*,)

    Without the nested loop I only get the first line in the table.
    Kimberly Weir
  • SavatageSavatage Member Posts: 7,142
    KimDyn wrote:
    I have ran the MSG segment in the loop and everything ran fine, Thanks! =D>
    Great!!
    KimDyn wrote:
    I have not been successful in getting the custom Purch. Line Comment Lines to loop in.

    Does the EDI system allow for nested loops?

    Command: Line Begin
    Segment PO1: PO Line Details
    Command: Line Begin
    Segment REF: Purch. Line Comment Line
    Command: Line End
    Command: Line End
    That is the one I really struggle with. ](*,)
    Without the nested loop I only get the first line in the table.
    My version doesn't have Line comments but "guessing" I would think it would be more like this?? but I'm guessing..
      Command: Line Begin Segment PO1: PO Line Details Segment REF: Purch. Line Comment Line Command: Line End
  • KimDynKimDyn Member Posts: 35
    Savatage wrote:
    My version doesn't have Line comments but "guessing" I would think it would be more like this?? but I'm guessing..
      Command: Line Begin Segment PO1: PO Line Details Segment REF: Purch. Line Comment Line Command: Line End

    That is how I tried to code it at first, but it doesn't loop through all the comments, it only pulls in the first one in the table. Then I attempt:
      Command: Line Begin Segment PO1: PO Line Details Command: Line Begin Segment REF: Purch. Line Comment Line Command: Line End Command: Line End

    And that does not work either.[/list]
    Kimberly Weir
  • Alex_ChowAlex_Chow Member Posts: 5,063
    Instead of putting the MSG into the comments, why not just show it on the EDI Received Elements? You can modify your pick tickets to read from the MSG segment from teh EDI received elements.

    We've only modified the comments to be exported in 810, 855, 856 to notify EDI customers of comments made.
  • KimDynKimDyn Member Posts: 35
    Alex Chow wrote:
    Instead of putting the MSG into the comments, why not just show it on the EDI Received Elements? You can modify your pick tickets to read from the MSG segment from teh EDI received elements.

    We've only modified the comments to be exported in 810, 855, 856 to notify EDI customers of comments made.

    That is how we handle inbound REF and MSG segments, but we need to send them out in an Outbound 850. With some help :) I am now successful in sending out the Header Comments, but I am not successful in sending out Purch. Line Comments.
    Kimberly Weir
  • Alex_ChowAlex_Chow Member Posts: 5,063
    KimDyn wrote:
    Alex Chow wrote:
    Instead of putting the MSG into the comments, why not just show it on the EDI Received Elements? You can modify your pick tickets to read from the MSG segment from teh EDI received elements.

    We've only modified the comments to be exported in 810, 855, 856 to notify EDI customers of comments made.

    That is how we handle inbound REF and MSG segments, but we need to send them out in an Outbound 850. With some help :) I am now successful in sending out the Header Comments, but I am not successful in sending out Purch. Line Comments.

    Where do you enter the purchase line comments? As a line without the Type field blank? Or is it a custom table?
  • KimDynKimDyn Member Posts: 35
    Alex Chow wrote:
    Where do you enter the purchase line comments? As a line without the Type field blank? Or is it a custom table?

    A custom table that is setup to operate the same way as the Purch. Comment Line functionality works but for each individual line.
    Kimberly Weir
  • Joe_MathisJoe_Mathis Member Posts: 173
    Might be late to the party, but did you modify the report 140002350 to get your customized tables made available?

    There is some code that has a bunch of
    '3|10|18|23|27|36|37|38|39|79|110|111|112|113|114|115|222|291|5404|14002350|14002353|' +
    
    text lines. You have to add your custom table there, run the report and import and compile the resulting text file.

    Also I tried to nest loops a while back and it never ran right. But that was in an older version (two years ago ??) than they currently offer, so it might work now.

    Good luck
  • Alex_ChowAlex_Chow Member Posts: 5,063
    I've gotten the comments to export as an MSG segment on the sales export looking into the sales comment line table. However, the modification was for codeunit 14002360, not the purchase side of the EDI module... :(

    My suggestion is to ask your NSC to develope this for you.
Sign In or Register to comment.