![]() The support for xbox - remains but the error string is reverted back to local codepage. This is essentially a partial revert of bed5f84. We return the local codepage version of the error string because if it - is output to the user's terminal it will likely be with functions which - expect the local codepage (eg fprintf, failf, infof). Two weeks ago bed5f84 fixed get_winapi_error() to work on xbox, but it - also changed the error string's encoding from local codepage to UTF-8. Reviewed-by: Marc Hörsken + Reported-by: Josh Soref - Closes #6066 - Fixes #6052 + Fixes - tests/server/util.c: fix support for Windows Unicode builds - Detected via #6066 - Closes #6070 +-Daniel Stenberg () - + docs/cmdline: fix grammar and typos - strerror: Revert to local codepage for Windows error string - Change get_winapi_error() to return the error string in the local - codepage instead of UTF-8 encoding. mailmap fixes +- winbuild/MakefileBuild.vc: bump copyright year - mailmap: fixups of some contributors - projects/build-wolfssl.bat: fix the copyright year range -Marc Hoersken () - CI/tests: fix invocation of tests for CMake builds +Jay Satiro () +- docs: mention max-filesize options also apply to MQTT transfers - Update appveyor.yml to set env variable TFLAGS and run tests - Remove curly braces due to CMake error ($ -> $TFLAGS) - Move testdeps build to build step (per review comments) + Also make it clearer that the caveat 'if the file size is unknown it + the option will have no effect' may apply to protocols other than FTP + and HTTP. In my opinion, the validation should be changed because there is as far as I know no excel Date-format available for dd.mm.jjjj. I found no SAP notes or other questions or blogs about this problem.Ĭurrently we change the XML-file: for every date field we change type String to Date. I have already reported this as an incident at SAP but I'm curious if we are the first to encounter this problem. There is no Date (Datum) format of type dd.mm.yyyy in Excel. The reason it is a type String and not Date is because in Excel, the following cell format is being used.Īpperently, this is translated by Excel-XML to type String. We found that during the upload a Validation is performed in method:ĬL_DMC_MD_EXTRACTOR_EXCEL_XML=>VALIDATE_PAYLOAD_DATA_TYPE at location 159-160Īt runtime, value for LV_TYPE is String, not Date. If we look at the XML-file in an XML-editor, we see that the date fields have a type String and not Date. ![]() The Dutch date format is the same as the German format. ![]() When populating the XML in Excel we use the date-format dd.mm.yyyy as described in the Introduction Sheet of the Template. We follow the normal steps: download XML-template, populate using Excel (XML 2003 Excel format), save and then upload in the DMC Fiori App. For every date-type fields we get two error messages:ĬNV_DMC_MD_EXTRACTOR 033 Field "Datum: berekening geldig tot" from sheet "Rekenwaarden" has a wrong data type in line 9ĬNV_DMC_MD_EXTRACTOR 034 Data type Date is expected in field "Datum: berekening geldig vanaf" The issue is that during upload of any DMC-file with date-type fields, we get the same error messages for every date-type field like 'POSTING_DATE', 'VALID_FROM, VALID_TO etc. ![]() We are using the Files/Staging Table scenario. Now we started testing SAP standard and custom migration objects and we are running into problems with the Date format for all migration objects. We are using the DMC and have copied our own migration objects to a new migration project. We are busy with an upgrade from S/4HANA 1809 to 2021.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |