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)".