Segment is not informed in FAGLFLEXT table

Hi
in my current project we are informing the "segment" field in certain documents using a substitution. The objective is to be able to discriminate those document when running the balance sheet program.
The problem is when I execute the Balance Sheet program and set a filter for a segment value, the balance sheet is no filtered as expected.
I have review the bseg table, and segment is informed as expected, but I have seen that segment is not informed in FAGLFLEXT. In my understanding this is the reason why balance sheet is not filtering by segment.
Does anybody knows why segment is not informed in FAGLFLEXT?
am I missing something?
how segment is informed in FAGLFLEXT?
is there any tool in order to update segment field in FAGLFLEXT when not informed?
I'll appreciate any help. Points will be rewarded.
Cheers!

You must assign scenario FIN_SEGM to your newGL ledger.
Also pls be aware that if you're using call point 3 substitution to set SEGMENT field, the value is not transferred to FAGLFLEX* tables. You should use BAdI: FAGL_DERIVE_SEGMENT instead.
Regards, Kyoko

Similar Messages

RE: Cost centre is not updating in FAGLFLEXT table

Dear experts,
During posting we give PSG and cost centre but cost centre is not updating in GL total table FAGLFLEXT as its statistical, in order to be able to update CC in the GL total table what we should activate?
please advice.
Regards,
Chandu.

Hi Chandu.
Sadly, this is the standard behavior of the system. In FAGLFLEXT only arrive real cost object, not statistical. This is explained in oss
964686 - Transfer of statistical postings in CO to FI
If you really nead the Cost Center, you can enhace table FAGL and and create Z field for statistical cost center. This is a common solution.
Arturo.

FAGLFLEXT table is not updating from FAGLFLEXA

Hello Experts,
In thru which program the summarisatin table of FAGLFLEXT getting updated from table FAGLFLEXA .
We've updated some filed values like prctr , cost center to FAGLFLEXA but the same cumulative amount is not showing in the table period wise and there is a difference in balace sheet.
Pls advise, how to generate the table FAGLFLEXT to get my overall balances or how to run this table to go and do their own std calculations and updation.
Pls advise.
thanks & regards
sankar.

Thanks

FAGLFLEXT Table not getting updated

Hello All,
I have activated 0L leading ledger and the document splitting is up and active, however while posting a document, the FAGLFLEXT Table is not getting updated.
Can anybody please help.
Regards,
Vikram

Hello Vikram,
Did you assigned any scenarios to ledger.There are six scenarios like profit center update,prep for consolidation and all....so if you assign these scenarios then the FAGLFLEXT will be updated...
pls let us know if you already assigned and then we need to look in to it...
Thanks,
Sai.

FAGLFLEXT table not updating Transaction type and Trading Partner

Hi,
The document which i post is development system is posted to FAGLFLEXT table properly along with the transaction type and trading Partner; however in the quality and production the document is getting posted in the table FAGLFLEXT but the transaction type and Trading partner fields are not getting updated for these documents it is coming as blank.
Please give us answer ASAP.
Thanks,
Anil.B

Hi,
I got it. Just ask BASIS to Open the QAS system client and delete all scenarios which was assigned in DEV and transported in to QAS system and reassigned itand saved in QAS system and then its worked. all fields are getting populated.
Go to IMG Fin Acc (New) -> Fin Acc Global Setting (New) -> Ledgers -> Ledger -> Assign Scenario
Thanks,
Anil.B
Edited by: SAP FICO on Nov 12, 2009 5:09 PM

Table truncated, but segments were not cleaned

Hi,
I am running oracle 11g 11.2.0.1.0 version on ASM.
I have truncated a 3.5 GB partitioned table, but the extents are not getting dropped and space is not getting released.
the table do not have any rows now, but the dba_extents and dba_segments are still showing 3.5 gb size.
Please suggest what could be the possible reason.
Please let me know if additional information is required to answer my qustion.
regards

Here's a demo which shows that if a table is created with a large INITIAL, a TRUNCATE doesn't shrink the initial size. A MOVE with a STORAGE clause can.
SQL> create table hkc_test_99 (id_column number, data_column varchar2(10)) storage (initial 64M);
Table created.
SQL> insert into hkc_test_99 select 1,'One' from dual;
1 row created.
SQL> commit;
Commit complete.
SQL> select extent_id, bytes/1024 from user_Extents where segment_name = 'HKC_TEST_99';
EXTENT_ID BYTES/1024
         0      65536
1 row selected.
SQL>
SQL> truncate table hkc_test_99;
Table truncated.
SQL> select extent_id, bytes/1024 from user_Extents where segment_name = 'HKC_TEST_99';
EXTENT_ID BYTES/1024
         0      65536
1 row selected.
SQL>
SQL> alter table hkc_test_99 move storage (initial 64K);
Table altered.
SQL> select extent_id, bytes/1024 from user_Extents where segment_name = 'HKC_TEST_99';
EXTENT_ID BYTES/1024
         0         64
1 row selected.
SQL>
Hemant K Chitale

Transaction Type is not updated to FAGLFLEXT

Hi,
When entering asset acquisition, user will use posting key:70 and transaction type 100 and enter the asset. This is updated in the BSEG. In the FAGLFLEXT table there is column transaction type, it is
not updated..
Pl.sugesst how to rectify the above bug and let me know if any OSS notes to be applied.
Thanx & Regs
Daddala

Check the following consulting note.
https://service.sap.com/sap/support/notes/990612
You have to add scenario FIN_CONS to your ledger in the following path in SPRO.
Financial Accounting (New) -> Financial Accounting Global Settings (New) -> Ledgers -> Ledger -> Assign Scenarios and Customer Fields to Ledgers

The online conversion of my pdf file to word did not correctly convert the tables and certain other formatting. I wish to obtain a refund.

The online conversion of my pdf file to word did not correctly convert the tables and certain other formatting. I wish to obtain a refund.

Hi yammyamm,
I'm sorry that your conversion didn't work out for you. Please contact Adobe Customer Support via phone or chat, and an agent will be able to process that cancellation/refund for you. Here is the contact information: Contact Customer Care
Best,
Sara

System error: Default TXJCD is not filled in the table T001

Hi friends,
Can anyone help me out in this scenario? We are facing a peculiar problem.
We are in a upgrade project from 4.5b to ECC 6.0.Client is not maintaining any tax codes i.e they are maintaining it outside SAP.The problem is when ever the billing document is released to accounting(VF02) in ECC 6.0 it is showing this error System error: Default TXJCD is not filled in the table T001.But this is working fine in 4.5b.
Are there any basic changes regarding TAX JURISDICTION CODE is concerned from upgrade. Please provide.
Thanks in advance,
Yoga

Hi Yoga,
Probably, the program is showing error message FF799, please maintain transaction OBCL with a default tax jurisdiction code.
The tax jurisdiction code should be maintained at state level only and
corresponds to the tax jurisdiction code structure maintained in table
TTXD. For example, if your structure is 2-3-4-1. Then your default
code should be XX00000000. I suspect that the settings in transaction
OBCL are incorrect and hence the FF799 error, when shipping from a US
plant to a foreign ship-to customer (non-US).
Addional info concerning the Tax Interface for standard methods for
US taxes you can find at -   http://www.saplabs.com/projects/tax/
Documentation: Tax Interface Configuration Guide for release 4.6x
Please have a look at attached notes 112609 and 385127.
Here is the explaination that the process for tax-exempt transactions
has been changed.
Other notes you may need for OBCL :
-> 0627091   Message FF749 with billing data transfer
-> 0608159   Error FS791 during billing data transfer
-> 0380158   Jurisdiction code for export business transaction
-> 0419124   Export billing document with tax jurisdictions
I hope this information helps you,.
Regards,
Paulo

Number of records in FAGLFLEXT table

Dear colleagues,
Could You please tell me what the maximum number of records FAGLFLEXT table may contain.
I was said during FI-GL migration project in 2008 that the optimal number of records is 500 000 per year.
After having implemented new project we expect the number of records to increase approximately up to 1 500 000 - 3 500 000 records for 1 year. Is this critical?
I read at the forum that SAP recommends to have maximum 10 000 000 records in this table but it was not clarified for what period: for one year or for the whole life of the system.
Regards,
Stanislav.

- hope below notes help.
[Note 820495|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=820495]
[Note 1045430|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1045430]
Rgds.

Drill down is not working for Pivot tables,but working for chart

I have two reports and trying to navigate betwen summary report to detail report. But details report is displaying all the records .The filter condition is not working and displaying all the filters .I have Case statement in my filter.But the summary report column where the filter condition is applied is aggregated in the RPD level. Does this might be the reason ?. Is it passing different type of data type to details report ?. The filter condition is not working for Pivot table .But Chart is working fine and displaying the only selected records based on the filter condition.
Please help me with the below issue.

Hi sil174sss,
Per my understanding you are experiencing the issue with the excel report which have add the drill down action, after export to excel only the expanded nodes included and the collapsed nodes is not shown, right?
Generally, if we expand the nodes before export to excel then the excel will display the expanded details row and keep collapsed the details row which haven't expand, but we have the toggle "+","-" on the left of the Excel to help
control the expand and collapse, when you click the "+" you can expand the collapsed notes to see the details rows.
I have tested on my local environment with different version of SSRS and can always see the "+","-" as below:
On the Top left corner you can find the "1","2", this help to control the "Collapse All" and "Expand All".
If you can't see the "+","-" in the excel, the issue can be caused by the Excel version you are currently using, and also excel have limit support of this, please provide us the Excel version information and the SSRS version. You
can reference to this similar thread:
lost collapsing columns when export to excel
Please try to export other drill down report to excel and check if they work fine, if they did, the issue can be caused by the drill down action you have added in this report is not correctly, if possible, please try to redesign the report.
Article below about how to add Expand/Collapse Action to an Item for your reference:
http://msdn.microsoft.com/en-us/library/dd220405.aspx
If your problem still exists, please feel free to ask
Regards
Vicky Liu

Need information about Internal Tables

Hi Every one!
I Need some information about Internal tables. Pls help be above the same.
Thanks & with Regards,
Chandra.

Hi..,

Internal tables 
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Data Types
Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.
Line type
The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
Key
The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.

Table type
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.

Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.

Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.

Generic Internal Tables
Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures . You cannot use them to declare data objects.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.

Choosing a Table Type
The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.

Standard tables
This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
Sorted tables
This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.

Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
regards,
sai ramesh

Create a procedure which requires displaying information from two tables

What if we want to create a procedure which requires displaying information from two tables. In this situation,
I need to display all the details of an employee from an 'emp' table based on the deptno. and also their salary information which is
stored in "Salgrade" Table. Is the use of "And" the correct way of using it?
Do I need to declare all the attributes before begin or I can just access them directly? Thanks
Create Procedure findDept
( I_deptno IN number
) As
Begin
Select Ename, Job, MGR, Hiredate, Sal, Comm, Dept_no from emp and exp, grade , location from salgrade where dept_no
= I_Deptno;
Exception
When NO_Data_Found then
DBMS_Output.Put_Line(' Department not found"|| I_deptno);
End findDept;

Hi,
Besides Qwerty's remark, you've also got a quoting error:
Change
DBMS_Output.Put_Line(' Department not found"|| I_deptno);
{code}
into
{code}
dbms_output.put_line(' Department not found: '|| i_deptno);
{code}
Which leads to the question:
What do you want to do when a record is found?
Display it?

First row from Service Order Object list not stored in OBJK table

Hi all,
Please be patience with my terminology .
Could you please explain me if we have SO created based on notification, and that notification already have Equipment number, why this equipment is not created in OBJK table? So always the first row (as in attachment) is not stored in OBJK, other rows(objects) are there.
I know the EQUNR is stored in AFIH, but it's useless for us because I'm creating HANA analytical view with following join logic (simplified):
AFIH.OBKNR=OBJK.OBKNR
OBJK.ILOAN=ILOA.ILOAN
ILOA.TPLNR=IFLOT.TPLNR
ILOA.ILOAN=EQUZ.ILOAN (where EQUZ.DATBI='99991231')
EQUZ.EQUNR=EQUI.EQUNR
The join logic might not be 100% correct.
Thank you for your help.

Using the tags to format your code may help you get a response sooner than later.
This and other useful pieces of information are located in the FAQ
http://wiki.oracle.com/page/Oracle+Discussion+Forums+FAQ

Wrong balances in FAGLFLEXT table

Dear All,
I am using datasource 0FI_GL_10 to extract data into BI from SAP AFS 5.0. We are using the new general ledger. extraction is fine and delta extraction happens without any issue.
The issue is that when i look at a account balance in BI and take a trial balance in SAP and compare the account values. there are a few accounts which have differences. When i looked into it i found out that the FAGLFLEXT table which carries the totals for the accounts have wrong balances for a few accounts. I'm not sure why this is but it is a definite showstopper at the moment. I have searched for notes related to it but have not been able to find an answer to it.
Have any of you experienced this issue before? would appreciate any help you could provide me.
Thank you,
dilanke

Dear All,
This is a bug in SAP and they are looking at it to correct the issue. closing thread.

Segment is not informed in FAGLFLEXT table

Similar Messages

Maybe you are looking for