Work Order Transmit Failing

[Former Member]

Hi All,

We've installed SAP Work Manager 6.1, on Normal orders i can update change and complete the orders, but as soon as I try and do the same with PM08 orders I get the below error.

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###execute::::FIELDUSER1::after BAPI execute: /SMERP/PM_DOWORKORDER_UPD |

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###checkForErrors::1::message ID::E::IW - 161 |

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###checkForErrors::1::message::E::Order 0000000TEST4 does not exist |

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###checkForErrors::1::V1::0000000TEST4 |

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###throwExceptionToClient::begin |

2015 03 23 13:02:35#+0200#INFO#System.out##anonymous#Agentry SAPWM61 Worker Thread###throwExceptionToClient::com.syclo.sap.component.workorder.steplet.WorkOrderPostSteplet::throwExceptionToClient::49516::WorkOrderPostSteplet - Order 0000000TEST4 does not exist |

All help would be appreciated.

Regards,

CJ

[Former Member]

OK so just an update we tested the scenario by creating a order and padding it with trailing zero's and it worked no the business needs to make a decision if that is the way we will do it going forward.

Thanks for all the help.

Regards,

CJ

[former_member208808]

Hi,

This may be happening because these work orders do not exist on SAP side, but they are present on device.

That's why when you are trying to update them on device and send it to backend its giving this exception.

Try implementing Data state steps for this to delete client side object if it is not available at back end.

Regards,

AK

[Former Member]

Hi AK,

The orders were created on SAP and sync down to the device, I can successfully download the data to the device and when I create an update and try to sync back to SAP then I get the error.

Regards,

CJ

[former_member208808]

Hi CJ,

Just make sure (this workorder 0000000TEST4) or any workrder that you get error for do exist at back end.[Is there anything specific implementation done for PM08 type workorders ?]

Also reset your client and sync again.Update any workorder and transmit (send it to backend).

And let us know about the same.

Regards,

AK

[Former Member]

Hi AK,

The order is definitely on the SAP system as all orders are only created on back-end system and then Mobile app pulls the data from SAP.  I have reset the client, but as soon as I start the Operation and make a change and then try transmit, the transmit fails with the same error.  I have checked with the client and there is nothing specific that was done, the only thing is that PM08 is a alpha numeric order number range.

Regards,

CJ

[resmi_sadasivan2]

Hi CJ,

Hope you could do similar changes in SAP Backend and having no errors. Is there any errors on SLG1 logs?. You could enable the logs in details and see whether any errors are there in logs.

You could also put a break point on work order generic class /SMERP/CL_PM_WORKORDER_DO method update and see where its failing.

Thanks

Resmi

[Former Member]

Hello , can you check you done SAP Agentry Configuration for that order type . can you turn on external debugging and check ? same error are getting in Syclo update and create BAPI's. Thanks & Regards, Kunal Varaiya

[Former Member]

HI Resmi,

After debugging I found the error, in the Bapi the order id automatically gets padded with leading zero's to fill the 12 character space.  Now on a normal numeric order id if I go to se16 to table AUFK and I enter the order id with the leading zero's and I hit the enter button SAP drops the leading zero's but not with the alpha numeric order id it keeps the zero's.  I even executed the search on se16 with the numeric order id leaving the leading zero's and SAP returns the order, but if I do the same with the alpha numeric order id SAP returns nothing, any suggestions?

Regards,

CJ

[former_member208808]

Hi,

AUFNR is defined with character of length 12,

and bapi makes it padded with leading zeros...

CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

EXPORTING

   input  = lv_orderid

IMPORTING

   output = lv_orderid.

so in case of alpha numeric order id, on sap side keep 12 characters id when creating it from there.

On agentry side it will not drop any leading zeros since it is defined as string.

so after you edit/update them it would work correctly.

Regards,

AK