Timespan for data is 1 year on Analytical, Procurement, and Sourcing Reporting.For example: The number of transactions posted within a certain time period may not exceed a certain maximum. I will discuss more on this at the Real life example section.īefore continuing with the Reporting API structure, I need to mention that there are limitations imposed on Reporting APIs: Upon completion, client application downloads the results one file at a time. Result data output is in ZIP files, recommended for a larger subset of data.Ĭlient application submit a job request to a queue and periodically polls the status of the job.
Request for data is submitted via scheduling a reporting job. Client application submit a request and wait for the response Instant result, data is batched and paginated with PageToken, recommended for a very small subset of data. While this post is focused on Analytical Reporting API, the general structure of SAP Ariba Reporting API is the same for all 3 branches of Reporting: Analytical Reporting API, Operational Reporting API for Procurement, and Operational Reporting API for Sourcing. Part 2: SAP Ariba Reporting API Structure I will discuss the typical use case of the API along with Q&A, FAQ, and Tips. Best practice: SAP Ariba Analytical Reporting API.I will cover the Synchronous and Asynchronous Method of data extraction, getting Metadata, using OOTB and custom ViewTemplates, Filtering data, using available Parameters, and reading the Rate limit. I will briefly cover the Reporting Dimension(s) and Fact(s) classes as Database object, Hierarchies, References, and ASM Data load. SAP Ariba Analytical Reporting Data Model.Understanding the basic data model of Analytical reporting database, Reporting API structures and its limitation will ensure a smooth project implementation of data extraction utilizing this API.īelow are the summary for each of the part: In this post, I will be covering the second part of the three part series on SAP Ariba Analytical Reporting API.
0 kommentar(er)
