Scribd
Upload
122 views

Notes On BRIM

The document discusses various steps and processes related to distributing contracts to other systems using ODI. Key points include: - ODI is used to transfer contracts to other systems when a contract is made. - The contract status is updated to "technically active" once successful distribution occurs. - Contracts can be distributed early for reporting purposes even if the contract start date is in the future. - Errors can occur which are monitored in distribution tables.

Uploaded by

sri r
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
122 views

Notes On BRIM

The document discusses various steps and processes related to distributing contracts to other systems using ODI. Key points include: - ODI is used to transfer contracts to other systems when a contract is made. - The contract status is updated to "technically active" once successful distribution occurs. - Contracts can be distributed early for reporting purposes even if the contract start date is in the future. - Errors can occur which are monitored in distribution tables.

Uploaded by

sri r
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

schema -steps (code runs in background) we define in system which ODI will perform

- they are dependent ontransaction type


when contract is made -> it is distributed to other systems -> ODI used to transfer

when it is succesfully distributed - technically active becomes yes

Sometimes contract starts in future but is distrubuted to FICA early (as soon as
contract is made not when it starts)
for revenue recognition, future forecasts keliye -
Early distribution - replicate it to FICA but not CC - that is no billing or
invoicing only reporting purposes
keliye FICA mein jaata hai
Revenue recognition is mandatory in US.
Error - Distribution monitor table

How do we know that contract has been replicated on the system

Change Process -
configuration change - upgrade ? provision to change attributes of
product/transaction

when payment method changed - new contract acoount created - change order created
to change transactional contract
number (which is intially created based on provider order number)

revoke cancellation works only on Deferrred cancellation cuz of future date


Backdated - when you requested but you are still being charged so past date.

all of cancellation has to go to convergent invoicing - because billing has to


stop.

Extension - types evergreen or manual extension periods


renewal is extension
technical identifier identifies subscritption contract correctly

start of contract term - when a change has been implemented - contract is sliced
into two
intial contract valid till the date the change has been implemented - new active
slice create hojata hai (new start of contract term, same contract start and end)

subscription contract directly goes to billing plan convergent invocing direct no


need cc
Bill plan generated at run time.

PSMB - condition type - monthly

Sales and distribution -> master data ->

Variant price - > Per quantity or time period or etc

You might also like