GL: Effect of Disabling Segments Used in Code Combination of the Accounting Flexfield (文档 ID 50531.1

摘自：https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=445150086854261&id=50531.1&_adf.ctrl-state=r1e4qvhzk_109

GL: Effect of Disabling Segments Used in Code Combination of the Accounting Flexfield (文档 ID 50531.1)

转到底部

---

APPLIES TO: Oracle General Ledger - Version 11.5.10.2 and later Information in this document applies to any platform. Form:GLXJEENT.FMB - Enter Journals/Encumbrances Executable:GLLEZL - Journal Import PURPOSE To clarify the effects disabling and date disabling segments have on the Accounting Key Flexfield. SCOPE Use with caution as there may be exceptions. DETAILS On the GLXJEENT Enter Journals form, an account is considered valid if it satisfies ALL of the following: 1. The account itself is enabled. 2. All of the individual segment values used in the account are enabled. 3. The effective date of the journal line (or the journal if this is a manual journal) is within the start and end date range specified for the account, if any. 4. The effective date of the journal line (or the journal if this is a manual journal) is within the start and end date range specified for each of the individual segment values used in the account. 5. The account itself is not a summary account. 6. None of the individual segment values used in the account are parent values. 7. The account exists OR if the account does not exist, it satisfies all of the following:      • The individual segment values used in the account are all defined and in the appropriate value sets.      • Dynamic insertion is turned on      • The account does not violate cross validation or security rules 8. For actual or encumbrance journals, detailed posting is on for the account. 9. For budget journals, detailed budgeting is on for the account. 10. For actual or encumbrance journals, detailed posting is on for all of the individual segments used in the account. 11. For budget journals, detailed budgeting is on for all of the individual segments used in the account. 12. Security rules don't deny the current user access to any of the individual segments used in the account. For Journal Import:      • If the account being processed is a NEW account (i.e. has never been used before), then the rules followed are exactly the same as for the Enter Journals form.       • If the account being processed is an existing account, then only rules 1, 3, 5, 8, and 9 are enforced for performance reasons.        Specifically only the account rules are enforced ... all of the rules that deal with individual segment values are not enforced. Disabling Code Combinations There are five main ways to prevent posting to code combinations; 1. Disable the Segment value. 2. Disable the code combination. 3. Create a security rule restricting access to a combination. 4. Create a cross validation rule preventing the creation of certain combinations. 5. Mark as unpostable. These rules are treated differently depending on whether you are entering new data, inquiring on existing data, reporting using standard Reports or Reporting on FSGs. 1. If you disable a segment value a new combination cannot be created using that segment value. The value will not appear on many of the reports. Disabled segment values can be used as the start/end of a ranges of values. Validation in some areas doesn't check to see if segments are disabled. So you cannot enter a journal for a new combination containing a disabled segment value even with dynamic insert switched on but you can post a journal to a combination with a disabled segment value if the combination is not disabled. Import is the same, the code combination was created/validated in the subledger and so will create a journal in the GL. This has repercussions in ADI and webadi if you do not 'pick' the segment values and do not validate on upload the segment values are assumed to be correct by import. If the code combination exists the journal is created. Disabling a segment value does not disable all the code combinations containing that segment value. See Note.300090.1 How to Disable Code combinations: You cannot quickpick the segment when trying to disable the code combination though this can be overcome by typing it in. 2. Disable the code combination and you will not be able to post existing journals, import or enter a new journals. Reports will still use combinations for end dated segments but disabling segment values will stop this in most standard reports. Sometimes this will not be the case as to do so will cause many reports to be out of balance. Account inquiry will allow access to a disabled combination. FSG will allow them to be used in row set, column set and content set but not to override the existing values when running a report. To prevent the users being able to run FSG reports against disabled combinations date end them. Budget Autocopy will post to disabled combinations but this can be corrected by using Maintain Budget Organisation's Report in 11.0 and higher. Some sub ledgers (Purchase Orders) do not re-validate code combinations at later stages in the matching process so journals can be posted against invalid accounts at a late stage. If the combination is not valid and suspense posting is allowed the balancing figure is posted to suspense and the erroneous code is put in the description field of the journal line to aid the correction process. 3. Security rules restrict access to combinations by responsibility. The responsibility cannot enter journals or change a journal line containing a secured combination (this gives the message "The line is read only because a security rule is in effect"). Version 9 had a bug that forced the user to exit the form or change the combination that they were secured against. 4. Cross-Validation rules do not affect existing combinations and so can only be used to prevent new combinations of restricted segments being created. After 10.5 the Cross-Validation Rules Violation Report can be run to show existing combinations that would not meet the Cross Validation rules criteria. 5. Marking a combination as unpostable prevents use in enter journals screen and causes existing journals to fail or post to suspense.   Note: 1. Date ending a code segment value renders it unusable in Journals where the effective date is after that date (journals for future enterable periods have an effective date of the 1st of the month while journals in the current period have an effective date of today or the last day of the month. Any new combinations which contain a date ended segment created by dynamic insert, up until the end date, will have the same end date. Earlier combinations are not affected. You can date disable with JAN-97 and still post in DEC-96. 2. It also makes them unusable as an override to FSG content sets in 10.5 and earlier even if your report is dated before the end date. 3. Changing values in Navigate>setup>financial>flexfield>key>value will often leave the original value in cache memory so the responsibility needs to be re-entered to use the change. This will affect other users as well. A common problem is that the account type if changed at segment level does not change at the combination level. In 11.0 this needs to be done at sql level while at 10.7 and lower you can go to combinations and tab through to change them. 4. See the General Ledger User Guide, section on Correcting Misclassified Accounts. (This can effect Fixed Assets which will import data from sub ledgers as both Expensed and Capitalised if the segment is Account type Asset and the combinations are Expensed). See note 1050920.6 11i: Troubleshooting Misclassified Accounts in General Ledger and Note.872162.1 How To Correct Misclassified Accounts in General Ledger R12.   Still Have Questions?   To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support General Ledger Community. To provide feedback on this note, click on the Rate this document link.