SAP ARCHIVOBJECT_CREATE_FAX_SYNC Function Module for
ARCHIVOBJECT_CREATE_FAX_SYNC is a standard archivobject create fax sync SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for archivobject create fax sync FM, simply by entering the name ARCHIVOBJECT_CREATE_FAX_SYNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: OA05
Program Name: SAPLOA05
Main Program: SAPLOA05
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ARCHIVOBJECT_CREATE_FAX_SYNC pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ARCHIVOBJECT_CREATE_FAX_SYNC'".
EXPORTING
LOGICAL_PATHNAME = "
LOGICAL_FILENAME = "Logical file name
ARCHIV_ID = "Archive
DOCUMENT_TYPE = "
* PAGES = "Number of Pages
* VSCAN_PROFILE = '/SCMS/KPRO_CREATE' "
IMPORTING
ARCHIV_DOC_ID = "Archive Document ID
EXCEPTIONS
ERROR_ARCHIV = 1 ERROR_COMMUNICATIONTABLE = 2 ERROR_KERNEL = 3 ERROR_FILE = 4 BLOCKED_BY_POLICY = 5
IMPORTING Parameters details for ARCHIVOBJECT_CREATE_FAX_SYNC
LOGICAL_PATHNAME -
Data type: SAPB-SAPPFADOptional: No
Call by Reference: No ( called with pass by value option)
LOGICAL_FILENAME - Logical file name
Data type: SAPB-SAPPFADOptional: No
Call by Reference: No ( called with pass by value option)
ARCHIV_ID - Archive
Data type: TOAV0-ARCHIV_IDOptional: No
Call by Reference: No ( called with pass by value option)
DOCUMENT_TYPE -
Data type: TOADD-DOC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
PAGES - Number of Pages
Data type: SOFX-PAGESOptional: Yes
Call by Reference: No ( called with pass by value option)
VSCAN_PROFILE -
Data type: VSCAN_PROFILEDefault: '/SCMS/KPRO_CREATE'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ARCHIVOBJECT_CREATE_FAX_SYNC
ARCHIV_DOC_ID - Archive Document ID
Data type: TOAV0-ARC_DOC_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_ARCHIV - Error from Archive System
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_COMMUNICATIONTABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_KERNEL - Error from SAP Kernel
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_FILE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BLOCKED_BY_POLICY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ARCHIVOBJECT_CREATE_FAX_SYNC Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_error_archiv | TYPE STRING, " | |||
| lv_archiv_doc_id | TYPE TOAV0-ARC_DOC_ID, " | |||
| lv_logical_pathname | TYPE SAPB-SAPPFAD, " | |||
| lv_logical_filename | TYPE SAPB-SAPPFAD, " | |||
| lv_error_communicationtable | TYPE SAPB, " | |||
| lv_archiv_id | TYPE TOAV0-ARCHIV_ID, " | |||
| lv_error_kernel | TYPE TOAV0, " | |||
| lv_error_file | TYPE TOAV0, " | |||
| lv_document_type | TYPE TOADD-DOC_TYPE, " | |||
| lv_pages | TYPE SOFX-PAGES, " | |||
| lv_blocked_by_policy | TYPE SOFX, " | |||
| lv_vscan_profile | TYPE VSCAN_PROFILE. " '/SCMS/KPRO_CREATE' |
|   CALL FUNCTION 'ARCHIVOBJECT_CREATE_FAX_SYNC' " |
| EXPORTING | ||
| LOGICAL_PATHNAME | = lv_logical_pathname | |
| LOGICAL_FILENAME | = lv_logical_filename | |
| ARCHIV_ID | = lv_archiv_id | |
| DOCUMENT_TYPE | = lv_document_type | |
| PAGES | = lv_pages | |
| VSCAN_PROFILE | = lv_vscan_profile | |
| IMPORTING | ||
| ARCHIV_DOC_ID | = lv_archiv_doc_id | |
| EXCEPTIONS | ||
| ERROR_ARCHIV = 1 | ||
| ERROR_COMMUNICATIONTABLE = 2 | ||
| ERROR_KERNEL = 3 | ||
| ERROR_FILE = 4 | ||
| BLOCKED_BY_POLICY = 5 | ||
| . " ARCHIVOBJECT_CREATE_FAX_SYNC | ||
ABAP code using 7.40 inline data declarations to call FM ARCHIVOBJECT_CREATE_FAX_SYNC
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single ARC_DOC_ID FROM TOAV0 INTO @DATA(ld_archiv_doc_id). | ||||
| "SELECT single SAPPFAD FROM SAPB INTO @DATA(ld_logical_pathname). | ||||
| "SELECT single SAPPFAD FROM SAPB INTO @DATA(ld_logical_filename). | ||||
| "SELECT single ARCHIV_ID FROM TOAV0 INTO @DATA(ld_archiv_id). | ||||
| "SELECT single DOC_TYPE FROM TOADD INTO @DATA(ld_document_type). | ||||
| "SELECT single PAGES FROM SOFX INTO @DATA(ld_pages). | ||||
| DATA(ld_vscan_profile) | = '/SCMS/KPRO_CREATE'. | |||
Search for further information about these or an SAP related objects