What are "On Triggers"

Hi All,
Could anyone please explain what are "On Triggers" on Database Objects?
Thanks for help.
Thanks
Suman

Database objects can have only BEFORE or AFTER triggers. If you're using Developer forms, you can have ON triggers.

Similar Messages

What are the events triggered in lsmw?

what are the the events trigered in lsmw?

check this link for complete info in LSMW
How to mantaian the manditory ,optional and required fields in LSMW
Regards
Prabhu

What are the major components in class?

1)     What is the purpose of load-of-program? When it will be trigger?
2)     Write the code for displaying the three parameters in single line with the first parameter as mandatory in the selection screen?
3)     Which event triggered whenever the user call the function BACK, EXIT, CANCEL?
4)     What are the major components in class?
5)     What is the functional module is used to get popup screen for ALV reports?
6)     Which type of pool is used to get drop-down list?
7)     What is the tcode for creating the variant truncations?
8)     Is it possible to call LDBs number of times in same report?
9)     What are the conditions to use control break statements in our report program?
10)     What is the use of range statement?
11)     What is the difference between normal reports and alv reports? With comparing to normal report are there any disadvantages in alv reports?
12)     What are the components used to suppress the fields in the selection-screen?
13)     What is the standard program to transport selection screen variants?
14)     What is the event keyword for defining event block for reporting events?
15)     What is the specific statement use when writing a drill down report?
16)     What are the different tools to report data in sap?
17)     Write the menu path to create a selection text in reports?
18)     How do we omit the leading zero s while formatting outputs in reports?
19)     What are the report truncations?
20)     How do we align selection input in single row?
21)     How do we suppress the display of input fields on selection screen?

this forum is not for answering your interview questions...if you stucked with any realtime problem then post...please try to respect forum terms and conditions.
Thank you.

What are the 3-bit field choices for Hw_Arm_Sel in PCI-6601

Hi,
I am programming our own driver to operate the PCI-6601. For our application we need hardware arm option. I know it is possible to use 2 counters for that, but NI-TIO should support also hw_arm. Although it is not explained in the registry document at all, after some tedious check in the DDK examples I found that this bits are located in the Gi counting mode register. I know the position of the HW_enable as well as the position of the 3 bits for pin sellect options. What I do not know is What are the 3-bit field choices for Hw_Arm_Sel . I contacted NI support but got no support. How can NI sell boards and when a customer who is not using LAbview or Measurement Studio or DDK, but is implementing his own driver is then so arrogantly turned down from NI? Also, how can NI publish just part of the registers the board support, and when a customer contacs and asks for some registers get not at all support? I can not foretell the missing registers, and it is pretty unprofessional to document just partly the registers of 660x devices. And on request you got nothing.
I hope someone from the community know about this Hw_Arm_Sel 3 pin options. Otherwise, there is just an option of error and trial. Or simply throw the board in the garbage.
Dr. Kirco Arsov
Solved!
Go to Solution.

Hi Kirco,
I have some more information for you :-)
I haven't been able to speak to the developer who is the most familiar with TIO programming since he's out of the office, but I have come across his notes from when he was writing support for the DAQmx driver.
As I described earlier, the HW_Arm_Sel bits don't select a connector I/O pin, but an internal trigger signal. There are seven internal trigger lines, and the HW_Arm_Sel bits map directly to the internal trigger signal: 0b000 - 0b111 map to 0d0 - 0d7. In order to route an I/O pin to an internal trigger, you must also write to a few more registers.
From what I've read, there are two more register families that need to be programmed: TG_x_LevelEdgeReg and TG_x_CombinationReg, where x is the internal trigger number. In your case, you only need one pin from the I/O connector to be your arm start trigger, so TG_0_LevelEdgeReg and TB_0_CombinationReg will suffice for your application.
TB_0_LevelEdgeReg :: Offset 0x660
TG_0_LevelEdgeReg is only 8 bits wide, and maps as follows:
7..6: EdgeMode
5..0: LESel
LESel selects the I/O connector pin to use as the source for the internal trigger signal. 0d0 - 0d39 will select the I/O pin of the same number. NB: behavior for TG_x_LevelEdgeReg is more limited for triggers 1-7, and only a small subset of the I/O pins can be selected for those trigger signals. Trigger 0 can use any I/O pin. Setting these bits to 0d63 forces the trigger source low, and can be used as a way to 'unroute' it when you're finished with your program.
EdgeMode determines whether the TIO will detect an edge of the incoming signal, or just pass the signal level straight through. When detecting edges, it will latch the signal and generate a single TIMEBASE3 pulse instead. 0b00 sets level mode; 0b01 sets rising edge; 0b10 sets falling edge; 0b11 sets either edge.
TG_0_CombinationReg :: Offset 0x6A0
TG_0_CombinationReg is 32 bits wide, and has three fields of interest:
19..16: CombFunction
5..4: CombTypeB
1..0: CombTypeA
CombTypeA controls which trigger subsystem to use as the source for the trigger signal. Since you're coming from an I/O pin and using the edge/level subsystem, you must set these bits to 0b01.
CombTypeB is similar to CombTypeA, and although you won't be using trigger B, set it to 0b01 to be safe.
CombFunction performs a simple logic function on A and B. Since you're only using a single I/O connector, you only need the A output, so set these bits to 0b1100.
All of the other bits should be set to 0b0.
Unfortunately, I'm unable to test these statements since my test machine is currently being used for another research project. Please let me know what happens if you decide to test.
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

What are the commands available to read a file from application server and

What are the commands available to read a file from application server and store the file into an internal table?

Hi,
To read a file from an Application Server to an Object there is a command in ABAP called READ DATASET. After that file is transported to that object you have to do a loop and put that data in an Internal Table.
This statement exports data from the file specified in dset into the data object dobj. For dobj, variables with elementary data types and flat structures can be specified. In Unicode programs, dobj must be character-type if the file was opened as a text file.
For dset, a character-type data object is expected - that is, an object that contains the platform-specific name of the file. The content is read from the file starting from the current file pointer. After the data transfer, the file pointer is positioned after the section that was read. Using the MAXIMUM LENGTH addition, the number of characters or bytes to be read from the file can be limited. Using ACTUAL LENGTH, the number of characters or bytes actually used can be determined.
In a Unicode program, the file must be opened with an arbitrary access type; otherwise, an exception that cannot be handled will be triggered.
If the file has not yet been opened in anon-Unicode program, it will be implicitly opened as a binary file for read access using the statement
OPEN DATASET dset FOR INPUT IN BINARY MODE.
. If a non-existing file is accessed, an exception that can be handled can be triggered.
Influence of Access Type
Files can be read independently of the access type. Whether data can be read or not depends solely on the position of the file pointer. If the latter is at the end of the file or after the file, no data can be read and sy-subrc will be set to 4.
Influence of the Storage Type
The import function will take place irrespective of the storage type in which the file was opened with the statement OPEN DATASET.
If the file was opened as a text file or as a legacy text file, the data is normally read from the current position of the file pointer to the next end-of-line marking, and the file pointer is positioned after the end-of-line marking. If the data object dobj is too short for the number of read characters, the superfluous characters and bytes are cut off. If it is longer, it will be filled with blanks to the right.
If the file was opened as a binary file or as a legacy-binary file, as much data is read that fits into the data object dobj. If the data object dobj is longer than the number of exported characters, it is filled with hexadecimal 0 on the right.
If the specified storage type makes conversion necessary, this is executed before the assignment to the data object dobj. Afterwards, the read data is placed, byte by byte, into the data object.
System Fields
sy-subrc Meaning
0 Data was read without reaching end of file.
4 Data was read and the end of the file was reached or there was an attempt to read after the end of the file.
Thanks,
Samantak.
Rewards points for useful answers.

What are the minimum db user privileges required for CDC?

What are the minimum privileges required for the source data server user in order to to successfully implement CDC
Currently I'm getting an "Insufficient privileges" error when trying to start a CDC journal on a model. The error is happening on the step that creates a trigger on the table in the source schema.
Here's the situation:
The data server uses the user "ODI_TEMP" for its connection. ODI_TEMP has been granted select privileges on the desired tables in the source schema. When starting the CDC journal on the model for the source schema, ODI tries to create a trigger on the source tables. This fails since the ODI_TEMP user can't create triggers on anything outside of it's own schema. For obvious fundamental security reasons, we cannot give the ODI_TEMP user the CREATE ANY TRIGGER system privilege on the data source.
Journalizing is set up using JKM Oracle Consistent. ODI is 11g, DB is 11g.

Hi,
You can go for this
Grant CREATE ANY TRIGGER system privilege to ODI_TMP
Start the Journal , it will create triggers in ODI_TMP schema for the tables present in your source schema.
Now revoke CREATE ANY TRIGGER system privilege from ODI_TMP.
It will continue to work .. only when you are restarting the journal (due to adding or removing some tables in CDC) , you will be requiring CREATE ANY TRIGGER privilege.
Thanks,
Sutirtha

What are structures of logical database.

hi
what are structures of logical database.

Dear Chaitanya,
The structure of LDB can be divided into three sections:
>Structure
>Selection
>Database Program
STRUCTURE:
The structure defines the data view of the logical database. It adopts the hierarchy of the database tables defined by their foreign key relationships. This also controls the sequence in which the tables are accessed. It determines the structure of the other components and the behavior of the logical database at runtime.
The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System. Logical databases have a tree-like structure, which can be defined as follows:
· There is a single node at the highest level. This is known as the root node.
· Each node can have one or several branches.
· Each node is derived from one other node.
The nodes must be structures defined in the ABAP Dictionary or data types from a type group. Normally, these are the structures of database tables which the logical database reads and passes to the user for further evaluation. However, it is also possible, and sometimes useful, to use ABAP Dictionary structures without an underlying database. For technical reasons, the maximum number of nodes allowed in the structure of a logical database is 300.
Any executable ABAP program that has a logical database linked to it can contain a GET statement for each node of the structure. When you run the program, the corresponding event blocks are processed in the sequence prescribed by the hierarchical structure of the logical database. If a program does not contain a GET statement for every node of a logical database, the processing passes through all the nodes that lie in the path from the root to the nodes specified by GET statements.
If you call a logical database using the function module LDB_PROCESS, the depth to which the system reads is controlled by an interface parameter.
SELECTIONS:
The selections define a selection screen, which forms the user interface of the executable programs that use the logical database. Its layout is usually determined by the structure. You can adapt the selections to your own requirements and also add new ones. When you link a logical database to an executable program, the selections of the logical database become part of the standard selection screen of the program (screen number 1000). If you call a logical database using the function module LDB_PROCESS, the selections are filled using interface parameters.
The selections in a logical database are defined using the normal statements for defining selection screens, that is, PARAMETERS, SELECT-OPTIONS and SELECTION-SCREEN. In a logical database, you can also use the additions VALUE-REQUEST and HELP-REQUEST to define specific input and value help. You define the selection screen in a special include program known as the selection include.
When you write programs using a logical database, you can also add your own program specific selections. The standard selection screen then contains the database-specific selections, followed by the program-specific selections that you have defined.
When the system generates the selection screen for an executable program, database-specific selection criteria and parameters are only displayed if you have declared an interface work area for them in your program using the NODES or TABLES statement.
Suppose you have a selection include containing the following lines:
SELECT-OPTIONS slifnr FOR lfa1-lifnr.
PARAMETERS pbukrs LIKE lfb1-bukrs FOR TABLE lfb1.
The selection criterion SLIFNR is linked to table LFA1, the parameter PBUKRS to table LFB1. If the TABLES statement in an executable program (report) declares LFA1 but not LFB1, SLIFNR is displayed on the selection screen, but PBUKRS does not appear.
The selection screen of a logical database can contain dynamic selections as well as static ones. Dynamic selections are extra, user-defined selections that the user can make as well as using the static selections defined in the selection include. To improve performance, you should always use this option instead of reading more data than you need and then sorting it out in the application program.
To make dynamic selections available for the node nodeof a logical database, the selection include must contain the following statement:
SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODE|TABLE node.
If the node node is requested by the user of the logical databases, the dynamic selections are included in the selection screen. A user can then choose Dynamic selections to enter extra selections for the corresponding fields. If you call the logical database using the function module LDB_PROCESS, you can pass a corresponding parameter. You can use these selections in dynamic statements in the logical database program to read data. The values of the program-specific selection criteria that you defined for a node for which dynamic selections were available are also passed to the logical database. The user can also define the fields for dynamic selections as a selection view for the logical database.
The selection screen of a logical database is part of the standard selection screen (number 1000) of the executable program to which the logical database is attached. It has a standardized layout - the selection criteria and parameters appear on separate lines in the order in which they were declared. You can change the layout using the SELECTION-SCREENstatement.
The runtime environment generates the selection screen with number 1000 for every program in which the attributes do not contain a different selection screen version. You can prevent certain input fields from the selection screen of a logical database from appearing on the selection screen by defining selection screen versions with a screen number lower than 1000 in the selection include, and entering this version number in the program attributes. By pressing F4 there, you can get an overview of the selection screen versions defined in the logical database concerned. To define a selection screen version, use the statements SELECTION-SCREEN BEGIN|END OF VERSION. Within these statements you can use SELECTION-SCREEN EXCLUDEto specify fields that you do not want to appear on the selection screen.
If the attributes of an executable program contain the number of a selection screen version, the version is used in the standard selection screen. Although the input fields that you excluded from the selection screen are not displayed, the corresponding selections still exist, and you can still edit them in the program or by calling the function module LDB_PROCESS.
DATABASE PROGRAM:
The database program contains the ABAP statements used to read the data and pass it to the user of the logical database. There is a container for special subroutines into which, amongst other things, the data from the database tables is read. These subroutines are called by the reporting processor in the runtime environment in a sequence that has been predefined by the structure. The database program is determined by the structure and selections and can be adapted or expanded to meet your requirements.
The name of the database program of a logical database ldbconforms to the naming convention SAPDBldb. It serves as a container for subroutines, which the ABAP runtime environment calls when a logical database is processed. The sequence of the calls and their interaction with the events in executable programs or the function module LDB_PROCESS depends on the structure of the logical database.
A logical database program usually contains the following subroutines:
· FORM LDB_PROCESS_INIT
Called once only before the logical database is processed. It prepares it to be called more than once by the function module LDB_PROCESS.
· FORM INIT
Called once only before the selection screen is processed.
· FORM PBO
Called before the selection screen is displayed, each time it is displayed. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS.
· FORM PAI
Called when the user interacts with the selection screen. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS. The interface parameters FNAME and MARK are passed to the subroutine.
FNAME contains the name of a selection criterion or parameter on the selection screen.
MARK describes the selection made by the user: MARK = space means that the user has entered a simple single value or range selection. MARK = '*' means that the user has also made entries on the Multiple Selection screen.
· FORM LDB_PROCESS_CHECK_SELECTIONS
Called instead of the subroutine PAI if the logical database is called using the function module LDB_PROCESS without a selection screen. This subroutine can check the selections passed in the function module interface.
· FORM PUT_node
Called in the sequence defined in the structure. Reads the data from the node nodeand uses the
PUT node.
statement to trigger a corresponding GETevent in the ABAP runtime environment. The PUT statement is the central statement in this subroutine: It can only be used within a subroutine of a logical database. The logical database must contain the node node, and the subroutine name must begin with PUT_node. The PUT statement directs the program flow according to the structure of the logical database. The depth to which the logical database is read is determined by the GET statements in the application program or the interface parameter CALLBACK of the function module LDB_PROCESS.
First, the subroutine PUT_root is executed for the root node. The PUT statement then directs the program flow as follows:
i. If the database program contains the subroutine AUTHORITY_CHECK_node, the first thing the PUT_node statement does is to call it.
ii. Next, the PUT statement triggers a GET event in the runtime environment. If there is a corresponding GET nodestatement in the executable program to which the logical database is linked, the associated event block is processed. If the CALLBACK parameter of the function module LDB_PROCESS is filled accordingly, the corresponding callback routine is called.
iii. The PUT statement directs the program flow
(a) To the next subroutine of a node that follows directly, if a lower-level node (not necessarily the very next) in the same subtree is requested by GET in the executable program or in the function module.
(b) To the subroutine of a node at the same level, if the preceding node branches to such a node and if a GET statement exists for such a node in the executable program or the function module.
The PUT statement in that subroutine starts again at step (i). In the subroutine of the lowest node in a subtree to be processed using GET, the program control does not branch further. Instead, the current subroutine is processed further. When a subroutine PUT_node has been executed in its entirety, the program flow returns to the PUTstatement from which it branched to the subroutine PUT_node.
iv. When control has returned from a lower-level subroutine PUT_node, the PUTstatement triggers the event GET node LATEin the runtime environment.
· FORM AUTHORITY_CHECK_node
Called automatically by the PUT node statement. In this subroutine, you can specify authorization checks for the appropriate node node from the structure of the logical database.
· FORM PUT_ldb_SP
Called when the user makes a selection using a search help to process the key chosen in the search help. ldb is the name of the logical database. From this subroutine, you can use the entries in the search help tables to read the relevant entries from the root node root. The processing in the program can then be triggered using PUT root. The subroutine PUT_root is then not called automatically.
· FORM BEFORE_EVENT
Called before an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value START-OF-SELECTION, to call a subroutine before this event.
· FORM AFTER_EVENT
Called after an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value END-OF-SELECTION, to call a subroutine after this event.
· FORM par_VAL, selop_VAL, selop-LOW_VAL, selop-HIGH_VAL
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
· FORM par_HLP, selop_HLP, selop-LOW_HLP, selop-HIGH_HLP
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
Example
Suppose that in the logical database structure, LFB1 is a branch of LFA1.
and that the following selection criteria are defined in the selection include:
SELECT-OPTIONS: slifnr FOR lfa1-lifnr,
sbukrs FOR lfb1-bukrs.
A section of the database program would then read:
FORM put_lfa1.
SELECT * FROM lfa1
WHERE lifnr IN slifnr.
PUT lfa1.
ENDSELECT.
ENDFORM.
FORM put_lfb1.
SELECT * FROM lfb1
WHERE lifnr = lfa1-lifnr.
AND bukrs IN sbukrs.
PUT lfb1.
ENDSELECT.
ENDFORM.
An executable program (report) linked to the logical database could contain the lines:
GET lfa1.
WRITE lfa1-lifnr.
GET lfb1.
WRITE lfb1-bukrs.
In this example, the runtime environment calls the routine put_lfa1 after the event START-OF-SELECTION. The event GET lfa1 is triggered by the statement PUT lfa1.
Once the corresponding event block in the program is complete, PUT lfa1 branches to the subroutine put_lfb1.
From this subroutine, the event GET lfb1 is triggered in the application program. If LFB1 is the last node to be read, processing resumes with the SELECTloop in put_lfb1. Otherwise, the program flow moves to the subroutine put_node of the next node. At the end of the SELECT loop of the last node, processing resumes in the SELECTloop of the node at the next level up. The example of programming using nested SELECT loops is only used to make the program flow clearer. In a real logical database, you would avoid doing this in order to minimize the number of database accesses.
Regards,
Rajesh K Soman
Please reward points if helpful.

What are the events in interactive reports?

what are the events in interactive reports?
could plz explain

hi,
First event -
Initialization : triggered when the report is loaded in memory.
At selection-screen output : triggered when the selection screen is loaded in memory before being displayed.
At selection-screen : before leaving the selection screen.
start-of-selection : the first event for displaying the report.
This event keyword defines an event block whose event is triggered by the ABAP runtime environment
when calling the executable program selection screen processing of a selection screen.
In an executable program, all statements that are not declarations,
and are listed before the first explicit processing block, are assigned to this event block.
If the program does not contain an explicitly defined event block START-OF-SELECTION,
these statements form the complete event block START-OF-SELECTION.
If a program contains an explicitly defined event block START-OF-SELECTION,
these statements are added to the beginning of the event block.
If the program contains no explicitly defined event blocks,
these statements form the entire event block START-OF-SELECTION.
end-of-selection : after the start-of-selection is completed.
classiscal report events.
top-of-page : every time a new page is started in the list.
end-of-page : every time the list data reaches the footer region of the page.
interactive report events.
top of page during line selection : top of page event for secondary list.
at line-selection : evey time user dbl-clicks(F2) on the list data.
at pF<key> : function key from F5 to F12 to perform interactive action on the list.
at user-command
http://help.sap.com/saphelp_47x200/helpdata/en/56/1eb6c705ad11d2952f0000e8353423/content.htm
Rgds
Anver

WHAT ARE SUBEVENTS OF DIFFERENT EVENTS IN REPORTS ?

WHAT ARE SUBEVENTS OF DIFFERENT EVENTS IN REPORTS ?
BEST REGARDS,
RYAN

hi,
output events are.........
start-of-selection.
using this event we can genarate basic list.
end-of-selection.
we can use this event also for genarating basic list
top-of-page.
this event is related to list, we can use this event to providing list header.
end-of-page.
this event is related to list, we can use this event to providing list footer.
if our program reading data from logical database, in that case GET and
GET LATE events triggered to genarate report.
interactive repotrs.
we use AT LINE -SELECTION and AT USER-COMMAND events to genarate secondary events based on user actions.
TOP-OF-PAGE DURING LINE-SELECTION EVENT, provides page heading to all secondary lists.
PBO and PAI events also used to genarating list.
regards,
AshokReddy.

What are types of reports?

what are types of reports?
could plz explailn clearly

Hi
From a theoretical perspective there are two type of reports
Classical Reports , and
Interactive Reports .
The classical reports are simple lists that display the data entries
in a simple format on one screen ( also called as basic list).
In case of Interactive reports , it is possible to transition/ move from the basic
list to secondary lists on triggering a command event like double_click ,
at line selection .
In interactive reports , on display of a secondary report , a new header can be
specified , as a different select query is executed for it .
The ALV reports are an expample of interactive reports .
ALC are of two kinds :> list and grid display .
These r basically used for customized data formatting and display.
Gris ALV has option for header details and provies a faciity for summing numering fields , or performing certain arithmetic oprns on it.
Alv reports can further b interactive where a secondary display is possible.
plz specify if u need further pointers on it
Regards
Pankaj

How to identify what are all the events are created in background jobs?

Hi all,
how to identify what are all the events are created for background jobs. And what events gets triggered for a particular job.
thanxs
haritha

Hi Haritha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
Also Pls check DB02 for database performance and ST03 for workload .
Analyse u will have an idea ,
*pls assign points,if info is useful**
Regards
CSM reddy
null

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

What are the advantages..

Hi friends,
 can you please tell me what are the advantages of using MVC? because i can use ABAP Objects without using MVC.
Thanks in advance,
Regards,
Kannan.

Hi Kanna,
 For Dynamically componentised you need to use controller.In the main page you partition for what you want to present dynamically and then call controller as a response to the user.What the action you have take in case of Page flow logic(Event Handler) need to be placed in controller.
Using the MVC design pattern has the following advantages:
· Structuring BSP applications is simplified, since the view is cleanly separated from the controller and the model. This not only facilitates changing BSP applications, but also considerably improves their maintenance.
· You have the option of generating program-driven layout. The HTML/XML output is therefore created by program code instead of a page with scripting.
· Navigation using the <bsp:goto> element and call using the <bsp:call> element. The advantage of using <bsp:goto> navigation over redirect is that there is no additional network traffic. Furthermore, you remain in the same work process, which can have advantages for creating objects and memory space. The call using <bsp:call> element is more variable than adding them using INCLUDEdirective, since it is triggered at runtime.
With the call option using <bsp:call>, you can also distribute the user interface into components.
· Optimized performance due to fewer redirects.
· Intuitive and east-to-use interface for application development.
Main advantage of MVC is that you can keep these(Model View ,Controller) separately.If you need to change in logic you do not have to worry about presentation(View).
Regards,
Albert

What are the possible errors that can happen in data loads(rsmo monitor)?

hi all,
what could be the error that could result in red color in the RSMO monitor of data load transaction?
1. request everything ok
(what are the possible error type which make here red)
2. extraction everything ok
(what are the possible error type which make here red)
3. transfer (idocs and trfc) error occured?
(what are the possible error type which make here red)
4. processing
- data package
5. process chain
(what are the possible error type which make here red)
6 other messages.
(what are the possible error type which make here red)
thanks
pooja

Hi,
I can tell you the most common reasons of these failures.
1. request everything ok
Here it will be telling you if the request was properly send to source system and got triggered there.
2. extraction everything ok
In this step the actual extraction of data happens, issue slike sysfail or CPIC error may cause this to fail.
3. transfer (idocs and trfc) error occured?
When extraction is complete and data is being send to BW. But if dur to some reason it fails, error may come here.
4. processing
Processing in BW fails for each data packet is displayed here.
This can also happen when you have sysfail in source.
5. process chain
This can show the logs of the chain here and also status of subsequent process.
6 other messages.
Any other error message.
Refer
What is the information we can get the through details tab in RSMO
working with RSMO errors
http://help.sap.com/saphelp_nw70/helpdata/en/12/43074208ae2a38e10000000a1550b0/frameset.htm
Also
Data Load Errors
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Data Load issues
Errors in loading
data loading errors
load Errors
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
process chain issues or errors
Hope this helps.
Thanks,
JituK

What is workflow ? What are the advantages of using workflow? What are the

what is workflow ? What are the advantages of using workflow? What are the steps for building a workflow ?

Hi Leela,
Your question is very straight question.
Better u can follow these links.
http://www.esnips.com/doc/90b7763b-f9d9-4861-a273-04674b9fe3f2/Workflow
http://www.esnips.com/doc/991843e0-8686-4949-94b9-f45d90081b22/workflow
And i'll give some theory answer for ur questions
i.e.,SAP Business Workflow can be used to define business processes that are not yet mapped in the R/3 System. These may be simple release or approval procedures, or more complex business processes such as creating a material master and the associated coordination of the departments involved. SAP Business Workflow is particularly suitable for situations in which work processes have to be run through repeatedly, or situations in which the business process requires the involvement of a large number of agents in a specific sequence.
You can also use SAP Business Workflow to respond to errors and exceptions in other, existing business processes. You can start a workflow when predefined events occur, for example an event can be triggered if particular errors are found during an automatic check.
SAP provides several workflows that map predefined business processes. These workflows do not require much implementation. For an overview of these SAP workflows, refer to Workflow Scenarios in Applications.
Integration
SAP Business Workflow uses the existing transactions and functions of the R/3 System and does not change the functions. You can combine the existing functions of the R/3 System to form new business processes with SAP Business Workflow. The workflow system takes over control of the business processes. If you are already using SAP Organizational Management, you can use the organizational structure created there to have the relevant agents carry out the individual activities. It is possible to have an activity carried out by a position. This ensures that the respective occupiers of the position can carry out the individual activities during execution of the workflow. This means that personnel changes in your organization are taken into account immediately in the execution of a workflow.
Features
SAP Business Workflow provides a number of tools for defining and analyzing workflows as well as for monitoring operation.
The Workflow Builder is for displaying and making changes to workflows. You can make small extensions directly to the original workflows supplied by SAP, such as carrying out your own agent assignments or changing deadline monitoring.
There are several Workflow Wizards to support you in the definition of workflows, with which you can create specific parts of a workflow. The Workflow Wizard Explorer gives you an overview of the existing Workflow Wizards.
In order to make the functions of the R/3 Systems available to a workflow, you use business objects, which you can define and analyze in the Business Object Builder. These business objects are made available to the workflow in reusable tasks. The Business Wizard Explorer gives you an overview of all existing tasks.
The end user receives information about the activities they are to carry out in their Business Workplace. This provides them with a central overview of all the activities that they are authorized to carry out. They can commence the activities from here.
Several tools are available to the workflow system administrator, with which they can control and analyze the current workflows. The workflow system administrator is notified of problems automatically by the system.
Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
This has a step by step procedure :
http://fuller.mit.edu/workflow/debugging.pdf
www.erpgenie.com/sap/workflow/debugging.htm
http://www.erpgenie.com/workflow/debugging.htm?2b5de440
Rewards if it is useful.

What are "On Triggers"

Similar Messages

Maybe you are looking for