/IXOS/AX_TRANSFER - Transfer data to ECR-ServerGeneral Material Data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Transfer data from SAP outbox to PDMS context server(s). If a mapping service is specified, only data exported for this mapping service (a mapping service corresponds to a mapping configuration within a specific PDMS context server) will be transferred to this specific context server. When no mapping service is specified, all data in outbox will be selected and transferred to the corresponding PDMS context server(s). The optional parameters insert date and time can be used to further restrict the amount of data transferred (e.g. in order to avoid long running transfers of huge amount of data during initial load).
Data need to be exported from SAP and placed in outbox via a DocuLink view configured for data export. For configuring the DocuLink view for data export a mapping service must be configured that defines which mapping configuration within a specific PDMS context server should be used for data exchange. Furthermore the PDMS context server must be configured accordingly (import & configure certificate user for SAP system, create and configure PDMS user to be used for data exchange, create mapping configuration).
Data is selected from outbox in blocks of records to reduce the amount of memory required in the SAP system. Furthermore selected data is transferred to the PDMS context server in blocks of records to reduce the size of XML requests that are transferred to the server (all records of a transfer block are included in a XML request that is sent to the context server). Selection block size and transfer block size may be different. Default is 1000 records for selection and 100 records for transfer. Usually it should not be necessary to change those defaults.
All records that could be transferred to the context server are deleted from outbox. For each transfer block that could not be transferred to the context server, all records in this transfer block are marked with 'transfer failed' in outbox. These records will be transferred again automatically when starting the next transfer (for this mapping id).
Even though all records of a failed transfer block are marked with 'transfer failed', only one or some of these records may actually caused problems. To determine which record(s) actually caused problems, the information in the SAP application log can be used (start transaction SLG1 and look for object /IXOS/AX). If the record(s) cannot be identified with help of the application log, a new transfer (for this mapping id) can be triggered to send the failed records again. If the transfer block size is reduced, more records (transfer blocks) may be transferred successfully. If the transfer block size is set to 1 only those records that actually caused problems remain in outbox. However setting the transfer block size to a very small number should be handled with care, because this would send a lot of requests to the context server, if a lot of records are available for transfer in the outbox.
Large transfers can be split up in several smaller transfers that are started in parallel processes in order to improve the overall throughput. However it must be ensured that each of the parallel running transfers selects a distinct set of data from outbox. It must also be considered that distinct mapping services could map to the same record types on the context server side. If that is the case, it is crucial that selection criteria used to collect data in the individual mapping service configurations, selects distinct sets of data, because parallel access to one single record on the context server would lead to transfer errors. If for example mapping service MAP1 is configured to select invoices for company code 3000 and mapping service MAP2 uses the same company code 3000 and both use the same context server, each record would be transferred to the context server twice. If on the context server the invoices from MAP1 and MAP2 are mapped to one single record type, one single record within this record type could be accessed in parallel if MAP1 and MAP2 are transferred in parallel processes (even though distinct sets - one for MAP1 and one for MAP2 - are selected from outbox). This would be a misconfiguration!
The number of data records and document links handled by this transfer is displayed. Additionally the number of deleted entries from outbox (records for that transfer succeeded) and number of failed entries (records for that transfer failed) is reported.
BAL_S_LOG - Application Log: Log header data PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 4878 Date: 20191014 Time: 202841 sap01-206 ( 37 ms )
Looking for Support? Questions?
Leave us your contact details and we will call you back. Panels marked with * are mandatory.