Thursday, August 14, 2014

FIC-Import Credit Trx via File Import


To BottomTo Bottom

In this Document
Goal
Solution
  Step # 1.  Create a File Import mapping.
 Step # 2.  Create a CSV (comma delimited) data file
 Step # 3.  Create a File Import Activity
 Step # 4.  Run Collect Transaction  (see Collect Transaction Troubleshooting Guide Doc ID 1392581.1) 
 Step # 5. Verify credited transaction imported and collected successfully
References


APPLIES TO:

Oracle Fusion Incentive Compensation Cloud Service - Version 11.1.7.0.0 and later
Oracle Fusion Incentive Compensation - Version 11.1.7.0.0 and later
Information in this document applies to any platform.

GOAL

This document will specify the required fields and mapping to import credited transactions using File Import for object Incentive Compensation Transactions.
Menu Path: Navigator > Incentive Compensation > Credits and Earnings > Import Transactions Using File Based Data Import

SOLUTION

 Step # 1.  Create a File Import mapping.

 Navigator > Setup and Maintenance > Search Task: Manage File Import Mappings
Screenshot of the mapping

 
Column HeaderSample ValueDescription
TRANSACTION_TYPEMANUALTask: Manage Incentive COmpensation Lookups - search on lookup type CN_TP_TRANSACTION_TYPE.  User can create new transaction types.  Use the lookup code as the value for the data file.
TRANSACTION_NUMBERImpTrx-1Normally, transaction number is unique. However for credited transactions, it can be the same as the next record as long as the credited_participant is not the same.  Meaning, you can load multiple credited participants for the same transaction.
EVENT_DATE01/16/2012 
CREDIT_DATE01/16/2012 
ROLLUP_DATE01/16/2012 
TRANSCTION_AMOUNT150.00 
QUANTITY25 
CURRENCY_CODEUSD 
CREDIT_CATEGORY300000001228758Use sql to find out the id value for the credit category:

SELECT eligible_cat_id, name
   FROM cn_eligible_cats_all_tl ;  
CREDIT_AMOUNT113.25 
CREDIT_SPLIT_PERCENT75.50Percentage. If this is not 100% then the credit_amount should reflect the transaction_amount X credit_split_percent.  Example: 150 X 75.50% = 113.25
CREDIT_REVENUE_TYPEREVENUE or NON_REVENUE
CREDITED_PARTICIPANT_ID10001Use sql to find out the id value for the credited_participant :

SELECT participant_id, participant_name
    FROM cn_srp_participants_all ;
PROCESS_CODECNRECThe process code will tell the system if the following process in this order (Classify, Credit, Rollup, Eligibility, Calculation) will be process or not.

CCREC = Normal,  process all
NCREC = Skip classification
NCNEC = Skip classification and rollup
CNNEC = Skip crediting and rollup
CNREC = Skip crediting
CCNEC = Skip rollup
NNREC = Skip classification and crediting
NNNEC = Skip classification, crediting, and rollup
Note: If you want to preserve the credit receivers and credit categories values, then use option to skip crediting (eg. CNREC)
BUSINESS_UNIT_ID300000001175314Use sql to find out value of business_unit_id.

SELECT DISTINCT bu.bu_id,   bu.bu_name
  FROM fun_all_business_units_v bu,
           fun_business_functions_b bf,
           fun_bu_usages_v buu
 WHERE bu.bu_id = buu.business_unit_id
     AND bf.business_function_code = 'INCENTIVE_COMPENSATION_BF'
     AND bf.business_function_id = buu.module_id ;
SOURCE_BUSINESS_UNIT_ID300000001175314 Use sql to find out value of business_unit_id.

SELECT DISTINCT bu.bu_id,   bu.bu_name
  FROM fun_all_business_units_v bu,
           fun_business_functions_b bf,
           fun_bu_usages_v buu
 WHERE bu.bu_id = buu.business_unit_id
     AND bf.business_function_code = 'INCENTIVE_COMPENSATION_BF'
     AND bf.business_function_id = buu.module_id ;
SALES_CHANNELEpipenOptional - example of Channel value used in classification or crediting rules.
ATTRIBUTE_NUMBER11220.00Optional - example of populating a numeric attribute value to be used for calculation.

SaaS  If you are a Software-as-a-Service (SaaS) customer, please log a Service Request in My Oracle Support for Oracle to get the results of the id values for business_unit_id. credit_category_id, and credited_participant_id queries for you.

Step # 2.  Create a CSV (comma delimited) data file

Download sample transaction data file here.
This sample csv data file will create three transactions:
      
 Transaction Number:  ImpCreditTrx-4  
 Transaction Amount:  150.00   
 ParticipantCredit AmountSplit PercentRevenue Type 
 10000$113.2575.5Revenue 
 10001$36.7524.5Revenue 
 10002$250.00100Non-Revenue 
      
 Transaction Number:  ImpCreditTrx-5  
 Transaction Amount:  150.00   
 ParticipantCredit AmountSplit PercentRevenue Type 
 10001$500.00100Revenue 
      
 Transaction Number:  ImpCreditTrx-6  
 Transaction Amount:  150.00   
 ParticipantCredit AmountSplit PercentRevenue Type 
 10000$75.00100Revenue 
      

Step # 3.  Create a File Import Activity

Navigation : Credits and Earnings > Import Transactions Using File Based Data Import
Screenshot of defining an import activity.


  
                             NOTE: When Status change to "Base table upload in progress" then this portion is completed.
  


Step # 4.  Run Collect Transaction  (see Collect Transaction Troubleshooting Guide Doc ID 1392581.1) 

Screenshot of submitting collect transaction.

Step # 5. Verify credited transaction imported and collected successfully

Navigator > Credits and Earnings > Manage Credits

FIC-Classification Rules

To BottomTo Bottom

In this Document
Goal
Solution
References


APPLIES TO:

Oracle Fusion Incentive Compensation Cloud Service - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

GOAL

We have Fusion Incentive Compensation setup to have classification run before crediting.
We are trying to upload credits via UCM (navigator - Credit and Earnings - Incentive Compensation Transaction Import).
If we don't populate the Eligible Category ID field in the file, the transaction and the credits get loaded without credit category, which is fine.

Now if we run classification, it assigns the credit category but wipes out the credited transaction.
What should happen is that  Fusion Incentive Compensation should look at the process code and if it says SKIP crediting, classification should not wipe out the credited transaction.

SOLUTION

If user is importing credits without credit category , and want to  classify these credits then they should set the timing of the classification
job to be "after crediting and rollup and before calculation".
.
Please note the following distinctions between the 2 timings of  classification job :
1. When the classification timing is "After collection and before crediting",classification job processes transactions

2. When the classification timing is "After crediting and rollup and before calculation", classification job processes credits

So, when you want to classify credits you have to set the timing of the classification job to be "After crediting and rollup and before calculation".

Further points will be managed in Enhancement Request :
Bug 18716312 : CACK-TEST RUNNING CLASSIFICATION AFTER CREDIT IMPORT WIPES OUT

FIC - Request Set/JobSet Functionlity

To BottomTo Bottom

In this Document
Goal
Solution
References


APPLIES TO:

Oracle Fusion Incentive Compensation Cloud Service - Version 11.1.5.0.0 and later
Oracle Fusion Incentive Compensation - Version 11.1.5.0.0 and later
Information in this document applies to any platform.

GOAL

How to create a request set to run a set of processes in Oracle Fusion Incentive Compensation.
User wants to create a request set (Job Set) to automatically run each job sequentially. This will save time from having to check the status on each processes.
Depending on your system parameter settings , these are the processes you need to run in order:
NOTE:  Currently, collection process can not be added to the request set because the parameters have to be pre-defined in the Enterprise Manager.  Users would not be able to change the parameter for the Collection process.
  
Rollup Using = Both, Classify after crediting
1. Revert Transaction
2. Run Crediting and Rollup
3. Run Classify Credit
4. Calculate

Rollup Using = Both, Classify before crediting
1. Revert Transaction
2. Run Classify Credits
3. Run Crediting and Rollup
4. Calculate

Rollup using Rollup Hierarchy, Classify after crediting
1. Revert Transaction
2. Run Crediting
3. Run Rollup
4. Run Classify Credits
5. Calculate

Rollup using Rollup Hierarchy, Classify before crediting
1. Revert Transaction
2. Run Classify Credits
3. Run Crediting
4. Run Rollup
5. Calculate

Rollup using Credit Hierarchy, Classify after crediting
1. Revert Transaction
2. Run Crediting and Rollup
3. Run Classify Credits
4. Calculate

Rollup using Credit Hierarchy, Classify before crediting
1. Revert Transaction
2. Run Classify Credits
3. Run Crediting and Rollup
4. Calculate

Rollup Using = Both, Do not use Classification
1. Revert Transaction
2. Run Crediting and Rollup
3. Calculate

Rollup using Rollup Hierarchy, Do not use Classification
1. Revert Transaction
2. Run Crediting
3. Run Rollup
4. Calculate

Rollup using Credit Hierarchy, Do not use Classification
1. Revert Transaction
2. Run Crediting and Rollup
3. Calculate

SOLUTION


SaaS If you are a Software-as-a-Service (SaaS) customer, the following section need not be performed by you. Please log a Service Request in My Oracle Support for Oracle to do this for you.


 
RequestMetadata Job Name
Deploy Compensation PlansDeployPlans
Deploy Credit RulesSynchronizeCreditRules
Deploy Classification RulesSyncrhonizeClassificationRules
Revert TransactionsRevertTransactions
Classify CreditsClassification
Run CreditingCrediting
Run Crediting and RollupCreditingAndRollup
Run RollupRollup
Calculation (for All Participants)CalculateAll















STEP # 1:  Create the jobset definition in ICDomain Enterprise Manager (EM)
Navigation: Farm_ICDomain > Scheduling Services > ESSAPP (ess_server1) > Job Metadata > Job Sets

Example #1. Creating a Calculation Jobset
New Request Set definition:
Application = IncentiveCompensationEssApp
Job Set Name = CUSTOM_CALC_JOBSET
Display Name = Custom Calculation Jobset
Select SERIAL

Add Step:
Note:  Do not name the step with a number in front (eg. 1_Revert) or have a space in the Step name.
  

Step ID                      Job                       Effective Application
Revert                       RevertTransactions Insert into main diagram
Classification              Classification         Insert into main diagram
Crediting                   Crediting                Insert into main diagram
Rollup                       Rollup                   Insert into main diagram
Calculate                   CalculateAll            Insert into main diagram


Add Application Defined Properties:
Name                                       Type    Initial Value
srsFlag                                     String   Y
jobDefinitionApplication              String   CN
EXT_PortletContainerWebModule String   IncentiveCompensation

Add System Properties:
System Properties             Type    Initial Value
SYS_effectiveApplication     String  EarIncentiveCompensationEss
SYS_product                     String  CN

Modify each step so if warning to continue on.



Example #2. Creating a Setup Jobset
New Request Set definition:
Application = IncentiveCompensationEssApp
Job Set Name = CUSTOM_SETUP_JOBSET
Display Name = Custom Setup Jobset
Select SERIAL

Add Steps:
Step ID                               Job                                             Effective Application
DeployClassificationRules      SynchronizeClassificationRules        Insert into main diagram
DeployCreditRules                SyncrhonizeCreditRUles                  Insert into main diagram
DeployCompensationPlans    DeployPlans                                  Insert into main diagram

... the rest is similar to Example # 1.


STEP # 2:  Grant Access to Jobset
Navigate to the Authorization Policy Manager

   1. Under Authorization Management tab, on the Home sub tab, select the pillar corresponding to the application where the Job Set was created.
       For IncentiveCompensationEssApp, the pillar is fscm.
   2. Under the Resources section, click on Search and enter the following filters:
       Resource Type: ESSMetadataResourceType
       Name:  oracle.apps.ess.custom
   3. Select the oracle.apps.ess.custom.* item and click on the Open icon
   4. Click Create Policy button at the top right and enter the following fields:
       Name: a representative name for the policy  (eg. CN_ESS_CUSTOM_POLICY)
       Display Name: the name visible for the policy  (eg. CN_ESS_CUSTOM_POLICY)
   5. For the Principals section, select Match = Any or All
       Note:
       Any: if the user should meet at least one of the roles described on the policy to access the Job Set
       All: If the user should meet ALL the roles described on the policy to access the Job Set
   6.  Click on Add icon to add the Principals
        a.    Search for the Application Role that will have access to the JobSet
        b.    Select the role from the Search Results list
               Example: For calculation type of request set, add role Incentive Compensation Plan Administrator
        c.    Click the Add Selected button to pass the role to the Selected Principals list
        d.    Repeat the process to add as many roles as necessary.
        e.    Click Add Principals button
    7.  From the Targets list, expand the oracle.apps.ess.custom.* item.
         Select the checkboxes: read, execute, update.

FIC-Compensation Plan Configuration

In this Document
Goal
Fix
 
 1. Create Credit Category
 2. Create Classification Rules
      A. Create parent rule
              Button: Create Hierarchy
     B. Create child rules
             Button: Create Node
             Button: Create Node
          Name = FAST Rule Orlando
         Start Date = 01-JAN-2007
         End Date = 31-DEC-2012
         Parent = FAST Rule FL
         Qualifying Criteria:
                City = Orlando
         Credit Category = FAST Category Orlando

       
 

            
     C. Submit synchronize classification rule process
          Navigation: Task > Jobs > Deploy Classification Rules
         From Date = 01-01-07
         To Date = 31-12-12
         Click Submit
    D. Check status of classification synchronization
         Navigation: Task > Job Status> View Jobs
 3. Create Expressions
 Navigation: Task > Expressions > Create Expression
       A. Create input expression
            Name = FAST Trx Amt
           Type = Calculation
           sequence 1) Attributes > Credit > TRX_AMT 
           sequence 2) /
           sequence 3) Attributes > Constant > 100
 
      B. Create output expression
           Name = FAST RTR Trx Amt
          Type = Calculation
          sequence 1) Attributes > Rate Table Rate
          sequence 2) *
          sequence 3) Attributes > Credit > TRX_AMT
 4. Create Rate Table
      A. Create Rate Dimension
           Navigation: Task > Rate Dimensions > Create Rate Dimension
          Name = FAST Simple Amount Dim
          Type = Amount
          Add Tiers
          
     B. Create Rate Table
          Navigation: Task > Rate Tables > Create Rate Table
         Name = FAST Simple Percent Rate
         Type = Percent
         Add Rate Dimensions - select name = FAST Simple Amount Dim
         SAVE
    C. Add Rates
         In the same Create Rate Table screen, click on Edit Rates button
        
 5. Create Performance Measures
 Navigation: Task > Performance Measures
      A. Create Performance Measure
           Name = FAST Simple Perf Measure
          Incentive Type = Commission
          Include in participant's reports = checked
          Start Date = 1/1/2007
          End Date = 12/31/2012
          Performance Interval = Period
          Unit of Measure = Amount
     B. Define Goal
          Target amount = 25000
         Unit of Measure = Amount
         Click on Distribute Evenly - get following error:
               "CN-1575209: You must define all of the required periods for the goal duration, from
                2007-01-01 to 2012-12-31, before distributing the target number. You can define the periods
                for the calendar through set up work area."
         Note: The duration ends 12/31/2012 but we only have periods defined up to 5/31/2012. So need to
                  go back to Calendar and add more periods (Jun-12 to Dec-12).  (see 
Note: 1272307.1)
      C. Define Credit Categories
           Name = FAST Category Orlando
      D. Define Credit Factors (optional)
          
          Start Date = 1/1/07
          End Date = 12/31/07
          Credit Factor = 75  (this is 75% of the transactions for 2007 year only for credit)
     E. Define Transaction Factors (optional)
          Transaction Type = Invoice
         Transaction Factor = 50 (this is 50% of the invoice amount)
      F. Measure Formula
           Process Transactions = Individually
          Expression Name = FAST Trx Amt (ie. performance expression)
          Running Total = unchecked
      G. Scorecard 
 
 6. Create Plan Components
 
 
      Navigation: Task > Plan Components > Create Plan Component

      Name = FAST Simple Component 1
      Incentive Type = Commission
      Earning Type = Monetary Earnings
      Start Date = 1/1/2007
      End Date = 12/31/2012
      Calculation Phase = Phase 1
       A. Add performance measure
            Name = FAST Simple Perf Measure
       B. Define incentive formula
            Payout Frequency = Period
           True Up = unchecked
           Expression Name = FAST RTR Trx Amt  (ie. output expression)
           Include Indirect Credits = All  (options:  All, Manager, Team, None)
        C. Add rate table
            How many dimensions will this rate table have? 1
           Split attainment across tiers = No
           Scorecard:  Add Rate Tables Name = FAST Simple Percent Rate
           Add rate dimensional input = FAST Trx Amt  (ie. input expression)
        D. Provide payment information
            Payment Plan Category = Commission
           Payment made through a third party? =  No
 7. Create Compensation Plan
      Navigation: Task > Compensation Plans > Create Compensation Plan
     Name = FAST Simple Compensation Plan 1
     Target Incentive = 30000
     Start Date = 1/1/2007
     End Date = 12/31/2012
     Allow Credit Category Overlap = Yes
     Approval Status = Not approved
     A. Add plan components - name = FAST Simple Plan Element 1
     B. Manually change the approval = Approved
 
 8. Deploy Compensation Plan
 OIC Work Area = Participant Assignments
Navigation: Task > Processes > Deploy Compensation Plan
Parameter:  <select business unit>

APPLIES TO:

Oracle Fusion Incentive Compensation - Version 1.0-Beta and later
Oracle Fusion Incentive Compensation Cloud Service - Version N/A and later
Information in this document applies to any platform.

GOAL

Part of the master document on how to setup a sample Fusion Incentive Compensation flow.
This document will show step by step how to setup a simple compensation plan.

FIX

1. Create Credit Category


Note:  "Credit Category" is the same as eBusiness Incentive Compensation (release R12)'s "Product" also named as "Revenue Class" in release R11i.

OIC Work Area = Compensation Plans
Navigation: Task > Credit Categories > Create Credit Category
examples: FAST Category USA
                FAST Category FL
                FAST Category Orlando

2. Create Classification Rules

     A. Create parent rule

          Navigation: Task > Classification Rules > Manage Classification Rules
             Button: Create Hierarchy
            Name = FAST State Rule
            Start Date = 01-JAN-2007
            End Date = 31-DEC-2012
            Qualifying Criteria: 
                       Customer Category = FAST
                       Country = United States
            Credit Category = FAST Category USA

    B. Create child rules

         Navigation: Task > Classification Rules > Manage Classification Rules
            Button: Create Node
         Name = FAST Rule FL
         Start Date = 01-JAN-2007
         End Date = 31-DEC-2012
         Parent = FAST Rule USA
         Qualifying Criteria:
                  State = FL
         Credit Category = FAST Category FL
            Button: Create Node
         Name = FAST Rule Orlando
         Start Date = 01-JAN-2007
         End Date = 31-DEC-2012
         Parent = FAST Rule FL
         Qualifying Criteria:
                City = Orlando
         Credit Category = FAST Category Orlando

       
Note: To view the specific hierarchy only,  select the top rule (eg. FAST Rule USA) and click on the Show as Top icon.


            

    C. Submit synchronize classification rule process

         Navigation: Task > Jobs > Deploy Classification Rules
         From Date = 01-01-07
         To Date = 31-12-12
         Click Submit

   D. Check status of classification synchronization

        Navigation: Task > Job Status> View Jobs

3. Create Expressions

Navigation: Task > Expressions > Create Expression

      A. Create input expression

           Name = FAST Trx Amt
           Type = Calculation
           sequence 1) Attributes > Credit > TRX_AMT 
           sequence 2) /
           sequence 3) Attributes > Constant > 100
Note: Column TRX_AMT is the user defined name for column TRANSACTION_AMT_CURR setup in Tables and Columns screen.

     B. Create output expression

          Name = FAST RTR Trx Amt
          Type = Calculation
          sequence 1) Attributes > Rate Table Rate
          sequence 2) *
          sequence 3) Attributes > Credit > TRX_AMT

4. Create Rate Table

     A. Create Rate Dimension

          Navigation: Task > Rate Dimensions > Create Rate Dimension
          Name = FAST Simple Amount Dim
          Type = Amount
          Add Tiers
          

    B. Create Rate Table

         Navigation: Task > Rate Tables > Create Rate Table
         Name = FAST Simple Percent Rate
         Type = Percent
         Add Rate Dimensions - select name = FAST Simple Amount Dim
         SAVE

   C. Add Rates

        In the same Create Rate Table screen, click on Edit Rates button
        

5. Create Performance Measures

Navigation: Task > Performance Measures

     A. Create Performance Measure

          Name = FAST Simple Perf Measure
          Incentive Type = Commission
          Include in participant's reports = checked
          Start Date = 1/1/2007
          End Date = 12/31/2012
          Performance Interval = Period
          Unit of Measure = Amount

    B. Define Goal

         Target amount = 25000
         Unit of Measure = Amount
         Click on Distribute Evenly - get following error:
               "CN-1575209: You must define all of the required periods for the goal duration, from
                2007-01-01 to 2012-12-31, before distributing the target number. You can define the periods
                for the calendar through set up work area."
         Note: The duration ends 12/31/2012 but we only have periods defined up to 5/31/2012. So need to
                  go back to Calendar and add more periods (Jun-12 to Dec-12).  (see Note: 1272307.1)

     C. Define Credit Categories

          Name = FAST Category Orlando

     D. Define Credit Factors (optional)

         
          Start Date = 1/1/07
          End Date = 12/31/07
          Credit Factor = 75  (this is 75% of the transactions for 2007 year only for credit)

    E. Define Transaction Factors (optional)


         Transaction Type = Invoice
         Transaction Factor = 50 (this is 50% of the invoice amount)

  F. Measure Formula

          Process Transactions = Individually
          Expression Name = FAST Trx Amt (ie. performance expression)
          Running Total = unchecked

     G. Scorecard 

          Note: can leave blank.

6. Create Plan Components

Note: "Plan Components" is the same as eBusiness Incentive Compensation (release R12 and 11i)'s "Plan Element".

      Navigation: Task > Plan Components > Create Plan Component

      Name = FAST Simple Component 1
      Incentive Type = Commission
      Earning Type = Monetary Earnings
      Start Date = 1/1/2007
      End Date = 12/31/2012
      Calculation Phase = Phase 1

      A. Add performance measure

           Name = FAST Simple Perf Measure

      B. Define incentive formula

           Payout Frequency = Period
           True Up = unchecked
           Expression Name = FAST RTR Trx Amt  (ie. output expression)
           Include Indirect Credits = All  (options:  All, Manager, Team, None)

       C. Add rate table

           How many dimensions will this rate table have? 1
           Split attainment across tiers = No
           Scorecard:  Add Rate Tables Name = FAST Simple Percent Rate
           Add rate dimensional input = FAST Trx Amt  (ie. input expression)

       D. Provide payment information

           Payment Plan Category = Commission
           Payment made through a third party? =  No

7. Create Compensation Plan

     Navigation: Task > Compensation Plans > Create Compensation Plan
     Name = FAST Simple Compensation Plan 1
     Target Incentive = 30000
     Start Date = 1/1/2007
     End Date = 12/31/2012
     Allow Credit Category Overlap = Yes
     Approval Status = Not approved

    A. Add plan components - name = FAST Simple Plan Element 1

    B. Manually change the approval = Approved

8. Deploy Compensation Plan

OIC Work Area = Participant Assignments
Navigation: Task > Processes > Deploy Compensation Plan
Parameter:  <select business unit>
 

Document Details

 
Email link to this documentOpen document in new windowPrintable Page
HOWTO
PUBLISHED
13/07/2012
13/07/2012
   
 

Related Products

 
Oracle Fusion Incentive Compensation
Oracle Fusion Incentive Compensation Cloud Service
   
 

Information Centers

 
No Information Center available for this document.
   
 

Document References

 
No References available for this document.