Business Integrator - External System Integration Analysis

Business Integrator - External SystemIntegration Analysis

DELMIA Apriso 2019 Technical Guide

®2018

DassaultSystèmes.Apriso,3D

EXPE

RIENCE,theCom

pass

logo

andthe3D

Slogo,C

ATIA,SOLIDWORKS

,ENOVIA,DELMIA,SIMULIA,GEO

VIA,EX

ALEA

D,3DVIA,BIOVIA,NET

VIBE

S,and3D

XCITE

arecommercialtrademarks

orregistered

trademarks

ofDassaultSystèmes

orits

subsidiariesintheU.S.and/orothercountries.Allothertrademarks

areow

nedby

theirrespectiveow

ners.

Use

ofanyDassaultSystèmes

orits

subsidiariestrademarks

issubjecttotheirexpress

writtenapproval.

Contents1 Introduction 51.1 Purpose 51.2 Scope 51.3 Intended Audience 51.4 Online Schema and Mapping Documents 5

2 Inbound (External System to DELMIA Apriso) 72.1 Perform the ALE (Application Link Enabling) Configuration 72.2 Material Master – SAP ECC 72.2.1 IDoc and Segments Details 72.2.2 Special Mapping Requirements 72.2.3 Download Instructions 9

2.3 Material Master – SAP ECC 92.3.1 IDoc and Segments Details 92.3.2 Special Mapping Requirements 92.3.3 Download Instructions 9

2.4 Work Center – SAP ECC 92.4.1 IDoc and Segments Details 102.4.2 Special Mapping Requirements 102.4.3 Download Instructions 10

2.5 Cost Center – SAP ECC 102.5.1 IDoc and Segments Details 112.5.2 Special Mapping Requirements 112.5.3 Download Instructions 11

2.6 Customer Masters – SAP ECC 112.6.1 IDoc and Segments Details 112.6.2 Special Mapping Requirements 112.6.3 Download Instructions 12

2.7 Vendor Masters and Carrier Masters – SAP ECC 122.7.1 IDoc and Segments Details 122.7.2 Special Mapping Requirements 122.7.3 Download Instructions 12

2.8 Employee Master – SAP ECC 122.8.1 IDoc and Segments Details 132.8.2 Special Mapping Requirements 132.8.3 Download Instructions 13

2.9 Bill of Materials – SAP ECC 132.9.1 IDoc and Segments Details 132.9.2 Special Mapping Requirements 142.9.3 Download Instructions 14

2.10 Bill of Materials – SAP ECC 14

Business Integrator - External System Integration Analysis | DELMIA Apriso 2019 2

2.10.1 IDoc and Segments Details 142.10.2 Download Instructions 15

2.11 Project/WBS Element – SAP ECC 152.11.1 IDoc and Segments Details 152.11.2 Special Mapping Requirements 152.11.3 Download Instructions 15

2.12 Production Orders – SAP ECC 152.12.1 IDoc and Segments Details 162.12.2 Special Mapping Requirements 162.12.3 Download Instructions 17

2.13 Maintenance Orders – SAP ECC 172.13.1 Special Mapping Requirements 18

2.14 Purchase Orders – SAP ECC 182.14.1 IDoc and Segments Details 182.14.2 Special Mapping Requirements 182.14.3 Download Instructions 18

2.15 Delivery Orders & Customer Return Delivery Orders – SAP ECC 192.15.1 IDoc and Segments Details 192.15.2 Download Instructions 19

2.16 Advanced Shipment Notification (ASN) Orders – SAP ECC 192.16.1 IDoc and Segments Details 202.16.2 Special Mapping Requirements 202.16.3 Download Instructions 20

2.17 Sales Orders – SAP ECC 202.17.1 IDoc and Segments Details 212.17.2 Special Mapping Requirements 212.17.3 Download Instructions 21

2.18 Shipment Orders – SAP ECC 212.18.1 IDoc and Segments Details 222.18.2 Special Mapping Requirements 222.18.3 Download Instructions 22

3 Outbound (DELMIA Apriso to External System) 233.1 Common Mapping Requirements 243.1.1 SAP Movement Types 243.1.2 Mapping EDI_DC40 for SAP ECC 25

3.2 Production Confirmations 263.2.1 IDoc and Segments Details 263.2.2 Production Confirmation Interfaces 26

3.3 Plant Maintenance Order Confirmations 283.3.1 IDoc and Segments Details 283.3.2 Special Instructions for Configuring the External System 283.3.3 Plant Maintenance Order Confirmation Interfaces 29


3.4 Inventory Confirmations Using the MBGMCR02 Interface for Move and Adjust 293.4.1 IDoc and Segments Details 293.4.2 Special Requirements 303.4.3 Special Instructions for Configuring the External System 303.4.4 Inventory Confirmations Interfaces 30

3.5 Goods Receipt 333.5.1 IDoc and Segments Details 333.5.2 Special Requirements 343.5.3 Special Instructions for Configuring the External System 393.5.4 Goods Receipt Interfaces 39

3.6 Delivery Orders Confirmation 413.6.1 IDoc and Segments Details 413.6.2 Possible Values for the Qualifier 413.6.3 Special Instructions for Configuring the External System 413.6.4 Inventory Confirmations Interfaces 423.6.5 SAP ECC – Delivery Orders Goods Receipt 44

3.7 Shipment Confirmations 453.7.1 IDoc and Segments Details 453.7.2 Possible Values 453.7.3 Special Instructions for Configuring the External System 463.7.4 IDoc and Segments Details 463.7.5 Special Instructions for Configuring the External System 463.7.6 SAP ECC – Create Sales Order 49

3.8 Create Purchase Requisition 503.8.1 IDoc and Segments Details 503.8.2 Special Instructions for Configuring the External System 513.8.3 SAP ECC – Create Purchase Requisition 513.8.4 SAP ECC – Template 51

4 BAPI Interface 524.1 Quality Inspection 52

5 References 55

FiguresFigure 1 DELMIA Apriso XML Schema Repository Documentation 6Figure 2 SAP – inbound process code 47Figure 3 SAP – logical Message 48Figure 4 SAP – inbound parameters 48Figure 5 SAP – IDoc: assignment of FM to log, message, and IDoc type 49Figure 6 SAP – Business Connector 49


1 Introduction1.1 PurposeThe purpose of this Technical Guide is to document the names of the XML schemas that are necessary for DELMIA Apriso to integrate with external systems (SAP) using DELMIA Apriso Business Integrator.

1.2 ScopeThe scope of this document describes the following:

All the standard mappings provided by DELMIA Apriso for SAP IDocs and BAPIEach mapping section specifies:

The from and to schema namesThe required segmentThe mapping nameThe special mapping requirements for a SAP segmentThe mapping logicThe SAP download instructions

1.3 Intended AudienceThis document is intended for people who perform analysis on the interfaces between DELMIA Apriso and the external system.

1.4 Online Schema and Mapping DocumentsAll the standard schemas and mapping documents are available in the HTML form accessible from the DELMIA Apriso Start page. Login is required to view the documents.

These HTML documents are organized in the same subfolder structure as Schema Repository.


Figure 1 DELMIA Apriso XML Schema Repository Documentation


2 Inbound (External System to DELMIA Apriso)2.1 Perform the ALE (Application Link Enabling) Configuration

2.2 Material Master – SAP ECC

External XML Schema Name MATMAS04.xsdDELMIA Apriso XML Schema name FlexNet_Products.xsd

Mapforce project name map_MATMAS04_FlexNet_Products.mfd

XSLT mapping name map_MATMAS04_FlexNet_Products.xslt

2.2.1 IDoc and Segments Details

Message Type MATMASIDoc type MATMAS04Required segment Optional segment

2.2.2 Special Mapping Requirements

The following table lists the Material Type and Product Inventory Type Value Conversion mappings.

SAP Material Type (MTART)

Description (MTBEZ) DELMIA Apriso (Product Inventory Type)

CONT Kanban containers 1COUP Coupons n/aDIEN Services n/aERSA Spare parts 5FERT Finished products 8FFFC Form-Fit-Function class n/aFGTR Beverages 8FHMI Prod. resources/tools 8FOOD Foods (excl.

perishables)8


FRIP Perishables 8HALB Semi-finished products 8HAWA Trading goods 8HERB Interchangeable part 8HERS Manufacturer parts 8HIBE Operating supplies n/aIBAU Maintenance

assemblies5

INTR Intra materials 8KMAT Configurable materials 8LEER Empties n/aLEIH Returnable packaging 1LGUT Empties (retail) n/aMODE Apparel (seasonal) 8NLAG Non-stock materials 6NOF1 Non-foods 8PIPE Pipeline materials 9PROC Process materials 8PROD Product groups n/aROH Raw materials 8UNBW Non-valuated materials 6VEHI Vehicle config. n/aVERP Packaging 2VKHM Additionals n/aVOLL Full products n/aVVGR Competitor product n/aWERB Product catalogs n/aWERT Value-only materials n/aWETT Competitor products n/a

The following table lists all of the mapping logic:

IDoc Field DescriptionE1MARAM/LVORM Active/Delete indicator

If LVORM = ‘X’, then Active = ‘0’; otherwise, Active = ‘1’E1MARCM/ XCHPF SAP Batch management requirement indicator (X = Yes)

If ‘X’, then 4 (Delivery, Issue and Receipt); otherwise, 0 (None)


Not used: 1 (Delivery), 2 (Issue), and 3 (Delivery) (EP1)E1MARCM/ SERNP SAP Serial control value ‘XXXX’

If Exist, then 4 (Delivery, Issue and Receipt); otherwise, 0 (None)Not used: 1 (Delivery), 2 (Issue), and 3 (Delivery) (EP1)

E1MARCM/ INSMK SAP Quality Indicator (X = Yes)If ‘X’, then 1 (Yes); otherwise, 0 (No) (EP1)

2.2.3 Download Instructions

1. Perform the necessary ALE configuration. For details, refer to 2.1 Perform the ALE (Application Link Enabling) Configuration.

2. Execute the BD10 transaction in SAP and specify the following parameters:The single material number or rangeThe class (left blank)The message type (MATMAS)The logical system name (the name of the external system)

2.3 Material Master – SAP ECC

External XML Schema Name MATMAS05.xsdDELMIA Apriso XML Schema name FlexNet_Products.xsd

Mapforce project name map_MATMAS05_FlexNet_Products.mfd

XSLT mapping name map_MATMAS05_FlexNet_Products.xslt


Message Type MATMASIDoc type MATMAS05Required segment Optional segment


The same as 4.6C in section 2.2.2 Special Mapping Requirements.


The same as 4.6C in section 2.2.3 Download Instructions.

2.4 Work Center – SAP ECCIt is not possible to download the Cost Center along with a standard IDoc. Therefore, the user exit is used to populate the Cost Center along with the standard IDoc that populates the Cost


Center assigned to that Work Center.

External XML Schema Name LOIWCS02.xsdDELMIA Apriso XML Schema name FlexNet_WorkCenters.xsd

Mapforce project name map_LOIWCS02_FlexNet_WorkCenters.mfd

XSLT mapping name map_LOIWCS02_FlexNet_WorkCenters.xslt


Message Type DESADV IDoc type LOIWCS02Required segment Optional segment


None.



2. Execute the POIM transaction for downloading the Work Centers from SAP. 3. Specify the following parameters:

Optimization System – FLEXNET (the name of the external logical system)Go to the WorkCenter tab and select the WORKCENTERS FOR radio buttonEnter the Work Center (From and To)Enter the Plant Number (From and To)Execute the Cost Centers

2.5 Cost Center – SAP ECCIt is possible to download the Cost Center using a standard IDoc. However, in SAP, Cost Centers are not linked directly to plants. Instead, they are linked to the company code through the controlling area.

External XML Schema Name COSMAS01.xsdDELMIA Apriso XML Schema name FlexNet_Departments.xsd

Mapforce project name map_COSMAS01_FlexNet_Departments_AndCostCenters.mfd

XSLT mapping name map_COSMAS01_FlexNet_Departments_AndCostCenters.mfd



Message Type DESADV IDoc type DELVRY03Required segment Optional segment


None.



2. To download, execute the BD16 transaction in SAP by specifying the following parameters:Controlling area ()Cost Center (From and To)Message type (COSMAS)Target system (the name of the external system)

3. To initially populate the DELMIA Apriso tables, a scheduled job is not required. Simply run the BD16 transaction manually

4. A batch job can be scheduled to run at a specified interval after the initial download.

2.6 Customer Masters – SAP ECC

External XML Schema Name DEBMAS03.dtdDELMIA Apriso XML Schema name FlexNet_Partners.xsd

Mapforce project name map_DEBMAS03_FlexNet_Partners_Customers.mfd

XSLT mapping name map_DEBMAS03_FlexNet_Partners_Customers.xslt


Message Type DEBMASIDoc type DEBMAS03Required segment Optional segment


None.




2. Go to the BD12 transaction and specify the following parameters:The single customer number or rangeThe class (left blank)The message type (DEBMAS)The logical system name (the name of the external system)The execute transaction

2.7 Vendor Masters and Carrier Masters – SAP ECCFor FlexNet/DELMIA Apriso versions 9.0 and above.

External XML Schema Name CREMAS03.dtdDELMIA Apriso XML Schema name FlexNet_Partners.xsd

Mapforce project name map_CREMAS03_FlexNet_Partners_VendorsAndCarriers.mfd

XSLT mapping name map_CREMAS03_FlexNet_Partners_VendorsAndCarriers.xslt


Message type CREMASIDoc type CREMAS03Required segment Optional segment


None.



2. Execute the BD14 transaction by specifying the following parameters:The single vendor number or rangeThe class (left blank)The message type (CREMAS)The logical system name (the name of the external system)

2.8 Employee Master – SAP ECCFor FlexNet/DELMIA Apriso versions 9.1 and above.


External XML Schema Name HRMD_A01DELMIA Apriso XML Schema name FlexNet_EmployeesMapforce project name map_HRMDA01_FlexNet_Employees.mfd

XSLT mapping name map_HRMDA01_FlexNet_Employees.xslt


Message Type HRMD_A IDoc type HRMD_A01Required segment Optional segment


None.



2. IDoc is triggered in a batch by running the employee download transaction (not in real-time) 3. The download of the employee takes place when the PFAL transaction is executed 4. To generate the IDoc, follow these steps:

a. Go to the PFAL transaction. b. Enter the following values on the selection screen:

Message Type – HRMD_AReceiver Partner No – <name of the logical system assigned for the external system>

c. Execute.

2.9 Bill of Materials – SAP ECCFor FlexNet/DELMIA Apriso versions 9.3 and above.

External XML Schema Name BOMMAT03.xsdDELMIA Apriso XML Schema name FlexNet_BillOfMaterials.xsd

Mapforce project name map_BOMMAT03_FlexNet_BillOfMaterials.mfd

XSLT mapping name map_BOMMAT03_FlexNet_BillOfMaterials.xslt


Message Type BOMMAT IDoc type BOMMAT03


Required segment Optional segment


None.



2. IDoc is triggered in a batch by running the BOM download transaction (not in real-time). 3. The download of the BOM takes place when the BD30 transaction is executed. 4. To generate the IDoc, follow these steps:

a. Go to the BD30 transaction. b. Enter the following values on the selection screen:

Material – <name of the parent material>Plant – <plant number>BOM Usage – 1Alternative BOM – (optional)Valid From – defaulted to current dateIgnore Distribution Box – (unchecked)Message Type – BOMMATMessage Code – CRELogical System – <name of the logical system assigned for the external system>

c. Execute.

2.10 Bill of Materials – SAP ECCFor FlexNet/DELMIA Apriso versions 9.3 and above.

External XML Schema Name BOMMAT04.xsdDELMIA Apriso XML Schema name FlexNet_BillOfMaterials.xsd

Mapforce project name map_BOMMAT04_FlexNet_BillOfMaterials.mfd

XSLT mapping name map_BOMMAT04_FlexNet_BillOfMaterials.xslt


Message Type BOMMAT IDoc type BOMMAT04Required segment Optional segment



Same as 4.6C.

2.11 Project/WBS Element – SAP ECCFor FlexNet versions 9.0 EP1 and above.

External XML Schema Name PROJECT01.xsdDELMIA Apriso XML Schema name FlexNet_Project.xsd

Mapforce project name map_PROJECT01_FlexNet_Project.mfd

XSLT mapping name map_PROJECT01_FlexNet_Project.xslt


Message Type PROJECTIDoc type PROJECT01Required segment Optional segment


None.


Not available.

2.12 Production Orders – SAP ECCThe production orders download includes components, lot numbers, and serial numbers for FlexNet/DELMIA Apriso versions 9.0 and above.

External XML Schema Name ZOIPRO01.dtdDELMIA Apriso XML Schema name

FlexNet_Production_PlantMaintenance_Orders.xsd

Mapforce project name map_ZOIPRO01_FlexNet_Production_PlantMaintenance_Orders.mfd

XSLT mapping name map_ZOIPRO01_FlexNet_Production_PlantMaintenance_Orders.xslt



Message type LOIPRO IDoc type ZOIPRO01Required segment Optional segment


The following is a list of all the valid job action types. For downloads that require order explosion, create a job XML that validates against JobCreationEvent.xsd and use the job action type 26.

Valid Job

Action Type

Description

1 Invoke Standard Operation2 Print Report3 Print Label4 Reprint5 Invoke Stored Procedure14 Invoke Task15 Invoke Business Component16 Publish WFM Message17 PB – Batch Release18 PB – Batch Propagate20 Invoke Background Clock In21 Invoke Background Clock Out22 Invoke Background Begin Recess23 Invoke Background End Recess24 Invoke Background Auto Clock Out25 Invoke Background Auto Start Indirect26 Invoke Explosion 27 Process Background Task28 Invoke Disposition Test Explosion32 Invoke Background Navigation

The following list highlights the IDoc field descriptions and the possible requirements.


IDoc Field DescriptionZ2HEAD/ORDNUM Trim lead zeroes if numeric.Z2HEAD/ORDTYP ‘N’ = regular production orders.Z2OPER/STDVAL1 Standard rate (for each Operation).Z2OPER/STDVAL2 Standard value for labor (for each Operation).Z2OPER/STDVAL3 Standard value for setup labor (for each Operation).

On re-download, the following list of tables is reset by selecting all of the rows for the given WipOrderNo and WipOrderType and then updating the Active field to 0 before the insert or update is performed.

DELMIA Apriso TablesWIP_OPERATIONWIP_OPERATION_SEQUENCEWIP_CONTENTWIP_SERIAL_NO_CONTENT



2. Perform the customization of the IDoc. 3. IDoc is triggered in real-time via the user exit. 4. Set up the routings for the finished product for which the order is being created. 5. The download of the order and Operations takes place when the order is first released. 6. To generate IDoc, an order needs to be created and released. 7. The Transaction Code to create the production order is CO01. 8. Enter the following information:

Initial screen:Material: (any of the finished products)Production Plant: C1P1Order Type: PP01

Second screen:Total Quantity:Finish Date:

9. Release, save, and note down the order number that appears at the bottom of the screen.

2.13 Maintenance Orders – SAP ECCProduction maintenance orders use the same IDoc as production orders. Additional mapping is included in the same mapping as the production orders. For more information, refer to 2.7 Vendor Masters and Carrier Masters – SAP ECC.



There is no product associated with the production maintenance orders.

The following list highlights the IDoc field description and possible requirements.

IDoc Field DescriptionZ2HEAD/ORDTYP ‘M’ = regular production maintenance orders.

2.14 Purchase Orders – SAP ECCFor FlexNet versions 9.0 and above:

External XML Schema Name ORDERS05.dtdDELMIA Apriso XML Schema name FlexNet_Orders.xsd

Mapforce project name map_ORDERS05_FlexNet_Orders_PurchaseOrders.mfd

XSLT mapping name map_ORDERS05_FlexNet_Orders_PurchaseOrders.xslt


Message Type ORDERSIDoc type ORDERS05Required segment Optional segment


IDoc Field DescriptionE1EDK01/BSART If NB, convert to 16.



2. Perform customization of the IDoc. 3. IDoc is triggered in real-time via the user exit. 4. The download of the order takes place when the order is created and saved. 5. To generate the IDoc, follow these steps:

a. The Transaction Code to create a purchase order in SAP is ME21N. b. Enter the following information:

Select Standard PO for the order typeEnter a Valid Vendor No.


Enter header-level information such as Purchasing organization, Purchase group, and Company CodeEnter the item overview and item detail information such as Material Number, Quantity, Plant, Storage Location, etc.

c. Save the order and note down the order number that appears at the bottom of the screen.

2.15 Delivery Orders & Customer Return Delivery Orders – SAP ECCFor FlexNet/DELMIA Apriso versions 9.0 and above.

External XML Schema Name DELVRY03.dtdDELMIA Apriso XML Schema name FlexNet_Orders.xsd

Mapforce project name map_DELVRY03_FlexNet_Orders.mfd

XSLT mapping name map_DELVRY03_FlexNet_Orders.xslt


Message Type DESADV IDoc type DELVRY03Required segment Optional segment



2. Perform the configuration for the IDoc. 3. IDoc is triggered in real-time via a message control using an output determination. 4. The download of the order takes place when the order is created and saved. 5. To generate the IDoc, follow these steps:

a. Create the sales order in SAP using the VA01 transaction. b. The Transaction Code to create the delivery order in SAP is VL01N. c. Enter the following information:

Enter the valid Sales Order No.Enter the header-level informationEnter the item overview and item detail information

d. Save the order and note down the order number that appears at the bottom of the screen.

2.16 Advanced Shipment Notification (ASN) Orders – SAP ECCFor FlexNet/DELMIA Apriso versions 9.0 and above.


External XML Schema Name DELVRY03.dtdDELMIA Apriso XML Schema name FlexNet_Orders.xsd

Mapforce project name map_DELVRY03_FlexNet_Orders.mfd

XSLT mapping name map_DELVRY03_FlexNet_Orders.xslt


Message Type WHSCONIDoc type DELVRY03Required segment Optional segment


Each partner has one Partner_Contact record.

IDoc Field DescriptionE1EDK01/BSART If NB, convert to 16.



2. Perform the configuration for the IDoc. 3. IDoc is triggered in real-time via the message control using an output determination. 4. The download of the order takes place when the order is created and saved. 5. To generate the IDoc, follow these steps:

a. Create the purchase order in SAP using the ME21N transaction. b. Create the ASN/Inbound delivery against the purchase order using VL31N. c. Enter the following information on the initial screen:

Enter the valid Purchase Order No.Enter the header-level informationEnter the item overview and item detail information


2.17 Sales Orders – SAP ECCFor FlexNet/DELMIA Apriso versions 9.1 and above.

External XML Schema Name ORDERS05DELMIA Apriso XML Schema name FlexNet_Orders.xsd

Mapforce project name map_DEBMAS03_FlexNet_Partners_Customers.mfd

XSLT mapping name map_DEBMAS03_FlexNet_Partners_Customers.xslt



Message Type ORDRSP IDoc type ORDERS05Required segment Optional segment


IDoc Field DescriptionBE1EDK01/VSART If 01, convert to 13.E1EDP19/IDTNR Product No. if E1EDP19.Qualf = ‘002’.E1EDK01/BELNR + E1EDP01/POSEX

WipOrderNo = Concatenate Order No + Order Line No.



2. IDoc is triggered in real-time via a message control. 3. The download of the order takes place when the order is created and saved. 4. To generate the IDoc, follow these steps:

a. The Transaction Code to create the sales order in SAP is VA01. b. Enter the following information:

The Select order type – (Standard Order Type OR can be used )Valid Sales Organization, Distribution Channel, and DivisionThe valid Sold To party and Customer PO numberMaterial and Quantity in the Item Detail screenThe Plant, Storage Location, and Shipping point for all itemsThe header-level information such as Sales Organization, Dist Channel, Division, etc.The item overview and item detail information such as Material Number, Quantity, Plant, Storage Location, Shipping point, Price, etc.

c. Check the Incompletion log for the order (Edit 4 Incompletion Log) and make sure the document is complete.


2.18 Shipment Orders – SAP ECCFor FlexNet/DELMIA Apriso versions 9.1 and above.

External XML Schema Name SHPMNT05.xsdDELMIA Apriso XML Schema name FlexNet_ShipmentOrders.xsd


Mapforce project name map_SHPMNT05_FlexNet_ShipmentOrders.mfd

XSLT mapping name map_SHPMNT05_FlexNet_ShipmentOrders.xslt


Message Type SHPMNT IDoc type SHPMNT05Required segment Optional segment


None.



2. Perform the configuration for the IDoc. 3. IDoc is triggered in real-time via the message control using an output determination. 4. The download of the order takes place when the order is created and saved. 5. To generate IDoc, follow these steps:

a. The Transaction Code to create shipments is VT01. b. Create the shipment. c. Attach the delivery orders to the shipment. d. Save the order and note down the order number that appears at the bottom of the screen.


3 Outbound (DELMIA Apriso to External System)The supported upload interfaces is listed as follows:

Production confirmations (see 3.2 Production Confirmations)Transactions – Stop Labor, Report Production Including Scrap and Rework, Complete WIP Operation

Plant maintenance order confirmations (see 3.3 Plant Maintenance Order Confirmations) (EP1)

Transactions – Report PM Orders, Stop Labor, Issue Against PM OrdersInventory confirmations using the MBGMCR02 interface for move and adjust (see 3.4 Inventory Confirmations Using the MBGMCR02 Interface for Move and Adjust)

For the list of SAP movement types, see 3.1.1 SAP Movement Types.Inventory Status Change Movements:

Storage Location to Storage LocationMaterial to MaterialQuality to Unrestricted and ReversalQuality to Blocked and ReversalUnrestricted to Blocked and ReversalMove Consignment to Own StocksLot to Lot

Adjust (Increment/Decrement) Inventory Movements:Goods Receipt without ReferenceGoods Receipt Reversal without Reference

Goods receipt (see 3.5 Goods Receipt)Goods receipt with reference to the following orders (version 9.0):

Purchase OrdersAdvance Shipping NoticeProduction OrdersCustomer Return Delivery Orders

Receipt reversal with reference to the following orders (version 9.0):Purchase ordersProduction OrdersReturn to Vendor

Goods Issue With reference to the following orders (version 9.0):Production OrdersPlant Maintenance Orders

Goods Issue reversals with reference to the following orders (version 9.0):Production OrdersPlant maintenance Orders

Delivery orders confirmation (see 3.6 Delivery Orders Confirmation):Delivery Order Pick ConfirmDelivery Order Pack Confirm


Post Goods Issue Confirm against DeliveryReceive against Return Delivery

Shipment confirmations (see 3.7 Shipment Confirmations )Create a sales order (see 3.7.3 Special Instructions for Configuring the External System) in SAP initiated from DELMIA Apriso by the Order Progress Status Business ComponentCreate a purchase requisition (see 3.8 Create Purchase Requisition ) in SAP initiated from DELMIA Apriso by the Generic Transaction History Writer Business Component

3.1 Common Mapping Requirements

3.1.1 SAP Movement Types

The list of SAP movement types supported by versions 8.0 and above:

DELMIA Apriso Transaction SAP Movement Type

SAP Transaction Code

Receive Against Purchase Order 101 MB01Receive Against Production Order 101 MB31Reversal of Receipt Against Production Order 102 MB31Reversal of Receipt Against Purchase Order 102 MB01Receive to Unrestricted, Quality, and Blocked Without Reference

501, 503, 505, 561

MB1C

Reversal of Receipt Without Reference 502, 504, 506, 562

MB1C

Issue of Component Against Production Order and Plant Maintenance Orders

261 MB1A

Reversal of Issue Against Production Orders and Plant Maintenance Orders

262 MB1A

Issue to a Cost Center 201 MB1AReversal of Issue to Cost Center 202 MB1AIssue Against Project / WBS Element 221 MB1AReversal of Issue Against Project/WBS Element 222 MB1AIssue to Scrap from Unrestricted 551 MB1CRev of Issue to Scrap from Unrestricted 552 MB1CIssue to Scrap from Quality 553 MB1CRev of Issue to Scrap from Quality 554 MB1CIssue to Scrap from Blocked 555 MB1CRev of Issue to Scrap from Blocked 556 MB1CInv. Move from Unrestricted to Quality 322 MB1B


Inv. Move from Quality to Unrestricted 321 MB1BInv. Move from Unrestricted to Blocked 344 MB1BInv. Move from Blocked to Unrestricted 343 MB1BInv. Move from Quality to Blocked 349 MB1BInv. Move from Blocked to Quality 350 MB1BInv. Move from Quality to Quality Within Plant 323 MB1BReversal of Inv. Move from Quality to Quality Within Plant 324 MB1BInv. Move from Blocked to Blocked Within Plant 325 MB1BReversal of Inv. Move from Blocked to Blocked Within Plant

326 MB1B

Inv. Move Between Storage Locations 311 MB1BReversal of Inv. Move Between Storage Locations 312 MB1BInv. Move Between Plants 301 MB1BReversal of Move Between Plants 302 MB1BInventory Move to Change Material 309 MB1BReversal of Inv Move to Change Material 310 MB1BInv. Move to Change Batch of Material Inv. Move from Vendor Consignment to own Stock MB1BIssue Against Outbound Delivery Orders 601 VL02NIssue Against ASN / Inbound Delivery Orders 101 VL31NReceive Against Customer Return Delivery Orders 651 VL02N

3.1.2 Mapping EDI_DC40 for SAP ECC

The following mappings for EDI_DC40 apply to all outbound IDocs.

All BEGIN and SEGMENT elements in the IDoc are defaulted to 1.

The following table lists all of the mappings from the elements in SessionContext to SAP’s EDI_DC40 segment.

SessionContext Field Name

EDI_DC40 Field Name

Description

TABNAM Constant value: EDI_DC40. DIRECT Constant value: 2. IDOCTYP Enter the basic IDoc type. CIMTYP If custom IDoc, enter the custom IDoc type. MESTYP Enter the message type.


SNDPOR SNDPOR The sender port.SNDPRT SNDPRT The sender partner type.SNDPRN SNDPRN The sender partner number.RCVPOR RCVPOR The receiver port.RCVPRT RCVPRT The receiver partner type.RCVPRN RCVPRN The receiver partner number.CLNT MANDT The client.TransactionTime CREDAT Use the fctGetDateString functoid to extract the unformat

date.TransactionTime CRETIM Use the fctGetDateString functoid to extract unformat time

and only get the first six characters.TransactionGUID SERIAL The unique number used to track IDocs in SAP.

3.2 Production ConfirmationsThe Business Components that should trigger production confirmation host upload are: Start Labor, Stop Labor, Report Production, Report Rework, and Report WIP Scrap.


Message Type PPCC2PRETTICKET01 IDoc type PPCC2PRETTICKET01 Required segment E1BP_PP_TIMETICKET Optional segment E1BP2017_GM_ITEM_CREATE

E1BP_LINK_CONF_GOODSMOV

3.2.2 Production Confirmation Interfaces

Use Report Production to report quantities and partial confirmation. Use the Complete WIP Operation to report final confirmations. Use the Stop Labor Function to report labor.

SAP ECC– Report Production

This is only for reporting quantities, and the confirmation is always partial.

External XML Schema Name PPCC2PRETTICKET01.xsdDELMIA Apriso XML Schema name FlexNet.BusinessFacade.Manufacturing.

OrderReporter.ReportOrder.xsd

Mapforce project name map_ReportOrderQty_PPCC2PRETTICKET01.mfd

XSLT mapping name map_ReportOrderQty_PPCC2PRETTICKET01.xslt


Special mapping requirements:

BC XML SegmentFlexNet.BusinessRules.Controller.Labor.Labor.Report

IDoc Field DescriptionE1BP_PP_TIMETICKET/RECORDTYPE

Record type for confirmation (L20/L40).

E1BP_PP_TIMETICKET/YIELD

Yield currently to be confirmed. Must have three (3) decimal places (1.000).

E1BP_PP_TIMETICKET/REWORK

Current rework quantity to be confirmed. Must have three (3) decimal places (1.000).

E1BP_PP_TIMETICKET/SCRAP

Scrap currently to be confirmed. Must have three (3) decimal places (1.000).

SAP ECC – Complete WIP Operation

This is only for reporting the Operation and order status as complete. There is no reporting of labor or quantities using this Function.


WipOperationCompleter.CompleteWipOperation.xsd

Mapforce project name map_CompleteWipOperation_PPCC2PRETTICKET01.mfd

XSLT mapping name map_CompleteWipOperation_PPCC2PRETTICKET01.xslt


BC XML SegmentFlexNet.BusinessRules.Manufacturing.Operations.WipOperationStatusProcessor.Complete

IDoc Field DescriptionE1BP_PP_TIMETICKET/RECORDTYPE The record type for confirmation (L20/L40).

SAP ECC – Report Labor (Versions 9.1 EP1 and Above)

This is only for reporting labor. For reporting quantities, report production is to be used.



OrderStopper.StopOrder.xsd

Mapforce project name map_StopOrderLabor_PPCC2PRETTICKET01.mfd

XSLT mapping name map_StopOrderLabor_PPCC2PRETTICKET01.xslt


BC XML SegmentFlexNet.BusinessRules.Controller.Labor.Labor.Stop

SAP ECC – Report Serial Range Quantity (Versions 9.1 EP1 and Above)

This is only for reporting labor with a range of serials. For reporting quantities, report production is to be used.

External XML Schema Name PPCC2PRETTICKET01.xsdDELMIA Apriso XML Schema name FlexNet.BusinessFacade.Labor.

LaborMarshall.ReportSerialRangeProduction.xsd

Mapforce project name map_ReportSerialRangeQty_PPCC2PRETTICKET01.mfd

XSLT mapping name map_ReportSerialRangeQty_PPCC2PRETTICKET01.xslt


BC XML SegmentFlexNet.BusinessRules.Controller.Labor.LaborController.ReportSerialRangeProduction

3.3 Plant Maintenance Order Confirmations


Message Type CONF32IDoc type CONF32Required segment E1CONF5

3.3.2 Special Instructions for Configuring the External System

Set up the message flow for CONF32 using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the CONF32 message type to the appropriate sending logical system (FLEXNET) and customer model

Set up the partner profile – transaction WE20 (SALE ► Communication ► Manual maintenance of partner profiles ► Maintain partner profile)

Add the CONF32 message as an inbound IDoc and use the process code = CON5


Must activate the event coupling (SPRO ► Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)When an inbound IDoc is sent to SAP, it does not get executed immediately – it is first written to the RUECK table

The CC3: Update PDC Messages job must be run, which will trigger the inbound IDocs for processingFor testing, the job can be run manually (it is transaction CIP3)

3.3.3 Plant Maintenance Order Confirmation Interfaces

SAP ECC – Plant Maintenance Labor Confirmations (V9.1EP1 and Beyond)

External XML Schema Name CONF32.xsdDELMIA Apriso XML Schema name FlexNet.BusinessFacade.Manufacturing.

OrderStopper.StopOrder.xsd

Mapforce project name map_StopOrderLabor_CONF32.mfd

XSLT mapping name map_StopOrderLabor_CONF32.xslt


BC XML SegmentFlexNet.BusinessRules.Controller.Labor.Labor.Stop

IDoc Field DescriptionE1CONF5/SATZA Record type for confirmation Partial / Finish of Processing (B40/B50).

3.4 Inventory Confirmations Using the MBGMCR02 Interface for Move and Adjust


Message Type MBGMCR IDoc type MBGMCR02 Required segment E1BP2017_GM_HEAD_01

E1BP2017_GM_CODE

E1BP2017_GM_ITEM_CREATE Optional segment E1BP2017_GM_SERIALNUMBER


3.4.2 Special Requirements

The possible values for the Goods Movement Code (GM_CODE):

GM Code Description SAP TCode01 Goods receipt for purchase orders. MB0102 Goods receipt for production orders. MB3103 Goods issue. MB1A04 Transfer posting. MB1B05 Other goods receipts. MB1C06 Reversal of goods movements. MB11


Set up the message flow for MBGMCR using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the WMMBXY message type to the appropriate sending logical system (FLEXNET) and customer model


Add the MBGMCR message as an inbound IDoc and use process code = BAPISet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate event coupling (SPRO ► Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)

3.4.4 Inventory Confirmations Interfaces

SAP ECC – Inventory Move Serial Confirmations Batch

External XML Schema Name MBGMCR02.xsdDELMIA Apriso XML Schema name FlexNet.BusinessFacade.Inventory.

InventoryMoveController_Batch.xsd

Mapforce project name map_Inventory_Move_MBGMCR02.mfd

XSLT mapping name map_Inventory_Move_MBGMCR02.xslt

Inventory Move Serial Confirmations Non-Batch (for versions 9.3 SP3 and above):


InventoryMoveController.Move.xsd


Mapforce project name map_Inventory_Move_NonBatch_MBGMCR02.mfd

XSLT mapping name map_Inventory_Move_NonBatch_MBGMCR02.mfd


BC XML SegmentFlexNet.BusinessRules.Inventory.InventoryMover.Move

FlexNet.BusinessRules.Inventory.InventoryMover

This section identifies the required fields for the following inventory move transactions:

Change of status from Unrestricted to Quality and reversal (COS)Change of Status from Unrestricted to Blocked and reversal (COS)Change of Status from Quality to Blocked and reversal (COS)Change of Storage location (COL)Change of Plant (COP)Change of Product / Lot (COPL)

Segment / Field Name

COS COL COP COPL Description

E1BP2017_GM_HEAD_01/

DOC_DATE

X X X X The document date.


PSTNG_DATE

X X X X The posting date.

E1BP2017_GM_CODE /

GM_CODE

X X X X The Goods Movement Code that links to the SAP Transaction Code. The list of possible values for GM_CODE are 01 to 06, Value = 04 for transfer posting.

E1BP2017_GM_ITEM_CREATE/

PLANT

X X X X The plant.


ENTRY_UOM

X X X X The unit of entry.



MATERIAL

X X X X The material number.


ENTRY_QNT

X X X X The quantity in the unit of entry.

/MOVE_TYPE

X X X X The movement type.


MOVE_PLANT

X X The receiving/issuing plant.


MOVE_STLOC

X X The receiving/issuing store location.

E1BP2017_GM_ITEM_CREATE

/STGE_LOC

X X X X The storage location.


BATCH

X The batch number.


MOVE_MAT

X The receiving/issuing material number.


MOVE_

X The receiving/issuing batch.


BATCH

SAP ECC – Inventory Adjust Confirmations


InventoryAdjustController_Batch.xsd

Mapforce project name map_Inventory_Adjust_MBGMCR02.mfd

XSLT mapping name map_Inventory_Adjust_MBGMCR02.xslt

SAP ECC – Inventory Adjust Confirmation Non-Batch


InventoryAdjustController.Adjust.xsd

Mapforce project name map_Inventory_Adjust_NonBatch_MBGMCR02.mfd

XSLT mapping name map_Inventory_Adjust_NonBatch_MBGMCR02.xslt

SAP ECC – Inventory Adjust Non-Stock Inventory Confirmations


NonInventoryAdjustController.AdjustNonStockItem.xsd

Mapforce project name map_Inventory_AdjustNonStock_MBGMCR02.mfd

XSLT mapping name map_Inventory_AdjustNonStock_MBGMCR02.xslt


BC XML SegmentFlexNet.BusinessRules.Inventory.NonInventoryAdjuster.Adjust

FlexNet.BusinessRules.Inventory.NonInventoryAdjuster

3.5 Goods Receipt


Message Type MBGMCR IDoc type MBGMCR02 Required segment E1BP2017_GM_HEAD_01


E1BP2017_GM_CODE

E1BP2017_GM_ITEM_CREATE Optional segment E1BP2017_GM_SERIALNUMBER

3.5.2 Special Requirements

Possible Values for the Goods Movement Code (GM_CODE)

GM Code Description SAP TCode01 Goods receipt for purchase orders. MB0102 Goods receipt for production orders. MB3103 Goods issue. MB1A04 Transfer posting. MB1B05 Other goods receipts. MB1C06 Reversal of goods movements. MB11

Possible Values for the Movement Indicator (MVT_IND)

Movement Indicator Description'' Goods movement without reference.'B' Goods movement for purchase order.'F' Goods movement for production order.'L' Goods movement for delivery note.'K' Goods movement for Kanban requirement (WM – internal only).'O' Subsequent adjustment of "material-provided" consumption.

Required Fields for Goods Issues, Receipt Reversals, and Issue Reversals with Reference

This section identifies the required fields for the following:

Reversal of Good Receipt against Production Orders (RGRPO)Goods Issue for Production Orders and PM Orders (GIPMO)Reversal of Goods Issue for Production Orders and PM Orders (RGIPMO)Goods Issue for a Project (GIP)Reversal of Goods Issue for a Project (RGIP)Goods Issue to a Cost Center and GL (GICG)Reversal of Goods Issue to a Cost Center and GL (RGICG)


Segment / Field Name

RGRPO GIPMO RGIPMO

GIP RGIP GICG RGICG Description


DOC_DATE

X X X X X X X The document date.


PSTNG_DATE

X X X X X X X The posting date.


REF_DOC_NO

X X X X X X X The reference document number (for tracking purposes).

E1BP2017_GM_CODE /

GM_CODE

02 03 06 03 06 03 06 The Goods Movement Code that links to the SAP Transaction Code. The possible values for GM_CODE are 01 to 06.


X X X X X X X The plant.


PLANTE1BP2017_GM_ITEM_CREATE/

CALC_MOTIVE

The accounting indicator.


RES_ITEM

X X The item number of the reservation.


RESERV_NO

X X The number of the reservation (if numeric, add leading zeroes

function in the mappings).


ENTRY_UOM

X X X X X X X The unit of entry.


SALES_ORD

The sales order number.


S_ORD_ITEM

The item number in the sales order.


The material docume


REF_DOC nt number.


WBS_ELEM

X X The work breakdown structure element.


MATERIAL

X X X X X X X The material number.


ENTRY_QNT

X X X X X X X The quantity in the unit of entry.


MOVE_TYPE

102 261 262 221 222 201 202 The movement type.


ORDERID

X X X The order number (if numeric, add leading zeroes function in the mappings).


MOVE_REAS

The Reason Code.


The stock type.


STCK_TYPEE1BP2017_GM_ITEM_CREATE/

COSTCENTER

X X The Cost Center.


GL_ACCOUNT

X X The G/L account number.


STGE_LOC

X X X X X X X The storage location.


PO_ITEM

The item number of the purchasing doc.


MVT_IND

F The movement indicator.


BATCH

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

The batch number (required only if the product is lot-controlled).


PO_NUMBER

The purchasing document number.



XSTOB

1 The reverse posting indicator. This is a Bit, Value = 1 convert to X in the mappings.

E1BP2017_GM_SERIALNUMBER/

SERIALNO

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

X/- DEPENDS

The serial number (only if the product is serial-controlled).


Set up the message flow for MBGMCR using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the WMMBXY message type to the appropriate sending logical system (FLEXNET) and customer model

Set up the Partner profile – transaction WE20 (SALE ► Communication ► Manual maintenance of partner profiles ► Maintain partner profile)

Add the MBGMCR message as an inbound IDoc and use process code = BAPISet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate the event coupling (SPRO ► Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)

3.5.4 Goods Receipt Interfaces

SAP ECC – Goods Receipt with Reference to Purchase Order






SAP ECC – Goods Receipt with Reference to Purchase Order Non-Batch








SAP ECC – Goods Receipt with Reference to Purchase Order with No Product


NonInventoryAdjustController.AdjustNonStockItem.xsd

Mapforce project name map_Inventory_AdjustNonStock_MBGMCR02.mfd

XSLT mapping name map_Inventory_AdjustNonStock_MBGMCR02.xslt




SAP ECC – Goods Receipt with Reference to Production Orders


InventoryAdjustController.Adjust




SAP ECC – Goods Receipt with Reference to Purchase Order Non-Batch








3.6 Delivery Orders ConfirmationIn versions 9.3 and above, the Business Component supports packaging at the header level and the structure of XSD is changed. The mappings are updated in order to support packaging at the header level.


Message Type WHSCONIDoc type DELVRY03

3.6.2 Possible Values for the Qualifier

E2EDL18/Qualf Value Description'CHG' Change delivery (inbound).'DEL' Delete delivery (inbound).'PGI' Post-delivery goods issue (inbound).'GWT' Change gross weight (inbound).'NWT' Change net weight (inbound).'VOL' Change volume (inbound).'PIC' Picking with flow records (inbound).


Set up the message flow for the WHSCON message type using the BD64 transaction (SALE 4 Distribution Customer Model 4 Maintain Customer Distribution Model directly)


Add WHSCON message type to the appropriate sending logical system (FLEXNET) and customer model

Set up the partner profile – transaction WE20 (SALE 4 Communication 4 Manual maintenance of partner profiles 4 Maintain partner profile)

Add the WHSCON message as an inbound IDoc and use process code = DELVSet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate event coupling (SPRO 4 Cross Applications 4 IDOC Interface / Electronic Data Interchange 4 IDOC Interface 4 Activate Event Coupling for IDOC inbound)

3.6.4 Inventory Confirmations Interfaces

SAP ECC – Delivery Order Packing Confirmation

External XML Schema Name DELVRY03DELMIA Apriso XML Schema name FlexNet.BusinessFacade.Common.

OrderProgressStatus.xsd

Mapforce project name map_PackConfirm_DELVRY03.mfd

XSLT mapping name map_PackConfirm_DELVRY03.xslt


Required IDoc SegmentE2EDL20

E2EDL37

E2EDL44

BC XML SegmentFlexNet.BusinessRules.Delivery.PackingConfirmation

SAP ECC – Delivery Order Picking Confirmation

External XML Schema Name WHSCONDELMIA Apriso XML Schema name FlexNet.BusinessFacade.Common.


Mapforce project name map_PickConfirm_DELVRY03.mfd

XSLT mapping name map_PickConfirm_DELVRY03.xslt




E2EDL18

E2EDL20

E2EDL24

BC XML SegmentFlexNet.BusinessRules.Delivery.PickingConfirmation

SAP ECC – Delivery Post Goods Issue (Prior to Version 9.1)

External XML Schema Name DELVRY03DELMIA Apriso XML Schema name FlexNet.BusinessFacade.Common.OrderProgressStatus.xsd

Mapforce project name map_PickConfirm_DELVRY03.mfd

XSLT mapping name map_PickConfirm_DELVRY03.xslt


BC XML SegmentFlexNet.BusinessRules.Delivery.GoodsIssue

SAP ECC – Delivery Orders Post Goods Issue (Versions 9.1 EP1 and Above)

FlexNet.BusinessRules.Delivery.GoodsIssue.xsd has been modified by adding the additional information required to support header-level and item-level weights and other unit characteristics.



Mapforce project name map_PostGoodsIssue_DELVRY03.mfd

XSLT mapping name map_PostGoodsIssue_DELVRY03.xslt



E2EDL18


E2EDL20

E2EDL24

BC XML SegmentFlexNet.BusinessRules.Delivery.GoodsIssue

IDoc Field DescriptionE1EDL18/QUALF Qualifier indicating Post Goods Issue, Value = PGI.E1EDL24/CHARG Batch number (only if product is lot-controlled).E1EDL11/SERNR Serial number (only If product is serial-controlled).

3.6.5 SAP ECC – Delivery Orders Goods Receipt



Mapforce project name map_PostGoodsReceipt_DELVRY03.mfd

XSLT mapping name map_PostGoodsReceipt_DELVRY03.xslt



E2EDL18

E2EDL20

E2EDL24

BC XML SegmentFlexNet.BusinessRules.Delivery.GoodsReceipt

IDoc Field DescriptionE1EDL18/QUALF Qualifier indicating Post Goods Issue, Value = ‘PGI’.E1EDL24/CHARG Batch number (only if the product is lot controlled).


E1EDL11/SERNR Serial number (only if the product is serial controlled).

3.7 Shipment Confirmations


Message Type SHPMNTIDoc type SHPMNT05

3.7.2 Possible Values

SAP Date Type Description001 Transport planning.002 Registration.003 Loading.004 Shipment completion.005 Shipment.008 Arrival.

DELMIA Apriso Progress Status Description0 Planned. 1 Planning completed. 2 Check-in. 3 Loading start.4 Loading end.5 Shipment completion.6 Shipment start.7 Shipment end.

Date Type Description Progress Status003 Load start. 3003 Load end. 4005 Shipment start. 6005 Shipment end. 7004 Shipment completion. 5001 Planning. 0/1



Set up the message flow for the WHSCON message type using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the SHPMNT message type to the appropriate sending logical system (FLEXNET) and customer model


Add the SHPMNT message as an inbound IDoc and use process code = SHPMSet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate event coupling (SPRO ►Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)When the IDoc is processed from WE19 in SAP, both box 4.6C and 4.7 with the valid IDoc data fail with this error message: “Transportation Planning Point Not defined” Create sales order

Creation of the sales order in SAP is initiated from DELMIA Apriso via the order progress status.


Message Type ORDERSIDoc type ORDERS05Required segments E1EDK01

E1EDK14

E1EDKA1

E1EDK02

E1EDP01

E1EDP03

E1EDP05

E1EDP19


Set up the message flow for the ORDRSP message type using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the ORDRSP message type to the appropriate sending logical system (FLEXNET) and customer model



Add the ORDRSP message as an inbound IDoc and use process code = ORDESet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate event coupling (SPRO ► Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)

Detailed ALE Configuration Steps with Screenshots

1. Go to WE40, select the ORDE process code, and click the “Logical message” folder on the left.

Figure 2 SAP – inbound process code

2. On the next screen, add your new message type (e.g., ORDRSP) and save.


Figure 3 SAP – logical Message

3. Go to WE20 and under Inbound, choose ORDRSP and then select ORDE as the new process code.

Figure 4 SAP – inbound parameters

4. Go to WE57 and the following record:


Figure 5 SAP – IDoc: assignment of FM to log, message, and IDoc type

5. Additional configuration in the Business Connector is required for this message to be done so that the routing rule with the sending logical system is created instead of the customer number:

Figure 6 SAP – Business Connector

3.7.6 SAP ECC – Create Sales Order

External XML Schema Name ORDERS05DELMIA Apriso XML Schema name FlexNet.BusinessFacade.Common.OrderProgressStatus


Mapforce project name map_SOCreateOrderProgressStatus_ORDERS05.mfd

XSLT mapping name map_SOCreateOrderProgressStatus_ORDERS05.xslt


E1EDK14/QUALF Value Description012 Order type.008 Sales organization.007 Distribution channel.006 Division.

BC XML SegmentFlexNet.BusinessRules.Delivery.OrderInformation

IDoc Field DescriptionE1EDKA1/ PARVW If PartnerRelationship-PartnerRole = ‘1’, convert to ‘AG’

If PartnerRole = ‘2’, convert to ‘WE’E1EDKA1/ /PARTN Sold To Party Name

If E1EDKA1-PARVW = ‘AG’, map PatnerRelationship.Account to partner

E1EDKA1(2) /PARTN

Ship To Party Number.If E1EDKA1-PARVW = ‘WE’, map PatnerRelationship.Account to partner

E1EDP01/PSTYV Default PSTYP = ‘TAN’ in the mapping.E1EDP19/IDTNR IDoc material num. (if ‘E1EDP19.QUALF’ = ‘002’ ).

3.8 Create Purchase Requisition The creation of a purchase requisition in SAP can be initiated from DELMIA Apriso via the Generic Transaction History Writer Business Component.


Message Type PREQCRIDoc type PREQCR02Required segments E1BPEBANC



Set up the message flow for the PREQCR message type using the BD64 transaction (SALE ► Distribution Customer Model ► Maintain Customer Distribution Model directly)

Add the PREQCR message type to the appropriate sending logical system (FLEXNET) and customer model


Add the PREQCR message as an inbound IDoc and use process code = BAPISet the inbound partner profile “Processing by Function module” mode to “Trigger Immediately”Must activate event coupling (SPRO ► Cross Applications ► IDOC Interface / Electronic Data Interchange ► IDOC Interface ► Activate Event Coupling for IDOC inbound)

3.8.3 SAP ECC – Create Purchase Requisition

External XML Schema Name PREQCR02DELMIA Apriso XML Schema name FlexNet.BusinessFacade.Utility.

TransactionHistoryWriter.WriteTransactionHistory

Mapforce project name map_PRUploadWriteTransactionHistory_PREQCR02.mfd

XSLT mapping name map_PRUploadWriteTransactionHistory_PREQCR02.xslt


BC XML SegmentSessionContext

IDoc Field DescriptionE1BPEBANC/DOC_TYPE Default to ‘NB’.E1BPEBANC/CREATED_BY Default to ‘APRISO’.E1BPEBANC/GR_IND Default to ‘X’.

3.8.4 SAP ECC – Template

External XML Schema Name SHPMNT05DELMIA Apriso XML Schema name FlexNet.BusinessFacade.Common.

OrderProgressStatusMapforce project name XSLT mapping name


4 BAPI InterfaceBusiness Integrator supports the RFC/BAPI interface for SAP. For more information, refer to Business Integrator Configuration Guidelines Technical Guide (section 8.4 – Invocation of BAPI/RFCs from DELMIA Apriso).

The BAPI interface is initiated from DELMIA Apriso while IDoc is initiated from SAP. Depending on the BAPI available, invocation of multiple BAPIs might be required to retrieve the data of an entity. In the case of Quality Inspection, five BAPIs are required to retrieve all of the information about an inspection lot.

4.1 Quality InspectionThe following five BAPIs are required in order to retrieve information on an inspection lot, and they must be executed one after the other in order to satisfy the dependency of the disposition tables. There is one BAPI used to report the recorded results to SAP.

Inspection Lot

The execution of this BAPI gets a list of inspection lots available for the desired product.

BAPI Name BAPI_INSPLOT_GETLISTQuery Schema name InspectionLot.GetList.query.xsd

Response schema InspectionLot.GetList.Response.xsd

Mapforce project name (query) XSLT mapping name (query) Mapforce project name (response) XSLT mapping name (response)

Inspection Lot Detail

The execution of this BAPI gets the detail information of a specified inspection lot.

BAPI Name BAPI_INSPLOT_GETDETAILQuery schema name InspectionLot.GetDetail.Query.xsd

Response schema InspectionLot.GetDetail.Response.xsd



Inspection Lot Operation

The execution of this BAPI gets all of the Operations defined for a specified inspection lot.

BAPI Name BAPI_INSPLOT_GETOPERATIONSQuery schema name InspectionLot.GetOperations.query.xsd

Response schema InspectionLot.GetOperations.Response.xsd


Inspection Lot Characteristic

The execution of this BAPI gets all of the characteristics defined for a specified inspection lot Operation.

BAPI Name BAPI_INSPOPER_GETCHARQuery schema name InspectionLotOperation.GetCharacteristics.query.xsd

Response schema InspectionLotOperation.GetCharacteristics.Response.xsd


Inspection Lot Characteristic Requirements

The execution of this BAPI gets the detail information of the characteristic for a specified inspection lot.

BAPI Name BAPI_INSPCHAR_GETREQUIREMENTSDELMIA Apriso XML Schema name

FlexNet.BusinessFacade.Utility.

TransactionHistoryWriter.WriteTransactionHistory.xsd

Query schema name InspLotCharacter.GetRequirements.query.xsd

Response schema InspLotCharacter.GetRequirements.Response.xsd

Mapforce project name (query) map_WriteTransactionHistory_InspChar_GetReq.query_BAPI.mfd

XSLT mapping name (query) map_WriteTransactionHistory_InspChar_GetReq.query_BAPI.xslt

Mapforce project name (response) map_InspLotOperCharReqResponse_InspOperCharReq.mfd


XSLT mapping name (response) map_InspLotOperCharReqResponse_InspOperCharReq.xslt

Inspection Lot Record Result (Upload)

BAPI Name BAPI_INSPLOT_GETLISTDELMIA Apriso XML schema name FlexNet.BusinessFacade.Quality.

DispositionTestStatusManager.CompleteDispositionTest.xsd

Query schema name InspectionLotOperation.RecordResults.Query.xsd

Response schema InspectionLotOperation.RecordResults.Response.xsd

Mapforce project name (query) map_CompleteDispositionTest_InspOperRecordResults.mfd

XSLT mapping name (query) map_CompleteDispositionTest_InspOperRecordResults.xslt

Mapforce project name (response) n/aXSLT mapping name (response) n/aMode Async


All the internal documents referenced in this section are available from the DELMIA AprisoStart page, which can be accessed on your DELMIA Apriso server (<server name>/apriso/start).The newest versions of all documents are available from 3DS Support at:http://www.3ds.com/support/documentation/overview/

5 ReferencesInternal Documentation

1. Business Integrator Configuration Guidelines Technical Guide

Provides the information required to configure DELMIA Apriso Business Integrator (BI), which enables adjusting the standard DELMIA Apriso configuration (installed) to custom configuration requirements.

3DS Support Knowledge Base

If you have any additional questions or doubts not addressed in our documentation, feel free to visit the 3DS Support Knowledge Base at https://www.3ds.com/support/knowledge-base/.


http://www.3ds.com/support/

https://www.3ds.com/support/knowledge-base/

Business Integrator - External System Integration Analysis

Documents

Transcript of Business Integrator - External System Integration Analysis