Grouping Rules and Line Ordering Rules
Line Ordering Rules
=================
1. Line ordering rules are used only by auto accounting program (obvious - why do we need this rule for manual?)
2. Line ordering rules are needed if there are more than 1 line in the invoice.
3. The ORDER of the lines in the invoice is decided by line ordering Rule (if there are more than one line).
Ex: 1. Based on Sale order number (ascending/decending), then by sales order line number (ascending/decending)
2. Based on line amount (ascending/decending)
Grouping Rule
============
Grouping rule is used to group the interface lines to create invoices. There are some mandatory grouping attributes like customer (ofcourse we can't have same invoice for two customers), currency, etc. If we need to group based on any other field value (other than mandatory ones), then we can define in the grouping rule. In the grouping rule, we need to attach the line ordering rule
The default hierarchy for grouping rule is Transaction source, then Customer profile class and then system options. If not found in all the above, then the seeded value "DEFAULT" is used.
| Is This Answer Correct ? | 0 Yes | 0 No |
Can it be set that the GL date is the Sale Order date or Ship to Date?
how to do bank reconciliation
what is the impact if i wrongly assign the account type to an segment value in oracle apps r12?
Substitute receipts and Unordered Receipts
What is the use of operating unit, while configure multiorg?
What is catch up depreciation
what are the key flex fields in oracle payables?
What are the steps in setting up Oracle GL ?
What are the issues you have faced at the time of implementation, Migration, Support and Upgradation project and how you resolve them(AP,AR,GL,FA,CM)!!!
1 Answers IBM, Oracle, Tech Mahindra, Wipro,
Can we use AME for PO approvals ?
How many views are generated when compiling flexfield structure ?
Types of Prepayments? And difference between them?