No FI docs despite revenue recognition status 'C' in VBREVE

Hi,
We have issue in revenue recognition tables. After the VF44 run the VBREVE-RRSTA is updated with 'C' and but no FI documents are created. Even the CRN is updated in VBREVE table.
We are using SAP 6.0. The note provided by SAP '414947' is not valid for 6.0 . In that its mentioned after 4.7 its fixed but still we have issue in 6.0
Can you help me to get the latest note for the fix.
Thanks
Shantha

Hi Shantha
Welcome to SDN Forum
Refer the following SAP Notes
SAP Note 819805
SAP Note 810480
Regards
Srinath

Similar Messages

Not able to delete a delivery after revenue recognition is reversed

Hello Gurus,
We have a situation for certain Sales Order types after creation of Sales Order -> Delivery and PGI, we do revenue recognition. But there was some mistake and delivery needed to be deleted and recreated if needed. So after doing revenue recognition reversal we are reversing the PGI. After this when we try to delete the Delivery ( which would have got deleted if there was no revenue recognition process ) we get the below error.
Is it a problem with the way Revenue recognition is configured or does the standard behave like this. If the Invoice is also present in the above I am able to cancel the Invoice. If you think its a problem with the way Revenue reccognition is configured please advise.
Item 000010 cannot be deleted (revenue recognition status)
Message no. VL896
Diagnosis
The delivery or delivery item cannot be deleted.
System response
The document cannot be deleted since the delivery contains items that
reference sales document items that are relevant for revenue
recognition. When the goods issue was posted, the system created revenue
lines that had already been recognized. This means that there are
subsequent documents in revenue recognition for this delivery.
Procedure
If you no longer require the delivery or delivery item for deletion, set
the delivery quantities to zero and repost the goods issue. Make sure
that the quantity zero is allowed in Customizing for the delivery item
category. When the goods issue is posted, the overall processing status
is set to C and the delivery can be archived. Message determination
should be configured not to send any messages in this case. To make sure
that the system makes revenue corrections if there are differences
vbetween billed and recognized values, set a billing-relevant rejection
reason in the sales document item if more than one partial delivery is
allowed.
If you still want to use the delivery, adjust the delivery quantities
accordingly. Alternatively, deliver the referencing sales document item
again. Note that the sales document item cannot be delivered again if
only a partial delivery is allowed.
What are the changes I can do to Delete the Delivery?
If I cannot Delete the Delivery, Should I make the Delivery as 0 qty and create a new delivery with changed qty and do further process. Or should I reject the Sales Order and create a new sales order with exact qty and do further process.
Please advise.
Regards,
SNK.
Delivery has one line item. For the above case scenario, invoice is there for some deliveries and for some deliveries there is no invoice. Eg: SO -> DN -> PGI -> Rev Recog -> Iv or SO -> DN -> PGI -> Rev Recog. Requirement was SO was wrongly created as the qty was wrong or in some cases SO needs to be rejected. I am able to cancel Invoice. Rev recog is reversed. PGI is cancelled by VL09. Not able to delete Delivery and I get the above error. Ideally I thought since Rev recog is reversed, Delivery should have been deleted but not happening and above error comes.
SO - Sales Order DN - Delivery IV - Invoice
Edited by: sapconsultnt on Dec 16, 2009 5:06 AM

Hello,
Please review the Note 1224871 which introduced this functionality.
Regards,
Raghavendra YN

Revenue Recognition based on User Status of assigned Sales Order line item

Dear Community members,
We have requirement to recognize / de-recognize revenue posted to WBS for calculation of RA, based on the 'User status' of the assigned Sales Order line item.
To elaborate requirement further -
1) WBS Element - XXX - 10 ( with operative indicator - Plan/Bill/Account Assign)
2) Sales Order(SO) Line Items assigned to the above WBS -
- SO No - 123 Line Item 10 - Actual Rev - $ 300 - User Status - EXE (Meaning this work is in progress , partial payment received thus actual revenue for RA at WBS is 'Zero'
- SO No - 124 Line Item 20 - Actual Rev - $ 400 - User Status - COMPL(Meaning this work is Complete , all payment received thus actual revenue for RA at WBS is $400
- SO No - 125 Line Item 10 - Actual Rev - $ 800 - User Status - EXE (Meaning this work is in progress , partial payment received thus actual revenue for RA at WBS is 'Zero'
As per WBS reports Actual Revenue posted to WBS XXX-10 is $ 1500 ( $300$400$800) , however since two SO line items ( SO 123 /line item 10 and SO 125 / line Item 10 ) are NOT having User status 'COMPLETE', the actual revenue posted by those line items $ 1100/- ($300 + 800) should not be included as Actual Revenue for RA at WBS level.
Thus Actual Revenue for RA at WBS XXX-10 should be $ 400 /- ( the revenue posted by SO 124/line item 20 which has user status as 'COMPLETE')
How do above can be achieved?? Is there any standard solution for this?? Is any SAP Note available for this (I too am looking for one but not found any ) ?? do we need any enhancement , Customer exit etc
Thanks in advance
with regards

Hi,
Thanks. You are right that the 'Completed Contract Method' would defer revenue recognition. However, the status checked would be of the RA object (WBS Element in this case, as RA key is on WBS and RA is being calculated on the WBS).
However, our requirement is to check the user status of the Sales Order Line items assigned to the WBS element and filter the revenues posted based on the active user status of individual Sales Order Line item.
Please give you inputs.
Thanks in advance
With regards

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 (AR Closed for future month in error)

Need help with revenue recognition. In the month of June in AR July was opened in error, so it was put in to close pending. Since July was closed the last 3 days worth of June invoices did not have any revenue recognition for July. Instead July's revenue was posted in to August since August was showing as a future period, and July was closed. Is there any fix to change the revenue recognition without doing a credit and rebill of 3 days worth of invoicing? If we reopen June, and run revenue recognition again, will that help? Thanks in advance for any help.

Well there are a few ways you can go ahead and fix this, but it depends on lot of factors.
Lets say you have 1 invoice for which the revenue has been recognized in August and not July, now you can query up that invoice in the transaction's workbench and incomplete it. After incompleting all the revenue recognized distributions would be deleted(applicable 11.5.10 onwards) and when you complete the invoice again & run the RR program the revenue would be recognized in July(provided it's in an open status). Please note though that you can incomplete a transaction only if it doesn't have any activity against it!
Now coming to the real world it's possible that the number of transaction's you have could be quite large and doing this manually through the screen might not be feasible. So you could possibly write a small pl/sql script to loop through those invoice's and incomplete them by calling the complete/incomplete group transaction's api. And then again complete them and re-run RR program to complete the fix.
Please note though that you can incomplete a transaction only if it doesn't have any activity against it!
With posted transaction's or transaction's having other activity, it's possible to fix them too but that would be taking things too far and Oracle Support/Development would be best equipped to provide you the fix in that scenario.
HTH,
Jasmeet.

Price Change for Revenue Recognition

Dear experts,
I am using Revenue Recognition of type B with Revenue Recognition before invoicing.
I have an issue/question about the way price changes are treated in the functionality.
The below example is used to describe the issue for your understanding:
1.Pricing master data: $100/EA
2.Price of item in sales order: $100/EA
3.Qty in sales order: 10 EA
4.Delivery & Goods issue: 10 EA
5.Revenue Recognised (VF44) for: $1000
Accounting Entry:
DR Unbilled Accounts Receivable $1000
CR Revenue $1000
6.Change in pricing master data: $120/EA
7.Partial Invoice for: 2 EA @ $120/EA
Accounting Entry:
DR Customer $240
CR Unbilled Accounts Receivable $240
8.Partial Invoice for balance qty: 8 EA @ $120/EA
Accounting Entry:
DR Customer $960
CR Unbilled Accounts Receivable $760
CR Deferred revenue $200
9.Subsequent Revenue Recognition (VF44)
Accounting Entry:
DR Deferred revenue $200
CR Revenue $200
As you can see in the example above, the amount of the price difference is not credited to sales in step 7. From what I have seen so far the additional amount due to price difference gets credited to sales only after the total invoice value for the item exceeds the revenue recognized.
Is there any option to set the system so that the price difference is taken into account for revenue recognition during each invoicing (even
when the invoicing is partial) ?
Thanks in advance for your help.

The price difference will not go to Sales in Step 7. The reason being Revenue Recognition works on the item rather than the amount. Since you have run F-44, the system finds the same in Unbilled Receivables and posts to that account.
For updating the price changes, you have to run VF46 to cancel the original RR entries. In this case, it will just clear of the RR lines if realization has not happened and post a reversal if realization has happened. This txn will also create a new RR line for VF44 which you can process.
Refer Note 820417 Implementation guide for RR. Download the attachments and look into Part2 doc page 13. This explains how to deal with price changes in sales document.
Hope this helps.
Ravi.

Config of billing type G2 for Revenue Recognition

Hello Experts.
I have a situation where I need to configure billing of credits for revenue recognition.
For normal builling we have copied doc type SO to ZBCS and added ZTAD item category (copied from TAD) for the RR.
To do this for credits I copied doctype CR to ZBCR and assigned ZTAD item category to it.
When billing the ZBCR not I get the message "Item category ZBCR ZTAD cannot be invoiced with billing type G2".
How can G2 be configured to allow this?
This is G2's current setup.
Billing Type G 2 C red tM e m o Created by
Number systems
No.range int.assgt. 19 Item no.increment 0
General control
SD document categ. O C re dit m emo Posting Block
Transaction group 7 B il lin g doc um ent s Statistics
Billing category
Document type DG C us tom er cr ed it me mo
Negative posting N o neg at ive p ost in g
Branch/Head office C us tom er =Pa ye r/B ra nch =s old -t o p ar ty
Credit memo w/ValDat N o
Invoice list type
Rebate settlement Rel.for rebate
AcctDetermProc. KOF I0 0 A cco unt De e rm n ato n
Doc. pric. procedure
Acc. det. rec. acc.
Acc. det. cash. set.
Acc. det. pay. cards
Output/partners/texts
Output determ.proc. Z10 00 0 B il lin g Out pu t Application V 3
Item output proc.
Output Type
Header partners FK B iln g D ocu m en t
Item partners FP B il lin g Ite m
TextDetermProcedure 03 Invo c e hea de r
Text determ.proc.itm
Delivery text

Hi,
You may be maually given the PR00 in ZBCR. But in your copy control (VTFA) --> item category ZTAD --> pricing type, you may be maintained B (Carry out new pricing).
If you maintain B, you have to change it to "D ".
When you maintain B, the system will search the Pricing again in Credit memo. All manual prices will be lost.
Thanks
M. Lakshmi Narasimhan

Revenu recognition options grayed up

Hi
We are facing an issue with the SPRO Revenu recognition options which are grayed up, which does not allow to select any values. We have allowed all the authorization etc. but no luck. Follows the procedure to see those option :
TC- SPRO --> SAP Reference IMG --> Sales and Distribution --> Basic Functions -->
Account Assignment/Costing --> Revenue Recognition -->
Click on Set Revenu Recognition For item Categories --> It shows the ItCa and Description column --> I click on change option and then double click any of them (eg. AES in ItCa column --> Click on change and when try to enter the value for any of the Business Data ie. 1) Rev. recognition, 2)Acc. period start, and 3) Revenu Dist (These options are grayed up and does not allow to select any the entry in fact the right check mark is also grayed up.
Any solution would be highly appreciated, as its very urgent in our production system.
Thanks and Regards
Abdul Majid

Hi Majid,
What's your client status ? Is it set to modifiable.
Cheers
Deepanshu

Revenue recognition job hangs and needs reboot of servers

We are on SAP BPC v7.0 SP6.1, using Microsoft Office 2007 and Internet Explorer 7. We have two environments - Production and QA. Production so far is running fine; QA is on a smaller environment.
I am an application user and load final production files into QA each month. For the past two months when trying to run the revenue recognition job for April 2010 and again for May 2010, the job just hangs where it would normally take about two minutes to complete. Both times it was the only job running at the time, as no one was using the QA environment. I had to terminate the job (which might leave the job running in the background) and have our Server team reboot our two servers (Application and SQL Server Analysis Services). Then the revenue recognition job completes.
Depending if I terminate and resubmit the revenue recognition job, I might get the following detail log message:
Execute formulasError
Failed to commit transaction
1 errors writing data
Send through SendGovenor failed
Last week, our DBA set the QA databases to Simple instead of Full recovery and shrank the transaction log files. I ran a test revenue recognition for July 2010 and the DBA tried to monitor the environment, but he could not see any job committing or any activity on the database. I ended up rebooting our servers to complete the test.
Has anyone experience similar problems and was able to resolve it. Any ideas would be appreciated. Thanks.
Bucky

Hi Sorin Radulescu,
I load the initial billing file using the Import logic script and select the data file and transformation file. I click on the Merge data values option; click No to run default logic; and click No, do not check work status settings. Once the import completes, I run the revenue recognition logic for the accounts and periods I am working with.
I compared our Production transformation file, default logic script (which I am not running), and revenue recognition logic script to QA and they both match. My problem is when I run the exact same revenue recognition job in QA, the job just sits in running status but should finish in a couple of minutes. I would let it run for a couple of hours in QA, then terminate the job and have our two servers rebooted, then the same revenue recognition job runs to completion within a couple of minutes.
I am just wondering if there could be some other setting that does not let the job submission kick off the actual update to the database. To make sure the database was not hosed from the terminated revenue recognition job, I ran a different but smaller job and it completed. Then I would ask for the reboot and resubmit the revenue recognition job and it completes.
I will let our DBA know about monitoring the dllhost.exe for amount of memory used. But the last time he tried to check for any activity on the database he could not see anything, but I do not know if he was checking dllhost.exe or some other files.
Thanks for your response and suggestions. Since this is our QA environment (which I try to keep current with Production), I am trying to see if I can identify the cause and fix it, in case it carryover to our Production environment.
Regards,
Bucky

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

Revenue Recognition user-exit documentation

Hi SD Gurus,
Does anyone have any documentation on below mentioned user-exits for Revenue Recognition. For e.g. how they are used, scenarios, examples etc. would be of great help.
Event      Description
00503101      Revenue realization: Copy conditions
00503102      Revenue realization: Start/end of selection period
00503103     Revenue realization: Determine selection period
00503104     Revenue realization: Billing u2013 FI document
00503105      Revenue realization: Forecast revenue lines
00503106     Revenue realization: Revenue amount adjustment
00503107      Revenue realization: Act determ.of non-billed rec.
00503108      Revenue realization: Display variants
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 Fields
00503115     Revenue realization: Set Exchange Rate Date
00503116     Revenue realization: Compression Data SD/FI             0
Thank You.
Regards,
Amit

Hi,
check following link
http://****************/Tutorials/ExitsBADIs/ExitsMain.htm
Regards,
Madhu

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

Help on Revenue Recognition

Hello Friends,
I’m hoping someone can help me in answering the following questions.
Example of a bundle solution that includes product license, education and consulting services. One parent SKU that auto-explodes into three child SKUs – product, education, consulting.
1. Booked revenue is allocated to one PL (based on parent SKU). Do we need to create a new unique PL? Can this be re-allocated to 3 PLs? How is this done?
Example of a Education blended offering which includes different delivery methods – ILT, video-ILT, eLibrary (WBT modules) and certification. One parent SKU that auto-explodes into the child SKUs. Each child SKU will trigger the appropriate behavior similar to the standalone offering. Customer will need to get a voucher for each component to redeem against.
2. Can we still track revenue for each delivery method and certification by the child SKU? If not, why not and how can this be done?
3. Will revenue recognition be handled separately for each component (child SKU) or as part of the bundle, by the parent SKU. For example, we send the customer a voucher for each component, sometime revenue can be recognized when the voucher is sent to the customer (eg. WBT can recognize revenue immediately once the voucher is sent to the customer).
4. Issues/requirements we need to be aware when setting this up?
Thanks for all the help...
Vijay

Hi
But the error is related to controlling . Just go to OKKP and check wheather you have checked in the controlling area properly or not
make the following down payment configurations
item category group - 0005
item category - TAO
for this TAO item category a billing plan 01 (milestone billing plan -01) will be assigned and its billing relevance should be I which is order related billing .
billing doc type - FAZ
cancellation billing doc type - FAS
maintain a condition type AZWR which is down payment settlement , it has requirement as 2 and calc type as 48 acct key as ERL
Now when you enter a material in line item 10 and go to item data , you can see the billing plan tab.
now go to billing plan tab and enter the start date and enter the dates on which billing has to be done and then in billing request enter 0009 which is for down payment.once u press enter automatically it all the dates get blocked and billing request by default you get as 1 , that you change it to 4 or 5 . 4 is for down payment at value basis and 5 is for down payment at percentage basis. and beside that there will be a billing type .assign billing doc type as FAZ. to all dates
check the copying requirements are there at VTFA as 20 and for item category TAO copying requirements 23 is maintained or not
now do the cycle OR - LF - FAZ (billing doc type)
Regards
Srinath

VF44 - revenue recognition error

while running VF44 (revenue recognition) run message is displaying 'Accrual period not determined for doc. 16343 000010; no revenue dist. possible.
If i were not wrong then in sales order >>accounting tab>the posting periods fields are blank ,for this reason might revenue list is not possible.
In item category i maintaed revenue recognition based on time related data in place of standard .
kindly look into matter.
Sourabh Singh

Hello Sourabh,
We had similar problem
The solution would be in the SAP Note: 879439
Regards,
Hemachandra K S
Don't forget to to reward points by marking as "Helpful" or "Very Helpful" or "Solved problem".

Revenue recognition error

Hi!
I'm having some problem setting up revenue recognition.
When I go to trans. VF44 to post the revenue I get this error log:
- Accounting document for collective processing 1000000005 was not created
- Incorrect doc.no.: $ 1. Select document number between 0090000000 and 0099999999
The document number you specified, "&v1", is not in the
appropriate number range. The number range is dependent on
the document type.
The exception to this rule is formed by recurring entry
documents, which must use number range 'X1' and sample
documents, which must use number range 'X2'.
Possible reasons for this error message are:
o   You have entered an incorrect document number.
o   An incorrect document number was transferred to this
     application during an update from another application
     (e.g. CO).
Any ideas?
Regards.
Eduardo

Hi check the number ranges of all the documents involved. What happens is that normally the accounting document is the same as the billing document. But sometimes FI consultants do not necessarily take this approach.

No FI docs despite revenue recognition status 'C' in VBREVE

Similar Messages

Maybe you are looking for