...
Version | Changes | Effective Date |
1.0 | First approved version 3Keys Uzbekistan OMS Add-On release 20222023_0401 | 01-NovFeb-20222023 |
1. Overview
This document describes changes in the 3Keys Uzbekistan OMS connector ABAP part.
2. Notes
Note | Description | Category |
Transaction New BC Set /K3TUZ/CUST_OMS_RESPONSE is missed | Error | |
New rule type Z3KUZ_OMS_AGGR_MPCK created to create aggregation reporting events based on object event by layers combining SGTINs from one aggregation level to one reporting events. For example, object event contains SSCC1 and SSCC2. SSCC1 has the following hierarchy at SAP ATTP system: SSCC1 - SSCC1_A - SGTIN1_A123 SSCC2 has the following hierarchy at SAP ATTP system: SSCC2 - SSCC2_B - SGTIN2_B456 After rule execution the following reporting events created: Reporting event 1 with aggregations SSCC1_A - SGTIN1_A123, SSCC2_B - SGTIN2_B456 (1st level) Reporting event 2 with aggregations SSCC1 - SSCC1_A, SSCC2 - SSCC2_B (2nd level) | New feature | |
Rule 3_2 Short Text: 3Keys Uzbekistan OMS Add-On 3.2 created. Software Component K3TUZ1 3Keys Uzbekistan OMS Add-On Release changed to 302 | New feature | |
Selection screen input validation added to transaction /K3TUZ/OMS_AGGR_INFO to prevent runtime error after incorrect data input | Error | |
The rule type Z3KUZ_OMS_AGGR_MPCK (implemented with note 2022_04_02) is triggered and created reporting event with rule Z3KUZ_OMS_AGGR instead of correct rule type Z3KUZ_OMS_AGGR_MPCKcreates aggregation report rejected by Uzbekistan OMS system in case object count in one aggregation report is more than 10000. Parameter REP-Z3KUZ_AG_MAXOBJPACK is set at Custgen transaction but new aggregation report is not created after splitting based on object count. In case of large aggregations OMS sequence check rule for aggregation report containing SSCC-SSCC aggregations is interrupted with error message “No memory for processing HTTP, HTTPS, or SMTP queries“. The reason is technical problem in ABAP code. Correction is implemented. | Error |
3. Transport request ATTP 3.0
The transport request A1DK900395 A1DK900422 includes the release notes RN_20222023_04 01 for ATTP 3.0 with following list of implemented notes.
Note | Transport | Prerequisites | Release date | |
20222023_0401_1 | A1DK900343N/A |
| 10-Aug-2022 | |
2022_042023_01_2 | A1DK900349A1DK900408 | A1DK900395 | 0206-SepDec-2022 | |
20222023_0401_3 | A1DK900359A1DK900412 | A1DK900349 A1DK900395 | 1906-SepDec-2022 |
4. Transport request ATTP 3.1
The transport request A2DK900363 A2DK900448 includes the release notes RN_20222023_04 01 for ATTP 3.1 with following list of implemented notes.
Note | Transport | Prerequisites | Release date | ||||||
20222023_0401_1 | N/A |
| |||||||
2023_01_2 | A2DK900390 | A2DK900363 | 06-Dec-2022 | _04_2A2DK900307 | 02-Sep-2022 | 2022_04_3 | A2DK900334 | A2DK900307 | 19-Sep|
2023_01_3 | A2DK900392 | A2DK900363 | 06-Dec-2022 |
5. Transport request ATTP 3.2
The transport request A3DK900077 includes the release notes RN_2023_01 for ATTP 3.2 with following list of implemented notes.
Note | Transport | Prerequisites | Release date |
2023_01_1 | A3DK900022 or SAPK-302COINK3TUZ1 | ATTP 3.2, Uzbekistan OMS Release 2022_04 | 09-Nov-2022 |
2023_01_2 | A3DK900020 or SAPK-302COINK3TUZ1 | ATTP 3.2, Uzbekistan OMS Release 2022_04 | 09-Nov-2022 |
2023_01_3 | A3DK900048 | A3DK900022 or SAPK-302COINK3TUZ1 | 06-Dec-2022 |
View file | ||
---|---|---|
|
View file | ||
---|---|---|
|
View file | ||
---|---|---|
|
...