HTTP request failed error in create preliminary billing document app
BlueskyAccepted Solutions (0)
Answers (1)
Good day @Michael_Pavlik_62
Thank you for your question
The error you mentioned is not enough on its own to identity the root cause. You can use the app to create preliminary billing documents from billing due list items such as sales orders, deliveries, and billing document requests.
See the following reference for more details.
I would also not conclude that the error occurs simply because you are in the configuration system. In a 3-system landscape, the configuration system is a separate client and has its own master and transactional data. However, the test system is the environment you can use to check the configuration before it goes to production.
See the following reference for more details.
Here is a quick guide:
- Open Create Preliminary Documents and filter for only one known billing due document.
- Select the item and choose Create Preliminary Billing Documents.
If “HTTP request failed” appears, the next useful step is to try the same creation through Schedule Creation of Preliminary Billing Documents. You can use it to schedule the creation of preliminary billing documents. Once the job finishes, open Display Billings Logs and inspect the corresponding run.
See the following reference for more insights.
This check is important because “HTTP request failed” may be the only message shown at the UI level, while the underlying billing process may have a more specific business or configuration error. See KBA 3721814 for more information.
If the scheduled job log provides a specific billing error, you can correct the related configuration or source document issue and then retest. If both the interactive creation and scheduled job fail without meaningful application log, raise an incident.
Let me know if you have any further questions.
Best regards
Chris
| User | Count |
|---|---|
| 13 | |
| 12 | |
| 7 | |
| 6 | |
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.