Welcome to Amrit's World of SAP

  We know that background jobs run by their own in the background and there is no interaction with them. Now, Suppose a background job got executed and we are getting some wrong data in the output, then how will I debug my background job. Transaction code for Debugging :- JDBG Also known as Job debugging. Debugging our Background Job :- Step 1 :- Go to SM37 transaction code and give a job name into it. Step 2 :- Click on execute button. Step 3 :- Now write JDBG transaction code and press enter. We can see, we have entered into the debugging mode. Now, Press F7 multiple times until you reach the program in which you have written your entire code. Here, you can debug your program as you want

  In the previous part, we have scheduled a background job for our Traffic Light in OOPS ALV program. Now, Suppose I want to schedule a background job for a particular variants i.e. for input ( 1 to 10 ). Creating a Variant for our program :- Step 1 :- Execute the OOPS ALV program and pass the inputs on the selection screen. Step 2 :- Now click on save button. Step 3 :- Pass the name of the variant and pass the short description and click on save button. Now, we can use this variant for job scheduling. Scheduling a background job for a particular variant :- Step 1 :- Go to SM36 transaction code. Step 2 :- Give a name to the job Step 3 :- Provide the job class. Step 4 :- Click on step to add program. Pass the program name and the variant name. Click on save button → Click on save button. The status will change to the schedule. Step 5 :- Click on start condition to give the start condition. Click on save button → click on save b

  Step 1 :- Go to SM36 transaction code and give a name for the background job. Step 2 :- Provide a job class for the same. Step 3 :- Press enter. Step 4 :- Provide the name of the program and click on save button. Step 5 :- Again click on save button so that the status of job can be changed to scheduled status. Step 6 :- Click on start condition → Click on date and time → Provide the date and time based on requirement. Step 7 :- If your job is periodic, then you can select the periodic job checkbox → click on period values to assign the period Click on save Click on save. Status Of job :- We can see its status is currently released as it will start on 11 : 55. At 11:55 , the delay count has started. and since, period is 1 minute, It will get executed at every minute. Now, select the job → go to job and change the status to schedule, If it is not mandatory.

  Suppose, I have a program for traffic lights in OOPS ALV. I want to schedule this program in a background job for a particular time period. Scheduling a Background Job for Immediate basis:- Step 1 :- Go to SM36 transaction code. Step 2 :- Give a name to the background job. Step 3 :- Now, we will select the priority of the job. Suppose, A selected it a high priority job ( Class A ). Step 4 :- Now click on save button or click enter button, you will see a popup screen. In this particular screen we will Step 5 :- In the name section, pass the name of the program. Step 6 :- Click on save button. As soon, as we will click on save button we will get a pop up message. Our background job is now scheduled. Step 7 :- No we can check the status of the background job in SM37 transaction code or I can click on Job selection tab for the same purpose. Step 8 :- Now we need to give the start condition. Click on start condition. A pop up

  In Advance Business Application Programming, we have two types of Jobs. Foreground Jobs :- They are also known as interactive jobs. User can interact i.e. User will give the input and get the output. So, basically whatever you create in SAP systems i.e. Reports, Tables, Classes, Objects etc. All are basically foreground jobs, For, example Suppose I have this below report. When, I will execute my program, I will have to pass the input, and based on my input. The system will show the output, So this kinds of jobs in which user can interact are called as Foreground jobs. 2. Background Jobs :- Background jobs are non interactive jobs i.e. users cannot interact with the job. The background jobs are the non - interactive jobs in the SAP system that perform their work in the background without affecting the normal operations. Once the background job is defined, the system makes sure that it runs the defined job at a specific time. Features of B

 In the previous part, we say that we call design our layout by clicking on the layout tab. We can see one master page is already given by ADLC ( Adobe Livecycle designer ) creates automatically. Master Page :- Every form design contains at least one master page that adobe livecycle designer creates automatically. Master pages are responsible for formatting body pages. The purpose of master page is to provide the design consistency, For eg. Suppose, you want to design a logo on all the body pages, so we will design that logo on the master page and it will be automatically br reflected on all the body pages. Body Page :- Body pages represent the pages of a form. Each body page derives its page size and orientation from a master page, and by default, each body page is associated with the default master page that adobe livecycle designer creates. Each body page is created with a default sub form that covers the whole page. What we have to design ? So, for Eac