Skip to main content

SAP S4HANA SD-FI INTEGRATION -ACCOUNT DETERMINATION VKOA


Account determination is main integration between SD -FI .

We will see the integration of this functionality and how it is triggering G/L account and how is it different from SD condition technique

ACCOUNT DETERMINATION is a functionality which also determines based on the CONDITION TECHNIQUE, But the way it is configured and controlled differentiates it from SD condition technique

in this Article we will discuss on, How to create a new Access sequence in VKOA- ACCOUNT DETERMINATION TABLE


I have create a new Table 496 with Condition type and account Key - Technically it will generate a database table as C496

the Configuration lies in Sales and distribution-->Basic functions-->Account Assignment-->Revenue Account determination


Unlike SD, where we set Exclusive Indicator on Access Sequence, VKOA has no such functionality
Then Question arises on how system will search and stop at particular Condition table?

So, in VKOA system will always search from More specific to Generic search ( Infact this is how access sequence functions)

If we have maintained G/L account for Table 1 ( C001) then automatically system will assign this G/L account to the SD condition type which has met with the Criteria.

If there is no G/L maintained or condition does not satisfied, then automatically system goes to next Table 2 (C002) and so on until it met successful Access.

I have maintained condition table C496 - with G/L and let us test how it works

STEPS:--

1. Create sales order

2. Create Delivery document

3. Create a Billing document

4. upon Saving billing document, system will try to check VKOA setting and it happens in the Function Module

"SD_COND_ACCESS"




Billing document--Account determination Analysis




tables which are used in this determination are T68* ( most of them will share with SD tables)

Please let me know your inputs,

Good Luck

Comments

  1. Thank you. Please also write a blog on revenue recognition

    ReplyDelete
  2. Good one. Can you please try to include the end user T-Codes in the Articles, so that both the programmers and actual end-users can be benefited.

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost ...

S4HANA-Project Systems Operative Indicators in WBS- CJ20N

  Use and Purpose of Operative Indicators in WBS elements When a customer Requests for ATO or ETO process where we create a Project with Integration between SD and PS ( project systems) As a First step we create a Project in CJ20N and under the Project we will Create Multiple WBS elements which has to be set for Operative Indicators This article deals with Operative Indicators in WBS elements. WE Use Operative Indicators to define characteristics of WBS and to specify which tasks WBS can perform during Execution In General, we have three Operative Indicators such as 1. Planning Indicator 2. Account Assignment Indicator 3. Billing Indicator Planning Element: WBS Elements will be set for planning Element,if we we want a plan cost to be enabled For Example, While Creating a Project- Manufacturing an Equipment. We will Create different WBS elements for each Level such as Design, Procurement of components, Production, Assembly and Installation. During Each state some cost is incurred an...

SAP SD - Advance Return Management for customer Returns

In all Sales Business Cycles, Returns from customers are Normal, Returns can be expected when 1.  Customers expected Quality is  not met by the  product delivered 2. Some times Customers Orders more products than it is required 3.  DOA or Miss shipments ( wrong Products delivered). In above all cases, Customers will return the material,  and these returns can be handeleted by ADVANCE RETURNS MANAGEMENT ADVANCE RETURN ORDER :                            Advance Return Order is the document  which initiates the Customer Returns                         It Controls , how a return should happen and its Results We have to enter   RETURN  REASON :  Reason for Customer Reason MATERIAL RECEIVED :  Identifies that the Physical material in the warehouse and initiates immediate delivery ...