Can any one pls tell the interview questions on Rebates and intercompany Billing.
Thanks in advance
A rebate is a special discount which is paid retroactively to a customer. This discount is based on the customer's sales volume over a specified time period
Rebates Processs in SAP is divided into three components
1) Configuring Rebates
2) Setting Up Rebates
3) Managing rebate agreeeements and payments
Pre-requsiistes- Check the following:
1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab.
2.The Billing type must be marked as relevant for rebates.
3.The Sales Organisation must be marked as relevant for rebates.
Condition Technique :
Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..
Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after going thru the right path of maintaining access sequence for rebates.
The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time.
Rebate related condition types are identified by codnition class -C.
After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.
The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.
Now payment of rebates:
Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn. You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period.
These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created
Customer account/ is debited and
Accrual provision account is credited.
What exactly do you wish to know in Rebates? The total outline of the Rebate process or each and every step in the SAP system?
A.First of all rebates are more or less discounts which are offered to customers. The rebates are based on the volume of the business the customer does with you within a specified time. for eg if the customer agrees for Rs.1 Crore worth of business with u in 1 year, then you activate your rebate process. if at the end of the year the customer DOES achieve the target u offer him say 2/3/4 % whatever is decided. The rebates are passed on to the customer in the form of Credit notes. The rebate can be given to the customer at one time or in installments also.
This is broadly the outline of the rebate process.
Note : I recommend you to study the theory part of why rebate and why not a discount.
This will help you understand better.
May be I can help you with rebate process.(IN -IMG)
1. define a rebate agreement type
2. define a condition type group
3. define a condition type and place this condition
Type in the pricing procedure.(REQUIREMENT=24)
ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU
YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.
Once you have defined all the 3 and assignment starts.
Assign the agreement type to the condition type group
Assign the cond type group to the condition type.
Condition technique is also used in rebates.
REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR THE BILLING DOCUMENT.
After having done this please proceed to maintain the condition record for the rebates (transaction code-vbo1)
Note: if you maintain the requirement column with the requirement as 24 - the rebate will be affected in the billing document and if you dont give the requirement as 24 your rebate will be affected in the sales order.
The rebate process is completed when you have created a credit memo to the customer.
The document type for the partial settlement is R3.
Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first you try with the standard condition type boo1, boo2 boo3 boo4.
AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER , DELIVERY AND BILLING.
GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE ACCOUNT PARTIALLY.
In a simple way,
1. First you need to create a Rebate agreement.
2. Create condition record for rebate giving the rebate rate and accrual rate.
3. when the rebate relevant billing doc is generated, the rebate and accruals are determined and
posted in a separate GL account as a noted item - amount to be settled. Also it gets copied in the rebate agreement.
4. create settlement run using credit memo request and then credit memo to settle this amount with the customer.
Can you partially settle rebate accruals?
Inter Company Billing:
INTER COMPANY BILLING
A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
Sales organizations and plants assigned to each other need not belong to the same company code.
In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
1) End Customer 2) Ordering Company code 3) Supplying Company Code.
Customer who orders goods from the ordering company code.
Ordering Company Code:
Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
Supplying Company Code:
Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
Assign Organizational units by Plant:
Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
Define Internal Customer Number By Sales Organization:
Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
Transaction Code: XD01
The ordering sales organization is represented as Internal customer of Supplying company code.
We need to create customer master in Account Group - Sold to Party and maintain minimum required financial & Sales Area data.
This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.We maintain PR00 condition type to represent the ordering company code's price to the end customer.
Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
Eg: Sales Org. of Ordering company code + End customer + Material.
We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
Pricing Procedure ICAA01is determined at Intercompany billing processing level.
Pricing Procedure ICAA01 - Pricing Procedure for Inter company billing is assigned to the combination of:Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
STEP 1: Create Sales Order
Manually Enter the Delivery Plant of the Supplying Company Code:
OBSERVE CONDITIONS SCREEN FOR ITEM:
PR00 represents Price to the end customer (in other words, revenue for the ordering company).
PI01 represents cost to ordering company (in other words, revenue for the supplying company). It is represented as statistical item only.
Delivery is carried out from the supplying point & hence we can observe that it is done from shipping point assigned to the supplying point.
Subsequently, Picking & PGI are carried out.
BILLING TO END CUSTOMER:
Create Intercompany Billing:
OBSERVE THE CONDITIONS SCREEN OF THE INTERNAL INVOICE:
IV01 Condition type represents revenue for the supplying company code.
VPRS condition type represents cost to the supplying company code.
PR00 in intercompany billing document displays amount billed to the end customer. It serves as just an information item and is inactive.
If the ordering company enters the incoming invoice manually, the delivering company can print out an invoice document with the help of output type RD00, which is then sent to the Payer.
If automatic invoice receipt has been agreed, we must use the SD output control functions to ensure that output type RD04 is found in internal billing. In R/3 system, output determination procedure V40000, which includes this output type, is assigned to Intercompany billing type IV.
The automatic posting to the vendor account is initiated when output type RD04 is processed. The system uses the EDI output type INVOIC in the FI variant.
To ensure that payables are posted in financial accounts of the ordering company, the delivery company must be created as a vendor.
also refer to the link below for some helpful guideness
Reward if Useful
Thanx & Regards...