cancel
Showing results for 
Search instead for 
Did you mean: 

Bapi table error

Former Member
0 Kudos

Hi,

I imported the "Bapi_Delivery_Getlist_Input" while selecting output tables (any out put table in Bapi) it is showing following exception,but there no problem in selecting input parameters

com.sap.dictionary.runtime.DdException: Incorrect amount type (not decimal): Service for units cannot be set up

at com.sap.dictionary.runtime.DdBroker.getUnitService(DdBroker.java:215)

at com.sap.dictionary.runtime.DdBroker.getUnitService(DdBroker.java:233)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getUnitService(DataTypeBroker.java:337)

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.initReferenceAttribute(DataAttributeInfo.java:346)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:738)

Any body could you please help me out,

Thanks,

Balaji

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi All,

I have imported function module "Bapi_Delivery_Getlist" to create an adaptive RFC model in WebDynpro DC. The DC is used for callable object in GP process. This GP process and concerned callable object was tested and working fine on the NetWeaver 7.0 SP 15. The server has recently been updated to SP18. After this upgrade, the callable object has become error prone; when tested gives following error:(No development has happened since long on the DC before and after the upgrade. The JCOs are tested fine too.).

Error Log:

Unable to create web dynpro callable object implementation.
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: Incorrect amount type (no decimal): Unit service cannot be set up
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.initReferenceAttribute(DataAttributeInfo.... [see details]
Detailed error
Unable to create web dynpro callable object implementation.
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: Incorrect amount type (no decimal): Unit service cannot be set up
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.initReferenceAttribute(DataAttributeInfo.java:349)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initStructureType(NodeInfo.java:738)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:239)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)

Please help urgently if you have any clue on this issue. Quite a critical error.

Former Member
0 Kudos

Hi,

Try Reimport the model and restart the J2ee engine.

It might resolve your problem.

Thanks,

Lohi.

monalisa_biswal
Contributor
0 Kudos

check whether your JCO detination is pointing to the same system using which u imported RFC model.

Former Member
0 Kudos

hi balaji,

if you are selecting the output node as well as input node then rename the nodes under the <b>output</b> since context doesn't accept duplicate names. if this is not your issue then just elaborate the error.

Regards,

Gopi

balaji_bodagala5
Participant
0 Kudos

Hi Gopi,

while importing the model it is creating the dictonary there is no issue,

at run time while calling the execute method it is throwing the exception

failed to create the dictionary

Thanks,

Balaji

Former Member
0 Kudos

Hello

Were you able to solve this issue, Even I am getting the same error.

Thanks and Regards

Manoj Kumar

balaji_bodagala5
Participant
0 Kudos

Hi,

still problem is not yet solved,

we have another option we can able to use another RFC

Bdp_Inb_Delivery_GetDetail,this rfc is satisfies my requirement.

Thanks,

Balaji