Types of Move Order

Move orders are created from different sources.

This can be identified from the Move Order header move order type field.

Different types of Move Orders are 

Move Order Requisitions: 

These are created from the move order form. Based on the setup at the organization and item level, move orders require approval before they can be allocated and transacted. These requisitions can be created to charge an account or move the material from one subinventory to another.

Replenishment Move Orders: 

These are auto-created with pre approved status. Depending on the planning type you can replenish the quantity in a subinventory for an item. Three types of replenishment plans (in relation to move orders) are available:

• Min-max Replenishment Planning
• Kanban Replenishment Planning
• Replenishing Count planning

Based on these sources, when appropriate programs are run, move orders are automatically created.

Pick Wave Move Order Requisitions: 

These move orders are specifically for the sales order picking process. When Pick Releasing program is run move orders are created as preapproved and allocated(depending on the Pick Release setup). Pick Confirm process transacts these pick wave move orders.

Query to find the Organization structure of a business

Run this script giving inventory org as the parameter

SELECT MP.ORGANIZATION_CODE,
       HAOU.NAME,

      HAOUBG.NAME BUSINESS_GROUP,
      GSOB.NAME SOB_NAME, /*gsob.short_name,*/
      GSOB.CURRENCY_CODE,
      GSOB.PERIOD_SET_NAME,
      (SELECT SEGMENT1 || ‘.’ || SEGMENT2 || ‘.’ ||SEGMENT3 || ‘.’ ||
              SEGMENT4 || ‘.’ || SEGMENT5 || ‘.’ ||SEGMENT6 || ‘.’ ||
              SEGMENT7 || ‘.’ || SEGMENT8 || ‘.’ ||SEGMENT9
         FROM APPS.GL_CODE_COMBINATIONS
        WHERE CODE_COMBINATION_ID =GSOB.CHART_OF_ACCOUNTS_ID) CHART_OF_ACCOUNT,
      HLE.NAME LE_NAME,
      HLE.VAT_REGISTRATION_NUMBER,
      HOU.NAME OU_NAME
—  ,hri.*
 FROM APPS.HR_ALL_ORGANIZATION_UNITS   HAOU,
      APPS.HR_ORGANIZATION_INFORMATION HRI,
      APPS.MTL_PARAMETERS              MP,
      APPS.GL_SETS_OF_BOOKS            GSOB,
      APPS.HR_LEGAL_ENTITIES           HLE,
      APPS.HR_OPERATING_UNITS          HOU,
      APPS.HR_ALL_ORGANIZATION_UNITS   HAOUBG,
      APPS.HR_ORGANIZATION_INFORMATION HRIBG

WHERE HRI.ORGANIZATION_ID = HAOU.ORGANIZATION_ID
  AND HAOU.ORGANIZATION_ID = MP.ORGANIZATION_ID
  AND MP.ORGANIZATION_CODE IN (‘V1’)
  AND HRI.ORG_INFORMATION_CONTEXT = ‘Accounting Information’
  AND GSOB.SET_OF_BOOKS_ID = HRI.ORG_INFORMATION1
  AND HLE.ORGANIZATION_ID = HRI.ORG_INFORMATION2
  AND HOU.ORGANIZATION_ID = HRI.ORG_INFORMATION3
  AND HAOUBG.ORGANIZATION_ID = HLE.BUSINESS_GROUP_ID
  AND HRIBG.ORG_INFORMATION_CONTEXT = ‘Business Group Information’
  AND HRIBG.ORGANIZATION_ID =HAOUBG.ORGANIZATION_ID; 

Difference in WMS cost group and Inventory cost group assignment

Cost Groups in Oracle WMS are assigned by the Cost Group Rules Engine.
In Oracle Inventory, Cost Groups are derived based on the primary cost Method of the organization and the location where the material is being moved. If the costing method is Standard-Costing, then the Cost Group associated with subinventory is assigned to the material. For the other costing methods, the Cost Group associated with the organization is used.
In Oracle Warehouse Management, once a Cost Group is associated with a material, it does no change when the material is moved within the organization. In Oracle Inventory, the Cost Group associated with the material changes with the location where it is residing.
So in WMS, once the material moved with in the organization, then cost group update needs to be done if you want to change the cost group assigned to the material.