How to remove bursting control file

Upon attaching a bursting control file to a data definition to test the functionality. Now there is no option to get rid of it, unfortunately there is no delete button or anything similar in XML Publisher Administrator. How can I delete the file?

Solution:

There is no option to set any inactive_date or delete the file on the whole. But you can, if you have access to the database the following option, to vanish the file:

DELETE
FROM XDO_LOBS
WHERE LOB_CODE=<DATA_DEFINITION_CODE>
AND LOB_TYPE='BURSTING_FILE';

How To Re Compile A Concurrent Program Parameter Descriptive Flexfield ( DFF)

Issue: The descriptive flexfield with application name XX(XX) and name $SRS$.XX ($SRS$.XX) is not compiled. Please contact your system administrator"

Solution:

We can retrieve and check the flexfield context definition by running the following SQL statement:

select *
from FND_DESCR_FLEX_CONTEXTS_VL
where descriptive_flexfield_name like '%IBY_FC_CREATE_SETTLE_BATCHES%'

To compile the parameter flexfield use the following steps:

1. System Administrator > Concurrent Request > Program > retrieve the concurrent program (e.g.XXABC_Report).

2. Click Parameters button.

3. Update description of one parameter e.g. add XX to description of P_CONC_PROGRAM_NAME parameter for example: Concurrent Program Name XX

4. This will trigger compilation of this DFF (internally it will run a PL/SQL package, not a concurrent request).

5. If you want the original description to remain, revert back the changes in step 3 and save.  This will force another recompilation and description will remain as seeded.

6. Test again the concurrent program.  It should not fail this time.

How to Prevent Users From Submitting Blank Timecard

The seeded functionality allows blank timecards to be successfully submitted where the attributes (Project, Task and Expenditure Type) and also the hours are NULL.

To prevent a blank timecard from being submitted by users, you can implement a time entry rule using seeded fast formula 'Period Hours vs Time Category ( Seeded formula)'.

Steps for creating the time entry rule:
- Create a time entry rule with formula 'Period Hours vs Time Category ( Seeded formula )'.  Formula Inputs:
   Period: <user's timecard period>
   Period Hours: 0
   Operator: Equal To
   Time Category: Project Processing Fields
- Create a time entry rule group which includes this time entry rule.  Choose your desired outcome.
- Assign this time entry rule group to employees via OTL preference 'Time Store Time Entry Rules'
- Retest by trying to submit a blank timecard.

OTL: How to prevent users from submitting timecards in OTL without Project info

Create a new Time Entry Rule to ensure that Projects Timecard fields are always required: 

Navigate to OTL Application Developer > Time Entry Rules > Define Time Entry Rules
Create a new Time Entry Rule with the following values:
Usage: choose the type proper for you (e.g Submission / Resubmission)
Formula: Mandatory timecard fields (Seeded Formula)
Formula Inputs: Projects Processing Fields
From: (e.g 01-Jan-1951)
Save it.


Go to Time Entry Rules > Define Time Entry Rule Groups
Create a new Time Entry Rule Group and choose the Time Entry Rule you just created, outcome: Error
Save it.

Go to Preferences
Add "Time Store Time Entry Rules" Preference to your main node and pick the Time Entry Rule Group you just created.
Save it.

If you want to make individual fields on the Project timecard to be Mandatory then you need to create a time category for each field and reference that time category in a separate Time Entry Rule that uses " Mandatory timecard fields (Seeded Formula)".

Unable to Void Payment

Check these 2 queries.

Query #1:

SELECT SUM(NVL(aid.amount,0))
FROM ap_invoice_payments_all aip,
ap_invoices_all ai,
ap_invoice_distributions_all aid,
ap_invoice_distributions_all aid2
WHERE aip.check_id = &CHECK_ID
AND ai.invoice_id = aip.invoice_id
AND ai.invoice_type_lookup_code = 'PREPAYMENT'
AND ai.invoice_id = aid2.invoice_id
AND aid2.line_type_lookup_code = 'ITEM'
AND aid.prepay_distribution_id = aid2.invoice_distribution_id;

-> If amount returned <> 0 then it means that prepayment has not been unapplied completely.Solution would be to unapply the prepayment and account that event.

Query #2:

SELECT aid.* FROM ap_invoice_distributions_all aid_prepay,
ap_invoice_payments_all aip,
ap_invoices_all ai_prepay,
ap_invoice_distributions_all aid,
ap_invoice_distributions_all aidp
WHERE aip.check_id = &CHECK_ID
AND aip.invoice_id = ai_prepay.invoice_id
AND ai_prepay.invoice_type_lookup_code = 'PREPAYMENT'
AND aid_prepay.invoice_id = ai_prepay.invoice_id
AND aid_prepay.invoice_distribution_id = aid.prepay_distribution_id
AND aid.prepay_distribution_id IS NOT NULL
AND aid.parent_reversal_id IS NOT NULL
AND aid.amount > 0AND nvl(aid.posted_flag, 'N') = 'N'
AND aid.invoice_id = aidp.invoice_id
AND aid.invoice_line_number = aidp.invoice_line_number
AND aid.parent_reversal_id = aidp.invoice_distribution_id
AND aid.prepay_distribution_id = aidp.prepay_distribution_id
AND nvl(aidp.posted_flag, 'N') = 'Y';

-> If this query returns data that means Prepayment unapplication event on the invoice has not been accounted.Solution is to make sure the standard invoice, on which the Prepayment is applied, has been validated and create new accounting.

How to Distribute Expenditure Cost

In PA_EXPENDITURE_ITEMS_ALL table,

If system_linkage_function(OT & ST) is "Timecards" then run "PRC: Distribute Labor Costs" program to distribute the cost.

If system_linkage_function(USG, INV, WIP & PJ) is "Usages or Inventory or Work In Process or Miscellaneous Transactions" then run "PRC: Distribute Usage and Miscellaneous Costs" program to distribute the cost.

If system_linkage_function(VI & ER) is "Supplier Invoices or Expense Reports" then run "PRC: Distribute Supplier Cost Adjustments" program to distribute the cost.

If system_linkage_function(BTC) is "Burden Transactions" then run "PRC: Create and Distribute Burden Transactions" program to distribute the cost. 

PA_NO_PROJFUNC_CURR_RATE - Project Functional Currency Error

PRC: Distribute Misc and Usage Costs has the following error:

Error: PA_NO_PROJFUNC_CURR_RATE

Complete the below setup to resolve the error.

• Go to Implementation Options Screen-> Currency Tab and verify the setup what is the date and type.
• Go to Expenditure Inquiry screen and query the problematic Lines.
• Click on Show Field and Add the Following Fields
• Transaction Currency
• Project Currency
• Project Functional Currency.
• Expenditure Item Date ( If in Implementation Options form expenditure date is setup to be considered, else the corresponding field based on the setup in Implementation form)
• Note Down All the Above Values
• Go to GL Responsibility --> Setup --> Currency-->Rates-->Daily.
• Make sure that a rate exist for the following combination.
• Transaction Currency/Project Currency for the Corresponding Date and Type.
• Transaction Currency/Project Functional Currency for the Corresponding Date and Type.
• Project Currency/Project Functional Currency for the Corresponding Date and Type.
• Save the Changes and re-test the issue.

Book Controls: Changing Divide Depreciation Field: FRM-40200: Field is Protected Against Update

Issue:  
The Divide Depreciation drop down box on the Book Controls screen does not allow update.

Solution:
The Divide Depreciation value for the Asset Book can be changed when the first period of a new fiscal year is the current period.

Make this change after the opening of a new fiscal year.

PA_FUNC_SECURITY_ENFORCED - While creating events through API from Custom Page

Error:

PA_FUNC_SECURITY_ENFORCED - While creating events through API from Custom Page

Solution:
The following functions needs to be added in the Custom menu created for Event creation.

Events maintainence for single project

Activity Management Gateway:Create Event

Activity Management Gateway:Delete Event

Activity Management Gateway:Update Event

Activity Management Gateway:Delete Event OK

Invoice Events Maintainence

Revenue Events Maintainence

CE: Error: FUN_INTRA_RULE_NOT_ASSIGNED' Validating a Bank Account Transfer

Error :

1. FUN_INTRA_RULE_NOT_ASSIGNED
2. Intercompany balancing was unable to generate the intercompany account
3. The intercompany account generated by the intercompany balancing rules is invalid
4. The intercompany account generated by the intercompany balancing rules is invalid

Cause:

The issue is caused as The Intercompany Balancing Rules are not set up.

Solution:

In order to correctly setup The Intercompany Balancing Rules, please follow the steps:

Responsibility - General Ledger

1.Navigate - Setup - Financials - Accounting Setup Manager
2.Find your Ledger
3.Update Accounting Options
4.Operating Units - Update
5.Confirm your Operating Units have been added, or add them if they are not already there.
6.Return to Accounting Options.
7.Intercompany Accounts - Update

8.Define Relationships between your Legal Entities
8.1.For your First Legal Entity
8.2.Click Define Relationships
8.3.Click Add Another Row
8.4.Transacting Balancing Segment = Enter the Balancing Segment Value for your first Legal Entity
8.5.Trading Partner Legal Entity = Enter the name of your Second Legal Entity
8.6.Trading Partner Balancing Segment Value = Enter the Balancing Segment Value for your second Legal Entity
8.7.Click Define Accounts
8.8.Enter your Intercompany Receivables Account
8.9.Enter your Intercompany Payables Account
8.10.Click Apply
8.11.Click Cancel
8.12.For  your second Legal Entity
8.13.Click Define Relationships
8.Click Add Another Row
8.15.Transacting Balancing Segment = Enter the Balancing Segment Value for your second Legal Entity
8.16.Trading Partner Legal Entity = The name of your First Legal Entity
8.17.Trading Partner Balancing Segment Value = Enter the Balancing Segment Value for your first Legal Entity
8.18.Click Define Accounts
8.19.Enter your Intercompany Receivables Account
8.20.Enter your Intercompany Payables Account
8.21.Click Apply
8.22.Click Cancel
8.23.Change Status to Complete
8.24.Click Done

9.Intercompany Balancing Rules - Update
9.1.For your First Legal Entity (LE)
9.2.Create Rule
9.2.1.Source = Cash Management
9.2.2.Category  = Bank Transfers(1)
9.2.3.Balancing Details Tab
9.2.3.1.Populate Debit Balancing Segment Value  - Specific Value you created for your LE
9.2.3.2.Populate Credit Balancing Segment Value  - Specific Value you created for your LE
9.2.3.3.Populate Debit Account
9.2.3.4.Populate Credit Account
9.2.4.Options Tab
9.2.4.1.Default Clearing Balancing Segment Value - Specific Value you created for your LE
9.2.5.Balancing Details Tab
9.2.5.1.Populate Debit Balancing Segment Value  - All Other
9.2.5.2.Populate Credit Balancing Segment Value  - All Other
9.2.5.3.Populate Debit Account
9.2.5.4.Populate Credit Account
9.3.Create Rule
9.3.1.Source = Other
9.3.2.Category  = Other
9.3.3.Balancing Details Tab
9.3.3.1.Populate Debit Balancing Segment Value  - All Other
9.3.3.2.Populate Credit Balancing Segment Value  - All Other
9.3.3.3.Populate Debit Account
9.3.3.4.Populate Credit Account
9.3.4.Options Tab
9.3.4.1.Default Clearing Balancing Segment Value - Specific Value you created for your LE
9.4.For  your second Legal Entity
9.5.Create Rule
9.5.1.Source = Cash Management
9.5.2.Category  = Bank Transfers(1)
9.5.3.Balancing Details Tab
9.5.3.1.Populate Debit Balancing Segment Value  - Specific Value you created for your LE
9.5.3.2.Populate Credit Balancing Segment Value  - Specific Value you created for your LE
9.5.3.3.Populate Debit Account
9.5.3.4.Populate Credit Account
9.5.4.Options Tab
9.5.4.1.Default Clearing Balancing Segment Value - Specific Value you created for your LE
9.5.5.Balancing Details Tab
9.5.5.1.Populate Debit Balancing Segment Value  - All Other
9.5.5.2.Populate Credit Balancing Segment Value  - All Other
9.5.5.3.Populate Debit Account
9.5.5.4.Populate Credit Account
9.6.Create Rule
9.6.1.Source = Other
9.6.2.Category  = Other
9.6.3.Balancing Details Tab
9.6.3.1.Populate Debit Balancing Segment Value  - All Other
9.6.3.2.Populate Credit Balancing Segment Value  - All Other
9.6.3.3.Populate Debit Account
9.6.3.4.Populate Credit Account
9.6.4.Options Tab
9.6.4.1.Default Clearing Balancing Segment Value - Specific Value you created for your LE