I am Bala from India , focusing on MM , WM , EWM , DMS , PP,SD, PM module functional areas . ... View more

The Application Development group is the place to engage with the community on everything from development methodologies and programming tools to career development. ... View more

(Check out the SAP Developer Challenge - APIs blog post for everything you need to know about the challenge to which this task relates!) In this task you'll move from the public Northwind service to a simple version powered by CAP, and explore data with an OData operation and some system query options. Background The OASIS curated Northwind service is great, but it's also sometimes useful to have one's own version. There's an extremely simplified version of the classic Northwind service, called Northbreeze (get it?) at https://developer-challenge.cfapps.eu10.hana.ondemand.com/odata/v4/northbreeze. This Northbreeze service is powered by the SAP Cloud Application Programming Model (CAP) and offers four entity sets: Products Suppliers Categories Summary of sales by years (Well there's technically a fifth, TotalProducts, but that's just a calculation projection on the count of products). The reason for running our own version of Northwind is that we can modify and extend it as we see fit, plus being based on CAP, we can learn about and experiment with CAP's rich support for serving OData APIs. In this task you'll start to become familiar with the data offered. Specifically for this task, you'll need to become familiar with the Products data. To do that, have a look at the Northbreeze service's metadata document at https://developer-challenge.cfapps.eu10.hana.ondemand.com/odata/v4/northbreeze/$metadata. Identify the EntityContainer element that describes the entity sets available, in the form of EntitySet elements, and find the element describing the entity set with the name Products, which should look like this: <EntitySet Name="Products" EntityType="Northbreeze.Products"> <NavigationPropertyBinding Path="Category" Target="Categories"/> <NavigationPropertyBinding Path="Supplier" Target="Suppliers"/> </EntitySet> You can see that this entity set is a collection of Northbreeze.Products entity types. The 'Northbreeze' part is essentially the namespace, generated based on the service name. Follow the trail to the Products entity type, which will be an element outside the EntityContainer element, but still within the Northbreeze-namespaced Schema element. The Products entity type should look like this: <EntityType Name="Products"> <Key> <PropertyRef Name="ProductID"/> </Key> <Property Name="ProductID" Type="Edm.Int32" Nullable="false"/> <Property Name="ProductName" Type="Edm.String"/> <Property Name="QuantityPerUnit" Type="Edm.String"/> <Property Name="UnitPrice" Type="Edm.Decimal" Scale="variable"/> <NavigationProperty Name="Category" Type="Northbreeze.Categories" Partner="Products"> <ReferentialConstraint Property="Category_CategoryID" ReferencedProperty="CategoryID"/> </NavigationProperty> <Property Name="Category_CategoryID" Type="Edm.Int32"/> <NavigationProperty Name="Supplier" Type="Northbreeze.Suppliers" Partner="Products"> <ReferentialConstraint Property="Supplier_SupplierID" ReferencedProperty="SupplierID"/> </NavigationProperty> <Property Name="Supplier_SupplierID" Type="Edm.Int32"/> <Property Name="UnitsInStock" Type="Edm.Int32"/> <Property Name="UnitsOnOrder" Type="Edm.Int32"/> <Property Name="ReorderLevel" Type="Edm.Int32"/> <Property Name="Discontinued" Type="Edm.Boolean"/> </EntityType> Amongst other things, you can see that a product has an ID (ProductID), a name (ProductName), a count of the number of units currently in stock (UnitsInStock) and a boolean that is used to indicate whether or not a product is discontinued (Discontinued). Request the first few products to see data for these and the other properties, via https://developer-challenge.cfapps.eu10.hana.ondemand.com/odata/v4/northbreeze/Products?$top=5. You should see something like this: { "@odata.context": "$metadata#Products", "value": [ { "ProductID": 1, "ProductName": "Chai", "QuantityPerUnit": "10 boxes x 20 bags", "UnitPrice": 18, "Category_CategoryID": 1, "Supplier_SupplierID": 1, "UnitsInStock": 39, "UnitsOnOrder": 0, "ReorderLevel": 10, "Discontinued": false }, { "ProductID": 2, "ProductName": "Chang", "QuantityPerUnit": "24 - 12 oz bottles", "UnitPrice": 19, "Category_CategoryID": 1, "Supplier_SupplierID": 1, "UnitsInStock": 17, "UnitsOnOrder": 40, "ReorderLevel": 25, "Discontinued": false }, { "ProductID": 3, "ProductName": "Aniseed Syrup", "QuantityPerUnit": "12 - 550 ml bottles", "UnitPrice": 10, "Category_CategoryID": 2, "Supplier_SupplierID": 1, "UnitsInStock": 13, "UnitsOnOrder": 70, "ReorderLevel": 25, "Discontinued": false }, { "ProductID": 4, "ProductName": "Chef Anton's Cajun Seasoning", "QuantityPerUnit": "48 - 6 oz jars", "UnitPrice": 22, "Category_CategoryID": 2, "Supplier_SupplierID": 2, "UnitsInStock": 53, "UnitsOnOrder": 0, "ReorderLevel": 0, "Discontinued": false }, { "ProductID": 5, "ProductName": "Chef Anton's Gumbo Mix", "QuantityPerUnit": "36 boxes", "UnitPrice": 21.35, "Category_CategoryID": 2, "Supplier_SupplierID": 2, "UnitsInStock": 0, "UnitsOnOrder": 0, "ReorderLevel": 0, "Discontinued": true } ] } Your task Your task is to calculate the total stock quantity (i.e. the total units in stock) for all current products, i.e. products that are not been marked as discontinued. The result of this calculation should be a number. Once you have calculated the number, which should be an integer, you should hash it and post the hash as a new reply to this discussion thread, as described in Task 0 - Learn to share your task results and in a similar way to how you've done this in the previous task. Hints and tips Like all tasks in this challenge, you are free to approach this one however you see fit. One way would be to request all the products (https://developer-challenge.cfapps.eu10.hana.ondemand.com/odata/v4/northbreeze/Products) and manually sum the values of the relevant UnitsInStock properties. But where's the fun in that? How about requesting the entire products entity set in your favorite language and obtaining result by parsing the response and using that language to make the calculation? You could also use OData's $filter system query option to first reduce the entity set result to only those products that have the value false for the Discontinued property. And what about the $count facility, which in OData V4 is now a system query option as well something you can append to a resource path? This would also be a good opportunity to take your first steps exploring some great new OData V4 features supported by CAP, such as data aggregation. For discussion How did you approach this task? If you used a programming language, which one did you use, and how did you do it? If you used an $apply based data aggregation feature, what was it, and was was your experience using it? ... View more

(Check out the SAP Developer Challenge - APIs blog post for everything you need to know about the challenge to which this task relates!) In this task you'll become acquainted with entity sets in the classic Northwind service. Background You may have heard of, or even interacted with an instance of, the Northwind model and service, originally and properly called "Northwind Traders". It has a classic and well-known set of related entities and is often a first introduction for many to database schemas, OData services and more. It was originally shipped with the Microsoft Access database application. The entities and their relationships are easy to understand and it's partly for this reason that it's so popular. In this task, you will briefly explore the Northwind service offered by OASIS Open, the non-profit standards body, where there's a working group that looks after the Open Data Protocol (OData) standard. There are various services available at the simple landing page at https://services.odata.org and the one we will use is the OData V4 version, which is available directly at this address: https://services.odata.org/V4/Northwind/Northwind.svc/ Your task Your task specifically is to list the entity sets available in this service. They should be presented as a single string, following these rules: the entity set names should be exactly as specified in the service you should keep whatever case the entity set names are written in the entity sets should be listed in alphabetical order they should be comma-separated, with no spaces Here's a short example of what a list should look like: Categories,Customers,Suppliers There are more entity sets than just these three, this is just an example. Once you have constructed the list, you should hash it and post the hash as a new reply to this discussion thread, as described in Task 0 - Learn to share your task results. This means that to get the hash, you would need to make a call to the hash service like this (based again on the above short example), supplying your SAP Community ID in the appropriate header too: https://developer-challenge.cfapps.eu10.hana.ondemand.com/v1/hash(value='Categories,Customers,Suppliers') Hints and tips What is an entity set? It is essentially a collection (a set) of entities. There are two places where an OData service typically details the entity sets on offer. One is the service document, available at the root of the service's base URL. And the other is the metadata document, available at the service's base URL with $metadata appended. Metadata documents contain a wealth of information for an OData service; the entity set details are included, but there's a lot of other information that is included too, information that you must exclude or otherwise ignore. Simpler perhaps would be to take the service document, which has a set of collections (this harks back to the origins of OData, incidentally) which more or less equate to entity sets. If you request the service document (https://services.odata.org/V4/Northwind/Northwind.svc/) in your browser, you get an XML based representation in response. You can parse this XML with any XML library, or command line tool (such as xmlstarlet or xmllint. While the service document's XML structure is much simpler than the metadata document, it's still XML, and it's arguably easier these days to avoid XML altogether when doing ad-hoc parsing activities. With OData V2 services, the service document is only available in an XML representation. It's also available in a JSON representation with OData V4 services. Using a command line HTTP client, for example, to request the service document, we get an entirely different representation. For example, this invocation of curl: curl \ --url "https://services.odata.org/V4/Northwind/Northwind.svc/" returns a JSON representation, that looks like this (redacted for brevity): { "@odata.context": "https://services.odata.org/V4/Northwind/Northwind.svc/$metadata", "value": [ { "name": "Categories", "kind": "EntitySet", "url": "Categories" }, { "name": "CustomerDemographics", "kind": "EntitySet", "url": "CustomerDemographics" }, { "name": "Customers", "kind": "EntitySet", "url": "Customers" }, { "name": "Employees", "kind": "EntitySet", "url": "Employees" }, { "name": "Order_Details", "kind": "EntitySet", "url": "Order_Details" } ] } In case you're interested, the shell pipeline to produce this redacted representation was: curl \ --silent \ --url "https://services.odata.org/V4/Northwind/Northwind.svc/" \ | jq '.value|=.[:5]' Once you have a JSON representation of the service document, you can use your favorite language (JavaScript, TypeScript, Python, ABAP, or perhaps jq) to parse out the entity set names, and form them, in alphabetical order, into the comma-separated list that you need. Of course, if you prefer to parse the XML representation of the service document, then by all means do that. For discussion We get different representations of the service document resource, depending on where we make the request. In the browser, the representation comes back in XML form. Using curl on the command line, the representation is in JSON form. Why do you think that is? ... View more

Hello, where can I find documentation of ECM APIs, e.g. CL_GENSRVC_CMIS_INTEG_API? Thanks, Peter       ... View more

OpenSAP Course “Generative AI at SAP” starting this week! Jump-Start Your Document Processing Use Case with Generative AI https://go3.events.sap.com/sapteched/virtual/2023/reg/flow/sap/sapteched23/catalog/page/catalog/session/1693019887245001sOwr Power the Future of Your Business with Generative AI https://go3.events.sap.com/sapteched/virtual/2023/reg/flow/sap/sapteched23/catalog/page/catalog/session/1693019887022001sy6x Developer Keynote https://go3.events.sap.com/sapteched/virtual/2023/reg/flow/sap/sapteched23/catalog/page/catalog/session/1693942771811001abcI OpenSAP course: Generative AI at SAP https://open.sap.com/courses/genai1/items/4lcxqpnLq196IaQlRRLQKP SAP BTP, ABAP Environment Release 2311 https://blogs.sap.com/2023/11/14/sap-btp-abap-environment-release-2311/ https://blogs.sap.com/2023/11/06/service-consumption-model-2-for-odata-client-proxy/ “Did You Know” shorts Nr. 2 – Deploy a Docker image to Cloud Foundry with the cf CLI Deploy Docker images in the Cloud Foundry environment: https://help.sap.com/docs/btp/sap-business-technology-platform/deploy-docker-images-in-cloud-foundry-environment  SAP Analytics Cloud 2023/Q4 Release What’s New in SAP Analytics Cloud Q4 2023: https://blogs.sap.com/2023/10/31/whats-new-in-sap-analytics-cloud-q4-2023/ SAP Analytics Cloud Highlight: Composite: https://blogs.sap.com/2023/11/13/sap-analytics-cloud-highlight-composite/ Announcing the new SAP Analytics Cloud feature: Widget Add-on: https://blogs.sap.com/2023/11/13/announcing-the-new-sap-analytics-cloud-feature-widget-add-on/ SAP Analytics Cloud: Custom Widget Hands-on Guide: https://blogs.sap.com/2023/11/03/sap-analytics-cloud-custom-widget-hands-on-guide/  The Open Resource Discovery protocol Open Resource Discovery, a Protocol for Decentralized Metadata Discovery, is now Open Source (blog post): https://blogs.sap.com/2023/11/14/open-resource-discovery-a-protocol-for-decentralized-metadata-discovery-is-now-open-source/ Introducing the Open Resource Discovery protocol (video): https://www.youtube.com/watch?v=7Z818CdoZJg New Learning Journey for SAP Fiori Elements and SAPUI5 in SAP Build Code  Developing an SAP Fiori Elements App Based on a CAP OData V4 Service (learning journey): https://learning.sap.com/learning-journey/developing-an-sap-fiori-elements-app-based-on-a-cap-odata-v4-service SAPUI5 Development with SAP Build Code (blog post): https://blogs.sap.com/2023/11/02/sapui5-development-with-sap-build-code/ ===================================================================== CHAPTER TITLES 0:00 Intro 0:10 OpenSAP Course “Generative AI at SAP” starting this week! 1:06 SAP BTP, ABAP Environment Release 2311 2:24 “Did You Know” shorts Nr. 2 – Deploy a Docker image to Cloud Foundry with the cf CLI 3:00 SAP Analytics Cloud 2023/Q4 Release 4:09 The Open Resource Discovery protocol 5:31 New Learning Journey for SAP Fiori Elements and SAPUI5 in SAP Build Code ... View more

There's a new Customer Engagement Initiative (CEI) for you to collaborate with SAP team members on a new service for hosting and serving frontend applications, a service that combines the HTML5 Repo and AppRouter capabilities, to provide a much simpler development, deployment and management experience, and introduce usage reporting and governance features too. If, like me, you've built and deployed HTML5 apps to SAP Business Technology Platform, you'll know that there's some room for simplification and streamlining. Well - this is it!  Get involved by joining the CEI "New service for hosting and serving frontend applications". And hurry - registration for this CEI ends very soon! ... View more

Hello, where can I find documentation on ABAP syntax differences between SAP 4.7 and ABAP for ERP 6? Are there any?   ... View more

If you're at SAP TechEd 2023 in Bengaluru, India you may have seen a little Easter Egg in the form of some Node.js code. If you've seen it and are curious about it, and want to execute it but don't know how, there are plenty of ways you can do it on the Web. You don't need to install Node.js on your machine if you don't want to. It's important to realise that while Node.js is JavaScript, it comes with more libraries and features relating to the runtime context that it provides. Think of it as "JavaScript++". So you can't run the Easter Egg code in, say, the Chrome Developer Tools console, for example. But you can run it on the Web. Here are a few places where this is possible: replit lets you "build software collaboratively with the power of AI, on any device, without spending a second on setup". CodeSandbox "keeps you in flow by giving you cloud development environments that resume in 1 second". RunKit "is a node playground in your browser". And of course, it almost goes without saying that you can run it in a Dev Space in the SAP Business Application Studio. So what are you waiting for? Stare at the code, try and work out what it's doing, what it emits, and if you get stuck, run it in one of these Web-based environments and see where it leads you. And have fun! (Originally published on qmacro.org) ... View more

(Check out the SAP Developer Challenge - APIs blog post for everything you need to know about the challenge to which this task relates!) This month's Developer Challenge consists of a number of tasks. Each task is introduced in a new, separate discussion thread on the SAP Community platform, specifically in the Application Development group. Background In each new discussion created, a new task will be presented. The context will be explained and relevant background information and pointers to helpful resources will be provided. But most importantly for you, the task itself will be described in detail, and that detail will include exactly the result that you need to produce. That result will be in the form of a string, which you will then need to share in a reply to that task's discussion thread. But. Instead of sharing the result in its raw form, you'll first need to hash it with your SAP Community ID. This is for two reasons: First, you can share your result but no-one can copy your answer, as it will be hashed with another value unique to you - your SAP Community ID. This means that you can share your hashed task result value openly but no-one can copy it and use it as their own. Second, it's a good opportunity to interact with a simple API, providing data in the URL path, but also providing your SAP Community ID as a value in a special header in the HTTP request. Hashing data is quite straightforward and there are libraries built into many programming languages to do this. It is not normally necessary to have to use an API call to use a hash function. We are just providing one here to give you some extra API work to do as part of this month's challenge! Hashing your value When you have a value which represents the result of a task, that you need to share, follow this procedure. For this example, let's say that the value is the string my-task-result. Call the hash endpoint to get your hash There's a simple HTTP service at https://developer-challenge.cfapps.eu10.hana.ondemand.com/ that currently provides a single endpoint /v1/hash. Use this endpoint as instructed to receive a hash. You must provide two pieces of information: the value you want to hash (as part of the URL path) your SAP Community ID (in a header) How you specify each of these two values is described on the HTTP service's landing page. Make sure you follow the instructions. If your call is successful, you'll receive a hash in response. The hash mechanism uses SHA256 and a hex digest is what's provided as the hash output, in case your interested. Reply to the task's discussion thread with that hash Once you have the hash, post a reply to the task's discussion thread, with that hash value. DO NOT ADD ANYTHING ELSE TO THAT REPLY. Don't be tempted to add any formatting, either. Include just the hash value, with no other content. This is because we will be automating the checks for correct responses, and if we cannot successfully parse out the hash value from your reply, that value won't be counted. Your task So the very first task of this month's Developer Challenge ... is to make sure you can follow the above process to hash a value (representing any given answer to a future task in this series) and provide it in a reply to the discussion thread. Use the static value this-is-the-year-of-the-api (don't include the line number 1 in there, that's just an artifact of how preformatted text is rendered on this platform) and follow the above process to get a hash for this value and post the hash as a reply to this discussion thread. You can call the hash endpoint any way you like. Note that you can't just call it in your browser, as a basic GET request. In other words, you can't just make a simple HTTP GET request to https://developer-challenge.cfapps.eu10.hana.ondemand.com/v1/hash(value='this-is-the-year-of-the-api') and expect to get a successful hash response. You must provide an extra HTTP header in your request, conveying your SAP Community ID, as described in the landing page. Hints and tips You can make the API call to get a hash for your combination of value and SAP Community ID any way you wish. Your favorite programming language For example, you could use your favorite programming language. There'll be a library that will let you make HTTP requests, add custom headers, and capture the body of the response. The REST Client extension If you're comfortable in VS Code or the SAP Business Application Studio, you can use the REST Client extension (which is built-in to SAP Business Application Studio Dev Spaces). This extension lets you define HTTP requests, and run them. Here's an example of this in action: Using the REST Client extension to make the hash API call Postman You could also use a graphical HTTP client such as Postman. Using Postman to make the hash API call A command line client You can of course use a command line client, arguably the most flexible and powerful approaches. And after all, #TheFutureIsTerminal, right? There are many command line HTTP clients, such as wget, httpie and of course curl, which is used everywhere, even on Mars. Here's an example using curl: curl \ --include \ --header "CommunityID: qmacro" \ --url "https://developer-challenge.cfapps.eu10.hana.ondemand.com/v1/hash(value='this-is-the-year-of-the-api')" The response (which includes the HTTP headers in that response, because we asked for them with the --include option), looks like this: HTTP/2 200 content-type: text/plain; charset=utf-8 date: Sat, 22 Jul 2023 13:53:34 GMT etag: W/"40-LWwbQuJtCsQ3SBBXmdG8hHlJ0EI" x-correlation-id: a718cf85-83a6-4d3a-54df-9791f1cea235 x-powered-by: Express x-vcap-request-id: a718cf85-83a6-4d3a-54df-9791f1cea235 content-length: 64 strict-transport-security: max-age=31536000; includeSubDomains; preload; b8193c6703e9d123e4aa639e43eee631a2f6e3788508b5c6fb3098a3f201607c Sharing your hash in a reply to the discussion thread In each of these examples, the hash received in response is: b8193c6703e9d123e4aa639e43eee631a2f6e3788508b5c6fb3098a3f201607c This is the value that must be posted in a reply to this discussion thread. Just copy-paste it into the body of a new reply. ... View more