...
Version | Changes | Effective Date |
1.0 | First approved version 3Keys Uzbekistan Add-On release 3.1 | 01-Apr-2022 |
2.0 | Release RN_2023_03 | 06-Jul-2023 |
| Table of Contents |
|---|
1. About This Guide
...
Rule | Notification |
BR_CRYPTO_COMM | Bus. Rule: Commissioning for Crypto Codes |
BR_CRYPTO_DECOMM | Bus. Rule: Decommissioning for Crypto Codes |
Z3KUZ_OMS_AGGR | Aggregation report to OMS |
Z3KKZ_OMS_AGGR_MPCK | Aggregation report to OMS based on object event in ATTP |
3. Constraints, Assumptions, Prerequisites and Dependencies
...
Maintain Country communication customizing if the transaction Safe storage will be using industry for maintaining OMS ID and OMS token, do the following
Call the transaction /STTP/C_CTY_URL
Create an entry for each industry you need to support as follows:
URL Type: Choose one of the following URL types:
...
Create a system in ATTP if the transaction Safe storage will be using systems for maintaining OMS ID and OMS token, otherwise the system is not needed, do the following:
Call transaction /STTP/COCKPIT
Navigate to
Master Data > Systems and then Choose Display/Edit.
...
To save OMS Identifier do the following:
Call transaction /STTP/RU_SAFESTORAGE.
Select radio button
By Industry.
Select the URL type for which the OMS Identifier needs to be updated.
Select the
Parameter OMSID – OMS Identifier.
...
To save existing client token do the following:
Call transaction /STTP/RU_SAFESTORAGE.
Select radio button
By Industry.
Select the URL type for which the client token needs to be updated.
...
4.5.2 By system
Do the following:
Call transaction /STTP/RU_SAFESTORAGE.
Select radio button
By system.
Select the system name for which the OMS Identifier needs to be updated.
...
To save existing client token do the following:
Call transaction /STTP/RU_SAFESTORAGE.
Select radio button
By system.
Select the system name for which the client token needs to be updated.
...
BR_CRYPTO_COMM for business step commissioning
Z3KUZ_OMS_AGGR can be maintained for aggregation event with action ADD or
Z3KUZ_OMS_AGGR_MPCK can be maintained for object event with action OBSERVE.
BR_CRYPTO_DECOMM for business step Decommissioning
SAP ATTP rule condition is based on BADI /STTP/BADI_RULE_CONDITIONS with filter = rule condition (Rule processing will stop check if result is skip rule)
...
The logic of the sequence check:
Check crypto codes utilization is confirmed
Check predecessor: there is no report with the same objects earlier than the current message without response (or in status Error Acknowledged)
For aggregation messages of SSCC to SSCC, the child SSCCs checked in OMS with online call. Child SSCC must contain at least 1 object
The sequence check can be skipped/ignored by user in the transaction /STTP/COCKPIT with button “User Approval” - “Approve and send”.
...
4.15.2 Response processing
ATTP 3.0
The report /K3TUZ/OMS_RESPONSE (could be planned as background job or run manually via transaction /K3TKZ/OMS_RESPONSE) to check the processing status in Uzbekistan OMS.
ATTP 3.1 and higher
The report /STTP/SNR_CRYPTO_GET_CONF_STAT (could be planned as background job or run manually via transaction /STTP/SNR_CRYPTO_CST) collects send reports with status “Send” and rule type Z3KUZ_OMS_AGGR, receives report status from OMS system and updates data:
...
to check the processing status in Uzbekistan OMS.
The report run results are stored as application log transaction SLG1, Object /STTP/, Sub object SNR, External ID /STTP/SNR_CRYPTO_GET_CONF_STAT