search

tian-zhihui / cordyssapcon

Automatically exported from code.google.com/p/cordyssapcon
Apache License 2.0
0 stars 0 forks source link

The error is occurring when we pass the field PARVW=IG in YISAORDERS05 IDOC #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The error is occurring when we pass the  field PARVW=IG.  The same is working 
fine, when we pass PARVW=RE or any other value.
So, there is syntax error throwing when the data  value is different for the 
same field. The syntax check happens at Cordys connector level.

Error log.

<log4j:event logger="com.cordys.coe.exception.ServerLocalizableException" 
timestamp="1354858507286" level="DEBUG" 
thread="socket:\\dcewbip01:35159/Worker-0">
<log4j:message><![CDATA[Going to use locale en_US to render message with ID 
com.eibus.applicationconnector.sap.exception.SAPConnectorExceptionMessages.Error
CheckingIdocSyntax]]></log4j:message>
<log4j:locationInfo class="com.cordys.coe.exception.ServerLocalizableException" 
method="getLocalizedMessage" file="ServerLocalizableException.java" line="193"/>
</log4j:event>

<log4j:event logger="com.cordys.coe.exception.ServerLocalizableException" 
timestamp="1354858507300" level="DEBUG" 
thread="socket:\\dcewbip01:35159/Worker-0">
<log4j:message><![CDATA[Going to use locale en_US to render message with ID 
com.eibus.applicationconnector.sap.exception.SAPConnectorExceptionMessages.Error
CheckingIdocSyntax]]></log4j:message>
<log4j:locationInfo class="com.eibus.applicationconnector.sap.SAPTransaction" 
method="process" file="SAPTransaction.java" line="305"/>
</log4j:event>

<log4j:event logger="com.cordys.coe.exception.ServerLocalizableException" 
timestamp="1354858507300" level="DEBUG" 
thread="socket:\\dcewbip01:35159/Worker-0">
<log4j:message><![CDATA[Going to use locale en_US to render message with ID 
com.eibus.applicationconnector.sap.exception.SAPConnectorExceptionMessages.Error
CheckingIdocSyntax]]></log4j:message>
<log4j:locationInfo class="com.eibus.applicationconnector.sap.SAPTransaction" 
method="process" file="SAPTransaction.java" line="305"/>
</log4j:event>

<log4j:throwable><![CDATA[com.eibus.applicationconnector.sap.exception.SAPConnec
torException: Error checking idoc syntax.
Field name: PARVW
Segment type: {1}
                at com.eibus.applicationconnector.sap.connection.jco.SAPJCoRequestSender.sendIDOCRequest(SAPJCoRequestSender.java:176)
                at com.eibus.applicationconnector.sap.connection.jco.SAPJCoRequestHandler.handleIDOCRequest(SAPJCoRequestHandler.java:353)
                at com.eibus.applicationconnector.sap.SAPTransaction.process(SAPTransaction.java:233)
                at com.eibus.soap.SOAPTransaction.handleBodyBlock(SOAPTransaction.java:1305)
                at com.eibus.soap.SOAPTransaction.<init>(SOAPTransaction.java:602)
                at com.eibus.soap.SOAPTransaction.<init>(SOAPTransaction.java:175)
                at com.eibus.soap.Processor.onReceive(Processor.java:970)
                at com.eibus.soap.Processor.onReceive(Processor.java:943)
                at com.eibus.connector.nom.Connector.onReceive(Connector.java:417)
                at com.eibus.transport.Middleware$NonTransactionalWorkerThreadBody.run(Middleware.java:1758)
                at com.eibus.util.threadpool.WorkerThread.run(WorkerThread.java:64)
Caused by: com.sap.mw.idoc.IDoc$SyntaxException: (1) IDOC_ERROR_SYNTAX: Invalid 
value for segment field: PARVW
                at com.sap.mw.idoc.jco.JCoIDoc$JCoRecord.checkFieldValues(JCoIDoc.java:4965)
                at com.sap.mw.idoc.jco.JCoIDoc$JCoSegment.checkSyntax(JCoIDoc.java:6409)
                at com.sap.mw.idoc.jco.JCoIDoc$JCoSegment.checkSyntax(JCoIDoc.java:6422)
                at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.checkSyntax(JCoIDoc.java:917)
                at com.sap.mw.idoc.jco.JCoIDoc$JCoDocument.checkSyntax(JCoIDoc.java:871)
                at com.eibus.applicationconnector.sap.connection.jco.SAPJCoRequestSender.sendIDOCRequest(SAPJCoRequestSender.java:172)
                ... 10 more
]]></log4j:throwable>
<log4j:locationInfo class="com.eibus.applicationconnector.sap.SAPTransaction" 
method="process" file="SAPTransaction.java" line="305"/>
</log4j:event>

Original issue reported on code.google.com by masthan....@cordys.com on 17 Dec 2012 at 11:11

GoogleCodeExporter commented 8 years ago 
I'll handle this one.

Original comment by jvmo...@cordys.com on 17 Dec 2012 at 11:21

GoogleCodeExporter commented 8 years ago 
I verified the IDOC definition on Schneider system. The CheckSyntax seems to be 
working as per the definitions. It is validating the input value against the 
segment - fields - domain - value range( from the data dictionary) . As per the 
data dictionary the permissible values for PARVW are as below. I can read this 
information from api.
AA = Customer - Financial document
AG = Sold-to party
AP = Contact Person
AW = Shipped-to party financial document
BA = Bank sold-to party
BB = Bank beneficiary/partner for debit memo
BE = Beneficiary
BK = Company code address
CC = SPEC2000 customer code
CO = Competitors
DE = Bank holding account
EK = Buyer
I1 = Sender's correspondent bank
I2 = Intermediary bank
I3 = Recipient's correspondent bank
I4 = External house bank
LF = Vendor
LFA = Vendor for additionals
LFL = Vendor (from vendor view)
ME = Declarant
OB = Opening bank
PA = Partner for debit memo/direct debit/bank collection
RE = Invoice recipient
RG = Payer
RS = Invoicing party
SLS = Supplementary logistics service
SP = Carrier
VR = Substitute
WE = Goods recipient
ZA = Payer
ZE = Payment recipient
ZM = Responsible employee

You can view this information in SAP - SE31 transaction . Please find the 
attached screen shot.

So now the question is, are you sending the value "IG" for PARVW if it is not 
listed in the data dictionary.

Original comment by jvmo...@cordys.com on 19 Dec 2012 at 4:43

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by jvmo...@cordys.com on 19 Dec 2012 at 4:46

GoogleCodeExporter commented 8 years ago 
Please report this in a more appropriate place.

Original comment by jvmo...@cordys.com on 19 Dec 2012 at 4:46