Is Downtime necessary for delta methods?

Hi all,
When we do initialization for full updates or delta initialization, downtime is necessary.
Is downtime necessary for delta updates also? Whenever a document is posted to an application tables, will it come directly to extraction queue, update table or delta queue(depending on delta method we chose)? Or do we need any downtimes?
Please explain me in detail...
Thanks.

Hi Komal,
You require Downtime only during a SETUP run, after the Successful Setup run and initialization in BW, you need to schedule JOBs to run DAILY/HOURLY along with the TYPE of DELTA that is required...Downtime is NOT required after this point.
The jobs scheduled will pick up any deltas and post it to for the BW Delta Queue. The Delta load in BW will then pick the Delta records.
Cheers,
Praveen.

Similar Messages

How to edit copa data source or change delta method.Need t-code/procedure

Hi gurus,
I have a copa extractor in production.The copa extraction is costing based.
I need to get an extra field from CE1**** table. when i go to KEB0 and display , i see my required field under the chracteristics from segment table. It is unchecked.
I want to know the transaction where i can go and edit the datasource to check that field and bring that data in.
I tried going to T-code KEDV. But i couldnt figure out what to do there?
I also tried deleting and recreating the datasource, then i am able to check that field. The problem is earlier existing data source used to say,
Delta Method     Time Stamp Management in Profitability Analysis
now it says
Delta Method         Generic Delta.
how do i change the delta method from generic delta to Time Stamp Management in Profitbility Analysis. During creation in KEB0 it doesnt give any option to change.
and what exactly is the differnce between both delta methods?
plz post your inputs.
Thanks in advance,
> Points will be assigned for inputs
Message was edited by:
        ravi a
Message was edited by:
        ravi a

Hi Ravi,
I would expect you are communicating to your users that you will need some downtime for you to change this. To add characteristics to COPA you actually have to first the delete the datasource in KEB0 then re-create the datasource. I would work with your CO-PA config team to get the T-Codes necessary to assign those objects to PA.
Please reference OSS note 392635 for further reference on your CO-PA timestamp question. This should answer your questions here.
Pls. assign pts if this helps.
Thanks,
-Alex

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

Need for locking system for delta initialization (BW-R3-LO)

Hello all,
Could someone please help me with the following,
Please be kind, don't get impatient for the lengthy post
1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
             a). say, I do full load with end date and time (10pm 12-31-2007)
             b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
         If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
         If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
4. How this scenario differs to early delta initialization?
Your responses would be greatly appreciated
Thank you

Hello,
1
>
curious maven wrote:
> Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
No,you don't need to lock the Source System which is the advantage of Early Delta Init.
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
[Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
2
>
curious maven wrote:
> 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
Early delta is not supported by all the extractors. See Lo Extraction
3
>
curious maven wrote:
Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
>
>     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
>
>              a). say, I do full load with end date and time (10pm 12-31-2007)
>              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
>
>          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
>
>          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
4
>
curious maven wrote:
How this scenario differs to early delta initialization?
If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
[How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
[How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
Thanks
Chandran

Where can we see the Delta Method suported by data source.

Hi all,
Please let me know where can we see delta method for the Business constraint DataSource ? such as where this data source had delta method as Direct Delta or Queued Delta or V3 Undersized update.
I want to find out for 0FI_GL_4 DataSource.
Regards
Ashutosh

0FI_GL_4 is delta capable.
http://help.sap.com/saphelp_nw70/helpdata/en/0c/b4973c115a6f3ae10000000a114084/content.htm
Finance works on Time Stamp not on LO.

ABR,ADR delta methods

Dear SDN,
I need the different types of delta methods provided like ABR ADR.
What are others.
Regards,
Rahul

You can find all the delta methods in table RODELTAM.
Take a look at this thread for more information...
Delta Process

Use Trigger or Query for Deltas

Hi Gurus,
It has come up that my boss wants us to use a trigger on one of the most critical talbes we use for our website. Instead I have suggested to query for deltas and feed them out on time intervals.....which method is the least performance impacting on our db?
Any info/suggestions would be much appreciated.
S

Hi,
ScarpacciOne wrote:
When is it a good idea to use triggers? What scenarios are a good fit to implement a trigger?DML triggers are great for autiomatically supplying or correcting data entry.
For example, supplying an id number from a sequence when a new row is inserted, or filling in last_modify_date and last_modify_user columns.
Sometimes you can autiomatically correct data entry errors. For example, if a string is supposed to be all upper-case, or a DATE column is supposed to be midnight. You can (and should) have CHECK constraints to make sure people don't enter bad data, but sometimes you can safely say "I'm sure he meant 'ACTIVE', even though he said 'active'", or "I'm sure she meant TURNC(SYSDATE), not SYSDATE", and avoid having any error.
DML triggers are the only way to ensure something is done the as soon as some DML is performed. If it can wait, even a few minutes, then some othe mechanism (like a scheduled job, or a materialized view) can probably handle the situation more easily and reliably.

Select-options for OO Methods

Hi all,
How can I define select-options for a method in a global class.
And how can I pass these select-options from a report.
Thanks & Regards
Eshwar

Hi all,
How can I define select-options for a method in a global class.
And how can I pass these select-options from a report.
Thanks & Regards
Eshwar

Can we use both 0FI_AP_3 and 0FI_AP_4 for Delta Loads at the same time.....

Hi Gurus:
Currently my company uses 0FI_AP_3 for some A/P reporting. It has been heavily customized & uses Delta loading. However, SAP recommends the use of "0FI_AP_4" for A/P data fro delta loads. I was able to Activate 0FI_AP_4 as well & do some Full Loads in Dev/Test boxes. Question is whether I can use both the extractors for "Delta" loads at the same time......? If there are any issue, what is the issue and how ccan I resolve it? Is the use of only one extractor recommended......??
Please let me know as this impacts a lot of my development....! Thanks....
Best...... ShruMaa
PS: I had posted this in "BI Extractors" forum but there has been no response...... Hope to get some response.......! Thanks

Hi,
I would recommend you to use 0FI_AP_4 rather using both, particularly for many reasons -
1. DS: 0FI_AP_4 replaces DataSource 0FI_AP_3 and still uses the same extraction structure. For more details refer to the OSS note 410797.
2. You can run the 0FI_AP_4 independent of any other FI datasources like 0FI_AR_4 and 0FI_GL_4 or even 0FI_GL_14. For more details refer to the OSS note: 551044.
3. Map the 0FI_AP_4 to DSO: 0FIAP_O03 (or create a Z one as per your requirement).
4. Load the same to a InfoCube (0FIAP_C03).
Hope this helps.
Thanks.
Nazeer

Is there a (relatively simple) way to skip tracks with an iPod touch 5th gen using a physical button? I'm aware songs can be skipped on-screen without unlocking the iPod, but I'm looking for a method that doesn't require taking my eyes off the road.

Is there a (relatively simple) way to skip tracks with an iPod touch 5th gen using a physical button? I'm aware songs can be skipped on-screen without unlocking the iPod, but I'm looking for a method that doesn't require taking my eyes off the road while driving. For that reason, I'm also not interested in adding in headphones or additional devices that have the desired button functions. Going both forward and back would be great but I would be pleased just to have a "sight-free" way to go forward.
I've seen some mention here and there about ways to maybe change it so the volume buttons change tracks and holding the volume buttons changes the volume... but I don't know what's involved in that or if its even possible/recommended for a new 5th gen iPod. I think its a great device but its sadly lacking in music oriented functions and features... which is disappointing since music is why most people would bother getting one instead of some other "iDevice" :/

Given that you cannot do what you have asked for, perhaps you simply need to find another solution to your root problem.
Presumably, you want to skip to the next track because you don't want to hear the current one, and that is because...
You don't like it.
You've heard it recently and don't want to hear it now.
Simply don't want to hear it at this time.
For problem number 1. Don't put it on the iPod in the first place. (I know, obvious answer!)
For problem number 2. How about playing from a Smart Playlist (initially created in your iTunes Library) which has only songs you've not played recently?
For problem number 3. Hhhmmm! Create alternative Playlists for use in the car.
As for going back to the start of the "now playing" track.... Well, if your Playlist has only songs that you really, really want to hear, then you'll be looking forward to that rather go back to the beginning of the current song.
I'm not trying to be prescriptive, just giving you food for thought.
(They are all cheaper options than buying a car which can control the iPod from the steering wheel.)

Short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow

hi all,
i am getting short dump error for delta load to 0CFM_C10 via 0CFM_DELTA_POSITIONS flow.
not able to figure out the actual issue and how to solve it.
can anyone suggest?
below is the details of the short dump
Short text
    Exception condition "UNKNOWN_TRANSCAT" raised.
What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    A RAISE statement in the program "CL_SERVICE_TRG================CP" raised the
     exception
    condition "UNKNOWN_TRANSCAT".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "RAISE_EXCEPTION" " "
    "CL_SERVICE_TRG================CP" or "CL_SERVICE_TRG================CM003"
    "SORT_TRANSACTIONS"
    or
    "CL_SERVICE_TRG================CP" "UNKNOWN_TRANSCAT"
    or
    "SBIE0001 " "UNKNOWN_TRANSCAT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

Hi,
It seems like some routine are there and check your rotines , transformation etc.
Regards
sivaraju

Is model view(BD64) necessary for EDI

is model view created using BD64 necessary for a EDI transactions? I have created a logical system, a RFC destination and a EDI File Port.
After all this i am trying to push a material master data using BD10 to the file port. When i do that the system gives me a message saying that master idoc created but it does not create a communication idoc. Only if i have a Model view set up in BD64 it creates a communication idoc. So my question is do we need a model view for EDI configuration?
~Suresh

Hi,
BD64 is required for master data distribution..
If you are having a interface that sends IDOCs to the customer or receive IDOCs from the vendor..You don't require BD64 setup..
Thanks,
Naren

HT3231 What cables are necessary for the fastest transfer of data from MacBook Pro to MacBook Air

What cables are necessary for the fastest transfer of data from MacBook Pro to MacBook Air

As I posted "it is an Unknown", at least to me, what type FW port is on the OPs older Mac.
LowLuster
HT3231 Re: What cables are necessary for the fastest transfer of data from MacBook Pro to MacBook Air
Dec 26, 2013 8:04 PM (in response to OGELTHORPE)
But the newest Mac notebooks do not have a firewire port.
So he may need a TB to FW adapter, $29, a FW 400 or 800 cable, $??, and then a FW 400 to 800 cable/port adapter (If the old Mac only has a FW 400 port), $??.
It is unknown if the old Mac has a FW 400 or 800 port.

Payment Advice for Payment method T- Transfer

Hi,
When I run F110 (Automatic payment program), I need to provide the payment advice for payment method T (bank transfer)
to the vendor in the format provided by the client.
My question is:
1. Where to assign the payment advice form in customisation for payment method T
2. which program has to be assigned to the payment advice form.
Very Important note: Here we are ALSO using DMEE file to upload- Under payment method country -I have configure the same for use payment medium workbench
Rgds,
Vidhya

Hi Vidhya,
All this is done in a single screen transaction code FBZP.
Where to assign the payment advice form in customisation for payment method T
This is in Payment methods in Company codeSelect your payment method-Expand form data and assign the paymnet advice form.
which program has to be assigned to the payment advice form.
FPAYM_INT_DMEE(For DMEE)./ in the next form you may have F110_IN_AVIS.
Thanks
Aravind

Exit for payment method(IDOC- PEXR2002)

Dear Experts,
I have add one Z Segment to the standard idoc PEXR2002 and msgtyp PAYEXT and now would like to pass the value to that Z segment field.
But i am not able to find out any Exit for payment method.
Program used to create the idoc is RFFOEDI1.
Kindly provide the solution.
Regards
Pankaj

if you will ook in the porgramit is sent via function module where there are lot of Call customer function which you can use for example EXIT_SAPLIEDP_902 i can see many.Just debuug it and check which suit your need.
Nabheet

Is Downtime necessary for delta methods?

Similar Messages

Maybe you are looking for