Hi,

Customers should document their customization. As per the Oracle E-Business Suite Developer's Guide, "To reduce the risk that your custom application short name could conflict with a future Oracle E-Business Suite short name, we recommend that your custom application short name begins with "XX"."

You can get the Application ID from FND_APPLICATION_TL and/or FND_APPLICATION. The concurrent program will be listed in fnd_concurrent_programs_tl and fnd_concurrent_programs.

If you are following Oracle's recommendation to uses "XX" as the start of your application name, you can determine which Applications are custom:
select application_id from FND_APPLICATION where application_short_name like 'XX%';
or
select application_id from FND_APPLICATION_TL where application_name like 'XX%';

For example if the above returns application_id = 1111, then you can query either the fnd_concurrent_programs_tl or fnd_concurrent_programs tables for the program names:
select user_concurrent_program_name from fnd_concurrent_programs_tl where application_id = 1111;
or
select concurrent_program_name from fnd_concurrent_programs where application_id = 1111;

Otherwise if you are not using a custom application, then you would need to determine who has the ability to create custom programs and query by their user ID from the created by column, for example:

select user_id from fnd_user where user_name = 'MYUSERNAME';
1111

select user_concurrent_program_name from fnd_concurrent_programs_tl where created_by = 1111;
or
select concurrent_program_name from fnd_concurrent_programs where created_by = 1111;

or

SELECT
xrd.report_name AS "Report Name",
xrd.report_description AS "Report Description",
xrd.report_type AS "Report Type",
xrd.report_id AS "Report ID",
fa.segment1 AS "Application Short Name",
xrd.template_type AS "Template Type"
FROM
xml_report_definitions xrd
JOIN
fnd_application fa ON xrd.application_id = fa.application_id
WHERE
xrd.report_name LIKE 'XX%' -- Custom XML reports often start with 'XX'
ORDER BY
xrd.report_name;

Hope this helps.

Regards,
Sadeesh

General data flow from PO to AP, project specific info after:

The PO has a match option to indicate whether AP invoices will be matched to the purchase order or to a receipt against the purchase order. It also has an option for whether to pay on receipt. A PO that pays on receipt will have the match option set to receipt.

When you create an AP invoice and the PO is set to match to a receipt, it will require you to select a receipt (select the po, line, shipment, receipt or click on the Match button to query/select the receipt). The invoice distribution will have the rcv transaction id of the receipt it matched to and may have the po distribution id. You can use the receipt transaction id or the po distribution id to link the invoice to the PO. This is called 3 way matching since the invoice, PO, and receipt are all involved. If a PO is set to pay on receipt and you enter a manual invoice, there will be a message to warn you overbilling is possible.

If the PO is set to pay on receipt, then instead of creating a manual invoice you will run the ERS Pay on Receipt Auto Invoice concurrent program, which will read the receipts and generate an AP invoice using the quantity from the receipt and the unit price from the PO. It is a two-step process, the Pay on Receipt Auto Invoice puts data in the AP interface and then it automatically launches Payable Open Interface Import to read the interface and create the invoices. This invoice will also have the rcv transaction id on the AP invoice distribution. The invoice will have a source of ERS to indicate it was generated. ERS invoices don't experience invoice price variance since the price is taken from the PO.

If the PO is set to match to the PO, then when you create the invoice you cannot select a specific receipt even if a receipt exists. In cases such as utility bills or services where there will be no receipt, you will also match to the PO.

Data flow from PO to AP specific to Projects,

If the po distribution's destination type code is EXPENSE, then the project, task, expenditure organization, and expenditure type from the po distribution will be copied to the AP invoice distribution. The AP invoice distribution has a pa addition flag that indicates if it has gone to Projects or not; it starts as N and changes to Y if it is interfaced, Z if its net zero, E if its not intended to go, etc.

If the po distribution's destination type code is INVENTORY or SHOP FLOOR, then the project, task, expenditure type, expenditure item date, expenditure organization fields won't be on the AP invoice distribution, but can be found by using the AP invoice distribution's po distribution id and/or rcv transaction id to link back to the PO or receipt.