Number of procedures and linie in procedures.

Hi,
I have to know how many procedures and functions are in my database. Furthermore, how many lines they have together. Is that possible from Oracle system's views?
Thanks for help.

select owner, name, type, count(*) from all_source group by owner, name, type;
user_source if you want to restrict to source owned by the schema.
all_arguments/user_arguments if you want to see public procedures/functions and their arguments.

Similar Messages

Diff, bet general SD pricing procedures and Internet Pricing procedure

Hi,
Will any one give clear picture about the diff, between SAP SD pricing procedure and Internet Pricing Procedure? and what are the areas it differs?. If you mail me any URL / Doc regarding Internet Pricing Procedure Configuration that will be of great help.
[email protected]

I hope by internet pricing procedure you mean pricing procedure used in Internet Sales / CRM Online.
Basically, there are no differences. Structure is same. The way pricing procedure is defined & used is same. The only different I would say is, the way you write code for formula & requirements. Usability-wise, they both are same.
Hope it helps.
Regards,
Kaushal

Difference between Sampling Procedure and Sample-drawing procedure

Friends,
I am new to QM and started learning QM Module. My doubt is what is the difference between Sampling Procedure and Sample-drawing procedure?
The reason for my doubt is, we can determine the sample quantity with Sampling procedure itself. then what is the need of sample-drawing procedure?
Also describe primary, pooled and reserved samples.
Regards,
IMIMINT

Hi,
Sampling Procedure
Definition
A procedure that contains the rules for determining the sample size for an inspection. The sampling procedure also specifies the type of valuation to use for results recording (attributive, variable, or manual).
Use
You assign a sampling procedure to each characteristic in an inspection plan to calculate the sample size.
Sample-Drawing Procedure
Definition
A master data object in which you plan the drawing of physical samples. In the sample-drawing procedure, you specify:
Which categories of physical samples must be drawn
How many physical samples must drawn
The size of each physical sample
Whether the drawing of physical samples must be confirmed
Use
The system uses the information in the sample-drawing procedure together with the information in the inspection plan to calculate the physical sample sizes, and to create physical-sample records when an inspection lot is created.
Primary Sample : It is the sample drawn from the lot directly.
Pooled Sample : It is the sample whcih is combination of 2 or more primary samples.i.e. primary sample sfrom say 3 differetn drums is mixed and tested.
Reserved Sample :sample which is preserved for the testing in future.
or in other words
Primary samples (1st stage)
Physical samples drawn directly from a material or batch that will be inspected or used to create pooled samples.
Pooled samples (2nd stage)
Physical samples to be created by mixing the contents of two or more primary samples from the same material or batch.
Reserve samples
Primary physical samples drawn from a material or batch reserved for future inspection.
Vishal
Edited by: VISHAL JONNALWAR on Feb 4, 2010 6:43 AM

Tax Procedures and MM pricing procedures

Currently when creating a PO under the invoice tab you can input the Tax code and jurisdiction code.
The tax code I am using is set up for a Canadian Tax procedure (TAXCAJ).
The procedure is calling two tax condition types JC1E (GST) and JC1I (PST). They are both condition class D and they are the same accross other statistics but they differ in condition category. JC1E is condition category 1 and JC1I is condition category 2.
JCIE uses account determination VST while JC1I uses NVV. JC1E needs to be posted to a seperate account as it is partially recoverable.
The real underlying issue here is that tax condition type JC1I comes accross to teh MM condition tab under NAVS but JC1E does not. I need the value from JC1E to come over to the conditions tab as my PO print is driven by this.
Any ideas how to get tax condition type JC1E (or its value) over to the conditions tab. I can make JC1E come over with JC1I but i need JC1E seperate. If you need clarification or more information just let me know.

Hi,
NAVS condition collects the non-deductible portion of the Tax Code and hence only showing JC1I which is a non-deductible condition type. The logic behind this is non-deductible tax is part of cost, so for updating the stock account at the time of GR with base value + discounts and other pricing conditions + non-deductible tax, NAVS condition type is being used in PO pricing procedure. JC1E is a deductible type tax and as not being a part of cost it is not updated in NAVS and hence the stock account at the time of GR.
If you want all the tax amounts for PO printing purpose, use JEXS condition type and insert this at the last of the pricing procedure with statistical indicator. Modify your print program to print value against JEXS instead of NAVS.
regards,
mallik

Support a singly report on SQL Stored Procedure and Oracle Stored Procedure

Hi,
I have a requirement in which I need to create a report that will run both on oracle and sql server.
Report is designed as follows.
Main report contain 2 sub-reports.Sub-reports are based on stored procedure that takes three input parameters(beginDate,endDate and hostname which is a comma-separated string).
Main report also have three parameters (beginDate,endDate and hostnameList) that I am linking with both sub-reports.
Since the crystal picks the same name of the parameter as we define in procedure it showing '@' symbol in all the parameters when I change the datasoure from oracle to sql server and that's why sub reports defined in main report loose all the linking and same happens when I switch from sql to oracle since in case of oracle it does not have '@' symbol in variable name.
How can I have one report that work with both DBs without loosing the links.
Any help will be appreciated.
Thanks,
Amrita

There is no way of doing this in CR. At least not that I've ever heard of anyway.
If you REALLY need to make this work and it REALLY has to be just 1 report... Here is what I'd do...
In the SQL Server database, add a new table that contains the same columns that are being returned by the sp's. If you can't add new tables to the database, use a different database or server...
Create a Linked Server linking the Oracle db to SQL Server. (If you take the 3rd server rout, do the same with the SQL Server)
Write a new sp that will accept the {?WhichServer} parameter and populate the new table with the result set.
Then just query that table for your report.
I know this probably isn't the rout you were wanting to take but it should work...
Jason

Help on Procedure and trigger for updating(urgent please)

SQL> / Table A
CTUT_ID CTUT_COMPANY_NAME CURRT_USER_ID FMIS_ID CREATE_DA UPDATE_BY UPDATE_DATE
1234 A 15-APR-03
2222 B 15-APR-03
3333 C 15-APR-03
4444 D 15-APR-03
5555 E 15-APR-03
6666 F 15-APR-03
150282 G oRACLE 23-APR-03
1 H 15-APR-03
2 I 15-APR-03
3 J 15-APR-03
150343 K TIGER 24-APR-03
150305 L EXAMPLE 23-APR-03
150342 M SCOTT 24-APR-03
sQL >/ Table B
Empno Empname UPDATE_BY UPDATE_DATE
1 AA
2 BB
3 CC
4 DD
What i need to do is i need to create an update trigger on both tables
like create a procedure
1)In procedure i need to check like
IF TABLEA.CURRT_USER_ID = (SELECT USER FROM DUAL)
THEN
UPDATE_BY = (CURRENT_USER_ID of CTUT_ID)
FOR EXAMPLE CURRENT USER_ID IS SCOTT THEN
UPDATE_BY = 150342
UPDATE_DATE = SYSDATE
ELSIF
UPDATE_BY <=> (CURRENT_USER_ID of CTUT_ID)
THEN
MESSAGE('USER IS NOT IN TABLE);
END IF;
and call that procedure in the update triggers
FOR BOTH TABLES TABLEA,TABLEB
i CREATED A PROCEDURE BUT IT IS NOT WORKING
ANY HELP PLEASE
CREATE OR REPLACE PROCEDURE UPDATE(
UPDATE_DATE out DATE,
UPDATE_BY out VARCHAR2)
IS
Uuser varchar2(20);
Udate date;
Ufound number(1);
BEGIN
SELECT USER,SYSDATE
INTO Uuser,Udate from dual;
SELECT count(*),CTUT_ID into Ufound,Uctut_id
FROM TABLEA
WHERE CURRT_USER_ID = Uuser
Group by Ctut_id;
IF (UFOUND = 1) THEN
UPDATE_DATE := UDATE;
UPDATE_BY := UCTUT_ID;
END IF;
EXCEPTION WHEN NO_DATA_FOUND THEN
RAISE_APPLICATION_ERROR(-20001,'User Does not Exist');
END UPD_CONSTITUENT;
CREATE A TRIGGER :
CREATE OR REPLACE TRIGGER TU
BEFORE INSERT ON TABLEA
FOR EACH ROW
BEGIN
UPDATE(:NEW.update_date,
 :NEW.update_BY);
END IF;
END;
SQL> update TABLEA
2 set CTUT_COMPANY_NAME = 'SCOTT TEST'
3 WHERE FMIS_USER_ID = 'N';
update TABLEA
ERROR at line 1:
ORA-04091: table TABLEA is mutating, trigger/function may not see it
ORA-06512: at "UPDATE", line 12
ORA-06512: at "TU", line 1
ORA-04088: error during execution of trigger 'TU'

Hi Mara,
You are right thats what i want
I have a table A
EmpNo Empname Currtuser_id Update_date Updateby
1 Denis Oracle
2 Scott Scott
3 Mara MMara
1)what i need to do is when any user tries to update the table Table A
Then the Trigger or procedure should check whether user is exits in table A in column currtuser_id
If his user id exits in table A
Then allow him to update the TABLE A
and insert his EMPNO in UPDATE_BY
and SYSDATE in UPDATE_BY
He will do all this process using forms
But i need to have trigger or procedure in database level for table
2) I have another table like 10 tables
Suppose TABLE B
When user tries to update TABLE B
Then the Trigger or procedure should check whether user is exits in table A in column currtuser_id
If his user id exits in table A
Then allow him to update the TABLE B
and insert his EMPNO in UPDATE_BY
and SYSDATE in UPDATE_BY
3) I need to have a common Procedure and call that procedure in all tables in UPDATE TRIGGER
Thanks for your help
Thanks

Relation between Tax procedure and Pricing procedure

Dear All,
I would like to get more clarity on Tax procedure, Pricing procedure.
a) Why do we have Tax procedure and assigned to Country?
b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module? We are even creating lot of pricing procedure for Sales in SD module.
Regards
Manivannan R

Hi
Tax
During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
Tax codes are the link between pricing procedure and tax calculation procedure.
Pricing
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
Example
Example of a Pricing Procedure
If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
Pricing Procedures in the R/3 System
The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
Creating and Maintaining Pricing Procedures
You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
To reach the pricing procedure screen from SD Customizing:
1. Choose Basic Functions
2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

Dynamically calling stored procedure and getting result set c++

Hello,
I am trying to write some c++ code that will dynamically bind values to a stored procedure and excute the procedure and get back a resultset. The problem I am running into is how to get back the resultset. Any help or example would be highly appreciated.

int main(int argc, char* argv[])
OCIError* pOciError;
char* pConnectChar = "dbname";
char* pUsernameChar = "scott";
char* pPasswordChar = "tiger";
int answer;
OCIStmt* pOciStatement;
char* sqlCharArray = "BEGIN :success := sp_ListEmp; END;";
int id;
char ename[40];
OCIEnv* g_pOciEnvironment = NULL;
OCIServer* g_pOciServer = NULL;
OCISession* g_pOciSession = NULL;
OCISvcCtx* g_pOciServiceContext = NULL;
sb2* pIndicator=0;
sb2* pIndicator2=0;
sb2* pIndicator3=0;
OCIDefine* pOciDefine;
OCIDefine* pOciDefine2;
OCIBind* pBind;
OCIStmt* cursor;
answer = OCIInitialize(OCI_THREADED, NULL, NULL, NULL, NULL);
answer = OCIEnvInit(&g_pOciEnvironment, OCI_DEFAULT, 0, NULL);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&pOciError, OCI_HTYPE_ERROR, 0, NULL);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciSession, OCI_HTYPE_SESSION, 0, NULL);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciServer, OCI_HTYPE_SERVER, 0, NULL);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciServiceContext, OCI_HTYPE_SVCCTX, 0, NULL);
answer = OCIServerAttach(g_pOciServer, pOciError, (unsigned char *)pConnectChar, strlen(pConnectChar),
OCI_DEFAULT);
answer = OCIAttrSet(g_pOciSession, OCI_HTYPE_SESSION, (unsigned char *)pUsernameChar, strlen(pUsernameChar),
OCI_ATTR_USERNAME, pOciError);
answer = OCIAttrSet(g_pOciSession, OCI_HTYPE_SESSION, (unsigned char *)pPasswordChar, strlen(pPasswordChar),
OCI_ATTR_PASSWORD, pOciError);
answer = OCIAttrSet(g_pOciServiceContext, OCI_HTYPE_SVCCTX, g_pOciServer, 0, OCI_ATTR_SERVER, pOciError);
answer = OCIAttrSet(g_pOciServiceContext, OCI_HTYPE_SVCCTX, g_pOciSession, 0, OCI_ATTR_SESSION, pOciError);
answer = OCISessionBegin(g_pOciServiceContext, pOciError, g_pOciSession, OCI_CRED_RDBMS, OCI_DEFAULT);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)(&pOciStatement), OCI_HTYPE_STMT, 0, NULL);
answer = OCIStmtPrepare(pOciStatement, pOciError, (unsigned char *)sqlCharArray, strlen(sqlCharArray),
OCI_NTV_SYNTAX, OCI_DEFAULT);
answer = OCIHandleAlloc(g_pOciEnvironment, (void **)(&cursor), OCI_HTYPE_STMT, 0, NULL);
answer = OCIBindByPos(pOciStatement,&pBind, pOciError, 1, &cursor, 0,SQLT_RSET,
pIndicator2, 0,NULL, 0,0,OCI_DEFAULT);
answer = OCIStmtExecute(g_pOciServiceContext, pOciStatement, pOciError, 1, 0, NULL, NULL,
OCI_COMMIT_ON_SUCCESS);
answer = OCIDefineByPos(cursor,&pOciDefine, pOciError,2,&id,sizeof(int),
SQLT_INT,pIndicator, 0, 0,OCI_DEFAULT);
answer = OCIDefineByPos(cursor,&pOciDefine2, pOciError,1,ename,40,
SQLT_STR,pIndicator3, 0, 0,OCI_DEFAULT);
if (answer == 0)
while ((answer = OCIStmtFetch(cursor,pOciError, 1,OCI_FETCH_NEXT,OCI_DEFAULT)) == 0)
printf("fetched id %d and name %s\n",id,ename);
answer = OCIHandleFree(pOciError, OCI_HTYPE_ERROR);
return 0;

SPL determination procedure and control procedure

Hello all
Can someone help me in understanding what a determination procedure and a control procedure means during SPL screening ? How these two are linked , during "configuring the SPL check algorithm" .?
How is the spl determination procedure is linked to the document type ? ( As i see that there are already standard determiantion procedures for each service eg: 1 : lespl for SPL check
2: leldt for licence det ..... etc
when a document is sent from R/3 to GTS how does the system identifies the procedure that it has to go with ? for eg lespl or leldt..
Thanks alot ..

Hi
Det Procedure
We define the Det procedures to use to determine the active legal regulations for a particular service like SPL. We define the determination stratgey for Det proc. to determine the Leg reg.
Control Procedure for Address comparison:
We define a control procedure to determine the rules according to which the system performs sanctioned party list (SPL) checks, this tell what exact detail has to be chekced for SPL like name , city and so on in an address and set rule for how the string of address will be checked against SPL data.
How is the spl determination procedure is linked to the document type ? ( As i see that there are already standard determiantion procedures for each service eg: 1 : lespl for SPL check
2: leldt for licence det ..... etc
Ans :
SPL det Proc determines the Leg reg which can be for SPL or Embargo . And for each service we like SPL we have document type activated this was Det Proc get related to Doc type.
when a document is sent from R/3 to GTS how does the system identifies the procedure that it has to go with ? for eg lespl or leldt..
Ans:
Each doc type coming from a Feeder system is assigned to Document type defined and activated for a particualr service like SPL , and also we actiavte Det Proc separatley for eac servces like SPL.
When ever a doc comes to GTS it get determined to which GTS doc type it is assigned and that then it is determined under what service that GTS doc type is defined.
Suppose OR is assigned to EXORD1 ( GTS doc type) and this doc type comes under SPL so now the configuration for SPL will have particualr Det Procedure actiavted.
Hope this helps
Kind Regards,
Sammer

Can anyone explain me the procedure and initial settings to do sto for schedule lines?

can anyone explain me the procedure and initial settings to do sto for schedule lines?
Create a STO with new doc type for material M1 to ship from plant 1 to plant 2 with qty as 100. On pressing enter you should be able to see schedule lines in delivery schedule tab. In schedule line you should see the Material availability date, GI date, loading date etc.
can anyone give the answer for this question..

Hi Megha,
Please find below links for Config STO with schedule lines.
http://dhavalatsap.blogspot.sg/p/configuration-of-plant-to-plant-sto.html
https://scn.sap.com/thread/1260375
Thanks,
Bala.

Calculate the total value of payments with the procedures and triggers?

Hello!
I work for a college project and I have a big problem because professor requires to do it by the examples he gives during the lecture. Here's an example that should be applied to its base, so please help!
I have three table with that should work:
Invoice (#number_of_invoices, date, comm, total_payment, number_of_customer, number_of_dispatch)
where:
number_of_invoices primary key (number),
date (date),
comm (var2),
total_payment is UDT (din - currency in my country) - in this field should be entered value is calculated
number_of_customer and number_of_dispatch (number) are foreign keys and they are not relevant for this example
Invoice_items (#serial_number, #number_of_invoices, quantity, pin)
serial_number primary key (number),
number_of_invoices primary key (number),
quantity (number),
pin foreign keys (number)
Item (#pin, name, price, tax, price_plus_tax)
pin primary key (number),
name (var2),
price, tax, UDT (din) not relevant for this example
price_plus_tax UDT (din)
These are the triggers and procedures with my calculation should be done:
trigger1:
CREATE OR REPLACE TRIGGER "trg1"
BEFORE INSERT OR UPDATE OR DELETE ON Invoice_items
FOR EACH ROW
BEGIN
 IF (INSERTING OR UPDATING)
 THEN
 BEGIN Invoice_items.number_of_invoices := :NEW.number_of_invoices; END;
 ELSE
 BEGIN Invoice_items.number_of_invoices :=: OLD.number_of_invoices; END;
 END IF;
END;trigger2:
CREATE OR REPLACE TRIGGER "trg2"
AFTER INSERT OR UPDATE OR DELETE ON Invoice_items
DECLARE
doc NUMBER := Invoice_items.number_of_invoices;
BEGIN
 entire_payment (doc);
END;procedure
CREATE OR REPLACE PROCEDURE "entire_payment" (code_of_doc IN NUMBER) AS
entire NUMBER := 0;
BEGIN
 SELECT SUM (a.price_plus_tax * i.quantity) INTO entire
 FROM Item a join Invoice_items i on (a.pin = i.pin)
 WHERE number_of_invoices = code_of_doc;
 UPDATE Invoice
 SET total_payment = entire
 WHERE number_of_invoices = code_of_doc;
END;As you can see the procedure is called from the triggers, I have a problem at the first trigger, and I think it will be even higher in procedure because UDT, field "total_payment".

I was not here a few days because I was trying to get additional information related to this problem. Professor gave me the information that I need to introduce a package and variable to get this thing work. But including that I still have problem. I hope that this time is less of a problem and that someone will be able to help me.
I also noticed that it was not a smart idea to try to translate the names of tables and attributes. That make trouble for me, especially you who are trying to understand and to help me, and absolutely nothing that will change the attribute and the table name will be. So this time I will set out the problem with the original name again to avoid confusion.
So, I try to base Implement optimization technique called: Repeating Single Detail with Master (so writes the slides that I received from professor, I hope that will mean something to you)
These are the lines of code that we get on the slides and should implement in the base, again I remind you that at this time in its original form, without translation.
- First create the package variable:
create or replace
package paket
AS
sifra number(10):=0;
end;This part is ok and it works.
- Secondly, it is necessary to create the first trigger:
create or replace
TRIGGER aktuelna_cena1
BEFORE INSERT OR UPDATE OR DELETE ON cena_artikla
FOR EACH ROW
BEGIN
 IF (INSERTING OR UPDATING)
 THEN
 BEGIN paket.sifra := :NEW.sifra_artikla; END;
 ELSE
 BEGIN paket.sifra := :OLD.sifra_artikla; END;
 END IF;
END;This part is ok and working.
Now the problems begin.
- It is necessary to create another trigger that will call the procedure:
create or replace
TRIGGER aktuelna_cena2
AFTER INSERT OR UPDATE OR DELETE ON cena_artikla
DECLARE
 s NUMBER := paket.sifra;
BEGIN
 aktuelnacena (s);
END;I suppose the trigger have problem because procedure is not ok.
I will copy error that I get from the compiler:
Error(7,2): PL/SQL: Statement ignored
Error(7,2): PLS-00905: object NUMBER6.AKTUELNACENA is invalid
And finally, it is necessary to create the procedure:
create or replace
PROCEDURE aktuelnacena (SifraPro IN NUMBER) AS
aktCena artikal.aktuelna_cena%type;
BEGIN aktCena:=0;
 SELECT cena INTO aktCena
 FROM cena_artikla
 WHERE sifra_artikla=SifraPro and datum_od=
 (select max(datum_od)
 from cena_artikla
 where sifra_artikla = SifraPro and datum_od<=sysdate);
 UPDATE artikal
 SET aktuelna_cena = aktCena
 WHERE sifra_artikla = SifraPro;
END;I will copy error that I get from the compiler:
Error(10,57): PLS-00103: Encountered the symbol " " when expecting one of the following: ( begin case declare end exception exit for goto if loop mod null pragma raise return select update while with << continue close current delete fetch lock insert open rollback savepoint set sql execute commit forall merge pipe purge The symbol " " was ignored.
Tables I work with are:
Artikal (sifra_artikla, naziv, aktuelna_cena),
Cena_artikla (sifra_artikla, datum_od, cena)
You will notice that this differs from the first problem, but my task is to implement the two optimization techniques and my base. Both techniques are quite similar and I hope that I now have enough information to help me. I suppose that when this problem is solved the othet one will too!
Thank in advance!

Tuning a procedure and using dbms_job.submit proc that call's functions

Hi
I have Procedure that have 3 curosrs which are nested one below with in each other
and it looks as below
it's structure will look some thing look like this
declare
empno_fetch number;
CURSOR deu_process IS
SELECT empno
FROM emp
WHERE flg_process = 'N'
AND ROWNUM <= 5000
ORDER BY empno;
CURSOR dup_all IS --c1 fetch around 400000 records
(select empno
from emp
where empno>l_empno
order by empno
where rownum<=empno_fetch;
CURSOR rules IS --c2
SELECT rule_id, rule_score, name_Of_func
FROM rule;
begin
l_count := 1;
OPEN dedupe_rule_attr;
LOOP
BEGIN
Here one loop is used for fetching 5000 records at time and
Here deu_process cursor is opened ,assume it fetches one record
Here another cursor dup_all is used for fetching the records and assume it fetched 400000 then
Here another cursor is opened name where it fetches 10 rows
Here logic is if first row then
call's stored function which has following functionalty
it compares fields such as address of outer most cursor i.e deu_process with all the address of the other rows i.e 400000 rows and return a number
if second row then
call's another stored function which has
compares other fields such as first name,last name
if third then other field
so on ....
up to 10
and then finally ends
so if i comment all the rules loop then it takes only one min to execute .If it validaes all of them if takes 14 minutes to execute .so there is problem in that 10 procedures to execute
So i found an approach to run all the rules simultaneously using dbms_job .But i face a problem that i can't uderstand how to send the input and out put parameter's to calling procedure.And these parameter's must be passed by variable from called procedure to calling procedure
Please suggest me what is the syntax of dbms_job with input and output parameters with variable's that must be passed as formal parameter's
Regarding DBMS_JOB.SUBMIT I am getting following error
Declare
x number:=1;
b number;
jobnumber number;
BEGIN
DBMS_JOB.SUBMIT(JOB => jobnumber,
WHAT => 'vamsi_proc1('||x||');',
NEXT_DATE => (sysdate+1/(86400)),
INTERVAL => null);
--dbms_output.put_line('value of b is '||b);
COMMIT;
END;
Declare
ERROR at line 1:
ORA-06550: line 1, column 107:
PLS-00103: Encountered the symbol ")" when expecting one of the following:
( - + case mod new not null others <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
The symbol "null" was substituted for ")" to continue.
ORA-06512: at "SYS.DBMS_JOB", line 79
ORA-06512: at "SYS.DBMS_JOB", line 136
ORA-06512: at line 5
create or replace procedure vamsi_proc1(v in out number) as
x number(4);
begin
--a:=1;
insert into emp_vamsi(select 677,ENAME,SAL,DEPTNO,MANAGER from emp where empno=v);
commit;
--a:=2;
--x:=a;
end;
using dbms_job.submit proc that call's functions which returns out and in parameters to calling procedure environment .I can't get this with out using data base table's.
If you have any method for this Plese suggest
And also please suggest me weather using job's is a good idea ,If not than suggest me what ever will the other approach.
Thank's and Regard's
vamsi krishna

Hi 
I have looked at all sql trace file , 
I found that there is no problem in sql statemens all of them are using proper indexes execpt the folllowing statement 
 
SELECT nvl(COUNT(ref_appln_no),0) 
FROM ci_cust_dedupe_mast 
WHERE flg_mnt_status='A' 
 
This statement executes only once for 1*3,77000*10 times 
The function that i had sent previously executes more than 4000000*20 times . 
I think all it takes is only for iterations that are caused 
 
I am also sending sql trace for reference
 
TKPROF: Release 9.2.0.4.0 - Production on Mon Aug 14 17:30:50 2006 
 
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. 
 
Trace file: afhuat_ora_2204.trc 
Sort options: default 
 
******************************************************************************** 
count = number of times OCI procedure was executed 
cpu = cpu time in seconds executing 
elapsed = elapsed time in seconds executing 
disk = number of physical reads of buffers from disk 
query = number of buffers gotten for consistent read 
current = number of buffers gotten in current mode (usually for update) 
rows = number of rows processed by the fetch or execute call 
******************************************************************************** 
 
alter session set sql_trace=true 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 0 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 1 0.00 0.00 0 0 0 0 
 
Misses in library cache during parse: 0 
Misses in library cache during execute: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 
******************************************************************************** 
 
declare 
x varchar2(100); 
y varchar2(100); 
ap number; 
begin 
x:=to_char(sysdate,'dd-mon-rrrr hh:mi:ss'); 
ap:=ap_ci_dedupe_proc; 
y:=to_char(sysdate,'dd-mon-rrrr hh:mi:ss'); 
dbms_output.put_line(x||' '||ap); 
dbms_output.put_line(y||' '||ap); 
end; 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 820.23 0 0 0 1 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 2 0.00 820.23 0 0 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 
******************************************************************************** 
 
select user# 
from 
sys.user$ where name = 'OUTLN' 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.00 0 2 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.00 0 2 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS BY INDEX ROWID USER$ (cr=2 r=0 w=0 time=31 us) 
1 INDEX UNIQUE SCAN I_USER1 (cr=1 r=0 w=0 time=18 us)(object id 44) 
 
******************************************************************************** 
 
SELECT * 
FROM ci_dedupe_rule_attr 
ORDER BY cod_rule_attr_id 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.06 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 21 0.00 0.01 1 3 0 20 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 23 0.00 0.07 1 3 0 20 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT COUNT(1) 
FROM ci_cust_dedupe_mast 
WHERE flg_process = 'N' 
AND 
AND 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.00 0 22 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.00 0 22 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT nvl(COUNT(ref_appln_no),0) 
FROM ci_cust_dedupe_mast 
WHERE flg_mnt_status='A' 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 1.68 3.03 18867 21183 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 1.68 3.03 18867 21183 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT ref_appln_no 
FROM ci_cust_dedupe_mast 
WHERE flg_process = 'N' 
AND 
AND 
AND 
ORDER BY ref_appln_no 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.09 18 43 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.09 18 43 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT 
FROM 
WHERE 
AND 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 377709 8.71 7.64 0 0 0 0 
Fetch 377709 18.18 60.19 19802 1510836 0 377709 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 755419 26.90 67.84 19802 1510836 0 377709 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT NVL(MAX(cod_serial_no),0) + 1 
FROM ci_dedupe_details_mast 
WHERE ref_appln_no = :b1 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.01 2 2 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.01 2 2 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT COUNT(1) 
FROM ci_dedupe_details_mast 
WHERE ref_appln_no = :b1 
AND 
AND flg_mnt_status = 'A' 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.00 0 3 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.00 0 3 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT ref_appln_no FROM 
( 
SELECT ref_appln_no 
FROM ci_cust_dedupe_mast 
WHERE 
AND 
ORDER BY ref_appln_no 
) 
WHERE ROWNUM <= :b2 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 77 0.01 0.00 0 0 0 0 
Fetch 377786 10.21 12.33 908 377865 0 377709 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 377864 10.23 12.33 908 377865 0 377709 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
SELECT cod_rule_id, cod_rule_score, nam_rule_func 
FROM ci_dedupe_rule_defn 
WHERE flg_valid = 'Y' 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 377708 5.50 4.03 0 0 0 0 
Fetch 4154788 62.79 54.04 16 4532496 0 3777080 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 4532497 68.29 58.07 16 4532496 0 3777080 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
select con#,obj#,rcon#,enabled,nvl(defer,0) 
from 
cdef$ where robj#=:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 2 0.00 0.01 1 2 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.01 1 2 0 0 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
select con#,type#,condlength,intcols,robj#,rcon#,match#,refact,nvl(enabled,0), 
rowid,cols,nvl(defer,0),mtime,nvl(spare1,0) 
from 
cdef$ where obj#=:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 2 0.00 0.01 2 4 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.01 2 4 0 0 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
select u.name,o.name, t.update$, t.insert$, t.delete$, t.enabled 
from 
obj$ o,user$ u,trigger$ t where t.baseobject=:1 and t.obj#=o.obj# and 
o.owner#=u.user# order by o.obj# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 3 0.00 0.00 0 0 0 0 
Execute 3 0.00 0.00 0 0 0 0 
Fetch 4 0.00 0.05 6 9 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 10 0.00 0.05 6 9 0 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
0 SORT ORDER BY (cr=1 r=1 w=0 time=4772 us) 
0 NESTED LOOPS (cr=1 r=1 w=0 time=4747 us) 
0 NESTED LOOPS (cr=1 r=1 w=0 time=4744 us) 
0 TABLE ACCESS BY INDEX ROWID TRIGGER$ (cr=1 r=1 w=0 time=4740 us) 
0 INDEX RANGE SCAN I_TRIGGER1 (cr=1 r=1 w=0 time=4736 us)(object id 130) 
0 TABLE ACCESS BY INDEX ROWID OBJ$ (cr=0 r=0 w=0 time=0 us) 
0 INDEX UNIQUE SCAN I_OBJ1 (cr=0 r=0 w=0 time=0 us)(object id 36) 
0 TABLE ACCESS CLUSTER USER$ (cr=0 r=0 w=0 time=0 us) 
0 INDEX UNIQUE SCAN I_USER# (cr=0 r=0 w=0 time=0 us)(object id 11) 
 
******************************************************************************** 
 
select o.owner#,o.name,o.namespace,o.remoteowner,o.linkname,o.subname, 
o.dataobj#,o.flags 
from 
obj$ o where o.obj#=:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 3 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.02 5 9 0 3 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 8 0.00 0.02 5 9 0 3 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 3) 
******************************************************************************** 
 
select col#, grantee#, privilege#,max(mod(nvl(option$,0),2)) 
from 
objauth$ where obj#=:1 and col# is not null group by privilege#, col#, 
grantee# order by col#, grantee# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 3 0.00 0.00 0 0 0 0 
Execute 3 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.01 2 6 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 9 0.00 0.02 2 6 0 0 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
INSERT INTO ci_dedupe_details_mast 
VALUES 
( 
:b6, 
:b5, 
:b4, 
:b3, 
'Y', 
'N', 
'', 
0, 
SYSDATE, 
'A', 
' ', 
:b2, 
'SYSTEM', 
:b1, 
1 
) 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.01 3 3 0 0 
Execute 1 0.00 0.01 4 1 6 1 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 2 0.00 0.02 7 4 6 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
select obj#,type#,ctime,mtime,stime,status,dataobj#,flags,oid$, spare1, 
spare2 
from 
obj$ where owner#=:1 and name=:2 and namespace=:3 and remoteowner is null 
and linkname is null and subname is null 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.01 2 3 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.01 2 3 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
select audit$,options 
from 
procedure$ where obj#=:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.01 3 3 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.01 3 3 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS BY INDEX ROWID PROCEDURE$ (cr=3 r=3 w=0 time=14110 us) 
1 INDEX UNIQUE SCAN I_PROCEDURE1 (cr=2 r=2 w=0 time=13871 us)(object id 115) 
 
******************************************************************************** 
 
select owner#,name,namespace,remoteowner,linkname,p_timestamp,p_obj#, 
d_owner#, nvl(property,0),subname 
from 
dependency$,obj$ where d_obj#=:1 and p_obj#=obj#(+) order by order# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 4 0.00 0.07 8 12 0 3 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.07 8 12 0 3 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
3 SORT ORDER BY (cr=12 r=8 w=0 time=72867 us) 
3 NESTED LOOPS OUTER (cr=12 r=8 w=0 time=72813 us) 
3 TABLE ACCESS BY INDEX ROWID DEPENDENCY$ (cr=4 r=4 w=0 time=41297 us) 
3 INDEX RANGE SCAN I_DEPENDENCY1 (cr=3 r=3 w=0 time=25897 us)(object id 127) 
3 TABLE ACCESS BY INDEX ROWID OBJ$ (cr=8 r=4 w=0 time=31484 us) 
3 INDEX UNIQUE SCAN I_OBJ1 (cr=5 r=2 w=0 time=14872 us)(object id 36) 
 
******************************************************************************** 
 
select order#,columns,types 
from 
access$ where d_obj#=:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 2 0.00 0.02 3 4 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 4 0.00 0.02 3 4 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS BY INDEX ROWID ACCESS$ (cr=4 r=3 w=0 time=27026 us) 
1 INDEX RANGE SCAN I_ACCESS1 (cr=3 r=2 w=0 time=21717 us)(object id 129) 
 
******************************************************************************** 
 
select /*+ index(idl_sb4$ i_idl_sb41) +*/ piece#,length,piece 
from 
idl_sb4$ where obj#=:1 and part=:2 and version=:3 order by piece# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.02 3 7 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 7 0.00 0.02 3 7 0 1 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
0 TABLE ACCESS BY INDEX ROWID IDL_SB4$ (cr=2 r=2 w=0 time=19830 us) 
0 INDEX RANGE SCAN I_IDL_SB41 (cr=2 r=2 w=0 time=19826 us)(object id 123) 
 
******************************************************************************** 
 
select /*+ index(idl_ub1$ i_idl_ub11) +*/ piece#,length,piece 
from 
idl_ub1$ where obj#=:1 and part=:2 and version=:3 order by piece# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.03 3 9 0 2 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 7 0.00 0.03 3 9 0 2 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
0 TABLE ACCESS BY INDEX ROWID IDL_UB1$ (cr=2 r=2 w=0 time=21757 us) 
0 INDEX RANGE SCAN I_IDL_UB11 (cr=2 r=2 w=0 time=21753 us)(object id 120) 
 
******************************************************************************** 
 
select /*+ index(idl_char$ i_idl_char1) +*/ piece#,length,piece 
from 
idl_char$ where obj#=:1 and part=:2 and version=:3 order by piece# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 2 0.00 0.01 2 4 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.01 2 4 0 0 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
0 TABLE ACCESS BY INDEX ROWID IDL_CHAR$ (cr=2 r=2 w=0 time=19465 us) 
0 INDEX RANGE SCAN I_IDL_CHAR1 (cr=2 r=2 w=0 time=19461 us)(object id 121) 
 
******************************************************************************** 
 
select /*+ index(idl_ub2$ i_idl_ub21) +*/ piece#,length,piece 
from 
idl_ub2$ where obj#=:1 and part=:2 and version=:3 order by piece# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.00 0 0 0 0 
Fetch 2 0.00 0.01 2 4 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 6 0.00 0.01 2 4 0 0 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
0 TABLE ACCESS BY INDEX ROWID IDL_UB2$ (cr=2 r=2 w=0 time=15070 us) 
0 INDEX RANGE SCAN I_IDL_UB21 (cr=2 r=2 w=0 time=15066 us)(object id 122) 
 
******************************************************************************** 
 
select baseobject,type#,update$,insert$,delete$,refnewname,refoldname, 
whenclause,definition,enabled,property,sys_evts,nttrigcol,nttrigatt, 
refprtname,rowid 
from 
trigger$ where obj# =:1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.00 1 2 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.00 1 2 0 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS BY INDEX ROWID TRIGGER$ (cr=2 r=1 w=0 time=9352 us) 
1 INDEX UNIQUE SCAN I_TRIGGER2 (cr=1 r=1 w=0 time=9340 us)(object id 131) 
 
******************************************************************************** 
 
select owner# 
from 
obj$ o where obj# = :1 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 1 0.00 0.00 0 3 0 1 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 3 0.00 0.00 0 3 0 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS BY INDEX ROWID OBJ$ (cr=3 r=0 w=0 time=15 us) 
1 INDEX UNIQUE SCAN I_OBJ1 (cr=2 r=0 w=0 time=7 us)(object id 36) 
 
******************************************************************************** 
 
select tc.type#,tc.intcol#,tc.position#,c.type#, c.length,c.scale, 
c.precision#,c.charsetid,c.charsetform 
from 
triggercol$ tc,col$ c ,trigger$ tr where tc.obj#=:1 and c.obj#=:2 and 
tc.intcol#=c.intcol# and tr.obj# = tc.obj# and (bitand(tr.property,32) != 
32 or bitand(tc.type#,20) = 20) union select type#,intcol#,position#,69,0,0, 
0,0,0 from triggercol$ where obj#=:3 and intcol#=1001 union select tc.type#, 
tc.intcol#,tc.position#,121,0,0,0,0,0 from triggercol$ tc,trigger$ tr where 
tr.obj# = tc.obj# and bitand(tr.property,32) = 32 and tc.obj# = :4 and 
bitand(tc.type#,20) != 20 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 0 
Fetch 34 0.00 0.05 8 236 0 33 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 36 0.00 0.05 8 236 0 33 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
33 SORT UNIQUE (cr=236 r=8 w=0 time=54877 us) 
33 UNION-ALL (cr=236 r=8 w=0 time=54606 us) 
33 NESTED LOOPS (cr=197 r=8 w=0 time=53779 us) 
33 NESTED LOOPS (cr=162 r=8 w=0 time=53053 us) 
77 TABLE ACCESS CLUSTER COL$ (cr=83 r=6 w=0 time=40045 us) 
1 INDEX UNIQUE SCAN I_OBJ# (cr=2 r=2 w=0 time=13764 us)(object id 3) 
33 INDEX RANGE SCAN I_TRIGGERCOL2 (cr=79 r=2 w=0 time=12523 us)(object id 133) 
33 TABLE ACCESS BY INDEX ROWID TRIGGER$ (cr=35 r=0 w=0 time=466 us) 
33 INDEX UNIQUE SCAN I_TRIGGER2 (cr=2 r=0 w=0 time=152 us)(object id 131) 
0 INDEX RANGE SCAN I_TRIGGERCOL2 (cr=2 r=0 w=0 time=5 us)(object id 133) 
0 NESTED LOOPS (cr=37 r=0 w=0 time=574 us) 
33 INDEX RANGE SCAN I_TRIGGERCOL2 (cr=2 r=0 w=0 time=81 us)(object id 133) 
0 TABLE ACCESS BY INDEX ROWID TRIGGER$ (cr=35 r=0 w=0 time=350 us) 
33 INDEX UNIQUE SCAN I_TRIGGER2 (cr=2 r=0 w=0 time=139 us)(object id 131) 
 
******************************************************************************** 
 
select grantee#,privilege#,nvl(col#,0),max(mod(nvl(option$,0),2)) 
from 
objauth$ where obj#=:1 group by grantee#,privilege#,nvl(col#,0) order by 
grantee# 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 3 0.00 0.00 0 0 0 0 
Execute 3 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.00 0 6 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 9 0.00 0.00 0 6 0 0 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
UPDATE 
SET 
WHERE ref_appln_no = :b1 
AND flg_mnt_status = 'A' 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.16 9 8 17 1 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 2 0.00 0.16 9 8 17 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
select type#,blocks,extents,minexts,maxexts,extsize,extpct,user#,iniexts, 
NVL(lists,65535),NVL(groups,65535),cachehint,hwmincr, NVL(spare1,0) 
from 
seg$ where ts#=:1 and file#=:2 and block#=:3 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 3 0.00 0.00 0 0 0 0 
Execute 3 0.00 0.00 0 0 0 0 
Fetch 3 0.00 0.01 3 9 0 3 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 9 0.00 0.01 3 9 0 3 
 
Misses in library cache during parse: 0 
Optimizer goal: CHOOSE 
Parsing user id: SYS (recursive depth: 2) 
 
Rows Row Source Operation 
------- --------------------------------------------------- 
1 TABLE ACCESS CLUSTER SEG$ (cr=3 r=3 w=0 time=17332 us) 
1 INDEX UNIQUE SCAN I_FILE#_BLOCK# (cr=2 r=2 w=0 time=10258 us)(object id 9) 
 
******************************************************************************** 
 
INSERT INTO ci_dedupe_details 
VALUES 
( 
:b31, 
:b32, 
:b31, 
:b30, 
:b29, 
:b28, 
:b27, 
:b26, 
:b25, 
:b24, 
:b23, 
:b22, 
:b21, 
:b20, 
:b19, 
:b18, 
:b17, 
:b16, 
:b15, 
:b14, 
:b13, 
:b12, 
:b11, 
:b10, 
:b9, 
:b8, 
:b7, 
:b6, 
:b5, 
:b4, 
:b3, 
:b2, 
:b1, 
'N', 
0, 
'E' ) 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.01 0.03 4 1 5 1 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 2 0.01 0.03 4 1 5 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
select /*+ rule */ bucket_cnt, row_cnt, cache_cnt, null_cnt, timestamp#, 
sample_size, minimum, maximum, distcnt, lowval, hival, density, col#, 
spare1, spare2, avgcln 
from 
hist_head$ where obj#=:1 and intcol#=:2 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 36 0.00 0.00 0 0 0 0 
Fetch 36 0.00 0.02 3 108 0 36 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 73 0.00 0.02 3 108 0 36 
 
Misses in library cache during parse: 1 
Optimizer goal: RULE 
Parsing user id: SYS (recursive depth: 2) 
******************************************************************************** 
 
COMMIT 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 2 0.00 0.01 0 0 1 0 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 4 0.00 0.01 0 0 1 0 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 (recursive depth: 1) 
******************************************************************************** 
 
BEGIN DBMS_OUTPUT.GET_LINES(:LINES, :NUMLINES); END; 
 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 1 0.00 0.00 0 0 0 0 
Execute 1 0.00 0.00 0 0 0 1 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 2 0.00 0.00 0 0 0 1 
 
Misses in library cache during parse: 1 
Optimizer goal: CHOOSE 
Parsing user id: 61 
 
 
 
******************************************************************************** 
 
OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 2 0.00 0.00 0 0 0 0 
Execute 3 0.00 820.23 0 0 0 2 
Fetch 0 0.00 0.00 0 0 0 0 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 5 0.00 820.23 0 0 0 2 
 
Misses in library cache during parse: 1 
Misses in library cache during execute: 1 
 
 
OVERALL TOTALS FOR ALL RECURSIVE STATEMENTS 
 
call count cpu elapsed disk query current rows 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
Parse 49 0.00 0.10 3 3 0 0 
Execute 755577 14.25 11.90 17 10 29 3 
Fetch 4910422 92.89 130.18 39671 6442895 0 4532611 
------- ------ -------- ---------- ---------- ---------- ---------- ---------- 
total 5666048 107.14 142.19 39691 6442908 29 4532614 
 
Misses in library cache during parse: 11 
 
17 user SQL statements in session. 
35 internal SQL statements in session. 
52 SQL statements in session. 
******************************************************************************** 
Trace file: afhuat_ora_2204.trc 
Trace file compatibility: 9.00.01 
Sort options: default 
 
1 session in tracefile. 
17 user SQL statements in trace file. 
35 internal SQL statements in trace file. 
52 SQL statements in trace file. 
36 unique SQL statements in trace file. 
5666466 lines in trace file. 
Regards 
vamsi krishna

Pricing procedure and CIN master

Hi MM Gurus,
I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating and can anybody show how the pricing procedure and excise (CIN) is related .
Regards,
Girish.C.M

Hi,
CIN Setting:
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each.
Definition: excise registration
Financial Accounting (FI)
An entity in India that is entitled by law to produce any goods liable to excise.
Each entity is assigned its own excise registration number.
Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Definition: excise group
Financial Accounting (FI)
A unit within an excise registration, in India, which keeps its own set of excise records.
Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
Return ->
Definition: excise group
Maintain Series Groups
Use
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.
Activities
· 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' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
You can then define a default local excise department for each excise group and a default customs department for each series group.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
Select Tax Calculation Procedure
Use
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.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
Define Tax Code for Purchasing Documents
Use
In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
Only carry out this activity if you use condition-based excise determination.
Activities
Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
Assign Tax Code to Company Codes
Use
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
Classify Condition Types
Use
In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
· For taxes on purchases, use the condition types contained in the tax procedure.
· For taxes on sales, use the condition types contained in the pricing procedures.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
Maintain Chapter IDs
Use
In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
Example
· Form type: CT3
· Form description: Concessional tax form
· Status: Receive
Define G/L Accounts for Taxes
Use
In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements
You have set up G/L accounts for each of the processing keys listed below.
Activities
Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
· VS1 (basic excise duty)
· VS2 (additional excise duty)
· VS3 (special excise duty)
· VS5 (sales tax setoff)
· MWS (central sales tax)
· MW3 (local sales tax)
· ESA (service tax)
· ESE (service tax expense)
Specify Excise Accounts per Excise Transaction
Use
In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
If you use subtransaction types, enter the accounts for each subtransaction type as well.
Activities
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example
Excise TT DC ind Account name
GRPO CR CENVAT clearing account
GRPO CR RG 23 BED account
GRPO DR CENVAT on hold account
Specify G/L Accounts per Excise Transaction
Use
In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
· Excise group
· Company code
· Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
· Defined the G/L accounts
· Defined the excise groups
· Maintained the transaction accounts
Activities
For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Define Processing Modes Per Transaction
Use
In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
This way, you can tailor the transaction to what your users have to do.
Standard settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
· J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
· J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
· J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Specify Which Movement Types Involve Excise InvoicesUse
In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Maintain Default Excise Groups and Series Groups
Use
In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
· Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
Maintain the Program, FORM routine, and the form for the output type.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
You can either:
· Debit all the excise duty to one account
· Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
Acct name BED perc.
RG 23A BED account 50
RG 23C BED account 50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
Acct name BED perc. +
RG 23A BED account X
RG 23C BED account X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
Maintain Minimum Balances for Excise Accounts
Use
In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans )
Rewards if Helpful
regards
rb

Reset file name and line number in preprocessor

We are using Sun Studio 12u1 on Solaris x86 10u9.
For one of our large projects our make file copies many C++ source files into one large allsource.cpp file. This results in significantly faster compilation and better inter-procedural optimizations.
Unfortunately, when the compiler generates warning or error messages they refer to allsource.cpp. Also when it comes time to debug, dbx is looking for debugging information for the original source file instead of looking for allsource.o.
On Windows (MSVC), we use the #line directive to reset the line number and filename so that the error messages point to the correct line and number, and so that the debugger knows that the debugging information for myfile.cpp is actually in allsource.o.
Does the Sun compiler have anything similar to the #line directive?

To reset the preprocessor to the start of a new file:
#1 "filename"
where filename is the name or complete path name of the file.
To change the line number within the current file:
#N
or
#line N
where N is an integer
Example:
% cat z.cc
struct S { X x; };
#1 "/foo/bar.h"
Int I;
#500
Float F;
#line 1000
Double D;
88% CC -c z.cc
"z.cc", line 1: Error: Type name expected instead of "X".
"/foo/bar.h", line 1: Error: Int is not defined.
"/foo/bar.h", line 500: Error: Float is not defined.
"/foo/bar.h", line 1000: Error: Double is not defined.
4 Error(s) detected.BTW, you might get a similar improvement in compile time by using precompiled headers.
The -xipo option provide inter-procedural optimization across compilation units. Refer to the C++ Users Guide for details.
We seem to have a bug in the Forum software. My original source code and the compiler output have double quotes ("...") but they show as single quotes in the code brackets.
Edited by: clamage45 on Apr 13, 2010 1:13 PM

How to find proc/func name from package name and line number?

Hi,
We are using the pl/sql call stack dump (dbms_utility.format_call_stack) for some debugging purposes. But in the case of a package body execution, the dump does not return the name of the procedure/function that is being executed, but only the name of the package and the line number being executed. So, we have a requirement wherein we need to extract the type and name of a package subunit from the package name and line number.
e.g.
From the information package 'A', line number 739
we should be able to deduce that line 739 is a part of *'function A.f'*
Does the oracle database provide any native mechanism (PL/SQL packages or otherwise) to support such functionality? If it does not, how can we achieve the desired result?
Thanks in advance,
Shashank

The approach we are currently planning to take up is this :
1. Write PL/SQL code to parse the entire source (user_source) and build a database table with a structure like this :
PACKAGE_NAME | UNIT_TYPE | UNIT_NAME | START_LINE | END_LINE
=============================================
A | PROCEDURE | P1 | 20 | 345
A | FUNCTION | F1 | 347 | 629
etc..
2. Start PL/SQL package execution.
3. Keep dumping call stack snapshots whenever a custom debug procedure is called.
4. Dump the package name and line number to a log file.
5. Using the package name and line number, query the table built in step 1 and build the final report which shows the control flow in a readable form.
What we want is to get rid of step 5 and by some means get the logic to extract the unit type and name in step 4 itself.
Keep them coming..
Thanks and regards,
Shashank

Number of procedures and linie in procedures.

Similar Messages

Maybe you are looking for