Material Issue API

The Material Issue API facilitates the communication of material issues from Oracle Fusion Supply Chain Management to Oracle Utilities Work and Asset Cloud Service. Once the material issue is created in Oracle Utilities Work and Asset Cloud Service:

  • On-demand and reservation quantities are reduced by the issued quantity if the material request is an activity resource requirement. Additionally, if the material request is fully issued, then the status of the activity resource requirement is also updated to Fulfilled.
  • On-demand and reservation quantities are cleared regardless of full or partial fulfillment if the material request is a standalone (not for an activity).

NOTE: There can only be one material issue per request line. If the material is partially issued, a new material request will be required.

Oracle Fusion Supply Chain Management will update the inventory quantity and average unit price of the stock item detail through the Add Inventory Adjustment API.

This enhances the user experience and reduces implementation costs by supporting the communication of material issues.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  • The following algorithms were added to the Material Issue Line Integration (W1-MaterialIssueLineInteg) business object to support the described behavior:
    • Create Stock Transaction for Issue Line (W1-CSKTXISLN): Responsible for reducing the on-demand and reserved quantities.
    • Determine and Transition Activity Material Requirement (W1-DETTRNAMR): Responsible for updating the status of the activity resource requirement.
  • If the described behavior is not desired, follow these steps to deactivate the algorithms:
  1. Navigate to Lifecycle tab of the Material Issue Line Integration BO.
  2. Broadcast the Issued status.
  3. Click the Edit hyperlink in the Status Details zone.
  4. In the Options section, add a new option for Inactive Algorithm, assign a unique sequence number, and set the Option Value to the algorithm that needs to be inactivated.
  5. Repeat the steps above if deactivating a second algorithm.