Skip to Content
1

Service Call error on update 9.2 Invalid Valid Value in BoSvcEpxDocTypes

Oct 24, 2016 at 08:16 PM

120

avatar image

Hi experts!

I have a very strange issue when trying to update through DI API a service call.

to reproduce the issue

- Create a service call

- Create an expense of type AP Invoice on that service call

- Update the service call

- Now when i run the following code through DI API

       Dim oServiceCall As SAPbobsCOM.ServiceCalls = Nothing




            oServiceCall = oCompany.GetBusinessObject(BoObjectTypes.oServiceCalls)


            If oServiceCall.GetByKey(21) Then
                oServiceCall.CustomerRefNo = "Test"
                oServiceCall.Description = "Test 2"
                iERR = oServiceCall.Update


                If iERR <> 0 Then
                    oCompany.GetLastError(iERR, sMsg)
                    Console.Write(sMsg)


                End If
            End If


This error appears

error -1013

Invalid valid value '18' in Enum 'BoSvcEpxDocTypes', the valid values are '13', '15', '16', '67', '14', '17'

I assume this simply means that the AP expense (since new in 9.2) have not yet been coded.

Is there a work around?

Thanks for any help or suggestions.

1servicecall.png (123.1 kB)
2servicecall.png (350.7 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Pedro Magueija Oct 25, 2016 at 05:11 AM
2

Hi Sebastiano,

I've just checked the BoSvcExpDocTypes and indeed those values (for the AP documents) are missing.

The error occurring during the update would be classified as a bug (SAP seems to often forget they have an API to maintain as well) and should be reported to SAP.

Unfortunately, there seems to be no workaround other than doing it via the client.

If you do report it to SAP, could you let us know their reply?

Good luck.

Pedro Magueija

LinkedIn | Twitter | Blog

Share
10 |10000 characters needed characters left characters exceeded
Sebastiano Todaro Oct 31, 2016 at 07:25 PM
1

9.2 PL 04 resolves the problem according to SAP.

Tested in a local environment and it does indeed work.

Thank you

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thanks for sharing Sebastiano :)

Cheers.

Pedro Magueija

LinkedIn | Twitter | Blog

0
Sebastiano Todaro Oct 25, 2016 at 01:12 PM
0

Thank you Pedro,

I am opening a call with SAP and will post the results here.

Have a good day.

Share
10 |10000 characters needed characters left characters exceeded
Lan Zhang Oct 25, 2016 at 05:04 PM
0

Hi All,

I have exactly the same problem. I believe it is a bug in sap b1 di api. Not sure if this issue is brought by our recent upgrade to 9.2 PL 03(32- bit). I have already informed this issue to the company who provide us SAP maintenance, but haven't got any feedback.

Lan

Share
10 |10000 characters needed characters left characters exceeded