WIP_DISCRETE_JOBS.STATUS_TYPE values in Oracle WIP ( work in process)

WIP_DISCRETE_JOBS.STATUS_TYPE values in Oracle WIP ( work in process)

The following lookup table can be query to find the status_type of a discrete job in oracle applications discrete manufacturing work in process.

SELECT *
FROM apps.fnd_lookup_values
WHERE lookup_type LIKE ‘%WIP_JOB_STATUS%’

SELECT status_type FROM wip_discrete_jobs WHERE wip_entity_id = 1743670;

Value	Meaning
7	Cancelled
8	Pending Bill Load
9	Failed Bill Load
10	Pending Routing Load
11	Failed Routing Load
12	Closed
13	Pending - Mass Loaded
14	Pending Close
15	Failed Close
1	Unreleased
3	Released
4	Complete
5	Complete - No Charges
6	On Hold

JAVA: JDBC connect to Oracle

import java.sql.*;
public class TestJDBC {

public static void main(String[] args) {

String host = "localhost";
String dbName = "orcl";
int port = 1521;
String oracleURL = "jdbc:oracle:thin:@" + host + ":" + port + ":" +dbName;
String username = "scott";
String password = "tiger";

try {
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection connection = DriverManager.getConnection(oracleURL, username, password);
Statement s = connection.createStatement();
String query =
"SELECT empno, ename, job, sal from emp where rownum < 10";
ResultSet results = s.executeQuery(query);

while(results.next()) {
System.out.println(results.getString(1) + "---" +results.getString(2) + "---" +
results.getString(3) + "---" +results.getString(4));

}

connection.close();
}

catch (ClassNotFoundException cnfe) {
System.out.println("Error loading driver: ");
}

catch (SQLException sqle) {
System.out.println("SQL Error ...........: ");
}

catch (Exception others) {
System.out.println("Error ........... others: " +others.getMessage());
}
}
} 

how to pass table type to procedure in oracle

example:

CREATE OR REPLACE PACKAGE xxabc AS

  TYPE qty_compl_t IS RECORD(

     action           VARCHAR2(30)

    ,production_order VARCHAR2(30)

    ,qty_completed    NUMBER

    ,operation_code   NUMBER

    ,production_card  VARCHAR2(30)

    ,shift            VARCHAR2(10)

    ,scrap            NUMBER

    ,resource_code    VARCHAR(30)

    ,time_usage       NUMBER

    ,operator         VARCHAR2(200)

    ,reg_date         DATE

    ,crate_id         VARCHAR2(200));

  TYPE qty_com_table_t IS TABLE OF qty_compl_t INDEX BY BINARY_INTEGER;

  PROCEDURE qtycom

  (

    p_prod_no       IN VARCHAR2

   ,p_qty_com_table IN qty_com_table_t

  );

END;

/

CREATE OR REPLACE PACKAGE BODY xxabc AS

  PROCEDURE qtycom

  (

    p_prod_no       IN VARCHAR2

   ,p_qty_com_table IN qty_com_table_t

  ) IS

  BEGIN

    dbms_output.put_line('p_prod_no :' || p_prod_no);

    dbms_output.put_line('p_qty_com_table.count :' || p_qty_com_table.count);

    NULL;

  END;

END;

/

DECLARE

  l_tab xxabc.qty_com_table_t;

BEGIN

  l_tab(1).action := 'hello';

  l_tab(2).action := 'world';

  xxabc.qtycom('value', l_tab);

END;

To run a procedure from sql developer

Here is a sample code to run a procedure from SQL Developer or TOAD.

Declare

    l_errbuf varchar2(100):= 'No error';

    l_retcode number:= 0;

begin

    dbms_output.put_line('Start of script');

    xxcus.xxabc_pkg.SendOrder (l_errbuf, l_retcode, 1299, 1420042);

    dbms_output.put_line('End of Script');

    commit;

end;

Import customers using interface tables in Oracle Apps R12

To Import Customers using interface tables

Step 01. 

Insert the data in ra_customers_interface_all and ra_customer_profiles_int_all

insert into ra_customers_interface_all
(orig_system_customer_ref, -- SHOULD BE UNIQUE
insert_update_flag,
customer_name, -- SHOULD BE UNIQUE
cust_tax_reference,
person_flag,
person_first_name,
person_last_name,
address1,
address2,
address3,
address4,
postal_code,
city,
country,
customer_status,
site_use_code,
primary_site_use_flag,
orig_system_address_ref, -- SHOULD BE UNIQUE
last_updated_by,
created_by,
creation_date,
org_id,
customer_type)
values( 2007, -- will be incremented
'I',
'Muhammad Ahmed',
4,
'ABM',
'MRO',
F10/1,
F10/2,
F10/3,
F10/4,
44000,
ISLAMABAD,
'PK',
'A',
'BILL TO',
'N',
'7002,
1327,
SYSDATE,
1327,
SYSDATE,
204, 
'R');

INSERT INTO RA_CUSTOMER_PROFILES_INT_ALL
(orig_system_customer_ref, -- SHOULD BE REFER THE ABOVE
-- ar_customers_interface_all.orig_system_customer_ref
insert_update_flag,
customer_profile_class_name,
credit_hold,
last_updated_by,
last_update_date,
created_by,
creation_date,
org_id)
VALUES
(2007,
'I',
'DEFAULT', 
'N',
1327,
SYSDATE,
1327,
SYSDATE,
204);

Step 02. 

Logon to receivables responsibility >> Receivables >> Request Customer interface
or logon to receivables responsibility >> Receivables >> Interfaces >> Customer

Step 03. 

Verify the customer in Apps:
>> Customers >> Customers
enter the customer name and click go:

select * from ar_customers
where customer_name like 'Muhammad Ahmed';

ora-00980 synonym translation is no longer valid

synonym translation is no longer valid

Cause: The synonym used is based on a table, view, or synonym that no longer exists.
Action: Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.
Oracle docs also has more information on ORA-00980 regarding invalid synonyms.  Here, they reveal that the “ORA-00980: synonym translation is no longer valid” is a common error encountered in a development environment. This ORA-00980 error can happen for many reasons. Some of them are:

1. You created a synonym on non-existing object by mistake. For example, you created a synonym on SCOTT.DEPT where either the SCOTT schema in not present or the DEPT table is missing.
2. You dropped an object but you did not drop the synonyms referencing the object.
3. You dropped a user, but you did not drop synonyms referencing the objects owned by that user.

Keep in mind when reviewing your ORA-00980 situation that as objects become dropped the synonyms are not dropped and they remain until explicitly dropped.

Key Tables in Oracle Apps Inventory

Table	Description
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.