Barcode Exception

When trying to implement the barcode in a jsp through servlet(passing xml and xsl), I'm getting the following exception.. This exception is getting caught when the method generate which will generate the barcode is called from xslt file. Please Help.
java.lang.RuntimeException: Function not supported!
at weblogic.apache.xml.utils.UnImplNode.error(UnImplNode.java:94)
at weblogic.apache.xml.utils.UnImplNode.item(UnImplNode.java:242)
at org.krysalis.barcode4j.xalan.BarcodeExt.generate(BarcodeExt.java:52)

Could you forward the barcoded form throwing the decode error to [email protected]?
Steve

Similar Messages

  • INTERNAL_SERVER_ERROR    while Calling SCMS_HTTP_CREATE Function Module

    Dear All,
    We want to attach document (PDF, DOCX, TXT etc.) in DMS using WD application.
    We converted data xstring to binary format. Now when we call Function Module SCMS_HTTP_CREATE, it gives SY-SUBRC = 5. INTERNAL_SERVER_ERROR.
    Code:
    *"*"Local Interface:
    *"  IMPORTING
    *"     VALUE(IV_ARCHIV_ID) TYPE  TOAOM-ARCHIV_ID
    *"     VALUE(IV_AR_OBJECT) TYPE  TOAOM-AR_OBJECT
    *"     VALUE(IV_OBJECT_ID) TYPE  SAPB-SAPOBJID
    *"     VALUE(IV_SAP_OBJECT) TYPE  TOAOM-SAP_OBJECT
    *"     VALUE(IV_LENGTH) TYPE  I
    *"     VALUE(IV_MIMETYPE) TYPE  STRING
    *"     VALUE(IT_DATA) TYPE  ZTAB
    *"  EXPORTING
    *"     VALUE(EV_FLAG) TYPE  CHAR1
    *"     VALUE(EV_DOC_ID) TYPE  SAEARDOID
    DATA : LV_ARC_DOC TYPE SYSUUID-C,
            LV_MIMETYPE TYPE W3CONTTYPE,
            LV_ARCDOC TYPE TOAV0-ARC_DOC_ID.
    CALL FUNCTION 'SYSTEM_UUID_C_CREATE'
      IMPORTING
        UUID          = LV_ARC_DOC.
    CALL FUNCTION 'SCMS_FE_GROUP_OPEN'.
    LV_MIMETYPE = IV_MIMETYPE.
    CALL FUNCTION 'SCMS_HTTP_CREATE'
       EXPORTING
        MANDT                       = SY-MANDT
         CREP_ID                     = IV_ARCHIV_ID
        DOC_ID                      = LV_ARC_DOC
        COMP_ID                     = 'data'
        MIMETYPE                    = LV_MIMETYPE
         LENGTH                      = IV_LENGTH
    *   SIGNATURE                   = 'X'
    *   DOC_PROT                    = 'rcud'
    *   TEXT_MODE                   = ' '
    *   ACCESSMODE                  = 'c'
    *   SECURITY                    = ' '
    *   OVERWRITE                   = '-'
    * IMPORTING
    *   DOC_ID_OUT                  =
       TABLES
         DATA                        = IT_DATA
      EXCEPTIONS
        BAD_REQUEST                 = 1
        UNAUTHORIZED                = 2
        FORBIDDEN                   = 3
        CONFLICT                    = 4
        INTERNAL_SERVER_ERROR       = 5
        ERROR_HTTP                  = 6
        ERROR_URL                   = 7
        ERROR_SIGNATURE             = 8
        ERROR_PARAMETER             = 9
        OTHERS                      = 10
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION 'SCMS_FE_GROUP_CLOSE'
    LV_ARCDOC = LV_ARC_DOC.
    CALL FUNCTION 'ARCHIV_CONNECTION_INSERT'
       EXPORTING
        ARCHIV_ID                    = IV_ARCHIV_ID
         ARC_DOC_ID                  = LV_ARCDOC
    *   AR_DATE                     = ' '
         AR_OBJECT                   = IV_AR_OBJECT
    *   DEL_DATE                    = ' '
    *   MANDANT                     = ' '
         OBJECT_ID                   = IV_OBJECT_ID
         SAP_OBJECT                  = IV_SAP_OBJECT
    *   DOC_TYPE                    = ' '
    *   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.
    While Calling FM 'SCMS_HTTP_CREATE' is Raise Exception 5 INTERNAL_SERVER_ERROR.
    Thanks
    Regards
    Rohit      

    Hi,
    Content-Type: application/xml
    ...check for the content type of the message that is sent ot the WS.....with the above mentioned content-type going to the WS currently...WS is not able to parse the req and hence the error....in other words wrong format being being passed.
    Regards,
    ABhishek.

  • Output type - Special function 8 - ARCHIV_CONNECTION_INSERT

    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.

    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

  • Problems viewing contents of archived document in archive link

    Good day guys,
    I used the function module ARCHIV_CONNECTION_INSERT to archive a pdf document and I can see that it has been archived in ArchiveLink via T-Code OAAD.
    However, I am unable to view the contents of the file when I click on the link. Can anyone help me on this issue?
    Thanks,
    Bryon

    DATA: l_file_arc     LIKE SAPB-SAPPFAD,
          l_arc_doc_id   LIKE SAPB-SAPADOKID,
          l_sap_obj_id   LIKE sapb-sapobjid,
          l_sap_obj_type LIKE toaom-sap_object,
          l_doc_type     LIKE TOADD-DOC_TYPE,
          l_arc_id       LIKE TOAAR-ARCHIV_ID.
    CHECK sy-mandt = '120'.
    BREAK TZZBLUOX.
    *l_file_arc = '/tmp/file.pdf'.   "Change the file path here
    l_file_arc = 'c:\file.pdf'.
    l_doc_type = 'PDF'.
    l_arc_id   = 'ZT'.
    store the uploaded file on the IXOS-archive:
    CALL FUNCTION 'ARCHIVOBJECT_CREATE_FILE'
      EXPORTING
        ARCHIV_ID                = l_arc_id
        DOCUMENT_TYPE            = l_doc_type
        PATH                     = l_file_arc
      IMPORTING
        ARCHIV_DOC_ID            = l_arc_doc_id
      EXCEPTIONS
        ERROR_ARCHIV             = 1
        ERROR_COMMUNICATIONTABLE = 2
        ERROR_UPLOAD             = 3
        ERROR_KERNEL             = 4
        OTHERS                   = 5.
    If sy-subrc = 0.
      BREAK TZZBLUOX.
      l_sap_obj_id   = '000000000013'.    "Contact log number
      l_sap_obj_type = 'BCONTACT'.
    link the archived document to the business object ‘BCONTACT':
      CALL FUNCTION 'ARCHIV_CONNECTION_INSERT'
        EXPORTING
          ARCHIV_ID                   = l_arc_id
          ARC_DOC_ID                  = l_arc_doc_id
        AR_DATE                     = ' '
          AR_OBJECT                   = 'ZSTDLTR'
        DEL_DATE                    = ' '
        MANDANT                     = ' '
          OBJECT_ID                   = l_sap_obj_id
          SAP_OBJECT                  = l_sap_obj_type
          DOC_TYPE                    = l_doc_type
        BARCODE                     = ' '
        EXCEPTIONS
          ERROR_CONNECTIONTABLE       = 1
          OTHERS                      = 2.
      BREAK TZZBLUOX.
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    Else.
      BREAK TZZBLUOX.
    EndIf.

  • Employee Photo Upload through binary data

    Hi all,
    I know the Provision for Photo upload through OAAD Tcode, I know FM to upload the photos by giving path as input data. my requirement is I have picture in the form of binary data . i want to upload that into PA30. I have return the following code. No Error but image is not displayed in PA30.Can u Please correct me?
    tables: toav0, toaom, twfdb, toapa.
    data: key like ojint-key,
          object like ojint-name,
          object_id like toav0-object_id,
          archiv_id like toav0-archiv_id,
          arc_doc_id like toav0-arc_doc_id,
          ablagedatum like sapb-sapabldate,
          ar_date like toav0-ar_date,
          del_date like toav0-del_date,
          sap_object like toaom-sap_object,
          ar_object like toaom-ar_object,
          expiry_tim like toaom-expiry_tim,
          method like ojint-method,
          return like ojint-return,
          parameter like ojint-parameter.
    data:begin of i_toav0 occurs 1.
            include structure toav0.
    data: end of i_toav0.
    data: begin of i_toaom occurs 1.
            include structure toaom.
    data: end of i_toaom.
    data: begin of fields occurs 1.
            include structure ojfields.
    data: end of fields.
    DATA:     filename1  TYPE string.
    Data: i_name TYPE STXBITMAPS-TDNAME value 'TEST',
    *  archiv_id like toav0-archiv_id,
    i_id TYPE STXBITMAPS-TDID VALUE 'BMAP',
    i_btype TYPE STXBITMAPS-TDBTYPE VALUE 'BCOL',
    l_bds_bytecnt TYPE i,
    FLENGTH TYPE SAPB-LENGTH,
    l_bds_content TYPE TABLE OF bapiconten,
    OUTDOC     LIKE     TOADT ,
    wa_l_bds_content TYPE  bapiconten.
    *DATA : BINARY TYPE STANDARD TABLE OF TBL1024,
    data : BINARY TYPE STANDARD TABLE OF TBL1024 WITH HEADER LINE,
    ARCHIVOBJECT type standard table of docs,
    archiv_doc_id like toav0-arc_doc_id,
    wa_binary type TBL1024.
    data:  lw_ar_object like toaom-ar_object,
          lw_object_id like sapb-sapobjid,
          lw_sap_object like toaom-sap_object,
          lw_doc_type like toadd-doc_type,
          lw_path like sapb-sappfad,"toav0-arc_doc_id
    *      archiv_doc_id like toav0-arc_doc_id,
          doc_type like toadt-doc_class.
    constants:  c_sap_object type toaom-sap_object value 'PREL',
                c_ar_object type toaom-ar_object value 'HRICOLFOTO',
                c_doc_type type toaom-doc_type value 'JPG'.
    PARAMETERS: filename(150) TYPE c OBLIGATORY.                               "Name of the File where source as  txt format
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR filename.
      PERFORM getfile.
    start-of-selection.
      filename1 = filename.
    key = '010001380002'.
      lw_ar_object = c_ar_object.
    *  lw_object_id = w_pernr_pass.
      lw_sap_object = c_sap_object.
      lw_doc_type = c_doc_type.
    *  lw_path = it_data-file_nam.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename = filename1
          filetype = 'BIN'
        TABLES
          data_tab = archivobject.
    * Object to be archived
          select single * from toaom where ar_object = c_ar_object and sap_object = c_sap_object.
          if sy-subrc <> 0.
            raise UPLOAD_ERROR.
          else.
    * Authority check with Archive id
            archiv_id = toaom-archiv_id.
            perform authority_check_create(oaall)
            using archiv_id object space ar_object space
            changing sy-subrc.
            if sy-subrc ne 0.
              raise UPLOAD_ERROR.
            else.
              if sy-subrc <> 0.
                raise UPLOAD_ERROR.
                clear toav0.
              else." Transfer key for archiving
                toav0-object_id = key.
                if key eq space.
                  Raise FUNCTION_ERROR.
                  clear toav0.
                else.
                  perform create_archive_object_new  .
                endif.
              endif.
            endif.
          endif.
    form create_archive_object_new .
    CALL FUNCTION 'ARCHIV_CREATE_TABLE'
        EXPORTING
          AR_OBJECT                      = lw_ar_object
    *   DEL_DATE                       =
          OBJECT_ID                      = '010001380002'
          SAP_OBJECT                     =  lw_sap_object
    *   FLENGTH                        = '2328'
       DOC_TYPE                       = lw_doc_type
    *   DOCUMENT                       =
    *   MANDT                          = SY-MANDT
    * IMPORTING
    *   OUTDOC                         =
       TABLES
       ARCHIVOBJECT                   =  ARCHIVOBJECT
    *     BINARCHIVOBJECT                = binary
    * EXCEPTIONS
    *   ERROR_ARCHIV                   = 1
    *   ERROR_COMMUNICATIONTABLE       = 2
    *   ERROR_CONNECTIONTABLE          = 3
    *   ERROR_KERNEL                   = 4
    *   ERROR_PARAMETER                = 5
    *   ERROR_USER_EXIT                = 6
    *   ERROR_MANDANT                  = 7
    *   OTHERS                         = 8
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      call function 'ARCHIVOBJECT_CREATE_TABLE'
        EXPORTING
          archiv_id                = archiv_id
          document_type            = lw_doc_type
    *      length                   = '2328'
        IMPORTING
          archiv_doc_id            = i_toav0-arc_doc_id
        TABLES
          archivobject             = archivobject
    *      binarchivobject          = BINARY
        EXCEPTIONS
          error_kernel             = 1
          error_communicationtable = 2
          error_archiv             = 3.
           move i_toav0 to toav0.
        toav0-sap_object = lw_sap_object.
        toav0-object_id = key.
        move archiv_id to toav0-archiv_id.
        move i_toav0-arc_doc_id to toav0-arc_doc_id.
        toav0-ar_object = lw_ar_object.
        move lw_doc_type to toav0-reserve.
        move lw_doc_type to doc_type.
        commit work.
      call function 'ARCHIV_CONNECTION_INSERT'
          exporting
            archiv_id                   = toav0-archiv_id
            arc_doc_id                  = toav0-arc_doc_id
            ar_date                     = ar_date
            ar_object                   = toav0-ar_object
    *     DEL_DATE                    = ' '
    *     MANDANT                     = ' '
            object_id                   = '010001380002'
            sap_object                  = toav0-sap_object
            doc_type                    = doc_type
    *        barcode                     = barcode
          exceptions
            error_connectiontable       = 1
            others                      = 2
    endform.
    FORM getfile .
      CALL FUNCTION 'WS_FILENAME_GET'
        EXPORTING
          def_filename     = ' '
          def_path         = '*.*'
          mask             = ''
          mode             = 'O'
          title            = ' SELECTING FILE FOR SOURCE PROGRAM'
        IMPORTING
          filename         = filename
        EXCEPTIONS
          selection_cancel = 3
          selection_error  = 4.

    Hi all,
    I know the Provision for Photo upload through OAAD Tcode, I know FM to upload the photos by giving path as input data. my requirement is I have picture in the form of binary data . i want to upload that into PA30. I have return the following code. No Error but image is not displayed in PA30.Can u Please correct me?
    tables: toav0, toaom, twfdb, toapa.
    data: key like ojint-key,
          object like ojint-name,
          object_id like toav0-object_id,
          archiv_id like toav0-archiv_id,
          arc_doc_id like toav0-arc_doc_id,
          ablagedatum like sapb-sapabldate,
          ar_date like toav0-ar_date,
          del_date like toav0-del_date,
          sap_object like toaom-sap_object,
          ar_object like toaom-ar_object,
          expiry_tim like toaom-expiry_tim,
          method like ojint-method,
          return like ojint-return,
          parameter like ojint-parameter.
    data:begin of i_toav0 occurs 1.
            include structure toav0.
    data: end of i_toav0.
    data: begin of i_toaom occurs 1.
            include structure toaom.
    data: end of i_toaom.
    data: begin of fields occurs 1.
            include structure ojfields.
    data: end of fields.
    DATA:     filename1  TYPE string.
    Data: i_name TYPE STXBITMAPS-TDNAME value 'TEST',
    *  archiv_id like toav0-archiv_id,
    i_id TYPE STXBITMAPS-TDID VALUE 'BMAP',
    i_btype TYPE STXBITMAPS-TDBTYPE VALUE 'BCOL',
    l_bds_bytecnt TYPE i,
    FLENGTH TYPE SAPB-LENGTH,
    l_bds_content TYPE TABLE OF bapiconten,
    OUTDOC     LIKE     TOADT ,
    wa_l_bds_content TYPE  bapiconten.
    *DATA : BINARY TYPE STANDARD TABLE OF TBL1024,
    data : BINARY TYPE STANDARD TABLE OF TBL1024 WITH HEADER LINE,
    ARCHIVOBJECT type standard table of docs,
    archiv_doc_id like toav0-arc_doc_id,
    wa_binary type TBL1024.
    data:  lw_ar_object like toaom-ar_object,
          lw_object_id like sapb-sapobjid,
          lw_sap_object like toaom-sap_object,
          lw_doc_type like toadd-doc_type,
          lw_path like sapb-sappfad,"toav0-arc_doc_id
    *      archiv_doc_id like toav0-arc_doc_id,
          doc_type like toadt-doc_class.
    constants:  c_sap_object type toaom-sap_object value 'PREL',
                c_ar_object type toaom-ar_object value 'HRICOLFOTO',
                c_doc_type type toaom-doc_type value 'JPG'.
    PARAMETERS: filename(150) TYPE c OBLIGATORY.                               "Name of the File where source as  txt format
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR filename.
      PERFORM getfile.
    start-of-selection.
      filename1 = filename.
    key = '010001380002'.
      lw_ar_object = c_ar_object.
    *  lw_object_id = w_pernr_pass.
      lw_sap_object = c_sap_object.
      lw_doc_type = c_doc_type.
    *  lw_path = it_data-file_nam.
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename = filename1
          filetype = 'BIN'
        TABLES
          data_tab = archivobject.
    * Object to be archived
          select single * from toaom where ar_object = c_ar_object and sap_object = c_sap_object.
          if sy-subrc <> 0.
            raise UPLOAD_ERROR.
          else.
    * Authority check with Archive id
            archiv_id = toaom-archiv_id.
            perform authority_check_create(oaall)
            using archiv_id object space ar_object space
            changing sy-subrc.
            if sy-subrc ne 0.
              raise UPLOAD_ERROR.
            else.
              if sy-subrc <> 0.
                raise UPLOAD_ERROR.
                clear toav0.
              else." Transfer key for archiving
                toav0-object_id = key.
                if key eq space.
                  Raise FUNCTION_ERROR.
                  clear toav0.
                else.
                  perform create_archive_object_new  .
                endif.
              endif.
            endif.
          endif.
    form create_archive_object_new .
    CALL FUNCTION 'ARCHIV_CREATE_TABLE'
        EXPORTING
          AR_OBJECT                      = lw_ar_object
    *   DEL_DATE                       =
          OBJECT_ID                      = '010001380002'
          SAP_OBJECT                     =  lw_sap_object
    *   FLENGTH                        = '2328'
       DOC_TYPE                       = lw_doc_type
    *   DOCUMENT                       =
    *   MANDT                          = SY-MANDT
    * IMPORTING
    *   OUTDOC                         =
       TABLES
       ARCHIVOBJECT                   =  ARCHIVOBJECT
    *     BINARCHIVOBJECT                = binary
    * EXCEPTIONS
    *   ERROR_ARCHIV                   = 1
    *   ERROR_COMMUNICATIONTABLE       = 2
    *   ERROR_CONNECTIONTABLE          = 3
    *   ERROR_KERNEL                   = 4
    *   ERROR_PARAMETER                = 5
    *   ERROR_USER_EXIT                = 6
    *   ERROR_MANDANT                  = 7
    *   OTHERS                         = 8
      IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      call function 'ARCHIVOBJECT_CREATE_TABLE'
        EXPORTING
          archiv_id                = archiv_id
          document_type            = lw_doc_type
    *      length                   = '2328'
        IMPORTING
          archiv_doc_id            = i_toav0-arc_doc_id
        TABLES
          archivobject             = archivobject
    *      binarchivobject          = BINARY
        EXCEPTIONS
          error_kernel             = 1
          error_communicationtable = 2
          error_archiv             = 3.
           move i_toav0 to toav0.
        toav0-sap_object = lw_sap_object.
        toav0-object_id = key.
        move archiv_id to toav0-archiv_id.
        move i_toav0-arc_doc_id to toav0-arc_doc_id.
        toav0-ar_object = lw_ar_object.
        move lw_doc_type to toav0-reserve.
        move lw_doc_type to doc_type.
        commit work.
      call function 'ARCHIV_CONNECTION_INSERT'
          exporting
            archiv_id                   = toav0-archiv_id
            arc_doc_id                  = toav0-arc_doc_id
            ar_date                     = ar_date
            ar_object                   = toav0-ar_object
    *     DEL_DATE                    = ' '
    *     MANDANT                     = ' '
            object_id                   = '010001380002'
            sap_object                  = toav0-sap_object
            doc_type                    = doc_type
    *        barcode                     = barcode
          exceptions
            error_connectiontable       = 1
            others                      = 2
    endform.
    FORM getfile .
      CALL FUNCTION 'WS_FILENAME_GET'
        EXPORTING
          def_filename     = ' '
          def_path         = '*.*'
          mask             = ''
          mode             = 'O'
          title            = ' SELECTING FILE FOR SOURCE PROGRAM'
        IMPORTING
          filename         = filename
        EXCEPTIONS
          selection_cancel = 3
          selection_error  = 4.

  • Special function 8 - Output Type

    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.
    <removed by moderator>. 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.
    Edited by: Thomas Zloch on Oct 26, 2011 10:52 AM

    ok, if you set for your output type NAST-VSZTP=3 you can add code in your print program to display popup window in which
    user specify own path for storing PDF...
    but if output type will be created in background ( VSZTP ne 3) then
    you must save PDF in server path...and user may download it by
    cg3y...
    regards, darek

  • Call function maximum print.

    Hi all.
    I have print proble. if  sombody  know that , please let me know.
    if  the  number of itab is  '400',  when 300 times print is not printing.  logic like below.
    loop at itab.
    call function 'OPEN_FORM'
        exporting
          device  = 'PRINTER'
          dialog  = ' '
          form    = 'Z_CPS_OUTBOX'
          options = option
        exceptions
          others  = 9.
      if sy-subrc <> 0.
        exit.
      endif.
      call function 'WRITE_FORM'
        exporting
          element  = l_element
          function = 'SET'
          type     = 'BODY'
          window   = 'MAIN'
        exceptions
          others   = 8.
      call function 'WRITE_FORM'
        exporting
          element  = l_element
          function = 'SET'
          type     = 'BODY'
          window   = 'BARCODE'
        exceptions
          others   = 8.
      call function 'CLOSE_FORM'
        exceptions
          others = 4.
      if sy-subrc <> 0.
        exit.
      endif.
    endloop.

    can u jot down ur exact requirement..
    why r u opening and closing the form inside the loop?
    u could have done this:
    openform...
    loop at itab.
    writeform...
    endloop.
    closeform...

  • Handling exceptions for barcode:

    Hi,
       How can I handle the exceptions for a barcode process? suppose I have a tiff document with 4 pages and 4 barcodes, and if one of them was failed in decoding, my whole process is running into exception. I want to handle that failed barcode alone and send a message to the output variable that the particualr barcode is failed.
      I tried using events with default exception handling. I dont know how to configure it and catch the runtime exception. I tried searching in the internet to get some configuration samples for that. I checked the sample from Tour de livecycle. Even that didnt guide me how to configure those exceptions.
    Chaitanya

    Can someone help me out on this..
    Thanks

  • I cannot remove embedded barcode from the image. Due to saving compression.

    Hi guys,
    I recreate a thread to prevent confusing on my previous one. Please only reply to this thread thanks.
    Ok, for a start I will give some general description about the application I made.
    I had some problem with the image being compressed while it is saved.
    Because saving an image will cause it to compress and had its pixel valued changed, I could not successfully remove the bardcode that is embedded inside a image(although some of the pixel value will be returned to original normally). I had placed my code below and will accept any opinion that will help me solve the removal of barcode problem.
    What my application does is actually very simple. It will take the pixel value of the area inside the image that will be embed with the barcode first, then it will take the pixel value of the barcode and use the formula (1-alpha * Image pixel value) + (alpha * barcode pixel value) = new pixel value which will contain the barcode that had been embedded inside. The formula works great but when I saved the image the pixel value will change due to compression. On the removal of barcode my application will read every pixel value from the image embedded with barcode (only the area with barcode embedded), then it will go on to read every pixel value of the barcode used for embedding and then use the formula (Embedded image pixel value - (alpha * Barcode pixel value) - (1 - alpha) = original pixel value. But due to the reason that compression will change some of the pixel inside the saved image to drop in its value, the result from the removal formula will be negative and hence caused my result image to become wierd as it will red colors instead of original color on some of its pixel. I tried saving under PNG format which people said to be lossless compression but the result is still the same.
    So I need to ask you guys for opinion or help me find the part where I actually did wrongly and caused the image pixel value to change.
    Thanks. Please proceed and read below for the codes that I used. It is messy and I will sort it out later.
    When alpha is set as 1 the barcode will appear to be overwrite onto the image. But when alpha is set as 0.1 the barcode will appear to be transparent and almost seems to be not there on the image when embedded.
    This is the code I used to retrieve image pixel when embedding:
    public static int[] getImagePixelValue(BufferedImage image, int x, int y){
              //Create an array to store image RGB value
              int[] imageRGB = new int[3];
              //Get height and width from input image
              int imageWidth = image.getWidth();
              int imageHeight = image.getHeight();
              //Get raw RGB value from image
              int imageValue = image.getRGB(x, y);
              //Convert image raw RGB value
              int imageRed = ((image.getRGB(x, y) >> 16) & 0xff);
              int imageGreen = ((image.getRGB(x, y) >> 8) & 0xff);
              int imageBlue = image.getRGB(x, y) & 0xff;
              //Input the converted RGB value into the array
              imageRGB[0] = imageRed;
              imageRGB[1] = imageGreen;
              imageRGB[2] = imageBlue;
              /*//Print out the pixel value to check
              System.out.println("Image red pixel: "+imageRGB[0]);
              System.out.println("Image green pixel: "+imageRGB[1]);
              System.out.println("Image blue pixel: "+imageRGB[2]);*/
              //Return image RGB value
              return imageRGB;
    }This is the code I used to retrieve barcode pixel for embedding:
    public static int[] getWatermarkPixelValue(BufferedImage watermark, int x, int y){
              //Create an array to store watermark RGB value
              int[] watermarkRGB = new int[3];
              //Get height and width from input watermark
              int watermarkWidth = watermark.getWidth();
              int watermarkHeight = watermark.getHeight();
              int watermarkValue = watermark.getRGB(x, y);
              //Convert watermark raw RGB value
              int watermarkRed = ((watermark.getRGB(x, y) >> 16) & 0xff);
              int watermarkGreen = ((watermark.getRGB(x, y) >> 8) & 0xff);
              int watermarkBlue = watermark.getRGB(x, y) & 0xff;
              //Input the converted RGB value into the array
              watermarkRGB[0] = watermarkRed;
              watermarkRGB[1] = watermarkGreen;
              watermarkRGB[2] = watermarkBlue;
              /*//Print out the pixel value to check
              System.out.println("Watermark red pixel: "+watermarkRGB[0]);
              System.out.println("Watermark green pixel: "+watermarkRGB[1]);
              System.out.println("Watermark blue pixel: "+watermarkRGB[2]);*/
              //Return watermark RGB value
              return watermarkRGB;
         }This is the code I used for merging the image pixel and barcode pixel to get the embedded pixel value:
    public static int[] getEmbeddedPixelValue(int[] imagePixelValue, int[] watermarkPixelValue, double alpha){
              //Create a object to hold embedded pixel value
              int[] embeddedRGBValue = new int[3];
              //Change image pixel value into double calculating equation
              double imgRedValue = (double) imagePixelValue[0];
              double imgGreenValue = (double) imagePixelValue[1];
              double imgBlueValue = (double) imagePixelValue[2];
              //Change watermark pixel value into double calculating equation
              double wmRedValue = (double) watermarkPixelValue[0];
              double wmGreenValue = (double) watermarkPixelValue[1];
              double wmBlueValue = (double) watermarkPixelValue[2];
              //Equation for embedding image and watermark together
              double embeddedRed = ((1.0 - alpha) * imgRedValue) + (alpha * wmRedValue);
              double embeddedGreen = ((1.0 - alpha) * imgGreenValue) + (alpha * wmGreenValue);
              double embeddedBlue = ((1.0 - alpha) * imgBlueValue) + (alpha * wmBlueValue);
              //Changing embedded value from double to int
              int embeddedRedValue = (int) embeddedRed;
              int embeddedGreenValue = (int) embeddedGreen;
              int embeddedBlueValue = (int) embeddedBlue;
              //input the embedded RGB value into the array
              embeddedRGBValue[0] = embeddedRedValue;
              embeddedRGBValue[1] = embeddedGreenValue;
              embeddedRGBValue[2] = embeddedBlueValue;
              //Return embedded pixel value
              return embeddedRGBValue;
         }This is the code where I used for the embedding process:
    else if(target == embedButton){
                   String xCoordinate = JOptionPane.showInputDialog(embedButton, "Enter coordinate X", "When you want to embed the watermark?", JOptionPane.QUESTION_MESSAGE);
                   String yCoordinate = JOptionPane.showInputDialog(embedButton, "Enter coordinate Y", "When you want to embed the watermark?", JOptionPane.QUESTION_MESSAGE);
                   int xValue = Integer.parseInt(xCoordinate);
                   int yValue = Integer.parseInt(yCoordinate);
                   int wCounter = 0;
                   int hCounter = 0;
                   //Create file object to be used in embedding and removing watermark
                   File inputImage = new File(imagePath);
                   File inputWatermark = new File(watermarkPath);
                   //Convert string into double for calculation of embedded pixel value
                   try {
                        alphaDouble = Double.valueOf(alphaValue).doubleValue();
                   catch (NumberFormatException nfe) {
                        System.out.println("NumberFormatException: " + nfe.getMessage());
                   try{
                        //Define selected image as testPic and make java read the file selected
                        BufferedImage image= ImageIO.read(inputImage);
                        BufferedImage watermark= ImageIO.read(inputWatermark);
                        BufferedImage testing;
                        //Get height and width value from the selected image
                        int imageWidth = image.getWidth();
                        int imageHeight = image.getHeight();
                        //Get height and width value from the selected barcode
                        int watermarkWidth = watermark.getWidth();
                        int watermarkHeight = watermark.getHeight();
                        int totalWidth = watermarkWidth + xValue;
                        int totalHeight = watermarkHeight + yValue;
                        //Use nested for loop to get RGB value from every pixel that the barcode will be embedded in the selected image
                        if(totalWidth <= imageWidth && totalHeight <= imageHeight){
                             for (int h = yValue ; h < totalHeight; h++){
                                  for (int w = xValue; w < totalWidth; w++){
                                       int[] imagePixelValue = getImagePixelValue(image, w, h);
                                       int[] watermarkPixelValue = getWatermarkPixelValue(watermark, wCounter, hCounter);
                                       int[] embeddedPixelRGBValue = getEmbeddedPixelValue(imagePixelValue, watermarkPixelValue, alphaDouble);
                                       setRed(image, w, h, embeddedPixelRGBValue[0]);
                                       setGreen(image, w, h, embeddedPixelRGBValue[1]);
                                       setBlue(image, w, h, embeddedPixelRGBValue[2]);
                                       wCounter++;
                                       if(wCounter == watermarkWidth){
                                            wCounter = 0;
                                            hCounter++;
                        else{
                             JOptionPane.showMessageDialog(embedButton, "The watermark cannot be embedded at the coordinates.");
                        tempImage = image;
                        imageIcon = new ImageIcon(tempImage);
                        labelImage.setIcon(imageIcon);
                        imagePanel.add(labelImage);
                        container.add(imagePanel, BorderLayout.CENTER);
                        setVisible(true);
                        System.out.println("Embedding completed");
                   catch(Exception errorEmbedding){
                        //If there is any error, the try and catch function will tell you the error
                        System.out.println("The following error occured: "+errorEmbedding);
              }This is the code I use to save the image that had been embedded with the barcode:
    else if(target == saveAction){
                   JFileChooser chooser = new JFileChooser();
                   FileNameExtensionFilter filter = new FileNameExtensionFilter("JPG & GIF Images", "jpg", "gif");
                   chooser.setFileFilter(filter);
                   chooser.setCurrentDirectory(new File("."));
                   int returnVal = chooser.showSaveDialog(getParent());
                   if(returnVal == JFileChooser.APPROVE_OPTION) {
                        String name = chooser.getSelectedFile().getAbsolutePath();
                        //Create a string instant to hold outputImage path name
                        String saveFile = chooser.getSelectedFile().getName()+"."+fileType;
                        //Create file output to decide what name will be used to save the file
                        File outputImage = new File(saveFile);
                        try{
                             //Save the file with the name used
                             ImageIO.write((RenderedImage) tempImage,fileType,outputImage);
                        catch(Exception errorSaving){
                             //If there is any error, the try and catch function will tell you the error
                             System.out.println("The following error occured: "+errorSaving);
                   else{
              }This is the code I used for removal process of barcode:
    else if(target == removeButton){
                   //Create file object to be used in embedding and removing watermark
                   File inputImage = new File("removalTesting.jpg");
                   //File inputWatermark = new File(watermarkPath);
                   //Used a defined barcode for testing of removing barcode from embedded image
                   File inputWatermark = new File("barcode.jpg");
                   /*//Convert string into double for calculation of embedded pixel value
                   try {
                        alphaDouble = Double.valueOf(alphaValue).doubleValue();
                   catch (NumberFormatException nfe) {
                        System.out.println("NumberFormatException: " + nfe.getMessage());
                   //Used a defined alpha value for testing of removing barcode from embedded image
                   //alphaDouble = 0.5;
                   //Create x and y value for the starting coordinates of barcode embedded in the embedded image
                   int xValue = 0;
                   int yValue = 0;
                   int wCounter = 0;
                   int hCounter = 0;
                   try{
                        //Define selected image as testPic and make java read the file selected
                        BufferedImage image= ImageIO.read(inputImage);
                        BufferedImage watermark= ImageIO.read(inputWatermark);
                        //Get height and width value from the selected image
                        int imageWidth = image.getWidth();
                        int imageHeight = image.getHeight();
                        //Get height and width value from the selected barcode
                        int watermarkWidth = watermark.getWidth();
                        int watermarkHeight = watermark.getHeight();
                        int totalWidth = watermarkWidth + xValue;
                        int totalHeight = watermarkHeight + yValue;
                        //Use nested for loop to get RGB value from every pixel that the barcode had been embedded in the embedded image
                        if(totalWidth <= imageWidth && totalHeight <= imageHeight){
                             for (int h = yValue ; h < totalHeight; h++){
                                  for (int w = xValue; w < totalWidth; w++){
                                       int[] imagePixelValue = getImagePixelValue(image, w, h);
                                       int[] watermarkPixelValue = getWatermarkPixelValue(watermark, wCounter, hCounter);
                                       int[] removedPixelRGBValue = getOriginalImagePixelValue(imagePixelValue, watermarkPixelValue, alphaDouble);
                                       setRed(image, w, h, removedPixelRGBValue[0]);
                                       setGreen(image, w, h, removedPixelRGBValue[1]);
                                       setBlue(image, w, h, removedPixelRGBValue[2]);
                                       wCounter++;
                                       if(wCounter == watermarkWidth){
                                            wCounter = 0;
                                            hCounter++;
                        tempImage = image;
                        imageIcon = new ImageIcon(tempImage);
                        labelImage.setIcon(imageIcon);
                        imagePanel.add(labelImage);
                        container.add(imagePanel, BorderLayout.CENTER);
                        setVisible(true);
                        System.out.println("Embedding completed");
                   catch(Exception errorEmbedding){
                        //If there is any error, the try and catch function will tell you the error
                        System.out.println("The following error occured: "+errorEmbedding);
              }Sorry if the codes are in a mess, I did not had the time to sort it out yet but most likely do it when I got the removal of barcode done.
    Follow this link to have a look of the result I see in my application when I got the barcode embedded into the image I selected:
    [http://img356.imageshack.us/my.php?image=beforeremovalresultmg2.jpg]
    Follow this link to have a look of the result I see in my application after I got the barcode removed:
    [http://img523.imageshack.us/my.php?image=removalresultmx4.jpg]
    As you can see from the link, after I remove the barcode from the image. Some of the pixel actually went back to normal in the barcode area when the the barcode is embedded into the image. But some pixel in the barcode area had its value changed due to compression when I save the image file I think.
    Anyone can help me find out the problem?
    Thanks.

    KamenRider wrote:
    I suspect the problem lies in the code when I save the image. Because people said that PNG was loseless compression but when I saved in PNG some of the pixel went back to normal while some did not. This is obviously the cause from changing of pixel value when I saved the image.You are almost certainly wrong. This is trivially easy to check. Print out the color of a certain pixel immediately before you save it. Open the saved PNG in your favorite image manipulation program and check the saved value of that same pixel. When you re-load the saved PNG, print out the color again. It should be unchanged.
    Thanks you for trying to help me spot the problem but the formula is correct. The alpha value i used in my application is used to set the transparency of the barcode that will be embedded in the image. Hence, when alpha = 1 the new pixel value should be the barcode value. ^^The formula isn't wrong, it's just not doing what you think it's doing. Remember that you're working with ints here, not floating point numbers, so they have finite precision. When you case from double to int, fractions are dropped. As morgalr pointed out, your formula is:
    (1-alpha * Image pixel value) + (alpha * barcode pixel value) = new pixel value You didn't show us the code for getOriginalImagePixelValue but I imagine it's:
    original pixel value = (new pixel value - alpha * barcode pixel value) / (1 - alpha)On a piece of paper, take alpha = 0.9, image pixel = 17 and barcode pixel = 100. Calculate out what you should get for new pixel value and then calculate what you should get for original pixel value. You will find they don't match.

  • Printing barcodes on 10g server running on Solaris OS

    Hi,
    We are using Reports 10g (10.1.2) on Solaris Operating System (SPARC 32-bit).
    We wanted to print barcodes using Java bean method. It prints fine in windows, but giving below error when run on web using rwservlet. Actually we are using virtual display using xvfb.
    My question is: Do we need to have physical display by setting up another machine like in 6i ?
    Can we achieve the rendering of barcode image using virtual display ?
    What are the setup steps needs to be followed if rendering is possible with out using physical display ??
    Thanks somuch!!!
    The ERROR is:
    REP-108: MSG-00100: < No Exception Message >
    MSG-00100:
    java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:121)
    MSG-00100: java.awt.Window.<init>(Window.java:274)
    MSG-00100: java.awt.Frame.<init>(Frame.java:401)
    MSG-00100: java.awt.Frame.<init>(Frame.java:366)
    MSG-00100: oracle.apps.barcode.BarCodeMaker.renderBarCode(BarCodeMaker.java:84)
    MSG-00100: oracle.reports.engine.EngineImpl.CRunReport(Native Method)
    MSG-00100: oracle.reports.engine.EngineImpl.run(EngineImpl.java:437)
    MSG-00100:
    oracle.reports.engine._EngineClassImplBase._invoke(_EngineClassImplBase.java:90)
    MSG-00100:
    com.sun.corba.se.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:353)
    MSG-00100: com.sun.corba.se.internal.iiop.ORB.process(ORB.java:280)
    MSG-00100:
    com.sun.corba.se.internal.iiop.RequestProcessor.process(RequestProcessor.java:81
    MSG-00100:
    com.sun.corba.se.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:10
    6)
    REP-0108: File '/tmp/srw002114024' not found.

    Thanks Sooooomuch!!!!!!
    we are running Xvfb located at /usr/openwin/bin/
    In particular, we are starting the Xvfb server with the following command:
    nohup Xvfb :1 -screen 0 1600x1200x32 &
    We are then setting the DISPLAY on the command line and in the reports.sh
    script using: DISPLAY=10.25.3.123:0.0; export DISPLAY
    We verify that it recognizes the display using "xset -q"
    In reports.sh file We entered below line:
    ## REPORTS_DEFAULT_DISPLAY=NO; export REPORTS_DEFAULT_DISPLAY
    DISPLAY=10.25.3.123:0.0; export DISPLAY
    But still we are getting java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:121)
    MSG-00100: java.awt.Window.<init>(Window.java:274) Errors.
    Is there anything wrong in the above setup ?
    Please advice.
    Thanks Soomuch,
    Ram.

  • Printing barcode in HP laser jet  through smartform

    Hi folks,
    can i print barcode in HP laser jet P3005 PCL6 by using smartform???
    plz advice.
    regards
    smita

    Yes, you can.. I guess, HP laser jet P3005 series PCL6 can print bar codes.
    I am attaching the list of BARCODE supported printers
    List of device types in SAP Releases 4.6x/6.xx/NW04/NW04s
    OSS NOTE : 8928
    Installation of new device types ********************
    Many device types are appended as a zip-attachment to this note.
    README.TXT contains information about these device types and codepages.
    README_UPLOAD.TXT contains information on how to import the device
    types.
    PRINTER DRIVERS AND DEVICE TYPES:
    In R/3, a distinction is made between "printer driver" and "device type". The device type consists of all the attributes defined for an output device. For correct access, these must be made known in the R/3 system. They cover aspects such as control commands for font selection, page size, character set selection, character set used and so on. One of these attributes is the printer driver to be used by SAPscript (R/3 forms processor) for this particular printer.
    If your printer is not specified in the list below, ask the manufacturer if the printer is compatible with one of the defined printers or if it can be used with another emulation (for example, Postscript).
    If the printer is not compatible or cannot be operated using an emulation, you must create a new device type (if the printer is not compatible). To print from SAPscript, you must choose one of the existing printer drivers.
    At present, there are five SAPscript printer drivers. They include:
    for HP-PCL5 (for example, HP Laserjet 3,4,5,6 series)
    for PostScript printers (PS level 2)
    for PRESCRIBE (for example, Kyocera FS-1500)
    for device types SWIN/SAPWIN/xxSWIN/xxSAPWIN
    for all other models.
    The last driver is known as the "standard driver". It cannot provide absolutely precise positioning on the paper and does not support proportional fonts. Printer drivers are relevant for forms output with SAPscript. For the output of ABAP lists special printer drivers are only used as of Release 4.5A. They are anchored in the C kernel and are developed and maintained exclusively by SAP.
    In the spool environment, device types refer not only to printers but also other output devices, for example, fax machines. Device types support specific printers or printer models. Device type definitions are stored completely in tables and can be individually adapted, modified or enhanced. If SAP performs such an adjustment for a customer, it constitutes a consulting service, and is generally charged seperately. On the other hand, the list of device types, above all in conjunction with SAP's hardware partners, is continually expanded.
    COMPATIBLE PRINTERS:
    Some printer models have been so successful on the market that many OEM products, clones and compatibles are also listed. You can often use compatible printers with R/3 by entering the printer definition of the original. Since complete compatibility is extremely rare, SAP can offer no assurances regarding the usability of compatible printers. This also applies to follow-up models made by the original producer.
    LIST OF PRINTERS:
    This is the list of device types supplied by SAP in different Releases. Most of these device types use "Western European" or "North American" character sets. Some device types in newer Releases however, also support other character sets and language areas such as Russian or Czech.
    The device types named in this list are supported in the standard R/3 System as of the release mentioned.
    If an OCR-A font (prerequisite for check printing) or an OCR-B font is supported in the R/3 device types, this is indicated. However, this generally requires additional font cassettes or firmware for the printer involved, since few printers have an OCR-A font "built in." For additional information about this, contact the printer manufacturer.
    Check related notes attached for addition information on printer supportin R/3.
    Related notes:
    Note 135894 contains information on printing labels on special label printers.
    Note 05196 contains information on printing bar codes with SAPscript
    Note 94233 contains information on printing MICR font with SAPscript
    Note 62178 contains information on device types for the Japanese version of the R/3 System.
    Note 77891 contains information on device types for IBM-SCS printers on the IBM AS/400 hardware platform.
    Note 98477 informs you on device types for printers by the manufacturer PSi.
    Note 107938 contains information on device types for printers by the producer Tally.
    Note 141719 contains information on device types for printers from the producer Printronix.
    Note 141914 contains information on device types for printers from the producer Lexmark.
    Note 153879 contains information on compatible printer models of producer EPSON.
    Note 154494 contains information on compatible printer models of producer Genicom.
    Note 199166 contains information on device types for printers from the producer Hewlett Packard.
    Note 214187 contains information on device types for printers from the producer Océ.
    Note 398236 contains information on device types for printers from the producer Sharp.
    Note 408189 contains information on device types for printers from the producer Konica Minolta.
    Note 436609 contains information on device types for printers from the producer Xerox.
    Note 458047 contains information on device types for printers from the producer Ricoh.
    Note 485240 contains information on device types for printers from the producer SAVIN.
    Note 485244 contains information on device types for printers from the producer NRG.
    Note 516687 contains information on device types for printers from the producer Lanier.
    Note 516669 contains information on device types for printers from the producer Gestetner.
    Note 878109 contains information on device types for printers from the producer Danka.
    ASCIIPRI
    Generic device type for line printers that can be used in urgent cases where no customized printer definition exists for a line printer. It contains no printer-specific control commands, but merely CARRIAGE RETURN, NEWLINE and FORMFEED commands. It uses the standard 7 bit ASCII character set (USASCII).
    COMPU960
    Device type for BULL line printers COMPUPRINT 4/66, as well as COMPUPRINT 960. Character set used: IBM 2 German.
    DECLA75P
    Device type for the DEC line printer DEC LA75 Plus.
    DECLN07
    Device type for the DEC laser printers LN07 and DECLaser 1100.
    HP256X
    Device type for all Hewlett-Packard line printers in the HP256... series. Based on the HP manual describing the HP256X series, OCR-A is included in this printer definition, but the printer needs an additional firmware/font cassette.
    HP2930
    Device type for Hewlett-Packard's HP2930 line printer.
    HPDJ500
    Device type for Hewlett-Packard's DeskJet 500 ink jet printer.
    HPLJIIID
    Device type for Hewlett-Packard's LaserJet IIIP, III, IIID and IIIsi printers, as well as the HP LaserJet 4 series. OCR-A and OCR-B are included in the printer definition, but the printer needs an additional firmware/font cassette. The "HP LaserJet barcodes & More Font Cartridge" is needed for this. Barcode printing from R/3 is not supported.
    HPLJSTND
    Generic device type for printers that have an HP LaserJet emulation but cannot be operated via the definitions HPLJ4, HPLJIIID or HPLJ_II.
    HPLJ_II
    Device type for the Hewlett-Packard LaserJet II laser printer series. OCR-A and OCR-B are included in the printer definition, but the printer needs an additional firmware/font cassette. The "HP LaserJet barcodes & More Font Cartridge" is needed for this. Barcode printing from R/3 is not supported.
    KYOF1000
    Device type for the Kyocera F-1000 laser printer. OCR fonts are not supported. Bar code printing is supported.
    KYOF1200
    Device type for the Kyocera laser printers F-1200 and F-1200S. OCR fonts are not supported. Barcode printing is supported.
    MT600
    Device type for the Mannesmann-Tally line printer MT600. Character set used: US-ASCII (that is no German umlauts).
    MT600GER
    Device type for the Mannesmann-Tally line printer MT600. Character set used: German. OCR-A and OCR-B (German standard) are included in the printer definition; the printer must be upgraded with these fonts.
    MT600NDA
    Device type for the Mannesmann-Tally line printer MT600. Character set used: Norwegian / Danish. OCR-A and OCR-B (German standard) are included in the printer definition; the printer must be upgraded with these fonts.
    OKI341
    Device type for the OKI Microline 3410 line printer.
    POSTSCPT
    Device type which is used for pure PostScript printers. Barcode printing from R/3 is not supported.
    S4440XTG
    Device type for the SEL Alcatel line printer 4440XT. Character set used: German.
    SAPWIN
    Generic device type for printers linked (or also fax devices) to PCs running under MS Windows 3.1, Windows 95 or Windows NT by means of the R/3 program SAPLPD. Windows printer drivers are used and the character set is ISO 8859-1. Barcode printing from R/3 is possible with the additional installation of a third-party DLL (see Note 25344), but is not supported in the standard system. OCR-A and OCR-B fonts are possible with an appropriate TrueType font (see also Note 48803).
    Important Note:
    As of Release 3.0E, you can use SAPWIN to:
    Print proportional fonts and lines/boxes in SAPscript
    Print black and white as well as color TIFF graphics (with the 32-bit SAPlpd on Windows 95 and Windows NT only).
    See Note 39031.
    SWIN
    Generic device type for printing/faxing using MS Windows with SAPlpd. It is available as of Release 3.1H. Device type SWIN differs from SAPWIN in the layout of X_... formats for ABAP/4 list printing. The font size and line spacing were adjusted, particularly for color list printing.
    In addition, SAPWIN contains an expanded list of SAPscript printer fonts for current releases, for example, Greek and Russian.
    SNI4009
    Device type for the Siemens-Nixdorf SNI 4009 line printer.
    SNI4010
    Device type for the Siemens-Nixdorf SNI 4010 line printer. OCR-A is included in the printer definition, but the printer needs an additional firmware/font cassette.
    SNI9014
    Device type for the Siemens-Nixdorf SNI 9014/12 line printer. OCR-A and OCR-B are included in the printer definition. The 9014/12 has OCR-A and OCR-B font installed as a default.
    SNIZD13
    Device type for the Siemens-Nixdorf SNI ZD13 line printer. OCR-A is included in the printer definition. The ZD13 has OCR-A font installed as a default.
    CIP1000
    Device type for C.ITOH line printers CI-1000 and CI-500. The IBM Proprinter II/XL emulation and IBM character set 2 (multilingual) are used.
    EPESCP
    Device type for all 24 or 48 element EPSON printers that use the control language ESC/P. Character set IBM 437 is used. OCR-A/OCR-B are included in the printer definition. However, some printers also require an additional firmware/font cassette.
    EPESCP2
    Device type for EPSON printers that use the control language ESC/P2. The character set IBM 850 (multilingual) is used. OCR-A/OCR-B are included in the printer definition. However, some printers also require an additional firmware/font cassette.
    EPESCP9
    Device type for all 9-pin dot matrix EPSON printers that use the control language ESC/P. The standard ASCII character set is used with some additional international characters.
    EPLQ550
    Device type for the EPSON LQ-55 dot matrix printer. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette.
    HP2300
    Device type for the Hewlett-Packard 2300 line printer series. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette.
    HPLJ4
    Device type for all printers in Hewlett-Packard's LaserJet 4 series (this includes LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4si). OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette. The "HP LASERJET barcodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with HP LaserJet 4 Series printers requires SIMM module "JetCAPS Intelligent Barcode SIMM" and is supported.
    IBM239X
    Device type for the IBM 238X/239X Plus line printer series from Lexmark. This includes the types IBM 2380 Plus, IBM 2381 Plus, IBM 2390 Plus, IBM 2391 Plus. The IBM emulation and character set IBM 850 are used.
    IBM4226
    Device type for the IBM 4226 line printers from Lexmark. The IBM emulation and the character set IBM 850 are used.
    IBM4232
    Device type for the IBM 4232-302 line printer from IBM. The 4202 emulation and the character set IBM 2 are used. OCR-A/OCR-B are included and supported. Barcode printing is not supported.
    IBM6408
    Device type for the IBM 6408-A00 line printer from IBM. The PropPrinter III XL emulation and the character set IBM 850/IBM 2 are used. OCR-A/OCR-B are included and supported. Barcode printing is not supported.
    IBMAFP
    Device type for IBM's external SAP2AFP converter. The R/3 spool output is converted to AFPDS format and passed to IBM AFP software. IBMAFP can only be used in conjunction with spool-exit (access method Z when defining the device type). Selection of printers directly connected to R/3 is not possible. IBMAFP must be used for 240 pel AFP printers.
    Character set is ISO 8859-1 (Latin 1). OCR-A and OCR-B are supported, as well as barcodes.
    IBMAFP is for use on R/3 UNIX and Windows NT platforms.
    IBMEFP is the proper device type for AS/400 R/3 Platforms and uses the EBCDIC character set.
    IBMAFP3
    Device type for IBM's external SAP2AFP converter that converts the R/3 spool output to an AFPDS format and sends it to IBM AFP software.IBMAFP3 can be used only in conjunction with spool-exit (access method Z when defining the device type). Selection of printers connected via R/3 is not possible. IBMAFP3 must be used for 300 pel AFP printers.
    Character set is ISO 8859-1 (Latin 1). OCR-A and OCR-B are supported, as well as barcodes.
    IBMAFP3 is for use on UNIX and Windows NT platforms.
    IBMEFP3 is the proper device type for AS/400 R/3 Platforms and uses the EBCDIC character set.
    IBMSCS
    Device Type IBMSCS supports the "basic IBMSNA Character String" data stream for printers that are connected under IBM OS/400. IBMSCS is only supported for the use under SAP R/3 on hardware platforms IBM AS/400.
    LX4039
    Device type for the Lexmark laser printer series 4039. OCR-A/OCR-B are included in the printer definition. However, the printer requires an additional firmware/typeface cassette. "HP LASERJET barcodes & MORE FONT CARTRIDGE" is required. Barcode printing from R/3 is not supported.
    KYOFS150
    Device type for the Kyocera laser printer FS-1500, FS-3500, FS-1550+. OCR fonts are not supported. Barcode printing is supported.
    NECP30
    Device type for the NEC matrix printers P20/P30. The character set used is IBM codepage 850 (multilingual).
    NECP72
    Device type for the NEC matrix printers P62/P72. The NEC Pinwriter level 2 emulation and the character set IBM codepage 850 (multilingual) are used. OCR-A/OCR-B are included in the printer definition. However, the printer requires an additional firmware/font cassette.
    NECPW
    Device type for the NEC 48-pin Pinwriter P5XL, P9XL, P6/P7, P6plus/P7plus, P2200, P2plus, P60/P70, P90, P20/P30, P22Q/P32Q, P42/P52, P62/P72. The character set IBM codepage 850 (multilingual) is used.
    SNI4011
    Device type for the 24-pin version of the SNI 4011 dot matrix printer. The EPSON LQ-850+ emulation and character set IBM codepage 850 (multilingual) are used. OCR-A/OCR-B are included in the printer definition. The printer has these fonts built in.
    SNI20XX8
    Device type for the Siemens-Nixdorf 2050-8, 2075-8 and 2090-8 laser printers (HP-LaserJet emulation). For operation with R/3, you need to obtain a special font diskette for the printer from SNI. This contains the fonts required, including OCR-A and OCR-B. Barcode printing from R/3 is not supported.
    MT2033
    Device type for the Mannesmann-Tally T2033 matrix printer. Uses MTPL+IBM Proprinter emulation and IBM codepage II for the character set. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
    MT2045
    Device type for the Mannesmann-Tally T2045 matrix printer. Uses MTPL+IBM Proprinter emulation and IBM codepage II for the character set. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
    DEVICE TYPES NEW TO RELEASE 3.1G:
    HPDJ660
    Device type for the color inkjet printer Hewlett-Packard DeskJet 660C. Lists are printed in color. OCR-A, OCR-B and barcode printing from R/3 are not supported.
    HPDJ850
    Device type for the color inkjet printer Hewlett-Packard DeskJet 850C. Lists are printed in color. OCR-A, OCR-B and barcode printing from R/3 are not supported.
    HPLJ5SI
    Device type for Hewlett-Packard's LaserJet 5Si. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware. The "HP LASERJET barcodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with HP LaserJet 5Si requires and supports SIMM module "JetCAPS Intelligent Barcode SIMM".
    MT6045
    Device type for the Mannesmam-Tally T6045 dot matrix printer. Uses MT660 emulation and character set Latin-1. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
    Important note: For use with R/3 the printer's standard character set must be set to Latin-1.
    NEW DEVICE TYPES IN RELEASE 3.1H:
    MT691
    Device type for the Mannesmann-Tally T691 dot matrix printer. Uses MT660 emulation and character set Latin-1. OCR-A/OCR-B are included in the printer definitions. These fonts are built into the printer at the factory.
    NEW DEVICE TYPES IN RELEASE 3.1I:
    SAPWIN5
    Device type for printing cyrillic characters (character set ISO 8859-5, for example Russian) with SAPlpd/Microsoft Windows. This device type works exclusively with the Russian Windows 95 or NT 4.0 (not with Windows 3.1). To use it, a 32 bit version of the SAPlpd with a number 4.00 or higher is required.
    DEVICE TYPES IN RELEASE 4.0A:
    HPLJ5
    Device type for all printers of the Hewlett-Packard LaserJet 5 printer series (LaserJet 5/5m, 5P/5MP, 5C) except for HP LaserJet 5 SI. OCR-A/OCR-B are included in the printer definitions. However, the printer needs an additional firmware/font cassettes. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with printers of the HP LaserJet 5 series requires and supports SIMM module "JetCAPS Intelligent Barcode SIMM".
    Important note: HPLJ5 uses new 4.0A features (scalable fonts under PCL-5) and can only be used in Release 4.0A and higher releases!
    I2HP4
    Device type for Eastern Europe for all printer of the Hewlett Packard LaserJet 4 printer series (for example, LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4Si). Uses character set "ISO 8859/2" (Latin 2). OCR-A/OCR-B are included in the printer definitions, however, the printer requires additional firmware/font diskette. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a respective SIMM module is required. For the barcode print from R/3 with printer of the HP LaserJet 4 series the SIMM module "JetCAPS Intelligent Barcode SIMM" is required and supported.
    I2SWIN
    Device type for Eastern Europe for printing under Microsoft Windows via a 32 bit SAPlpd. I2SWIN uses the character set ISO 8859/2 (Latin 2). To use I2SWIN, the following preconditions are required:
    SAPlpd 32 bit version, from 4.00
    Microsoft Windows NT 4.0 or eastern European Win95 (Latin 2 version)
    R/3 Release 3.0E or higher
    Important note: Microsoft Windows 3.1 (SAPlpd 16 bit) is NOT supported!
    I7SWIN
    Device type for Greece for printing under Microsoft Windows via SAPlpd 32 bit. I7SWIN uses character set "ISO 8859/7" (Greek). Requirements for operation of I7SWIN are:
    SAPlpd 32 bit as of Version 4.00
    MS Windows NT 4.0 or Greek Windows 95
    R/3 Release 3.0E or newer
    Important note: MS Windows 3.1 (SAPlpd 16 bit) is not supported!
    NEW DEVICE TYPES IN RELEASE 4.5A:
    HPLJ4000
    Device type for the Hewlett Packard LaserJet 4000 printer and
    related models such as LaserJet 5000, 8000, 8100 and 8150.
    HPLJ4000 uses character set "ISO 8859/1" (Latin 1). For the barcode print from R/3 with HP LaserJet 4000, the DIMM module "JetCAPS Intelligent Barcode DIMM" is required and supported. In addition to the barcodes this DIMM module contains the OCR-A and OCR-B fonts that are supported by HPLJ4000.
    Device type HPLJ4000 offers improved output of ABAP print lists by using a special PCL-5-printer drivers and can therefore only be used in Releases as of 4.5A.
    I9HP4
    Device type for Turkey for all printers of the Hewlett-Packard LaserJet 4 printer series (among others LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4Si). I9HP4 uses character set "ISO 8859/9" (Latin 5). OCR-A/ OCR-B are contained in the device type, however, the printer needs extra firmware or an extra font cartridge. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a corresponding SIMM module is needed for this. The SIMM module "JetCAPS Intelligent Barcode SIMM" is a requirement for printing barcodes from R/3 with printers of the HP LaserJet 4 series and is supported.
    KYOFS170
    Device type for the Kyocera laser printer FS-1700. OCR fonts are not supported. Barcode printing is supported.
    Device type KYOFS170 offers improved output of ABAP print lists by using a special PRESCRIBE-II-printer driver and can therefore only be used in Releases as of 4.5A.
    POST2
    New device type for PostScript-level-2-printer which can be used alternatively to POSTSCPT. Barcode printing and OCR printing from R/3 is not supported.
    Device type POST2 offers an improved output of ABAP print lists by using a special PostScript-L2-printer driver and can therefore only be used in Releases as of 4.5A.
    NEW DEVICE TYPES IN RELEASE 4.6A:
    IXLINK
    Device type for the external XLink/SAP translator of Xerox, which translates R/3 SAPGOF data to Xerox format and transfers data to the Xerox production printer. IXLINK can only be used if the XLink/SAP translator is being used. You cannot access printers, which are connected via R/3!
    OCR-A and OCR-B fonts as well as bar codes are supported.
    NEW DEVICE TYPES IN RELEASE 4.6C:
    HPLJ8000
    Device type for Hewlett Packard LaserJet 8000, 8000N, 8000DN printers. HPLJ8000 uses character set "ISO 8859/1" (Latin 1). For the barcode print from R/3 with HP LaserJet 4000, the DIMM module "JetCAPS Intelligent Barcode DIMM" is required and supported. In addition to the barcodes this DIMM module contains the OCR-A and OCR-B fonts that are supported by HPLJ4000.
    Device type HPLJ8000 offers improved output of ABAP print lists by using a special PCL-5-printer driver and can therefore only be used in Releases as of 4.5A.
    HPLJ1100
    Device type for Hewlett Packard LaserJet 1100 printer. HPLJ1100 uses character set "ISO 8859/1" (Latin 1). OCR-A/B as well as barcode print from R/3 are not supported.
    Device type HPLJ1100 can only be used in Releases as of 4.6C.
    I9SWIN
    Device type for Turkey und printing with MS Windows via SAPlpd 32 bit. I9SWIN uses character set "ISO 8859/9" (Latin 5). Preconditions for using I9SWIN:
    SAPlpd 32 bit as of version 4.00
    MS Windows NT 4.0 or Turkish Windows 95 (Latin 5 Version)
    R/3 Release 3.0E or newer
    Important note: MS Windows 3.1 (SAPlpd 16 bit) is not supported!
    IBMNP
    Device type for laser printer IBM InfoPrint 20 as well as the IBM Network Printer 12, 17, 24, IBM InfoPrint 32, InfoPrint 40. OCR- and MICR fonts are supported by the device type. The printer needs an additional module for these fonts. "Barcode-, MICR and OCR A+B SIMM for IBM Network Printers" is required. Read Note 133660 also. Bar code printing from R/3 is not supported.
    Important note: IBMNP uses new 4.0A features (scaleable font under PCL-5) and can only be used in maintenance level 4.0A and higher.
    NEW DEVICE TYPES IN RELEASE 6.10:
    IBMIP12
    Device type for laser printer IBM InfoPrint 12. IBMIP12 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBMIP21
    Device type for laser printer IBM InfoPrint 21. IBMIP21 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBMIP32
    Device type for laser printers IBM InfoPrint 32 and InfoPrint 40. IBMIP32 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBMIP2K
    Device type for production laser printer IBM InfoPrint 2000 with PCL-5 emulation. IBMIP2K uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBMIP60
    Device type for laser printer IBM InfoPrint 60. IBMIP60 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBMIP70
    Device type for laser printer IBM InfoPrint 70. IBMIP70 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
    IBM4247
    Device type for line printer IBM 4247. The printer's 4247 emulation and character set IBM2 is used. OCR-fonts are supported. Bar code printing from SAP is not supported.
    Attention: Please follow note 396462 when installing the printer.
    NEW DEVICE TYPES IN RELEASE 6.20:
    IBM6400
    Device type for line printer IBM 6400. The printer's "P-Series" emulation and character set PC850 is used. OCR-fonts are supported. Bar code printing from SAP is not supported.
    Attention: Please follow note 396462 when installing the printer.
    HP1200
    Device type for HP LaserJet 1200/1220. HP1200 uses character set "ISO 8859/1" (Latin 1).
    HP1200 is compatible with all releases from 4.0A.
    HP2200
    Device type for HP LaserJet 2200. HP2200 uses character set "ISO 8859/1" (Latin 1).
    HP2200 is compatible with all releases from 4.0A.
    HP2250
    Device type for HP Business Inkjet 2250. HP2250 uses character set "ISO 8859/1" (Latin 1).
    HP2250 is compatible with all releases from 4.5B.
    Attention: Business Inkjet 2200 is not compatible with HP2250.
    HP2500
    Device type for HP DeskJet 2500C with PCL-5 option. HP2500 uses character set "ISO 8859/1" (Latin 1).
    HP2500 is compatible with all releases from 4.0A.
    HP3200
    Device type for HP LaserJet 3200m. HP3200 uses character set "ISO 8859/1" (Latin 1).
    HP3200 is compatible with all releases from 4.0A.
    HP4100
    Device type for HP LaserJet 4100. HP4100 uses character set "ISO 8859/1" (Latin 1).
    HP4100 is compatible with all releases from 4.0A.
    HP4550
    Device type for HP LaserJet 4550 (color laser). HP4550 uses character set "ISO 8859/1" (Latin 1).
    HP4550 is compatible with all releases from 4.5A.
    HP8150
    Device type for HP LaserJet 8150. HP8150 uses character set "ISO 8859/1" (Latin 1).
    HP8150 is compatible with all releases from 4.0A.
    HP8550
    Device type for HP LaserJet 8550 (color laser). HP8550 uses character set "ISO 8859/1" (Latin 1).
    HP4550 is compatible with all releases from 4.5A.
    HP9000
    Device type for HP LaserJet 9000. HP9000 uses character set "ISO 8859/1" (Latin 1).
    HP9000 is compatible with all releases from 4.0A.
    NEW DEVICE TYPES IN RELEASE NW04:
    BRHL
    Device type for Brother laser printer HL-2460. This device type is compatible to other Brother laser printers, see below.
    OCR-A and OCR-B fonts as well as bar codes are supported.
    BRHL is compatible with all releases from 4.5A.
    IP2085
    Device type for the IBM Infoprint 2085 Laser printer with printer language PCL-5. OCR font and bar code printing from SAP are not supported.
    IP2085 is compatible with all releases 4.5A and higher.
    IP2085P
    Device type for the IBM Infoprint 2085 Laser printer with printer language PostScript. OCR font and bar code printing from SAP are not supported.
    IP2085P is compatible with all releases 4.5A and higher.
    IP2105
    Device type for the IBM Infoprint 2105 Laser printer with printer language PCL-5. OCR font and bar code printing from SAP are not supported.
    IP2105 is compatible with all releases 4.5A and higher.
    IP2105P
    Device type for the IBM Infoprint 2105 Laser printer with printer language PostScript. OCR font and bar code printing from SAP are not supported.
    IP2105P is compatible with all releases 4.5A and higher.
    LEXT622
    Device type for the Lexmark T622 laser printer. OCR-fonts and bar code printing from SAP are supported if the printer is equipped with a corresponding option (note 119471).
    LEXT622 is compatible with all releases 4.5A and higher.
    LEXW820
    Device type for the Lexmark W820 laser printer. OCR-fonts and bar code printing from SAP are supported if the printer is equipped with a corresponding option (note 119471).
    LEXW820 is compatible with all releases 4.5A and higher.
    LEX4227P
    Device type for the Lexmark 4227plus line printer. The device type supports the Latin-1 character set. For using the device type, the IBM emulation must be set in the printer.
    OCR fonts and barcode printing from SAP are not supported.
    LEX4227P is compatible with all releases.
    I5LEX
    Device type for Cyrillic printing (e.g. Russian) with Lexmark T522 laser printer. Lexmark T522 natively supports Cyrillic fonts and character set ISO 8859-5.
    OCR-fonts are not supported. Bar code printing is supported (with a bar code DIMM, see note 119471).
    I5LEX is compatible with all releases 4.0A and higher.
    CNLX522
    Device type for Lexmark T522 laser printer with add-on "Simplified Chinese DBCS font DIMM kit" (Lexmark product number 09H0690). The device type supports Simplified Chinese. OCR-fonts and bar code printing from SAP are not supported.
    CNLX522 is compatible with all releases 4.0A and higher.
    JPLX522
    Device type for Lexmark T522 laser printer with add-on "Japanese DBCS font DIMM kit" (Lexmark product number 13K0227). The device type supports Japanese character set. OCR-fonts and bar code printing from SAP are not supported.
    JPLX522 is compatible with all releases 4.0A and higher.
    KPLX522
    Device type for Lexmark T522 laser printer with add-on "Korean DBCS font DIMM kit" (Lexmark product number 10G1705). The device type supports Korean character set. OCR-fonts and printing of bar codes from SAP are not supported.
    KPLX522 is compatible with all releases 4.0A and higher.
    TWLX522
    Device type for Lexmark T522 laser printer with add-on "Traditional Chinese DBCS font DIMM kit" (Lexmark product number 09H0691). The device type supports traditional Chinese character set. OCR-fonts and bar code printing from SAP are not supported.
    TWLX522 is compatible with all releases 4.0A and higher.
    HP5000
    Device type for HP LaserJet 5000. HP5000 uses character set "ISO 8859/1" (Latin 1).
    HP5000 is compatible with all releases from 4.0A.
    HP23
    Device type for HP LaserJet 2300. HP23 uses character set "ISO 8859/1" (Latin 1).
    HP23 is compatible with all releases from 4.5A.
    HP3000
    Device type for HP business inkjet 3000. HP3000 uses character set "ISO 8859/1" (Latin 1).
    HP3000 is compatible with all releases from 4.5A.
    HP4300
    Device type for HP LaserJet 4200 and HP LaserJet 4300. HP4300 uses character set "ISO 8859/1" (Latin 1).
    HP4300 is compatible with all releases from 4.5A.
    HP4600
    Device type for HP color LaserJet 4600. HP4600 uses character set "ISO 8859/1" (Latin 1).
    HP4600 is compatible with all releases from 4.5A.
    HP5100
    Device type for HP LaserJet 5100. HP5100 uses character set "ISO 8859/1" (Latin 1).
    HP5100 is compatible with all releases from 4.5A.
    HP5500
    Device type for HP color LaserJet 5500. HP5500 uses character set "ISO 8859/1" (Latin 1).
    HP5500 is compatible with all releases from 4.5A.
    HP9500
    Device type for HP color LaserJet 9500. HP9500 uses character set "ISO 8859/1" (Latin 1).
    HP9500 is compatible with all releases from 4.5A.
    I2HPPS
    Device type for certain HP LaserJet models with PostScript emulation (see Note 575916). I2HPPS supports character set "ISO 8859/2" (Latin 2).
    I2HPPS is compatible with all releases as of 4.0A.
    Barcode printing and OCR fonts are not supported.
    CAN105
    Device type for Canon laser printer imageRUNNER 105. CAN105 supports character set ISO 8859-1 (Latin 1).
    CAN105 is compatible with all releases as of 4.5A.
    OCR-fonts are supported, barcode printing is not supported.
    CAN22
    Device type for Canon laser printers imageRUNNER 2200/2800/3300/3300i. CAN22 supports character set ISO 8859-1 (Latin 1).
    CAN22 is compatible with all releases as of 4.5A.
    OCR-fonts are supported, barcode printing is not supported.
    CAN5
    Device type for Canon laser printers imageRUNNER 5000/5000i/6000. CAN5 supports character set ISO 8859-1 (Latin 1).
    CAN5 is compatible with all releases as of 4.5A.
    OCR-fonts are supported, barcode printing is not supported.
    CAN85
    Device type for Canon laser printers imageRUNNER 8500/7200/85. CAN85 supports character set ISO 8859-1 (Latin 1).
    CAN85 is compatible with all releases as of 4.5A.
    OCR-fonts are supported, barcode printing is not supported.
    CN105PS
    PostScript device type for Canon laser printer imageRUNNER 105. CN105PS supports character set ISO 8859-1 (Latin 1).
    CN105PS is compatible with all releases as of 4.5A.
    OCR-fonts and barcode printing is not supported.
    CN22PS
    PostScript device type for Canon laser printers imageRUNNER 2200/2800/3300/3300i. CN22PS supports character set ISO 8859-1 (Latin 1).
    CN22PS is compatible with all releases as of 4.5A.
    OCR-fonts and barcode printing is not supported.
    CN5PS
    PostScript device type for Canon laser printer imageRUNNER 5000/5000i/6000. CN5PS supports character set ISO 8859-1 (Latin 1).
    CN5PS is compatible with all releases as of 4.5A.
    OCR-fonts and barcode printing is not supported.
    CN85PS
    PostScript device type for Canon laser printer imageRUNNER 8500/7200/85. CN85PS supports character set ISO 8859-1 (Latin 1).
    CN85PS is compatible with all releases as of 4.5A.
    OCR-fonts and barcode printing is not supported.
    CAN400
    PCL5 device type for Canon laser printer imageRUNNER 330/400. CAN400 supports character set ISO 8859-1 (Latin 1).
    CAN400 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CN400PS
    PostScript device type for Canon laser printer imageRUNNER 330/400. CN400PS supports character set ISO 8859-1 (Latin 1).
    CN400PS is compatible with all releases as of 4.5A.
    OCR-fonts and barcode printing is not supported.
    CANC32
    PCL5 device type for Canon color laser printer Color imageRUNNER C3200. CANC32 supports character set ISO 8859-1 (Latin 1).
    CANC32 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    NEW DEVICE TYPES IN RELEASE SAP NetWeaver 04s:
    ARM205
    PCL-5 device type for Sharp laser printer AR-M205. ARM205 uses character set ISO 8859-1 (Latin-1).
    ARM205 is compatible with all releases as of 4.5A.
    OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
    ARM276
    PCL-5 device type for Sharp laser printer AR-M276. ARM276 uses character set ISO 8859-1 (Latin-1).
    ARM276 is compatible with all releases as of 4.5A.
    OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
    ARM450
    PCL-5 device type for Sharp laser printer AR-M450. ARM450 uses character set ISO 8859-1 (Latin-1).
    ARM450 is compatible with all releases as of 4.5A.
    OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
    ARM550
    PCL-5 device type for Sharp laser printer AR-M550U. ARM550 uses character set ISO 8859-1 (Latin-1).
    ARM550 is compatible with all releases as of 4.5A.
    OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
    ARC262P
    PostScript device type for Sharp color laser printer ARC-262M. ARC262P is compatible with all releases as of 4.5A.
    OCR fonts are not supported.
    CAN2220
    PCL5 device type for Canon laser printer imageRUNNER 2220n/2220i/3320n/3320i. CAN2220 supports character set ISO 8859-1 (Latin 1).
    CAN2220 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CN2220P
    PostScript device type for Canon laser printer imageRUNNER 2220n/2220i/3320n/3320i. CN2220P supports character set ISO 8859-1 (Latin 1).
    CN2220P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CAN5020
    PCL5 device type for Canon laser printer imageRUNNER 5020n/5020i/6020n/6020i. CAN5020 supports character set ISO 8859-1 (Latin 1).
    CAN5020 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CN5020P
    PostScript device type for Canon laser printer imageRUNNER 5020n/5020i/6020n/6020i. CN5020P supports character set ISO 8859-1 (Latin 1).
    CN5020P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC3100
    PCL5 device type for Canon color laser printer imageRUNNER C3100. CNC3100 supports character set ISO 8859-1 (Latin 1).
    CNC3100 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CNC31PS
    PostScript device type for Canon color laser printer imageRUNNER C3100. CNC31PS supports character set ISO 8859-1 (Latin 1).
    CNC31PS is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC3220
    PCL5 device type for Canon color laser printers imageRUNNER C3220/C2620. CNC3220 supports character set ISO 8859-1 (Latin 1).
    CNC3220 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CNC322P
    PostScript device type for Canon color laser printers imageRUNNER C3220/C2620. CNC322P supports character set ISO 8859-1 (Latin 1).
    CNC322P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC6800
    PCL5 device type for Canon color laser printers imageRUNNER C5800/C6800. CNC6800 supports character set ISO 8859-1 (Latin 1).
    CNC6800 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is not supported.
    CNC68PS
    PostScript device type for Canon color laser printers imageRUNNER C5800/C6800. CNC68PS supports character set ISO 8859-1 (Latin 1).
    CNC68PS is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC31E
    PCL5 device type for Canon color laser printer imageRUNNER C3100 with imagePASS-E1 controller. CNC31E supports character set ISO 8859-1 (Latin 1).
    CNC31E is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC31EP
    PostScript device type for Canon color laser printer imageRUNNER C3100 with imagePASS-E1 controller. CNC31EP supports character set ISO 8859-1 (Latin 1).
    CNC31EP is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC322E
    PCL5 device type for Canon color laser printer imageRUNNER C3220/C2620 with imagePASS-C1 V.2 controller. CNC322E supports character set ISO 8859-1 (Latin 1).
    CNC322E is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC322EP
    PostScript device type for Canon color laser printer imageRUNNER C3220/C2620 with imagePASS-C1 V.2 controller. CNC322EP supports character set ISO 8859-1 (Latin 1).
    CNC322EP is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC68E
    PCL5 device type for Canon color laser printers imageRUNNER C5800/C6800 with imagePASS-D1 controller. CNC68E supports character set ISO 8859-1 (Latin 1).
    CNC68E is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CNC68EP
    PostScript device type for Canon color laser printers imageRUNNER C5800/C6800 with imagePASS-D1 controller. CNC68EP supports character set ISO 8859-1 (Latin 1).
    CNC68EP is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    CN2270
    PCL5 device type for Canon laser printers imageRUNNER 2270/2870/3570/4570. CN2270 supports character set ISO 8859-1 (Latin 1).
    CN2270 is compatible with all releases as of 4.5A.
    OCR-fonts are supported. Barcode printing is supported with usage of the optional barcode printing kit.
    CN2270P
    PostScript device type for Canon laser printer imageRUNNER 2270/2870/3570/4570. CN2270P supports character set ISO 8859-1 (Latin 1).
    CN2270P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcode printing are not supported.
    DL3100
    PCL5 device type for DELL color laser printer 3100cn. DL3100 supports character set ISO 8859-1 (Latin 1).
    DL3100 is compatible with all releases as of 4.5A.
    OCR-fonts and Barcodes are not supported.
    DL3100P
    PostScript device type for DELL color laser printer 3100cn. DL3100P supports character set ISO 8859-1 (Latin 1).
    DL3100P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcodes are not supported.
    DL5100
    PCL5 device type for DELL color laser printer 5100cn. DL5100 supports character set ISO 8859-1 (Latin 1).
    DL5100 is compatible with all releases as of 4.5A.
    OCR-fonts and Barcodes are not supported.
    DL5100P
    PostScript device type for DELL color laser printer 5100cn. DL5100P supports character set ISO 8859-1 (Latin 1).
    DL5100P is compatible with all releases as of 4.5A.
    OCR-fonts and Barcodes are not supported.
    HP3700
    Device type for HP color LaserJet 3700. HP3700 supports character set ISO 8859-1 (Latin 1).
    HP3700 is compatible with all releases as of 4.5A.
    HPBI23
    Device type for HP business inkjet 2300. HPBI23 supports character set ISO 8859-1 (Latin 1).
    HPBI23 is compatible with all releases as of 4.0A.
    HP9055
    Device type for HP LaserJet 9055mfp. HP9055 supports character set ISO 8859-1 (Latin 1).
    HP9055 is compatible with all releases as of 4.5A.
    HP9065
    Device type for HP LaserJet 9065mfp. HP9065 supports character set ISO 8859-1 (Latin 1).
    HP9065 is compatible with all releases as of 4.5A.
    I7HP4
    Device type for HP LaserJet printers with "Greek Font DIMM" (add-on module with Greek fonts). Information can be found under www.hp.com/go/sap/drivers. I7HP4 supports character setISO 8859/7 (Greek).
    I7HP4 is compatible with all releases as of 4.6B.
    HP4250
    Device type for HP LaserJet 4250 printer. HP4250 supports character set ISO 8859-1 (Latin 1).
    HP4250 is compatible with all releases as of 4.5A.
    HP1160
    Device type for HP LaserJet 1160 printer. HP1160 supports character set ISO 8859-1 (Latin 1).
    HP1160 is compatible with all releases as of 4.5A.
    HP1320
    Device type for HP LaserJet 1320 printer. HP1320 supports character set ISO 8859-1 (Latin 1).
    HP1320 is compatible with all releases as of 4.5A.
    HP2430
    Device type for HP LaserJet 2430 printer. HP2430 supports character set ISO 8859-1 (Latin 1).
    HP2430 is compatible with all releases as of 4.5A.
    HP3030
    Device type for HP LaserJet 3030 printer. HP3030 supports character set ISO 8859-1 (Latin 1).
    HP3030 is compatible with all releases as of 4.5A.
    HP4650
    Device type for HP Color LaserJet 4650 printer. HP4650 supports character set ISO 8859-1 (Latin 1).
    HP4650 is compatible with all releases as of 4.5A.
    HP5550
    Device type for HP Color LaserJet 5550 printer. HP5550 supports character set ISO 8859-1 (Latin 1).
    HP5550 is compatible with all releases as of 4.5A.
    HP9850
    Device type for HP 9850mfp. HP9850 supports character set ISO 8859-1 (Latin 1).
    HP9850 is compatible with all releases as of 4.5A.
    HPLJ9050
    Device type for HP LaserJet 9050 printer. HP9050 supports character set ISO 8859-1 (Latin 1).
    HP9050 is compatible with all releases as of 4.5A.
    HPOJ9130
    Device type for HP officejet 9130. HPOJ9130 supports character set ISO 8859-1 (Latin 1).
    HPOJ9130 is compatible with all releases as of 4.0B.
    HP4345
    Device type for HP LaserJet 4345mfp. HP4345 supports character set ISO 8859-1 (Latin 1).
    HP4345 is compatible with all releases as of 4.5B.
    HP9040
    Device type for HP LaserJet 9040mfp. HP9040 supports character set ISO 8859-1 (Latin 1).
    HP9040 is compatible with all releases as of 4.5B.
    HP9050
    Device type for HP LaserJet 9050mfp. HP9050 supports character set ISO 8859-1 (Latin 1).
    HP9050 is compatible with all releases as of 4.5B.
    HP9500M
    Device type for HP LaserJet 9500mfp. HP9500M supports character set ISO 8859-1 (Latin 1).
    HP9500M is compatible with all releases as of 4.5B.
    IP2060
    Device type for the IBM Infoprint 2060ES Laser printer with printer language PCL-5. IP2060 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2060 is compatible with all releases 4.5A and higher.
    IP2060P
    Device type for the IBM Infoprint 2060ES Laser printer with printer language PostScript. IP2060P supports character set ISO 8859-1 (Latin 1).OCR font and bar code printing from SAP are not supported.
    IP2060P is compatible with all releases 4.5A and higher.
    IP2075
    Device type for the IBM Infoprint 2075ES Laser printer with printer language PCL-5. IP2075 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2075 is compatible with all releases 4.5A and higher.
    IP2075P
    Device type for the IBM Infoprint 2075ES Laser printer with printer language PostScript. IP2075P supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2075P is compatible with all releases 4.5A and higher.
    IP2090
    Device type for the IBM Infoprint 2090ES Laser printer with printer language PCL-5. IP2090 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2090 is compatible with all releases 4.5A and higher.
    IP2090P
    Device type for the IBM Infoprint 2090ES Laser printer with printer language PostScript. IP2090P supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2090P is compatible with all releases 4.5A and higher.
    IP2105E
    Device type for the IBM Infoprint 2105ES Laser printer with printer language PCL-5. IP2105E supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2105E is compatible with all releases 4.5A and higher.
    IP2105EP
    Device type for the IBM Infoprint 2105ES Laser printer with printer language PostScript. IP2105EP supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
    IP2105EP is compatible with all releases 4.5A and higher.
    OKI6100
    Device type for OKI laser printer B6100. OKI6100 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
    OKI6100 is compatible with all releases as of 4.5A.
    OKI8300
    Device type for OKI laser printer B8300. OKI8300 supports character set ISO 8859-1 (Latin 1). OCR-fonts are not supported. Barcode printing is supported with an OKI add-on product.
    OKI8300 is compatible with all releases as of 4.5A.
    OKI9500
    Device type for OKI color laser printer C9500. OKI9500 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
    OKI9500 is compatible with all releases as of 4.5A.
    OKI4350
    Device type for OKI laser printer B4350. OKI4350 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
    OKI4350 is compatible with all releases as of 4.5A.
    OKI5400
    Device type for OKI color laser printer C5400. OKI5400 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
    OKI5400 is compatible with all releases as of 4.5A.
    OKI6300
    Device type for OKI laser printer B6300. OKI6300 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
    OKI6300 is compatible with all releases as of 4.5A.
    SML1451, SML1451

  • Barcode input to excel and read data

    Hello,
    I am creating a program where I would scan a barcode into LV and from there LV scans an excel spreadsheet for that barcode and returns the data from that row. I found an example online that helps with the barcode number find in excel but I am not coming up with a strange issue when trying to display the information from that row. My program finds the correct barcode in every case. Only when I enter the number from row 1 will the row information be correct. When I enter in information from row 2 lets say it displays the row information from row 3. When I enter in row 3 the program display row 5 information. Attached is my rough copy of code(this is my first stab at Active X controls so bear with it please) and an example spreadsheet I have created with some information about how the program is working. I have checked other posts for similar problems and couldnt find one that hepls with my particular issue. I have also checked the excel specific thread but found no links to code that can help. Any help is appreciated. Im thinking I am over looking something but since this is my first shot at this type of programming im not quite sure what it is. Thanks in advance for any information.
    Solved!
    Go to Solution.
    Attachments:
    Programmer(PC02).vi ‏14 KB
    Program Numbers.xlsx ‏10 KB

    nyc wrote:
    The other thread has no VI nor Excel.
    I'm curious what is going on in the VI, but I can't open it.
    It's the same question, except this time the OP provided a follow-up saying, "OK, here's what I got, and it does this. Why?" I would have just continued in that thread. Whatever.
    In any event, your error is that you do not want to wire the found row to the set of Range.Item(get) methods. You need to wire a constant of 1 to the "Row" parameters for both of those. Since you are operating on a found range, you do not want to change the row.
    As it stands right now your VI does not close Excel when done. The Excel process remains running in the background. Please review the example that ships with LabVIEW, which closes Excel when done.

  • Barcode using api

    Hi,
    I'm trying to solve problem with showing barcodes when generating html or pdf documents using api. I have function in db which generates barcodes 128b with correct start, control and stop chars, I've tested it notepad, using font AdvC128b, printed, scanned and everything is correct. The problem is obviously in word template in which I add field like <?BARCODE?> and set font for the field AdvC128b upload template to bi publisher. Using api I generate html and I do get barcode on page but it's not correct it cannot be scanned, on view source I can see that it creates page like this:
    .c0 {line-height: 27.744pt;margin-top: 0.0pt;margin-bottom: 0.0pt;margin-left: 6.35pt;margin-right: 6.049pt;}
    .c1 {font-family: 'AdvC128b';font-size: 24.0pt;color: #000000;}
    <p class="c0"><span class="c1">Ě90902qÎ </span><a name="page-total-master0" id="page-total-master0"></a><a name="page-total" id="page-total"></a></p>In pdf document I cannot see barcode I can only see Ě90902qÎ Do I need to put some fonts in my java runtime like I did put Albany fonts for special characters?
    This is quite urgent, what are my options? What needs to be done to show correct barcodes in html and pdf documents using api and word templates,
    any suggestions are more than welcome,
    thanks in advance,
    Tomislav.

    this is my config
    <?xml version="1.0" encoding="UTF-8"?>
    <config version="1.0.0" xmlns="http://xmlns.oracle.com/oxp/config/"><!-- Properties -->
    <properties>
    <!-- System level properties    -->
    <property name="system-temp-dir">c:\tmp</property>
    <!-- PDF compression
    <property name="pdf-compression">true</property>     -->
    <!-- PDF Security
    <property name="pdf-security">true</property>
    <property name="pdf-open-password">user</property>
    <property name="pdf-permissions-password">owner</property>
    <property name="pdf-no-printing">true</property>
    <property name="pdf-no-changing-the-document">true</property>     -->
    </properties>
    <!-- Font setting -->
    <fonts>
    <!-- Font setting (for FO to PDF etc...) -->
    <font family="Arial" style="normal" weight="normal">
    <truetype path="/fonts/Arial.ttf"/>
    </font>
    <font family="Default" style="normal" weight="normal">
    <truetype path="/fonts/ALBANWTJ.ttf"/>
    </font>
    <font family="advc128b" style="normal" weight="normal">
    <truetype path="C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf"/>
    </font>
    <!--Font substitute setting (for PDFForm filling etc...) -->
    <font-substitute name="MSGothic">
    <truetype path="/fonts/msgothic.ttc" ttcno="0"/>
    </font-substitute>
    </fonts>
    </config>and this is my complete log, sorry for posting it whole but I think it will be more useful to you:
    [100609_074839647][][STATEMENT] Logger.init(): *** DEBUG MODE IS ON. ***
    [100609_074839648][][STATEMENT] Logger.init(): LogDir=C:/tmp
    [100609_074839891][][STATEMENT] [ PDF GENERATOR ]---------------------------------------------
    [100609_074839892][][STATEMENT] XDO version   = Oracle BI Publisher 10.1.3.4.1
    [100609_074839892][][STATEMENT] java.home     = C:\Program Files\Java\jre1.6.0_06
    [100609_074839892][][STATEMENT] XDO_TOP       = null
    [100609_074839893][][STATEMENT] Config Path   = null
    [100609_074839893][][STATEMENT] Debug Cfg Path= C:\Program Files\Java\jre1.6.0_06\lib\xdodebug.cfg
    [100609_074839893][][STATEMENT] Font dir      = C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\
    [100609_074839894][][STATEMENT] Locale        = en-us
    [100609_074839894][][STATEMENT] Fallback font = truetype./fonts/ALBANWTJ.ttf
    [100609_074839894][][STATEMENT] [ PDF GENERATOR PROPERTIES ]----------------------------------
    [100609_074839896][][STATEMENT] digit-substitution=null(not set)
    [100609_074839896][][STATEMENT] font.ADVC128B.normal.normal=truetype.C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf
    [100609_074839898][][STATEMENT] font.ALBANY WT J.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf
    [100609_074839899][][STATEMENT] font.ALBANY WT K.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTK.ttf
    [100609_074839899][][STATEMENT] font.ALBANY WT SC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTS.ttf
    [100609_074839899][][STATEMENT] font.ALBANY WT TC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTT.ttf
    [100609_074839900][][STATEMENT] font.ALBANY WT.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANYWT.ttf
    [100609_074839900][][STATEMENT] font.ANDALE DUOSPACE WT J.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOJB.ttf
    [100609_074839901][][STATEMENT] font.ANDALE DUOSPACE WT J.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOJ.ttf
    [100609_074839901][][STATEMENT] font.ANDALE DUOSPACE WT K.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOKB.ttf
    [100609_074839901][][STATEMENT] font.ANDALE DUOSPACE WT K.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOK.ttf
    [100609_074839902][][STATEMENT] font.ANDALE DUOSPACE WT SC.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOSCB.ttf
    [100609_074839902][][STATEMENT] font.ANDALE DUOSPACE WT SC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOSC.ttf
    [100609_074839903][][STATEMENT] font.ANDALE DUOSPACE WT TC.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOTCB.ttf
    [100609_074839903][][STATEMENT] font.ANDALE DUOSPACE WT TC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOTC.ttf
    [100609_074839903][][STATEMENT] font.ANDALE DUOSPACE WT.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOB.ttf
    [100609_074839904][][STATEMENT] font.ANDALE DUOSPACE WT.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUO.ttf
    [100609_074839904][][STATEMENT] font.ARIAL.normal.normal=truetype./fonts/Arial.ttf
    [100609_074839904][][STATEMENT] font.CG TIMES.italic.bold=type1.Times-BoldItalic
    [100609_074839905][][STATEMENT] font.CG TIMES.italic.normal=type1.Times-Italic
    [100609_074839905][][STATEMENT] font.CG TIMES.normal.bold=type1.Times-Bold
    [100609_074839905][][STATEMENT] font.CG TIMES.normal.normal=type1.Times-Roman
    [100609_074839906][][STATEMENT] font.COURIER NEW.italic.bold=type1.Courier-BoldOblique
    [100609_074839906][][STATEMENT] font.COURIER NEW.italic.normal=type1.Courier-Oblique
    [100609_074839906][][STATEMENT] font.COURIER NEW.normal.bold=type1.Courier-Bold
    [100609_074839907][][STATEMENT] font.COURIER NEW.normal.normal=type1.Courier
    [100609_074839907][][STATEMENT] font.COURIER.italic.bold=type1.Courier-BoldOblique
    [100609_074839907][][STATEMENT] font.COURIER.italic.normal=type1.Courier-Oblique
    [100609_074839908][][STATEMENT] font.COURIER.normal.bold=type1.Courier-Bold
    [100609_074839908][][STATEMENT] font.COURIER.normal.normal=type1.Courier
    [100609_074839908][][STATEMENT] font.DEFAULT.italic.bold=type1.Helvetica-BoldOblique
    [100609_074839909][][STATEMENT] font.DEFAULT.italic.normal=type1.Helvetica-Oblique
    [100609_074839909][][STATEMENT] font.DEFAULT.normal.bold=type1.Helvetica-Bold
    [100609_074839909][][STATEMENT] font.DEFAULT.normal.normal=truetype./fonts/ALBANWTJ.ttf
    [100609_074839910][][STATEMENT] font.GLFALLBACK.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf
    [100609_074839910][][STATEMENT] font.HELVETICA.italic.bold=type1.Helvetica-BoldOblique
    [100609_074839910][][STATEMENT] font.HELVETICA.italic.normal=type1.Helvetica-Oblique
    [100609_074839910][][STATEMENT] font.HELVETICA.normal.bold=type1.Helvetica-Bold
    [100609_074839911][][STATEMENT] font.HELVETICA.normal.normal=type1.Helvetica
    [100609_074839911][][STATEMENT] font.MONOSPACE.italic.bold=type1.Courier-BoldOblique
    [100609_074839911][][STATEMENT] font.MONOSPACE.italic.normal=type1.Courier-Oblique
    [100609_074839912][][STATEMENT] font.MONOSPACE.normal.bold=type1.Courier-Bold
    [100609_074839912][][STATEMENT] font.MONOSPACE.normal.normal=type1.Courier
    [100609_074839912][][STATEMENT] font.SANS-SERIF.italic.bold=type1.Helvetica-BoldOblique
    [100609_074839913][][STATEMENT] font.SANS-SERIF.italic.normal=type1.Helvetica-Oblique
    [100609_074839913][][STATEMENT] font.SANS-SERIF.normal.bold=type1.Helvetica-Bold
    [100609_074839913][][STATEMENT] font.SANS-SERIF.normal.normal=type1.Helvetica
    [100609_074839914][][STATEMENT] font.SERIF.italic.bold=type1.Times-BoldItalic
    [100609_074839914][][STATEMENT] font.SERIF.italic.normal=type1.Times-Italic
    [100609_074839914][][STATEMENT] font.SERIF.normal.bold=type1.Times-Bold
    [100609_074839915][][STATEMENT] font.SERIF.normal.normal=type1.Times-Roman
    [100609_074839915][][STATEMENT] font.SYMBOL.normal.normal=type1.Symbol
    [100609_074839915][][STATEMENT] font.TIMES NEW ROMAN.italic.bold=type1.Times-BoldItalic
    [100609_074839916][][STATEMENT] font.TIMES NEW ROMAN.italic.normal=type1.Times-Italic
    [100609_074839916][][STATEMENT] font.TIMES NEW ROMAN.normal.bold=type1.Times-Bold
    [100609_074839916][][STATEMENT] font.TIMES NEW ROMAN.normal.normal=type1.Times-Roman
    [100609_074839917][][STATEMENT] font.TIMES.italic.bold=type1.Times-BoldItalic
    [100609_074839917][][STATEMENT] font.TIMES.italic.normal=type1.Times-Italic
    [100609_074839917][][STATEMENT] font.TIMES.normal.bold=type1.Times-Bold
    [100609_074839918][][STATEMENT] font.TIMES.normal.normal=type1.Times-Roman
    [100609_074839918][][STATEMENT] font.ZAPFDINGBATS.normal.normal=type1.ZapfDingbats
    [100609_074839918][][STATEMENT] pdf-changes-allowed=0
    [100609_074839919][][STATEMENT] pdf-compression=true
    [100609_074839919][][STATEMENT] pdf-enable-accessibility=true
    [100609_074839920][][STATEMENT] pdf-enable-copying=false
    [100609_074839920][][STATEMENT] pdf-encryption-level=0
    [100609_074839920][][STATEMENT] pdf-font-embedding=true
    [100609_074839920][][STATEMENT] pdf-hide-menubar=false
    [100609_074839921][][STATEMENT] pdf-hide-toolbar=false
    [100609_074839921][][STATEMENT] pdf-no-accff=false
    [100609_074839922][][STATEMENT] pdf-no-cceda=false
    [100609_074839922][][STATEMENT] pdf-no-changing-the-document=false
    [100609_074839923][][STATEMENT] pdf-no-printing=false
    [100609_074839923][][STATEMENT] pdf-open-password=
    [100609_074839923][][STATEMENT] pdf-permissions=0
    [100609_074839924][][STATEMENT] pdf-permissions-password=
    [100609_074839924][][STATEMENT] pdf-printing-allowed=0
    [100609_074839925][][STATEMENT] pdf-replace-smartquotes=true
    [100609_074839925][][STATEMENT] pdf-security=false
    [100609_074839926][][STATEMENT] ------------------------------------------------------
    [100609_074840004][oracle.apps.xdo.template.rtf.field.RTFFieldResult][STATEMENT] stylename=Normal
    [100609_074840030][oracle.apps.xdo.common.font.FontFactory$FontDef][ERROR] Failed to open TrueType font: /fonts/ALBANWTJ.ttf(0)
    [100609_074840031][oracle.apps.xdo.common.font.FontFactory$FontDef][ERROR] Failed to open Type3 font (SVG embedded): null
    [100609_074840031][][EXCEPTION] Default.normal.normal is invalid. Set it to Helvetica
    [100609_074840033][oracle.apps.xdo.common.font.FontFactory$FontDef][STATEMENT] TrueType font created: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf(0)
    [100609_074840034][oracle.apps.xdo.common.font.FontFactory$FontDef][STATEMENT] TrueType font created: C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf(0)
    [100609_074840041][oracle.apps.xdo.common.font.FontFactory$FontDef][STATEMENT] Type1 font created: Helvetica
    [100609_074840047][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840048][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840049][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840052][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840052][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840058][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840059][oracle.apps.xdo.template.rtf.RTFParagraph][STATEMENT] stylename=Normal
    [100609_074840070][oracle.apps.xdo.template.rtf.RTF2XSLParser][STATEMENT] Time spent: 185
    [100609_074840072][oracle.apps.xdo.common.font.FontFactory][STATEMENT] type1.Helvetica closed.
    [100609_074840072][oracle.apps.xdo.common.font.FontFactory][STATEMENT] truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf closed.
    [100609_074840073][oracle.apps.xdo.common.font.FontFactory][STATEMENT] truetype.C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf closed.
    [100609_074840097][][STATEMENT] Logger.init(): *** DEBUG MODE IS ON. ***
    [100609_074840097][][STATEMENT] Logger.init(): LogDir=C:/tmp
    [100609_074840098][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor constructor is called.
    [100609_074840174][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor has been initialized without default config.
    [100609_074840174][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setData(String) is called with 'C:\Users\RIFnet\Downloads\04_Ispis_prijevoznog_lista.xml'.
    [100609_074840176][][STATEMENT] Logger.init(): *** DEBUG MODE IS ON. ***
    [100609_074840176][][STATEMENT] Logger.init(): LogDir=C:/tmp
    [100609_074840176][oracle.apps.xdo.template.FOProcessor][STATEMENT]    Log file 'xdo_100609_074840176_fo_data_11.xml' is created.
    [100609_074840178][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setTemplate(String) is called with 'C:\Users\RIFnet\AppData\Local\Oracle\BIPublisher\TemplateBuilderforWord\tmp\tmp.xsl'.
    [100609_074840180][oracle.apps.xdo.template.FOProcessor][STATEMENT]    Log file 'xdo_100609_074840176_fo_data_12.xsl' is created.
    [100609_074840182][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setOutput(String)is called with 'C:\Users\RIFnet\AppData\Local\Oracle\BIPublisher\TemplateBuilderforWord\tmp\581254851319596out.pdf'.
    [100609_074840208][oracle.apps.xdo.template.FOProcessor][STATEMENT]    Log file 'xdo_100609_074840176_fo_out3.out' is created.
    [100609_074840209][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setLocale is called with 'en-us'.
    [100609_074840209][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setOutputFormat(byte)is called with ID=1.
    [100609_074840210][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.setConfig(String) is called with 'C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdo.cfg'.
    [100609_074840212][oracle.apps.xdo.template.FOProcessor][STATEMENT] Start Memory: max=254MB, total=6MB, free=1MB
    [100609_074840212][oracle.apps.xdo.template.FOProcessor][STATEMENT] FOProcessor.generate() called.
    [100609_074840216][oracle.apps.xdo.template.FOProcessor][STATEMENT] createFO(Object, Object) is called.
    [100609_074840409][oracle.apps.xdo.common.xml.XSLT10gR1][STATEMENT] Oracle XML Developers Kit 10.1.0.5.0 - Production
    [100609_074840410][oracle.apps.xdo.common.xml.XSLT10gR1][STATEMENT] Scalable Feature Disabled
    [100609_074840590][oracle.apps.xdo.template.FOProcessor][STATEMENT]    Log file 'xdo_100609_074840176_fo_fo_14.fo' is created.
    [100609_074840592][][STATEMENT] XSL-T time used: 329
    [100609_074840592][oracle.apps.xdo.template.fo.FOProcessingEngine][STATEMENT] Using proxy for PDF Generator
    [100609_074840598][oracle.apps.xdo.template.FOProcessor][STATEMENT] Calling FOProcessingEngine.process()
    [100609_074840599][][STATEMENT] Using optimized xslt
    [100609_074840614][][STATEMENT] [ PDF GENERATOR ]---------------------------------------------
    [100609_074840615][][STATEMENT] XDO version   = Oracle BI Publisher 10.1.3.4.1
    [100609_074840615][][STATEMENT] java.home     = C:\Program Files\Java\jre1.6.0_06
    [100609_074840615][][STATEMENT] XDO_TOP       = null
    [100609_074840615][][STATEMENT] Config Path   = null
    [100609_074840616][][STATEMENT] Debug Cfg Path= C:\Program Files\Java\jre1.6.0_06\lib\xdodebug.cfg
    [100609_074840616][][STATEMENT] Font dir      = C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\
    [100609_074840616][][STATEMENT] Locale        = en-us
    [100609_074840616][][STATEMENT] Fallback font = truetype./fonts/ALBANWTJ.ttf
    [100609_074840617][][STATEMENT] [ PDF GENERATOR PROPERTIES ]----------------------------------
    [100609_074840618][][STATEMENT] digit-substitution=null(not set)
    [100609_074840620][][STATEMENT] font.ADVC128B.normal.normal=truetype.C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf
    [100609_074840620][][STATEMENT] font.ALBANY WT J.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf
    [100609_074840620][][STATEMENT] font.ALBANY WT K.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTK.ttf
    [100609_074840621][][STATEMENT] font.ALBANY WT SC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTS.ttf
    [100609_074840621][][STATEMENT] font.ALBANY WT TC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTT.ttf
    [100609_074840621][][STATEMENT] font.ALBANY WT.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANYWT.ttf
    [100609_074840622][][STATEMENT] font.ANDALE DUOSPACE WT J.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOJB.ttf
    [100609_074840622][][STATEMENT] font.ANDALE DUOSPACE WT J.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOJ.ttf
    [100609_074840622][][STATEMENT] font.ANDALE DUOSPACE WT K.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOKB.ttf
    [100609_074840623][][STATEMENT] font.ANDALE DUOSPACE WT K.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOK.ttf
    [100609_074840623][][STATEMENT] font.ANDALE DUOSPACE WT SC.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOSCB.ttf
    [100609_074840623][][STATEMENT] font.ANDALE DUOSPACE WT SC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOSC.ttf
    [100609_074840624][][STATEMENT] font.ANDALE DUOSPACE WT TC.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOTCB.ttf
    [100609_074840624][][STATEMENT] font.ANDALE DUOSPACE WT TC.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOTC.ttf
    [100609_074840624][][STATEMENT] font.ANDALE DUOSPACE WT.normal.bold=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUOB.ttf
    [100609_074840624][][STATEMENT] font.ANDALE DUOSPACE WT.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ADUO.ttf
    [100609_074840625][][STATEMENT] font.ARIAL.normal.normal=truetype./fonts/Arial.ttf
    [100609_074840625][][STATEMENT] font.CG TIMES.italic.bold=type1.Times-BoldItalic
    [100609_074840625][][STATEMENT] font.CG TIMES.italic.normal=type1.Times-Italic
    [100609_074840625][][STATEMENT] font.CG TIMES.normal.bold=type1.Times-Bold
    [100609_074840626][][STATEMENT] font.CG TIMES.normal.normal=type1.Times-Roman
    [100609_074840626][][STATEMENT] font.COURIER NEW.italic.bold=type1.Courier-BoldOblique
    [100609_074840626][][STATEMENT] font.COURIER NEW.italic.normal=type1.Courier-Oblique
    [100609_074840627][][STATEMENT] font.COURIER NEW.normal.bold=type1.Courier-Bold
    [100609_074840627][][STATEMENT] font.COURIER NEW.normal.normal=type1.Courier
    [100609_074840627][][STATEMENT] font.COURIER.italic.bold=type1.Courier-BoldOblique
    [100609_074840627][][STATEMENT] font.COURIER.italic.normal=type1.Courier-Oblique
    [100609_074840628][][STATEMENT] font.COURIER.normal.bold=type1.Courier-Bold
    [100609_074840628][][STATEMENT] font.COURIER.normal.normal=type1.Courier
    [100609_074840628][][STATEMENT] font.DEFAULT.italic.bold=type1.Helvetica-BoldOblique
    [100609_074840629][][STATEMENT] font.DEFAULT.italic.normal=type1.Helvetica-Oblique
    [100609_074840629][][STATEMENT] font.DEFAULT.normal.bold=type1.Helvetica-Bold
    [100609_074840629][][STATEMENT] font.DEFAULT.normal.normal=truetype./fonts/ALBANWTJ.ttf
    [100609_074840629][][STATEMENT] font.GLFALLBACK.normal.normal=truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf
    [100609_074840630][][STATEMENT] font.HELVETICA.italic.bold=type1.Helvetica-BoldOblique
    [100609_074840630][][STATEMENT] font.HELVETICA.italic.normal=type1.Helvetica-Oblique
    [100609_074840630][][STATEMENT] font.HELVETICA.normal.bold=type1.Helvetica-Bold
    [100609_074840631][][STATEMENT] font.HELVETICA.normal.normal=type1.Helvetica
    [100609_074840631][][STATEMENT] font.MONOSPACE.italic.bold=type1.Courier-BoldOblique
    [100609_074840631][][STATEMENT] font.MONOSPACE.italic.normal=type1.Courier-Oblique
    [100609_074840631][][STATEMENT] font.MONOSPACE.normal.bold=type1.Courier-Bold
    [100609_074840632][][STATEMENT] font.MONOSPACE.normal.normal=type1.Courier
    [100609_074840632][][STATEMENT] font.SANS-SERIF.italic.bold=type1.Helvetica-BoldOblique
    [100609_074840633][][STATEMENT] font.SANS-SERIF.italic.normal=type1.Helvetica-Oblique
    [100609_074840633][][STATEMENT] font.SANS-SERIF.normal.bold=type1.Helvetica-Bold
    [100609_074840633][][STATEMENT] font.SANS-SERIF.normal.normal=type1.Helvetica
    [100609_074840634][][STATEMENT] font.SERIF.italic.bold=type1.Times-BoldItalic
    [100609_074840634][][STATEMENT] font.SERIF.italic.normal=type1.Times-Italic
    [100609_074840635][][STATEMENT] font.SERIF.normal.bold=type1.Times-Bold
    [100609_074840635][][STATEMENT] font.SERIF.normal.normal=type1.Times-Roman
    [100609_074840635][][STATEMENT] font.SYMBOL.normal.normal=type1.Symbol
    [100609_074840636][][STATEMENT] font.TIMES NEW ROMAN.italic.bold=type1.Times-BoldItalic
    [100609_074840636][][STATEMENT] font.TIMES NEW ROMAN.italic.normal=type1.Times-Italic
    [100609_074840636][][STATEMENT] font.TIMES NEW ROMAN.normal.bold=type1.Times-Bold
    [100609_074840637][][STATEMENT] font.TIMES NEW ROMAN.normal.normal=type1.Times-Roman
    [100609_074840637][][STATEMENT] font.TIMES.italic.bold=type1.Times-BoldItalic
    [100609_074840637][][STATEMENT] font.TIMES.italic.normal=type1.Times-Italic
    [100609_074840638][][STATEMENT] font.TIMES.normal.bold=type1.Times-Bold
    [100609_074840638][][STATEMENT] font.TIMES.normal.normal=type1.Times-Roman
    [100609_074840639][][STATEMENT] font.ZAPFDINGBATS.normal.normal=type1.ZapfDingbats
    [100609_074840639][][STATEMENT] pdf-changes-allowed=0
    [100609_074840639][][STATEMENT] pdf-compression=true
    [100609_074840640][][STATEMENT] pdf-enable-accessibility=true
    [100609_074840640][][STATEMENT] pdf-enable-copying=false
    [100609_074840640][][STATEMENT] pdf-encryption-level=0
    [100609_074840641][][STATEMENT] pdf-font-embedding=true
    [100609_074840641][][STATEMENT] pdf-hide-menubar=false
    [100609_074840642][][STATEMENT] pdf-hide-toolbar=false
    [100609_074840642][][STATEMENT] pdf-no-accff=false
    [100609_074840642][][STATEMENT] pdf-no-cceda=false
    [100609_074840643][][STATEMENT] pdf-no-changing-the-document=false
    [100609_074840643][][STATEMENT] pdf-no-printing=false
    [100609_074840643][][STATEMENT] pdf-open-password=
    [100609_074840643][][STATEMENT] pdf-permissions=0
    [100609_074840644][][STATEMENT] pdf-permissions-password=
    [100609_074840644][][STATEMENT] pdf-printing-allowed=0
    [100609_074840645][][STATEMENT] pdf-replace-smartquotes=true
    [100609_074840645][][STATEMENT] pdf-security=false
    [100609_074840645][][STATEMENT] ------------------------------------------------------
    [100609_074840672][][STATEMENT]  Rendering page [1]
    [100609_074840679][oracle.apps.xdo.common.font.FontFactory$FontDef][ERROR] Failed to open TrueType font: /fonts/ALBANWTJ.ttf(0)
    [100609_074840680][oracle.apps.xdo.common.font.FontFactory$FontDef][ERROR] Failed to open Type3 font (SVG embedded): null
    [100609_074840680][][EXCEPTION] Default.normal.normal is invalid. Set it to Helvetica
    [100609_074840681][oracle.apps.xdo.common.font.FontFactory$FontDef][STATEMENT] TrueType font created: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf(0)
    [100609_074840681][oracle.apps.xdo.common.font.FontFactory$FontDef][STATEMENT] TrueType font created: C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf(0)
    [100609_074840692][][STATEMENT] Phase2 time used: 42ms
    [100609_074840692][][STATEMENT]  Continue rendering page [1]
    [100609_074840693][][STATEMENT]  Generating page [1]
    [100609_074840703][][STATEMENT] Phase2 time used: 11ms
    [100609_074840704][][STATEMENT] Total time used: 102ms for processing XSL-FO
    [100609_074840719][oracle.apps.xdo.common.font.FontFactory][STATEMENT] truetype.C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts\ALBANWTJ.ttf closed.
    [100609_074840719][oracle.apps.xdo.common.font.FontFactory][STATEMENT] truetype.C:\Program Files\Java\jre1.6.0_06\lib\fonts\advc128b.ttf closed.
    [100609_074840720][][STATEMENT] FO+Gen time used: 121 msecs
    [100609_074840720][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) is called.
    [100609_074840721][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) done. All inputs are cleared.
    [100609_074840723][oracle.apps.xdo.template.FOProcessor][STATEMENT] End Memory: max=254MB, total=7MB, free=0MB

  • NeoDynamic Barcode Proffessional Upload Error in SSRS Report Server 2012

    Hi,
    I am Developing a SSRS Report for Displaying Barcode . I am Using Neodynamic Barcode Proffessional and the Report is Working fine in Developer Machine (MY Machine). When i try to Upload the Report into SSRS Report Server i get this Error Can any one Help on
    this. Thanks in Advance
    Note : I am Using SSRS 2012 Version and The Report Server is also the Same
    Error : Error while loading code module: ‘Neodynamic.ReportingServices.Barcode, Version=7.0.2000.0, Culture=neutral, PublicKeyToken=c6b33c3093a0d4cd’. Details: Could not load file or assembly 'Neodynamic.ReportingServices.Barcode, Version=7.0.2000.0, Culture=neutral,
    PublicKeyToken=c6b33c3093a0d4cd' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (rsErrorLoadingCodeModule) Get Online HelpError in class instance declaration
    for class Neodynamic.ReportingServices.Barcode: [BC30002] Type 'Neodynamic.ReportingServices.Barcode' is not defined. (rsCompilerErrorInClassInstanceDeclaration) Get Online Help There is an error on line 4 of custom code: [BC30451] Name 'Neodynamic' is not
    declared. (rsCompilerErrorInCode) Get Online Help

    Hi cbazrm,
    According to your description, you add an external assembly to display barcode in your report. It works properly in developing environment. But it throw the above error after deploying onto report server. Right?
    Based on the error message, the report server side doesn't have the assembly added, so it can't use the assembly to render the barcode.
    In this scenario, we should copy the AgeAssembly.dll to the “C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\bin” folder then drag and drop the assembly to the C:\Windows\assembly too.
    Reference:
    SSRS - Custom Code with External Assemblies
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • ADF Faces & BC 10.1.3.4: Barcode Printing & ADF version of WebUtil?

    Hi all,
    Our existing application is built with Oracle Forms/Reports 9i which also uses Oracle WebUtil 10g because we need to print bar code labels. Our oracle forms appilcation invokes "Host" commands which allows it to print directly to the server's printer ports, this is accomplished by invoking WebUtil functionality which somehow bypasses(probably not the correct term to use) the jvm security sandbox. We need to have a similar barcode printing functionality on our ADF Faces/BC application however I'm not aware of the existence of "ADF WebUtil" which can be configured to allow access to printer ports.
    Here is some code snipets for the 9i Forms application for printing (which is done through Internet Explore Browser)
    CLIENT_TEXT_IO.PUT_LINE(myPrinter, output_str);
    If lineType = 'B' Then vertStartTemp := vertStartTemp + vertBStep;
    Else vertStartTemp := vertStartTemp + vertAStep;
    End If;
    End Loop;
    /* last line */
    output_str := 'P1'||chr(13)||chr(10);
    CLIENT_TEXT_IO.PUT_LINE(myPrinter, output_str);
    CLIENT_TEXT_IO.FCLOSE(myPrinter);
    EXCEPTION
    WHEN OTHERS THEN
    CLIENT_TEXT_IO.FCLOSE(myPrinter);
    message(sqlerrm );
    Raise Form_Trigger_Failure;
    END;
    Here is some java code which uses the awt library (only works locally due to jvm secuirty sandbox)
    public void testZebraBarCode(ActionEvent actionEvent) {
    //called from a commandButton action listner. will fail upon deployment to server because its trying to access native resouces.
    try {
    PrintService psZebra = null;
    PrinterJob printJob = PrinterJob.getPrinterJob();
    if (printJob.printDialog()) {
    psZebra = printJob.getPrintService();
    DocPrintJob job = psZebra.createPrintJob();
    String s =
    // Set Reference Point
    // Clear Image Buffer
    // Print direction (from Bottom of buffer)
    // Set label Length and gap
    "R0,0\n" + "N\n" + "ZB\n" + "Q122,16\n" +
    "A160,2,0,3,1,1,N,\"DATA: CARUGATE\"\n" +
    "B160,30,0,1A,2,7,50,N,\"612041600021580109\"\n" +
    "A160,92,0,1,1,1,N,\"AIA AGRICOLA IT.ALIMENT.S - 594679/VR\"\n" +
    "P1\n";
    byte[] by = s.getBytes();
    DocFlavor flavor = DocFlavor.BYTE_ARRAY.AUTOSENSE;
    // MIME type = "application/octet-stream",
    // print data representation class name = "[B" (byte array).
                Doc doc = new SimpleDoc(by, flavor, null);
                job.print(doc, null);
            } catch (PrintException e) {
    e.printStackTrace();
    Can anyone point me to the proper direction on how to accomplish this task?
    Thanks,
    Wes

    Hi,
    if you build a web application then you have to integrate a Swing based Applet to the web age to access the local client. You can't with native web means
    Frank

Maybe you are looking for

  • Icon display in Module pool screen not visible to some users

    Hi, I have added an icon in one of the module pool screen with dynamic quick info.  The page is rendered fine and the info is also displayed well for most users except some.  I can't figure out why the icon is not being displayed for some users. Do s

  • Communication error in login function in windows mobile in sup 2.0

    hello experts, i have developed sample application using sup 2.0 the application works fine for windows I am using windows xp sp3 i refer all the dll required for the application i also configure Active sync 4.5 and Virtual machine 2007 SP1 for windo

  • Anonymous Communication Client-Server

    I need some urgent help.... What socket should i use and how can i change the sender's ip address? I need this for my graduation thesis practical part, for a client who can send packets to a server and viceversa, without awearness of the server where

  • XI content certification - ABAP proxies

    Hi, can we use <b>ABAP proxies</b> in XI content certification ? I mean develop an ABAP proxy in IR that will be generated in ERP and just supply the code for it ? thank you, Regards, michal

  • I Need a Refund!

    Dear Readers, The question of how to request a refund is asked often.  To help find the information and details quickly, here are links to the FAQ articles which explain Skype's refund policies:  https://support.skype.com/en/faq/FA12149/can-i-get​-a-