cancel
Showing results for 
Search instead for 
Did you mean: 

config problem with new ISA b2b objects

Former Member
0 Kudos

Hi guys,

I have written below objects and now struggling to configure it for b2b crm 2007 application.

Action Layer: Z_PromiseShipToDateDisplayAction.java

Business Layer: Z_PromiseShipToDatebo.java, Z_PromiseShipToDateValue.java, Z_PromiseShipToDateLineItem.java

EAI Layer: Z_PromiseShipToDate.java, Z_PromiseShipToDateCRM.java

JSP Files: Z_PromiseShipToDateView.jsp

Custom BOM : Z_CustomeBusinessObjectManager

Basically I have added a new hyperlink to the orderstatusdetails page of b2b isa application and as per the required functionality click on it should open a new window showing some details fetched from the backend.

the customer version of backendobject-config.xml and bom-config.xml look like this after my changes

backendobject-config.xml

<backendobject xmlns:isa="com.sap.isa.core.config" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xml="http://www.w3.org/XML/1998/namespace">

<configs>

<!-- customer changes in backendobject-config should be done here by extending/overwriting the base configuration-->

<xi:include href="$/modification/backendobject-config.xml#xpointer(backendobject/configs/*)"/> <config isa:extends="../configs@id='crmdefault'"> <businessObject type="Z_PromiseShipToDate" name="Z_PromiseShipToDate" className="com.mycomp.isa.promiseShipToDateView.backend.crm.Z_PromiseShipToDateCRM" connectionFactoryName="JCO" defaultConnectionName="ISAStateless" /> </config> </configs> </backendobject> bom-config.xml <BusinessObjectManagers xmlns:isa="com.sap.isa.core.config" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xml="http://www.w3.org/XML/1998/namespace"> <!-- customer changes in bom-config should be done here by extending/overwriting the base configuration--> <xi:include href="$/modification/bom-config.xml#xpointer(BusinessObjectManagers/*)"/>

<BusinessObjectManager name="Z_CUSTOM-BOM" className="com.mycomp.isa.customBusinessmanager.Z_CustomBusinessObjectManager"/>

</BusinessObjectManagers>

But still when i click on the newly added link I get the following error message in new window popup

500 Internal Server Error

SAP J2EE Engine/7.00

ISA Framework: java.lang.NullPointerException com.mycomp.isa.promiseShipToDateView.actions.Z_PromiseShipToDateDisplayAction.doPerform(Z_PromiseShipToDateDisplayAction.java:61) com.sap.isa.core.BaseAction.execute(BaseAction.java:211) org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:684) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:401)

Line 61 of action Z_PromiseShipToDateDisplayAction.is

Z_PromiseShipToDateValue z_PromiseShipToDateValue=z_PromiseShipToDatebo.getPromiseShipToDate(orderNo);

which again goes here

public class Z_PromiseShipToDatebo extends BOBase implements BackendAware {

private BackendObjectManager bem;

private Z_PromiseShipToDate backendCustomContrDet;

private static IsaLocation log = IsaLocation.getInstance(Z_PromiseShipToDatebo.class.getName());

public Z_PromiseShipToDatebo()

{

}

public Z_PromiseShipToDateValue getPromiseShipToDate(String orderNo)

{

return getPromiseShipToDateInfoBackend().getPromiseShipToDate(orderNo);

}

private Z_PromiseShipToDate getPromiseShipToDateInfoBackend(){

if (backendCustomContrDet == null)

{

try {

backendCustomContrDet =

(Z_PromiseShipToDate)bem.createBackendBusinessObject("Z_PromiseShipToDate");

} catch (BackendException bex)

{

log.error(bex);

}

}

return backendCustomContrDet;

}

public void setBackendObjectManager(BackendObjectManager bem) {

this.bem = bem;

}

}

*Can you guys please help me with this.Can you please tell me whether this is happening because objects are not registered properly or some other reason.Please help me with is as this has stuck all my work.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

There was problem from crm side...its working now..