Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Document History

...

Name

Description, Values

EDO_SYSTEM

ATTP System name (with assigned RFC with path /edo/api )

Example: EDO

EDO_SYSTEM_API

ATTP System name for internal Connector calls (with assigned RFC without path /edo/api )

Example: EDO

MON_NAVIG_ACTIVE

Navigation to ATTP Cockpit is active for transaction /K3TKZ/DOC_MONITOR

X - active

Following the recommended minimum set of parameters

Name

Value

EDO_SYSTEM

Example: EDO

EDO_SYSTEM_API

Example: EDO_API

Customizing for Reports

Relevant industry

...

Field

Description, Values

Industry

Industry relevant for connector operations

Product group

Product group at EDO system

Text

Free text used to describe industry

Inbound document active

Flag to activate inbound document processing (for future releases)

 This This mapping will be used to identify correct product group (Commodity group) on execution True EDO API request.

Example:

Industry

Product group

Text

20

Pharma

Pharmaceuticals

...

Field

Description, Values

Doc Type

Internal document type (values are predefined).

  • 1 Act of receipt transfer Single distributor

  • 2 Introduce from EAEU

  • 3 Import from 3rd country

  • 4 Withdrawal Notification

  • 5 Repeat introduce Notification

  • 6 Act internal transfer

  • 7 Act internal transfer Single distributor

  • 10 Act of receipt transfer

  • 11 Codes transfer from non-resident

  • 91 OMS Report

  • 6000 New aggregation out of production

Document Type Description

Text to be displayed at Report Monitor for document type

EDO Document Type

EDO System API document type

Mapping attributes

...

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:

...

Class-based rule condition is maintained via transaction /K3TKZ/EDO_CUST node “Rule condition” and based on class method /K3TKZ/CL_EDO_RULES=>GET_RULE_CONDITION_CLASS. Method is used to get class name from table /K3TKZ/C_EDOCOND, custom class could be assigned as condition processor. Class method /K3TKZ/IF_EDO_3K_RULE_CONDITIONS~EXECUTE COND~EXECUTE is called. (Rule processing will stop check if result is skip rule). 

...

Program works as single instance for all configurations each selected configuration (based on logical lock).

In case sending failed program updates field “Error text” and leave processing status without change to send report with next run.

...

Program works as single instance for all configurations each selected configuration (based on logical lock).

First response for report is requested after delay set in the configuration transaction /K3TKZ/EDO_CONF. 

...

The report run results are stored as application log transaction SLG1, Object  /STTP/, Sub object REP, External ID /K3TKZ/EDO_OMS_REPORT

5. Enhancements of the Solution

...

  • 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”

...