1. Implementing Manufacturing and Supply Chain Materials Management
  2. Manage Interface Tables for Supply Chain Orchestration

Manage Interface Tables for Supply Chain Orchestration

Use a scheduled process to delete supply requests and keep your interface tables running at optimal performance.

This scheduled process removes records from database tables, and that reduces the load on your queries.

  1. Go to the Scheduled Processes workarea.
  2. Click Schedule New Process.
  3. Search for the Purge Supply Chain Orchestration Interface scheduled process.
  4. Set the parameters.

    Parameter

    Description

    Supply Request Status Specify the status of the supply request that you want this process to consider. The process will look only at supply requests that are in the status you specify.

    For example, set it to Success, and the process will only look at supply requests that have a Success status.
    From Creation Date

    To Creation Date

    		 Filter the data that you want to process according to the supply request's creation date.
    Supply Type

    Specify the type of supply. The scheduled process will look only at the type of supply requests that you specify. For example, set it to:

    • Buy. The process will look only at purchase orders.
    • Make. The process will look only at work orders.
    • Transfer. The process will look only at transfer orders.
    Supply Request Source Specify an application. The scheduled process will look only at supply requests that it received from the application that you specify.

    For example, if you set this parameter to Order Management, the process will look only at supply requests that it received for Order Management.
    From Supply Request Batch Number

    To Supply Request Batch Number

    		Filter the data that you want to process according to the supply request's batch number.
    From Supply Request Reference Number

    To Supply Request Reference Number

    Filter the data that you want to process according to the supply request's reference number.

    For details about reference numbers, see Create Supply Requests.
Note

Guidelines

  • We recommend that you run this scheduled process regularly to help manage how much data you keep for your supply requests. We recommend that you keep data for the past three months to support troubleshooting efforts.

  • If you set the Supply Request Status parameter to On Hold, then the process will delete records that remain on hold after the item ships.

    The scheduled process normally deletes records when they move through various statuses, such as Success and Closed. In some rare instances, back-to-back processing might not finish as expected, records that are in the On Hold status don't get updated to the current status, such as Closed, so they don't get deleted. You can use the scheduled process to delete them.

  • Get a report that includes a summary of what the scheduled process achieved, and details about the records that the scheduled process deleted. If you enable the Report Only option, then the scheduled process will create a report that you can use to see what records the scheduled process will remove before you actually remove them. If all looks good, you can run the scheduled process again but disable the Report Only option.
  • Use each From and To set of parameters to filter for a range of values. For example, set the From Supply Request Batch Number parameter to 100, and set the From Supply Request Batch Number parameter to 200, and the process will look at all supply requests that in batches 100 through 200.
  • Avoid performance problems. If you have a large number of records, then use one or more sets of From and To parameters to filter the number of records that you will process, and run the process more than one time. Assume you need to delete all supply requests that you received during the month of March. Assume you received approximately 100 requests on each day. You can run the process three times and process about 1,000 records on each run instead of processing about 3,000 records on a single run.
    Run From Creation Date To Creation Date
    1 March 1 March 10
    2 March 11 March 20
    3 March 21 March 31