...
Consumer proxy | URL suffix |
/K3T/CO_RU_MDLP_API | /mdlp/connector/ru_mdlp_api |
/K3T/CO_RU_MDLP_GET_200 | /mdlp/connector/ru_mdlp_get_200 |
/K3T/CO_RU_MDLP_GET_ORIG_DOC | /mdlp/connector/ru_mdlp_get_orig_doc |
/K3T/CO_RU_MDLP_GET_TOKEN | /mdlp/connector/ru_mdlp_get_token |
/K3T/CO_RU_MDLP_REQ | /mdlp/connector/ru_mdlp_req |
/K3T/CO_RU_GET_OMS_TOKEN | /mdlp/connector/ru_get_oms_token |
/K3T/CO_RU_GET_OMS_AUTH | /mdlp/connector/ru_get_oms_auth |
/K3T/CO_RU_MDLP_CHECK_TOKEN | /mdlp/connector/ru_mdlp_check_token |
/K3T/CO_RU_MDLP_REQ_SIGNED | /mdlp/connector/ru_mdlp_req_signed |
/K3T/CO_RU_MDLP_UPDATE_TOKEN | /mdlp/connector/ru_mdlp_update_token |
/K3T/CO_RU_UPDATE_OMS_TOKEN | /mdlp/connector/ru_update_oms_token |
The values for user, password, URL port and Transport Binding Type (SOAP 1.1 or SOAP 1.2, the default value is SOAP 1.1) shall match the values in the configuration file of the connector Java part.
...
Field | Description, Values |
MDLP Conf ID | Free text used to describe the Configuration ID |
Approver | User for automatic approval (optional) |
Approver Group | Approver Group to be checked (optional) |
User Apprvl | Wait explicit user approval (optional) |
Queue Name | Free text for Queue name in the transaction SMQ1 can be used to group the messages (optional) |
Skip file upload | Set check box to deactivate storage files in the folder as SAP ATTP standard |
Description | Description |
JCon Destination | RFC destination name in case RFC used for connection to connector Java part |
Logical Port | Logical port in case web service used for connection to connector Java part |
Signature Required | Manual signature mode for token and outbound reports (optional) |
Assign the MDLP long (36-digit participant GUID ) and short(14-digit domestic location ID) Subject ID in the transaction /K3T/RU_CONF under “MDLP Subject ID”, if Configuration ID shall be determined based on the Subject ID
...
Function module | Description |
/K3T/RU_AIF_IN_AUTO_701 | Function module generates the message 701 based on content of inbound message. |
/K3T/RU_AIF_IN_EMAIL | Function module triggers alert email based on content of inbound message. The alert category and email shall be maintained in the transaction /K3T/RU_CONF under “Alert recipient” |
/K3T/RU_AIF_IN_LM | Function module updates confirmation status in logistic monitor for 605, 606, 607, 627, 628 inbound messages |
/K3T/RU_AIF_IN_NO_REACTION | Function module set inbound message status processed |
/K3T/RU_AIF_IN_OMS_MSG | Function module updates serial number MDLP status from message 10311, 10319 (OMS) |
/K3T/RU_AIF_IN_REP | Function module creates SAP ATTP reporting event |
/K3T/RU_AIF_IN_ST_REFUSAL | Function module updates serial number MDLP status from message 605, 606 (message cancelation) |
/K3T/RU_AIF_IN_ST_UPDATE | Function module updates serial number MDLP status by requesting status from MDLP |
/K3T/RU_AIF_IN_RETURN_SCN | Function module posts unpacking, receiving, and shipping event for return process, if inbound message contains only SGTINs and turnover_type = 2. Otherwise, the function module /K3T/RU_AIF_IN_SCN will be executed. |
/K3T/RU_AIF_IN_RETURN_SCN2 | Function module posts unpacking, receiving, and shipping event for return process, if inbound message contains only SGTIN, or SSCC as originally shipped, or SSCC unpacked from originally shipped SSCC, or SSCC with less SGTINs as originally shipped and turnover type = “2”-return. Otherwise, the function module /K3T/RU_AIF_IN_SCN will be executed. |
/K3T/RU_AIF_IN_SCN | Function module posts commissioning, packing, shipping, receiving event based on inbound message. The current hierarchy will be downloaded from MDLP and compared with current hierarchy in SAP ATTP. The hierarchy shall not exist in SAP ATTP or matched with MDLP. The source / destination mapping parameters and the events to be posted can be configured with transaction /K3T/RU_SCN_MAP |
...
report manual signature filter - OMS token for manual signature configurations will not be updated by program if program is executed on background mode (only dialog mode)
manual signature - If OMS token for manual signature configuration need to be updated additional popup window appears to execute manual signature to sign authorization data via SAP GUI and Crypto Pro SSF integration. After signature data is send to MDLP Connector Java part and token is updated at ATTP system
...
5. Enhancements of the Solution
...