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

Similar Messages

To trigger the user exit EXIT_RMMR1MRB_001

Hi all,
When I keep a breakpoint in the exit EXIT_RMMR1MRB_001 and run the transaction MIRO, it is not going to this user exit .
The field entered are
Invoice date,posting date,reference ,amount,purchasing doc number,baseline date ,payment terms,payment method and NF type.
But it is not trigerring the MIRO. In the user exit documentation ,it is given that this user exit will call only if EF_CHANGE = 'X'.
1) So can you please mention which field does it corresponds to in MIRO transaction?
Kindly help me so...
Thanks in advance
Points will be rewarded

Hi ,
Following are some of the user exit that you can consider for Invoice verification.
LMR1M001 - User exits in Logistics Invoice Verification
LMR1M004 - Logistics Invoice Verification: item text for follow-on docs
MM08R002 - User exit for tolerance checks
Function EXIT_RMMR1MRB_001 - This is called only by report RMMR1MRB
Regards
Sriram

As01 transaction using substitution user exit populate classificaion

Hi all,
I have a requirement, where in using the substitution user exit rule U210, I need to populate fields ANLB-NDPER, ANLB-NDJAR and ALNA-VMGLI from the values maintained in Ztable.
I am able to overwrite the SAP standard values for the fields ANLB-NDPER and ANLB-NDJAR. But not able to populate the filed VMGLI(Classification key).
For some asset classes, the classification key is not mandatory and the user without giving the value in that field if save the transaction, then I need to populate the value of VMGLI with the ztable value.
The present rule U210 is not working for classification key.
Please suggest, is there any other user exit for the scenario where we can populate VBGLI field.
regards
Rajani Yeluri

In the user exit documentation, it doesn't say anything about this exit being used for validation, therefore, it probably shouldn't be used as a validation routine, especially if its not being trigger at every PAI.
<i>FU EXIT_SAPLAISA_001
Short text
Assign Inventory Number
Functionality
Using this user exit, it is possible to assign an inventory number when you create a new asset master record.
Notes
In the user exit, it is absolutely forbidden to use a statement that leads to an update or removal of database changes. Examples of such statements are:
'Commit Work' , 'Rollback Work' or call of function module 'DB_COMMIT'.
Parameter
I_ANLA
E_INVNR
Exceptions
Function group
XAIS</i>
Regards,
Rich Heilman

User exit MB_CF001 in MIGO

Folks,
I am using the user exit MB_CF001 to get the data from XMSEG table and send it to an external system. I was asked to call an RFC function module in this user exit to send the XMSEG data to an external system but the user exit documentation clearly says not to use RFC function call in this user exit.
I also heard that I can do this by using the idocs that get posted after MIGO is done. Could anyone give me step by step procedure how to do this as I am new to IDOCS.
Points will be rewarded for best answers.
Thanks,
Alok

Dear Alok,
Below is a documentation about IDOCs. Hope it will be useful to you.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Important links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
>SAP ALE & IDOC
Steps to configuration(Basis)
>>1. Create Logical System (LS) for each applicable ALE-enabled client
>>2. Link client to Logical System on the respective servers
>>3. Create background user, to be used by ALE(with authorizaton for ALE postings)
>>4. Create RFC Destinations(SM59)
>>5. Ports in Idoc processing(WE21)
>>6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
>Steps to customize a new IDoc
>>1. Define IDoc Segment (WE31)
>>2. Convert Segments into an IDoc type (WE30)
>>3. Create a Message Type (WE81)
>>4. Create valid Combination of Message & IDoc type(WE82)
>>5. Define Processing Code(WE41 for OUT / WE42 for IN)
>>6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Best Regards,
Rajesh.
Please reward points if found helpful.

User Exit Transaction AS01 and AS02

Hi Everybody,
I found the user exit EXIT_SAPLAISA_001 for transaction AS01 and AS02. When i save data in transaction AS02, i can validate it before save, using error messages. But when the data is validated in transaction AS01 the user exit only show the error messages the first time that the user push the button save and not the next times. ¿How can i validate all the times that the user push the save button in transaction AS01?
Thanks

In the user exit documentation, it doesn't say anything about this exit being used for validation, therefore, it probably shouldn't be used as a validation routine, especially if its not being trigger at every PAI.
<i>FU EXIT_SAPLAISA_001
Short text
Assign Inventory Number
Functionality
Using this user exit, it is possible to assign an inventory number when you create a new asset master record.
Notes
In the user exit, it is absolutely forbidden to use a statement that leads to an update or removal of database changes. Examples of such statements are:
'Commit Work' , 'Rollback Work' or call of function module 'DB_COMMIT'.
Parameter
I_ANLA
E_INVNR
Exceptions
Function group
XAIS</i>
Regards,
Rich Heilman

GATP User Exit EXIT_/SAPAPO/SAPLATPR_002

Hi
I am planning to use the user exit EXIT_/SAPAPO/SAPLATPR_002 which is used to modify/change the results of rules evaluation. In the user exit documentation it is mentioned that the user exit is called more than once. In case you have used this user exit can you explain why this happens and if there is a way to avoid this.
Rajiv

Rajiv,
I think I am in same situation as you were.
Can you please explain me the scenario (what made you change the rule evaluation results) and config you did to achieve the objective?
Thanks

Revenue Recognition BADI or user exit or BTE

Hi Experts,
We do have a requirement where once a Payment is processed through F-28 Transaction, the system should automatically release the Revenue Recognition Block ( Table VBREVE - Field REVPOBLCK ) on the Billing DOcument. Currently it is getting cleared manually through VA44 transaction. We need to Make the process automatic. Any user exit or BADI or BTE available for the same?
Thanks
Tirthankar

you could check the business transaction events (Transaction FIBF)
mainly the Process-BTE's 00001120 or 00001140.
Guess they are processed in the F-28 like in other FI-transactions

User exit for revenue recognition VF44

Subject changed by moderator. Please use informative subject in future
I am trying to find a user exit for revenue recognition tcode : VF44. Can anybody help me in finding one. I have a program to find user exits. But it couldnt list any userexit or badi.
Can anybody shed light on this.
Best Regards.
Edited by: Matt on Jan 16, 2009 11:31 AM

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

User exit to Change Accrual period in revenue recognition

Hi All ,
I have requirement to change the accrual period while revenue posting from VF44 in collective processing from 365 days to static 12 months .
Need help finding the rigth user exit and approach .
Thanks in advance
vinay

Hi Amuktha ,
Look s like I have to implement a Bussiness transaction event OUTBOUND_CALL_00503103_E
the program LVFRR069 , I found below lines
    If accrual period start date and/or end date has been changed
    through userexit 'OUTBOUND_CALL_00503102_E' forecarst lines are
    created in single step mode
      if pif_accpd_start ne lvf_fplt_start or
         pif_accpd_end   ne lvf_fplt_end.
Need help in implemeting this .
thanks
Vinay

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

Any BTE/Exit for Block/ Unblock Revenue Recognition using VBREVEu2013REVPOBLCK

Hi Experts,
         I have a requirement to block/unblock SD based Revenue Recognition by changing the value of VBREVEu2013REVPOBLCK in VA02/VA42 through any available user-exit/BTE. On input side I need VBAP and VBREVK structure to give the criteria for blocking and unblocking. Depends on the certain criteria I need to change the value of VBREVEu2013REVPOBLCK to block/unblock.
On analysis I found that there is a similar BTE 00503113 which is having similar interface except, it has VBREVE u2013RRSTA, but I need VBREVEu2013REVPOBLCK as export parameter.
Could you please suggest some BTE/Used exits that may help me for this scenario?
Waiting for your valuable inputs
<removed by moderator>
Edited by: Thomas Zloch on Jun 2, 2011 10:29 PM

Create an implementation in this BADI - BADI_SD_REV_REC_PODEV
In this case you have a changing parameter: rrpodevcust
depending on the condition, you just need to change rrpodevcust-REVPOBLCK to X.
Include the following
    rrpodevcust-vbeln     = iv_salesdoc_number.
    rrpodevcust-posnr     = iv_salesdoc_item.
append rrpodevcust TO ct_rrpodevcust.
check vbreve table and see if it updates the field.

Missing English documentation for WPUE0002 enhancemnt user-exits

Hi all,
I'd like to change some segment fields data before processing IDoc type WPUWBW, and I thought user-exit EXIT_SAPLWPUE_141 from WPUE0002 enhancement could help me to do so.
But, when I search for documentation on this module it doesn't exist in English, only in German. How can I get it in English?
Or, anyone could tell me how to use it? Any examples?
Thanks very much in advance,
Maite.

Hello Maite,
just a brief summary of the documentation:
Function module to check and/or modify IDOCs, before the POS inbound processing
The original IDOC is transfered in table INPUT_IDOC_SEGMENTS of parameter I_INTERFACE. Only the modified segments have to be exported in table OUTPUT_CHANGED_IDOC_SEGMENTS.
Log of modifications (if not switched off via parameter O_NO_LOGGING_REQUIRED):
- EDI log - logs the modified segments (same as for modifications in EDI editor)
- POS log - logs the modifications for each field
   O_NO_LOGGING_REQUIRED =
   'P' write only POS log
   'X' write only EDI log
   'A' write minimum EDI log (one record per change transaction, independant from the no. of changes)
Use parameter O_STOP_IDOC_PROCESSING to stop the IDOC processing. POS-Status 4 "refused by system" is set for the IDOC. For IDOCs with POS status 4, the user can decide, to process the IDOC. In this case, the parameter shouldn't be set again. The import table I_INTERFACE-WPLST contains records with "VERBUCHUNG" (UPDATE?) = '4' for the segments, the user decided to process again.
When the IDOC has been processed, it cannot be refused completely. If parameter O_STOP_IDOC_PROCESSING is set in this case, the processing will be cancelled and message WP032 is written to the log.
Messages for the processing logs can be exported in table OUTPUT_ERROR_MESSAGES.
- Raising exceptions will cause a short dump. You can use MESSAGE ... RAISING to transfer error messages into the protocol.
- Commit work not allowed
- All database changes have to be done by update modules.
Best regards
Stephan

Regarding documentation on User Exits, IDOCS, Interfaces etc.

Hi Friends,
Can any one help me if any documentation on User Exits(MM/WM related), ALE IDOCS/ INTERFACES etc available which shall help in understanding the above concepts.
Quick help will be highly appreciated and rewarded pls.
Thanks in Advance
Regards,
Prasanna.

this info is spread though all channels SAP has, but unfortunatly not consistent, thats why it is so hard to find something.
You can find info at help.sap.com
e.g. this link (see the menu on the left as well)
http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/frameset.htm
Further you can find info at SAP MArketplace (OSS notes)
Or directly to the coding in SE37 and SE38.
IDOC and ALE documentation can be found here:
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
and
http://www.logosworld.com/www5/books/IDocBook/IDocBook.htm
Edited by: Jürgen L. on Oct 24, 2008 12:21 PM

Blocking Periodic Revenue recognition without billing block

Hi All,
I am posting here first time and need some help with Periodic Revenue Recpgnition.
We have scenario where User wants to control the Revenue Recognition based on some contingency flag in Sales Order. If that flag is set then Periodic monthly Rev. Recog should not happen but when user unsets that flag in SO line item then Rev Recog should happen.
I know for Service Based Rev Recog there is a solution SAP provides as Customer Event Type by which we can achieve this without stopping invoicing.
But i am not sure how to block the Rev Recog to occur for Periodic Rev Recog as Customer Event type is not configurable in Item Category with Time-Related Rev Recog (A).
Please suggest some solution on how to achieve this goal with Periodic Rev Recog.
I will give full points for any good suggestion.
Thanks
Ravi

hi
check is there any user exit or BADI available.

Charaction Relationship User Exit

Hi, all.
In our project we encountered with one problem with BI IP. We have characteristic relationship based on attribute without derivation, but the problem in that control date don't work correct. We tried solve this problem, but we didn't its. And now we want instead CR based on attribute use CR based on User Exit. But I don't clearly understand what method of interface IF_RSPLS_CR_METHODSI must use.
I know how use DERIVE method of this interface, but this method is triggered, when we try to save data. But in this case I need create combinations of relationship during executing query.
Anybody know or have any documentation about methods CREATE and CHECK of this interface.
wbr,
Fanil.

Hi, Haritha.
I say about Characteristic Relationship based on Exit without derivation. Maybe I don't clearly understand you.
wbr,
Fanil.

Revenue Recognition user-exit documentation

Similar Messages

Maybe you are looking for