| Author |
Message
|
| punky |
 Posted: Wed Mar 27, 2013 8:31 pm Post subject: Facing issues with SAP adapter in version 7.0.0.5 |
 |
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi Masters,
We are using SAP adapter (inbound) for scenario SAP--> WMB to publish data on topics.
Initially we were at version 7.0.0.2, where we faced issues where SAP adapter getting confused with multiple (types) of IDOCs coming in.
With advice from masters and raisinga query to IBM, we moved with upgrading the toolkit and the runtime.
As adviced by IBM we rediscovered the IDOCS from sap adapter connection wizard before deployment.
Issue:
The flow was tested ok in dev, QAL and UAT environment, BUT
in production we are observing issues in which the SAP adapter fails to receive complete IDOC (it receives control records and ignores data records).
Incomplete message
| Quote: |
- <NS1:SapZMdBupaInbMainSaveM01 xmlns:NS1="http://www.nol.com.sg/sapzmdbupainbmainsavem01">
<SAPTransactionID>AC115937024850F12B5F0BA1</SAPTransactionID>
- <SapZMdBupaInbMainSaveM01IDocBO>
- <SapIDocControlRecord>
<RCVPOR>ZWMB_PUB</RCVPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC />
<TEST />
<MESCOD />
<IDOCTYP>Z_MD_BUPA_INB_MAIN_SAVE_M01</IDOCTYP>
<SNDPRN>PCPCLNT168</SNDPRN>
<STD />
<ARCKEY />
<CRETIM>205146</CRETIM>
<DOCTYP />
<TABNAM />
<CREDAT>20130111</CREDAT>
<REFGRP />
<OUTMOD>2</OUTMOD>
<MANDT>168</MANDT>
<RCVSAD />
<MESTYP>Z_MD_BUPA_INB_MAIN_SAVE_M</MESTYP>
<RCVPRN>PCPCLNT111</RCVPRN>
<STDVRS />
<RCVLAD />
<DIRECT>1</DIRECT>
<SNDLAD />
<EXPRSS />
<SNDSAD />
<DOCREL>701</DOCREL>
<SERIAL>20130111205146</SERIAL>
<SNDPOR>SAPPCP</SNDPOR>
<DOCNUM>0000000003155071</DOCNUM>
<STDMES />
<REFINT />
<RCVPFC />
<REFMES />
<MESFCT />
<CIMTYP />
<STATUS>30</STATUS>
<RCVPRT>LS</RCVPRT>
</SapIDocControlRecord>
<SapZMdBupaInbMainSaveM01DataRecord />
</SapZMdBupaInbMainSaveM01IDocBO>
</NS1:SapZMdBupaInbMainSaveM01> |
Expected structure:
| Quote: |
- <NS1:SapZMdBupaInbMainSaveM01 xmlns:NS1="http://www.nol.com.sg/sapzmdbupainbmainsavem01">
<SAPTransactionID>AC11582401A350F29784E3AB</SAPTransactionID>
- <SapZMdBupaInbMainSaveM01IDocBO>
- <SapIDocControlRecord>
<RCVPOR>ZWMB_PUB</RCVPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC />
<TEST />
<MESCOD />
<IDOCTYP>Z_MD_BUPA_INB_MAIN_SAVE_M01</IDOCTYP>
<SNDPRN>PCPCLNT168</SNDPRN>
<STD />
<ARCKEY />
<CRETIM>031610</CRETIM>
<DOCTYP />
<TABNAM />
<CREDAT>20130113</CREDAT>
<REFGRP />
<OUTMOD>2</OUTMOD>
<MANDT>168</MANDT>
<RCVSAD />
<MESTYP>Z_MD_BUPA_INB_MAIN_SAVE_M</MESTYP>
<RCVPRN>PCPCLNT111</RCVPRN>
<STDVRS />
<RCVLAD />
<DIRECT>1</DIRECT>
<SNDLAD />
<EXPRSS />
<SNDSAD />
<DOCREL>701</DOCREL>
<SERIAL>20130113031609</SERIAL>
<SNDPOR>SAPPCP</SNDPOR>
<DOCNUM>0000000003173457</DOCNUM>
<STDMES />
<REFINT />
<RCVPFC />
<REFMES />
<MESFCT />
<CIMTYP />
<STATUS>30</STATUS>
<RCVPRT>LS</RCVPRT>
</SapIDocControlRecord>
- <SapZMdBupaInbMainSaveM01DataRecord>
- <SapZMdBupaInbMainSaveM01Z201zcrmdstSbusEiExtern000>
<APPL_SNAME>ZCRMDST_SBUS_EI_EXTERN</APPL_SNAME>
<ZZKQV_CURRENT_STATE />
<ZZKQV_TIME_DEPENDENT />
- <SapZMdBupaInbMainSaveM01E201busEiHeader000>
<APPL_SNAME>BUS_EI_HEADER</APPL_SNAME>
<OBJECT>BusinessPartner</OBJECT>
<OBJECT_TASK>I</OBJECT_TASK>
- <SapZMdBupaInbMainSaveM01E201busEiInstance000>
<APPL_SNAME>BUS_EI_INSTANCE</APPL_SNAME>
<BPARTNER>9100287315</BPARTNER>
<BPARTNERGUID>50F2BDCE1D4601A3E1008000AC115824</BPARTNERGUID>
<IDENTIFICATIONCATEGORY />
<IDENTIFICATIONNUMBER />
</SapZMdBupaInbMainSaveM01E201busEiInstance000>
</SapZMdBupaInbMainSaveM01E201busEiHeader000>
- <SapZMdBupaInbMainSaveM01Z201stSbusEiCentralData000>
<APPL_SNAME>ZCRMDST_SBUS_EI_CENTRAL_DATA</APPL_SNAME>
- <SapZMdBupaInbMainSaveM01Z201stSbusEiBupaCentral000>
<APPL_SNAME>ZCRMDST_SBUS_EI_BUPA_CENTRAL</APPL_SNAME>
- <SapZMdBupaInbMainSaveM01E201usEiBupaCentralData000>
<APPL_SNAME>BUS_EI_BUPA_CENTRAL_DATA</APPL_SNAME>
<BP_EEW_DUMMY />
- <SapZMdBupaInbMainSaveM01E201usEiBupaCentralMain000>
<APPL_SNAME>BUS_EI_BUPA_CENTRAL_MAIN</APPL_SNAME>
<CATEGORY>1</CATEGORY>
<GROUPING>Z001</GROUPING>
</SapZMdBupaInbMainSaveM01E201usEiBupaCentralMain000>
- <SapZMdBupaInbMainSaveM01E201busEiStrucCentral001>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL</APPL_SNAME>
<SEARCHTERM1 />
<SEARCHTERM2>Z001</SEARCHTERM2>
<PARTNERTYPE>Z001</PARTNERTYPE>
<AUTHORIZATIONGROUP>ZC01</AUTHORIZATIONGROUP>
<PARTNERLANGUAGE />
<PARTNERLANGUAGEISO />
<DATAORIGINTYPE />
<CENTRALARCHIVINGFLAG />
<CENTRALBLOCK />
<TITLE_KEY />
<CONTACTALLOWANCE />
<PARTNEREXTERNAL />
<TITLELETTER />
<NOTRELEASED />
<COMM_TYPE />
<PRINT_MODE />
</SapZMdBupaInbMainSaveM01E201busEiStrucCentral001>
- <SapZMdBupaInbMainSaveM01E201eiStrucCentralPerson001>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_PERSON</APPL_SNAME>
<FIRSTNAME>****</FIRSTNAME>
<LASTNAME />
<BIRTHNAME />
<MIDDLENAME />
<SECONDNAME />
<TITLE_ACA1 />
<TITLE_ACA2 />
<TITLE_SPPL />
<PREFIX1 />
<PREFIX2 />
<NICKNAME />
<INITIALS />
<NAMEFORMAT />
<NAMCOUNTRY />
<NAMCOUNTRYISO />
<SEX />
<BIRTHPLACE />
<BIRTHDATE>00000000</BIRTHDATE>
<DEATHDATE>00000000</DEATHDATE>
<MARITALSTATUS />
<CORRESPONDLANGUAGE>E</CORRESPONDLANGUAGE>
<CORRESPONDLANGUAGEISO>EN</CORRESPONDLANGUAGEISO>
<FULLNAME />
<EMPLOYER />
<OCCUPATION />
<NATIONALITY />
<NATIONALITYISO />
<COUNTRYORIGIN />
<FULLNAME_MAN />
</SapZMdBupaInbMainSaveM01E201eiStrucCentralPerson001>
- <SapZMdBupaInbMainSaveM01E201EiStrucCentralOrgan000>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_ORGAN</APPL_SNAME>
<NAME1 />
<NAME2 />
<NAME3 />
<NAME4 />
<LEGALFORM />
<INDUSTRYSECTOR />
<FOUNDATIONDATE>00000000</FOUNDATIONDATE>
<LIQUIDATIONDATE>00000000</LIQUIDATIONDATE>
<LOC_NO_1>0000000</LOC_NO_1>
<LOC_NO_2>00000</LOC_NO_2>
<CHK_DIGIT>0</CHK_DIGIT>
<LEGALORG />
</SapZMdBupaInbMainSaveM01E201EiStrucCentralOrgan000>
- <SapZMdBupaInbMainSaveM01E201EiStrucCentralGroup000>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_GROUP</APPL_SNAME>
<NAMEGROUP1 />
<NAMEGROUP2 />
<GROUPTYPE />
</SapZMdBupaInbMainSaveM01E201EiStrucCentralGroup000>
- <SapZMdBupaInbMainSaveM01Z201ciEewBut000000>
<APPL_SNAME>CI_EEW_BUT000</APPL_SNAME>
<ZZCRMD_ORGN />
<ZZCRMD_PNAME />
<ZZCRMD_CPFUL>****</ZZCRMD_CPFUL>
<ZZCRMD_BRC_TRR />
<ZZCRMD_CHNG_FLAG />
<ZZCRMD_UC_NAME />
<ZZCRMD_ACC_STAT>A</ZZCRMD_ACC_STAT>
<ZZCRMD_DEPT />
<ZZCRMD_UPD_DAT>00000000</ZZCRMD_UPD_DAT>
<ZZCRMD_UPD_TIM>000000</ZZCRMD_UPD_TIM>
<ZZCRMD_TIM_ZON />
<ZZCRMD_COMP />
</SapZMdBupaInbMainSaveM01Z201ciEewBut000000>
</SapZMdBupaInbMainSaveM01E201usEiBupaCentralData000>
- <SapZMdBupaInbMainSaveM01E201bupaCentralDataXflag000>
<APPL_SNAME>BUS_EI_BUPA_CENTRAL_DATA_XFLAG</APPL_SNAME>
<BP_EEW_DUMMY />
- <SapZMdBupaInbMainSaveM01E201busEiStrucCentralX001>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_X</APPL_SNAME>
<SEARCHTERM1>X</SEARCHTERM1>
<SEARCHTERM2>X</SEARCHTERM2>
<PARTNERTYPE>X</PARTNERTYPE>
<AUTHORIZATIONGROUP>X</AUTHORIZATIONGROUP>
<PARTNERLANGUAGE>X</PARTNERLANGUAGE>
<PARTNERLANGUAGEISO>X</PARTNERLANGUAGEISO>
<DATAORIGINTYPE>X</DATAORIGINTYPE>
<CENTRALARCHIVINGFLAG>X</CENTRALARCHIVINGFLAG>
<CENTRALBLOCK>X</CENTRALBLOCK>
<TITLE_KEY>X</TITLE_KEY>
<CONTACTALLOWANCE>X</CONTACTALLOWANCE>
<PARTNEREXTERNAL>X</PARTNEREXTERNAL>
<TITLELETTER>X</TITLELETTER>
<NOTRELEASED>X</NOTRELEASED>
<COMM_TYPE>X</COMM_TYPE>
<PRINT_MODE>X</PRINT_MODE>
</SapZMdBupaInbMainSaveM01E201busEiStrucCentralX001>
- <SapZMdBupaInbMainSaveM01E201StrucCentralPersonX000>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_PERSON_X</APPL_SNAME>
<FIRSTNAME>X</FIRSTNAME>
<LASTNAME>X</LASTNAME>
<BIRTHNAME>X</BIRTHNAME>
<MIDDLENAME>X</MIDDLENAME>
<SECONDNAME>X</SECONDNAME>
<TITLE_ACA1>X</TITLE_ACA1>
<TITLE_ACA2>X</TITLE_ACA2>
<TITLE_SPPL>X</TITLE_SPPL>
<PREFIX1>X</PREFIX1>
<PREFIX2>X</PREFIX2>
<NICKNAME>X</NICKNAME>
<INITIALS>X</INITIALS>
<NAMEFORMAT>X</NAMEFORMAT>
<NAMCOUNTRY>X</NAMCOUNTRY>
<NAMCOUNTRYISO>X</NAMCOUNTRYISO>
<SEX>X</SEX>
<BIRTHPLACE>X</BIRTHPLACE>
<BIRTHDATE>X</BIRTHDATE>
<DEATHDATE>X</DEATHDATE>
<MARITALSTATUS>X</MARITALSTATUS>
<CORRESPONDLANGUAGE>X</CORRESPONDLANGUAGE>
<CORRESPONDLANGUAGEISO>X</CORRESPONDLANGUAGEISO>
<FULLNAME />
<EMPLOYER>X</EMPLOYER>
<OCCUPATION>X</OCCUPATION>
<NATIONALITY>X</NATIONALITY>
<NATIONALITYISO>X</NATIONALITYISO>
<COUNTRYORIGIN>X</COUNTRYORIGIN>
</SapZMdBupaInbMainSaveM01E201StrucCentralPersonX000>
- <SapZMdBupaInbMainSaveM01E201iStrucCentralOrganX000>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_ORGAN_X</APPL_SNAME>
<NAME1 />
<NAME2 />
<NAME3 />
<NAME4 />
<LEGALFORM />
<INDUSTRYSECTOR />
<FOUNDATIONDATE />
<LIQUIDATIONDATE />
<LOC_NO_1 />
<LOC_NO_2 />
<CHK_DIGIT />
<LEGALORG />
</SapZMdBupaInbMainSaveM01E201iStrucCentralOrganX000>
- <SapZMdBupaInbMainSaveM01E201iStrucCentralGroupX000>
<APPL_SNAME>BUS_EI_STRUC_CENTRAL_GROUP_X</APPL_SNAME>
<NAMEGROUP1 />
<NAMEGROUP2 />
<GROUPTYPE />
</SapZMdBupaInbMainSaveM01E201iStrucCentralGroupX000>
- <SapZMdBupaInbMainSaveM01Z201ciEewBut000X000>
<APPL_SNAME>CI_EEW_BUT000_X</APPL_SNAME>
<ZZCRMD_ORGN>X</ZZCRMD_ORGN>
<ZZCRMD_PNAME>X</ZZCRMD_PNAME>
<ZZCRMD_CPFUL>X</ZZCRMD_CPFUL>
<ZZCRMD_BRC_TRR>X</ZZCRMD_BRC_TRR>
<ZZCRMD_CHNG_FLAG>X</ZZCRMD_CHNG_FLAG>
<ZZCRMD_UC_NAME>X</ZZCRMD_UC_NAME>
<ZZCRMD_ACC_STAT>X</ZZCRMD_ACC_STAT>
<ZZCRMD_DEPT>X</ZZCRMD_DEPT>
<ZZCRMD_UPD_DAT>X</ZZCRMD_UPD_DAT>
<ZZCRMD_UPD_TIM>X</ZZCRMD_UPD_TIM>
<ZZCRMD_TIM_ZON>X</ZZCRMD_TIM_ZON>
<ZZCRMD_COMP>X</ZZCRMD_COMP>
</SapZMdBupaInbMainSaveM01Z201ciEewBut000X000>
</SapZMdBupaInbMainSaveM01E201bupaCentralDataXflag000>
</SapZMdBupaInbMainSaveM01Z201stSbusEiBupaCentral000>
- <SapZMdBupaInbMainSaveM01E201busEiRoles000>
<APPL_SNAME>BUS_EI_ROLES</APPL_SNAME>
<CURRENT_STATE />
<TIME_DEPENDENT />
- <SapZMdBupaInbMainSaveM01E201busEiBupaRoles000>
<APPL_SNAME>BUS_EI_BUPA_ROLES</APPL_SNAME>
<TASK>I</TASK>
<DATA_KEY>BUP001</DATA_KEY>
<CURRENTLY_VALID>X</CURRENTLY_VALID>
- <SapZMdBupaInbMainSaveM01E201busEiRoleData000>
<APPL_SNAME>BUS_EI_ROLE_DATA</APPL_SNAME>
<DIFFTYPEVALUE />
<ROLECATEGORY>******</ROLECATEGORY>
<VALID_FROM>00010101</VALID_FROM>
<VALID_TO>99991231</VALID_TO>
</SapZMdBupaInbMainSaveM01E201busEiRoleData000>
- <SapZMdBupaInbMainSaveM01E201busEiRoleDataX000>
<APPL_SNAME>BUS_EI_ROLE_DATA_X</APPL_SNAME>
<VALID_FROM>X</VALID_FROM>
<VALID_TO>X</VALID_TO>
</SapZMdBupaInbMainSaveM01E201busEiRoleDataX000>
</SapZMdBupaInbMainSaveM01E201busEiBupaRoles000>
</SapZMdBupaInbMainSaveM01E201busEiRoles000>
- <SapZMdBupaInbMainSaveM01E201busEiBankdetail000>
<APPL_SNAME>BUS_EI_BANKDETAIL</APPL_SNAME>
<CURRENT_STATE />
<TIME_DEPENDENT />
</SapZMdBupaInbMainSaveM01E201busEiBankdetail000>
- <SapZMdBupaInbMainSaveM01E201busEiCreditcard000>
<APPL_SNAME>BUS_EI_CREDITCARD</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiCreditcard000>
- <SapZMdBupaInbMainSaveM01E201busEiIndustrysector000>
<APPL_SNAME>BUS_EI_INDUSTRYSECTOR</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiIndustrysector000>
- <SapZMdBupaInbMainSaveM01E201busEiIdentification000>
<APPL_SNAME>BUS_EI_IDENTIFICATION</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiIdentification000>
- <SapZMdBupaInbMainSaveM01E201busEiTaxnumber000>
<APPL_SNAME>BUS_EI_TAXNUMBER</APPL_SNAME>
<CURRENT_STATE />
- <SapZMdBupaInbMainSaveM01E201busEiTaxCommon000>
<APPL_SNAME>BUS_EI_TAX_COMMON</APPL_SNAME>
- <SapZMdBupaInbMainSaveM01E201busEiStrucTaxCommon000>
<APPL_SNAME>BUS_EI_STRUC_TAX_COMMON</APPL_SNAME>
<NAT_PERSON />
</SapZMdBupaInbMainSaveM01E201busEiStrucTaxCommon000>
- <SapZMdBupaInbMainSaveM01E201sEiStrucTaxCommonX000>
<APPL_SNAME>BUS_EI_STRUC_TAX_COMMON_X</APPL_SNAME>
<NAT_PERSON />
</SapZMdBupaInbMainSaveM01E201sEiStrucTaxCommonX000>
</SapZMdBupaInbMainSaveM01E201busEiTaxCommon000>
</SapZMdBupaInbMainSaveM01E201busEiTaxnumber000>
- <SapZMdBupaInbMainSaveM01E201busEiCommunication000>
<APPL_SNAME>BUS_EI_COMMUNICATION</APPL_SNAME>
<TIME_DEPENDENT />
- <SapZMdBupaInbMainSaveM01E201busEiTelData000>
<APPL_SNAME>BUS_EI_TEL_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiTelData000>
- <SapZMdBupaInbMainSaveM01E201busEiFaxData000>
<APPL_SNAME>BUS_EI_FAX_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiFaxData000>
- <SapZMdBupaInbMainSaveM01E201busEiTtxData000>
<APPL_SNAME>BUS_EI_TTX_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiTtxData000>
- <SapZMdBupaInbMainSaveM01E201busEiTlxData000>
<APPL_SNAME>BUS_EI_TLX_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiTlxData000>
- <SapZMdBupaInbMainSaveM01E201busEiSmtpData000>
<APPL_SNAME>BUS_EI_SMTP_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiSmtpData000>
- <SapZMdBupaInbMainSaveM01E201busEiRmlData000>
<APPL_SNAME>BUS_EI_RML_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiRmlData000>
- <SapZMdBupaInbMainSaveM01E201busEiX400Data000>
<APPL_SNAME>BUS_EI_X400_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiX400Data000>
- <SapZMdBupaInbMainSaveM01E201busEiRfcData000>
<APPL_SNAME>BUS_EI_RFC_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiRfcData000>
- <SapZMdBupaInbMainSaveM01E201busEiPrtData000>
<APPL_SNAME>BUS_EI_PRT_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiPrtData000>
- <SapZMdBupaInbMainSaveM01E201busEiSsfData000>
<APPL_SNAME>BUS_EI_SSF_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiSsfData000>
- <SapZMdBupaInbMainSaveM01E201busEiUriData000>
<APPL_SNAME>BUS_EI_URI_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiUriData000>
- <SapZMdBupaInbMainSaveM01E201busEiPagData000>
<APPL_SNAME>BUS_EI_PAG_DATA</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiPagData000>
</SapZMdBupaInbMainSaveM01E201busEiCommunication000>
- <SapZMdBupaInbMainSaveM01Z201zcrmdstSbusEiAddress000>
<APPL_SNAME>ZCRMDST_SBUS_EI_ADDRESS</APPL_SNAME>
<CURRENT_STATE />
<TIME_DEPENDENT />
</SapZMdBupaInbMainSaveM01Z201zcrmdstSbusEiAddress000>
- <SapZMdBupaInbMainSaveM01E201busEiHour000>
<APPL_SNAME>BUS_EI_HOUR</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiHour000>
- <SapZMdBupaInbMainSaveM01E201busEiStatus000>
<APPL_SNAME>BUS_EI_STATUS</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiStatus000>
- <SapZMdBupaInbMainSaveM01E201busEiLongtext000>
<APPL_SNAME>BUS_EI_LONGTEXT</APPL_SNAME>
<CURRENT_STATE />
</SapZMdBupaInbMainSaveM01E201busEiLongtext000>
</SapZMdBupaInbMainSaveM01Z201stSbusEiCentralData000>
</SapZMdBupaInbMainSaveM01Z201zcrmdstSbusEiExtern000>
</SapZMdBupaInbMainSaveM01DataRecord>
</SapZMdBupaInbMainSaveM01IDocBO>
</NS1:SapZMdBupaInbMainSaveM01> |
As this is intermittent (happens for say 4 IDOCS in a week) so the possible issues could be:
1. Data
2. Volume
3. System issues.
Our analysis:
Data: when we reprocess the failed IDOCS again from SAP, they get processed. So we can rule out the possibility for data issues.
Volume: We have load tested the flow for 10K IDOCs in UAT environment and it performed OK.
We have done a day to day analysis for the IDOCs processed by the SAP adapter and found that the IDOCS going through the SAP adapter are higher then the normal avarage on the day the issue occurs (but still less then the load tested for).
System issues: We have checked the system logs, and they appear OK.
In addition, we got the JVM max heap increased from 1 GB to 1.5 GB, but the issue is still observed.
As this is production environment, and issue is intermittent, it would be difficult to get the traces (service and user).
Please help me with your experience and advice me on the approach to fix this issue.
Best Regards,
Punky |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Mar 27, 2013 9:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To trouble shoot this problem you'd need an RFC trace (see adapter tracing).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| punky |
| Posted: Wed Mar 27, 2013 11:15 pm Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi fjb_saper,
Just to mention again:
We were not able to replicate this issue in non-production environment.
So do you advice setting up the trace in production environment and at what level?
Even we are not sure when the issue occurs, so say if it occurs after processing 25K IDOCS, this may impact performance as well as the business.
Please advice.
| Quote: |
mqsicreateconfigurableservice WBRK61_DEFAULT_BROKER -c SAPConnection -o mySAPAdapter.outadapter
-n applicationServerHost,client,RFCTraceOn,RFCTracePath -v test.sap.ibm.com,001,true,/home/pbayapp
|
Regards,
Punky |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 28, 2013 3:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So I would hope that you weren't using WBRK61_DEFAULT_BROKER - In production
- as the name of a 7.0.0.x Broker
That's the name that is created by the default configuration wizard for v6.1. The default configuration wizard will create the queue manager for the broker for you, and this is pretty much guaranteed to be sized wrong for production uses.
Since you can't seem to recreate the issue, then the best you can do is try and categorize *when* it happens, and that requires knowing *that* it has happened.
You should also open a PMR with IBM and discuss this.
You should also look for errors on the system log and examine the SYSTEM.BROKER queues to see if there's any stray messages.
You should ALSO very thoroughly examine the SAP logs and make sure that it's not reporting any errors anywhere when it tries to send these records and they fail. |
|
| Back to top |
|
|
| punky |
| Posted: Thu Mar 28, 2013 4:25 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi mqjeff,
The command mentioned is just a sample.
We have configured the flow in a way that whenever an IDOC comes in without payload (data records), an alert mail is sent to me.
So I am analysing the data for last 15 days, to draw out some pattern to find out when this happens.
Approach ahead:
would analyse the patter for occurence of this issue.
would analyse the system for memory and CPU utilisation at SAP end.
Would check teh system logs at SAP end for the time of errors.
Even would ask WMB team to use some stastical and analysis tools (need to check on them) to monitor system resources during the errors.
Please let me know if I someone has faced this issue before and let me know if I can add something to the approach above.
Regards,
Punky |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 28, 2013 4:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| punky wrote: |
| The command mentioned is just a sample. |
Excellent.
| punky wrote: |
We have configured the flow in a way that whenever an IDOC comes in without payload (data records), an alert mail is sent to me.
So I am analysing the data for last 15 days, to draw out some pattern to find out when this happens.
Approach ahead:
would analyse the patter for occurence of this issue.
would analyse the system for memory and CPU utilisation at SAP end.
Would check teh system logs at SAP end for the time of errors.
Even would ask WMB team to use some stastical and analysis tools (need to check on them) to monitor system resources during the errors.
Please let me know if I someone has faced this issue before and let me know if I can add something to the approach above.
|
And again, no errors on the broker side at the time? and no stray messages on SYSTEM.BROKER queues? |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Mar 28, 2013 9:05 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
I have seen same kind of phenomenon with initially failed IDocs which were reprocessed from SAP. I know that client opened PMR. My advice for you is also to open PMR to get official help.
--
Marko |
|
| Back to top |
|
|
| punky |
| Posted: Wed Apr 24, 2013 12:38 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi Marko,
I have raised a SR and IBM has asked for traces (service and user).
Can you advice me on the cause of this error and the fix delivered by IBM. As the issue is intermittent and the environment is production, so I am unable to get the traces.
So now IBM has asked me to test after using upgrated JCO files.
The current version I am using is 3.0.7 and the latest available in SAP marketplace is 3.0.9
I am a bit doubtful, if changing these JCO files may bring some effect on other flows (interfaces).
Details on Analysis done:
I have observed the volume and error occurence for 3 weeks.
It is observed that the issue occurs on the days when the load is more than the other days (nearly 1.5 times).
But this should not be an issue with Volume as the flow was volume tested with 20K idocs (in UAT environment) and in production the volume is nearly half of it.
Kindly help !!!
Regards,
Punky |
|
| Back to top |
|
|
| Jimmy_S |
| Posted: Thu May 30, 2013 7:24 am Post subject: |
|
|
Newbie
Joined: 30 May 2013
Posts: 1
|
Hi Punky
I'm seeing the exact same issue you describe above at a client site.
Interestingly I see the issue only in the test environment and not in production, even though both environments run the exact same versions of broker and mq, also the JCO libs are the same on both as are the linux machines running the software.
The advantage I have is that as it's test i can use RFC tracing which shows (on level  that the full IDOC message IS being pulled from SAP (I can see the full message in the RFC) yet the message written to the MQ Queue at the end of the adapter flow only contains the IDOC header.
Did you get any further with your investigations ? Any clues on what I could look at next ?
Jimbo |
|
| Back to top |
|
|
|
|
