JCOProxy error trying to retrieve BOM

[Former Member]

I am having a problem with the CSEP_MAT_BOM_READ remote enabled function module that is used to retrieve the Bill of Material. It works in SAP R/3 but returns an error when it is called from xMII.

The input parameters are not show and in their place the following error is show: "JCOProxy error: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified."

Is there some way around this error, or another function module or BAPI that can be used to get the Bill of Material?

Any help would be appreciated.

-Dan

[former_member4529 · Accepted solution]

Hi,

For the RFC input parameters for which you are not passing any value assign <<RemoveXML>> from the link editor.

Thanks,

Dipankar

[Former Member]

Try generating the xml again.

[salvatore_castro]

Daniel,

Please post both your Request XML and Response XML to the forum so that I can see what you're doing. Also try testing out the operation of this RFC in the SAP GUI via transaction code se37.

-Sam

[Former Member]

More details...

SAP ECC 6.0 is connected to xMII 12.0 through JCO. When the request and response documents are generated the following XML is returned:

<?xml version="1.0" encoding="UTF-8"?>
<Rowsets DateCreated="2007-07-12T08:36:49" EndDate="2007-07-12T08:36:49" StartDate="2007-07-12T08:36:49" Version="12.0.0 Build(58)">
<FatalError>JCOProxy error: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified. </FatalError>
</Rowsets>

The RFC works correctly in ECC 6.0 when it is run through SE37.

Do you know of any other BAPI or remote-enabled function module that can be used to retrieve the BOM.

Thanks for your help,

Daniel Pleski

Message was edited by:

Daniel Pleski

[salvatore_castro]

Daniel,

I tried to load this RFC in the xMII 11.5.3 Business Logic Environment and it worked fine. There may be a bug with the v12 build that you have. My suggestion is to enter this into CSS so that it can be properly tracked and corrected.

-Sam

[jcgood25]

Dipankar's suggestion to do a <<Remove XML>> for all of the unused Tables in the Request document is accurate for your 12.0.0 build of xMII. This was a known bug and has been addressed in the 12.0.1 update that just went onto Service Marketplace.

Best Regards,

Jeremy

[Former Member]

Thanks Jeremy and Dipankar. Using <<Remove XML>> will typically solve that error message when it is returned after executing a transaction. However, it appears the XML is malformed when Request/Response documents generated from R/3, even before the transaction has been executed. Another odd twist is that it works on one of our ECC 6.0 systems but not the other (maybe config or ABAP differences on our ECC 6.0 system). A customer message with SAP has been created, and they are investigating why this Function Module not working with xMII. I will post an update when the issue is resolved.

-Daniel Pleski

[jcgood25]

Daniel,

I just tried the BAPI with 12.0.1 and received a valid Request XML document as follows:

<?xml version="1.0" encoding="UTF-8"?>

<CSEP_MAT_BOM_READ><INPUT><ALTERNATIVE/><BOM_USAGE/><CHANGE_NO/><FL_DMU_TMX/><FL_DOC_LINKS/><MATERIAL>*</MATERIAL><PLANT>1100</PLANT><REVISION_LEVEL/><VALID_FROM/><VALID_TO/></INPUT><TABLES><T_DEP_DATA><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><DEP_INTERN/><DEP_EXTERN/><DEP_TYPE/><DEP_TYPE2/><SCE_FLAG/><STATUS/><GROUP/><WHR_TO_USE/><FLDELETE/></item></T_DEP_DATA><T_DEP_DESCR><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><DEP_INTERN/><DEP_EXTERN/><LANGUAGE/><DESCRIPT/><FLDELETE/><LANGUAGE_ISO/></item></T_DEP_DESCR><T_DEP_DOC><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><DEP_INTERN/><DEP_EXTERN/><LANGUAGE/><LINE_NO/><TXT_FORM/><TXT_LINE/><LANGUAGE_ISO/></item></T_DEP_DOC><T_DEP_ORDER><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><DEP_INTERN/><DEP_EXTERN/><DEP_LINENO/></item></T_DEP_ORDER><T_DEP_SOURCE><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><DEP_INTERN/><DEP_EXTERN/><LINE_NO/><LINE/></item></T_DEP_SOURCE><T_DMU_TMX><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><MANDT/><TMXGUID/><LOCOX/><LOCOY/><LOCOZ/><AXIS1X/><AXIS1Y/><AXIS1Z/><AXIS2X/><AXIS2Y/><AXIS2Z/><AXIS3X/><AXIS3Y/><AXIS3Z/><SCALE/></item></T_DMU_TMX><T_DOC_LINK><item><OBJECT_ID/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><MANDT/><DOKAR/><DOKNR/><DOKVR/><DOKTL/><DOKOB/><OBZAE/><OBJKY/><VRKSTAT/><VRKSTAT1/><VOBJ/><VKEY/><VDIR/><VIEWFLAG/><DELFLAG/><LONGTEXT_ID/><CAD_POS/><CM_FIXED/><FLDELETE/></item></T_DOC_LINK><T_STKO><item><BASE_QUAN/><BASE_UNIT/><BOM_STATUS/><ALT_TEXT/><LABORATORY/><DELETE_IND/><BOM_TEXT/><BOM_GROUP/><AUTH_GROUP/><CAD_IND/><ID_GUID/><BOM_NO/><ALE_IND/><VALID_TO/><CHG_NO_TO/><CREATED_ON/><CREATED_BY/><CHANGED_ON/><CHANGED_BY/><VALID_FROM/><CHG_NO/></item></T_STKO><T_STPO><item><ITEM_CATEG/><ITEM_NO/><COMPONENT/><COMP_QTY/><COMP_UNIT/><FIXED_QTY/><ITEM_TEXT1/><ITEM_TEXT2/><SORTSTRING/><REL_COST/><REL_ENGIN/><REL_PMAINT/><REL_PROD/><REL_SALES/><SPARE_PART/><MAT_PROVIS/><BULK_MAT/><REC_ALLOWD/><COMP_SCRAP/><OP_SCRAP/><OP_NET_IND/><DISTR_KEY/><EXPL_TYPE/><SPPROCTYPE/><SUPPLYAREA/><ISSUE_LOC/><LEAD_TIME/><OP_LEAD_TM/><OP_LT_UNIT/><CO_PRODUCT/><DISCON_GRP/><FOLLOW_GRP/><AI_GROUP/><AI_STRATEG/><AI_PRIO/><USAGE_PROB/><REFPOINT/><PM_ASSMBLY/><COST_ELEM/><DELIV_TIME/><GRP_TIME/><MAT_GROUP/><PRICE/><PRICE_UNIT/><CURRENCY/><PURCH_GRP/><PURCH_ORG/><VENDOR/><VSI_NO/><VSI_QTY/><VSI_SIZE1/><VSI_SIZE2/><VSI_SIZE3/><VSI_SZUNIT/><VSI_FORMUL/><DOCUMENT/><DOC_TYPE/><DOC_PART/><DOC_VERS/><CLASS/><CLASS_TYPE/><RES_ITM_CT/><SEL_COND/><REQD_COMP/><MULT_SELEC/><REL_HLCONF/><CAD_IND/><ITM_IDENT/><ITEM_GUID/><VALID_FROM/><CHANGE_NO/><IDENTIFIER/><BOM_NO/><ITEM_NODE/><ITEM_COUNT/><RECURSIVE/><DEP_LINK/><ALE_IND/><VALID_TO/><CHG_NO_TO/><CREATED_ON/><CREATED_BY/><CHANGED_ON/><CHANGED_BY/><BOM_ALT/><FLDELETE/><KTEXT/><MSTAE/><REVISION_LEVEL/></item></T_STPO></TABLES></CSEP_MAT_BOM_READ>

So it would appear that the issue is resolved with the updated version on Service Marketplace.

Best Regards,

Jeremy Good