Please explain me about pricing determination procedure in SAP SD ?

Could you please explain me about the pricing determination procedure in SAP SD ?
Edited by: Piruthiviraja on Aug 18, 2009 8:00 AM

Hello,
Please go through the following
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Basic Function u2013> Pricing Control u2013> Pricing Procedure -> Determine Pricing Procedure.
Step 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.
SANTOSH

Similar Messages

Please explain me about SDM & JSPM

Hi Experts
please explain me about SDM & JSPM,
what is diffrence between SDM & JSPM and why we use both tools.
please provide me any documents or any links about SDM & JSPM.
Regards
BANDLA

Dear Kondalu,
SDM & JSPM are used to manage support packs in Java stack, As of SPAM in Abap stack.
SDM was used in versions 3.0
Find the link
http://help.sap.com/saphelp_nw04/helpdata/en/63/2c4f65a54c4a4db1a3600397ae617f/content.htm
JSPM is used from 7.0 and above.
Java Support Package Manager is a software deployment tool that can be used for installing business packages, software components, and SAP kernel binaries.
Java Support Package Manager can be used for the following:
u2022 Installing support package stacks for existing software components
u2022 Installing support packages for existing software components
u2022 Installing or upgrading business packages
u2022 Updating SAP kernel binaries, Software Delivery Manager (SDM), and Internet Graphics Service (IGS)
u2022 Self-updating Java Support Package Manager so that the latest version is used
u2022 Deploying new SAP and non-SAP software components
u2022 Installing additional usage types such as Enterprise Portal (EP) or Process Integration (PI)
Regards
Injamuri

Please explain what are the various procedures to find user-eixts

Hi,
Please explain what are the various procedures to find user-eixts ?
Ramana

Hi,
1. By executing this Program.
*& Report ZFIND_EXIT
REPORT ZFIND_EXIT.
*report zbadi_find .
tables : tstc,
tadir,
modsapt,
modact,
trdir,
tfdir,
enlfdir,
sxs_attrt ,
tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode,
p_pgmna like tstc-pgmna .
data wa_tadir type tadir.
start-of-selection.
if not p_tcode is initial.
select single * from tstc where tcode eq p_tcode.
elseif not p_pgmna is initial.
tstc-pgmna = p_pgmna.
endif.
if sy-subrc eq 0.
select single * from tadir
where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir
where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir
where pname = tstc-pgmna.
select single * from enlfdir
where funcname = tfdir-funcname.
select single * from tadir
where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object in ('SMOD', 'SXSD')
and devclass = v_devclass.
select single * from tstct
where sprsl eq sy-langu
and tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(105) sy-uline.
format color col_heading intensified on.
Sorting the internal Table
sort jtab by object.
data : wf_txt(60) type c,
wf_smod type i ,
wf_badi type i ,
wf_object2(30) type c.
clear : wf_smod, wf_badi , wf_object2.
Get the total SMOD.
loop at jtab into wa_tadir.
at first.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Enhancement/ Business Add-in',
41 sy-vline ,
42 'Description',
105 sy-vline.
write:/(105) sy-uline.
endat.
clear wf_txt.
at new object.
if wa_tadir-object = 'SMOD'.
wf_object2 = 'Enhancement' .
elseif wa_tadir-object = 'SXSD'.
wf_object2 = ' Business Add-in'.
endif.
format color col_group intensified on.
write:/1 sy-vline,
2 wf_object2,
105 sy-vline.
endat.
case wa_tadir-object.
when 'SMOD'.
wf_smod = wf_smod + 1.
select single modtext into wf_txt
from modsapt
where sprsl = sy-langu
and name = wa_tadir-obj_name.
format color col_normal intensified off.
when 'SXSD'.
For BADis
wf_badi = wf_badi + 1 .
select single text into wf_txt
from sxs_attrt
where sprsl = sy-langu
and exit_name = wa_tadir-obj_name.
format color col_normal intensified on.
endcase.
write:/1 sy-vline,
2 wa_tadir-obj_name hotspot on,
41 sy-vline ,
42 wf_txt,
105 sy-vline.
at end of object.
write : /(105) sy-uline.
endat.
endloop.
write:/(105) sy-uline.
skip.
format color col_total intensified on.
write:/ 'No.of Exits:' , wf_smod.
write:/ 'No.of BADis:' , wf_badi.
else.
format color col_negative intensified on.
write:/(105) 'No userexits or BADis exist'.
endif.
else.
format color col_negative intensified on.
write:/(105) 'Transaction does not exist'.
endif.
at line-selection.
data : wf_object type tadir-object.
clear wf_object.
get cursor field field1.
check field1(8) eq 'WA_TADIR'.
read table jtab with key obj_name = sy-lisel+1(20).
move jtab-object to wf_object.
case wf_object.
when 'SMOD'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
when 'SXSD'.
set parameter id 'EXN' field sy-lisel+1(20).
call transaction 'SE18' and skip first screen.
endcase.
2. . Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
3. 1. in se11, goto table MODSAP
View table contents
in Type field, enter
'E' (for user exit / Function Exit)
OR 'S' (for screen exit)
4. Calling Customer- fucntion in Main Program
Thanks,
Anitha

Please tell me about Enhancement Techniques used in SAP Other then BADI/Usr

Hi Experts .
Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
1.) what is set and how to create it ?
2.) What is formula is SAP and How to set it for Enhancement Pupose .
3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
Please Elabarate the reply with step by step procedure .
Thanx .
Regards : Rajneesh

Hi Raj,
Check these links
help.sap.com/saphelp_nw04/helpdata/en/eb/3e7ceb940e11d295df0000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
Regards,
Sana.
reward for useful answers..

Please explain me about customer exist program ZXRSRU01

Hi all,
I do not have enough knowledge to code for a customer exist.
please explain me for the below scenerio.
Dimensions                                                        Key figures
Business Partner (ZH11).
Created On Date (ZH22).
Status (ZH33).
Product (ZH88)
Product contains following
Product l1(zid1)
Product release description.
for this product release description for every new release we creating a variable.
and using this variable we are creating a restricted key figure as follows.
1.1 1.2 1.3. like this
My requirement is a query is already created for report to show bugs weekly releases.
I have to find out a way if the transaction contains a new version then i have to add new column in the output of the report (for example 1.4,1.5...)
as I do not have knowledge in ABAP please explain me how to solve this problem.
I do not have enough regarding Zxrsruo1.
if contains some predefined components.
Please explain for the predefined components.
IMPORTING
*"     VALUE(I_VNAM) LIKE RSZGLOBV-VNAM
*"     VALUE(I_VARTYP) LIKE RSZGLOBV-VARTYP
*"     VALUE(I_IOBJNM) LIKE RSZGLOBV-IOBJNM
*"     VALUE(I_S_COB_PRO) TYPE RSD_S_COB_PRO
*"     VALUE(I_S_RKB1D) TYPE RSR_S_RKB1D
*"     VALUE(I_PERIV) TYPE RRO01_S_RKB1F-PERIV
*"     VALUE(I_T_VAR_RANGE) TYPE RRS0_T_VAR_RANGE
*"     VALUE(I_STEP) TYPE I DEFAULT 0
*" EXPORTING
*"     VALUE(E_T_RANGE) TYPE RSR_T_RANGESID
*"     VALUE(E_MEEHT) LIKE RSZGLOBV-MEEHT
*"     VALUE(E_MEFAC) LIKE RSZGLOBV-MEFAC
*"     VALUE(E_WAERS) LIKE RSZGLOBV-WAERS
*"     VALUE(E_WHFAC) LIKE RSZGLOBV-WHFAC
*" CHANGING
*"     VALUE(C_S_CUSTOMER) TYPE RRO04_S_CUSTOMER OPTIONAL
Thanks,
James

Hi James,
You are talking about the include we use to write the user exit for variables in BW.
There are a lot of code examples that Edwin posted in the forum so you can use them to code yours.
A little bit of details on the paramaters in the include:
I-Vnam : The variable name to be calculated
i_t-Var_range: A table that contains all the system's variables data
i_step: The step for variable determination: 0,1,2 or 3.
i_step= 1: used to call default variables, called once per variable before the variable screen is displayed
istep= 2: used for those variables that are not ready for input, called after the variable screen is displayed
i_step=3 : Used for valiadation purposes, and called after isep=2
e_t_range: Is the table that the exit populated the varaible value to.contains the following important fileds:
   low: contains the value of the lower limit for intervals, for text variables it contains the text and for formula vatiables the calculated value.
   high: contains the upper limit for intervals
   sign: ususally I (Include), can be also E (Exclude)
   opt: usually EQ (Equal) or BT(Between)
See also:
https://websmp202.sap-ag.de/~sapdownload/011000358700002762582003E/HowToDeriveVariableValue.pdf
Hope it helps, if so please assign points,
Gili

While doing pricing determination procedure in ovvkk

while doing pricing procedure process i.e., creating condition tables, accseques, types and finally assigning in ovkk, is there a necessary to declare the condition type or it directly takes it, another thing do we require a condition table for PR00 also.

write-up on pricing procedure:
Check the Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): 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 (T.Code: V/07): 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 (T.Code: V/06): 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 (T.Code: V/08): 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 (T.Code: VOK0): 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 (T.Code: VK11 / VK12): 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. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Please explain me about data mating. i got a question in the interview

dear experts,
can any body help me in explanation about the data mart, what is the functionality of the data mart altogether. what are the senarios we use the data mart concept.
please respond with a clear elaboration of the topic.

hi krishna,
in data mart staus cube, ods behaves like sources.means whenever u want to load data from one data target to oher, then v ll get dm staus.its my self bw system.
ODS:
whenever u create update rules on ods, ods technical name will be prefixed with 8,
means its ready to behave like source to other targets.
CUBE;
in case of cube its different, manually we have to make it as source, by right click on cube, click on export generate data source,now the update rules name ll be
8 followed by cube name.
u can check the data mart staus in manage data target screen, in request tab page..u ll find one column dm staus.
hope it helps,
assign points,
regards,
yunus

Please explain this about URL rewriting

I am trying to write a simple example to understand URL rewriting...
On Test1 Servlet in the doGet I have the following
               HttpSession session = req.getSession(true);
               session.setAttribute("userid","123");
               String url = resp.encodeURL("Test2.jsp");
               System.out.println(url);
               resp.sendRedirect(url);In the Test2.jsp I have the following
<P>OK......</P>
<%String id = (String)session.getAttribute("userid");%>
<%=id%>Even though I see the URL being appended like
http://localhost:9080/urlTest/Test2.jsp;jsessionid=00006O173z1PBf6mXOujvK25iJc:-1
and I also see the result 123 on the screen...
How do I know that its not using HttpSession and its using URL rewriting?

The call to encodeURL is what is putting the "jsessionid" section into the URL. That is what it is using to maintain the session.
So it IS using HTTPSession, but the sessionid is being maintained via URL rewriting, rather than with a session cookie.
As an experiment, take out the call to "resp.encodeURL()" and see what the result is.
Also, if you are using the url to redirect to, you should be using the method response.encodeRedirectURL. The rules for encoding a url being used as a redirect are slightly different from one being used as a link on a page.

Difference between tax determination procedure and pricing procedure....

Hi,
What is the use of Tax determination procedure when we maintain tax condition types in pricing procedure.(and condition records will pick the correct tax rates).
My question is that, can we trigger an o/p tax without maintaining a tax procedure at document type level?If yes then what is the basic use of tax determination procedure in SAP?

Tax procedure is being used in the Country Version India Add-On and requires to maintain additional data in the Excise Rate Maintenance transaction, J1ID. Each of the excise duties in the tax Procedure Tax procedure has its own condition types, and each condition type is assigned to a formula in the standard SAP. This formula instructs the system to calculate the excise duty using the data that have been maintained in the Excise Rate Maintenance transaction.
FTXP for a country is determine from TAX procedure assign to the country.
[Entering content frame formula-based excise determination (LO)|http://help.sap.com/saphelp_470/helpdata/pt/e6/2adbdec6974f4c9f35d732b108d09e/content.htm]
[Formula-Based Excise Determination|http://help.sap.com/saphelp_47x200/helpdata/de/20/53bfce14ff11d4b5b1006094b9ec21/content.htm]
[Condition-Based Excise Determination|http://help.sap.com/saphelp_470/helpdata/ru/08/34bc3cdc322866e10000000a114084/content.htm]
Thanks & Regards
JP

Text determination procedure with sales doc type

For the Sales Doc type 'OR' , I am getting TEXT automatically in the Sales Order Header data , TEXT tab page.
Can Any one tell me how can I remove the text, when i create sales order.
Or please can any one give me the document or link or explain how the text determination procedure with sales doc type.

Hi Sanjay,
Thanks for your help.
I managed to go there but I am really confused of what changes I have to do there.
If you dont mind can you explain a bit in detail.
Sorry for the trouble

Campaign Pricing Determination

Hi,
Does anyone knows if Campaign Determination for Pricing is only for Campaign for category Trade Promotion only ? So how about Campaigns ? How does Campaign Determination for Pricing work ? Using Events?
Regards,
Niversphere.

hi
for that you need to get through the difference between the campaign and TP,the only thing that is different in Tp is that it is for particular account type,due to this particular property of Tp the campaign determination is triggered for TP by default
but you can trigger campaign also by setting your condition types,then assocate those condition with the access sequence,the system will look through the sequence for the condition type,and based on the condition you have maintained the campaign is triggered.
the condition table by default fill the value for Trade Promition and when you do campaign determiantion the system pick the value from the table and that valuse is for TP only,that is the reason for Tp determination.
but as i said you can determine campaign by the above said way of mine.
guess it will help you
i will advise you also study the pricing determination procedure to get better hold of the concept
best bregards
ashish

Explain me about cost in explain plan.

Hi All,
Please explain me about cost in explain plan.
Below is my explan plans
1. first plan showing cost is more but query is returing the result very fast (564 msecs ) --- local database.
2. second plan showing less cost but result is very slow (14 secs) .
1. local database.
PLAN_TABLE_OUTPUT
| ID | Operation                         | NAME                      | ROWS | Bytes | COST |
|   0 | SELECT STATEMENT                  |                           |    17 | 2312 |    60 |
|   1 | SORT UNIQUE                      |                           |    17 | 2312 |    59 |
|   2 |   COUNT STOPKEY                   |                           |       |       |       |
|   3 |    NESTED LOOPS                   |                           |    17 | 2312 |    58 |
|   4 |     MAT_VIEW ACCESS BY INDEX ROWID| MV_EDECO_ESONGS           |    17 | 1326 |    24 |
|   5 |      INDEX RANGE SCAN             | IDX_ESNG_REG_TITLE        |    21 |       |     3 |
|   6 |     TABLE ACCESS BY INDEX ROWID   | MV_EDECO_ESONGS_TERR_CTRY |     1 |    58 |     2 |
|   7 |      INDEX UNIQUE SCAN            | IDX_ESNG_TERR_ESNG_ID_1   |     1 |       |     1 |
PLAN_TABLE_OUTPUT
| ID | Operation                         | NAME                       | ROWS | Bytes | COST |
|   0 | SELECT STATEMENT                  |                            |     9 | 1260 |    34 |
|   1 | SORT UNIQUE                      |                            |     9 | 1260 |    33 |
|   2 |   COUNT STOPKEY                   |                            |       |       |       |
|   3 |    NESTED LOOPS                   |                            |     9 | 1260 |    32 |
|   4 |     MAT_VIEW ACCESS BY INDEX ROWID| MV_EDECO_ESONGS            |     9 |   720 |    14 |
|   5 |      INDEX RANGE SCAN             | IDX_ESNG_REG_TITLE         |    11 |       |     3 |
|   6 |     MAT_VIEW ACCESS BY INDEX ROWID| MV_EDECO_ESONGS_TERR_CTRY |     1 |    60 |     2 |
|   7 |      INDEX UNIQUE SCAN            | PK_EDESONGSTERCTRY_ESONGID |     1 |       |     1 |
------------------------------------------------------------------------------------------------Regards,
Rajasekhar

rajasekhar_n wrote:
Hoek, I have cross checked the results both the querys are precessing same records and returing same result *(both are using DB links).*But you said the first query was on a local database?
If you're using dblinks then it's not local is it! ?:|

Please tell me about Enhancement Technique like BTE , SET and Formula

Hi Experts .
Please guide me about Enhancement Techniques used in SAP apart from BADI/User-Exit .
1.) what is set and how to create it ?
2.) What is formula is SAP and How to set it for Enhancement Pupose .
3.) What is BTE (Buisness Transection Events) ? How to create it for Enhancement Pupose ?
Please Elabarate the reply with step by step procedure .
Thanx .
Regards : Rajneesh

Hi rajneesh mittal ,
Business Transaction Events
Business Transaction Events (Open FI) The Open FI enhancement technique was developed in the Financial Accounting component. Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically. This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
SAP business transaction events are one type of customer enhancements provided by SAP! We can access the business transaction events using FIBF.Next we have to find the process interface for duplicate invoice check!
check this blog for details on SAP business transaction events
Business Transaction Events
Business Transaction Events
http://fuller.mit.edu/user_exits/business_transaction_event.htm
FI Enhancement Technique How-To-Guide on the Usage of Business Transaction Events (BTE)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
Creation of Events via Business Transaction Events
http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm
In SAP R/3 you must activate the business transaction events (BTEs) for Availability Check Using SAP R/3. To set this indicator in SAP R/3:........
http://help.sap.com/saphelp_crm40/helpdata/en/b6/de3efc6bbcdc4b948d466857a10323/content.htm
cheers!
gyanaraj
****Pls reward points if u find this helpful

Ledger printing procedure in sap for statutory authority

hi gurus,
please tell me the ledger printing procedure in sap for statutory authority.
sumit

hi,
There is one way standard SAP B1,create a print layout designer(PLD) for ar invoice(non EDI customer), set the template as default for non EDI customers,this way,
Create user defined field and set a flag as 'Y' or 'N'(apply formatted search)
based on EDI/Non EDI customer,
create another template for EDI customer,apply formulas in PLD to blank all fields in PLD.
Hope it will solve problem.
Jeyakanthan

Please explain about LAST_OPERATION_FAILED

Hi all,
Please explain about the parameter LAST_OPERATION_FAILED.
and if I found this warning message in DB16 what is the procedure or actions we need to take?
Thanks&Regards,
Prakash

Hi,
This condition checks whether the last DBA operation, which isidentified by a function ID specified in the OBJECT field of the DBCHECKORA table, has failed.
This condition has no checking operands, threshold values and value units.
Caution: In SAP Releases 4.0 and 4.5, where the OBJECT field is not yet defined in DBCHECKORA, you can define this condition by specifying the function ID in the PARAM field. You also have this option in later releases.
Regards
Ganesh

Please explain me about pricing determination procedure in SAP SD ?

Similar Messages

Maybe you are looking for