BAD REQUEST - Sorry, a technical error occurred. Please try again later.

[roblespm]

Hi,

I have the Following error when I try to access Fiori App Create Billing Document. Could you please help me ?

Sorry, a technical error occurred. Please try again later.

\{
	"requestUri": "/sap/opu/odata/sap/SD_CUSTOMER_INVOICES_CREATE/$metadata?sap-client=100&sap-documentation=heading&sap-language=EN&sap-context-token=20200916144355",
	"statusCode": 400,
	"statusText": "Bad Request",
	"headers": [],
	"body": "<code>/IWFND/CM_MGW/391

Context token '20200916144355' is in the future476DDC932CBC4FC9A0D215A30180CCB720200916131951.6640640For backend administrators: use ADT feed reader \"SAP Gateway Error Log\" or run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more detailsSee SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)" }

[lucian_a_patrutu]

Hi,

I also faced similar issue and found a fix for when it occurs.

Run report /UI5/UPD_ODATA_METADATA_CACHE with 0 hrs. It will reset the validity of the context tokens. This is based on resolution given by SAP in note https://me.sap.com/notes/0003189255

Regards,

Lucian

[TammyPowlas]

Hi - please see the troubleshooting guide attached to SAP Note https://launchpad.support.sap.com/#/notes/1797736

It states:

"Client Error 4xx The 4xx class of status code is intended for cases in which the client seems to have erred. •

400 Bad Request o The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications. o

Examples: ▪ GET: Resource not found • If this error occurs, the request has been sent with an invalid URI. Check the Syntax of the URI. ▪

POST: Duplicate resource • If this error occurs, the desired key does already exist in the database. You cannot implement different data with the same key." source: SAP

You may want to ask your Developer/Basis person

[roblespm]

Hi Tammy,

Thank you for your reply. I'm already checking with a basis team. The sap note 1797736 it's generic troubleshooting guide, it doesn't help to solve the issue. We had this problem after testing some custom fields, after custom fields was disabled, the error still coming so it seems that we need to regenerate something but we cannot find how or what. We opened a sap note to find a solution for that. I'll post if we found a solution.