SAC error "status:500 body:Internal Server Error" on import

[S4_Hana]

Hello,

I have set up an OData connection from SAC to Business ByDesign. I have a Cloud Datasource with thousands of records. I have created a Report in ByD and assigned it to a Work Center.

I first tried to Generate OData Queries directly from the Report in ByD but SAC gave an error when I tried to create the connection with this link.

I then just set up the Odata connection in SAC using the Work Center. I was then able in SAC to select the Report, however, during importing I just get this error "status:500 body:Internal Server Error".

How can I get this data into SAC?

Thanks

[S4_Hana]

debjit.singha

Thank you, these suggestions are very helpful.

Can you direct me to where in ByD I can increase the ByD timeout setting?

Thanks

[DebjitSingha]

In my case BASIS/ Admin team take care of confg changes.

Here is an example for inactive users setting. Though there must be session setting as well, unless it is the same config.

Session Timeout

Hope this help.

[S4_Hana]

Thanks for the example.

In our case the timeout has already been set to the max of 4hrs.

[S4_Hana]

Right now I have added filtered key figures by year to the ByD datasource, then tried to import just those key figures one at a time (one year at a time). Still getting the error.

Next I will try to filter by half year.

[former_member497128]

Dear belinda.lloyd,

Are you still facing issues? if yes then you can first try to see if the extraction is working or not which you can try by following as below:

-> Connection is already created, so create a new model

-> Select only 1 or 2 field for extraction and use filter also (it could be on vehicle make id, vehicle model id) so that there should not be any issue with respect to data volume.

-> check if extraction is happening successfully. If you are able to extract data then it will mean that all the configurations done by you are correct (then you can try the same process with larger set of data, like all desired fields with filters but not for whole year, try to get data for a quarter or half year).

If not then we have to check the configuration part again (in this case, you can raise an incident and someone from our end can check further).

If you have any further concerns, do let us know.

Regards,
Saurav Kumar

[Abd_Am_K]

Hi belinda.lloyd,

I would try to open the service url in a browser window to see if the Metadata JSON shows up. For example if you take the sample northwind service url using: https://services.odata.org/V2/Northwind/Northwind.svc/

you will get the metadata for the service. If this works then the next step would be as debjit.singha mentioned to simplify your query. It can be possible that the Byd system rejects the ODATA query due to missing capabilities.

Thanks,

Amer