Receipts are created in Ariba, however, they are failing to send to the ERP (external system) due to ERP Push Errors. Some of them are negative receipts (reversal receipts) and they are failing as well.

Understanding receipt workflow:

• As soon as a receipt is approved, Ariba will attempt to send it to the ERP (based on the Integration Configuration). If it fails, by default the system will retry to push for a total of 25 times based on Application.Receiving.MaxRetriesToSendPushFailedReceipts parameter. Please refer this KBA for more information.
• The retries are about 6 hours apart and will allow a window of about 6 days to identify and address the ERP side error. If you want the receipts to be repushed more frequently Application.Receiving.EnableProcessPendingReceiptsFrequently parameter can be enabled so that receipts are repushed every 3 hours once.
• In cases where fixing the error takes longer than 25 retries (or any value configured in Application.Receiving.MaxRetriesToSendPushFailedReceipts parameter), then an Case can be logged to request increasing the maximum retries to send receipts. Please note that this parameter change will impact all receipts that are in Awaiting Processing status and the ones in Processing status only if Application.Receiving.EnableProcessPendingReceipts parameter is set to true.

In situations where the error cannot be fixed, we can recommend the below approaches:

Option 1:
Force Process the Receipt on Ariba, using the Force Process button on the Receipt's header. Then create the Receipt manually on ERP. This approach is the recommended one as it's simpler and straightforward.

Option 2:
If manual creation of Receipts is not allowed and conflicts with your business processes, you can try the below.

• Force Process the stuck receipts (the one receiving ERP Push Errors).
  
• Create a new Receipt that will reverse the stuck receipt: if the first receipt has quantity 1, then the reverse receipt should have quantity -1; and vice versa.
• Ensure that the new Receipt gets an ERP Push Error as well (suggestion: marking Delivery Complete or closing the Order for receiving on the ERP, not Ariba, can help).
• After that, the new reversal receipt should also be Force Processed.
• This will leave the Order on Ariba with 2 receipts canceling each other out.
• Now you need to ensure that any new receipt created will successfully flow to the ERP, then create a new Receipt.

Caution: This should be tested first as it will not be applicable if any step is missed, or if there's complex receiving performed on the Order. It is also important to understand the logic behind it and can vary based on the ERP response. For instance, if ERP accepts the negative receipt and posts it instead of sending back error, this approach cannot be followed.

Option 3:
The third approach is to edit the Receipt with ERP Push Error and set the Amount Accepted/Number Accepted as 0 and resubmit. However you should use the Close Order radio button on the Receipt as the system does not allow submitting a Receipt with 0 Qty/Amount unless you are closing the Order. Please note that you can still reopen the PO.

Caution: Do not use this approach if there are any new Receipts posted against the Order. Even if they are in Processed state and exported to ERP, system removes them. This option is also not possible if your site is enabled for Purchase Order line level closure.

Cause of the errors needs to be investigated on the ERP side as ERP is sending back the errors for some specific reason. In the case that the error is identified to be some missing information being sent (not sent in this case) from Ariba, then you will need to provide the information that the ERP is expecting to be on the Receipt.

If the error is caused by the order not being found on the ERP, ensure that the order wasn't Force Ordered or deleted on the ERP after it was sent from Ariba. Future operations aren't supported for forced orders, refer to document Order transmission and failed orders.

• If the site is configured for receipts integration with Ariba Network (AN), please note that Force Processed receipts will still be sent to AN. In this case, Ariba and AN would be in sync but ERP would be out of sync. 
• Force Processed receipts cannot be sent to the ERP again, if a user Force Processes a Receipt accidentally, then one of the first two options needs to be followed.
• For sites configured with File Channel integration, the Receipt will be queued for export as soon as it is approved. So Force Process will not stop it from being exported the first time. It will, however, stop the receipt from being queued the next time and this scenario happens only when it receives an ERP push Error.
• Ariba doesn't support receipt cancellation. You can only do receiving and later reverse it with negative receiving, but not Cancel/Delete/Obsolete an Approved receipt.

To further read about specific documentations about receiving, please refer below:

• Exporting receipt data
• Configuring and managing receiving
• Workflow of a failed receipt export
• Exporting receipts to SAP ERP
• Receipt export errors

SAP Ariba Buying and Invoicing