search

SAP / apibusinesshub-integration-recipes

Accelerate integration projects using SAP Cloud Platform Integration with crowdsourced best practices, curated by experts, designed for developers.
Apache License 2.0
113 stars 84 forks source link

Issue withSAP Ariba Integration with Third-Party for Analytical Reporting #106

Open venkatakishoremaguluri opened 2 months ago

venkatakishoremaguluri commented 2 months ago

Describe the bug Hi - We have configured the iflow "Analytical Reporting - Template Name - Async Fetch and Reporting" for template as per the config guide.

When we deploy it, iflow is always going through route highlighted in attached ScreenShot-1. This is due to properties "AdhocJob" & "ScheduledJob" created in "Initialization" step always returning as blank. These properties created in "Initialization" step as Global Variables.

Question:

  1. How and which process/iflow creates these global variables ?
  2. Do we have to run any other iflow that creates these global variables ?

Please correct me if my understands of this iflow is wrong.

Regards, Kishore

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Screenshots Attached ScreenShot-1

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

venkatakishoremaguluri commented 2 months ago

Hi All - Any update ?

bertrandhenkel commented 3 weeks ago

Hi,

thank you very much for your request: Please find below response

  1. How and which process/iflow creates these global variables ? iFlow – ‘Analytical Reporting - Template Name - Async Fetch and Reporting’ creates the local variables (not global). These also get cleared off post-report generation refer to SubFlow - Post Execution Clearance iFlows should be copied per template.

  2. Do we have to run any other iflow that creates these global variables? These are local variables and not global hence other iFlows cannot be updated. Note: iFlow ‘Analytical Reporting - Template Name - Async Fetch and Reporting’ orchestrates calls with the other iFlows via PD calls for report generation

I hope this helps. BR Bertrand