Oracle eBS經驗分享

• Transportation Execution Module Tables (FTE)
• Version 11.5.10.2
  FTE_BULKLOAD_DATA
  FTE_BULKLOAD_FILE
  FTE_DELIVERY_PROOF
  FTE_FACILITY_CARRIERS
  FTE_FAILURE_REASONS
  FTE_FREIGHT_COSTS_TEMP
  FTE_INTERFACE_LANES
  FTE_INTERFACE_ZONES
  FTE_INVOICE_HEADERS
  FTE_INVOICE_HISTORY
  FTE_INVOICE_LINES
  FTE_LANES
  FTE_LANE_COMMODITIES
  FTE_LANE_EQUIPMENTS
  FTE_LANE_GROUPS
  FTE_LANE_GROUP_COMPONENTS
  FTE_LANE_RATE_CHARTS
  FTE_LANE_SERVICES
  FTE_LANE_VEHICLES
  FTE_LOCATION_MILEAGES
  FTE_LOCATION_PARAMETERS
  FTE_MESSAGE_ADDRESS
  FTE_MESSAGE_CONTACT
  FTE_MESSAGE_LOCATION
  FTE_MESSAGE_PARTNER
  FTE_MILE_ATTRIBUTES
  FTE_MILE_COLUMN_ATTRIBUTES
  FTE_MILE_DOWNLOAD_FILES
  FTE_MILE_DOWNLOAD_LINES
  FTE_MILE_TEMPLATES
  FTE_MILE_TEMPLATE_COLUMNS
  FTE_MOVES
  FTE_MOVES_INTERFACE
  FTE_PRC_PARAMETERS
  FTE_PRC_PARAMETER_DEFAULTS
  FTE_PTRK_EVENTS
  FTE_PTRK_PAGES
  FTE_PTRK_PARAMS
  FTE_PTRK_SOURCES
  FTE_SCHEDULES
  FTE_SEL_ATTRIBUTES
  FTE_SEL_ATTRIBUTES_TMP
  FTE_SEL_GROUPS
  FTE_SEL_GROUP_ASSIGNMENTS
  FTE_SEL_GROUP_ATTRIBUTES
  FTE_SEL_OBJECTS
  FTE_SEL_RESULTS
  FTE_SEL_RESULT_ASSIGNMENTS
  FTE_SEL_RESULT_ATTRIBUTES
  FTE_SEL_RULES
  FTE_SEL_RULE_RESTRICTIONS
  FTE_SHIPMENT_STATUS_DETAILS
  FTE_SHIPMENT_STATUS_EXCEPTIONS
  FTE_SHIPMENT_STATUS_HEADERS
  FTE_TARIFF_CARRIERS
  FTE_TENDER_SNAPSHOT
  FTE_TRIPS
  FTE_TRIP_MOVES
  FTE_TRIP_MOVES_INTERFACE
  FTE_VEHICLE_FEATURES
  FTE_VEHICLE_TYPES
  FTE_WSH_TRIPS

Demo on New features 12.1.1 In Internal Sales Orders – Internal Requisitions Flow [ID 883508.1]

How to Generate the COGS Account from the Order Type [ID 414314.1]

Modified 26-NOV-2010     Type BULLETIN     Status PUBLISHED

In this Document
Purpose
Scope and Application
How to Generate the COGS Account from the Order Type
References

Applies to:

Oracle Order Management - Version: 11.5.1 to 12.0.6 - Release: 11.5 to 12.0
Information in this document applies to any platform.
FORM:OEXDTTYP.FMB - Define Transaction Types
Checked for relevance on 26-Nov-2010

Purpose

In order to generate the COGS account from the Cost of Goods Sold account assigned to the order type (A.K.A. OM Transaction Type) of the order, the seeded COGS workflow needs to be modified to change the default node from Get CCID for a line to Get CCID from the Order Type ID.  This bulletin will detail the required changes to accomplish this.

Scope and Application

Familiarity with Workflow and Workflow Builder is required.

How to Generate the COGS Account from the Order Type

Background:

The COGS Account Generator is a Workflow Process that derives the Cost of Goods Sold account for a transaction interfaced to Inventory from Order Management/Shipping. The workflow item type ‘OM: Generate Cost of Goods Sold Account’ which has an internal name of OECOGS encompasses all processes designed to build the COGS. The ‘Generate Default Account’ is a seeded process which builds the COGS Account. It comes seeded with the function Get CCID (account ID) for a line. This function will return the CCID assigned to an item as it exists in the shipping warehouse. The intent of this function is to retrieve the CCID from the Cost of Goods Sold assigned to the item on the sales order line within the shipping
inventory organization.

Modifying the 'Generate Default Account' to derive the Cost of Goods Sold account from the Order Type:

1. The first step is to copy the existing 'OM: Generate Default Account’ process. Give it a new name, e.g. 'NEW_DEFAULT_ACCOUNT_GENERATOR', in the property sheet Internal Name field. Please do not simply modify the existing default process.
2. Double-click on the new process from within the Navigator and continue by deleting the link between the ‘Start generating Code Combination’ and the ‘Get CCID for a line’ function. Insert between them the function ‘Get CCID from the Order Type’ by dragging it from the Navigator to the process screen. Using the right mouse button, draw a line connecting the ‘Start generating Code Combination’ to the ‘Get CCID from the Order Type’ function. Save this process definition off to the database.
Point the Chart of Accounts to the new process:
Saving new Workflow Process Definitions to the database is all well and good, but it is of no benefit unless the Chart of Accounts structure can invoke it. The relationship between the Chart of Accounts structure and the Workflow Process for the ‘OM: Generate Cost of Good Sold’ item type is made in the ‘Account Generator Processes’ form (OM: Setup > Financials > Flexfields > Key > Accounts). Using the flashlight icon choose the applicable Chart of Accounts. Then assign the new process to the ‘Generate Cost of Goods Sold Account’ Item Type.

Ensure that the new Account Generator points to the correct Chart of Accounts:

Care must be taken to ensure that the new Account Generator points to the correct Chart of Accounts. To determine the correct Chart of accounts, follow the steps below:

1. Get the value of the Set of Books for the inventory organization for which you wish to interface the transactions. Get this from the Organization Definitions form. (Inv: Setup > Organization > Organizations). Query the name of the inventory organization desired, then with the cursor on the ‘Inventory Organization’ organization classification, click the ‘Others’ button. Choose ‘Accounting Information’.
2. Determine the Set of Books for the Order Management responsibility for which the order is assigned. Accomplish this task in the same way as with the inventory organization as demonstrated above, except place the cursor on the ‘Operating Unit’ line rather than the ‘Inventory Organization’ line. Choose Operating Unit Information.
3. Query this Set of Books up in the Define Set of Books form (Setup > Financials > Books). Record the value for the ‘Chart of Accounts’.
4. Finally, find the workflow process this chart of accounts uses when building the COGS account from the Account Generator Processes form (Setup > Financials > Flexfields > Key > Accounts).

Intercompany IR/ISO => OM: Generate Cost of Goods Sold Account

Intercompany SO => OM : Generate Cost of Goods Sold Account

Standard SO => OM : Generate Cost of Goods Sold Account

Which parameter names are supported in Shipping Document sets ? [ID 1079914.1]

Unexpected Error: Error in Routine WSH_DELIVERY_DETAILS_PKG.CREATE_DELIVERY_DETAILS_BULK,  Oracle Error - 1
User-Defined Exception

Cause

The issue is caused by the following setup: The Shipping Parameters were not setup for the Shipping organization.

Solution

-- To implement the solution, please execute the following steps:
1. Go into the responsibility: Order Management Super User
2. Navigate to Shipping > Setup > Shipping Parameters
3. Setup the parameters for the Shipping Organizations (orgs).
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.

  SELECT l.lookup_code, l.meaning
    FROM so_lookups l
   WHERE l.lookup_type = 'FREIGHT_TERMS' AND l.enabled_flag = 'Y'
     AND TRUNC (SYSDATE) BETWEEN NVL (start_date_active, TRUNC (SYSDATE))
                             AND NVL (end_date_active, TRUNC (SYSDATE))
ORDER BY l.meaning

------------------------------------------------------------------

失效很久沒有使用的Price List : Disable not-used price list

------------------------------------------------------------------

Carrier Setup

Where to maintain {service level}

Issue Description

We cannot use “Workflow Status” when we using new responsility of OM but we can see the function at Toolbar.

Function Name : View Detailed Shipping Status

Responsibility: OM Super User

Navigator : Shipping > Setup > Regions and Zones > Regions and Zones 

Issue description : I cannot choose any value from Country List-of-value at Regions and Zones form.

This may be any positive integer numeric value.
When a line is scheduled it is also automatically reserved whenever the schedule
date is within the reservation time fence.

Sysdate is 27-JUL-2011

Case 1 : SAD > Sysdate +5 days

OM System Parameters

UPDATE  wsh_delivery_details wdd
SET     released_status = 'D'
       ,src_requested_quantity = 0
       ,src_requested_quantity2 = decode (src_requested_quantity2
                                         ,NULL
                                         ,NULL
                                         ,0)
       ,requested_quantity = 0
       ,requested_quantity2 = decode (requested_quantity2
                                     ,NULL
                                     ,NULL
                                     ,0)
       ,shipped_quantity = 0
       ,shipped_quantity2 = decode (shipped_quantity2
                                   ,NULL
                                   ,NULL
                                   ,0)
       ,picked_quantity = 0
       ,picked_quantity2 = decode (picked_quantity2
                                  ,NULL
                                  ,NULL
                                  ,0)
       ,cycle_count_quantity = 0
       ,cycle_count_quantity2 = decode (src_requested_quantity2
                                       ,NULL
                                       ,NULL
                                       ,0)
       ,cancelled_quantity = decode (requested_quantity
                                    ,0
                                    ,cancelled_quantity
                                    ,requested_quantity)
       ,cancelled_quantity2 = decode (requested_quantity2
                                     ,NULL
                                     ,NULL
                                     ,0
                                     ,cancelled_quantity2
                                     ,requested_quantity2)
       ,subinventory = NULL
       ,locator_id = NULL
       ,lot_number = NULL
       ,serial_number = NULL
       ,to_serial_number = NULL
       ,transaction_temp_id = NULL
       ,revision = NULL
       ,ship_set_id = NULL
       ,inv_interfaced_flag = 'X'
       ,oe_interfaced_flag = 'X'
       ,last_updated_by = - 1
       ,last_update_date = SYSDATE
WHERE   EXISTS
        (
        SELECT  1
        FROM    oe_order_lines_all oola
               ,oe_order_headers_all ooha
               ,mtl_system_items_b msib
               ,mtl_parameters mp
        WHERE   wdd.source_line_id = oola.line_id
        AND     msib.inventory_item_id = wdd.inventory_item_id
        AND     msib.organization_id = wdd.organization_id
        AND     wdd.organization_id = mp.organization_id
        AND     oola.header_id = ooha.header_id
        AND     wdd.source_code = 'OE'
        AND     wdd.released_status NOT IN ('C','D')
        AND     oola.org_id IN (86,88)
        AND     oola.flow_status_code = 'CANCELLED'
        AND     ooha.open_flag = 'N'
        AND     EXISTS
                (
                SELECT  1
                FROM    oe_order_lines_all ool
                WHERE   ool.line_id = wdd.source_line_id
                AND     oola.open_flag = 'N'
                )
        );

Document : Pricing Data Bulk Loader API

翻譯 By me…

Overview

這份文件是用來說明”Pricing Data Bulk Loader API”功能的概要。這個功能可以用在Base Pricing 與Advanced Pricing.對於Base Pricing 設置， 只需要提供基本要匯入系統的Pricing 資料即可；”Pricing Data Bulk Loader API”是由一組Interface tables 與一個Concurrent Program 組成。所有的檢核工作與預設值都會在資料被inserte,deleted or updated前就完成，系統會自動把以經成功轉入的資料從Interface Table清除。

We hold on order line.

Order Line –>Action > Additional Line Information.

When user do book ,system display error“Order-level sales credit total () must equal 100%.”

WHY

怎麼找”Generate Constraints Validation Packages”會產生的package

Generate validation package 是抓取”Validation Template”的設定

The generated validation packages all live in the apps schema.

The easiest way to get the name of your package(s) is from the validation_pkg column of the oe_pc_validation_pkgs table. The format is:
OE_{ a }PC{ b }_{ c }_{ d }

where:
a = the validating_entity_id
b = the validation_entity_id
c = the validation entity short name (LINE, ORDER, BLKTHDR, HDRADJ etc.)
d = the validation template short name (i.e. the short name you used when defining the template)