I deactivated the metadata cache and model cache in the development system.
I tried to compare this snippet with that in ZGWSAMPLE, but still no luck
↧
Re: Disable Conversion Exits in Gateway
↧
Re: $Batch with Odata
Thanks Ashwin for quick reply
i have followed above instructions still iam getting 202 response and errors in response body .
--D9F229F70009A726D195F276271C776B0
Content-Type: application/http
Content-Length: 849
content-transfer-encoding: binary
HTTP/1.1 400 Bad Request
Content-Type: application/xml
Content-Length: 744
dataserviceversion: 1.0
<?xml version="1.0" encoding="utf-8"?>
<error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<code>CX_ST_MATCH_ELEMENT/544FAE4641562346A1372144E7396586</code>
<message xml:lang="en">System expected the element '{http://www.w3.org/2005/Atom}entry'</message>
<innererror>
<transactionid>589603E5B054F11180CB12829B923AF1</transactionid>
<timestamp>20150526120519.9770000</timestamp>
<Error_Resolution>
<SAP_Transaction>Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details</SAP_Transaction>
<SAP_Note>See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)</SAP_Note>
</Error_Resolution>
<errordetails/>
</innererror>
</error>
--D9F229F70009A726D195F276271C776B0--
↧
↧
Re: Disable Conversion Exits in Gateway
I comment out the conversion function directly in the MPC class.
lo_property->set_conversion_exit( 'ALPHA' ). "#EC NOTEXT
then comment out the bind structure as follows.
*lo_entity_type->bind_structure( iv_structure_name = 'BAPI_EPM_BP_HEADER'
* iv_bind_conversions = 'X' ). "#EC NOTEXT
lo_entity_type->bind_structure( iv_structure_name = 'BAPI_EPM_BP_HEADER'
). "#EC NOTEXT
after these two steps , my program worked. so I doubt that my command
model->set_no_conversion( abap_true ).
does not work in my case, but it does work for the ZGWSAMPLE project.
↧
Re: $Batch with Odata
In the payload change the Content-Type as ' application/xml ' and check please.
↧
BAPI_MATPHYSINV_GETITEMS
Hey,
I'm trying to create an Odata Service which displays the Items from via RFC 'BAPI_MATPHYSINV_COUNT' .
But I have a Problem, i just want(can) to use 1 of the export tables. In this case just the ITEMS. So if I try to create Query for it, it shows me 'Mandatory data source parameter HEADERS is not mapped'.
But as soon as I Map a parameter from HEADERS it says 'In Query operation, only one output table can be used', which both makes sense.
I there any workaround for that? what am I doing wrong?
Thanks in advance
↧
↧
Re: BAPI_MATPHYSINV_GETITEMS
May be the function module also expect some input whihc are to be passed by HEADERS. In this case you need to create an entity which will contain properties from both items and header. For some help refer to Detailed step by step procedure for Creating Gateway Service with all the CRUD Operations and testing them in Service Explorer Part1.
If not, a code based approach may be suitable for this case (a guess)
http://scn.sap.com/community/gateway/blog/2013/06/18/to-code-or-not-to-code
↧
Re: Data expose between two non SAP systems using SAP NWGW/NWPAM
Hi Venkatagiri,
SAP Gateway can not be used for connecting to non-SAP systems in native way. If the non-SAP system can expose some RESTful or SOAP web services, Gateway can consume those services and expose as OData service.
Regards,
Ekansh
↧
Gateway Entity and Property Names
Hello Experts,
As per the following URL, it is recommended to name entities and entity properties using Upper Camel Case.
Creating High-Quality OData Services - SAP NetWeaver Gateway Foundation (SAP_GWFND) - SAP Library
UI developers in our team are recommending to use lower camel case names for properties and upper camel case names for entities to enable UI developers to distinguish between properties and entities.
Can you provide your feedback.
Can you please help us find more information on the following:
1. Why does SAP recommend Upper Camel Case to name entities and entity properties?
2. What are the advantages of doing so from a design, implementation as well as integration perspective?
Regards,
Jiten
↧
Re: Resource not found for the segment
Hi Adem,
Could you check the logic written in the gateway and also check if you are trying to call function module(RFC) from gateway system then try to check the RFC is giving correct result or not.
the above is one of the situation to get the error what are facing.
Thanks,
Suresh
↧
↧
Re: BAPI_MATPHYSINV_GETITEMS
Hi Ekansh, I made a mistake ther, I meant BAPI_MATHPHYS_GETITEMS, like in the title.
↧
Re: BAPI_MATPHYSINV_GETITEMS
Hi Chris,
Yes, SEGW tool wouldn't allow you to map two obligatory tables in one query call. You need to take code based implementation approach for this. In the GET_ENTITYSET method of related entity, pass an empty table for HEADERS.
Regards,
Ekansh
↧
Odata creation for standard reports(MB5B)
HI Experts,
Is there any better way to create the odata for critical & complex reports like (MB5B inventory related reports).
Please give me suggestions
↧
Re: Odata creation for standard reports(MB5B)
Hi Hussain,
Please give us more details on what you are trying to create. We would be able to help you better if more details are posted.
Regards
Prabaharan Asokan
↧
↧
Re: Odata creation for standard reports(MB5B)
Hi Prabaharan,
Let assume i have requirement to dispaly the opening stock , closing stock, receipts ,issue
for this we have already report MB5B, is there any posibility to use standard report with out ant performence issue?if yes how?
↧
Re: SAP NetWeaver Gateway Service Send import parameter RFC function
Have u tried searching properly in SCN/Google regarding what you require?????...<text removed by Moderator> below will help you.
1)http://www.****************/Tutorials/ABAP/FunctionModule/page1.htm
2)Let’s code CRUDQ and Function Import operations in OData service!
Regards,
Vishnu
Message was edited by: Jitendra Kansal (Moderator)
↧
Re: BAPI_MATPHYSINV_GETITEMS
I'll try that and give you feedback tomorrow. Thank you
↧
Odata best practices
Hi community.
Do you guys know any good blog or document that would present the best practices when designing Odata services ?
I recall seing something like this a few months ago on SDN, where people were giving feedback and tips regarding Odata design but I can't find it anymore.
I understand the technical principles of Odata, but I am more interested in design questions such as : is it better to develop specific functions for a use case, or use the CRUD operations of the entities meaning that you then have more calls to make etc.
Thanks.
Regards,
Helder
↧
↧
Re: Odata best practices
↧
Re: Odata best practices
I tried pointing some of them here in this blog in the context of UI5 development.
SAPUI5 – Best practises- Do’s & don’t do’s
Sree
↧
Re: Gateway Entity and Property Names
Jiten,
"Naming Conventions" are just conventions as the name suggests. Their aim is better readability and usability by consumers. Beyond that, there will not be any specific reasons. Functionality/Performance will not be affected by naming conventions.
Within OData service, I do not find a specific use case to differentiate between an Entity and a Property. They are easily distinguishable if you know OData URL conventions. URI Conventions (OData Version 2.0) &middot; OData - the Best Way to REST
But again, Frontend developers are actual consumers of your OData service. If they have a preference, there is nothing wrong in following it.
Thanks
Krishna
↧