Oracle Applications - Getting Journals posted after a cut off time - Oracle GL

select '="'||to_char(to_date(h.period_name,'MON-YY'),'MON-YY')||'"' as period_name
                           ,'="'||to_char(h.posted_date,'DD-MON-YYYY HH24:MI:SS')||'"' as posted_date
                          --,to_char(h.posted_date,v_date_format) as posted_date
                         -- ,to_char(h.posted_date,'DD-MON-YYYY HH:MI:SS') as posted_date
                           ,u2.user_name     as Posted_by
                          ,replace(u2.description,',',NULL)   as Posted_by_name
                          ,replace(replace(replace(b.name,',',NULL),chr(10),NULL),chr(13),NULL) as batch_name
                          ,h.name             as journal_name
                          ,replace(replace(replace(h.description,',',NULL),chr(10),NULL),chr(13),NULL) as description
                          ,h.je_source
                          ,h.je_category
                          --,h.date_created
                          ,'="'||to_char(h.date_created,'DD-MON-YYYY HH24:MI:SS')||'"' as date_created
                          ,u1.user_name     as Created_by
                          ,replace(u1.description,',',NULL)     as Created_by_name
                    from apps.gl_je_batches    b
                        ,apps.gl_je_headers    h
                        ,apps.gl_je_categories cat
                        ,fnd_user                u1
                        ,fnd_user                u2
                    where b.je_batch_id      = h.je_batch_id
                      and   h.created_by      = u1.user_id
                      and h.last_updated_by = u2.user_id
                      and h.je_category     = cat.je_category_name
                      and h.set_of_books_id = 1
                      --and h.period_name     in ('JUN-10')
                      and h.period_name     = 'APR-12'
                      and h.status             = 'P'
                      and h.posted_date >= to_date('4-MAY-2012 21:00:00','DD-MON-YYYY HH24:MI:SS')
        order by h.posted_date;

Oracle Applications - Query to get all responsibilities assigned to all active users

select  distinct responsibility_name ,y.user_name
       ,y.description
      , z.employee_number
      , z.full_name,
       z.first_name,
       z.last_name
        from apps.fnd_user_resp_groups x , fnd_user y , per_people_f z ,fnd_responsibility_tl a
              where x.responsibility_id = a.responsibility_id    
    and  x.start_date <=sysdate and (x.end_date is null OR x.end_date > sysdate)
    and y.user_id = x.user_id
    and  y.start_date <=sysdate and (y.end_date is null OR y.end_date > sysdate)
    and z.employee_number = y.user_name
    and  z.effective_start_date <=sysdate
    and (z.effective_end_date  > sysdate or z.effective_end_date is NULL)
    and language = 'US'
    order by employee_number nulls first

Copying data along with the Column headers from Data grid in Toad

When you need to copy data from the Toad Data grid, CTRL+V will not copy the column headers. If you need the Column headers to be copied, press CTRL+INSERT to copy the headers as well.

SQL to get the Next or previous Weekend Date - NEXT_DAY

The below SQL gives the next Saturday and the next Sunday dates.


SELECT NEXT_DAY('06-MAR-2012', 'SATURDAY') "next saturday" 
,NEXT_DAY('06-MAR-2012', 'SUNDAY') "next sunday"
FROM dual;

If the requirement is to find the previous weekend dates, just subtract the dates by 7.


SELECT NEXT_DAY('06-MAR-2012', 'SATURDAY')-7 "next saturday" 
,NEXT_DAY('06-MAR-2012', 'SUNDAY')-7 "next sunday" 
FROM dual;

SQLLDR - SQL* Loader ORA-01008: not all variables bound

IF you are receiving this error, it might be due to issues in multiple places. You have to understand that the error is not in SQL Loader alone.

It might be due to the Call to SQL Loader when a bind variable used to call it is undefined.

But the majority of this issue is due to the bind variables referenced in the control file of the SQL Loader itself.

Check for any typos in all the bind variables or any bind variable name that is not used in the control file.

Record 2: Rejected - Error on table TEST.
ORA-01008: not all variables bound

Oracle Applications - Key tables - MTL_SYSTEM_ITEMS_B

MTL_SYSTEM_ITEMS_B

columns: 

INVENTORY_ITEM_ID : Inventory item identifier 
ORGANIZATION_ID : Organization identifier 
ACCOUNTING_RULE_ID : Accounting rule identifier 
INVOICING_RULE_ID : Invoicing rule identifier 
PURCHASING_ITEM_FLAG: Flag indicating purchasing item 
SHIPPABLE_ITEM_FLAG : Flag indicating shippable item 
CUSTOMER_ORDER_FLAG : Flag indicating customer orderable item 
INTERNAL_ORDER_FLAG : Flag indicating internally orderable item 
SERVICE_ITEM_FLAG : Flag indicating service item 
INVENTORY_ITEM_FLAG : Flag indicating inventory item 
ENG_ITEM_FLAG : Flag indicating engineering item 
INVENTORY_ASSET_FLAG : Flag indicating item is an inventory asset 
PURCHASING_ENABLED_FLAG : Flag indicating item is purchasable 
CUSTOMER_ORDER_ENABLED_FLAG : Flag indicating item is customer orderable 
INTERNAL_ORDER_ENABLED_FLAG : Flag indicating item is internally orderable 
SO_TRANSACTIONS_FLAG VARCHAR2 : Sales order transactions flag 
MTL_TRANSACTIONS_ENABLED_FLAG : Flag indicating item is transact-able 
STOCK_ENABLED_FLAG : Flag indicating item is stock-able 
BOM_ENABLED_FLAG : Flag indicating item may appear on a BOM 
BUILD_IN_WIP_FLAG : Flag indicating item may be built in WIP

Description: 

MTL_SYSTEM_ITEMS_B is the master table for items. This table contains the definitions for inventory items, engineering items, and purchasing items. Main item characteristics include  Bill of Material, Costing, Purchasing, Receiving, Inventory, Physical attributes, General Planning, MPS/MRP Planning, Lead times, Work in Process, Order Management, and Invoicing.

The primary key for an item is the INVENTORY_ITEM_ID and ORGANIZATION_ID.

Each item is initially defined in an item master organization. The user. A row is inserted for each new organization the item is assigned to. Many columns such as MTL_TRANSACTIONS_ENABLED_FLAG and BOM_ENABLED_FLAG correspond to item attributes defined in the
MTL_ITEM_ATTRIBUTES table. The attributes that are available to the user depend on which Oracle applications are installed. The table MTL_ATTR_APPL_DEPENDENCIES maintains the relationships between items attributes and Oracle applications.

Two unit of measure columns are stored in MTL_SYSTEM_ITEMS_B table. PRIMARY_UOM_CODE is the 3-character unit that is used throughout Oracle Manufacturing. PRIMARY_UNIT_OF_MEASURE is the 25-character Unit of Measure that is used throughout Oracle Purchasing. Unlike the PRIMARY_UOM_CODE, the Unit of Measure is language-dependent attribute, however, PRIMARY_UNIT_OF_MEASURE column stores value in the installation base language only.

MLS tables are 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. DESCRIPTION column in the base table (MTL_SYSTEM_ITEMS_B) is for backward compatibility and is maintained in the installation base language only.

Oracle Applications - Query to list all the responsibilities assigned to a user

Oracle Applications - Query to list all the responsibilities assigned to a user

SELECT DISTINCT
fu.user_name, frtl.RESPONSIBILITY_NAME
FROM fnd_responsibility fr
, fnd_responsibility_TL frtl
, fnd_user_resp_groups furg
, fnd_user fu
WHERE furg.responsibility_id = fr.responsibility_id
AND frtl.responsibility_id = fr.responsibility_id
and fr.APPLICATION_ID=furg.RESPONSIBILITY_APPLICATION_ID
AND fu.user_id = furg.user_id
AND fu.user_name = '12345'  -- username here
order by fu.user_name