Zend certified PHP/Magento developer

SAP: issue with output type in shipment

I’m a junior SAP functional consultant and I was challenged to find the solution to an issue that several experimented functional and technical consultants haven’t been able to find yet. Let’s see if I’m lucky.

Here’s what’s going on: a shipment (of type ZG11 and assigned to the output determination procedure V7STRA) is created with transaction VT01N. One of the output types associated with the shipment type ZG11 is ZCMR. Sometimes, the first time a shipment is processed (that is, when the shipment type is created with transaction VT01N), the system doesn’t trigger the output type (there’s no printing of the form) because, as one can see in the processing log of the output type, the shipment does not exist (!):

FIRST IMAGE

When the shipment is processed a second time (with transaction VT02N), the system finally finds the shipment and triggers the output:

SECOND IMAGE

Above, the first line corresponds to the error of the output type the first time the shipment was processed (of which I gave the details in the first image), and the second line corresponds to the successful triggering of the output type after a second processing of the shipment.

Now, I went through the configurations of output type ZCMR and compared it to the configurations of the other output types assigned to the output determination procedure V7STRA. The program (a Z program) that is called up by the system to process this output type is common to 12 other output types of procedure V7STRA. I don’t think that all of the other output types that have this program have this issue, so I don’t think that the Z program is what is causing the problem.

Also, the access sequence assigned to this output type is not a standard one. That access sequence goes through two tables: one is a standard table, the other isn’t. All of the fields that belong to the two tables in question are fields that belong to the standard field catalog, so I guess they are correctly mapped to the convenient communication structures.

I’m now going through a list of several shipments created after 1 of January 2020 and see for which ones the output types malfunctioned and those for which everything went fine and see if there’s a pattern. I’m wondering if the non-standard access sequence has something to do with all of this, since there is at least another ouptut type with this problem.

With all of this said, is there something you think I should do to identify the problem?

Thank you for your time.