My Oracle Support Banner

Demand Class Is Not defaulted on The Resulting Lot from Starting Lot When ImportingLot Split Transactions (Doc ID 2761889.1)

Last updated on MARCH 21, 2021

Applies to:

Oracle Shop Floor Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior
When performing Lot Split transaction for the lot based job with Demand Class via OIF, Demand Class is not defaulted on the resulting lot from starting lot.
*The issue does not happen when performing Lot Split via form.

Expected Behavior
When performing Lot Split transaction via OIF, Demand Class is defaulted on the resulting lot from starting lot.

Steps to Reproduce

  1. Ensure the Demand Class is set on the lot based job.
  2. Populate below tables

    INSERT INTO wsm_split_merge_txn_interface VALUES l_split_merge_rec;
    INSERT INTO wsm_starting_jobs_interface VALUES l_starting_job_rec;
    INSERT INTO wsm_resulting_jobs_interface VALUES l_resulting_job_rec;
    *Set same demand class in wsm_resulting_jobs_interface.DEMAND_CLASS.

  3. Execute below API

    apps.wsmpload.LOAD (v_err_buf
    ,v_err_code
    ,2
    ,l_group_id ----wsm_sm_txn_int_group_s, if NULL
    ,1);
    .

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.