Pricing subtotal Fn.module
Hello all,
I'm using Fn.module RV_PRICE_PRINT_HEAD to get the Pricing conditions but I'm not getting the subtotals.Is there any Fn.module to get this.
Thanks for any answers..
Edited by: John G on Feb 5, 2008 11:09 PM
Hi John,
Search SDN before posting your Question.
You can go through this link
using of RV_PRICE_PRINT_ITEM in smartforms
Similar Messages
-
Interview Questions and Answers for Pricing and Shipping Modules!!!!
Please let me know the Interview Questions and Answers for Pricing and Shipping Modules?
http://www.google.co.in/#hl=en&tbo=d&sclient=psy-ab&q=interview+questions+in+oracle+pricing+and+shipping&oq=interview+questions+in+oracle+pricing+and+shipping&gs_l=hp.3..33i21.1169.38878.0.39096.61.45.10.6.6.4.4004.21813.2-21j9j6j3j2j1j1j1.44.0.les%3B..0.0...1c.1.jEq3EQIj8vA&pbx=1&bav=on.2,or.r_gc.r_pw.r_qf.&bvm=bv.1357700187,d.bmk&fp=cedcde5e8e6bc792&biw=1280&bih=619
HTH
Mahendra -
Pricing for assortment modules
hi gurus
i want to link each Assortment Module in value contract to specific Price and accordingly each item within the assortment module will use the specified price when creating sales order with reference to the contractCheck this -
Pricing in sales order
Regards. -
SD: Pricing: Subtotal, Alt Cal type, Requirements
Dear All
Can you please help providing details on functions of standard Subtotal and Alt Cal Types provided in SAP-SD Pricing.
I mean:
1. Standard Subtotals like 2,3,5,G etc.
2. Alt Cal Types like 4,7 etc.
3. Requirements Like 10, 70, 71, 4 etc.
Any document details will be highly appreciated.
Thanks
Raghu A.Subtotal:
u2022 The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
u2022 Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
u2022 If the same fields are used to store different condition amounts, the system totals the individual amounts.
u2022 These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
u2022 It is a routine that is written by an ABAP consultant according to the business requirement.
u2022 By defining Requirement in condition technique we can restrict the access of condition type.
u2022 To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
u2022 For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
u2022 This Requirement will ensure that these condition types will appear only during the billing document processing.
u2022 If new Requirements are to be defined we follow the procedure given below.
u2022 Go to T.Code: VOFM. - Maintain Requirements & Formulas
u2022 Click on the "Requirements" in the top menu and then click on "pricing".
u2022 We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
u2022 And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
u2022 It is again a Routine that is written by ABAP Consultant.
u2022 It is an alternative formula for the condition type that can be used instead of standard formulas.
u2022 For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
u2022 Ex.: 950 0 Profit Margin 11.
u2022 So we assign 11 - Profit Margin.
u2022 If new routines are to be defined we follow the procedure given below.
u2022 Go to T.Code: VOFM. - Maintain Requirements & Formulas
u2022
u2022 Click on the "Formulas" and then on the "Condition Values".
u2022 We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
u2022 And we assign the application type.
AltCBV - Alternative formula for condition base value:
u2022 Formula for determining the condition basis as an alternative to the standard.
u2022 It is again a Routine that is written by ABAP Consultant.
u2022 It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
u2022 Ex.: Freight - KF00.
u2022 Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
u2022 In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
u2022 During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
u2022 Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs. -
HI
in pricing procedure subtotal can we give same subtotal key say 1 KOMP_KZWI1 to different ctypes
say PRoo & zhbo Discount
Will it create any problemDear Friend.
It depends what your requirment is. It is possible. and should not create any problem. this subtotal will be stored in the perticular field and then you can reuse it for further calculations.
The sub total field is used to cumulate the condition types values. e.g if you want all discounts to be calculated together in one field for further references...you want different pricing conditions to be cumulated and so on,
The example you have used tells about pricing conditions and discount conditions which will be cumulated in one field outcome will be stored in perticular field and you can use that for further calculatons. But mixing pricing and discount seems unlikely.
I hope clears your doubt.
Regards,
Paresh -
HI,
explain pricing.
kathir.Hi,
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Reward points if useful
Regards,
Amrish Purohit -
Modules included is APS Purchase
There are four modules listed as part of the Oracles APS Solution: Demand planning, Global ATP Server; Manufacturing Planning; Advanced Supply Chain Planning.
When buying the Oracle APS solution do these modules come packaged as one product or are they priced separately. If priced seperately, which modules are required.The Oracle APS modules include the following and can be purchased separately.
1. Advanced Supply Chain Planning (ASCP)
1a. Constraint Based Planning Option
1b. Global ATP Server
2. Demand Planning
3. Manufacturing Scheduling
The only dependencies are that you must purchase ASCP in order to use either the Constraint Based Planning Option or the Global ATP Server. Both Demand Planning and Manufacturing Scheduling can be purchased and used independently. -
Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be u201800012u2019. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field u201Cno Credit Checku201D with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etcu2026)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
400000 405500
405505 405549
405555 415927
415929 424603
424606 427532
427534 428799
428900 471699
471700 499999
Visa Procurement Expires in 7 days.
405501 405504
405550 405554
415928 415928
424604 424605
427533 427533
428800 428899
Mastercard Credit Expires in 30 days
500000 540499
540600 554999
557000 599999
Mastercard Procurement Expires in 30 days
540500 540599
555000 556999
American Express Credit Expires in 30 days
340000 349999
370000 379999
Discover Card Credit Expires in 30 days
601100 601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter u201C03u201D in the column labeled u201CPTu201D for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa 7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence u201CA001u201D
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu -
Credit Management System - Update of SD Documents after CMS start
Hi,
we are starting CMS functionality in our SD module. CMS (Credit Management System) works remotely by an XI connection. When we switch to use CMS in production system, we have to transfer all opened orders (not yet invoiced) to CMS system.
How can we achieve it? Can program RFDKLI20 (t-code F.28) be used for this purpose? Does it require any settings to point out the CMS connection?
Thank you
/BRHi Wojciech
CREDIT MANAGEMENT
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Reward if useful to u -
What is credit management how should we tell
hi
gurus my question is what is credit management.
2) If one customer exceeds his credit limit the sales order is blocked in the enduser system. WHO will release that order. Whether enduser called his higher authority by telephone or mailed or it is automatically knows by the superior means who is working in the managerial level working in n.s.o.
thanks in advancehi
The customers credit limit is assigned to the customer by going to the Logistics overview screen, Accounting, Financial accounting, Accounts receivable, Master records, Credit management, Change.
A credit control area is an organizational unit that is comprised of one or more company codes.
Create a credit control area and assign it to a company code in the Enterprise structure under financial accounting.
A customers risk category is a grouping category that controls the credit checks when automatic credit control takes place.
In SD credit check can occur in only three places: sales order, delivery and goods issue.
The system can use a simple credit check, static credit check or a dynamic credit check.
The simple credit check is set at the document type level e.g., sales order, delivery etc.
Simple Credit Check
Assign credit limit check to the sales doc type:
A warning message
B Error message
C Delivery block
D Automatic credit control
SAP enables static and dynamic credit checks so that a sales order for a good customer with a low risk credit rating is created and a sales order for a high risk customer with a high risk rating for the same doc type is blocked.
Automatic credit control divides the sales doc types, delivery doc types, and goods issue into specific credit groups.
An outcome procedure is defined using the credit group, the customers risk category along with the credit control area.
Risk categories are defined in the FI module.
Create the different credit groups e.g., for sales order, delivery, goods issue.
Assign the credit groups to the sales and delivery doc types.
Now define the settings for automatic credit control -> combination of credit control area, customers risk category, and credit group.
All that remains is the assignment of the risk category to the customer master record. This occurs in Finance by going to the Logistics overview screen -> Accounting, Financial Accounting, Accounts receivable, Master records, Credit management, Change or FD32.
The static credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer.
The dynamic credit check is a check comparing the credit limit assigned to the customer to the total value of open sales orders not yet delivered, plus the total value of open deliveries not yet invoiced, plus the total value of open billing documents not yet passed on to accounting, plus the total value of billing documents that have been passed on to accounting, but which have not been paid by the customer. The dynamic credit check has an attached time period that states that the system is not to include sales orders in the total of outstanding items created after the specified time period.
The credit relevant data is updated into an information structure, where it is accessed and updated. Thus each automatic credit control must be assigned an update group. The system allows for no update, and update group 000012, 000015 and 000018. However, update group 000012 is thorough and used in most businesses.
To view the customers credit master sheet, proceed from the logistics screen and go to accounting, financial accounting, accounts receivable, environment, credit management, check, credit master sheet [F.35].
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Reward if USeful
Thanx & Regrads.
Naren.. -
Sales order credit control area
Hi,
How can i identify the credit control area the sales order belongs to?
Is there any way to identify in the SO itself?
(not checking the sales org and checking the cc ar)Credit Control
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
u2022 SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items you can have the followings credit limit check:-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you donu2019t want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.You can use the u201CNextReview dateu201D and u201CNumber of daysu201D fields and combined it with the u201CLast int.reviewu201D field in customer credit master u201CStatusu201D view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Releasing the Credit Block
These are the three transaction code you can used for releasing the SAP credit management block.
VKM3 - Sales Order
VKM5 - Delivery Order
VKM4 - Both Sales Order and Delivery Order
There are basically two types of customers:
1)Credit worthy
2)Normal customers
Coming to credit worthy customers these customers we can believe and we will give some credit ness for them.For such a type of customers we are going to set them some credit limit.Based on that we will give service to them till that limit.It the limit crosses we will get the messages while creating orders for them.
Their credit limit can be set in FD32 T.Code.
Automatic credit check will be maintained in OVA8
Follow these steps:
1. Go to IMG - enterprise structure - definition - financial accounting - define credit control area.
2. Assignment of company code to credit control area & sales area to credit control area.
3. Go to OVAK select ur sales document type and in the check credit column choose from A B or C. D is for automatic credit control for which you have to maintain the credit group and risk categories.
4. In FD32 you select your customer and click on STATUS icon and press enter. here u maintain the credit amount allowed. but this is done by the Finance people.
5. Now when you create the sales order and if the amount exceeds the credit limit then u will get the message as you maintained in the TC OVAK. Normally the system starts doing credit checks from the second sales.
order.
What are the different types of credit checks?
By Sunilmadho
Credit Check can be :
1) Simple Credit Check
2) Automatic Credit Control
Automatic Credit Control can be at various levels :
1) Order
2) Delivery
3) Goods Issue
Automatic Credit Check is of many types :
1) Static
2) Dynamic
3) MaximumDocument Value
4) Maximum Open Items in percentage
5) Oldest Open Item in number of days
6) Crtitical fields change
7) Highest dunning level, etc.
You can create more.
Credit Check happens only in SD module, never in FI. Because the stage of the check is in the sales cycle, which exists in SD. FI guys will check the credit master sheets of the customer, the MIS, the analysis etc, review the credit limits of customers. But the check will happen only in SD, while creating order, delivery or doing the goods issue.
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
More control in transaction OVA8 - Automatic credit control
You check for open orders and deliveries, or just open deliveries.
or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
In credit mgmt how the Amount & limit can be can be configured at sales order,delivery & PGI Level.
Please give me the solution .
1)First create Credit control area
Path:IMG\ES\Definition\FA\Define Credit Control Area
2) Assign your credit control area to your company code
Path:IMG\ES\Assignment\FA\Assign Company code Credit Control Area
3) And enter the credit limit using above mentioned transaction code FD32.
4) And assign this credit control area in your customer master Sales Org Data (XD02)
5)if you have maintained the credit control area for your customer then goto T.Code FD32.
6)Enter your customer number and the credit control area.
7)Select the status tab.Press enter.
8)Maintain the credit limit in the field.Save.
9)Go to OVA8 T.Code and then click on open orde -
Dear Friends,
Right now the credit check is on Delivery Order. It displays error message when doing PGI for Gross Value (Price + Tax). Now I want to do it for Sale Order Level.
I did all changes according to the following; but on sale order the error message is only for (Price). It is not including tax value. Your assistance is required....
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPFV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be
marked in Transaction OB45, or the credit control area must be entered
under the relevant company code in table T001CM of the credit control
areas allowed.
Company code:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. You can
use Transaction FD32 to assign this risk category to a credit account.
10. Transaction OVA8
Here, the individual credit checks for key fields
- credit control area
- risk category
- credit group
are set. Take these key fields from the above settings and go
to the detail screen. In particular, check whether fields
"Reaction" and "Status/block" are set correctly. To carry out
follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values
Update of the credit values is required for the limit check (static or
dynamic credit limit check).
13. You want the item to be relevant for billing. If an item is not
relevant for billing or for pro forma billing, no update occurs.
14. Transaction OVA7
Update of the credit value is active for the corresponding item type
if the check box is marked. This field corresponds to field "Active
receivable" in Transaction VOV7.
Item type:
Active receivable:
15. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be
entered in a line for determining the credit value (mark the pricing
procedure and doubleclick on "Control"). Usually, the net value plus
taxes is used. This way the system is determined to use this subtotal
for credit pricing. The credit price is stored in field VBAP-CMPRE and
used for update and credit check.
You can find the used pricing procedure of the order under "Item ->
Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
16. Transaction OB45
Which update group (field "Update") do you use in the relevant credit
control area? The default setting is "12". If you use another update
group, check whether this is fine with you. If you open an OSS
message, please tell us the alternative update group.
Credit control area:
Update:
17. Transaction OMO1
Which kind of update did you choose for structure S066? In any case,
"Synchronous update (1)" has to be chosen as the kind of update. All
other settings will lead to errors.
Regards,
ShahbazDear Lakshmipathi,
Yes, "A" is there.
Regards,
Shahbaz -
Check Credit and Stock on Sale Order
Hi All
Could you please tell me how to check Credit and Stock on Sale Order.
Thank and Best Regard
ThangHow To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors
Regards
Raja
Edited by: ramanathan raja on Jul 25, 2008 4:37 PM -
hello SD gurus
I have 2 issues:
1) when the sales order value exceeds 1000000 system has to give the warning / error message . where should I have to do the settings
2) if any customer enter wrongly like Qty : 1,0000,000 system has to give the warning / error message , where i have to do the settings
Please give me some light on this
thanks and regards
siva
Message was edited by:
siva narayanaHi
goto Tcode FD32
enter the customer number and credit control area and select the status check box
to set the credit limit to the customer select goto control area data -
status
we can specify the credit limit of the customer in the field credit limit .
In fd32. you can give the total and individual limit for that particular customer in that particular sales areas or all the sales areas. and also activate in sales document type which credit limit ie, simple or automatic and risk category. in the tcode OVA8. and also in the item category to check the credit for the line items in the order. and also give credit control area in the customer master record and dont forget to assign the credit control area to the company code and the sales area. and in pricing subtotal give A and recquirement 4 which all the credit data will be activated and stored in the table KOMP-CMPRE.
Sail -
Header pricng condition : Sales order
Hi All,
I am adding a new condition type while creation of a sales order. Now my requirement is that the RATE entered against this conditon type should get copied to another conditon type as well.
How can this be realized ?
Awaiting a quick response.
Regards
Nishanthave u seen VOFM transaction ?
for the new condition u have to create a Requirement , that requirement u have to assing in the pricing procedure .
<b>Profit margin considering rebate agreements
Purpose
This is an example of a condition value formula. This type of formula can be used to influence the value shown for the condition in pricing. A condition value formula is assigned to a condition type or value line in the pricing procedure.
Formula '1' sets the value equal to the pricing subtotal '3' minus the cost of the line item.
Example
A company offers rebate agreements to their customers that are paid out at the end of the year based on cumulative sales. On a sales order, rebate agreement accruals show up as a statistical amount and do not effect the net value of the line item. The company, however, would like to see the profit margin in the line item reflect the expected rebate payments. In order to accomplish this, the user assigns the subtotal field '3' to the relevant condition types in the pricing procedure so it's value equals the net value as well as the value of any rebate accruals. The condition value formula '1' is then assigned to the 'Profit Margin' line in the pricing procedure. Note that subtotal '3' is just an example supplied by the system. Another subtotal could be used and the user would then copy this formula and create a new one that uses the other subtotal value. If rebate accruals should not be included in the profit margin calculation, the user would select condition value formula '11'.</b>
<b>VOFM->Formula>Condition Value.</b>
for more info , please have a word with ur FC he can give clear view .
Regards
Prabhu
Maybe you are looking for
-
Internal Order - carryforward MIRO Invoice against MIGO receipt
Hi, I have created an internal order (TCode KO04 & KO21 ) Allocated full budget for year 2007 Then I have linked it to an asset. A Purchase Order is made with link to the asset. A Goods receipt (MIGO) entry also was created against the PO All these t
-
Hi, I want to export my Robohelp 7 HTML help to a Word document. I want the output to look exactly like the main help file, but want to add some headers and footers using a Word template, Here's what I've tried: In the Single Source Layouts> Printed
-
Hello, In PO item level, in delivery address I can see address details are populated but where as address field is empty with no number in it.Could some one let m eknow from where the address number is copied?
-
This is my first ever post - and it has to be a problem! We've been using Incopy for a few years without any issues. Our editor and designer works off-site so they share packages. The editor went to Create for Indesign and email and it didn't work -
-
Does Mac Lion OX 10.7.5 have access to iCloud
For syncing I now use Dropbox, but I would like to use iCloud. My old 2007 MacBook Air will only run Lion OX 10.7.5, and I dont see anything about iCloud. does it not exist on OX Lion 10.7.5? Thanks in advance