PO Interfaces

PO_HEADERS_INTERFACE
is the interface table that imports header information from e– Commerce Gateway for blanket purchase orders and catalog quotations.
INTERFACE_HEADER_ID
BATCH_ID
INTERFACE_SOURCE_CODE

PO_LINES_INTERFACE
is the interface table that imports lines information from e– commerce Gateway for blanket purchase orders and catalog quotations.
INTERFACE_LINE_ID
INTERFACE_HEADER_ID
ACTION NULL Action to be completed: New or Add
GROUP_CODE (Null) Indicates the grouping of the requisition lines

PO_DISTRIBUTIONS_INTERFACE
is the interface table that imports distribution information from e– Commerce Gateway for blanket purchase orders and catalog quotations.
INTERFACE_HEADER_ID
INTERFACE_LINE_ID
INTERFACE_DISTRIBUTION_ID
ORG_ID

PO_REQUISITIONS_INTERFACE_ALL
contains requisition information from other applications. Import feature uses this information to create new requisition headers, lines and distributions.
TRANSACTION_ID (PK) Transaction unique identifier
PROCESS_FLAG NULL Transaction processing state

PO_REQ_DIST_INTERFACE_ALL
Is the interface table that creates multiple distributions using Requisition Import.
ACCRUAL_ACCOUNT_ID Unique identifier for the General Ledger accrual account
ALLOCATION_TYPE Specifies the method of allocation across distributions. Can be PERCENT.
ALLOCATION_VALUE Allocation split value
BATCH_ID Import batch identifier
BUDGET_ACCOUNT_ID Unique identifier for the General Ledger budget account
CHARGE_ACCOUNT_ID Unique identifier for the General Ledger charge account

RCV_HEADERS_INTERFACE
is the interface table that stores receiving header information.
HEADER_INTERFACE_ID Interface EDI header unique identifier
GROUP_ID NULL Interface group for set processing
EDI_CONTROL_NUM EDI transaction control number if data
is sent via EDI
PROCESSING_STATUS_CODE Processing status of the interface
header row
RECEIPT_SOURCE_CODE Source type of the shipment
ASN_TYPE NULL The document type: values are
ASN, ASBN, or RECEIVE
TRANSACTION_TYPE The transaction purpose code: values are
NEW, REPLACE, ADD,or CANCEL

RCV_LOTS_INTERFACE
Holds temporary lot number transaction records for a parent record in the RCV_TRANSACTIONS_INTERFACE table.

RCV_TRANSACTIONS_INTERFACE
stores information about receiving transactions that are waiting to be processed by the receiving transaction processor or were rejected due to an error when the transaction processor attempted to process the transaction.
TRANSACTION_TYPE
TRANSACTION_DATE
PROCESSING_STATUS_CODE

Interface Table
--PO_REQUISITION_INTERFACE_ALL
Program Name to Launch the PO Import program -Requisition Import program
In the first phase, the program validates your data and derives or defaults additional information. The program generates an error message for every validation that fails and creates a row
PO_REQUISITIONS_INTERFACE_ALL
It contains requisition information from other applications. Each row includes all the information necessary to create approved or unapproved requisitions in Oracle Purchasing.
The Oracle Purchasing Requisition Import feature uses this information to create new requisition headers, lines and distributions.

PO_REQUISITIONS_INTERFACE_ALL
table are identical to the corresponding columns in the
PO_REQUISITIONS_HEADERS_ALL,
PO_REQUISITION_LINES_ALL and PO_REQ_DISTRIBUTIONS_ALL
tables.

Po_requisition_interface_all
INTERFACE_SOURCE_CODE --VDP
,SOURCE_TYPE_CODE --INVENTORY
,DESTINATION_TYPE_CODE --EXPENSE
,AUTHORIZATION_STATUS --Status Always Approved we will get ..
,REQ_NUMBER_SEGMENT1 --Request id
,PREPARER_ID -- ASSOCIATE ID comes from VDP
,LINE_TYPE_ID
,LINE_TYPE --vArchar Requisition line type name
,QUANTITY --Quantity
,UNIT_PRICE
,CHARGE_ACCOUNT_ID -- to be hard coded based on the line type
,DESTINATION_ORGANIZATION_ID --v-org_id
,DELIVER_TO_LOCATION_ID -- location id
,DELIVER_TO_REQUESTOR_ID -- ASSOCIATE ID Same as Prepare_id
,ITEM_ID -- item code
,ITEM_DESCRIPTION --Based on the item code description is taken
,CATEGORY_ID
,UOM_CODE
,CURRENCY_CODE --if this is supplied then next two should be filled
,RATE
,RATE_DATE
,RATE_TYPE
If you use Oracle Master Scheduling/MRP or a non– Oracle MRP system with Oracle Purchasing, you may find that you need to reschedule requisitions as your planning requirements change.

Reschedule Interface Table Since you have already loaded your requisitions into Oracle Purchasing, you simply need to identify for Oracle Purchasing the requisition lines you want to reschedule. After you identify each line to reschedule, you can update the quantity and the need– by date for the corresponding requisition line.
PO_RESCHEDULE_INTERFACE table for each change you want to make to a requisition. Each row includes the requisition line identifier, the new quantity, and the new need– by date for the requisition line. You run the Requisition Reschedule program to implement the changes. Import Requisitions from the External System to Oracle Purchasing Write a Import Program to load the external data Dump data into the some interface table .Validate the data through some PL/SQL
(Applying Business Logic---
Run Import Program
Requisition is imported and created as many
number of requisition as successful records .Others -if error then run exceptional report to see the reason of failure.

Inventory and PO Interface Tables

Inventory Interfaces
Open Item Interface
Interface Table:
MTL_SYSTEM_ITEM_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE
MTL_ITEM_CATEGORY_INTERFACE
MTL_INTERFACE_ERRORS

Base Table:
MTL_SYSTEM_ITEMS_B
MTL_ITEM_REVISIONS
MTL_ITEM_CATEGORIES

Open Transaction Interface
MTL_TRANSACTIONS_INTERFACE
MTL_TRANSACTION_LOTS_INTERFACE
MTL_SERIAL_NUMBERS_INTERFACE
MTL_INTERFACE_ERRORS

Base Tables
MTL_MATERIAL_TRANSACTIONS
MTL_TRANSACTION_LOT_NUMBERS
MTL_SERIAL_NUMBERS

PO Interfaces
Requistion
PO_REQUISITIONS_INTERFACE_ALL
table are identical to the corresponding columns in the
PO_REQUISITIONS_HEADERS_ALL,
PO_REQUISITION_LINES_ALL and PO_REQ_DISTRIBUTIONS_ALL
tables.

Receiving
RCV_HEADERS_INTERFACE
RCV_LOTS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
Tables:
RCV_SHIPMENT_HEADERS
RCT_SHIPMENT_LINES
RCV_TRANSACTIONS

Forms Customization

What is custom development?
Custom development is new development, In order to provide new functionality , which is not available in Oracle Application, we are going for custom development.
What is customization?
Customization is not a new development. The existing form will be modified as per our requirement. This may be cosmetic change or navigation change or functionality change.
Compare Custom development & customization. When they are used and Why?
Custom development.
a. New development
b. Template form has to use
c. The required functionality is not provided by oracle in that case we have to go for custom development.
Customization.
a. Tailoring the existing application
b. Same source file has to use
c. The existing functionality is not fully satisfy our requirement, Then we are going for customization.
What are step you have to follow to register a custom application?
1. Register your Application
2. Create directory structure
3. Set the Environment variable for directory
4. Create the schema
5. Attach your application & Schema with standard data group
6. Create the table, views, and trigger in your schema.
7. Create synonym for table to APPS schema
8. Built the form
9. Register the form
10. Create form function
11. Create the menu
12. Attach the menu to the responsibility
13. Attach the responsibility to the user
How do you find out the FMB name?
Select menu bar Help menu of the form, then select About Oracle Application menu, that will show the FMB of the form.
Name the directory having the FORMS source codes ( FMB files ) ?
AU_TOP forms directory.
What is template form?
Template form is a form, which have standard functionality of the oracle application, like menu bar, tool bar action and some standard trigger. All forms in oracle application will be developed using this form, To get standard appearance oracle application provide this form.
What are step you have to follow to register a Form?
Create the function.
Attach the function to a form function
Attach the form function to menu.
What is a Form function?
Form function is nothing but form. Oracle Apps treats all the forms as function.
What is Form sub function?
Sub function is a non-form function. Sub function will created based on form function. By using this we can restrict functionality of the form.
How the form sub function is implemented?
By using parameter and profiles.
What is folder form?
Folder form is a special form, here the user allow changing the appearance of the form as he/she like. The user can rearrange the fields, resize the fields. This changes will be permanent belongs to the user.
Name the directories where you have to copy your Fmb and Fmx files?
All FMB files will be coped in AU_TOP form directory. FMX will be copied to corresponding Prod_Top form directory.
e.x all GL forms fmx will be coped in GL_Top form directory.
Why we have to maintain the file names in Capital Letter? ( Library/FMB)
Some of operation system will have case sensitivity, those OS may not able to get the correct file, for avoiding case sensitivity problem we have to maintain the file name in UPPER case.
What is naming convention for Data base trigger?
Tablename_Ti. ( “i” = 1,2,3…..)
What is naming convention for unique Constraint?
Tablename_Ui (“i” = 1,2,3….)
What is naming convention for Primary Constraint?
Tablename_PK
Can we put all the logic in the trigger?
No, Create a package, put all the logic in package. Call the package from the trigger.
What is item handler package?
Item handler package is a package. This package will take care of the item validation, navigation. Each block can have one package with the name of block name.
What is event handler package?
Event handler package is a package. This package will take care of the various event of the form, like post query, pre query, when new record instance etc. Each form has event handler package with the name of form name.
What is table handler package?
Table handler package is a package. This package will take care of the insert, update and delete operation of view-based block. Each form can have one package with the name of form name.
What are the standard libraries available in template form?
1.APPCORE, 2. APPDAYPK, 3. FNDSQF , 4.CUSTOM
What is who column and how can you set the values?
Who columns are database columns, which gives the history of the record. ( it will gives created user name with date and last modified user name with date of the record).
By using fnd_standard.set_who procedure we can set the value.
What is use of custom library?
By using this library we have to do cosmetic and navigation change in form customization.
How can you change the default menu bar action?
By using APPCORE library
What is use of APPDAYPK library?
By using this library you can change the functionality of menu action and tool bar actions, and you can add custom help files in the application.
What is a reference trigger? Can we modify a reference trigger?
Reference trigger is a trigger, definition of the trigger will be in some other file.
We can, But Oracle Application advise against modifying the reference trigger. Because this change will affect the whole application.
Why we have to create packages instead of procedure / function?
If we create procedure/function, this will be compiled every call of the procedure/function, But if you create package it will not complied every call, It will increase performance of the application.
Can you comment your form? How?
Yes.
You can give comment of the from in Form module “comment window”.
By using FND_Standard.Form_info procedure you can comment your form, this is in Pre_Form trigger.
Which form objects we should not use?
1. Activex, Vbx, Ocx, Ole
2. Timer
3. Mouse Trigger
4. Open_Form
5. Combo Box
6. Test_io, Host built-in
What is use of APPDAYPK library?
By using this library you can display calendar window in date field LOV.
What is use of FNDSQF library?
This library will tack care of concurrent program, profile options and flex filed behavior.
Can we change the profile value? How?
Yes.
By using FNDSQF library we can change the profile values.
Shall we modify all the triggers?
No, we should not do any modification in certain form level trigger.
What are the triggers we should not modify?
1. Close_this_window.
2. Close_window
3. Export
4. Folder_Action
5. Key-Commit
6. Key-Edit
7. Key-Exit
8. Key-Help
9. Lastrecord
10. Menu_to­_Appcore
11. Standard_Attachment
12. When_window_closed
13. When_form_navigate
14. Zoom
Shall we delete exiting triggers?
We should not delete any form level trigger. But Oracle application not encouraging deletion of any trigger.