...
To create a system, do the following:
Call transaction /STTP/COCKPIT
Navigate to Master Data > Systems and then Choose Display/Edit.
Choose Create. A popup is displayed.
In the popup, define a system name and use following parameters:
a. System name (for example MPT)
...
Property | Description | Mandatory? |
ZR_KZ_CORR_FLAG | Sign of a corrected Act (new Act as a correction of the original one)
Default = false | N |
ZR_KZ_CORR_DOC_ID | GUID of the document to which the adjustment is sent | Y - if a sign of a corrected Act (correctionFlag) = true |
ZR_KZ_OPER_TYPE | Operation type:
| Y |
ZR_KZ_REG_DOC_NUM | Registration number of the document to which the adjustment is transmitted | Y - if a sign of a corrected Act (correctionFlag) = true |
ZR_KZ_REG_DOC_DATE | Date of registration of the document to which the adjustment is transferred | Y - if a sign of a corrected Act (correctionFlag) = true |
ZR_KZ_PRM_DOC_NUM | Primary document number | N |
ZR_KZ_PRM_DOC_DATE | The date of the primary document, in the dd.mm.yyyy format | N |
ZR_KZ_SUPPL_ID | IIN/BIN of the sender (supplier) | Y |
ZR_KZ_SUPPL_NAME | Name of sender (supplier) | N |
ZR_KZ_CONS_ID | IIN/BIN of the recipient (buyer) | Y |
ZR_KZ_CONS_NAME | Name of the recipient (buyer) | N |
...
The logic of the sequence check:
Call BADI /K3TKZ/BADI_REP_SEQ_CHECK method BEFORE_CHECK
Check objects MPT status (status found). The MPT status tracked for every SGTIN in the table /K3TKZ/OBJ_STA. The SSCC MPT status determined based on the first found SGTIN in the current hierarchy
Processing status: there is no report with the same objects in status “Send”
Check predecessor: there is no report with the same objects earlier than the current message
Call BADI /K3TKZ/BADI_REP_SEQ_CHECK method AFTER_CHECK
The MPT status could be updated with transaction /K3TKZ/MPT_SN_INFO or program /K3TKZ/OMS_REP (if SGTIN was send to OMS with BR_CRYPTO_COMM event).
...
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 MPT.
Specify relevant industry for reporting (transaction /K3TKZ/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 |
RR_RU_NTF_REV | ZP | 600 |
...
The new True API method not existing in the 3Keys Connector MPT 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-MPT-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
5.1.6. Enhancement spot /K3TKZ/ES_REP
...