PURCHASING - Setup Buyer in Oracle APPS R12

1)  Login to Purchasing Super User Responsibility

Navigation : Setup -> Personnel -> Buyers

2) Search for user name to be added as Buyer and save changes 

Enable Diagnostics Menu in Oracle Apps R12 FORMs

 Steps to enable Diagnostics menu in Oracle APPS Form

Step1: Set FND: Diagnostics profile option Yes

Step2: Set "Hide Diagnostics menu entry" profile option value to No

Logout of the application and login again

SQL Developer Connect Error - ORA-00604: SQL level 1 ORA-12705: Cannot access NLS data files or invalid environment specified

When using SQL Developer we will sometime get following error if our computer default language is settings don't go well with Oracle SQL Developer.

While connecting to database from the SQL Developer fails with the following error:

ORA-00604: error occurred at recursive SQL level 1 ORA-12705: Cannot access NLS data files or invalid environment specified

How to fix this?

Find sqldeveloper.conf file: under SQLDeveloper Home / Bin directory. 

Edit config file to add below options and save. 

AddVMOption -Duser.language=en

AddVMOption -Duser.country=US

Restart SQL Developer and try connection again.

Oracle EBS R12 FNDLOAD Commands Example

 FNDLOAD Commands:

1) Concurrent Program Download:

FNDLOAD apps/<<AppsPassword>> O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct <<XX_LDT_FILE_NAME>>.ldt PROGRAM APPLICATION_SHORT_NAME="<<XXCUSTAPP>>" CONCURRENT_PROGRAM_NAME="<<CONC_PROG_SHORT_NAME>>"

2) Concurrent Program Upload:

FNDLOAD apps/<<apps password>> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct <<XX_LDT_FILE_NAME>>.ldt -WARNING=YES UPLOAD_MODE=REPLACE -CUSTOM_MODE=FORCE 

3) Request SET Download

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <<XX_LDT_FILE_NAME>>.ldt REQ_SET REQUEST_SET_NAME='<<REQSET_INTERNAL_NAME>>'

3) Request Set Links Download:

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <<XX_LDT_FILE_NAME>>.ldt REQ_SET_LINKS REQUEST_SET_NAME='<<REQSET_INTERNAL_NAME>>'

4) Alert Download:

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct <<XX_LDT_FILE_NAME>>.ldt ALR_ALERTS APPLICATION_SHORT_NAME="<<XXCUSTAPP>>" ALERT_NAME="<<Alert Display Name>>"

5) Message Download

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct <<XX_LDT_FILE_NAME>>.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME="<<XXCUSTAPP>>" MESSAGE_NAME="<<MESSAGE_NAME>>"

6) Concurrent Program Assignment to Request Group Download

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct <<XX_LDT_FILE_NAME>>.ldt REQUEST_GROUP REQUEST_GROUP_NAME="<<REQUEST_GROUP_NAME>>" APPLICATION_SHORT_NAME="<<REQ_GROUP_APPLICATION>>" UNIT_NAME="<<CONC_PROG_SHORT_NAME>>" 

7) Concurrent Program Assignment to Request Group Upload

FNDLOAD apps/<<AppsPassword>> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct <<XX_LDT_FILE_NAME>>.ldt

8) Value Set Download

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <<XX_LDT_FILE_NAME>>.ldt VALUE_SET FLEX_VALUE_SET_NAME="<<VALUE_SET_NAME>>"

9) Value Set Upload

FNDLOAD apps/<<apps_password>> 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct <<XX_LDT_FILE_NAME>>.ldt - WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE 

10) DFF Download

FNDLOAD apps/<<AppsPassword>> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <<XX_LDT_FILE_NAME>>.ldt DESC_FLEX APPLICATION_SHORT_NAME=<<APPLICATION_SHORT_NAME>> DESCRIPTIVE_FLEXFIELD_NAME='<<DFF_NAME_INTERNAL>>' 

11) DFF Upload

FNDLOAD apps/<<AppsPassword>> 0 Y UPLOAD $FND_TOP/patch/115/import/ afffload.lct  <<XX_LDT_FILE_NAME>>.ldt -WARNING=YES UPLOAD_MODE=REPLACE -CUSTOM_MODE=FORCE

12) System Profile Download
-- ---------
FNDLOAD apps/<<AppsPassword>>O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct XX_CUSTOM_PRF.ldt PROFILE PROFILE_NAME="XX_PROFILE_NAME" APPLICATION_SHORT_NAME="XXCUST"

13) System Profile Upload

FNDLOAD apps/<<AppsPassword>>0 Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct XX_CUSTOM_PRF.ldt - WARNING=YES UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

14) Form Download

FNDLOAD apps/<<AppsPassword>> O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt> FORM APPLICATION_SHORT_NAME=”CUST” FORM_NAME=”CUSTFRMNAME”

15) Form Upload

FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt>

16) Function Download

FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt>  FUNCTION FUNC_APP_SHORT_NAME=”CUST” FUNCTION_NAME=”CUSTFUNNAME”

17) Function Upload

FNDLOAD apps/<apps_pass>O Y UPLOAD $FND_TOP:patch/115/import/afsload.lct <file_name.ldt>

18) Menu Download

FNDLOAD apps/<apps_pass>O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <file_name.ldt>   MENU MENU_NAME=”CUSTMENUNAME”

19) Menu Upload 

FNDLOAD apps/<apps_pass>0 Y UPLOAD $FND_TOP/115/import/afsload.lct <file_name.ldt>

Steps to generate concurrent program trace file

Steps to generate trace file for concurrent job and  locate it on server:
1. Login applications user with System Administrator responsibility
2. Go to -> System Administrator -> Concurrent : Program -> Define and Press F11
3. Enter the Concurrent Program Name (Eg. Journal Import) -> Press Ctrl + F11
4. Enable the check box "Enable Trace" above "Copy To" button. Click on Save and close the window.
5. Select Requests -> Run->Submit the concurrent request for which you enabled trace
6. The trace file will be created in the Database Server under the location of "udump"
sql>select value from v$parameter where name like '%user_dump_dest%';

Setup steps for Drop Shipments in Oracle EBS

 

Oracle Order Entry and Oracle Purchasing integrate to provide drop shipments. Drop shipments are orders for items that your supplier ships directly to the customer either because you don't stock or currently have the items in inventory, or because it's more cost-effective for the supplier to ship the item to the customer directly

SETUP

A) Associate drop shipments with a receiving location.
B) Drop shipments support a Destination Type of Expense or Inventory only.
C) We can handle returns of drop shipments using standard Order Entry/Shipping or Purchasing functionality. There are different ways you may want to handle returns depending on whether the customer returned the item to you or directly to the supplier.

We have to consider the following setup:

1- Inventory Setup 

Inventory Setup : (Define and Maintain The Item)
The drop ship inventory organization, item and subinventory must be setup prior to creating any drop ship orders. All drop ship subinventory must have the Reservable box checked.
Below are list of the required item attributes for a drop ship item. All of these attributes MUST be enabled unless otherwise specified.

Inventory Attributes: Inventory Item , Stockable, Transactable, Reservable
Purchasing Attributes: Purchased, Purchaseable
Costing Attributes: Costing Enabled – this should only be checked for items that are cost enabled, Inventory Asset Value – this should only be checked for asset items (non-expense items)
Receiving Attributes: Receipt Routing set to Direct – this is not required, but preferred since it makes receiving process one step versus two or three
Order Management Attributes: Customer Ordered, Customer Orders Enabled, OE Transactable
As a Troubleshooting tips on creating a drop ship item and subinventory:

•  Make sure the subinventory is Reservable.If the subinventory is not Reservable, the sales order issue transaction will not be created in MTL_TRANSACTIONS_INTERFACE.
•  Make sure the item has the above mentioned item attributes in the drop ship organization. If the above item attributes are not set, problems will arise in various places during the drop ship transaction process.

2- OM Setup

• Make sure the sales order line Source Type is External. If the source type is not External, workflow will not distinguish the line as being a drop shipment and will not insert any data into the purchasing module’s requisitions interface. 
• For customer, enter internal ship to location.
• Customer must have a valid ship-to and bill-to locations. 
•  Make sure that either the schedule ship date or request date is populated.If both of these are null, the requisition will not be imported into the purchasing module’s requisitions interface. 
•  Make sure there are no holds against the line. If there is a hold, the hold must be removed and then the order can be progressed or the line must be manually purchased release.
  Verify in HR, that the employee has an active status and has not been terminated.

For more details metalink
Note 99888.1: Drop Shipments – Setup
Note:99886.1 : Drop Shipments – FAQ
Note:99889.1 : Drop Shipments - Troubleshooting

3- PO Setup

• Make sure the Import Source parameter list of values contains ORDER ENTRY.
  If ORDER ENTRY appears in the Import Source parameter list of values, then it means that the Workflow Background Processor successfully inserted a requisition into PO_REQUISITIONS_INTERFACE_ALL. If ORDER ENTRY is not visible in the Import Source parameter list of values, then no rows were inserted into the table. Review the setup under Order Management. 
• User should be setup as a valid PO Buyer.
•  Make sure the Group By parameter is actually set the user wants the requisitions grouped.

---

Query : Find Request Group name for Concurrent program name

Very useful query to retreive the Request Group and other information for Concurrent program from its name :
 
SELECT cpt.user_concurrent_program_name     "Concurrent Program Name",
       DECODE(rgu.request_unit_type,
              'P', 'Program',
              'S', 'Set',
              rgu.request_unit_type)        "Unit Type",
       cp.concurrent_program_name           "Concurrent Program Short Name",
       rg.application_id                    "Application ID",
       rg.request_group_name                "Request Group Name",
       fat.application_name                 "Application Name",
       fa.application_short_name            "Application Short Name",
       fa.basepath                          "Basepath"
         FROM fnd_request_groups          rg,
       fnd_request_group_units     rgu,
       fnd_concurrent_programs     cp,
       fnd_concurrent_programs_tl  cpt,
       fnd_application             fa,
       fnd_application_tl          fat
 WHERE rg.request_group_id       =  rgu.request_group_id
   AND rgu.request_unit_id       =  cp.concurrent_program_id
   AND cp.concurrent_program_id  =  cpt.concurrent_program_id
   AND rg.application_id         =  fat.application_id
   AND fa.application_id         =  fat.application_id
   AND cpt.language              =  USERENV('LANG')
   AND fat.language              =  USERENV('LANG')
   AND cpt.user_concurrent_program_name like 'Your CP Name';

गारपीट

                                                ।। गारपीट ।।                             


आल्या पावसाच्या धारा,
सरा  मांडला पसारा,
उभं पिक रानामधी,
गेल्या  नासवून गारा. 

झाला   फुलाले अघात,
समधि गळाली रे पानं
पाणी पाणी चोहीकडे 
तरी जळाली रे मनं 

                                                       काही माणूस भी गेले 
                                                       काही तुटले छप्पर 
                                                       कुठे जीवाच्या भयाने 
                                                       पार हंबरती गुर 

                                                       कुठे गहू कुठे कांदा  
                                                       कुठे दाळिंब अंगूर 
                                                       कुठे गळा लागे फास 
                                                       खेळ नियतीचा क्रूर 

ऐक माझ्या देवा 
माझं एकच गाऱ्हाणे 
इडा पिडा हि जाऊदे 
एवढ  एकच मागणे 

नको हिरे मोती 
हवी कष्टाची पावती 
सुखी ठेव बळीराजा 
सुखी ठेव काळी माती …. 

                                    --अविनाश 

मनाचे मनाशी पटेना कुणाशी
कुणाला कळेना हि चूक! कुणाची

मुकी भावना हि डोळ्यात पाणी
मुक्या आसवांची मुकी हि कहाणी
मुक्यानेच बोलू मुक्या साजानाशी
मनाचे मनाशी ….

जुनी भेट आपली नव्याने आठवते
पुन्हा भेटीसाठी नवी सांज झुरते
का ऐकू येत नाही साद तुझ्या कांकनाची
मनाचे मनाशी ….


                                         -- अविनाश

Oracle APPS Create Responsibility and User in Oracle EBS

How to create Responsibility and User in Oracle EBS

How to Create a Responsibility?

Step 1: Connect to Oracle Application with APPSADMIN/APPSADMIN User.

Step 2: Go to Application Administrator.

Step 3: Go to Security then Responsibility then Define

Step 4: Enter the Data in the opened Window.

Note: Above Information of Responsibility is stored in FND_RESPONSIBILITY Table.

How to Create a User?

Step 1: Connect to Oracle Application with APPSADMIN/APPSADMIN User.

Step 2: Go to Application Administrator.

Step 3: Go to Security then User then Define

Step 4: Enter the Data in the opened Window.

Note: Above Information of User is stored in FND_USER Table.

User Responsibilities stored in FND_USER_RESP_GROUPS Table.

Use of Who Columns in Oracle APPS table

Oracle APPS : WHO COLUMNS

WHO columns are used to track the information updated or inserted by the users against the tables. FND_STANDARD package is used for this purpose. FND_STANDARD.SET_WHO Procedure is used to update the WHO columns in a Table when a DML operation s (i.e. INSERT, UPDATE) performed.

Steps required to Track WHO Information in our form

  1. ALTER the table by adding WHO columns in the table.
  2. Open TEMPLATE.fmb in form Builder.
  3. Perform all the pre‐requisites to develop a form.
  4. Include all the WHO columns in the Data Block with NULL Canvas.
  5. Call FND_STAND.SET_WHO procedure in Pre‐Insert and Pre‐Update triggers
      at Block Level.
  6. Save and Compile the Form.
  7. Perform all the pre‐requisites to register the form

Note: 1. WHO Columns need not register with the table registration option.
          2. Table registration will be done only for KFF and DFF columns.
          3. For Form development table registrations not required.

To Show the Module Form Directory Path
1. In PRE‐FORM Trigger change the module name from FND to specific module
short name (i.e. EX, INC, PPR, etc.,).

2. Save and Compile the form.

Debug OAF Page

How to Debug OAF Page

We can enable logging by setting the below profile option:-

Option: 1)
• FND: Debug Log Enabled profile set to ‘Yes’
• Turn on low level statement logging for a single user to monitor
• FND: Debug Log Level= Statement



Option: 1)
Another way of gathering the same info is the following:

1)  Enable profile option FND: Diagnostics 
2)  Add following at the end of existing page URL,   &aflog_level=Statement&aflog_module=*

• Use '*' for wildcard, not '%'. '%' is a special URL character)

Example:
• http://host:port/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE&aflog_level=STATEMENT&aflog_module=pa

You can see the log on screen by using by below code in your controller OR in Application ModuleImpl

For AM

getOADBTransaction().writeDiagnostics(this, "I am in the Application Module", 1);

For Controller

 pageContext.writeDiagnostics(this, "I am in Controller PFR", 1);

राजकुमार

                      ।।   राजकुमार  ।।

सुंदर रातीला
सुंदर पहाटे 
सुंदर झाली सकाळ ,

सुंदर राज्यात
सुंदर राजाचा
सुंदर राजकुमार .

                                        अल्लड वाऱ्याची
                                        अल्लड झुळुक
                                        अल्लड ही सायंकाळ,

                                        अल्लड चालणे
                                        अल्लड बोलणे
                                        अल्लड त्याचा रुबाब.

रंगीत फुलाची 
रंगीत पाकळी
रंगीत आला सुवास,

रंगीत मनात 
रंगीत विचार
रंगीत त्याचा अभास.
                           
                                      भन्नाट गाण्याच
                                      भन्नाट संगीत
                                      भन्नाट सूर ताल,

                                      भन्नाट देशात
                                      भन्नाट राणीचा
                                      भन्नाट राजकुमार…।


                                                                      --अविनाश काळे

 

Use CUSTOM.pll for forms customization

What is the CUSTOM Library

- Standard oracle liabrary supplied with Oracle Applications

- Allows customer to enhance standard functionality of the oracle Applications

- Every forms based screen will access CUSTOM.pll

- Ideal point to create business rule which affects entire organization

- This is the Only method supported by Oracle for Oracle Applicaitons enhancements

How to Use the CUSTOM Library

Since the CUSTOM library is a typical Forms PL/SQL library, it can include standard PL/SQL logic, Oracle Forms

built-in commands and may have other Forms PL/SQL libraries attached to it. The base CUSTOM library is located

in the $AU_TOP/resource directory on your forms server.

Explore the CUSTOM.pll using the Oracle Forms Designer module to examine the sample code that exists in library. Once any enhancements are made, the library must be generated into an executable library (CUSTOM.plx) that then can be used by the Oracle Applications Forms runtime module. Since the CUSTOM library is loaded once for a given session, a user must log out of the application and sign-on again before any changes will become apparent. It is suggested that you also place a copy of the CUSTOM library in your customization directory as a safety precaution.

Since the CUSTOM library’s standard location is in the $AU_TOP/resource, it can be

overwritten during an upgrade of the Applications. Once enhancements are implemented, the CUSTOM library is accessed by the Oracle Applications based upon ‘events’. The ‘events’ define the occasions when the Applications will look into the CUSTOM library for additional code to execute.

Some events are generic:

        WHEN-NEW-FORM-INSTANCE – initially entering a form

        WHEN-NEW-BLOCK-INSTANCE – entering a zone (or block) within a form

        WHEN-NEW-ITEM-INSTANCE – moving into a new field within the form

        WHEN-NEW-RECORD-INSTANCE - creating a new record

        WHEN-FORM-NAVIGATE – navigating thru a form using the mouse

        WHEN-VALIDATE-RECORD – saving (committing) the information to the database

        EXPORT – triggered by using the Export feature

Some events are field specific

        ZOOM – Pre -11 feature for moving to another form and querying up specific records

Some events are form specific

       SPECIALn - (where n is a number between 1 and 45) used to generate entries in the ‘Special’ menu of the

                         tool bar and the code is triggered by selecting a menu choices from the ‘Special’ option on the toolbar

       KEY-Fn – (where n is a number between 1 and 8) triggered by pressing the corresponding function key

Some events are application specific:

       Application Object Library

           WHEN-LOGIN-CHANGED – when a user logs on as a different user

           WHEN-RESPONSIBILITY-CHANGED – when a user changes responsibilities

           WHEN-PASSWORD-CHANGED – when a user changes their password