Professional Documents
Culture Documents
Sales Order Changed History Display
Sales Order Changed History Display
*
* Sales Order Changed History Display
*
* You can execute the report by :
* 1. Change Date
* 2. User Name
* 3. Sales Order Number
*
* Submitted by : SAP Basis, ABAP Programming and Other IMG Stuff
*
http://www.sap-img.com
*
REPORT ZSDCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING
LINE-COUNT 065(001)
MESSAGE-ID VR.
TABLES: DD04T,
CDHDR,
CDPOS,
DD03L,
DD41V,
T685T,
VBPA,
TPART,
KONVC,
VBUK.
DATA: BEGIN OF ICDHDR OCCURS 50.
INCLUDE STRUCTURE CDHDR.
DATA: END OF ICDHDR.
SELECT-OPTIONS: XUDATE FOR ICDHDR-UDATE,
XNAME FOR ICDHDR-USERNAME,
XVBELN FOR VBUK-VBELN.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK BLK1
PARAMETERS: SUDATE RADIOBUTTON GROUP
SNAME RADIOBUTTON GROUP
SOBID RADIOBUTTON GROUP
SELECTION-SCREEN END OF BLOCK BLK1.
DATA: WFLAG,
WCHANGENR LIKE CDHDR-CHANGENR,
WUDATE LIKE CDHDR-UDATE,
WNAME LIKE CDHDR-USERNAME,
WVBELN LIKE VBUK-VBELN,
WDEC1 TYPE P DECIMALS 3,
WDEC2 TYPE P DECIMALS 3,
WDEC3 TYPE P DECIMALS 3,
WDEC4 TYPE P DECIMALS 3.
ENDIF.
IF ITAB-CHNGIND = 'I'.
REPLACE '%' WITH ITEXT INTO ITAB-INDTEXT.
ELSEIF ITAB-CHNGIND = 'U'.
REPLACE '%' WITH UTEXT INTO ITAB-INDTEXT.
ELSE.
REPLACE '%' WITH DTEXT INTO ITAB-INDTEXT.
ENDIF.
CONDENSE ITAB-INDTEXT.
MODIFY ITAB.
ENDLOOP.
ENDSELECT.
IF SUDATE = 'X'.
SORT ITAB BY UDATE VBELN POSNR ETENR.
ELSEIF SOBID = 'X'.
SORT ITAB BY VBELN POSNR ETENR UDATE.
ELSE.
SORT ITAB BY USERNAME VBELN POSNR ETENR UDATE.
ENDIF.
LOOP AT ITAB.
CLEAR WFLAG.
IF SUDATE = 'X'.
IF WUDATE NE ITAB-UDATE.
SKIP.
WRITE:/001 ITAB-UDATE,
023 ITAB-USERNAME,
037(10) ITAB-VBELN.
WFLAG = 'X'.
WUDATE = ITAB-UDATE.
WCHANGENR = ITAB-CHANGENR.
ENDIF.
ELSEIF SOBID NE 'X'.
IF WVBELN NE ITAB-VBELN.
SKIP.
WRITE:/001 ITAB-VBELN.
WVBELN = ITAB-VBELN.
ENDIF.
ELSE.
IF WNAME NE ITAB-USERNAME.
SKIP.
WRITE:/001 ITAB-USERNAME.
WNAME = ITAB-USERNAME.
ENDIF.
ENDIF.
IF WCHANGENR NE ITAB-CHANGENR.
WRITE:/023 ITAB-USERNAME,
037(10) ITAB-VBELN.
WFLAG = 'X'.
WCHANGENR = ITAB-CHANGENR.
ENDIF.
IF WFLAG = 'X'.
WRITE: 013 ITAB-CHNGIND,
049 ITAB-POSNR,
057 ITAB-ETENR,
065 ITAB-INDTEXT(60).
ELSE.
WRITE: /013 ITAB-CHNGIND,
049 ITAB-POSNR,
057 ITAB-ETENR,
065 ITAB-INDTEXT(60).
ENDIF.
WRITE:/065 ITAB-F_OLD.
WRITE:/065 ITAB-F_NEW.
ENDLOOP.
FORM READHEADER.
CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
EXPORTING
DATE_OF_CHANGE
= CDHDR-UDATE
OBJECTCLASS
= CDHDR-OBJECTCLAS
OBJECTID
= CDHDR-OBJECTID
TIME_OF_CHANGE
= CDHDR-UTIME
USERNAME
= CDHDR-USERNAME
TABLES
I_CDHDR
= ICDHDR
EXCEPTIONS
NO_POSITION_FOUND = 1
OTHERS
= 2.
CASE SY-SUBRC.
WHEN '0000'.
WHEN '0001'.
MESSAGE S311.
LEAVE.
WHEN '0002'.
MESSAGE S311.
LEAVE.
ENDCASE.
ENDFORM.
FORM READPOS.
LOOP AT ICDHDR.
CHECK ICDHDR-UDATE
IN XUDATE.
CHECK ICDHDR-USERNAME
IN XNAME.
CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
EXPORTING
CHANGENUMBER
= ICDHDR-CHANGENR
TABLEKEY
= CDPOS-TABKEY
TABLENAME
= CDPOS-TABNAME
IMPORTING
HEADER
= CDHDR
TABLES
EDITPOS
= ICDSHW
EXCEPTIONS
NO_POSITION_FOUND = 1
OTHERS
= 2.
CASE SY-SUBRC.
WHEN '0000'.
LOOP AT ICDSHW.
CHECK ICDSHW-CHNGIND NE 'E'.
CLEAR ITAB.
MOVE-CORRESPONDING ICDHDR TO ITAB.
MOVE-CORRESPONDING ICDSHW TO ITAB.
CASE ITAB-TABNAME.
WHEN 'KONVC'.
MOVE ICDHDR-OBJECTID TO ITAB-VBELN.
MOVE ICDSHW-TABKEY(6) TO ITAB-POSNR.
WHEN OTHERS.
MOVE ICDSHW-TABKEY+3(10) TO ITAB-VBELN.
MOVE ICDSHW-TABKEY+13(6) TO ITAB-POSNR.
MOVE ICDSHW-TABKEY+19(4) TO ITAB-ETENR.
ENDCASE.
MOVE '& %' TO ITAB-INDTEXT.
APPEND ITAB.
CLEAR ITAB.
ENDLOOP.
WHEN OTHERS.
MESSAGE S311.
LEAVE.
ENDCASE.
ENDLOOP.
ENDFORM.
TOP-OF-PAGE.
WRITE:/ SY-DATUM,SY-UZEIT,
50 'SALES ORDER CHANGE HISTORY',
120 'Page', SY-PAGNO.
WRITE: / SY-REPID,
60 'SALES ORDERS STATISTICS'.
SKIP.
ULINE.
IF SUDATE = 'X'.
WRITE:/001 'Change Date',
013 'Time',
023 'User Name',
037 'Sale Order',
049 'Line',
057 'Sch No',
065 'Changes'.
ELSEIF SOBID = 'X'.
WRITE:/001 'Sale Order',
013 'Line',
021 'Sch No',
029 'Change Date',
041 'Time',
051 'User Name',
065 'Comment'.
ELSE.
WRITE:/001 'User Name',
015 'Time',
025 'Change Date',
037 'Sale Order',
049 'Line',
057 'Sch No',
065 'Changes'.
ENDIF.
ULINE.
*--- End of Program
You will find all User Exits on Sales and Distribution along with
functionality.
Please explain the difference between Ek01 ( Actual Cost) and EK02 Calculated
Cost.
These are the condition type that will display the results of the unit costing for certain
type of sales document.
EK01 :
If you use this condition type, the result of unit costing is issued to the first position on
the conditions screen for the item. The value can be used as a basis for price
determination.
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which
you can compare with the price.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the
pricing procedure.
I have a customer who is being offered two discounts ie k007 and k005, now I want
to exclude k007 for the next 2
orders or so? I have set the exclusion indicator for the condition type,but still the
condition is being accepted when I create a sales order. Am I missing something,
how do I do it?
I think u need to change the validity of the condition record for the condition type K007
defining it not valid for that particular 2 months. And also the settings of the
Requirements as it is correct that it overrules the exclusion.
Sabir
Reg pricing procedure.
1. Use transaction code v/07 to create a access sequence and assign tables based on which
you want to carry on
pricing as accesses.
2. Use transaction code v/06 to define condition type. It can be for base price, discount,
freight etc.,
(Do assign relevant access sequence)
3. Use transaction code v/08 to define pricing procedure.
4. Assign this to your relevant sales area+ dpp+cupp.
While specifying requirement, we can give reqt no.22 which specifies that plant has to be
set. This is generally done for output taxes since output taxes depend upon the delivering
plant. But directly there is no assignment between plant and pricing procedure.
Hope this helps,
uses the table behind this access if the sales order for which the price must be calculated
is in a foreign currency.
Re-pricing in a Quotation
How can I, or am I able to find anything on a way of RE-Pricing be done in a
QUOTATION?
You can always 'Update" pricing manually in a quotation the same way you do in a sales
order, either in create or change modes. Menu path Edit --> New Pricing or press the
'Update pricing' button on the item conditions tab.
If you are asking how to reprice a quotation when it converts into a sales order, that can
be done with the copy controls of the Item Category. IMG: Sales & Dist --> Sales --> -->
Maintain Copy Control for Sales Docs --> Sales Doc to Sales Doc (transaction vtaa). Just
choose the combination of documents and the respective item category. The field you
need to be concerned with is "Pricing type".
However, from a business process perspective it makes absolutely NO sense to reprice a
quotation when converting to a sales order. After all, the entire point of using quotations
is to firm up details like pricing before creating the sales order
You are fairly certain there is basic functionality that covers this, but you're just not
sure where to start.
Taking your requirements literally. Standard SAP scale pricing will not do it in that you
only want the reduced price to come into effect when the order quantity is multiple of
some bulk factor.
It is agreed with that creating a separate material number is not a good idea.
You can try this :1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)
2. Maintain UOM conversion between your base UOM and this new UOM
3. Configure you bulk pricing condition type by usual means (it should be a base price
rather than discount).
4. Place this new bulk price behind your normal "PR00" price in the pricing procedure
5. Create a new condition base value routine via VOFM where you check XKWERT to
see if it is a whole number. If it is not then set XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing procedure in ALT
condition base value column.
7. Maintain bulk price conditon record in the Bulk UOM.
That should do it.
Any other value other than B in the pricing type will take the reference document price
mentioned in the pricing source field.
but for the pricing type B. The new price is determined in the billing order.
if you don't want to do that Online, write your own abap report and use Function
SD_BULK_CHANGE (check where-Used at SE37, Trace VA05 on how to fill the
parameters, Function MPRF => New Pricing)
Of this to handle your first problem that is the rebate has to be applied
only on the "effort" you have to set up a line in the pricing procedure
which gives the rebate basis i.e the value to be used for rebate cond types.
This I believe solves your problem of rebate only on effort.
Your second problem i.e the discount should start getting applied
automatically when it reaches the first scale for which the values span few
financial years. This I am not really sure whether it can be made possible
in the invoice itself. But a work around is not giving the discount directly
in the invoice but settling it against the rebate agreements by Credit notes
periodically.
Hope it helps.
Thanks
-----Reply Message----Subject: RE: Customer discounts on effort only
Hi
Arent we looking at rebate agreeement. That appears to be a straightaway
solution to your problem. You activate the sales organization and the
payer for that
Regards
-----Reply Message----Subject: RE: Customer discounts on effort only
I am in SAP R/3 rel.30F.
We have 2 options to meet your requirement.
1. Using scale in condition type ( tcode V/06 ), choose scale basis
G.Scale based on a formula ( be: your based amount is invoice ). Define
scale formula. You need ABAPER to define it.
2. Using routine in Alt.calc.type ( tcode V/08 , Maintain Pricing
Procedure ). Here, you also need ABAPER to create routine.
hope this help
DICTIONARY
Transaction Code: SE11
9) Edit MV45AFZZ userexit_pricing_prepare_tkomk (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP
EDITOR
Transaction Code: SE38
10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP
EDITOR
Transaction Code: SE38
11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client
Independent)
Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP
EDITOR
Transaction Code: SE38
The following code should be inserted into program MV45AFZZ to allow the system to
re-execute pricing if the user makes a change to the relevant partner function (alteration,
addition, deletion).
13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->;
DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: OV24
14) Create Condition Tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->;
DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: V/03
15) Create an access sequence containing the new tables (Client Independent)
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->;
DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES
Transaction Code: V/07
16) Create a new condition type
Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND
DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->;
DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES
Transaction Code: V/06
For example you want to use field PSTYV ('Sales document item category') that is
included in structure KOMP ('Pricing Communication Item') as a key for a condition
table.
When you create a condition table (Transaction V/03), however, the system does not
propose the field in the field catalog.
Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ,
KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
Reason and Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in
structure KOMG ('Allowed Fields for Condition Structures').
Proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV.
Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales
document item category' and as a field label, you can use the field labels of PSTYV.Save,
check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change
mode and make the following entry:
Component Component type:
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in
structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions ->
Pricing -> Pricing Control' and execute 'Define Condition Tables'.
Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition
table Axxx.
6. Supply the new field you defined by including the following source code line in
USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing
document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customerspecific fields as key fields in a condition table.
For header fields, use structure KOMKAZ instead of structure KOMPAZ and
USEREXIT_PRICING_PREPARE_TKOMK instead of
USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path 'Sales and Distribution ->
System Modifications -> Create New Fields (Using Condition Technique) -> New Fields
for Pricing' and OSS Note 21040.
Discount
Rs. 100.00
Rs. 105.00
Rs. 110.00 etc.
2. You are creating a sales order for a customer with five different items with different
quantities as below
ITEM 1 - 25 No's
ITEM 2 - 3 No's
ITEM 3 - 12 No's
ITEM 4 - 27 No's
ITEM 5 - 62 No's
All the material is having the material group = 01.
3. While calculating the discount, because of this group condition, system add the
quantities of items which have material group = 01. In the above example total quantity is
= 109. System apply a discount of Rs. 110.00 to each item irrespective of the individual
quantities.
4. If you have not activated the group condition feature, system determines the discount
value based on individual item quantity which is as below.
Discount
ITEM 1 - 25 No's
Rs. 105.00
ITEM 2 - 3 No's
Rs. 100.00
ITEM 3 - 12 No's
Rs. 105.00
ITEM 4 - 27 No's
Rs. 105.00
ITEM 5 - 62 No's
Rs. 115.00
5. Is it clear now. Just try a sales order and see the out come
Procedure to Test:
1. Create 3 materials. Maintain Material Group of each item is same.
2. Activate the condition type as a group condition.
3. Create a condition record for this condition type with scales.
4. Process a sales order for a customer with these three material with different quantities.
Step 1. Define/Choose your Table (with the requirement parameters that influence the
price)
Step 2. Define your Access Sequence and include the above Table in your Access
Sequence
Step 3. Define your Condition Type (There are four Price Types Basic Price, Discount,
Freight and Tax) and include your Access Seq. Its always better to copy the Price Types
provided by SAP.
Step 4. Now comes your Pricing Procedure where you include include Condition Types
and format.
Step 5. Now comes Procedure Determination where you specify the Document Pricing
Procedure and Customer Pricing Procedure along with Sales Organisation, Distribution
Channel.
Step 6. Maintain Condition Records for your Condition Types
I guess you can make it 8 Steps by dividing some of the main steps. Few important things
to note is following..
1. XD01 - Create Customer - Always ensure that you pick the right Customer Pricing
Procedure from here.
2. VA01 - Sales Order - Ensure that you have the right Document Pricing Procedure from
here
3. While Creating Access Sequence, check your Fields and ensure that they appear with
any warning (Highlighted in Red)
4. Do not forget to mention your Access Sequence while defining your Condition Type
5. Always remember that your Procedure Determination has only Basic Price as
Condition Type
6. Do not forget to mention the Range (From To) while creating your Pricing Procedure.
I made most of the mistakes that appear above. Hope it helps.
Header conditions are entered manually in order processing. R/3 includes the following
header conditions:
- Percent discount (HA00)
- Absolute discount (HB00)
- Freight (HD00)
- Order value (HM00)
Header Condition: If this condition is marked as a header condition, it is possible to enter
the condition type in the header condition screen. Checks for changing the condition
manually are unaffected by this.
Group Condition: Group conditions are helpfull incase of discounts. If group condition is
selected then the discount percentage or quantity is applicable for the total sum of the
quantity in the PO for those materials belonging to the same material group. Suppose if
two materials of same matl grp have discounts for 100 qty and above but in PO if the two
matls are bieng procured for 50 qty then they cant avail discounts but if group condition
is selected then the sum of the quantity of both matl of same matl group is considered (50
+ 50) and discount can be availed for 100 qty.
Further Group condition: Indicates whether the system calculates the basis for the scale
value from more than one item in the document.
The nature of header condition is that whatever value you are giving in sale order /
billing, line item wise, it will be distributed proportionately.
If you access V/06 and the header condition type, you can see that the condition type
- does not have any access sequence
- field Group condition is selected
Normally Freight Header condition like condition type "HD00" is calculated on the basis
of weight. This is a Manual condition and you have to enter it in the header screen. It
will be proportionately distributed on each item on the basis of weight. If you will
uncheck the group condition field, the same freight amount will be copied to each item,
possibly irrespective of different weight which may not be logical.
That is the standard behaviour of the header condition type.
Based on whether the group condition field is ticked on or off, it will either split the
header condition value to the items on pro-rata basis or it will just duplicate the header
value to all the items.
What you are experiencing with Fixed Amount Header conditions is standard behaviour.
Please see below Notes:
- 876617 FAQ: Header conditions / Header condition screen
- 317112 Behavior of conditions w/ calculation rule B changed
- 485740 Conditions with fixed amount in copy activities
In any normal situation there could be more than one condition type in a pricing
procedure offering a discount to a customer. Should the discounts be automatically
determined, there is the risk that the customer will receive all the relevant discounts and
thus purchase the product for a lower price than he should.
By using condition exclusion groups you can ensure that the customer does not receive
all the discounts, but instead only receives the best of the available discount condition
types.
Menu path IMG - Sales & Distribution - Basic functions pricing condition
exclusion condition exclusion for groups of conditions (OV31).
A condition exclusion group is merely a grouping of condition types that are compared to
each other during pricing and result in the exclusion of particular condition types within a
group or entire groups. It is important to note that the condition types you want the
system to compare must exist in the pricing procedure and must have valid condition
records created for them.
If for example, a sales order is created using the pricing procedure that the exclusion
group is assigned to, you can see that the condition offering the most favorable discount
to the customer is represented in the pricing procedure.
For instance, condition type K007 has offered a discount of 10% off the sale price or a
real value of $30, while another condition type K005 has offered a real value discount of
$10. The system then takes the best discount for the customer between the two, which is
K007 and makes the other discount K005 inactive. This can be seen by double clicking
on the condition type K005, where you can find a entry saying Inactive A condition
exclusion item.
There are four possible methods of using condition exclusion groups
A best condition between the condition types
B best condition within the condition types
C best condition between the two exclusion groups
D exclusive
E least favorable within the condition type
F least favorable within the two exclusion groups
Configuring Condition Exclusion Groups
First step is to define a condition exclusion group by using a four character alpha
numeric key.
Next step is to assign the relevant condition types to the exclusion groups such as
discount condition types, freight condition types.
After completing the assignment of the condition types to the exclusion group, proceed
with assigning the condition exclusion group to the relevant pricing procedure.
After selecting the pricing procedure for which you want the condition exclusion to be
active, select the folder Exclusion where you can assign the relevant condition exclusion
procedure to the relevant condition exclusion group.
When using the condition exclusion group to find the best condition record in a condition
type only use one condition type per exclusion group. The most important thing to
remember here is to deactivate the Exclusive Indicator on the access sequence assigned
to that condition type. Otherwise, the system will merely find the first condition record
and stop searching for other records.
1. get information for price (discounts) that existed at previous period (Say June 200X)
2. Inform potential buyer about the current price (and discounts)
3. Review price and discounts.
Though all the above T Codes and there are many More standard SAP Reports have very
high utility, it is not widely used. Clients prefer customized reports when it comes to
pricing reports - all Z programs and Transactions.
These kind of reports are generally required by the Top Management for periodical
review // Finance team for price control // Master data team for record purposes // Process
audits by Internal/external agency // Of late, for every SOX audit done in the
company...especially the change records for prices.
Condition Index
Condition index is very useful for searching the condition record for a customer.
It becomes easier and faster to search for condition records for a customer or material just
like it become easier to search a topics in the book with help of index.
You have to mark the "condition index" check box in the condition type and you have to
activate the index in customization.
You can set the discount for fast ten orders through "condition update".
First, in your discount condition type(V/06) activate the "condition update" check box.
Second, in the condition record, in additional data put "maximum number of orders" as
10.
You may also create the condition record for discount through VK31. Now go to
change(VK32), scroll to the right, you will find a column "N". This is maximum number
of order field. Here you can put value 10 and save it.
Now, system will give the discount to the first 10 orders.
Condition base value is a concept used in pricing procedure and actual term used is
alternate condition base value. This is a formula assigned to a condition type in order to
promote an alternate base value for the calculation of the value.
If you have to calculate price of a material then you have to have a base value for it. For
e.g. if you want to calculate the discount of 10 % for a material then you have to have a
base value on which this 10% is calculated. Normally you take the condition value of the
base price of the material to calculate the value.
Now, you don't want to take the base value and take other value as base value which are
derived on some formula. So you create a routine which will do the mathematical
operations in the routine and derive you a value which is now used as the base value for
calculating the condition value for a particular condition type.
As per my understanding there is Alternative Condition Base Value, It is a routine which
is assigned to the condition type in the pricing procedure.
Go to transaction V/08 here you select pricing procedure then go in to the control data of
the pricing procedure here you can find Alter native Condition
Base Value in the 14th column of the pricing procedure control data.
What is the difference between:
1. Conditional base value
2. Conditional value.
3. Conditional amount
1. Conditional base value
When a value is derived for a condition type, based on certain calculation this value is
taken as base.
2. Conditional value.
For the number of units ordered depending on the condition amount mentioned this value
is derived.
3. Conditional amount
This is nothing but the unit list price what you are mentioning for the line item.
1) What is the role of alternative calculation type, condition base value, requirement
in pricing procedure?
2) Where do we define value for alternative condition base value and alternative
calculation type so that system picks up different value, when the value for
alternative condition base value and alternative calculation type is mention in
pricing procedure?
**Alternative Calculation Type:**
This function allows you use a formula as an alternative in finding the value of the
condition type, instead of standard condition technique. this can be used to calculate
complex tax structures.
Alternative condition base value
The alternative condition base value is a formula assigned to a condition type in order to
promote an alternative base value for the calculation of a value.
Example
An absolute header discount is, for example, distributed in the standard system according
to the cumulative value of the items.
If the system distributes the absolute header discount according to volume based on the
Alternative formula for condition base value , a header discount of $30 results in the
following discounts:
Item Value Volume .
1 $1000 2 cbm
2 $500 4 cbm
Stand. disc. Volume disc.(With Formula)
$20 $10
$10 $20
Condition formula for alternative calculation type
Alternative formula to the formula in the standard system that determines a condition.
Requirement
This function is used to assign a requirement to the condition type. This requirement can
be used to exclude the system from accessing the condition type and trying to determine
the value. This can be used to specify that the condition type should only be accessed if
the customer has a low risk credit.
To use a field not defined in the field catalog, you need to add this field to the KOMK or
KOMP structures, and then write the ABAP code to transfer the data in the field from the
transaction tables to the communication structure. Follow these steps:
1. Create the field in the KOMK (header data) and KOMP (item data) tables using the
standard includes provided for this requirement.
2. Write the code in the user exit to read the transaction data and transfer it to the KOM
x structures.
Menu Path
The menu path here is IMG, Sales and distribution, System modification, Create new
fields (using the condition technique), New fields for pricing.
Adding the Field to KOMK and KOMP
This process requires some knowledge of the ABAP dictionary and how to use the ABAP
dictionary to create and change fields and tables. You may have to use an ABAP skill to
assist you. If the field is from the header table (for example, the order table VBAK),
youll need to add it to the include table KOMKAZ in table KOMK. If the field is from
the item table (for example, the order item table VBAP), youll need to add it to the
include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price and the base material is not
in the pricing field catalog. The base material is a field on the material master basic data
screen and is defined as MARA-WRKST. Since this relates to the material, it is at the
item level, so you would add the field to the KOMPAZ include table.
Note
When you add a field to these tables, it must start with ZZ. Therefore, the
field you add would be ZZWRKST. In ABAP, when you add the field, use the same
domain as in the field in the original table MARAWRKST.
After adding the field, generate the structure KOMP. This field is not available in the field
catalog and can be used in condition tables.
Writing the ABAP Code
The field in the communications structure will be blank unless the ABAP code transfers
the data from the material master to the field KOMPZZWRKST. Pricing occurs in the
order and in the invoice, so you need to put this code in both places. For the order
transaction, write the ABAP code in user exit
USEREXIT_PRICING_PREPARE_TKOMP in include program MV45AFZZ. For the
billing transaction, write the ABAP code in user exit
USEREXIT_PRICING_PREPARE_TKOMP in RV60AFZZ.
Note : The TKOMP is for the item level. If you are writing the code for
a field at the header level, you would use the user exits that end with
TKOMK. The ABAP code would select the Base material field from the
material master table using the material from table VBAP/VBRP. It would
then transfer this field to the structure TKOMP from MOVE MARAWRKST to
TKOMP-ZZWRKST.
can only be canceled with billing type S1 with VBTYP 'N' . A billing type with
VBTYP '5' can only be canceled with the VBTYP '6' and vice versa.
3) Cancellation billing document type partner functions A check is made to see if the
cancellation billing document type partner functions are empty or if those that
correspond to the billing type used are empty.
Next, make sure that you maintain the copy control for the Billing Types:
Sales documents in VTFA
Target
e.g. F1 - Invoice
F1 - Invoice
Source
OR - Standard Sales Order
ZOR - Your Sales Order
2.
3.
4.
5.
6.
7.
8.
Item
Turbine
100,000
Billing Plan
Billing date Description
Billing Status
01-10-94
Contract
01-03-95
Assembly
01-04-95
Maintenance
01-05-95
Acceptance
01-06-95
Final invoice
Value
10
30
30
30
..
10,000
30,000
30,000
30,000
..
Network/Activities
Milestone
Assembly
Maintenance
Estimate
01-03-95
01-04-95
Actual
01-03-95
Billing Block
x
x
x
x
Milestone
x
x
x
x
Acceptance
01-05-95
For each billing date in a milestone billing plan, you can specify
whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is
earlier than the
planned billing date for the date
In Customizing for Sales, you control how the system automatically creates the schedule
of dates in a billing plan. The system determines the schedule of individual dates based
on general date information, such as the start and end dates. This general date information
is copied either from contract header data or from proposals in the billing plan type.
Pricing
Sales document items are billed as each billing date in the plan becomes due. The system
determines the amount to be billed either from the condition records that are applicable to
the item or from the values that are explicitly entered in the billing plan for a particular
billing date. In milestone billing, for example, you can specify a percentage to be billed
or an actual amount.
Billing block
A billing block can be set for each date in a billing plan. The block prevents processing
for a particular billing date but does not necessarily affect any of the other dates in the
plan. In milestone billing, the system automatically sets a billing block for each billing
date. This block remains in effect until the project system reports back that the milestone
in the corresponding network has been successfully completed. At this point the system
removes the block.
Billing index
For every billing date in a plan, the system creates and updates a billing index. If a billing
date is blocked for billing, the system copies this information into the index.
Billing status
The system assigns a billing status to each billing date in the plan. The status indicates to
what extent the billing has been processed for that particular date. After billing has been
carried out successfully, the billing status is automatically set to C. This prevents a
billed date from being billed again.
Billing Rule for Milestone Billing
For every date in the milestone billing plan, you can specify a billing rule. The rule
determines how the billing amount for the particular date is calculated. For example, you
can specify whether the billing amount is a percentage of the total amount or whether it is
a fixed amount.
In addition, you can specify that the amount to be billed is a final settlement that takes
into account billing that has not yet been processed. For example, price changes may take
place after billing dates in the plan have already been processed. The price differences
can be taken into account during final settlement.
Final settlement is not automatically proposed in the billing plan by the system; you must
enter it manually during processing.
Fixed dates in milestone billing
You can control for each date in a billing plan, whether the date is fixed or whether the
system copies the date from the planned or actual milestone dates in a project.
Document flow
After a particular date in a billing plan is processed for billing, the system updates the
document flow for the corresponding sales document item.
The document flow for the sales document displays the following data:
Creation date
Billing date
Billed value
Is it possible to split invoice Item category wise. I mean If in sales order there is
TAN and TANN then the invoice should split,is it possible?
Naina
Yes, it is possible. Create a modification of copy control routine for billing and use
VBAP-PSTYV as an additional split criteria there.
Martishev Sabir
Thank you for your reply. Can you please tell me the exact steps what should I add
under that(additional split criteria).
Naina
In trx VTFA (if your billing is sales order based) choose your billing type and SO type,
there select your item categories and there select the field VBRK/VBRP data. In that field
you will see the currently used routine. With the help of your ABAP guy create a copy of
that routine under a different number and add your lines of code. Let's say you use
routine 001.
FORM DATEN_KOPIEREN_001.
* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
VBRK-ZUKRI = ZUK.
ENDFORM.
This is how it should look after modification:
* Header data
* VBRK-xxxxx = ............
* Item data
* VBRP-xxxxx = ............
* Additional split criteria
DATA: BEGIN OF ZUK,
MODUL(3) VALUE '001',
VTWEG LIKE VBAK-VTWEG,
SPART LIKE VBAK-SPART,
PSTYV LIKE VBAP-PSTYV, <- New line
END OF ZUK.
ZUK-SPART = VBAK-SPART.
ZUK-VTWEG = VBAK-VTWEG.
ZUK-PSTYV = VBAP-PSTYV. <- New line
VBRK-ZUKRI = ZUK.
ENDFORM.
After this routine is created and activated place it as the default copy control routine
instead of the old ones.
To overcome this, the only way was to break the accounting invoices, 1 with 950 items
and the other with the rest.
with item category groups (can be used to determine what default item category that
should appear). This would mean that you either have different materialnumbers for the
different processes or use different distribution channels in the sales order. DC 10 could
be
the normal process and DC 20 the prepaid process. Then you need to create the sales
views in material master for DC 20 for all materials that should be possible to run in the
prepaid scenario, and enter the "prepaid item category group in the sales item category
group field in material master.
Here is a proposal of customizing activities to achieve this:
1. Create a new item category as a copy of the normal item category used for non-prepaid
sales. (Change the billing in the item category to order related billing with no billing
plan)
2. Create a new item category group "ZXXX" or something of your choice with the
description "Prepaid" or something like that.
3. In item category assignment, add or check entries so that you have the order type used,
and item category group defaulting the new item category.
4. Check copy control from sales document to billing document for the new item
category.
Also delivery copy control could be good to check.
5. Create a new distribution channel and assign it to the company structure (plant, sales
org etc)
6. Extend your material(s) with views for the new distribution channel and enter the
"ZXXX"
item category group in the field for sales item category group (I think it is on sales 2
screen
but I am not sure, can't access a system right now).
Now you should be able to create a sales order with the new distribution channel where
the new item category is defaulted. Check that the sales order is completed when both
billing and goods issue for the delivery is posted. If not check the completion rule in the
new item category.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion
with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions:
Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order
Types to required Sales Area. This will minimize selection of Sales Order Type as per
sales area.
Sales Document Item:
*1. Define Item Categories: If possible use Standard Item Category. Incase if required to
create new, copy as from standard & maintain New.
*2. Assign Item Categories: If possible, use standard. Formula for deriving item category:
Sales Document Type + Item Category Group + Usage + Higher Level Item Category =
Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if
required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving
Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
*1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to
create new, copy as from standard & maintain New.
*2. Define Item Categories for Deliveries: If possible use Standard Item Categories for
Delivery Type. Incase if required to create new, copy as from standard & maintain New.
*3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create
new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls
such as Sales Order to Billing, Deliver to Billing, etc.
Note: Ensure that Copy Control settings are done
Sales Order to Sales Order (QT --> OR): VTAA
Sales Order to Delivery (OR --> LF): VTLA
Sales Order to Billing (OR --> F1): VTFA
Delivery to Billing(LF --> F2): VTFL
Billing to Sales Order (F2 --> RE): VTAF
The configuration differs from scenario to scenario & requirement of the
client.
5. Continue further to complete the task, now you batch job will run at a specified time
which you mentioned, if you mentioned as immediately, then once you comple this
process, your vairant will run, and billing documents will be created.
6. Plese ensure that all the deliveries are perfect, meaning there is no billing block or any
thing.
You can check the status of your batch job using t. code SM37.
Difference between the RSNAST00 and SDBILLDL program.
RSNAST00 is a program which is related to output related activities. Using this program,
we can schedule the creation of outputs (PDFs, email etc) in total for any document
created in any of the applications. The details are read and stored in the database table
NAST. The same program is customised for each applications using programs like
SD70AV1A which are also used for the same purpose but only for sales orders.
SDBILLDL is the program for Billing due list. This program finds out all the orders or
deliveries or both which are due for billing and it will trigger the billing creation. It reads
tables like VBAK, VBAP, VBUK, VBUP, LIKP, LIPS etc and the created billing
documents are stored in tables VBRK, VBRP.
Check your DIP Profile; specifically the sources section to ensure you are not filtering
out any dynamic items.
CO Configuration:
KL03: Check activity type validity dates
KA03: Check cost element validity dates
KA03: For labour, check cost element category is 43
KA03: Check if Record qty flag is set on Indicators tab
KA03: Check cost element assigned to your controlling area
KP26: Check that activity type is linked to cost centre
KP26: Check that there is a rate for the activity type/cost centre
KP26: Check are you using the correct version
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.
Tips by : Kapilaa
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:
Code:
DATA: W_ZSDCRD TYPE ZSD_CREDITBLCK.
DATA: W_CMGST LIKE VBUK-CMGST.
SELECT SINGLE * INTO W_ZSDCRD
FROM ZSD_CREDITBLCK
WHERE KKBER = VBAK-KKBER
AND CTLPC = VBAK-CTLPC.
IF SY-SUBRC = 0 AND VBUK-CMGST CA 'B'.
IMPORT VBUK-CMGST TO W_CMGST FROM MEMORY ID 'CREDIT'.
IF W_CMGST = SPACE.
MESSAGE I706(Z1).
EXPORT VBUK-CMGST TO MEMORY ID 'CREDIT'.
ENDIF.
*} REPLACE
*{ INSERT DEVK966908 1
*} INSERT
* Read the subsequent function information for the message
PERFORM FOFUN_TEXT_READ USING GL_FOFUN
CHANGING FOFUN_TEXT.
MESSAGE ID 'V1' TYPE 'E' NUMBER '849'
WITH FOFUN_TEXT
RAISING ERROR.
*{ INSERT DEVK966908 2
*} INSERT
ENDIF.
ENDFORM.
Rich Dragani
-----Reply Message----Subject: Re: LOG: Credit Mgmt Dynamic checking
From: Swami Subramanyan
Program RVKRED08? Or manually execute function module
SD_ORDER_CREDIT_RECHECK.
Regards
Swami
-----Reply Message----Subject: Re: Credit Mgmt Dynamic checking
From: Leslie Paolucci
We check credit at the time of the delivery (at delivery creation and before picking) and
use the blocked sales doc process/list to release them. This can be set up in customizing
under risk management-> credit management.
-----End of Reply Message-----
Hi,
You need to check couple of settings like:
1. Your customer should be assigned the credit control area.
2. In your Item Category Credit should be active.
Regards,
-----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing
customer is assign to concorn CCA and item category is mark for credit active
-----Reply Message----Subject: RE: Sales value field in not getting updated after creating the billing
Hi,
Check the credit update group in the transaction OB45. The credit update group controls
when the values of open sales orders, deliveries and billing documents are updated. It
should be '000012'.
Further also refer to the OSS note 18613.
Have fun
-----End of Message-----
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
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 no
Credit Check 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 02 defined for payment cards. Other than the
descriptor, the only other entry should be 3 in the column labeled PymtGuaCat
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 1
Payment Guarantee Form 02
Routine Number 0 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 = Payment Card Payment Cards (All Customers
can use Payment Cards).
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
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 03 in the column labeled
PT 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.
function modules for authorization and settlement along with the proper RFC destinations
for each.
Enter Merchant IDs
Transaction:
Tables: TCCM
Action: Create the merchant ids that the company uses to process payment cards
Assign merchant ids
Transaction:
Tables: TCCAA
Action: Enter the merchant ids with each clearinghouse account
- Amount limits
- Texts for the dunning notices
In SAP, you will maintain the Dunning Procedure at customer master. Referring to this
your SD Team / FI Team (user team) will effect Dunning
PS: You might remembered the dunning procedure laid by Relaince Mobile, sometime
back, sending street rowdies for recovering the bad debts from users. That is dunning.
Remember Reliance, you will not forget dunning forever.
3. What role exposure play in the credit management process. I mean does the
system match the value of credit exposure with credit limit to find that it is exceeded
or it does it differently?
Credit exposure is in fact the main player. In credit management if the customers credit
limit is 10000 and credit exposure is 9900 then customer can only be able to buy now
worth of 100 only. Its the credit exposure which should not crossed over the credit limit.
For reporting purpose, where we can get customer credit exposure which showing in
FD32.
Go to t.code F.31 for an overview of the credit exposure, and also you can use
s_ALR_8701212218 to overview the credit exposure.
excise duty.
- The maximum number of items to be printed on each excise invoice
- Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has
registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is
located.
Excise Collectorate: The code of the excise collectorate in whose area the excise
registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to
basic excise duty and special excise duty. Example - Additional Excise duty is livable in
case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum
number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and
Distribution (SD) for factory sales and for other movements. This information is used to
split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only
a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on
the material into its deductible and nondeductible amounts. It posts the deductible duty to
the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in
Financial Accounting (FI). Here ED is document type for cenvat posting.
Exchange rate type - Key representing a type of exchange rate in the system.
- You enter the exchange rate type to store different exchange rates. Example - You can
use the exchange rate type to define a buying rate, selling rate, or average rate for
translating foreign currency amounts. You can use the average rate for the currency
translation, and the bank buying and selling rates for valuation of foreign currency
amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an
Excise invoice for export sales then the exchange rate for duty calculation will be picked
up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to
your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
- Specify whether it is a manufacturing site or a depot.
- Assign it an excise registration ID. - You can assign the same ID to more than one plant,
if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare
register RG 23D, and follow different procedures for goods receipt and invoice
generation.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each
excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to
maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and
PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every
business to maintain only one set of excise registers and one set of accounts. But through
exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one
excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI
as blank. If you receive multiple GR's for a given Excise challan and would like to avail
multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple
credit'. Alternatively if you want to availa the credit only after all the goods receipts
have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of
billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately
and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto
post'. This will post the selected records into RG23D automatically. You cannot cancel
the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan
quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for
RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements
automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of
material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material
through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the
receipt of material into consumption stock. Excise Group Governs which set of excise
registers a business transaction will be included in.
Following is the relation between excise group, plant and registration. - In define excise
groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise
invoice, you specify which excise group you are using. This information tells the system
which G/L accounts to post the excise to. At the end of the period, when you come to
prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG
23D, and follow different procedures for goods receipt and invoice generation.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales
and Distribution (SD) excise invoice immediately you create a commercial invoice or a
pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this
function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution
(SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will
create Depot excise invoice by posting the selection of excise invoices in single step. If
this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic
posting of RG23D selection then the Post Goods Issue should have been completed
before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt
using 'MB01' system will default the excise invoice quantity on to the Goods receipt
document.
Folio number for depo Posting - If this indicator is marked then while creating Excise
invoice for other movements system automatically does the Verify and Post. You need not
separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
- Blocked stock
- Stock transport order
- Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups
within your company. Series groups allow you to maintain multiple number ranges for
the outgoing excise documents. Based on excise regulations and exemptions from the
authorities you can maintain multiple number series for outgoing documents. But each of
these series has to be declared to the excise authorities.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you
tick the 'No utilization' indicator.
- If the CENVAT has to be paid immediately and you need not wait for the Fort nightly
payment then mark the 'Immediate Utilization' Iindicator. Example - You could define
two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
- No account postings for CENVAT in sales cycle
- No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just
generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group
but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the
system immediately pays the amount from CENVAT and creates the Part II entry. Such
invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the
account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being
done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty
indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings >
Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining
excise duties and sales taxes on input materials in India.
- If you use condition-based excise determination, use a copy of the tax procedure
TAXINN.
- If you use formula-based excise determination, use a copy of the tax procedure
TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can
work with both concurrently.
We strongly recommend that new customers use condition-based excise determination.
Note that once you have started using a tax procedure, you cannot switch to another one,
otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and
pricing condition types are used in calculating excise taxes using formula-based excise
determination.
If you use condition-based excise determination, fill out the CVD cond.
field and leave all the others blank.
If you use formula-based excise determination, fill out all of the
fields as follows:
- Enter the tax procedure and the pricing conditions that are relevant
for excise tax processing.
- Specify the purchasing and sales conditions types used for basic
excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise
rates.
- Specify the countervailing duty condition type used for import
purchase orders.
In my company, we use project stock (movement type 601 Q for PGI). VL09 creates the
movement type 602 Q. But rather than VL09, the generally accepted method in my
company for the reverse items is to use the movement type 653, "back to the to the
storage location." The accounting document takes the cost "from" the project and moves
it back "to" the storage location.
The movement types are entered in the schedule lines in customizing, which are then
assigned to the item categories. However, in this process, "no invoice" takes place. If you
have a delivery related invoice, it should be cancelled beforehand.
If you do not give replacement, the Customer Account needs to be credited.
Please do not forget to create a Billing document (Formally Return Credit Memo) with
reference to return delivery. It is very important in order to close the cycle. If you do not
create a return credit memo, your delivery will keep appearing in the "Billing Due" list
and with status "Being processed". When you create a return order type RE, the billing
type is picked up as RE (Return Credit Memo) automatically.
When you are creating a replacement, you can create a replacement order, delivery, and
billing. To create the replacement order, you can define an order type by copying from
order type OR. In the copy control, you can define the relevant item categories from RE
to OR. You can make reference Mandatory for this order type. The delivery type for this
replacement order type will be LF and billing type F2.
When you create a return based on a complaint, you: Post the goods to your warehouse
for checking And then, implement one of the following activities:
- Approve the complaint and create a credit memo
- Approve the complaint, and implement a free of charge subsequent delivery based on
the return
- Reject the complaint
PGI (Post Goods Issue) may be cancelled by Transaction code VL09. The accounting
document is just the reverse of the original PGI document.
In my company, we use project stock (movement type 601 Q for PGI). VL09 creates the
movement type 602 Q. But rather than VL09, the generally accepted method in my
company for the reverse items is to use the movement type 653, "back to the to the
storage location." The accounting document takes the cost "from" the project and moves
it back "to" the storage location.
The movement types are entered in the schedule lines in customizing, which are then
assigned to the item categories. However, in this process, "no invoice" takes place. If you
have a delivery related invoice, it should be cancelled beforehand.
If you do not give replacement, the Customer Account needs to be credited.
Please do not forget to create a Billing document (Formally Return Credit Memo) with
reference to return delivery. It is very important in order to close the cycle. If you do not
create a return credit memo, your delivery will keep appearing in the "Billing Due" list
and with status "Being processed". When you create a return order type RE, the billing
type is picked up as RE (Return Credit Memo) automatically.
When you are creating a replacement, you can create a replacement order,
delivery, and billing. To create the replacement order, you can define
an order type by copying from order type OR. In the copy control, you
can define the relevant item categories from RE to OR. You can make
reference Mandatory for this order type. The delivery type for this
replacement order type will be LF and billing type F2.
partner function for each level. In the partner procedure, in each partner function you
must indicate the source partner function. With this informacition, in the order, you
obtain the bussiness partner for each partner function.
3) Assign acount groups: you indicate which accounts groups are allowed for being part
or your hierarchy.
4) Assign sales areas: symple you indicate wich sales areas are allowed in your hierarchy.
(Here you can customize common sales areas, just for not having to build de hierarchy in
all the different sales areas).
5) Assigning hierarchy type for pricing: you indicate which classes of documentos uses
hierarchy in pricing determination.
It is possible to maintain so called customer hierarchies. This might be useful when for
example you create a condition discount for a customer that is part of such a hierarchy
structure. All subnodes in the hierarchy below that customer, will thus receive the same
discount.
Customer hierarchy setup, firstly decide the hierarchy type to be used.
The standard is type A.
You can also assign a partner function to the customer so that the higher level customer in
the hierarchy is copied into a sales order as a partner function - but you don't need that
right?
Next assign your customer account group to the hierarchy type. And enter the
combinations that will be allowed for creating the hierarchy.
You want to assign a ship-to to a payer. So enter the ship to account group and enter the
payer account group as the higher level.
You must also make an entry for permitted sales area assignments. So if you want to a
hierarchy for customers in the same sales area then enter the sales area and enter the same
one as the higher level sales area.
All these settings can be found in the IMG. Under SD - master data - business partners customers - customer hierarchy
You use for example customer hierarchy when you have an company like Unilever and
you agree both on a discount. Unilever does have different locations / businesses and you
have to maintain the discount for all customers. If you use a customer hierarchy you can
maintain the discount for the partner in the top of the hierarchy and in this way it will be
valid for all customers in the hierarchy.
Product hierarchies can be created using code OVSV. A product hierarchy is assigned to
the material master record. The hierarchy is broken down into specific levels, each level
containing its own characteristics.
A product hierarchy is recorded by the sequence of digits within a hierarchy number. The
hierarchy number can have a maximum of 18 digits with a maximum number of nine
levels.
Thus by assigning the hierarchy number to the material, one can determine a
classification of the material. This hierarchy can be used in pricing with each level being
used as field in the condition technique.
Its like if you are having category CAR. In that many cars come into picture.
CAR>>MARUTI>>SX4, Swift, zen, alto.
B>> 01 >>01
Then from above example B0101 is the hierarchy for SX4.
So in that hierarchy many cars come, like variants and all the things.
In this way you can take e.g. of wood products also.
It shows the next level of the product. How many levels that product are
having.
The product hierarchy can be structured via DDIC structure PRODHS. In the standard
system, a product hierarchy can be created with up to three levels. The individual levels
can contain the following number of digits:
Level number of allowed digits:
15
25
38
This can be changed as of Release 3.0, where it is possible to extend the maximum
number of levels to 9.
If you want to change the standard setting of PRODHS, e.g. you want to change the
number of levels, proceed as follows:
1. Create an appropriate domain in the Data Dictionary (type CHAR with the required
length).
2. Assign these domains to the standard data elements PRODH1, PRODH2, ..., PRODH9.
Please note that you should use these standard data elements.
3. Change the structure PRODHS by creating or deleting fields with reference to the data
elements.
Choose ZZPRODHN as field name, where n is the position of the field in the structure
PRODHS.
You want to change the structure of the product hierarchy from 5/5/8 digits to 5/5/5/3.
Proceed as follows:
Create the following domains:
ZPRODH3 with length 5, category CHAR,
ZPRODH4 with length 3, category CHAR,
Change structure PRODHS:
Structure PRODHS in the standard system:
Structure Fields Data element Category Length
PRODHS ->
PRODH1 PRODH1 CHAR 5
further break down a procedure into smaller parts for future validation of components
comprising a specific material
3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the
assignment of an allocation procedure to an LIS information structure. Secondly, a
character is assigned to the information structure to permit collective planning. Finally,
the user can assign a step level to the procedure and information structure to sequence the
order in which allocation quantities are checked. This functionality allows the user the
opportunity to check product allocation against several product allocation scenarios,
before the required quantity is confirmed
4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality
is only valid if the allocation method flag has been set (OV1Z). If you have de-selected
the method field, this functionality is not available. The consumption window indicates
the number of past and future periods to be used in the allocation check.
5.Control Product Allocation (OV4Z) In order for the allocation process to function
properly, allocation control records are created primarily to map allocation procedure
steps to their corresponding objects so that the allocation data records can be located for
validation. Secondly, validity periods must be established to indicate when the allocation
control records are active. Finally, the user has the option of establishing a conversion
factor per allocation control record to accommodate BOM listings of constrained
materials
6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the
standard order processing functionality, the requirements class must have a flag
indicating that allocation is relevant.
7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation
in the standard order processing functionality, the schedule line must have a flag
indicating that allocation is relevant
8.Create Planning Hierarchy (MC61) In order to adequately establish allocation
quantities, the user must initially determine the level at which the allocation is to take
place and the aggregation factor of the allocation quantities. In this step, the levels for the
collective allocation search procedure are also identified.
9.Generate Masking Character (OV7Z) Upon completion of the level determination for
the planning hierarchy, the collective allocation masking character must be generated to
allow aggregation indicators to be established. This transaction simply reads the
hierarchy established in the planning table and then generates a collective mask character
for each level of the hierarchy
10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial
hierarchy was established. In order to complete the hierarchical set up, the collective
allocation (mask character) hierarchy must now be maintained with the appropriate
aggregation factors
11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the
allocation process are the materials. Each material that is to be considered in allocation
scenario must be mapped to an allocation procedure. In order entry, then, when a material
is entered with a valid allocation procedure in the material master, the allocation data is
verified prior to confirming the line item ordered
12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS
information structures that can be used in the product allocation process. This report
simply reads through the data dictionary and selects all the active information structures
that contain the field product allocation object (KONOB) as the first field. This data can
then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step
to an information structure (previous step).
zche_sales_order
****************************Declarations********************************
TABLES: vbkd,vepvg.",vbak,vbap,vbpa,vakpa, vapma.
DATA: BEGIN OF sal OCCURS 0,
ch TYPE checkbox,
vbeln LIKE vbak-vbeln,
netwr LIKE vbak-netwr,
matnr LIKE vbap-matnr,
waerk LIKE vbak-waerk,
dat
LIKE vbak-erdat,
END OF sal.
DATA: newsal LIKE sal OCCURS
LOOP AT newsal.
ON CHANGE OF newsal-dat.
IF sy-tabix <> 1.
WRITE:/ sy-vline, AT 14 sy-vline,AT 27 sy-vline,AT 48 sy-vline.
WRITE:/ sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline.
ELSE.
WRITE: sy-vline,newsal-dat,sy-vline,AT 27 sy-vline,AT 48 sy-vline.
ENDIF.
ENDON.
WRITE:/ sy-vline, AT 14 sy-vline,newsal-vbeln,sy-vline,
newsal-matnr, sy-vline, newsal-netwr, newsal-waerk.
AT LAST.
SUM.
ULINE. FORMAT COLOR = 3.
WRITE:/ sy-vline, AT 15 'Total Amount for selected month:',
newsal-netwr UNDER newsal-netwr.
FORMAT COLOR OFF.
ULINE.
ENDAT.
ENDLOOP.
lin = 1.
FREE newsal.
ENDFORM.
"SELECTION
* This Date convertion is must for pick the particular Date from the
*
-displayed line, and here we are reversing the Date like
YYYY/MM/DD
* -because to Check or assign the date we need to give in reverse
order
*&--------------------------------------------------------------------*
*&
Form DATECON
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM datecon.
date2 = sy-lisel(17).
SHIFT date2 LEFT BY 4 PLACES.
WHILE date2 <> ''.
SHIFT date2 RIGHT.
date4 = date2+11.
IF date4 <> '.'.
CONCATENATE date4 date3 INTO date3.
ENDIF.
ENDWHILE.
date5 = date3(2).
date6 = date3+2.
date3 = date3+4.
CONCATENATE date3 date6 date5 INTO date3.
dat = date3.
* SORT dat BY dat.
* DELETE ADJACENT DUPLICATES FROM dat COMPARING dat.
ENDFORM.
"DATECON
* Here we are doing different kinds of selections by the EndUser's
needs
*&---------When user selectiong an Sales Organisation-----------------*
*&
Form ORGANISATION
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM organisation.
SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln,
sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN
vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON
f~vbeln = p~vbeln WHERE p~audat IN date AND p~vkorg = vkorg.
APPEND sal.
ENDSELECT.
ENDFORM.
"ORGANISATION
*&---------Without Sales Organisation i.e All Organisation------------*
*&
Form ORGANISATION_ELSE
*&--------------------------------------------------------------------*
*
text
*---------------------------------------------------------------------*
FORM organisation_else.
SELECT f~vbeln p~matnr c~netwr c~waerk p~audat INTO (sal-vbeln,
sal-matnr, sal-netwr,sal-waerk, sal-dat) FROM ( vakpa AS f INNER JOIN
vbak AS c ON f~vbeln = c~vbeln ) INNER JOIN vapma AS p ON
f~vbeln = p~vbeln WHERE p~audat IN date.
APPEND sal.
ENDSELECT.
ENDFORM.
"ORGANISATION_ELSE
"CUS_ORGA
field, you can explicitly specify a recipient that will override the standard partner. There
must also be a master record for the partner that is specified explicitly.), Medium, Time &
Language.}
Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time &
Language.
Path For Output Determination For Sales Documents: Logistics -> Sales/distribution ->
Master data -> Output -> Sales Document -> Create (t-code VV11)
Path for Output Determination for Delivery Documents : Logistics -> Sales/distribution
-> Master data -> Output -> shipping -> Create ( t-ode VV21)
Path for Output Determination for Billing Documents : Logistics ->
Sales/distribution -> Master data -> Output -> Billing Document ->
Create ( t- code VV31)
Print DDueList
SpK
SpW
06 No printing
07 Quantity Change
08 Kanban Delivery
Printing block field:
Indicates whether the system automatically blocks output for sales documents that are
blocked for delivery.
Example :
In the case of sales orders that are blocked for delivery because of credit reasons, you
may want to block the printing of order confirmations.
Note:
The particular output that is affected by a delivery block is determined in output control.
PS: If the document is exceeds by the credit limit output type will not determine and as
well as we should not give the output type in sales order. We have to assign the routine 2
to sales order output types and 3 routine to delivery output types to restrict from output if
the docuement exceeds by credit limit.