Show TOC

Background documentationData Extraction from Interactive PDF-Based Print Forms

 

You program the data transfer from interactive PDF-based print forms as follows:

  1. Create a public instance method in a global or a local class. You can choose any name for the technical name. The instance generation of the class must be public and the constructor is not allowed to have any parameters.

  2. Define the signature of the method for the data transfer as follows:

    Import Parameters

    • io_log as reference to the interface if_fkk_corr_log

    • The parameters of the form interface, in which you expect the entered data

    • iv_simulation_run of type ifp_dte_simulation_run, to display if a simulation should be executed.

      If the parameter is set (abap_true), you are not allowed to make any changes in the method. If the parameter is not entered, the method is not called during the simulation if the transfer of the document is requested.

    • iv_document of type xstring

    • iv_document_type of type ifp_dte_document_type

    Class-Based Exception

    • cx_ifp_failure

    To add messages to the log, use the methods of the logging interface of correspondence. The parameter io_log provides the reference to this interface.

    If you recognize an error that should lead to the termination of processing of a data record, trigger a class-based exception. You create your own class-based exceptions using the T100 interface. These exceptions must inherit from class cx_ifp_failure. Inbound processing automatically copies the message contained in the exception to the log.

    Example Example

    End of the example.

  3. The static method S_GET of class CL_IFP_DOCUMENT_FACTORY makes a reference available to the interface IF_IFP_EXTRACT_DATA. This interface offers a number of methods for accessing the document processor. You can use these methods to provide, for example, the following:

    • The document

    • The extracted XML data

    • The name of the underlying form

    For more information, see Integrating the Inbound Processing Processor in Your Own Programs.