Manufacturing

Get Involved. Join the Conversation.

Topic

    Bala krishna
    Backdate Close Status for Manufacturing Work Orders
    Topic posted August 8, 2019 by Bala krishna, tagged Work Execution 
    32 Views, 1 Comment
    Title:
    Backdate Close Status for Manufacturing Work Orders
    Summary:
    Backdate Close Status for Manufacturing Work Orders
    Content:

    Hi All,

    In the recent 19C patch, there is a new feature related to Mfg (see the below details). I wanted to understand, if this feature applies to Contract Manufacturing Org (CMO) process ? Also is it possible to edit the Closed work order in a CMO process? Can someone please clarify.

    ==========================================================================================================

    You can specify a work order close date that is earlier than the system date (referred to as backdating) in Oracle Manufacturing Cloud. This enables you to book the cost accounting entries for close in a prior open period even as you transition to the next period.

    The accounting of scrap, product cost adjustments, and variances now use this user-specified close date rather than the date the work order was closed.

    Consider the following example:

    • Let’s assume the system date is 02-May.
    • You close the work order on 02-May, but specify a close date of 30-April.

    In this scenario, the user-specified date of 30-April is used as the work order close date.

    You cannot enter a date that is earlier than the latest material or resource transaction. In addition, if you enter a date that is earlier than an existing costed transaction for the item, then the date would be set to immediately after the existing costed transaction.

    Let’s take another example:

    • The system date is still 02-May.
    • The last transaction reported for the work order is 17-April.
    • You close the work order on 02-May and specify a close date of 30-April.
    • There was a product completion for the same finished good from a different work order on 01-May and that transaction has already been costed and accounted.

    In this scenario, the costed and accounted date for this work order close event is 01-May, because a transaction already exists for the combination of cost organization, cost book, item and valuation unit.

    STEPS TO ENABLE

     

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

     

    ROLE INFORMATION

     

    • Privilege Name and Code:
      • Review Cost Distributions (CST_REVIEW_COST_DISTRIBUTIONS)
    • Job Role Name and Code:
      • Cost Accountant (ORA_CST_COST_ACCOUNTANT)
    Version:
    R13, 19C

    Comment