Printing without spool request/output determination generated? Doubts about spool system

[andreschgz95]

Hi SAP experts,

There is an SAP standard solution for electronic invoicing (B2G) that overall works as follows:

1. Send a document to government entity system for getting documents signed/cleared/approved.
2. After few minutes an SAP job is triggered and runs a program that retrieves the document status from governement system (it does a remote call to external system).
3. If documents are signed/cleared/approved, the document is flagged with "100" code in SAP standard table. That means that document is approved by government.
4. The same program that retrieves the status from government (program J_1BNFE_CF_STATUS_UPDATE) now triggers the printing process for each approved document, so if doc XYZ001 is approved, it will be also printed.

All the process flow is working fine and there are no errors with the printing, meaning that all documents that has to be printed, are effectively printed.

However, not all documents generate spool request and output determination when are printed. When I say that "not all documents generate spool request" I'm not saying that spool request are not generated at all (at least I cannot affirm that as a fact), but I'm not able to see the spool request associated to them in the SP01 tcode, so maybe spool request are being generated but not stored.

So, there are some documents that generate and store the spool request and output determination in the system while others don't. Why is that?

When I see the job's steps log I can see that same steps are being executed for both types of documents - the one that generates spool request and the one that doesn't - however, I can see spool request log in the job that runs a document that generates spool request while the other job doesn't have any spool request log.

I think this could be an standard behavior, maybe ruled/determined by some configuration, but honestly I'm not sure or either I know where could be that configuration stored.

Have you ever seen this kind of behavior before? Do you know some possible explanation for this? Does it look like and error or just regular behavior based on solution configuration?

PD: I have already checked and there aren't issues related to spool request ranges at all.

Thanks and regards.

Andres.

[RaymondGiuseppi]

Are there any information available in the application log (SLG1)

e.g.

• Object - NFE
• Sub Object - MONITOR

In the transactions used to display the documents, is there an option to navigate to some log or output status ?

[Sandra_Rossi]

First of all I don't know B2G, I just provide a general answer concerning NW ABAP Print and Output Management.

It's difficult to help if you don't describe an exact scenario how to reproduce the issue.

When an ABAP program generates a spool request, there's an option "delete immediately after printing". There's also a spool retention period and a spool cleanup job.