Hi all,
We are making a custom WD Java application for update of infotype 22 with portal (Actually this infotype is not mantained with portal).
It's an FPM application and we made it similar to the family one (infotype 21).
We developed it for Spain only, all user settings are set to ES. We are using ERP2005.
We created our custom RFCs function module ZHRXSS_PER_P0022_ES for processing of intotype 0022 as a copy of HRXSS_PER_P0021_ES one, using our custom type ZHCMT_BSP_PA_ES_R0022_TAB defined as a table of lines of type ZHCMT_BSP_PA_ES_R0022.
We have customized the V_T588UICONVCLAS view as SAP notes 936179 and 835625 says:
SNAME = ZHCMT_BSP_PA_ES_R0022
INFTY = 0022
STYPE = MAIN (Main Infotype)
VERSIONID = 04 (Spain)
CLSNAME = ZCL_HRPA_UI_CONVERT_0022_ES
ZCL_HRPA_UI_CONVERT_0022_ES is a copy of CL_HRPA_UI_CONVERT_0022_XX leaving only fields of spanish structure.
In SAP/R3 backend when we execute the method READ of the CL_HRPA_PERNR_INFTY_XSS class we are getting no error, the read is done correctly.
Althought, when we execute the application from the portal just at the start of the application, when FPM executes the read method of our Fc we are getting the "Country/Structure do not match aplication country" error (To be exact, we receive this message in spanish "Pais/Estructura no coincide con pais de aplicacion")
Any idea why this is happening? Are we missing any setup?
The start of the error trace is this:
"País/Estructura no concuerda con país de aplicación:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: País/Estructura no concuerda con país de aplicación
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
at com.sap.xss.per.helpers.MessageHelper.raiseException(MessageHelper.java:43)
at com.sap.home.ess.es.zpafor.fc.FcFormation.readRecord(FcFormation.java:334)
at com.sap.home.ess.es.zpafor.fc.wdp.InternalFcFormation.readRecord(InternalFcFormation.java:589)
at com.sap.home.ess.es.zpafor.fc.FcFormationInterface.readRecord(FcFormationInterface.java:183)
at com.sap.home.ess.es.zpafor.fc.wdp.InternalFcFormationInterface.readRecord(InternalFcFormationInterface.java:197)
at com.sap.home.ess.es.zpafor.fc.wdp.InternalFcFormationInterface$External.readRecord(InternalFcFormationInterface.java:273)
at com.sap.home.ess.es.zpafor.overview.VcFormationOverview.onBeforeOutput(VcFormationOverview.java:258)
at com.sap.home.ess.es.zpafor.overview.wdp.InternalVcFormationOverview.onBeforeOutput(InternalVcFormationOverview.java:234)
at com.sap.home.ess.es.zpafor.overview.VcFormationOverviewInterface.onBeforeOutput(VcFormationOverviewInterface.java:135)
at com.sap.home.ess.es.zpafor.overview.wdp.InternalVcFormationOverviewInterface.onBeforeOutput(InternalVcFormationOverviewInterface.java:132)
at com.sap.home.ess.es.zpafor.overview.wdp.InternalVcFormationOverviewInterface$External.onBeforeOutput(InternalVcFormationOverviewInterface.java:208)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:602)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:568)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
..."
Thanks for your answers, points will be rewarded.
Gabriel.