October 9, 2013Project: BCS SAP RolloutRICEFW ID : REQ-PTP-191

Functional and Technical Specifications Document

Contents1.System32.General Description32.1.Business use and intended functionality32.2.Technical Infrastructure Design32.3.Application Architecture Design42.4.Other impacted processes/Systems42.5.Critical Objects42.6.Change References53.Detailed Description53.1.Features53.2.Functional rules53.3.Restrictions53.4.Error Conditions63.5.Execution63.6.Interfaces63.7.System Configuration63.8.Security73.9.Data and Conversion requirements73.10.Forms83.11.Screens83.12.Reports83.13.Translation93.14.User Help / Documentation94.Tests and test data95.Development documentation96.APPENDIX - Additional information106.1.Dependecies with other requirments or RICEFW106.2.Verification check list10

5/2/2012Page iDocument Usage Information:This document is designed to encompass both the Functional specifications and Technical specifications. Teams should create the document during the Design phase filling in the functional information and then add to the document the technical information prior to the Build phase. The section which must be filled out for the Functional specification and Technical specification is listed in Section 0.The document and subsequent revisions will be posted on the project Sharepoint environment.

Review / Approval Status

Approval steps NameDateSTATUS

Functional specificationDieter Pompe20.03.2014

Business acceptance of FSMartin Shaw20.03.2014

Technical specificationDieter Pompe

TS review

Estimated effort(MD)

Activity Functional teamTechnical teamTotal

Functional specification

Technical specification

Development

Tests

Totals

Modification History

Index of revisionDate

Description of Modification

1.020.03.2014First Version

SystemThis section is required to be populated as part of the functional specification

This is a summary of the Change due to this project:

Version1.0

EnvironmentSAP EE3

Project IDREQ-PTP-191

GAP ID

Change TypeDEV

Change Category

Business SeverityHigh

Critical ObjectNo

Object ID(s)

General Description

.1. Business use and intended functionalityThis section is required to be populated as part of functional specifications.

2.1.1 Background A global form for BCS is needed

2.1.2 Business utilization Send for each non Production Material a Purchase Order

2.1.3 Development RequirementCopy existing report from ECE for BCS

2.1.4 Required due dates :

SCHEDULE DATESDUE DATE

Due date for test data25.04.2014

Due date for functional test

Due date for completion

Other relevant dates

.2. Technical Infrastructure DesignThis section is required to be populated as part of technical specifications.

< Describe and diagram the infrastructure environment required for this solution. Include all application, database, web, and other servers (including type and Operating System) and associated disk arrays, network elements, and, if applicable, special desktop or handheld devices. Note servers in the DMZ if applicable, and whether an element in the solution communicates outside the firewall or has external network connections. Make special note of any special features, including but not limited to server clusters, virtual servers, SANs or other storage solutions, optical jukeboxes, DNS round-robin routers, non-standard network connections, special hardware such as search appliances, optical scanners, SSL accelerators, and handheld devices. Note if the solution is a single instance, or if there are multiple instances in the same or different locations, and note those locations.

.3. Application Architecture DesignThis section is required to be populated as part of technical specifications.

< Describe and diagram the architectural design of the solution. Include the application tiers (application logic, database, presentation), and show any key third party processes such as application servers/servlet engines and the protocols used for intra-application communication (including encryption, if applicable) and database connectivity technologies to be used. Describe the sign-on and authentication services to be used. Include interfaces to external systems and processes, such as EDI solutions, payment processing, and external vendor systems and processes, and note the technologies used for the integration. Indicate any application frameworks used in building the application, and programming and/or scripting languages used. Note whether the application is entirely interactive, or whether there are batch processing components. Note any assumptions about the environment used for presentation (e.g., specific browser versions).>

.4. Other impacted processes/SystemsThis section is required to be populated as part of the functional specification.

1. List all of the functional and non-functional requirements in a detailed response for impacted systems that will be addressed as part of the overall requirement. >

To ease solution release management, reference other CHANGES in the table below.Author(FS/TS)ReferenceDescriptionFunctional Impact

.5. Critical ObjectsThis section is required to be populated as part of the functional specification.

.6. Change ReferencesThis section is required to be populated as part of the functional specification and may be updated as part of the technical specifications.

ER: Enhancement Request, DR Break/Fix

Detailed DescriptionThe existing form should be replaced by a new none. The Original Program / Form must be copied into a new name for BCS. Copy existing Program ZJMEDPRI. Output message type will be YPH1.This form / program is also used for purchase orders (see other change requests).

Old Document

See Sharepoint REQ-PTP-191_ScheduleRelease_Layout_old.pdf

New Document

See Sharepoint REQ-PTP-191_ScheduleRelease_Layout_new.doc

This document has to be printed in German for german suppliers, or in English for all the others. As it is in the current form from ECE.For future OUCs using SAP, for teh standard text, please insert in the form a condition based on the OUC number instead of 713. 713 has to be considered as one of them. It the standard text is found, then use it for printing, if not print use the one in EN. If not found again, then print nothing.

The address on the header is stored in standard text Y_713_BO_HEADER_1 The bank information at the bottom is in text Y_713_BO_FOOTER_MID1 The address at the bottom is in text Y_713_BO_FOOTER_RIGHT1 The line for VAT Number has to be replaced by the standard text Y_713_BO_HEADER_3 Name, phone number and email under line for scheduler are coming from V_T024D-DISPOV_T024D-DSNAMV_T024D-DSTELV_T024D-USRKEYTo get this material planner, take the material from the first line of the current vendor scheduling agreement release, then in MARC-DISPO. The text before the releases quantities is a standard text Y_713_BO_HEADER_4 in DE or in EN by default. Then comes the list of dates of quantities from the current release. The current release is compared to the previous one (if it exists). P for planned: coming from RM06E-ETSTA in ME38. But it is not mandatory. It may be equal to 1 (firm) 2 (trade-off) or blank. To define the strategy for printing it, then check EKPO-ETFZ1. If this field is empty then print a P when the date of the shipment is over 4 weeks time. If EKPO-ETFZ1 is not empty, print P when field RM06E-ETSTA is empty..1. FeaturesThis section is required to be populated as part of the functional specification

.2. Functional rulesThis section is required to be populated as part of the functional specification

.3. RestrictionsThis section is required to be populated as part of the functional specification

.4. Error ConditionsThis section is required to be populated as part of the functional specification

.5. ExecutionThis section is required to be populated as part of the functional specification

.6. InterfacesThis section is required to be populated as part of the functional specification.Updates and revision by the ABAP team will be done through document versioning.

.7. SecurityThis section is required to be populated as part of the functional specification under the responsibility and execution of TRW.

.8. Data and Conversion requirementsThis section is required to be populated as part of the functional specificationUpdates and revision by the ABAP team will be done through document versioning.

.9. FormsThis section is required to be populated as part of the functional specificationUpdates and revision by the ABAP team will be done through document versioning.

.10. ScreensThis section is required to be populated as part of the functional specificationUpdates and revision by the ABAP team will be done through document versioning.

.11. ReportsThis section is required to be populated as part of the functional specificationUpdates and revision by the ABAP team will be done through document versioning.

Define data selection rules if necessary-Define output mode (printer, text file, EXCEL sheet,)-Specify special template requirementsSpecify the following information wherever applicable:-Any, List, Interactive list, special printing/media requirements:-Output Layout: Portrait/Landscape, columns, sort, page and other breaks, sub-totals, totals General-Attach a form layout. Include field layout, spacing, header/footer details. Indicate whether times should indicate local or system time. Specify paper format and paper size if not indicated in media requirements. Define sort criteria, sum, logo, copy rights, general address or points of contact info,Use the attached recommended template, if appropriate. >

.12. TranslationThis section is required to be populated as part of the functional specification. English language will be used as the default for specification and development. In case translations are required, this will be provided by the business and implemented by the developer.< Identify all the languages in which the program will be used. >

Tests and test dataThis section is required to be populated as part of the functional specification .

Development documentationThis section is required to be populated as part of the technical specification.< In this section will be mentioned HOW the required features have been developed.The topics need to be added: Technologies used(sapscript forms/smartforms ) selection data , algorithm (program logic/ form logic) output, function modules used or developed naming convention used etc (to be completed) >

APPENDIX - Additional information This section is required to be populated as part of the functional specification .

.1. Dependecies with other requirments or RICEFW

requirement idRelated requirements id or ricefw id

.2. Verification check list

NControlOK/NAComment

1General

1.1Error management on functional level is described. (message type, text, pop-up or standard, error log )

1.2Authorization management is described. (Specific, standard .)

1.3The prototype realized for the feasibility study is mentioned.

1.4The difference between standard and specific functionality is clearly defined.

1.5A view of the global process is presented.

1.6Re-use of existing functions or parts of them are indicated.

1.7Table names, BAPIs, user-exits and BADIs to be used are given.

1.8Technical transactions to be used (e.g. SE75 for text id) are indicated.

1.9How the program shall be executed is described (interactive, batch, scheduled)

2Data model

2.1The integration with the existing data model is described.

2.2Table links or keys are given (if applicable/known)

3Forms

3.1The technique to be used, if not standard, is indicated : SAPSCRIPT, SMARTFORMS

3.2The layout is clearly defined (model, field formats - size - alignment, descriptions, rules .)

3.3The display mode is described: puff export, print, display smart form .

3.4The style sheet name to be used is indicated (or indicate if one has to be created)

3.5The breaks to be used are identified and described.

3.6If a logo is to be used, it has been defined.

3.7Other technologies used are described, e. g. for barcode printing

4Interface

4.1The interface type (inbound/outbound) is clearly defined.

4.2The way to launch (scheduled, event driven,) is given.

4.3The volume is indicated (can have an impact on technique and the tests).

4.4The technique to be used is indicated: BAPI, direct input, batch input, message bus or call transaction. If inbound, file creation, IDoc if outbound, operating system environment (Unix, PC) from which the file is to be read/has to be written

4.5File naming convention, if not standard, is given

4.6The file format is known (xml, excel, txt, tab delimited, cave, )

4.7Error management on functional level is specified

4.8type of Commit to be used is indicated (every record, global, )

4.9If the usage of a file server or PC directory is required the mandatory information depending on the file system is defined.

4.10If processing is in background, check: no local files, only server files.

4.11File naming, if not standard, is given; maybe reference to standard/guidelines (If logical files, the paths and names are given).

4.12The log/spool information is described.

4.13All trans codification rules are clearly defined and complete (fields, rules, conditions .).

5Transactional (screens)

5.1ALL screens are defines and the layout is given.

5.2ALL match-codes are correctly identified and described (columns, restrictions on values to be listed, drop-down list or search-help, list of values or selection screen ...)

5.3The use of standard buttons red, yellow, and green arrows is described (data control, confirmation messages, previous screen, return to menu).

5.4Object access management is described (object locks, function modules, when to block and unblock the objects .)

5.5Display rules are clearly described (descriptions, capital letters, date formats, ..)

6Reports

6.1The report type is indicated : list, grid, tree

6.2The goal of the report is defined, such as identified constraints related to its use.

6.3The complete list of all columns (displayed or not) is given and the descriptions used are indicated (short, long, automatic ....).

6.4The status bar to be displayed is described (standard or a specific status with button descriptions).

6.5If lines can be selected the possibilities are described (e.g. single-/multi-selection).

6.6If a hot-spot or double-click is required, it is defined.

6.7If a dynamic display is required it is described.

6.8Default values are given: empty numeric values blank, zero or null; conditions based on those default values are given?

6.9The display format of the data is given

6.10The management rule is given for the multi-value formats.

6.11If printout - printing properties are defined.

6.12The use of long texts and their particularities are defined (display in the ALV, export to Excel .)

6.13If an Excel export is required, the rule is clearly defined.

6.14If color formatting is required, is it described (e.g. table keys in color)

7Tables

7.1The authorization group to be used is defined.

7.2The function group to be used is defined.

7.3Number of screens is specified.

END OF DOCUMENT

Revision History for TemplateVersionDateChange

1October 10, 2013 Original version for BCS SAP Rollout

Stefanini SAPUpdated on: 10-10-21013Author: Veronica DumitrachePage 7 / 17

Interface specification

Note: Field Titles in BOLD require input.

Business AnalystJason Taylor

DescriptionInterface from Amarillo Plant UP05 Longview to Compass - transfer CDMA sales order and sales order text/attributes.

DependenciesCommon solution for ER5176

Data type(s)Sales Order and Sale Order text/attributes

Direction FORMCHECKBOX Inbound FORMCHECKBOX Outbound FORMCHECKBOX Bi-Directional

Sending or Receiving Application FORMCHECKBOX Sending Compass

FORMCHECKBOX Receiving

Anticipated volumeAround 50K records

Frequency FORMCHECKBOX Batch FORMCHECKBOX On Demand FORMCHECKBOX Real Time FORMCHECKBOX Other

File type FORMCHECKBOX BOD (XML) FORMCHECKBOX IDOC FORMCHECKBOX Space Delimited FORMCHECKBOX Tab Delimited

FORMCHECKBOX Other Amarillo send IDoc to EAI, EAI sftp pipe delimited text file to Compass

File namePlease reference to Compass function spec by Michael Smith

Communication method FORMCHECKBOX ALE FORMCHECKBOX Connect:Direct FORMCHECKBOX FTP FORMCHECKBOX XI FORMCHECKBOX WebMethods FORMCHECKBOX Other

Security requirements

Interface control Reports

EAI receive the IDoc from Amarillo, do Data mapping and convert to two text files, The new files should be delimited using a pipe symbol "|" to separate each value of the fields. 1. Sales order

2. Sales order text/attributesReference to Standardized MES formats

File layout (inbound or outbound)

PositionField nameTypeLengthDecimalsDescriptionRequired/Optional (R/O)

Field 1C

Field 2N

Field 3N

Field 4N

Field 5N

Input screen (data mapping)

Transaction

Screen numberField nameInput File Name: Position Field nameCommand

Trigger FORMCHECKBOX Transaction FORMCHECKBOX Script FORMCHECKBOX Manual FORMCHECKBOX Other < If transaction, provide transaction code.if script, provide script name.If manual, provide procedure.If other provide details>

Job performance

Program

Error recovery and Notification process

Other Considerations

Complexity Level FORMCHECKBOX High FORMCHECKBOX Medium FORMCHECKBOX Low

_1442918202.xlsSales order EAI->Compass

Amarillo SAPCompass, PSS

CommentsTabel NameField NameField numberField Desc.Segment NameField NameRequiredEAI Mapping ruleFormatLengthData UsageNotesStandard Segment

HeaderSO Header Text: CSO numberSTXLTDID = Z001CLUSTD1QTC Sales Order NumberE1EDKT1 TDID Z001[]E1EDKT2TDLINEYStraight mappingCHAR10Header text of sales order. First 10 characters.Use FM READ_TEXT with object VBBK, ID Z001, Name = Amarillo SO # with leading 0's.X

ER 5729STXLTDID = Z405CLUSTD2QTC Customer Sales Order SpecE1EDKT1 TDID Z405[]E1EDKT2TDLINEYStraight mappingCHAR7Customer sales order specsee ER05729X

ER 5729STXLTDID = Z405CLUSTD3QTC Customer Sales Order Line NumberE1EDP01[]E1EDPT1,TDID Z405[]E1EDPT2TDLINEYStraight mappingCHAR6Customer sales order line numbersee ER05729X

Item text: ISO number = BP ISO number / line number (10/6 char format)STXLTDID = Z005CLUSTD4BP ISO sales order number and line numberE1EDP01[]E1EDPT1,TDID Z005[]E1EDPT2TDLINEYStraight mappingCHAR1710 char for sales order number, 6 char for line number, 1 char for separator.Use FM READ_TEXT with object VBBP, ID Z005, Name = Amarillo SO # with leading 0's concatenated with item number with leading 0's.X

PO referenceVBKDBSTKD5BP STO numberE1EDK02QUALF 001 BELNRYStraight mappingCHAR35BP STO Number (PO Number)X

Amarillo ISOVBAPVBELN6Amarillo Sales Order NumberE1EDK01BELNRYStraight mappingCHAR10Unique identifier for Amarillo sales orderX

Header text: QTC PO Number (customers PO)STXLTDID = Z003CLUSTD7QTC PO Number (End Customer PO Number to ALU )E1EDKT1 TDID Z003[]E1EDKT2TDLINEYStraight mappingCHAR10Header text of sales order. First 10 characters.Use FM READ_TEXT with object VBBK, ID Z003, Name = Amarillo SO # with leading 0's.X

VBAKAUART8Amarillo Sales Order TypeE1EDK14QUALF 012 ORGIDYStraight mappingCHAR4Defines order type in AmarilloX

VBAKVDATU9Requested Delivery DateE1EDK03IDDAT 002 DATUMYStraight mappingCHAR8Customer requested delivery dateyyyymmddX

VBAKAUDAT10Order DateE1EDK03IDDAT 012 DATUMYStraight mappingCHAR8Document dateyyyymmddX

End customer number partner function PARVW = ZEKNA1NAME111Final Customer /Name 1 of an addressE1EDKA1PARVW ZE NAME1YStraight mappingCHAR40Name of end customerobtain from partner type ZE on Amarillo sales order.X

VBAKLIFSK12Order Header StatusE1EDK01LIFSKYStraight mappingCHAR2Indicator of delivery blockX

VBAKVKBUR13Sales OfficeE1EDK14QUALF 016 ORGIDYStraight mappingCHAR4indicator of sales office (business unit)X

VBAKERDAT14Created OnE1EDK03IDDAT 025 DATUMYStraight mappingCHAR8Date upon which the order was created.yyyymmddX

VBAKAEDAT15Last Changed OnZE1EDK60AEDATYStraight mappingCHAR8Date upon which the order was last changed.yyyymmdd

VBAKVKGRP16Sales GroupE1EDK14QUALF 010 ORGIDYStraight mappingCHAR3Group of sales responsible peopleX

VBAKKVGR117ISO Header ROHS value (Addt. Data A tab)E1EDK35QUALZ 001 CUSADDYStraight mappingCHAR3indicator of RoHS request for sales order header.X

Line itemVBAPPOSNR18Amarillo Sales Order Line NumberE1EDP01POSEXYStraight mappingCHAR6Item number in Amarillo sales documentX

19ATO CodeE1EDP01[]E1EDP35 QUALZ 001?CUSADDYStraight mappingtbdsee ER05729X

20ATO Code additional InformationE1EDP01[]E1EDPT1,TDID ????[]E1EDPT2TDLINEYStraight mappingtbdsee ER05729X

VBAPMATNR21Material NumberE1EDP01[]E1EDP19 QUALF 002IDTNRYStraight mappingCHAR18Material sold to customerX

MAKTMAKTX22Material DescriptionE1EDP01[]E1EDP19 QUALF 002KTEXTYStraight mappingCHAR40Description of materialX

VBAPMATWA23Material EnteredE1EDP01[]ZE1EDP60MATWAYStraight mappingCHAR18Material originally requested by the customer.

VBAPKDMAT24Customer Part NumberE1EDP01[]E1EDP19 QUALF 001IDTNRYStraight mappingCHAR35Customer material numberCan include CLEIX

identify cabinet installed versus loose ship materialMVKEMVGR425Material Group 4E1EDP01[]E1EDP35 QUALZ 004CUSADDYStraight mappingCHAR3X

MARCBESKZ26Make or buy flag - Procurement Type E, F, XE1EDP01[]ZE1EDP60BESKZYStraight mappingCHAR1indicates make / buy / both

VBAPGRKOR27Delivery GroupE1EDP01GRKORYStraight mappingCHAR3indicates items to be delivered togetherX

identifies where the loose ship parts ship from ,Longview or Monterrey,Its used in Compass to know its loose ship or cabinet items.VBAPVSTEL28Shipping PointE1EDP01VSTELYStraight mappingCHAR4identifies where the loose ship parts ship from ,Longview or MonterreyX

VBEPMBDAT29material availability date (confirmed schedule line)E1EDP01[]ZE1EDP60MBDATYStraight mappingCHAR8The date by which sufficient quantities of the item must be available for picking to begin.yyyymmdd

its not confirmed quantityVBAPKWMENG30Order quantityE1EDP01MENGEYStraight mappingNUM10.3Order quantityX

mapping with the delivery documentVBEPD (Structure - calculated field)VSMNG31Delivered quantityE1EDP01[]ZE1EDP61DNQTYYStraight mappingNUM10.3Delivered quantity

VBAPKBMENG32cumulative confirmed quantityE1EDP01[]ZE1EDP60KBMENGYStraight mappingNUM10.3Reservation quantity

MARCSERNP33Master Data Serial ProfileE1EDP01[]ZE1EDP60SERNPYStraight mappingCHAR4indicates material requires serialization

VBAPERDAT34Line item Created dateE1EDK03IDDAT 025 DATUMYStraight mappingCHAR8The date at which the line item was createdX

VBAPAEDAT35Line item Changed on dateE1EDP01[]ZE1EDP60AEDATYStraight mappingCHAR8The date at which the line item was last changedyyyymmdd

multiple line for multiple delivery documentJDo not include cancelled.LIKPVBELN36Delivery Document Number (if a delivery has been created)E1EDP01[]ZE1EDP61DNNUMYMultiple lines in flat file if multiple delivery documents existing for this line item,blank if nothingCHAR10Delivery documentblank if nothing created, yet.

AUSPATWRT37Master Data Cabinet Flag indicator obtain via BAPIE1EDP01[]ZE1EDP60CABINYStraight mappingCHAR1indicator of Cabinet ( C ) vs. Sub-Unit (S) vs. neither (blank)

AUSPATWRT38Master Data ROHS Characteristic ValueE1EDP01[]ZE1EDP60ROHSCYStraight mappingCHAR2indicator of RoHS value of orderable material

38Line Item StatusSplit to row 43-46NLine Status - scheduled status unscheduled, scheduledDelivery completion status partially delivered, fully deliveredCancelled flagged for deletionBlock require OM to spell out different blocksFully blocked for any activityBlocked for shippingBlocked for deliveryBlocked for schedulingNeed OM to complete this.

VBEPD (Structure - calculated field)43Actual Ship DateE1EDP01[]ZE1EDP61ASDATYStraight mappingCHAR8date at which the goods were issued from Amarilloyyyymmdd

use "confirmed qty" field VBEP-BMENG. If this field is populated "not equal" to zero, then line item is scheduled39Scheduled status unscheduled, scheduledE1EDP01[]ZE1EDP60SCHEDYStraight mappingCHAR20

VBUPLFSTA40Delivery completion status partially delivered, fully deliveredE1EDP01[]ZE1EDP60LFSTAYStraight mappingCHAR20

reason for rejectionVBAPABGRU41Cancelled flagged for deletionE1EDP01ABGRUYStraight mappingCHAR20X

ZM and Z1 in AmarilloVBEPLIFSP42BlockE1EDP01[]ZE1EDP60LIFSPYStraight mappingCHAR20

SO attribute EAI->Compass

Amarillo SAPCompass, PSS

CommentsTabel NameField NameField numberField Desc.Segment NameField NameRequiredEAI Mapping ruleFormatLengthData UsageNotes

HeaderSO Header Text: CSO numberSTXLTDID = Z001CLUSTD1QTC Sales Order NumberE1EDKT1 TDID Z001[]E1EDKT2TDLINEYStraight mappingCHAR10Header text of sales order. First 10 characters.Use FM READ_TEXT with object VBBK, ID Z001, Name = Amarillo SO # with leading 0's.

OM ER 5729STXLTDID = Z405CLUSTD2QTC Customer Sales Order SpecE1EDKT1 TDID Z405[]E1EDKT2TDLINEYStraight mappingCHAR7Customer sales order specsee ER05729

OM ER 5729STXLTDID = Z405CLUSTD3QTC Customer Sales Order Line NumberE1EDP01[]E1EDPT1,TDID Z405[]E1EDPT2TDLINEYStraight mappingCHAR6Customer sales order line numbersee ER05729

Item text: ISO number = BP ISO number / line number (10/6 char format)STXLTDID = Z005CLUSTD4BP ISO sales order number and line numberE1EDP01[]E1EDPT1,TDID Z005[]E1EDPT2TDLINEYStraight mappingCHAR1710 char for sales order number, 6 char for line number, 1 char for separator.Use FM READ_TEXT with object VBBP, ID Z005, Name = Amarillo SO # with leading 0's concatenated with item number with leading 0's.

PO referenceVBKDBSTKD5BP STO numberE1EDK02QUALF 001 BELNRYStraight mappingCHAR35BP STO Number (PO Number)

Amarillo ISOVBAPVBELN6Amarillo Sales Order NumberE1EDK01BELNRYStraight mappingCHAR10Unique identifier for Amarillo sales order

Line itemVBAPPOSNR7Amarillo Sales Order Line NumberE1EDP01POSEXYStraight mappingCHAR6Item number in Amarillo sales document

Fixed value8Text Type (Fixed value ATTR)YFixed Value 'ATTR'CHAR4

Calculated value9Text Line Count (eg sequential from 1 to n)E1EDP01[]E1EDPT1,TDID Z411[]E1EDPT2TDLINEYGet the Line count number based on E1EDPT2, one record for each lineNUM3

Item Text (ER 5729)STXHTDID =Z41110TextE1EDP01[]E1EDPT1,TDID Z411[]E1EDPT2TDLINEYStraight mappingCHAR70See ER05729

ZORDERS05 SAP->EAI

Segment NameField NameField Desc.Tabel NameField NameComments

E1EDK01BELNRAmarillo Sales Order NumberVBAPPOSNRAmarillo ISO

E1EDK01LIFSKOrder Header StatusVBAKLIFSKIndicator of delivery block

E1EDK14QUALF 010 ORGIDSales GroupVBAKVKGRP

E1EDK14QUALF 012 ORGIDAmarillo Sales Order TypeVBAKAUARTDefines order type in Amarillo

E1EDK14QUALF 016 ORGIDSales OfficeVBAKVKBURindicator of sales office (business unit)

E1EDK03IDDAT 025 DATUMLine item Created dateVBAPERDAT

E1EDK03IDDAT 002 DATUMRequested Delivery DateVBAKVDATUCustomer requested delivery date

E1EDK03IDDAT 012 DATUMOrder DateVBAKAUDATDocument date

E1EDK03IDDAT 025 DATUMCreated OnVBAKERDATDate upon which the order was created.

E1EDKA1PARVW ZE NAME1Final Customer /Name 1 of an addressKNA1NAME1End customer number partner function PARVW = ZE

E1EDK02QUALF 001 BELNRBP STO numberVBKDBSTKDPO reference

E1EDK35QUALZ 001 CUSADDISO Header ROHS value (Addt. Data A tab)VBAKKVGR1

E1EDKT1 TDID Z001[]E1EDKT2TDLINEQTC Sales Order NumberSTXHTDID = Z001SO Header Text: CSO number

E1EDKT1 TDID Z405[]E1EDKT2TDLINEQTC Customer Sales Order SpecSTXHTDID = Z405OM ER 5729

E1EDKT1 TDID Z003[]E1EDKT2TDLINEQTC PO Number (End Customer PO Number to ALU )STXHTDID = Z003Header text: QTC PO Number (customers PO)

E1EDP01POSEXAmarillo Sales Order Line NumberVBAPPOSNR

E1EDP01GRKORDelivery GroupVBAPGRKOR

E1EDP01VSTELShipping PointVBAPVSTELidentifies where the loose ship parts ship from ,Longview or Monterrey,Its used in Compass to know its loose ship or cabinet items.

E1EDP01MENGEOrder quantityVBAPKWMENG

E1EDP01ABGRUCancelled flagged for deletionVBAPABGRU

E1EDP01[]E1EDP35 QUALZ 001?CUSADDATO CodeVBAPMVGR1?OM ER 5729

E1EDP01[]E1EDP35 QUALZ 004CUSADDMaterial Group 4MVKEMVGR4identify cabinet installed versus loose ship material

E1EDP01[]E1EDPT1,TDID ????[]E1EDPT2TDLINEATO Code additional InformationSTXHTDID =?OM ER 5729

E1EDP01[]E1EDPT1,TDID Z405[]E1EDPT2TDLINEQTC Customer Sales Order Line NumberSTXHTDID = Z405OM ER 5729

E1EDP01[]E1EDPT1,TDID Z005[]E1EDPT2TDLINEBP ISO sales order number and line numberSTXHTDID = Z005Item text: ISO number = BP ISO number / line number (10/6 char format)

E1EDP01[]E1EDPT1,TDID Z411[]E1EDPT2TDLINEAttribute TextSTXHTDID = Z411OM ER 5729

E1EDP01[]E1EDP19 QUALF 002IDTNRMaterial NumberVBAPMATNR

E1EDP01[]E1EDP19 QUALF 002KTEXTMaterial DescriptionVBAPARKTX

E1EDP01[]E1EDP19 QUALF 001IDTNRCustomer Part NumberVBAPKDMAT

ZE1EDK60AEDATLast Changed OnVBAKAEDATDate upon which the order was last changed.

E1EDP01[]ZE1EDP60MATWAMaterial EnteredVBAPMATWA

BESKZMaterial Procurement TypeMARCBESKZ

SERNPMaster Data Serial ProfileMARCSERNP

ROHSCMaster Data ROHS Characteristic ValueAUSPATWRTindicator of RoHS value of orderable material

CABINMaster Data Cabinet Flag indicator obtain via BAPIAUSPATWRTindicator of Cabinet ( C ) vs. Sub-Unit (S) vs. neither (blank)

MBDATmaterial availability date (confirmed schedule line)VBEPMBDAT

KBMENGcumulative confirmed quantityVBAPKBMENGReservation quantity

AEDATLine item Changed on dateVBAPAEDATThe date at which the line item was last changed

SCHEDScheduled status unscheduled, scheduleduse "confirmed qty" field VBEP-BMENG. If this field is populated "not equal" to zero, then line item is scheduled

LFSTADelivery completion status partially delivered, fully deliveredVBUPLFSTA

LIFSPBlockVBEPLIFSP

E1EDP01[]ZE1EDP61DNNUMDelivery Document Number (if a delivery has been created)VBFAVBELNmultiple line for multiple delivery documentJDo not include cancelled.

DNQTYDelivered quantitymapping with the delivery document

ASDATActual Ship DateVBEPD (Structure - calculated field)date at which the goods were issued from Amarillo

ZORDERS05 Segments

ZORDERS05Purchasing/Sales

E1EDK01IDoc: Document header general data

E1EDK14IDoc: Document Header Organizational Data

E1EDK03IDoc: Document header date segment

E1EDK04IDoc: Document header taxes

E1EDK05IDoc: Document header conditions

E1EDKA1IDoc: Document Header Partner Information

E1EDKA3IDoc: Document Header Partner Information Additional Data

E1EDK02IDoc: Document header reference data

E1EDK17IDoc: Document Header Terms of Delivery

E1EDK18IDoc: Document Header Terms of Payment

E1EDK35IDoc: Document Header Additional Data

E1EDK36IDOC: Doc.header payment cards

E1EDKT1IDoc: Document Header Text Identification

E1EDKT2IDoc: Document Header Texts

E1EDP01IDoc: Document Item General Data

E1EDP02IDoc: Document Item Reference Data

E1CUREFCU: Reference order item / instance in configuration

E1ADDI1IDoc: Additionals

E1EDP03IDoc: Document Item Date Segment

E1EDP04IDoc: Document Item Taxes

E1EDP05IDoc: Document Item Conditions

E1EDP20IDoc schedule lines

E1EDPA1IDoc: Doc.item partner information

E1EDP19IDoc: Document Item Object Identification

E1EDPADA&D: Material Exchange

E1EDP17IDoc: Document item terms of delivery

E1EDP18IDoc: Document Item Terms of Payment

E1EDP35IDoc: Document Item Additional Data

E1EDPT1IDoc: Document Item Text Identification

E1EDPT2IDoc: Document Item Texts

E1EDC01SS: Service specifications general data

ZE1EDP60Item additional

ZE1EDP61Item delivery

E1CUCFGCU: Configuration data

E1EDL37Handling unit header

E1EDS01IDoc: Summary segment general

ZE1EDK60Header additional

Directory Creation/Change/Retire Request

Spec ID:

example: ZIFS FIN 0001

ER # / Project

Date:

Request type:

FORMCHECKBOX Create FORMCHECKBOX Change FORMCHECKBOX RetireDescription:

Functional area: Valid functional areas: [ CSM, CSV, DSP, FIN, FLE, MFG, ORD, PDM, PLM, PSM, RPT, SER, SSP]

Interface Directory Name (/intf// is assumed; for example, /fin/zifsfin0001 )/intf// /working . /history sub-directories required

EAI Directory Required: EAI Direction :

[for inbound interfaces /incoming . /working . /history sub-directories required

for outbound interfaces /incoming . /working sub-directories required

SAP System IDs: FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX AD1 AQ1 AP1 AS1

Directory ownersNameEmail Address

Business1. 2.1.2.

Functional1. 2. 1. 2.

Space Quota (Kilobytes)Retention Period (Days)

Main Directory:

Archive Directory:

Main Directory:

30Archive Directory:

30

Additional notesAll fields must be populated.

Directory Request Form

20 Aug 2013

0000000

Instructions#Instructions1To enter the field map, click on the 'Field Map' tab page.2Enter the name (I.e. Vendor Master) in the Data Type.3A comment is inserted on the column heading. To view the comment, just lace the cursor on the column heading. A popup description should be displayed.4To display the SAP program and screen name, click on the menu option in the SAP application screen and select System>Status.5To display SAP field information click the mouse on 'Technical Information'.6The acronym PT (Process Team), LSA (Legacy System Analyst), and CD (ABAP Code Developer) are the group of people should be filling in the columns. These acronyms are just above the column headers.

GuidelinesThis document identifies the columns on the Field Mapping spreadsheet, that are not self-explanatory.Data Type:Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.T-CodeEnter the transaction code.Note Field UseAcceptable values for this field are:R for requiredO for optionalS for suppressedOrg. LevelSpecifies whether the data is client, company or plant related.SAP UsageDescribes how SAP uses the field. You will have to identify if the field is a primary key. (unique key)As Is UsageIf the field usage is different from what SAP has intended for the field, you need to document the existing implementation intention. You'll have to identify the domain for the primary key.The characteristic of the differences must be listed here in full.Project UsageIf the field usage is different from what SAP has intended for the field, you need to document the future implementation intention(ongoing project).You'll have to identify the domain for the primary key.ERP Best PracticeDescribes the ERP practice if any.The following columns are required to be REVIEWED by the legacy IS/IT.Conversion/Editing Logic:Enter any logic to be followed by the conversion developer, such as: Handling of field lengths that are not equal, default values to use if the legacy field is empty or not valid,legacy fields to be used in conversion that do not directly map to SAP fields. Please refer to list of values if any.Conversion/Mapping Rule:Enter one of the following conversion rule:R0 - System Generated.R1 - Fill with Legacy's system.R2 - Fill with default, select value based on conversion logic.R3 - Fill with Legacy if available, else fill with default.R4 - Fill from prior screen.R9 - No Conversion. Manual online entry post go-live.If you do not know yet what rule to put in, leave this column blank.Data Cleansing Activities:Enter any specific data cleansing activities, that you planned/required to carry out for this field. e.g. Postal Codes, not aligned to standard SAP/country format, Descriptions not consistent with Bombardiers, standard etc.Legacy System:Enter the name of the legacy system, from which this legacy field will be extracted. i.e. Source system for the field.Source Screen or Program Name or ID:Enter the name or ID of the legacy screen, report or other output you are using to identify this legacy field.Source Field Name:Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Source Table Name:Enter the name or ID of the legacy system table or file where this field is located.Source Field Format:Enter the data format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format e.g. dd/mm/yyy)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any decimal, hyphens, slashes, spaces, etc.)Source Field Length:Enter the exact number of characters allowed for this field on the source table or file.

SAP Field MAPData Type: [Data Concept]SAP FIELDSDATA CONVERSION/EDITING LOGICDATA CLEANSINGLEGACY SYSTEM FIELDSPTPTPTPTPTPTPTPTPTPTPTPTPTLSALSALSALSALSALSAField DataData Element InformationNo. ofNoteERPConversion/EditingConversion/DataLegacySource/DestinationSource/DestinationSource/DestinationSource/DestinationSource/DestinationTableFieldShort TextDataNo. ofDecimalFieldOrg.SAPAs IsProjectBestLogicMappingCleansingSystemScreen or ProgramTableFieldFieldFieldNameNameTypeChar'sPlacesUseLevelUsageUsageUsagePracticesRuleActivitiesName or IDNameNameFormatLengthTransaction Code:[Data Concept] Create: Initial Screen[Data Concept] Create: HeaderDocument HistoryCreated By:Date Created:Reviewed By:Date Reviewed:Approved By:Date approved:Modification HistoryDate ModifiedRev#Modified ByBrief Description of change

&LField MapProject BMIS&L&F&CPage &P&R&DProcess Team memberProcess Team memberProcess Team memberProcess Team memberProcess Team memberBombardier:Enter number of decimal places for numeric fields only.Process Team memberBombardier:Enter default value.Process Team memberProcess Team memberProcess Team memberProcess Team memberLegacy Systems AnalystLegacy Systems AnalystLegacy System AnalystLegacy System AnalystLegacy System AnalystGo to screen in SAP.Highlight field.Press F1 or click on Help to open.Enter table name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 or click Help to open.Enter field name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 or click Help to open.Highlight data element in Help screen, double click to open.Enter short text from data element screen.Go to screen in SAP.Highlight field.Press F1 or click on Help to open.Highlight data element, double click to open.Enter data type from data element screen.Go to screen in SAP.Highlight field.Press F1 or click on Help to open.Highlight data element, double click to open.Enter No. of characters from data element screen.Bombardier:The number of decimal places required for a numeric data type field.Acceptable values for this cell are:S - SuppressR - Required entryO - Optional entryBombardier:Specify whether the data is Company, Client, or Plant related.Bombardier:In summary, describe how SAP system uses the field.

In many cases, you can cut and paste the help description for the field from SAP system.Bombardier:If the field usage is different from what SAP has intended for the field, you need to document the existing implementation intention.The characteristic of the differences must be listed here in full.Enter any logic to be followed by the conversion developer, such as:how to handle field lengths that are not equalwhat default value to use if the legacy field is empty or not valid.legacy fields to be used in conversion that do not directly map to SAP fields.Enter one of the following conversion rule:R0 - System Generated.R1 - Fill with Legacy's system.R2 - Fill with default, select value based on conversion logic.R3 - Fill with Legacy if available, else fill with default.R4 - Fill from prior screen.R9 - No Conversion. Manual online entry post go-live. If you do not know yet what rule to put in, leave this column blank.Enter the name or ID of the legacy screen, report or other output you are using to identify this legacy field.Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Enter the name or ID of the legacy system table or file where this field is located.Enter the format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any hyphens, slashes, spaces, etc.)Enter the exact number of characters allowed for this field on the source/destination table or file.Process Team memberBombardier:If the field usage is different from what SAP has intended for the field, you need to document the future implementation intention.The characteristic of the differences must be listed here in full.Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.

LOGO

FORWARDING ADVICE n XXXXX

AVIS DEXPEDITION du jj-mm-aaaa Loading scheduled on: jj-mm-aaaa XXXXXXXXXXXXXXXX tlphone : +XX X XX XX XX

56, rue Clmenceau BP 19 tlcopie : +XX X XX XX XX

XXXXXXXXXXxxx Cedex France N SIRET : XXXXXXXXXXX

Adresse Factur L1

Adresse Factur L2

1rst delivery address / 1re adresse de livraison

Adresse Factur L3

Adresse Liv. L1

Adresse Factur L4

Adresse Liv. L2

Adresse Liv. L3

Adresse Liv. L4

Adresse Liv. L5

Adresse Liv. L6

Delivery to / Livraison ladresse de

Adresse DO L1

Adresse DO L2

Adresse DO L3

Adresse DO L4

Adresse DO L5

Adresse DO L6

Dispatch/Expdition

Delivery terms/Cond. livraison

COND LIV 1

COND LIV 2

COND LIV 3

PAGE: 1/2

Your ref.

Our ref.

N

Description/Description

Bundle

Weight/Poids

Colis gross/brut net/net

AEMG Autorisation dExportation Matriel de Guerre

CREDOC

KG KG

LBS

BUNDLE N

GRADE (S): ASTM 904 L

Xxx/xx

1 PLATE (S)

YOUR REF. : xxxxxxxxxxxx

2200.00 MM x 80000.00 MM x 16.0000 MM

HEAT J1471 N xxxxxx ( 1 )

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

LOGO

FORWARDING ADVICE n XXXXX

AVIS DEXPEDITION du jj-mm-aaaa

Loading scheduled on: jj-mm-aaaa

XXXXXXXXXXXXXX tlphone : +XX X XX XX XX XX

56, rue Clmenceau BP 19 tlcopie : + XX X XX XX XX XX

XXXXXXXXXXXX Cedex France N SIRET : XXXXXXXXXX

PAGE: 2/2

Your ref.

Our ref.

N

Description/Description

Bundle

Weight/Poids

Colis gross/brut net/net

KG KG

LBS

CARRY FORWARD XXXX XXXX

BUNDLE N

XXXXX XXXX

Xxx/xx

1 PLATE (S)

XXXX

XXXX

YOUR REF. : xxxxxxxxxxxx

2200.00 MM x 80000.00 MM x 16.0000 MM

HEAT J1471 N xxxxxx ( 1 )

TOTALS

---------------------------------------------------------------

XXXXXXXXXX

XXXXX

Texte Marquage L1

Texte Marquage L2

Texte Marquage L3

Texte Marquage L4

Please fill corresponding data rules for every point related in the form layout

Also indicate where you want the underline or boxes to appear in the layout.

When you need special display, for text element for example, give details in order to avoid multiple changes during or after development.

For quantity and currency values precise clearly their unit and the output format (separator , )

A table to be added in which elements are specified.

3

4

5

1

LOGOO

2

5 ter

5 bis

TITRE

7

6

8

ADR_SOCIETE

ADR_FACT

9

10

17

ADR_LIVR1

11

Name of the window

48

ADR_LIVR2

48

bis

12

TRANSPORT

13

PAGE

14

15

REFERENCE

COND_LIVR

22

16

20

19

21

18

26

23

25

24

27

54

49

50

UNIT

31

30

32

29

52

28

33

37

35

38

36

53

39

34

ITEM

MAIN

FOOTER

REPORT

56

55

TOTAL

40

41

42

43

44

45

51

MARQUAGE

46

Screen layout template

When a new transaction is created its important to know the global screen logic flow. Please provide one as shown in example:

For each Screen , please give details on :

Screen Field Mapping:

Field #Field Desc.Field Type SAP Reference FieldScreen Field LengthInput/Output FieldMandatory/OptionalDefault valuesLast Entered value required (Y/N)Match codes used (if any)Other formatting requirements

Other formatting requirements left or right justification, padding requirements, visible/invisible, bright, etc.

(necessary field validations and sorting logic, if any)

Processing Functionality

Pre-screen display processing:

Screen processing:

Post-screen display processing:

Screen 1

Screen 2

Screen 3

Screen 4

Screen 5

Buttons to be created and their behaviour

Fields to be displayed with their related description ,if a label is needed , if its only displayed or changeable and their position in the screen

Table controls if needed

Report Design Specifications

Report Name

Report Description

Report Invocation Method

Report Application

Report Type

Report Classification

Report Medium

Report Frequency

Report Request Method

Report Timing

Variant NameParameter NameParameter ValueParameter Description

Report Layout

Report Field NameLogical Data Base / TableField NameComputation / Edit Rule

Sort By Report Field NameSort By (ascending, descending)