Sample TSD 6

.
Proprietary and Confidential
Technical Specification
Object name: OTC-TECH-INT-GLOB-PI PHOENIX UnitOfMeasure
Object version- current: 1.0 Object version - proposed: 1.0
Revision History
Document
Date Author Description of Change
Version #
1.0 11/29/2010 Meeravali Dudekula CR 8000013544
Hospira, Inc. Page 1 of 7

.
Table of Contents
1.1 General Information.....................................................................................................................................2
1.2 Development Description - Technical Details.............................................................................................2
1.2.1 Object Details.....................................................................................................................................2
1.2.2 Selection Screen Details.....................................................................................................................3
1.2.3 Search Help Requirements.................................................................................................................3
1.2.4 Program Logic:..................................................................................................................................3
1.2.5 Data Input Details..............................................................................................................................3
IDOC: ZMATMASERP.ZMATMASERP..............................................................................................................4
Intermediate File: MN_ProductUOM.txt................................................................................................................4
1.2.6 Database Tables Used.........................................................................................................................4
1.2.7 External files used..............................................................................................................................4
1.3 Process Flow................................................................................................................................................4
1.3.1 Dependencies.....................................................................................................................................4
1.3.2 Data Flow...........................................................................................................................................4
1.3.3 Security and Control Requirements...................................................................................................5
1.3.4 Trouble Shooting / Error Handling/Restart & Recovery...................................................................5
1.3.5 Batch Scheduling Requirements........................................................................................................5
1.3.6 Program Output..................................................................................................................................5
1.4 References....................................................................................................................................................5
1.4.1 Hospira Functional Spec....................................................................................................................5
1.4.2 Functional Contacts............................................................................................................................5
1.4.3 Other Technical Contacts...................................................................................................................6

.
1.1 General Information

The Product Unit of Measure master data is triggered by the SAP system whenever a product
records is created or changed. The data is populated into the IDOC and the IDOC is triggered to
the PI system.
The PI system, performs the validation on the mandatory fields and posts that data as a TXT file
to one of the folder’s in it’s own file system for the first IDOC, and the data from the rest of the
IDOC’s is appended to that TXT file. This TXT file is then picked by the PI system, converted
into XML message, and is mapped to the XML message structure of Model N and will be posted
to the FTP server for Model N to process.
1.2 Development Description - Technical Details

1.2.1 Object Details
Interface Configuration
# ID Scenario IR Namespace Sender Receiver
Adapter Adapter
1 CS_Phoenix_UnitOfMeasure_S http://HOSPIRA.com/PHOENIX/ None File
AP_to_ModelN productuom:sap_to_mn
CS_Phoenix_UnitOfMeasure_S http://HOSPIRA.com/PHOENIX/ File File
AP_to_ModelN productuom:sap_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
1 R/3 LS ZMATM None None Transfer ZMAT None None
ASERP Immed. MASE
RP
SAP PI - ID Configuration
# ID Scenario Sender Business Sender Comm. Receiver Receiver Comm.
System Channel Business Channel
System
1 CS_Phoenix_Unit BS_D01_030 None BS_DX1_0 CC_Phoenix_NFS_Fil
OfMeasure_SAP_ 20 e_UnitOfMeasure_RC
to_ModelN V
CS_Phoenix_Unit BS_DX1_020 CC_Phoenix_N BS_MODE CC_Phoenix_ModelN
OfMeasure_SAP_ FS_File_UnitO LN _File_UnitOfMeasure
to_ModelN fMeasure_SND _RCV

.
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 http://HOSPI UnitOf UnitO No Phoenix_ I_ZMAT I_ZMAT N/A ZMAT
RA.com/PH Measur fMeas need UnitOfMe MASER MASER MASER
OENIX/prod e_Prod ure_Pr asure_Pro P_TO_U P_TO_U P.ZMAT
uctuom:sap_t uct_DT oduct duct_Asnc NITOFM NITOFM MASER
o_mn _MT h_In_SI EASURE EASURE P
_PRODU _PRODU
CT_MM CT_OM
2 http://HOSPI UnitOf UnitO Phoeni Phoenix_ I_UNITO I_UNITO XD_U N/A
RA.com/PH Measur fMeas x_Unit ModelN_ FMEAS FMEAS NITO
OENIX/prod e_Prod ure_Pr OfMea UnitOfMe URE_TO URE_TO FME
uctuom:sap_t uct_DT oduct sure_Pr asure_Pro _MN_U _MN_U ASUR
o_mn _MT oduct_ duct_Asnc NITOFM NITOFM E_PR
Asnch_ h_In_SI EASURE EASURE ODU
Out_SI _PRODU _PRODU CT
CT_MM CT_OM
1.2.2 Selection Screen Details

None
1.2.3 Search Help Requirements

None
1.2.4 Program Logic:
Receive the IDOCs’ from the SAP system, map them to the intermediate file structure and post /
append the data to the text file.
Pick the text file, convert its data into XML message and map this XML message to the XML
message structure of Model N.
Post the final XML message as an XML file into the FTP server for Model N to process.
I_ZMATMASERP_TO I_UNITOFMEASURE_
_UNITOFMEASURE_PRODUCT_MM.xls
TO_MN_UNITOFMEASURE_PRODUCT_MM.xls

.
1.2.5 Data Input Details

IDOC: ZMATMASERP.ZMATMASERP
Intermediate File: MN_ProductUOM.txt
1.2.6 Database Tables Used

None
1.2.7 External files used

None
1.3 Process Flow

1.3.1 Dependencies
The required RFC destinations need to be setup on R/3 and PI systems.
The input IDOC needs to be generated in SAP R/3 and sent to PI server, which will trigger the
process.
An FTP account will be required on the Model N server for PI to connect and PUT the final file.
1.3.2 Data Flow

.
1. A new IDOC is created for any change or create to product unit of measure.
2. The IDoc is sent to PI by batch program once in every 2 hours
3. PI performs all the data validations in the IDOC for all the mandatory fields and appends the
records from each IDOC into a flat file in it’s file system
4. PI will raise an alert in case of any missing mandatory fields or communication failure with the
file server
5. PI then picks the flat file, converts it into XML message, and maps it to the XML message
structure of Model N
6. PI moves the .xml file to the secured file server
7. A scheduled job is executed in the Model N system to pick the file from the Secured File Server
and update the data in it’s database
8. Model N performs required data validations and runs the standard product dataflow to store data
in Model N master data tables
Once the data is processed by Model N, it moves the files that are successfully processed into the
“Success” folder and all the files that are failed to process into the “Failed” folder and a notification is
sent by Model N to SAP support team to resolve the validation issues and resend the data.
1.3.3 Security and Control Requirements

None
1.3.4 Trouble Shooting / Error Handling/Restart & Recovery

If an error occurs in the transmission of data coming to SAP, the SAP 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.5 Batch Scheduling Requirements

SAP Job Schedule to run daily at pre determined time will trigger program RBDMIDOC in SAP
R/3. This will create the ZMATMASERP.ZMATMASERP IDOCs and trigger the process in SAP
PI.
1.3.6 Program Output

File ProductUOM_ModelNMmddyyyyHHmmss.xml will be FTP’ed to Model N server.
1.4 References
1.4.1 Hospira Functional Spec

.
1.4.2 Functional Contacts
1.4.3 Other Technical Contacts

IntelliGroup Technical
Other Documents and Links (Attachments)
None
**End of Document**

Sample TSD 6

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Sample TSD 6

Încărcat de

Drepturi de autor:

Formate disponibile

.

Proprietary and Confidential

Hospira, Inc. Page 1 of 7

Proprietary and Confidential

Hospira, Inc. Page 2 of 7

Proprietary and Confidential

1.1 General Information

1.2 Development Description - Technical Details

SAP R/3 Configuration

# Part Partner Message Message Message Output Basic IDOC User

Hospira, Inc. Page 3 of 7

Proprietary and Confidential

SAP PI - IR Design & Development

1.2.2 Selection Screen Details

1.2.3 Search Help Requirements

Hospira, Inc. Page 4 of 7

Proprietary and Confidential

1.2.5 Data Input Details

Intermediate File: MN_ProductUOM.txt

1.2.6 Database Tables Used

1.2.7 External files used

1.3 Process Flow

1.3.2 Data Flow

Hospira, Inc. Page 5 of 7

Proprietary and Confidential

1.3.3 Security and Control Requirements

1.3.4 Trouble Shooting / Error Handling/Restart & Recovery

1.3.5 Batch Scheduling Requirements

1.3.6 Program Output

Hospira, Inc. Page 6 of 7

Proprietary and Confidential

1.4.2 Functional Contacts

1.4.3 Other Technical Contacts

Hospira, Inc. Page 7 of 7

S-ar putea să vă placă și