SELECT *
FROM apps.fnd_user
WHERE trunc(SYSDATE) BETWEEN trunc(start_date) AND
nvl(end_date,trunc(SYSDATE));

select
fg.request_group_name,e.executable_name,responsibility_key,user_concurrent_program_name
from fnd_responsibility r,
fnd_concurrent_programs_tl p,
fnd_request_group_units u,
fnd_request_groups fg,
fnd_executables e,
fnd_concurrent_programs fcp
where r.request_group_id=u.request_group_id
and u.request_group_id = fg.request_group_id
and u.request_unit_id = p.concurrent_program_id
and fcp.executable_id = e.executable_id
and user_concurrent_program_name like ‘%Period close value summary%’
and fcp.concurrent_program_id = p.concurrent_program_id

To find out various concurrent programs associated with certain responsibility, following query will be useful.

select user_concurrent_program_name  from fnd_concurrent_programs_tl
where concurrent_program_id in (
select request_unit_id from fnd_request_group_units
where request_group_id in (
select request_group_id from fnd_request_groups where request_group_id in (
select request_group_id from fnd_responsibility where responsibility_key like ‘%ORACLE_INVENTORY%’)
));

To find out concurrent programs scheduled go to ‘Find Requests’ window using ‘System Administrator’ responsibility.

a) Click on ‘Specific Requests’ radio button.

b) select ‘Scheduled’ in Status drop-down as shown in following screen shot.

c) Click on ‘Find’ button.

All scheduled requests will be shown as in following screen shot.

d) Select any concurrent program and click on ‘View Details’ button, and you can seen concurrent program schedule details as follows.

Similary using ‘Phase’ drop down in ‘Find Requests’ window, you can find out all concurrent programs which are either in ‘Running’, ‘Completed’, ‘Inactive’ or ‘Pending’ state.

Here is a sample PL/SQL procedure which can read a file from a specified location, into a BLOB and returns it.

The calling program can convert this blob data into any form.

Calling program can be another PL/SQL procedure or a Java Program or some other language program.

Note: following procedure works only on Oracle Database.

=============================================================

create or replace procedure READ_FILE_TO_BLOB(

dest_lob_return OUT BLOB,

file_name IN VARCHAR2)

is

    – BFILE_LOC is the directory created, with help of

    –create directory BFILE_LOC as ‘/export/home/test/d01/oratst/testcomn/admin/out/TEST_xxxxxxr06/’;

    src_lob  BFILE := BFILENAME(‘BFILE_LOC’, file_name); 

    dest_lob BLOB;

    v_lob_len INTEGER;

    v_offset NUMBER := 1;

    v_buffer       RAW(20);

    v_buffer_size  BINARY_INTEGER := 20;

BEGIN

   DBMS_LOB.CREATETEMPORARY(dest_lob, TRUE, DBMS_LOB.SESSION);

   DBMS_LOB.OPEN(src_lob, DBMS_LOB.LOB_READONLY);

   DBMS_LOB.LoadFromFile( DEST_LOB => dest_lob,

                          SRC_LOB  => src_lob,

                          AMOUNT   => DBMS_LOB.GETLENGTH(src_lob) );

   DBMS_LOB.CLOSE(src_lob);

   dest_lob_return := dest_lob;

end READ_FILE_TO_BLOB;

===============================================================

Instead of running Receiving Interface Errors Report concurrent Program, you can simply query the error from Oracle Database in po_interface_errors table.

Use following query:

select * from apps.po_interface_errors where request_id = 1192033 order by creation_date desc;

where parameter request_id is , request id of concurrent program receiving transaction processor.

To Define Subinventory:

1) loginto Oracle Applications.

2) Click on path Inventory -> setup: organizations -> Subinventories.

3) select the organization in which you are going to create subinvenotry, in organizations window displayed.

4) Click on New button in Subinventories Summary window displayed.

5) Subinventories window will appear.

6) Enter unique name for subinventory.

7) Status field: Indicate material status of this subinventory, which controls all material transactions within this subinventory.

Default Cost Group: Assign a default cost group value. This cost group will be there with subinventory until you change cost group. If, cost group assignement material rule fails for a received material, then this default cost group will be assigned.

9) Type field: Select the type of the subinventory Storage or Receiving.

Storage: Designates subinventory as Storage Subinventory.

Receiving: Designates subinventory as Receiving Subinventory, can be used for only Receiving Material. Material in this type of subinventory can’t be onhand or reserved.

Subinventory Parameters:

Quantity Tracked: indicates whether each transaction for this subinventory updates quantity on hand for subinventory.

Asset Subinventory: Indicates whether to maintain value of this subinventory on balance sheet. Update this value only if there is no on hand qunatity for subinventory.

Depriciable: Indicates whether subinventory is depriciable.

Enable PAR Level Planning: Indicates Periodic Automatic Replenishment is enabled. If this is enabled min-max planning can’t be performed on this subinventory.

Locator Control: Select locator control only if this organization has locator control parameter as Determined at Subinventory Level. Updates on this field are allowed only if there is no on hand quantity available.

• None

• : Inventory transactions within this subinventory do not require locator information.
• Prespecified

 

• : Inventory transactions within this subinventory require you to enter a valid predefined locator for each item.
• Dynamic entry

 

• : Inventory transactions within this subinventory require you to enter a locator for each item. You may choose a valid predefined locator, or define a locator dynamically at the time of transaction.
• Item level

 

• : Inventory transactions use locator control information that you define at the item level.

Default Locator Status field will be available only if Warehouse Management installed.

Inactive On: Optionally enter date on which subinventory goes inactive.

Location: Enter location for subinventory, if it is receiving subinventory field is mandatory.

Picking UOM: Indicate the picking unit of measure used to store material in this subinventory.

Picking UOM Default Replenishment: Select the appropriate Default Replenishment Count Type from the drop downlist.

Optionally enter all Lead Times.

Sourcing Type: Select Source Type for Item Replenishment.

• Inventory

• : Replenish items internally, from another organization.
• Supplier

 

• : Replenish items externally, from a supplier you specify in Oracle Purchasing.

• : Replenish items internally, from another subinventory in the same inventory organization.

Organization: Select the organization used to replenish items in this subinventory. You must enter a value in this field if you entered

 

Inventory

in the Type field. The organization you select must have a shipping network defined.

SubInventory: Select the subinventory used to replenish items in this subinventory. You must enter a value in this field if you entered your current organization in the Organization field.

 

 

 

Only users having System Administrator previliges can create new users in Oracle E-Business Suite.

STEPS:

1) Login to Oracle E-Business Suite using System Administrator Responsibility.

2) Click on menu link Security: user –> Define, you will be shown below screen.

3) Enter UserName in User Name field.

4) Enter Password in Password field.

Note: Password should be entered twice, so that system will confirm it.

5) Associate this user to any person from Person field LOV. (Optional)

6) We can set user password to be expire in certain days or never expired using ‘Password Expiration’ Section.

7) Add responsibilities for current user, in Direct Responsiblities tab.

8 ) Click on Save Button.

New user is created to access Oracle E-Business Suite.

It is a template based publishing solution developed with Oracle E-Business Suite.

XML Publisher leverages standard, well-known technologies and tools, so you can rapidly develop and maintain custom report formats.

The flexiblity of XML Publisher is seperation of presentation of the report from its data structure, data is still maintained by E-Business Suite, but now we can design and control how the report output files will be presented in seperate template files.

How it will be done:

At runtime XML Publisher merges designed template with report data to create variety of outputs, that business needs.

This requirement may come in case of generating cheques for invoices, Signature content on each report like invoice, packslips, purchase orders.

To do this add XML publisher content tag as

<?start@last-page:body?> <?end body?>

before this line add ‘Continuous Section Break’ of MS-Word in your rtf template file.

Click on Insert->Break menu in MS-Word and select ‘Continuous’ radious button in the break dialog that comes up.

Any content followed above tag line will be shown at footer part of your report.

In some cases if report fits on single page, then you can use

<?start@last-page-first:body?> <?end body?>

as last page content tag.