This means the condition based down payment functionality was designed only for 'real' sales order documents with VBTYP 'C' (order) or VBTYP 'L'(debit memo requests), but NOT for VBTYP ‘G’ (contract). It only works for the document category (VBTYP): Technically speaking, this is due to the standard design in the condition value calculation formula 049 (FV64A049) assigned to condition AZWB. Therefore condition AZWB cannot get determined in the contract. So contract is not supported for the condition based down payment process. Supported sales documents are quotations, orders, and debit memo requests. The answer can be found from the SAP Note 1788841: So now the question comes to why there’s no AZWB got determined in the quantity contract. The pricing type was set as ‘D’ in the copying control, which means there’s no redetermination of AZWB during SO creation. This should not happen, as AZWB is supposed to get determined in SO with value 0.īy taking a look at the document flow again, I noticed the SO was created reference to a quantity contract, after a further check of the copying control settings between Quantity contract -> SO, I’ve figured out why AZWB is missing in the SO. However, in this case, even though customer has activated the business function, after doing the incoming payment for down payment via F-29, the down payment clearing condition AZWB is still not appearing in the subsequent SD billing:Īfter checking the referenced SO 18903, I noticed AZWB doesn’t appear in the SO at all: It’s the technical prerequisite for the condition-based down payment function. I’d just like to share with you about one case that I’ve met before, which shows several points that need to pay attention to when making use of this function.įirst of all, it must be ensured that the business function SD_01 under ENTERPRISE_BUSINESS_FUNCTIONS is activated via T-cd: SFW5. SAP Note 1788841 also provides the basic info regarding this function. For the detailed process flow & customizing regarding the condition-based down payments processing, you may refer to the SAP online help:ĭown Payment Processing (Basis: Document Condition) Here I am not going to explain in details about how does condition-based down payment processing look like or how to customize it, as there’re already enough documentations available. The issue in that case is altogether different.From Enhancement Package 2 for ERP 6.0, SAP has provided an enhancement of the existing down payment processing: condition-based down payment. If there is a correction in quantities, you should ideally be working on your deliveries and not on invoices. This is the case unless you are giving a special credit to all the customer with a specific value. ![]() In order to state the correct reason, you may decide to use some texts in these requests which can be carried to the Credit or Debit notes, which will be created by referencing these requests.Īlso I would prefer the values in credit memos be updated manually and not automatically as the value will be known only after analysing the invoice. In order to rectify the correction in the value, the credit memo request is created. This implies that an invoice for X quantity was created but with incorrect values. The only thing you can change is the value of some condition types so that you can create the credit memo request for the desired value. In this order, it is advisable not to tamper the quantity or material number. If there is a correction to invoice, you should be creating a credit memo request or debit memo request for the invoice you have created. ![]() The credit memo or debit memo (any correction to invoice) is only a correction to invoice and not a correction to quantity. There is some difference in understanding.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |