Workflow functionality for condition contracts can be achieved in a few configuration steps. Each type of settlement document performs the costing procedure (if accounting is to be settled) and presents two different pricing methods in the following, one for regular discounts (ZUK002) and the other for delta provisions (ZUK003). Since ZU3 is the condition that has a value of the business volume update, ZUC1/ZUC2 are conditions specified in the condition contract. In the treatment of accrual accounts, the ZUX1 condition has the value of the provisions already processed in the delta regulation, then the ZAC3 condition is a copy of the ZUC3 condition, but without provisions, which is defined in a condition type and uses ZUC3 AS the reference condition. If the sales document was created before the contract was created, the discount is provided as part of the invoicing process and the discount condition will be visible in the credit note that displays the correct accumulation amount on the respective accounts. It is therefore no longer necessary to resume the sales order. I can create the condition contract and my order now reflects the REA1 condition, and the discount percentage is selected from the contract created in the previous step. The condition tables also contain the entries we created. As we move from the world of ERP business combination to the world of S/4 HANA, there are many things that can be found in different modules such as FI, SD, PP, Output Management, etc. and there is always the question of how my business will affect, what is the way forward and am I entering completely uncharted territory? The first thing someone would do is search for topics on SCN blogs, Google, JAM pages which are actually a good place to start.

However, sometimes (or especially) it`s a bit difficult to run a hands-on end-to-end scenario for the new features that will be part of S/4 HANA. I had similar problems when I tried to understand “condition contract management” in settlement management, which replaces traditional “discount management”, so I thought it would be nice to share my experience. Like its predecessor – ECC`s discount agreement feature – Settlement Management uses a combination of a contract master and pricing terms to determine the settlement period and terms. A new element called “Business Volume” can be seen as a huge filter used to identify the relevant sales document elements for each agreement. At a high level, these three parts work pretty well together, but if you look at the impact of traditional SAP pricing, you`ll find a few quirks. Create a ZBBI contract type that is a copy of SBBI Let`s create a condition contract in the SAPGUI WCOCO – Condition contract transaction. You can follow the blog to create a condition contract. Thank you for the information. Do you have the Customizing-to-Sales (SD) module? Save the condition contract.

The workflow is automatically started in the background. You must now assign the previously created ZREB condition types to this group of condition types. You can click the path under In my example, the ZUR1 purchase conditions type group has been created, in which three types of conditions are used. ZUC1 is a percentage condition, ZUC2 is a fixed amount condition and ZUC3 is a provision condition. It is important that the types of conditions in the group are defined as relevant to the determination of CC. This is due to the following condition that we have created in the condition contract. Second step of the condition contract type – settlement process In the header conditions you will find the discount condition that we had created as part of the condition contract. The second part of the configuration of the condition contract type is more demanding and is divided into a few steps that are then combined when defining the contract type. The “Exclusive” flag is set because we don`t want multiple conditions to apply to the same contract. However, in this scenario, when we perform the pricing, the material pricing process “12345” applies the $0.75 price from Table 905 and stops due to the “Exclusive” indicator. The provision of $0.10 for contract 50002 will not be made.

This book is for all users who now or in the future want to map delivery processes in SAP S/4HANA and gain a practical understanding of contract processing. Decision makers and IT managers can also quickly identify possible applications of SAP S/4HANA for conditional contract settlement (CCS/CCM) as a sub-function of billing management. Since SAP ERP 6.0 EHP6, component agency activities (LO-AB) and compensation management (LO-GT-CHB) have been combined in this holistic application. The subsequent settlement and SD bonus have also been replaced by the new SAP S/4HANA tool. Here`s an example: You have a relevant sales order line for two conditional contracts: 50001 and 50002. These contracts use the same type of condition, ZTPM, which can set different rates at the Contract/Material or Contract/Material Group level. I will not explain how to create a sales document, delivery, PGI, invoice, etc., but what should be mentioned is that these documents can be created before the creation of the condition contract or after the preparation of the condition contract. If the sales document is created after the contract is created, the REBA supply condition will be available on the Conditions tab page. Click the “Agent Assignment” button for the workflow step 000004 release condition contract Last but not least, to correct what you said, the accumulation and remittance conditions are almost the same YES, but in addition to the checkbox of the layout, there are other differences (sign, Group condition section) Readers will also learn other interesting features such as inter-partner contracts, calculation variants in pricing, and cancellation of incorrect billing.

This practical guide is complemented by information on data control reports and useful tips for integration into accounting. My contract works well, but I can`t find the step to activate all the buttons to release, block, delete, prepare archiving and inversion in wcocoall, for example. In the condition type group, you assign the ZREB condition type for managing a delivery condition in the condition contract. This condition is selected in the condition agreement and included in the price of the sales order. In this case, the ZUC3 condition type carries the value value that has been set in the case of a ZUX1 condition-based contract, which already has provisions that have already been settled. The value is then used during a new delta accumulation or a final settlement in the pricing process during the CC settlement (conditional contract). As you can see below, the scope of activity 1.5 is updated according to the condition contract Do you have a useful link to set up PPF actions for condition contracts? I am facing a problem in the checkout process where I have a FIXED billing condition in WCOCO and a split billing document at the header level. The system can be configured to manage workflows for the processing of discounts, e.B.

the approval processes of status contracts and settlement documents as well as the release of status contracts for settlement. If we remove the “Exclusive” indicator from the access sequence, the provision of $0.10 is made for 50002, but in contract 50001, two provisions are made – $0.75 at the “Contract / Material” level and $0.50 at the contract / group of materials level.. .