Thursday 31 December 2015

Open various accounting periods in Oracle Apps



1. Please check "GL Set of Books Name" profile for the responsibility in which you are receiving,   from System Administrator responsibility. It should be set to the correct Set of Books name

2. Ensure the GL period is open for the accounting period in question using:
    Purchasing -> Setup -> Financials -> Accounting -> Open and Close Periods

3. Ensure the Purchasing period is open for the accounting period in question using:
    Purchasing ->  Setup-> Financials -> Accounting -> Control PO Periods

4. Ensure the Inventory period is open for the accounting period in question using:
    Inventory ->  Accounting Close Cycle -> Inventory Accounting Periods

5. Ensure the Accounts Payable period is open for the accounting period in question using:
    Payables -> Accounting -> Control Payables Period



Tuesday 22 December 2015

Creating JAR files on desktop for custom OAF project files



Creating JAR files on desktop for OAF project files

Steps:

1) Go to the <code path>/myprojects/oracle/apps
2) Copy xxcst folder and paste to <jdev install dir>/jdevbin\jdk\bin
3) Remove any unnecessary files from xxcst folder.
4) Go to Cmd and cd to <jdev install dir>/jdevbin\jdk\bin
5) Execute the below cmd

jar -cf <jar file name>.jar xxcst

6) Deploy the JAR appropriately

Thursday 17 December 2015

Useful metalinks for EBS Developers


Useful metalinks for EBS Developers

Oracle Applications Framework(OAF) related notes:

Dev Guides:

Oracle Application Framework Developer's Guide Release 12.1.3 [ID 1107973.1]

Oracle Application Framework Developer's Guide Release 12.1.2 [ID 972774.1]

Oracle Application Framework Developer's Guide Release 12.1.1 [ID 744832.1]

Configuring JDeveloper For Use With Oracle Applications 11i and R12 [ID 330236.1])

Oracle Application Framework: Allowing an Extended VO to See Subsequent Parent VO Changes (Doc ID 353443.1)

How To Make DFF Segments Read Only Using OAF Personalise (Doc ID 438215.1)

Oracle Application Framework: Allowing an Extended VO to See Subsequent Parent VO Changes (Doc ID 353443.1)


MOAC related notes:

Oracle Applications Multiple Organizations Access Control for Custom Code [ID 420787.1] --> Very Good document for developers.

SQL Queries and Multi-Org Architecture in Release 12 [ID 462383.1]

Multi Org Access Control (MOAC) in Oracle Purchasing [ID 397362.1]

FAQ - Multiple Organizations Architechure (Multi-Org) [ID 165042.1]


Localizations related notes:

Globalization Guide for Oracle Applications Release 12 (Doc ID 393861.1)

Country-Specific Features (Globalizations/Localizations) Guide (Doc ID 403211.1)

Oracle Applications 11i Internationalization Guide (Doc ID 333785.1) --> char set

Oracle E-Business Suite Release 12.1+ Information Center - Localizations [ID 885960.1]

Introduction to Add-On Localizations for R12 [ID 429042.1]


XML Publisher related notes:


XML Publisher Report Issues, Recommendations and Errors (Doc ID 862644.1)

R12: Troubleshooting Known XML Publisher and E-Business Suite (EBS) Integration Issues (Doc ID 1410160.1)

Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite [ID 364547.1]

Concurrent Processing and Post Processor related notes:

Unable to Find the Concurrent Request Output Post Processor (OPP) Service [ID 465036.1]

The Output Post Processor does not process all requests. [ID 1399463.1]
BI Publisher Requests in Pending Status End in Warning When Starting Concurrent Managers [ID 375208.1]

APIs and Integration repository:

Note: 462586.1 - Where are the Oracle® Release 12 (R12) API Reference Guide?


Note: 458225.1 - Release 12 Integration Repository


Note: 396116.1 - Oracle Integration Repository Documentation Resources Release 12


Audit Trail:

FAQ (Audit Trail) (Doc ID 107330.1)




AP (Oracle Payables):

Information Center: Using Oracle Payables (Doc ID 1417577.2)

AP: How To Determine Ap Invoice Approval Status Via The Backend? (Doc ID 220653.1)


11i & R12: AP: Where Is The Invoice Validation Status Stored? How Is The Invoice Validation Status Determined? (Doc ID 301806.1)


PO(Oracle Purchasing):

Attachments:

Note 338651.1: trouble shouting attachmetns and export

How to Query Attachments with SQL - Querying an Item Attachment? (Doc ID 370176.1)

Enable Attachments in a Form (Doc ID 369215.1)

How to enter images in the HRMS Application (Doc ID 103263.1)

How To Use Attachments In Oracle Applications? (Doc ID 197549.1)

Is There A File Size Limit For EBS Attachments (Doc ID 739643.1)

Misc Notes:

ICX related notes:

How To Handle Numeric Fields When Profile Icx: Numeric Character = 10.000,00 [ID 452839.1]

What is the setting and functionality of Profile Option ICX: Numeric characters? [ID 167513.1]

Report is missing data ICX Numeric Characters Profile option set to 10.000,00 [ID 858245.1]


Other Notes:

How to Determine Data Populated in the Reference Columns in GL,AR,AP Interface tables for AGIS Invoices [ID 853296.1]
Reports Exchange (RXi) Basics (Doc ID 119736.1)


AME:
How To Copy / Migrate AME Setup Like Rules/Attributes/Transactions etc From One Instance To Another Instance ? (Doc ID 371605.1)
How To Migrate AME Setups From One Instance To Another (Doc ID 1168883.1)

R12.1 Where can I find the latest eTRM information for 12.1.3 or 12.1.2? (Doc ID 1190603.1)

Oracle E-Business Suite Electronic Technical Reference Manual (eTRM), Release 12.1 and 12.2 (Doc ID 2736939.1)


Format number in BI report according to the ICX: Numeric Char profile option

Format number in BI report according to the ICX: Numeric Char profile option:

Its common in Oracle Apps UIs that the number and date formats are displayed according to the user preferences.


Often we need the number format preference be honoured in BI Publisher (XML Publisher) reports.


With the following we can achieve the same:

1) Set the profile 'ICX: Numeric characters' according to your need.
2) Set the profile XDO: Numeric characters to 'Read from ICX: Numeric characters'

When the above is set, the system passes the separators to xslt._XDONFSEPARATORS XDO parameter during runtime.


In your RTF for the number field - write the following code:

<?format-number:NUM_COLUMN;'999G999D99'?>

Where 'G' denotes thousands separtor and D denotes decimal separator.


During runtime, the BIP engine uses XSL-FO style sheet instead of RTF that was uploaded. 

As soon as you upload the RTF document and save you can see one more extra record in XDO_LOBS for the XSL:

We can see the XSL from the BIP add-in as well.


Open your RTF --> From Add-ins --> Tools --> export --> XSL-FO Style sheet.


You will something like this:


<xsl:value-of select="xdoxslt:xdo_format_number($_XDOXSLTCTX, .//NUM_COLUMN, '999G999D99')"/>



$_XDOXSLTCTX is made up of locale, timezone, calendar, numeric separtors etc..


You can refer metalink notes 760434.1,1355022.1

Wednesday 16 December 2015

ORA-00947: not enough values even when number of VALUES matches the insert

ORA-00947: not enough values even when number of VALUES matches the insert

I faced the issue "ORA-00947: not enough values even when number of VALUES matches the insert" - I checked the couple of sites but did not get any clue finally found that the issue is because of 'VALUES' clause with 'SELECT' statement..


Wrong:
insert into tabA(a,b,c) Values (Select 'a', 'b', 'c' from dual); 

Correct: - No Values clause
insert into tabA(a,b,c) 
(Select 'a', 'b', 'c' from dual);  

Tuesday 8 December 2015

Format Numbers as text so that the report output displays leading zeros.


Introduction:
Many times when working with reports customers use sequence numbers that often appended with zeros to the start of the number. When we use that in the report, the report output Excel or PDF, usually the Zero's disappears.

Example: 
Data in the table: 000000220513
Report output    : 220513


Steps:
To display the report output as 220513, the following options can be used.

1. Changes in RTF layout template.

Open the the BI Publisher properties for the field and check Force LTR option.

When you check this option you can see the following code in the Advanced tab or Form field help text field you can see following:

<fo:bidi-override direction="ltr" unicode-bidi="bidi-override"><?DOC_SEQ_NUM?></fo:bidi-override>

Alternatley you can write the above code for the field.


2. Change the SQL to output the column with quotes so that the character format preserves.

select '="' ||DOC_SEQ_NUM || '"'  from dual;

Script to copy parameters from one concurrent program to other


Input:
l_from_prog_short_name  => From Program short name
l_to_prog_short_name => To Program short name
l_to_prog_appl_short_name => To program application short name


Script:
declare
l_from_prog_short_name varchar2(240) := '<From Prog Name>';
l_to_prog_short_name varchar2(240) := '<to prog name>';
l_to_prog_appl_short_name varchar2(240) := '<to prog appl short name>';

cursor cp_from_program_parms
is
select
 params.column_seq_num sequence
,params.end_user_column_name parameter
,params.description
,params.enabled_flag enabled
,vs.flex_value_set_name value_set
,params.default_type
,params.default_value
,params.required_flag required
,params.security_enabled_flag enable_security
,params.range_code range
,params.display_flag display
,params.display_size
,params.maximum_description_len description_size
,params.concatenation_description_len concatenated_description_size
,params.form_left_prompt prompt
,params.srw_param token
,'N'    cd_parameter  --cp.cd_parameter
from FND_DESCR_FLEX_COL_USAGE_VL params, fnd_flex_value_sets vs
where 1=1
and descriptive_flexfield_name = '$SRS$.'||l_from_prog_short_name
and vs.flex_value_set_id=params.flex_value_set_id(+);
begin
for param_rec in cp_from_program_parms
 loop

  begin
  fnd_program.parameter(
program_short_name    =>  l_to_prog_short_name, -- program short name
application           =>  l_to_prog_appl_short_name, -- application short name
sequence              =>  param_rec.sequence,
  parameter             =>  param_rec.parameter,
--parameter             =>  param_rec.token,
description           =>  param_rec.description,
enabled              =>  param_rec.enabled,
value_set            =>  param_rec.value_set,
default_type           =>  param_rec.default_type,
default_value          =>  param_rec.default_value,
required                 =>  param_rec.required,
enable_security           =>  param_rec.enable_security,
range                      =>  param_rec.range,
display                   =>  param_rec.display,
display_size               =>  param_rec.display_size,
description_size          =>  param_rec.description_size,
concatenated_description_size =>  param_rec.concatenated_description_size,
prompt                       =>  param_rec.prompt,
  token                        =>  param_rec.token,
  --token                        =>  null,
cd_parameter                 =>  param_rec.cd_parameter);
  exception
   when others
    then
    dbms_output.put_line(param_rec.parameter);
    dbms_output.put_line(sqlerrm);
  end;

 end loop;
  --commit;
 dbms_output.put_line('Success');
exception
 when others then
  rollback;
  dbms_output.put_line(SQLERRM);
end;
/