Function documentationCustomizing SAP ERP for eDocument - Slovenia

 

General Settings

Regardless of which eDocument solution variant you are implementing in your system, you make the following settings:

Business Transaction Events (BTE)

You activate the BTE for the EDOC SAP application using the FIBF transaction in the SAP Menu.

Customzing

You make the following settings in Customizing for eDocuments under Start of the navigation path Cross-Application Components Next navigation step General Application Functions Next navigation step eDocument End of the navigation path:

  1. For a company code, you activate the types of source documents for which you want eDocuments to be created in Activate Source Type Documents for Company Code (EDOCOMPANYACTIV).

  2. You select the interface type that calls the eDocument solution variant that you want to use for the generation of eDocuments in the Define Interface Type for eDocument (EDOINTTYPEV).

  3. You assign eDocument types to the relevant source document types in the following Customizing activities:

    • Assign eDocument Type to Accounting Document Type (T003EDOCV)

    • Assign eDocument Type to Delivery Type (TVLKEDOCV)

    • Assign eDocument Type to Billing Document Type (TVFKEDOCV). You use this Customizing activity to maintain billing documents which are not relevant for accounting, such as proforma invoices, in the

Business and Add-Ins (BAdIs)

The Business Add-Ins (BAdIs) relevant for all eDocument solution variants are contained in the ES_EDOCUMENT enhancement spot.

You implement the following BAdIs in Customizing for eDocuments under Start of the navigation path Cross-Application Components Next navigation step General Application Functions Next navigation step eDocument Next navigation step General Settings Next navigation step Business Add-Ins End of the navigation path:

  • Enhancements for eDocument BAdI (EDOC_ADAPTOR): You use this BAdI to define customer-specific rules for the generation of eDocuments.

  • Define Interface Connector for eDocument BAdI (EDOC_INTERFACE_CONNECTOR) You use this BAdI to define the communication process you want to use for transferring eDocuments over to external or tax authorities’ systems. The implementation of this BAdI varies depending on which eDocument solution variant you are using.

Country-Specific Settings

For the Cash Invoice Registration scenario, you make the following settings in Customizing for eDocuments under Start of the navigation path Cross-Application Components Next navigation step General Application Functions Next navigation step eDocument Next navigation step Country-Specific Settings Next navigation step Slovenia End of the navigation path

  • Enter the Tax IDs of the operators of cash machines in Maintain Operator Tax's ID (EDOSVNOPV).

  • Create number groups for the cash invoice documents in Create Number Groups (EDOSVNNUMGRPV).

  • Define Number Range Object EDOC_SVN for the cash invoice documents in the Define Number Range Object (SNRO).

  • Create and maintain the data of your business premises where you issue cash invoices in the Maintain Business Premises cluster view (EDOSVNBPMVC).

  • Maintain the data of your electronic devices in Maintain Electronic Devices.

  • Generate the ZOI code to be inserted in the eDocument. For that, you Implement the Generate ZOI code (GENERATE_ZOI_CODE) BAdI method of the eDocument Slovenia Enhancements (BADI_EDOCUMENT_SVN) BAdI.

Additionally, each user who operates a cash point needs to assign himself or herself to an electronic device of a business premise. In SAP Easy Access Menu, go to Start of the navigation path Cross-Application Components Next navigation step eDocument Next navigation step Slovenia Next navigation step Operator Assignment. End of the navigation path. or use the EDOC_OP_ASGMNT transaction.

Settings for For Utilities Industry Solution (IS-U)

The following settings are required to enable IS-U Invoices as source documents for the creation of eDocuments:

  1. Function Module for printing:

    For IS-U invoices, in transaction FQEVENTS assign the function module EDOC_ISU_R394 to event the R394. For more information, see the SAP Note 2058588Information published on SAP site.

  2. Add eDocument field in Contract Account Level:

    Add the eInvoice Reference field (EINV_REFERENCE) in Contract Account and maintain it in master data for your contract accounts. For more information, see SAP Note 2059978Information published on SAP site.

For more information about IS-U invoices, see the application help at https:/help.sap.com under Start of the navigation path Enterprise Management Next navigation step SAP ERP Next navigation step Application Help (English) Next navigation step Industries in SAP ERP Next navigation step SAP Utilities Next navigation step Invoicing End of the navigation path.