integration between agile plm and sap 2011-04-04 v1

Confidential RJ Information Consulting

1

PLM2ERP Adapter Functional Overview

April 03, 2011

Confidential RJ Information Consulting 2

•Event based Integration•Publishes Content to external systems

•JMS, HTTP or FTP•Integrated into Agile workflow•Built in Scheduler•All security rules are preserved

AgileContent

JMS, File

HTTP Portal

CustomDatabase application

Content Mgmt

Web service

Oracle Agile PLM Interface Framework

Ex: SAP


Create Part

*Create Change

*Update Costs,

Inventory

Update BOM

Update AML

Agile Content Service

PLM2ERPAdapter

ERP Interface Tables

Agile PLM Product

Collaboration

Agile PLM Product

Collaboration

ERPERP

Agile PLM to SAP

Integration between Agile PLM and SAP - Process

*Note: It is not included in the scope

*SAP to Agile PLM

SAP BAPI/RFC


Integration from Agile PLM to SAP - Data Flow

Agile Product Collaboration

ECO: 1959ECO: 1959PART: 1234-01PART: 1234-01REV: EREV: EOBS: 062997OBS: 062997REV: FREV: FEFF: 070497EFF: 070497

ECO Releasedin Agile database

Agile Content Agile Content ServiceService

Agile Content Agile Content ServiceServicePolls the Agile database

Based on AGILE ECO

Change packet and FTP data to

PLM2ERP dapter

PLM2ERPPLM2ERPAdapterAdapter

XMLXML

BaseTables

ERPPInterface

ConcurrentConcurrent

ProcedureProcedure

SAP ERP

(by customization)


PLM2ERP Adapter Major Features

• Based on Agile AIF integration Framework• Using standard ACS (Agile Content Service)

• Flexible configuration Agile workflows for the Released data• Allow to select or modify workflow and specify the “status” to push the released

data from Agile to SAP• Replicate Profile with template support• Easily to maintain the change without coding modification

• Flexible configuration mapping of SAP tables and fields• Ability to access SAP Interface tables to establish available Configuration

Mappings• Based on the pre-defined rule to assign default or onvert the published value

• Error reporting on communications failures and on transaction successes and failures, • Notification e:mailed to a specified list of receivers

• Support standard SAP Interface


AgileAgilePLMPLM

SAPSAP

aXML FileFolder

Item,BOM,AML

Interface

ColumnMapping.xml

LogTable

SAP

InterfaceTables

Agile Content Server

PLM2ERP Adapter System Architecture PLM2ERP Adapter System Architecture (SAP)(SAP)

Xml ProcessFolder

BackupFolder

PLM2ERP Adapter

Parsing

Manager

Folder

Manager

Import

Manager


Agile to SAP Integration Agile to SAP Integration Item Master Maintain Process FlowItem Master Maintain Process Flow

<ACS>Transfer XML to

Table records

<SAP>scheduling

job

Agile

<SAP>Batch get

data

submit data to SAP table

ZPLM001

Job track

ZPLM001

SAP Temp Table

<SAP>

Update End date/time

Batch start

date/time

BAPI process

<SAP>Check and

create/change material

1. If material existence when creation, perform material update2. If material doesn’t exist, perform material creation

get data

<SAP>Update track

table

PLM DB

SAP Material DB


Agile to SAP Integration Agile to SAP Integration BOM Maintain Process FlowBOM Maintain Process Flow

<ACS>Transfer XML to

Table records

<SAP>scheduling

job

Agile

<SAP>Batch get

data

submit data to SAP table

ZPLM002

Job track

ZPLM002

SAP Temp Table

<SAP>

Update End date/time

Batch start

date/time

BDC process

<SAP>Check and

create/change BOM

1. If BOM existence when creation, perform BOM update2. If BOM doesn’t exist, perform BOM creation

get data

<SAP>Update track

table

PLM DB

SAP Material DB

1. If BOM existence when creation, perform CS02 transaction2. If BOM doesn’t exist, perform CS01 transaction, then CS07 transaction


Sample Interface Tables for Integration from Agile to SAP – Part 1　 Field in Interface Table Mapping Type Mapping Rules

ZPLM001: PartsMaintenance

1. ZCDATE SYSDATE PLM creation date YYYYMMDD

2. ZCTIME SYSDATE PLM creation time HHMMSS

3. ZRDATE VALUE ECN release date YYYYMMDD

4. ZRTIME VALUE ECN release time HHMMSS

5. AENNR VALUE Change Cover Page.Number

6. MATNR VALUE Parts.Title Block.Part Number

7. MBRSH CONSTANT O

8. MTART CONDITION 條件 1. IF (Parts. Title Block.Part Type start with = ‘R’

THEN ‘ROH’

條件 2. IF (Parts. Title Block.Part Type start with = ‘S’

THEN ‘HALB’

條件 3. IF (Parts. Title Block.Part Type start with = ‘F’

THEN ‘FERT’

9. MEINS VALUE Parts.Page Two.Base unit of measure

10. MATKL VALUE Parts.Page Two.Material Group

11. MTPOS CONSTANT ‘NORM’

12. MSTAE CONDITION 條件 1. IF (Parts. Title Block.Lifecycle Phase= ‘暫時核準’

THEN ‘89’

條件 2. IF (Parts. Title Block.Lifecycle Phase = ‘正式核準’

THEN ‘88’

13. SPRAS CONSTANT ZF

14. GROES VALUE Parts.Page Two.Size/Dimensions

15. MAKTX VALUE Parts.Title Block.Description


Sample Interface Tables for Integration from Agile to SAP – Part 2

　 Field in Interface Table Mapping Type Mapping Rules

ZPLM002: ECOControlledBOMMasterMaintenance

1. ZCDATE SYSDATE PLM creation date YYYYMMDD

2. ZCTIME SYSDATE PLM creation time HHMMSS




6. MATNR VALUE Change Orders.Affected Items.Item Number

7. POSNR VALUE Parts.BOM.Find Num(長度為 4 碼 ,不足需補零 )

8. MENGE VALUE Parts.BOM.Qty

9. STLAN CONSTANT 1

10. POSTP CONSTANT L

11. IDNRK VALUE Parts.BOM.Part Number

12. STLAL VALUE Parts.BOM.Alternative Group

13. ALPRF VALUE Parts.BOM.Priority

14. ALPST CONSTANT 1

15. EWAHR VALUE Parts.BOM.Usage %


Sample Interface Tables for Integration from Agile to SAP – Part 3

　 Field in Interface Table Mapping Type Mapping Rules

ZPLM003: ECOControlledItemMasterMaintenance




4. MATNR VALUE Change Orders.Affected Items.Item Number

5. TYPE CONDITION 條件 1. IF Change Orders. Cover Page.ChangeType in (‘BOM Release’,ECN)

THEN ‘B’

條件 2. IF Change Orders. Cover Page.ChangeType = ‘Parts Approval’

THEN ‘P’

integration between agile plm and sap 2011-04-04 v1

Documents

rj information

update end

sample interface

update track

part type

agile content

bom doesnt

number change