Ansicht
Dokumentation

SIPT_SDT_SD_V - Define Special Scenario Document Types (SD)

SIPT_SDT_SD_V - Define Special Scenario Document Types (SD)

General Data in Customer Master   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

In this activity, you define how the system handles print forms for SD billing documents for Portugal.

To ensure that the print forms for your invoices are compliant with Portuguese regulations, you maintain settings for the following special scenarios:

  • Recovery documents: Documents that were lost in a database crash but later entered in the system from paper backup.
  • Manual documents: Documents that were written by hand during any system downtime and were later manually entered in the system.
  • Interface documents: Documents that were imported from external systems.

When you print your invoice, the system checks the settings in this activity to see if the billing document that is printed falls into one of these scenarios. When it does, the printout form states that it is a copy, even if it is the first printout.

To enable invoices to use this printing output, do the following:

  1. In the Billing Type column, enter a billing type that is used for the special printing scenario.
  2. In the Doc. Type column, choose the scenario for the document (recovery, manual, or interface).
  3. In the Document Number Field column, choose the field from which the system obtains the original document number information that is printed on the invoice (relevant only for Recoveryand Manualdocument types)

Note

For interface documents, the system checks table SIPT_IF_VBRK for the original digital signature, invoice number, invoice date, and certificate ID. In this table, you must maintain the information for interface documents. If you do not, the system will not print out the document.

Table SIPT_IF_VBRK is used in 2 processes related to the posting of interface documents and external documents:

  • Interface documents - delivered with SAP Note 2166344
    With internal digital signature: Tables SIPT_VBRK and SIPT_IF_VBRK are filled. Data is filled in SIPT_IF_VBRK by custom development.
  • During reporting, the system derives the digital signature and ATCUD from the corresponding fields in SIPT_IF_VBRK.

Caution

  • Don't use the same billing type for external postings with and without digital signature.
  • Don't use the same billing type for internal and external postings.
  • Don't change the assignment in this activity after you've initiated the corresponding series by posting a document. Changing or deleting the assignment after posting can lead to inconsistencies, including the handling of ATCUD for the series. If issues occur, stop the number range, don't use the interval anymore, and restart with a new interval.
  • Don’t request the ATCUD for interface documents. You transfer the ATCUD for interface documents from the external system. Therefore, make sure you assign a series to this leading billing type that doesn't require ATCUD and doesn't adhere to the naming conventions for ATCUD, for example, 0001.
  • You can request the ATCUD for recovery documents and manual documents.






General Data in Customer Master   General Material Data  
This documentation is copyright by SAP AG.

Length: 4088 Date: 20240523 Time: 180123     sap01-206 ( 68 ms )