Kontakt

Ansicht
Dokumentation

J_1UFDI_PROC_IN - Processing Incoming Electronic Files

J_1UFDI_PROC_IN - Processing Incoming Electronic Files

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this program to process incoming and outgoing XML-based files for the Register of Tax Invoices program for Ukraine.

Integration

Prerequisites

  • Check that you have created folders for incoming and outgoing XML-based files and made the settings needed to trigger the program that processes these files. By default, the system uses C:\temp\incoming for incoming files and C:\temp\outgoing for outgoing files.
  • Tax Invoices and Correction Tax Invoices must follow the format requirements set up by the tax authorities.
  • Extract from the Unified Register must contain a list of registered tax invoices and correction tax invoices, and conform to the XML format as defined by law. There are two ways of processing the incoming XML document:
  1. If the incoming XML file is a response to a request that contained a list of tax invoices and correction tax invoices, whose status is checked. For all invoices that are in the file the status is changed to Registered. For those invoices that are not in the file, but that were requested in the same ERPN request (request number and date), the status is changed to Rejected.
  2. If the incoming XML file is a response to a request that contained a list of documents registered in ERPN by a specific date. For all tax invoices and correction tax invoices in XML file the report tries to find a corresponding accounting document using the following data:
  • For incoming invoices: Company Code, Year, Status (should be other than Registered), Document date, Document type, Reference document number (XBLNR field), INN, Branch, Amount

  • For outgoing invoices: Company Code, Year, Status (should be other than Registered), Period, Sequence number, Branch, Document date, Document type, INN, Branch, Amount

If an accounting invoice is found, status is changed to Registered. If an accounting invoice is found but its amount differs, then status is changed to Error. If no accounting invoice is found, then status is not changed and the incoming XML file stays in the initial folder (C:\temp\incoming by default).
  • The XML-based file for the Electronic VAT Administration Extract must adhere to the legal structure requirements. The system compares the Company Code (based on INN code and Branch in the Extract) and Fiscal Year (based on date of the Extract) to those in the Manage Electronic VAT Extracts (transaction J1UFDIVATADMV) activity. If there is no data for this Company Code - Fiscal Year combination, the system creates a new entry for it, and if there is existing data, the system either updates existing data or produces an error.
The system will update existing data if:
  • The date of the Extract is later than that in the activity, or

  • The Extract number and date and time of Request to ERPN in the Extract do not match those in the activity, but the time stamp of the Extract is later than that in the activity.

The system will produce an error if:
  • The date of the Extract is earlier than that in the activity, or

  • The Extract number and date and time of Request to ERPN in the Extract match those in the activity and/or the time stamp of the Extract is earlier than that in the activity.

  • Confirmation of delivery to ERPN must be in .DOC, .RTF, .TXT or .RPL format. The file name must contain the name of the XML-based file (without its extension) that we sent to ERPN. The XML-based file name must also be included in the confirmation file. The file must also contain the appropriate text in Ukrainian ("Zvit dostavleno" in Cyrillic characters). Status of the corresponding tax documents in the Register is changed to Delivered.
  • Registration notification from ERPN must be in .DOC, .RTF, .TXT, .RPL or .XML format. The file name must contain the name of the XML-based file (without its extension) that we sent to ERPN. The XML-based file name must also be included in the confirmation file. The file must also contain the appropriate text in Ukrainian ("DOKUMENT NE PRIYNYATO" in Cyrillic characters if the document has been rejected or "DOKUMENT PRIYNYATO" in Cyrillic characters if the document has been registered). If the text mentions that the document was registered, then status of the corresponding tax document in the Register is changed to Registered. If the text mentions that the document was rejected, then status of the corresponding tax document in the Register is changed to Rejected.
  • If a document was marked as Registered by ERPN but XML data of the document differs from the data provided in the registration notification (document date, document sequence number / activity / branch, document total amount and document VAT amount), document registration status will be changed to Error.
  • If a registration notification or Extract from the Unified Register is received for an outgoing tax invoice with tax reason code 14* (import of services by non-resident vendors), then the system selects an incoming tax invoice.
  • If the posting period and year of an incoming parked negative tax invoice are not equal to its registration period and year in the registration notification, then the posting date and year are overwritten with the registration period and year.
  • If the posting period and year of an incoming parked non-negative tax invoice are less than its registration period and year in the registration notification and the difference is more than 15 days, then the posting date and year are overwritten with the registration period and year.
  • If the posting period and year of an outgoing parked negative tax invoice is not equal to its registration period and year in the registration notification, then the posting date and year are overwritten with the registration period and year.

Features

You can use the program to do the following:

  • Read the contents of the upload folder
  • Process the read content
  • Save the XML files to the system if they meet the requirements below
  • Check the XML files against the accounting documents included in the register by Company Code, Fiscal Year, Document Type (tax invoice or corrective tax invoice) and header data. If there is a match of one XML file and one accounting document, the program creates a link automatically. If not, it produces an error and writes it to the log
  • Change some of the statuses

Selection

On the selection screen, enter the maximum number of files to process and set the source folder.

Standard Variants

Output

The program outputs an output screen with the number of files processed successfully or with errors. The system saves information into a log that can be accessed via the Analyze Application Log (transaction SLG1) program.

Activities

To access the report on the SAP Easy Access screen, choose Accounting → Financial Accounting → General Ledger → Reporting → Tax Reports → Ukraine → VAT → Process XML Files (transaction J1UFDIPROCIN).

Example






Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 8509 Date: 20240531 Time: 041038     sap01-206 ( 160 ms )