http://sairamgoudmalla.blogspot.hu/2010_12_01_archive.html

langyos...
Pre-requisites setup’s are: Payment terms, Pay Groups, CCID, Supplier classifications, Bank Accounts , Employees (if employees have to set up as vendors).

https://viratoracleapps.wordpress.com/page/3/

meleg...
https://community.oracle.com/thread/1134991?tstart=0
https://community.oracle.com/thread/2544569?tstart=0


éééés... megvan!!!

CCID - Code Combination ID. It never ceases to amaze me how many people use this acronym because it's a technical term, but it's usually used in a functional way. The CCID is technically, the ID of the record in the GL_CODE_COMBINATIONS table that represents a combination of values in the accounting flexfield. For example, the account combination of "01.2500.36.C12" could be stored in the table with the ID of 384569. Typically, people are referring to "01.2500.36.C12" not 384569 when speaking of the CCID.

--------------------------------------------------
Note added at 2 hrs (2016-01-27 20:40:43 GMT)
--------------------------------------------------

https://blogs.oracle.com/financials/entry/gl_sla_sob_coa_bsv...
Idemásolom a többi okosságot is:

GL - usually pertaining to the General Ledger product. Sometimes you'll hear "in GL" which more than likely means "not some other product" like payables, receivables, subledger accounting, or intercompany.
SLA - subledger accounting (architecture). In Release 12, we introduced subledger accounting, the centralized rule-based accounting engine for all subledgers. Oddly enough, the product prefix for SLA is XLA, so you if you see references to tables and forms that are prefixed with XLA - it's SLA related.
SOB - Set of Books, grouping of journals. In Release 12, SOB has been renamed "Ledger", luckily it's only one word, so there's no need for an acronym. You'll typically see SOB written, but not spoken - saying SOB makes people giggle.
JE - typically, "journal entry" in GL. However, JE is the also the product prefix for the EMEA localizations, so it's helpful to know if you're talking Europe or accounting.
COA - Chart of Accounts. Technically speaking, COA is the set of valid combinations of values that make up your accounting flexfield. Frequently, we hear customers speak of "a single COA" when they really mean "a single COA structure". The difference is slight and can greatly impact a conversation. "A single COA" implies that there is one set of valid combinations that is uses by all SOBs or ledgers. "A single COA structure" says that all of SOBs have the same segment names, but there may be multiple valuesets for a given segment (ie- the Cost Center segment in the US is made up of "ABC","DEF", "GHI"; whereas the Cost Center segment in the UK contains "E11","E12","E13")
BSV - Balancing Segment Value. The value part of this is frequently misused. Accurately use, the BSV is the value of the segment of the combination that is qualified as the balancing segment (in the Vision instance, "01", "03","99", etc.) However, it's often used in conversation to mean the segment name (in the Vision instance, the balancing segment name is usually "Company").
CCID - Code Combination ID. It never ceases to amaze me how many people use this acronym because it's a technical term, but it's usually used in a functional way. The CCID is technically, the ID of the record in the GL_CODE_COMBINATIONS table that represents a combination of values in the accounting flexfield. For example, the account combination of "01.2500.36.C12" could be stored in the table with the ID of 384569. Typically, people are referring to "01.2500.36.C12" not 384569 when speaking of the CCID.
LE - Legal Entity. This is relatively new term in Release 12 because legal entities play a more prominent role Legal Entities are used to determine tax as well as the difference between intercompany (between LEs) and intracompany (within LE) trading and accounting. In R12, BSVs can be mapped to LE as part of the accounting setup.
Account - depends on whom you ask. On most of our user interfaces, "account" refers to the complete accounting flexfield ("01.2500.36.C12"). However, when defining your COA structure, one of the segments must be qualified as the Natural Account segment (possibly segment 2), and sometimes people refer to just this segment value when referring to "account" (if segment 2 is the natural account segment, then in the context of the combination "01.2500.36.C12", the term "account" would refer to just "2500").

--------------------------------------------------
Note added at 2 hrs (2016-01-27 20:41:59 GMT)
--------------------------------------------------

Automating the creation of account code combinations ...
www.oracleappsblog.com/.../automating-creation-account-code...
Jul 10, 2004 - In certain instances it may be necessary to manually create account code combinations (CCID's) in Oracle General Ledger. To some extent this ...
Deriving Oracle GL Account Code Combination ID's (CCID's ...
https://imdjkoch.wordpress.com/.../deriving-oracle-gl-accoun...
This API Finds combination_id for given set of key flexfield segment values. ... It also creates a new combination if it is valid and the flexfield allows dynamic inserts and the combination does not already exist. .

--------------------------------------------------
Note added at 5 days (2016-02-01 21:09:21 GMT) Post-grading
--------------------------------------------------

Köszönöm