Zero Total Value on PR for Limit Orders in SAP Ariba Guided Buying !

[ATR]

Hello SAP Community,  🙌

We are experiencing an issue in our SAP Ariba Guided Buying system, specifically when raising Limit Orders. Despite filling in the minimum amount, maximum amount, and start and end dates, the total value on the PR (Purchase Requisition) is appearing as zero.

Background of the Issue: 👈

1.System Customisation: Our SAP Ariba solution is highly customised to align with our organisation's requirements.

2.Recent Changes: Guided Sourcing was recently implemented and went live successfully.

3. Specific Impact: The issue seems isolated to Limit Orders only. Other functionalities are working as expected.

Actions Taken: 👈

1. We raised a P2 ticket in Ariba Connect with our internal tech team.

2. The issue was escalated to SAP's Brazil team. However, after 10 days, we are yet to receive a concrete solution.

3. The SAP Ariba team has asked multiple questions regarding system behavior, but we haven’t seen progress towards a resolution.

Request for Assistance: 👈

We would like insights from the SAP Community on:

1. Troubleshooting Guidance: Have you encountered similar issues with Limit Orders? If yes, how was it resolved?

2. Turnaround Workarounds: Are there any temporary fixes or alternative processes we could use to bypass this issue while waiting for a resolution from SAP?

3. Configuration Tips: Could this be related to a missing or incorrect configuration in New guided sourcing, Guided Buying or the integration between Ariba and SAP ECC/R3?

We would appreciate any advice or suggestions from the community to address this issue. 

Note: For reference, screenshots highlighting the issue and the PR behaviour have been attached to provide additional clarity.

Thank you in advance for your support!

SAP Guided Buying for SAP S/4HANA SAP Ariba Procurement, cloud edition SAP Ariba Contracts SAP Help Portal  RISE with SAP 

@Harish_Vatsa  @Abhijit_Shinde @KateMcCusker_ @ajmaradiaga @JorgeAlonso @BijayKumarBarik @aribaconsultant @I508691 @amandalaldin l

[Abhijit_Shinde]

Hello,

Have not seen this before. It could possibly be due to some customization. Try once with different data and different sequence of operations. Also, deactivating customizations and trying once could help to analyze further.

[ATR]

Appreciate your response. We are still waiting for a resolution from Ariba team, Brazil. They are trying to fix the code. Finger crossed!