Output type - Special function 8 - ARCHIV_CONNECTION_INSERT

Question

Hi gurus,
I created a new Output Type with special function 8 called ZPDF in transaction NACE with application MR (invoice verification) and I added to that Output Type ZPDF our custom program called ZXXX_ARCHIVE_LINK in order to post into the MM invoice, a PDF who cames from the SD inovoice.
The SD invoice number is recorder into the field "Referece" in the MM invoice.
So, the program should (through the output type and the program):
1. Read the MM invoice number generated (NAST table into NAST-OBJKY).
2. Enter to table RBKP with MM invoice number RBKP-BELNR and get the SD invoice number: RBKP-XBLNR.
3. Enter with SD invoice number XBLNR to table TOA01-OBJECT_ID And get TOA01-ARC_DOC_ID.
4. Call FM ARCHIV_CONNECTION_INSERT.
The problem here is when I post a MM inovice in MIRO transaction the system through the condition record added the ZPDF Output Type but don´t read the program ZMIC_INVOICE_PDF_ARCHIVE_LINK added to that output type. The status of the output type is green (but without any processing log). I checked the setting for the Output Type like 100 times and everything seems to be OK.
Please this is very urgent. Any advice?
I don´t know why SAP don´t call the program. I think the ABAP code is wrong:
REPORT ZXXX_ARCHIVE_LINK.
Table Declaration
TABLES: NAST, " Message Status
CMFP, " Storage Structure for Errors Collected
EDIDS, " Status Record (IDoc)
VBRK, " Billing Document: Header Data
TOA01. " Link table 1
TYPES: BEGIN OF TY_RBKP,
BELNR TYPE RE_BELNR, " Document number of an invoice document
XBLNR TYPE XBLNR1, "SAEOBJID, " Reference Document Number
END OF TY_RBKP.
TYPES: BEGIN OF TY_TOA01,
OBJECT_ID TYPE SAEOBJID, " SAP ArchiveLink: Object ID (object identifier)
ARC_DOC_ID TYPE SAEARDOID, " SAP ArchiveLink: Document ID
END OF TY_TOA01.
Data Declaration
DATA: WA_BELNR TYPE RE_BELNR ,
WA_ARC_DOC_ID TYPE TY_TOA01 , "-ARC_DOC_ID,
WA_SAP_OBJECT LIKE SAPB-SAPOBJID," TYPE TOAOM-SAP_OBJECT ,
ARC_DOC_ID TYPE TOAV0-ARC_DOC_ID,
GT_RBKP TYPE STANDARD TABLE OF TY_RBKP , "WITH HEADER LINE,
GT1_RBKP TYPE STANDARD TABLE OF TY_RBKP, " WITH HEADER LINE,
GT_ARC_DOC_ID TYPE STANDARD TABLE OF TY_TOA01, " -ARC_DOC_ID,
WA1_RBKP TYPE TY_RBKP ,
WA_RBKP TYPE TY_RBKP.
DATA: WA1_OBJECT_ID TYPE SAEOBJID.
DATA: WA_OBJKY TYPE NA_OBJKEY,
WA1_OBJKY TYPE RE_BELNR.
FORM entry USING ent_retco ent_screen.
CLEAR ent_retco.
PERFORM ARCHIV_CONNECTION_INSERT USING nast-objky ent_retco.
ENDFORM. "entry
FORM ARCHIV_CONNECTION_INSERT USING objky returncode.
* Select Reference Document Number from RBKP table
SELECT BELNR XBLNR
FROM RBKP
INTO TABLE GT_RBKP
WHERE BELNR = objky . " .WA1_OBJKY .
IF SY-SUBRC EQ 0 .
LOOP AT GT_RBKP INTO WA_RBKP.
WA1_OBJECT_ID = WA_RBKP-XBLNR .
CONCATENATE WA1_OBJECT_ID '%' INTO WA1_OBJECT_ID .
WA_SAP_OBJECT = WA_RBKP-BELNR .
SELECT OBJECT_ID
ARC_DOC_ID
FROM TOA01
INTO TABLE GT_ARC_DOC_ID
WHERE OBJECT_ID LIKE WA1_OBJECT_ID.
IF SY-SUBRC EQ 0 .
READ TABLE GT_ARC_DOC_ID INTO WA_ARC_DOC_ID INDEX 1.
ARC_DOC_ID = WA_ARC_DOC_ID-ARC_DOC_ID.
WA_SAP_OBJECT = WA_ARC_DOC_ID-OBJECT_ID.
ENDIF.
CALL Function Module:Link table operations
CALL FUNCTION 'ARCHIV_CONNECTION_INSERT'
EXPORTING
ARCHIV_ID = 'Z0'
ARC_DOC_ID = ARC_DOC_ID
AR_DATE = SY-DATUM
AR_OBJECT = 'MMILOGINV'
DEL_DATE = ' '
MANDANT = SY-MANDT
OBJECT_ID = WA_SAP_OBJECT
SAP_OBJECT = 'BUS2081'
DOC_TYPE = 'PDF'
BARCODE = ' '
EXCEPTIONS
ERROR_CONNECTIONTABLE = 1
OTHERS = 2
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR: WA_RBKP.
ENDLOOP.
ENDIF.
ENDFORM.

Answer 1

Hi,
Use
You can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00 or a corresponding application function.
The individual possibilites are:
Time 1: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually.
Time 2: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date.
Time 3: The message is selected and processed by application specific programs. Processing can take place online or in the background.
Time 4: The message is processed when the application document is saved. No further processing of the message is necessary.
Kapil