AIM – Automated

Interface Monitor
 AIM – Automated Interface Monitoring
• AIM – is an automated solution which creates Top Down tickets and assigns these directly to the market Assignment Group based on the EMSG portal
 The current solution
 Top Down tickets are created manually by ICC 1st level Monitoring & Support team when IDocs are failing in SAP
 The EMSG – error messaging portal is used as the source to find relevant market resolution group (= Assignment Group in Prime) and the corresponding ticket priority (P1/P2/P3/P4/P5)
 Tickets are manually created and assigned to the market AG - assignment groups for resolution
 The ticket contains a spreadsheet with failed IDoc numbers
 ZCMCL (or ZCMCL+ ) transaction is used by all market key contacts and LGO people to review failed Idocs and to reprocess or block them

 AIM – Automated Interface Monitoring

 AIM is the new solution which will replace manually raised Top Down tickets with automated incidents
 The incident will be created based on an automated look-up in the error messaging portal to retrive the correct market resolution group (=AG) and the ticket priority for the failing IDOC & message type based on 1) Sending partner 2) Message Type 3) Error message defined
by the Error ID and Error number
 NEW: The AIM incident contains a new key field called AIM ID. This information will be found in the description field and also in the incident reference ->TAB:
 Related Records - > External -> MYR reference = AIM ID
 The AIM ID number is a unique identifier key which is used to retrive the failed IDOC numbers when using ZCMCL transaction in SAP
 ZCMCL or ZCMCL+ transaction is used by all market key contacts and LGO people to review failed Idocs and to reprocess or block them

8-Jul-19 3
 AIM – roll out
• Automated Interface Monitoring solution will be rolled out in several phases

 AIM roll-out in 4 different phases:

1. Low priority & low volume

2. Low priority & higher volume

3. Low/Medium priority & higher volume

4. Medium priority (=P3) & high volume like masterdata and high volume transactional data (ORDERS), + P1/P2 message categories

 P1/P2 : Created by AIM and assigned to ICC 1st level Monitoring & Support team
 AIM P1/P2 tickets will be generated automatically but assigned to ICC 1st level Monitoring & Support team instead of direct assignment to a market AG

 ICC 1st level Monitoring & Support team team will escalate P1/P2 tickets to the market Assignment Groups via Group Servicedesk (process = normal P1/P2 escation process)

 Group Servicedesk will make a call out as per normal procedure

 The AIM – automated P2/P1 messages will not be rolled out YET!

 Manual monitoring using ZCMC (MSS/CA8) is the current work process for P1&P2s

8-Jul-19 4
 AIM + ZCMC monitoring
• ICC Offshore to continue monitoring with ZCMC (MMS) tool

 ZCMC monitoring in CA8/C38 (MMS) is still the standard monitoring process and will be active together with the AIM solution

 ICC 1st level Monitoring & Support team team will monitor and create manually Top Down tickets for interfaces which is not yet LIVE with AIM

 AIM will update the classification field with AIM reference number and this is visible when using ZCMC tool (MSS) – no manually created Top Down ticket is required when AIM reference exist!

 The auto classification table will still be used with AIM

 ICC 1st level Monitoring & Support team will receive the AIM tickets whenever there is a missing EMSG portal entry for the given partner/message and error message combination. This is also true for ALL P1 & P2 tickets, which has to be manually escalated through Group Servicedesk with the correct market Assignment Group.

 It is important that the monitoring team updates the EMSG portal correctly whenever they receive an AIM created ticket in order to reduce failed EMSG look-ups in the future

8-Jul-19 5
 AIM + EMSG PORTAL process
 AIM table in SAP maintained with:
 Sending Partner and Message type
 SAP Job runs frequently, groups failed IDocs for:
 The Sending Partner and Message type which is maintained in the AIM table
 Incidents will be created for the SAME / UNIQUE :
 Sending Partner (plant) + Message Type + Error Message ID & Number
 AIM – checks the Error ID, Error message number , Message Type and
Environment in the EMSG portal
 LOOK-UP in EMSG - Entry exists? YES
 AIM retrieves: Assignment Group and Ticket Priority
 NOTE: WILDCARDS (USEWMS*) will not work!!!

 LOOK-UP in EMSG - Entry exists? NO

 The incident is automatically created and assigned to ICC 1st level Monitoring & Support
team and they will manually check EMSG to find the correct Assignment Group and
assign the ticket to the MARKET AG
 ICC 1st level Monitoring & Support team will update the portal with the missing
entry/plant to avoid reoccuring problems.

8-Jul-19 6
 AIM Tickets will be grouped as in this
example
 SOS – failed IDOCs
 IDOC1: ORDERS, USEWMS5555, Error msg: Order can not be posted
 IDOC2: DESADV, ARETMS0001, Error msg: Already posted
 IDOC3: ORDCHG, USEWMS5555, Error msg: Order can not be posted
 IDOC4: DESADV, ARETMS0001, Error msg: Already posted
 IDOC5: ORDERS, USEWMS5555, Error msg: Order can not be posted

Tickets generated
 Ticket 1
 IDOC1: ORDERS, USEWMS5555, Error msg: Order can not be posted
 IDOC5: ORDERS, USEWMS5555, Error msg: Order can not be posted
 Ticket 2
 IDOC2: DESADV, ARETMS0001, Error msg: Already posted
 IDOC4: DESADV, ARETMS0001, Error msg: Already posted
 Ticket 3
 IDOC3: ORDCHG, USEWMS5555, Error msg: Order can not be posted

8-Jul-19 7
AIM – Process Flow 3. ABAP map makes WebServices call to retrieve RG,
Priority and Resolution Instructions from the Messaging
Portal

GSS

MMS Service Center

EMSG

Connect IT
CMC

XLink
0. Current manual
monitoring in MMS. IDoc
connections from all R/3
systems

EUR
6. Connect IT uses the XML
received to generate a ticket in
AOA
Service Centre
AMS

COM
5. XLink with Post-Processing script
SOS
XI writes upload files to SHARE folder
FIN

4. XML formatted file sent to

1. Collector “functions” in R/3 boxes 2. Asynchronous ABAP Proxy Connect IT
monitor error conditions and group like used to transmit error conditions
errors to XI

8-Jul-19 8
AIM – Technical process flow and main tables
AIM PROGRAM
/GLB/RGTIN_IDOC_ERROR_MONITOR XI
XML look-up
Table Server
/GLB/RGTT_AIMCFG Hqbusa0059

CC_SOAP_RCV_Auto_Int_Mon_PR

IDOC
IDOC IDOC
SAP Status
Status “51”
Status
“51” “51”
(SOS/COM/FI)
ERROR!!!!
ERROR!!!!
ERROR!!!! Sender Interface
MI_Automatic_Interface_Monitor_R3_Out

AIM Config Table Receiver Service

/GLB/RGTT_AIMMSG GLB_GT_3_SM7MANAGER_PP_SM7

Receiver Namespace
http://gt.glb.nestle.com/xa/AIM
Auto classification
Receiver Interface
/GLB/XGTCMCACNFG
MI_ServiceManager_Incidents_Inb

8-Jul-19 9
AIM – Automated Interface Monitoring
high level overview
IDOC
IDOC
Status
Status
IDOC
Status
“51”
“51”
ERROR!!!!
ERROR!!!!
“51”
ERROR!!!!
Error Messaging
Portal

XI Market Assignment
XML look-up Groups
&
SAP (SOS/COM/FI) Ticket Priority

AIM PROGRAM

SM7
PRIME

INCIDENTS to:
Assignment
Groups

8-Jul-19 10
AIM - Operational Process
SAP R/3 System SAP XI / EMSG Service Center
ICC Messaging
Support
Assignment Group

IDoc
Errors

Direct
AIM Collector ABAP Service
Assignement
Program Map Center
to AG

Automatic
Assignment to
ICC

ICC manually
Identifies AG
EMSG from EMSG &
Messaging Portal assignes to AG

AG resolves
ZCMCL / ticket and blocks/
ZCMCL+ to reprocesses
block / reprocess Idocs using
IDocs ZCMCL /
ZCMCL+

8-Jul-19 11
AIM – Tables
Auto Classification Table
AIM Config table
AIM Config Table
/GLB/RGTT_AIMMSG /GLB/XGTCMCACNFG
/GLB/RGTT_AIMCFG
CA8 CA8
XI

JOB JOB
[AOA] [AOA] AIM Activation table
XA_[AMS]_RGTTAB_AIM_DAILY_SEND XA_[AMS]_RGTTAB_AIM_DAILY_SEND
[EUR] [EUR]
/GLB/RGTT_ECCACT

FI/COM/SOS

Auto Classification Table

AIM Config Table AIM Message Type
/GLB/RGTT_AIMMSG /GLB/XGTCMCACNFG Activation table

FI/COM/SOS FI/COM/SOS /GLB/RGTT_AIMMSG

FI/COM/SOS

8-Jul-19 12
AIM ID + ZCMCL Monitor & Process IDocs
SM7
PRIME INCIDENTS
ZCMCL transaction
+ AIM Identifier
AIM Identifier nnn nnn

ZCMCL IDOC
REPROCESS IDocs Status “53”
IDOCIDOCIDOC Processed OK
Status
Status
“51”
Status
“51” “51”
ERROR!!!!
ERROR!!!!
ERROR!!!!

ZCMCL IDOC
BLOCK IDocs Status “59”
(no further processing!) BLOCKED

8-Jul-19 13
SM7 •Incidents:
Incident Information:AIM Identification
AIM Identifier number
to retrieve the failed IDocs
• AIM ID example below: 000000000000351

Ticket INFO:
•SAP SID
•Message type
•Sender system
•SAP receiving
system
•AIM – identifier to
look-up the failed
IDocs!

8-Jul-19 14
Incident Details: AIM ID
•
•
AIM Identifier is used to retrieve IDoc specific information using transaction ZCMCL in SAP
AIM Identifier is found in the Incident description, or under TAB:
• RELATED RECORDS -> EXTERNAL ->

• TYPE MYR Reference:

• AIM ID example below: 000000000000351
• NOTE: the AIM ID substitutes the old IDoc attachment! There are no longer a list of IDoc numbers attached to the Prime incident

8-Jul-19 15
ZCMCL
• AIMtransaction + IDoc
Identifier is used to retrieve AIM IDinformation
specific number, I
using ZCMCL
• Use AIM ID in ZCMCL transaction , field = IDENTIFIER
• EXECUTE report.

8-Jul-19 16
ZCMCL: Status Monitor for ALE Messages
•

•
View of the failed IDocs which are represented by the AIM ID

Click on the Display IDocs button to view the IDoc field contents

• ZCMCL – Status Monitor for ALE Messages

• The AIM ID reported 2 IDocs in error!

8-Jul-19 17
ZCMCL: IDoc Error Message and Status
•

•
IDoc details and error message!

Error: PU Ordered quantity exceeded by 25.000 KG…

• Expand “Data Records” to review Idoc segments and field contents

8-Jul-19 18
 Ticket handling process for the Market AG and Satyam

• Correct work process for Top Down tickets:

1. Market AG: Reprocess the failed Idocs using ZCMCL transaction
2. IF IDocs posted successfully to status “53”
• Update the ticket: IDoc’s processed successfully!
• CLOSE the ticket.
3. IF the IDoc’s failed again with status “51” and can’t be reprocessed successfully because of incorrect data:
• BLOCK the idocs (= status “59”) and update the ticket confirming the Idocs have been blocked.
• CLOSE the ticket.
4. If market/LGO doesn’t have access to ZCMCL or can’t reprocess the failed IDocs:
1. Put GISIT_IT MESSAGING MON_SATYAM in collaboration on the ticket.
• Do not re-assign the ticket!
2. Request to reprocess or block the IDocs
3. The ticket should be closed by the market AG only when the IDoc’s have been processed successfully or blocked.

8-Jul-19 19
 AIM TEC INCIDENT – when AIM Top
Down process fails
• AIM TEC Incident description
 The upload of tickets to SM7 uses a newly developed XML interface that validates the format and content of the XML file before
creating the incident
 Where the format of the XML is found to be incorrect or reference checks against valid values in SM7 fail, a TEC ticket will be
generated to assignment group “GISIT_IT MESSAGING MON_SATYAM”.
 Offshore team will reassign the ticket to Onshore team after initial investigation
 The tickets will have the following Title and Description. Note the highlighted text to easily identify these TEC tickets:
• Title:
• EUR Tivoli ddinta0003.globedev.ddc Message -:| AIM - An Auto Interface Monitor XML file with errors failed to generate an Incident
in SM7. Please investigate the issue. To find out the correct filename, please follow the links below or check the event in queue
//hqbusa0059/scinterface_PP/GLOBAL/NBS_MESSAGING/1_New/../6_Log/|//hqbusa0059/scinterface_PP/GLOBAL/NBS_MESSAGING/
1_New/../4_Invalid_format (IAM Ref=000-000-001-169-000-090-006)

• Description:
• EUR Tivoli ddinta0003.globedev.ddc Message -:
• A XML file was processed with errors by the Tactical ESS interface. Please investigate the issue. To find out the correct filename, please
follow the links below or check the event in queue.
• //hqbusa0059/scinterface_PP/GLOBAL/NBS_MESSAGING/1_New/../6_Log/
• //hqbusa0059/scinterface_PP/GLOBAL/NBS_MESSAGING/1_New/../4_Invalid_format (IAM Ref=000-000-001-169-000-090-
006)

8-Jul-19 20
Exceptions to AIM monitored Idocs
• Some partners will be excluded from AIM monitoring due to the
complexities of automating this.
• These will be…….

• SAP to SAP messages - ( ZMATMAS, /GLB/XGTDEBMAS etc) where the sender and receiver logical
systems are SAP systems
• Generic** partners to SAP (TOM, NCPS, QUADRAM, etc)
• Outbound from SAP messages

• **A Generic partner is defined where more than one AG is assigned to the message/partner combination in the ,messaging portal
i.e. Not specific to one market

8-Jul-19 21
 AIM – Support Process (New Interfaces)
Exceptions to maintaining AIM Table:
AIM table - /GLB/RGTT_AIMMSG in MMS should be No SAP to SAP
maintained at the same time when maintaining the No Generic partners to SAP
messaging portal by ICC 2nd level Support team No Outbound from SAP

New AIM table entries are automatically replicated

To Local R3 systems via /GLB/RGTTAB
Idoc replication from MMS to locals
Add in Messaging
Portal for PP and PR

New CRs (tasks Also

for DEV)
to be Add in AIM Config
executed Table
/GLB/RGTT_AIMMSG
for PP and PR

MMS (C38 , CA8)

8-Jul-19 22
 AIM – Support Process (New Interfaces)
Add to Messaging
Portal

Should be done
by ICC 2nd level
Support team

Add entries to
AIM table - /GLB/RGTT_AIMMSG in
MMS
In pre-prod and prod

8-Jul-19 23
AIM – Support Process (Delete Interfaces)
When removing entries in the messaging portal, ICC 2nd level
Support team should also remove entries in the AIM table -
/GLB/RGTT_AIMMSG in MMS and the AIM table in the local
systems ** Deletions are not distributed from MMS via the
normal /GLB/RGTTAB process

Delete in AIM Config

Table
New CRs (tasks /GLB/RGTT_AIMMSG
IDOC
IDOC Remove entries from
for obsoletion for PP and PR
Status
Status
“51”
“51” Messaging
to be on
ERROR!!!!
ERROR!!!! Portal for PP and PR
Executed) MMS (C38 , CA8)
also
Delete in the related
Local R3 systems
(COM,SOS, FI)

8-Jul-19 24
 AIM – Support Process (AIM ticket but no MP Entry)
Ticket in Monitoring Queue

MSat to Identify from Ticket:

1. Message Type MSat to reassign Ticket
2. Sender Do not change priority
3. Receiver Do not use GRP
- Default P3

Add in Messaging
Portal for PP & PR
If no AG can be identified, (Refer to similar Message
contact ICC 2nd level Support Types and Partners)

8-Jul-19 25
AIM – Support Process (Regular Checks)
Find new inbound Message
Types (FI/COM/SOS) Add in AIM Config
in PP or PR: Table
Add in Messaging /GLB/RGTT_AIMMSG
1. SE16 Portal for PP & PR for PP or PR
2. DBTABLOG
3. Date Range MMS(CA8 , C38)
4. Table EDP21

Exceptions:
No SAP to SAP
No Generic to SAP
(TOM, NCPS, QUADRAM, etc)

8-Jul-19 26
 AIM TEC Work Process – What To Do?
• STEP 1: View XML folders and raise a manual Top Down
 Check folder \\hqbusa0059\SCInterface\GLOBAL\NBS_MESSAGING\4_Invalid_format for the failed message
 Check folder \\hqbusa0059\SCInterface\GLOBAL\NBS_MESSAGING\6_Log to get details of the error.
 Manually create a new incident in SM7 using the Title and Description from the XML file and assign to the Market
Assignment Group, like the manual Top Down ticket process.
 IF the format of the file is incorrect – inform GISIT_IT Messaging by creating an incident (RM) + EMAIL ICC.

• STEP 2: Investigate why the XML look-up failed and resolve

 Check the Assignment Group in the Messaging portal is a valid AG in SM7 (Service Manager)
 Correct the Messaging Portal / Configuration Table / Mapping table as required to avoid reoccuring issues

8-Jul-19 27
 AIM – Technical documents
• AIM – One Pager (for ICC support teams)

• Automatic Interface Monitor - AIM - DEVWR0020614- One Pager (Vers. 1.0)

http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3810ceda7

• AIM - Auto Interface Monitoring ICC Offshore Runbook (Vers. 1.5)

http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3810d2f46

• ***********************************************************************************
*****************

• Technical documentation (for ICC_Center)

• Technical Spec XML Interface for Incidents (Vers. 1.0)

http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d381054bab

• Nestle PRIME Base Design Specification - XML Interface

http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d380feb59f

8-Jul-19 28
PICP 7.31 Specific Update.
The ABAP Proxy configured in Different SAP system needs to be redirected
from XI 7.0 to PICP 7.31 system.

As PICP 7.31 doesn’t have ABAP stack therefore the ABAP mapping done in
XI needs to be converted to a Java mapping.

As discussed in PICP Maturity meeting, one of the design option can be to

copy the table /GLB/RGTT_AIMCFG to SAP Solution manager along with its
content.

In PICP System at runtime an RFC Lookup can be called to read the table
/GLB/RGTT_AIMCFG in SOLMAN and the response can be sent to the JAVA
Mapping which in turn will call the web service of Messaging portal. Then
the consolidated data will be sent to the Xlink.

8-Jul-19 29