What is safty delta and safety interval

Hello,
PLease tell me What is mean by Safety Delta and Safety Interval?

Hi,
Safety interval should be set so that no document is missed even if it was not stored in the DB table when the extraction took place.
Example for Determining Selection Intervals with a Generic Delta:
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again. If a record is created when load was running, those records may get lost.
To prevent this situation, lower limit can be used to backup the starting sequence number. This may result in some records being processed more than once; therefore, be sure this DataSources is only feeding an ODS Object
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Assign points if this is needful.
Rgs,
I.R.K

Similar Messages

Generic Delta with numeric pointer (Without safety interval and no field)

Hi
We have problems with Generic Delta extraction. Our previous Dev has created the data source with numeric pointer as the data source without any safety interval and without any field for numeric pointer selection even we have the date field (creation and change dates in view)....
He created the generic delta with numeric pointer and Additive delta selection on top of view (EKKO,EKPO and EKKN). So we are missing lot of records. Now I need to fix this asap, I have done generic delta with timestamp and cal day with change/creation date.
Now in order to fix our delta loads should I use the cal day as the delta pointer with change or creation date already available or is it ok to use numeric pointer with additive delta and safety lower limit as 10 or 20 with upper limit blank?
Also Should I use any field in the field nm section or is it ok to leave it blank ? Please advice...
Note: I checked the missing delta records in ECC and the change timing is in the afternoon and our load time is only night...We also have several other data sources with same settings (numeric with no safety and no field) but it is not giving any issues.
Thanks
Edited by: ganesh uttitti on Jan 26, 2011 10:33 PM

Hi Ganesh ,
I'm a little confuse,Why are you not use LO Delata for it?

WHAT IS GENERIC DELTA

Please explain me what is generic delta and how to create generic datasource for transaction data?

Hi,
Generic extraction
Usage:
1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
3. FI-SL requires generic extractors.
How:
You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
Steps
Log on sap R/3.
Step 1. create a table or view for generic extraction in se11.
Step 2. Goto t-code RSO2
Step 3. Here u have to decide whether to extract transaction data or master data attributes or texts.
Step 4. suppose if u have opted for transaction data,then give name in the column ex:ztd_m(data source name)
Step 5. select create button,this will take u to another screen.
Step 6. Here u have to decide from which application component u r extacting data.Ex: SD,MM,..
Step 7. in this screen u have to fill short disciption,medium,long( these r mandatory).
Step 8. then U have to Table name or view name which u have created in se11.
Step 9. I f u want to maintain generic delta then u can select generic delta in top left hand side corner.
Step 10. in next screen u have to give some field which is primary key.
step 11. here u to specify whether time stamp or cal day or numeric pointer depending on u r requirement.
step 12. then u have to specify whether new status for changed records or additive delta.
If u choose additive delta ,then u have to load data to infocube or ods object.
If u choose new status for changed records, then u to load data to ods object only.
Step 13. then save it.
Step 14. then logon to sap bw ,then replicate the data source then as usuall.
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Thanks,
JituK

Doubt Reg Generic Delta "Safety Interval" Setting

Hi Experts,
I have a doubt regarding Setting "Safety Interval Upper Limit" and Lower limit in RSO2 for generic delta.
What does this setting imply?
If I do setting for calender day say both 1 then wht will be difference between delta before setting amd after setting?
Plz explain in terms other tham help provided...
Points will be awarded to say thanks..
Thanks in advance,
Sorabh

Hi Sorabh,
Here some SAP informations:
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure. The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read. Leaving the value blank increases the risk that the system could not extract records arising during extraction. Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00. A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction. For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Extracted Data Delta Type
The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.
A distinction is made between the following:
1. Additive delta
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
2. New status for changed records
Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
Check also examples in "How to... Create Generic Delta" under www.service.sap.com/bi.
Ciao.
Riccardo.

What type of Data target is used when the safety interval is used?

Hi ,
what type of Data target is used when the safety interval is used in generic delta in datasource?DSO or cube or cube?
Pls explain me ?
Thanks,
Nimai

It's up to your reporting requirement to go for dso or cube..
I prefer to having staging with DSO and then further reporting on Cube ..
It's always easier to manage when you have any changes to the cube .. you need not to extract data from R/3 .. if you have dso you can extract directly to cube
Another thing is -for any reason some of your records got corrupted so you can have full loads to dso which has the overwrite functionality... and sends delta records to cube. even in cube you can do selective deletion but we have to very careful to avoid double records in next loads
Edited by: Srinivas on Jul 29, 2010 8:23 PM

Regd Safety Interval Lower Limit for Generic Delta

Hi All,
Safety Interval Upper Limit =1 for a Generic Delta would get Delta based on yesterday's BW data.
What would Safety Interval Lower Limit would do for a Generic Delta .
Your inputs please
Sree

Hi,
just a short example:
you run a init today --> 20070525 (internal date format).
for the next delta tomorrow the system takes the last extraction date - 1 day so 20070524 for data selection and will store 20070526 as last extraction date and so on.
This is to make sure that you will get all additional records extracted which were changed or created on each extraction date, but after last extraction. OK, you will get some records twice, but therefore you normally post the data to a ods via overwrite mode and this will take care about the 'real' delta while doing the further posting to the cube.
Hope this helps
kind regards
Siggi

What is the significance of Safety Upper Limit and Lower Limit

Hello Experts,
I was trying to create a generic datasouce in rso2 , while setting the delta specific field I have selected date field and I need to know the significance of other two input fields provided over there:
Safety Interval Upper Limit.
Safety Interval Lower Limit.
and check box Real Time Enable.
Thanks,
Vijay

Hi Vijay
Safety Interval Upper Limit of Delta Selection This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure. The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read. Leaving the value blank increases the risk that the system could not extract records arising during extraction. Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00. A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either. For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number). Safety Interval Lower Limit This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction. For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems. Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable. these are used to determining the delta in a datasource: 1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format. 2. Calendar day - The field is a DATS8 field which always contains the day of the last change. 3. Numerical pointer - The field contains another numerical pointer that appears with each new record .
also dwload this How to Generic Delta doc https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
2.
You can determine the upper limit of the time. To do this, you specify a time period relative to the current date. The time unit for the time period can be specified in days, weeks, months, quarters, years, posting periods, or fiscal years.
The upper limit can also be rounded down to the end of a time period by selecting another, additional time unit, so that, for example, only complete months or years can be archived when a date field is selected as a selection characteristic for the time slice. The time slice defined in this way contains the complete time period before the upper limit calculated.
1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.
This will load Delta in BW as of yesterday. Leave Lower limit blank.
2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).
This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use
Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10
records will be loaded again. If a record is created when load was running, those records
may get lost. To prevent this situation, lower limit can be used to backup the starting
sequence number. This may result in some records being processed more than once;
therefore, be sure this DataSources is only feeding an ODS Object
Hope this will help you
Thanks & Regards
Kiran

In Material Master Screen,functionally what is Safety time and safety time

In Material Master Screen,functionally what is Safety time and safety time indicator in the MRP Screen.Pls explain its functionality

Hi,
The safety time / actual range of coverage ensures that the planned warehouse stock covers the requirements of a defined number of days. It therefore serves as a time float and thus works alongside the safety stock, which acts as quantity float.
The system simulates bringing the requirements forward by the specified number of days and the planning for the receipts, created for these requirements in the planning run, is also brought forward by this number of days.
Prerequisites
·   You have set the Safety Time indicator in the material master record (MRP 2 View) to define whether the safety time is only to apply to independent requirements or to all requirements.
·    In the material master record (MRP 2 View), in the Safety Time/Actual Range of Coverage field, you have entered the number of workdays by which the requirements are to be brought forward.
·    If, in addition to this actual range of coverage, you also want to define a different number of workdays in certain periods or a safety time less than one day then, in Customizing for MRP in the activity Define Period Profile for Safety Time/Actual Range of Coverage you can define a period profile and assign it to the material in the material master record.
Regards,
Vijay

What are the delta mechanisms and tables used for Lo Extraction & COPA

Hi all
what are the delta mechanisms and tables used for Lo Extraction & COPA.
please explain clealry.
Thanks & Regards,
James

James,
Please go through Roberto's weblog :
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Anyways,
As you know LO cockpit consists of different modules(MM, PP, SD, etc)
They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
Assign points if helpful
Kalyan

What is a delta migration and is there any tool that support delta migration?

Hi,
We are migrating from MOSS 2007 to SharePoint 2013.
What is a delta migration and is there any tool that supports delta migration...Please help me understand.

hi
there are many tools are availabe in market like DocAve,Metalogic-Content migration and Quest Migration
so as per my experince Content Matrix is good to support all the feature while migration form Sharepoint 2007 and Sharepoint 2010 or Sharepoint 2013.
See the below link
http://www.metalogix.com/help/Content%20Matrix%20Console/SharePoint%20Edition/002_HowTo/003_MigrationActions/020_IncrementalCopying.htm
Please mark the answer if this help full..

What if I forget my safty question and answer

I forgot my safty question and answer

See this previous discussion:
i forgot both my security questions?: Apple Support Communities

What is difference between additive delta and new status for change record

Hi Experts
Can any one explain me about the difference between additive delta and new status for change record with example
if any one has a document please post it iam thank full to u
thanks
Ahmed
Please search the forum before posting a thread
Edited by: Pravender on Feb 12, 2012 1:54 PM

Hi
Additive delta --- We will get the changed quantity.
say suppose you have sales order and quantity like 1111 30 which is loaded to cube(BW).
now same record qty has changed from 30 to 40. As we have additive delta, we will get new record as 1111 10.
new status for change record: This is same as like After image delta type in standard SAP data sources. for every change in record you should have new record.
say if you have any number which will be generated by system for new/changed record, then you can use this.
You can use this option when delta option set to "numeric pointer"
Regards,
Venkatesh

Safety interval

hi -
is there a way to find out what is the saftey interval assigned for a datasource. lets say for fi_ap_4 what is the safety interval. where is it mentioned? is there a way to change this and if so how?
thanks
ravi

Hi Ravi,
In case of FI extraction you can find this information from the table BWOM_SETTINGS .
For further information , take a look on the following site ( especially 'Global settings' paragraph).
http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
With rgds,
Anil Kumar Sharma .P

MacBook Pro Health and safety issue: Potential Burn during normal use

Hi,
I am not a complainer. I worked for Apple of 6+ years and have had a top of the line Apple Notebook since Apple created the concept of the laptop notebook.
I recently experienced a 3rd degree burn using my MacBook Pro that I think Apple needs to warn folks about:
MacBook Pro 17"
Machine Model: MacBookPro1,2
CPU Type: Intel Core Duo
Number Of Cores: 2
CPU Speed: 2.16 GHz
L2 Cache (shared): 2 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: MBP12.0061.B00
Serial Number: ()
SMC Version: 1.5f10
Sudden Motion Sensor:
State: Enabled
I had my laptop on my lap. I was wearing shorts. It noticed that it was warm on my leg where the left side of the MacBook Pro was touching my leg, but it didn't create a reflex pain response.
Upon completing my session, when I closed the machine and put it away, I noticed a 1 inch x .75 inch blister on my leg where it had been touching the MacBook/Pro; and it has turn out to be a significant burn.
I checked all the documentaiton that came with my MacBook Pro and there was no warning about the potential of this situation.
I recommend that Apple let owners know, perhaps through an email or a popup when they visit the Apple site. Lastly, when I encountered this issue, I wasn't running any high performance, compute bound applications. It was email. So, I have to believe that it is possible to detect wait states within the processes running and take the processors to a low power mode of operation when they are not performing actual work. Am I out in left field here?
I want Apple to be successful. I haven't heard of a similar complaint on any of the high performance PC's at work. Beyond a Health and Safety issue, this is also a reputation issue. Better to face into the storm and honestly deal with this issue.
A slightly crisp, but loyal, MacBook Pro user.
Mike Doherty
MacBook Pro Mac OS X (10.4.5) Potential Health and Safety Issue- 3rd degreee burn potential under normal use

Mike... I do sympathize with your situation but let me correct you:
I recently experienced a 3rd degree burn using my
MacBook Pro
Do you know what a 3rd degree burn is? A 3rd degree burn involves the dermis, and is full thickness involving the subcutaneous tissues and fat underneath your skin layers. This is something that usually happens when man meets fire, electrocution, and chemical burns. A 3rd degree burn is not typically achieved by a simple transfer of energy by conduction, unless extreme heat for an extended period of time.
I had my laptop on my lap. I was wearing shorts. It
noticed that it was warm on my leg where the left
side of the MacBook Pro was touching my leg, but it
didn't create a reflex pain response.
Reflex pain response? Don't try to make up medical terminology. You didn't feel it much like you don't feel the sun when you get a sunburn initially... your skin slowly adjusted to the temperature, and at some point the heat increased over the threshold of which causes damage. You should have gone to the doctor if you were overly concerned.
Upon completing my session, when I closed the machine
and put it away, I noticed a 1 inch x .75 inch
blister on my leg where it had been touching the
MacBook/Pro; and it has turn out to be a significant
burn.
You're right, if you have a 1inch by almost 1 inch heat related blister on your leg, it is bad, nothing that I would consider significant. That is less then 1% of your body, probably about 0.25% to 0.5%, and only a 2nd degree burn. Your most significant complication would be a local skin infection.
I checked all the documentaiton that came with my
MacBook Pro and there was no warning about the
potential of this situation.
Actually... I'd hate to call you a liar, but I'm pretty sure that it does warn about burns.
To confirm this, apple has also information online:
http://docs.info.apple.com/article.html?artnum=30612
I recommend that Apple let owners know, perhaps
through an email or a popup when they visit the Apple
site.
They do... link above.
Lastly, when I encountered this issue, I wasn't
running any high performance, compute bound
applications. It was email. So, I have to believe
that it is possible to detect wait states within the
processes running and take the processors to a low
power mode of operation when they are not performing
actual work. Am I out in left field here?
No, you're definitely not. Here's where I start to agree with you. For the computer to heat up that much, when not doing things like rendering video is abnormal, and you deserve to have apple check out your computer. I think you should contact them on this concern.
I want Apple to be successful. I haven't heard of a
similar complaint on any of the high performance PC's
at work. Beyond a Health and Safety issue, this is
also a reputation issue. Better to face into the
storm and honestly deal with this issue.
It's harder for other manufacturers... our computers are aluminum, designed to disperse the heat. Technically they are considered "portables" not laptops, but I don't get into that argument because I disagree with the word "portable"... it's meant to work on your lap, and if you can't comfortably using regular apps, you deserve an answer.
A slightly crisp, but loyal, MacBook Pro user.
Hey, at least you're taking it with some humor. It's a shame you had to get hurt as a result of your computer. If I were you I would have gone to your Primary Care Physician, documented the burn, and returned your computer for a new one, and for something say, a free iPod for your pain.
Sorry you got hurt, I think you should have your heat issue professionally investigated through apple care

R/3 extraction.{direct delta and queued delta and V3}

Hi,
I am new to BW.Can anyone explain me about R/3 extraction in detail and steps to extract from R/3 to BW.
I understood direct delta.But i couldn't understand queued delta.Can anyone please explain queued delta and also V3.Are queued delta and V3 same?
Detail explanation or links will help a lot.
Thanks,
Sunny.

Hi Sunny,
Procurement - MM :
MM is a part of SCM. There are several section in this, say Procurement, manufacturing, vendor evaluation etc... All can be found under follwoing link.
Please find the procedure and important links for LO extraction..
LO'S Procedure:
Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
Go to transaction RSA3 and check the data.
Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
Now you can go to your data target and see the delta record.
Re: LO-Cockpit V1 and V2 update
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Also Refer this link:
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Inventory.. dwload go thru it
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
*Steps*:
1st delet the septup table----lbwg(for application 3)(need to cleanup the setup tables in r/3 side by using (LBWG for AC:03)
1) Fill setup table (fill up the set up tables BX, BF and UM by using (MCNB,OLI1BW and OLIZBW).
for BX(Open stock)-tcode--MCNB,
for BF Tcode(oli1bw)
for UM tcode(olizbw)
after that pull data to BW with (Once the data is ready in RSA3, then in BW you have to set up compression for zero marker update for the Cube (coz is related to Noncummulative Keyfiger scenario) then load BX data. onces its completed load normally the BF and UMs.
BW side:-
make the compression
for BX load normally
and BF&UM(step table data):-compression with zero mark update(select that check box option)
after completion of compression do delta(Note: for deltas follow the compression normally)
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/c5/a26f37eb997866e10000009b38f8cf/frameset.htm
SD - Enterprise Sales and Distribution
SD comes under CRM application component (ERP Analytics).
sd flow
salesorder:
VBRK - header
VBAP - item
VBEP - scheduling
delivery:
LIKP - header
LIPS - item
billing:
VBRK - header
VBRP - item
shipement
VTTK - header
VTTP - item
customer data
SD links FI table
salesarea data general data companycode data
knvp kna1 knb1
material master data
SD link to MM table
salesdata Basic data salestext data
MARC MARA STXH(Textfile header)
MVKE MAKT STXL
process:
1.sales reresntive enter sales order in R/3 system, it sotres the transaction into three
SD tables.
2.delivery due list is executed for all sales orders and delivers are created in table LIKP, LIPS.
A goodsissue updating MKPF & MSEG.
3.invoice due list is then executed for all deliviers. after an invoice is created, which creates an acct.doc ( BKPF & BSEG, FI TABLES) and set up the receivalbe in table BSID (open tem).
4.The receivalbe is cleared when paymen check is required. anoher acct.doc is created ( BKPF & BSEG) the open receivable is cleared and table BSAD (closed line item) is updated
First u select application component.. SD,MM,FI,PM
then got to rsa5.. u can install data source...
after next step RSA6-Display data sources
Then select our ds which we need to enhance then click on the
append structure (application tool bar)
u can see start with ZAGTFIGL_4 ( fi example)
u given component name and component type ( here given to existing
data element)
save + activate....
then go to the t code CMOD...>there select the project
name--> go to the exit in RSAP0001->
or also u can goto tcode se37 fuction module.. EXIT_SAPLRSAP_001
transactional data
click on display...
then u can see INCLUDE ZXRSAU01( program ) double click it.....
then u can change option click it.
So please follow the link below:
http://help.sap.com/saphelp_nw70/helpdata/en/c5/bbe737a294946fe10000009b38f8cf/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/17/cd5e407aa4c44ce10000000a1550b0/frameset.htm
Check these links,
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
http://www.erpgenie.com/abap/tables_sd.htm
http://www.erpgenie.com/abap/tables_mm.htm
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Re: LO-Cockpit V1 and V2 update
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Regards
CSM Reddy

What is safty delta and safety interval

Similar Messages

Maybe you are looking for