You try to create a job, but the process fails. You observe one of the two symptoms:
1. The BP_JOB_CREATE function module returned the exception CANT_CREATE_JOB. In addition, the system log contained the error messages EFW, EG7, and EGA (in exactly this sequence).
2. In the syslog you see the messages EAS, EBC, EBN (in exactly this sequence).
This is not an SAP error.
The problem above has the following background:
The unique key for a job in the database is derived from the combination <job name><job count>. The job count consists of 8 digits and is created by the system while it is creating the job.
The first 6 digits are a time stamp in the HHMMSS format (where H equals "Hour", M equals "Minute" and S equals "Second") that describes the second in which the system has created the job.
The last two digits are a sequence number, starting with 01.
If, for example, the system creates a job with the name ABC at 8:20:07, the job will have the job count "08200701" if another job ABC with this job count does not exist yet.
If this job already exists, the system tries to assign job count 08200702, in other words, it increases the sequence number. If a job ABC with job count 08200702 also already exists, the system will try job count 08200703, and so on.
Important: With Note 942804, the job count generation process has been enhanced. The system now also uses capital letters as the last two characters. This increases the limit mentioned below from 99 to 1295. As a result, the problem is partly solved.
From this behavior, we can draw two conclusions:
1. Within the same second, the system can create a maximum number of 99 jobs with the same name. In practical terms, this limit is probably unimportant.
2. If the system creates, for example, the same job every day at the same second, and if the jobs are never deleted, the job can no longer be created in this same second after it was scheduled 99 times, and the EFW, EG7, and EGA error messages will be written to the system log. This scenario is not unrealistic.
Remark:
If you are scheduling a periodic successor job, and if this scheduling fails for the above-mentioned reasons, you will see the messages EAS, EBC, EBN in the syslog instead of the messages mentioned above.
If you want to be sure that this is the problem you have encountered, you can check the contents of the TBTCO job table.
Delete old jobs at regular intervals with the RSBTCDEL deletion report or with the newer RSBTCDEL2 report.
You can schedule the RSBTCDEL job as a standard job.