Sort key in GL

Hi guys,
What is the purpose of the sort key in the GL account?
why does it do.
Thanks,
Srikanth.

Hi Srikanth,
The sort key helps to fill up the field 'ASSIGNMENT' in all the documents. There are a number of default sort keys provided by SAP. You have to select an appropriate one in the master data (GL/Vendor/Customer) to get a meaningful entry in the assignment field of the document line item.
The assignment field helps you to -
1. Sort the documents/line items in a report
2. helps in the automatic clearing process
Regards,
Mike

Similar Messages

The sort key in the master data G/l account and master data customer

Sort Key
Hi All,
in the master data (control data) of the G/l account XXXXXX (it's a reconciliation account) I've filled in the sort key the value ZZ1 (XBLNR).
Instead, in the master data of a certain customer which has its Reconciliation Account equal to xxxxxx, I've filled in the sort key ZZ2 (BELNR).
Posting a document, I need that the Assignment number is equal to XBLNR.
How could I obtain this?
Thanks a lot
G.

Hi,
You are assign short key with Customer master in ZZ1 (Account Management Tab Bottam).
I think it is helpful to you.
Regards,
Spradip

Importance of the Sort key?

Hi SAP Gurus,
I have posted g/l transaction (gl with out sort key), In open item report assignment no only missing.
Just clarify what is the importance of sort key & assignment no?
In sort key I am finding different no (i.e 001,012,018) can any body tell me what the logic behind this numbers?
While creating vendor master If give the customer sort key , in customer open items assignment no not updating ..other than this, Is there is any difference ?
Thank You
Ramakanth

Hi...if i am not wrong as the name specifies sort keys are used to sort the line items.... as u said there are differet options for sort key each one sorts the line item in particular manner ...that is one sort key tells that the line items are displayed according to the date ...in some like customer reconciliatio account the sort key sorts the line items according to customer numbers instead of date because the sorting of line items for customer records is given in corresponding cutomer master record.... and generally customer/vendor reconciliation accounts are not flagged for open item management because in real time a customer/vendor reconciliation has a number of line items and if these are flagged for open item management this may limit the system capabilith as it utilizes lot of system resources to pull up all the line items from all the customers ... hence the accounts corresponding to each customer are displayed rather than all the line items....

Sort Key .... where we can see the activity in GL, Vendor, Customer mater

Hi gurus,
what is the use Sort key,
where we can see that activity. in GL Accounts, Vendor, customer master sort key where we can see effects. what is the use, how it will sort, where i can see.
Thanks for your reply.
Anil

Dear Anil,
Sort key is the one that fills the "Assignment field" of a line item automatically.
For example, for the GR / IR accounts, we normally give the "Purchase Order" as the sort key. This will make the line items in the GR/IR account to be filled with the Purchase order and the Item number.
The automatic clearing (F.13) works with the assignment field. In case the net of two line items (Dr - Cr) is equal to zero and the assignment field of these two lines are the same, then the system will automatically clear these two lines. Hence "Sort key " fills the assignment field and is very useful in automatic clearing
regards
Venkatesh
Assign points if useful

EXPLAIN SORT KEY IN G/L MASTER

Can anyone tell in detail what is the use of sort key in G/L master. When we choose to sort suppose by posting date, what is its impact on a G/L document. I am still not clear on this.
Another question what is the field Open Item Managed used for in G/L master. Explain in detail on this one too.
Thanks
Lakshmi

<b>This is the function of SORT KEY. Pl let me know if you require more info</b>
The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.
For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.

Addition of new field in GL sort key

Hi all
I have inserted a new field VBELN: Billing number in Choose sort fields in IMG for S: GL accounts. Then i have created a new sort key in tcode OB16 with this field VBELN & entered this new sort key in a revenue GL.
However in the accounting view of the invoice, the assignment number is blank.
Please advise.
Thanks
-Dinesh

hi
thanks for ur prompt reply.
yes i am expecting it to appear in the automatic line item display.
can u clarify what do u mean by substitution... i am a SD consultant so will appreaciate if u cud please elaborate.
thanks.
-Dinesh

Sort Key in G/L Acounts and Customer MAster Records.

Dear SAP Guru's,
What is the specific use of the Sort Key?How will this effect the Line item entry in FBL5N?
In our Company The G/L Accounts the sort key is maintained As 000 Allocation Number.
_Also In Customer Master-->Company Code Data
The Feild sort key : It is maintained "000" Allocation Number _
If I change the sort key Now after 1 year of several records updated Will the System sort according to the changed sort key?
I want the sort key to be document Number Now after a year will the previous records be shown with the immediate effect.
I have gone through this link.
https://www.sdn.sap.com/irj/sdn/forums.
regards,
Amlan Sarkar

Sort key field is also known as Allocation field.
The u201Callocation fieldu201D is populated automatically onto line items, during document entry, based on the default sort indicator set in the master record.
When you display or change line items, they are displayed in a standard sort sequence as per sort key defined in master records.
Sort key is defined in G/L master, Vendor master and Customer master. The key defined here is taken as the default key by the system when you want to display the line items pertaining to that account.
The sort key determines what is populated in the allocation field upon posting.
Changing the sort key will only change future postings not already existing line items.

Sort Key

in GL account we maintain sort key 010 but the line item report fbl3n not display sort key wise.

Hi,
The purpose of the sort key is for two purposes:
If you maintain the sort key in GL Account:
Assignment field in line item report FBL3N would automatically be filled with this sort key.
Second this is you can sort or sub-total on this assignment field.
Hope this helps you.
Regards,
Ravi

Assignment in Billing document displays different value than sort key

Hello,
The billing document is generated from VBRK where no manual intervention is possible. The accounting document which gets generated is directly posted in system.
Sort key is used to fill up the assignment field at line item level. In case we have a sort key defined at the GL account at company code level & also at Customer account at company code level system will give priority to the customer sort key.
In our case we have 2 customers where the settings are identical at both GL account & customer master at company code level.
The sort key has been defined as posting date at GL account level & Document number + fiscal year at customer level.
Hence system always updates assignment field with Document number, fiscal year.
However in a peculiar case when we have generated the billing document in 1 case the assignment field has been correctly populated whereas in the other a WBS element has appeared.
Could you explain from how & where this WBS element has appeared when other billing documents for the same customer are having the assignment field being populated correctly.
Thanks & Regards
Shreenath

In addition to Ajay's suggestion, please note three exchange rates you can find in billing document. They are
VBRP-KURSK = Document currency for Price determination which depends on the setting of TVCPFLP-PFKUR in copy control
VBRK-KURRF = Document currency for FI postings. If you input manually in sale order field VBKD-KURRF, it is copied to above table / field. Otherwise, this will be determined during invoice generation. For more details see Note 36070 - Fixed foreign currency rate for Accounting document
KOMV-KKURS = this is for local currency at Price condition level which will be determined based on pricing date.
G. Lakshmipathi

Reg the Sort Key field in Vendor Master Record

Hi MM Gurus,
I have the requirement of displaying the Purchase Order number & Line Item number in the Accounting document of the Goods Receipt. i.e., in the "Assignment" field.
I have made the necessary configuration in FS00 for the specific GL account & also specified 014 code in the corresponding Vendor master record.
However, once I post the GR document, and checked the "Assignment" field, it displays only the Purchase Order number and not the Line item number.
Kindly help me on this.
Best Regards
Sudhi

Have you posted the above document after set 014 in FS00 ?
Can you test the same in your practice client.
Check the document for more details Sort Key Functionalities and the wiki content How to update Assignment field in FBL*N report - ERP Financials - SCN Wiki
(Note: The changes of FS00 as 014 will not effect old documents)

Sort key in vendor master ..?

Hi all
Can anybody explain me , what is the use of sort key in vendor master .
What we have to select in sort key options screen...
Please explain me clearly..
Thanks
sap-mm

hi,
use of sort key is basically for the Account person.
when document is posted in MIRO it is liable to to pay for that vendor.
now account person can see the list of that document in his report FB03.
wherein he can see the reference of that document with the help of SORT KEY.
e.g
say if sort key is selected as PO no and Po item.
then in FB03 he can see the
accounting document with reference of PO no and item no in PO.
regards,
sujit

T.code FS00: changing the SORT KEY in the 'Control data'

Hi All,
I need to change the SORT KEY in the 'Control data' of a G/L master data.
Is there a SAP standard program by which the field 'Assignment' is updated.
Thanks
Gandalf

Sorry,
i did't mean updating a field ...
I meant:
is there a program which changes the content of the field 'Assignment' according to the new content of the field 'Sort key'?
Thanks

Error ORA-01467: sort key too long

Hi. I have just come across the error ORA-01467: sort key too long .
In the Oracle documentation, the 2 line
description of this error basically says that there may be too many columns
or group functions in the query, so I need to reduce the number of columns
in the query.
Here's the problem. The documentation does not say how many the limit is.
The query is quite complex, I suppose, but I don't see why it should be a
problem. In a nutshell, the main table has 3 text fields (which are the
index) and 154 floats. The query joins one of the text fields to another
table to get a lookup value and selects this out, along with the other two
text fields and the SUM of the numeric fields. The query groups by the two
text fields and the lookup.
I guess I saw this when I was using MS SQL Server 6.5 and tried to sum more
than 125 columns, but that went away in SQL Server 7. I am using Oracle 8
at this point but need to support Oracle 7, too.
I guess what I am looking for (at least) is the maximum number of columns
that can be in a grouping/summing query. I'd also like to know if this can
be worked around by changing a setting on the server, something to set the
maximum number of sums to 1000, perhaps? I am fine with working around this
in my software if I need to, as I have done previously (I took the first 125
sums into a temp table, then the next 125, etc. and joined the resulting
tables to get my results), but would really like to get a workaround that
was server-based, if possible.
Thanks for your help!
null

Hi. I have just come across the error ORA-01467: sort key too long .
In the Oracle documentation, the 2 line
description of this error basically says that there may be too many columns
or group functions in the query, so I need to reduce the number of columns
in the query.
Here's the problem. The documentation does not say how many the limit is.
The query is quite complex, I suppose, but I don't see why it should be a
problem. In a nutshell, the main table has 3 text fields (which are the
index) and 154 floats. The query joins one of the text fields to another
table to get a lookup value and selects this out, along with the other two
text fields and the SUM of the numeric fields. The query groups by the two
text fields and the lookup.
I guess I saw this when I was using MS SQL Server 6.5 and tried to sum more
than 125 columns, but that went away in SQL Server 7. I am using Oracle 8
at this point but need to support Oracle 7, too.
I guess what I am looking for (at least) is the maximum number of columns
that can be in a grouping/summing query. I'd also like to know if this can
be worked around by changing a setting on the server, something to set the
maximum number of sums to 1000, perhaps? I am fine with working around this
in my software if I need to, as I have done previously (I took the first 125
sums into a temp table, then the next 125, etc. and joined the resulting
tables to get my results), but would really like to get a workaround that
was server-based, if possible.
Thanks for your help!
null

Sort key too long - maximum number of columns in select statement

the sort key too long is caused by either too many group
functions or too many columns selected. Does anyone know the
maximum number of columns that can be selected in one statement ?

The Oracle 9i reference states ...
The GROUP BY expression and all of the
nondistinct aggregates functions (for example,
SUM, AVG) must fit within a single database
block.
... and the Oracle 9i SQL Reference states that ...
An order_by_clause can contain no more than 255
expressions.
You could check your own documentation, but i think it will
be the same.

Bridge Sort Order - Secondary Sort Key

Noticed an anamoly to sort order when rating images.
I have sort order set to Ascending by date. Everything starts off fine - all images in the correct order. When I start labeling the images (using numbers 6, 7, 8, 9) the sort order starts changing.
I have several images with the same exact date/time (e.g., 8/22/08 10:15:13) - my camera shoots 6 frames per second.
I start labeling "three" images with the same date/time - as I do, the image I label goes to the "end" of the "three" that have the same date/time stamp. So, now an image I just labeled is moved in the order and I end up labeling it again - which based on how bridge works actually undoes the label - label does a toggle.
Then I hit the next image and rate it - same thing. appears to be sorting on a secondary key when the date/time are the same for multiple images.
Is there a way to stop the secondary sort key affect. It really screws up the labeling flow.
Image order:
Image01
Image02
Image03
Label Image01 as a "6" - order changes to:
Image02
Image03
Image01
So now image01 is back in the labeling flow...

To further explain this issue:
Original file order:
1
2
3
I look at each file then star File # 1. Instantly, the files rearrange to:
3
2
1
So I back track and start the sequence over (so that I can see files 2 and 3). So I decide I also like file # 2. The order rearranges again into:
1
3
2 or something like that
By now, I'm all mixed up as to what order the event actually happened. The more I star, the more the files rearrange. When I go back to see the rearranged files, they rearrange again. It's all very frustrating when I'm trying to edit a wedding and tell the story. It's imperative that I see all different camera files in order.

Sort key error

I am getting sort key error when I run the below error. what is the problem with this query
select a.table_name child_table,
a.constraint_name child_constraint,
max(decode(a.position, 1, a.column_name,NULL)) ||
max(decode(a.position, 2,', '||a.column_name,NULL)) ||
max(decode(a.position, 3,', '||a.column_name,NULL)) ||
max(decode(a.position, 4,', '||a.column_name,NULL)) ||
max(decode(a.position, 5,', '||a.column_name,NULL)) ||
max(decode(a.position, 6,', '||a.column_name,NULL)) ||
max(decode(a.position, 7,', '||a.column_name,NULL)) ||
max(decode(a.position, 8,', '||a.column_name,NULL)) ||
max(decode(a.position, 9,', '||a.column_name,NULL)) ||
max(decode(a.position,10,', '||a.column_name,NULL)) ||
max(decode(a.position,11,', '||a.column_name,NULL)) ||
max(decode(a.position,12,', '||a.column_name,NULL)) ||
max(decode(a.position,13,', '||a.column_name,NULL)) ||
max(decode(a.position,14,', '||a.column_name,NULL)) ||
max(decode(a.position,15,', '||a.column_name,NULL)) ||
max(decode(a.position,16,', '||a.column_name,NULL)) child_columns,
c.table_name as parent_table,
b.R_CONSTRAINT_NAME parent_constraint,
max(decode(d.position, 1, d.column_name,NULL)) ||
max(decode(d.position, 2,', '||d.column_name,NULL)) ||
max(decode(d.position, 3,', '||d.column_name,NULL)) ||
max(decode(d.position, 4,', '||d.column_name,NULL)) ||
max(decode(d.position, 5,', '||d.column_name,NULL)) ||
max(decode(d.position, 6,', '||d.column_name,NULL)) ||
max(decode(d.position, 7,', '||d.column_name,NULL)) ||
max(decode(d.position, 8,', '||d.column_name,NULL)) ||
max(decode(d.position, 9,', '||d.column_name,NULL)) ||
max(decode(d.position,10,', '||d.column_name,NULL)) ||
max(decode(d.position,11,', '||d.column_name,NULL)) ||
max(decode(d.position,12,', '||d.column_name,NULL)) ||
max(decode(d.position,13,', '||d.column_name,NULL)) ||
max(decode(d.position,14,', '||d.column_name,NULL)) ||
max(decode(d.position,15,', '||d.column_name,NULL)) ||
max(decode(d.position,16,', '||d.column_name,NULL)) parent_columns
from USER_cons_columns a, USER_constraints b , USER_constraints c, USER_cons_columns d
where a.constraint_name = b.constraint_name
and b.constraint_type = 'R'
and a.owner = b.owner
and a.owner = 'SCOTT'
and b.r_owner = c.owner
and b.R_CONSTRAINT_NAME = c.constraint_name
and c.constraint_name = d.constraint_name
and c.owner = d.owner
group by a.table_name, a.constraint_name,c.table_name,b.R_CONSTRAINT_NAME
order by child_table;
ERROR at line 37:
ORA-01467: sort key too long

make a short query and union to solve
select a.table_name child_table,
a.constraint_name child_constraint,
max(decode(a.position, 1, a.column_name,NULL)) ||
max(decode(a.position, 2,', '||a.column_name,NULL)) ||
max(decode(a.position, 3,', '||a.column_name,NULL)) ||
max(decode(a.position, 4,', '||a.column_name,NULL)) ||
max(decode(a.position, 5,', '||a.column_name,NULL)) ||
max(decode(a.position, 6,', '||a.column_name,NULL)) ||
max(decode(a.position, 7,', '||a.column_name,NULL)) ||
max(decode(a.position, 8,', '||a.column_name,NULL)) ||
max(decode(a.position, 9,', '||a.column_name,NULL)) ||
max(decode(a.position,10,', '||a.column_name,NULL)) ||
max(decode(a.position,11,', '||a.column_name,NULL)) ||
max(decode(a.position,12,', '||a.column_name,NULL)) ||
max(decode(a.position,13,', '||a.column_name,NULL)) ||
max(decode(a.position,14,', '||a.column_name,NULL)) ||
max(decode(a.position,15,', '||a.column_name,NULL)) ||
max(decode(a.position,16,', '||a.column_name,NULL)) child_columns
from USER_cons_columns a, USER_constraints b , USER_constraints c, USER_cons_columns d
where a.constraint_name = b.constraint_name
and b.constraint_type = 'R'
and a.owner = b.owner
and a.owner = 'SCOTT'
and b.r_owner = c.owner
and b.R_CONSTRAINT_NAME = c.constraint_name
and c.constraint_name = d.constraint_name
and c.owner = d.owner
group by a.table_name, a.constraint_name,c.table_name,b.R_CONSTRAINT_NAME
order by child_table

Sort key in GL

Similar Messages

Maybe you are looking for