Error - Journal Entry in R12 -"This balancing segment value....."

Hello Friends,
On R12 -> PROD version
When I enter an Account in Journal, I am getting Error - > "This balancing segment value is not valid for current Ledger"
It is completly a new setup of R12 accounts.

Hello Friends,
Finally I was able to post to GL, ofcourse learned in process how to find where the issue lies. Anyway....still there are some questions.
Coming back to my earlier 2 questions:
I noticed, when I assigned Balancing Segment to the Primary Ledger, I get the problem "This balancing segment......", so I just didnot assign any this time and was able to post to GL. I understand that BS assignment might be required to balance the entries in Ledger but I then have not yet quiet grasped the concept, so for a while I might just go with this.
The 2nd error, I did get that again but I proceeded inspite of that and it is working okay, so donot know what was that one for and now that I know have to dubug, I will keep an eye for it and post any info on that later.
Thank you all for the help and pointers..

Similar Messages

Error : This balancing segment value is not valid for the current ledger

Dear friend,
Error : This balancing segment value is not valid for the current ledger.
when I click Account Assignment in Budget Organization.
I used R12
Thank you
Best regards,
Hareyuya, Junior.

Hi,
Please see these documents.
Note: 756765.1 - Cannot Use Parent Balancing Segment Values In Massbudget or MassAllocation Formula
Note: 790339.1 - Cannot Select Parent Values In Mass Budgets
Note: 437588.1 - Rel 12: Balancing Segment Value Is Not Valid For Current Ledger
Regards,
Hussein

Balancing Segment Value assignment to Legal Entity using Account Setup Mgr

Hello,
This is on r12.06
By mistake- I did not assign BSV at Legal Entity level, insteady I directly assigned at Ledger level. Now, I am getting following error when running "Accounting Program" standard program
The subledger journal entry contains lines with balancing segment values that are not assigned to any legal entity. Unassigned balancing segments cannot be used to balance a subledger journal entry with balancing segments already assigned to a legal entity. Either update the balancing segment value assignments for the ledger ADP/Claims Solutions Group or update the balancing segment values used on the subledger journal entry Upon research, It was discovered that that the Balancing segment is assigned only at ledger level and it is not assigned at Legal Entity level in account setup manager.
When I attempted to assign the BSV at LE level, it is not showing the BSV in list of values.
I even end dated BS at ledger level and tried again but still the concerned BSV is not showing up in LOV at Legal entity level.
Now I am completely stuck. Any idea what am I missing? Why, the new BSV is not showing up at LE level LOV when attempting to assign BSV at LE level?
Thank you for reading this post in advance.
Regards,
R

Once a BSV is assigned to the ledger it does not appear in the LOV of BSV-LE assignment field. Pl see if you can delete the BSV from ledger assignment, then only you can re-assign to LE. In my opinion, it allows you to delete the BSV from ledger level if you have not already used it in transactions. In your case, I wonder if it will allow you to delete it. If not, you have to raise SR with Oracle support.
Thanks
Tarun

Balancing segment value is not valid for this ledger

Hello All,
I am getting above error while running the Journal Import.
Can any send me the query to check this details from Backend.
Your help is appreciated.
Thanks,
AB
Edited by: ABA on Jan 6, 2010 6:23 AM

ABA wrote:
Hello All,
I am getting above error while running the Journal Import.What is exact error?
Please also check Note:R12: Consolidation Journal Import Fails With Em30: Balancing Segment Value Not Valid For Ledger [ID 851061.1] and see its helpful
GL Manuals and eTRMs from 10.7 to 11i [ID 66935.1]
You can also check e-trm site for your issue(Interface Table : GL_INTERFACE -Base Tables : GL_JE_BATCHES - GL_JE_HEADERS-GL_JE_LINES -GL_BALANCES)
Regard
Helios

Query to Check whether balancing segment value is assign to ledger

Hello All,
I am getting above error while running the Journal Import.
Can any send me the query to check this details from Backend.
Your help is appreciated.
Thanks,
AB
Edited by: ABA on Jan 6, 2010 6:23 AM

Here is the query to check balancing segment value Assigned to ledger or not.
select ledger_id,segment_value balancing_segment,legal_entity_id
from GL_LEDGER_NORM_SEG_VALS where segment_type_code = 'B'
Thanks,
AB

(ADI) JOURNAL UPLOAD IS ADDING ZEROS TO SEGMENT VALUES

제품 : FIN_GL
작성날짜 : 2003-09-16
(ADI) JOURNAL UPLOAD IS ADDING ZEROS TO SEGMENT VALUES
======================================================
Problem Description
ADI에서 Journal Import를 시도할때, Account segment value값에"0"를 자리수만큼 채워서 upload를 시도하는 경우가 있다.
예를들어, segment value가 300 인데, ADI에서 Journal Import시
0300 으로 바뀌는 경우이다.
이 경우, Segment Value중에 0300이라는 값이 없기 때문에, upload시
에러가 발생한다.
재현방법 :
Responsibility = General Ledger Super User
ADI path = Click on the Ledger Book from the ADI toolbar/Enter Journals
1. Log on to ADI as the General Ledger Super User.
2. Proceed to the Create Journal Worksheet form using the above navigation.
3. Choose the appropriate journal type and click on the green check mark to
continue. This will load Excel and the appropriate journal template.
4. Enter your Journal information in the header and body. Place the value of
the segments that you would like in the segment value portion of the journal.
5. Once the journal is completed, click on the Ledger Book from the ADI toolbar
and select the green arrow to upload the journal.
6. Once the journal upload is complete, you notice that the values that were
uploaded for a certain segment have a zero added to them.
Solution Description
"0"가 자릿수만큼 채워지는 것을 막기위해, ADI setup중 "Zero Pad" 기능을 uncheck한다.
Responsibility = General Ledger Super User
ADI path = Click on the Hammer and Screwdriver(망치와 드라이버가 그려져 있는 Icon) from the ADI toolbar/General
options/Settings
1. Log on to ADI as the General Ledger Super User.
2. Proceed to the Settings form using the above menu path.
3. Uncheck the Zero Pad check box on this form.
4. Save your changes and repeat the journal import process for this journal.
Explanation
"Zero Pad"기능은 check되었을때, 해당 Segment의 Maximun Size만큼 "0"으로 채워준다.
이 기능을 uncheck하면, "0"의 추가확장 없이 입력된 그대로를 사용하게 된다.
Reference Documents
Note : 113051.1

Hi,
Are you choosing Functional Journals template and trying to upload Foreign Currency journals or vice versa? Please check
Regards,
Sridhar

Updating Balancing Segment Values in Legal Entity

Dear Members :
I am trying to add one more balancing segment value to one already existing in Legal Entity. Neither am I able to add one or remove the one already existing. I am novice in Financial and really appreciate some explanation on
[1] Importance of segment values on Legal Entity/Primary ledger & Secondary Ledger(Balancing Segment Value Assignments, in last two cases)
[2] Way out for my problem.
Thanks in advance.
Atanu

Thanks. I exactly intended to do that, but surprisingly not able to select, I mean find my other company code when I opt for adding segment value to Legal entity. Say now I have company code 10 attached and there's one more 05, which I want to add; I am not seeing that value when entering in Values LOV.
Could you please provide some clues - about trouble shooting the issue. Also what repurcussion will it have if I can or can not attach my desired company code - if you please tell ?
Thanks.
Atanu

Assign a Balancing Segment Value

Dear Members,
I have two legal entities and one balancing segment value(bsv).
I have assigned the bsv to the first legal entity. Later I have discovered that it should be assigned to second legal entity. So I have disabled the bsv by entering the end date at the first legal entity. I want to assign it to the second legal entity but it doesnt show up in the lov.
What is the solution?
Please advise.
Many thanks in advance.

1. Exact hit. Refer Note 465928.1
2. Also refer Note 749971.1
It seems some kind of workaround is available.
Please confirm if second note helps you
Regards,
Srini

Period LOV in GL journal entry from r12

I am trying to do some customization for the period LOV in GL journal entry form.
In found the below SQL from the record group of the LOV:
SELECT period_name,
         start_date,
         end_date,
         period_num,
         period_year
    FROM gl_periods
   WHERE period_set_name = :PARAMETER.period_set_name
     AND period_type = :PARAMETER.accounted_period_type
ORDER BY period_year DESC, period_num DESC
Since, I don't know how to get the values for :PARAMETER.period_set_name and :PARAMETER.accounted_period_type ....I ran the SQL
select * from gl_periods where period_name = 'APR-15'
in toad to find values for period_set_name and values and period_type and then ran the main SQL in toad but it returned lot of records ~500.
But, in the application PERIOD LOV just displays open periods. I am wondering if you can tell me how it works.
I checked to form to make sure there is no existing personalization for PERIOD LOV.
Thanks.

Hi,
I am pasting my comments next to yours :
These are the issues that needs to be resolved:
• Depreciated balance are over stated in Fixed Assets and needs to be adjusted to reflect what is in GL. => I wasn't sure how this was was possible, since I assumed that your Asset depreciation journals in GL were being fed from FA. So if depreciation was thought to be incorrect in FA, its corresponding balance in GL should've been incorrect as well. But I guess that's not the case because your other questions imply that some of these assets were acquired and their might have been some conversion activity involved.
• Fixed Assets mass additions are selecting GL accounts that should not be selected. We need to know how to change the criteria for selection. +=> Check the Asset Clearing and CIP clearing accounts on your asset categories+
Later:
• We need to learn the proper way to convert assets we acquired from acquisition into our Oracle Fixed Assets system, so that depreciation start at the time we acquire the assets. => That is correct, you could change your original date placed in service to the acquisition date as part of conversion and if you have the correct prorate convention, they should depreciate the way you want it to.

Unbalance transaction Error - Journal Entry Posting

Hi all,
Good afternoon. i posted journal entry using DI -API. I have two Journal Entry when i add the first journal Entry added the second journal entry not added its show the Error Unbalanced transaction
Each Journal Entry have 2 lines
I am using 8.8 patch Level 12
Please anyone help me out of this issue
Edited by: lakshmi narayanan on Oct 19, 2011 9:11 AM

Hi Jitin,
Did you solved this issue? I just have the same problem with SAP Business One 2007 A (8.00.181) SP: 00 PL: 47
Here my oJournalEntry XML before Add.
You can see that Debit amount is equal to Credit amount (highlited with red)
I would like to receive some suggestions.
<?xml version="1.0" encoding="UTF-16"?>
<BOM>
<BO>
<AdmInfo>
<Object>30</Object>
</AdmInfo>
<OJDT>
<row>
<BatchNum>0</BatchNum>
<TransId>0</TransId>
<BtfStatus>O</BtfStatus>
<TransType>-1</TransType>
<BaseRef/>
<RefDate>20140104</RefDate>
<Memo>AS400-89532</Memo>
<Ref1/>
<Ref2/>
<CreatedBy>0</CreatedBy>
<LocTotal>0.000000</LocTotal>
<FcTotal>0.000000</FcTotal>
<SysTotal>0.000000</SysTotal>
<TransCode/>
<OrignCurr/>
<TransRate>0.000000</TransRate>
<BtfLine>0</BtfLine>
<TransCurr/>
<Project/>
<DueDate/>
<TaxDate>20140104</TaxDate>
<PCAddition>N</PCAddition>
<FinncPriod>0</FinncPriod>
<DataSource>N</DataSource>
<UpdateDate/>
<CreateDate/>
<UserSign>0</UserSign>
<UserSign2>0</UserSign2>
<RefndRprt>N</RefndRprt>
<LogInstanc>0</LogInstanc>
<ObjType>30</ObjType>
<Indicator/>
<AdjTran>N</AdjTran>
<RevSource>N</RevSource>
<StornoDate/>
<StornoToTr>0</StornoToTr>
<AutoStorno>N</AutoStorno>
<Corisptivi>N</Corisptivi>
<VatDate/>
<StampTax>N</StampTax>
<Series>1543</Series>
<Number>0</Number>
<AutoVAT>N</AutoVAT>
<DocSeries>0</DocSeries>
<FolioPref/>
<FolioNum>0</FolioNum>
<CreateTime>0</CreateTime>
<BlockDunn>N</BlockDunn>
<ReportEU>N</ReportEU>
<Report347>N</Report347>
<Printed>N</Printed>
<BaseTrans>0</BaseTrans>
<U_MIGSAP_KEY/>
<U_YVA_RENDI/>
<U_YVA_NUMREN>0</U_YVA_NUMREN>
<U_YVA_ANULADO/>
</row>
</OJDT>
<JDT1>
<row>
<TransId>0</TransId>
<Line_ID>0</Line_ID>
<Account>12121</Account>
<Debit>0.000000</Debit>
<Credit>0.000000</Credit>
<SYSCred>0.000000</SYSCred>
<SYSDeb>0.000000</SYSDeb>
<FCDebit>0.000000</FCDebit>
<FCCredit>863.420000</FCCredit>
<FCCurrency>USD</FCCurrency>
<DueDate>20140104</DueDate>
<SourceID>0</SourceID>
<SourceLine>0</SourceLine>
<ShortName>C10211220550</ShortName>
<IntrnMatch>0</IntrnMatch>
<ExtrMatch>0</ExtrMatch>
<ContraAct>C10211220550</ContraAct>
<LineMemo>AS400-89532</LineMemo>
<Ref3Line/>
<TransType>-1</TransType>
<RefDate/>
<Ref2Date/>
<Ref1/>
<Ref2>89532</Ref2>
<CreatedBy>0</CreatedBy>
<BaseRef/>
<Project/>
<TransCode/>
<ProfitCode/>
<TaxDate/>
<SystemRate>0.000000</SystemRate>
<MthDate/>
<ToMthSum>0.000000</ToMthSum>
<UserSign>0</UserSign>
<BatchNum>0</BatchNum>
<FinncPriod>0</FinncPriod>
<RelTransId>-1</RelTransId>
<RelLineID>-1</RelLineID>
<RelType>N</RelType>
<LogInstanc>0</LogInstanc>
<VatGroup/>
<BaseSum>0.000000</BaseSum>
<VatRate>0.000000</VatRate>
<Indicator/>
<AdjTran>N</AdjTran>
<RevSource>N</RevSource>
<ObjType>30</ObjType>
<VatDate/>
<PaymentRef/>
<SYSBaseSum>0.000000</SYSBaseSum>
<MultMatch>0</MultMatch>
<VatLine>N</VatLine>
<VatAmount>0.000000</VatAmount>
<SYSVatSum>0.000000</SYSVatSum>
<Closed>N</Closed>
<GrossValue>0.000000</GrossValue>
<CheckAbs>0</CheckAbs>
<LineType>0</LineType>
<DebCred/>
<SequenceNr>0</SequenceNr>
<StornoAcc/>
<BalDueDeb>0.000000</BalDueDeb>
<BalDueCred>0.000000</BalDueCred>
<BalFcDeb>0.000000</BalFcDeb>
<BalFcCred>0.000000</BalFcCred>
<BalScDeb>0.000000</BalScDeb>
<BalScCred>0.000000</BalScCred>
<IsNet>Y</IsNet>
<DunWizBlck>N</DunWizBlck>
<DunnLevel>0</DunnLevel>
<DunDate/>
<TaxType>0</TaxType>
<TaxPostAcc>N</TaxPostAcc>
<StaCode/>
<StaType>0</StaType>
<TaxCode/>
<ValidFrom>19000101</ValidFrom>
<GrossValFc>0.000000</GrossValFc>
<LvlUpdDate/>
<U_BPP_CTAD/>
<U_BPP_CTAPAT/>
<U_BPP_DCCD>0</U_BPP_DCCD>
<U_BPP_DCPR>N</U_BPP_DCPR>
<U_INFOPE01/>
<U_INFOPE02/>
<U_INFOPE03/>
<U_InfoCo01/>
<U_YVA_TIENDA/>
<U_YVA_UNDTRANS/>
<U_YVA_FECDOC/>
<U_HYP_Status>3</U_HYP_Status>
<U_HYP_BofEx400>89532</U_HYP_BofEx400>
<U_HYP_Closed>N</U_HYP_Closed>
</row>
<row>
<TransId>0</TransId>
<Line_ID>0</Line_ID>
<Account>12311</Account>
<Debit>0.000000</Debit>
<Credit>0.000000</Credit>
<SYSCred>0.000000</SYSCred>
<SYSDeb>0.000000</SYSDeb>
<FCDebit>431.710000</FCDebit>
<FCCredit>0.000000</FCCredit>
<FCCurrency>USD</FCCurrency>
<DueDate>20140203</DueDate>
<SourceID>0</SourceID>
<SourceLine>0</SourceLine>
<ShortName>C10211220550</ShortName>
<IntrnMatch>0</IntrnMatch>
<ExtrMatch>0</ExtrMatch>
<ContraAct>C10211220550</ContraAct>
<LineMemo>LT-268302</LineMemo>
<Ref3Line/>
<TransType>-1</TransType>
<RefDate/>
<Ref2Date/>
<Ref1/>
<Ref2>268302</Ref2>
<CreatedBy>0</CreatedBy>
<BaseRef/>
<Project/>
<TransCode/>
<ProfitCode/>
<TaxDate/>
<SystemRate>0.000000</SystemRate>
<MthDate/>
<ToMthSum>0.000000</ToMthSum>
<UserSign>0</UserSign>
<BatchNum>0</BatchNum>
<FinncPriod>0</FinncPriod>
<RelTransId>-1</RelTransId>
<RelLineID>-1</RelLineID>
<RelType>N</RelType>
<LogInstanc>0</LogInstanc>
<VatGroup/>
<BaseSum>0.000000</BaseSum>
<VatRate>0.000000</VatRate>
<Indicator/>
<AdjTran>N</AdjTran>
<RevSource>N</RevSource>
<ObjType>30</ObjType>
<VatDate/>
<PaymentRef/>
<SYSBaseSum>0.000000</SYSBaseSum>
<MultMatch>0</MultMatch>
<VatLine>N</VatLine>
<VatAmount>0.000000</VatAmount>
<SYSVatSum>0.000000</SYSVatSum>
<Closed>N</Closed>
<GrossValue>0.000000</GrossValue>
<CheckAbs>0</CheckAbs>
<LineType>0</LineType>
<DebCred/>
<SequenceNr>0</SequenceNr>
<StornoAcc/>
<BalDueDeb>0.000000</BalDueDeb>
<BalDueCred>0.000000</BalDueCred>
<BalFcDeb>0.000000</BalFcDeb>
<BalFcCred>0.000000</BalFcCred>
<BalScDeb>0.000000</BalScDeb>
<BalScCred>0.000000</BalScCred>
<IsNet>Y</IsNet>
<DunWizBlck>N</DunWizBlck>
<DunnLevel>0</DunnLevel>
<DunDate/>
<TaxType>0</TaxType>
<TaxPostAcc>N</TaxPostAcc>
<StaCode/>
<StaType>0</StaType>
<TaxCode/>
<ValidFrom>19000101</ValidFrom>
<GrossValFc>0.000000</GrossValFc>
<LvlUpdDate/>
<U_BPP_CTAD/>
<U_BPP_CTAPAT/>
<U_BPP_DCCD>0</U_BPP_DCCD>
<U_BPP_DCPR>N</U_BPP_DCPR>
<U_INFOPE01/>
<U_INFOPE02/>
<U_INFOPE03/>
<U_InfoCo01/>
<U_YVA_TIENDA/>
<U_YVA_UNDTRANS/>
<U_YVA_FECDOC/>
<U_HYP_Status>3</U_HYP_Status>
<U_HYP_BofEx400>268302</U_HYP_BofEx400>
<U_HYP_Closed>N</U_HYP_Closed>
</row>
<row>
<TransId>0</TransId>
<Line_ID>0</Line_ID>
<Account>12311</Account>
<Debit>0.000000</Debit>
<Credit>0.000000</Credit>
<SYSCred>0.000000</SYSCred>
<SYSDeb>0.000000</SYSDeb>
<FCDebit>431.710000</FCDebit>
<FCCredit>0.000000</FCCredit>
<FCCurrency>USD</FCCurrency>
<DueDate>20140305</DueDate>
<SourceID>0</SourceID>
<SourceLine>0</SourceLine>
<ShortName>C10211220550</ShortName>
<IntrnMatch>0</IntrnMatch>
<ExtrMatch>0</ExtrMatch>
<ContraAct>C10211220550</ContraAct>
<LineMemo>LT-268303</LineMemo>
<Ref3Line/>
<TransType>-1</TransType>
<RefDate/>
<Ref2Date/>
<Ref1/>
<Ref2>268303</Ref2>
<CreatedBy>0</CreatedBy>
<BaseRef/>
<Project/>
<TransCode/>
<ProfitCode/>
<TaxDate/>
<SystemRate>0.000000</SystemRate>
<MthDate/>
<ToMthSum>0.000000</ToMthSum>
<UserSign>0</UserSign>
<BatchNum>0</BatchNum>
<FinncPriod>0</FinncPriod>
<RelTransId>-1</RelTransId>
<RelLineID>-1</RelLineID>
<RelType>N</RelType>
<LogInstanc>0</LogInstanc>
<VatGroup/>
<BaseSum>0.000000</BaseSum>
<VatRate>0.000000</VatRate>
<Indicator/>
<AdjTran>N</AdjTran>
<RevSource>N</RevSource>
<ObjType>30</ObjType>
<VatDate/>
<PaymentRef/>
<SYSBaseSum>0.000000</SYSBaseSum>
<MultMatch>0</MultMatch>
<VatLine>N</VatLine>
<VatAmount>0.000000</VatAmount>
<SYSVatSum>0.000000</SYSVatSum>
<Closed>N</Closed>
<GrossValue>0.000000</GrossValue>
<CheckAbs>0</CheckAbs>
<LineType>0</LineType>
<DebCred/>
<SequenceNr>0</SequenceNr>
<StornoAcc/>
<BalDueDeb>0.000000</BalDueDeb>
<BalDueCred>0.000000</BalDueCred>
<BalFcDeb>0.000000</BalFcDeb>
<BalFcCred>0.000000</BalFcCred>
<BalScDeb>0.000000</BalScDeb>
<BalScCred>0.000000</BalScCred>
<IsNet>Y</IsNet>
<DunWizBlck>N</DunWizBlck>
<DunnLevel>0</DunnLevel>
<DunDate/>
<TaxType>0</TaxType>
<TaxPostAcc>N</TaxPostAcc>
<StaCode/>
<StaType>0</StaType>
<TaxCode/>
<ValidFrom>19000101</ValidFrom>
<GrossValFc>0.000000</GrossValFc>
<LvlUpdDate/>
<U_BPP_CTAD/>
<U_BPP_CTAPAT/>
<U_BPP_DCCD>0</U_BPP_DCCD>
<U_BPP_DCPR>N</U_BPP_DCPR>
<U_INFOPE01/>
<U_INFOPE02/>
<U_INFOPE03/>
<U_InfoCo01/>
<U_YVA_TIENDA/>
<U_YVA_UNDTRANS/>
<U_YVA_FECDOC/>
<U_HYP_Status>3</U_HYP_Status>
<U_HYP_BofEx400>268303</U_HYP_BofEx400>
<U_HYP_Closed>N</U_HYP_Closed>
</row>
</JDT1>
</BO>
</BOM>

Balancing Segment Value set Does't show values and Giving error Page.

In R12,LOV of Balancing segment, doesn't show values and giving error page while creating Retained Earnings Account in Ledger Options Page.
If once the ledger options finished, and it gets the status completed, can't we modify the Ledger options in future.
By mistake we finished. can i delete Primary ledger from Accounting stucture?
Thanks in advance,
VRC Murthy

Turn on the dynamic insert for your chart of account structure.
Make sure you have at least one value in each of the value value set attached to COA segments. Make sure retained earning account value exists in your Account value set.
Now you will be able to pick your retained earnings account in Accounting Setups screen.
After completing your ledger setup you will be able to modify some options like suspense account, reversal set, future enterable periods etc.
I have explained the GL setup in detail in my online training videos at http://handsonerp.com
Regards
Edited by: user2648997 on Nov 13, 2009 11:50 AM

DTW error (Journal Entry)

Hi,
Please help me to know what is wrong to import Journal Entry by DTW;
Reason is
"You are not allowed to edit posting date by row Application-defined or object-defined error 65171"
Version is 2005B SP00 PL41
I create the header file as below;
RecordKey, JdtNum, DueDate, ReferenceDate, TaxDate, TransactionCode, Memo
1,,20081110,20081110,20081110,100,ABC
the line file is;
RecordKey, LineNum, AccountCode, Debit, Credit, Reference1, Reference2, AdditionalReference, LineMemo, CostingCode
1,0,738008,4800,0,21486,20081017,ABC,DEF,212
1,1,112200,0,4800,21486,20081017,ABC,DEF,212
The first time I tried it was successful to import, but after change amount I can not import them.
If you have any solution or instructions, please let me know.
Thank you for your help in advance.
KAORI

Hi
I create the header file as below;
RecordKey, JdtNum, DueDate, ReferenceDate, TaxDate, TransactionCode, Memo
1,,20081110,20081110,20081110,100,ABC
1. Please aviod transaction code
2. you have to add AutoVAT coloumn tYES.
RecordKey, LineNum, AccountCode, Debit, Credit, Reference1, Reference2, AdditionalReference, LineMemo, CostingCode
1,0,738008,4800,0,21486,20081017,ABC,DEF,212
1,1,112200,0,4800,21486,20081017,ABC,DEF,212
1. You have to add vat details if it is no need in the last 5 colomns.
2. tax date , tax group , vat amount , vat date , vat line.
20081110 , Exempt , 0 , 20081110 , tYES
3. tax group is the tax code. You should be given the tax code. if no tax code in the JE, nesessary you should be use tax exempt in the colomn.
4. forthur you have to check the GL Accounts whether it is ok.
let me know
regards

Balancing Segment issue

Hi,
I am confusing on the balance segments usage. I checked from the articles.
"If a Balancing Segment Value is assigned to a Legal Entity, one would be able to create transactions from this Legal Entity only if a Balancing Segment Value is assigned. (in payables/ receivables to which this legal entity is assigned)."
If it is true, I have the question:
I did a test. We have a ledger "USD LEDGER". Under this ledger, we have 3 legal entities "A", "B" and "C". The following is the currnet BSV assigment:
BSV 6049 to ledger "USD LEDGER"
BSV 6426 to ledger "USD LEDGER"
BSV 6439 to ledger "USD LEDGER"
BSV 6448 to ledger "USD LEDGER"
BSV 6415 to entity A
BSV 6422 to entity B
BSV 6424 to entity C
From the above setting, I created an AP invoices in entity B with the following distribution lines:
1. Item, Amount=1.00, Account=6422.0000.343162.0000.000000.000.0000.000
2. Item, Amount=1.00, Account=6049.0000.343162.0000.000000.000.0000.000
3. Item, Amount=-1.00,Account=6049.0000.343162.0000.000000.000.0000.000
The default AP liability account=6422.0000.311101.0000.000000.000.0000.000
Supposed I can use BSV 6422 only if I create AP invoice in legal entity B. However, I can also use 6409 as expense item in AP distributions and its acccounting could be created succssfully. Here is the AP jounral created in legal entity B:
6422.0000.311101.0000.000000.000.0000.000     Liability     Dr 1.00
6422.0000.311101.0000.000000.000.0000.000     Liability Cr 2.00
6422.0000.343162.0000.000000.000.0000.000     Item Expense Dr 1.00
6049.0000.343162.0000.000000.000.0000.000     Item Expense Cr 0.00
Why could I user 6049 in the above entry? Could anybody please kindly explain and show me why? Thanks.
Regards,
Edmond

Hi Edmond,
the reason for asking the source of article was to find out in what context that was referred in, i was not implying that the statement is misleading or incorrect ... Oracle Support documentations are considered final in key decision making areas during implementation and post implementation period ... hence there is no question on the validity of what Oracle says ... However the interpretations are to be carefully reviewed ....
Assignment of BSV values to Ledger and Legal Entity was a change brought forward in Release 12 version of Oracle E business suite, it was not the case in the older version i.e. 11i... Now there are two places in which BSV values are to be assigned ....
1) At the Legal Entity Level - This is MANDATORY
Every transaction that is recorded at the operating unit level will have a reference to its legal entity as well ... By looking at the account code combination or BSV
used in the subledger transaction, we can clearly identify which Legal Entity this transaction belongs to, whereas we have to let the system know of that as well i.e.
which BSV's point of which LE's. This link needs to be established for performing transaction processing at the Operating unit Level ....
There are no transactions that are processed at Legal Entity Level, all transactions are recorded and processed at Operating unit level, however this configuration
became a pre-requisite to do that ..
Assume a Scenario where,
USD Ledger has 2 Legal entities LE 1 and LE 2 ...and 3 Operating units OU 1 and OU 2 under LE 1 and OU 3 under LE 2
In 11i, when you enter a transaction in OU 1 and OU 2, it is clear that the transaction belongs to LE 1 and not any other ....
whereas in R12, that is not enough ... i have to say that which value of my company segment points to LE 1 and LE 2 ... The change is due to the system design ....and
other system dependancies ....The link between Operating unit and Legal Entity is established or governed through BSV value assignments
2) At the Ledger Level - This is purely OPTIONAL
This assignment is normally not performed in most of the client places or atleast i have not seen it being performed ....
This is useful when you are performing a transaction that does not belong to a Legal Entity .... when a transaction does not belong to LE, which means it does not have a operating unit as well ... which also means that, such transactions will not be performed at Subledger level, they can only be done at the Ledger Level ..i.e. in
General Ledger MOdule.
Assume a scenario where,
Client has 3 different Ledgers and wants to consolidate the 3 ledgers data in to a new ledger .. this new ledger would be used only to hold consolidation data and
extract financial reports nothing more .. in which case this new ledger will not require a Legal entity, when there is no Legal entity, you cannot assign BSV value ...
so in that case, BSV assignment at Ledger level would help in performing the consolidating activity and adjustments type of transactions ......
Also note, that when no BSV is assigned at Ledger level, system displays all values.
I am yet to see a documentation from oracle or others, which states the restrictions on displaying or not displaying LE values based on BSV assignments at LE or Ledger Level ....
Regards,
Ivruksha

GL - replacing the balancing segment another value

Hi,
An example of a situation, we need to replace the balancing segment value to another. External entity has proposed update on set of values and update the GL_code_combinations table. I rknow that Oracle does not recommend making updates on the tables, but needs additional arguments to specify that this is not the correct way:
- losing the historical data on the balancing segment value primary (no option to report data after update)
- The possibility of wrongful conduct customized solutions
- lack of certainty of updating the tables with values and code combinations are enough to udate?
Do you have any idea what else could be danger with that solution?
Thank you very much for suggestions..
Magda

Instead of updating the base table, you can follow the below mentioned approach.
Take the Detail trial balance for the old BSV.
Create a new journal passing the CR/DR to the new BSV with other combination remaining same, this will knock off the balance of Old BSV.
Use the replacement account feature for all the future Subledger pending accounting entry for Old BSV.
Regards

Create trigger in UDF on Journal Entry

Hi SAP Users,
       Need help for this ...
       I add User Defined Fields in Journal Entry module, I want this field not to leave blank/empty. Can somebody teach me on how to create a code in SP that will trigger the module to avoid adding the journal entry data if this field in UDF is blank. And where specifically in SP will I put the code if I am pertaining on Journal Entry module
        Thanks
Vissia

Hi,
Try Below...
IF @transaction_type = N'A' AND (@Object_type = N'30')
BEGIN
if Exists ( select T0.TransId from OJDT T0 where T0.Transtype='30' and
t0.transid = @list_of_cols_val_tab_del and (T0.UDF-NAME is null or T0.UDF-NAME= ''))
BEGIN
SELECT @Error = 1, @error_message = N'Please select UDF Name !!'
END
END
Apply this in sql server >>choose Data base>>Programmbility>>stored procedure>> SP Transaction notification>> Copy above code and paste and execute
Note: Above code is for header level UDF. If your udf is row level then just replace the table name OJDT by JDT1 in above code
Edited by: Deepak Tyagi on Sep 22, 2011 7:30 AM
Edited by: Deepak Tyagi on Sep 22, 2011 7:33 AM

Error - Journal Entry in R12 -"This balancing segment value....."

Similar Messages

Maybe you are looking for