Comments

  • Venkatesh Malapati

    The Oracle Visual Builder Add-in for Excel allows you to access REST APIs from the spreadsheet to Manage Data from a REST Service Using an Excel Workbook. The Visual Builder Add-in for Excel is evolving and depending on how complex of interface/worksheet you need to build, it may be an option to look into further.

     

     

  • Venkatesh Malapati

    Please refer to Implement Security section which has an example on how to check if the user has a specific role granted or not through an extension.

  • Venkatesh Malapati

    The notification you are referencing don't apply to Order Management Cloud and as mentioned in the earlier update, there are no plans at this time to move away from the current file based data import.

  • Venkatesh Malapati

    There are no plans at this time to support the import maps. Please elaborate the specific need or the requirement you have and we can check if it can be meet with an alternative option.

    If you need the import map support, please log an idea and product development will review the requirement further and prioritize depending on the number of customers who are looking for the same.

  • Venkatesh Malapati

    You will need to write an Order Management Extension if the requirement is to create either header or line level salescredits automatically based of the primary salesperson entered on the header or the line. Rules doesn't support creating the salescredit automatically based of the primary salesperson.

  • Venkatesh Malapati

    This looks to me more of Internal Material Transfer flow. Have you reviewed the documentation for Internal Material Transfer flow.

  • Venkatesh Malapati

    There is an example that I had provided in another post. Please refer to that.

     

  • Venkatesh Malapati

    You should use the Order Management Extension for defaulting from the customer profile/customer. I assume you are planning to use a DFF attribute on the customer to capture the shipping method from which it should be defaulted. Please refer to the post where I provided a sample Order Management extension for defaulting it from the customer.

  • Venkatesh Malapati

    Item substitution is currently supported only on standard items in Order Management Cloud. There is also an ER#28557113  on Order Management for supporting upsell/cross-sell relationship when an order is entered.

  • Venkatesh Malapati

    There is no guaranty the sequence that is in the import file will be followed while the orders are imported as import can be run in multiple threads. Also the sequence in which the orders are scheduled depends on which of the lines get to the scheduling task/step even within that order. The orchestration is at the line level and each line is orchestrated independently unless all the lines are in a ship set or the lines are part of a model/kit. So the sequence in which the line hits the scheduling task is likely to be the influencing factor in terms of the sequence that is likely to be followed for scheduling and which is dependent on multitude of factors such system load conditions, which import thread/webservice threads/SOA threads run quicker. So the sequence in the import file shouldn't be relied for any scheduling sequencing/priority.

    You probably may want to either evaluate manual scheduling if the number of lines that you are trying to schedule are small in number or may have to use the override scheduling mode. Both of these are recommended only for small set of lines.

    You can import the orders where the orchestration process is setup to require Manual Scheduling and then using GOP check availability UI you can reorder the lines using the override priority. This option is recommended only for small number of lines. You need to multi-select the lines and then select check availability option as shown in the attached screenshot.

    Please also check on the with Supply Chain Planning team for the timelines & availability of the backlog management which might possibly be a fit for this scenario. Which customer is this needed for and are they already live?

  • Venkatesh Malapati

    If the order is pre priced in an external application/channel, then you can send in the  "FreezePriceFlag": true which requires the charge & charge components to be sent in when the order is being created. Whereas the order is priced in Fusion and in which the   "FreezePriceFlag": false is what you will send as and the charge & charge components won't be required to be passed.

    So depending on whether the order is pre-priced or not, the charge & charge components need to be sent. Please note sending the  "FreezePriceFlag": true means the order will never be repriced in Order Management Cloud.

  • Venkatesh Malapati

    If there are webservices available for creating a project & task from the Project Management Execution, those can be invoked either from the Order Management Extensions or from the Orchestration process during the fulfillment using the Template Task Layer. The same applies to the subscription management. You should check with the Project Management Execution & Subscription Management SOAP webservices documentation for the availability of the services.

    Please refer to the support note, How To: Defining Order Management Extensions - Including Examples (Doc ID 2428750.1) and the implementation guide.

    https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/19d/faiom/extend-your-set-up.html#FAIOM2829675

    For using the Template Task Layer in the Orchestration process and invoking the Project Management Execution & Subscription Management services through the Template Task Layer, please refer to the documentation and section on Overview of Connecting Order Management to Your Fulfillment System. Using Template Task Layer requires the development of connector or deployment of the connector either on OIC or some other integration platform.

    https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/19d/faiom/integrate.html#FAIOM3551586

     

  • Venkatesh Malapati

    Can you share the JSON payload along with the URL you used for the patch?

     

    The following URL for POST along with the payload referenced below for creating the order works for me. I further subsequently used the patch operation for changing the warehouse on the line. 

    Please note this was for a Fusion Priced Order where the freezeflags were sent as false and hence the charge & charge components don't need to be passed in the payload. Only if it is a pre-priced order, then the charge & charge components need to be passed in the payload while creating the order. But for change, only whatever the attributes that are being changed need to be sent in the payload as shown for the warehouse example below.

    https://host:port/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub/

    {
       
        "SourceTransactionNumber": "VM1",
        "SourceTransactionSystem": "GPR",
        "SourceTransactionId": "VM1",
        "BusinessUnitId": 204,
        "BusinessUnitName": "Vision Operations",
        "TransactionOn": "2019-10-04T18:35:19+00:00",
        "BuyingPartyId": 1006,
        "BuyingPartyName": "Computer Service and Rentals",
        "BuyingPartyNumber": "1006",
        "RequestedShipDate": "2019-10-04T18:35:19+00:00",
        "RequestingBusinessUnitId": 204,
        "RequestingBusinessUnitName": "Vision Operations",
        "RequestingLegalEntityId": 204,
        "RequestingLegalEntity": "Vision Operations",
        "FreezePriceFlag": false,
        "FreezeShippingChargeFlag": false,
        "FreezeTaxFlag": false,
        "lines": [
            {
                "SourceTransactionLineId": "1",
                "SourceTransactionLineNumber": "1",
              "SourceTransactionScheduleId":"1",
              "SourceScheduleNumber":"1",
                "TransactionCategoryCode": "ORDER",
                "ProductId": 149,
                "ProductNumber": "AS54888",
                "ProductDescription": "Standard Desktop",
                "OrderedQuantity": 6,
                "OrderedUOMCode": "Ea",
                "OrderedUOM": "Each"
              }
    ]
    }

    For patch, use the following URL. For the Order Key in the URL, you will have to provide the sourceordersystem:sourceorderID as shown below.

    https://host:port/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub/GPR:300100180763845

    {
    "lines": [
    {
    "FulfillLineId":300100180763870,
    "RequestedFulfillmentOrganizationCode": "M1"

    }
    ]
    }

     

     

  • Venkatesh Malapati

    I am not seeing the same error in 19C environment where I tried as what you are running into. I suggest you follow through with support through an SR.

    The following payload works for me except where the backordered line got canceled. But the line that was at awaiting billing ran into an error for which a defect is already tracked.

    https://host:port/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub/GPR:300100181813776

    {
    "lines": [
    {
    "FulfillLineId":300100181814670,
    "OrderedQuantity": 0

    }
    ]
    }

  • Venkatesh Malapati

    Yes, the REST API allows the backordered line to be canceled. Even though the backordered line does get canceled, we have seem in some instances where the shipped line which is at Awaiting Billing is going into an error state upon the cancellation of the backordered line and there is a defect that is tracked for that scenario. Are you seeing the same issue in your case as well?