cancel
Showing results for 
Search instead for 
Did you mean: 

Tracking Labor Time in SAP ME 6.1 -- incompatible: stream classdesc exception.

former_member202208
Active Participant
0 Kudos

Hi all,

I am trying Tracking Labor Time example Example: Tracking Labor Time - SAP Manufacturing Execution (SAP ME) - SAP Library

One difference I see between document and ME screen.

Point #10 In Rollup Processing Rules tab page in Labor Rule Maintenance..

Per document -- Idle Factor for Labor Time is User ID

but in screen; its Labor on to Labor Off and Labor on to Labor On.

When i execute ODSLaborRollup.bat i am getting the following error message;

Can anyone tell me what is the issue and how to fix it?

ODSLog:

Fri Jan 24 04:36:10 EST 2014 LTLabor: Started

Fri Jan 24 04:36:12 EST 2014 LTLabor: Labor Rollup AutoClockout

Fri Jan 24 04:36:12 EST 2014 LTLabor: Committing Auto-clockout

Fri Jan 24 04:36:13 EST 2014 LTLabor: Labor Rollup Extraction

Fri Jan 24 04:36:13 EST 2014 LTLabor: Extract inserted 0 records into ODS_TEMP_LABOR_LOG

Fri Jan 24 04:36:13 EST 2014 LTLabor: Extract inserted 2 records into ODS_TEMP_LABOR_LOG

Fri Jan 24 04:36:14 EST 2014 LTLabor: Extract inserted 0 records into ODS_TEMP_LABOR_LOG_MEMBER

Fri Jan 24 04:36:14 EST 2014 LTLabor: Extract inserted 3 records into ODS_TEMP_LABOR_LOG_MEMBER

Fri Jan 24 04:36:14 EST 2014 LTLabor: Extract inserted 0 records into ODS_TEMP_ATTENDANCE_LOG

Fri Jan 24 04:36:14 EST 2014 LTLabor: Labor Rollup Expansion

Fri Jan 24 04:36:14 EST 2014 LTLabor: Exception Occurred.

com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception

  at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:665)

  at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:634)

  at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:160)

  at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)

  at com.sun.proxy.$Proxy6.getPropertiesLaborRule(Unknown Source)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

  at java.lang.reflect.Method.invoke(Method.java:597)

  at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)

  at com.sun.proxy.$Proxy7.getPropertiesLaborRule(Unknown Source)

  at com.sap.me.ods.olap.ODSLaborLogRollupProcess.ODSExpansion(ODSLaborLogRollupProcess.java:391)

  at com.sap.me.ods.LTLabor.main(LTLabor.java:134)

Caused by: java.io.InvalidClassException: com.sap.me.frame.BOHandle; local class incompatible: stream classdesc serialVersionUID = -5275325738858182014, local class serialVersionUID = 3281602716688756754

  at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:560)

  at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1588)

  at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1501)

  at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1737)

  at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1334)

  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:356)

  at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.readArgs(P4DynamicSkeleton.java:459)

  at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:232)

  at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:466)

  at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)

  at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)

  at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)

  at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)

  at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)

  at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

  at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Fri Jan 24 04:36:14 EST 2014 LTLabor: Complete

SAP ME Version:

Base 6.1.2.1 Counter 36

Build ID 155895

Any help would be highly appreaciated..

Br,

Accepted Solutions (1)

Accepted Solutions (1)

former_member182330
Active Contributor
0 Kudos

Also you may want to make sure that version/patch of your Clients libraries in lib folder corresponds to the version of ME.

Br,

KC

former_member202208
Active Participant
0 Kudos

Hi Konstantin,

It was version mis-match issue. Copied the correct files and it worked.

Thanks,

Br,

Shridhar..

Answers (2)

Answers (2)

former_member202208
Active Participant
0 Kudos

Hi,


The ME instance i am working on is not connected to ECC. I am executing the exercise by creating the Shop order in ME.

After the rolled up time is approved by the Supervisor, I don't see the workflow trigger which will send data to ECC.


  • Is this because the Order was not created in ECC and transferred to ME [LOIPRO IDOC]?
  • If so, is there a way to trigger Labor workflow inside ME?


any help would be highly appreciated.


Br,

Shridhar..

sergiy_katerinich
Active Contributor
0 Kudos

Hi,

Recently there has been a number of fixes to labor rollup implemented in 6.1.4. So, I would advise you to try the same on the latest patch of SP04 instead of 6.1.2.1.

Regards,

Sergiy