community-content

Forum Replies Created

Viewing 15 posts - 7,651 through 7,665 (of 9,652 total)
  • Author
    Posts
  • in reply to: parsing an edi file before it reaches the ediadapter? #15036

    If your EDI message is rejected because of a code value, it would behoove you to try to edit the receiving schema or envelope definition. In your case, it is most likely the Syntax definition you want to modify.

    in reply to: The recipient of the document isn’t recognized #15063

    This is how I have it configured now:

    Sender for both documents:
    Name: EDI Qualifier: EDI Value: EDI://619448418:01:AT&T-CBS/VTN

    Recipient 1, Document 1:
    Name: EDI Qualifier: EDI Value: EDI://CDHFVTNS:01:CDHFVTNS

    Recipient 2, Document 2:
    Name: EDI Qualifier: EDI Value: EDI://MAGATT:ZZ:MAGATT

    Is there something here that you see is a problem and if so, how would I correct it?

    in reply to: The recipient of the document isn’t recognized #15069

    And why two different identification code qualifiers, is that possible? In your file that pass through you got only one qulifier: 01…

    in reply to: The recipient of the document isn’t recognized #15068

    [quote:92ba16e9cf=\”nickka\”]I have found Microsoft BizTalk documentation that tells me to set up a Party Alias for both sender and recipient. It also says to use \”EDI\” in name and qualifier field.

    I have done all that but still get the error \”The recipient of the document isn’t recognized\”.

    I don’t know what steps to take to track this down. Any suggestions on what else I have to do?[/quote:92ba16e9cf]

    have you set up a PARTY sender and receiver with equivalent adress to sender and recipient adress… (in biztalk explorer)
    you also need to configure your edi adapter in biztalk administrator consol / … / adapters / edi:
    the send port needs edi adress and port no
    receive port only needs port no …

    in reply to: The recipient of the document isn’t recognized #15062

    I have found Microsoft BizTalk documentation that tells me to set up a Party Alias for both sender and recipient. It also says to use \”EDI\” in name and qualifier field.

    I have done all that but still get the error \”The recipient of the document isn’t recognized\”.

    I don’t know what steps to take to track this down. Any suggestions on what else I have to do?

    in reply to: reading lines of file #15049

    Exists other way?? Can we use to do this an ReceivePipeline?
    Thanks

    in reply to: reading lines of file #15052

    first thing it came up to my head:
    Use a filed as a \”flag\”, then on the orchestrations test the field (don’t forget to promote the field), and give it different sendports!

    in reply to: ServicedComponent in Orchestration #14054

    I think you’ll need to talk to the person who wrote the component but usually I’ve seen this when I had older VB 6, C++, etc code that must run as a COM+ component. i.e. not .net code.

    Hope this helps.

    in reply to: how to deal with multiple-line-trailer in flatfile #14052

    I’d create an Envelope Schema like:
    <root>
    <Doc>
    <Header>
    <Details> (1 to many for 1 record out and 1 to 1 for single records out)
    <Trailer> (record CR/LF delimited)
    <Totals>

    Set the body xpath at <root> and define three schemas for header, details, and trailer. Then, you should get three separate files out.

    To get into SQL you could simple use the SQL Adapter in a messaging solution or a simple Orchestration.

    Make sense?

    in reply to: reading lines of file #15048

    but, if I Have to create a new map, how I can aggregate this code??
    Or I have to aggregate this code in a form in the orchestration?

    and ,if for example, my file only contains a Id Field in the header, a Name field in the body and a IdEnd field in the end of the field.. how it would be the xslt?

    Thanks!! 😆

    Hi,

    I have two tables Table1 and Table2 in SQL 2000 db instance. I need to enter following data(parent-child) in these two tables.

    — sample file start——

    <?xml version=\”1.0\” encoding=\”utf-8\” ?>
    – <ns0:SampInst xmlns:ns0=\”http://TestFFSchemaProj1.SampInstSchema1\”>
    – <OutputHeader>
    <StrVariable1 />
    <ID>EXP-4</ID>
    <Initials>Bc</Initials>
    <Title>manager</Title>
    <Date>01.01.2002</Date>
    – <OutputValues>
    <Time>10:15:29</Time>
    <var1>107.0 1</var1>
    <var2>06.9</var2>
    <var3>75.0</var3>
    <var4>80.6</var4>
    </OutputValues>
    – <OutputValues>
    <Time>10:15:34</Time>
    <Lref>107.0 1</Lref>
    <var2>07.6</var2>
    <var3>75.0</var3>
    <var4>81.3</var4>
    </OutputValues>
    – <OutputValues>
    <Time>10:15:44</Time>
    <Lref>100.0 1</Lref>
    <var2>07.6</var2>
    <var3>85.0</var3>
    <var4>83.3</var4>
    </OutputValues>
    – <ReferenceNumber>
    <ReferenceID>12884566</ReferenceID>
    <ReferenceDate>2006-07-21T10:14:56</ReferenceDate>
    </ReferenceNumber>
    </ns0:SampInst>

    — sample file end——

    I am able to enter the data specified whithin <outputheader> into Table1 successfully. But I am only able to enter one child record from from the element <OutputValues> whithin Table2. I need to enter all rest of the child records whithin Table2.

    Need help..

    in reply to: Document type does not match any of the given schemas. #14046

    Looks like now I’m facing this issue:

    http://geekswithblogs.net/dmillard/archive/2004/12/10/17250.aspx

    This regards mapping TO an envelope schema.
    We receive data from a vendor, and want to \”scrub\” it and write to an envelope schema, then debatch it. The debatch is working, and the XSLT by itself to map to the envelope schema works. It just doesn’t work \”automatically\” on the receive port.

    I just wondered if any new solutions have come up.
    I hate to use an orchestration just to get around this error.

    Here’s the error:

    The Messaging Engine failed while executing the inbound map for the message coming from source URL:\”c:\\CompassionServices\\File Drops\\ISADailyBatchIn\\*.xml\” with the Message Type \”ci1xmltest\”. Details:\”Document type \”http://schemas.compassion.com/constituent/batch/cprinfo/2006-06-01#CPRInfo\” does not match any of the given schemas.

    Also see:
    http://www.webservertalk.com/archive178-2004-8-338739.html

    http://hugorodgerbrown.blogspot.com/2004/12/envelopes-maps-and-pipelines.html

    Thanks in advance,
    Neal

    in reply to: SAP Adapter For BTS2006 Wizard Disappeared #15091

    I have seen a lot of problems with SAP in BizTalk 2006.

    I think there is an SP1 for the SAP Adapter. Not sure were to get it – but I know there is also a CTP version and that version really causes problems.

    Hope this helps.

    in reply to: Rule Composer Facts Explorer #15098

    Does the Facts Explorer only recognize SQLServer databases? On the Database tab, when I Browse for servers all I see are SQLServers. I need to access facts in an Oracle db. After some time, I finally have a FactRetriever making an OleDb connection to Oracle that seems to work because I no longer get errors to the event log. How do you build rules that use an Oracle db?

    Thanks,

    in reply to: Publishing message #15078

    It’s been a while since I looked at the message box, but if I remember right the main table is the SPOOL table. The data is stored as a binary image so it’s hard to understand.

    I’d suggest not really digging into the message box. It’s not really a good place to look. Using the BizTalk Admin tool and HAT are much better ways to go.

    Hope this helps.

Viewing 15 posts - 7,651 through 7,665 (of 9,652 total)