Revenue Recognition Analytic xApp misses standard BAPIs / Services

We have an opportunity to develop a SAP xApp Analytics for Revenue Recognition. This xApp is especially interesting for companies in the High tech, Software industry. One of the problems we are facing is that some of the BAPIs which connect to the ERP system are not in the SAP standard offering. Does anyone have experience or developed BAPIs / Services in the following area:
Name: REVREC_01
Functional Description: BAPI enable transaction VF45 (rather than BAPI enable direct table read) - In this way we maintain the same KPI presentation logic as in ERP.
Inputs: As for VF45 input, but Sales Doc must not be mandatory entry. Additional Input fields required such as Sales Org, Product Category, Material (All mutiple values) - Sold To Party must also be mutiple value input.
Outputs: As for VF45 Control Lines output and Revenues and Billing Docs (by Period) Output. In addition for both outputs we would require output by Sales Org, Product Category, Material and Employee Responsible. Also require additional KPIs in the Control Lines such as Revenue Recognised MTD and Rev to be Recognised MTD.
Name: REVREC_02
Functional Description: BAPI enable transaction VF44 (rather than BAPI enable direct table read) - In this way we maintain the same KPI presentation logic as in ERP.
Inputs: As for VF44 input. Additional Input fields required such as Sales Org, Product Category, Material.
Outputs: As for VF44 Output. In addition for both outputs we would require output by Sales Org, Product Category, Material and Employee Responsible.
Thank you,
Claus

Similar Messages

Service Based Revenue Recognition - Prov Account Missing when using WBS

Hi,
I´ve activated RR functionality using service based and aceptance date.
I've followed the intructions from the best practices documents and the notes:
Note 820417 u2013 IMPLEMENTATION GUIDE FOR REVENUE RECOGNITION
Note 1172799 u2013 NEW VERSION OF BEST PRACTICES FOR REVENUE RECOGNITION
Note 678260 CONSTRAINTS
Note 777996 u2013 ACCOUNT SETTINGS FOR REVENUE RECOGNITION PROCESS
Note 779366 u2013 REVENUE RECOGNITION IN THE SD MODULE
Note 1166848 u2013 CUSTOMIZING SETTINGS
Note 782758 u2013 PREREQUISITS FOR USING REVENUE RECOGNITION
Note 835367 - Activating SAP ERP SD revenue recognition
Note 1000830 - Revenue recognition through incoming invoice (third-party
Note 1025066 - Revenue recognition by proof of delivery (POD)
Note 1120297 - Revenue recognition by acceptance date
Note 1125456 - Revenue recognition due to customer-specific event
We are implementing SD, FI (using New Gral Ledger), PS, CO and MM in a company that sells projects. Therefore we're posting everything to the WBS elements.
We need to post the revenue values to the WBS elements too.
The problem is that when we create a sales order for RR indicating a WBS element and try to save it, the system activates the incompletion log saying that the provision account is missing, despite the account is in VKOA.
The strange thing is that if we use a material with profit center (without any WBS or order indication in the sales order) all the revenue recognition process runs perfectly (we save the order, VBREVK is fullfiled, VF44 is run and the invoice is done correctly).
Does anybody know why when using a WBS element in the sales order, SAKN2 field is not fullfiled and the incompletion log is activated???
Is it a program error? Or are we doing something wrong?
Quick responses will be apreciated since we need to move on within two weeks!
Thanks in advance!
María del Valle Pintor.
Moderator: This thread has been locked due to crossposting.
Please do not post the same question in different forums.

sap note 883544

SD Revenue Recognition-Account settings for deferring COGS

Hi Experts
In the current process, COGS, cost of goods sold is getting posted into the COGS G/L account, while creation of billing document.
In VF44 transaction, we find option for VPRS cost being captured against every line item & are available for posting along with revenue line.
In that case, if we have to defer the COGS while creating the billing document & would recogonize it while running VF44 alone with the revenue lines, could you suggest me the account setting to be done for the same?
Anticipating earliest responses
Thanks
Banu

hi
820417 - Implementation Guide for Revenue Recognition
779365 - Best Practice document for revenue recognition
REVENUE RECOGNITION
In revenue recog. you can create your billing documents and they will be passed to accountings.But in this case your customer account would be debited and deferred accounts would be credited.
The purpose of revenue recognition is that you can post all the revenues from a deferred account to sales revenue account for a particular period together for all the docs. through transaction VF44.
if you can se your sales docs no. in VF44,then your revenue recognition is successful.Press on collective processing inside VF44 for posting the revenues from deffered acc to sales revenue account.
Configuration part includes the setting of revenue recog. in item category by following the path sd-basic functionsaccount assnmnt/costingrevenue recog.
Then you have to assign G/L accounts.In the first column of assigning g/l accounts ,enter your sales revenue account and in the second column enter deferred revenue accounts.Deferred revenue account is a spcl g/l account.
Don't forget to enter reconcilliation account in your customer master as well.
It may happen that in revenue recog item categories fields may greyed out but you have to get authorization for your id from a basis guy.
:The point at which revenue (income) is credited to a revenue account in General Ledger. There are three possible types
Time-based : Revenue is recognized in equal proportions between specific start and end dates based on the number of posting periods defined at the company level. Revenue recognition for time-based documents can occur before, during, or after the invoice process.
Performance-based : Revenue is recognized based on the occurrence of certain events such as goods issue or the performance of a service. Revenue recognition for performance-based documents can occur before, during, or after the invoice process.
Standard : Revenue is recognized at time of invoice:
The specified item was not found.
Re: Revenue Recognition
CONTRACTS
Lets take standard CQ contract type:
First maintain customer - material info record in VD51 T-code
Secondly maintain pricing for customer / material or only material combination in VK31 / VK11 T-code
Then use VA41 T-code to create a contract
VA42 to change contract
VA43 to display / view contract
In VA41, enter the document type CQ, followed by the sales area details,
Enter Sold to party.
Enter PO number
Enter PO Date
Enter Validitiy from Date
Enter Validity to Date
Enter Material
Enter Quantity say 999,999,999 or any other higher quantity as it is referred again and agaain
Hit Enter.
Save.
regards
balajia

Revenue Recognition Forecast Based on Quotations

I have a requirement to create a revenue recognition forecast based on the open quotations. These quotations linked to opportunities are open for some time before being signed and provide a good basis for forecasting revenue recognition in upcoming quarters. We have many revenue recognition methods here including time based, service based, collection based, POD, and POC. I don't see much useful standard functionality in SD revenue recognition nor in results analysis for creating these forecasts from quotes.
The SD revenue schedules in tables VBREV* are not generated on quotation document lines nor on items that are not billing relevant. RA can be run in planning mode, but it is a secondary process on the saved data in CO on a cost object that must be run individually for each future period.
Not only do we need the Revrec forecast, but we want to simulate changes to our quotes and projects and immediately see the affect on Revrec. I am about to create a custom development within sales document processing to create the Revrec forecasts in a rough manner in a Z table. Before I start to code, I am curious to know if anyone else has had such requirement and has better ideas of how to accomplish this.

Hello Karl,
The Best Practices document in the Note 1172799 provides details regarding all the SAP supported processes for RR functionality.
Regards,
Raghavendra

Service based revenue recognition (u0091Bu0092) contract with call off

I am trying to understand Revenue Recognition. I have come across the above term." Contract with call off"
Can anyone tell me what exactly this means.

Dear sap
The contract consists of items defining the individual materials, material groups, or services with prices and in many cases quantities.
An item is assigned to an item category, which defines the type of procurement (e.g. item category K for consignment, or L for subcontracting).
An item of the procurement type "external service" contains a set of service specifications. Such specifications may be hierarchically structured. The summary view of such a hierarchical structure is termed an "outline", and the individual levels of the hierarchy are referred to as "outline levels". Quantities are specified in service lines. Services can be released (ordered, or called off against the contract) at item level or at the level of the service line.
Thanks
G. Lakshmipathi

Service-related revenue recognition

Hi Experts,
When post VF44 for a contract with Service-related revenue recognition (revenue recognition category B) get the message below. No RR FI document posted too.
<<Document for SD reference number u2018delivery orderu2019 does not exist
Message no. JHE019
DiagnosisDocument for SD reference number &1 does not exist. If accounting documents for revenue recognition have been created at collective processing level, you cannot navigate in the original document.>>
Any advise.
Cheers.

hi,
please check in scribd these is a link related to RR.
or
please check in forums on the same.
regards,
balaia

UNBILLED RECIEVABLE ACCOUNT- SERVICE CONTRACT WITH REVENUE RECOGNITION

Hi SAP Gurus,
I want to draw your kind attention towards my problem:
I have created service contract with one year contract and created an invoice for the whole year in advance.
Now in-between i cancelled a contract (after three months) and want to recognised a revenue for the contract period , so i'm creating a revenue recognition for the three months one by one using transaction code-VF44,
first month revenue recogniton is working fine as first month amount is going from deffered account to revenue account
But for second month instead of deffered account ,system is using unbilled recievable account ,which is wrong .
Can anybody tell me why the system is picking unbilled receivable account instead of deffered account in case of second month revenue recogniton.
This may help us:
"When i was cancelling a contract ,at that time i was entering a billing plan end date in billing plan tab at an item level.
and just after entering end date ,system was creating two lines instead of one in billing plan tab and i think because of that extra line system is picking unbilled receivables in second revenue recognition."
Thanks in advance
Ujjawal
Edited by: Ujjawal Singh Karki on Dec 29, 2010 12:05 PM

Hi,
Thank you for your reply.
I am doing a contract billing for overall period that is for 12 months (contract is of 12 months).
Just after 3 months i have realized that somehow we have to cancel the contract and we canceled that in 3rd month.
I had created the created a contract with periodic billing plan and for canceling that contract i'm putting contract end date in BILLING PLAN TAB as 31/03/2011 (Let say contract is from 01/01/2011 to 31/12/2011).
Can you/anybody please tell me whether is this the correct way of canceling the contract with periodic billing plan?
As per your analysis:
"It seems you have done the billing document for one period and you are doing the RR document for multiple periods and hence the revenue is going to unbilled receivable account for the period for which billing document has not been done"
As i have billed the customer for 12 months but contract was only for 3 months so i'll create RR for only 3 months and for rest of the period (i.e. 9 months) i'll create credit memo and send it to customer.
"Please use a billing type where you will specify only start date and end date of the contract and not the billing plan in contract"
How can we use billing type for contract start and end date .
I think as soon as i'm changing the dates in billing plan tab system is proposing another line item with different billing dates and that is not getting covered under deferred account that is still unbilled amount .
Waiting for your valuable inputs.
In case of any clarification kindly revert to me.
Thanks,
Ujjawal
Edited by: Ujjawal Singh Karki on Jan 20, 2011 11:10 AM

Revenue recognition and error message" Missing data: Provision account Message no. VU019

Hi,
I have configured revenue recognition type "B" for my item categories and I am using BOMs where pricing is set at item level. The issue is that when I have more than one components in my BOM then I get an error message (Missing data: Provision account Message no. VU019) at the time of saving sales order though I have configured the provision account. However If I enter the same component/material in the sales order without BOM which will have same pricing data then it does not through the above error message. Please help what could be the potential issue.
Best Regards
Javed

Have you checked the Analysis from condition tab once you created a BOM? If so, what is the message you could see for pricing.
G. Lakshmipathi

Revenue Recognition Category after Credit memo request generation via BAPI

Hi all,
I have used the BAPi " SD_SALESDOCUMENT_CREATE" to generate Credit Memo Request. After the generaion of the credit memo request the Revenue Recognition Catrgory [ "RR_RELTYP"(Data Element) ] is not determined. Can anyone let me know what are all to be filled to this BAPI for this field to get populated.

Hello Mr. Shiva Ram,
First of all thanks a lot for your help.The problem of credit memo is now solved but to resolve the status of the existing sales order documents as per your suggestion we have run the program SDVBUK00 in SA38.Still we didn't get the desired result as the status of the completed normal sales orders are still showing "Being Processed" even after running the program.
Please suggest what else need to be done to change the status of the completed sales documents till invoice.
Regards
Priyanka Mitra

Revenue Recognition with RA on Service Contracts

We have configured SD Revenue Recognition function (ECC 5.0). We have warranty maintenance contracts running. On this basis we have the following scenario and issue.
The warranty maintenance contracts are created without a billing plan (Reqmt. type SE so that we can settle costs later). The value of which is transferred to Deferred Revenue Account and is recognised at the end of the contract period (As it bears the retention money with the customer). Until this step things are working fine. We use VF44 to recognise revenues.
However, there are costs incurred (both material & labour) in relation to such contracts. To track this, we create a Service Order s against the Service Contract for each month. Later on fulfillment, the orders are settled to the Service Contract. This is reflecting in the Service Order. But the finance team wants to recognise the revenues to the extent of costs incurred. I'm not sure how we can do this. The following is an example scenario.
Contract Value : $1000
Contract period : 1 yr (1.1.2010 to 31.12.2010)
Contract billed at the start of the year on 1.1.2010 so the amount is moved to Revenue Provision (Deferred Revenue)
At the end of the year $1000 lying in Deferred Revenue will be moved to Revenue Account through Revenue Recognition (VF44)
Now, costs incurred as follows which are booked in separate service orders against the contract and on completion, settled to the contract. There is no definite schedule for these costs.
Apr 2010 : $100
Jun 2010 : $200
Sep 2010 : $500
Now, the finance team wants to recognise revenue to this extent during the relevant periods. For eg.
Apr 2010 :
Deferred Revenue A/c $100
To Revenue A/c $100
Jun 2010 :
Deferred Revenue A/c $200
To Revenue A/c $200
Sep 2010 :
Deferred Revenue A/c $500
To Revenue A/c $500
And at the end of Dec 2010 :
Deferred Revenue A/c $200
To Revenue A/c $200
(for the remaining amount)
Can anyone guide me how this can be achieved? Can I do it by running RA on Service Contracts?
Thanks in advance.
Ravi.

One option:
This is how we do it in my company. This scenario is of committed services where biling is based on bill plan but revenue is as incurred. So you will bill 100% in advance to have a deferred position but evey month you calculate the service delivered/incurred and recognize the revenue reference to that service. You have to deliver the equivalent hours (To match the amount you want to recognize) and the VF44 based on delivery document. You might have to adjust your ETC based on the amount you want to recognize every month and the total qyantity to deliver.
In summary, basically you use following steps:
1. Sales order with delivery related item category (Assigned to service contract, in my case we use WBS).
2. VF04 for billing as per plan
3. VL01N to deliver the quantity matching the amount
4. VF44 with reference to delivery.
Item category has revenue recognition 'B'.
Hope it gives some idea.
Thanks.
Rahul

Revenue recognition BAPI/FM

Hi all,
Can any one share the BAPI name or any function module to post revenue recognition (VF44)
Thanks
Chandra

hii chandra,
FM SD_REV_REC_BILLING
I found the following BTEs:
00503101 Revenue realization: Copy conditions
00503102 Revenue realization: Start/end of selection period
00503103 Revenue realization: Determine selection period
00503104 Revenue realization: Billing <-> FI document VF47
00503105 Revenue realization: Forecast revenue lines
00503106 Revenue realization: Revenue amount adjustment
00503107 Revenue realization: Det. Acct Non-Billed Receiv.
00503108 Revenue realization: Layout
00503109 Revenue realization: Enter split criterion
00503110 Revenue realization: Change accounting data
00503111 Revenue realization: Change document date/type
00503113 Revenue Realization: Status Change
00503114 Revenue Realization:Additional Value/Quantity Flds
00503115 Revenue Realization: Set Exchange Rate Date
00503103 is called within FM SD_REV_REC_BILLING
regards,
Shweta

What is the Revenue recognition process ?

Hello Experts,
Could you explain the concept of "Revenue recognition" and what is the use of this process.
Thanks and Regards

Hi
Revenue recognition controls the posting period in which revenues are entered and their value.
Revenue recognition means that revenues can be posted in FI independently from the billing document (which normally posts to revenue accounts). This means that revenues can be posted before, during or after billing or a value that has already been billed can be distributed between various periods.
Revenues can be posted periodically or on the basis of specific events:
Standard revenue recognition means that the billing document posts directly to a revenue account. This posting is made without involving the Accrual Engine, i.e. without a revenue recognition process.
Periodic (time-related) revenue recognition means that the revenue from a sale is distributed and posted equally across the entire contract validity period. Billing posts to an accruals account here and revenues are first transfer posted to the revenue accounts in a second step.
Service-related revenue recognition means that the revenue is recognized as the result of an event such as a confirmation or a delivery. Billing also posts to an accruals account here and revenues are first transfer posted to the revenue accounts in a second step.
to know the integration with ECC click on this
http://help.sap.com/saphelp_crm60/helpdata/en/45/f004d98b8f3481e10000000a1553f6/frameset.htm
Reward if helps
Regards
Manohar

Revenue recognition - deferred revenue

Hi Experts,
We want to recognize some of our revenues other than the billing date.
Some of our sales are by sea and using CIF incoterms, so if the goods was sent during the last days of the accounting period, we can not recognize it in the FI reports till the goods arrived it's destination.
So I want to do the PGI and the billing today and credit the deferred revenue account instead of the revenue account.
I saw the SPRO regards it.
1. What are the specific setting I have to use in "spro, sales and distribution, basic function, account assignment/costing, revenue recognition, set revenue recognition for item category" for this case? (time related/service related/billing related...etc)
2. Can I use regular sales order, delivery, PGI, billing document or do I have to use contract or something else?
3. Can the trigger be the incoterms/destination country instead of the item category?
Thanks
Ifer

Symptom
After you implement Note 1239165, the source code prerequisites for connecting the accruals account determination to the incompletion log in the standard system are met. This note describes the Customizing settings that you have to make to use the functions described in Note 1239165.
Other terms
Standard revenue realization, Customizing, incompletion, KONV, SAKN1, SAKN2, ZZ_RR_TVUVF, RV_INVOICE_ACCOUNT_DETERM, RR_ACCOUNT_MISS_DEF, RR_ACCOUNT_MISS_UNB, TVUVF, SAKUR, TVRRUR
Reason and Prerequisites
The Customizing settings are required to use an error group in revenue realization to specify the incompletion and to prevent the system creating subsequent documents.
Solution
Make the following settings:
1. Create the following procedures in Customizing:
Sales and Distribution -> Basic Functions -> Log of Incomplete Items -> Define Incompleteness Procedures -> Incompletion Group B (Sales - Item) -> Procedures ->
-> RR (text RevRec item). Save your entry.
2. For the accruals account, create the following status group:
Sales and Distribution -> Basic Functions -> Log of Incomplete Items -> Define Status Groups
-> Status grp General Delivery Billing doc. Price Goods movement
   RR        X        X         X             X
Additional information: The revenue accounts are assigned to the status group 00 through the error group "MP". This status group permits subsequent documents to be created.
3. It is not necessary to assign the incompletion procedure RR to the item category that is relevant for revenue recognition. In the case of item categories that are relevant for account determination, by default, the system uses the error group "MP" for the revenue accounts and the error group "RR" for the accruals accounts.
4. Create the report ZZ_RR_TVUVF to execute the entries required to check the fields and to assign the status groups. The report enters the required entries in the tables and in TVUVF. If these already exist, the system issues an error message.
The following check fields and status groups are entered:
Table     Field name Description   Screen Status Warning Rank
KONV SAKN2    accruals account          PKON RR
TVRRUR SAKUR    unbilled receivable account       RR
Attributes
Title: Insert/delete RR incompletion settings in TVUV and TVUVF
Type: 1 (Executable program)
Status: T (Test program)
Application: V (Sales and Distribution)
Package: (Customer-specific package)
Selection texts
P_DELKZ Delete revenue recognition records
P_INSKZ Create revenue recognition records
The source code is provided in the attached correction instructions.
Insert Block
*& Report ZZ_RR_TVUVF                                                 *
report zz_rr_tvuvf.
Tables *
tables: tvuvf.
Work areas *
data: begin of gvt_tvuvf occurs 0.
        include structure tvuvf.
data: end of gvt_tvuvf.
data: lvf_subrc1 like sy-subrc,
      lvf_subrc2 like sy-subrc.
data: gvs_tvuvf like tvuvf.
======================================================================
Definition of the selection screen                                   *
======================================================================
parameters p_inskz radiobutton group act.
parameters p_delkz radiobutton group act.
======================================================================
Initialization                                                       *
======================================================================
initialization.
clear   gvt_tvuvf.
refresh gvt_tvuvf.
======================================================================
Selection of data                                                    *
======================================================================
start-of-selection.
select single * from tvuvf into gvs_tvuvf
                            where fehgr = 'RR'.
                            and tbnam = 'KONV'
                            and fdnam = 'SAKN2'
                            and statg = 'RR'
                            and fcode = 'PKON'.
lvf_subrc1 = sy-subrc.
select single * from tvuvf into gvs_tvuvf
                            where fehgr = 'RR'.
                            and tbnam = 'TVRRUR'
                            and fdnam = 'SAKUR'
                            and statg = 'RR'
                            and fcode = '    '.
lvf_subrc2 = sy-subrc.
Populate fields
gvt_tvuvf-mandt = sy-mandt.
gvt_tvuvf-fehgr = 'RR'.
gvt_tvuvf-tbnam = 'KONV'.
gvt_tvuvf-fdnam = 'SAKN2'.
gvt_tvuvf-statg = 'RR'.
gvt_tvuvf-fcode = 'PKON'.
append gvt_tvuvf.
clear gvt_tvuvf.
gvt_tvuvf-mandt = sy-mandt.
gvt_tvuvf-fehgr = 'RR'.
gvt_tvuvf-tbnam = 'TVRRUR'.
gvt_tvuvf-fdnam = 'SAKUR'.
gvt_tvuvf-statg = 'RR'.
gvt_tvuvf-fcode = '    '.
append gvt_tvuvf.
clear gvt_tvuvf.
insert case
if not p_inskz is initial.
    if not lvf_subrc1 is initial and
       not lvf_subrc2 is initial.
    insert line
      insert tvuvf from table gvt_tvuvf.
      if sy-subrc is initial.
      line already there
        write: 'Line in table TVUVF inserted'.
      else.
      Error when insert
        write: 'Insert not possible'.
      endif.
    else.
    line already there
      write: 'At least one entry already in the table TVUVF'.
    endif.
else.
delete case
    if not p_delkz is initial.
      if lvf_subrc1 is initial
      and lvf_subrc2 is initial.
      delete line
        delete tvuvf from table gvt_tvuvf.
        if sy-subrc is initial.
        line already there
          write: 'Lines in table TVUVF deleted'.
        else.
        error when insert
          write: 'Delete not possible'.
        endif.
      else.
      line not there
        write: 'At least one entry not in the table TVUVF'.
      endif.
    endif.
endif.
See you Monday

Revenue Recognition based on percentage of completion of work.

Hello Experts,
My customer has the following scenario for revenue recognition.
My customer sell services. So I create a project and attach to the sales contract which has mile stones for billing.
After completion of milestones, billing is triggered automatically. No issues on this part.
When comes to revenue recogntion, they recognise the revenue after the work completion and nothing related to billing.
They take forecasted manhours(planned hours) for the services and take the time sheet hours (actual hours) and calculate the percentage of completion. They apply the percentage in revenue and based on the percentage of completion, they do revenue recognition.
My questions..
1. Is this a standard functionality in SAP? My customer is in sap 4.7
2. If this is not a standard functionality, then how to tackle this issue. Is there any work around?
Any type of help would be grateful.
Regards
Srinivasan Desingh

Hello,
The Best Practices document alongwith the scenarios supported in standard SAP is available as an attachment in the Note 1172799.
Regards,
Raghavendra YN

Multiple Revenue Recognition Methods on a Project(Task Level)

We have projects where certain portion of revenue is recognized based on events(ex: equipment shipment) and certain portion is recognized as cost is incurred(Percentage of Completion).
In Oracle Projects we can have only one Distribution rule for Revenue per project and doesn't allow to have different Revenue distribution rule at the task level.
Business case: Project is for Equipment and Additional Service is purchased, separate tasks are created for Equipment(Task#10) and Service(Task#20).
Billing is based on Events.
Equipment(task#10) revenue is recognized based on order line shipment(event created),
revenue for Service(task#20) is recognized as Cost is incurred to perform the Service, based on POC calculation.
Following is what we tried as Proof Of Concept:
Funding is at Task Level (set at Project Type), Baseline Funding without Budget is enabled(i.e Revenue budgets are created when funding is baselined)
Billing extension Cost-to-Cost Revenue is assigned on project type, Forecast Cost Budget is used in calculations
Set the distribution rule on project to COST/EVENT
On tasks for Equipment(Task 10), we entered $0 Forecast cost budget
On tasks for Service(Task 20) we entered a $$ Amount(non zero) for Forecast Cost budgets.
Task 10( Equipment - Event based revenue), $0 Cost budget
Create Costs on task 10, Distribute, Account, run the processes to generate revenue
Create a manual revenue event for equipment shipment
Revenue events from Billing extension are not generated, since there is no cost budget, Revenue is generated only for the manual event we created - This works as expected.
Task 20(Service - POC based revenue), Cost budget is $10000 (for ex:)
Create Costs on task 20, Distribute, Account, run the processes to generate revenue
Automatic Revenue events from Billing extension(Cost-to-Cost Revenue) are generated, since there is cost budget, Revenue is generated based on POC calculation.
Questions:
With the assumption that we will not maintain forecast cost budgets for equipment tasks and use the standard Cost-to-Cost Revenue extension.
We would like to know what is the impact of the above solution option on standard Project Billing functionality and any others.
Any other workarounds to achieve what we are looking for(i.e multiple revenue recognition methods on a project)
How others achieved similar business requirement with Oracle Projects(At present we are creating a 2nd project for Service component) and it has it's cons(consolidated billing etc, since we will be funding 2 projects)
Harish

Dear Harish,
I am not sure i have a perfect solution but you can try this.
Set Billing extension to Cost/Event (Percent complete revenue) this will be used for all the scenarios where revenue should be recognised by the system like Ex: Task20
Use Pre-Approved batches for rest of transactions where the cost directly effects the Project.
Regards
Shaan

Revenue Recognition Analytic xApp misses standard BAPIs / Services

Similar Messages

Maybe you are looking for