Topics Covered -

• SAP Program and Banking Challenges
• Backward Job Scheduling in SAP
• Job Scheduling, Execution, and Workflow
• Scheduling Background Tasks and Variants
• Report Program Variants and Debugging
• BBDC Documents and Divorce Discussion
• Background Program Job Scheduling and Execution
• SAP Performance Tuning and Code Optimization
• File Sharing and Data Project Updates

Summary

SAP Program and Banking Challenges

pradeep led a discussion about a bank's SAP program and how it handles loan payments. The team discussed the concept of 'above coding', which refers to the process of selecting the amount from the customer and intaking it into the bank. pradeep proposed a challenge to the team: to create a program that executes a specific task every month, on a specific day, at a specific time. The team debated the technicalities of this, including the use of hard coded dates and the practicality of setting an alarm for every day. The discussion concluded with pradeep acknowledging the team's efforts but noting that the proposed solution may not be fully applicable in practice.

Backward Job Scheduling in SAP

pradeep explained the concept of 'backward job scheduling' in SAP, which allows users to schedule their programs to run in the background at specific times. He used an example to illustrate this and outlined the plan to teach the team how to schedule report programs in the background. pradeep further discussed the process of scheduling background jobs, including setting up variants, handling failed jobs, and the use of job logs. He also clarified the use of the 'cancel' option in case a customer cancels the job after payment.

Job Scheduling, Execution, and Workflow

pradeep explained the process of job scheduling and execution, emphasizing that the team doesn't need to write the back-end coding as it is standard and will be handled by the basis team. He highlighted the importance of understanding the function models and encouraged the team to complete the loop statement for BDC by the weekend. pradeep also mentioned that LSMW, a part of BDC, is not their work but will be handled by the functional team. Furthermore, he discussed the concept of workflow, noting that it is not currently in use but will be utilized in the future for approval processes and other related tasks.

Scheduling Background Tasks and Variants

pradeep explained the process of scheduling background tasks and saving variants, emphasizing that only one variant can be given at a time and it's possible to modify a variant if created incorrectly. He further demonstrated how to use the T. Code Sm. 36 to schedule a background task, including specifying the job name, program name, and variant. pradeep also showed how to use a new job creation and execution feature, explaining the various options and settings available, and how to check the status and output of a job. He clarified the process of job dependency and its impact on execution order. Shyam and Ajo were present and seemed to understand the explanations and demonstrations.

Report Program Variants and Debugging

Ajo and pradeep clarified the use of report program variants, agreeing that one program can use multiple variants. pradeep explained that each variant requires a separate background job to function properly. Shyam raised concerns about identifying whether a program is running and whether it's picking requests. Pradeep advised checking the SM37 for job status and, if necessary, using Abapas to debug the program for a specific variant. Pradeep encouraged the team to try this approach with their own programs and reach out if they had any questions or issues.

BBDC Documents and Divorce Discussion

Pradeep agreed to share all the documents, including those related to BBDC. Shyam brought up an unrelated topic about divorce and asked when would be the right time for it. The conversation seemed disjointed and lacked clear context.

Background Program Job Scheduling and Execution

Shyam, pradeep, Pritish, and Ajo discussed issues related to job scheduling and execution in a background program. They explored how to debug the program, schedule jobs with different priorities, and handle situations where jobs are not executed as expected. pradeep clarified that the program would run in a queue and that jobs with higher priority would take precedence. Ajo was guided through the process of scheduling and executing a job, and they also discussed how to handle errors and incorrect job scheduling. pradeep committed to sending documentation to aid in understanding the background job functionality.

SAP Performance Tuning and Code Optimization

pradeep discussed the importance of performance tuning in SAP coding. He demonstrated how to use the 'check' and 'code inspector' features to identify issues and improve code efficiency. He emphasized the need for proper exception handling and the use of binary search instead of 'select' for better performance. pradeep also mentioned that he would provide further details on these topics in upcoming sessions. Shyam confirmed that the discussed inbuilt program is used to detect coding errors.

File Sharing and Data Project Updates

Shyam requested pradeep to share files via email due to download issues, which pradeep agreed to. pradeep then discussed the advanced topic of enhancements for the upcoming Monday session and assigned a mini project for the team to complete by the weekend. Pritish shared his progress on a data project, which pradeep confirmed was correct, and they discussed the importance of maintaining the same structure when transferring data from a notepad to an internal table. The team was advised to have a clear structure and pass all data for understanding.