Depr key lini and lins

Dear Forum,
LINI Str.-line frm acq.value pro rata to 0 w/o interest
LINS Str.-line over rem.life pro rata to zero
May I know what is the difference for these 2?
Thanks
Rgds

Hi,
both have straight-line depreciaiton, but they are really different.
Please see in Tr. AFAMA:
LINI
Ord.depreciation     1     0007     001     003     010
LINS
Ord.depreciation     1     0011     001     003     001     5     0,0
Ord.depreciation     2     0017     001     003     013          0,0
Main Differences:
1) As you can see LINS has a second phase (5 Changeover after end of the useful life)
2) Treatment of end of depreciaiton
LINS: Dep. after plnd.life end: No
LINI:   Dep. after plnd.life end: Yes
3) Base value
LINS: 24       Net book value
LINI:   03       Replacement value
Regards Bernhard

Similar Messages

Creating Condition Table.. Key fields and line items

dear all
I am creating a Condition table and have 6 fields, I want to make 5 of them as key fields and also header line fields.
I want my 6th field as line item field but I am unable to do that. My last key field is also shoiwing in line item.
Please help.
Thank you.
Madhu.

Hi,
Check this thread
Re: VK11
Regards,
Chandra

Usr/bin/pacman-key: line 615: printf: write error: Broken pipe

I've got some instances of same error from pacman which I think is abnormal when I tried to upgrade pacman-keyring via "pacman -Syu".
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
What action should I take for the errors to maintain my system?
Searching the web and this forum won't answer my question...
The quotation of pacman.log of the upgrade sesson which evoked pacman-keyring upgrading is below:
[2013-04-20 22:04] [PACMAN] Running 'pacman -Syu'
[2013-04-20 22:04] [PACMAN] synchronizing package lists
[2013-04-20 22:04] [PACMAN] starting full system upgrade
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 1 valid: 5 signed: 64 trust: 0-, 0q, 0n, 5m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: depth: 2 valid: 64 signed: 1 trust: 64-, 0q, 0n, 0m, 0f, 0u
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2013-04-20 22:05] [ALPM-SCRIPTLET] usr/bin/pacman-key: line 615: printf: write error: Broken pipe
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Updating trust database...
[2013-04-20 22:05] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2014-01-22
[2013-04-20 22:05] [PACMAN] upgraded archlinux-keyring (20130224-1 -> 20130406-1)
[2013-04-20 22:05] [PACMAN] upgraded bash-completion (2.0-3 -> 2.1-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generating locales...
[2013-04-20 22:05] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] ja_JP.UTF-8... done
[2013-04-20 22:05] [ALPM-SCRIPTLET] Generation complete.
[2013-04-20 22:05] [PACMAN] upgraded glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded binutils (2.23.2-1 -> 2.23.2-2)
[2013-04-20 22:05] [PACMAN] upgraded m4 (1.4.16-2 -> 1.4.16-3)
[2013-04-20 22:05] [PACMAN] upgraded bison (2.7-1 -> 2.7.1-1)
[2013-04-20 22:05] [PACMAN] upgraded curl (7.29.0-2 -> 7.30.0-1)
[2013-04-20 22:05] [PACMAN] upgraded expat (2.1.0-1 -> 2.1.0-2)
[2013-04-20 22:05] [PACMAN] upgraded freeglut (2.8.0-2 -> 2.8.1-1)
[2013-04-20 22:05] [PACMAN] upgraded gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gcc (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded gpm (1.20.7-1 -> 1.20.7-2)
[2013-04-20 22:05] [PACMAN] upgraded harfbuzz (0.9.14-1 -> 0.9.16-1)
[2013-04-20 22:05] [PACMAN] upgraded isl (0.11.1-1 -> 0.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded kmod (12-1 -> 13-1)
[2013-04-20 22:05] [PACMAN] upgraded libldap (2.4.34-1 -> 2.4.35-1)
[2013-04-20 22:05] [PACMAN] upgraded krb5 (1.11.1-1 -> 1.11.2-1)
[2013-04-20 22:05] [PACMAN] upgraded lib32-glibc (2.17-4 -> 2.17-5)
[2013-04-20 22:05] [PACMAN] upgraded lib32-gcc-libs (4.8.0-1 -> 4.8.0-2)
[2013-04-20 22:05] [PACMAN] upgraded libcap (2.22-3 -> 2.22-4)
[2013-04-20 22:05] [PACMAN] upgraded libpng (1.5.14-1 -> 1.5.15-1)
[2013-04-20 22:05] [PACMAN] upgraded libtasn1 (3.2-1 -> 3.3-1)
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2013-04-20 22:05] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'default'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Building image from preset: 'fallback'
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Starting build: 3.8.7-1-ARCH
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keymap]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2013-04-20 22:05] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Creating cat initcpio image: /boot/initramfs-linux-fallback.img
[2013-04-20 22:05] [ALPM-SCRIPTLET] ==> Image generation successful
[2013-04-20 22:05] [PACMAN] upgraded linux (3.8.5-1 -> 3.8.7-1)
[2013-04-20 22:05] [PACMAN] upgraded orc (0.4.16-1 -> 0.4.17-1)
[2013-04-20 22:05] [PACMAN] upgraded perl (5.16.3-1 -> 5.16.3-2)
[2013-04-20 22:05] [PACMAN] upgraded psmisc (22.19-1 -> 22.20-1)
[2013-04-20 22:05] [PACMAN] upgraded sqlite (3.7.16.1-1 -> 3.7.16.2-1)
[2013-04-20 22:05] [PACMAN] upgraded sudo (1.8.6.p7-2 -> 1.8.6.p8-1)
[2013-04-20 22:05] [PACMAN] upgraded systemd (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded systemd-sysvcompat (198-2 -> 201-2)
[2013-04-20 22:05] [PACMAN] upgraded tar (1.26-2 -> 1.26-3)
[2013-04-20 22:05] [PACMAN] upgraded wayland (1.0.6-1 -> 1.1.0-1)
Thanks in advance!

I just encountered the same issue with the latest update. I never had something similar to this:
:: Retrieving packages ...
archlinux-keyring-20130525-2-any 367,2 KiB 1023K/s 00:00 [################################################################] 100%
linux-3.9.5-1-x86_64 45,5 MiB 1015K/s 00:46 [################################################################] 100%
linux-headers-3.9.5-1-x86_64 5,6 MiB 1117K/s 00:05 [################################################################] 100%
gnome-bluetooth-3.8.1-2-x86_64 835,0 KiB 955K/s 00:01 [################################################################] 100%
gnome-documents-3.8.3-1-x86_64 305,0 KiB 1034K/s 00:00 [################################################################] 100%
vlc-2.0.7-2-x86_64 7,6 MiB 1162K/s 00:07 [################################################################] 100%
(6/6) checking keys in keyring [################################################################] 100%
(6/6) checking package integrity [################################################################] 100%
(6/6) loading package files [################################################################] 100%
(6/6) checking for file conflicts [################################################################] 100%
(6/6) checking available disk space [################################################################] 100%
(1/6) upgrading archlinux-keyring [################################################################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
usr/bin/pacman-key: line 615: printf: write error: Broken pipe
-> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
-> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
-> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
-> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...

Unplanned adjustment for closed FY and changing of depr key for new FY

Hi Everyone,
i understand that this is a common problem and some folk have already post similar post, however i find that confusing or maybe i have not search enough.
here is my problem:
we have gone live for 2 year, since 2009. we have posted depreciation based on the old depre key for the last 2 years. in the current FY, the auditor have found a mistake and wanted to change the depreciation key and post the unplanned depreciation for the overcharge. may i know the correct steps to execute this change? and is there any important area that i have to pay attention to?
please take note that the current FY is already coming to an end.
example of steps:
1. post the overcharge amount through unplanned depreciation AFAA
2. change the depreciation key and change the start of depreciation date, expired useful life
3. run depreciation posting for planned and unplanned
Regards,
John

1. post the overcharge amount through unplanned depreciation AFAA
2. change the depreciation key and change the start of depreciation date, expired useful life
3. run depreciation posting for planned and unplanned
1. You create a separate transaction type for this purpose of else use 640 or 641. Posting them by using AB01 or ABSO. At this point this will be at FI-AA only, when you run depreciation to AFAB, then the GL entries will be posted.
2. You need to execute LSMW in order to change the Dep. Key, Depreciation Start Date and Expired Useful.
3. You run the repeat run in AFAB, if you have already posted the depreciation, otherwise, usually select "planned posting run".
Edited by: Ravi Sankar Venna on Dec 9, 2011 1:49 PM

Infoset Join condition on Key feilds and data fields

Hi Guys,
I have a requirement to biuld the Info set with join conditon on two DSO's the info objects which i am using in the JOin condition are defined as data fieds in one DSO and defined as key fields in another DSO, is it possible to define join condition on key fields and data fields.
The two info objects are
                       0AC_DOC_NO
                       0ITEM_NUM
These two info objects are defined as data fields in DSO :   0LIV_DS1   Invocie verificaion
                                                        key fields in DSO:    0FIAP_0o3 FI AP Line Item
Please suggest me is it possible to define join the condtion on the data fields and key feilds.
Thanks
Best regards
SG

Hi
yes you can create join, you will get any issue in reporting level.
example: Say i want to create Info Set on 0MATERIAL and Sales DSO.
In 0MATERIAL Info Object it is key filed, but in my DSO 0MATERIAL is data field.Still we can create
Creation of join is dependent on fields common in your source objects.
check out the below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7?QuickLink=index&overridelayout=true
Regards,
Venkatesh
Edited by: Venkateswarlu Nandimandalam on Sep 27, 2011 2:26 AM

Key fields and data fields in a DSO ??

i have a question regarding key fields and data fields in a Standard DSO...
i am using 2 datasources to build a open sales report 2LIS_11_VASTH and 2LIS_11_VASTI i am pulling in data from these 2 data sources to a DSO and i am wondering what infoobjects should be in the key fields and data fields .....does this reflect back to table VBUK and VBUP tables and does the key field in the DSO have to be the key fields in VBUK and VBUP tables ???? or what really should be included as key fields and data fields ????
please help....

If you look at the various SD tables, VBELN and POSNR are commonly used as the document number and document line item.
For VBAP and VBUP, it's referring to the Sales Order Line Item with the columns VBELN and POSNR as the key for both tables. However, if you look at the LIPS table, which is the Delivery Line Item table, it too has VBELN and POSNR as the key. Likewise, the VTTP table, which is the Shipment Line Item table, also has VBELN and POSNR as the key.
While using RSOSFIELDMAP as a map is a fairly good "rule of thumb", it still needs to be used with a level of skepticism.

Which FM can append table sturcture(add key fields and so on)

Hi everybody,
does any one of u know a FM which append structures of table (to add the key fields and so on) in ABAP dictionary.
The FM DDIF_TABL_PUT is only used to write a new table and I don't want to call this FM twice to realize my application.
Thanks in advance!
Liying

Hi Raja,
I got a runtime error:Perform_NOT_FOUND
EXCEPTION:CX_SY_DYN_CALL_ILLEGAL_FORM
following is my codes:
DATA ATA DDFIELDS LIKE DDFIELD OCCURS 2 WITH HEADER LINE.
DATA NAME LIKE DD02L-TABNAME.
DDFIELDS-FIELDNAME = 'F3'.
DDFIELDS-POSITION = '3'.
DDFIELDS-KEYFLAG = 'X'.
DDFIELDS-DATATYPE = 'INT4'.
APPEND DDFIELDS.
DDFIELDS-FIELDNAME = 'F4'.
DDFIELDS-POSITION = '4'.
DDFIELDS-KEYFLAG = ''.
DDFIELDS-DATATYPE = 'INT4'.
APPEND DDFIELDS.
NAME = 'ZTEST'.
CALL FUNCTION 'DB_ADD_TABLE_FIELDS'
    EXPORTING
        TABNAME = NAME
    TABLES
        DDFIELDS = DDFIELDS
    EXCEPTIONS
        FIELDS_NOT_ADDED = 01
        PROGRAM_NOT_GENERATED = 02
        PROGRAM_NOT_WRITTEN = 03
        TABLE_DOES_NOT_EXIST = 04.
What might be the reason?
B.R.
Liying

Issue with Period Control 03 for Depri key MSTL with 6446

Hi Gurus,
We want to use mid-month calculation for Dep. key MSTL using period control 03 (i.e. 03/03/03/03). We are also using 6446 as year-depedent Fiscal year (i.e. Jan and Dec 6 weeks other rest 4 weeks). period control 03 is pro rata at mid period
period 12 for 2009 start 11/14/09 ends 12/25/09
period 1 for 2010 start   12/26/09 ends 02/05/10
as per period control 03 mid month is Dec-04-2009 (setup in OAVH)
When i acquire an asset on Dec-04-09, the dep start date is Nov-14-09 which is correct and all calculation is correct
however when i acquire an asset on Dec-06-09 the dep start date is still Nov-14-09 which is not correct infact it should start dep from next month which will be Dec-26-09 (This is 1st period of Fiscal year 2010)
As mentioned above we are using 6-4-4-6 fiscal year
When acquiring an asset with mid month concept at year end we are facing problem in depri start date and hence calculation.
The setting in OAVH for period control 03 are as below
FV   Period Control     Desc.                             Year   Month   Day    Period    MidMonth
NL        03              Pro rata at mid period          2009    12        4         12           ticked
NL        03              Pro rata at mid period          2009    12        25       12           ticked
NL        03              Pro rata at mid period          2009    12        31        1            ticked
NL        03              Pro rata at mid period          2010    1          15        1            ticked
Thanks in advance

Deepak,
Your period 12/2009 starts and ends between 11/14/09 ends 12/25/09. Now you acquire an asset on 12/4/2009. As per OAVH, you want depreciation calculation start mid-period. Then how is depreciation start date of Nov 14, 2009 for this case?
Then you acquire an asset on Dec6, 2009. This, as per OAVH, falls into period 12/2009. Then why should the calculation start from period 1/2010 for this case?
Thanks,
Asheesh

DSO - What key fields and data fields in dso

Hi experts,
I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

Check this for standard DSO:
http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
Thanks...
Shambhu

What is diffrernce between key figures and characteristics?

Hi all,
I am a newbie to SAP BI....i am doing Masters in ERP(SAP)....I have confusion about what is basic difference between key figures and characteristics?
Why do we have to define attributes in characteristics?
If any one can refer me a thread that answers my questions or explain with very lucid example I will highly appreciate it.....please answer this question as I have just spend 4-5 months studying BI and have not really implemented in the Industry but we do have access to SAP BI where we perform tutorials....
Also please let me know the links to materials where basics of BI are explained in a very simple way.....
Thanks,
Regards,
Rahul

KF is anything which can quantitatively measured: Amount, Number, Value, Price... whatever you want to measure is called Key Figure. This key figures are also called KPI (Key Performance Indicator). If you want to know the number of sales orders, the number of deliveries, the amount of deliveries... all are key figures
And to add to that, key figures are also divided into two:
Cumulative KF: Like I said, amount, value, price
Non-cumulative KF, this is different kind of key figures which shouldn't be summed up, for example: Age, Inventory, Number of Employees. When you measure this key figures, you don't add the age of every body, because that doesn't make any sense, but adding the sum of all deliveries, or adding all Sales does make sense, that is the difference between the two key figures.
Characteristics: are anything which couldn't be quantitatively measured: material, customer, plant, employee ID and so on...
Aways, in BI you measure the KF against the Key figures..
thanks.
Wond

Key Fields, Data Fields, Key Figures and Characteristis, Dimesions & Key Fi

Hi All,
Can any one please describe more about the below terms and with the Example....
Like when we identify which one is Key filelds and Data fileds, how to distingush creating new dimesions (Is it based on user reporting) Key figures in Dimestions...
DSO/ODS: Key fields, Data Fields
InfoCube: Dimensions, Key Figures
Infoobjects: Key figures, Characteritics
Regards,
Prem

Hi,
Search through SDN for more information on these concepts,
Re: ods data fields or key fields?
Re: Key Fields and Data Fields in ODS
defining Key -field and data fields
Regards,
Mani

Prerequsites for deciding Key fields and data fields

Hi
I would like to know the criteria to decide upon KEY fields and Data fields for an infoprovider.

Hi,
What is a Key field in a Database and How should I choose one?
Keys are crucial to a table structure for many reasons, some of which are identified below:
They ensure that each record in a table is precisely identified.
They help establish and enforce various types of integrity.
They serve to establish table relationships.
Datafields may be Charecteristics and it may be keyfigures
Regards,
Marasa.

Difference b/w KEY FILEDS and DATA FILEDS

Hello Experts...!
What is the difference between char , KF and keyfields and data fileds...?
we are going to map this in the ODS concept.
char to keyfileds.
keyfig to datafields.
regards,
amit.

Hai Amit,
In ODS Key fields means the Primary keys characteristics.
So when ever we map the primary key characteristics (ie characteristics on which some info objects are dependent) should be assigned to key fields
and to data fields the Key figure Infoobjects as well as characteristics which does not have the primary/in-dependent fileds
Regards
Madhavi

Identify key fields and data fields

Hi
i have datasource 0co_om_cca_9 .
i want build 1 DSO, how can i identify what are key fields and data fields to build DSO based on that datasource.

Hi sunnel,
The DSO are like 2-D database tables.
We use the technical keys here in counterpart to the business keys in Infocubes.
The key fields are the one based on which the records are identified uniquely in the database table.
And the data fields are the ones which are aggrgated or summarised or overwritten based on the value in key filed.
For example:
The ID no.s of the employees will be unique and it can be used as a key field.
The feilds like the Salary taken by the employee every month :"SALARY"
and the no. of leaves they taken: " NO. OF LEAVES" can be used as data fields.
So that the salary or the leaves taken by a particular employee can be aggregated based on her/his ID no.
The key fields in DSO doesnty mean Key figures.The key field means any unique key or a key based on which the records are sorted in the DSO
And key figures are the data fields.Some of the Characteristics can also be data fields in DSO.
Please give points if u r satisfied wit the information
Also let me know if u hav any doubt and if any thing is wrong.
Regards,
Kalpana M

Defining Key -field and data fields

Hi all
i have to define Key-Fields and data-Fields for a DSO(say DSO3).
DSO1 is a combination of DSO2 and DSO3..
DSO1 and DSO2 are SAP defined DSOs.
DSO3 is a User defined DSO.
my assumption:
   DSO3 has 30 fields
   DSO2 has 16 fields.
   can i create the DSO3 with remaining 14 fields which is there in DSO1?
   or i have to create the DSO3 with 30 fields(all DSO1 fields).
can any body explain....
Thanks & Regards
krishna

The problem is not how many fields you create where, the issue is where is the data is going to come from.
Since you data is going from DSO3 to DSO1and if the field is already getting populated in DSO1 from DSO2, then you don't have to worry about populating those fields again, unless and otherwise you want to overwrite them.
Remember any fields exist in both DSO3 and DSO2 which overlapping will be overwritten by the latest update.
Again, going back to your question, you should consider does your datasource has missing fields (14 of them).
thanks.
Wond

Depr key lini and lins

Similar Messages

Maybe you are looking for