Thursday, August 3, 2017

How to track EAM Assets in Oracle Installed Base

Track EAM asset in Installed Base

In order to track EAM assets in Oracle Installed base:

1. Enable the Inventory item(EAM Asset) to be Installed Base trackable by checking the flag under service tab in Item Master UI.
2. Enable the Transactable flag in the Inventory tab of Item Master UI.

The above two are key setups required to track an EAM asset in IB.
Verify this by following use case:

1.       With above two setups in place for the Inventory Item Create Asset in EAM module
2.       As the asset is created in EAM a new record for the item will be created in IB as a new item instance.

3.       Now Update the Asset in eAM  and a new transaction record will be inserted in IB

Wednesday, February 19, 2014

Warranty Contract Creation in Oracle Applications CRM Service Contracts

In order to have warranty contracts created for the items being shipped to customer below are the mandatory setups required.
1.       The item which needs to be shipped to the customer should be defined as an Install Base Trackable item.
2.       Create a Warranty Coverage Template in Service Contracts module.
3.       Define a warranty program by creating the same as an inventory item in Oracle Inventory.
4.       Under Services Tab of Item Master form in Inventory module provide the Contract Item Type as Warranty, Duration in numbers, Duration Period (Days, Months or Years). In the template field provide the coverage template name as created in step2. You can provide a numeric value in starting Delay (Days) this will put the start date of the contract as shipping date plus these many days.  
5.       Make the item as customer order enabled and Save the item definition.
6.       Define a BOM for the item which needs to be shipped to the customer location and add the warranty item to the BOM configuration.
Above are the mandatory setups for creating a warranty contract.
Now enter a sales order for the item which needs to be shipped to customer location.
Complete the Order Booking, Pick Release and Ship Confirm activity for the sales order. Once the shipping is complete the SFM queue will create the Install Base instance for the shipped item and a corresponding warranty will be created in service contracts module.

Friday, August 9, 2013

Install Base Instance creation for an Intangible non-shippable item on a sales order.

In order to start with this topic one should have a clear understanding of Tangible and Intangible items.
Tangible Items: Items which are physical and exists in real world are known as tangible items. Install base instances can be used to track such items. This includes all the items which you can see from your eyes and can feel by touching. Like your computer laptop, mouse and so on.
Intangible Items: Items which cannot be seen but exists in virtual world or in business processes such as licenses, software, services and agreements. Install base instance can be leveraged to track such assets too.
The below fig depicts a high level flow of the Order processing for both Tangible (Shippable) item and Intangible (Non-Shippable) Item:

Oracle Install Base tracking of intangible items at fulfillment requires workflow customization as defined below:
Tracking intangible items, which are non-shippable and non-stockable, requires a separate procedure because Oracle Installed Base has no direct interaction with Oracle Inventory. With the sales order fulfillment these intangible items are created and tracked. For this an integration of Oracle Installed base with Oracle Order Management is required this integration is achieved by modifying the order line workflows. The following two steps are required to modify order line workflows to enable Oracle Installed Base tracking for intangible items:

Setup Oracle Workflow Builder

The workflow builder setup is done in oracle workflow Builder.
1.> Using Oracle Workflow builder on your client PC connect to the database of your dev instance.
2.> Select OM Order Line from Show Item Types window.
3.> Click << button to move to visible list, and click OK.
4.> In navigator window expand the list by clicking on + sign.
5.> Click OEOL/OM order line to select it, and now you can add a new function.
6.> Choose Edit>New>Function from the menu.
7.> In the activity tab page provide Internal Name: INSTALL_BASE_INETRFACE, Display Name: Install Base Interface, Description: IB interface for fulfillable order lines, Function Name: CSI_ORDER_FULFILL_PUB.FULFILL_WF, Function Type: PL/SQL, Result Type: Blank
8.> In the details tab page Error Item Type: WFERROR, Error Process: RETRY_ONLY, On Revisit: RESET.
9.> Once clicked on OK, you can create a new process and assign this new function to the new process.
10.>               Select processes, right click the order line flow that you want to customize and choose copy, once you apply paste the process property window opens.
11.>               Enter a different internal name and display name for the newly created process and click ok. The process is now created.
12.>               Open the process as created above and click on new function. Click the Internal Name LOV and choose Install Base Interface.
13.>               Delete the line after the fulfill function. This line is the one going from fulfill to the node after Fulfill. Insert Install base Interface after the fulfill function; drag the Fulfill to the Install base Interface. Now drag the Install base interface to the node after Fulfill. Choose Any for option results and Save.

Setup oracle Order Management Transaction Type

Below steps can be used to set up the required transaction types in Oracle Order Management.
1.>   Navigate to Order Management Super User (R)-> Setup(F)-> Transcation types
2.>   Query the desired transaction types and assign workflows.
3.>   End Date appropriate seeded line types using seeded workflows.
4.>   Create another record with the same line type as above.
5.>   Assign modified workflow process as above to this line type and save.

Process The Sales Order for an intangible non-shippable item as below:

Once the above two steps are complete the sales order lines which would be using the newly customized workflows will have an interface to Oracle Installed Base. Below steps can be leveraged to process the sales order for Intangible items.
Place an order for an intangible non-shippable item through Oracle Order Management using the customized line type.
·         Book the Sales Order.
·         Run the Workflow Background process.
·         View the instance created in Install Base.

Thursday, August 8, 2013

How and when an Instance is Created in Oracle Installed Base?

In order to create an Install Base instance for an inventory item in oracle one has to mark the item as Install base trackable at master organization level. This can be done in Item Master under service tab. Once the item is set up as trackable in Oracle Install Base, then an inventory receipt such as miscellaneous receipt or PO receipt creates or updates an Oracle Install Base instance. These inventory transactions send a message to SFM Event queue which updates the Oracle Installed Base.

For non-serialized items, if an instance already exists then the new instance is added to the quantity of existing one at the same location.
If an item is serial controlled at receipt, then an instance is created with quantity 1.
If an item is serial controlled at order issue, then it is treated as non-serialized in inventory and only when the order is issued it gets a serial number and an instance is created with this serial number.

For an Oracle Installed Base trackable, shippable item, a shipping transaction generates an inventory issue transaction in Oracle Inventory. If the inventory item is serialized (serialized at receipt) this transaction would change the location and ownership depending upon the transaction type being used. But if the item is serialized at sales order issue this shipment transaction causes the creation of a new instance with the serial number. For non-serialized items, the quantity is subtracted from the instance at inventory location, and a new instance is created with customer ownership and location.


Once the IB instance is created, then any subsequent inventory transactions will be tracked in Oracle Installed Base as well. For any inventory transfer or move order transactions the location of an instance is updated to reflect the new location for a serialized item. For a non-serialized item, the quantity for the instance at the TO location is increased and is subtracted at the FROM location with the quantity which is being moved. If there is a WIP job opened for the item then the location of the item reflects the WIP job number.

Oracle Install Base WebADI Mass Update Feature - How to Use?

With Release 12.1.3 oracle has introduced the functionality for Mass Update of Install Base Item Instances using the desktop Integrator WEBADI tool. Oracle introduced the WebADI batch type with release 12.1.3 by patch 16095785:R12.CSI.B. In order to proceed with using the Mass Update batch type WebADI one has to apply the above patch first.
After the patch is applied check first if all mandatory Install Base setups are in place. The most important would be to set the profile option “Service: Inventory Validation Organization” to a valid organization.
Once the above setups are complete login to Oracle Installed Base Agent User Responsibility (R) -> Item Instances and click on Mass Update as shown below


In the Mass Update windows choose create batch option as WEB ADI and click on GO.

Now provide a unique Batch name for your batch as shown below and in Action there are two operations available:
·         Manage Item Instances:-> Choose this option to create new Item Instances.
·         Search and Manage Item Instances:-> Choose this option to update the existing item instances in the system.


Manage Item Instances

After choosing Manage Item Instances and clicking on Next below screen appears, and now you have to choose the viewer the below options are available. I would recommend clicking on Excel 2007 if you are on a higher version of MS Excel. In this document we will be going with Excel 2007.


Once you click on Next oracle will start downloading an excel file to your local machine choose Open once the below dialogue box opens.



Now as the excel opens click on Enable editing if below message appears.



Next the below message will appear and click on Enable Content.
As you click on Enable Content the below screen appears,



Finally the WebADI gets downloaded as shown below with the configuration message click on close and now your webADI is ready for mass creation.



In case you are having trouble with the download and excel open’s up with below error the please refer to my previous article on this blog as how to resolve this error.



Now we can start entering data to this sheet the first column Upl is a flag column which automatically gets marked as you enter data in the particular row. The columns named as LOV are validating the data against the Oracle DB in real time and you can use the same to search the required data like as shown below for Organization LOV.



As you are done with entering the data you can use the below menu to upload the data to oracle.



Once you click on Upload below message appears now select Rows to Upload as Flagged Rows and only select All Rows if you want to upload all rows which are available in excel sheet. Please take care when you are selecting All Rows there should be no blank rows in the sheet else your upload process will error. Keep both the check boxes checked to validate the data before upload and to Automatically submit Import program. Click on Upload




The below message appears if the upload is successful. With the request number generated here you can query the concurrent request by navigating to the form based application and check if the instance were uploaded successfully or not. The Output file shows the report for success and failure with new generated instance numbers.  Shown below is a sample output as well.



If the upload message says error or invalid then you can navigate towards the last column of the sheet with column Header as Messages and you can find the error message. Below this appears as green because the batch was uploaded successfully.


Search and Manage Item Instances


If one tries to use Search and Manage Item Instances option the below search window is available to search the existing item instances and once clicked on Export the WebADI is downloaded to local machine and one can perform the updates in the same fashion as explained above.



Key Features
  • Single user interface to search and manage one or more item instances in a single window
  • Allows creation of one or more Item Instances
  • Enables splitting of item instance quantity on update
  • Enables create / update of contract associations on item instances
  • Provides feasibility to add Batch note to uploaded instances (both updated and created instances)
  • Supports DFF attribute values and pricing attribute associations
  • Allows view, mass update, mass corrections and reload of item instances and configurations
  • Validates fields in Mass Update UI; Leverage the full power of Excel
  • Faster Data Upload and Re-upload
Limitation

  1. Item Instance Party-Contacts Association can be displayed only at top level. ie. Only one level of association is only possible with Webadi excel.
  2. Bill To and Ship to Association can be only added and no update is possible on these associations.
  3. Contracts covered at the product level alone would be displayed in the excel.
  4. There will be no contract impact on Item Instance owner change.
  5. Operational Status code will be defaulted to 'NOT_USED' and that is the only supported code through Webadi-Ib Mass Update.
  6. Inventory owned instance cannot be updated as there is a limitation on the location details displayed. Since the user will not be able to fetch the values for location as location type code inventory is not present, subinventory details are not present it will throw error saying location details are mandatory.

Friday, August 2, 2013

R12 Using Install Base Web ADI - Run-time error'1004' Method 'VBProject' of object '_Workbook' failed

R12 Using Install Base Web ADI  

In order to know about “How To Use Install Base WebADI Mass Update Feature In Release 12.1.3” please check the metalink DOC ID 1536498.1.
Here we will explain how to resolve the error Run-time error'1004' Method 'VBProject' of object '_Workbook' failed.
After you download the WEB ADI for IB most of the users receives the below error

 In Excel 2003:
go to "Tools" > "Macro" > "Security" and select the "Trusted Sources" tab.  Check the box next to "Trust access to Visual Basic Project".
(Note: The box for "Trust all installed add-ins and templates" should also be checked.)


For Excel 2007

Step1: Go to excel and click on office button. Click on Excel Options







Step2: Go To Trust Center Tab. Click on Trust Centre Settings

 

Step3: Go To Macro Settings Tab. Enable Check Box Trust Access to the VBA project object model



Step4: Click on OK




Step4: Restart the machine and open the WebADI



For Excel 2010: You will find the option under the File menu




Tuesday, June 11, 2013

Service Contract Billing – Arrears and Advance Invoicing with Entering Offset Days for Interface

Service Contract Billing – Arrear and Advance Invoicing with Entering Offset Days for Interface

Release: R12.1.2 

Using the Service Contracts Manager responsibility:
  1.  Navigate to Launch Contracts from the Main Menu.
  2.  Open the Contract Navigator tab.
  3.  Position the cursor on the desired Contract Group.
  4.  Position the cursor on the desired contract.
  5.  Select 'Tools' from the toolbar; select 'Open'.
  6.  Open the Lines tab.
  7.  Open the Pricing / Products subtab.
  8.  Press the Billing Button.
  9.  Enter the information for a Stream Level.  This is an example
      of the input:
      Seq No = 1
      Periods = 24
      UOM/Period = 1
      Period = Month
  10. Press the Schedule button.
  11. Take note of the values in the Interface Date on each line of the
      Billing Schedule.
  12. Enter a negative value (x) in the Interface Offset Days for the Billing
      Stream.
  13. Press the Schedule button.  Note that the Interface Date changes on
      each line of the schedule.  The Interface Date is (x) days earlier than
      the Bill From date on each line of the schedule.

Further explained the same as below: 
So, if the line level billing period is suppose from 1-Jun-2013 to 30-Jun-2013, then the invoicing rule acts as below: 
If Invoicing rule is Arrear invoice -> Billing will be done(i.e. lines will be interface to AR for billing) for this period on 01-Jul-2013. As shown below:


Whereas, if Invoicing rule is chosen as Advance Invoice -> Billing will done (i.e. lines will be interface to AR for billing) for this period on 1-Jun-2013, As shown below:


The billing date (Interface Date) can be controlled using the offset days field next to Total amount in above screenshots.
So suppose if you provide the offset days as -30 in above scenario of Advance Invoice the billing date (Interface Date) will be changed to 02-May-2013. (i.e. 30 Days in Advance).
Whereas, if you provide the same value as +30 for the Arrears Invoice scenario above the dates will be postponed till 31-JUL-2013 and with a negative offset of -30 the dates will be preponed to 01-Jun-2013.

Note: For Advance Invoicing the Interface Date defaults to the earliestof these dates:
 - Invoice Date
- Bill From Date
- Bill From Date + Interface Offset

The date must be greater than or equal to the sysdate.