There is no transaction process.
There is an open log file.
This entry point is always called when sending a document to EFAT.
The variable EFAT_DATA_EMAIL_TO already has the email address where the file will be sent.
You can overwrite this variable or add new emails, separated by a semicolon (;).
In the table below, the Significant content setting indicates that the content is in phase with the context. That is, the current invoice is loaded.
Table | Significant content | Table title |
COMPANY | Yes | Company |
SINVOICE | Yes | Invoice headers |
Use this to change the report code in the WARP_RPTCOD variable.
There is no transaction process.
There is an open log file.
This entry point is always called when sending a document to EFAT.
The variable WARP_RPTCOD already has the report code of the report that will be printed.
This variable can be overwritten.
Variable or mask | Definition |
WARP_RPTCOD | Local variable storing report code to be used in EFAT |
In the table below, the Significant content setting indicates that the content is in phase with the context. That is, the current invoice is loaded.
Table | Significant content | Table title |
COMPANY | Yes | Company |
SINVOICE | Yes | Invoice headers |
TABPRTMOD | Yes | Print template table |
Use this entry point to customize the name of the company that goes on the final email to the customer.
There is no transaction process.
There is an open log file.
The variable [L]EFAT_SPE_CPYNAM is available.
After the entry point is finished, the company name changes to the value in the variable. If the variable is empty, the value in GESCPY is used.