Diff b/w sy-datum - 0calday

hi ,
i got a requirement that i need to show difference b/w current date and 0calday in report can any body help me regarding this

Hi,
If you want to get it in Reporting itslef, you have to take 0CALDAY into rows and have to take 2 Formula variables. One FV is a Replacement path varibale with Characterstic = 0CALDAY ,Replace variable with = KEY and dimenaion indicator = Date .And another Fv should be a Customer exit variable with dimenaion indicator = Date .
In the code for 2nd variable , you will simply asign sy-datum.
These 2 variables are used in the formula as FV1-Fv2.
With rgds,
Anil Kumar Sharma .P

Similar Messages

Delete data from infocube which is older than 7 days.

Hi Gurus,
I have a Cube with the time dimension characteristic as 0CALDAY. This cube gets data from a DSO ,which has 0calday as one of its key fields, in Delta mode. I am in a need to delete the data with calday in the previous week. i.e SY-DATUM - 0CALDAY >= 7 in the infocube.
I just tried to create a transformation such that both the data target and the source is the above mentioned DSO and used the technical rule group to set the record mode as "D" for the older records and it works fine with the DSO.
But the Cube still has the data. Just the keyfigure becomes zero. But i want to completely delete the data. I do not want to use "DELETE-FACTS" or the FM "rsdrd_sel_deletion."
Please help me get out of this problem.
Thanks in advance,
Rajesh.

Hello Rajesh
Not sure if I understood the problem correctly, but what I understood is you need to keep only last 7 days data in the cube and anything else got loaded earlier should need to be deleted.
If this is correct then can you delete the whole cube content and load only last 7 days data from DSO to cube via DTP filter ( or some start routine).
In this case first time delta ( or full) will never read from change log table but it will read from active table of DSO only
Regards
Anindya

SQL: Aggregating Problem

Hello,
i have following problem with aggregating values with one of our tables:
For each day there is a row which contains the change to the previous day.We need now a view containing for each date of the year a subtotal from the beginning of the year . Is there any aggregating function with this functionality? Is it possible to solve this without using PL/SQL?
Example:
create table example (datum date, diff number);
Rows in the table:
insert into example (to_date('01-01-2005','dd-mm-yyyy'), -1);
insert into example (to_date('02-01-2005','dd-mm-yyyy'),1);
insert into example (to_date('03-01-2005','dd-mm-yyyy'),2);
insert into example (to_date('04-01-2005','dd-mm-yyyy'), -1);
We need following result:
'01-01-2005', -1 --(sum from 01-01-2005 to 01-01-2005)
'02-01-2005', 0 --(sum from 01-01-2005 to 02-01-2005)
'03-01-2005', 2 --(sum from 01-01-2005 to 03-01-2005)
'04-01-2005', 1 --(sum from 01-01-2005 to 04-01-2005)
Thanks for your help
Philipp
Message was edited by:
[email protected]

The windowing clause may not be required, but depending on how the O/P feelas about multiple months, or years, something like this may be more accurate.
DATUM             DIFF
01-JAN-2005         -1
02-JAN-2005          1
03-JAN-2005          2
04-JAN-2005         -1
29-DEC-2004          1
30-DEC-2004          2
31-DEC-2004          3
SQL> SELECT datum, SUM (diff) OVER (ORDER BY datum) diff
2    FROM example;
DATUM             DIFF
29-DEC-2004          1
30-DEC-2004          3
31-DEC-2004          6
01-JAN-2005          5
02-JAN-2005          6
03-JAN-2005          8
04-JAN-2005          7
SQL> SELECT datum, SUM (diff) OVER (PARTITION BY TRUNC(datum,'YEAR')
2                                 ORDER BY datum) diff
3 FROM example;
DATUM             DIFF
29-DEC-2004          1
30-DEC-2004          3
31-DEC-2004          6
01-JAN-2005         -1
02-JAN-2005          0
03-JAN-2005          2
04-JAN-2005          1John

Create a new "actual day variable" for 0CALDAY

Hello,
i want to create a new "actual day variable" for InfoObject 0Calday. The variable should have the same functions like 0DAT.
How can I create this? Coding for CMOD?
Thanks and regards,
Heiko

Hi,
As I understand your question properly, You need a dynamic variable which will give the actual date i.e current date.
create a variable for 0calday with single value processing type customer exit. reay for input deselect.
in cmod
When 'vARIABLE FOR CALDAY'.
CLEAR L_S_RANGE.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
L_S_RANGE-LOW = SY-DATUM.
APPEND L_S_RANGE TO E_T_RANGE.
Regards,
Ranganath.

Customer exit on 0calday

Hi,
This is Madhavi. Plz help me to find out the solution for this.
Create an exit on 0CALDAY. Default this value to Be current Monday of the week and popup to user.Validate User input with the Monday of the week.If its not a Monday give an error asking to enter Monday of that week
Thanks and Regards,
Madhu

Hi,
Try the below code, this may help you.
data: l_curr_day type SCAL-DATE,
 l_date type /BI0/OICALDAY,
 l_no_day type SCAL-indicator,
 l_day1 type P,
 l_diff type P,
 l_daym type /OSP/DT_DAY,
 l_day(2),
 l_month type /BI0/OIFISCPER3,
 l_year(4),
 l_curr_month type i,
 l_curr_year type i,
 l_month_temp type i,
 l_year_temp type i,
 l_s_range type rsr_s_rangesid,
 l_s_var_range type line of rrs0_t_var_range.
if i_step = 1. "Before Selection screen is shown
 l_curr_day = sy-datum.
 l_curr_month = sy-datum+4(2).
 l_curr_year = sy-datum+0(4).
 CALL FUNCTION 'DATE_COMPUTE_DAY'
 EXPORTING
 DATE = l_curr_day
 IMPORTING
 DAY = l_no_day.
 if l_no_day = 1.
 l_s_range-sign = 'I'.
 l_s_range-opt = 'EQ'.
 l_s_range-low = l_curr_day.
 l_s_range-high = ''.
 append l_s_range to e_t_range.
 else.
 l_day1 = sy-datum+6(2).
 l_diff = l_day1 - l_no_day + 1.
 if l_diff > 0.
 clear l_date.
 l_day = l_diff.
 l_month = l_curr_month.
 l_year = l_curr_year.
 concatenate l_year l_month+1(2) l_day into l_date.
 else.
 l_month_temp = l_curr_month - 1.
 if l_month_temp > 0.
 l_day = l_day1.
 l_month = l_month_temp.
 l_year = l_curr_year.
 concatenate l_year l_month+1(2) l_day into l_date.
 CALL FUNCTION '/OSP/GET_DAYS_IN_MONTH'
 EXPORTING
 IV_DATE = l_date
 IMPORTING
 EV_DAYS = l_daym.
 l_diff = l_diff + l_daym.
 l_day = l_diff.
 concatenate l_year l_month+1(2) l_day into l_date.
 else.
 l_year = l_curr_year - 1.
 l_day = l_day1.
 concatenate l_year '12' l_day into l_date.
 CALL FUNCTION '/OSP/GET_DAYS_IN_MONTH'
 EXPORTING
 IV_DATE = l_date
 IMPORTING
 EV_DAYS = l_daym.
 l_diff = l_diff + l_daym.
 l_day = l_diff.
 concatenate l_year '12' l_day into l_date.
 endif.
 endif.
 clear l_s_RANGE.
 l_s_range-sign = 'I'.
 l_s_range-opt = 'EQ'.
 l_s_range-low = l_date.
 l_s_range-high =''.
 append l_s_range to e_t_range.
 endif.
endif.
if i_step = 3. " Validate user input
 read table I_T_VAR_RANGE into l_s_var_range with key vnam = 'YTSTDAY'.
 if sy-subrc = 0.
 l_curr_day = l_s_var_range-low.
 CALL FUNCTION 'DATE_COMPUTE_DAY'
 EXPORTING
 DATE = l_curr_day
 IMPORTING
 DAY = l_no_day.
 if l_no_day <> 1.
 raise NOT_MONDAY.
 endif.
 endif.
endif.
endfunction.
regards
rajesh

Sichtbarer bereich bzw datum und uhrzeit

Hallo
mein problem als neuling ist das ich ich mts files über import camera-archiv durchführe.
soweit klappt alles.nun füge ich datum und uhrzeit mit der titel funktion ein und schaue es an auf dem imac27.
super.nun brenne ich es und auf dem tv fehlt mir die hälfte vom datum und uhrzeit.
habe versucht 16:9 und 4:3 leider immer wieder.
kann mir jemand helfen?
kann mann das datum verschieben?mehr zur mitte?
mfg
mathias

mathiasfromdortmund wrote:
Hallo
mein problem ... brenne ich es und auf dem tv fehlt mir die hälfte vom datum und uhrzeit...
english: my problem is, after 'burning', titltes are chopped on TV
depends on the settings of your TV or DVDplayer:
the titles in iM for 16:9 are made for modern flat-screens; older 'tube'-TVs struggle with over- or under-scan: they don't show the full 768x576pixel resolution of a DVD.
try diff. settings in your DVDplayer's or TV's menu.
German Version:
Der Zeitstempel ist nicht 'frei' beweglich in iMovie; brennt man nun DVDs, kann es, gerade auf Röhren-TVs, dazu kommen, dass diese nicht den vollen Wiedergabebereich anzeigen. Kann man evtl. abhelfen durch andere Einstellungen am DVDplayer oder am TV, ... lies dazu http://de.wikipedia.org/wiki/Overscan
im engl. wiki mit Bildern: http://en.wikipedia.org/wiki/Overscan

Datum/Uhrzeit des Originals - Import und Sortierung

In Photoshop 6 Elements (PSE6) habe ich tausende Fotos importiert, welche zuvor mit ACDsee 10 bezüglich des Bildzeitstempels teilweise überarbeitet wurden. Im Windows-XP-Explorer werden die Zeitstempel korrekt angezeigt, sprich aus den jpg-Dateien richtig ausgelesen :-)
PSE6 übernimmt diese EXIF-Datümer nicht immer richtig in den Organizer. Es wird vielmehr das letzte Änderungsdatum genommen und danach sortiert :-o Dabei wird in PSE6 in den Eigenschaften der jpg-Datei sehr wohl das richtige Datum/Uhrzeit des Originals (von ACDsee gesetzt) angezeigt! PSE6 liest folglich die EXIF-Daten beim Import einfach nicht richtig aus...
Warum kann Microsoft etwas besser als Adobe? Bei meiner Suche in diesem Forum gab es ähnliche Threads schon zu Photoshop 4 und es hat sich scheinbar nichts im Laufe der Zeit bei Adobe geändert.
Besonders leide ich in Premiere 4 Elements, weil Fotos und Videos im Organizer einfach nicht chronologisch sortiert werden :-(
Gibt es Tipps und Tricks?
MfG Curt

mathiasfromdortmund wrote:
Hallo
mein problem ... brenne ich es und auf dem tv fehlt mir die hälfte vom datum und uhrzeit...
english: my problem is, after 'burning', titltes are chopped on TV
depends on the settings of your TV or DVDplayer:
the titles in iM for 16:9 are made for modern flat-screens; older 'tube'-TVs struggle with over- or under-scan: they don't show the full 768x576pixel resolution of a DVD.
try diff. settings in your DVDplayer's or TV's menu.
German Version:
Der Zeitstempel ist nicht 'frei' beweglich in iMovie; brennt man nun DVDs, kann es, gerade auf Röhren-TVs, dazu kommen, dass diese nicht den vollen Wiedergabebereich anzeigen. Kann man evtl. abhelfen durch andere Einstellungen am DVDplayer oder am TV, ... lies dazu http://de.wikipedia.org/wiki/Overscan
im engl. wiki mit Bildern: http://en.wikipedia.org/wiki/Overscan

Diff bet BDC in appln & present

Gud morning guys,
hav a gr8 day
Coul any1 of u tel me diff bet BDC in application layer and presentation layer...
cheers
sakthi

Hi
Hope it will help you.
Reward if help.
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
The first is when application data to be replaced is transferred at once, and only once.
The second situation is to transfer data periodically from external systems to SAP and vice versa.
There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called batch input or batch data communication.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
Flat file can be created in your hard disk as follows:
1 Vinod Hyderabad
2 Kavitha Secunderabad
3 Kishore Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
ID(10),
NAME(25),
CITY(25),
END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = C:\FF.TXT
FILE TYPE = ASC
TABLES
DATA_TAB = ITAB
EXCEPTIONS
CONVERSION_ERROR = 1
INVALID_TABLE_WIDTH = 2
INVALID_TYPE = 3
NO_BATCH = 4
UNKNOWN_ERROR = 5
OTHERS = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT = SY-MANDT
GROUP = POTHURI
HOLDDATE = DATE1
KEEP = X
USER = SY-UNAME
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
EXPORTING
TCODE = TFBA
TABLES
DYNPROTAB = BDCTAB
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
Endif.
Endif.
*& Form GENERATE_DATA
Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.

What is diff b/w sy-index and sy-tabix

Hi all,
Can u plz give me the diff b/w sy-index and sy-tabix exactly and how it works.
Thanks & Regards
Venkat

Hi Venkat,
1.SY-INDEX
->Current loop pass
->In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
2.SY-TABIX
->Current line index
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables.
The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.

COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.

SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
I think that it clears ur doubt.
Thanks,
Venkat.O

How can I use same account in 2 iphone with diff contact list?

how can I use same account number but other all totally diff such as contact list, application, everything ..... I found that it's bad on IOS5.
when I used IOS4 .. old verison, I can keep my phone in diff data. Afte upgrade IOS 5, it's bad. Even take photo, it can not focus zoom in and out.

how can I use same account number but other all totally diff such as contact list, application, everything ..... I found that it's bad on IOS5.
when I used IOS4 .. old verison, I can keep my phone in diff data. Afte upgrade IOS 5, it's bad. Even take photo, it can not focus zoom in and out.

How can we assign system fields like sy-datum, sy-uzeit to the ztable field

hi experts,
i have created one ztable inthis one it has some fields like date changed , time changed... in this table when the user enters the data it automatically updates time and date... for this where i have to assign those fields and code pls....

Hi Gopal,
Make use of the events in Table maintenance generator,
Generate a Table maintenance genrator and in TMG make use of the events
Link to create the events
http://www.goodpeople.co.in/jobseeker/JobDetailPage.aspx?postjobid=43001
select the table maintenance event maintenance dialog as 05
in the event between form and endform write the following code
field1 = sy-uname.
field2 = sy-uzeit
field3 = sy-datum.
regards
prasanth

Difference between sy-datum and any given date

Dear Friends;
I have one query regarding DATE I wanna calculate the difference between
SY-DATUM and ANY GIVEN DATE . Is there any function or code available that take one parameter as sy-datum and another parameter as any given date and give result as no. of days between them
Regards;
Parag

DATA: DATEDIFF TYPE P.
CALL FUNCTION 'SD_DATETIME_DIFFERENCE'
EXPORTING
    date1                 = '20071122'
    time1                 = '000001'
    date2                 = '20070905'
    time2                 = '000001'
IMPORTING
   DATEDIFF               = DATEDIFF
EXCEPTIONS
   INVALID_DATETIME       = 1
   OTHERS                 = 2.
Greetings,
Blag.

Difference between sy-datum and sy-datlo

difference between sy-datum and sy-datlo

hi,
The GET TIME statement synchronizes the time on the application server with the time on the database server and writes it to the field SY-UZEIT. SY-DATUM and the system fields for the local timezone (SY-TIMLO, SY-DATLO, and SY-ZONLO) are also reset.
SY-DATLO
Users local date, for example 19981129, 19990628,
SY-DATUM
Current application server date, for example 19981130, 19990627,
SY-DAYST
X during summertime, otherwise space.
SY-FDAYW
Factory calendar day of the week: Monday = 1 Friday = 5.
SY-TIMLO
Users local time, for example 154353, 225312,
SY-TZONE
Time difference in seconds between local time and Greenwich Mean Time (UTC), for example,
360, 10800.
SY-UZEIT
Current application server time. for example 164353, 215312,
SY-ZONLO
Users time zone, for example, EST, UTC,
reward points if useful

Diff b/w btree and bitmap index ?

What is the difference between btree and bitmap index ?
which one to used and when.
how they are differ from each other.

you'd love to see
http://www.oracle.com/technology/pub/articles/sharma_indexes.html

Diff b/n sy-tabix and sy-indx

diff b/n sy-tabix and sy-indx ?

Hi Henry,
SY-INDEX is the value of the current iteration. It is applicable for the following programming constructs in ABAP -
DO...ENDDO.
WHILE...ENDWHILE.
SY-TABIX (TABle IndeX) is applicable to internal tables. If you scroll down in the link which Eddie has given, you will find a more detailed explanation for sy-tabix and which statements affect its value.
Regards,
Anand Mandalika.

Diff b/w sy-datum - 0calday

Similar Messages

Maybe you are looking for