The specifics of master data entry for one-time accounts are covered in this blog post. I made the decision to compile my most recent discoveries into a post. If you run into similar problems, I hope it will be interesting to you and maybe even save you some time.
One-time accounts (OTA) are a unique kind of master data for suppliers or clients. One time accounts do not keep any information on the customer or vendor prior to the time the document is created in the system, in contrast to regular master data. During invoice posting, the system can be configured with address information, tax requirements, and bank information.
The benefit of this method is that you can always record an operation with a variety of customers or vendors, even if your system does not yet include a permanent master record for them. It is assumed that you do not intend to continue doing business with this business partner on a regular basis in the future.
Below is a screenshot of the screen where OTA customers enter their master data. Based on FB70 posting, the snapshot was created.
Normally, you can configure a field status group for the customer or vendor to change the selection of the master data fields or to make some of them hidden, optional, or required.
A different reference account group is mentioned in the master record for a one-time customer. The settings from this reference account group will therefore be inherited by any new customers you establish (e.g., DEBI, not from CPD).
T-code OBD2 allows for the maintenance of the customer’s field status group. You may get an overview of the account group DEBI’s settings in the attachment. As can be seen, taxes 1, 2, and 4 are still retained as optional. These tax numbers were available for entry in FB70, as you may have seen in the first screenshot.
I was really aback to see how different the page is for OTA clients entering sales orders. I was unable to enter tax numbers 1, 2, or 4 and my attempts to change the field status group were all unsuccessful. Additionally, entering bank information is not possible. However, I don’t believe that a one-time customer actually needs to provide bank information.
I discovered that the feature for OTA-customers operates slightly differently in logistics after some debugging and study (i.e., in sales in distribution).
The field selection for address data is essentially hard coded, according to OSS note 1798425, “VA01 for CPD client.” The procedure FORM 5000 CAM INIT can be used to manage any implicit enhancements that are made to the address data for OTA-customers (program SAPLV09C, include LV09CF47).
Another OSS note 2185322, “VA01: Customer and Vendor Field Availability,” notes that altering table IDSDTXNUMVIS controls how tax numbers are shown (can be edited via SM30). This table includes a list of typical tax number check boxes that can be selected for each country. For a number of nations, but not all, SAP offers a standard set of options for this table. There were no options for Ukraine in my circumstance.
I was able to enter the required tax numbers once I had added the parameters. See the illustration below.
When you save a sales order, the application automatically generates an address key and stores the address information. In table VBPA, for a suitable partner function that is designated as a “One-time account,” this address key can be found (VBPA-XCPDK).
All other related papers in the sales cycle, such as the delivery and invoicing documents, inherit the address key for the one-time customer.
A sales order is connected to the tax information that is kept in table VBPA3 (and other sales documents as well).
However, there is a problem: certain nations employ extra fields as tax requirements, such as the checkbox “Liable for VAT” (KNA1-STKZU / LFA1-STKZU). In the table IDSDTXNUMVIS, this checkbox is absent. In addition. This field is likewise absent from the table VBPA3, which keeps track of a customer’s one-time tax information. It does not appear to be anything that can be remedied by straightforward improvement at this time. It might be addressed via the SAP incident method.
As long as you enter the client invoice for OTA directly into Finance using FB70, there won’t be a problem because the table BSEC already has the majority of the necessary master data elements:
One final point about the inclusion of tax information for one-time clients. According to OSS Note 361364, “Tax numbers for one-time clients – Legal Changes,” maintaining tax numbers is only possible using the online model; BAPI cannot be used for this.