Finance Document Park and Release

Having multi-level control of the documents being parked is a requirement of many finance departments. 

SAP offers the park and post functionality and the ability to block and release documents before a payment could be made for an invoice.

This document will detail out the basic configuration steps for document park and release functionality.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Gayani Karunathilake

Finance Document Park and Release by Gayani Karunathilake

How to Determine Different Accounting Document Types for the Same Billing Type

As we all know, when a billing document is posted to FI, there will be an accounting document generated in the system. This has an accounting document type assigned to its header.

The default accounting document type is assigned to the billing document type in customizing. This is configured in below IMG Path under the field "Document Type".

Sales and Distribution / Billing / Billing Documents / Define Billing type / Define Billing Types

Today let's see how you can determine different Accounting Document Types for the Same Billing Type.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Anupa Wijesinghe

  How to Determine Different Accounting Document Types for the Same Billing Type by Anupa Wijesinghe on Scribd

Invoice creation batch job setup in SAP

Most of the business organizations would like to create their customer invoices in a batch job (Background job). This batch job can be setup in a way that it executes in a pre-defined frequency (eg: Once a day at night) and pick all documents that are due for billing. Such billing due documents can be comprise of;

• Sales orders in case of the third party orders for order related billing

• Credit / Debit memo requests which does not have “Billing block” for order related billing

• Post goods issues deliveries in case of delivery related billing

We can execute the as billing due list in SAP via transaction VF04. 
Today let’s look at how we can setup this transaction as a background job and key differences in this billing batch job against any other. 
Please click here to read more about background job setup in SAP.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Author: Anupa Wijesinghe

  Invoice Creation Batch Job Setup in SAP by Anupa Wijesinghe on Scribd

Invoice Split Logic in SAP

 For certain business requirements, you need to define customer specific invoice split criteria. This can be achieved using below method.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

   Invoice Split Logic in SAP

Functionality behind Pricing Date in the Sales Order

The "Pricing Date" in the sales document is used to determine correct prices (Based on condition master records with validity periods) for the sales order.

For example, let's say you adjust prices in the beginning of every year. This year you are going to create a contract for a customer which is valid from next year. Therefore the prices which should appear in the contract have to be next year prices, not this year prices. In such a scenario, "Pricing date" field plays a key role. When you create the pricing condition records in transaction VK11, you have to specify the validity periods. When determining correct prices in the sales order, the pricing date works in conjunction with these validity periods.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

   Functionality Behind Pricing Date in the Sales Order

Condition Exclusion

Condition Exclusion is very commonly used functionality in SAP SD area to determine best condition or condition value in the sales order. For example, if you have multiple discount condition records setup in the system and you want only the best condition to appear in the sales order and not all discounts, then you can use this functionality.

Let’s see how you can configure condition exclusion in SAP.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Condition Exclusion

Sales Deals

A sales deal is a set of pricing master data that allows managing customer and material profiling. A group of customers is assigned a group of materials and a specific discount rate. This is basically a CRM functionality which resides in standard SAP. The entire functionality does not require any custom ABAP coding; it is entirely based on standard SAP customizing.
Main configuration point's needs to be created are the “Sales Deal Types”, “Condition Type Groups” and “Condition Types”. This process reduces the condition record maintenance effort drastically.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Sales Deals

Size wise tax classification in SAP (IS-AFS)

In the typical apparel and footwear business world it is common to have different tax rates for different size ranges. For example, some countries have reduced tax rate for kid's sizes where as adult sizes are fully taxed. Therefore this functionality has been built in SAP AFS (IS-AFS) to maintain size wise prices as well as size wise tax classifications.

As we all know, the tax rate (Eg: 18%, 10%) in the sales order is determined based on the tax condition master record maintained in transaction VK11. This record is maintained for the combination of customer tax classification and material tax classification. Customer tax classification is maintained in the customer master / sales area data / Billing Documents tab. In the standard SAP environment, you maintain the material tax classification in the material master "Sales: Sales Org. Data 1" tab. But in that field you do not have a provision to maintain tax classifications per each size.

Therefore SAP has provided a solution to maintain tax classifications at size level based on Grid control data. This is available only in SAP AFS (IS-AFS).

If you're looking for tax account determination in SAP, please click here.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Size Wise Tax Classification in SAP (is-AFS)

Calculation Schema for Purchase Orders

In order to calculate the cost of the purchase order, SAP has provided functionality called "Calculation Schema". The famous "Condition Technique" is used for this as well. (Click here to see more information on the "condition technique"). The same technique is used in SD Pricing as well. Let's see how this works in SAP for purchase orders.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Calculation Schema for Purchase Orders 

"Manual" field in the pricing procedure Vs. "Manual entries" field in the condition type

It is often misunderstood the functionality behind the "Manual" field in the pricing procedure and the "Manual entries" field in the condition type customizing. 

Therefore today I would like to go through the combination of these 2 fields and see how it works in SAP.

Click here to view more information about 16 fields in the pricing procedure.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Usage of Manual Field in the Pricing Procedure Together With Manual Entries Field in the Condition Type

Release Procedure for pricing conditions

Like in purchase order release strategy (Click here to view it) or sales order release strategy (Commonly known as "Status Profile" in SAP. Click here to it), you can have a release procedure for your pricing conditions. This will allows you, for example, to create condition records purely for planning purposes, which are later taken into consideration after a pricing release.

For this release procedure, you can use the functionality together with "Processing" and "Release" Statuses. Processing statuses are freely definable. But release statuses are pre-defined by SAP and therefore, you can only assign your processing statuses to those release statuses.

Please note, these release status for condition tables are only available from release 4.6 A. But it is possible to convert existing condition records to the new format with the release status.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Release Procedure for Pricing Conditions

Definition and Usage of 16 fields in the Pricing Procedure

In one of my previous posts, we discussed how condition technique works in SAP (Click here to view more details). There we identified all condition types are grouped in a basket called "Procedure". Same functionality is used in output determination, tax determination, pricing, revenue account determination, listing and exclusion, etc.

Today let's see what fields are available in a pricing procedure and the use of each field. You should be able to identify below 16 fields in a standard pricing procedure. They are;

1) Step No

2) Counter

3) CTyp - Condition type

4) Description

5) From

6) To

7) Manual

8) Required

9) Statistics

10) Print

11) SuTot - Sub Total

12) Reqt - Requirement

13) CalTyp - Condition formula for alternative calculation type

14) BasTyp - Alternative formula for condition base value

15) AccKey - Account Key

16) Accruals

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Definition and Usage of 16 Fields in the Pricing Procedure

Condition technique in SAP (Step by step explanations)

Condition technique is the most common method used in SAP to determine certain records/values during various processes such as sales order pricing, output processing, VAS processing.
In SD, condition technique can be seen in pricing conditions (Click here to view more details), text determination (Click here to view details), and output determination (Click here to view details) areas.

Therefore today I thought of sharing how this famous condition technique works in SAP with a simple example in pricing. Same is applied to other areas as well.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

Condition Technique in SAP

How to Configure Pricing Reports in SAP

Pricing reports can be configured to view VK11 condition master records in SAP system.

For example if you have condition records with different validity periods & different access sequences, this can be used to view all conditions records with relevant validity periods directly in one screen; where as you cannot use VK12 / VK13 to view all condition values in one screen.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

   How to Configure Pricing Reports in SAP by Anupa Wijesinghe

Adding new fields to condition field catalog (Pricing)

If you want to add a new field to the condition field catalog (Which is not available in the standard field catalog) and use it for condition record determination, then you need to setup below described configuration/coding correctly.

Happy Reading!!

Please feel free to post your suggestions, feedback and comments!

   Adding New Fields to Condition Field Catalog by Anupa Wijesinghe