Reply: 1

Auto translated

Job for dunning run- generated spool requests without authorization group

Hello everyone,

I would like to carry out a weekly dunning run with an automated SAP job. The job has a step with the program RF150SMS. This job triggers a follow-up job with the programs SAPF150S2 and SAPF150D2. The spool requests can be found in program SAPF150D2. Four lists are generated, but unfortunately only one list receives the authorization value from the original job (frame job) with program RF150SMS, so that the department can see this spool request.

My question is, what do I have to do so that the remaining three lists, which are also generated by the follow-up job, also receive the authorization group so that the department can also see them? The authorization group is not inherited by them. These lists are apparently generated sequentially at different times when the program runs. In short, I would like to ensure that all spool requests from the automated dunning run can be viewed by the department. Thank you very much.

You must be logged in to post a reply.

Login now

1 Answers

  • BETA
    ChatBot
    Automated answer
    This reply was automagically generated by our Espressi A.I. Think of it as a one-off attempt to instantly solve your problem. It will not respond to further replies.

    Hello, there are several possible approaches to the problem you have described with the spool requests in the SAP system and the transfer of authorization groups. The aim is to ensure that all spool requests generated by the follow-up job receive the same authorization group as the original job. 1. Check the job and program configuration: First of all, it is important to check the configuration of the initial job and the follow-up jobs carefully. It could be that the authorization group is only set specifically in the first step of the job. You should check whether there are options in the job definitions (SM37) and in the program parameters to define the authorization group explicitly. 2. Adaptation of the programs: Another option is to adapt the SAP programs SAPF150S2 and SAPF150D2 so that they explicitly adopt the authorization group of the original program RF150SMS. This could be achieved by a programmatic adjustment in which the authorization group is transferred as a parameter and set accordingly by the subsequent programs. 3. Use of variables/buffers: You could use a temporary storage solution (e.g. an SAP buffer table) to store the authorization group during the run of the frame job and then retrieve it in the subsequent jobs. However, this technical solution would require a change in the ABAP programs in order to set and retrieve the value. 4 Subsequent adjustment of the spool requests: A pragmatic solution could be to adjust the authorization groups of the spool requests subsequently after creation using a separate program or script. This could be automated by setting up another job that monitors the spool requests and modifies them accordingly. 5. SAP authorization management: Also make sure that SAP authorization management is set up correctly so that the transfer of authorization groups within jobs is technically supported. It is recommended to perform the adjustments in a test environment before they are transferred to the production systems to avoid unintended effects. If possible, consult an SAP consultant to assess the impact on other areas or processes in the SAP system and to provide technical support. I hope these steps help you!

    Need more help from our chatbot? Click here and visit our AI SAP Helper on the SAP learning platform et.training.1

    1. log in with your Espresso Tutorials account. Digital subscription or trial access required.