Exception on billing address and generic error message on checkout

[valeriocicchiel]

Hello community,

we are using WCEM 2.0 with a SAP ECC backend. When a user click Checkout the application throws this exception and a generic error message is displayed on the browser:

com.sap.wec.tc.core.runtime.jsf.binding.BindingModelException: Cannot call method com.sap.wec.app.ecom.module.checkout.ui.handler.CheckoutViewHandlerImpl.atBuildTime caused by java.lang.reflect.InvocationTargetException.

...

Caused by: java.lang.NullPointerException: while trying to invoke the method com.sap.wec.app.common.module.businesspartner.businessobject.interf.Address.isValid() of an object returned from com.sap.wec.app.common.module.transaction.businessobject.interf.PartnerBase.getAddress()

    at com.sap.wec.app.ecom.module.checkout.ui.stepelements.validator.BillingAddressValidator.validateBO(BillingAddressValidator.java:36)

The application was running fine until some days ago, apparently "nothing" has changed on the ECC backend, but we are unable to troubleshooting further the issue.Could anyone help us how to check the validity of billing addresses?

Best regards,

valerio

[former_member193379 · Accepted solution]

Hi Valerio,

It may happens due to some initialization problem.
Pleaes have a look of the below Note.

1848953 - Module initialization can cause cyclic dependencies

Thanks,
Hamendra

[valeriocicchiel · Accepted solution]

Hello Hamendra,

thank you for your help. SAP Note 1848953 is not "strictly" applicable in our case because we have a patch level (pl24) above the recommended (pl22) for component WEC and WEC-FRW. Furthermore, until some days ago the problem was not present.

Regards,

Valerio

[former_member193379 · Accepted solution]

Hi Valerio,

The way is left to debug the code.

Please put break point in BillingAddressValidator.java class, it will give you to find right cause of the problem.

Thanks,

Hamendra

[valeriocicchiel · Accepted solution]

Hello community,

our development team find out that some ABAP classes were recently modified on the ECC backend causing the issue on the portal. Unfortunately we have no more informations to share.

Thank everybody you for your help.

Valerio

[former_member193379 · Accepted solution]

Hi Valerio,

If this is the case then first try to execute the FM directly and debug FM itself.

Thanks,

Hamendra

[steffen_mueller3]

Hi Valerio,

as it worked correctly before, have you maintained a validity range for the address? Otherwise, the debugger will tell you what issue occurs.

Best regards,

  Steffen