GL_JE_BATCHES does not have LEDger_ID in R12

Perguntas relacionadas a questões técnicas do Oracle EBS. Criação de Concorrentes, Value Sets, Alerts, Forms Personalizations, Configurações, etc
Post Reply
User avatar
dr_gori
Moderador
Moderador
Posts: 5026
Joined: Mon, 03 May 2004 3:08 pm
Location: Portland, OR USA
Contact:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

Before R11, the GL_JE_BATCHES table owned the set_of_books_id.
In R12 This field has been renamed to set_of_books_id_11i and there is no LEDger_ID field in this table.

After searching a lot, I discovered that it is possible as follows:

Select all

 
SELECT * 
FROM GL_JE_BATCHES 
WHERE je_batch_id IN  
  (SELECT DISTINCT h.je_batch_id 
  FROM gl_je_headers h 
  WHERE h.ledger_id = :$PROFILES$.GL_SET_OF_BKS_ID  
  ) 
ORDER BY NAME
But this way it is very slow, because Gl_JE_Batches is huge.
Does anyone there have any solution for this case?
User avatar
dr_gori
Moderador
Moderador
Posts: 5026
Joined: Mon, 03 May 2004 3:08 pm
Location: Portland, OR USA
Contact:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

After searching in Metalink, I found the following note:

Select all

R12: How to Restrict the Journal Batch List of Values (LOV) to Display only Batches Related to Specific Ledger Assigned to the Responsibility (Doc ID 1235026.1) 
 
GOAL 
How to restrict the Journal Batch List of Values (LOV) to display batches that belong to the ledger assigned to the responsibility ? 
 
SOLUTION 
=== ODM Answer === 
In release 12, journal batch LOV shows the list of all the batches from all the ledgers. This is expected functionality.  
Even though the batch displays all batches, a user can select and view only those batches which are allowed as defined in the GL: Data Access set /Ledger assigned to the responsibility. So, they are no security concerns and this functionality wouldn't cause any issues . 
Then looks like we can only show all lots. :-O
DanielNN
Moderador
Moderador
Posts: 641
Joined: Mon, 03 Sep 2007 3:26 pm
Location: Fortaleza - CE
att,

Daniel N.N.

Oops,

I work a lot with GL at 11i, but I do not Mechi in 12 still.
I was curious. It means that in 12 no longer there is the "set_of_books_id" ??? Was it renamed for "set_of_books_id11i"?
now the field that identifies the book is the ledger_id and it owns in headers but does not own in bacthes ?????
And how does batch and balances identify the book ???
User avatar
dr_gori
Moderador
Moderador
Posts: 5026
Joined: Mon, 03 May 2004 3:08 pm
Location: Portland, OR USA
Contact:
Thomas F. G

Você já respondeu a dúvida de alguém hoje?
https://glufke.net/oracle/search.php?search_id=unanswered

It's a different concept now.
A responsible can have access to several "Set of Books" (which in R12 is Ledger_ID). This is called Ledger Set.

For example:
* My responsibility gives me access to all 3 Ledgers in Brazil. So, I can filter in the report if I want only 1, or if I want everyone.

has a number of new things in R12. There is one thing called SLA (Sub Ledger Accounting) that is a "field medium" between the sub-ledgers (modules) and GL.

So, it is possible to make a series of transformations in the accounts before falling into GL.
(Example, a particular account in the subledger must be released as expense, but when it falls into the array, the same account must be released as active. SLA causes this type of transformation).

So, to do Join between GL and the module, you need to go through SLA. (There are some joins that need to be made).
This all left the GL extremely flexible, and avoiding a series of accounting jobs, moving account lots, etc.
DanielNN
Moderador
Moderador
Posts: 641
Joined: Mon, 03 Sep 2007 3:26 pm
Location: Fortaleza - CE
att,

Daniel N.N.

Interesting.
Thanks for the answer.
Post Reply
  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest