Hi, Thanks for the explanation. I have a doubt. We can also use cross-validation rules also instead of SLA. But why we should use SLA rules instead of CVR?
Hi, if you look at the use case mentioned in this video, requirement is to derive Cost center based on the Natural Account segment value. This cannot be achieved by Cross Validation Rules... Cross Validation rules only stops the user from entering of Account code combination which is violating Cross Validation rules which are setup, but CVR cannot derive a Segment value
Hi, Very clear cut and nice explanation, But I want to understand the Customizing the AP SLA to track the expenses for the department wise or what is the exact requirement? Is the department segment 740 should be tracked for the natural account which is above 5010 ? and for what purpose is it?
Here, the requirement is if the user uses a natural account value which is greater than 5010, then SLA rules should consider the department as "740" irrespective of the department used by the user in AP Invoice distribution lines. I had taken this example as i had implemented similar AP SLA rule for one of our client where all natural accounts greater than 5010 are particular type of expense accounts and if the users uses those expense accounts, always sLA rule should account that AP invoice distribution rule using department "740" (as users can make mistakes of selecting any department even though they are trained properly).
It is a very informative video. Need a small clarification for ADR. We have two lines in ADR, 1st is All Segments line and 2nd line is Service Department. All Segments will take precedence over Services Segment as it is the 1st line so it will derive all segment from 1st line. How is the precedence of rule "Service Department" decide over "All Segments" Rule
Thanks Aravind ! Thanks a lot ! I am having a doubt about overall purpose of the SLA and in the video you have created SLA for AP Invoice but the other invoice types will work on ceded "Standard Accrual" basis only ? if yes how ? and can i know the overall picture of SLA and it hierarchy.
Hi, in this example, my requirement is to change Department segment value if the natural account segment value is greater than "XXX"..... If you have same requirement for other invoice types i.e. Credit Memo, Debit Memo, Prepayment etc..., then you need to create similar SLA rules....
@@OracleEbizandFusionVideos Ok is this only purpose we use SLA or on another requirements also ? Pls dont mind i am not yet clear on overall understanding of SLA
@ Sai Surya, Whenever you create any transaction in Oracle Financial modules i.e. Create a Invoice, or make a payment or make adjustment etc..... system generates accounting entries.... If you have business requirement to change the accounting based on your business requirement, then we use SLA, customize it to meet your requirements
I have one doubt bro.. How do we derive the Invoice Distribution DFF Segment 7 value to Invoice distribution account at time of recognizing the line for MPA functionality without mapping set? how do we wright the ADR rule?
i have a question please, what if we want to the company segment in credit side to be as company segment in debit side, at AP Invoice, Thanks in advance.
@@OracleEbizandFusionVideos thanks for replying, I mean if we have debit side with 1100.123455.000 1100 is the balancing segment we need the derive this value to the credit side also, Credit is 100.123455.000 We need to change the company 100 to 1100 as the debit. I wish it's clear now.
So, do you want the balancing segment of Credit side to be copied from Debit side, then you can try AP Automatic offset... Refer the below video on my channel about AP automatic offset... See, if this can be meet your requirement.. th-cam.com/video/l4sIr_Ni6xw/w-d-xo.html
Its because based on the use case which i explained in my video, i am trying to customize deriving of segment value for AP Invoice Line distribution account
Hi, Thanks for the explanation. I have a doubt. We can also use cross-validation rules also instead of SLA. But why we should use SLA rules instead of CVR?
will SLA makes subledger and GL journal entries mismatch ? it creates mismatch with distribution lines also if SLA edited. rt ? am confused how this kind of mismatch is handled. plz clarify
At first, transactions are created in Subledger and then Create Accounting program is ran which will generate lines in SLA layer and what ever is generated in SLA layer, the same will be sent to GL... All Subledger to GL reconciliation reports uses the data from SLA layer and hence there will not be any mismatch/reconciliation issue between Subledgers and GL
Just awesome... Your step by step explanation is second to none.
Thank you
Thanks a lot..... Clear cut explanation very much useful
Thanks
Great Arvind.
Thanks
great explanation. good work
Thank you!
Wonderful explanation. Thanks for uploading. Please keep some more videos on Oracle Finance. 👍👍👍👍🙏🙏
Thanks and sure, i will do
Thanks for sharing this
My pleasure
Great job..keep post more videos.
Thanks
Sure... Thanks
Thanks for uploading such useful videos.
Thanks
Good one
Thanks for your feedback
awesome explaination
Thanks
Hi, Thanks for the explanation. I have a doubt. We can also use cross-validation rules also instead of SLA. But why we should use SLA rules instead of CVR?
Hi, if you look at the use case mentioned in this video, requirement is to derive Cost center based on the Natural Account segment value. This cannot be achieved by Cross Validation Rules... Cross Validation rules only stops the user from entering of Account code combination which is violating Cross Validation rules which are setup, but CVR cannot derive a Segment value
Clear. Useful. Thanks a lot!
Thanks
Hi, Very clear cut and nice explanation, But I want to understand the Customizing the AP SLA to track the expenses for the department wise or what is the exact requirement? Is the department segment 740 should be tracked for the natural account which is above 5010 ? and for what purpose is it?
Hi Aravind, Would like to know are you tracking the expenses on for the department segment?
Here, the requirement is if the user uses a natural account value which is greater than 5010, then SLA rules should consider the department as "740" irrespective of the department used by the user in AP Invoice distribution lines.
I had taken this example as i had implemented similar AP SLA rule for one of our client where all natural accounts greater than 5010 are particular type of expense accounts and if the users uses those expense accounts, always sLA rule should account that AP invoice distribution rule using department "740" (as users can make mistakes of selecting any department even though they are trained properly).
Thanks for the explanation.
It is a very informative video. Need a small clarification for ADR. We have two lines in ADR, 1st is All Segments line and 2nd line is Service Department. All Segments will take precedence over Services Segment as it is the 1st line so it will derive all segment from 1st line. How is the precedence of rule "Service Department" decide over "All Segments" Rule
Its other way round.... i.e. first preference will be given to the ADR's assigned to individual segments and then to ADR assigned to All Segments
@@OracleEbizandFusionVideos Thank you for the clarification
thanks a lot. GRT explanation
Thanks
v useful u r gennius
Thanks for your feedback
For fusion in mapping set output type which one select either segment or value set and also what about the input source?
good explanation
Thanks
Thanks Aravind ! Thanks a lot !
I am having a doubt about overall purpose of the SLA and in the video you have created SLA for AP Invoice but the other invoice types will work on ceded "Standard Accrual" basis only ? if yes how ? and can i know the overall picture of SLA and it hierarchy.
Hi, in this example, my requirement is to change Department segment value if the natural account segment value is greater than "XXX"..... If you have same requirement for other invoice types i.e. Credit Memo, Debit Memo, Prepayment etc..., then you need to create similar SLA rules....
@@OracleEbizandFusionVideos Ok is this only purpose we use SLA or on another requirements also ? Pls dont mind i am not yet clear on overall understanding of SLA
@ Sai Surya, Whenever you create any transaction in Oracle Financial modules i.e. Create a Invoice, or make a payment or make adjustment etc..... system generates accounting entries.... If you have business requirement to change the accounting based on your business requirement, then we use SLA, customize it to meet your requirements
In Simple terms, SLA is used to derive Accounting based on your business requirement
@@OracleEbizandFusionVideos got it. Thanks Aravind . I send you DM in linked . Kindly check.
I have one doubt bro.. How do we derive the Invoice Distribution DFF Segment 7 value to Invoice distribution account at time of recognizing the line for MPA functionality without mapping set? how do we wright the ADR rule?
Thanks bro!
No problem!
Can you make vedios for fusion too?
Sure, i will create similar videos on Fusion SLA... Keep stay tuned to my channel
Hello Sir, Do you have SLA Customization for Oracle Fusion
Sure, soon, i will create vidoes on custom SLA rules in Fusion... Stay tuned to my TH-cam channel
i have a question please, what if we want to the company segment in credit side to be as company segment in debit side, at AP Invoice, Thanks in advance.
Sorry, i did not understand your question... Can you rephrase your question with an example
@@OracleEbizandFusionVideos thanks for replying,
I mean if we have debit side with 1100.123455.000
1100 is the balancing segment we need the derive this value to the credit side also,
Credit is 100.123455.000
We need to change the company 100 to 1100 as the debit.
I wish it's clear now.
So, do you want the balancing segment of Credit side to be copied from Debit side, then you can try AP Automatic offset... Refer the below video on my channel about AP automatic offset... See, if this can be meet your requirement..
th-cam.com/video/l4sIr_Ni6xw/w-d-xo.html
@@OracleEbizandFusionVideos thanks, will test it
Please explain why was "Item Expense" selected in 7:20?
Its because based on the use case which i explained in my video, i am trying to customize deriving of segment value for AP Invoice Line distribution account
Can we use cross - Validation rule also to meet this requirement?
No. The functionality of Cross Validation rules is different from customization of SLA rules
Hi, Thanks for the explanation. I have a doubt. We can also use cross-validation rules also instead of SLA. But why we should use SLA rules instead of CVR?
will SLA makes subledger and GL journal entries mismatch ? it creates mismatch with distribution lines also if SLA edited. rt ? am confused how this kind of mismatch is handled. plz clarify
At first, transactions are created in Subledger and then Create Accounting program is ran which will generate lines in SLA layer and what ever is generated in SLA layer, the same will be sent to GL... All Subledger to GL reconciliation reports uses the data from SLA layer and hence there will not be any mismatch/reconciliation issue between Subledgers and GL