The error is, that the field PTFNG should be in date-format just as DOC_DATE.
The strange thing is, that the XSLT we’re using to create the IDoc has identical rules for PSTNG and for DOC_DATE!
Relevant XSLT section:
…
<e1bp2017_gm_head_01>
<pstng_date>
<xsl:if>
<xsl:variable>
<xsl:call-template>
<xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:value-of>
<xsl:value-of>
<xsl:value-of>
</xsl:if>
</pstng_date>
<doc_date>
<xsl:if>
<xsl:variable>
<xsl:call-template>
<xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:value-of>
<xsl:value-of>
<xsl:value-of>
</xsl:if>
</doc_date>
…
I can’t reproduce the error, since everytime i trigger the original message again, the resulting IDoc is correct!?
Up to now the error occured only one time on the target system. All other Idocs created by the shown XSLT are correct…
Does anybody of you have similar experience or a hint for possible reasons?
Thanks in Advance!
Armin
I am sending the documents from Source system to WM environment. I am unable to see those documents in the target system. How do i check the documents in the queues???
how can i go to check the queues?
you could hava started a new thread since this thread is opened for a different problem.
Can you elaborate more on your process and what WM components are you using in your integration.
Anyways if your source pushing the documents to IS/Broker6.x here is the location of the Queue to view them
1.Go to Broker Admin page.(http://localhost:5555/WmBrokerAdmin/)
2. Click on the Broker Servers on the Broker Admin page.
3. Go to the Brokers in that Broker Server.You can see the Brokers tab at the top if you are using 6.1 version.
4. Click on the Broker.(can be any name you kept while creating brokers)
5. You will see the Document Types, Client Groups and Clients mentioned under Broker Information.
6. Click on the Clients.There you will see a client with your Trigger Name in the Client ID.
7. For that Client ID you will see a column called ‘Documents in Queue’.You can click on the ‘Documents in Queue’.
or else you can use the DocumentTracker tool and cofigure it to view the document traffic in the particular broker.