Transaction Type 1: To fill Material Type Description: Fill Reference material type. Scenario/Usage: To identify Product Type (of the materials from the complete product data) IMPORT PARAMETERS: WA_MASTER (Allows MATNR, MAKTL, MAKTX, and EAN11 to be available to identify the corresponding PRODUCT_TYPE) EXPORT PARAMERTERS: WA_MASTER-MTREF Report would send complete product data (matnr, matkl, maktx, ean11 in the work area wa_master); exit should then fetch mtref from customer specific coding and fill up the user exit’s export parameter product_type in the user exit. -------------------------------------------------------------------------------------------------------------------------------- Transaction Type 2: To set description of Transactions in Fi Section of XML file. Scenario: Used to set the description of transactions. Import Parameters: wa_master Export Parameters: tdgl_desc Pass the description of transaction in the parameter tdgl_desc. -------------------------------------------------------------------------------------------------------------------------------- Transaction Type 3: To map the correct Invoice Type of Billing Documents. Scenario: Invoice Type mapping The customer has some set of document types specifically for the invoice, but this is not same as ones described by the DGCI Authorities and hence needs to be map customer specific invoice type values to Tax Authority Specific Values XML field: InvoiceType Solution: User Exit Option provided to map customer specific Invoice Types to the Tax Authorities specified Types. Use Transaction Type = ‘3’ to map the customer specific values to Tax Authorities specified values
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Transaction Type 1: To fill Material Type
Description: Fill Reference material type.
Scenario/Usage:
To identify Product Type (of the materials from the complete product data)
IMPORT PARAMETERS: WA_MASTER
(Allows MATNR, MAKTL, MAKTX, and EAN11 to be available to identify the corresponding
PRODUCT_TYPE)
EXPORT PARAMERTERS: WA_MASTER-MTREF
Report would send complete product data (matnr, matkl, maktx, ean11 in the work area
wa_master); exit should then fetch mtref from customer specific coding and fill up the user exit’s
Transaction Type 3: To map the correct Invoice Type of Billing Documents.
Scenario: Invoice Type mapping The customer has some set of document types specifically for the invoice, but this is not same as ones described by the DGCI Authorities and hence needs to be map customer specific invoice type values to Tax Authority Specific Values XML field: InvoiceType Solution: User Exit Option provided to map customer specific Invoice Types to the Tax Authorities specified Types. Use Transaction Type = ‘3’ to map the customer specific values to Tax Authorities specified values
Transaction Type 4: To fetch the customer details for the master section.
Description: Reading customer specific name ( 1 to 4 ). Import Parameter: WA_MASTER Parameters available: ALL CUSTOMER MASTER INFORMATION Export Parameter: WA_MASTER_CP Scenario /Usage:
Allows to retrieve customer details , if has to deviate from generic fetch Customer specific values can be retrieved and populated to the new work area:
WA_MASTER_CP, which has exactly the same structure definition as WA_MASTER.
If WA_MASTER_CP is populated, these values will be considered for customer data population for the XML creation.
Transaction Type 5: To fetch the vendor details for the master section.
Description: Reading customer specific name ( 1 to 4 ). Import Parameter: WA_MASTER Parameters available: ALL Vendor MASTER INFORMATION Export Parameter: WA_MASTER_CP Scenario /Usage:
Allows to retrieve vendor details , if has to deviate from the generic fetch Vendor specific values can be retrieved and populated to the new work area:
WA_MASTER_CP, which has exactly the same structure definition as WA_MASTER. If WA_MASTER_CP is populated, these values will be considered for vendor master names population for the XML creation
Transaction Type 6: To set the customer specific debit/credit amounts.
Report will pass document details in the work area wa_master, exit should then copy this data into one more work area of the exit - wa_master_cp and then fill up the fields sd_dr_amount/ sd_cr_amount of wa_master_cp based on customer specific VBTYP.
Transaction Type 10: To set the customer specific Condition Type and Settlement Amount.
Refer note : 1300586 for more details on this. If customers use kntyp as ‘E’ but a different kschl which is part of condition record for the document, it would be sufficient to pass kschl into the user exit’s export parameter product_type. If customers don’t use kntyp as ‘E’ then exit has to pass the line settelemnt amount in the user exit’s export parameter wrk_amount.
To identify FI invoices other than using “SD00” and document types Wa_master has the information based on current line item being processed and also the document header. CALL FUNCTION 'PT_USER_EXIT_DART'
EXPORTING
wa_master = wa_master
transaction_type = '20'
wa_fi_hd = wa_fi_hd
IMPORTING
invoice_type = tdglsedc.
Pass “Y” to invoice_type value from the user exit, if the document is a manual FI invoice to be considered for the XML creation
Transaction Type 22: To set the Numbering Seies of SD documents.
Report will pass document details in the work area wa_master, exit should then send the “Numbering series” to the user exit’s export parameter “tdgl_desc” so that this can be concatenated to invoice number filed of the XML file.
Transaction Type 25: To set the Payment Payment Mechanism
Report fill up this field with values ‘TB’ or ‘CH’ based on zlsch(Payment Method) from VBRK values T and C. For user specific types, exit will be called and based on billing document details from the work area wa_master, customer specific PaymentMechanism has to be filled in the user exit’s export parameter tdgl_desc.
Transaction Type 27: For Material Master Data Creation(FI invoices)
The materials have to be identified explicitly in the cases where it is not a part of the standard
MARA tables
SAFTPT_FIMD(G/L account based material identification) And PTSAFT_MATPRE (SAFT PT: prefix for material numbers) of company code Combinations.
The materials are provided in each line item of Accounting document(TEXT) as shown Below VF3WC8HZC9E043129 – is the product description, but a product code associated with this cannot be identified from any of the 3 options mentioned above
Pre-Requisites Pre-requisites before the user exit can be made use of Product Code 1. Customers should have mechanism to relate the product description to a product code via creating & maintaining customer specific tables 2. Customer needs to maintain code for retrieving data based on the data maintained in the customer specific table and for the transaction type = 27 in the user exit Function module parameters available for material identification INPUT/ IMPORTING PARAMETERS TO FUNCTION MODULE
WA_MASTER
TRANSACTION_TYPE = 27
OUTPUT / exporting (tables) parameters from function module
Materials identified to be part of XML file to be filled in an internal table with type SAFTPT_PRODS Need to pass to report the following values
MATNR (Material Number)
MTREF (Reference material type)
CNAME1(Material Group Description)
MAKTX(Material Description (Short Text))
EAN11(International Article Number (EAN/UPC),if available
Transaction Type 28: Product Code is empty always for manual FI invoices
Description: Product code and description are derived based on line item description when sales invoices are generated from FI module directly. The user exit is required to include the materials derived from line item description, when the materials used in the manual invoice cannot be identified by contract type or by the G/L accounts to which it is being posted to. Line item descriptions provided in the accounting document is taken as the product description. Scenario: Each FI invoice will have the product description mentioned in the line item description .From this, it’s not possible to identify a product code to be made available in XML file -How to use the user exit in SourceDocuments sections Pre-requisites 1. Customers should a. Maintain the product code/product description data in customer specific tables (or) b. Have logic to identify product code from line item descriptions 2. Use the transaction type = 28 to retrieve or maintain logic for product code /product description in case of SourceDocuments section(FISD_RE) Function module parameters available for material identification
Importing parameters/ inputs to function module
Wa_master ( provides all information including the line item number which is being currently processed WA_MASTER-POSNR)
Document header – based on which the line items have to be retrieved and corresponding descriptions identified
OUTPUT / exporting (tables) parameters from function module PROD_CODE => PRODUCT CODE PROD_DESCRIPTION => PRODUCT DESCRIPTION --------------------------------------------------------------------------------------------------------------------------------
Transaction Type 31: To set the Exchange rate for Billing Documents
Scenario:
If exchange rate in FI document differs from SD invoice, then populate the user exit to pass the
Transaction Type 35: Invalid Line Items to be ignored from SD document.
Purpose of User Exit: Only valid line items are reported, especially when sub item are present for a main invoice line item which will bear more details of the main line item. When these lines items need to be ignored, the user exit can be used. When the main line item has to avoided and all sub items are to be reported in SAF-T, in cases where the sub items bear information relevant for reporting and main line item is just a dummy/summary of information this can be used IMPORT PARAMETRS: a. INVOICE NUMBER: WA_MASTER-VBELN
b. INVOICE LINE ITEM NUMBER: WA_MASTER-POSNR
c. INVOICE TYPE: WA_MASTER-FKART EXPORT PARAMETERS: TDGLSEDC AS SPACE OR CLEARED as TDGLSEDC should be ‘X’ for all valid line items , which will be the default value. When the line item has to be excluded, then this value has to be cleared and exported back to the report Invoked at subroutines : create_bidata_items ,Calculate_totals
Transaction Type 54: To set the correct Address Details.
Scenario: Inconsistent address details were reported in source documents <SHIPTO> section of the SAFT XML file when customer address detail gets changed over a period of time. Though, this change information is available in the change tables CDHDR and CDPOS, it is too costly for us to consider this in the standard report, considering the fact that many customers will not have this case.
Input Parameters: wa_master wa_bi_hd Expected values from the exit: Parameter tdglsedc = 'X' “wa_master_export-st_ort01” for city “wa_master_export-st_stras” for address detail “wa_master_export-st_land1” for country “wa_master_export-st_pstlz” for postal code
1. When a plant has more than one storage location; then Ship from address details populated in
SD section is inconsistent. We only read address information of plant. So if customers have
multiple storage locations for a plant and if they want that information to be reported, then this
exit has to be implemented and the values should be populated in the below parameters.
Input Parameters: wa_master wa_bi_hd Expected values from the exit: Parameter tdglsedc = 'SL' “wa_master_export-sf_ort01” for city “wa_master_export-sf_stras” for address detail “wa_master_export-sf_land1” for country “wa_master_export-sf_pstlz” for postal code
2. In source document section of the file for the tag <CustomerID>, by default SHIP-TO Party will be reported. Few customers wanted Payer ID to be reported instead. In such case this exit has to be implemented.
Input Parameters: wa_master wa_bi_hd
Expected values from the exit: Parameter tdglsedc = 'SL' Parameter “KUNRG” for populating Payer ID in XML file.
Transaction Type 60: To populate the tax information if 3rd party tax engine is used.
Scenario: To populate Tax Information in source document section of the file when customers are using an
external (3rd party) tax engine such as SABRIX to calculate taxes. [For SD Invoices]
Input Parameters: wa_master wa_bi_hd Expected values from the exit: Parameter tdglsedc = 'X' "wa_master_export-md_tax_percntg" for tax percentage "wa_master_export-md_tax_type" for tax type "wa_master_export-md_taxcountryregion" for tax country region "wa_master_export-md_tax_code" for tax code "wa_master_export-md_tax_desc1" for tax code description "wa_master_export-md_tax_exp_date" for tax expiration date "wa_master_export-md_tax_amount" for tax amount "wa_master_export-md_tax_exempt_reason" for tax exemption reason
Transaction Type 61: To populate the tax information if 3rd party tax engine is used for manual FI
invoices.
Scenario: To populate Tax Information in source document section of the file when customers are using an
external (3rd party) tax engine such as SABRIX to calculate taxes. [For Manual FI Invoices]
Input Parameters: wa_master wa_bi_hd Expected values from the exit: Parameter tdglsedc = 'X' "wa_master_export-md_tax_percntg" for tax percentage "wa_master_export-md_tax_type" for tax type "wa_master_export-md_taxcountryregion" for tax country region "wa_master_export-md_tax_code" for tax code
"wa_master_export-md_tax_desc1" for tax code description "wa_master_export-md_tax_exp_date" for tax expiration date "wa_master_export-md_tax_amount" for tax amount "wa_master_export-md_tax_exempt_reason" for tax exemption reason
Transaction Type 77: To identify archived documents.
Scenario: Duplication of Invoices in the SAFT XML file if the underlying accounting documents of invoices are archived. So this exit has been provided for customers to identify such accounting documents that are archived, thereby avoiding the invoices being duplicated in SAFT XML file.
Expected values from the exit: Parameter e_archive = 'X' --------------------------------------------------------------------------------------------------------------------------------
Transaction Type 79: To change Tax Point Date
Import Parameters:
wa_master
wa_bi_hd
Export Parameter:
GL_DATE
Usage: If you want to display different Tax Pointing Date, then pass the value to the parameter