none
Override UNA6Suffix in Orchestration RRS feed

  • Question

  • I am trying to set the UNA6Suffix to CRLF in the orchestration as below,

    FinalMessage(EdiOverride.OverrideEDIHeader) = true;
    FinalMessage(EdiOverride.UNB2_1) = Str_Sender;
    FinalMessage(EdiOverride.UNB3_1) = Str_Receiver;
    FinalMessage(EdiOverride.GenerateUNA) = true;
    FinalMessage(EdiOverride.UNA6Suffix) = "0x0D 0x0A";
    FinalMessage(EdiOverride.UNA1) = ":";
    FinalMessage(EdiOverride.UNA2) = "+";
    FinalMessage(EdiOverride.UNA3) = ".";
    FinalMessage(EdiOverride.UNA4) = "?";
    FinalMessage(EdiOverride.UNA5) = " ";
    FinalMessage(EdiOverride.UNA6) = "'";

    all the values are overridden successfully, but UNA6Suffix is not at all overridden and the file is coming as a straight line. Any help will much appreciated.

    Wednesday, February 28, 2018 9:52 AM

All replies

  • Can explain a bit on why you're trying to do this?  You probably shouldn't even try or don't need to.

    First, use Agreements.  Trying to avoid Agreements by using EdiOverride will likely cause more problems than it could ever solve.

    Second, segments really should have no suffix, especially in production.  This is for readability only and I don't recall every having a receiver that required them.  So, quadruple check, then get it in writing, that the receiver requires a CR/LF suffix.

    Wednesday, February 28, 2018 12:21 PM
  • I don't recall every having a receiver that required them.  So, quadruple check, then get it in writing, that the receiver requires a CR/LF suffix.

    You're in luck :)
    We have a bunch who parses edifact line by line, even adding extra valid elements can cause problems

    /Peter

    Wednesday, February 28, 2018 3:20 PM
  • In these cases, the first step is forcing them to admit they have the problem ;)
    Wednesday, February 28, 2018 3:57 PM