| Agile Product Lifecycle Management Integration Pack for SAP: Design to Release Implementation Guide Release 3.6 E88840-01 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Integration Pack for SAP: Design to Release Implementation Guide Release 3.6 E88840-01 |
|
Previous |
Next |
This chapter describes how to implement the Agile PLM Integration Pack for SAP: Design to Release, including prerequisites, setting up the participating applications, loading cross-reference data, configuring the pre-built integration, working with domain value maps (DVMs), application interfaces, and how to handle errors.
The Agile Product Lifecycle Management (PLM) integration is deployed through the Oracle Application Integration Architecture (Oracle AIA) Installer. For proper functioning, the integration requires certain settings and configurations in partner applications such as Agile PLM and System Application and Products Enterprise Resource Planning (SAP ERP), as well as the Oracle AIA configuration property files.
Service-Oriented Architecture (SOA) 12.2.1.1.0 must be installed and relevant patches applied.
SOA Domain must be created.
Agile PLM must be installed and configured accordingly.
Oracle Application adapter for SAP must be installed.
All the required webservices for the corresponding Business Application Programming Interfaces (BAPIs) and IDOCs of SAP must be generated from the Oracle Application adapter.
SAP environment must be installed and configured accordingly.
Before enabling the Agile PLM Integration Pack for SAP: Design to Release, you must set up the following participating applications:
Agile PLM
SAP
Cross-reference data
After installing the Agile PLM Integration Pack for SAP: Design to Release, the Agile Administrator must set up the Agile Content Services (ACS) as well as the following post-installation configurations using Java client:
Create a new Java Message Service (JMS) Destination.
Create new events for Engineering Change Order (ECO), Manufacturing Change Order (MCO), and Site Change Order (SCO).
Define filters.
Create new subscribers for ECO, MCO, and SCO.
Set privileges.
Create Auto Numbers
Update Change Order (CO) Page Two Fields
Configure Sites
Configure Site Attributes
Configure and Deploy Process Extension (PX)
Set up Agile notification
To create new JMS Destination:
Login to Agile Java Client using the login credentials provided.
Navigate to Admin, System Settings, Agile Content Service, Destinations.
Click New to create a new JMS Destination with the following information.
| Parameters | Variables |
|---|---|
| Name | SOA Application Server |
| Description | SOA Application Server |
| Protocol | JMS |
| Username | SOA Application Server Username |
| Password | SOA Application Server Password |
| Provider Context Factory | weblogic.jndi.WLInitialContextFactory |
| Connection Factory | jms/aia/AIAAgilePLMECOCF |
| Default Provider URL | t3://<soa_hostname>:<port> |
| Destination Name | jms/aia/AIAAgilePLMECOJMSQueue |
|
Note: If you are pointing Agile to a clustered Fusion Middleware (FMW) environment, the Default Provider URL must contain all possible URLs in the cluster separated by a comma. For example, t3://<soa_hostname1>:<soa_port1>,<soa_hostname2>:<soa_port2>. |
Test the JMS Destination.
The test must be successful.
To create new events for ECO, MCO and SCO:
Navigate to Admin, System Settings, Agile Content Service, Events.
Click New to create new Event(s).
Enter values for Name and Description.
Choose relevant workflows.
For SCO choose Default Site Change Orders.
For ECO choose Default Change Orders.
For MCO choose Default Manufacturer Orders.
Choose the workflow status as Released.
To create new subscribers for ECO, MCO and SCO:
Navigate to Admin, System Settings, Agile Content Service, Subscribers
Click New to create new Subscribers for ECO, MCO and SCO
Enter a Name and a Description for the subscribers
Associate the workflow as Automated Transfer Orders (ATOs)
Choose All Change Orders, All Manufacturer Orders, and All Site Change Orders as criteria for ECO, MCO and SCO respectively
Choose the appropriate Event that you created for ECO, MCO and SCO
Click OK
Select the Subscriber Details tab to add the subscriber detail information.
Click the Add Row icon to create a new row.
This opens Subscriber Detail window
Click Destinations and select the JMS Destination that was created
Click Filters and choose the following filters for Filters field using > button in the pop up that appears
ECO: Default Change Order Filter
MCO: Default Manufacturer Order Filter
SCO: Default Site Changes Order Filter
Add the Default Item Filter as filter for the ECO, MCO and SCO
Click Role(s) and select all the roles using > button in the pop up that appears
Select aXML as Format
Select English as Language
Select All as Site
Select each subscriber at a time and click Enable to enable all the created subscriptions
Navigate to Admin, System Settings, Agile Content Service, Filters
Select Default Item Filter and double-click
Navigate to the Filters tab and append Sites to the View Tabs field value
Choose Tab and Items as the value for BOM Options
Select All Levels as the value for BOM Level
Choose Tab and Manufacturer Parts as the value for AMLOptions
Select Default Change Order Filter and double-click
Navigate to the Filters tab
Choose Redline Changes Only option as No
Choose Affected Items Options as Tab and Items
Select Default Site Change Order Filter and double-click
Navigate to the Filters tab
Choose Redline Changes Only option as No
Choose Affected Items options as Tab and Items
Navigate to Admin, User Settings, Privileges
Click Edit to modify privileges for Changes, MCO and SCO
Enter a Name and Description
Select Yes for Enabled
Select Modify for Privilege
Click Criteria and choose the relevant criteria for Changes,MCO and SCO
Click Applied to and select all attributes, including the invisible and disabled attributes
Click OK
This opens the privilege screen of the entity for which you set privileges. You must now assign roles to the privileges that you have created for Changes, MCO, and SCO.
Navigate to the Where Used tab.
Click Add Roles and select the roles in the Select Roles pop up
Click OK to assign these roles to the privilege that you created.
Navigate to Admin, User Settings, Privileges and double click Read.
Click New in the Privileges to Read screen to create Read privileges for MCO
In the Create Privilege pop up that opens
Enter Name and Description
Choose Yes for Enabled
Choose Read for Privilege
Choose All Manufacturer Orders for Criteria
Choose both visible as well as invisible and disabled attributes for Applied
Click OK
This opens privilege information screen for MCO.
Navigate to Where Used tab
Click Add Roles to select roles and assign to the created privilege
Modify the Read Changes and Read Items to include Admin user
Click OK
Navigate to Admin, Data Settings and double click Classes
Double click Parts in Classes window
Navigate to the User Interface Tabs tab
Double click Page Two
Navigate to the Attributes Page Two tab
Check for the attribute Numeric01 and double click it and change the Name to ERP Manufacturer Cost
|
Note: If you do not have the Sites version on the Agile application, continue performing steps 31 through 45. If you have the Sites version, continue to the next section. |
Navigate to Admin, Data Settings and double click Classes
Double click Parts in Classes window
|
Note: Repeat the process also for Document. |
Navigate to the User Interface Tabs tab
Double click Page Two
Navigate to the Attributes Page Two tab.
Check for the MultiList01 and double click it and change the Name to OrganizationCodes.
You must also assign the values that are specific to Sites or Organization codes on the Agile side.
Click New List to create the List of Values (LOV)
Click OK
This opens the Create a New List Value screen.
Enter the values for Name and Description specifying the list of Organizations used
Click Add
Navigate to List tab
Click Add to add the batch list
Add batch list values in the pop up window
Click OK
Ensure that Page Two on these classes in enabled
To create auto numbers:
Navigate to Admin, Data Settings, AutoNumbers
Click New to create auto numbers for New Part Request (NPR) Document Number
Enter the following values in the Define the AutoNumber screen
Enter the name as NPR Document Number
Choose Yes for Enabled
Choose Custom for Type
Choose Document for Where Used
Choose com.oracle.aia.npr.NPRAutoNumber for Custom AutoNumber
Click OK
Click New to create auto numbers for NPR Part Number
Enter the following values in the Define the AutoNumber screen
Enter the name as NPR Part Number
Choose Yes for Enabled
Choose Custom for Type
Choose Part for Where Used
Choose com.oracle.aia.npr.NPRAutoNumber for Custom AutoNumber
Click OK
To update Change Order Page Two fields:
Navigate to Admin, DataSettings, Classes
Double click Classes and navigate to Changes, Change Orders
Double click Change Orders and navigate to the User Interface tabs in the Change Order window
Double click Page Two and Navigate to the Attribute Page Two tab
Select Text02 and double click
Set Visible to Yes in the Attributes Text02 window
Click Save
Navigate to Admin, User Settings, Privileges and double click Read
Click New to create a new Read privilege to read all the ECO fields.
Select required fields for the Applied To field in the Read Changes Page Two window.
Click OK
Navigate to Where Used tab.
Click Select Roles to select roles and select appropriate users in the Select Roles window.
Use the same procedure that you used for setting Read privileges and set Modify privilege for ECO fields.
You are only required to configure sites if the Agile application is enabled with the Sites version.
To configure sites:
Log in to the web client using http://<AGILE_HOSTNAME>/Agile/PLMServlet
Navigate to Search criteria and select Sites option
Select Sites from the options
Select Site for Type and enter Site Name
Click Finish
To configure Site attributes:
Navigate to Admin, Data Settings, Classes
Double click Classes and navigate to Items, Parts in Classes window.
Double click Parts and navigate to User Interface Tabs, Sites.
Double click Sites and navigate to Attributes: Sites tab.
Select Numeric01 and double click in the window that opens
Change Name to UnitCostAttribute
Set Visibility to Yes
Enable Actions Items in ATO
Go to Admin > Data Settings > Classes > ATO.
Click User Interface tab.
Click Action Items.
Modify Visible = Yes.
Save all the changes.
Read privileges for ATO Action Item Object
Go to Admin > User Settings > Privileges > Read
Search for Read ATO.3. Click Read ATO.
Go to Applied to.
Uncheck Show visible attributes only check box.6. Move Status, Subject, Description, Due Date, Notes and Assigned To to Selected column.
Save all the changes.
Modify privileges for ATO Action Item Object
Go to Admin > User Settings > Privileges > Modify.
Search for Modify ATO.
Click Modify ATO.
Go to Applied to.
Uncheck Show visible attributes only check box.
Move Status, Subject, Description, Due Date, Notes and Assigned To to Selected column
Save all the changes.
Default values for ATO Action Item attributes
Go to Admin > Data Settings > Classes > ATO.
Click User Interface tab.
Click Action Item > Attributes.
Enter default values for Notes and Due Date.
For Due Date, we recommend you to enter value "$NOW". For Notes, we recommend you to provide a wiki link for Buisiness User to refer various known error and their resolutions provided with the PIP out-of-the-box (OOTB).
Save all the changes.
Notifications can be setup in Agile PLM to send email when any error occurs during ACS processing in the change order release process integration flow.
To set up the notifications:
Log in to Agile Java Client.
In the Admin tab, navigate to System Settings > Agile Content Service > Destinations.
Open the destination that was configured for the change order release flow to send the data to the JMS queue.
In the Notification User field, add the users and user groups who need to be notified on failure of ACS transfer.
Save the changes.
The SAP Application Link Enabling (ALE) interface is part of the integration layer within SAP's Business Framework Architecture (BFA). It is a component-based architecture that enables business process integration and asynchronous data communication either between two or more SAP systems or between SAP and external systems.
Application systems are loosely coupled in an ALE integrated system and the data is exchanged asynchronously. Consistency is maintained as data is exchanged between application systems in a controlled manner.
The following steps must be performed and maintained for ALE configuration:
Define logical systems
Assign logical systems
Model the distribution scenario
Define the Remote Function Call (RFC) Destination
Define ports
Define partner profiles
Globally activate the change pointers
Set up reference material
To define logical systems:
Enter transaction code SALE in the transaction space.
Go to Sending and Receiving Systems > Logical Systems and select the Define Logical System option.
In the Change View "Logical System" Overview screen, select the New Entries option.
In New Entries: Overview of Added Entries screen, type in the logical system names, which must be assigned to the systems that are in communication.
Click Save.
To assign logical systems:
Enter the transaction code SALEin the transaction space
Go to Sending and Receiving Systems > Logical Systems and select Assign Client to Logical Systems option.
In the Change View "Clients": Overview screen, select the New Entries option.
By selecting New Entries, you are automatically directed to the New Entries: Details of Added Entries screen.
Enter the Client & Logical System defined earlier. Also enter the other appropriate values and save the data.
To model the distribution scenario:
Enter transaction code BD64, switch to edit mode and select Create Model View.
In the Create Model View screen, enter values for Short Text, Technical Name, Start Date and End Date.
Select the Model view and Add Message TypeMATMAS.
Save the entries.
Select the Model view and then choose the EDIT option in the menu bar. Choose Model view and then Distribute.
The Model view is now Distributed.
To define the RFC destination:
Enter transaction SM59, choose TCP/IP connections and then go to the menu and click Create
In the RFC Destination screen, enter data in RFC destination, Connection type as T and Description, respectively.
Click Enter to enable TCP/IP connection related fields.
Choose Registration and provide Program ID and save the entries.
To define ports:
Enter transaction code WE21 in the transaction space.
Select Transactional RFC and choose the Create option.
In the Ports in IDoc processing pop-up, select the Generate port name option.
Provide the port name, if the Own port name option is selected.
In the Creating a RFC port screen, enter Description, RFC Destination and select an appropriate Version and save the entries.
To define partner profiles:
Enter transaction code WE20 in the transaction space.
From the drop down list, choose Partner Type LS and select Create option.
In the Partner profiles screen, add message type SYNCH in out bound parameters and MATMAS in inbound parameters.
Provide any other relevant information, like ports, idoc type and save the inputs.
|
Note: The Outbound parameters screen displays the parameters and the setup of ALEConfiguration is completed. |
You must globally activate Change Pointers so that they trigger the MATMAS Idoc to send Material Attributes from SAP to Agile.
To activate Change Pointers:
Enter transaction code BD61 in the transaction area.
In the Activate Change Pointers Generally screen, select Change Pointers and save the transaction.
To activate Change Pointers for MATMAS Message Type:
Enter transaction code BD50
In the Change View "Activate Change Pointers for Messagee Type": Overview screen, select MATMAS message type
Click Save
To activate Change Pointers for Individual fields in the Material Master:
Enter transaction code BD52
In the work area enter the Message Type as MATMAS and click Continue
Delete those fields for which Change Pointer activation are not required
Click Save
To create an Item in SAP, reference material must be configured based on the Material type. If the Item is created in more than one plant then the reference material must be maintained in all the plants .The purpose of this reference material is to default all the mandatory values, which are required for the creation of material in SAP. This reference material varies from customer to customer based on their implementation setup.
A SQL script is used to load cross-reference records.
The following is an example of a SQL script that loads cross-reference records for the XRef table, ITEM_ITEMID with columns AGILE_01 and SAP_01. This sample script allows you to build XREF records for a single item.You can modify this SQL script tosuit your specific requirements.
DECLARE
XrefTableName_vc2 VARCHAR2 (2000);
XrefColumnName1_vc2 VARCHAR2 (2000);
XrefColumnName2_vc2 VARCHAR2 (2000);
XrefColumnName3_vc2 VARCHAR2 (2000);
Value_vc2 VARCHAR2 (2000);
RowNumber_vc2 VARCHAR2 (48);
IsDeleted_vc2 VARCHAR2 (1);
LastModified_ts TIMESTAMP (6);
BEGIN
/* The following values need to be set just once per load*/
XrefTableName_vc2 := 'oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref';
IsDeleted_vc2 := 'N';
XrefColumnName1_vc2 := 'COMMON';
XrefColumnName2_vc2 := 'AGILE_01';
XrefColumnName3_vc2 := 'SAP_01';
/* You'll just need to change the Value_vc2 variable for your specific edge app values
*/
/* Row Number is unique to a group of three inserts and ties them together. It's a system generated guid in all cases */
/* Copy this section as many times as needed for each set of three records you need inserted */
/********************************************** Begin set of 3 inserts
******************************************/
RowNumber_vc2 := SYS_GUID;
/* Common row should have a guid for its value */
Value_vc2 := SYS_GUID;
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName1_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Agile value generation please check XREF_
Instructions.doc */
Value_vc2 := 'AgileValue1';
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName2_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for SAP value generation please check XREF_
Instructions.doc */
Value_vc2 := 'SAPValue1';
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName3_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/************************************************** End of set of 3 inserts
******************************************/
END;
The following is an example of a SQL script that loads cross-reference records for the XRef table, CHANGE_CHANGEID with columns AGILE_01 and SAP_01. You can modify this SQL script to suit your specific requirements.
DECLARE
XrefTableName_vc2 VARCHAR2 (2000);
XrefColumnName1_vc2 VARCHAR2 (2000);
XrefColumnName2_vc2 VARCHAR2 (2000);
XrefColumnName3_vc2 VARCHAR2 (2000);
Value_vc2 VARCHAR2 (2000);
RowNumber_vc2 VARCHAR2 (48);
IsDeleted_vc2 VARCHAR2 (1);
LastModified_ts TIMESTAMP (6);
BEGIN
/* The following values need to be set just once per load*/
XrefTableName_vc2 := 'oramds:/apps/AIAMetaData/xref/CHANGE_
CHANGEID.xref';
IsDeleted_vc2 := 'N';
XrefColumnName1_vc2 := 'COMMON';
XrefColumnName2_vc2 := 'AGILE_01';
XrefColumnName3_vc2 := 'SAP_01';
/* You'll just need to change the Value_vc2 variable for your specific edge app values
*/
/* Row Number is unique to a group of three inserts and ties them together. Its a
system generated guid in all cases */
/* Copy this section as many times as needed for each set of three records you need
inserted */
/********************************************** Begin set of 3 inserts
******************************************/
RowNumber_vc2 := SYS_GUID;
/* Common row should have a guid for its value */
Value_vc2 := SYS_GUID;
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName1_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for Agile value generation please check XREF_
Instructions.doc */
Value_vc2 := 'AgileValue1';
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName2_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/* Value specific to each application, for SAP value generation please check XREF_
Instructions.doc */
Value_vc2 := 'SAPValue1';
LastModified_ts := SYSTIMESTAMP;
Insert into XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) values
(XrefTableName_vc2, XrefColumnName3_vc2, RowNumber_vc2, Value_vc2,
IsDeleted_vc2, LastModified_ts);
/************************************************** End of set of 3 inserts
******************************************/
END;
This pre-built integration uses the XREF_DATA table present in Metadata Database (MDS) to maintain cross-reference information between Agile and SAP. This cross-reference information helps map Agile Parts, Documents, and Change Orders to SAP Items and Change Orders.
There are two main virtual tables in the AIA_XREF schemas XREF_DATA table that maintain this cross-reference information.
CHANGE_CHANGEID - maintains all the Change Order information
ITEM_ITEMID - maintains Item information.
Example:
A Change Order ECO001 contains two revised items:
P0001 in site Detroit
P0002 in site Michigan
Both these revised items have component items:
P0001 has component items C0001 and C0002
P0002 has component items C0003 and C0004
When this Change Order is released from Agile to the SAP, the following entries are made in the CHANGE_CHANGEID virtual table.
| XREF_TABLE | XREF_COLUMN | ROW_NUMBER | VALUE |
|---|---|---|---|
| CHANGE_CHANGEID | AGILE_01 | E45E015046AF11DD9F2E436FB39961A8 | ECO001::DETROIT |
| CHANGE_CHANGEID | COMMON | E45E015046AF11DD9F2E436FB39961A8 | 2d373833303237303132383837353631 |
| CHANGE_CHANGEID | SAP_01 | E45E015046AF11DD9F2E436FB39961A8 | 11075 |
| CHANGE_CHANGEID | AGILE_01 | E45E015046AF11DD9F2E436FB39961A9 | ECO001::MICHIGAN |
| CHANGE_CHANGEID | COMMON | E45E015046AF11DD9F2E436FB39961A9 | 2d373833303237303132383837353632 |
| CHANGE_CHANGEID | SAP_01 | E45E015046AF11DD9F2E436FB39961A9 | 11076 |
The first row entry is made by the Agile BPEL flow for Change Order number ECO001 that is created on an item, which belongs to a site mapped to the 0001 Plant in SAP.
The second entry (Common) is also created by the Agile BPEL flow. It indicates the common business component id for this particular integration entity and is used for linking change orders to SAP change orders.
The third row entry represents the SAP change id corresponding to the Agile change order ECO001. Another set of entries are made for the change order ECO0001 for site PAV0.
For each revised item and component items in the Change Order, entries are made into the ITEM_ITEMID virtual table. For ECO001, the following entries are made in the ITEM_ITEMID table:
| XREF_TABLE | XREF_COLUMN | ROW_NUMBER | VALUE |
|---|---|---|---|
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFB | P0001::DETROIT |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFB | 35313835373739353732383638303435 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFB | 66247::204 |
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFC | P0002::MICHIGAN |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFC | 35313835373739353732383638303436 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFC | 66248::207 |
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFD | C0001::DETROIT |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFD | 35313835373739353732383638303437 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFD | 66249::204 |
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFE | C0002::DETROIT |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFE | 35313835373739353732383638303438 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFE | 66250::204 |
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFF | C0003::MICHIGAN |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFF | 35313835373739353732383638303439 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFF | 66251::207 |
| ITEM_ITEMID | AGILE_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFG | C0004::MICHIGAN |
| ITEM_ITEMID | COMMON | 0078BE703EC711DDBF9CA7AA7FE3BDFG | 35313835373739353732383638303440 |
| ITEM_ITEMID | SAP_01 | 0078BE703EC711DDBF9CA7AA7FE3BDFG | 66252::207 |
The first row entry is made by the Agile PLM BPEL flow for part P0001. This part belongs to an Agile site that is mapped to site DETROIT.
The second entry (Common) is also created by the Agile BPEL flow. It indicates the common business component Id for this particular in integration entity and is used to link Agile Parts, Documents, and Change Orders to SAP Items and Change Orders.
The third row entry represents the SAP inventory item Iid corresponding to the item P1B and the organization Id for the item. The rest of the entries represent the revised and component items for ECO001.
The ITEM_ITEMID virtual table contains the similar cross-reference entries for each item and part created through the new part request process.
If data is ported from other existing integrations to the Agile PLM pre-built integration, first the relationship between the Agile entities and the SAP entities must be established and each Agile site must be mapped to the corresponding SAP plant by inserting the relevant data in the XREF_DATA table.
You must load the required integration data manually in to the XREF_DATA table to establish the link between Agile PLM and SAP. This data maps the Agile PLM entities to the SAP entities as described in the previous section.
Even for existing Agile PLM pre-built integrations, if an item or change order is created in SAP then it must be created in Agile. For the pre-built integration to process the item, a cross-reference entry for that item must be made. All the update (reverse) flows for the pre-built integration updates the item attributes in Agile only if there is an entry in the XREF_DATA table for that particular item.
The cross-reference file is stored in the MDS repository in the below path
oramds:/apps/AIAMetaData/xref/<xref-name>.xref where xref-name is ITEM_ITEMID or CHANGE_CHANGE_ID
The data that has to be inserted in the XREF_DATA table must be put in an XML file with the following format.
This is a sample change order data file:
Example 5-1
<xref xmlns="http://xmlns.oracle.com/xref">
<table name="CHANGE_CHANGEID">
<columns>
<column name="SAP_01"/>
<column name="COMMON"/>
<column name="AGILE_01"/>
</columns>
<rows>
<row>
<cell colName="SAP_01">11075</cell>
<cell colName="COMMON">2d373833303237303132383837353631</cell>
<cell colName="AGILE_01">ECO001::DETROIT</cell>
</row>
<row>
<cell colName="SAP_01">11076</cell>
<cell colName="COMMON">2d373833303237303132383837353632</cell>
<cell colName="AGILE_01"> ECO001::MICHIGAN</cell>
</row>
</rows>
</table>
</xref>
The Change Id number that is inserted in the SAP_01 column for a particular change order can be obtained using the following query:-
Select change_id from eng_engineering_changes
where
change_notice=<AgileChangeOrder>;
The business component id that is inserted in the COMMON column can be any unique number.
The Agile change order number and the SAP organization corresponding to the Agile site are inserted into the AGILE_01 column separated by ":"
This is a sample Item Data file:
Example 5-2
<xref xmlns="http://xmlns.oracle.com/xref">
<table name="ITEM_ITEMID">
<columns>
<column name="SAP_01"/>
<column name="COMMON"/>
<column name="AGILE_01"/>
</columns>
<rows>
<row>
<cell colName="SAP_01">66247::0001</cell>
<cell colName="COMMON">35313835373739353732383638303435</cell>
<cell colName="AGILE_01"> P0001::DETROIT</cell>
</row>
<row>
<cell colName="SAP_01">66248::PAV0</cell>
<cell colName="COMMON">35313835373739353732383638303436</cell>
<cell colName="AGILE_01"> P0002::MICHIGAN</cell>
</row>
<row>
<cell colName="SAP_01">66249::0001</cell>
<cell colName="COMMON">35313835373739353732383638303437</cell>
<cell colName="AGILE_01"> C0001::DETROIT</cell>
</row>
<row>
<cell colName="SAP_01">66250::0001</cell>
<cell colName="COMMON">35313835373739353732383638303438</cell>
<cell colName="AGILE_01"> C0002::DETROIT</cell>
</row>
<row>
<cell colName="SAP_01">66251::PAV0</cell>
<cell colName="COMMON">35313835373739353732383638303439</cell>
<cell colName="AGILE_01"> C0003::MICHIGAN</cell>
</row>
<row>
<cell colName="SAP_01">66252::PAV0</cell>
<cell colName="COMMON">35313835373739353732383638303440</cell>
<cell colName="AGILE_01"> C0004::MICHIGAN</cell>
</row>
</rows>
</table>
</xref>
The Item inventory number and the organization id is inserted in the SAP_01 column separated by ":".
The business component id that is inserted in the COMMON column can be any unique number.
The Agile item number and the SAP plant corresponding to the Agile site are inserted into the AGILE_01 column separated by "::".
If you want to perform an initial data load, after the data load is performed in edge applications, then you must manually populate the ITEM_ITEMID and CHANGE_CHANGEID cross-reference tables after installing and configuring the re-built integration. You must manually add the cross-reference data into the ITEM_ITEMID and CHANGE_CHANGEID XRef tables by using SQL insert statements.
For each SAP item processed through initial loads, the following rows must be created in the XREF_DATA table:
· One row for Agile: AGILE_01
· One row for SAP: SAP_01
· One row for Common: COMMON
The physical XREF_DATA table is located in the database configured for FMW and SOA and contains the following columns:
XREF_DATA Table Format
| Column Name | Description |
|---|---|
| XREF_TABLE_NAME | This column stores the XREF data types. For example:
oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref |
| XREF_COLUMN_NAME | This column stores the values indicating the edge applications and COMMON value:
AGILE_01 SAP_01 COMMON |
| ROW_NUMBER | This column stores the GUID. |
| IS_DELETED | This column indicates whether the column is deleted or not. For example, 'N'. |
| LAST_MODIFIED | This column stores last modified time. |
ITEM_ITEMID XRef Table Value Format
| XRef_Column_Name | Value |
|---|---|
| COMMON | GUID |
| AGILE_01 | Agile ItemID::Site
For example, Part1::DETROIT |
| SAP_01 | SAP ItemID::Plant ID
For example, 60031::0001 |
Sample SQL Insert Statements for ITEM_ITEMID Table:
For SAP_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', 'SAP_01', 'BD618D40B30C11DEBFA5D9490F57512E ', '532922::0001', 'N', SYSTIMESTAMP)
For AGILE_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', ' AGILE_01', 'BD618D40B30C11DEBFA5D9490F57512E', ' TM0101P::DETROIT', 'N', SYSTIMESTAMP)
For COMMON:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES (' oramds:/apps/AIAMetaData/xref/ITEM_ITEMID.xref ', ' COMMON ',
'BD618D40B30C11DEBFA5D9490F57512E', '2d373037303636323539363632323735', 'N', SYSTIMESTAMP)
Sample Data for XRef ITEM_ITEMID Table
| XRef_Table | XRef_Column | Row_Number | Value | IS_Deleted | Last_Modified |
|---|---|---|---|---|---|
| oramds:/apps/AIA
MetaData/xref/ITE M_ITEMID.xref |
SAP_01 | BD618D40B3
0C11DEBFA5 D9490F57512E |
532922
::0001 |
N | 2012-4-11.11.29. 54. 210000000 |
| oramds:/apps/AIA
MetaData/xref/ITE M_ITEMID.xref |
AGILE_01 | BD618D40B30C11D
EBFA5D9490F57512E |
TM010
1P::DETROIT |
N | 2012-4-11.11.29. 54. 210000000 |
| oramds:/apps/AIA
MetaData/xref/ITE M_ITEMID.xref |
COMMON | BD618D40B30C11DEBFA
5D9490F57512E |
2d37303730
3636323539 3636323237 35 |
N | 2012-4-11.11.29. 54. 210000000 |
CHANGE_CHANGEID XRef Table Value Format
| XRef_Column_Name | Value |
|---|---|
| COMMON | GUID |
| AGILE_01 | Agile ItemID::Site
For example, Part1::DETROIT |
| SAP_01 | SAP ChangeID
For example, 60031 |
Sample SQL Insert Statements for CHANGE_CHANGEID Table
For SAP_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES ('
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' SAP_01',
'C7D0C3D0740D11E1BFF50FA2D024BE6E', '92219', 'N', SYSTIMESTAMP)
For AGILE_01:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES ('
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' AGILE_01',
'C7D0C3D0740D11E1BFF50FA2D024BE6E ', ' C00374::V1', 'N', SYSTIMESTAMP)
For COMMON:
INSERT INTO XREF_DATA (XREF_TABLE_NAME, XREF_COLUMN_NAME, ROW_
NUMBER, VALUE, IS_DELETED, LAST_MODIFIED) VALUES ('
oramds:/apps/AIAMetaData/xref/CHANGE_CHANGEID.xref ', ' COMMON', '
C7D0C3D0740D11E1BFF50FA2D024BE6E ', '2d383932333633343735363134363035', 'N',
SYSTIMESTAMP)
Sample Data for CHANGE_CHANGEID Table
| XRef_Table | XRef_Column | Row_Number | Value | IS_Deleted | Last_Modified |
|---|---|---|---|---|---|
| oramds:/apps/AIA
MetaData/xref/CH ANGE_CHANGEI D.xref |
SAP_01 | BD618D40B30C11D
EBFA5D9490F57512E |
92219 | N | 2012-4-11.11.29. 54. 210000000 |
| oramds:/apps/AIA
MetaData/xref/CH ANGE_CHANGEI D.xref |
AGILE_01 | C7D0C3D0740D11E1BFF50FA2D024BE6E | C0037
4::DETROIT |
N | 2012-4-11.11.29. 54. 210000000 |
| oramds:/apps/AIA
MetaData/xref/CH ANGE_CHANGEI D.xref |
COMMON | C7D0C3D0740D11E1BFF50FA2D024BE6E | 2d3839323336333437353631
34363035 |
N | 2012-4-11.11.29. 54. 210000000 |
This pre-built integration uses various configuration parameters that control the behavior of the flow. The standard AIA XML configuration file, AIAConfigurationProperties.xml, is used for capturing configuration parameters. The Oracle AIA configuration file supports system-level configuration parameters, service-level parameters, and module configuration parameters. System-level parameters apply to all pre-built integrations running on the SOA suite. Service-level parameters are configured at the individual service levels, such as Application Business Connector Service (ABCS).
The configuration properties from the Agile Module and the SAP Module are listed separately in this section for the purpose of identification. The actual AIAConfigurationProperties.xml file on the Oracle AIA Server is a merger of both.
This pre-built integration uses the following type of configuration parameters -
PIP-Level configuration parameters: PIP configuration parameters are implemented using the Oracle AIA module configuration entry. The module configuration entry has a name and can contain any number of configuration parameters. A naming convention of PIPS.PIPName is used for naming modules. The parameters inside the module are named using a cascaded naming convention where individual words are separated with dots. For example, agile.replicate.item.
Service-Level configuration parameters: While most configuration requirements are satisfied by the PIP-Level configuration parameters, sometimes the behavior of a flow must be controlled at the service level. These parameters can be captured using Oracle AIA service configuration parameters. Service configuration entry is identified by the service name, such as CreateItemAgileReqABCSImpl. The parameter names themselves are named using a cascaded naming convention as explained previously.
To upload to MDS:
1. Update the required property in the AIAConfigurationProperties.xml file
2. Go to <AIA_HOME>\aia_instances\AIA1115\config' path and open the UpdateMetaDataDP.xml file. Add <include name="config/AIAConfigurationProperties.xml"/>.
3. Go to <AIA_HOME>\Infrastructure\Install\config and run the following command:
ant -f UpdateMetaData.xml
|
Note: Whenever the AIAConfigurationProperties.xml file is updated, the file must be updated in MDS. |
| Properties | (default) Value/Setting | Description |
|---|---|---|
| Module Name | Agile | |
| MULTISITE_ENABLED | TRUE | When set to True, the sites specified in Sites Tab of Items are used to determine the Plants in SAP to which they are mapped.
When set to False, Page2 Multilist01attribute is used to determine the Plants in SAP to which the Item will be extended to. |
| LANG_LOCALE | English | Specifies the language locale information |
| Item.UnitCostAttribute | Site.Numeric01 | Determines the attribute to which the unit cost from SAP would be updated in Agile. |
| Change.TransferStatusAttribute | PageTwo.Text02 | Determines the attribute to which the transfer status of a Change should be written.
When the Change flow is from Agile to SAP, the possible values are "Transferred" or "Errored". When the Change flow is from SAP to Agile, the value would be the same as that of the Status of the Change in all the Plants of SAP. |
| Change.TransferStatusDetailedMessageAttribute | PageTwo.Multitext35 | Contains detailed error message in case of Transfer Validation failure |
| AgileATOActionItem Status | Not Accepted | Determine the value of Status in Action Item row in an ATO in Agile PLM. Default value is the recommended value. This can be updated with valid Status value available in Agile PLM. |
| AgileATOActionItem Subject | Integration Error | Determine the value of Subject in Action Item row in an ATO in Agile PLM |
| EnableAgileATOActionItemIntegration | TRUE | This value can be updated to FALSE to disable Error Landing Feature |
| User | Agile PLM user provided at the time
of PIP installation. |
Action Item gets assinged to User provided here in case Change Analyst information is not available in a Change Order |
| ServiceName | CreateQueueService | |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | QueueProcessorServiceImpl | |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | UpdateItemListAgileProvABCSImpl | |
| ABCSExtension.PreProcessABM | FALSE | User exit for the pre-process ABM should be called or not |
| ABCSExtension.PreProcessEBM | FALSE | User exit for the pre-process EBM should be called or not |
| ABCSExtension.PostProcessEBM | FALSE | User exit for the post-process EBM should be called or not |
| ABCSExtension.PostProcessABM | FALSE | User exit for the post-process ABM should be called or not |
| TRACE.LOG.ENABLED | FALSE | Use tracelog for the flow |
| Default.SystemID | AGILE_01 | System ID of the Agile PLM application instance |
| Routing.ItemResponseEBS.UpdateItemListResponse.MessageProcessingInstruction.EnvironmentCode | PRODUCTION | Environment code such as 'PRODUCTION'/'CAVS' and so on. Identifies the installation environment. |
| Routing.ItemABSService.AGILE_01.EndpointURI | http://${agile.host}:${agile.port}/Agile/integration/services/ItemABS | Route to ItemABS |
| ItemResponseEBS.UpdateItemListResponse.RouteToCAVS | FALSE | Route to CAVS is set to TRUE |
| Routing.ItemResponseEBS.UpdateItemListResponse.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/ AIAValidationSystemServlet/syncresponsesimulator | CAVS URL; When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is regarding item response EBS |
| ServiceName | ProcessEngineeringChangeOrderAgileReqABCSImpl | |
| ABCSExtension.PreProcessABM | FALSE | User exit for the pre-process ABM should be called or not |
| ABCSExtension.PreProcessEBM | FALSE | User exit for the pre-process EBM should be called or not |
| ABCSExtension.PostProcessEBM | FALSE | User exit for the post-process EBM should be called or not |
| ABCSExtension.PostProcessABM | FALSE | User exit for the post-process ABM should be called or not |
| TRACE.LOG.ENABLED | FALSE | Use tracelog for the flow |
| Default.SystemID | AGILE_01 | System ID of the Agile PLM application instance |
| Routing.ChangeABSService.AGILE_01.EndpointURI | http://${http.hostna
me}:${http.port}/ Agile/integration/services/ChangeABS |
property is set to false, use the URL mentioned
to connect to the Agile PLM ChangeABS Service for the ChangeABSService partnerlink. This is the default value. This can be modified to point it to some other service where message should be routed like CAVS service. |
| Routing.TableService.AGILE_01.EndpointURI | http://${http.hostna
me}:${http.port}/ CoreService/services/Table |
This is the default value. This can be modified
to point it to some other service where message should be routed like CAVS service. |
| Routing.Engineering ChangeOrderEBS.Cre
ateEngineeringChang eOrderList.RouteToC AVS |
False | If set to True, route to CAVS; otherwise, route
to EngineeringChangeOrder EBS (Enterprise Business Service) |
| Routing.Engineering
ChangeOrderEBS.Cre ateEngineeringChang eOrderList.CAVS.EndpointURI |
http://${http.hostna
me}:${http.port}/AIA ValidationSystemSer vlet/asyncresponsesi mulator |
CAVS URL
When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS |
| Routing.Engineering
ChangeOrderEBS.Cre ateEngineeringChang eOrderList.MessageP rocessingInstruction. EnvironmentCode |
PRODUCTION | Environment code such as 'PRODUCTION'/
'CAVS'. Identifies the installation environment |
| ServiceName | CreateItemAgileReqABCS | |
| TRACE.LOG.ENABLED | false | Use tracelog for the flow |
| ServiceName | CreateItemAgileReqABCSImpl | |
| ABCSExtension.PreProcessABM | FALSE | User exit for the pre-process ABM should be called or not |
| ABCSExtension.PreProcessEBM | FALSE | User exit for the pre-process EBM should be called or not |
| BCSExtension.PostProcessEBM | FALSE | User exit for the post-process EBM should be called or not |
| ABCSExtension.PostProcessABM | FALSE | User exit for the post-process ABM should be called or not |
| TRACE.LOG.ENABLED | FALSE | Use tracelog for the flow |
| Default.SystemID | AGILE_01 | System ID of the Agile PLM application instance |
| Routing.ItemEBS.CreateItem.RouteToCAVS | FALSE | CAVS URL; When the RouteToCAVS property is set to True, use the URL mentioned to connect to CAVS. This invocation is regarding item response EBS |
| Routing.ItemEBS.CreateItem.CAVS.EndpointURI | Runtime target endpoint URI | |
| Routing.ItemEBS.CreateItem.MessageProcessingInstruction.EnvironmentCode | Runtime target endpoint URI |
|
Note: Multisite_Enabled property is governed by Distributed Processing aspects covered in Chapter 2: Process Integration for ECO/PREL. When it is set to TRUE (default), the Item.UnitCostAttribute is set to Site Tab Flex Attributes. You can use Numeric, Text or Money flex fields in the Site tab for these settings and is denoted by the first element, Site. For example, if Site.Numeric01 is set to FALSE, all these attributes are set to Page2 or Page3 flex fields. Hence, the settings need to be changed to PageTwo.Numeric01 or PageThree.Numeric01 accordingly. The names of the attributes can be derived from the ItemABM Schema, which can be found in Agile Application Interfaces. |
|
Note: The Composite Application Validation System (CAVS) feature is not supported for the flows in this release. However, the CAVS enabling properties for the flows are deployed. |
| Properties | (Default) Value/Setting | Description |
|---|---|---|
| ModuleName | SAP | |
| LANG_LOCALE | en-US | Used to specify the language code and locale of the SAP system |
| GLOBAL_LEVEL_BOM | FALSE | When this property is set to FALSE, in SAP the BOM are created at plant level and not at the global level. If set to TRUE, the BOM will be created at the global level. |
| DEFAULT_SYSTEM_ID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| MATERIAL_TYPE | FERT | Used to specify the material type in SAP to be "Finished Product" |
| SAP46_N_ABOVE | TRUE | Specifies that the version of SAP used is greater than 4.6. |
| BOM_USAGE | 1 | BOM_USAGE denotes the usage of the BOM. 1indicates production level BOM. This value is dependent on the business process implemented at the client site. Some other values are:
2 indicates engineering/design BOM 3 indicates universal BOM 4 indicates plant maintenance BOM |
| ITEM_CATEGORY | L | ITEM_CATEGORY denotes the category of the item that is added to the BOM. L indicates stock item. This value is dependent on the business process implemented at the client site. Some other values are:
N indicates non-stock item T denotes text item D denotes document item |
| ServiceName | ReserveItemSAPProvABCS | |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the post-process Item EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the pre-process Item EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.ItemResponseEBS.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.GenerateItemNumberService_Reserve.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ReserveItemService/ReserveItemService_ep | ReserveItemSAP runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | CreateEngineeringChangeOrderListEBF | |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSITEMEBM | False | User exit for the post-process Item EBM should be called or not |
| ABCSEXTENSION.PREPROCESSITEMEBM | False | User exit for the pre-process Item EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.ItemEBSV2.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.ItemEBSV2.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/ asyncresponserecipient | CAVS Endpoint URI |
| Routing.EngineeringChangeOrderResponseEBS.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.EngineeringChangeOrderResponseEBS.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/EngineeringChangeOrderResponseEBS!1.0/EngineeringChangeOrderResponseEBS_ep | EngineeringChangeOrderEBS runtime target endpoint URI |
| Routing.EngineeringChangeOrderResponseEBS.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/ asyncresponserecipient | CAVS Endpoint URI |
| Routing.CreateEngineeringChangeOrderListSAPProvABCS.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/CreateEngineeringChangeOrderListSAPProvABCS/CreateEngineeringChangeOrderListSAPProvABCS_client_ep | CreateEngineeringChangeOrderListSAPProvABCS runtime target endpoint URI |
| Routing.ProcessBillOfMaterialsListSAPProvABCS.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ ProcessBillOfMaterialsListSAPProvABCS/ProcessBillOfMaterialsListSAPProvABCS_client_ep | ProcessBillOfMaterialsListSAPProvABCS runtime target endpoint URI |
| Routing.EngineeringChangeOrderResponseEBS.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ EngineeringChangeOrderResponseEBS/EngineeringChangeOrderResponseEBS_ep | EngineeringChangeOrderResponseEBS runtime target endpoint URI |
| Routing.SyncItemListSAPProvABCS.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ SyncItemListSAPProvABCS/SyncItemListSAPProvABCS_client_ep | SyncItemListSAPProvABCS runtime endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | CreateEngineeringChangeOrderListSAPProvABCS | |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the pre-process ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.CreateEngineeringChangeOrderService.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-Infra/services/default/ECOService/ECORouterService_ep | CreateEngineeringChangeOrderService runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | SyncItemListSAPProvABCS | |
| ABCSEXTENSION.PREPROCESSREVLEVELABM | False | User exit for the pre-process ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSREVLEVELABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSSAVEDDATAABM | False | User exit for the pre-process SAVED DATA ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSSAVEDDATAABM | False | User exit for the post-process SAVED DATA ABM should be called or not |
| ABCSEXTENSION.PREPROCESSREFMATERIALABM | False | User exit for the pre-process REF MATERIAL ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSREFMATERIALABM | False | User exit for the post-process REF MATERIAL ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.Call_ItemListResponseEBS.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.Call_ItemListResponseEBS.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/ asyncresponserecipient | CAVS Endpoint URI |
| Routing.ItemServiceESB.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-Infra/services/default/ ItemServiceESB/ItemServiceESB_ep | ItemServiceESB runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | ProcessBillOfMaterialsListSAPProvABCS | |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the pre-process ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.BillOfMaterialsEBS_UpdatePlantSpecificBillOfMaterials.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.BillOfMaterialsEBS_UpdateGlobalLevelBillOfMaterials.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.BillOfMaterialsEBS_CreatePlantSpecificBillOfMaterials.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.BillOfMaterialsEBS_CreatePlantSpecificBillOfMaterials.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/ AIAValidationSystemServlet/asyncresponserecipient | BillOfMaterialsEBS runtime target endpoint URI |
| Routing.BOMExistenceCheckService.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ BOMServiceESB/BOMServiceESB_ep | BillOfMaterialExistenceCheckService runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | CreateBillOfMaterialsListSAPProvABCSImpl | |
| ABCSEXTENSION.PREPROCESSBOMEXISTENCECHECKABM | False | User exit for the pre-process BOM Existence Check ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMEXISTENCECHECKABM | False | User exit for the post-process BOM Existence Check ABM should be called or not |
| ABCSEXTENSION.PREPROCESSBOMPLANTEXTENSIONABM | False | User exit for the pre-process BOM Plant Existence Check ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMPLANTEXTENSIONABM | False | User exit for the post-process BOM Plant Existence Check ABM should be called or not |
| ABCSEXTENSION.PREPROCESSBOMCREATEABM | False | User exit for the pre-process BOM Create ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMCREATEABM | False | User exit for the post-process BOM Create ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.BillOfMaterialsResponseEBS.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.CreateEngineeringChangeOrderService.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ CreateBillOfMaterialsListSAPProvABCSImpl/CreateBillOfMaterialsListSAPProvABCSImpl_client_ep | CreateEngineeringChangeOrderService runtime target endpoint URI |
| Routing.BillOfMaterialsRouterService.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ BOMServiceESB/BOMServiceESB_ep | BillOfMaterialsRouterService runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
| ServiceName | UpdateBillOfMaterialsListSAPProvABCSImpl | |
| ABCSEXTENSION.PREPROCESSBOMEXISTENCECHECKABM | False | User exit for the pre-process BOM Existence Check ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMEXISTENCECHECKABM | False | User exit for the post-process BOM Existence Check ABM should be called or not |
| ABCSEXTENSION.PREPROCESSBOMPLANTEXTENSIONABM | False | User exit for the pre-process BOM Plant Existence Check ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMPLANTEXTENSIONABM | False | User exit for the post-process BOM Plant Existence Check ABM should be called or not |
| ABCSEXTENSION.PREPROCESSBOMUPDATEABM | False | User exit for the pre-process BOM Update ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSBOMUPDATEABM | False | User exit for the post-process BOM Update ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.BillOfMaterialsResponseEBS.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.ProcessBillOfMaterialsListSAPProvABCS.SAP_01.EndpointURI | http:// ${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default ProcessBillOfMaterialsListSAPProvABCS/ProcessBillOfMaterialsListSAPProvABCS_client_ep | ProcessBillOfMaterialsListSAPProvABCS runtime target endpoint URI |
| Routing.BillOfMaterialsRouterService.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ BOMServiceESB/BOMServiceESB_ep | BillOfMaterialsRouterService runtime target endpoint URI |
| Routing.UpdateBillOfMaterialService.SAP_01.EndpointURI | http:// ${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/BOMServiceESB/BOMServiceESB_ep | UpdateBillOfMaterialService runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use trace log for the flow |
| ServiceName | UpdateItemListSAPReqABCSImpl | |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the pre-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.ItemEBSV2.RouteToCAVS | False | Route to CAVS, if set as True |
| Routing.ItemEBSV2.SAP_01.EndpointURI | http:// ${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/ItemEBSV2/ItemEBSV2_ep | ItemEBS runtime target endpoint URI |
| Routing.ItemEBSV2.CAVS.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/AIAValidationSystemServlet/syncresponsesimulator | CAVS Endpoint URI |
| ServiceName | UpdateItemListSAPReqABCS | |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the pre-process ABM should be called or not |
| Default.SystemID | SAP_01 | |
| TRACE.LOG.ENABLED | False | |
| ServiceName | ProcessBillOfMaterialsListSAPProvABCSImpl | |
| ABCSEXTENSION.PREPROCESSABM | False | User exit for the pre-process ABM should be called or not |
| ABCSEXTENSION.POSTPROCESSABM | False | User exit for the post-process ABM should be called or not |
| ABCSEXTENSION.PREPROCESSEBM | False | User exit for the pre-process EBM should be called or not |
| ABCSEXTENSION.POSTPROCESSEBM | False | User exit for the post-process EBM should be called or not |
| Default.SystemID | SAP_01 | Used to get the default XREF Target column name when TargetId is empty in incoming EBM. It should be kept SAP_01 as default for this release |
| Routing.Retreive_BOMData.SAP_01.EndpointURI | http://${fp.server.soaserverhostname}:${fp.server.soaserverport}/soa-infra/services/default/BOMServiceESB/BOMServiceESB_ep | ProcessBillOfMaterialsListImpl runtime target endpoint URI |
| TRACE.LOG.ENABLED | False | Use tracelog for the flow |
You must perform the following steps to set up National Language Support (NSL):
· Set up NLS in Agile
· Set up NLS in FMW for Agile
· Edit AIAConfigurations
· Set Up DVMs
· Set up the DVMs for NLS
To set up NLS in Agile:
In Agile Java Client, for each subscriber of MCO, SCO, ECO, go to the subscriber details page and set the language.
Change the language preference of all the users creating CO and Items, including integration user.
To set up NLS in FMW for Agile:
Edit the following XSL file and replace the hard-coded string 'Preliminary' to the preferred language equivalent coming from Agile List values
\AIA_HOME\services\core\Agile\UtilityServices\QueueProcessorServiceImpl\AgileData_to_AgileCreateEngineeringChangeOrderListABM_Impl.xsl
Edit the following XSL file and replace the following values:
\AIA_HOME\services\core\Agile\RequesterABCS\ProcessEngineeringChangeOrderAgileReqABCSImpl\ AgileCreateEngineeringChangeOrderListABM_to_CreateEngineeringChangeOrderListEBM_Impl.xsl
Replace the hard-coded string Preliminary to the preferred language equivalent coming from Agile list values.
Replace the hard-coded string SCO to the preferred language equivalent coming from Agile list values.
Edit the following XSL file and replace hard coded strings Errored with the preferred language equivalent
\AIA_HOME\services\core\Agile\RequesterABCS\ProcessEngineeringChangeOrderAgileReqABCSImpl\ AgileCreateEngineeringChangeOrderListABM_to_AgileUpdateEngineeringChangeOrderListABM_Impl.xsl
Edit the following XSL file and replace the following values:
\AIA_HOME\services\core\Agile\RequesterABCS\ProcessEngineeringChangeOrderAgileReqABCSImpl\ UpdateEngineeringChangeOrderListEBM_to_AgileUpdateEngineeringChangeOrderListABM_Impl.xsl
Replace the hard coded string Transferred with its preferred language equivalent.
Replace the hard coded string 'Errored' with its preferred language equivalent.
|
Note: Use an UTF-8 based editor such as JEdit to perform these tasks. Choose UTF-8 as the character set while loading the file to edit. Set File transfer protocol (FTP) transfer mode to Binary while uploading these files to Oracle AIA components. |
Edit the property LANG_LOCALE under module Agile to the preferred language. The language value is available under column COMMON in the DVM - LANGUAGE_CODE.
To set up DVMs, enter the preferred language values under Agile column, AGILE_01 in the following DVMs:
ITEM_PRIMARYCLASSIFICATIONCODE
ITEM_STATUS_CODE
ITEM_UOM_CODE
ECO_STATUS_CODE
After all the xsls are modified, the corresponding process flows must be redeployed for the xsl changes to take effect.
DVMs are a standard feature of the Oracle SOA Suite. They enable you to equate lookup codes and other static values across applications, for example, FOOT and FT or US and USA.DVMs are static in nature, though administrators can add additional maps as required. Transactional business processes never update DVMs; they only read from them. DVMs are stored in XML files and cached in memory at run time.
DVM types are seeded for the Agile PLM Integration Pack for SAP: Design to Release pre-built integration flows and administrators can extend the list of mapped values by adding more maps. The DVM data should be synchronized with what the participating applications use. This synchronization should occur before any initial loads are run or any incremental transactional flows are initiated.
During installation, the DVMs used for the pre-built integration are imported with default data mappings. The values mapped by these DVMs must be changed as required. Many DVMs are seeded and do not require any changes. Because most of the Agile PLM attributes being mapped are list values, the Agile PLM data is not seeded and should be changed accordingly and then updated to MDS.
During installation, the DVMs used for the pre-built integration are imported with default data mappings. The values mapped by these DVMs have to be changed as needed. There are many DVMs that are seeded and need not be touched. Since most of the Agile attributes being mapped are list values, the Agile data is not seeded. Hence, it should be changed accordingly and then updated in the MDS.
Some of the most used DVMs, with their out-of-the-box (OOTB) values, are listed here. You can modify their values as per your requirements. For complete list of available DVMs, including the most used ones, see the "List of DVMs".
|
Note: You can only add more rows of value mappings and must not change the DVM name, the column names, or the number of columns. |
ECO_ENGINEERINGCHANGEORDERLINE_STATUS_CODE
Used for SAP attribute - ECO_ATTR/ECO_REVISED_ITEM_TYPE/ECO_REVISED_ITEM_TYPE_ITEM/STATUS_NAME
| SAP_01 | COMMON |
|---|---|
| Release | RELEASE |
| Open1 | OPEN_1 |
| EBS_Release | EBS_RELEASE |
| EBS Open | EBS_OPEN |
| Implemented | IMPLEMENTED |
| Create | CREATE |
| In Progress | IN_PROGRESS |
| Scheduled1 | SCHEDULED_1 |
| Cancelled | CANCELLED |
| Approval | APPROVAL |
| Pending Response | PENDING_RESPONSE |
| EBS_Create | EBS_CREATE |
| EBS_Review | EBS_REVIEW |
| EBS_Archive | EBS_ARCHIVE |
| Completed | COMPLETED |
| Hold | HOLD |
| Draft | DRAFT |
| Review | REVIEW |
| Released | RELEASED |
| Archive | ARCHIVE |
ECO_STATUS_CODE
Used for SAP attribute - ECO_CHANGE_ORDER_TYPE/STATUS_NAME, ECO_REVISED_ITEM_TYPE/STATUS_NAME. Use for Agile's Status attribute of a Change.
| SAP_01 | COMMON | AGILE_01 |
|---|---|---|
| Release | RELEASE | |
| EBS_Approval | EBS_APPROVAL | |
| Open1 | OPEN_1 | |
| EBS_Release | EBS_RELEASE | |
| EBS Open | EBS_OPEN | |
| Implemented | IMPLEMENTED | Implemented |
| Create | CREATE | |
| In Progress | IN_PROGRESS | |
| Scheduled | SCHEDULED | Released |
| Cancelled | CANCELLED | |
| Approval | APPROVAL | |
| Pending Response | PENDING_RESPONSE | |
| EBS_Create | EBS_CREATE | |
| EBS_Review | EBS_REVIEW | |
| EBS_Archive | EBS_ARCHIVE | |
| Completed | COMPLETED | |
| Hold | HOLD | |
| Draft | DRAFT | |
| Review | REVIEW | |
| Released | RELEASED | |
| Archive | ARCHIVE |
ITEM_STATUS_CODE
This value is used for SAP Item attribute ITEM_OBJ/MAIN_OBJ_TYPE/INVENTORY_ITEM_STATUS_CODE. The Agile Item Lifecycle phase attribute is mapped.
| SAP_01 | COMMON | AGILE_01 |
|---|---|---|
| A | A | |
| Concept | CONCEPT | |
| Design | DESIGN | Preliminary |
| Engineer | ENGINEER | Pilot |
| Inactive | INACTIVE | Inactive, 02 |
| Lease | LEASE | |
| Non-Stock | NONSTOCK | |
| Nwe B | NWEB | |
| OPM | OPM | |
| Obsolete | OBSOLETE | Obsolete, 02 |
| Pending | PENDING | |
| Phase-Out | PHASEOUT | |
| Production | PRODUCTION | Production, 03 |
| Prototype | PROTOTYPE | Prototype |
| R&D | R&D |
AGILE_SITE_TARGET_MAPPING
DEFAULT_MASTER_ORG in SAP is specified here. This is used when the Multisite_Enabled property is set to False and no Plant is specified for the Item where it extends to.
When the Multisite_Enabled property is set to True, the Sites in Agile are mapped to various Plants in SAP. A Site may be mapped to multiple Plants in the SAP column with | delimiter.
AGILE_TARGET_SITE_MAPPING
The SAP Plants to Agile Sites are mapped. This is used for SAP to Agile flows. There is a one-to-one mapping between the SAP Plant to Agile Site.
This table describes the domain value mappings and their description:
| Domain Value Map | Description |
|---|---|
| ITEM_UOM_CODE: | This DVM is used to maintain the Unit of Measure values of Agile corresponding to SAP |
| REFERENCEMATERIALS: | We are maintaining this DVM to populate the mandatory parameters of SAP BasicData1, Basic data2, MRP1, MRP2, MRP3 views which are not being sent from Agile |
| LANGUAGE_CODE: | This DVM is used to populate the Multi languages, as of now we are dealing with only English language |
| ITEM_STATUS_CODE: | This DVM is used to maintain the Life Cycle Phase codes and Special Plant Material Status of SAP |
| ITEM_PRIMARYCLASSIFICATIONCODE: | This DVM is used to populate the Material type of SAP |
| ECO_STATUS_CODE: | The DVM is used to handle the Status Codes of Change Order in SAP. |
| AGILE_SITE_TARGET_MAPPING | This DVM is used to map SAP Plants to Agile Sites. This is used for Agile to SAP flows |
| AGILE_TARGET_SITE_MAPPING | This DVM is used to map SAP Plants to Agile Sites. This is used for SAP to Agile flows |
| ECO_ENGINEERINGCHANGEORDERLINE_REVISEDBILLOFMATERIALS_BILLOFMATERIALSCOMPONENTITEM_CHANGETYPECODE: | We are using this DVM to recognize the Creation or updation of Bill of Materials in Agile |
Application Interfaces are the web services and APIs that communicate and transact between Application and Integration Layers.
These are the Agile PLM interfaces used in this integration:
WSDLs
| ItemABS.wsdl | Used to create an item in SAP |
| ItemABS.wsdl | Used to update an Item in SAP |
| ChangeABS.wsdl | Used to create an EngineeringChangeOrder in SAP |
XSDs
| ItemABM.xsd | Contains the Item Request and Response ABM |
| ItemABM.xsd | Contains the Update Item List Request and Response ABM |
| EngineeringChangeOrderABM.xsd | Contains CreateEngineeringChangeOrderListABM and CreateEngineeringChangeOrderListResponseABM |
These are the SAP interfaces used in this integration:
WSDLs
| ReserveItemservice.wsdl | The interface to the SAP Process Item API |
| GenerateItemNumberService_Reserve.wsdl | BAPI_STDMATERIAL_GETINTNUMBER |
| ItemServiceESB.wsdl | The interface to the SAP Process Item API - |
| CreateReferencematerial.wsdl | BAPI_MATERIAL_GET_ALL |
| CreateItemService.wsdl | BAPI_MATERIAL_SAVEDATA |
| CreateDetailReferencematerial.wsdl | BAPI_MATERIAL_GET_DETAIL |
| CreateItemRevisionService.wsdl | CCAP_REV_LEVEL_MAINTAIN |
| BOMServiceESB.wsdl | The interface to the SAP Process BOM API |
| BOMPlantExtensionService.wsdl | CSAP_MAT_BOM_ALLOC_CREATE |
| CreateBillOfMaterialService.wsdl | CSAP_MAT_BOM_CREATE |
| BillOfMaterialExistenceCheckService.wsdl | BAPI_MAT_BOM_EXISTENCE_CHECK |
| BOMServiceESB.wsdl | The interface to the SAP Process BOM API - |
| BOMPlantExtensionService.wsdl | CSAP_MAT_BOM_ALLOC_CREATE |
| UpdateBillOfMaterialService.wsdl | CSAP_MAT_BOM_MAINTAIN |
| BillOfMaterialExistenceCheckService.wsdl | BAPI_MAT_BOM_EXISTENCE_CHECK |
| BOMServiceESB.wsdl | The interface to the SAP Process BOM API - |
| BillOfMaterialExistenceCheckService.wsdl | BAPI_MAT_BOM_EXISTENCE_CHECK |
| ECORouterService.wsdl | The interface to the SAP Process ECO API - |
| CreateEngineeringChangeOrderService.wsdl | CCAP_ECN_MAINTAIN |
| MATMAS01_receive.wsdl | The interface to the SAP Process Item API - MATMAS01 |
| ProcessBOMService.wsdl | The interface to the SAP Process BOM API |
| ProcessBillOfMaterialsListImpl.wsdl | CSAP_MAT_BOM_READ |
XSDs
| BAPI_MAT_BOM_EXISTENCE_CHECK_request.xsd | Contains the BillOfMaterialExistenceCheck Request ABM |
| BAPI_MAT_BOM_EXISTENCE_CHECK_response.xsd | Contains the BillOfMaterialExistenceCheck Response ABM |
| CCAP_ECN_MAINTAIN_request.xsd | Contains the CreateEngineeringChangeOrderList Request ABM |
| CCAP_ECN_MAINTAIN_response.xsd | Contains the CreateEngineeringChangeOrderList Response ABM |
| MATMAS01_event.xsd | Contains the UpdateItemList ABM |
| BAPI_STDMATERIAL_GETINTNUMBER_request.xsd | Contains the ReserveItem Request ABM |
| BAPI_STDMATERIAL_GETINTNUMBER_response.xsd | Contains the ReserveItem Response ABM |
| BAPI_MATERIAL_GET_ALL_request.xsd | Contains the CreateReferencematerial Request ABM |
| BAPI_MATERIAL_GET_ALL_response.xsd | Contains the CreateReferencematerial Response ABM |
| BAPI_MATERIAL_GET_DETAIL_request.xsd | Contains the CreateDetailReferencematerial Request ABM |
| BAPI_MATERIAL_GET_DETAIL_response.xsd | Contains the CreateDetailReferencematerial Response ABM |
| BAPI_MATERIAL_SAVEDATA_request.xsd | Contains the CreateItem Request ABM |
| BAPI_MATERIAL_SAVEDATA_response.xsd | Contains the CreateItem Response ABM |
| CCAP_REV_LEVEL_MAINTAIN_request.xsd | Contains the CreateItemRevision Request ABM |
| CCAP_REV_LEVEL_MAINTAIN_response.xsd | Contains the CreateItemRevision Response ABM |
| BAPI_MAT_BOM_EXISTENCE_CHECK_request.xsd | Contains the BillOfMaterialExistenceCheck Request ABM |
| BAPI_MAT_BOM_EXISTENCE_CHECK_response.xsd | Contains the BillOfMaterialExistenceCheck Response ABM |
| CSAP_MAT_BOM_ALLOC_CREATE_request.xsd | Contains the BOMPlantExtension Request ABM |
| CSAP_MAT_BOM_ALLOC_CREATE_response.xsd | Contains the BOMPlantExtension Response ABM |
| CSAP_MAT_BOM_CREATE_request.xsd | Contains the CreateBillOfMaterial Request ABM |
| CSAP_MAT_BOM_CREATE_response.xsd | Contains the CreateBillOfMaterial Response ABM |
| BAPI_MAT_BOM_EXISTENCE_CHECK_request.xsd | Contains the BillOfMaterialExistenceCheck Request ABM |
| BAPI_MAT_BOM_EXISTENCE_CHECK_response.xsd | Contains the BillOfMaterialExistenceCheck Response ABM |
| CSAP_MAT_BOM_ALLOC_CREATE_request.xsd | Contains the BOMPlantExtension Request ABM |
| CSAP_MAT_BOM_ALLOC_CREATE_response.xsd | Contains the BOMPlantExtension Response ABM |
| CSAP_MAT_BOM_MAINTAIN_request.xsd | Contains the UpdateBillOfMaterial Request ABM |
| CSAP_MAT_BOM_MAINTAIN_response.xsd | Contains the UpdateBillOfMaterial Response ABM |
| CSAP_MAT_BOM_READ_request.xsd | Contains the Read BOM Request ABM |
| CSAP_MAT_BOM_READ_response.xsd | Contains the Read BOM Response ABM |
Based on the roles defined for the services, email notifications are sent if an error occurs. The roles below can be assigned at various levels in a hierarchy (service, process, domain) so that when a service errors out -- the Error Handling Framework uses the role value to derive the user(s) that must be notified of the error. The Error Handling Framework then notifies the user(s) through their preferred notification method, puts the error in the user's Oracle Worklist as well as in the error log.
Role: Actor role associated with the error notification. Actor roles receive notifications for and are assigned to error scenarios occurring in Oracle AIA integration flows. An example of an Actor role is a task editable in the Error Console and is meant to be worked on, and resolved by the actor assigned to the task.
FYI Role: For Your Information (FYI) role associated with the error notification. This role receives FYI notifications for error scenarios occurring in Oracle AIA integration flows. An example of an FYI role is a customer service representative (CSR). The task is displayed in read-only view in the Error Console.
For more information about Oracle AIA error handling, see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1,"Setting Up Error Handling."
Any failure in the processing of a change order is captured by Queue Manager. This Errored process can be identified in Queue Monitor, symbolized by.
To see the reason for the error, click the link Errored in the Process Status column.
This Error Message comprises two parts:
Error Text - This is the description of the error source, which can be from any of the participating ABCS services that faulted.
Details - The error details consist of:
Service Name: The name of the service where an instance failed to run
Instance ID: The identification number of the instance that failed
Multiple faults generated by the service are captured and displayed in this UI. In addition to this, any failures in the flows are captured in the AIA Error Logs. These can be seen from the Enterprise Manager Console logs section.
In an event in which a certain service is down and the error is not related to the payload users can resubmit the change in the Queue Manager UI.
This section provides an overview of the error-handling and recovery options available for initial load of items and discusses:
Transaction Handling
Recovery Options
Overview
Errors raised either by an item extract process or an item load process due to a system error are logged by the AIAAsyncErrorHandling process as a failure and no error files are created. You need to restart the process when the system is functional. The BPEL process is marked as a failure in the Enterprise Manager (EM) console.
While loading item data into Agile PLM, if an error occurs when one or more items in the input
file are added or updated, then an error file is created which contains only erroneous item rows. The process continues with the remaining correct items in the file and eventually the processed file is archived. The BPEL process is marked as successful in the EM console.
The XML file with erroneous item rows must be corrected, and resubmitted depending on the kind of error.
If the items are successfully added in the Agile PLM but subsequent cross-references updates fails, then the AIAAsyncErrorHandling process is invoked and no error files are created.
The item load processed file is not archived and is marked as a failure in the EM console.
Transaction Handling
The item extract process is a read-only process and therefore no transactions are associated with it. For item load process, the transactions associated with BPEL and Agile web service are different. For example, the agile web service uses SOAP/ HTTP and acts as a communication interface for loading items into Agile PLM. Therefore, the item extract process does not participate in the transaction of the BPEL process.
Recovery Options
The item extract process can be run multiple times even after a failure as it just overwrites the current file if it exists. The item load process may fail under different scenarios and the error recovery options for these failures differ accordingly. The following table lists different error recovery options made available for different types of item load failures.
Recovery options
Type of Item Load Failures Recovery Options
| System error | Resubmission of the processing file is the recovery option. |
| Cross-reference update failure when you update item details. | Retrieve the processing file from the archiving folder and
resubmit it for processing |
| Synchronization failure. When you update item details, if the Agile web service fails to synchronize the item data with Agile PLM, then erroneous item rows are written to a
separate file in the failed message folder. |
You must select the error file, correct the item data and resubmit
for recovery. |
Viewing EBO EIMs
For more information about using XSL Mapping Analyzer (XMAN), see Oracle Fusion Middleware Infrastructure Components and Utilities User's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1, Using the XSL Mapping Analyzer.
For more information about how services are mapped, see the My Oracle Support document: EBO Implementation Maps (EIMs) 1095494.1.
