![]() ![]() 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. This can make XR1-XR6 base value as either negative or less than XR1-XR6 tax value and because of this accounting document is not getting posted error message Inconsistent amounts (F5 704).Īny idea how the tax condition base value is changing from credit memo request to credit memo? Pricing type in copy control is maintained as N.From Enhancement Package 2 for ERP 6.0, SAP has provided an enhancement of the existing down payment processing: condition-based down payment. Now issue comes when credit memo is created then system is considering condition base value for XR1-XR6 as ZR00 minus the deactivated HA00 value. When tax is calculated in credit memo request then the condition base value for XR1-XR6 is ZR00 condition value and this is correct. So in this case system will ignore PR00 and HA00 and ZR00 will become the net value. Now if user enters ZR00 manually then PR00 will obviously become inactive since only one condition class B can be active. ![]() In my credit memo request PR00 will be determined automatically by condition record and HA00 is calculated based on PR00. I also have header discount condition type HA00. It is entered manually by user in credit memo request. In my credit memo request pricing procedure I have condition type ZR00 which has condition class B (Prices). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |