You are on page 1of 5

.

Proprietary and Confidential

Technical Specification
Object name: DELPHI-TECH-INT-GLOB-PI PHOENIX Territory
Object version- current: 1.0 Object version - proposed: 1.0

Revision History

Document
Date Author Description of Change
Version #
1.0 08/24/2010 Meeravali Dudekula Initial document

Hospira, Inc. Page 1 of 5


.

Proprietary and Confidential

Technical Specification
Object name: DELPHI-TECH-INT-GLOB-PI PHOENIX Territory
Object version- current: 1.0 Object version - proposed: 1.0

1.1 General Information

Territory information is maintained in the Delphi system. A scheduled job in Delphi creates a “.txt” file
with the newly created / changed Territory records every night. This file will be sent to Model N in XML
format through PI.

PI picks the .txt file and converts it into the XML message as per Model N’s specifications and posts the
XML message as a file onto the FTP Server.

Model N then imports the XML file from the FTP Server and creates / updates the Territory records into
its database.

1.2 Development Description - Technical Details


1.2.1 Object Details
Interface Configuration
# ID Scenario IR Namespace Sender Receiver
Adapter Adapter
1 CS_Phoenix_Territory_Delphi_ http://HOSPIRA.com/PHOENIX/ File File
to_ModelN territory:delphi_to_mn

SAP R/3 Configuration

# Part Partner Message Message Message Output Basic IDOC User


ner Type Type Code Function Mode Type Extensi Exit
on

SAP PI - ID Configuration
# ID Scenario Sender Business Sender Comm. Receiver Receiver Comm.
System Channel Business Channel
System
1 CS_Phoenix_Terri BS_DELPHI CC_Phoenix_D BS_MODE CC_Phoenix_modelN
tory_Delphi_to_M elphi_NFS_Fil LN _File_Territory_RCV
odelN e_Territory_SN
D

Hospira, Inc. Page 2 of 5


.

Proprietary and Confidential

Technical Specification
Object name: DELPHI-TECH-INT-GLOB-PI PHOENIX Territory
Object version- current: 1.0 Object version - proposed: 1.0

SAP PI - IR Design & Development


# Software Data Messa Outbo Inbound Message Interface Exter Import
Component Type ge und Message Mapping Mapping nal ed
Version and Type Messa Interface Defini RFC/
Namespace ge tion IDOC
Interfa
ce
1 HOSPIRA_D Territor Territ Territor Territory_ Territory Territory XD_T N/A
ELPHI 1.0 y_Delp ory_D y_Delp MN_IB_S _New_D _Delphi_ ERRI
http://HOSPI hi_DT elphi_ hi_OB I elphi_To To_Mode TORY
RA.com/PH MT _SI _ModelN lN_OM
OENIX/territ _MM
ory:delphi_to
_mn

Selection Screen Details


1.2.2
None

1.2.3 Search Help Requirements


None
1.2.4 Program Logic:
Convert the .txt file provided by Delphi into XML.
Map the converted XML message and perform the validation on mandatory fields. Raise alert if
the mandatory fields are missing.
Map the converted XML message to the XML message structure of Model N and post the XML
file to the Secure File Server for processing by Model N.

Territory_New_Delph
i_To_ModelN_MM.xls

1.2.5 Data Input Details


Delphi will provide the file “Model N_Export_Territory.txt” (CSV Format)

1.2.6 Database Tables Used


None

1.2.7 External files used


None

Hospira, Inc. Page 3 of 5


.

Proprietary and Confidential

Technical Specification
Object name: DELPHI-TECH-INT-GLOB-PI PHOENIX Territory
Object version- current: 1.0 Object version - proposed: 1.0

1.3 Process Flow


1.3.1 Dependencies
 Delphi should provide a TXT file with the newly created / changed Territory records every day
onto the FTP Server.
 PI will pick the file from the FTP Server, and send it to Model N in the form of an XML file
 Model N will pick the file given by PI from the FTP Server and import the Territory records into its
database.

Data Flow

1. A new text file is created with Territory information in Delphi.


2. PI then picks the flat file, converts it into XML message, and maps it to the XML message
structure of Model N
3. PI will perform a check for mandatory fields in the Territory XML message and raise an Alert if
any mandatory field is missing.
4. PI will raise an alert in case of any communication failure with the FTP Server

Hospira, Inc. Page 4 of 5


.

Proprietary and Confidential

Technical Specification
Object name: DELPHI-TECH-INT-GLOB-PI PHOENIX Territory
Object version- current: 1.0 Object version - proposed: 1.0

5. PI, then maps the source .txt file message of Territory from Delphi to the XML message structure
of Model N, and posts the data as an XML file to the FTP Server.
6. A scheduled job is executed in the Model N system to pick the file from the Secured FTP Server
and update the data in it’s database
7. Model N performs required data validations and runs the standard customer dataflow to store data
in Model N master data tables

1.3.2 Security and Control Requirements


None

1.3.3 Trouble Shooting / Error Handling/Restart & Recovery


If an error occurs in the transmission of data coming to Delphi, the Delphi support team is
responsible for researching and resolving the error. Once the error is resolved, the interface can be
re-executed. If the file does not trigger the SAP PI process or the file cannot be FTP’ed to the
Model N server or failure occurs within the PI environment, then the BASIS and PI groups will
resolve the issue and reprocess failed data. If the file fails to load to the Model N Staging Area
then the Model Group will resolve the issue.

1.3.4 Batch Scheduling Requirements

1.3.5 Program Output


Output Filename: Delphi_to_ModelN_Territory.xml
Output File Destination: Production:
Development:

1.4 References
1.4.1 Hospira Functional Spec
1.4.2 Functional Contacts

1.4.3 Other Technical Contacts


Intelli Group Technical
Other Documents and Links (Attachments)
None

**End of Document**

Hospira, Inc. Page 5 of 5