1. What is 2-way, 3-way, 4-way matching? How is this set up?
2. How do you reflect discount from a supplier on a Purchase orders?
3. How do you change the created date on a Purchase Order?
4. When do you see the status of a Purchase order as Archived?
5. What does the error 'APP-50022: Oracle Human Resources could not retrieve a value for User Type profile option' mean?
Monday, September 15, 2008
Thursday, September 4, 2008
Three Questions
1. Which entity should be defined first, the "routing" or "BOM"?
2. What are the pre-requisites for Routing define?
3. What is the use of "Department" on the routing?
Please use "comments" option to answer with your inputs
2. What are the pre-requisites for Routing define?
3. What is the use of "Department" on the routing?
Please use "comments" option to answer with your inputs
Sunday, August 24, 2008
Oracle Quality - An Introduction
Oracle Quality application can be used to gather user-defined quality data. It is integrated with the Oracle Manufacturing and Distribution applications. Data collected and input into Oracle Quality may come from functions such as purchasing, service, shopfloor inspection or directly from the customer, to name a few. Quality data can also be collected in a totally standalone method or may be linked to third party systems.
The data collection structure in Oracle Quality comprises of:
a) Collection Elements
b) Specifications
c) Collection Plans
The basic building block of this structure is the collection element, which is used in both the specification and the collection plan. Collection elements define the characteristics or the quality parameters of the product or the process, which is being analyzed and for which we collect and report data. Collection Plans are similar to test or inspection plans. Collection plans specify which are the collection elements to be used in collecting data. Collection plans specify when
and how to collect the data as well as the actions to take based on the data collected. Specifications set the quality standards to which the product or the process should conform. These standards can be in the form of absolute values or a specific range within which the results would be acceptable. The type of collection elements being used determines the nature of the specification.
Industry professionals already working in Quality functions (Quality Assurance, Quality Control) might find this interesting to know more?
The data collection structure in Oracle Quality comprises of:
a) Collection Elements
b) Specifications
c) Collection Plans
The basic building block of this structure is the collection element, which is used in both the specification and the collection plan. Collection elements define the characteristics or the quality parameters of the product or the process, which is being analyzed and for which we collect and report data. Collection Plans are similar to test or inspection plans. Collection plans specify which are the collection elements to be used in collecting data. Collection plans specify when
and how to collect the data as well as the actions to take based on the data collected. Specifications set the quality standards to which the product or the process should conform. These standards can be in the form of absolute values or a specific range within which the results would be acceptable. The type of collection elements being used determines the nature of the specification.
Industry professionals already working in Quality functions (Quality Assurance, Quality Control) might find this interesting to know more?
Thursday, August 21, 2008
Oracle Work in Process (WIP) Tables
wip_move_transactions
wip_discrete_jobs
wip_repetitive_schedules
wip_move_txn_interface
wip_cost_txn_interface
wip_job_shedule_interface
wip_job_dtls_interface
wip_discrete_jobs
wip_repetitive_schedules
wip_move_txn_interface
wip_cost_txn_interface
wip_job_shedule_interface
wip_job_dtls_interface
Oracle Bills of Material (BOM) Tables
bom_bill_of_materials
bom_inventory_components
bom_reference_designators
bom_substitute_components
mtl_item_revisions
bom_operational_routings
bom_operation_sequences
bom_operation_resources
BOM_BILL_OF_MTLS_INTERFACE
BOM_INVENTORY_COMPS_INTERFACE
BOM_REF_DESGS_INTERFACE
BOM_SUB_COMPS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
MTL_RTG_ITEM_REVS_INTERFACE
bom_inventory_components
bom_reference_designators
bom_substitute_components
mtl_item_revisions
bom_operational_routings
bom_operation_sequences
bom_operation_resources
BOM_BILL_OF_MTLS_INTERFACE
BOM_INVENTORY_COMPS_INTERFACE
BOM_REF_DESGS_INTERFACE
BOM_SUB_COMPS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE
BOM_OP_ROUTINGS_INTERFACE
BOM_OP_SEQUENCES_INTERFACE
BOM_OP_RESOURCES_INTERFACE
MTL_RTG_ITEM_REVS_INTERFACE
Subscribe to:
Posts (Atom)
Please enter your email address to subscribe
You won't repent doing this!