APPS.JE_NO_GEI_SREPORT_V 會計科目餘額表

CREATE OR REPLACE FORCE VIEW APPS.JE_NO_GEI_SREPORT_V
(
   AUTHORITY_TYPE,
   PERIOD,
   ACTUAL_FLAG,
   ACCOUNT_NUMBER,
   BALANCE,
   TEMPLATE_ID,
   PERIOD_NUM,
   PERIOD_YEAR
)
AS
   SELECT gcc.segment4     authority_type,
          gbs.period_name  period,
          gbs.actual_flag  actual_flag,
          gcc.segment2     account_number,
          (gbs.period_net_dr - gbs.period_net_cr) balance,
          gbs.template_id  template_id,
          gbs.period_num   period_num,
          gbs.period_year  period_year
     FROM gl_code_combinations gcc,
          gl_balances gbs,
          gl_sets_of_books gso
    WHERE     gbs.code_combination_id = gcc.code_combination_id
          AND gbs.ledger_id           = gso.set_of_books_id
          AND gso.currency_code       = gbs.currency_code;
----簡直就是亂寫----gl_balances 是主題
gl_code_combinations 是抓出 segment4 AS authority_type
gl_sets_of_books     是限制
gl_balances.ledger_id    =gl_sets_of_books.set_of_books_id
gl_balances.currency_code=gl_sets_of_books.currency_code





 

建立 WIP_OPERATIONS_V 重構連結方式

建立 WIP_OPERATIONS_V 重構連結方式

           FROM WIP_OPERATIONS          WO
     INNER JOIN BOM_DEPARTMENTS         BD  ON WO.DEPARTMENT_ID         = BD.DEPARTMENT_ID
LEFT OUTER JOIN BOM_STANDARD_OPERATIONS BSO ON WO.STANDARD_OPERATION_ID = BSO.STANDARD_OPERATION_ID  
                                           AND BSO.LINE_ID IS NULL 
                                           AND NVL (BSO.OPERATION_TYPE, 1) = 1
LEFT OUTER JOIN MFG_LOOKUPS             LU1 ON WO.SHUTDOWN_TYPE            = LU1.LOOKUP_CODE 
                                           AND 'BOM_EAM_SHUTDOWN_TYPE'     = LU1.LOOKUP_TYPE
LEFT OUTER JOIN PER_ALL_PEOPLE_F        PAP ON WO.EMPLOYEE_ID              = PAP.PERSON_ID

以下寫法跟胡說八道幾乎相同
還是Oracle 原廠的瘋子寫的方式
原廠就是自大與偷懶...
不好意思說你智商低...

FROM BOM_DEPARTMENTS         BD,
            BOM_STANDARD_OPERATIONS BSO,
            WIP_OPERATIONS          WO,
            MFG_LOOKUPS             LU1,
            PER_ALL_PEOPLE_F        PAP
      WHERE     BD.DEPARTMENT_ID = WO.DEPARTMENT_ID
            AND BSO.STANDARD_OPERATION_ID(+) = WO.STANDARD_OPERATION_ID
            AND NVL (BSO.OPERATION_TYPE, 1) = 1
            AND BSO.LINE_ID IS NULL
            AND LU1.LOOKUP_TYPE(+) = 'BOM_EAM_SHUTDOWN_TYPE'
            AND LU1.LOOKUP_CODE(+) = WO.SHUTDOWN_TYPE
            AND WO.EMPLOYEE_ID = PAP.PERSON_ID(+)
  
CEATE OR REPLACE FORCE VIEW APPS.WIP_OPERATIONS_V
(  ROW_ID,
   WIP_ENTITY_ID,
   OPERATION_SEQ_NUM,
   ORGANIZATION_ID,
   REPETITIVE_SCHEDULE_ID,
   LAST_UPDATE_DATE,
   LAST_UPDATED_BY,
   CREATION_DATE,
   CREATED_BY,
   LAST_UPDATE_LOGIN,
   REQUEST_ID,
   PROGRAM_APPLICATION_ID,
   PROGRAM_ID,
   PROGRAM_UPDATE_DATE,
   OPERATION_SEQUENCE_ID,
   STANDARD_OPERATION_ID,
   OPERATION_CODE,
   DEPARTMENT_ID,
   DEPARTMENT_CODE,
   LOCATION_ID,
   DESCRIPTION,
   SCHEDULED_QUANTITY,
   QUANTITY_IN_QUEUE,
   QUANTITY_RUNNING,
   QUANTITY_WAITING_TO_MOVE,
   QUANTITY_REJECTED,
   QUANTITY_SCRAPPED,
   QUANTITY_COMPLETED,
   FIRST_UNIT_START_DATE,
   FIRST_UNIT_COMPLETION_DATE,
   LAST_UNIT_START_DATE,
   LAST_UNIT_COMPLETION_DATE,
   PREVIOUS_OPERATION_SEQ_NUM,
   NEXT_OPERATION_SEQ_NUM,
   COUNT_POINT_TYPE,
   COUNT_POINT_FLAG,
   AUTOCHARGE_FLAG,
   BACKFLUSH_FLAG,
   MINIMUM_TRANSFER_QUANTITY,
   DATE_LAST_MOVED,
   ATTRIBUTE_CATEGORY,
   ATTRIBUTE1,
   ATTRIBUTE2,
   ATTRIBUTE3,
   ATTRIBUTE4,
   ATTRIBUTE5,
   ATTRIBUTE6,
   ATTRIBUTE7,
   ATTRIBUTE8,
   ATTRIBUTE9,
   ATTRIBUTE10,
   ATTRIBUTE11,
   ATTRIBUTE12,
   ATTRIBUTE13,
   ATTRIBUTE14,
   ATTRIBUTE15,
   OPERATION_YIELD,
   CUMULATIVE_SCRAP_QUANTITY,
   OPERATION_YIELD_ENABLED,
   OPERATION_COMPLETED,
   SHUTDOWN_TYPE,
   SHUTDOWN_TYPE_DISP,
   X_POS,
   Y_POS,
   LONG_DESCRIPTION,
   DISABLE_DATE,
   RECOMMENDED,
   PROGRESS_PERCENTAGE,
   WSM_BONUS_QUANTITY,
   ACTUAL_START_DATE,
   ACTUAL_COMPLETION_DATE,
   EMPLOYEE_ID,
   EMPLOYEE_NAME,
   LOWEST_ACCEPTABLE_YIELD,
   CHECK_SKILL
)
AS
     SELECT WO.ROWID ROW_ID,
            WO.WIP_ENTITY_ID,
            WO.OPERATION_SEQ_NUM,
            WO.ORGANIZATION_ID,
            WO.REPETITIVE_SCHEDULE_ID,
            WO.LAST_UPDATE_DATE,
            WO.LAST_UPDATED_BY,
            WO.CREATION_DATE,
            WO.CREATED_BY,
            WO.LAST_UPDATE_LOGIN,
            WO.REQUEST_ID,
            WO.PROGRAM_APPLICATION_ID,
            WO.PROGRAM_ID,
            WO.PROGRAM_UPDATE_DATE,
            WO.OPERATION_SEQUENCE_ID,
            WO.STANDARD_OPERATION_ID,
            BSO.OPERATION_CODE,
            WO.DEPARTMENT_ID,
            BD.DEPARTMENT_CODE,
            BD.LOCATION_ID,
            WO.DESCRIPTION,
            WO.SCHEDULED_QUANTITY,
            DECODE (WO.QUANTITY_IN_QUEUE, 0, NULL, WO.QUANTITY_IN_QUEUE),
            DECODE (WO.QUANTITY_RUNNING, 0, NULL, WO.QUANTITY_RUNNING),
            DECODE (WO.QUANTITY_WAITING_TO_MOVE,
                    0, NULL,
                    WO.QUANTITY_WAITING_TO_MOVE),
            DECODE (WO.QUANTITY_REJECTED, 0, NULL, WO.QUANTITY_REJECTED),
            DECODE (WO.QUANTITY_SCRAPPED, 0, NULL, WO.QUANTITY_SCRAPPED),
            DECODE (WO.QUANTITY_COMPLETED, 0, NULL, WO.QUANTITY_COMPLETED),
            WO.FIRST_UNIT_START_DATE,
            WO.FIRST_UNIT_COMPLETION_DATE,
            WO.LAST_UNIT_START_DATE,
            WO.LAST_UNIT_COMPLETION_DATE,
            WO.PREVIOUS_OPERATION_SEQ_NUM,
            WO.NEXT_OPERATION_SEQ_NUM,
            WO.COUNT_POINT_TYPE,
            DECODE (WO.COUNT_POINT_TYPE, 1, 1, 2) "COUNT_POINT_FLAG",
            DECODE (WO.COUNT_POINT_TYPE, 3, 2, 1) "AUTOCHARGE_FLAG",
            WO.BACKFLUSH_FLAG,
            WO.MINIMUM_TRANSFER_QUANTITY,
            WO.DATE_LAST_MOVED,
            WO.ATTRIBUTE_CATEGORY,
            WO.ATTRIBUTE1,
            WO.ATTRIBUTE2,
            WO.ATTRIBUTE3,
            WO.ATTRIBUTE4,
            WO.ATTRIBUTE5,
            WO.ATTRIBUTE6,
            WO.ATTRIBUTE7,
            WO.ATTRIBUTE8,
            WO.ATTRIBUTE9,
            WO.ATTRIBUTE10,
            WO.ATTRIBUTE11,
            WO.ATTRIBUTE12,
            WO.ATTRIBUTE13,
            WO.ATTRIBUTE14,
            WO.ATTRIBUTE15,
            WO.OPERATION_YIELD,
            WO.CUMULATIVE_SCRAP_QUANTITY,
            WO.OPERATION_YIELD_ENABLED,
            NVL (WO.OPERATION_COMPLETED, 'N'),
            WO.SHUTDOWN_TYPE,
            LU1.MEANING,
            WO.X_POS,
            WO.Y_POS,
            WO.LONG_DESCRIPTION,
            WO.DISABLE_DATE,
            WO.RECOMMENDED,
            WO.PROGRESS_PERCENTAGE,
            WO.WSM_BONUS_QUANTITY,
            WO.ACTUAL_START_DATE,
            WO.ACTUAL_COMPLETION_DATE,
            WO.EMPLOYEE_ID,
            PAP.FULL_NAME,
            WO.LOWEST_ACCEPTABLE_YIELD,
            NVL (wo.CHECK_SKILL, 2) CHECK_SKILL
      
           FROM WIP_OPERATIONS          WO
     INNER JOIN BOM_DEPARTMENTS         BD  ON WO.DEPARTMENT_ID        = BD.DEPARTMENT_ID
LEFT OUTER JOIN BOM_STANDARD_OPERATIONS BSO ON WO.STANDARD_OPERATION_ID= BSO.STANDARD_OPERATION_ID  AND  BSO.LINE_ID IS NULL AND NVL (BSO.OPERATION_TYPE, 1) = 1
LEFT OUTER JOIN MFG_LOOKUPS             LU1 ON WO.SHUTDOWN_TYPE        = LU1.LOOKUP_CODE  AND 'BOM_EAM_SHUTDOWN_TYPE'= LU1.LOOKUP_TYPE
LEFT OUTER JOIN PER_ALL_PEOPLE_F        PAP ON WO.EMPLOYEE_ID          = PAP.PERSON_ID
     
      WHERE     BD.DEPARTMENT_ID = WO.DEPARTMENT_ID
            AND BSO.STANDARD_OPERATION_ID(+) = WO.STANDARD_OPERATION_ID
            AND NVL (BSO.OPERATION_TYPE, 1) = 1
            AND BSO.LINE_ID IS NULL
            AND LU1.LOOKUP_TYPE(+) = 'BOM_EAM_SHUTDOWN_TYPE'
            AND LU1.LOOKUP_CODE(+) = WO.SHUTDOWN_TYPE
            AND WO.EMPLOYEE_ID = PAP.PERSON_ID(+)
   ORDER BY WO.OPERATION_SEQ_NUM;

ORACLE EBS CATEGORY 的資料表與主鍵 CATEGORY _ID

OWNER	TABLE_NAME	COLUMN_NAME		DATA_TYPE	DATA_LENGTH
AK	AK_CATEGORY_USAGES	CATEGORY_ID	NUMBER	22
APPS	AK_CATEGORY_USAGES_V	CATEGORY_ID	NUMBER	22
ASL	ASL_CATEGORY_SUMMARY_INFO	CATEGORY_ID	NUMBER	22
ASL	ASL_CATEGORY_SUMMARY_INFO	CATEGORY_SET_ID	NUMBER	22
ASL	ASL_INV_CATEGORY_ACC	CATEGORY_ID	NUMBER	22
ASL	ASL_INV_CATEGORY_ACC	CATEGORY_SET_ID	NUMBER	22
APPS	AS_INTEREST_CATEGORY_SETS	CATEGORY_SET_ID	NUMBER	22
OSM	AS_INTEREST_CATEGORY_SETS_ALL	CATEGORY_SET_ID	NUMBER	22
APPS	AS_INTEREST_CATEGORY_SETS_V	CATEGORY_SET_ID	NUMBER	22
BOM	BOM_ITEM_ATTACH_CATEGORY_ASSOC	ATTACH_CATEGORY_ID	NUMBER	22
APPS	CLN_INV_CATEGORY_V	CATEGORY_ID	NUMBER	22
APPS	CLN_ITEMMST_ITEMCATEGORY_V	CATEGORY_ID	NUMBER	22
APPS	CLN_ITEMMST_ITEMCATEGORY_V	CATEGORY_SET_ID	NUMBER	22
APPS	CLN_PROCAT_ITEMCATEGORY_V	CATEGORY_ID	NUMBER	22
APPS	CSC_PROF_CATEGORY_LOOKUPS_V	GROUP_CATEGORY_ID	NUMBER	22
APPS	CST_XLA_INV_CATEGORY_REF_V	CATEGORY_ID	NUMBER	22
APPS	CST_XLA_INV_CATEGORY_REF_V	CATEGORY_ITEM_ID	NUMBER	22
APPS	CST_XLA_INV_CATEGORY_REF_V	CATEGORY_ORGANIZATION_ID	NUMBER	22
APPS	CST_XLA_PLA_CATEGORY_REF_V	PLA_CATEGORY_ID	NUMBER	22
CS	CS_KB_CATEGORY_GROUPS_B	CATEGORY_GROUP_ID	NUMBER	22
CS	CS_KB_CATEGORY_GROUPS_TL	CATEGORY_GROUP_ID	NUMBER	22
APPS	CS_KB_CATEGORY_GROUPS_VL	CATEGORY_GROUP_ID	NUMBER	22
APPS	CUS_ITEM_CATEGORY	CATEGORY_ID	NUMBER	22
APPS	CUS_ITEM_CATEGORY_UPD3	CATEGORY_ID	NUMBER	22
APPS	CUS_MTL_CATEGORY_SETS_150604	CATEGORY_SET_ID	NUMBER	22
APPS	CUS_MTL_CATEGORY_SETS_150604	DEFAULT_CATEGORY_ID	NUMBER	22
APPS	CUS_SALE_CATEGORY_UPD1	CATEGORY_ID	NUMBER	22
DOM	DOM_CATEGORY_LIFECYCLES	CATEGORY_ID	NUMBER	22
DOM	DOM_CATEGORY_PUB_TEMPL	CATEGORY_ID	NUMBER	22
APPS	EDW_ITEMS_CATEGORY_FKV	CATEGORY_ID	NUMBER	22
APPS	ENI_ITEM_CATEGORY_V	PRODUCT_CATEGORY_ID	VARCHAR2	40
FA	FA_CATEGORY_BOOKS	CATEGORY_ID	NUMBER	22
FA	FA_CATEGORY_BOOK_DEFAULTS	CATEGORY_ID	NUMBER	22
APPLSYS	FND_DOC_CATEGORY_USAGES	CATEGORY_ID	NUMBER	22
APPLSYS	FND_DOC_CATEGORY_USAGES	DOC_CATEGORY_USAGE_ID	NUMBER	22
APPS	FND_DOC_CATEGORY_USAGES_VL	CATEGORY_ID	NUMBER	22
APPS	FND_DOC_CATEGORY_USAGES_VL	DOC_CATEGORY_USAGE_ID	NUMBER	22
APPLSYS	FND_SOA_LOG_CATEGORY	CATEGORY_ID	NUMBER	22
GMD	GMD_LCF_CATEGORY_DTL_GTMP	CATEGORY_ID	NUMBER	22
GMD	GMD_LCF_CATEGORY_HDR_GTMP	CATEGORY_ID	NUMBER	22
GMD	GMD_LCF_CATEGORY_HDR_GTMP	CATEGORY_SET_ID	NUMBER	22
GMI	GMI_CATEGORY_SETS	CATEGORY_SET_ID	NUMBER	22
APPS	GMP_PDR_CATEGORY_V	CATEGORY_SET_ID	NUMBER	22
APPS	HRBV_PROPOSAL_CATEGORY_MEMBE_V	PARENT_CATEGORY_TYPE_ID	NUMBER	22
APPS	HRBV_PROPOSAL_CATEGORY_MEMBE_V	PROPOSAL_CATEGORY_MEMBER_ID	NUMBER	22
APPS	HRBV_PROPOSAL_CATEGORY_MEMBE_V	PROPOSAL_CATEGORY_TYPE_ID	NUMBER	22
APPS	HRBV_PROPOSAL_CATEGORY_TYPES_V	PROPOSAL_CATEGORY_TYPE_ID	NUMBER	22
HXC	HXC_TIME_CATEGORY_COMPS	REF_TIME_CATEGORY_ID	NUMBER	22
HXC	HXC_TIME_CATEGORY_COMPS	TIME_CATEGORY_COMP_ID	NUMBER	22
HXC	HXC_TIME_CATEGORY_COMPS	TIME_CATEGORY_ID	NUMBER	22
APPS	HXC_TIME_CATEGORY_COMPS_V	REF_TIME_CATEGORY_ID	NUMBER	22
APPS	HXC_TIME_CATEGORY_COMPS_V	TIME_CATEGORY_COMP_ID	NUMBER	22
APPS	HXC_TIME_CATEGORY_COMPS_V	TIME_CATEGORY_ID	NUMBER	22
HXC	HXC_TIME_CATEGORY_COMP_SQL	TIME_CATEGORY_COMP_ID	NUMBER	22
HXC	HXC_TIME_CATEGORY_COMP_SQL	TIME_CATEGORY_COMP_SQL_ID	NUMBER	22
APPS	ICX_CATEGORY_LOV	CATEGORY_ID	NUMBER	22
APPS	ICX_CATEGORY_LOV	CATEGORY_SET_ID	NUMBER	22
APPS	ICX_CATEGORY_SET_LOV	CATEGORY_SET_ID	NUMBER	22
ICX	ICX_CAT_CATEGORY_ITEMS	RT_CATEGORY_ID	NUMBER	22
ICX	ICX_POR_CATEGORY_DATA_SOURCES	RT_CATEGORY_ID	NUMBER	22
ICX	ICX_POR_CATEGORY_DEFAULTS	RT_CATEGORY_ID	NUMBER	22
ICX	ICX_POR_CATEGORY_ITEMS	RT_CATEGORY_ID	NUMBER	22
ICX	ICX_POR_CATEGORY_ORDER_MAP	RT_CATEGORY_ID	NUMBER	22
IEM	IEM_EMAIL_CATEGORY_MAPS	KB_CATEGORY_ID	NUMBER	22
IGI	IGI_IAC_CATEGORY_BOOKS	CATEGORY_ID	NUMBER	22
IGI	IGI_MHC_CATEGORY_BOOKS	CATEGORY_ID	NUMBER	22
IGI	IGI_MHC_CATEGORY_BOOK_DEFAULTS	CATEGORY_ID	NUMBER	22
IGS	IGR_EPU_CATEGORY_UPG	PRODUCT_CATEGORY_ID	NUMBER	22
IGS	IGR_EPU_CATEGORY_UPG	PRODUCT_CATEGORY_SET_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_ASGNS	CATEGORY_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_ASGNS	CATEGORY_SET_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_TYPES	CATEGORY_SET_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_TYPES	DEFAULT_CATEGORY_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_TYPE_ASGNS	CATEGORY_ID	NUMBER	22
APPS	INVBV_ITEM_CATEGORY_TYPE_ASGNS	CATEGORY_SET_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_ASGNS	CATEGORY_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_ASGNS	CATEGORY_SET_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_TYPES	CATEGORY_SET_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_TYPES	DEFAULT_CATEGORY_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_TYPE_ASGNS	CATEGORY_ID	NUMBER	22
APPS	INVFV_ITEM_CATEGORY_TYPE_ASGNS	CATEGORY_SET_ID	NUMBER	22
APPS	LOS_API_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_API_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_ARR_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_ARR_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_ART_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_ART_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
XTR	LOS_CATEGORY_LINES	CATEGORY_ID	NUMBER	22
XTR	LOS_CATEGORY_LINES	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_GL_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_GL_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_NMB_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_NMB_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_NMN_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_NMN_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
APPS	LOS_XTR_CATEGORY_LINES_V	CATEGORY_ID	NUMBER	22
APPS	LOS_XTR_CATEGORY_LINES_V	CATEGORY_LINE_ID	NUMBER	22
MGDSYS	MGD_IDENCODING_CATEGORY	CATEGORY_ID	NUMBER	22
MGDSYS	MGD_IDENCODING_CATEGORY_TAB	CATEGORY_ID	NUMBER	22
MGDSYS	MGD_USR_IDENCODING_CATEGORY	CATEGORY_ID	NUMBER	22
INV	MLOG$_MTL_DEFAULT_CATEGORY	CATEGORY_SET_ID	NUMBER	22
APPS	MRP_AP_CATEGORY_SETS_V	CATEGORY_SET_ID	NUMBER	22
APPS	MRP_AP_DEFAULT_ITEM_CATEGORY_V	CATEGORY_ID	NUMBER	22
MSC	MSC_CATEGORY_SETS	CATEGORY_SET_ID	NUMBER	22
MSC	MSC_CATEGORY_SETS	SR_CATEGORY_SET_ID	NUMBER	22
MSC	MSC_CATEGORY_SET_ID_LID	CATEGORY_SET_ID	NUMBER	22
MSC	MSC_CATEGORY_SET_ID_LID	SR_CATEGORY_SET_ID	NUMBER	22
APPS	MSC_PUSH_CATEGORY_V	SR_CATEGORY_ID	NUMBER	22
MSC	MSC_RP_CATEGORY_MV	CATEGORY_SET_ID	NUMBER	22
MSC	MSC_RP_CATEGORY_MV	SR_CATEGORY_ID	NUMBER	22
MSC	MSC_ST_CATEGORY_SETS	CATEGORY_SET_ID	NUMBER	22
MSC	MSC_ST_CATEGORY_SETS	SOURCE_SR_CATEGORY_SET_ID	NUMBER	22
MSC	MSC_ST_CATEGORY_SETS	SR_CATEGORY_SET_ID	NUMBER	22
APPS	MSD_CATEGORY_SETS_V	CATEGORY_SET_ID	NUMBER	22
APPS	MSD_DEM_SR_CATEGORY_SETS_V	CATEGORY_SET_ID	NUMBER	22
INV	MTL_CATEGORY_ACCOUNTS	CATEGORY_ID	NUMBER	22
INV	MTL_CATEGORY_ACCOUNTS	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_ACCOUNTS_V	CATEGORY_ID	NUMBER	22
APPS	MTL_CATEGORY_ACCOUNTS_V	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_GRANTS_V	CATEGORY_ID	VARCHAR2	256
APPS	MTL_CATEGORY_GRANTS_V	CATEGORY_SET_ID	VARCHAR2	256
APPS	MTL_CATEGORY_SETS_ALL_V	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_SETS_ALL_V	DEFAULT_CATEGORY_ID	NUMBER	22
INV	MTL_CATEGORY_SETS_B	CATEGORY_SET_ID	NUMBER	22
INV	MTL_CATEGORY_SETS_B	DEFAULT_CATEGORY_ID	NUMBER	22
INV	MTL_CATEGORY_SETS_TL	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_SETS_V	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_SETS_V	DEFAULT_CATEGORY_ID	NUMBER	22
APPS	MTL_CATEGORY_SETS_VL	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_CATEGORY_SETS_VL	DEFAULT_CATEGORY_ID	NUMBER	22
INV	MTL_CATEGORY_SET_VALID_CATS	CATEGORY_ID	NUMBER	22
INV	MTL_CATEGORY_SET_VALID_CATS	CATEGORY_SET_ID	NUMBER	22
INV	MTL_CATEGORY_SET_VALID_CATS	PARENT_CATEGORY_ID	NUMBER	22
APPS	MTL_CATEGORY_SET_VALID_CATS_V	CATEGORY_ID	NUMBER	22
APPS	MTL_CATEGORY_SET_VALID_CATS_V	CATEGORY_SET_ID	NUMBER	22
INV	MTL_DEFAULT_CATEGORY_SETS	CATEGORY_SET_ID	NUMBER	22
APPS	MTL_DEFAULT_CATEGORY_SETS_FK_V	CATEGORY_SET_ID	NUMBER	22
MDSYS	OLS_DIR_CATEGORY_TYPES	CATEGORY_TYPE_ID	NUMBER	22
OTA	OTA_CATEGORY_USAGES	CATEGORY_USAGE_ID	NUMBER	22
OTA	OTA_CATEGORY_USAGES_TL	CATEGORY_USAGE_ID	NUMBER	22
APPS	OTA_CATEGORY_USAGES_V1	CATEGORY_USAGE_ID	NUMBER	22
APPS	OTA_CATEGORY_USAGES_VL	CATEGORY_USAGE_ID	NUMBER	22
HR	PAY_REPORT_CATEGORY_COMPONENTS	REPORT_CATEGORY_COMP_ID	NUMBER	22
HR	PAY_REPORT_CATEGORY_COMPONENTS	REPORT_CATEGORY_ID	NUMBER	22
APPS	PA_ITEM_CATEGORY_RES_V	ITEM_CATEGORY_ID	NUMBER	22
APPS	PA_REP_UTIL_CATEGORY_V	UTIL_CATEGORY_ID	NUMBER	22
HR	PER_PROPOSAL_CATEGORY_MEMBERS	PARENT_CATEGORY_TYPE_ID	NUMBER	22
HR	PER_PROPOSAL_CATEGORY_MEMBERS	PROPOSAL_CATEGORY_MEMBER_ID	NUMBER	22
HR	PER_PROPOSAL_CATEGORY_MEMBERS	PROPOSAL_CATEGORY_TYPE_ID	NUMBER	22
HR	PER_PROPOSAL_CATEGORY_TYPES	PROPOSAL_CATEGORY_TYPE_ID	NUMBER	22
APPS	PER_PROPOSAL_CATEGORY_TYPES_V	PROPOSAL_CATEGORY_TYPE_ID	NUMBER	22
APPS	POR_CATEGORY_LOV_V	CATEGORY_ID	NUMBER	22
APPS	POR_CATEGORY_LOV_V	CATEGORY_SET_ID	NUMBER	22
HR	PQH_TXN_CATEGORY_ATTRIBUTES	TRANSACTION_CATEGORY_ID	NUMBER	22
HR	PQH_TXN_CATEGORY_ATTRIBUTES	TXN_CATEGORY_ATTRIBUTE_ID	NUMBER	22
APPS	PQH_TXN_CATEGORY_ATTRIBUTES_V	TRANSACTION_CATEGORY_ID	NUMBER	22
APPS	PQH_TXN_CATEGORY_ATTRIBUTES_V	TXN_CATEGORY_ATTRIBUTE_ID	NUMBER	22
HR	PQH_TXN_CATEGORY_DOCUMENTS	TRANSACTION_CATEGORY_ID	NUMBER	22
RLM	RLM_MESSAGE_CATEGORY	MESSAGE_CATEGORY_ID	NUMBER	22
APPS	RLM_MESSAGE_CATEGORY_V	MESSAGE_CATEGORY_ID	NUMBER	22

ORACLE R12 客製化相關資料資料表串接欄位

參照來源
http://allfaqsforall.blogspot.tw/
但是一些沒驗證通過的已經依據 R12 驗證通過

GL AND AP
=========
GL_CODE_COMBINATIONS  AP_INVOICES_ALL
code_combination_id = acct_pay_code_combination_id

GL_CODE_COMBINATIONS  AP_INVOICES_DISTRIBUTIONS_ALL
code_combination_id = dist_code_combination_id

GL_SETS_OF_BOOKS  AP_INVOICES_ALL
set_of_books_id = set_of_books_id

SELECT COUNT(*) --4919133
      FROM AP_INVOICE_DISTRIBUTIONS_ALL  a
INNER JOIN GL_CODE_COMBINATIONS          b ON a.dist_code_combination_id=b.code_combination_id

SELECT COUNT(*) --874612
      FROM AP_INVOICES_ALL  a
INNER JOIN GL_SETS_OF_BOOKS b ON a.set_of_books_id=b.set_of_books_id

SELECT COUNT(*) --4323869
      FROM RA_CUST_TRX_LINE_GL_DIST_ALL  a
INNER JOIN GL_CODE_COMBINATIONS          b ON a.code_combination_id=b.code_combination_id

SELECT COUNT(*) --340594
      FROM MTL_SYSTEM_ITEMS_B   a
INNER JOIN GL_CODE_COMBINATIONS b ON a.cost_of_sales_account=b.code_combination_id

SELECT COUNT(*) --1755370
      FROM PO_DISTRIBUTIONS_ALL   a
INNER JOIN GL_CODE_COMBINATIONS   b ON a.code_combination_id=b.code_combination_id

GL AND AR
=========
GL_CODE_COMBINATIONS RA_CUST_TRX_LINE__GL_DIST_ALL
code_combination_id = code_combination_id

GL AND INV
==========
GL_CODE_COMBINATIONS MTL_SYSTEM_ITEMS_B
code_combination_id = cost_of_sales_account

GL AND PO
=========
GL_CODE_COMBINATIONS PO_DISTRIBUTIONS_ALL
code_combination_id = code_combination_id

PO AND AP
==========
PO_DISTRIBUTIONS_ALL AP_INVOICE_DISTRIBUTIONS_ALL
po_distribution_id = po_distribution_id

PO_VENDORS AP_INVOICES_ALL
vendor_id = vendor_id

PO AND SHIPMENTS
=================
PO_HEADERS_ALL RCV_TRANSACTIONS
po_header_id = po_header_id

PO_DISTRIBUTIONS_ALL RCV_TRANSACTIONS
po_distribution_id = po_distribution_id

SHIPMENTS AND INVOICE
=====================
RCV_TRANSACTIONS AP_INVOICE_DISTRIBUTIONS_ALL
RCV_TRANSACTION_ID = RCV_TRANSACTION_ID


PO AND INV
==========
PO_REQUISITION_LINES_ALL MTL_SYSTEM_ITEMS_B
item_id = inventory_item_id
org_id = organization_id

PO AND HRMS
============
PO_HEADERS_ALL HR_EMPLOYEES
Agent_id = employee_id

PO AND REQUISITION
==================
PO_DISTRIBUTIONS_ALL PO_REQ_DISTRIBUTIONS_ALL
req_distribution_id = distribution_id


SHIPMENTS AND INV
=================
RCV_TRANSACTIONS MTL_SYSTEM_ITEMS_B
Organization_id = organization_id

INV AND HRMS
============
MTL_SYSTEM_ITEMS_B HR_EMPLOYEES
buyer_id = employee_id

OM AND AR
==========
OE_ORDER_HEADERS_ALL RA_CUSTOMER_TRX_LINES_ALL
TO_CHAR( Order_number) = interface_line_attribute1
OE_ORDER_LINES_ALL RA_CUSTOMER_TRX_LINES_ALL
TO_CHAR(Line_id) = interface_line_attribute6

OE_ORDER_LINES_ALL RA_CUSTOMER_TRX_LINES_ALL
reference_customer_trx_line_id = customer_trx_line_id

OM AND SHIPPING
===============
OE_ORDER_HEADERS_ALL WSH_DELIVARY_DETAILS

HEADER_ID = SOURCE_HEADER_ID

OE_ORDER_HEADERS_ALL WSH_DELIVARY_DETAILS
LINE_ID = SOURCE_LINE_ID

AP AND AR (BANKS)
=================
AR_CASH_RECEIPTS_ALL AP_BANK_ACCOUNTS
REMITTANCE_BANK_ACCOUNT_ID = ABA.BANK_ACCOUNT_ID

AP AND AR
=========
HZ_PARTIES AP_INVOICES_ALL
PARTY_ID = PARTY_ID

OM AND CRM
===========
OE_ORDER_LINES_ALL CSI_ITEM_INSTANCES(Install Base)
LINE_ID = LAST_OE_ORDER_LINE_ID



Table Name: Po_Requisition_Headers_All A
Column Names Table Name Column Name
A. REQUISITION_HEADER_ID PO_REQUISITION_LINES_ALL REQUISITION_HEADER_ID
A. TYPE_LOOKUP_CODE=PO_DOCUMENT_TYPES DOCUMENT_SUBTYPE
A. PREPARER_ID=PER_PEOPLE_F PERSON_ID
A. ORG_ID=MTL_SYSTEM_ITEMS ORGANIZATION_ID
A. ORG_ID=MTL_ORGANIZATIONS ORGANIZATION_ID

Table Name: Po_Requisition_Lines_All B
Column Names Table Name Column Name
B .REQUISITION_HEADER_ID PO_REQUISITION_HEADERS_ALL REQUISITION_HEADER_ID
B .REQUISITION_LINE_ID PO_REQ_DISTRIBUTIONS_ALL REQUISITION_LINE_ID
B .LINE_TYPE_ID PO_LINE_TYPES LINE_TYPE_ID
B .ITEM_ID MTL_SYSTEM_ITEMS INVENTORY_ITEM_ID
B .ORG_ID MTL_SYSTEM_ITEMS ORGANIZATION_ID

Table Name: Po_Requisition_Distributions_All C .
Column Names Table Name Column Name
C .REQUISITION_LINE_ID PO_REQUISITION_LINES_ALL REQUISITION_LINE_ID
C .DISTRIBUTION_ID PO_DISTRIBUTIONS_ALL REQ_DISTRIBUTION_ID
C .SET_OF_BOOKS_ID GL_SETS_OF_BOOKS SET_OF_BOOKS_ID
C .CODE_COMBINATION_ID GL_CODE-COMBINATIONS CODE_COMBINATION_ID

Table Name: Po_Distributions_All D .
Column Names Table Name Column Name
D .PO_LINE_ID PO_LINES PO_LINE_ID
D .REQ_DISTRIBUTION_ID PO_REQ_DISTRIBUTIONS_ALL DISTRIBUTION_ID
D .PO_DISTRIBUTION_ID AP_INVOICE_DISTRIBUTIONS_ALL PO_DISTRIBUTION_ID

Table Name: Po_Headers_All E .
Column Names Table Name Column Name
E .PO_HEADER_ID=>PO_LINES PO_HEADER_ID
E .PO_HEADER_ID=>RCV_SHIPMENT_LINES PO_HEADER_ID
E .VENDOR_ID PO_VENDORS VENDOR_ID
E .AGENT_ID PER_PEOPLE PERSON_ID
E .TYPE_LOOK_UP_CODE PO_DOCUMENT_TYPES DOCUMENT_SUBTYPE

Table Name: Po_Lines_All F.
Column Names Table Name Column Name
F.PO_HEADER_ID PO_HEADERS PO_HEADER_ID
F.PO_LINE_ID PO_DISTRIBUTIONS_ALL PO_LINE_ID
F.ITEM_ID MTL_SYSTEM_ITEMS ITEM_ID

Table Name: Rcv_Shipment_Lines G.
Column Names Table Name Column Name
G.PO_HEADER_ID PO_HEADERS PO_HEADER_ID
G.SHIPMENT_HEADER_ID RCV_SHIPMENT_HEADERS SHIPMENT_HEADER_ID

Table Name: Ap_Invoices_All H.
Column Names Table Name Column Name
H. INVOICE_ID => AP_INVOICE_DISTRIBUTIONS_ALL.INVOICE_ID

Table Name: Oe_Order_Headers_All I.
Column Names Table Name Column Name
I.HEADER_ID                => OE_ORDER_LINES HEADER_ID
I.SOURCE_HEADER_ID=> WISH_DELIVERY_DETAILS.SOURCE_HEADER_ID
I.PRICE_LIST_ID           => QP_LIST_HEADERS_TL.LIST_HEADER_ID
I.ORG_ID                      => MTL_ORGANIZATIONS.ORGANIZATION_ID
I.SALESREP_ID            => JTF_RS_SALESREPS.SALESREP_ID
I.ORDER_TYPE_ID       => OE_TRANSACTION_TYPES TRANSACTION_TYPE_ID
I.ORDER_SOURCE_ID => OE_ORDER_SOURCES ORDER_SOURCE_ID
I.ACCOUNTING_RULE_ID=> RA_RULES RULE_ID
I.PAYMENT_TERM_ID      => RA_TERMS TERM_ID
I.SOLD_TO_ORG_ID       => HZ_CUST_ACCOUNTS CUST_ACCOUNT_ID
I.SHIP_FROM_ORG_ID   => MTL_PARAMETERS ORGANIZATION_ID
I.SHIP_TO_ORG_ID        => HZ_CUST_SITE_USES_ALL SITE_USE_ID

Table Name: Oe_Order_Lines_All J.
Column Names Table Name Column Name
J.LINE_TYPE_ID OE_TRANSACTION_TYPES_TL TRANSACTION_TYPE_ID
J.INVOICING_RULE_ID RA_RULES RULE_ID

Table Name: Hz_Parties K.
Column Names Table Name Column Name
K.PATY_ID                   =>HZ_CUST_ACCOUNTS PATY_ID
K.CUST_ACCOUNT_ID=>OE_ORDER_LINES SOLD_TO_ORG_ID

Table Name: Hz_Party_Sites_All L.
Column Names Table Name Column Name
L.PATY_ID          =>HZ_PARTIES PATY_ID
L. LOCATION_ID=>HZ_LOCATIONS LOCATION_ID

Table Name: Wsh_delivery_details M.
Column Names Table Name Column Name
M.SOURCE_HEADER_ID=>OE_ORDER_HEADERS.SOURCE_HEADER_ID
M.DELIVERY_DETAIL_ID=>WSH_DELIVERY_ASSIGNMENTS.DELIVERY_DETAIL_ID
M.DELIVERY_ID             =>WSH_NEW_DELIVERIES DELIVERY_ID
M.INVENTORY_ITEM_ID=>MTL_SYSTEM_ITEMS.INVENTORY_ITEM_ID


Table Name: RA_CUSTOMER_TRX_ALL N.
Column Names Table Name Column Name
N.CUSTOMER_TRX_ID AR_RECEIVABLE_APPLICATIONS_ALL APPLIED_CUSTOMER_TRX_ID
N.TERM_ID RA_TERMS TERM_ID
N.CUSTOMER_TRX_ID RA_CUST_TRX_LINE_GL_DIST CUSTOMER_TRX_ID
Table Name: AR_CASH_REC EIPTS_ALL O.
Column Names Table Name Column Name
O.CASH_RECEIPT_ID AR_RECEIVABLE_APPLICATIONS_ALL CASH_RECEIPT_ID
O.SET_OF_BOOKS_ID GL_SETS_OF_BOOKS SET_OF_BOOKS_ID

MTL_PARAMETERS	It maintains a set of default options like general ledger accounts; locator, lot, and serial controls, inter-organization options, costing method, etc. for each organization defined in Oracle Inventory. Each organization’s item master organization (MASTER_ORGANIZATION_ID) and costing organization (COST_ORGANIZATION_ID) are maintained here.
MTL_SYSTEM_ITEMS_B	This is the definition table for items. This table holds the definitions for inventory items, engineering items, and purchasing items. The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID. Therefore, the same item can be defined in more than one organization. Items now support multilingual description. MLS is implemented with a pair of tables: MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL. Translations table (MTL_SYSTEM_ITEMS_TL) holds item Description and Long Description in multiple languages.
MTL_ITEM_STATUS	This is the definition table for material status codes. Status code is a required item attribute. It indicates the status of an item, i.e., Active, Pending, Obsolete.
MTL_UNITS_OF_MEASURE_TL	This is the definition table for both the 25-character and the 3-character units of measure. The base_uom_flag indicates if the unit of measure is the primary unit of measure for the uom_class. Oracle Inventory uses this table to keep track of the units of measure used to transact an item.
MTL_ITEM_LOCATIONS	This is the definition table for stock locators. The associated attributes describe which subinventory this locator belongs to, what the locator physical capacity is, etc.
MTL_ITEM_CATEGORIES	This table stores inventory item assignments to categories within a category set. For each category assignment, this table stores the item, the category set, and the category. Items always may be assigned to multiple category sets. However, depending on the Multiple Assignments Allowed attribute value in a given category set definition, an item can be assigned to either many or only one category in that category set.
MTL_CATEGORIES_B	This is the code combinations table for item categories. Items are grouped into categories within the context of a category set to provide flexible grouping schemes. Item categories now support multilingual category description. MLS is implemented with a pair of tables: MTL_CATEGORIES_B and MTL_CATEGORIES_TL. MTL_CATEGORIES_TL table holds translated Description for Categories.
MTL_CATEGORY_SETS_B	It contains the entity definition for category sets. A category set is a categorization scheme for a group of items. Items may be assigned to different categories in different category sets to represent the different groupings of items used for different purposes. An item may be assigned to only one category within a category set, however. STRUCTURE_ID identifies the flexfield structure associated with the category set. Category Sets now support multilingual category set name and description. MLS is implemented with a pair of tables: MTL_CATEGORY_SETS_B and MTL_CATEGORY_SETS_TL. MTL_CATEGORY_SETS_TL table holds translated Name and Description for Category Sets.
MTL_DEMAND	This table stores demand and reservation information used in Available To Promise, Planning and other Manufacturing functions. There are three major row types stored in the table: Summary Demand rows, Open Demand Rows, and Reservation Rows.
MTL_SECONDARY_INVENTORIES	This is the definition table for the subinventory. A subinventory is a section of inventory, i.e., raw material, finished goods, etc. Subinventories are assigned to items (in a many to one relationship), indicating a list of valid places where this item will physically exist in inventory.
MTL_ONHAND_QUANTITIES	It stores quantity on hand information by control level and location. It is maintained as a stack of receipt records, which are consumed by issue transactions in FIFO order. The quantity on hand of an item at any particular control level and location can be found by summing TRANSACTION_QUANTITY for all records that match the criteria.
MTL_TRANSACTION_TYPES	It contains seeded transaction types and the user defined ones. USER_DEFINED_FLAG will distinguish the two. The table also stores the TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID that is associated with each transaction type.
MTL_MATERIAL_TRANSACTIONS	This table stores a record of every material transaction or cost update performed in Inventory. Records are inserted into this table either through the transaction processor or by the standard cost update program. The columns TRANSACTION_TYPE_ID, TRANSACTION_ACTION_ID, TRANSACTION_SOURCE_TYPE_ID, TRANSACTION_SOURCE_ID and TRANSACTION_SOURCE_NAME describe what the transaction is and against what entity it was performed.
MTL_ITEM_ATTRIBUTES	This table stores information on item attributes. Each row in the table corresponds to an attribute. The table stores the attribute name, the corresponding user-friendly name seen by the users, and the kind of validation enforced on the attribute.
MTL_ITEM_CATALOG_GROUPS_B	This is the code combinations table for item catalog groups. An item catalog group consists of items that can be described by the same set of descriptive elements or item properties. When an item is associated with an item catalog group, the item inherits the descriptive elements for that group which then behave like additional item attributes.
MTL_ITEM_REVISIONS_B	It stores revision levels for an inventory item. When an item is defined a starting revision record is written out to this table, so every item will at least have one starting revision.
MTL_ITEM_TEMPLATES_B	This is the definition table for item templates. It contains the user-defined name (TEMPLATE_NAME) and description (DESCRIPTION) ONLY for backward compatibility. You can use a template to set certain item attributes.
MTL_DESCRIPTIVE_ELEMENTS	It stores the descriptive element definitions for an item catalog group. Descriptive elements are defining properties used to describe in the catalog group.
MTL_DESCR_ELEMENT_VALUES	It stores the descriptive element values for a specific item. When an item is associated with a particular item catalog group, one row per descriptive element (for that catalog group) is inserted into this table.
ORG_ACCT_PERIODS	It holds the open and closed financial periods for organizations.
MTL_CUSTOMER_ITEMS	It stores customer item information for a specific customer. Each record can be defined at one of the following levels: Customer, Address Category, and Address. The customer item definition is organization independent.
MTL_SYSTEM_ITEMS_INTERFACE	It temporarily stores the definitions for inventory items, engineering items and purchasing items before loading this information into Oracle Inventory.
MTL_TRANSACTIONS_INTERFACE	It allows calling applications to post material transactions (movements, issues, receipts etc. to Oracle Inventory  transaction module.
MTL_ITEM_REVISIONS_INTERFACE	It temporarily stores revision levels for an inventory item before loading this information into Oracle Inventory.
MTL_ITEM_CATEGORIES_INTERFACE	This table temporarily stores data about inventory item assignments to category sets and categories before loading this information into Oracle Inventory.
MTL_DESC_ELEM_VAL_INTERFACE	This table temporarily stores descriptive element values for an item that is associated with an item catalog group before loading this information into Oracle Inventory.
MTL_DEMAND_INTERFACE	It is the interface point between non-Inventory applications and the Inventory demand module. Records inserted into this table are processed by the Demand Manager concurrent program.
MTL_INTERFACE_ERRORS	It stores errors that occur during the item interface process reporting where the errors occurred along with the error messages.

Oracle ASCP 客製化的相關知識 Viewing Pegged Supply and Demand

Viewing Pegged Supply and Demand

Prerequisites

   You must have Pegging selected as a plan option. See: Reviewing or Adding Plan Options.

   You must have the Pegging item attribute (in Oracle Inventory) set to one of the following options:

• Soft Pegging

• End Assembly Pegging

• End Assembly/Soft Pegging

If you are working in a project environment, you may also have the Pegging item attribute set to one of the following options:

• Hard Pegging

• End Assembly/Hard Pegging

See: MPS/MRP Planning Attribute Group.

   To view pegged supply information:

1. Navigate to the Planner Workbench window.

2. Select a plan name.

3. Choose Supply/Demand to display the Supply/Demand window.

4. In the Find Supply/Demand folder window, enter your search conditions. See: Using Query Find, Using Query Operators, and Customizing the Presentation of Data in a Folder.

5. Choose Find.

6. In the Supply/Demand window, select a demand order (indicated by a negative quantity) to reveal its pegged supply.

7. Choose Pegging to open the Object Navigator window for a graphical display of supply/demand relationships for an item.

With the Object Navigator, you can display your data in a visual hierarchy. Each element in the sourcing rule is displayed in a rectangular node, with connecting lines that depict the nodes' relationships to each another (known as the data flow). The nodes are color-coded for easy identification, and other aspects of the data flow can be changed to meet specific requirements.

   To view pegged demand information:

1. Navigate to the Supply/Demand window.

2. In the Supply/Demand window, select a supply order (indicated by a positive quantity) to reveal its source of demand.

3. Choose Pegging to open the Object Navigator window for a graphical display of supply/demand relationships for an item.

See Also

Reviewing or Adding Plan Options

You can enter additional plan options for any plan. You can also view plan options in the Plan Status window.

Note: If you are launching the planning process for this plan name for the first time, the plan options you defined in the setup parameters are displayed. Otherwise, the plan options you chose for the last launch of the planning process are displayed.

Supply Chain Planning users can also launch a DRP and supply chain MRP and MPS plan. Supply Chain Planning users should refer to Reviewing or Adding Supply Chain Plan Options for further instruction.

   To add plan options:

1. Navigate to the Plan Options window.

2. Query a plan name.

3. Select an overwrite option:

All: For an MPS plan, overwrite all entries and regenerate new MPS entries based on the source master demand schedule.

For an MRP, overwrite all planned orders and MRP firm planned orders for MRP items.

This option is displayed when you generate a plan for the first time.

Caution: Be very cautious when using this option since it overwrites firm planned orders and/or master schedule entries. If you do not want to overwrite MRP firm planned orders, select None.

Outside planning time fence: For an MPS plan, overwrite all MPS entries outside the planning time fence.

For an MRP, overwrite all planned orders and firm planned orders outside the planning time fence.

Caution: Be very cautious when using this option since it overwrites MRP firm planned orders and master schedule entries outside the planning time fence. If you do not want to overwrite MRP firm planned orders, select None.

None: Do not overwrite any firm planned orders for MPS or MRP plans and net change replan.

4. Check Append Planned Orders to append new planned orders in the following situations:

• If the MPS plan name has an existing schedule associated with it and you enter None as the overwrite option, the planning process does not recommend rescheduling or suggest new planned orders before the end of the existing MPS (the last planned order)--even if so indicated by new demand from the master demand schedule. This is analogous to firming your master production schedule. By not overwriting, the master scheduler is taking responsibility for manually planning items. For an MRP plan name, this option creates planned orders where needed, considering existing MRP firm planned orders.

Attention: If you want to add firm planned orders using net change replan, set the overwrite option to Outside planning time fence or None.

• If the plan name has an existing MPS or MRP associated with it and you enter All as the overwrite option, the planning process deletes all previous planned entries and creates new planned orders based on the source master schedule.

• If the plan name has an existing MPS or MRP associated with it and you enter Outside planning time fence as the overwrite option, the planning process deletes all planned entries after the planning time fence and creates new planned orders after that date. In this case, since you are overwriting after the planning time fence, you are also appending new planned orders after that date.

• If the plan name has an existing MPS or MRP associated with it and you enter None as the overwrite option and do not check this, the planning process reports the instances where the plan is out of balance with the source master schedule. It does not recommend any new orders. Instead it lets you manually solve any problems in the process. This gives maximum control to the master scheduler and/or material planner.

5. Check Demand Time Fence Control to indicate whether the planning process considers any demand from forecasts within the demand time fence.

The planning process does not consider any demand from forecasts within the demand time fence, but considers demand from sales orders.

6. Check Net WIP to indicate whether the planning process considers standard discrete jobs, non-standard discrete jobs, or repetitive schedules when planning the items during the last execution of the plan.

7. Check Net Reservations to indicate whether the planning process considers stock designated for a specific order when planning the items during the last execution of the plan.

8. Check Snapshot Lock Tables to indicate whether tables are locked during the snapshot process to guarantee consistent data.

This option temporarily prevents other users from processing certain transactions.

9. Check Planning Time Fence Control to indicate whether the planning process violates planning time fences for items.

For discrete items, the planning process does not create planned orders or recommend to reschedule in existing orders within the planning time fence of the item. The planning process can still recommend to reschedule orders out.

For repetitive items, the planning process can vary the suggested schedule from the optimal schedule, within the planning time fence, by the acceptable rate increase and/or decrease you specified for the item.

Note: For purchase requisitions and internal requisitions, the planning process ignores the planning time fence in all cases.

10. Check Net Purchases to indicate whether the planning process considers approved purchase requisitions when planning the items during the last execution of the plan

11. Check Plan Safety Stock to indicate whether the planning process calculates safety stock for each item during the last execution of the plan.

12. Check Plan Capacity to indicate whether you want to generate a capacity plan.

13. If you checked Plan Capacity, specify the Bill of Resources (for MPS plans only) and, optionally, a Simulation Set. See: Capacity Modifications and Simulations and Bills of Resources.

14. Check Pegging to calculate graphical pegging information. See: Overview of Graphical Pegging. The planning process then traces supply information for an item to its corresponding end demand details, which you then can view in a diagrammatic display.

Note: Graphical Pegging is available only when you enable the Memory-based Planning Engine. See: Memory-based Planning Engine.

15. If you are working in a project environment, set a Reservation Level and (optionally) a Hard Pegging Level. See: Reviewing or Adding Project MRP Plan Options.

16. Select a Material Scheduling Method:

Operation start date: Schedule material to arrive in inventory for availability on the start date of a specific operation in the manufacturing process.

Order start date: Schedule material to arrive in inventory for availability on the work in process order start date.

17. Specify which planned items or components you want included:

Note: If you are launching the planning process for a master production schedule, you cannot edit or enter data in MDS/MPS components fields.

All planned items: Include all planned items in the planning process. You would chose this option to be certain that all item are planned, such as those you add to a job or schedule that are not components on any bill.

Note: You may want to plan using this option to avoid missing items you want to plan. For items you do not want to plan, define them with an MRP planning method of Not planned when you define an item in Oracle Inventory.

Demand schedule items only

Supply schedule items only

Demand and supply schedule items

18. Save your work.

 

 

MPS/MRP Planning Attribute Group

Following are the MPS/MRP Planning item attributes and their possible values. You set these attributes when defining or updating items. See: Defining Items and Updating Organization Level Items.

Planning Method

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Select the option that Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses to decide when to plan the item:

Not planned	The item does not require long-term planning of material requirements. Choose this option for high volume and/or low cost items that do not warrant the administrative overhead of MRP; typically dependent demand items.
MRP planning	Choose this option for non-critical items that do not require manual planning control, typically dependent demand items.
MPS planning	You master schedule the item and require manual planning control. Choose this option for items with independent demand, items that are critical to your business, or items that control critical resources.
MRP/DRP Planned	Choose this option when you want both MRP and DRP planning for the item.
MPS/DRP Planned	Choose this option when you want both MPS and DRP planning for the item.
DRP Planned	Choose this option when you have multiple organizations for which you are exercising Distribution Requirements Planning for the item.

You cannot select Not planned if the Pick Components attribute is turned on. See: Order Entry Attribute Group. This is an item defining attribute. If you select MPS or MRP planning, the item is automatically assigned to the default category set for the Oracle Master Scheduling/MRP and Oracle Supply Chain Planning functional area. See: Item Defining Attributes.
See also: Overview of Material Requirements Planning.

Forecast Control

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Select an option to determine the types of demand you place for the item. This guides the key processes of two-level master scheduling: forecast explosion, forecast consumption, planning, production relief, and shipment relief. This is appropriate only for items that are models, option classes, options, or mandatory components of models and option classes.

Consume	You forecast demand directly, rather than by exploding forecast demand.
Consume and derive	You forecast demand directly, explode forecast demand, or use a combination of both methods.
None	You place sales order demand but do not forecast demand.

See: Overview of Two-Level Master Scheduling.

Exception Set

This attribute is controlled at the Organization level only. Enter the name of the planning exception set that groups together the sensitivity controls and exception time periods for item-level planning exceptions for the item. The item-level planning exceptions include: overcommitted, shortage, excess, and repetitive variance. The planning process uses this attribute to decide when to raise planning exceptions for the item.
Since different items may require different sensitivity controls and exception time periods, you can define multiple planning exception sets and assign different sets to different items. In other cases, where many items require the same sensitivity controls and exception time periods, you can associate the same set to multiple items. See: Overview of Material Requirements Planning and Creating Planning Exception Sets.

Pegging

Enter the pegging option. See: Reviewing Item Planning Information.

Soft Pegging	This option allocates supply to demand based on the Reservation Level option set in the MRP Plan options. See: Reviewing or Adding Plan Options.
End Assembly Pegging	This option traces the end assembly the item is pegged to at the top of the bill of material. Even if you do not select end assembly pegging, you can still calculate and view end assemblies on-line.
End Assembly/ Soft Pegging	Choose this option for both soft pegging and end assembly pegging.
Hard Pegging	This option allocates supply to demand based on the Reservation Level option set in the MRP Plan options. This pegs supply to demand and demand to supply by project at all levels of a bill of material. This allows you to pre-allocate supply to demand and generate planned orders based on the plan level options. See: Reviewing or Adding Plan Options.
End Assembly/ Hard Pegging	Choose this option for both hard pegging and end assembly pegging.
None	This option disables project material allocation, end assembly pegging, and full pegging.

Attention: You must use the memory-based planner to calculate end assembly pegging.

Round Order Quantities

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Indicate whether the planning process uses decimal or whole number values when calculating planned order quantities or repetitive rates. When this option is turned on, decimal values round up (never down) to the next whole number. The planning process carries any excess quantities and rates forward into subsequent periods as additional supply. See: Overview of Material Requirements Planning.

Shrinkage Rate

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Enter a factor that represents the average amount of material you expect to lose during manufacturing or in storage. The planning process inflates demand to compensate for this expected loss. For example, if on average 20% of all units fail final inspection, enter 0.2; the planning process inflates net requirements by a factor of 1.25 (1 / 1 - shrinkage rate). See: Overview of Material Requirements Planning.

Acceptable Early Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Enter the number of days before which the planning process will not reschedule orders. The planning process only suggests rescheduling out if:

   the new calculated order date is later than the original order due date plus the acceptable early days

   the new calculated order is does not violate the order of current scheduled receipts

For example, if the original order due date is 10-JUN, and Acceptable Early Days is 3, the planning process not suggest rescheduling if the new due date is less than or equal to 13-JUN. When rescheduling does not occur (because of Acceptable Early Days), a second order, due before the first, will not be rescheduled past the first order. This lets you reduce plan nervousness and eliminate minor reschedule recommendations, especially when it is cheaper to build and carry excess inventory for a short time than it is to reschedule an order.
This applies to discrete items only. For repetitive items, use Overrun Percentage. See: Overview of Material Requirements Planning.

Repetitive Planning

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Indicate whether to plan material requirements in repetitive daily rates. The planning process suggests repetitive schedules you can implement using the Planner Workbench. Turn this option off to plan material requirements in discrete quantities. The planning process suggests planned orders you can implement as discrete jobs or as purchase requisitions. See: Overview of Planner Workbench.

Overrun Percentage

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Enter a percentage the planning process uses to suggest new daily rates. The planning process only suggests a new daily rate if the current rate exceeds the suggested rate by more than the acceptable overrun amount.
The acceptable overrun amount is calculated by multiplying this percentage by the suggested daily rate. For example, if the suggested daily rate is 100/day, and Overrun Percentage is 10, the planning process only suggests a new rate if the current rate is greater than 110/day (100/day + 100/day x 10%).
This lets you reduce plan nervousness and eliminate minor rate change recommendations, especially when it is cheaper to carry excess inventory for a short time than it is to administer the rate change.
This attribute applies to repetitive items only. For discrete items, use Acceptable Early Days.
See: Overview of Repetitive Planning.

Acceptable Rate Decrease

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Enter the amount the planning process uses to decrease current daily rates inside the planning time fence. The planning process does not suggest a new daily rate less than the current daily rate minus the acceptable rate decrease amount.
The acceptable rate decrease amount is calculated by multiplying this value by the current daily rate. For example, if the current daily rate is 100/day, and the Acceptable Rate Decrease is 10, the planning process does not suggest a new daily rate that is less than 90/day (100/day - 100/day x 10%).
If you do not enter an Acceptable Rate Decrease, the planning process assumes no lower limit to the new daily rate it can suggest inside the planning time fence. If you enter zero, the planning process assumes it cannot suggest any rate less than the current daily rate inside the planning time fence.
This lets you minimize disruption to shop floor schedules by restricting short term rate change suggestions. This applies to repetitive items only. See: Overview of Repetitive Planning.

Acceptable Rate Increase

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Enter the amount the planning process uses to increase current daily rates inside the planning time fence. The planning process does not suggest a new daily rate greater than the current daily rate plus the acceptable rate increase amount.
The acceptable rate increase amount is calculated by multiplying this value by the current daily rate. For example, if the current daily rate is 100/day, and the Acceptable Rate Increase is 10, the planning process does not suggest a new daily rate that is greater than 110/day (100/day + 100/day x 10%).
If you do not enter an Acceptable Rate Increase, the planning process assumes no upper limit to the new daily rate it can suggest inside the planning time fence. If you enter zero, the planning process assumes it cannot suggest any rate greater than the current daily rate inside the planning time fence.
This lets you minimize disruption to shop floor schedules by restricting short term rate change suggestions. This applies to repetitive items only. See: Overview of Repetitive Planning.

Calculate ATP

Indicate whether to calculate and print available to promise (ATP) on the Planning Detail Report, using the following formula: ATP = Planned production - committed demand

Planned production = planned orders, scheduled receipts (purchase orders, jobs, and repetitive schedules), suggested repetitive schedules, nettable quantity on hand.

Committed demand = sales orders, component demand (from planned orders, discrete jobs, suggested repetitive schedules, and lot expirations). Committed demand does not include forecasted demand.

Attention: ATP calculated by the planning process is not related to ATP information calculated and maintained by Oracle Inventory.
As such, planning ATP does not consider ATP rules from the Available to Promise Rule window, and is not related to the ATP information displayed in the View Item Available to Promise Information window.

See: Overview of Material Requirements Planning.

Reduce MPS

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Select an option to decide when to reduce master production schedule (MPS) quantities to zero.
If Oracle Work in Process and Oracle Purchasing are installed, you get automatic production relief when you create a discrete job, purchase requisition, or purchase order. In this case, you would typically set this attribute to None.
If you do not have automatic production relief, you may select one of the following options to reduce MPS quantities and avoid overstating your supply.

None	Do not reduce order quantities on the MPS. 不可以縮減主排程訂單數量
Past due	Reduce order quantities on MPS entries to zero when the entry is past due. 當主排程已過期時, 縮減主排程訂單數量歸零
Demand time fence	Reduce order quantities on MPS entries to zero when the due date moves inside the demand time fence. 當主排程到期日進入需求時間柵欄時 ,縮減主排程訂單數量歸零
Planning time fence	Reduce order quantities on MPS entries to zero when the due date moves inside the planning time fence. 當主排程到期日進入計畫時間柵欄時 ,縮減主排程訂單數量歸零

See: Starting the Planning Manager.

Planning Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Choose one of the following options to determine a point in time inside which certain restrictions on planning recommendations apply. For discrete items, the planning process cannot suggest new planned orders or rescheduling existing orders to an earlier date. For repetitive items, the planning process can only suggest new daily rates that fall inside the acceptable rate increase and decrease boundaries. For items having a WIP Supply Type of Phantom, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning ignores the planning time fence.
A time fence increases manual control of the plan, minimizing short term disruption to shop floor and purchasing schedules.
Calculate the planning time fence as the plan date (or the next workday if the plan is generated on a non-workday) plus:

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Planning Time Fence Days.

See: Overview of Time Fence Planning.

Planning Time Fence Days 計畫時間柵欄日數

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the planning time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this value when Planning Time Fence is User-defined.

Demand Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Select an option to determine a point in time inside which the planning process ignores forecast demand and considers only sales order demand when calculating gross requirements. This reduces the risk of carrying excess inventory. For items having a WIP Supply Type of Phantom, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning ignores the demand time fence.

Attention: Oracle Master Scheduling/MRP and Oracle Supply Chain Planning also uses the demand time fence when loading master schedules.
主排程計畫跟供應鏈計劃都有使用需求時間柵欄在載入主排程時.
The demand time fence is calculated as the start date of the master schedule load plus one of the following options.
需求時間柵欄是計算主排程起始日期

Calculate the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus:

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Demand Time Fence Days.

See: Overview of Time Fence Planning.

Demand Time Fence Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this attribute when Demand Time Fence is User-defined.

Release Time Fence

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Choose an option to determine a point in time inside which planned orders for discretely planned items are automatically released as WIP jobs or purchase requisitions. The planned orders must meet the following auto-release criteria:

• the new due date lies within the auto-release time fence

• the lead time is not compressed

• the orders are for standard items (will not release models, option classes, and planning items)

• the orders are not for Kanban items

• the orders are for DRP planned items in a DRP plan, MPS planned items in an MPS plan, or MRP planned items in an MRP plan (See: Auto-release Planned Orders.)

• the release time fence option is defined as anything other than Do not auto-release, Do not release (Kanban), or Null

• DRP, MPS, and MRP plans must be run with the Memory-based Planning Engine (See: Enabling the Memory-based Planning Engine

Auto-release of repetitive schedules is not applicable for repetitively planned items. No material availability check is performed before WIP jobs are released. Calculate the release time fence as the plan date (or the next workday if the plan is generated on a non workday) plus:

Cumulative mfg. lead time	The cumulative manufacturing lead time for the item.
Cumulative total lead time	The total manufacturing lead time for the item.
Total lead time	The total lead time for the item.
User-defined	The value you enter for Release Time Fence Days.
Do not auto- release	The item cannot be auto-released

Do not release (Kanban)

For Kanban items, prevent release of planned orders manually or automatically.

See: Overview of Time Fence Planning.

Release Time Fence Days

ORACLE MASTER SCHEDULING/MRP AND SUPPLY CHAIN PLANNING ONLY Oracle Master Scheduling/MRP and Oracle Supply Chain Planning calculates the release time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here. Oracle Master Scheduling/MRP and Oracle Supply Chain Planning uses this value when Release Time Fence is User-defined.

 

Overview of Time Fence Planning

Time fences are boundaries between different periods in the planning horizon. They define short term regions within which planning restrictions minimize costly disruption to shop floor and supplier schedules. Time fences also provide guidelines to establish where various restrictions or changes in operating procedures take place. For example, you can easily accomplish changes to the MPS beyond the cumulative lead time while changes inside the cumulative lead time are more difficult to accomplish. Oracle Master Scheduling/MRP and Supply Chain Planning makes use of three time fences: the planning time fence, demand time fence, and release time fence.

Time Fences for Items

You can define planning, demand, and release time fence days for an item based on the cumulative manufacturing lead time, cumulative total lead time, total lead time, or a user-defined value. You can also use the release time fence to stop the release of Kanban items from Oracle Master Scheduling/MRP and Supply Chain Planning into Oracle Work in Process and Oracle Purchasing.

Master Schedule Creation Using the Demand Time Fence

When you load forecasts and sales orders into a master schedule you can specify whether to use demand time fence control. You can specify whether you load forecasts outside the demand time fence, sales orders within the demand time fence, or ignore demand time fences. See: Selecting Master Schedule Load Options.

Material Planning with the Demand and Planning Time Fences
有需求跟計畫時間柵欄的材料計畫

When you launch the planning process you can specify whether to consider planning, or demand time fence control. For an MPS plan, you can also choose to overwrite master schedule entries outside the planning time fence. For an MRP plan, you can overwrite all planned orders as well as firm planned orders that fall outside the planning time fence.

Planning Time Fences for Requisitions

Purchase requisitions and internal requisitions are not subject to planning time fence processes.

Material Planning with the Release Time Fence
有發布時間柵欄的材料計畫

When you define a plan or schedule name, you can allow the planning process to automatically release planned orders as standard discrete jobs in Oracle Work in Process, or as purchase requisitions in Oracle Purchasing.

You can also use the release time fence to stop the release of Kanban items from Oracle Master Scheduling/MRP and Supply Chain Planning.

Item Defining Attributes 品項定義屬性

An item defining attribute identifies the nature of an item.
每一個品項定義屬性, 來辨識該品項的原生屬性
What designates an item as an "engineering item" is the attribute Engineering Item, but what controls the functionality of the item are the collection of attributes that describe it.

You can buy an engineering item if you want to; simply set Engineering Item, Purchased, and Purchasable to Yes.
我們可以買一個工程品項假如我們要這樣
就是定義工程品項是採購品是可以採購的


The item defining attributes are:

Functional Area	Item Defining Attribute
Oracle Inventory	Inventory Item
Oracle Purchasing	Purchased, or Internal Ordered Item
Oracle Master Scheduling/MRP and Oracle Supply Chain Planning	MRP Planning Method
Oracle Cost Management	Costing Enabled
Oracle Engineering	Engineering Item
Oracle Order Entry	Customer Ordered Item
Oracle Service	Support Service, or Serviceable Product

When you set an item defining attribute to Yes, the item is automatically assigned to the default category set of the corresponding functional area. For example, if you set Inventory Item to Yes, the item is automatically assigned to the default category set for the Inventory functional area.

Defining Default Category Sets

When you install Oracle Inventory, you must assign a default category set to each of the following functional areas: Inventory, Purchasing, Order Entry, Costing, Engineering, and Planning. Product Line Accounting is seeded with the Inventory category set. Inventory makes the default category set mandatory for all items defined for use by a functional area. If your item is enabled for a particular functional area you cannot delete the item's corresponding default category set assignment. Default category sets are required so that each functional area has at least one category set that contains all items in that functional area. You can enable an item for each functional area by using that functional area's item defining attribute. An item defining attribute identifies the nature of an item. For example, what designates an item as an "engineering item" is the attribute Engineering Item. If a functional area's item defining attribute is controlled at the Organization level, then that functional area may only have an Organization level default category set.
You set the item defining attribute when you define the item. The item defining attributes are:

Functional Area	Item Defining Attribute	Enabling Value
Inventory	Inventory Item	Yes
Purchasing	Purchased	Yes
	Internal Ordered Item	Yes
Master Scheduling/ MRP	MRP Planning Method	MRP Planning, MPS Planning
Cost Management	Costing Enabled	Yes
Engineering	Engineering Item	Yes
Order Entry	Customer Ordered Item	Yes
Service	Support Service, or	Yes
	Serviceable Product	Yes
Product Line Accounting	none	n/a

When you enable an item for a certain functional area, Oracle Inventory automatically assigns the item to the default category set of that functional area and the default category of that set. For example, if you set Inventory Item to Yes, then Inventory automatically assigns the item to the Inventory functional area's default category set and default category. You may change a functional area's default category set under certain conditions. You should ensure that every item within the functional area belongs to the new default category set (which replaces the existing default category set). If the item defining attribute of the functional area is controlled at the Organization level then the new default category set should also be controlled at the Organization level.

Prerequisites

   You must define at least one category set. See: Defining Category Sets.

   To define a default category set:

1. Navigate to the Default Category Sets window.

2. Select the category set to use as the default for the functional area.

Oracle Inventory also makes this category set mandatory for all items defined for use by the functional area.

You should not change the Purchasing category set after you have created requisition or purchase order lines using the categories.

Product Line Accounting is enabled when you assign a default category set.

3. Save your work.

 

Item Attributes Listed by Group Name

Main

• Primary Unit of Measure

• User Item Type

• Item Status

• Conversions

Inventory

• Inventory Item

• Stockable

• Transactable

• Revision Control

• Reservable

• Lot Expiration (Shelf Life) Control

• Shelf Life Days

• Lot Control

• Starting Lot Prefix

• Starting Lot Number

• Cycle Count Enabled

• Negative Measurement Error

• Positive Measurement Error

• Serial Generation

• Starting Serial Prefix

• Starting Serial Number

• Locator Control

• Restrict Subinventories

• Restrict Locators

Bills of Material

• BOM Allowed

• BOM Item Type

• Base Model

• Engineering Item (Oracle Engineering only)

Costing

• Costing Enabled

• Inventory Asset Value

• Include in Rollup

• Cost of Goods Sold Account

• Standard Lot Size

Purchasing

• Purchased

• Purchasable

• Use Approved Supplier

• Allow Description Update

• RFQ Required

• Outside Processing Item

• Outside Processing Unit Type

• Taxable

• Receipt Required (Three-Way Invoice Matching)

• Inspection Required (Four-Way Invoice Matching)

• Default Buyer

• Unit of Issue

• Receipt Close Tolerance

• Invoice Close Tolerance

• UN Number

• Hazard Class

• List Price

• Market Price

• Price Tolerance

• Rounding Factor

• Encumbrance Account

• Expense Account

• Asset Category

Receiving

• Receipt Date Action

• Receipt Days Early

• Receipt Days Late

• Overreceipt Quantity Control Action

• Overreceipt Quantity Control Tolerance

• Allow Substitute Receipts

• Allow Unordered Receipts

• Allow Express Transactions

• Receipt Routing

• Enforce Ship-To

Physical Attributes

• Weight Unit of Measure

• Unit Weight

• Volume Unit of Measure

• Unit Volume

• Container

• Vehicle

• Container Type

• Internal Volume

• Maximum Load Weight

• Minimum Fill Percentage

General Planning

• Inventory Planning Method

• Planner

• Make or Buy

• Min-Max Minimum Quantity

• Min-Max Maximum Quantity

• Minimum Order Quantity

• Maximum Order Quantity

• Order Cost

• Carrying Cost Percent

• Source Type (Replenishment)

• Source Organization

• Source Subinventory

• Safety Stock Method

• Safety Stock Bucket Days

• Safety Stock Percent

• Fixed Order Quantity

• Fixed Days Supply

• Fixed Lot Multiplier

MPS/MRP Planning

• Planning Method

• Forecast Control

• Exception Set

• Pegging

• Shrinkage Rate

• Round Order Quantities

• Acceptable Early Days

• Repetitive Planning

• Overrun Percentage

• Acceptable Rate Increase

• Acceptable Rate Decrease

• Calculate ATP

• Reduce MPS

• Planning Time Fence

• Planning Time Fence Days

• Demand Time Fence

• Demand Time Fence Days

• Release Time Fence

• Release Time Fence Days

Lead Times

• Preprocessing

• Processing

• Postprocessing

• Fixed

• Variable

• Cumulative Manufacturing

• Cumulative Total

• Lead Time Lot Size

Work in Process

• Build in WIP

• Supply Type

• Supply Subinventory

• Supply Locator

Order Entry

• Customer Ordered

• Customer Orders Enabled

• Shippable

• Internal Ordered

• Internal Orders Enabled

• OE Transactable

• Pick Components

• Assemble to Order

• ATP Components

• Ship Model Complete

• Check ATP

• ATP Rule

• Picking Rule

• Collateral Item

• Default Shipping Organization

• Returnable

• RMA Inspection Required

Invoicing

• Invoiceable Item

• Invoice Enabled

• Accounting Rule

• Invoicing Rule

• Tax Code

• Sales Account

• Payment Terms

Service

• Support Service

• Warranty

• Coverage

• Service Duration

• Billing Type

• Serviceable Product

• Service Starting Delay