Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

NACE - Storage system - Document type

karthick1608
Participant
0 Likes
3,324

Hello all,

Whenever we change the Document type on NACE -> Output types -> Storage system -> Document type.

While creating OR whenever reprocessing a delivery, there is dump gets created.

"WRITE_FORM is invalid, OPEN_FORM is missing".

Ideally, it will show the attachment file in Delivery -> Attachment list. When we change the document type throws dump.

I am totally new to this kind of issue. Please tell me where to check and what will the flow of execution.

Please share your points.

Thanks

Karthick

4 REPLIES 4
Read only

FredericGirod
Active Contributor
0 Likes
2,115

Could you clarify what is your objective ?

Read only

karthick1608
Participant
0 Likes
2,115

Hi Frederic,

Main objective is to understand the pre-requisite to be checked before changing the document type.

Dump should not occur while changing the document type.

Read only

VeselinaPeykova
Active Contributor
2,115

Are you really, 100% sure that the dump is related to your ArchiveLink configuration?

I ask because this kind of problem usually points to issues with printforms or wrong print programs, not to the storage of documents.

If you believe that the problem is with ArchiveLink you can run transaction OACK to verify at least some of the required settings.

Still, as a first step I would ensure that the process works when the output type is configured with Print only option in Storage mode and then start investigating problems with ArchiveLink.

This is particularly important if this is a custom output type with custom print program etc.

Even the long text of the error message for TD 423 hints that one should check the print program.

If this is a standard output type with standard print form and standard print program it makes sense to search SAP notes by specifying TD423 as criterion, because I can see a few notes on the subject for some older releases.

If this is not a standard output type with standard print program and print form and the error is raised even with Print only it also makes sense to test whether the process works for standard outputs (again with Print only option).

Read only

kaus19d
Active Contributor
0 Likes
2,115

Hi Karthick R,

1. Check t-codes: OMJ3 and OMJ4 where you option for output type links to your printer device

2. As we are aware, there is no such option provided by SAP in scripts to print the text in different colors. So we can create a driver program to call the SAP Script (OPEN_FORM, WRITE_FORM and CLOSE_FORM) in order to get the OTF data. Try the FM ‘PRINT_OTF’.

3. Please check the following,

https://answers.sap.com/questions/10518336/writeform-is-invalid-openform-is-missing.html

https://answers.sap.com/questions/9938546/storing-sd-invoices-in-sap-dms.html

https://answers.sap.com/questions/10755973/output-type-document-archiving-is-failing.html

Thanks,

Kaushik