Integrating with Oracle Manufacturing Cloud

ORACLE WHITE PAPER | JULY 2018

Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.

[O.FOOTER] ENTER TITLE OF DOCUMENT HERE

Table of Contents

Disclaimer 1

Executive Overview 2

Introduction 2

Getting Started with Integration 3

Integration Methods 4

SOAP Web Services 4

REST Web Services 5

Business Events 5

Spreadsheet Integration 5

File-Based Data Import 5

Reporting Tools 5

Outbound Integration to the Manufacturing Cloud 6

Using Oracle Business Intelligence Cloud Service and BIP Enterprise 6

Using REST APIs 8

Inbound Integration to the Manufacturing Cloud 9

Using Oracle Integration Cloud Services (ICS) 9

Using File-Based Data Import 9

Using SOAP web service 10

Using REST APIs 10

Integration Examples 11

Integration Scenario 1: Work Order Scheduling in an External System 11

0 | Integration with Oracle Manufacturing Cloud

 Outbound Integration Considerations 12

Inbound Integration Considerations 12

Integration Scenario 2: Integrating with Manufacturing Execution Systems 12

Outbound Integration Considerations 13

Inbound Integration Considerations 14

Integration Scenario 3: Integrate with third party mobile applications 14

Getting Work Order details based on Assembly Serial 15

Response Payload for dispatchListWorkOrderOperations 16

Getting list of Components to be issued for the Work Order Operation 16

Response Payload for workOrders/WorkOrderMaterial 18

Post Material Transaction for the Work Order Operation 19

Request Payload for Material Transactions 20

Response Payload of Material Transactions 20

Conclusion 21

Additional Resources 22

1 | Integration with Oracle Manufacturing Cloud

Executive Overview
Modern manufacturing solutions help organizations in streamlining shop floor execution by enabling you to schedule work
orders, record component and resource consumption, and manage quality issues. While many organizations are
considering moving their entire manufacturing execution systems to Oracle Cloud, there are scenarios where companies
are looking to have their shop floor systems coexist with Oracle Manufacturing Cloud.

This paper is designed to guide you through adoption choices for manufacturing execution in the cloud, with
considerations of how to integrate with your existing shop floor execution systems with Oracle Cloud. With the right
integration approach, you can successfully deploy Oracle Manufacturing Cloud and achieve the benefits of modern
business processes.

Introduction
As part of your Oracle Cloud implementation for manufacturing execution, you must evaluate how these solutions will work
with your existing internal systems and the different integration options available to you. The approach you take will
depend on your business requirements, processes, capabilities of your existing systems, and configurations. Oracle Cloud
provides flexible options for inbound and outbound integration which you can leverage during your implementation.

The first part of this paper discusses how you can leverage the outbound integration capabilities to export different types
of manufacturing master data, work orders, and inventory information to your internal systems.

The second part of the paper discusses how you can leverage the inbound integration capabilities to import scheduled
work orders, operation, resource, and material transactions to the Oracle Manufacturing Cloud from your internal systems.

The rest of this paper provides considerations for each type of internal system, describes the available integration
technologies, and provides references to additional sources of information. With a successful coexistence strategy, you
can gain the advantages from the Oracle Manufacturing Cloud and start realizing business benefits as quickly as possible.

In this paper we will discuss the following integration scenarios involving Oracle Manufacturing Cloud:
» Integration with Production Scheduling Systems
» Integration with Manufacturing Execution Systems
» Integration with Third Party Mobile Applications

2 | Integration with Oracle Manufacturing Cloud

 Figure 1. Integration between Oracle Manufacturing Cloud and External Systems

Getting Started with Integration

Before you start any integration project, you should analyze your business processes and assess the options that make
the most sense for your organization. The first step is to evaluate the manufacturing process supported within Oracle
Manufacturing Cloud. You should have a compelling need to use your internal system to integrate with Oracle
Manufacturing Cloud.

After the integration need is established, you must:

» analyze each manufacturing object in Oracle Manufacturing Cloud
» consumption of the manufacturing object in your internal system and
» evaluate both the frequency and volume of information that needs to be synchronized.

Some complexities are unavoidable when implementing systematic integration. For example, apart from the process
integration, you must also consider error handling, error recovery, and adaptability to changing or extended data models.
The right strategy can mitigate unnecessary investments in building integration and simplify your overall strategy.

Oracle Help Center is an online resource for discovering Oracle Cloud Applications metadata. You can use Oracle Help
Center to find information on the integration assets that are available for specific objects and processes across Cloud,
including those related to Oracle Supply Chain Management Cloud. This website will always contain the most recent
information on what is available. As time passes, you should consult Oracle Help Center for the most currently available
assets (and any new updates) prior to beginning an integration project. Oracle expects that new assets will become
available over time.

Examples of the types of assets that you can discover within Oracle Help Center include:
» Web services (SOAP and REST services)

3 | Integration with Oracle Manufacturing Cloud

 » File-Based data integrations
» View objects (Tables and Views)
» Interface table definitions
» Sample templates
» Delivered reports for each module

Integration Methods
Oracle Cloud applications are built with Oracle’s Application Development Framework (ADF) and provide many methods of
integration with other applications, such as, ADF Services (commonly referred to as Web Services), File-Based Data Import
(FBDI), and Reporting Tools.

The following diagram illustrates various options of the Oracle Cloud to extend applications and interface with them:

Figure 2. Extensibility and Integration Options for Oracle SCM Cloud Applications

These options are available at different levels in the technology stack. Applications Extensibility Framework offers Page
Composer, Apps Composer and Flex Framework that help to build basic User Interface (UI) extensions to UI and data
model. You can use configurability in cloud applications to define the detailed behavior of the applications through options,
rules, and workflows. You can extend or integrate the application functionality using the REST and SOAP services. In case
of high volume use cases, you can use FBDI. Finally, some of the cloud applications offer pre-built B2B messages using
OAGIS standards.

SOAP Web Services

4 | Integration with Oracle Manufacturing Cloud

A SOAP (Simple Object Access Protocol) web service provides a standardized way of integrating two web-based
applications. A SOAP web service is a program that can be accessed remotely using different XML-based languages. ADF
Services simplify integration by enabling XML data exchange between different applications and different platforms. On-
premise implementations can access the Enterprise Manager and tailor the available web services for inbound and
outbound integration. But for areas where there are no web services currently available, generating OTBI or BI Publisher
reports that can be used for integration may suffice depending on what is being integrated.

REST Web Services

REST (Representational State Transfer) describes a set of architectural principles by which data can be transmitted over a
standardized interface, such as HTTP. REST does not contain an additional messaging layer and focuses on design rules
for creating stateless services. A client can access the resource using the unique URI and a representation of the resource
is returned. With each new resource representation, the client is said to transfer state. While accessing REST resources
with HTTP protocol, the URL of the resource serves as the resource identifier and GET, PUT, DELETE, POST and HEAD
are the standard HTTP operations to be performed on that resource.

Business Events

The Oracle Workflow Business Event System is an application service that leverages Oracle Advanced Queuing (AQ)
infrastructure to communicate business events between systems. The Business Event System consists of the Event
Manager and workflow process event activities.

The Event Manager contains a registry of business events, systems, named communication agents within those systems,
and subscriptions indicating that an event is significant to a particular system. Events can be raised locally or received from
an external system or the local system through AQ.

Spreadsheet Integration

Spreadsheet integration through ADFdi enables the use of familiar spreadsheet tools such as Excel. ADF Desktop
Integration (ADFdi) is part of the ADF framework and enables desktop integration with MS Excel spreadsheets to manage
large volume data uploads to Cloud Applications. The integration provided with ADFdi includes interactivity that enables web
picker to search for valid values, perform validation during data entry, display error messages, and immediately submit
transactions directly from Microsoft Excel.

File-Based Data Import

File-Based Data Import (FBDI) is another option for getting information into Cloud applications. For applications deployed in
the public cloud, in the absence of a delivered web service, the currently available option is file-based integration to transfer
files to a location that the source system can consume. The process of using FBDI is quite simple. Download an excel
template that identifies all of the fields, populate the spreadsheet with data from the external system, save the file as a .csv
file type, upload the file, and run processes to transfer the data to the interface tables and import to various applications. All
of the data is validated during import to insure its integrity. External data can be extracted and formatted into a source file for
transfer and import to Oracle Cloud applications.

Reporting Tools

Reporting tools can be used to extract data from Cloud applications for further analysis and import data to external

5 | Integration with Oracle Manufacturing Cloud

systems through XML, Excel or other file types. You have two options to export data, which are Oracle Transactional
Business Intelligence (OTBI) and BI Publisher (BIP).

OTBI is a dynamic reporting layer built against the Oracle Fusion transactional tables. OTBI is designed to enable you to
build custom reports and perform dynamic analysis. OTBI reports in the Manufacturing Cloud offers predefined subject
areas that you can use to extract data for import to your external systems. OTBI provides the ability to build custom queries
on transactional data. The output of this data can be downloaded to Excel. You can configure an Oracle Business
Transaction Intelligence (OTBI) report.

The key features of OTBI in Oracle Manufacturing Cloud are:

» OTBI offers you real time, self-service reporting directly from Oracle Manufacturing Cloud data. There is no data movement from Oracle
Fusion applications to Business Intelligence (BI) application. Every time an analysis is invoked, it directly fetches the latest data from
Oracle Fusion applications.
» The subject areas support analysis of both in-house manufacturing and contract manufacturing related work orders, and their transactions.
» OTBI provides four Oracle Manufacturing Cloud subject areas, which you can use to build custom analysis. These subject areas are:
» Manufacturing - Work Order Performance Real Time
» Manufacturing - Material Usage Real Time
» Manufacturing - Resource Usage Real Time
» Manufacturing - Actual Production Real Time
» The dimensions and facts in these subject areas provide you visibility to work order management and work execution transactions.
» OTBI is built on Oracle Business Intelligence Enterprise Edition (OBIEE) technology. All standard functions provided by OBIEE are also
available for Oracle Manufacturing Cloud subject areas.

BI Publisher (Business Intelligence Publisher) allows you to customize an existing out of the box data model or report, and
to create your own custom BIP data models and reports. You can also build your own data model using the development
tools and extract the data from the cloud applications and import the data to your system. So, if you want to reuse the data
models in the application, we recommend you to use OTBI. If you want to build your own data model or customize the pre-
built model, we recommend you to use BIP.

Outbound Integration to the Manufacturing Cloud

Oracle Manufacturing Cloud has a repository of all the master data for manufacturing execution which can be leveraged by
your internal systems. As part of the process integration, you can also export documents, such as work orders, material
transactions, operation transactions, and resource transactions.

You can choose the following to export data from Manufacturing Cloud:
» Oracle Business Intelligence Cloud Service
» BIP Enterprise
» REST APIs

Using Oracle Business Intelligence Cloud Service and BIP Enterprise

You must build a data model to extract the master data from Oracle Manufacturing Cloud to a spreadsheet, and import it to
your internal system. You must evaluate between the options of extracting all the data every time and do a complete
overwrite of the data to your internal system or synchronize only the changes. Your decision depends on the volume of the

6 | Integration with Oracle Manufacturing Cloud

data and frequency of changes.

TABLE 1. DATA BASE TABLES FOR EXPORTING MASTER DATA FROM THE MANUFACTURING CLOUD

Master Data Object dB TABLE NOTES

Plant RCS_MFG_PARAMETERS_V This view has the plant attributes.

Items EGP_SYSTEM_ITEMS This table has the item specific attributes.

Subinventory INV_SECONDARY_INVENTORIES This table has the subinventory attributes.

Locators INV_ITEM_LOCATIONS This table has the locators attributes.

Inventory Transaction Types INV_TRANSACTION_TYPES This table has definition of the inventory transaction
types.

Work Areas WIS_WORK_AREAS_B This table has definition of the work areas.

Work Centers WIS_WORK_CENTERS_B This table has definition of the work centers.

Resources WIS_RESOURCES_B This table has definition of the resources.

Resource assignment to Work WIS_WC_RESOURCES This table has details of assignment of resources to work center.
Center

Shifts of a Resource assigned WIS_WC_RESOURCE_SHIFTS This table has details of shifts of the resources assigned to a work
to a Work Center center.
Work Definition Header WIS_WORK_DEFINITIONS This table has the work definition header details.

Work Definition Versions WIS_WD_VERSIONS_V This view has the work definition version details.

Work Definition Operations WIS_WD_OPERATIONS_V This view has the work definition operation details.

Work Definition Operation WIS_WD_OPERATION_MATERIALS_V This view has the work definition operation material details.
Materials

Work Definition Operation WIS_WD_OPERATION_RESOURCES_V This view has the details of work definition operation
Resources resources.

Current Shifts WIE_CURRENT_SHIFTS_V This view has the details of the shifts.

For process integration, you must synchronize transaction documents between Oracle Manufacturing Cloud and your internal
systems. You must decide the master system that owns the document and evaluate the options to export the transaction
data to the target system. If Oracle Manufacturing Cloud is the master system, you must export data using Oracle BIP. Table
2 helps you export the transaction documents.

TABLE 2. DATA BASE TABLES FOR EXPORTING PRODUCTION TRANSACTIONS FROM THE MANUFACTURING CLOUD

ENTITY dB TABLE notes

7 | Integration with Oracle Manufacturing Cloud

 Work Order Header WIE_WORK_ORDERS_V This view contains the details of the work order header.

Work Order Operations WIE_WO_OPERATIONS_V This view contains the details of the work order operations.

Work Order Operation WIE_WO_OPERATION_MATERIALS_V This view contains the details of the work order operation
Materials materials.

Work Order Operation WIE_WO_OPERATION_RESOURCES_V This view contains the details of the work order operation
Resources resources.

Work Order Serials INV_SERIAL_NUMBERS This table contains the details of the work order serials.

Dispatch List WIE_WO_DISPATCH_LISTS_V This view contains the details of the dispatch list.

Using REST APIs

You can also export master data entities, work orders, and dispatch list using REST APIs.

TABLE 3. REST APIS FOR EXPORTING MASTER DATA, WORK ORDER AND DISPATCH LIST FROM THE MANUFACTURING CLOUD

ENTITY REST End Point Notes

Work Area /fscmRestApi/resources/<version>/workAreas Using GET of this REST API, you can export work
areas.

Work Center /fscmRestApi/resources/<version>/workCenters Using GET of this REST API, you can export work
centers.

Work Order Statuses /fscmRestApi/resources/<version>/workOrderStatuses Using GET of this REST API, you can export work
order statuses.

Production /fscmRestApi/resources/<version>/productionResources Using GET of this REST API, you can export
Resources production resources.

Work Definitions /fscmRestApi/resources/<version>/workDefinitions Using GET of this REST API, you can export work
definitions.

Standard Operations /fscmRestApi/resources/<version>/standardOperations Using GET of this REST API, you can export
standard operations.

Work Orders /fscmRestApi/resources/<version>/workOrders Using GET of this REST API, you can export work
orders.

Work Orders Metrics /fscmRestApi/resources/<version>/workOrdersMetrics Using GET of this REST API, you can export
metrics related to work orders.

Work Order Operations for /fscmRestApi/resources/<version>/dispatchListWorkOrde Using GET of this REST API, you can export work order
Dispatch Lists rOperations operations dispatch list.

Operation Starts and Stops /fscmRestApi/resources/<version>/operationStartStops Using GET of this REST API, you can export start and
stop times of a work order operation.

8 | Integration with Oracle Manufacturing Cloud

Inbound Integration to the Manufacturing Cloud
You may have to import work orders, operation, resource and material transactions from your internal system to the
Manufacturing Cloud. You have the following three options to import the data to the Manufacturing Cloud:

» Develop an adapter in Oracle Integration Cloud Services (ICS) that can populate the interface tables
» Use File-Based Data Import
» Use SOAP web services
» Use REST APIs

Using Oracle Integration Cloud Services (ICS)

You can use Oracle Integration Cloud Services (ICS) to import data from your internal system to the Manufacturing Cloud.
Oracle ICS provides infrastructure to develop an adapter that can automate the inbound integration process. This adapter in
ICS will insert records to appropriate Manufacturing Cloud tables. Table 4 summarizes the interface tables in the
Manufacturing Cloud.

TABLE 4: INTERFACE TABLES IN THE MANUFACTURING CLOUD

Entity INTERFACE TABLE Notes

Work Order Header WIE_WORK_ORDERS_INT This is the interface table for the work order header. It would contain details about the
work definition on which the work order is created, the work order type the assembly
quantities etc.

Work Order Details WIE_WORK_ORDER_DETAILS_INT This is the child interface table that carries the operations, operation resource and
operation material of the work order.

Material Transaction WIE_MATERIAL_TRANSACTIONS_INT This table will be the interface from Manufacturing for all the material transactions

Resource Transaction WIE_RESOURCE_TRANSACTIONS_INT This is the interface table for the charging of resources to record the actual usage of
the labor, equipment and tooling type of resources.

Operation Transaction WIE_OPERATION_TRANSACTIONS_INT This is the interface table for the work order operation level transactions.

Transaction Lots WIE_TRANSACTION_LOTS_INT This table stores the lot number information that is being interfaced to manufacturing. A
record in this table is either the child of the material transactions interface or the
operation transactions interface.

Transaction Serials WIE_TRANSACTION_SERIALS_INT This table stores the serial number information for the transaction interfaced as part of
a transactional interface to manufacturing.

Using File-Based Data Import

The Manufacturing Cloud also provides xlsm templates for work orders, operation, material and resource transactions to
import data. You can find these templates at:
http://docs.oracle.com/cloud/<version>/scmcs_gs/OEFSC/FBDIOverview.htm#FBDIOverview

9 | Integration with Oracle Manufacturing Cloud

TABLE 5: FBDI FILE LOCATIONS

Entity Location

Work Order https://docs.oracle.com/en/cloud/saas/supply-chain-management/<version>/oefsc/toc.htm

Operation Transaction https://docs.oracle.com/en/cloud/saas/supply-chain-management/<version>/oefsc/toc.htm

Material Transaction https://docs.oracle.com/en/cloud/saas/supply-chain-management/<version>/oefsc/toc.htm

Resource Transaction https://docs.oracle.com/en/cloud/saas/supply-chain-management/<version>/oefsc/toc.htm

Using SOAP web service

You can use SOAP web service to create material and operation transactions using REST APIs. However, Oracle
recommends REST APIs over SOAP web services. Table 6 summarizes the REST APIs:

TABLE 6: SOAP web services

Entity SOAP API endpoint Notes

Operation Transaction /wieMaterialTransactions/WorkOrderOperationTransaction You can use this SOAP web service to create an operation transaction
Service?WSDL

Material Transaction /wieMaterialTransactions/WorkOrderMaterialTransactionS You can use this SOAP web service to create a material transaction
ervice?WSDL

Using REST APIs

You can use REST APIs to create work order, material, resource and operation transactions using REST APIs. Table 7
summarizes the REST APIs:

TABLE 7: REST APIs

Entity REST API endpoint Notes

Work Orders /fscmRestApi/resources/<version>/workOrders You can use this REST API to create and update work orders.

Operation Transaction /fscmRestApi/resources/<version>/operationTransactions You can use this REST API to create an operation transaction

Material Transaction /fscmRestApi/resources/<version>/materialTransactions You can use this REST API to create a material transaction

10 | Integration with Oracle Manufacturing Cloud

 Resource Transaction /fscmRestApi/resources/<version>/resourceTransactions You can use this REST API to create a resource transaction

Operation Starts and /fscmRestApi/resources/<version>/operationStartStops You can use this REST API to create and update operation start and stop
Stops times of an operation

Integration Examples
Let us discuss three scenarios of integrating Oracle Manufacturing Cloud with external systems. The first scenario will
explain integration of Manufacturing Cloud with an external work order scheduling system using BI Publisher and FBDI. The
second scenario will explain integration of Manufacturing Cloud with an external MES using BI Publisher and FBDI. The third
scenario will detail the integration of an app running on a mobile device with Manufacturing Cloud.

Integration Scenario 1: Work Order Scheduling in an External System

Production scheduling systems typically employ constraint-based scheduling algorithms to schedule the work orders. These
algorithms attempt to find a feasible schedule by optimizing a performance metric (often called as an objective function) given
a set of manufacturing activities that have precedence constraints, and those that require a set of resources having finite
capacity.

For example, the feasible solution may result in splitting of a work order into two or more work orders where each work order
is worked on different start and end dates. Each work order may use different work definitions.

In this approach, the Oracle Planning Central System creates the work order and the work orders are exported to external
Production Scheduling Systems for scheduling. Oracle Planning Central system sends the work order header data containing
the work definition. Oracle Manufacturing Cloud then explodes the work definition to create detailed operations, operation
items, and schedules the work order.

Oracle Manufacturing takes availability of resources of a work center into consideration while scheduling the work orders.
However, Oracle Manufacturing Cloud assumes that the resources have infinite capacity, and schedules the work orders
without considering the load profile of the resources. If you need constraint-based scheduling, you must integrate Oracle
Manufacturing Cloud with your Production Scheduling System. From the Production Scheduling System, you will import
scheduled work orders to Oracle Manufacturing Cloud.

The following master data objects in the Manufacturing Cloud may need to be exported to the Production Scheduling
System:
» Item
» Production Calendar
» Shifts
» Resource
» Work Centers
» Assignment of Resources to Work Center
» Work Definition
The following transaction objects in the Manufacturing Cloud may need to be exported to the Production Scheduling System:
» Work Orders
» Inventory On Hand

11 | Integration with Oracle Manufacturing Cloud

» Projected Inventory

Figure 3. Integration between Oracle Manufacturing Cloud and External Scheduling System

Outbound Integration Considerations

You must use Oracle BI Publisher to export the master and transactional data from Oracle Manufacturing Cloud. You can
create a data model creating a data set for each of the entity you want to export. From the saved data model, you can
create and export the data into a csv file. This csv file can be imported to your Production Scheduling Systems.

You must export the master data whenever there is an update in the Manufacturing Cloud. Depending upon your
Production Scheduling Systems, you can decide to do a full extract of the master data or only an extract of the updates.
You may also have to refresh periodically the Production Calendars and availability of the resources for each work center.

Work Orders except those, which are in Completed, and Closed status must be exported to your Production Scheduling
System. Apart from the Work Orders, you may also have to export ‘Inventory-on-Hand’ and ‘Projected Inventory’ to know
the availability of the components.

Inbound Integration Considerations

After scheduling the work orders in the Production Scheduling Systems, you can import these work orders to the
Manufacturing Cloud. You can download the scheduled work orders to the specified work order xlsm format and upload
them to work order interface tables in the Manufacturing Cloud.

To prevent rescheduling of the work order in the Manufacturing Cloud, you must set the scheduling method as
‘No_Scheduling’. Oracle Manufacturing does not re-schedule the work orders if the scheduling method is ‘No_Scheduling’
and the operation start and end dates in the interface tables are not changed.

Integration Scenario 2: Integrating with Manufacturing Execution Systems

12 | Integration with Oracle Manufacturing Cloud

If you currently have a third party MES to control your shop floor activities, then you should import work orders from the
Manufacturing Cloud to the Manufacturing Execution System (MES), and execute them in your MES. MES will monitor the
flow of material and records operating conditions of the manufacturing execution. It also records material and resource
consumption for each operation. MES also records operation completion and product completions.

The following master data objects in the Manufacturing Cloud may need to be exported to MES:
» Item
» Production Calendar
» Shifts
» Resource
» Work Centers
» Assignment of Resources to Work Center
» Work Center Resource Calendar
» Work Definition

The following transaction objects in the Manufacturing Cloud may need to be exported to MES:
» Work Orders
» Inventory On Hand
» Projected Inventory

Figure 4. Integration between Oracle Manufacturing Cloud to 3rd party Manufacturing Execution System

Outbound Integration Considerations

You must use Oracle BI Publisher to export the master and transactional data from Oracle Manufacturing Cloud. You can
create a data model by creating a data set for each of the entities you want to export. From the saved data model, you can

13 | Integration with Oracle Manufacturing Cloud

create and export the data to a csv file. This csv file can be imported to your MES.
Work orders except those in Completed and Closed status must be exported to your Manufacturing Execution System
(MES). Apart from the work orders, you may also have to export Inventory-on-Hand and Projected Inventory to know the
availability of the components.

Inbound Integration Considerations

Manufacturing Execution System (MES) records material and resource consumptions apart from recording operation and
product completions. You can either use FBDI or web service to import data to Oracle Manufacturing Cloud.If you are using
Descriptive Flexfields DFF in operation, material and resource transactions, then it is recommended to use FBDI approach
for integration.

You can find the required files for FBDI here:

TABLE 5: FBDI FILE LOCATIONS

ENTITY LOCATION

Operation Transaction http://docs.oracle.com/cloud/<version>/scmcs_gs/OEFSC/Work_Order_Operation_Transaction_Import_104

04236_fbdi_45.htm#10404236

Material Transaction http://docs.oracle.com/cloud/<version>/scmcs_gs/OEFSC/Work_Order_Material_Transaction_Import_10024

236_fbdi_44.htm#10024236

Resource Transaction http://docs.oracle.com/cloud/<version>/scmcs_gs/OEFSC/Work_Order_Resource_Transaction_Import_101

242376_fbdi_46.htm#101242376

Similarly, you can find the details of SOAP based web services here:

TABLE 6: SOAP SERVICES

ENTITY LOCATION

Operation Transaction http://docs.oracle.com/cloud/<version>/scmcs_gs/OESSC/Import_Operation_Transactions_WorkOrderOper

ationTransactionService_svc_4.htm#oracle.apps.scm.commonWorkExecution.operationTransactions.o
perationTransactionsService.WorkOrderOperationTransactionService

Material Transaction http://docs.oracle.com/cloud/<version>/scmcs_gs/OESSC/Import_Material_Transactions_WorkOrderMateria

lTransactionService_svc_3.htm#oracle.apps.scm.commonWorkExecution.workOrderMaterialTransac io
ns.materialTransactionsService.WorkOrderMaterialTransactionService

Integration Scenario 3: Integrate with third party mobile applications

You can use a third party mobile application to issue components to a work order operation. You can use a REST API to get
details of a work order by scanning a serial of an assembly and post a material transaction for the components that are
issued to a particular work order operation.

For example, assume you create a solution that allows your customers to use a mobile client to connect to your partner
application. Assume this application allows your customer, a discrete manufacturer, to scan a serial of an assembly and get
the list of components required to manufacture the assembly. The issue of components is recorded in the application and
then posted as material transaction in Manufacturing Cloud.

14 | Integration with Oracle Manufacturing Cloud

Assume that an application is running on a mobile client. The application scans the serial of an assembly PRE5712, and
gets the details of the serial. The client gets work order number M1-1208, operation sequence number 20 and then gets the
component CO-1234, to be issued for that operation. It then scans the serial number of the component DZ1234, to be
issued and posts the material transaction to issue the component to the assembly.

Getting Work Order details based on Assembly Serial

The following diagram illustrates the request and response between the client application and Oracle Manufacturing Cloud:

Explanation of Callouts

The REST API does the following work:

1. You use the following command to send a REST API request from the client to the server. This command gets work order
details for an assembly serial PRE5712:
curl -u username:password
"server:port/fscmRestApi/resources/<version>/dispatchListWorkOrderOperations?finder=findBySerialNumber;SerialNumber=PRE5
712,OrganizationCode=M1,DispatchState=READY"

Data Value

API fscmRestApi
Resource dispatchListWorkOrderOperations
Finder findBySerialNumber
Finder Bind Variable SerialNumber, OrganizationCode, DispatchState
Method GET

2. The server processes the request.

3. The server sends a reply in the response payload. This payload includes details that describe the results of the request.

15 | Integration with Oracle Manufacturing Cloud

 4. Your partner application extracts the values for the following attributes from the response payload, and then displays them in the
client.

Attribute Description
ItemNumber Uniquely identifies the Assembly Number. For example, MI-1234
ItemDescription Text description of the Assembly. For example, 5.5in mobile
WorkOrderNumber Number that identifies the work order. For example, M1-1208.
OperationSequenceNumber Number that identifies the work order operation. For example, 20.
WorkCenterCode Code that uniquely identifies the work center. For example, YLX_WC_02
DispatchState Dispatch state of the assembly. For example, READY.

Response Payload for dispatchListWorkOrderOperations

The server sends the following example response payload:

{
"items" : [ {
"OrganizationId" : 207,
"OrganizationCode" : "M1",
"OrganizationName" : "Seattle Manufacturing",
"WorkAreaId" : 300100091177813,
"WorkAreaCode" : "YLX_WA_02",
"WorkAreaName" : "YLX_WA_02",
"WorkCenterId" : 300100091177814,
"WorkCenterCode" : "YLX_WC_02",
"WorkCenterName" : "YLX_WC_02",
"WorkCenterDescription" : "YLX_WC_02",
"WorkOrderId" : 300100093180128,
"WorkOrderNumber" : "M1-1208",
"WorkOrderDescription" : “WO for prototype”,
"InventoryItemId" : 300100039626650,
"ItemNumber" : "MI-1234",
"ItemDescription" : "5.5in mobile",
"OperationId" : 300100093180130,
"OperationSequenceNumber" : 20,
"OperationName" : "OP20",
"OperationDescription" : “Assemble”,
"DispatchState" : "READY",
"Quantity" : 10,
"UnitOfMeasure" : "Each",
"PlannedStartDate" : "2016-10-27T04:38:00-07:00",
"PlannedCompletionDate" : "2016-10-27T04:38:00-07:00",
"WorkOrderPriority" : null,
"PurchaseOrderId" : null,
"PurchaseOrder" : null,
"PurchaseOrderLineId" : null,
"PurchaseOrderLine" : null,
"CustomerId" : null,
"CustomerName" : null,
}]
}

Getting list of Components to be issued for the Work Order Operation

16 | Integration with Oracle Manufacturing Cloud

The following diagram illustrates the request and response between the client application and Oracle Manufacturing Cloud:

Explanation of Callouts

1. The client application will construct a URL for a REST request to manufacturing Cloud using the below attributes in the
previous response payload to get the details of the components:

Attribute Description
WorkOrderId Unique key that is generated when a work order is created. For example,
300100093180128
WorkOrderOperationId Unique key that is generated when a work order operation is created. For
example, 300100093180130

You use the following command to send a REST API request from the client to the server. This command gets component
details for a work order M1-1208:

curl -u username:password
"server:port/fscmRestApi/resources/<version>/
workOrders/300100093180128/child/WorkOrderMaterial?q=WorkOrderOperationId=300100093180130 "

Data Value
API fscmRestApi
Resource workOrders, WorkOrderMaterial
Q parameter WorkOrderOperationId

17 | Integration with Oracle Manufacturing Cloud

 Method GET

2. The server processes the request.

3. The server sends a reply in the response payload. This payload includes details that describe the results of the request.
4. Your partner application extracts the values for the following attributes from the response payload, and then displays them
in the client.

Attribute Description
ItemNumber Uniquely identifies the component Number. For example, CO-1234
ItemDescription Text description of the Assembly. For example, Touch Screen
SupplyTypeDescription Description of the Supply Type of the component. For example,
Push
SupplySubinventory Subinventory to use for issuing the component. For example,
Stores.
SupplyLocatorId Uniquely identifies the locator to use for issue of the component.
For example, 01-01-01
QuantityPERProduct Required component quantity per serial of the Assembly
UnitOfMeasure Unit of Measure of the component

Response Payload for workOrders/WorkOrderMaterial

{
"items": [
{
"OrganizationId": 207,
"WorkOrderId": 300100093180128,
"WorkOrderOperationId": 300100093180130,
"OperationSequenceNumber": 20,
"OperationName": "OP20",
"StandardOperationId": null,
"StandardOperationCode": null,
"WorkAreaId": 300100091177813,
"WorkAreaName": "YLX_WA_02",
"WorkCenterId": 300100091177814,
"WorkCenterName": "YLX_WC_02",
"WorkOrderOperationMaterialId": 300100093180131,
"MaterialSequenceNumber": 10,
"MaterialType": "COMPONENT",
"InventoryItemId": 300100036689391,
"ItemNumber": "CO-1234",
"ItemDescription": "Touch Screen",
"ItemRevision": null,
"QuantityPERProduct": 1,
"BasisType": "2",
"Quantity": 1,
"InverseQuantity": 1,
"UnitOfMeasure": "Each",
"RequiredDate": "2016-10-27T04:38:00-07:00",
"YieldFactor": 1,
"IncludeInPlanningFlag": true,
"SupplyType": "1",
"SupplyTypeDescription": "Push",
"SupplySubinventory": "Stores",

18 | Integration with Oracle Manufacturing Cloud

 "SupplyLocatorId": null,
"IssuedQuantity": null,
"ProducedQuantity": null,
}]
}

Post Material Transaction for the Work Order Operation

The following diagram illustrates the flow that posts material transaction:

Explanation of Callouts

1. The client application will capture the component quantity issued to the serial.
2. You use the following command to send a REST API request from the client to the server. This command posts one
material transaction in plant M1, for work order M1-1208, Operation Sequence 20 and component CO-1234:

curl -u username:password -X POST -H "Content-type:application/vnd.oracle.adf.resourceitem+json" -d ' { "SourceSystemCode" : "Client",

"SourceSystemType" : "EXTERNAL", "MaterialTransactionDetail" : [{ "OrganizationCode" : "M1", "OrganizationId" : 207, "SubinventoryCode" :
"Stores","TransactionDate" : "2016-11-01 07:55:49", "TransactionNote" : "Issue of Material", "TransactionQuantity" : 1, "TransactionTypeCode" :
"MATERIAL_ISSUE", "TransactionUomCode" : "Ea", "WoOperationSeqNumber" : 20, "WorkOrderNumber" : "M1-1208", "AssemblySerialNumber"
: PRE5712", "InventoryItemNumber" : "CO-1234", "TransactionSerial" : [{"SerialNumber":"DZ1234"}]}]}'
"<server>:<port>/fscmRestApi/resources/<version>/materialTransactions"

3. The server processes the request.

4. The server sends a reply in the REST response payload. This payload includes details that describe the results of the
request.
5. Your partner application extracts the values for the following attributes from the response payload, and then displays them
in the client. Note that some resources contain only a few attributes. Others might contain several hundred attributes. The
following table includes only some of the attributes from the material transaction resource.

19 | Integration with Oracle Manufacturing Cloud

 Attribute Description
InvTransactionId Unique number that identifies the material transaction number. For
example, 22386581
ErrorsExistFlag A flag that indicates whether the transaction succeeded or failed

Request Payload for Material Transactions

{
"SourceSystemCode" : "Client",
"SourceSystemType" : "EXTERNAL",
"MaterialTransactionDetail" : [
{
"OrganizationCode" : "M1",
"OrganizationId" : 207,
"SubinventoryCode" : "Stores",
"TransactionDate" : "2016-11-01 07:55:49",
"TransactionNote" : "Issued from Mobile client",
"TransactionQuantity" : 1,
"TransactionTypeCode" : "MATERIAL_ISSUE",
"TransactionUomCode" : "Ea",
"WoOperationSeqNumber" : 20,
"WorkOrderNumber" : "M1-1208",
"AssemblySerialNumber" : "PRE5712",
"InventoryItemNumber" : "CO-1234",
"TransactionSerial" : [{
"SerialNumber":"DZ1234"
}]
}]
}

Response Payload of Material Transactions

{
"SourceSystemCode" : "Client",
"SourceSystemType" : "EXTERNAL",
"ErrorsExistFlag" : "false",
"MaterialTransactionDetail" : [ {
"InvTransactionId" : 22386581,
"SourceSystemCode" : “Client”,
"OrganizationCode" : "M1",
"WorkOrderNumber" : " M1-1208",
"AssemblySerialNumber" : "PRE5712",
"WoOperationSequenceNumber" : 20,
"TransactionDate" : "2016-11-01 07:55:49",
"TransactionTypeCode" : " MATERIAL_ISSUE",
"InventoryItemNumber" : "CO-1234",
"ItemRevision" : "A",
"TransactionQuantity" : 1,
"TransactionUnitOfMeasure" : "Each",
"SubinventoryCode" : "Stores",
"Locator" : null,
"WorkDefinitionCode" : null,
"WorkOrderType" : null,
"WorkOrderSubType" : null,
"SourceHeaderReference" : null,
"SourceHeaderReferenceId" : null,
"SourceLineReference" : null,
"SourceLineReferenceId" : null,
"ReasonCode" : null,
"TransactionNote" : "Issued from Mobile client",

20 | Integration with Oracle Manufacturing Cloud

 "POLineNumber" : null,
"PONumber" : null,
"SoldToLegalEntityName" : null,
"ErrorMessages" : "",
"ErrorMessageNames" : "",
"TransactionSerial" : [ {
"LotNumber" : null,
"SerialNumber" : "DZ1234",
"SerialNumberTo" : "DZ1234",
"ErrorMessages" : "",
"ErrorMessageNames" : "",
}]
}]
}

Conclusion
This paper provides recommendations based on technologies available at the time of publication. Please consult
https://docs.oracle.com/en/ for the latest available web services, import and export processes, and other integration assets.

21 | Integration with Oracle Manufacturing Cloud

 Additional Resources
Oracle provides many resources to help with integration options. Please reference the resources below for additional information.

TABLE 6. ADDITIONAL RESOURCES

Title TYPE Description

External Data Integration Services for Reference Describes how to load data from external sources into Oracle Fusion Applications. My
Oracle Cloud Oracle Support: Doc ID 1474204.1

Oracle Help Center Web Site Use the Oracle Help Center for technical information about integrating with other applications,
including services, operations, composites, events, and integration tables.
This includes diagrams, schematics, and links to other technical documentation.
https://docs.oracle.com/en/

Tables and Views of Oracle Supply Chain Web Site Use the Oracle Help Center for technical information about data base details of Oracle
Management Cloud Manufacturing Cloud. This includes diagrams, schematics, and links to other technical
documentation.

https://docs.oracle.com/cloud/farel9/scmcs_gs/OEDSC/toc.htm

File-Based Data Import for Oracle Supply Web Site Use the Oracle Help Center for technical information about file-based data import for Oracle
Chain Management Cloud Supply Chain Management Cloud.
https://docs.oracle.com/en/cloud/saas/supply-chain-management/r13-
update18a/oefsc/toc.htm

SOAP Web Services for Oracle Supply Web Site Use the Oracle Help Center for technical information about SOAP web services for Oracle
Chain Management Cloud Supply Chain Management Cloud.
https://docs.oracle.com/cloud/<version>/scmcs_gs/OESSC/toc.htm

REST Web Services for Oracle Supply Web Site Use the Oracle Help Center for technical information about REST web services for Oracle
Chain Management Cloud Supply Chain Management Cloud.
https://docs.oracle.com/cloud/<version>/scmcs_gs/FASRP/Overview_of_REST_API.html

Oracle Integration Cloud Service Web Site Contains all the documents related to Oracle Integration Cloud Service (ICS).
https://docs.oracle.com/cloud/<version>/intcs_gs/

Oracle Business Intelligence Publisher Web Site Contains all the documents related to Oracle BI Publisher (BIP).
http://docs.oracle.com/middleware/12212/bip/index.html

22 | Integration with Oracle Manufacturing Cloud

 Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

blogs.oracle.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means,
twitter.com/oracle electronic or mechanical, for any purpose, without our prior written permission.

oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0718

Integration with Oracle Manufacturing Cloud

July 2018
Author: Nageshwara Sharma Manda
Contributing Authors: Aravindan Sankaramurthy

1 | Integration with Oracle Manufacturing Cloud