Oracle Toolkit to Fix Your Automotive EDI NeedsMukesh Rao Uppadashaping tomorrow with youAbstract:Electronic Data Interchange (EDI) is the standard usedworldwide to exchange business documents betweenorganizations in the most effective way. The EDI specific needsvary for every customer especially in the Automotive Industry.To cater to these diverse Customer specific requirements,Organizations largely customize their processes resulting inhighly customized Enterprise Application. Maintenance of thesecustomizations is not a simple job and Organizations have tokeep spending a lot of resources just to maintain these. Overand above that, whenever the Enterprise Application providerlike Oracle, comes up with a major release, there is an overheadof checking the compatibility of these customizations.Understanding the concerns of its Customers, to manage theirCustomer EDI needs, Oracle provides a toolkit to fix AutomotiveEDI needs. Oracle’s Automotive Trading Partner (TP) toolkithelps to manage the TP specific customizations separate fromthe Base product without being affected by the futureminor/major releases.

Need for Enterprise Applications with EDI capabilitiesFor Companies, to stay ahead of their competitors, a robust, flexible andscalable IT infrastructure is indispensable. Enterprise applications provideorganizations a competitive edge and certainly a greater Return onInvestment (ROI). EDI is rampant in the Automotive Industry to manage theJust-in-time (JIT) requirements accurately and effectively. Companies sendthe EDI demand to various suppliers and it becomes the onus of eachsupplier to consider the aspects important for itself in a way which helpsthe particular supplier to fulfill the demand most effectively. These aspectscan be but not limited to: Past-Due Firm Demand Pull Reference Number Purchase Orders (850s) processed by supplier as Shipping Schedules(862s) Retaining Forecast from previous Customer Schedules Considering Request Date changes between two schedules havingsame Matching AttributesDue to the nature of the EDI requirements, which is very Customer specific,Organizations are looking for enterprise applications which can cater to it.Oracle E-Business Suite is closely integrated with EDI using the modules: Oracle e-Commerce Gateway Oracle Release Management (RLM)It provides many functional tools to handle Customer/TP mandates:E-Commerce Gateway Transaction TemplatesWith Oracle e-Commerce Gateway, Organizations can generate uniqueinbound and outbound templates for transactions to accommodateadditional trading partner data, such as flexfields. It can capture andpublish this additional data to a translator.

TranslatorsEven though it doesn’t come under Oracle’s umbrella, translators offer robustmapping tools that let you map trading partner specific transaction formatsinto Oracle e-Commerce Gateway. Changes to a trading partner file formatmay simply require a change in a translator mapping.E-Commerce Gateway Code ConversionsThe Oracle e-Commerce Gateway lets you define code conversion values fordata elements, so you can transform trading partner data into your ownapplication data. You can establish trading partner values and automaticallytransform inbound and outbound data to reflect this conversion.Trading Partner FlexfieldsAs part of Oracle Automotive Trading Partner Toolkit, you can add newattributes in Oracle Release Management, Order Management and ShippingExecution to accommodate trading partner specific attributes. These productshave added additional columns in key tables, reserved for trading partnerflexfields. You can seed appropriate values for each trading partner and useOracle Applications flexfield technology to view these attributes from theappropriate forms.Trading Partner LayersOracle additionally offers a very useful toolkit “Automotive Trading Partner(TP) Toolkit” to handle Trading Partner (Customer/Supplier/Bank/Others)specific requirements. In Oracle Release Management and Oracle Shipping,you can adapt “published” code so that it processes according to specificrequirements without impacting the processing for other trading partners. Youcan create custom procedures, then identify and register a group ofprocedures as a layer. In this way, you can build trading partner libraries intrading partner-enabled forms in Oracle Release Management and OracleShipping Execution.

Oracle Automotive Trading Partner ToolkitTo manage the customer-wise process changes in application, which cannotbe fulfilled by the Oracle EDI Extensible Architecture, Oracle provides andendorses the Automotive Trading Partner (TP) Toolkit.How it worksThe toolkit helps manage the customer specific custom code separatelyfrom the seeded code. It acts like a multi-output switch, based on theincoming EDI demand, it decides whether to process it using custom code(specific to individual Customer) or the generic/seeded code. Let usconsider a program unit, say “Validate EDI” which validates the type of EDItransaction. The Oracle seeded flow is:When Automotive TP toolkit is introduced and EDI demand for a TradingPartner say “XYZ” is processed then the new flow checks for the TP forwhich the particular EDI is being processed and based on the TP the flow isdecided:

Benefits Automotive Trading Partner (TP) Toolkit helps to develop, add andmaintain TP specific customizations in the most effective andorganized way. It helps the Organization with their various TP specific customizationsto be at one place. Need not develop individual customizations fromscratch rather the common steps to develop TP layers are to beperformed just once hence requires less time and reducesredundancy. It is Oracle’s product which is closely integrated to Oracle ReleaseManagement (RLM) and Shipping (WSH) hence highly recommendedand related support is provided. Not affected by future Oracle releases/patches.References Automotive TP Toolkit User’s Guide 01/acrobat/115veaug.pdf