-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong result from RFC #197
Comments
Error look like coder errors, reported and reproduced with NWRFC SDK 7.50 PL7, on Linux and Darwin: #196 Are you using PL7 and can you try with PL6 ? |
How can I download NWRFC SDK 7.50 PL6 for Windows Server? |
Only the latest NWRFC SDK version is available on Service Portal. Older version is removed as soon the latest one published. You can try with older version only if you downloaded it before and saved a local copy. The root cause is new unicode handling logic in PL7, I am working on patch. |
I did not download it in my local, so I have to wait your work, right? |
Right, no way to reach PL6 files. The new NWRFC SDK version or patch should be installed in test environment first, before deployment in production. If any issues in test env, the older version is available in production. The latest version is fully backwards compatible and only the latest version is supported, that is why past versions not available for download. |
Please try the 2.1.0 release |
Thank you very much Srdjan, no error after pynwrfc 2.1.0 installation. |
You can also use this workaround for the PL7: #213 |
Hi,
Even though SAP table has some records, Python code that reach this table from RFC has different records.
Firstly, headers of SAP table are MATNR and MAKTX, in RFC code outputs can be sometimes MATNR/x01 and MAKTX/x01.
And secondly, in some records a random letter created after long spaces although nothing like this exists.
What can be the reason of this, and how can it be solved?
SAP table:
Python output:
The text was updated successfully, but these errors were encountered: