Process Flow of Document Transfer without Revenue Item 

Process Flow

The function module FKK_EBS_TOI_IDOC_INPUT_COPA processes the IDocs as follows:

       1.      Assignment of a reconciliation key

¡        Call via parallelization tool

¡        Use of the reconciliation key assigned per job (event 2401)

¡        Direct call of IDoc processing

¡        Assignment of a reconciliation key per run (event 2401)

       2.      Start of mass run
Call of standard function module FKK_CREATE_DOC_MASS_START

       3.      Conversion of data to SAP format

¡        Translation of IDoc data without structure using the relevant segment definitions

¡        Execution of any necessary format conversions and checks

       4.      Processing of segment E1FKK_EBS_TOI_HEADER, creation of header item FKKKO and addition of following data (document header table DFKKKO):

Field	Note
XBLNR, BLDAT, BUDAT, WAERS, AWKEY	Fields are filled with IDoc data in segment E1FKK_EBS_TOI_HEADER
AWSYS	Partner number from IDoc control record; agrees with the partner number in the partner agreement
BLART	Customizing information (Data Transfer ® Communication with External Billing Systems ® Transfer of Accounting Documents ® Basic Settings for Document Transfer)
FIKEY	Reconciliation key is assigned automatically
AWTYP	IDOCB (constant)
HERKF	70 (constant)
APPLK	For example, T for industry component Telecommunications
ERNAM, CPUDT, CPUTM	System fields

       5.      Processing of the IDoc segment E1FKK_EBS_TOI_ITEMS of IDoc type FKK_EBS_TOI_COPA, creation of header item FKKKO, and addition of following data in the line items (table DFKKOP):

Field	Note
APPLK, BLART, BLDAT, BUDAT, WAERS	Read from document header (table DFKKKO)
VKONT	Determination using contract account identifier (CTRACT_ID in IDoc) (see Customizing)
GPART, KOFIZ	Determination from contract account definition
BUKRS, HVORG, TVORG, SPART, GSBER	Determination in event 2417 In the standard the data is determined from Customizing information (Data Transfer ® Communication with External Billing Systems ® Transfer of Invoice Documents ® Define Translation of External Item IDs) POS_ID1 – POS_ID5 from the IDoc item data give the key for the table entry
MWSKZ	Determination from item data by function module
ADD_REFOBJ, ADD_REFOBJ_ID	IDoc data, only relevant for IS-T
FINREY	IDoc data

For more information about account determination during the creation of the business partner item, see Account Determination.

¡        Conversion and addition of data analog to function module FKK_EBS_TOI_IDOC_INPUT

¡        Determination of taxes at item level – if any exist – via the internal tax calculation (call event 1110) and comparison with taxes of IDoc segment of type E1IFKK_EBS_TOI_TAX – if it exists (event 2406).

       6.      Check for IDoc segment of type E1FKK_EBS_TOI_COPA
Value transfer (quantity and unit of measurement) – if they exist – and internal characteristic assignment based on the settings in Customizing (Data Transfer ® Communication with External Billing Systems ® Transfer of Accounting Documents ® Define Characteristic Derivations for CO-PA Update). To consider CO account assignments (for example, cost center) in the derivation, event 2414 is called; here you have to fill the fields accordingly.

       7.      Check for IDoc segment of type E1FKK_EBS_TOI_COPA_ITEM
If available, value transfer and internal characteristic assignment based on the settings in Customizing (see point 6); possible customer-specific derivations via event modules; assignment to event 2407.
When you post a document, the operating concern defines with which characteristics the document can be posted. In the characteristic derivation, the CO-PA import structure COPABBSEG is filled with characteristic values. The account assignment object number PAOBJNR is generated from this. In the interface, there is a distinction between the internal and external characteristic assignment. Internal characteristic assignment takes place if the segment E1FKK_EBS_TOI_COPA exists. The internal structure FKK_COPACRIT is filled with characteristic values from the structures FKKOP, FKKKO, and FKKVKP and the business partner data automatically. On the basis of the Customizing setting (see point 6), this data is then copied into the CO-PA import structure COPABBSEG. Some CO-PA-relevant characteristic values are set internally automatically in the program.
If the segment E1FKK_EBS_TOI_COPA contains one or more same level segments of the type E1FKK_EBS_TOI_COPA_ITEM, there is an external characteristic assignment for each one of these segments. To do this event 2407 is called; here you have to transfer the external characteristic value to the CO-PA import structure COPABBSEG. For this purpose the characteristic values are assigned on the basis of the entries in table FKK_EBS_TOI_COPA in the sample function module FKK_EBS_TOI_COPA_DET_2407. In event 2407 you can also access the FKKOP item. This enables you, for example, to transport additional data in a customer include.
Based on these characteristics/characteristic value combination, the CO-PA PAOBJNR is determined; it is saved in an interim table with additional account assignment information. Alternatively, you can also use a project-specific IDoc segment for the transfer of CO-PA data from an external system (see Project-Specific CO-PA Data Segment). For detailed information about using CO-PA, see Enhancement of the CO-PA Interface.

       8.      Creation of general ledger item
A revenue item is created for each business partner item and tax item. Event 1100 is called for this. You add CO-PA additional account assignments from Customizing in this event analog to the default account assignments in the CO-PA account assignment derivation. The account assignment information is copied from the interim table to the G/L items. The business partners are summarized if you have configured this in Customizing (Data Transfer ® Communication with External Billing Systems ® Transfer of Accounting Documents ® Basic Settings for Document Transfer).

       9.      Check the tax data at document level if segment E1FKK_EBS_TOI_TAX_ALL exists
The tax items calculated internally at document level are deleted. By calling event 1110, an internal total tax item is created based on the entries in the internal table FKKOP. The tax comparison (internal-external) at document level is implemented in event 2405 and can be replaced by a customer-specific function module.

   10.      Subsequent processing of the entries in the internal tables FKKKO, FKKOP, and FKKOPK
The subsequent processing takes place in event 2408. As sample implementation, SAP delivers the function module FKK_EBS_TOI_CHECK_EXT_FIN_2408. This summarizes the G/L items dependent on the settings for summarization.

   11.      Post documents
The complete data is posted in function module FKK_CREATE_DOC_MASS. There is always a distinction between internal and external number assignment dependent on the Customizing settings. If external number assignment is defined in Customizing, the invoice document number (XBLNR) is automatically the document number (OPBEL).