IMG Path - Financial Accounting > Revenue Accounting > Revenue Accounting Contracts > Define Performance Obligation Types
Fulfillment Event Types
IMG Path - Financial Accounting > Revenue Accounting >Revenue Accounting Contracts > Define Fulfilment Event Types
Items | Qty | SO Rate | SSP | Contractual Price | Total SSP | Allocated Amount | Allocation Effect |
TG13 | 1 | 20,000 | 17,000 | 20,000 | 17,000 | 20,284.09 | 284.09 |
SM0001 | 1 | 1,000 | 600 | 1,000 | 600 | 715.91 | (284.09) |
21,000 | 17,600 | 21,000 | 0 |
We start with Value Contract creation with materials & services associated with agreement.
Next, with reference to value contract further Sales Order is created and condition type PPR0, Standalone Sales Price (SSP) will be manually updated at every item level for testing but without SSP system will not save the Sales Order.
For many entities, Step 1 will be straight forward; the key point is to determine when a contract exists. Using Tcode FARR_RAI_MON or Fiori App Manage Revenue Accounting Items, all sales order items will be showcase initially as processable RAI’s. Then all such processable RAI’s are transferred using default sender integration component as SD with RAI class as SD01 with source document item type as SDOI to RAR.
All processable RAI’s are further transferred collectively or individually transfer to RAR. Once RAI’s are processed successfully, in 1st step system will automatically create one Revenue Recognition Contract 1000000301 against one Sales Order and in 2nd step Performance Obligations 2000003003/04 for each Sales Order Items.
As per IFRS 15 prerequisite, RAR component will automatically perform the allocation amount and allocation effect against each Performance Obligation. This determines transaction price and allocate to the separate POB’s level.
RAR Contract will calculate detail revenue schedule with status of each POB’s fulfillment type and status.
With reference to Sales Order, Outbound Delivery and PGI done for material relevant order items.
All processable RAI’s are transferred using default sender integration component as SD with RAI class as SD03 with source document item type as SDII to RAR.
This is the final step to determine for each POB when revenue should be recognized. Revenue is recognized when POB is fulfilled – that is when customer invoice is posted, or services are eligible for post. The system records costs and recognizes revenue based on allocated amounts. The customer invoice posting triggers real time creation of the revenue entry recording contract asset based on the allocated revenue. The solution is based on the Universal Journal and provides real time information on the data at point of time.
In transaction FARR_RAI_MON or Fiori App Manage Revenue Accounting Items, RAR Contract details will be displayed with all information related to Order Items, Fulfillment Items and Invoice Items.
In October we can see 16.67% completion of the Service Item
In December we can see 50% completion of the Service Item
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
2 |