Catalogue Item Notification and Price

Document for
Albert Heijn

Authors
Rakesh Ramesh

Date
July 9, 2015

Document Version
1.0
Status
First Release

TEKsystems Global Services 2015

Page 1 of

Document Control
Change History
Date

Versi
on

Description

Author(s)

02-06-2015

1.0

First Release for 3098 ( EDI Upgrade ) Phase 2b

Rakesh Ramesh

TEKsystems Global Services 2015

Page 2 of

Table of Contents
Requirements..................................................................................................................... 4
Quantitative Requirements............................................................................................................ 4

Integration Process Layout.................................................................................................5

Integration Process Overview............................................................................................. 6
TN Gateway Cluster....................................................................................................................... 6
TN (XML) Inbound Processing Cluster............................................................................................. 6

TN Gateway Cluster............................................................................................................ 7
TN Processing Rule........................................................................................................................ 7
Packages and Flow Services........................................................................................................... 7

TN (XML) Inbound Processing Cluster.................................................................................8

TN Processing Rules....................................................................................................................... 8
TN Document Type Definition and Document Attribute..................................................................8
Packages and Flow Services........................................................................................................... 8

Errorhandling and Notification.......................................................................................... 10

Common Services............................................................................................................. 11
System Test Scenarios...................................................................................................... 12

TEKsystems Global Services 2015

Page 3 of

Requirements
Quantitative Requirements

norm course
Interface ID
Interface Name
Complexity
Direction
Record-length (or message, for single-record messages) in
bytes
Needed response time for one individual message
Needed response time for occurrences in bulk
Frequency max.
Frequency avg.
Average number of records per message/event
Maximum number of records per message/event
Quality Level of incident Handling
line-1
Line-2 Line-3
Total
Gold
10min 30min 3h + 20min
4h
Silver
10min 60min 6h + 50min
8h
Bronze 15min 60min 22h + 45min
24h
Tin
15min ---

Canonical 2100 DELFOR 96A from Broker to TN

Canonical 2100 DELFOR 96A from Broker to TN
Complex
TN -> EDII
>32 kb (flat file)

Service Level
Gold
Silver
Bronze
Tin

Gold / Silver / Bronze / Tin

Support Window
7 X 24
6 X 15 (mon-sat 07:00-22:00)
5 X 10 (mon-fri 08:00-18:00)
5 X 8 (mon-fri 09:00-17:00)

15 minutes
1 hour
6500 per hour
350 per hour
2033 bytes per invoice
9995 bytes per invoice
Gold / Silver / Bronze / Tin

Stress requirements in critical circumstances (like outage, or bulk

updates)
(Please consider that many types of batch-related communication are not suitable for a NRT interface)
Interface No.
Interface ID
Canonical 2100 DELFOR 96A to TN
Interface Name
Canonical 2100 DELFOR 96A from Broker to TN
Direction
Broker -> TN
Max number of messages
25000 (3 days of outage)
Needed response time
2 hours

TEKsystems Global Services 2015

Page 4 of

Integration Process Layout

< Add Logical Flow Diagram >
Figure 1: High Level Design for Inbound Catalogue Item Notification and Price Document for ETOS

TEKsystems Global Services 2015

Page 5 of

Integration Process Overview

TN Gateway Cluster
< Add Logical Flow Diagram >
Business partner SA2 (0821620400007) sends catalogueItemNotification
(v2.3, v2.7, and v2.8) and
priceDocument (v2.3, v2.7, and v2.8) messages to ETOS via Trading Networks. These messages arrive in the
Trading Networks of the Gateway Cluster via Enterprise Gateway. The Trading Networks (TN) Recognizer
identifies the Sender, Receiver and Document Type and determines the appropriate Processing Rule to execute
the processing service.
The processing service extracts the XML data. It constructs the TNGWGenericDoc document and published to
the TN Broker.
On success, it updates the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN to DONE with appropriate Activity Log.
In case of any exception, it updates the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN with corresponding Activity Log.

TN (XML) Inbound Processing Cluster

Trigger Service for TNGWGenericDoc Document
< Add Logical Flow Diagram>
The IS Trigger on the Integration Servers of the Inbound Processing Cluster consumes the TNGWGenericDoc
document based on /TNGWGenericDoc/Header/MessageControl/IntegrationName and
/TNGWGenericDoc/Header/MessageControl/IntegrationVersion and invokes the processing service. The
processing service extracts the XML message from /TNGWGenericDoc/Payload/Data and submits it as
InputStream to the Trading Networks of the Inbound Processing Cluster. The TN XML Recognizer identifies the
Sender, Receiver and Document Type and determines the appropriate Processing Rule to execute the processing
service.
Processing Service for catalogueItemNotification
v2.7, and v2.8)

(v2.3, v2.7, and v2.8) or priceDocument (v2.3,

< Add Logical Flow Diagram >

The processing service first extracts the XML data from TN BizDocEnvelope and parses and creates canonical
dt_cin from XML data.
Then the service publishes the canonical dt_cin.
On success, it updates the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN to DONE with appropriate Activity Log.
If any exception occurs, the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN is updated with corresponding Activity Log.

TEKsystems Global Services 2015

Page 6 of

TN Gateway Cluster
TN Processing Rule
Processing
Rule

Document
Types

Sender

Receiver

User
Stat
us

Action

IN_GW_CIN_AND_PRICE_2
.3_ETOS

catalogueItemNotification
2.3
catalogueItemNotification
2.7
catalogueItemNotification
2.8
priceDocument 2.3
priceDocument 2.7
priceDocument 2.8

0821620400
007

871019800000
4

Any

ah_inbound_pdm.v01.main:processTN

Execute a service

Packages and Flow Services

Package
Service Name
Trigger
Input Signature
Output Signature

Logical Flow

AH_Inbound_PDM
ah_inbound_pdm.v01.main:processTN
Processing Rule IN_GW_CIN_AND_PRICE_2.3_ETOS
bizdoc (document reference of wm.tn.rec:BizDocEnvelope)
sender (document reference of wm.tn.rec:ProfileSummary)
receiver (document reference of wm.tn.rec:ProfileSummary)
None
(1) Extract XML data content from
BizDocEnvelope(ah_tngw_common.v01.inbound.flow.xml:getBizDocContent)
(2) Construct the TNGWGenericDoc document with /MessageControl/integrationName
= AH_Inbound_PDM and /MessageControl/integrationVersion = 01
(ah_tngw_common.v01.inbound.map.xml:mapTNGWGenericDoc)
(3) Publish the TNGWGenericDoc to the broker
(ah_tngw_common.v01.inbound.flow.xml:publishTNGWGenericDoc)
(4) Update the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN to DONE with appropriate
Activity Log.
If any exception occurs, the logging data with corresponding status code is published to
EBER and the User Status of the catalogueItemNotification (v2.3, v2.7, and v2.8) or
priceDocument (v2.3, v2.7, and v2.8) message in TN is updated with corresponding
Activity Log.

TEKsystems Global Services 2015

Page 7 of

TN (XML) Inbound Processing Cluster

TN Processing Rules
Processing
Rule

Document
Types

Sender

Receiv
er

User
Status

Action
Execute a service

IN_CIN_AND_PRICE_2.3_ET
OS

catalogueItemNotificatio
n 2.3
catalogueItemNotificatio
n 2.7
catalogueItemNotificatio
n 2.8
priceDocument 2.3
priceDocument 2.7
priceDocument 2.8

08216204000
07

8710198000
004

Any

ah_pdm_pub_trnw.v01.main:PdmDelivery

TN Document Type Definition and Document Attribute

TN Document Types
catalogueItemNotification (v2.3, v2.7, and v2.8) or priceDocument (v2.3, v2.7, and v2.8)
TN Document Attribute
The following custom document attribute(s) will be associated with catalogueItemNotification (v2.3, v2.7, and
v2.8) or priceDocument (v2.3, v2.7, and v2.8)
Name

Description

Type

REF_TNGW_DOCID

Internal Document Id for Transaction Set Document from Gateway

Cluster

STRIN
G

Enable
d
Y

Packages and Flow Services

Package
Service Name
Trigger
Input Signature
Output Signature
Logical Flow
Package
Trigger

Trigger Properties

AH_PDM_Pub_TRNW
ah_pdm_pub_trnw.v01.main:processTNGWGenericDoc
ah_pdm_pub_trnw.v01.trigger:subscribeTNGWGenericDoc consumes the
TNGWGenericDoc document with /MessageControl/integrationName =
AH_Inbound_PDM and /MessageControl/integrationVersion = 01 and invokes the service
ah_pdm_pub_trnw.v01.main:processTNGWGenericDoc
TNGWGenericDoc (Document reference of
ah_tngw_common.v01.doc:dt_TNGWGenericDoc)
None
(1) Extracts XML data string from TNGWGenericDoc (/TNGWGenericDoc/Payload/Data)
(2) Submit the XML data to the Trading Networks as java.io.InputStream
(ah_tngw_common.v01.inbound.flow.xml:sendToTN)
AH_PDM_Pub_TRNW
ah_pdm_pub_trnw.v01.trigger:subscribeTNGWGenericDoc
Property Group
Property Name
Capacity
Trigger queue
Refill level
Acknowledgement queue size
Processing mode
Message processing
Max execution thread
Fatal error handling
Suspend on error
Retry until
Max retry attempt
Transient error
Retry interval
handling
On retry failure
Resource monitoring service

TEKsystems Global Services 2015

Value
10
4
1
Concurrent
2
False
Max attempts reached
0
10 seconds
Throw exception

Page 8 of

Package
Service Name
Trigger
Input Signature
Output Signature

Logical Flow

AH_PDM_Pub_TRNW
ah_pdm_pub_trnw.v01.main:PdmDelivery
Processing Rule IN_CIN_AND_PRICE_2.3_ETOS
bizdoc (document reference of wm.tn.rec:BizDocEnvelope)
sender (document reference of wm.tn.rec:ProfileSummary)
receiver (document reference of wm.tn.rec:ProfileSummary)
None
(1) Invoke service ah_pdm_pub_trnw.v01.flow:doPdmDelivery
(2) Get FTP parameters from the AH_Config
(ah_pdm_common.v01.flow:getPdmParam)
(3) Login to FTP server and move to Inbound directory returned by the getParam
service
(4) Create a unique filename based on timestamp
(ah_pdm_common.v01.flow:createFileName)
(5) Append .processing to the unique filename returned and check if the file
already exists in the Inbound directory. If its not, place the file into it.
(6) If the file is successfully placed, rename the file with .arrived extension.
If any exception occurs, the user status of the catalogueItemNotification (v2.3, v2.7,
and v2.8) or priceDocument (v2.3, v2.7, and v2.8) message in TN is updated with
corresponding Activity Log

TEKsystems Global Services 2015

Page 9 of

Errorhandling and Notification

For catching errors and failures out of webMethods processes and process-steps a separate component is
available in the AHOLD webMethods development kit. This is called the Error Handling Framework [EHF].
The EHF can publish an error message to the broker, where a dedicated service subscribes to them. This service
is called Message Broker Configuration and Notification service [MBCN]. It describes all sustained errors and
how- and when to propagate these to the support environments (TEC, PEREGRINE). All errors bound from EHF
are stored here and subsequently processed conform MBCN instructions. When an instruction is missing for a
certain message, a default notification will be produced.
The overview below shows the basic errors and their notification instructions in MBCN.
The severity is the severity as known from the escalation card.
The weekdays notifying indicates on which weekdays the errors will be notified to TEC and Peregrine. 1 =
Monday, 2 = Tuesday etc.
The assignment groups are the assignment groups as known in Peregrine.
Examples:
Process(step)

Error (basic description)

1,4,6,7

TEKsystems Global Services 2015

setting

value

Severity

Bronze

Date start notifying

Date of implementation

Date end notifying

Not yet specified.

Weekdays notifying

1-5

Time notifying

00:00 23:59

2. level support
assignment group as
known in Peregrine

BSS SUPPLY CHAIN SYSTEMS

3. level support
assignment group as
known in Peregrine

BIS ICC

Min. errors

Min. timeframe

Page 10 of

Common Services
Package

AH_TNGW_Common

AH_Common
AH_PDM_Common

TEKsystems Global Services 2015

Service Namespace
ah_tngw_common.v01.inbound.flow.xml :getBizDocContent
ah_tngw_common.v01.inbound.map.xml :mapTNGWGenericDoc
ah_tngw_common.v01.inbound.flow.xml :publishTNGWGenericDoc
ah_tngw_common.v01.inbound.flow.xml :sendToTN
ah_tngw_common.v01.util.doc:updateTN
ah_common.ehf_client.v01:publishEvent
ah_common.ehf_client.v01:setServiceContext
ah_pdm_common.v01.flow:createFileName
ah_pdm_common.v01.flow:ftpLogin
ah_pdm_common.v01.flow:getPdmParam

Page 11 of

System Test Scenarios

1) One catalogueItemNotification (v2.3, v2.7, and v2.8) or priceDocument (v2.3, v2.7, and v2.8) successfully
FTPd to the server
2) One catalogueItemNotification 2.8 or priceDocument (v2.3, v2.7, and v2.8) with invalid data or missing
mandatory fields results in error
3) One catalogueItemNotification (v2.3, v2.7, and v2.8) or priceDocument (v2.3, v2.7, and v2.8) with special
characters successfully FTPd to the server

TEKsystems Global Services 2015

Page 12 of