Document History
...
Participant tax code fields could be filled with value from source or destination fields of the EPCIS event or business transaction in the transaction /K3TKZ/EDO_ATTR_MAP .
The following location data source is supported:
...
Maintain additional parameters in the transaction /K3TKZ/EDO_CONF under “Rule Configuration” if required skip specific rules using SAP ATTP rule conditions or class-based rule conditions
Field | Description, Values |
Scenario | Free text used to describe the scenario and group multiple rules to be triggered for the same event |
Rule processing sequence | Sequence of rule triggering for the same Scenario |
Rule Condition Cust | Rule condition |
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 sequence check can be skipped/ignored by user in the transaction /K3TKZ/EDO_MONITOR with button Approval
...
Configuration ID determination
The Configuration ID represents the user / certificate for login to the EDO system and electronic signature of the message in the connector Java part configuration file.
...
Maintain Configuration ID in the transaction /K3TKZ/EDO_CONF under “Configuration ID”
Field | Description, Values |
Configuration ID | Free text used to describe the Configuration ID |
Config description | Description |
Delay Response | Delay in seconds before first response for notification |
Max error | Maximum error counter before set notification status “No response” |
User Apprvl | Wait explicit user approval (optional) |
Maintain Participant Tax code in the transaction /K3TKZ/EDO_CONF under “Participant Tax code”
Field | Description, Values |
Participant tax code | Participant Tax code from notification |
Configuration ID | Free text used to describe the Configuration ID |
EDO SSO UUID | GUID from EDO system (obsolete after Nov 2023) |
Background jobs for report processing
...
The report run results are stored as application log transaction SLG1, Object /STTP/, Sub object REP, External ID /K3TKZ/EDO_OMS_REPORT
...
Enhancements of the Solution
The 3Keys Kazakhstan EDO connector EDO solution is designed as to be possibly enhance based on customizing and code enhancements. Code enhancements are realized through BAdI implementations.
...
Enhancing rule determination
3Keys rule configuration includes a possibility to further refine the selection criteria for a rule to be executed. This can be accomplished by using one of the following options:
...
Maintain rule type in the transaction /K3TKZ/EDO_CUST under “Rule Type”
Field | Description, Values |
Rule Type | Rule type Example Z3KKZ_EDO |
Class name | Customer class name to redefine logic |
Description | Text description |
Implementing a BADI /STTP/BADI_RULE_CONDITIONS with filter = rule condition
Implementing 3Keys rule condition class containing interface /K3TKZ/IF_EDO_3K_RULE_COND. Custom logic needs to be created at method /K3TKZ/IF_EDO_3K_RULE_COND~EXECUTE.
Maintain rule condition in the transaction /K3TKZ/EDO_CUST under “Rule Condition”
Field | Description, Values |
Customer Condition for Rules | Rule condition unique name |
Class name | Customer class name |
...
Change report content
The report JSON generated by ATTP standard may not fit to the business requirements. To change Following options for the report JSON the following options changing are available:
...
Create custom mapping logic
To compose report data, it is possible to use own logic by creating new rule type with own rule type execution class by implementing interface /K3TKZ/IF_EDO_3K_RULE_MAPPING (method EXECUTE).
...
To assign custom execution class use transaction /K3TKZ/EDO_CUST, node “Mapping Attributes”, column “Mapper Class”.
...
Change existing mapping logic
To compose report data it is possible to change existing rule type logic by using mapping class redefinition. It is necessary to create own class as child class of /K3TKZ/CL_EDO_0011_MAPPER Collect notification data (or copy of this class) and assign this new class to relevant rule type via transaction /K3TKZ/EDO_CUST, node “Mapping Attributes”, column “Mapper class”.
...
Change check logic after mapping
Badi /K3TKZ/BADI_EDO_CHG_AFTER_CHK shall be implemented for the rule type and own processing logic needs to be implemented.
...
Change report after mapping
Badi /K3TKZ/BADI_EDO_CHG_AFTER_MAP shall be implemented for the rule type and own processing logic needs to be implemented.
...
New custom EDO report type
The new EDO reporting type not existing in the 3Keys Kazakhstan Connector EDO can be created with following steps:
Create new rule type via transaction /STTP/CUST_RULE_TYPE - Define Rule types
Create new notification type via transaction /STTP/REP_NOTIF_TYPE - Define Reporting Notification Types
Create ABAP structures for AIF (use structure /K3TKZ/S_EDO_IMPNRES_AIF as example)
Create AIF customizing via transaction /AIF/CUST (Namespace /STTC3):
...
Define interface
...
Specify interface engine
...
Define structure mapping
Create customizing for mapping report content via transaction /K3TKZ/EDO_CUST (“Mapping attributes” node)
Add logic to extract report data implementing BADI /K3TKZ/BADI_EDO_PARSE
Create customizing for new rule via transaction /STTP/CUST_RULES (3Keys General rule)
Create customizing for new rule via transaction /K3TKZ/EDO_CONF (“Rule configuration” node)
Create logic to parse data by implementing Badi /K3TKZ/BADI_EDO_PARSE
...
New industry
The new industry not supported by SAP ATTP standard can be created with following steps:
Create fixed value append for domain /STTP/D_INDUSTRY (for example ZP – Perfume). Skip this step if industry is supported by 3Keys Kazakhstan Connector for EDO.
Specify relevant industry for reporting (transaction /K3TKZ/EDO_CUST, node “Relevant Industry”)
Add new REST path for created industry (transaction SM30 view /STTP/V_RSRVPATH)
Add general customizing parameter RR_RU_NTF_REV for industry using transaction /STTP/CUSTGEN
Customizing Parameter Key | Customizing Parameter Option | Value |
Z3KKZ_EDO_NTF_REV | ZP | 600 |
...
Create new True API function
The new True API method not existing in the 3Keys Connector EDO can be created with following steps
If base class for API processing does not exist create child class of /K3TKZ/CL_TRUE_API_REQ as custom class ZCL_TRUE_API_REQ
Create method GET_INSTANCE_ATT as copy of GET_INSTANCE at custom class ZCL_TRUE_API_REQ
Create new constant for rest operation (use constant /K3TKZ/CL_REST_CONST=>GCS_REST_OPERATION-NOTIFICATION-EDO-GET_CISES_INFO as example)
Add new REST path for created REST operation (transaction SM30 view /STTP/V_RSRVPATH)
Create processor class (use class /K3TKZ/CL_TRUE_API_CISES_INFO as example), for example ZCL_TRUE_API_CISES_INFO2
Add processor (class ZCL_TRUE_API_CISES_INFO2) instance creation logic into method GET_INSTANCE_ATT (based on rest operation) of base class ZCL_TRUE_API_REQ
Implement new created API processing class ZCL_TRUE_API_REQ call into custom code
...
Enhancement spot /K3TKZ/ES_EDO
Badi | Description |
/K3TKZ/BADI_EDO_PARSE | Parse EDO report data Additional processing logic to parse notification data into report monitor entry on notification creation |
/K3TKZ/BADI_EDO_RESPONSE | Get Response from EDO Additional processing logic to change report monitor entry after report response receiving |
/K3TKZ/BADI_EDO_SEQ_CHECK | Sequence check on EDO Interaction Redefine default sequence check logic with own logic |
/K3TKZ/BADI_EDO_CHG_AFTER_CHK | EDO: Change Data After Check Redefine check result on notification creation with own logic |
/K3TKZ/BADI_EDO_CHG_AFTER_MAP | EDO: Change Data After Mapping Redefine field mapping on notification creation with own logic |
...
Enhancement for navigation to ATTP cockpit
Add general customizing parameter /K3TKZ/COCKPIT_NAVIG (usage scope Customizing) to enable navigation to ATTP Cockpit from transaction /K3TKZ/EDO_MONITOR using transaction /STTP/CUSTGEN
Component | Customizing Parameter Key | Customizing Parameter Option | Value |
REP | /K3TKZ/COCKPIT_NAVIG |
| X |