Home| Forums | Join Google Group | Join Yahoo Group | Jobs

Earn Money
а Trading Forex Online
ааParamount Airways
ааFree Data Recovery
аCargo
аJob Portal
ааHSBC Investment
аManagement
аCheap Web Hosting
ааMake Trip
ааCheap Air Travel
аLeisure Hotel
ааFree Air Travel
ааMutual Fund Informations
а аCheapest Cellular Plan
аFree Sexy Indians
ааCall Center Software
ааHot Indian

Programming Help | Homework Help | Counseling
Astrology Advice | Tarot Advice | Parenting
Dating Advice | Love Advice | Divorce Advice
Legal Advice | Debt Advice | Career Advice
How do you set up background jobs in SAP? What are the steps? What are events driven batch jobs? - Create a job using function module JOB-OPEN - Collect the job specifications. - Add a job step to the job with the function module JOB-SUBMIT. - Close the job and pass it to Background processing system for execution with the function module JOB-CLOSE - EVENT DRIVEN BATCH JOBS :- - Types = System events н triggered when activation of new operation mode takes place - User events - Triggered from ABAP/4 or external program. - Triggering an event notifies the background processing that named condition has been reached. The Background system reacts by starting any jobs that were waiting for the event. Transaction codes related to background jobs creation and processing are :- SM36(Job creation) SM37(Job selection and execution). What are presentation and application servers in SAP? -A presentation server is actually a program named Sapgui.exe. It is usually installed on a user's workstation. - Application server is a set of executables that collectively interpret the ABAP/4 programs and manage the input & output for them. In an ABAP/4 program how do you access data that exists on a presentation server v/s on an application server? - For presentation server use UPLOAD or WS_UPLOAD function modules. For application server use OPEN DATASET, READ DATASET and CLOSE DATASET commands. What is the difference between Synchronous and Asynchronous updates ? - A program asks the system to perform a certain task, and then either waits or doesn't wait for the task to finish. In synchronous processing, the program waits: control returns to the program only when the task has been completed. In asynchronous processing, the program does not wait: the system returns control after merely logging the request for execution. Transferring SPA/GPA Parameters to Transactions To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-related SAP memory. You use the SAP memory to transfer values between programs beyond the borders of transactions. A user can access the values stored in the SAP memory during one terminal session for all modes used in parallel. To fill an SPA/GPA parameter, use: Syntax SET PARAMETER ID <pid> FIELD <f>.