For the last few weeks, I have been working on a requirement that required a custom Adobe form for a standard GR label through NACE but later, we had to opt for new BRF+ O/P management. The ideal approach is to use fragmented Adobe form, but the number of fields was not there in the standard service interface. So, we opted for the DDIC interface option available in ‘Assign Form Templates’.
Challenge: To achieve this requirement, I had faced a couple of challenges:
Spool request could not be found - APOC_OR_MESSAGES (145): Discussed in this blog.
Dump - /BOBF/CX_FRW_FATAL – CLASS CL_APOC_OR_A_ITEM_GET_DOCUMENT: Create a Z* Driver program for the form individually and check the issue there – for my case, ADS Configuration was the issue, handled by me and basis tech guy
In this blog post we will cover the steps to print GR Label and handle Spool request could not be found - APOC_OR_MESSAGES (145).
Firstly, get the name of the standard program – subroutine (Form routine) that you would be triggered in the back-end from the business process. You can later, choose any other sub-routine as well, if that one has better parameters as per your requirement. Make sure the sub-routine you are choosing has *PDF or ADOBE* naming pattern to have the FP_JOB_OPEN/CLOSE else you must manually change the printout subroutine.
** In my case, I have used Program – SAPM07DR, Routine - ENTRY_WE03_PDF.
2. Create an executable report ZAB_IM_SAPM07DR replicating subroutine-pool SAPM07DR, Includes ZIN_IM_M07DRTOP, ZIN_IM_M07DRSON_PDF from M07DRTOP, M07DRSON_PDF resp. and replace the std. includes with them in program ZAB_IM_SAPM07DR.
3. Go to SFP, create a DDIC interface as per the parameters exported in the sub-routine, handle the required processing logic, and create the required layout in ADOBE form to the interface.