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

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

3. 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)

4. Overview

5. SPEC2000 vs. Total Orders

6. ATA SPEC2000 Chapters 3 & 4

7. 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

8. S1BOOKED Record Format

9. IDoc Segments

10. IDoc List – WE02

11. 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)

12. 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.

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

14. 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”

15. 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

16. 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?!

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

18. 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.)

19. 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

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

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