Customizing SAP ERP for eDocument - Peru

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 transaction FIBF 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 eDocument General Settings End of the navigation path :

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).
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).
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 Blling Document Type (TVFKEDOCV)
For an eDocument Type, you define which process statuses are assigned to which eDocument status. You do this in Assign eDocument Status to Process Status (EDOMETASTATDETV).

Customizing for Full Solution

In addition to the above mentioned Customizing activities, for the Full solution maintain the following activities in Customizing for eDocuments under Start of the navigation path Cross-Application Components Next navigation step General Application Functions eDocument General Settings End of the navigation path :

You activate specific fields in the Create and Submit eDocument report in Activate Solution Specific Fields (EDOCOUNTRYSOLV). By default, only the fields for the Basic solution are activated.
You define SOA services to logical ports in Define SOA Services for Communication (EDOSOASERV).
You assign SOA services to eDocument interfaces in Assign SOA Services to eDocument Interfaces (EDOINTV).

If it occurs that it is temporarily not possible to submit eDocuments to the tax authority, you can define that certain eDocument types they are created in contingency modus. You do that in the Activate Contingency for eDocument Types activity.

Business 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 eDocument General Settings 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.

Define Partner Connector (EDOC_PARTNER_CONNECTOR): You use this BAdI to implement your own customer-specific solution to send eDocuments to your customers.

Note Note

For Peru, you can implement the GET_VARIABLE_KEY method of the eDocument Adaptor BAdI (EDOC_ADAPTOR) to give you more flexibility when defining the document numbering strategy used in your company. Refer to BAdI method documentation direct in the system for more information on its implementation.

End of the note.

Refer to the BAdI implementation documentation as well as the corresponding BAdI Methods documentation for more detailed information.

Peru-Specific Settings

In addition to the general settings mentioned above, you make settings which are specific for Peru in Customizing for eDocuments under Start of the navigation path Cross-Application Components Next navigation step General Application Functions eDocument Country-Specific Settings Peru End of the navigation path :

You define the rules for the document numbering as required by the tax authorities in the following activities:

Define Series for eDocument Numbering (EDOPESERIESV)
Define Number Groups for eDocument Numbering (EDOPENUMGRV)
Assign Number Group to Company Code and Series (EDOPENGRASSIGNV)
Maintain Number Ranges for eDocument Numbering (EDOC_PERU_NUMBER transaction)
Assign Number Ranges to Document Types (EDOPENUMBERV)

For more information on how the system numbers the eDocuments, see eDocument Numbering.