Error while triggering IDoc

[former_member246543]

Hi Experts,

I was trying to tigger the Idoc MATMAS and LOIBOM from ECC using RFC CLOI_DOWNLOAD_TRIGGER_MDAT.

But the following is the error which i am getting

Unable to make RFC call Exception: [Hashtabelle mit Material/Werkskombinationen]

I am passing the following request xml to it. Earlier using the same request parameter i was able to trigger the Idocs successfully.

The request xml is as follows.

<CLOI_DOWNLOAD_TRIGGER_MDAT>

<INPUT>

<BOM_EXPLODE>'0'</BOM_EXPLODE>

<BOM_EXPL_STOP>'0'</BOM_EXPL_STOP>

<BOM_PRODVERS>'0'</BOM_PRODVERS>

<DATE_FR>1999-12-31</DATE_FR>

<DATE_TO>9999-01-01</DATE_TO>

<LOT_FR>0</LOT_FR>

<LOT_TO>0</LOT_TO>

<MAT_KUP>'0'</MAT_KUP>

<MODEL> </MODEL>

<MODEL_TYPE> </MODEL_TYPE>

<MOD_BOM>2</MOD_BOM>

<MOD_CLS>'0'</MOD_CLS>

<MOD_EQU>'0'</MOD_EQU>

<MOD_HIR>'0'</MOD_HIR>

<MOD_KAL>'0'</MOD_KAL>

<MOD_MAT>2</MOD_MAT>

<MOD_NET>'0'</MOD_NET>

<MOD_PGR>'0'</MOD_PGR>

<MOD_ROU>'0'</MOD_ROU>

<MOD_WRK>'0'</MOD_WRK>

<OPT_SYS>XMII</OPT_SYS>

<PLANT_CHANGE>'0'</PLANT_CHANGE>

<PROCESS_DARK> </PROCESS_DARK>

<PSIZE>20</PSIZE>

<RFCGR> </RFCGR>

<ROU_SEL_RES> </ROU_SEL_RES>

<SEND_ONLY_CHANGES> </SEND_ONLY_CHANGES>

<SND_BOM>1</SND_BOM>

<SND_CLS>'0'</SND_CLS>

<SND_EQU>'0'</SND_EQU>

<SND_HIR>'0'</SND_HIR>

<SND_KAL>'0'</SND_KAL>

<SND_MAT>1</SND_MAT>

<SND_NET>'0'</SND_NET>

<SND_PGR>'0'</SND_PGR>

<SND_ROU>'0'</SND_ROU>

<SND_WRK>'0'</SND_WRK>

</INPUT>

<TABLES>

<ARBPL_WC>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</ARBPL_WC>

<CLASS>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</CLASS>

<CLASSTYP>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</CLASSTYP>

<EQU_KEY>

<item>

<MATNR/>

<WERKS/>

</item>

</EQU_KEY>

<HIER_HI>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</HIER_HI>

<IDENT>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</IDENT>

<JAHR>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</JAHR>

<KEY_MAT_STD>

<item>

<MATNR>SEPCOAL</MATNR>

<WERKS>APSL</WERKS>

<BOMLEV>100</BOMLEV>

</item>

</KEY_MAT_STD>

<KEY_PGR>

<item>

<MATNR/>

<WERKS/>

<BOMLEV/>

</item>

</KEY_PGR>

<KEY_ROU>

<item>

<MATNR/>

<WERKS/>

<BOMLEV/>

</item>

</KEY_ROU>

<KEY_TMX>

<item>

<MANDT/>

<WERKS/>

<MATRIX_ID/>

</item>

</KEY_TMX>

<MATNR_BO>

<item>

<SIGN>I</SIGN>

<OPTION>EQ</OPTION>

<LOW>SEPCOAL</LOW>

<HIGH/>

</item>

</MATNR_BO>

<NETW_NW>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</NETW_NW>

<WERKS_BO>

<item>

<SIGN>I</SIGN>

<OPTION>EQ</OPTION>

<LOW>APSL</LOW>

<HIGH/>

</item>

</WERKS_BO>

<WERKS_HI>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</WERKS_HI>

<WERKS_MA>

<item>

<SIGN>I</SIGN>

<OPTION>EQ</OPTION>

<LOW>APSL</LOW>

<HIGH/>

</item>

</WERKS_MA>

<WERKS_NW>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</WERKS_NW>

<WERKS_WC>

<item>

<SIGN/>

<OPTION/>

<LOW/>

<HIGH/>

</item>

</WERKS_WC>

</TABLES>

</CLOI_DOWNLOAD_TRIGGER_MDAT>

I would like to know what does this error means and its possible solution.

Thanks in advance,

Sanjeev Sharma

[Former Member · Accepted solution]

Sanjeev,

Check where IDOC configuration is fine at ECC & SAP MII.

Go through the link

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a02bc706-15f2-2c10-1aab-a1927ada11f0

Thanks

Rajesh.S

[former_member246543 · Accepted solution]

Hi Rajesh,

First of all thanks for your quick reply,

I have already checked its configuration and when I try triggering an Idoc from ECC I am able to receive it successfully in MII. and I can see it in message monitor.

Thanks ,

Sanjeev

[agentry_src · Accepted solution]

Hi Sanjeev,

The error message, although German, indicates that your combination of Plant (WERKS) and Material is not valid. You may want to research that in the ECC system before rerunning your test.

And if you go to the project downloads for MII and click on: [Download 12.x Templates|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/90537bfe-fd6b-2910-fda3-b04f1177c51e], there is folder for IDOC, which contains transactions used in MII for remote triggering of that RFC. Look it over for data formatting and good practices for executing the POIT and POIM functions remotely.

Also try changing the dates from 2011-12-31 to 20111231. If you enter the dates from POIM, they will automatically reformat the dates to the internal format. That does not happen with using the RFC remotely. So you may be experiencing an error due to the date format.

Good luck,

Mike

Edited by: Michael Appleby on Aug 30, 2011 5:44 PM

[former_member246543 · Accepted solution]

Hi Mike,

In the SAP JCo Function action block I changed the RFC Type from "Best Efffort" to "Exactly Once" and it removed the error, but zero IDocs were triggerd.Now I am working on the possible combination of material and plant. but we were able send the IDocs from ECC to MII with this same combination. I have reffered the sample project for IDocs and I am giving the dates as mentioned in it.

Thanks

Sanjeev Sharma

[agentry_src · Accepted solution]

Hi Sanjeev,

One other thing occurs to me which would account for the error message despite being able to send directly from POIM. If your material is a non-alphabetic and you do not put in the leading zeroes, it will probably not find the material. As an example:

you enter 50000782 in POIM, what really gets submitted is 000000000050000782. There are some functions built into most ECC pages which automatically prepend the zeroes, or in the case of dates, remove the delimiters between the days, months and years. Even SE37 and BAPI do the automatic formatting. But very few RFC/BAPI functions do the same when executed externally.

So try adding the leading zeroes to the material number (and modify your dates) and execute your transaction again. Let us know how it does.

Regards,

Mike

Went back and looked at your xml and saw that the material number is alphabetic, so the comment about prepending zeroes does not apply, but try it with the date modification.

Edited by: Michael Appleby on Aug 31, 2011 1:34 PM

[former_member246543 · Accepted solution]

Hi Mike,

I tried changing the date format as you suggested. but still no IDoc is getting triggerd from ECC.

In the Log Viewer I found the following errors.

Error while confirming TID 
[EXCEPTION]
 com.sap.mw.jco.JCO$Exception: (121) JCO_ERROR_NULL_HANDLE: Invalid rfc_handle = NULL encountered 
Category: com.sap.xmii.storage.connections.JCOCallHandler 
Location: com.sap.xmii.storage.connections.JCOCallHandler 

ERROR:  
[EXCEPTION]
 com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Exception condition "USER_AUTHORIZATION_FAILED" raised.
Category: com.sap.xmii.storage.connections.JCOCallHandler 
Location: com.sap.xmii.storage.connections.JCOCallHandler 

Please suggest what this error means.

Thanks,

Sanjeev

[agentry_src · Accepted solution]

Please go back and check the spelling of the RFC. You may have a typo causing an invalid rfc handle error. And it looks like your user permissions do not include executing RFCs remotely. Check with your SAP Basis or Security person regarding the following (my thanks to Eoin Donnelly):

Review note 16642. The following authorisation objects are required for

ALE users.

S_IDOCCTRL - General access to IDoc functions

S_IDOCDEFT - Access to IDoc development

S_IDOCMONI - Access to IDoc monitoring

S_IDOCPART - Access to partner profile (IDoc)

S_IDOCPORT - Access to port definition (IDoc)

and I would also suggest trying this, but it is more applicable to META DATA UNAVAILABLE errors:

The function IDOCTYPE_READ_COMPLETE can also be called directly via a

JCO/JRA call from the MII Workbench to help identify a number of causes

for errors.

Good luck,

Mike

Edited by: Michael Appleby on Sep 7, 2011 3:10 PM

[former_member193328 · Accepted solution]

Check whether the connection and credential alias (or user passwords) configured in your action are correct or not. This seems to be the issue by looking at the log.

[former_member193328 · Accepted solution]

Exactly Once means Asynchronous tRFC call. This means that no error message will be received in MII but they may still be there in ERP. You can check ERP logs for the errors. Also try to execute the RFC in ERP with the same parameters that you try in MII. If this works you should be ok except for certain leading zero cases which Mike Appelby mentioned.

[former_member246543 · Accepted solution]

Hi Partha,

The problem is resolved now. Actually the problem was with the authorization of JCo credentials which I was using. Anyway thanks for your suggestion it is always helpfull.

Regards,

Sanjeev