SPEC2000 Configuration and Considerations in SAP (Sales & Distribution - SD) Ali Khodafar Goodrich Aerostructures Group

Agenda SPEC2000 Overview Goodrich SPEC2000 Landscape Key configuration items – Master Data Customized routines Solution Strengths and Gaps Lessons learned ATA SPEC2000 & SAP Resources Questions

Overview A set of e-business specifications developed by the aerospace industry to facilitate e-commerce between airlines and suppliers Over 1000 companies, 2 million messages per months, in use over 40 years Seamless, stable, and cost effective ATA Aviation Marketplace (5+ million records, 300 participants, over 80 airlines)

Overview

SPEC2000 vs. Total Orders

ATA SPEC2000 Chapters 3 & 4

Goodrich SPEC2000 Landscape Cortland System to format raw data and fill functionality gap Airline Network Connection Unix script runs RFC: Function modules for inbound & outbound (flatfile to SPEC2K & visa versa) Enterprise Application Integration (EAI) - Moves data , controls data flow thru e*Ways, and archiving

S1BOOKED Record Format

IDoc Segments

IDoc List – WE02

Key Configuration Items – Master Data Partner Information Table - SPCPRTNRINF Setup both inbound and outbound entries for: Sold to Party (SP), Bill to Party (BP) Ship to Parties (SH) as many as needed. Multiple addresses, if required by the customer (Z function module to process and send out the messages)

Key Config. – Partner Profiles Setup both inbound and outbound parameters for : Sold to Party (SP), Bill to Party (BP) Ship to Parties (SH) as many as needed. What port (SPEC2K), FM (IDOC_INPUT_S1BOOKED_MM), and message type (BA01) to use.

Key Config. – Conversion Rules BD55 – Conversion Rules Maintain for every SPEC2000 message type for every customer (3 segments for S1BOOKED) Use the conversion rules to map SPEC2000 fields to R/3 in BD79

Key Config. – Conversion Rules BD79 – Maintain conversion rule for SPC_IP_MM_S1B_K11 M Map SPEC2000 fields (3 byte field name) to R/3 (Variable length) Can use constants (supplier or cage codes) Assign own values (CIC to SAP sold to party) Create own “Special conversion routines”

Customized Routines Create only when absolutely necessary Multiple SITA addresses (not the same as multiple ship to codes – VOE4 - EDPAR table) Material Substitution Customer specific – Optional elements (S1FRADDR, S1TOADDR) Fallout report, IDoc reprocessing Invoice / Acknowledgment reconciliation

Strengths and Weaknesses SAP SPEC2000 solution strengths: Excellent technical support (Service Marketplace), documentation, and on-line help Stable, comprehensive, and per ATA guidelines Customizable - Conversion exits, Z function modules Did I mention excellent technical support?!

Functionality Gap Acknowledgment sent only for successful IDocs SAP should ack. at this point regardless of IDoc status No Acknowledgments!

Strengths and Weaknesses Improvement areas: Functionality gaps: Ack. of unsuccessful IDocs or changes Reprocessing of IDocs (RFCUSER) – Ack. & S1ORDEXC Direct SAP connection to SITA/ARINC Optional data elements (S1FRADDR & S1TOADDR) – No IDocs! Master data maintenance (volume, transport) Reporting/Search capabilities (by part , PO, etc.)

Lessons Learned Need to have the right infrastructure, technical support, and development resources Do not underestimate master data and configuration efforts Need knowledge of SPEC2000 and IDoc processing Test different scenarios on different clients (Test SITA address - virtual customer) Allow plenty of time to test and implement Monitor the system regularly and carefully

SPEC2000 Resources SPEC2000.COM Contact Air Transport Association (Ken Jones, director of marketing and sales – kjones@airlines.org) Annual SPEC2000/e-business user conference mySAP Aerospace & Defense (SPEC2K interface for ATA SPEC2000) SAP Service marketplace - OSS message Xansa – SAP implementation partner (chris.avery@xansa.com)

Thank you for attending! Please remember to complete and return your evaluation form following this session. Session Code: 1303